Phone shut down, will only boot to MAGLDR screen now and errors out when you try to get to android. The error is:
"sd kernel open failed"
Any ideas on where I should go from here?
Thanks
Wood
Was it successfully running Android before it shut down?
NAND or SD?
What ROM?
What did you do before it shut down, that got you to this point?
As much information about the events and circumstances leading up to your current situation will help others to help you, it's probably something simple why it's not working, but you have to be specific and as detailed as possible to let everyone know exactly whats going on with your phone
huggs said:
Was it successfully running Android before it shut down?
NAND or SD?
What ROM?
What did you do before it shut down, that got you to this point?
As much information about the events and circumstances leading up to your current situation will help others to help you, it's probably something simple why it's not working, but you have to be specific and as detailed as possible to let everyone know exactly whats going on with your phone
Click to expand...
Click to collapse
Yes it was running, NAND , recovery 400M. Just turned screen on to make a call and it was on MAGLDR screen.
In MAGLDR, go down to services, click on it, choose boot settings, choose boot source, choose Android from NAND, and then choose boot AD NAND from MAGLDR's main menu. It sounds like it's trying to boot Android from the sd card, maybe your pocket changed the settings in the MAGLDR menu.
get error "NAND kernel open failed"
Can you load Clockwork Recovery?
If so, you can restore a backup if you have one, or flash a new kernel and see if that helps. Maybe it is a problem with the kernel, although I doubt it. Here's a kernel you can flash which works well for me:
http://forum.xda-developers.com/showthread.php?t=940823
If the new kernel doesn't get it going again, and you don't have a CWM backup made, then it looks like you're screwed and will have to start over with a fresh ROM. But fortunately Android is pretty easy so set up, so in the worst case scenario, you can be up and running with a new ROM set up fairly quickly.
Always make a full backup in CWM at least once every week or two, so that if something goes bad like this, you can easily restore everything back to the state it was in at the time of the backup.
Related
Would it be possible to make a boot loader GUI for the eris to easily select between a few ROM's. Does something like this already exist?
have you seen this?
http://forum.xda-developers.com/showthread.php?t=661413
it will probably do what you are looking for
Kinda... I searched but seemed to have missed that. I'm thinking of something more like a GUI that prompts you when you turn your phone on without booting into recovery. It would then give you the option to choose what ROM you wanted to boot. All this without having to navigate through a recovery boot screen.
rkymtnbum said:
Kinda... I searched but seemed to have missed that. I'm thinking of something more like a GUI that prompts you when you turn your phone on without booting into recovery. It would then give you the option to choose what ROM you wanted to boot. All this without having to navigate through a recovery boot screen.
Click to expand...
Click to collapse
You are referring to a "dual-boot" setup which is highly improbable on the Eris. The Eris is short on internal memory to start with, but to add a dual-boot you would need to partition off the space even more. There just isn't enough space to do that effectively. IMO
Just get comfortable with Recovery and the options are there. You could have nand backups of every rom available and switch them that way if you really wanted.
The problem is, you wouldn't be able to have multiple roms loaded on the phone at the same time (well, at least not easily). There wouldn't be enough space on the phone. The only way I could see doing it would be to create the current back up/restore steps, but that seems like it'd be terribly slow.
FunkyFender said:
The problem is, you wouldn't be able to have multiple roms loaded on the phone at the same time (well, at least not easily). There wouldn't be enough space on the phone. The only way I could see doing it would be to create the current back up/restore steps, but that seems like it'd be terribly slow.
Click to expand...
Click to collapse
I figured that might have been the case. Nand backups would take more time than I would want at boot. Internal space is a little too limited... your right.. I overlooked that. It would have been cool though haha.
Last night I installed Gingerbread 2.3.1 on my HTC HD2.. Followed the directions exactly and was able to boot Android and customize and had no problems. Tonight, suddenly my buttons at the bottom (home button, start menu, back, etc) started flashing -- side note: if anyone knows why this happens and how that can be stopped please let me know!! --, I figured I would just restart my phone. Well, when I restarted, suddenly I had no service when I booted Android.
I have rebooted my phone in the different methods (reboot, recovery, and bootloader), tried powering it off and then turning it back on, tried putting it on airplane mode (dunno why) and then back off, took out the battery and sim and waited for 20 min and then put it back in... Nothing has had any luck.
When I boot Windows Mobile, I have a phone signal, but for some reason when I'm booting Android, it isn't there.
Anyone else have a similar problem or can suggest how to fix this? I really want to be able to continue using Android but that's not going to happen if it continues to have this problem...
Flash official windows again, then try NAND Gingerbread 2.3.4 Its great ROM and all works.
sultans said:
Last night I installed Gingerbread 2.3.1 on my HTC HD2.. Followed the directions exactly and was able to boot Android and customize and had no problems. Tonight, suddenly my buttons at the bottom (home button, start menu, back, etc) started flashing -- side note: if anyone knows why this happens and how that can be stopped please let me know!! --, I figured I would just restart my phone. Well, when I restarted, suddenly I had no service when I booted Android.
I have rebooted my phone in the different methods (reboot, recovery, and bootloader), tried powering it off and then turning it back on, tried putting it on airplane mode (dunno why) and then back off, took out the battery and sim and waited for 20 min and then put it back in... Nothing has had any luck.
When I boot Windows Mobile, I have a phone signal, but for some reason when I'm booting Android, it isn't there.
Anyone else have a similar problem or can suggest how to fix this? I really want to be able to continue using Android but that's not going to happen if it continues to have this problem...
Click to expand...
Click to collapse
try a different rom, the flashing buttons was common on early builds of gingerbread
i take it you are using an sd version rather than nand ?
Try switching to 2G only and see if your signal is back.
Richy99 said:
try a different rom, the flashing buttons was common on early builds of gingerbread
i take it you are using an sd version rather than nand ?
Click to expand...
Click to collapse
Yes, I'm using SD version... To be honest, I didn't really know the difference, but from what I was told NAND basically erases Windows, right? If that's correct, I was afraid of the installation not going right and being stuck without a working phone.
michie said:
Try switching to 2G only and see if your signal is back.
Click to expand...
Click to collapse
I tried going to my settings to switch to 2G, but at first it was greyed out, so I couldn't even select it. Then I clicked Access Point Networks and went back and suddenly it was available to be clicked. I clicked it and went to another screen and for some reason decided to go back to check it and it had been unclicked and greyed out again....
Seems it's a problem related to your rom and not a hardware problem because it works on wm.
Im not familiar with SD roms, maybe you should try a different SD rom or a NAND rom and see if the problem is solved.
Hope u get it sorted !
Since it seems I just need to try a different rom, can anyone suggest a link? I think I want to try SD again just because if I'm having these problems I don't want to completely wipe Windows and not have something to resort back to if I run into something again..
bluur said:
Flash official windows again, then try NAND Gingerbread 2.3.4 Its great ROM and all works.
Click to expand...
Click to collapse
Honestly I don't want to NAND it because I don't want to completely wipe Windows in case I have a problem again... (this is all assuming I understand NAND correctly)... Right now I have a problem so I was able to go back to Windows Mobile. Do you have any suggestions for another SD rom?
Not quite true. You can always go back to Winmo from Android Nand if you are unhappy with it. I used to think the same way but since taking the plunge I've always found it easy to reinstall Winmo in order to use my tomtom navigator
ROM wise there are various fantastic offerings with Android Nand. Some are even spotting the new sense 3. You can try either CoreDroid or LeoRC Mix.
For now head over to the Nand section and read the stickies at the top. There are ample and easy guides on how to prepare your HD2 for a Nand Rom and how you can return to Winmo if you don't like it. If you follow the instructions properly, trust me nothing will go wrong.
Sent from my Desire using XDA App
I'll give it a try, thanks!
I have an HD2 that I had someone flash to android for me.
The phone initially functioned pretty well, although i immediately noticed that the phone would sometimes crash when I launched Navigator.
Months down the road, the phone began crashing more frequently, and now has become a serious concern for me. The phone will crash when running youtube, gps (google & navigator), and sometimes with the camcorder.
Sometimes it will just restart- out of nowhere.
I have about 120 apps- just mentioning-- not sure if this makes a difference--
So I've decided that i would like to change the Rom.
I've been reading through the forum for a while-- I would like to be pointed to the best reference for proceeding with this-- since I haven't actually done this before.
Will I need to go through the process of radios and stuff-- not sure, since i already have an android rom running on the system.
What is one of the better Rom's available, with working features?
Thanks in advance for any help--
here is a shot of my current system:
well i'll say if you ask a 10 people here what ROM is best your bound to get 20 different responces. this is simply because some people rather sence based, some like miui and some prefer CyanogenMod. what i would suggest is a ROM thats rather easy to flash & use so you can get an idea of how to flash it. after you feel comfortable you can check out the vast Android builds the hd2 has to offer.
i would suggest either rafdroid hd found here or bluetopia hd found here. both builds are very easy to flash, just make sure you follow the directions closely and you wont have a problem. you dont need to change the radio more then likely since its probably already been done before. please note that bluetopia is meant for tmous users and not 512. personally i'd check out rafdroid hd anyway just because it has a very detailed description on how to flash the ROM.
both of those are sence builds but if you rather a non-sence base you can look at this webpage for a ROM you rather flash. it lists tons of builds to go through so pick one that you feel would be better for you.
htccraze said:
well i'll say if you ask a 10 people here what ROM is best your bound to get 20 different responces. this is simply because some people rather sence based, some like miui and some prefer CyanogenMod. what i would suggest is a ROM thats rather easy to flash & use so you can get an idea of how to flash it. after you feel comfortable you can check out the vast Android builds the hd2 has to offer.
i would suggest either rafdroid hd found here or bluetopia hd found here. both builds are very easy to flash, just make sure you follow the directions closely and you wont have a problem. you dont need to change the radio more then likely since its probably already been done before. please note that bluetopia is meant for tmous users and not 512. personally i'd check out rafdroid hd anyway just because it has a very detailed description on how to flash the ROM.
both of those are sence builds but if you rather a non-sence base you can look at this webpage for a ROM you rather flash. it lists tons of builds to go through so pick one that you feel would be better for you.
Click to expand...
Click to collapse
Glad to see a fellow hd2 user on Rafdroid HD.
Yes Rafdroid HD is one of the completed sense roms but is not the latest.
Latest roms have sense 3 but will have bugs
You will need this (ClockWorkMod. aka CWM) Flash magdlr first.
http://forum.xda-developers.com/showthread.php?t=1044830
Depending on rom, you will have to choose cwm partition size. RafDroid Hd uses 400mb. Other roms may have to set custom partition size.Click Here for Rafdroid HD
Lastly, you may need sd-ext3 partition. Recommended 1Gb
1)
...If you are still on magdlr flashing method and not cwm boot to magdlr menu.(Hold power button till you see a menu). Press Android Hardreset.(Call button to select, volume keys up/down)
...If on CWM already, boot to magdlr menu and select Recovery. Press the "delete data/factory reset"
2)
Flash a new cwm partition using USB flasher option.
3)
Put rom in sd card (do not unzip the rom, leave it as .zip)
4)
Boot to CWM and select install zip from sdcard. Navigate to rom file and select. Flashing may take up to 15mins or more.(Just be patient, do NOT remove battery when it is flashing halfway, just leave it alone)
5)
Once done press reboot system. First boot may take longer to load. Once it boots to setup phone screen, youre good to go!
OK-- I'm not really following all of this CWM stuff-- I watched the guy who put android on my phone go through the process-- and asked him to briefly detail me the steps--
he never mentioned anything about cwm... so what exactly is that?
since android was already flashed to my device-- what would be the best process of removing the current android system and installing another?
i powered up my phone while holding down volume key--
its reads
PB81120 SSB3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
serial
Click to expand...
Click to collapse
i also know that i have a magldr---
how do i know whether i have tmous or 512?
the_mask313 said:
OK-- I'm not really following all of this CWM stuff-- I watched the guy who put android on my phone go through the process-- and asked him to briefly detail me the steps--
he never mentioned anything about cwm... so what exactly is that?
since android was already flashed to my device-- what would be the best process of removing the current android system and installing another?
i powered up my phone while holding down volume key--
its reads
i also know that i have a magldr---
how do i know whether i have tmous or 512?
Click to expand...
Click to collapse
i would read:
http://forum.xda-developers.com/showthread.php?t=1021837
basically, cwm allows you to flash android roms without using a computer to install. (as opposed to daf.exe roms, which you need to tether to the computer.) it is much more than that, but that is all you need to know now. but read the thread above.
if your hardkey buttons are green/red it is tmousa, 1024
if they are not, it is 512
So- another question-- can anyone take a guess at why my phone is crashing so often--
could it be the number of apps i have downloaded (over 120-- mostly stored to SD)
could it be conflicts in the current ROM being used?
Might it be the battery?
When the ROM was freshly added, the system ran perfectly well, with the exception of Navigator crashing once in a while--
I've probably been running with Android for over 6 months now--
its been acting up for about 3 months now.
problems i often encounter:
crashes when i run-
navigator, gps, youtube, sometimes camcorder
forces closes apps somewhat frequently
I have my system clocked down to around 800mhz on conservative mode, via setCpu, because i feared it was running too hot.
thanks much-- ive read all the posted links--
what i'd like to know-- once i install cwm--
is there a need to wipe the existing rom, before installing another--
or do you just install the desired rom?
yes back up everything 1st. i also like to make a copy of my sd card on my computer. then when your about to flash a ROM you will need tp wipe data & cache. once you've wiped them both you'll need to go down to advanced and select that, go to delvic and wipe that. press back and now you are finally ready to flash the rom by selecting install rom from sd. after it runs dont be alarmed but it can take several mins for it to go through the process. when it says its done then reboot the phone. the boot up time will depend greatly on the rom you've chosen so be patient. it can take up to 10-15 mins for your phone to completly reboot.
htccraze said:
yes back up everything 1st. i also like to make a copy of my sd card on my computer. then when your about to flash a ROM you will need tp wipe data & cache. once you've wiped them both you'll need to go down to advanced and select that, go to delvic and wipe that. press back and now you are finally ready to flash the rom by selecting install rom from sd. after it runs dont be alarmed but it can take several mins for it to go through the process. when it says its done then reboot the phone. the boot up time will depend greatly on the rom you've chosen so be patient. it can take up to 10-15 mins for your phone to completly reboot.
Click to expand...
Click to collapse
this is where i get confused---
where do I "wipe" anything-- what program do i use to do this--
and if I'm "wiping" memory, will i need to reinstall programs like magldr, or any radios, again?
you said "go down to advanced"--- 'advanced' in what running program?
you wipe whats listed above in magldr. you can enter magldr by turning off the phone, then turn on the phone but hold the power button down. you will see magldr pop up if its installed. option 8 is recovery you scroll down my pressing vol up and vol down. to select press the green talk button.
so when you enter magldr you go to option 8, it will go to cwr (recovery) then scroll using vol down/up to wipe data. press the green talk to wipe. do the same thing to wipe cache..then scroll down to advanced and select that by pressing green talk. scroll down to delvic and wipe that by pressing green talk. press back and then select install from sd. now you are able and ready to install a rom. simply select the zip file of the rom you want thats on your sd card. (sorry this should have been listed above..place the rom you want on your sd card) now select the rom by scrolling up or down by vol keys and press talk to select your rom. it will begin flashing. at this point it can take a few mins so dont panic. after it completes you will need to press back button and the reboot phone. when you flash a rom sometimes it can take as long as 10-15 mins for it to boot up. take this time to review and make sure you did every step as its been said and you followed all the instructions listed.
you need to wipe everything between flashes because sometimes there is left over code/data etc that can interfer and mess up your phone. it does not wipe anything like magldr/radio/rom..it really just prepares it for it to except a new rom by deleteing the old data. its the same thing as a factory reset really.
Choosing wipe data/factory reset wipes all the partitions,, cache,dalvik, etcetera, ,, no need to manually clear all the different bits one by one.
yes but a little extra safety precautions never hurt anyone
Watch the screen when you do 'wipe data's, it clears the cache, data,dalvik,sd-ext.... so if you then do them individually too you are wiping already wiped partitions.
i know it goes through them all, i been flashing a looong time since the days of winmo 6. personally i like the comfort of making sure as do a lot of other people here on XDA do. im not the 1st person to suggest doing this. i've seen numerous people give these instruction & i still feel its a good way of double checking before flashing a ROM.
Hi friends,
this is my first post here so I think it's time to say thankyou to the devs and the mods of this forum. really great work.
After my CoreDroid install crashed (most apps wouldn''t start any more) a friend of mine pointed me to the typhoon cm mod. I'm very happy with this mod as it is very smooth und looking good.
My first version was 3.6.5.
Some days after install I noticed that I couldn't start BT. It says "activating.." but then stays off.
I updated today to 3.6.9. but this didn't change anything.
Is there anything I have to configure or am I doing something wrong?
Thanx in advance for your help!
Edit: Hm. No answer at all? Was this a stupid question? When searching this forum I just find bluetooth connection problems. Should I take any steps like task29 and reinstall this mod? Do you need some more information about the phone?
Sorry, just bumping.
Really no one?
Not even a tiny neat hint?
It seems to me as I also have the bluetooth power drain bug (~60mAh in Standby with only 2g/3g activated data off, wlan off and of course no bluetooth active - at least it seems so).
pleeeaasse... heeelp..
Seeing as it's not something that has come up before, you will need to do a cwm backup then do some testing, try a few roms, maybe go back to winmo, post back with what works what doesn't.
Without trying other roms there's no hint whether its hardware or software.
Thank you for this hints.
Would you suggest to do a hardreset after making a cwm-backup? What other steps of precaution should I take between switching between different mods for beeing on the clean side?
no, not a hard reset (assuming you meant a winmo hard reset, , that doesnt do anything), , , if you are flashing another android rom, , in CWM choose 'wipe data factory reset' which will wipe all the partitions, most importantly this will wipe the sd-ext partition and clear the protected android folders on the fat32 part of the sd card.
Do this even if you are going to change the partition size (i.e reflash CWM for a rom that requires a different size) because re flashing cwm will clear all the nand partitions, but wont touch anything on the sd card, and its often the stuff left over on the sd card that causes problems.
I'd try one android rom, and if that doesn't work id go back to winmo stock (if you have a tmous, usual warnings apply to ONLY use tmous stock roms), and if it still doesnt work, its almost certainly hardware fault. had any bumps or bangs?
hm. some problem here: cmw seems to be corrupted. when I press either up or down vol, it seems as if "abort" (red) is also pressed (the hat appears on screen). after pressing up/down vol again, the menue appears again and the marked line moved one step.
this way I can do a backup, but when navigating in the secodn level menues, I fall back to top level menue. :/
Any way I can repair cwm?
I can't remember how I installed it. Think it came with magldr.
What now?
Enter magldr, "USB flashing", flash cwm.
didn't do the trick.
still not able to navigate in cwm.
but: nand gone. no android to boot. :[
Edit: I'm trying to get into the bootloader by holding down vol-down then hold down power. But I get into magldr.
Doing it wrong?
sounds to me like you have a hardware problem with the keys. Also, there are a few threads that talk about not being able to get into bootloader, not read any of them, but thats probably where you should start.
Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.
I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.
I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).
I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.
I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.
Any ideas on how I can get touch working / get a NAND android rom to work again.
Thanks in advance guys
First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen
Go back to the hd2 nand toolkit
1.task29
2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.
3.Select magldr update recovery or cLK install recovery depending on your selection above.
4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.
5. Install ICS from sd card as before
Thanks for the help, I had to flash a different radio version to get magdlr to boot.
I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.
I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
htccraze said:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
Click to expand...
Click to collapse
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks
http://forum.xda-developers.com/showthread.php?t=769026
I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.
Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
htccraze said:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
Click to expand...
Click to collapse
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.
The ROM you linked, I can find download links on the page, not sure if I'm just missing them.
I just tried an SD card rom, its doing the same thing, no touch input is accepted.
Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.
I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.
Another update: I just restored to default using the method listed below.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.
WM boots fine and everything, but still no input is accepted.
I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
Sent from my HTC HD2 using XDA
Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.
It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
Sent from my HTC HD2 using XDA
This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!
The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.