I have a small affair since CM resized the partitions, and some questions haunt me.
The system partition of my phone is in the initial format 600MB and 1.3 GB for data. As everyone will know CM changed partitions to 400MB and 1.5GB of data.
Approach: I would like to have a ROM of Ginger for sporadic use of the camera and any other issues with Nandroid saved. I understand that this requires the old system partitions that i have, and kk for regular use with current system partition, copied also with Nandroid.
The issue is if when move from one to another from the corresponding copies saved from the recovery also restores the size of the partitions or not.
If not, is it absolutely necessary to have the partitions on the current format of CM for KK?, What problems can be if left to the native format 600MB, 1.3GB?
Regards
Note: Edited to better understanding, sorry for my poor english.
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.
what exactly is app2sd??
I am using RAFDROID ROM on a TMOUS HD2
in the instructions he said that if I am using a euro HD2 with 512 rom I should partition my sd card
so I did not do that and flashed the rom on my NAND
then when I started using apps I noticed that after two weeks usage I have only 50 MB left!!!!
so I want to activate app2sd and move my apps to the sd card..
so please I need some help from the experienced users on this great forum that can advise me about what exactly is this and how to activate and use it
thanks in advance!!
Apps2sd moves your apps to the sdcard, usually to an ext 3/4 partition. I don't know about the ROM you're using, but on the one I use (mdj's Cyanogen 2.6), you can move apps to external storage like this: settings --> applications --> manage applications. Then select an app and there is an option to move to sdcard.
@freeincolorado, the method you described is not A2SD+, that method is called move2sd.
A2SD+ puts the dalvik cache as well as the applications in a EXT2/3/4 partition, usually called the sd-ext partition. This method will still show you that the application is in the ROM. However, the sd-ext is used instead, depending on the chief implementing A2SD+ in their ROM, the remaining ROM space is suppose to report the partition "sd-ext" free space, however, certain ROMs are not properly done in my view, and will report the userdata partition free space instead. Such as MDJ's Cyanomodgen 7+ Gingerbread.
How to use A2SD+
Usually, they require you to partition your SD Card into 2 primary partition. The first partition is FAT32 where you store all your extras, such as music, ebook, etc (Like how your SD card is presently used). The 2nd partition is EXT2/3/4 depending on your preference, most people do not use EXT2 anymore as it does not support Journaling, since data can be easily corrupted with a battery pull. EXT3 and EXT4 contains journaling feature, so when battery is pulled, data corruption is minimal.
NOT ALL ROMS SUPPORT EXT4. This is a kernel thing, so if the rom uses a kernel that does not use EXT4, then it will not read the partition.
A2SD+ has a nice feature as well, when you switch ROM, you do not need to re-install all the applications, since all applications are placed in the sd-ext folder, including the dalvik cache. However, this also includes the system default applications which might not be compatible with another rom build.
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.
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
archibrid said:
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
Click to expand...
Click to collapse
You've got it completely the wrong way around, the /system partition is where the actual OS is installed, so the smaller the /system partition, the greater the internal storage which remains, which is thus usable for apps.
Smaller partition = more storage.
Well, I have the Cube i10 Android/Windows Tablet. Nice thing, except maybe the space for the Android OS being a bit too small.
I managed to upgrade my Windows 10 to 10586 and with seperate language pack, it back in my language.
Now i looked around the internet, if I could change the predefined space for either System. (It is possible to increase the partition size of the Andorid OS, but it requires a re-flashing, which I don't neccessarily want. In windows disc-management i saw all the partitions given for android etc, but did not dare to touch something as it was shown in RAW-format. Now i installed a "real" partitioning program (Paragon Partition Manager 15) and it shows me the "real" informations.
Total disk: 28.9 gb (which sums up to ~32gb advertised)
- then a lot of small (5x 16 and 3x 64 and 1x 32mb) GTP partitions, no label, all hidden (i expect these to be android Dalvik, recovery and cache partitions)
- then 4x Linux ext4 partitions (16mb, partially full, 1gb, hardly full, 256mb, half full another almost full 1gb partition) don't know what these are, also all hidden
- then a 3GB Linux ext4 partition (which surely represents the ROM from the Android part, with exact taken/free space data from android)
- then - my problem - a 128mb GPT-Volume, which i can't move
- then the 22.7gb Windows Partition (is resizeable)
- and last, a 450mb hidden backup/windows recovery partition
my problem is, that i can't move the 128mb GPT-Volume. So even if i can split ~2-3gb off the Windows partition, it stays after the GPT volume but it has to be before that to be merged with the android 3gb to make it bigger. I read around that you can delete the GPT-partitions, but don't want to risk it. I "could" merge my 3gb Linux partition with any of the 4 other partitions, but as all of those are not empty, i expect them to be some system recovery backup or whatever. Any information?
I'm afraid that you have to do repartitioning with android flasher and then reinstall Windows too.
Sent from Nexus 6P using Tapatalk
sad, i was afraid that it would be able by editing the partition.tbl file in the rom. Well then i have to stay with the few space i got.