Database Users

jumping to kernel

have a tmo us hd2
had a past version of android with sense it worked fine. tried a different and got the pause at jumping to kernel so tried a clean version, it worked. ive booted it plenty of times, then tonight it stopped working
so im trying froyostone with sense and now it wont boot either
im on omega v7 newest and radio 2.1.5.28_2

I was on the same problem, i think you have the android files directly on your SD Card? So that is the problem, put them in a new folder android.
That helps me, the first boot was by me also possible, but after that all reboots end in "jumping to kernel"

nope. theyre in the android folder.
and i just tried switching to the 2.12 radio
the strangest part is that is was working the past few days and earlier today...
id understand a certain build not working but why would it randomly stop working.

Have you made, since this problem more reboots. I have on my HD2 sometimes that i must boot 2-3 times to come up

yup, tried multiple reboots and both radios

have you solved a problem? I've similar problem. Each time I turn on the phone - I'm getting this error. Sometimes it helps to remove "cache' folder and some others and restart twice or may be 3 times. But no working 100% solution.

My Results
ppp vr.
Market ok
WIFI ok
BT ok
whitout freezes
little bit more sensitive touch screen
Very good job, DEV team you are masters

When I'm getting stuck at jump to kernel, I normally remove and reinsert the sd card when I booted into WM and most of the time that fixes it.

I (and other members) have found that "Jumping to kernel..." freeze occurs when one is using Windows for a period of time. The solution is usually to re-boot and once Windows loads *immediately* boot into Android. This has not failed me yet! Before I was like you, wondering why sometimes I get the freeze and other times I don't...but a fresh boot into Android solved my issue.
Hope this helps.

have you changed the kernal lately or switched any file , or renamed anything

have you tried changing the startup.txt file? look around for that solution..it has been posted here many times.
I would give you a link but I am posting from my cell so it would be a little difficult.
Sent from my HTC HD2 using XDA app on darkstone froyo sense v2

[Q] hd2 hangs when gets warm - might it be caused by rom update and how to fix it?

Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.

Guys,
I'm kindly asking to share your thoughs on any of the questions. It is very important for me since I don't know whether it is my fault or the phone was already damaged.
The rom I tried to flash was a stock rom and the flashing process hasn't been interrupted.
Thank you!

had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.

az_registration said:
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Click to expand...
Click to collapse
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.

Thank you for your replies!
T-Macgnolia said:
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Click to expand...
Click to collapse
Yes, that's a useful tool, but I'm afraid that I might damage the existing rom and will not be able to flash it agian. Also it requires to flash HSPL before which also potentially might brick the device ( I mean the flashing process).
sike222 said:
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
Click to expand...
Click to collapse
So it was a factory defect, wasn't it?
If I did something wrong during the stock rom flashing process, could be the reason of the problem?
Thank you.

After reading forums it seems to me that the issue appears mostly for T-Mobile US version..
If it is a hardware problem, does anybody know what part of hardware is damaged?
Thanks!

[Q]-Android Gingerbread NAND Constant Phone FC and Crash (Full of Details)-

I have been searching all over for answers, but have not found any solid solutions. There was another case similar to mine, HERE but I really don't think things are quite the same. I am new to flashing with HD2, but am very seasoned with the Samsung Vibrant.
I had the phone app crashing and robot voice for a while. I have done all of the supposed fixes but nothing has worked yet. I bought my HD2 second hand, (like the big screen and more RAM better than on my TMO vibrant), but when I got it it was in great condition, completely stock. So I wanted to put android on it because MinMo is (for my concerns) unusable. SO, here is what I have done.
Started with a TMO(US) HD2 Stock
-Flashed New Radio from 2.14.50.02 to 2.15.50.14
-Flashed HD2O WM 6.5 ROM (Phone Worked fine, but decided WinMo sucks)
-Flashed MagLDR
-Flashed CWM
-FLashed BOYPPC SHIFT PDA sense&HOneycomb (FAST!)
But then whenever I tried to make phone calls I get the robot voice and three seconds later, crash. (the process phone in com.android.phone is not responding...)
-The first fix I tried was HERE for the Low volume fix. No Dice...
-Then I Tried this Volume Fix HERE, but did not fix problem.
-I tried disabling the contact sync, seen in another thread, and still nothing.
-Went into Rom Manager, Flashed Clockwork recovery, then used it to "fix Permissions"
-During the permission fixing, I received a normal clear phone call with no FC.
-Then after call it said that it was done with permissions, and asked me to restart.
-After the reboot it would just constantly Force Close every five seconds, and it was not showing any network signal.
So Then I:
-Flashed a new Radio. -2.06.50.04 -TMO US
-Still Not working
-Went back to the MAGLDR and did an AD Hardreset, and tried flashing HYPERDROID.
-Still nothing.
-Reset again and Reflashed BOYPPC SHIFT, (liked it better, I know, a lot of flashes...)
-Now getting network signal, and able to get into the phone program, but as soon as I try to make a call, same problems occur with Robovoice and FC.
Sorry so thorough, but I always feel like more info is better than too little!
I had looked at another thread that said something about wearing out the radio from flashing, but on my vibrant I have flashed over 30 ROMs and 10 or more Kernals, and it still works good, so, I dunno. Kinda stuck.
Got my finger ready for the thanks button for ANY help offered.

Also noticed that now, no sounds are playing at all. Speaker driver error? It worked ok the first time I loaded this rom.

Just installed CMYLXGO's Desire Rom Yesterday and the phone works.
Now running CMY's gingersense streak, which is also a Sense ROM, and it works too. Is there any reason that anyone can think of as to why my phone will only work with sense themes?

i'm having a very similar issue.... i've tried a few roms and i get the same thing. calls go out for a few sec then force close. ppl tell me they can't call me sometimes because of this. i even task 29'd and reflashed everything. radio, magldr, cwm and now hyperdroids latest... still get force close and an unusable phone....
wtf

2.15.50.14
The above is the recommended radio that was a good start. Now the next thing to go under settings --> sound --> Feedback. I forget which one it is that causes the phone to crash/give robot voice but that is most likely what is causing the issue for you guys. I believe non sense builds also have these options if I recall correctly. I use sense builds myself. Also be sure to restart phone after you uncheck the settings under feedback. Phone should work after that and no robot voice.

I dont have robot voice and i'm running that radio. hyperdroid was running fine until recently and i have this problem. i can't get calls it causes the phone app to crash and sometimes calls crash a little bit in.... i've task 29'd and redone a clean install with old known working hyperdroid WITH NOTHING INSTALLED still does it, tried new hyperdroid; same thing...

antiparadigm said:
Just installed CMYLXGO's Desire Rom Yesterday and the phone works.
Now running CMY's gingersense streak, which is also a Sense ROM, and it works too. Is there any reason that anyone can think of as to why my phone will only work with sense themes?
Click to expand...
Click to collapse
you can try cyanogenmod and miui by starting over again but remember to do task29 to be sure that you dont leave any traces of previous installations !
!!
good luck and regards !! !

[Q] Help would be appreciated.

I recently received a new HD2 i the mail (wore out the hard keys on my last one ) and i quickly proceeded to remove winmo ASAP. The same way I've done a thousand times. Android (sense of eclipse) finally boots and every time i try to download an app it says the download has failed. EVERY TIME! I've tried re flashing the rom numerous times, re flashing cwm, magldr, task29 all with the same outcome. I also tried 3 diffferent sd cards and formatted 2 of them. This is a rom that was working fine on my old phone and i even tried a different rom (typhoon cm7) with exactly the same problem. I've had andoid on my phon since the sd days so i'm not really new at all this, but I'm not an expert so if somebody thinks this sounds familiar please help. Thanks for your time.
T-MOUS
Radio 2.15.50
HSPL 2.08
Sorry. Guess I could have put this in the Android Q&A

drakepayton said:
I recently received a new HD2 i the mail (wore out the hard keys on my last one ) and i quickly proceeded to remove winmo ASAP. The same way I've done a thousand times. Android (sense of eclipse) finally boots and every time i try to download an app it says the download has failed. EVERY TIME! I've tried re flashing the rom numerous times, re flashing cwm, magldr, task29 all with the same outcome. I also tried 3 diffferent sd cards and formatted 2 of them. This is a rom that was working fine on my old phone and i even tried a different rom (typhoon cm7) with exactly the same problem. I've had andoid on my phon since the sd days so i'm not really new at all this, but I'm not an expert so if somebody thinks this sounds familiar please help. Thanks for your time.
T-MOUS
Radio 2.15.50
HSPL 2.08
Sorry. Guess I could have put this in the Android Q&A
Click to expand...
Click to collapse
Hi,
I can't say I've had problems with every downloaded app,but certainly a few.
As you can see from my sig,I'm using the same ROM.
If any app failed to download,I just repeated the process several times,and it evetually took.
The other thing I tried,was switching from wi-fi to data,or vice-versa.Then it worked.

thanks for the reply
I've tried WiFi and on edge. used the WiFi for a long time so i know its not that, and the browsing works fine.hmmm

drakepayton said:
I've tried WiFi and on edge. used the WiFi for a long time so i know its not that, and the browsing works fine.hmmm
Click to expand...
Click to collapse
Hi,
What I meant was,if it didn't download on wi-fi,try downloading it on data.

Unexplained
Ok, so I used winmo for the entire day yesterday. Then this morning I tried flashing android one more time just for the heck of it. For no apparent reason it's working fine, apps downloading and installing perfectly. Now I'm afraid to flash any different roms, worried it might happen again. I did everything the same as always so I'm not sure what was wrong be fore or if it'll happen again. Hmmmm...

It is a common problem. You need to make sure that you set up / login to the gmail account before trying the market. The solution I received is quoted at the bottom of this post.
Here is the solution given to me when I couldn't download from the android market. I went from a working SD Android version to the next version (when the market wouldn't download). The only difference was that I had set up the gmail account then went onto the market with the first version but went straight onto the market with the next version and then logged onto gmail.
pascalsg said:
To fix it you go into Settings/Applications/manage applications/all and click on the following:
Google Backup Transport - then click clear data
Google Partner Set Up - then click clear data
Google Services Framework - then click clear data
Market - clear data
Reboot the phone, and Market should then work
Make sure you add your gmail account 1st before attempt to use the market
Click to expand...
Click to collapse

Thanks for the reply
Thanks for your input. I am having trouble figuring out what was wrong and what fixed it. I know that's not the issue here because the I would try apps in "my apps" (meaning I was signed in) in the market and also ones I've never downloaded before. Also maybe its gierbread or just the two roms I was on but I couldn't even open the market till I signed in with Google. I know cause after flashing a million times I was anxious to try the market quickly and forgot to sign in. It would then re direct me to the Google sign in. Strange

[Q] Whats wrong with this HD2? Anyone else getting these problems?

Ok first and foremost...I have tried searching
I have been a lurker most of the time here on xda seeing as if I just search and read I'll get most of my answers, but not this time.
Ok some background info first:
TMOUS US HD2 1024Leo
Radio: I'm not 100% sure but I did a task29 that supposedly flashed 2.15.50.14
HSPL: 2.08
MAGLDR 1.13
I bought this phone about a year ago, flashed tytung's Nexus HD2 Gingerbread rom which worked flawlessly for about 10 months or so. One day the phone froze up, pulled battery then inserted and the rom reset to the point where it was like new. Around that time tytung's ICS AOSP thread came alive and I followed it closely watching the updates and what not.
I never installed it until Beta 10. Followed his instructions, set up the partition to 200MBs with a cache of 45MB...45MB for cache because I suspect I may have some bad NAND blocks. Anyways install went flawlessly, everything that was supposed to work, worked...ect ect
Used it for about 24hrs then all of a sudden it froze, when I rebooted I started getting all these random apps crashing(gapps[google apps?], Email, Google Login Services ect), needless to say I task29'd the HD2 and reinstalled everything, worked fine for a day then everything started crashing again.
So after all that info I'm just wondering if someone is experiencing the same problems and/or can maybe lead me in the right direction to figure out this problem.
I know its only a beta but I havent read many posts containing my problems. So Im just left wondering if my NAND is going bad completely and I need a new phone or if theres just something I'm doing wrong.

Before i begin - I have no experience with that Rom, these are just common general ideas.
1) as the rom starts well and then only after a day it breaks, maybe it is because of something (update) getting installed on your device. Have you tried fixing permissions after you encounter the problem?
Or try figuring out which update of which app does it.
2)It also might be the problem of the nand bad blocks, if you suspect it, but if thats the case, there is not really a lot you can do...

No offense, but that's the reason its beta. It doesn't have all the bugs worked out yet.
If you're looking for a daily driver, you should try something more stable.

Hi,
Not sure if you still have this problem..
Have you tried re-installing the ROM again or a different ROM to confirm if the issue is with your phone (hardware) or with the ROM (beta version)?