Database Users

[Q] Can't install a .zip rom from clockwork recovery... what am I doing wrong?

I searched for quite a while, and never found any ideas on how to fix this issue.
I followed the youtube video and got the clockwork mod installed correctly. However, anytime I try to install a rom via recovery, it shows that it's installed successfully... but after rebooting, my device freezes on the boot screen (after magdlr displays GO GO GO.)
I've tried 2 different roms, both MDJ builds, and they both do the same thing. I made sure to wait 15 minutes when booting for the first time, thinking it may be slow on first boot... but it never booted. Does anyone know the partition size to use for MDJ's roms? I thought this might be part of the problem, but I'm open to any ideas and suggestions.
In the meantime, I'll just install via Magdlr... but I would really love to have Clockwork mod working. So, any help with this is greatly appreciated.

Make sure you have HSPL 2.08.
Make sure your Radio is at least 2.10.50 and above.

Done and done.

Then you need to Partition the NANDFLASH.
flash.cfg
Code:
misc ya 1M
recovery ya|ro 5M
boot ya|boot|ro 5M
system ya 150M
cache ya 10M
userdata ya|asize|hr allsize
I use the above for MDJ Gingerbread, but now, I am thinking of allocating 350M to system partition instead of 150M which is too small to play with other ROMs.
Finally, after you repartition, boot into Clockwork Recovery on your SD Card, then install ZIP.
After you are done, turn off your device and remove the SD Card. Turn on the device and see if it works.
Clockwork cannot partition your NANDFLASH, which is why you need to use DAF.exe and flash.cfg file to partition the NAND.

gilla409 said:
I searched for quite a while, and never found any ideas on how to fix this issue.
I followed the youtube video and got the clockwork mod installed correctly. However, anytime I try to install a rom via recovery, it shows that it's installed successfully... but after rebooting, my device freezes on the boot screen (after magdlr displays GO GO GO.)
I've tried 2 different roms, both MDJ builds, and they both do the same thing. I made sure to wait 15 minutes when booting for the first time, thinking it may be slow on first boot... but it never booted. Does anyone know the partition size to use for MDJ's roms? I thought this might be part of the problem, but I'm open to any ideas and suggestions.
In the meantime, I'll just install via Magdlr... but I would really love to have Clockwork mod working. So, any help with this is greatly appreciated.
Click to expand...
Click to collapse
I have the same problem

What is the brand, size and class rating for your MicroSDHC card?
Have you tried doing a low level format on the card yet?
It is not that hard to choose a partition size for system.
Look at the size of the system.img, then allocate that size. So say system image file is 237MB, you just allocate 250MB.
350MB seems to cover most of the DesireHD stock CW rom.
250MB covers most other custom CW rom
150MB covers MDJ's Gingerbread 2.3

[Q] AD RECOVERY fails after flashing CWM

Dear Friends,
I usually flash ZIP Android using CWM, through menu no.8 in MAGLDR menu. CMW was flashed via USB Flasher menu no.5 in MGLDR menu.
But after several times of failures, I gave up. I hope somebody can inform me what went wrong.
Here is the issue:
After flashing CWM (partition layout) and try to go into recovery mode, the screen says:
"ANDROID LOAD RAW
ERROR: ERROR: Cannot read kernel image"
I tried so many attempts but always like that. I did task 29, reflashing MAGLDR, radio, I even tried to go back to Winmo and back again to reflash HSPL 2.08 and so on. But no luck
I remember that this happen after I tried flashing CWM using SD Card method (via menu no.2 in MAGLDR). If I used this method, I can go into recovery mode. I dont like this method, because I never succeeded flashing ZIP ANdroid using this method. That is why I want to go back to recovery mode via menu no.8 in MAGLDR.
Is the problem related with what i did (flashing CWM via SD Card method)? Is the NAND is damaged?
Is there a way to solve that?
Many thanks in advance

silverwind said:
After flashing CWM (partition layout)
Click to expand...
Click to collapse
what are the contents of flash.cfg? (you can open that file in notepad)

samsamuel said:
what are the contents of flash.cfg? (you can open that file in notepad)
Click to expand...
Click to collapse
Which one? is it the one with CWM partitioner lay out?
This one was flashed when I tried to flash: Ultimate Droid v.3.1.1.v2:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 30M
userdata ya|asize|hr allsize
And this one is the standard one with 150MB lay out:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 44M
userdata ya|asize|hr allsize
I used either one as per instruction in the relevant thread

hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?

samsamuel said:
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
Click to expand...
Click to collapse
Yes. Never happened before until I flashed cwm using ad method as explained in the following:
http://forum.xda-developers.com/showthread.php?t=987531

once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience

Richy99 said:
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Click to expand...
Click to collapse
After flashed Recovery via AD SD boot, I flashed the ROM. But it won't boot. So, I decided to reflashed Recovery via USB FLasher (of course I did task 29, flash MAGLDR again).
After that, I went into MAGLDR menu and selected no.8 (AD Recovery). And, it wont boot to Recovery. It says ERROR cannot read kernel image.
My point is that I want to flash ROM via CWM (this CWM was flashed via USB Flasher), but the CWM itself failed to boot (after successful flashing).
I dont have problem boot into CWM if it is flashed via AD BOOT (menu no.2 in MAGLDR) and I cant flash the ROM (though the ROM fails to boot).
Any idea?

ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.

samsamuel said:
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
Click to expand...
Click to collapse
Yes Magldr 1.13. I didn't restore any nandroid backup. How can I restore if recovery failed to boot?
It seem this tweaked cwm did/wrote something In the NAND that cannot be erased by task 29 or by flashing stock rom. I stiil can bot recovery through AD boot (menu no.2 in magldr) the tweaked recovery show version 3.0.1.9. Maybe I
should try mtty?

think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.

As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App

samsamuel said:
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
Click to expand...
Click to collapse
Like I said, I did start it all over again
But, still it didnt help. That is why I am beginning to think that task 29 does not erase all NAND or else there is a damaged/defect in the physical NAND. Should I try use MTTY?

greg17477 said:
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Yes I know. There are 3 methods (as I know from XDA ) to boot Recovery Clockword Mode (CWM). Firstly, flashing via USB Flasher (menu no.5) and after flashing, we should select menu no.8 to go into CWM mode (this one is the issue I am talking about), secondly, flashing via AD Boot (menu no.2), it will directly bring you into the CWM menu, and thirdly, using cLK (which I never try it).
I just wanted to try the second method and it works. However, due to the partition lay out issue (as far as I am concerned, the second method doesnt provide flexibility in providing partition lay out. it uses 150MB lay out). So, for the ROM requires different partition layout, I need to flash CWM in accordance with the relevant ROM requirement. This can only be done if we flash CWM via First method. When I flash CWM (for different partition lay out), it seems flashing successful , but when I selected menu no.8 to go into CWM mode it then says: "Error, cannot read kernel image".
Up to now, I can only boot CWM using second method. I just hope the dev of this method can provide a way to flash different partition lay out or did I miss something?
thanks

does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.

seadersn said:
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
Click to expand...
Click to collapse
Thank Bro, I will try your suggestion and let u know the result.
I also guess there is something wrong with the NAND, maybe the cluster, block, etc. Maybe need to be defragmented (is there any app for doing that?)
I use standar 150MB partion layout from Raider x and also 135MB layout for flashing Typhoon Cyanogenmod.
I still can flash using DAF, but since there is only few ROM for this method, then I would prefer to go through via CWM
thanks again

sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.

seadersn said:
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
Click to expand...
Click to collapse
Yes, since I tried the SD card CWM (no offense Bro )
You are right, CWM is app you cant live without it if you are an Android lover
I highly appreciate if you can provide DAF version. I only knows how to convert from ZIP to DAF but not the other way round
Many thanks

k, i will create it todays evening ~ 20:00 gmt+1; but first, pls try to test the other tipps (6M for adding "some spare blocks" and if nothing helps cLK pls).
i'll pm you if i'm ready ok?

i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings

seadersn said:
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
Click to expand...
Click to collapse
No need to push yourself mate I am patient enough to learn
For installing cLK, I will do it later because I have to learn it since I am not familiar with it (or else if you have or know tutorial for newbie, i would go for it)
I will start with flashing with Recovery with 150MB layout provided by Raider x. Currently I am using Winmo with HSPL 4.
Here is what I will do:
1. Turn of the phone.
2. Go into bootloader mode
3. Task 29
4. Flashing HSPL 2.08
5. Flashing MAGLDR 1.13
6. Flashing CWM 150MB via USB Flasher in MAGLDR menu no.5
7. Boot into Recovery Mode via MGLDR menu no.8
This is the point where i got the problem. If it works, then I can go into Recovery mode to install ZIP ROM , but if fails then it will say Error: cannot read kernel image and it will bring me back to MAGLDR screen.
EDIT:
After flashing MAGLDR 1.13, the phone reboot and I unplugged the usb cable.
It booted and the screen says:
"Booting Android from SD
Android load at 11800000
from Micro SD
Load zimage
k: / zimage
ssSD kernel open failed"
then it brought me to MAGLDR screen menu.
I thought it is normal, isnt it?
then I flash CWM using USB flasher via menu no.5
After flashing CWM complete, the phone reboot and again it showed the above screen and finally went back into MAGLDR screen.
Here is the same old problem. In MAGLDR screen, I selected menu no.8 in order to boot the Recovery mode.
But it failed and the screen says:
"LOAD ANDROID RAW
ERROR: ERROR: cannot read kernel image"
So, it happens again.
Before I continue with the next trial, I wanna hear your opinion about that.
BTW, the winmo before I started this, is ENERGY ROM.
PC I used is WIN XP SP2.
Battery is full, SIM CArd was in but Micro SD was removed.
Do you think I miss something?
Thanks in advance

[Q] sense 3.5 roms stuck at boot screen

hi guys i have used the Recommands partition for the roms 1GB ext4 partition on my sdcard and tried 2GB, flashed WIPE IT and wiped dalvik also tried task29 and started from scratch, any help would be much appreciated really want to try sense 3.5
thanks

Hi, a possible cause of problem - check your zip file (ROM), copy it to PC and try to unpack, may be it's broken. Sometimes you don't have error message when flashing, but when check on PC it shows errors.

thanks mate i will give that a try

i just extract the 2 roms i have been trying to get to work they seems ok

have you got the correct partition size for the rom ?

Which Sense ROM are you using, anyways?

Try a ext 3 partition on your sdcard then run clean install

thanks guys im sure that i have the correct partition size used HD2 tools and i have been trying to run SENSATION XL ROM EU Clk V 1.0, TBD_Runnymede_sensation_xl and not sure if i have a ext 3 partition i used cLk to partition the sd card thanks again

cozman85 said:
thanks guys im sure that i have the correct partition size used HD2 tools and i have been trying to run SENSATION XL ROM EU Clk V 1.0, TBD_Runnymede_sensation_xl and not sure if i have a ext 3 partition i used cLk to partition the sd card thanks again
Click to expand...
Click to collapse
Have a look at this it enables you to see your partition and convert or revert, might be of some interest to you..... Good Luck.
http://forum.xda-developers.com/showthread.php?t=1154221

can that be flashed on the hd2

cozman85 said:
can that be flashed on the hd2
Click to expand...
Click to collapse
yep... just install via cmw and it will reboot go into ad recovery and you'll see some new options.
Note:Once you reboot it will be gone, if you want it back repeat install.
Nice and handy - Check it out..
Edit: I'm using 4EXTRecovery v2.1.3 RC2 - No problems.

i have had a go at 4EXTRecovery created ext3 and tried ext4 1gb partitions
and copied the rom over through 4EXTRecovery but the rom always hangs at wipe sd-ext

same problem
good morning everbody,
i have same problem - for days i am trying to flash a newer rom and after installing my phone is always keeping to show the bootup logo of each rom i flashed.
i use the magloader 1.13, the recovery 3.0.0.5 and the radio 15.
i am able to install the stock rom of winmo 6.5 from htc (vodafone) an everthing is fine. but going back to a custom android rom is not working anymore.
even if i try to go the "right" way, means:
having the winmo rom --> flashing radio --> flashing magloader --> flashing recovery --> wiping data/reset, wiping cache, wiping that dia*** --> putting rom.zip on the sd card via pc --> installing the zip via recovery. that all works until the phone has to boot. i tried over 8 different roms.
befor i startet to update, i hab an coredroid rom v1.3 and it was booting.
perhaps anybody knows whats my problem with this nd lets me now what i have too look for?
great thanx, cause until now i can only go back to my stock winmo rom and thats boring to me... :-(

Nickman_83 said:
good morning everbody,
i have same problem - for days i am trying to flash a newer rom and after installing my phone is always keeping to show the bootup logo of each rom i flashed.
i use the magloader 1.13, the recovery 3.0.0.5 and the radio 15.
i am able to install the stock rom of winmo 6.5 from htc (vodafone) an everthing is fine. but going back to a custom android rom is not working anymore.
even if i try to go the "right" way, means:
having the winmo rom --> flashing radio --> flashing magloader --> flashing recovery --> wiping data/reset, wiping cache, wiping that dia*** --> putting rom.zip on the sd card via pc --> installing the zip via recovery. that all works until the phone has to boot. i tried over 8 different roms.
befor i startet to update, i hab an coredroid rom v1.3 and it was booting.
perhaps anybody knows whats my problem with this nd lets me now what i have too look for?
great thanx, cause until now i can only go back to my stock winmo rom and thats boring to me... :-(
Click to expand...
Click to collapse
cozman85 said:
i have had a go at 4EXTRecovery created ext3 and tried ext4 1gb partitions
and copied the rom over through 4EXTRecovery but the rom always hangs at wipe sd-ext
Click to expand...
Click to collapse
I'd try this: Back up sd if required.
1/ Remove sd from ph and place in a card reader on pc use "SDFormatter" change options format type to Full (Erase) this will erase the Ext Partition & format the card. Put the card back in the ph.
2/ Volume Down + Power Tri color connect usb. Using "HD2 Toolkit" do Task29 this will wipe the ph.
3/ Tri color Using "HD2 Toolkit" install Magldr (don't know about cLK)
4/ Boot ph go into Magldr navigate To "usb flasher" Using "HD2 Toolkit" select "Magldr repartition" Make sure that you are using the recommended partition size for your rom! Flash partition as directed. Ph will reboot go into "ad recovery" "advanced - partition sd card" select 1024m - 0M this will create 3EXT partition. (Some roms are not compatible with 4Ext) Reboot into "Recovery" select "mount sd" move your "Rom.zip" to sd. Close "mount sd" and select "Install zip from sd - Choose zip from sd" select the zip and install and reboot! .....

thanks everyone for your help after a week digging it was my sd card put a new one in and now running sense 3.5 . thanks again

@ a3r0n1 :
thansk for your advise. it took me some days cause i had no time but after i did exactly what you wrote, my newest coredroid rom is running.
Many Thanks !!!!

[Q] **** Solved **** Cannot install Nand Roms....

:victory:****** Solved *******
Hi, thank you for all of your help and assistance.
It was all down to selecting the correct partitions (and me getting over enthusiastic in flashing roms and not reading FULLY on how and what partitions are required)
I have used HD2 Nand toolkit, and partitioned MAGLDR, then partitioned SD card within Clockworkmod.
Thank you all again for pointing me in the right direction...
Good Evening All,
I am sorry if this has been covered. I have searched the forums but cannot find an answer.
I have read all the FAQ and How-to's.
I am not an exact newbie, I have owned a HD2 before (about 2 years ago) and could install all sorts of different roms (including NAND)
I have Installed my Radio 2.15.50.14
I have installed HARD SPL 2.08
I have Installed MAGdlr 1.13
I ahve installed clockwork mod recovery 1.3 with 400M
Copied rom to root of SD Nexus HD2 jellybean v1.2 [dataonext]
and I have installed Nexus HD2 jellybean v1.2 [dataonext]
this installed fine,
I then decided to try another,
I downloaded QSEA_JB-MUSIC EDITION_V1 and placed on root of SD,
I booted into Magldr, then into clockwork mod
from here i wipe data, and factory reset,
wipe cache partition
and wiped delvic cache.
Then i install zip from sd card QSEA_JB-MUSIC EDITION_V1
when this is done,
It asks me to reboot,
Then it stays on the boot screen, and the rom does not load.....
I can restore the back up from the original rom install. but whatever rom I install (from Nand rom downloads) none of them install...
Please help...
Matt

matt_tee said:
Good Evening All,
I am sorry if this has been covered. I have searched the forums but cannot find an answer.
I have read all the FAQ and How-to's.
I am not an exact newbie, I have owned a HD2 before (about 2 years ago) and could install all sorts of different roms (including NAND)
I have Installed my Radio 2.15.50.14
I have installed HARD SPL 2.08
I have Installed MAGdlr 1.13
I ahve installed clockwork mod recovery 1.3 with 400M
Copied rom to root of SD Nexus HD2 jellybean v1.2 [dataonext]
and I have installed Nexus HD2 jellybean v1.2 [dataonext]
this installed fine,
I then decided to try another,
I downloaded QSEA_JB-MUSIC EDITION_V1 and placed on root of SD,
I booted into Magldr, then into clockwork mod
from here i wipe data, and factory reset,
wipe cache partition
and wiped delvic cache.
Then i install zip from sd card QSEA_JB-MUSIC EDITION_V1
when this is done,
It asks me to reboot,
Then it stays on the boot screen, and the rom does not load.....
I can restore the back up from the original rom install. but whatever rom I install (from Nand rom downloads) none of them install...
Please help...
Matt
Click to expand...
Click to collapse
1-Why? Use the HD2 NAND Toolkit to partition your system according to the developer.
2- Never reboot directly from the "reboot now" option of amarullz's installer. Instead, uncheck the "reboot now" option, click finish and reboot manually from CWM.
(The reboot option somehow makes your rom not boot, at least that happens to me every time)

Marvlesz said:
1-Why? Use the HD2 NAND Toolkit to partition your system according to the developer.
2- Never reboot directly from the "reboot now" option of amarullz's installer. Instead, uncheck the "reboot now" option, click finish and reboot manually from CWM.
(The reboot option somehow makes your rom not boot, at least that happens to me every time)
Click to expand...
Click to collapse
Thanks,
I will give it a go!
Have already downloaded toolkit, and just watching the video on how to use...
Matt:fingers-crossed:

So, do I just use Magldr to partition and don't install CWM?
I tried to re-partition with CWM, but lost magldr.....
What am I doing wrong?
Still cannot install NAND rom.
Going to do Task 29 again, where from there??
Thanks for your help and patience...

try the links below, it might help

matt_tee said:
So, do I just use Magldr to partition and don't install CWM?
I tried to re-partition with CWM, but lost magldr.....
What am I doing wrong?
Still cannot install NAND rom.
Going to do Task 29 again, where from there??
Thanks for your help and patience...
Click to expand...
Click to collapse
I don't use magldr, so I am not sure.
But I think you have to "MAGLDR recovery update" first, and then after it finishes you have to "magdlr repartition". Im not sure though.

How do I just install clockwork mod? Without using Magldr?
If I Task29 first,
What's my next step.....?

After Task29 (don't do task29 again) you have to do the following: http://forum.xda-developers.com/showthread.php?p=25781675#post25781675 until you see the "recovery" .. from there, dont continue to flashing wp7, just put your rom on your sd and flash it from recovery. (don't forget to thank the the one who made the thread/guide)
Don't forget to NOT use 300mb, but use the one written on your rom's thread.

matt_tee said:
How do I just install clockwork mod? Without using Magldr?
If I Task29 first,
What's my next step.....?
Click to expand...
Click to collapse
You can't have CWM without MAGLDR. If you've flashed CWM you shouldn't have lost MAGLDR at all, so I don't know what you did wrong. Task 29s are also almost always useless and unnecessary, if a guide says 'task 29' as the first step then usually you can just skip that part. I find that the best guide is the one in my sig, try it out.

[Q] CM9 & CM10 Boot Failures

Hey guys, really struggling trying to get this working and I'm not sure why. I've been flashing roms to my HTC HD2 (1024 LEO - TMo USA) for a few years now without any issues. For some reason I can not get either of these CM builds to boot properly at all.
- [ROM][720p] NexusHD2-ICS-4.0.4-CM9-HWA V2.8 [NativeSD]
Boots to the grey-ish android text splash logo and cycles through the animation for 1h+. No signs of continued activity.
- [ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]
Boots to green HTC splash text for 10 seconds then phone completely turns off and reboots repeatedly. Left going for 30 min, no change.​
Both installers use the AROMA installer platform. Maybe I'm missing something here? It's been a while since I've tried anything new like the AROMA stuff. I just can't seem to get these to function properly. If there's anything at all I can try to do I would really appreciate the assistance.
I'd like to give 4ext a try, but I'm not sure how I can do that with replacing Clockwork in the process.
Here's my specs:
Environment:
-HTC HD2 (1024 LEO - TMo USA)
-16Gb SD HC Card [512MB Paritioned EXT4 / 32MB SWAP] (Attempted with standard 2Gb SD as well with same setup, same results.)
-HSPL 2.08
-MAGLDR 1.13
-CWM Recovery 5.0.2.7
Things to Note:
-Wipe data/factory reset, Wipe cache partition, Wipe Dalvik Cache, Fix Permissions all run before installations.
-Installations for both ROMS attempted with all 3 installation types (NAND, NAND with DataOnEXT, NativeSD). Exact same resulting errors as listed above, regardless of installation method chosen.
-ROM's zips installed via CWM Recovery's 'Install from SD Card' utility.
-SD Card formated after failed install attempts.
-MD5 verified. No visible file corruptions.
Click to expand...
Click to collapse

This seems quite odd, I assume you've tested other ROMs which boot perfectly? It's possible that your SD simply isn't compatible with MAGLDR (mine isn't) so NativeSD doesn't work. As for NAND/Data on EXT do you correctly repartition in CWM as per the OP of the ROM threads before flashing?

Nigeldg said:
This seems quite odd, I assume you've tested other ROMs which boot perfectly? It's possible that your SD simply isn't compatible with MAGLDR (mine isn't) so NativeSD doesn't work. As for NAND/Data on EXT do you correctly repartition in CWM as per the OP of the ROM threads before flashing?
Click to expand...
Click to collapse
All other ROMs I installed worked fine. SD card has worked fine as well for other builds. After some research I found that doing an SD format/partition via CWM Recovery defaults to EXT3 with no options for EXT4 apparently.
I was able to fix the issue late last night however. I flashed 4ext recovery via CWM and used that to convert the SD card's EXT3 system partition into EXT4. Ran the CM10 install and everything came up perfectly. I still think that's strange though considering I chose a pure NAND install.

warpedcell said:
All other ROMs I installed worked fine. SD card has worked fine as well for other builds. After some research I found that doing an SD format/partition via CWM Recovery defaults to EXT3 with no options for EXT4 apparently.
I was able to fix the issue late last night however. I flashed 4ext recovery via CWM and used that to convert the SD card's EXT3 system partition into EXT4. Ran the CM10 install and everything came up perfectly. I still think that's strange though considering I chose a pure NAND install.
Click to expand...
Click to collapse
Oh darn it! I came a little too late to help you. When I first opened this thread, I told myself "damn, too much letters and words! will look at it later." when the issue is actually easily fixed. Sorry!
I was on NAND (cLK), but then I wanted to try nativesd. so I flashed about 3 nativesd roms, but non of them worked. I switched from cwm to 4EXT recovery and voilà, everything worked!
I had almost exactly the same set up, except the recovery. It is indeed weird why cwm doesn't work whereas 4ext does.

Marvlesz said:
Oh darn it! I came a little too late to help you. When I first opened this thread, I told myself "damn, too much letters and words! will look at it later." when the issue is actually easily fixed. Sorry!
I was on NAND (cLK), but then I wanted to try nativesd. so I flashed about 3 nativesd roms, but non of them worked. I switched from cwm to 4EXT recovery and voilà, everything worked!
I had almost exactly the same set up, except the recovery. It is indeed weird why cwm doesn't work whereas 4ext does.
Click to expand...
Click to collapse
No problem, I appreciate at least knowing I wasn't the only one to have issues with it! Maybe you can still help me out though.
The only way I am able to boot into 4EXT recovery is by installing a special zip file with CWM each boot; it would load a 1-time instance of 4EXT recovery. Is there some way to flat-out replace CWM with 4EXT? Until CWM has EXT4 formatting capabilities, I'm not seeing the advantage of it with these new ROMs being so dependent on it. Or maybe it's because of the AROMA installers, which I definitely see as being the new preferred standard for ROM installation packages.

NexusHD2-JellyBean-CM10_V1.3a and VJ CM10.1 | Jelly Bean 4.2.1
hi guys
help me ...
Sorry for my post here
i cant post in [DEV/ROM/4.2.1] [Jan 26 2013] VJ CM10.1 | Jelly Bean 4.2.1 - v4.6 for HD2's topic
wifi fixed for this rom ?
and on NexusHD2-JellyBean-CM10_V1.3a disabled lock screen animation!
can enable animation lock screen ?