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
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 just got my HD2 repair but i think they just gave me new one cuz my old one had a nick on the top left corner and this one doesn't (bigger bonus)
the point it that the phone is 100% stock but i reflashed HSPL and MAGLDR
but at the moment i don't have an SD card so i can't do anything with Android Recovery , and i found the Desire S Build but its only CWR flashable
so
my
question
is
...
is it possible to convert a CWM android build to a DFT flasher
With magldr 1.13, you can flash cwm srraight to nand, no need for sd card
Sent from my HTC HD2
huggs said:
With magldr 1.13, you can flash cwm srraight to nand, no need for sd card
Sent from my HTC HD2
Click to expand...
Click to collapse
Problem is that CWM requires SDcard to flash.
Would be nice if there's a CWM-to-DFT converter. Or maybe I just dont know about it?
that would be the best,
There's no possible way to convert .zip files to DFT ones as of yet. I doubt there ever will be too.
Why don't you just buy a cheap 4GB SD card or something?
i was thing of extracting the files of the zip and then converting the system folder and the recovery folder into iso's and then finding a dft build and replacing the iso's in the folder with the iso's i made
humpinbaybays said:
i was thing of extracting the files of the zip and then converting the system folder and the recovery folder into iso's and then finding a dft build and replacing the iso's in the folder with the iso's i made
Click to expand...
Click to collapse
i asked exactly that a day or two ago, but the meta inf folder aparently contains symbolic link info that wouldnt get integrated when you converted the system folder into an img.
quote
greg17477 said:
Extracting the system folder from CWM zip wont work. Its because during the zip installation the updater script is beeing called and it creates a lot of symlinks. So, if you just extract and convert, you will miss the whole bunch of symlinks (and permissions, etc..)
Click to expand...
Click to collapse
There is a simple one click daf to cwm converter, HERE, perhaps it can be reversed? (i dont have time to look at that stuff,) .. the bat file is a simple set of commands, perhaps run the commands in reverse (using the appropriate tools, should they exists, , spare few hours anyone?)
that's what i was thinking but when you go from img to zip it doesnt have the META folder , so maybe with some builds its possible
It does have the Meta info,its in a folder in the img2cwm tools folder.
so is it possible to go from CMW to DFT????
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 .
Hello everyone, quick question, I am trying to install a new ROM on my HD2 and it requires 190mbs of system partition but mine only has 150mbs. My question is can I install the ROM even though the cwm partition size is only 150mbs?
ROM I am trying to Flash: http://forum.xda-developers.com/showthread.php?t=1354267
I have searched everywhere and haven't found an answer but if I can't I know I can use HD2 Nand ToolKit and install a a custom system partition. Thank you
You're going to have to re-partition. If the Chef says 190is needed, you can't stuff 190MB into 150MB of space. Just do a nandroid backup if your worried about losing stuff from your current build or are unsure of the new build. And copy your pictures/music/ringtones to your pc. Besides pictures, what will you really lose if you reformat anyhow?
Ahh I see, thank you for your prompt reply. I have done a backup as you suggested and I'm going to change the size thanks again
Just reflash clockwork........ in the clockwork file on your pc edit the " flash.cfg " change the system partition to whatever you like 200, 250
Sent from my HTC HD2 using XDA App
Change to clk 1.5. You can repartition without connecting to a computer or anything.
Sent from my HD2 using xda premium
Sir,
I installed ICS_Cm9 V1.3.3 via CWM - install Zip method and it is working fine.
I wanted to try a different rom Jelly bean CM10.2 afresh via the same method. But I failed as it did not install.
I found that ICS directory structure is of 4 folder and a file I.e. boot, data, meta-inf ,sys and a file
whereas the dir structure of Jelly bean of 7 folders including sdcard, mod & custom.
Is this not the proper nand build and if so from where I can download an update or build compatible with CWM 5.0.2.6. partition is 250 mb.
or is there a way to tweak the 7 folders to 4 and proceed.
Please guide.
forgive my ignorance.
I tried many links but failed.as all the nand roms I have downloaded are of 7 dirs.
thanks
vkwd7.
vkwd7 said:
Sir,
I installed ICS_Cm9 V1.3.3 via CWM - install Zip method and it is working fine.
I wanted to try a different rom Jelly bean CM10.2 afresh via the same method. But I failed as it did not install.
I found that ICS directory structure is of 4 folder and a file I.e. boot, data, meta-inf ,sys and a file
whereas the dir structure of Jelly bean of 7 folders including sdcard, mod & custom.
Is this not the proper nand build and if so from where I can download an update or build compatible with CWM 5.0.2.6. partition is 250 mb.
or is there a way to tweak the 7 folders to 4 and proceed.
Please guide.
forgive my ignorance.
I tried many links but failed.as all the nand roms I have downloaded are of 7 dirs.
thanks
vkwd7.
Click to expand...
Click to collapse
Usually the structure is the same. Also you're not supposed to look inside the zip folder because that's not the issue, you just copy the whole .zip file onto your sdcard and flash-as-zip from CWM.
Are you sure you've downloaded the correct file?
There are more directories in the rom.zips of latest roms because there are more than one way of installing the rom eg nand only, dataonext, nativeSD and sometimes DirectSD. You get to choose how to install the rom in aroma installer which appears after flashing.
If you want a nand only installation, just choose that option in aroma.
If you have an international (not tmous) hd2, you may find no room for apps since latest roms may be a bit larger than ics, in which case you will have to create an ext4 partition on your sdcard and use dataonext or nativesd.
nand roms builds flashable with different directory structure
Robbie P said:
There are more directories in the rom.zips of latest roms because there are more than one way of installing the rom eg nand only, dataonext, nativeSD and sometimes DirectSD. You get to choose how to install the rom in aroma installer which appears after flashing.
If you want a nand only installation, just choose that option in aroma.
If you have an international (not tmous) hd2, you may find no room for apps since latest roms may be a bit larger than ics, in which case you will have to create an ext4 partition on your sdcard and use dataonext or native sd.
Click to expand...
Click to collapse
Thanks and to all those who advised .
In fact, I earlier installed Nand rom on Htc hd2 (international) via recovery 3.0.....However, through the same recovery I tried to install latest roms that are installable only through recovery 5.0.2.6 with aroma installer, that now I understand. I never knew it.
With your guidance and of the forum , I am now able to install roms via all the three methods and am having fun with the hd2 that was discarded by my daughter and after I had lost mine.
People are so nice here.Tthey have helped a person aged 70 to do things for himself so far discarded phones are concerned.
thanks again
vkwd7.