A friend had Android running on his HD2 but it kept freezing at random moments. It looked like bad memory or incorrect partitions on the SD. Either way, I offered to install his, since it works fine on mine.
So I put on the right radio, did Task29 (twice), installed MagDlr and on to CWM. First time it failed. Second time it worked, but didn't restart automatically. After a restart AD Recovery didn't load up CWM. So I figured I'd better redo the MagDlr install. Again the same.
Another step back I tried to reinstall a WM6.5 rom, just to check if that worked. First time it froze up at 31%, second time at 59% and the third time at 12%. No success.
Last step back: try to install HSPL 2.08 again. Again it froze up during installation. Now if I reboot into HSPL it displays 'Software update failure, please try again!' before it goes into the HSPL bootscreen (tricolour).
And finally, after that long story, here's the problem: in the white bar there is no word at all! No 'serial' and definitely no 'usb' when I plug it in.
Is it hard bricked? Do I need JTAG? If so, anyone in or near the Netherlands able to do this?
---------- Post added at 11:33 PM ---------- Previous post was at 11:16 PM ----------
Ok, I just kept trying and despite the missing words, it still was able to connect appearently. So I did another install of HSPL 2.08 and this time it worked!
However, this success didn't last long. I tried to install from the start again for Android, so the next step was the correct radio rom.
The radio rom (2.15.50.14) installed fine till 96%. It hangs for a few seconds, which seems normal as it happened to my own phone as well, and jumps to 100%. But on the phone there's a triangle with exlamation mark and on the PC I get the message 'ERROR [290]: INVALID COMMAND.
After a restart, the same as before: warning about failure to update and HSPL with no words in the white area. Repeated 3 times, same every time.
Anyone any idea?
Hardware problem?
Well, that really sounds like some hardware issue in the flash memory chip.
If your friend is still in warranty I would suggest sending the phone in for repair (After flashing (or attempting to flash) a stock ROM of course )
Thanks for the reply, I was afraid of this. The warranty is long gone I think.
sytze said:
Thanks for the reply, I was afraid of this. The warranty is long gone I think.
Click to expand...
Click to collapse
but in my case i'm sure because i can connect on my laptop in my home. but in my office i can not connect hspl to my pc (hspl 2.08, ir remains on serial)
does anyone know why?!!!
Related
Hello!
I tried to unistall HSPL from my HD2 by installing 1.66 ROM from Sunnysoft. I put leoimg.nbh on my memorycard and got into bootloader mode to install this rom. At the beginning everything was fine, i pressed the power buton and installation started but after a few seconds a screen with 4 colours appeared. And now, nothing can bring my leo to life: hard reset, task29, installing rom directly from usb or doing again this process. I don't know what to do . Help me, please. (I want to sell this phone)
It seems that you have interrupted you update-process which is not good...
Try this: Another try from your SD, don't worry if it switches on and off while the progress; it is finished, when there's "Update SUCCESS"on your screen", before you shouldn't touch it.
If it does not work, install HardSPL again; bring phone directly into bootloader-mode (coloured stripes) and run HSPL2, install some ROM; I guess your failed update has already brought you back stock SPL, so that you cannot use RUU or Task29.
I waited a long time (2 hours) after this 4 colour screen appeared and nothing happened. But i'll try installing HSPL one more time. Thank you for the reply. I'll post a reply if it works.
Ok, it helped but when i again tried to install 1.66 from sd card, again after installing the first part appeared OK and then phone restarted and appeared the inscription: Not allowed and again 4 colour screen
Could I unistall the HSPL by installing 1.66 ROM by usb cabel not by sd card?
No, you can't. Try another SD. And again. Do not touch your phone once the process has been started. Take out the battery when there is "SUCCESS" on the screen in highlighted letters. Then put it back in again and normally start your phone.
EDIT: Make sure, that you really take the ROM that you originally had on your HD2 (branded, unbranded, aso.), no matter what version.
Hey, so I have an HD2 that was flashed badly. No problem, enter bootloader, reflash, right?
Strangely enough, it was acting strangely, and would freeze while in bootloader mode (plug in, nothing would recognize it, plug out and USB is still on the screen).
I pull the battery, try again, and get to flashing the Radio, it stops at 96%, and then fails. Try to do the recovery, but when I restart it, I a triangle with an exlamation mark (!), and I can't enter bootloader.
So, is that it...?
Oook, so I got into bootloader, flashed the HardSPL ver to 2, trying to flash the radio again, and it's not moving at 0%...
I'm having a similar issue. I have cotulla's HSPL 2.08 and I cannot flash ANY rom, no stock t-mobile, no android, nothing! Someone please help us! I would hate to see our HD2's go in the drawer and be forgotten
T-MOUS
boymeetsfence said:
I'm having a similar issue. I have cotulla's HSPL 2.08 and I cannot flash ANY rom, no stock t-mobile, no android, nothing! Someone please help us! I would hate to see our HD2's go in the drawer and be forgotten
T-MOUS
Click to expand...
Click to collapse
By any chance was the existing ROM the 3.14 one?
CrowJA said:
Hey, so I have an HD2 that was flashed badly. No problem, enter bootloader, reflash, right?
Strangely enough, it was acting strangely, and would freeze while in bootloader mode (plug in, nothing would recognize it, plug out and USB is still on the screen).
I pull the battery, try again, and get to flashing the Radio, it stops at 96%, and then fails. Try to do the recovery, but when I restart it, I a triangle with an exlamation mark (!), and I can't enter bootloader.
So, is that it...?
Click to expand...
Click to collapse
Try and flash the stock (or branded) ROM, either by USB or SD method.
No, I installed that update when it came out, seemed to make the phone worse so I went back to 2.13
boymeetsfence said:
No, I installed that update when it came out, seemed to make the phone worse so I went back to 2.13
Click to expand...
Click to collapse
a friend was doing similar ...
he upgraded to cotulla's HSPL 2.08 no problem, but when updating to most recent radio to allow him to play with putty or energy it froze at 96% and now just boots to ! screen
will not acknowledge attempts to SDcard flash, and his attempt to flash with latest stock HTC rom fails at random spots between 1% and 45%
going to grab an old stock rom and try voldown/power into tricolor and downgrade I guess
may have had some success ... seems his sdcard was formatted as FAT not FAT32 (doh!)
put duttys latest on the card and sd flashed that no problems, then put latest radio on card and sd flashed that, made it to 100% but 10 mins later and radio flash attempt still sitting at 'update in progress' with bar at 100%
guess I'll try with HTC stock via sd now
no joy there either ... hangs after attempting to flash the first radio portion
RESULT! seems the root cause was cotulla's HSPL 2.08
Ran HSPL_2 went back to 1.66-HSPL
then installed stock 1.48.405.2 which flashed completely and cleanly
phew
hd2 died help!
i accidentaly flashed an incorrect radio rom and thats where my problem started. although it still vibrates continusly once i put the battery back but im not sure if i can revive this. please help me out.
I managed to flash the latest radio successfully with 1.66-HSPL in place.
I just bullheadedly continually kept reattempting to sdcard flash just the latest radio, maybe 15-20x it either locked or gave me RSA errors.
Just before I was about to fling it into the fireplace, it just *worked* for no apparent reason ...
Just whacked Dutty's latest on there, and now happily looking at the 'tap next to begin screen'
Where to start... I had SPL-2.08.HSPL and Magldr v1.13 with MIUI rom installed on a T-Mobile HD2 and everything was peachy. Then all of the sudden for some reason I was getting 1EFATAL HIT 1 on boot up. I googled it and found this thread: http://forum.xda-developers.com/showthread.php?t=908915. #7 looked promising and seemed logical. Task29 completed without a hitch and I was back at the bootloader with SPL-2.08.HSPL, looking good. I downloaded Leo_RADIO_2.15.50.14 from http://forum.xda-developers.com/showthread.php?t=611787 and that's when things went wrong.
The install seemed to be going fine until 100% when a little caution triangle (I think) was at the end of the progress bar. The window on my computer said something like "This cannot be flashed ... Error" or something along those lines and the phone goes black. I'm like that's weird so I pull the battery out and put it back in and try and boot the phone... Nothing. Do it again... Nothing. Tried multiple times with and without SIM/SD card to no avail. Phone isn't turning on at all... Bricked.
TL;DR: Had HSPL/Magldr and everything was working got 1EFATAL HIT 1 error, tried to fix it end up with a phone not turning on at all.
Any ideas?
You are correct your HD2 is hard bricked. I don't know what went wrong with the radio flash , but that is what bricked your HD2. Having a radio stop flashing for any reason will always result in a bricked device.
The only way to fix your HD2 now is by JTAG. If you like I casn send you a PM with contact info on someone that can JTAG your HD2.
That really sucks, and PM Sent.
OK. It's not me who have the problem and I may not provide you enough information. However, I will try as much as I can to get the info from the man who has the problem.
A friend of mine got an used HD2, with stock WinMo. The fist thing he did was of course hard-reset it. Aaand the system got ****ed up. He couldn't boot it sometimes (had a grey screen, he said with some weird text under, like Boot_W_PWE_KEY_PRESSED or BOOTUP_W_WARM_RESET after trying to install sth, few times it managed to boot up but lagged so much). I ignored it and wanted to do task29, radio, magldr, android. First thing - HSPL. Downloaded HSPL4, installed HSPL 2.08 fine. Then - Task29 + Radio. And nothing. ROM Code Error. After few tries, HTC logo and progress bar showed up. Task29 is stuck on 96% though and then displays an exclamation mark in a triangle.
After a restart, grey screen is still present.
We can't install magldr as well (dat error again).
What could go wrong?
try use HSPL3 cuz HSPL4 is for wp7 mango but not for HD2 Leo
Demo3827 said:
try use HSPL3 cuz HSPL4 is for wp7 mango but not for HD2 Leo
Click to expand...
Click to collapse
You need to study more.
OK, so we managed to install magldr on 11th? try and on 21st try we managed to boot Android from SD.
I'm pretty sure that NAND is damaged (NAND Android and WP7 couldn't boot at all, 1E FATAL HIT, same was with Android SD, but after many tries it booted), but when the phone hangs up after trying to play Angry Birds (so much that only thing he could do was to pull out the battery) and sometimes hangs up just for a while without a particular reason means that something else is damaged as well?
Boot loader
Has he tried booting into the boot loader.
Hold the down volume button and the power key at the same time.
If he gets a multi-colored screen then he is not bricked.
By 'bricked' I mean unusable because of physical damage that doesn't allow to run the phone properly.
Oh. Also he managed to install and boot WP7. It will return a 'Fatal hit' if it won't have enough break without a battey. It boots only after few mins turned off (which makes installing cabs almost impossible D: )... It was bought used, I think it had fallen and few more components were damaged...
A friend gave me his non-working HD2 to try fix. It would only boot to a white screen (no HTC logo). I was able to get to the multicoloured screen by pressing the vol down + power button. I tried flashing the latest RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship rom via USB but repeatedly it got as far as 1% then gave me an error 270 message. I then extracted the image, copied it an sd card and tried to install from the card. It seemed to go ok until it stopped at 4% then rebooted. I now get as far as a white screen plus HTC logo but no further. Any attempt to flash another rom from the sd card gives an error 00028002 'not allowed' then I get the multicoloured screen but the SPL has changed to 3.03.0000 from I think 2.08 but I can't be certain. Perhaps with hindsight I should have written down what the old screen said!
Any ideas to rescue the situation willingly accepted.
Thanks,
Geoff.
With SPL being stock, you don't have many options. You can try flashing HSPL and then stock winmo/other OS. Or you can try to flash original stock through SD.
By the way, if the device was originally broken because of an overheating issue, you might have to cool the device before attempting to flash anything.
Good luck.
rebgershon said:
A friend gave me his non-working HD2 to try fix. It would only boot to a white screen (no HTC logo). I was able to get to the multicoloured screen by pressing the vol down + power button. I tried flashing the latest RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship rom via USB but repeatedly it got as far as 1% then gave me an error 270 message. I then extracted the image, copied it an sd card and tried to install from the card. It seemed to go ok until it stopped at 4% then rebooted. I now get as far as a white screen plus HTC logo but no further. Any attempt to flash another rom from the sd card gives an error 00028002 'not allowed' then I get the multicoloured screen but the SPL has changed to 3.03.0000 from I think 2.08 but I can't be certain. Perhaps with hindsight I should have written down what the old screen said!
Any ideas to rescue the situation willingly accepted.
Thanks,
Geoff.
Click to expand...
Click to collapse
the first thing to happen when you sd card flash a stock rom, is that hspl gets removed, or if it isnt present, teh stock spl gets updated to teh one contained in teh new rom. Then the phone reboots into the new bootloader, and flashing starts.
What happened to you is it removed hspl, rebooted, and the fresh 3.03.0000 detected that the rom region/carrier doesnt match the phones region/carrier, and so failed.
That being said, teh fact that it wouldnt flash over usb is worrying, im leaning towards a faulty phone, but its early days yet.
Try setting hspl again, hspl4, set 3.03.hspl (not .0000) and try flash the rom you listed again, over usb, and report back.
samsamuel said:
the first thing to happen when you sd card flash a stock rom, is that hspl gets removed, or if it isnt present, teh stock spl gets updated to teh one contained in teh new rom. Then the phone reboots into the new bootloader, and flashing starts.
What happened to you is it removed hspl, rebooted, and the fresh 3.03.0000 detected that the rom region/carrier doesnt match the phones region/carrier, and so failed.
That being said, teh fact that it wouldnt flash over usb is worrying, im leaning towards a faulty phone, but its early days yet.
Try setting hspl again, hspl4, set 3.03.hspl (not .0000) and try flash the rom you listed again, over usb, and report back.
Click to expand...
Click to collapse
I've got a very similar problem to this. My phone only boots to a blank white screen. When I hold the volume down button when turning it on, I can get to the bootloader.
From there, sometimes I can set 3.03 hspl, but most of the time the phone freezes at 0%. If I try to flash a stock rom, it stays frozen at 0%. If any of these updates work, then it still only boots to the HTC logo on the white screen.
I'm trying to flash via USB, could this be a faulty phone? I wonder what could be faulty?
yeoldgreat1 said:
could this be a faulty phone? I wonder what could be faulty?
Click to expand...
Click to collapse
yea sounds like it, lots of reports of exactly this, some kind of hardware probably, though JTAG may help.