Software recovery problem - HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting

I managed to break my original HD2 a while ago and I've only just decided to replace it. I have another main phone but I loved that I could pretty much do anything with my old HD2. I had a bit of experience with installing cooked ROMs before moving on to installing Android and WP7 on it.
As I had a bit of experience with playing about with software recovery/updates, I decided to buy a phone that was described as "booting to a white screen" off ebay. I thought it would be a fun little hobby to get it working again.
My first few steps would be to get it to stock and start playing with it from scratch.
I booted into the bootloader and tried to flash a stock ROM but it kept freezing at 0%.
I've since managed to change the SPL version from 2.08 HSPL (I could get the phone to boot into MAGDLR 1.13, so they must've been playing with WP7 or Android NAND) to 3.03.
I downloaded and installed the stock 3.14 T-Mobile UK ROM, but it won't boot past the white screen with the HTC logo. If I pull the battery out to turn it off and try to turn it on again, then it gets stuck at a blank white screen with no HTC logo at all. I'm very confused and would like some help if possible. Thanks in advance.

Related

Bootloader white loading... screen - SOLVED

I've just been trying a few ROMs and whist trying to downgrade from 3.5 to 1.2 spl I found myself stuck in the bootloader white loading.. screen.
If I pull the battery it boots the ROM fine but whenever I entered bootloader or ran a ROMupdateutility to try a reflash I got this white screen.
I've searched for an answer on here with no joy and actually started this post to ask for help but I've just removed the SD card and it went straight to the normal bootloader screen and I'm re-flashing as we speak.
Just thought I'd complete the post for any future searchers.
Thanks
Mine has been stuck on the screen every time I try to re-flash (which actually has saved me from wasting a lot of time as well ....) but I did the same & now have the Bootloader.
Back to the endless routine of upgrades and downgrades then.

[Q] Bricked Hero? touch panel-fail

Hello, I have an unrooted Hero from Orange (Spain) that enters in a boot loop. I have tryed everything to restore it but with no success. In the hboot menu it says "touch panel-fail" and even if I flash again the original rom from the hboot, it still gets in a boot loop.
First of all I will explain my case.
I had the Hero rooted, with custom roms etc, but when I bought a Nexus One, I gave my Hero to my brother. In September he told me that the official 2.1 had arrived to the Hero, so he wanted it instead of a custom rom, so I just proceeded to do so. I created a GoldCard, installed the 1.5 RUU of WWE, made the two OTAs and all OK. The last week (I think) he received a new small OTA, he updated successfully. My brother went to sleep with the Hero almost charged, but when he woke up, the Hero was off. Then, when he turned it on, and after a while (15mins or so) the Hero finally boot up, but the touchscreen wasn`t working and using it with the trackball the Hero was always prompting FC of android.process.acore (every 2 seconds more or less).
After watching that, I installed the official 1.5 of Orange hoping that it will fix it, but no way. Now it gets stuck in a loop while booting after the Orange bootscreen.
I tryed again to flash the WWE version, but with my old GoldCard doesn't seem to work (incorrect cid) and not being able to boot it up, I cannot create a new GoldCard or even root it.
I have tryed a lot of fastboot comands but I can do just little things because for the most useful things I need root.
Other thing that might be good to know is that when I plug the power to the Hero nothing happens, the led is not turning on, and I don't know how much battery I still have. Thank goodness that the battery was full before I moved the Hero to this infernal boot loop.
Please I will be so thankful if anyone can help me or just giving me any clue about how can I fix this.
I had the same problem on a refurbished hero I had. It had touchpanel fail in hboot and was in a constant loop.
I managed to get it to boot into android once by installing the ruu while in fastboot mode, however the touchscreen did not work and when I rebooted the phone it went back to the loop.
I sent the phone back for a replacement. If u check my previous threads ull see the thread icreated. In it I said that it had worked as that was when it finally booted but before I realised the sgreen didn't work
Sent from my HTC Hero using XDA App
Thank you for your reply, I will check your posts when I arrive home this evening.
hi.
I had the same problem and solve it by flashing this rom (goldcard needed)
http://shipped-roms.com/shipped/Her...io_63.18.55.06P_6.35.15.11_release_signed.exe

[Q] Bricked Trying to Revert to Stock WinMo

I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App

[Q] Radio bricked?

Hi,
I just bought a HD2 secondhand from an online shop which was promised to me to be in working condition.
Tried booting it up and it was stuck at the Windows Mobile screen.
Managed to flash HSPL 2.08 (after 3-4 tries?) but when I tried to flash the radio, the tool indicated the current image was... nothing.
It simply didn't display any image version, I thought that was a little strange but I tried flashing 2.07.51.22.2 on it anyways.
A few other versions later (2.12.50.02.2, 2.14.50.02.2, 2.08.50.05, 2.15.50.14) and still no luck (it usually fails around 96% when I do it via USB and its stuck at nearly maximum when I try an SD flash)
Not entirely sure where it came from, but it is HTC branded T8585.
I've tried a Task 29 (though LEO Advanced RUU) which was successful. But still no luck with the radio.
Phone won't boot up most of the time - but I can still enter the bootloader.
Various screens I've got so far:
HTC screen (white background)
Screen with exclamation mark and triangle
Screen that says software update has failed
Sooo... any idea if the phone is salvageable? I've been looking around the forum but I've tried most of the above and don't know what else I can do.
Cheers.
Edit: Doesn't actually say FAIL when I use an SD. It just gets stuck at like 99/100% (full bar) with the words Update In Progress... and never progresses.

[Q] Help needed to unbrick HD2 - After restoring WinMo rom

Hi guys,
I successfully flashed Android to my HD2 a few months back. I used what I believe is Cotulla's rom(?). However the other day my phone sorta died and whenever I plugged it into the charger it would vibrate go through the boot screen and reset at the "1234 go go go" stage. I read some reading on the forum and flashed it back to "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship" from the HTC website, using the SD card. Windows mobile restored the phone and I started using it again.
I tried to put android back on it and I think I unsuccessfully tried to update the radio after which the phone sorta died again. So I thought ok, no problem, lets get back to windows again. So I installed the HTC rom again through the SD card, which the screen told me was successful. But now I can't get the phone to boot or go into bootloader or anything. When I plug the charger in, I get a vibrate and HTC bootscreen, with the red writing at the bottom left and then dead to only do this again and again. If i pull out the charger, the phone just dies. Battery charge was about 50% when it died.
Any ideas or help on how to resurrect my beloved HD2 would be greatly appreciated!
*quick update*
I stuck the phone in the fridge for a while and managed to get it into the bootloader just once and flashed the official winmo rom again, which was successful but still dead phone!
What made you decide to stick the phone in the fridge??
What is your SPL version??
mentalityx said:
What made you decide to stick the phone in the fridge??
Click to expand...
Click to collapse
Probably the dozens of threads that talk about successfully flashing only when the phone has been cooled.
@op it doesn't look good. Usually the fridge trick working implies hardware overheating issues.
Just confirm please, its not a tmous right?
Samsamuel is right, i just read about it and thought hey, why not! plus it got a priceless look from the mrs! lol
It's definitely not TMOUS, its UK Virgin and the SPL was 3.03.0000 if I recall correctly.
When I cool it, I can get it into bootloader, but only once.
well, i still suspect its hardware and unfixable, but there have been cases where for whatever reason a rom suddenly seems to fix it. Try all the versions of the correct stock Rom.
Try the 1.43 the 1,66 and again the 3.14, wwe ones, chilling the phone well before each flash, a good 20 mins.

Categories

Resources