There are different recovery sizes. 190MB, 400MB and a lot of other sizes.
I like CWM because it's super easy to flash (just download the image to the SD card, even without computer). But it kinda defeats purpose of easy flashing if i have to install different recovery for each rom.
Why cannot these sizes be flashed directly from recovery, so you don't need to reflash from computer?
If you have a TMoUS HD2, I think you'd be safe to just always use the 400mb one. I think the others are mainly for EU's because of their less ROM space. I could be wrong about it, but I have a 400mb system space and have flashed a few different roms without problems.
I use an ext partition with a2sd, so I never need to worry about system storage space.
Sent from my HTC HD2 using XDA App
I have EU unfortunately. While you can have 400MB all the time, it will shrink data image on ROMs that can have everything stored on device itself.
Some devs highly dont recommend big recoveries for their ROMs.
For ROMs like Miui and CM7 you can get away with with 1 size recovery (150-200), however for Sense ROMs you need a different size, for Sense Lite ROMs a bit less.
Hi,
I've just flashed the ROM in my sig,which required 130M recovery.
When the ROM had finished loading I checked the internal phone storage and was very pleased to see 260MB of space.
Largest amount of space I've had from any ROM so far.
Related
Hi All,
I need real help with ClockworkMod Recovery. I have been installing Android on HD2 using storage card (haret.exe) method. Then I moved to NAND without any problems.
But I am not able to understand ClockworkMod Recovery at all. I looked at lots of threads and also the main thread for ClockworkMod Recovery. I know how to install it. I have installed it on my phone. But for some reason I was stuck in the loop after installing the ROM {[22 JAN] -=MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC]}. I did exactly same as the video tutorial says. My radios and HSPL is fine. Coz I am able to use the same ROM in NAND mode. But still in ClockworkMod Recovery mode the phone kept restarting and never got to the main screen.
I also do not know what ext2, ext3, ext4 partitions are. Do I need to make them before installing the ROM? Also on the main thread for ClockworkMod Recovery, it has 3 partition files. 250MB, 350MB and 450MB. I do not know what that is. Which one to use for which ROM and what are the differences between them?
What is the use of ClockworkMod Recovery if I have to flash this partitions every time I install new ROM?
Also can someone tell me what backing up the ROM means? Does it mean I can back up my current one and flash new one, and if I do not like the new one I can restore the old one in the same state (with my APPS and SETTINGS)?
Please please help me with ClockworkMod Recovery fundamentals. I would really appreciate it.
One more thing, I would not post a question if I haven't looked around enough for answers. As you can see I have been doing this from months, but only asked one question before and this is the second one. So please do not take me for someone who does not look around for answers. I do, its just that I did not find anything real good to explain me from the bottom. So please someone help me out.
Thanks in advance.
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Digital Outcast said:
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Click to expand...
Click to collapse
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
jalshah05 said:
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
Click to expand...
Click to collapse
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
To be very frank I did not understand what you just told me sir. Only thing I can tell for sure is I downloaded the .zip file from the thread at http://forum.xda-developers.com/showthread.php?t=877777 . And I do not know what logcat is. I am sure you must be thinking that I am an idiot. Forgive me for my ignorance.
Google is your friend!
I'm a better one: http://wiki.cyanogenmod.com/index.php?title=Logcat
Edit: very interesting read by the way, Digital Outcast. Much appreciated!
Digital Outcast said:
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
Click to expand...
Click to collapse
Thanks a lott Digital Outcast for this amazing explanation. I hope I can get the Recovery mode working. I will try some different roms and see what can be done. meanwhile if you get chance please explain me your response "Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?"
Thanks a lott once again.
Ok, I've been able to keep up with all the flashing of android on hd2 fairly easy since the beginning almost a year ago. This is the only time I've ever really had a hard time figuring it this thing out.
I have flashed nand miui rom with 250mb partition on my eu hd2 through clockwork recovery. I'm trying to try other builds so I do the same method previously by flashing the zip file on my sd card through clockwork but it always get stuck at "unpacking sdext" files.
Is it because each build require different size partitions? Is it something else? Am I missing a step?
This clockwork stuff is pretty confusing...help is appreciated and thank you all in advanced. Much love.
Yes, different builds do require different partition sizes. A GingerBread build can get by on a 150mb (and possibly less) partition, whereas a Desire HD based build will require a 400mb partition.
so how do i go about doing this? because ive tried to partition my card, but it just erases everything clean even with a backup
mini_robot said:
so how do i go about doing this? because ive tried to partition my card, but it just erases everything clean even with a backup
Click to expand...
Click to collapse
The latest cwm partitions are flashed to your NAND and has nothing to do with partitions on your sd card. The sd card partitions are needed to run certain roms on the EU512 device.
To flash a cwm 1.3 partition, you need magldr 1.13, download the partition size you need, boot to usb flasher in magldr and run the daf.exe file from the download. It will wipe data on your phone NAND memory and should have no impact on data on the sd card.
I already have cwm 1.3 and magldr 1.13. I already flashed miui rom. That means I have to use a computer to flash other Roms as well? I thought the point of cwm is so u can flash and switch between roms without a comp?
or does this mean flash through the computer once and then u can switch between roms? sorry if I'm really dumb
You can (as long as you have the same partition size as is needed). I haven't tried it, but I guess you could install the 400mb partition and that should cover all rom types. The only problem is that you then create a larger partition on NAND than may be needed for some roms thereby reducing the internal memory available.
ClydeB1 said:
You can (as long as you have the same partition size as is needed). I haven't tried it, but I guess you could install the 400mb partition and that should cover all rom types. The only problem is that you then create a larger partition on NAND than may be needed for some roms thereby reducing the internal memory available.
Click to expand...
Click to collapse
ahhhhhh. I think I will try that and report back to see how it goes. thanks so much for your help. I will try to do the same for other people once I figure this out
I'd be interested to know the answer. Good luck....
welps. I have tried with no luck. I actually ruined my 8gb SD card trying it and had to get a new one.
Ive been able to flash the 400mb partition and have been able to flash any rom but like it has already been stated it affects the amount of internal memory available, not too bad for me as i have a tmous
Sent from my HTC HD2 using XDA App
mini_robot said:
welps. I have tried with no luck. I actually ruined my 8gb SD card trying it and had to get a new one.
Click to expand...
Click to collapse
Ok, send me your 8Go SD if you think it's dead
NAND and SD are two different things. For your SD, just delete/recreate the partition and it will be new again.
Explanation I post somewhere else (hope it wll help you to understand):
===
I will try to explain.
I assume you have a non-TMOUS device. So your internal storage (let call it NAND) is 512Mo. This is all what your have.
The CWM xxxMo will be what your allocate for your build.
If you allocate 150 (by flashing CWM 150MB) you will have 512-150=362Mo free.
If you use CWM 400... you will have 112Mo free space.
The build you want to use take a little bit more than 100Mo. So why using CWM400 to fill it with only 100Mo???
You have to use the smallest CWM to put your build in it. This will give you the more storage space after installing the build.
Don't think the more "CWM" you will use the more space you will have. It's exacly the opposite.
Hope you understand. Please take into account that the figures I give are appoximation. Don't complain if instead of 362Mo you have only 300... it's more than enough anyway for most of us.
===
So if your first NAND needed a small partition only, you may have to flash again CWM with another partition setting (for ex a 400Mo to fit a desire HD NAND).
Go on the CWM thread to find the version you need (150, 250 and 400 are available). Some thread are also available to modify the config file to make the partition size you want.
By using the 400Mo most build will be flashable... but you will have very little free space and will have to use your SD card (APP2SD or other soft).
I prefer to put everything in NAND for two reasons:
1/ I can remove my SD when I want
2/ I think it's better for battery consumption to not use the SD (but this I don't know, it's just what I think).
i was able to recover the sd card (thanks). anddddd i was able to kind of, sort of, dual boot, two different builds except that one of them has force close issues constantly.
mini_robot said:
i was able to recover the sd card (thanks). anddddd i was able to kind of, sort of, dual boot, two different builds except that one of them has force close issues constantly.
Click to expand...
Click to collapse
What are you talking about? You can't dual boot with clockwork
Sent from my HTC HD2 using XDA App
dung8604 said:
What are you talking about? You can't dual boot with clockwork
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
well its not dual booting. i just kind of re-install each build from clockwork.
I'm trying to flash a rom for example http://forum.xda-developers.com/showthread.php?t=1100707 and requires 260m recovery size and 1gb partition.
My phone currently has a 400m recovery and 1gb partition from previous rom. Would it be possible if I just installed the new rom without changing recovery to 260m?
If possible any side effects?
Googled b4 and no results...
Ok tried it and booted successfully.
Problem was that I had almost no storage space..
calvinfoo said:
Ok tried it and booted successfully.
Problem was that I had almost no storage space..
Click to expand...
Click to collapse
Hi,
The point of the correct CWM size is to accommodate the system for the ROM you are using.
It only needs to be a little bit bigger than the actual system itself.
The rest of the space can then be allocated to the internal memory and therfore be used to install apps.
If you use a CWM that is too big,you will have no room for your apps etc. as you found out.
It's not difficult to re-partition your CWM especially now that KSUBEDI has made THIS TOOL (Don't forget to thank him).
If I resize my recovery partition on my HD2, is all data on my SD card lost? and would i have to reflash a new NAND ROM?
Repartitioning your internal memory will not affect the data on your sd card in any way.
Yes, you would have to flash a new ROM, or restore a backup.
so i take it the recovery partition clockwork uses it not on that sd card
which leads to my other question, if my rom requires a 169mb recovery and i use a 400mb recovery, will it work?
yes it will work, but you will waste 231mb of rom space. This is because you will set a system partition of 400mb, and load into it 169mb of files, BUT once the rom is running, all your user data, installed apps, etc get put into different partitions. Nothing will use the extra 231mb in the system partition, so it will be completely wasted and unuseable.
abdalla21 said:
so i take it the recovery partition clockwork uses it not on that sd card
which leads to my other question, if my rom requires a 169mb recovery and i use a 400mb recovery, will it work?
Click to expand...
Click to collapse
is there any sense rom that will work on a 150mb recovery? if so please share the link
Very unlikely. Why not just change the size?
samsamuel said:
Very unlikely. Why not just change the size?
Click to expand...
Click to collapse
bored on my help desk job, was gonna mess with my rom,but if im goin to resize i rather do it at home....lol
think im gonna try the bliss rom, any takes on it?
well you could always flash the rom, play with it, then when you get home, do a cwm backup, change the part size, reflash the rom, then in cwm do an advanced restore and just restore the sd-ext and data partitions. hey presto, system size changed and any settings you configure today will be restored into the new flash.
CAnt comment on the rom, i only use typhoon.
abdalla21 said:
so i take it the recovery partition clockwork uses it not on that sd card
which leads to my other question, if my rom requires a 169mb recovery and i use a 400mb recovery, will it work?
Click to expand...
Click to collapse
CAUTION; the CWM partition make it is for the SD and it WILL ERASE ALL DATA ON SD , for partition internal memory u have to use other tools on a PC (my favorite its HD2 toolkit)
Enviado desde mi HTC HD2
Typhoon has a nice stable sense rom.?
Send me a link
Sent from my HTC HD2 using XDA App
Typhoon is a cm7 rom. Cm7 roms don't have sense.
I CAN highly recommend it, though. I've been on an older version typhoon for over a month now, and the only bug is the occasional failed video capture. Annoying, but doesn't happen often.
I have LEO T8585, and when i flash Android 4.0.3. NAND (http://forum.xda-developers.com/showthread.php?t=1354267) i have only 100MB for apps. I tried this HD2 Android NAND toolkit to make partition bigger but no luck.
No matter what size i choose i'll get same size for downloaded apps - 100MB.
Im not total noob flashing NAND ROM-s , but do i miss something?
Or is it possible to make this partition bigger?
Thanks
First, the space shown as available doesn't include the system, boot or cache partition size, only the data partition size, and since during flashing, the data partition size is set to be whatever is left over after the rom is flashed, the only way to increase data size is by reducing the system partition size, , but then of course the rom wouldn't fit (because you flash the system partition to be only fractionally larger than the size of the system folder contents, if you flashed a larger system partition, the extra space would be wasted, unused by anything, example put a rom requiring 150mg onto a 250 Meg layout and you lose 100mb)
Secondly, if you set up an ext partition on the SD card, the rom will consider that internal memory BUT (on most roms) wont show it on the available internal storage calculation, but it WILL use it as internal.
third, the 4.x roms are still beta, and vary as to sizes required, whether they have ap2sd+ built in or whether you need to manually install and configure it. If you are looking for a rom you can keep as a daily for a while, wait until 4.x is a few more betas along.
Thanks!
Thats what i thougt. I made minimal part. 190MB and got 100 extra. My ext. on SD is 1024. For now its ok. And this 4.0 beta 10 it is very nice ROM, looks stable and smooth on HD2.