The G2 and DZ have slightly different partitioning as standard. As I understand it, the G2 has 28 partitions, and the DZ has 29, with the system (and userdata) partitions being slightly smaller on the DZ to allow room for that 29th partition (info from http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning ).
Is this a big issue in reality ? Just throwing the question out there for discussion, as part of the whole G2/DZ differences (possible forum merge ?) thing.
The issues that I'm aware of are that you'd need to make sure you flash the correct hboot image if you're changing that (since it looks up the partitions), and that a stock G2 ROM won't flash straight onto a DZ since it won't quite fit (but can easily be trimmed down in custom ROMs).
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.
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.
Hi,
I've been seeing all the new F2FS ROMs and Kernel's being developed for the N7. I'm very interested in trying it out, but I'm also getting very confused. I know what it is in principle, "a different file system created to be more optimized to the characteristics of NAND memory in flash devices." (as explained in the XDA article) - but what's the difference between 'F2FS' and All-F2FS'; which partitions does each modify? is there a performance difference between them? which ROMs/Kernel's can be used on each? etc?
Thanks!
F2FS means only the /data partition is formatted with the filesystem, while All-F2FS means all of the partitions are.
AFAIK, for F2FS one only needs a compatible kernel (and recovery) and can use any rom.
For All-F2FS one need a compatible kernel, recovery and rom.
(I'm not using f2fs myself, so someone with more experience can correct me if I'm wrong.)
Thanks Erovia, that helps
Now the question remains, is there much/any performance difference between F2FS and All-F2FS..?
I'm sure there is, but since the most used partition (in I/O perspective) the ext4->f2fs/all-f2fs gain is bigger than the f2fs->all-f2fs gain.
Dear All:
This is a fundamental / dumb question that I am not sure where to post it.
I have a Moto X Pure/Style. I have a relatively strange variant (Chinese, XT1570). But that is not the point.
I have obtained two official images from Chinese website. Version wise they are identical.
One strange difference is size of "system.img" file.
The one I choose to flash my phone with (mind you that this is the OFFICIAL stock image with no modifications) has a system.img file which is 1.36GB in size.
Another package I obtained from a different Chinese source has a system.img file of 3.99GB in size.
When I looked to my phone, system.img file of 4GB is about right, that is how much it occupied on my phone.
Why this 1.36GB system.img file worked at first place? is there a differeces?
thanks in advance.
The larger image is probably a sector/sector image of the entire partition (dd). The smaller is just the files in use.
If you want to test this, flash the smaller image and note the free space remaining. Then flash the larger. I bet the two numbers will be similar if not the same.
sector/sector image of entire partition?
gpz1100 said:
The larger image is probably a sector/sector image of the entire partition (dd). The smaller is just the files in use.
If you want to test this, flash the smaller image and note the free space remaining. Then flash the larger. I bet the two numbers will be similar if not the same.
Click to expand...
Click to collapse
Thanks for your reply. I got a couple questions.
The large system.img file was created by clobber the sparsechunk.x file together.
What do you mean "entire partition?"
Here is what I am trying to do:
I have a Chinese version of Moto X Pure. It is the only dual-SIM version that support both AT&T and China's LTE band. However, China banned Google services thus the Chinese version contains NO Google services nor Google Service framework. What I want is to flash the XT1572 version (Rest of Asia) dual SIM Android OS while keep the modem part intact.
1. is it safe to assume all Moto X Pure|Style's partition structure is identical?
2. on Chinese web, an article stated that all I have to do is flash the boot.img AND system.img and leave everything else intact, the phone will work. Is this something I can just assume?
3. I noticed that bluetooth has its on firmware (BTFM.bin). does GPS has its own firmware as well? if it is, which image file is it? The reason I am asking this is because hardware wise, Chinese variant is different from rest of Moto X Pure in terms of navigation hardware: Chinese variant has GPS, Beidou (Chinese), and Glonass (Russian) all three receivers. and given the choice, i would like to keep that intact as well.
Thanks in advance
Entire partition as in the entire 4GB partition space. Obviously the system is not occupying all of this space, but the image created was a snapshot of the entire space including unused space.
1) I don't see why they would create different partition layouts for different regions. Usually the only difference would be in software
2) Boot.img is the kernel and system.img is the system partition. You should be fine flashing these two.
3) I don't recall ever seeing a separate gps partition. I'd think the code for it would be part of the baseband.
Whether or not the xt1572 has the right drivers for this is another matter.
Make a backup of system, boot, and data partitions, then flash the xt1572 boot and system only. You'll maybe able to boot right up or you'll have to do a factory reset from within the recovery if it bootloops on startup.
now I am confused... I see TWO system partitions in Teamwin recovery
when I tried to do a backup with Teamwin recovery, i actually see TWO "System" partition:
System (which is about 1.5GB)
and
System R/O (which is about 4GB)
what is the differences between these two system partitions?
when I do
fastboot -s XXXYYYZZZ flash system system.img
which "system" partition am I really flashing?
and when teamwin recovery said I can backup "system" partition and "system R/O" partition, how doe these two partition map to fastboot's partition? I see I can flash
partition
bootloader
modem
fsg
bluetooth
boot
recovery
system
there is only one system...
gpz1100 said:
Entire partition as in the entire 4GB partition space. Obviously the system is not occupying all of this space, but the image created was a snapshot of the entire space including unused space.
1) I don't see why they would create different partition layouts for different regions. Usually the only difference would be in software
2) Boot.img is the kernel and system.img is the system partition. You should be fine flashing these two.
3) I don't recall ever seeing a separate gps partition. I'd think the code for it would be part of the baseband.
Whether or not the xt1572 has the right drivers for this is another matter.
Make a backup of system, boot, and data partitions, then flash the xt1572 boot and system only. You'll maybe able to boot right up or you'll have to do a factory reset from within the recovery if it bootloops on startup.
Click to expand...
Click to collapse
Strange. Which version of twrp are you using?
Can you post a pic?
Is there a way to increase the partition size for the apps?
goodjuju said:
Is there a way to increase the partition size for the apps?
Click to expand...
Click to collapse
I am going to make an assumption here that you don't mean via adopted storage... Is there a way? Probably
Is there a reasonably safe way to increase the /data partition size? No... This device has around 30 partitions, if you start messing with one you have to mess with all of them and the issue is we can't control 2/3 of them at all. It would be very easy to hard brick your device, not to mention you would never be able to accept an OTA again (it re-writes the gpt.bin which is the partition table) or flash a stock image, and although 3rd party ROMs likely wouldn't care the problem is the chances of modifying it and getting it right are slim. And since we don't have working blankflash files, brick means hard brick and send to Moto if they will even look at it since the bootloader is unlocked.
Best answer? Use adopted storage or get a device with more internal storage... it's been many core Android versions ago since messing with the partition table was even slightly safe (even then a brick condition was pretty easy).