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
Hi
I have a big problem and don't know what is wrong
I was using ultimate droid on nand on my hd2,than i decided to flash shiftpda rom v33 from boyPPC and the problems started. i installed it from my sd card using cwm and when phone rebooted first time magldr said something about missing kernel file. then i tried to flash it again,did task 29 several times,installed magldr and everything again. but it kept saying about missing kernel file. and when i try to install it again cwm says 'installation aborted'. so i decided to flash it from pc with daf.exe. installation was successfull,but phone just reboots over and over again... looks like it will never stop rebooting. dont know what to do please help...
can it be due to wrong radio?
zurjap said:
Hi
I have a big problem and don't know what is wrong
I was using ultimate droid on nand on my hd2,than i decided to flash shiftpda rom v33 from boyPPC and the problems started. i installed it from my sd card using cwm and when phone rebooted first time magldr said something about missing kernel file. then i tried to flash it again,did task 29 several times,installed magldr and everything again. but it kept saying about missing kernel file. and when i try to install it again cwm says 'installation aborted'. so i decided to flash it from pc with daf.exe. installation was successfull,but phone just reboots over and over again... looks like it will never stop rebooting. dont know what to do please help...
Click to expand...
Click to collapse
Can you explain the exact steps you made to install this Rom?
well i will explain what am i'm doing right now. i run task 29 and installed radio 2.15.50.14. after that i installed mgldr 1.13. and on mgldr booting screen it said "sd open kernel failed". after that mgldr menu appears. then i choose usb flasher and install rom from the computer. it says installation successful and phone reboots. after that i see mgldr booting screen and everything looks just fine,then i see HTC screen and phone reboots again...and again and again and again. if i will just put the phone on the table it will just keep rebooting forever ((( am i doing anything wrong? i shouldnt because its not the first rom i am installing...and what does that "sd open kernel failed" message mean??? (
1) First of all, boot into MAGLDR and go to services (option 10). Go to boot settings, Boot source and make sure Android from Nand is selected.
2) Unzip the Boyppc v33 package on your computer and install his CWR DAF package that is included with the rom (The boot loops could be due to having the wrong CWR partition)
3) Load CWR and manually wipe data/factory reset, Go into advanced and wipe Dalvik Cache. Once this is done try and reinstall the V33 zip that you said you had already copied to your SD card. Hope this solves the problem
I've had the same problem twice now. "sd open kernel failed" i believe is shown in red correct? all i did to fix it was reflash MAGLDR & Clockworkmod Recovery then reflash the ROM.
i wish i knew why it happened but its always when im going from 1 ROM to the next & not just restarting my phone up. im thinking maybe it was just a bad flash or something but the steps above has fixed it for me now both times.
try to install recovery and intall a ron throught ur sd card ... rom that r instaleed from daf r pretty simple but maybe the rom was corrumpted during the download or there's a missing file that's not flashed to ur phone ... i suggest to install recovery and to copy ur rom to sd ...it's much simple than the first way
I'm a noob and getting really frustrated.
I Wipe (Type 29) my phone and reinstalled MAGLDR v1.13, Radio & HSPL 2.08 just fine with HD2 Android NAND Toolkit. I can't get CWM on my phone to save my life. When I go to AD Recovery it says "No boot source" and I don't know how to get it back so I can load a new ROM.
PLEASE HELP ME IF YOU CAN!!!!!!!!!!
Thank you very much in advance for your help.
you said youve flashed hspl, radio, and mag ... you made no mention of flashing a CWR. just as a rom has to be flashed to boot up ... so does CWR or else theres nothing to boot. im not trying to flame or insult ... sometimes we miss the small things in our hurry to get to the party! i truly hope its as simple as this :-D
go to usb flasher (i believe option 5 in magLDR) and flash the CWR. Then boot AD Recovery ...
That is strange the toolkit should have installed CWM, but it seems that it didn't. Your next option is to download CWM and install it manually. Just be sure that the flash.cfg is setup correctly for your phone and rom that you want to install. the latest version is 5026 and can be installed via usb from magldr.
You can get it here at the end of the second post.
http://forum.xda-developers.com/showthread.php?t=987531&page=98
I have flashed several roms using CLW already and it always worked fine, but now I'm really stuck.
The problem is that I installed the Hyperdroid CM7 rom. It worked fine. But when I wanted to install the Google Apps I just couldn't get into the recovery mode from the MAGLDR menue anymore. It just says "ERROR ERROR: Cannot read ramdisk image". I tried to update the CLW using the Rom Manager but it didn't solve my problem. Unfortunatelly I also can't boot the rom anymore now (I can't since I formated the SD card).
Can I now just install CLW again (over the existing version) with the "USB Flasher" option from the boot menue? Or can I repair the installed version somehow?
Is there a way of installing CLW under Linux? I've tried using WINE to run the daf.exe but it didn't work since it couldn't find the the usb connection.
Which would be the preffered method of installing roms NAND roms with Linux?
Thanks for any help in advance!
Mr.Mobody said:
I have flashed several roms using CLW already and it always worked fine, but now I'm really stuck.
The problem is that I installed the Hyperdroid CM7 rom. It worked fine. But when I wanted to install the Google Apps I just couldn't get into the recovery mode from the MAGLDR menue anymore. It just says "ERROR ERROR: Cannot read ramdisk image". I tried to update the CLW using the Rom Manager but it didn't solve my problem. Unfortunatelly I also can't boot the rom anymore now (I can't since I formated the SD card).
Can I now just install CLW again (over the existing version) with the "USB Flasher" option from the boot menue? Or can I repair the installed version somehow?
Is there a way of installing CLW under Linux? I've tried using WINE to run the daf.exe but it didn't work since it couldn't find the the usb connection.
Which would be the preffered method of installing roms NAND roms with Linux?
Thanks for any help in advance!
Click to expand...
Click to collapse
ROM Manager isn't compatible with MAGLDR, which is probably why your phone was messed up when you tried to use it. It only works if you use the cLK bootloader. As for your problem, I really can't see much else you can do other than fresh installing CWM through USB Flasher. I don't use Linux so I can't help you there, sorry.
Oh, I wasn't aware that MAGDLR isn't compatible with the ROM manager because it came with the MAGDRL/CWM rom i flashed. But thanks for that information!
Can I just install CWM "over" the allready installed but not existing version? Or will that cause even mor eproblems?
Mr.Mobody said:
Oh, I wasn't aware that MAGDLR isn't compatible with the ROM manager because it came with the MAGDRL/CWM rom i flashed. But thanks for that information!
Can I just install CWM "over" the allready installed but not existing version? Or will that cause even mor eproblems?
Click to expand...
Click to collapse
I think that would be fine, there isn't much point in Task29ing unless you are having major issues.
Ok,so since I couldn't get hold of a windows PC yet I couldn't re-install clockwork flashing with USB cabel.
But I couldn't load CWM recovery from SD card as described in this post #4 of this topic: http://forum.xda-developers.com/showthread.php?t=1352395
I was not able install the CWM then in the second step form zip file on the SD card. Some error message appeared, but I was able to flash a ROM. So my CWM is still broken, but the ROM is working fine which is ok for me now. When I get access to a Windows PC I'll re-flash CWM too.
So the "Linux problem" isn't solved but anyone experiencing problems to get into recovery from MAGDRLR menu should try the way in the above mentioned post.
Mr.Mobody said:
Ok,so since I couldn't get hold of a windows PC yet I couldn't re-install clockwork flashing with USB cabel.
But I couldn't load CWM recovery from SD card as described in this post #4 of this topic: http://forum.xda-developers.com/showthread.php?t=1352395
I was not able install the CWM then in the second step form zip file on the SD card. Some error message appeared, but I was able to flash a ROM. So my CWM is still broken, but the ROM is working fine which is ok for me now. When I get access to a Windows PC I'll re-flash CWM too.
So the "Linux problem" isn't solved but anyone experiencing problems to get into recovery from MAGDRLR menu should try the way in the above mentioned post.
Click to expand...
Click to collapse
Glad to hear it You aren't putting CWM 5.0.2.6 SD as a zip on your SD card by any chance are you? Because you need to extract it to your SD, I misread it first time around and was quite confused as to how that worked as a .zip file.
http://forum.xda-developers.com/showthread.php?t=1352395
this should help
deckoff said:
http://forum.xda-developers.com/showthread.php?t=1352395
this should help
Click to expand...
Click to collapse
LOL, I linked you to that thread on your other post because I saw it on this thread, and you've now managed to make it come back around here
Nigeldg said:
LOL, I linked you to that thread on your other post because I saw it on this thread, and you've now managed to make it come back around here
Click to expand...
Click to collapse
Endless loop, they say
At least this means I read what it says