Related
I have a htc rhodium 210(t-mobile branded) and i am running the latest xdandroid froyo (as of a few days ago) And iv been gettn a low phone storage space alert in my status bar asking me to uninstall apps wenever i install a new one. Also if i receive messages while this alert is there they are delete due to 'lack of storage' But when i open appmonster to uninstall some apps im told i have used only memory:24mb/247mb SD:1.991/7.560mb and im using an 8gb micro sd which is less than half full so storage shouldnt be a problem?
Any ideas and why im gettn this warning and is there any way to stop it? because i dont have a huge amount of apps and i shouldnt have to keep uninstalling decent apps when i should have enough storage.
tanks in advance
This has been answered several times before...
The data.img file is only 256mb. If you want a bigger one, you have to either expand the file yourself or modify the rootfs so it builds a larger data.img.
For most, 256mb is plenty. Lots of people don't even come close to using that much, plus if the users card was only 512mb, creating a 512mb data.img on boot would be a problem.
Ok tanx, sry if this sounds like a noobish question but how can i expand my data.img file? without creating a new one.
but wait i dont even need a bigger data.img file because it shouldnt be full. It says im only using 24mb outta the 256. And yet it still says low storage and rejects my messages?
Huh... I don't know. I've never had it reject my messages before, or give me that error message.
May want to try the typical troubleshooting crap. Delete (move, rename) data.img, delete everything & start with a fresh build, format SD & start completely over - in that order.
yeah iv tried that, id say my best bet would be to expand the data.img file do you kno any way to do this?
Jandyman said:
yeah iv tried that, id say my best bet would be to expand the data.img file do you kno any way to do this?
Click to expand...
Click to collapse
Either you can expand it manually or modify the rootfs to create a larger one for you.
how can i edit the img files? i have vista and no way of opinging these files. Iv heard you need linux.
Jandyman said:
how can i edit the img files? i have vista and no way of opinging these files. Iv heard you need linux.
Click to expand...
Click to collapse
Yes. Virtual machine to the rescue!
Try cachemate picced up 8mb
Sent from my MSM using XDA App
tanx for the help, iv searced and found no program capable of simply editing the file and saving it bigger so il try my hand at using virtual machine, or a friends netbook running ubuntu to do so. But having little or no knowledge of the layout or coding an whatnot in the files it will probly take some more time and searching to figure out.
also i am now using cachemate also, it doesnt solve my problems but its handy app nonetheless for quick freeing up wen im browsing and get the low storage message.
.. is there a way to make the data.img bigger directly on the PDA? may be with the total commander?
THX
_cv
_cv said:
.. is there a way to make the data.img bigger directly on the PDA? may be with the total commander?
Click to expand...
Click to collapse
Did you think I was joking when I outlined the two methods required to expand the file...?
arrrghhh said:
Did you think I was joking when I outlined the two methods required to expand the file...?
Click to expand...
Click to collapse
sorry, but i thought that there are more solutions and you are talking about two of them.
OK, i understand there is no way on my PDA to make the data.img bigger.
grz
_cv
If you want to make the data.img file bigger than 256mb, I suggest you to use Neopeek's build. It is totally a different setup since neopeek's doesn't use the data.img file. If you want to have more storage, you are gonna have to make the ext2 partition a little bit more bigger using GParted Live, max is 512mb. Right now I have my ext2 partition to 495mb and I have more than 30 app's installed and I haven't gotten one of those messages you get.
Found a post where a guy setup a 4gb data.img...
Here
1 GB rootfs
Here is my modded rootfs.img i use to create a 1GB data.img. Use it will create a 1GB data.img. its only a few days old, but after the data.img is created you can raplace it with the new up-to-date rootfs.img. Hope this works for ya
Note: you must create a fresh Data.img for it to work.
devilcuban said:
Here is my modded rootfs.img i use to create a 1GB data.img. Use it will create a 1GB data.img. its only a few days old, but after the data.img is created you can raplace it with the new up-to-date rootfs.img. Hope this works for ya
Note: you must create a fresh Data.img for it to work.
Click to expand...
Click to collapse
Awesome dude I was hoping someone would post a 1gb one All I could find was that 4gb one haha! Now peoples have choices!
arrrghhh said:
Awesome dude I was hoping someone would post a 1gb one All I could find was that 4gb one haha! Now peoples have choices!
Click to expand...
Click to collapse
haha yea no problem 4GB its alot specially if u only have a few GBs on the SDcard lol, i did a 512mb but my girl downloads 2 many apps lol wasn't enough lol,
devilcuban said:
Here is my modded rootfs.img i use to create a 1GB data.img. Use it will create a 1GB data.img. its only a few days old, but after the data.img is created you can raplace it with the new up-to-date rootfs.img. Hope this works for ya
Note: you must create a fresh Data.img for it to work.
Click to expand...
Click to collapse
So. I just have to delete my data.img. and my rootfs.img. and replace it with yours (rootfs.img)?
sprint htc touch pro 2 (rhod400)
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****​
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content​
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert
I've been wanting to make a larger /data partition on a Droid Incredible. I mean, after all, it comes with a lot of storage. But there is not nearly enough for apps. Sure. I can use my SD card. But unless there is something I'm not aware of, you can only install some apps to the SD and even when you do, pieces of that app still exist in /data. But what's even worse is the fact that I already use my SD card for movies and videos and such and I just don't really use the unclaimed space of which there is plenty, in the phone, for that sort of thing and yet I can't use it to install apps. I haven't found too much on this topic outside of using App2SD. I did find a lot of talk of using parted and even gparted. But this talk is generally about partitioning your SD card. If I were to use parted or gparted to resize the /data partition at the expense of another partition's space and I did it properly, would the Android system not boot because of it? And if this is doable, is there a better, easier way to do it than using parted and adb or gparted? Also, is there a guide for resizing your /data partition? I could probably survive without one if I had to but it would really be helpful just in case there are some big DO NOT DO's that should be avoided that aren't obvious. Any help would be greatly appreciated.
enigmatl said:
I've been wanting to make a larger /data partition on a Droid Incredible. I mean, after all, it comes with a lot of storage. But there is not nearly enough for apps. Sure. I can use my SD card. But unless there is something I'm not aware of, you can only install some apps to the SD and even when you do, pieces of that app still exist in /data. But what's even worse is the fact that I already use my SD card for movies and videos and such and I just don't really use the unclaimed space of which there is plenty, in the phone, for that sort of thing and yet I can't use it to install apps. I haven't found too much on this topic outside of using App2SD. I did find a lot of talk of using parted and even gparted. But this talk is generally about partitioning your SD card. If I were to use parted or gparted to resize the /data partition at the expense of another partition's space and I did it properly, would the Android system not boot because of it? And if this is doable, is there a better, easier way to do it than using parted and adb or gparted? Also, is there a guide for resizing your /data partition? I could probably survive without one if I had to but it would really be helpful just in case there are some big DO NOT DO's that should be avoided that aren't obvious. Any help would be greatly appreciated.
Click to expand...
Click to collapse
theres around 780mb in there thats not enough?
JoelZ9614 said:
theres around 780mb in there thats not enough?
Click to expand...
Click to collapse
He's talking about /data/data/ which is like 150mb, I use the NotEnoughSpace app it lets you store data on cache, emmc, sd card, you should check it out.
Well, I messed with notenoughspace too which was my eason for posting. This was the app that made me say enough is enough, can I just resize /data/data?.
-1- So much space on the incredible is going to waste while programs such as these would have me put apps on the SD where I really do want space for my other stuff like music and movies.
-2- Unless I missed a button or option, NotEnoughSpace came off as annoying to me. I would go into apps and wait for a minute for it to scan every time I do it and then I pick an app, for example Beejive. It makes me move it ONE FILE AT A TIME. And even then, there is stuff you can't move. Can I not just move the app, all of it in one click?
But most importantly, I just want more space on /data/data. I want to resize the partition. The phone has what, 8 gigs on it and allows 150 mb for apps in there which is just crazy.
Can I resize the partition where apps are stored (/data/data) by way of parted or gparted? to avoid the annoyance of using my external storage which I want to use for movies and music? There's probably 6 or so gigs on my phone I'll never use for media that should be meant for apps.
Has anybody resized the data partition? Are there consequences to doing it if it's done properly? Is there a guide? What is the easiest way to do this? Any help would be appreciated.
enigmatl said:
Well, I messed with notenoughspace too which was my eason for posting. This was the app that made me say enough is enough, can I just resize /data/data?.
-1- So much space on the incredible is going to waste while programs such as these would have me put apps on the SD where I really do want space for my other stuff like music and movies.
-2- Unless I missed a button or option, NotEnoughSpace came off as annoying to me. I would go into apps and wait for a minute for it to scan every time I do it and then I pick an app, for example Beejive. It makes me move it ONE FILE AT A TIME. And even then, there is stuff you can't move. Can I not just move the app, all of it in one click?
But most importantly, I just want more space on /data/data. I want to resize the partition. The phone has what, 8 gigs on it and allows 150 mb for apps in there which is just crazy.
Can I resize the partition where apps are stored (/data/data) by way of parted or gparted? to avoid the annoyance of using my external storage which I want to use for movies and music? There's probably 6 or so gigs on my phone I'll never use for media that should be meant for apps.
Has anybody resized the data partition? Are there consequences to doing it if it's done properly? Is there a guide? What is the easiest way to do this? Any help would be appreciated.
Click to expand...
Click to collapse
Ask conap hes good with this type of thing
Making progress but still need help.
There's some talk on the net that you can modify the size of the .img files that nandroid makes and simply flash them back to your phone.
Problem is, I can't find a windows way to do it on the net. The closest that I've come is a program called toporesize. This program will let you open files such as data.img from your nandroid backup. But you can't resize them because you get an error box that says this appears to not be an ext* filesystem. Check size file only to resize the file or use other tools. I'm assuming that means it wants you to check a button that says resize file only no resize2fs. In the one guide I found that talks about this app, it says do not check this box. So I'm assuming if you did, it would work and then when you flashed the file back to your phone, it would either not boot or the size would not be changed properly.
I also noted that there's a thread or two that has posted some custom sized data.img files for download. I would do this as a last resort but would prefer to resize my own data.img for a more precise choice of how large I want it.
The error mentions other tools. Are there other tools or programs for Windows users?
Does anybody have any insight on resizing the /data/data partition either by this method, by using parted/gparted, or any other method that works effectively?
I would avoid trying to alter the size of the partitions on your phone. That is how you end up with a brick. There are other ways including finding out which apps are taking up all of your space. 150 MB does not sound like a lot, but it is considering what is stored there.
Go into Manage Applications and click on the All tab. Then press the menu key and sort by size. Click on the apps near the top with anything higher than 3 or 4 MB. Look at the details in the storage section for each app. You will see a Data line item. If it is really high in proportion of the size of the Application, you should clear it. That will save you a lot of space.
In the case of the Mail app or other social networking apps like Facebook or Twitter, you can go into the settings and restrict how much data is stored on the phone. They can really eat up space by downloading a month of emails, etc ...
ihtfp69 said:
I would avoid trying to alter the size of the partitions on your phone. That is how you end up with a brick. There are other ways including finding out which apps are taking up all of your space. 150 MB does not sound like a lot, but it is considering what is stored there.
Go into Manage Applications and click on the All tab. Then press the menu key and sort by size. Click on the apps near the top with anything higher than 3 or 4 MB. Look at the details in the storage section for each app. You will see a Data line item. If it is really high in proportion of the size of the Application, you should clear it. That will save you a lot of space.
In the case of the Mail app or other social networking apps like Facebook or Twitter, you can go into the settings and restrict how much data is stored on the phone. They can really eat up space by downloading a month of emails, etc ...
Click to expand...
Click to collapse
This request is meant with respect and NOT as a flame but I have to make this request so others don't follow and potentially change the thread into a debate on whether to resize or not resize the partition.
Please let's not start talking about whether this is a good idea or not nor if doing this can make our phone into a brick. Now that it's been said, those lurking and considering this for themselves can make up their own minds. But there are a lot of things talked about throughout XDA that can make your phone into a brick yet things are done in the name of making our devices better.
And yes. We can take action to reduce the amount of data that apps are taking up. To tell you the truth, I would do that even if I had a 1GB partition. I think always saving space when space can be saved is a good idea.
But just in principle, I and probably others want to reclaim that space on our phones that will never be used by anything. Maybe HTC allocated the space as it's allocated because some users won't use an SD card and will then use that space for their media and other miscellaneous stuff.
But once you have an SD card that's way bigger than the extra space on your phone, it becomes pointless to use that space on your phone for media. So I want it available for data.
So both sides of whether to do this or not have now been posed. I ask can we please get back to the topic of how to though I do thank you for your input.
That said, again, does anybody know how to resize your data partition whether by doing it live with parted or gparted or by editing the data.img file that nandroid via clockwork mod puts out? I would really appreciate it.
I tried making a nandroid backup of the phone through clockworkmod, sending the data.img file to my computer, using toporesize to resize it. And by the way, I was forced to check the resize file only no resize2fs button as not doing this generated an error. I then used md5sum to get an md5sum for the new data.img. I then inserted the md5sum in clockwork/nandroid's nandroid.md5 file (with a linux file compatable text editor). I then sent the entire backup back to the phone in a different clockworkmod/backup folder, used rom manager to restore, selected the new resized backup.
After the flashing was complete, I went into my phone only to find that the data partition still had the same amount free (give or take a few K). I wondered if that's because I had to shrink the system file? I was thinking before I started that it's probable that I would have to shrink another partition that had free space so I chose system. I attempted to repeat the above steps from the beginning this time with the plan of shrinking system.img.
No go. toporesize will not shrink it properly. Errors are reported in the process though when I reload it into toporesize, it looks like it has the size I want. Knowing it would probably fail, I tried to continue anyway. Even with the correct md5sum, nandroid won't even start the recovery of that set. You get a status bar for a second and then, the phone just reboots.
So for now, I'm at a loss but I know this can be done.
Whether using this method or another, does anybody know how to properly change the size of the data partition using WINDOWS?
Don't come crying when you brick it.
ihtfp69 said:
Don't come crying when you brick it.
Click to expand...
Click to collapse
I have no intentions of such. -1- I will quite likely never brick it as nandroid pretty much has me covered. But if I do, -2- I don't plan on having this phone forever. It's not new any more. There are already several models that are better than the droid incredible that I'm looking at. If I were to brick this phone, yay. Good excuse to buy a new phone. But, odds are, i'll never brick it and come November or December, I'll buy something else anyhow.
So please, this isn't about the risks, of course you can brick your phone trying this or many other things on XDA.
Does anyone know how to resize the data partition using any method that can be done with the help of a Windows machine?
This is a fundamental change to a very sensitive area you have
276 mb for the system rom and 748mb for user apps.Many rom devs seem to be straining to keep the rom below 200mb and it is amazingly easy to fill up 748 mb with little apps.
I would think if it were possible to do this it would have been done by the rom devs first thing. I would love to see a rom dev bump this to 500mb and 1024mb.
Chances are to re partition the partitions on the phones memory is not possible with out a hboot flash or something of a custom bootloader...
I find removing these help... Also i use handcent and gmail.app instead of the stock apps...
friendstream
peep
twitter
flicker
stocks app
facebook
748 mb? I only have 150 available in /data/data. How do you get 748?
enigmatl said:
748 mb? I only have 150 available in /data/data. How do you get 748?
Click to expand...
Click to collapse
748mb is the size of the entire /data partition what us devs are doing with the new roms is symlinking things to the /system from /data i've managed to do it without symlinking but it bring the /system to its limits and thats usually not good to do
enigmatl said:
748 mb? I only have 150 available in /data/data. How do you get 748?
Click to expand...
Click to collapse
In my /data/data i have 95.96 MB free
rom 35MB free
app space 212 MB free
internal 6.44GB free
Also /data/data is a different partition than /data so the 150 is not included as part of the 748.
Resize /data/data partition - Update?
Did you ever find a solution to resizing the HTC Incredible's partitions?
I too am fed up with having to constantly clear caches and uninstalled apps, just because the tiny 150MB partition fills up. It's been a problem since my wife and I bought our phones.
I expect it would have to be done by a custom bootloader, but thought I would check and see if you had any success.
If nandroid recreates the partition tables based on the sizes of the .img partition backups, then they could probably be resized by mounting the .IMG files directly under Linux and using Linux tools to resize each one - or - creating a new .img partition of the new size(s), mount the backups and copy everything over to the new one, unmount it and go from there?
Steve
Have you used the Ext4 mod created by Tiny and Jermaine151?
http://forum.xda-developers.com/showthread.php?t=1623038
...and the following is the original thread which has the details of what exactly the mod does:
http://forum.xda-developers.com/showthread.php?t=1315372
If I'm reading this (outdated) thread correctly, this mod is what you're looking for in regards to partitioning /data/data. The second link is provided in the OP of my first link.
SlimSnoopOS said:
Have you used the Ext4 mod created by Tiny and Jermaine151?
http://forum.xda-developers.com/showthread.php?t=1623038
...and the following is the original thread which has the details of what exactly the mod does:
http://forum.xda-developers.com/showthread.php?t=1315372
If I'm reading this (outdated) thread correctly, this mod is what you're looking for in regards to partitioning /data/data. The second link is provided in the OP of my first link.
Click to expand...
Click to collapse
What he said ^^^^
Just do it.
I have done wonderful things to my device thanks in large part to this community. Thank you.
I see that the system partition has about 1 GB of free space yet there are only 427 MB of files in there. Do I need that much free space? If not, how can I safely resize it?
Using parted. I've tried doing it though, shrinking my data partition to give more to system but it won't stick for some reason. Either I'm doing it wrong, or it doesn't work
The parted binary for android can be found on Cyanogenmod's github in the android_bootable_recovery repo
@CNexus, thanks. I appreciate that. I'll take a peek at that. Strangely enough I'm looking to shrink my system partition. I've seen others are wanting the opposite.
I've partitioned PC drives before but this appears to be much more involved.
Does anyone know of an optimum allotment for system and cache that I should follow?
You should be fine whatever you do.
Worst case if something goes wrong, just flash the PIT file for your internal storage size in Odin and all should be good
But yes, this will be more involved since it will need to be all command-line
Noogie was the image to put on the NST so that you could backup or restore the entire internal memory.
It was usually put on the removable SD card.
In fact, it could have been just booted directly through fastboot.
Later, people worked on and succeeded on a way to boot up the NST without any valid internal memory at all.
This made the NST unbrickable.
Neo Noogie is pretty much the same, but updated for the Glow2 & Glow3.
Since these models don't have a removable SD card they need to be able to boot over fastboot.
This means that if you totally wipe out the memory on your Nook (including where fastboot is) you'll be bricked.
(That is, until we get working on a USB bootloader method.) We do have a bootloader, see https://forum.xda-developers.com/nook-touch/general/fix-bricked-glow2-3-4-t4002911
Warning: Windows will offer to format anything it doesn't understand! Do not format!
Code:
C:\>adb reboot fastboot
C:\>fastboot boot nnglow2.img
<use your favorite utility to copy to/from the disk that appears>
C:\>adb reboot
Update
New versions as of 2019-12-18, nnglow2.img, nnglow3.img, nnglow4.img
Download through the signature
Renate NST said:
Noogie was the image to put on the NST so that you could backup or restore the entire internal memory.
It was usually put on the removable SD card.
In fact, it could have been just booted directly through fastboot.
Later, people worked on and succeeded on a way to boot up the NST without any valid internal memory at all.
This made the NST unbrickable.
Neo Noogie is pretty much the same, but updated for the Glow2 & Glow3.
Since these models don't have a removable SD card they need to be able to boot over fastboot.
This means that if you totally wipe out the memory on your Nook (including where fastboot is) you'll be bricked.
(That is, until we get working on a USB bootloader method.)
Warning: Windows will offer to format anything it doesn't understand! Do not format!
Click to expand...
Click to collapse
Can you add md5 sums for the images?
eriol1 said:
Can you add md5 sums for the images?
Click to expand...
Click to collapse
Neo Noogie does four things:
It boots up without mounting any partitions at all
It presents the entire internal SD card as a UMS volume over USB
It supports ADB
It supports the hardware console shell (Ok, most people didn't install a jack in their Nook)
None of this has anything to do with MD5.
But I'm glad you brought it up.
You can get an MD5 of the internal SD card (only when Neo Noogie is running, not when B&N has everything mounted).
Code:
# md5sum /dev/block/mmcblk0
0a1c3941a12abff93b44a2603381ad12 /dev/block/mmcblk0
It reliably generates the same MD5 since nothing is changing.
After you have pulled the 4 or 8 GB over to your host machine, you can likewise calculate the MD5.
Right now I seem to be getting two different MD5's despite the MD5's being repeatable (on either end) and multiple transfers give no differences.
Renate NST said:
Neo Noogie does four things:
It boots up without mounting any partitions at all
It presents the entire internal SD card as a UMS volume over USB
It supports ADB
It supports the hardware console shell (Ok, most people didn't install a jack in their Nook)
None of this has anything to do with MD5.
But I'm glad you brought it up.
You can get an MD5 of the internal SD card (only when Neo Noogie is running, not when B&N has everything mounted).
It reliably generates the same MD5 since nothing is changing.
After you have pulled the 4 or 8 GB over to your host machine, you can likewise calculate the MD5.
Right now I seem to be getting two different MD5's despite the MD5's being repeatable (on either end) and multiple transfers give no differences.
Right now it's a head scratcher.
Click to expand...
Click to collapse
I actually just meant md5 of the bootable img files, so we can make sure the file is intact before booting.
But it seems you hit an interesting issue so I guess we're lucky I didn't explain myself properly
eriol1 said:
I actually just meant md5 of the bootable img files...
Click to expand...
Click to collapse
Oh...
Code:
nnglow2.img
[strike]21ce45fe df9abe3f 882c73fa 4928d091[/strike] [color=red]Obsolete numbers[/color]
nnglow3.img
[strike]1e3975db 5b0a8a3b 7c6cbf60 ef8e2449[/strike] [color=red]Obsolete numbers[/color]
Something strange is going on with the 8G MD5s, but not the files themselves.
I generate 233 MD5s on 32Meg chunks.
All 233 are identical on both sides!
I generate a single MD5 over the entire thing and they are not the same.
Ok, no problem at all.
What I was seeing was an MD5 utility on my Windows box that hadn't anticipated files > 4G.
MD5's of the transferred images (4GB or 8GB) on Nook and host agree.
Renate NST said:
Oh...
Something strange is going on with the 8G MD5s, but not the files themselves.
I generate 233 MD5s on 32Meg chunks.
All 233 are identical on both sides!
I generate a single MD5 over the entire thing and they are not the same.
Ok, no problem at all.
What I was seeing was an MD5 utility on my Windows box that hadn't anticipated files > 4G.
MD5's of the transferred images (4GB or 8GB) on Nook and host agree.
Click to expand...
Click to collapse
I was just about to suggest something along those lines
Good to know there's no deeper issue. Thanks!
Renate NST said:
(That is, until we get working on a USB bootloader method.)
Click to expand...
Click to collapse
Like i.imx6 usb recovery mode?
https://boundarydevices.com/unbricking-nitrogen6x-sabre-lite-i-mx6-board/
But, I don't really think it will be possible without disassembly.
RyogoNA said:
But, I don't really think it will be possible without disassembly.
Click to expand...
Click to collapse
Right, it's not so friendly as the OMAP in the NST.
You have to play with the boot mode jumpers (which don't physically exist on this board).
You might me able to ground an easily accessible test point.
OTOH, if you've gone that far a JTAG interface would work too.
Big oops on my part
I accidentally left the setting in Neo Noogie for the internal SD card in read-only.
It's actually not a big deal (ahem, since no one complained).
Any backups that you made are fine.
It just means that you can't write them back into the Nook this second using that version of Neo Noogie.
Keep on making backups if you like.
I'll put up new versions of Neo Noogie in a bit.
I put new versions of the images in the first post's attachments.
The simple change was just to omit the read-only flag for the internal SD card.
I did a bunch of cleanup that you will probably not notice unless you use the shell.
Rant
Ever see that "__bionic_open_tzdata: couldn't find any tzdata" when running TWRP or other images?
The libc.so wants to get its hands on information about timezones.
Sometimes it's missing and then you get three lines of that gobble-dee-gook error message every time you use any command.
The simple solution is to park the tzdata somewhere (and patch libc.so with the hard-coded path).
All this just to say, "Ok, just use UTC and don't give me the stupid error messages continuously"?
Well, it's stupider. The full tzdata is 0.5 Megs.
Why? So we can have timezones for every podunk village on the globe (576 timezones).
I'm using a modified version of tzdata that includes only UTC and is 194 bytes.
Renate NST said:
Noogie was the image to put on the NST so that you could backup or restore the entire internal memory.
It was usually put on the removable SD card.
In fact, it could have been just booted directly through fastboot.
Later, people worked on and succeeded on a way to boot up the NST without any valid internal memory at all.
This made the NST unbrickable.
Neo Noogie is pretty much the same, but updated for the Glow2 & Glow3.
Since these models don't have a removable SD card they need to be able to boot over fastboot.
This means that if you totally wipe out the memory on your Nook (including where fastboot is) you'll be bricked.
(That is, until we get working on a USB bootloader method.)
Warning: Windows will offer to format anything it doesn't understand! Do not format!
Code:
C:\>adb reboot fastboot
C:\>fastboot boot nnglow2.img
<use your favorite utility to copy to/from the disk that appears>
C:\>adb reboot
Update
New versions as of 2018-05-04
nnglow2.img c52e433e 1340acd8 f4d89f9b fa572334
nnglow3.img 6bf28a03 aaa24b93 584a8c35 09cf3a0c
Click to expand...
Click to collapse
Hello - neewby here - I got the Nook Glowlight Plus -
is this a custom image ?ROM?
Thank you
DanChr79 said:
is this a custom image? ROM?
Click to expand...
Click to collapse
It's not really a ROM because it's doesn't run Android or apps.
It is a custom image because it is a minimal OS.
Its only purpose is to allow you to copy the full internal memory to/from your desktop computer.
There are three ways to boot up an OS:
From the boot partition (normally the regular OS)
From the recovery partition (normally the factory restore routine)
Downloaded over fastboot (normally not used)
Renate NST said:
It's not really a ROM because it's doesn't run Android or apps.
It is a custom image because it is a minimal OS.
Its only purpose is to allow you to copy the full internal memory to/from your desktop computer.
There are three ways to boot up an OS:
From the boot partition (normally the regular OS)
From the recovery partition (normally the factory restore routine)
Downloaded over fastboot (normally not used)
Click to expand...
Click to collapse
Thank you for the reply
Then do you know of a customer rom or how to root the device?
The posts here are super old and I am not sure how to fully use (full android) my new Glowlight Plus?
DanChr79 said:
Then do you know of a customer rom or how to root the device?
Click to expand...
Click to collapse
Well, there's a million ways to root it, but since you're on this thread, we can do it this way.
Code:
C:\>adb reboot fastboot
C:\>fastboot devices
1234567812345678 fastboot
C:\>fastboot boot nnglow2.img [color=red]nnglow2 for Glowlight Plus[/color]
C:\>adb shell
# echo /dev/block/mmcblk0p1 > /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file
# cat /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file [color=red]this is just a check to make sure that it worked[/color]
/dev/block/mmcblk0p1
# ^D
C:\>sdcard /r G p1.img [color=red]might not be G, use File Explorer and see what letter it is[/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size
C:\p1.img, 0 bytes
Copy SD card G to image (Y or N)? y
Copying SD card G to C:\p1.img
100%
Finished
C:\>imgutil /x p1.img default.prop
[color=red]Use a real text editor (not Notepad!) to change ro.secure=0 and ro.debuggable=1[/color]
C:\>imgutil /r p1.img default.prop
C:\>sdcard /w G p1.img [color=red]we're writing now, make sure everything was correct![/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size [color=red]make sure that this number is exactly the same as the first time![/color]
C:\p1.img, 4,421,632 bytes [color=red]this number will be somewhere around this, less than the 6.2M[/color]
Copy image to SD card (Y or N)? y
Copying C:\p1.img to SD card G
100%
Finished
C:\>adb reboot
sdcard.exe and imgutil.exe are in the signature, nnglow2.img is in the first post of this thread.
Renate NST said:
Well, there's a million ways to root it, but since you're on this thread, we can do it this way.
Code:
C:\>adb reboot fastboot
C:\>fastboot devices
1234567812345678 fastboot
C:\>fastboot boot nnglow2.img [color=red]nnglow2 for Glowlight Plus[/color]
C:\>adb shell
# echo /dev/block/mmcblk0p1 > /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file
# cat /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file [color=red]this is just a check to make sure that it worked[/color]
/dev/block/mmcblk0p1
# ^D
C:\>sdcard /r G p1.img [color=red]might not be G, use File Explorer and see what letter it is[/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size
C:\p1.img, 0 bytes
Copy SD card G to image (Y or N)? y
Copying SD card G to C:\p1.img
100%
Finished
C:\>imgutil /x p1.img default.prop
[color=red]Use a real text editor (not Notepad!) to change ro.secure=0 and ro.debuggable=1[/color]
C:\>imgutil /r p1.img default.prop
C:\>sdcard /w G p1.img [color=red]we're writing now, make sure everything was correct![/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size [color=red]make sure that this number is exactly the same as the first time![/color]
C:\p1.img, 4,421,632 bytes [color=red]this number will be somewhere around this, less than the 6.2M[/color]
Copy image to SD card (Y or N)? y
Copying C:\p1.img to SD card G
100%
Finished
C:\>adb reboot
sdcard.exe and imgutil.exe are in the signature, nnglow2.img is in the first post of this thread.
Click to expand...
Click to collapse
Thank you so much for your time and reply.
This will root the device?
I will still need a custom rom ? android to install on it?
Is there a script available or BAT file since I am a computer noob?
DanChr79 said:
Thank you so much for your time and reply.
This will root the device?
I will still need a custom rom ? android to install on it?
Is there a script available or BAT file since I am a computer noob?
Click to expand...
Click to collapse
This will give you shell root access.
What you want to do with it is another question.
I don't have a script.
There may be other threads on this forum that use different approaches, do a dozen things and have scripts.
I haven't really paid any attention because I just rooted my devices with a hardware root console.
Renate NST said:
This will give you shell root access.
What you want to do with it is another question.
I don't have a script.
There may be other threads on this forum that use different approaches, do a dozen things and have scripts.
I haven't really paid any attention because I just rooted my devices with a hardware root console.
Click to expand...
Click to collapse
Danke Renate....
Usually after rooting, customers image will be applied to phones or tablets no?
So I root it and then.... I am able to use custom apk?
DanChr79 said:
So I root it and then.... I am able to use custom apk?
Click to expand...
Click to collapse
If you just want to install an APK, you can just install an APK without rooting.
Have you tried that yet?
Code:
C:\>adb install whatever.apk
I could be wrong. I've never had an unrooted Nook.
Does anyone has a glow3 backup that can share?
I "managed" to brick mine and I will need images to (hopefully) revive it.
Can anyone point me to a recovery guide via USB?
I suppose I should be able to start u-boot via mfgtool/uuu/imx_usb_loader with fastboot enabled and recover partitions content from there?
Thanks,
C
cipibad said:
I should be able to start u-boot via mfgtool/uuu/imx_usb_loader
Click to expand...
Click to collapse
A late response, but...
I've tried various of the iMX loaders and didn't have much luck, so I wrote my own, imxboot.exe
It's available in the signature.
There are three new Neo Noogie images to download for the Glow2, 3, 4.
There has been a bit of cleanup and a few improvements.
It's easier to mount partions now, no need to do all the parameters yourself.
Code:
# mount system
# mount data
@Renate NST
Please add md5 for images
And update thread name to " & Glow4"
Thank you for all your work!