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.
Hi guys,
I'm cooking a WM6.1 ROM with a small set of applications using osKitchen Zero v1.33.5. This gives me lots of free space on the user partition. I have been searching for way to redefine the partition sizes and shrink the user data partition, but haven't found any information regarding this.
Does any one know how to do this or is it even possible?
Thanks
jlsaraiva
Any reason to shrink it?
The idea is to use the remaining space to create the android partitions and boot android with haret from the WM partition. Having both WM and Android on NAND.
Well, that's the thing you can't do via ROM. At least I think so. You need some extra storagemanager drivers.
sounds intriguing though at first - moving the ext2-partitions to nand and telling haret to look for them there instead on sd. you'd still have to boot winmo first, but android would be faster. "semi-nand-flash", kinda.
but thinking about it - not enough internal memory for two os on the x1.
Dont think this is possible just yet. Like your thinking of having two os on internal memory but especially with us poor EURO 512mb devices I dont think it could cope. It would also mean a resdign of haret.exe as it looks for android on SD card.
I striped out pretty much all non essential WM parts from the ROM and I get about 400MB of free space on the user data partition, which is enough to have xdandroid.
You would have to boot into WM first, but I wouldn't mind if it ment running everything out of nand.
No need to change haret. It would be just like we have now, running xdandroid out of the sd card. Only need to change the init script on initrd to mount the nand partitons instead of the sd card and change the init script on the rootfs filesystem. Both are not dificult to do. The only issue here is really "to be or not to be" able to resize the user data partition of WM.
jlsaraiva said:
I striped out pretty much all non essential WM parts from the ROM and I get about 400MB of free space on the user data partition, which is enough to have xdandroid.
You would have to boot into WM first, but I wouldn't mind if it ment running everything out of nand.
No need to change haret. It would be just like we have now, running xdandroid out of the sd card. Only need to change the init script on initrd to mount the nand partitons instead of the sd card and change the init script on the rootfs filesystem. Both are not dificult to do. The only issue here is really "to be or not to be" able to resize the user data partition of WM.
Click to expand...
Click to collapse
This could be a nice idea as you could in theory have android running on nand with out the limitations of either magldr or clk. You would be hard pushed to get a sense build running, but a gingerbread version would be cool! I assume you really have to strip down WM to get it to fit?
I remember looking into this a long time ago before magldr came out and found out some registery keys that could run hart.exe and clard.exe for you with out any user input. I'll see if I can digg them up for you!
I removed almost all EXT packages plus some microsoft apps like office, windows live etc...
But all this falls short if we can't resize the WM partitions.
I've been looking into re-partitioning the NAND on my Xperia X1, so I could increase the storage space when using a smaller rom, but I also have not found a way to do it.
I was originally hoping there was an app, either in Windows mobile, or android, that would work as a partition manager, but I have only found apps that will partition SDcards.
Another option I'm thinking of is using a linux partition manager in android, or using a full blown linux on my phone and using a linux partition manager that way.
I've also thought of using mtty, but I don't know any commands that will let me manipulate the partitioning.
I actually have no idea if any of this will work out, I don't know how the whole boot-procedure works, so I don't know if the bootloader expects the WM-rom partition to be at a certain address, or if it just goes to a certain partition, regardless of the starting and ending positions.
Hi,
Is that possible to set cache size to 45 mb with cLK?
Yes, it's possible.
Upgrade to 1.5, and you can do it by holding the back button then going to the settings.
Marvlesz said:
Yes, it's possible.
Upgrade to 1.5, and you can do it by holding the back button then going to the settings.
Click to expand...
Click to collapse
Hi there!
I've got a question regarden de ideal partition size. I use an HD2 with 0.5GB internal memory, with the HD2 Toolkit i partitiond the MAGLDR partition to 300MB, is that okay? What size should the cache be?:cyclops:
What size should the cLK partition be with an ROM installed of 140MB?
Thank you very much!:laugh:
Greetings
Maxxdiss
maxxdiss said:
Hi there!
I've got a question regarden de ideal partition size. I use an HD2 with 0.5GB internal memory, with the HD2 Toolkit i partitiond the MAGLDR partition to 300MB, is that okay? What size should the cache be?:cyclops:
What size should the cLK partition be with an ROM installed of 140MB?
Thank you very much!:laugh:
Greetings
Maxxdiss
Click to expand...
Click to collapse
It is always better to use the least size possible, as the remaining storage is going to be your internal storage for apps and so.
I think that 300MB is too much, no ROM currently uses such a big partition. (Taking into account the fact that you have a european HD2 and always using A2SD).
There is no such thing as "ideal partition size".
The best partition sizes (system, cache, boot ... etc) are the one recommended by the ROM developer himself, he built it, and he knows on a how big partition it will fit.
I have noticed that I mean read that the advice for the settings on partition sometimes can be set lower than the advice from the developper.
There are people here they test it out it is possible but I follow the directions always to begin and it works,
Titanium Backup
I know it may be a bit tedious, but what I can recommend is to experiment with it.
If you use European HD2 with A2SD then it does not really take much time since only the ROM takes place there.
You can start with a generous amount of system partition (say 300 MB) and start Titanium Backup (there may be an easier way, but TB is usually included in every ROM). In the lower part of the start screen there is an information about the free space in the "System ROM" partition (say it is 100 MB). If you use A2SD, then you can repartition your NAND using a 300-100+5 (for safety) = 205 MB.
Of course, if you have bad NAND blocks then you need to play a bit more around.
Like everyone here, I have the famous HTC Leo. A friend installed Android on NAND, the 2.3.4 with the mod-HyperDroid CM7-v2.1.0.
This is a great device, but the more I use it, the more I have less internal memory.
At first, I installed a lot of applications, I was full of things and I ended up filling the internal memory. I moved the more applications possible on the SD card, but the internal memory ended up being full. So I uninstalled applications not too useful, and applications more useful, clean caches, remove data, but it is still too small. My system tells me that I only have 217.3 Mb total internal memory and while I hardly more than application system installed, I only have 21.3 MB available. Now, I know that this model has double.
I do not understand: what is this devilry? Where is my memory? How can I resume normal operation until all the memory is gone and my phone becomes unusable?
I can't be the only one to whom it happens, right?
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
samsamuel said:
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
Click to expand...
Click to collapse
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
shanman-2 said:
Excellent advice, but I think you forgot to mention this
Click to expand...
Click to collapse
so, pretty much exactly what i described, then....
shanman-2 said:
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
Click to expand...
Click to collapse
So, I don't really need to use this. I just can install a new ROM on my NAND after making extending place on my SD for the 'dataonext', can't I?
I have to choose a dataonext ROM (with french version) and make new partition on my CD card. I'm saving all the SD card data's just now (with luckyBackup, because I'm on ubuntu PC).
My problem is find a good ROM for my needs. So, I have HSPL 2.0.8 and MAGLDR. How can I find the rom radio number? I need this information to choose the good ROM. Any advices about good ROM for my needs?
r no need to change the radio,,, if magldr works then the radio is fine.
samsamuel said:
r no need to change the radio,,, if magldr works then the radio is fine.
Click to expand...
Click to collapse
I bought a new 16 GB SD card to try the method of post 1843062. I am trying to format as it should, and tonight or tomorrow, I'm trying to see if I can install the script without too much risk, I am not a very experienced user of ROM for HD2 and, in addition, as I'm 100% Linux Ubuntu, I saw that many procedures are more complicated or impossible to run from a Linux desktop.
Thank you for all your help and I'll let you know.
I need to understand.
I have a EU HD2 with HyperDroid CM7 installed on it.
Like many people here, my memory became too small over time. So I look for a solution and I was guided to this thread. While speaking, I read everything I could understand (and frankly there really is too much to read and understand, here ) and I ended up deciding to adopt the solution Kokotas.
So I bought a new SD card (16GB class 10 Duracell - I know, Duracell is a brand of batteries ...) and I formatted properly Gparted as shown, with one primary partition of 12 GB fat32 I named /données (French for datas) and a second primary partition 4 GB Ext4 I named /data.
Then I primed to install the script Kokotas (but I have not yet done so, this is the trick!) And there: surprise!
I suddenly 4 times more free memory internally (from 20 MB to 80 MB), but it is still the same overall size!
I wonder how it is done, because it's been months that I want to release the NAND memory, I deleted almost all my applications downloaded without great effect and there, before installing the solution Kokotas, hop, I have the place!
I run Nautilus on my HD2 connected via USB and what do I see? in the partition /data in ext4, records were Cres /app /app-private and /dalvik-cache.
What does that mean? My ROM can do one DATAtoEXT 2011 alone, when she sees a partition SD / data?
Do I install the script Kokotas or it is not worth it?
Do I flash a new ROM (I thought MIUI-MIX_3.3.1, but I'm not sure it's a good idea) without risk, in short I need to understand what happens with my phone.
Thank you.
(Sorry for my english : this is the fault of Google translation )
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
orangekid said:
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
Click to expand...
Click to collapse
I thought NAND is better for battery's management...
Monolecte said:
I thought NAND is better for battery's management...
Click to expand...
Click to collapse
I didn't see any great battery improvement with NAND.
ROM flashing don't work
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Monolecte said:
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Click to expand...
Click to collapse
use the nand toolkit
samsamuel said:
use the nand toolkit
Click to expand...
Click to collapse
With an Ubuntu PC?
After miles of thread reading here, I won against the machine!
I have something like a new phone.
Thank you everybody.
If I can do it, anybody can do it!
ubuntu or windows will be fine.
The NAND Toolkit is a Windows software... so...
Hi Guys,
A friend of mine has handed me a HD2 to install android on. I did it on a US version a couple of years ago. For the EU/International version if he wants a basic ICS or Jellybean rom whats the average system partition and cache size to use? I know it varies from rom to rom, but if I was to go for the NexusHD2 roms what would you recommend.
He also has a 8GB SD Card, so roughly what size should I partition that to? He would definitely rather a NAND rather than SD version. Then I guess once up and running it's just a case of using something like Apps2SD to get the apps on the SD card?
Thanks for the help
if it's eu, it's very hard, if not impossible, to install and run ics/jb roms on nand only. why not just go with dataonext? better than app2sd scripts, you could have 400mb system partition and 1-2gb or 512mb ext4 partition for data. that would be IMO very easy and beter solution than nand only on eu.
re
manicdefender said:
Hi Guys,
A friend of mine has handed me a HD2 to install android on. I did it on a US version a couple of years ago. For the EU/International version if he wants a basic ICS or Jellybean rom whats the average system partition and cache size to use? I know it varies from rom to rom, but if I was to go for the NexusHD2 roms what would you recommend.
He also has a 8GB SD Card, so roughly what size should I partition that to? He would definitely rather a NAND rather than SD version. Then I guess once up and running it's just a case of using something like Apps2SD to get the apps on the SD card?
Thanks for the help
Click to expand...
Click to collapse
you can install a stock ICS or JB rom with non extra apps inside. The problem with EU and Nand install is the install of your apps. this apps is only in system/apps and with this install your phone is very slow and have reboots. for the EU HD2 is better the nativeSD or DataOnEXT install. for this install methods you must have a fast SD Card with two Partitions. the first is the FAT32/cluster default/primary and the second is the EXT4/cluster default/primary
Pixelfreak