Has anyone written a nice Newb overview of what this is?
There's bits all over the place but I really havent got the foggiest what it is. I read about partitions and .zip files etc etc but I cant find a nice Newb overview. Yes, I've found the CWM thread explaining how to install it but not what it's really for.
Is it an alternative to MAGLDR? Does it do more/less?? Why do I need partitions? Why is the SD card involved. Can it take 2 NANDS? All this seems to be touched on in various areas but it's hard to assimilate all the info.
Could someone either point me to the nice Newb overview or even write one!
Thanks
It allows you to backup,restore your data from nand and flash Roms from SD Card. I don't need it because the rom that I am using allows me to backup my data via Magldr. But if you like testing different roms or you update ur roms but your data gets erased everytime, Clockworkmod is for you.
Also If you install it, it will erase your nand. So if you had an android rom on your phone you will need to reflash it through SD because flashing through USB will mess up Clockworkmod, therefore you would have to reflash Clockworkmod.
With the SD card two file types are stored which allows clockworkmod to work. Think of it as a program data that is needed for Clockworkmod to fuction. Backing up Nand (Android) using clockworkmod will restore the operating system, settings and apps. Its like using System Restore on a PC. You can also choose between backing up your apps or your entire System.
I think you should wait because Magldr 1.12 will be released soon and if I can recall, it features a Recovery option.
Hope this helps in someway.
Dimension2035 said:
It allows you to backup,restore your data from nand and flash Roms from SD Card. I don't need it because the rom that I am using allows me to backup my data via Magldr. But if you like testing different roms or you update ur roms but your data gets erased everytime, Clockworkmod is for you.
Also If you install it, it will erase your nand. So if you had an android rom on your phone you will need to reflash it through SD because flashing through USB will mess up Clockworkmod, therefore you would have to reflash Clockworkmod.
With the SD card two file types are stored which allows clockworkmod to work. Think of it as a program data that is needed for Clockworkmod to fuction. Backing up Nand (Android) using clockworkmod will restore the operating system, settings and apps. Its like using System Restore on a PC. You can also choose between backing up your apps or your entire System.
I think you should wait because Magldr 1.12 will be released soon and if I can recall, it features a Recovery option.
Hope this helps in someway.
Click to expand...
Click to collapse
Thanks. And I'm assuming you use all the 'old' Roms for CWM rather than the NAND builds?
jamesbond_28_007 said:
Thanks. And I'm assuming you use all the 'old' Roms for CWM rather than the NAND builds?
Click to expand...
Click to collapse
Already explained above, but CWM is for NAND builds.
Could still do with an explanation in the 'how to flash everything' guide. This thing took off and there's very little for newbs.
There are many guides...you are looking in the wrong place. Look in the Android Nand Forum.
Here is a link to one of them: http://forum.xda-developers.com/showthread.php?t=893948
Well it's not written in the main guide. There bits and pieces throughout that thread but nothing explains what it really is, and more importantly its pros/cons/limitations.
Anyway, I'm certainly not on my high horse about this, would just be very grateful if someone could take the time to write a step by step guide. This site is great for newbs but I feel this has been overlooked.
Related
Hi guys,
Ive been reading about Clockwork recovery (watched the videos etc.) but still have a question.
I am using this rom on my HD2: NexusHD2-Froyo V1.9b NAND
I have configured my phone with all my personal settings, app, etc. and I want to install clockwork recovery so that I can install Apps2SD (using the .zip installation file). My 8GB SDcard is already partitioned with 1GB ext4 partition following the 7GB fat32 partition.
The question is can I install clockwork recovery without having to flash a new rom afterwards thus loosing all my current configuration? Or installing clockwork (copy files to SD root, then flash etc) does not affect current installed NAND rom?
Sorry if I was supposed to get this info through the various threads - I just could not find a clear answer.
Regards,
F
copy over the 2 files it tells you to and follow the insteructions, it wont do anything tothe existing installtion, well it didnt to me anyways
Richy99 said:
copy over the 2 files it tells you to and follow the insteructions, it wont do anything tothe existing installtion, well it didnt to me anyways
Click to expand...
Click to collapse
cheers m8
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,
I currently have MDJ ginger running in NAND. I successfully ran Desire3.2 to SD (via AD to SD-Magldr) The problem I have is that I have the ginger build running app2SD to an ext4 partition. That creates a problem with 2 builds running in the same Android directory and causing the Desire3.2 to run very slow.
I tried to create 3 directories in the following order: FAT32, EXT4, FAT32, to keep the Android directories from clashing with each other. The FAT32 partitions are labeled sdcard and sdcard1.
When I boot into MAGLDR to boot the SDcard via AD SD, it only sees the sdcard partition. Is there a way for MAGLDR to see more than one sdcard partiton??
I am running only 2 androids for now, windows 6.5 or 7 is not even in the picture at this time. I have tried to search the forums for a solution, but so far I have not been able to find a way to see 2 FAT partitions in MAGLDR-AD SD. Is it possible? If so, can you give me the link to the TUT or show me how?
Thanks!
ljjehl said:
When I boot into MAGLDR to boot the SDcard via AD SD, it only sees the sdcard partition. Is there a way for MAGLDR to see more than one sdcard partiton??
Click to expand...
Click to collapse
MAGLDR is only able to see the first FAT32 primary partition, so what you want isn't possible (at least not with the current release).
Sincerely,
Mac
Macelangelo77 said:
MAGLDR is only able to see the first FAT32 primary partition, so what you want isn't possible (at least not with the current release).
Sincerely,
Mac
Click to expand...
Click to collapse
ahhh, too bad. That doesn't make it easy to test new Android systems before you decide whether or not to flash to NAND. I appreciate your response. Hopefully the next version of Magldr will include the extra option!
Thanks!
ljjehl said:
ahhh, too bad. That doesn't make it easy to test new Android systems before you decide whether or not to flash to NAND. I appreciate your response. Hopefully the next version of Magldr will include the extra option!
Click to expand...
Click to collapse
But that's the power of CWR (ClockworkMod Recovery). You can use it to make Nandroid backups and flash ROM's. If you tried a ROM, make a backup with NANDROID, and try another one. If you don't like it, restore the previous one
Sincerely,
Mac
Macelangelo77 said:
But that's the power of CWR (ClockworkMod Recovery). You can use it to make Nandroid backups and flash ROM's. If you tried a ROM, make a backup with NANDROID, and try another one. If you don't like it, restore the previous one
Sincerely,
Mac
Click to expand...
Click to collapse
Mac,
Thanks for giving me a summary regarding ClockworkMod Recovery. I skimmed through the info, but I never did look through the info enough to interest me. I definitely will try this out. Regarding Nandroid backups, does it also backup all the user settings?? I would hate to have to start over on my user settings after it being used for a while....(text messages, MMS, downloads, etc.)
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 want to re-partition my NAND, and don't have windows around. So I downloaded cwm-sd.zip and cwm.zip. I extracted cwm-sd.zip to the root of my sd card , copied cwm.zip with appropriate flash.cfg inserted. I will reboot, go to Mahler, ad sd. (As described)
But I will get sd kernel open failed.
I try with the latest stable clockworkmod. 5.0.26
Any ideas what the problem might be.
I want to repart nand only, so any other ideas not including windows pc are welcome, I have pc with Ubuntu on it.
Sent from my HTC HD2 using xda premium
1st-sorry, don't know why its not entering cwm
But
2n- it doesn't work like that. you can't repartition magldr from SD. If it did boot "ad SD" it would run cwm, nothing more. The SD cwm is so you can backup/flash roms without having nand cwm, but it relies on the nand already being partitioned.
If you want to partition from SD use clk instead of magldr.
I have a working CWM installed. I just want to re-part, really.
According to this thread,
http://forum.xda-developers.com/showthread.php?t=987531
it seems this should be possible. I dont want to re-install CWM though, I just want to re-part. I can cope with terminal and adb , I think, and these options are (I think) available under linux, but I dont know how to do it
Well, I disagree, but hey, you have the info. I'll be interested in reading your how-to if you manage it.
(Also, from your other threads you seem not to have noticed that partitioning also installs cwm at the same time)
deckoff said:
I have a working CWM installed. I just want to re-part, really.
According to this thread,
http://forum.xda-developers.com/showthread.php?t=987531
it seems this should be possible. I dont want to re-install CWM though, I just want to re-part. I can cope with terminal and adb , I think, and these options are (I think) available under linux, but I dont know how to do it
Click to expand...
Click to collapse
Even with this link i failed at setting up ADB on my Ubuntu machine but you may have better luck than i.
I am almost 100% sure I managed to do this way back in time. What I don't know is if I can use adb to partition NAND , and if so, how. Not to mention that the phone is not the typical android phone.
Sent from my HTC HD2 using xda premium
samsamuel said:
Well, I disagree, but hey, you have the info. I'll be interested in reading your how-to if you manage it.
(Also, from your other threads you seem not to have noticed that partitioning also installs cwm at the same time)
Click to expand...
Click to collapse
I have noticed it, I assume it will install over the existing one...
I dont have any info, I just cite a source. The process apparently fails for me, so I am stuck. I am probably misunderstanding it.
You CAN install cwm over the current one, by booting into cwm and then using flash zip from sd card, and selecting the new cwm.zip from your sd (just like flashing a rom), BUT this doesn't partition anything, it is just loading the contents of the zip into the recovery partition that already exists.
trust me, if you want to partition the phone without a pc, you need to be using cLK.
From the link above:
For MAGLDR up to 1.13, booting from SDCard (SD-files version):
Download the file attached
Extract the files to the root directory of your sdcard
Start recovery within MAGLDR with menu point "AD SD"
Recovery should start
You're done
Click to expand...
Click to collapse
What exactly is this used method used for? It is described in the Install CWM methods(if I am not wrong)
Flash.cfg files in clockworkmod.zip are used to re-part data and user partitions. What happens if I re-flash CWM.zip with custom flash.cfg file inside via method at the top of the post. Or just flashing CWM.zip with flash.cfg via the installed CWM. What and when reads the flash.cfg files and act accordingly?
It is not a question of trust, I would love to know the basic workflow of the process
The cwm that comes with a flash,cfg is for flashing to nand via usb - magldr - usb flasher, or the cLK equivalent.
the cwm-sd version, and the process outlined in your quote, is used to boot into a valid working copy of cwm from sd card instead of the nand recovery partition.
For example if your nand version of cwm gets corrupted, .. for example trying to use rom manager under magldr, corrupts the nand copy of cwm, so you can load to the sd version of cwm, and use that to do a backup of your rom and/or reinstall cwm into the nand partition. It does NOT let you repartition the nand in the process. The partitioning happens via teh daf.exe and flash.cfg, , its daf.exe that does it. cwm just works with teh contents of teh partitions, not teh actual partitions.
If you were really tight on space, you could omit the nand recovery partition altogether and only ever run cwm from sd, gaining a whole FIVE MEG to put towards the data partition!