[Q] screen freezes and does not boot

[fastscorpion2010]

Hello there,

I bought my HTC HD2 two weeks ago, and when I received it, it had a ROM of a 3.14 Version with a Radio of 2.15.50
(RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship). The previous buyer told me he had Android Running on SD Card.

When I started "playing" with the phone, I got a lot of Screen Freezes during any app (Internet, Mail, Facebook). Not only did the screen frooze, but also did the no longer start up properly. Either it didnt hang during the Logo, or when entering the PIN. Even during Hardware resets it frooze sometimes.

As the described ROM from above not the "real" supported ROM for THAT HD2 is, I flashed the original 1.72 Version with a Radio of 2.07.51 (RUU_Leo_TMO_DE_1.72.111.4_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship downloaded directly from HTC.com).
I thought, maybe its the ROMs problem. However, now I face the same problems and start to think the problems are hardware related. Am I correct there, or do you guys have any other thoughts?

 

[tictac0566]

Could be hardware related indeed.

Did you try to run your device without SD card?

Sometimes, older SIM cards can also cause trouble.

And finally, what SPL is on your device now? You can check this information in the bootloader screen.

 

[fastscorpion2010]

Could be hardware related indeed.

Did you try to run your device without SD card?

Sometimes, older SIM cards can also cause trouble.

And finally, what SPL is on your device now? You can check this information in the bootloader screen.

I have a SPL-2.08.0000 (not HSPL). I run it without the SD Card aswell, but i got the same issues. Since I still have warranty on the phone, do u think I should make use of it and send it in? but then I want to make sure, that there are no traces on my phone that I installed some Android NAND versions...

 

[qadeer123]

SAME PROBLEM IN MY TMOU-HD2

 

[fastscorpion2010]

SAME PROBLEM IN MY TMOU-HD2

mine is t-mobile, but a GERMAN t-mobile, I'm not having the US-version. but what did u do? did u get a fix?

 

[fastscorpion2010]

now my phone is stuck again in the boot logo, which gives me the perfect opportunity to write down all the details:

R 2.07.51.22~2
G 15.32.50.07U
D 1.72.86525

anything wrong with that? I flashed the rom, which i downloaded directly from HTC.com (the only capable for my phone (TMOU GERMANY))

 

[tictac0566]

now my phone is stuck again in the boot logo, which gives me the perfect opportunity to write down all the details:

R 2.07.51.22~2
G 15.32.50.07U
D 1.72.86525

anything wrong with that? I flashed the rom, which i downloaded directly from HTC.com (the only capable for my phone (TMOU GERMANY))

Well, you do have the older T-Mob ROM, combined with a newer SPL.

Try to flash SPL 1.66 with the program HSPL2.exe before sending it anywhere, then make a hard reset. Re-try again with the SD card out, in the worst case, there might be some buggy data in the application data folder (if there is one).

 

[fastscorpion2010]

Well, you do have the older T-Mob ROM, combined with a newer SPL.

Try to flash SPL 1.66 with the program HSPL2.exe before sending it anywhere, then make a hard reset. Re-try again with the SD card out, in the worst case, there might be some buggy data in the application data folder (if there is one).

Thank you. with the SPL 1.66 Windows is running smooth again. But what caused all the crashes in the 3.14 version with SPL 2.08 or in Android NAND Versions with 2.08.HSPL ?? I think if I send my phone in for warranty, they tell me everything is fine with the phone....

 

[tictac0566]

Thank you. with the SPL 1.66 Windows is running smooth again. But what caused all the crashes in the 3.14 version with SPL 2.08 or in Android NAND Versions with 2.08.HSPL ?? I think if I send my phone in for warranty, they tell me everything is fine with the phone....

The official 3.14 ROM shouldn´t run with any other SPL than 3.03.

NAND ROMs require MAGLDR, and this, on the other hand, requires HSPL 2.08. If there was still a different SPL on your device (which should be checked by the tool, as far as I remember, and therefore, I don´t know if that´s possible), you might have to source of problems.

The 2 major sources of problems are a) a wrong Radio ROM or b) a corrupt SD card, in some rarer cases an older SIM card.

If your system and device are running properly now, I think it might be indeed a waste of time to send it to a service center. If you like, it might be worth to give another try with a proper installation: Put HSPL 2.08 on your device, then Radio ROM 2.15.50.04, then MAGLDR 1.13, and then a nice Android NAND build.

No need to ever boot into Windows once you start all that flashing stuff.

 

[fastscorpion2010]

The official 3.14 ROM shouldn´t run with any other SPL than 3.03.

NAND ROMs require MAGLDR, and this, on the other hand, requires HSPL 2.08. If there was still a different SPL on your device (which should be checked by the tool, as far as I remember, and therefore, I don´t know if that´s possible), you might have to source of problems.

The 2 major sources of problems are a) a wrong Radio ROM or b) a corrupt SD card, in some rarer cases an older SIM card.

If your system and device are running properly now, I think it might be indeed a waste of time to send it to a service center. If you like, it might be worth to give another try with a proper installation: Put HSPL 2.08 on your device, then Radio ROM 2.15.50.04, then MAGLDR 1.13, and then a nice Android NAND build.

No need to ever boot into Windows once you start all that flashing stuff.

I gave it a try, but for some reason I am unable to flash any rom anymore. I tried to flash it via SD card and via the .exe file through the bootloader. Through the .exe file the process only proceeded until 8 or 10% and aborted. Through the SD-Card it only showed the grew screen for a few seconds and returns to bootloader with "Upgrade ROM code error Please try again"


Apperantly I did something wrong, but I dont know what. Ytd I was still able to flash the original stock windows 1.72 rom from sd card, but even that one is not working anymore.

 

[fastscorpion2010]

The official 3.14 ROM shouldn´t run with any other SPL than 3.03.

NAND ROMs require MAGLDR, and this, on the other hand, requires HSPL 2.08. If there was still a different SPL on your device (which should be checked by the tool, as far as I remember, and therefore, I don´t know if that´s possible), you might have to source of problems.

The 2 major sources of problems are a) a wrong Radio ROM or b) a corrupt SD card, in some rarer cases an older SIM card.

If your system and device are running properly now, I think it might be indeed a waste of time to send it to a service center. If you like, it might be worth to give another try with a proper installation: Put HSPL 2.08 on your device, then Radio ROM 2.15.50.04, then MAGLDR 1.13, and then a nice Android NAND build.

No need to ever boot into Windows once you start all that flashing stuff.

I also tried installing only the radio rom, but that fails somehow as well. I flashed Radio Rom

Leo_RADIO_2.15.50.14
Leo_RADIO_2.14.50.02
Leo_RADIO_2.12.50.02_2

which i found in this forum http://forum.xda-developers.com/showthread.php?t=611787

they flash to 100% but then I get a message on the phone "Software update failed. Please try again" and the computer says "This Update cannot be used for your PDA Phone. Please check your update Utility.

 

[fastscorpion2010]

anyone has any idea?
i dont know what to do anymore, the only flashing that works is hspl. i dont want to try magdlr, since the rom before hat a .51 radio, but i cant flash roms or radios....

i need some help, please.

 

[tictac0566]

If you tried everything, and only the official 1.72 ROM runs properly, the last remaining tip would be task 29. But I´m afraid, now that we can exclude almost everything, that the service center might be a good idea.

I would re-flash the latest ROM, which doesn´t perform well as you write, and send the device in to get it fixed.

 

[fastscorpion2010]

If you tried everything, and only the official 1.72 ROM runs properly, the last remaining tip would be task 29. But I´m afraid, now that we can exclude almost everything, that the service center might be a good idea.

I would re-flash the latest ROM, which doesn´t perform well as you write, and send the device in to get it fixed.

what is task 29? I havent heard about it till yet? I will give it a try. Currently I'm trying all combinaitions to at least get 1.72 to get flashed again. This one isnt flashing either right now.

 

[fastscorpion2010]

big news:

I have no idea why it worked but it did.

After flashing the entire night with different methods and ROMs and Radios, I almost gave up, and thought my phone is bricked. However, i didnt touch it at all until this afternoon.
First I run HSPL.2.08 again,
then I tried to flash the Stock ROM via SD didn't work.
then I tried to flash the Stock ROM via USB: here it used to stop at 10% and gave me an error.... this time it stopped at 10% for like 30sec and then continued!!!

So now I put SPL.1.66.0000 again to have it in original condition. Can I send it in under warranty like this? Every trace has been removed, correct?

I still don't know what is wrong with the phone. 48h ago, when nothing worked, the only flashing method which did work was via SD. Then I was at branded T-mobile Windows 6.5 on a 1.72 ROM. (Basically exactly where I am now) However, THEN I tried to flash to a higher ROM (3.14) to have a radio of .50 (to flash MAGDLR etc). but this never succedded and I ended up with one flash error after the other.
For a moment I thought my Radio is broken, since I could not flash any Radio. However all the radios i tried to flash were .50 radios. The radio of the current 1.72 ROM is however a .51 version. Does that mean I have some sort of "Radio-Lock" on my phone?

If anyone has any other ideas, please let me know, but I think I dont wanna flash anything until I get the device back from HTC. However, once it get it back, how do I know that I can flash to the higher ROM again?? I am very cautious and distrustful to my phone right now.