Database Users

[Q][11Jan] Possibly silly question about Clockwork recovery..

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

[Q] ClockworkMod Recovery Issues

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.

Bit of a noob here, got a quick question!

So I just bought a HD2 last week, after a little trial and error I managed to install this ROM http://forum.xda-developers.com/showthread.php?t=1117787 following the guide in the thread.
Every thing is running fine, no bugs, really fast and am really pleased with the phone and rom.
The only thing that I am a little unsure of, is that looking around the forums at other roms and also in the MIUI forums I see a lot of people talking about needing specific cache/partition/swap (not exactly sure which) sizes to run each ROM, in the MIUI forum it says "rom need to be at 150mb for magler/cLK to work right."
But following the guide for the ROM there is no mention of this an I did not do this step, the only thing I did was use CWM to create a EXT and swap (just chose sizes I thought would suffice) to get apps2sd to work once I had installed the rom.
Now I know the ROM runs fine but my question is will it run any better if I created the correct sized cache/partition/swap (whatever the hell it is!!)?
Sorry for sounding such a noob but this phone is a little different from my old hero to install ROMs on

When you flash clockwork mod you can edit the size of the system.
Open the folder of clockwork mod you downloaded and edit flash.cfg file with notepad and change system size to 150M .
That´s it

When you flash clock work mod???
As far as I can tell CWM just runs of my SD card (if I wipe the files off the SD card that are provided with the rom, it doesnt load CWM when I hold the power button then choose the number one option)
This is what I dont get, is CWM supposed to be permanently flashed to the nand as well, like the ROM is? And if it does just run off the SD, then why does it need a certain system size and what does this do?

Okay i think i have to write much now
Okay first you flash magldr (it´s the ´base´)
then you flash Clockwork Mod via USB Flasher option in magldr:
"For MAGLDR 1.13, booting from NAND:
Download the file attached
Download a partition layout incl. recovery from this thread which fits your ROM you want to use best and unzip it into "C:\recovery" for example
Copy over the recovery image file from inside the zip archive into this folder "C:\recovery", delete existing "recovery-raw.img" and rename copied image file to "recovery-raw.img"
Flash the recovery and partition layout using "DAF.exe" as usual and described in the thread of raiderx or the ROM provider
Boot Recovery with menu point "8. AD Recovery"
You're done"
Go here to get it :http://forum.xda-developers.com/showthread.php?t=987531
Before flashing it edit the flash.cfg file like i described it before ,then flash the .zip ROM..

Thanks for the detailed reply, so I'm gathering that this will install CWM onto my nand, but as I have the ROM running fine and don't really mind that CWM runs from the SD card, are there any benefits to doing this?? And will I lose some storage space on the phone if I do this?

you can use the sd version too
I suggest that when you change your ROM next time ,use the nand version with the right partition .

[Q] I am very confused!!!!

Since some days and i 'm downloading ROMS EU or others.
I become very confused as i'm looking for ROM that can flashed easy way as attached here that 1st snap-shot shows that after extracting ROM downloaded that there is no file DFA.EXE to run but instead of that all there are folders.
although installation instructions said that run DFA.EXE.
I did not see that file except in one and old version.
I need to have newest version.
Here i flashed my HD2 within 10 minutes and it was very good exp to this transform to android and no more windows!!!!
Guys,
How can i have a flash that contain DFA.EXE and it does not rely on SD
I downloaded 3 ROMS but all of them are folders with no DFA.EXE is there some ways that to know if ROM file has a DFA.EXE file instead of downloading and waste my time as my connection is little bit slow!!!!.
My HD version is MIDDLE EAST

The rom you opened in second Screenshot doesn't use dark forces flasher.
You will have to flash a recovery (clockwork mod). And flash the rom via clockwork mod.
It makes flashing much easier and you can make backups etc.
For tutorial see the android nand section -> roll up sticky.
Look out for how to flash your first rom and clockwork mod.
Hope that helps you
Sent from my HD2 using xda premium

It makes flashing much easier and you can make backups etc.
Click to expand...
Click to collapse
Did you miss the bit where he says he wants one that doesn't rely on SD card?
@OP No there are very few roms that use daf.exe, nearly all use cwm and SD card.
You could learn how to load a cwm rom into the android sdk on the PC, then dump the system and boot folder to images and replace the system and boot images in the old daf rom folder, remembering to adjust flash.cfg partition size for the new system size.

samsamuel said:
Did you miss the bit where he says he wants one that doesn't rely on SD card?
@OP No there are very few roms that use daf.exe, nearly all use cwm and SD card.
You could learn how to load a cwm rom into the android sdk on the PC, then dump the system and boot folder to images and replace the system and boot images in the old daf rom folder, remembering to adjust flash.cfg partition size for the new system size.
Click to expand...
Click to collapse
Oh yes but he maybe he will notice that cwm is a very useful flasher etc.
Sent from my HD2 using xda premium

Enabling storage of EXT4 on SD-card

Hi
I recently installed a Sense 3.x ROM from the Sensation XL Android 2.3.5 and I got only 9MB of free space. I have an initrd-patcher for ICS and JB, but I doubt that it will work on older versions of android.
Is there a way to make android 2.3.5 use the EXT4 partition on the SD-card?

Yes, you have to flash an a2sd or DataOnExt script after first boot/flashing the rom immediately. Of course, while having an ext partition created beforehand.

Marvlesz said:
Yes, you have to flash an a2sd or DataOnExt script after first boot/flashing the rom immediately. Of course, while having an ext partition created beforehand.
Click to expand...
Click to collapse
Thanks for the reply. Can you recommend a good script for doing this?

I'd suggest this one, but there's a whole lot of other ones. So if this one doesn't work well or you don't like it, don't come here asking for another one. Instead, go out there and look for the one that you like.

Marvlesz said:
I'd suggest this one, but there's a whole lot of other ones. So if this one doesn't work well or you don't like it, don't come here asking for another one. Instead, go out there and look for the one that you like.
Click to expand...
Click to collapse
and just a little clue to help out a little bit
its in the second post of the thread that Marvlesz link to

I used initrd_patcher_v2 on Gingerbread 2.3.7 and it's worked fine. So it should work on GB 2.3.5 as well. Remember to make an EXT4 partition on your SD before any installation, via recovery, and remove any script like a2sd from zip ROM.

eclyptos said:
I used initrd_patcher_v2 on Gingerbread 2.3.7 and it's worked fine. So it should work on GB 2.3.5 as well. Remember to make an EXT4 partition on your SD before any installation, via recovery, and remove any script like a2sd from zip ROM.
Click to expand...
Click to collapse
I tried to search for initrd_patcher_v2 and found this one: http://forum.xda-developers.com/showthread.php?p=36049396
I tried running it on my system, but freezes up just before boot-animation.
I use the SENSATION XL ROM V 3.0 STOCK from here: http://forum.xda-developers.com/showthread.php?t=1316632&highlight=sensation+all+in+one
I can't seem to find any a2sd-scripts in the ROM zip, but there's a sd-ext folder inside the ZIP.

CTSRP said:
I tried to search for initrd_patcher_v2 and found this one: http://forum.xda-developers.com/showthread.php?p=36049396
I tried running it on my system, but freezes up just before boot-animation.
I use the SENSATION XL ROM V 3.0 STOCK from here: http://forum.xda-developers.com/showthread.php?t=1316632&highlight=sensation+all+in+one
I can't seem to find any a2sd-scripts in the ROM zip, but there's a sd-ext folder inside the ZIP.
Click to expand...
Click to collapse
Can you do a fresh installation again of this ROM or you try to keep all you data which you using right now?

Sv: Enabling storage of EXT4 on SD-card
I tried from a fresh install, before booting the first time, and also from an aleady configured installation.

CTSRP said:
I tried from a fresh install, before booting the first time, and also from an aleady configured installation.
Click to expand...
Click to collapse
You don't understand, I mean can you format you phone and install this rom again with my advices?
Did you made an EXT4 partition of 1GB or more, with Mini Tool (free), on your sd BEFORE fresh installation of this ROM?
I checked your ROM and the script (apps2sd) is already in that ROM so you probably make a wrong Installation.

Sv: Enabling storage of EXT4 on SD-card
I do understand what you say. I made a task29, clk repartition and recovery from hd2toolkit. Under installation the installer asks if I have 1024mb us model or 512mb EU version. I selected the EU version, as this is the one I have. The only question it asks me is if I have magldr or clk.
After that it returns to clk recovery and I press reboot now. I have created the ext4 partition before I even tried installing android the very first time.
If you want, I can perform a new installation with a video recording to document the process

CTSRP said:
I do understand what you say. I made a task29, clk repartition and recovery from hd2toolkit. Under installation the installer asks if I have 1024mb us model or 512mb EU version. I selected the EU version, as this is the one I have. The only question it asks me is if I have magldr or clk.
After that it returns to clk recovery and I press reboot now. I have created the ext4 partition before I even tried installing android the very first time.
If you want, I can perform a new installation with a video recording to document the process
Click to expand...
Click to collapse
Do not use CLK or HD2toolkit this time.
I will recommend to do in this way, before touch your phone format your SD with GUIFORMAT (look here on XDA for it) in FAT32 normal mode (no quick), after format the SD use Mini Tool and make a ext4 partition of 2gb (2048mb) at the end of the SD, so when you look at the partition the ext partition have to be at the right side of you. Put inside the SD the zip of Sensation XL 3.0 only, do not do anything else with your sd.
Format your Phone with Task29, reboot in Bootloader,
Flash MAGLDR 1.13 for HD2,
From MAGLDR 1.13 via USB Flasher flash the Recovery Touch Beta 8, (I provided you the Recovery ready for you, unzip and flash)
Reboot in MAGLDR,
put the SD into the Phone,
run Recovery,
Do a wipe data and wipe cache partition and wipe dalvick cache,
Install from sd the zip via recovery,
In Aroma do not select any option if you don't know anything about it, the installation will recognize the EXT4 partition automatically and you ready to GO, GO, GO.
Let me know.