hi guys,
pls help me out here. i have a t mobile htc hd2 running energy rom. with some third party applications. it was working fine until i plugged it to a previously unused power supply to charge. as it started to charge the battery suddenly the phone went blank. no response at all. charging indicator was also not working. i tried removing the battery, soft reset button and hard reset too. but nothing worked. so i took the phone to a shop and they tell me it needs a "boot repair" which costs 90usd. my queries are these.
1. what is a boot repair? is it a hardware problem or a software problem?
2. why did this happen? is it because of a power supply error? is it due to the custom rom or applications i m using?
3. is this a known issue with the hd2?
4. how can i prevent this from happening again?
thanks
A boot repair must be a JTAG cause that is what JTAG does for a device is reserect the SPL or what is know as the bootloader. The bootloader is what boots first when you power on your device and it boots up the hardware and software of the device. Plus to JTAG a device you have to totally remove the main board from the device. So you see a "boot repair" is part a hardware repair and part a software repair because it is the software that allows the software to use the hardware.
I am not exactly sure why it happened, but I am sure it must have had something to do with the charger you plugged it into. I can pretty much assure you it had nothing to do with the ROM you was using. What makes me wonder though is sense it happen when you plugged it into a charger. You may need more than a JTAG as it might have fried your main board somehow.
The only known issue with bricking a T-Mobile HD2 is flashing a radio version of 2.04.50.xx, 2.05.50.xx, 2.06.50.xx, or any x.xx.51.xx radio will always brick a TMOUS. Also somehow letting the HD2 become disconnected from the USB cable while you are flashing a ROM or radio will cause a HD2 or most any device to become bricked.
As for preventing it from happening again I would pay attention to my above warnnings and also not use that charger again.
Also PM me and I can reffer aomeone that can JTAG your HD2 for $50 USD too. You would have to shipp your HD2 to them though, but the live in the US.
T-Macgnolia said:
A boot repair must be a JTAG cause that is what JTAG does for a device is reserect the SPL or what is know as the bootloader. The bootloader is what boots first when you power on your device and it boots up the hardware and software of the device. Plus to JTAG a device you have to totally remove the main board from the device. So you see a "boot repair" is part a hardware repair and part a software repair because it is the software that allows the software to use the hardware.
I am not exactly sure why it happened, but I am sure it must have had something to do with the charger you plugged it into. I can pretty much assure you it had nothing to do with the ROM you was using. What makes me wonder though is sense it happen when you plugged it into a charger. You may need more than a JTAG as it might have fried your main board somehow.
The only known issue with bricking a T-Mobile HD2 is flashing a radio version of 2.04.50.xx, 2.05.50.xx, 2.06.50.xx, or any x.xx.51.xx radio will always brick a TMOUS. Also somehow letting the HD2 become disconnected from the USB cable while you are flashing a ROM or radio will cause a HD2 or most any device to become bricked.
As for preventing it from happening again I would pay attention to my above warnnings and also not use that charger again.
Also PM me and I can reffer aomeone that can JTAG your HD2 for $50 USD too. You would have to shipp your HD2 to them though, but the live in the US.
Click to expand...
Click to collapse
thanks. that enlightened me a lot. somebody told me that after the boot reapir their is increased risk of bricking the phone again. is that true? (he said its because the procedure involves somthing to do with writing the "bios" ) and is it safe to install the custom rom again?
kanishkapd said:
thanks. that enlightened me a lot. somebody told me that after the boot reapir their is increased risk of bricking the phone again. is that true? (he said its because the procedure involves somthing to do with writing the "bios" ) and is it safe to install the custom rom again?
Click to expand...
Click to collapse
Yes when you JTAG a HD2 you are doing something very similiar to rewritting the bios of a computer. But the HD2 does not have bios like a computet, someone please correct me if I am wrong with that statement. What you are actually doing when you JTAG a HD2 is rewritting the SPL or as the RiffBox software calls it "reserect the SPL".
Now as far as I know thos does not make your HD2 any more suseptable to being bricked than before it was JTAGed. And yes you can still flash custom ROM, MAGLDR, or cLK but you will have to flash HSPL again before you flash any of them because JTAG will only rewrite stock SPL to the HD2.
T-Macgnolia said:
Yes when you JTAG a HD2 you are doing something very similiar to rewritting the bios of a computer. But the HD2 does not have bios like a computet, someone please correct me if I am wrong with that statement. What you are actually doing when you JTAG a HD2 is rewritting the SPL or as the RiffBox software calls it "reserect the SPL".
Now as far as I know thos does not make your HD2 any more suseptable to being bricked than before it was JTAGed. And yes you can still flash custom ROM, MAGLDR, or cLK but you will have to flash HSPL again before you flash any of them because JTAG will only rewrite stock SPL to the HD2.
Click to expand...
Click to collapse
thanks, but the problem is worse now. they say now that there is some kind of "short circuit" in the system and because of that they are unable to repair it. currently they have sent a mail to htc requesting for a map of the hd2 circuit or something.
what could i do? is there anything to do or is it better to get a new phone?
T-Macgnolia said:
.... someone please correct me if I am wrong with that statement. What you are actually doing when you JTAG a HD2 is rewritting the SPL or as the RiffBox software calls it "reserect the SPL".
Now as far as I know thos does not make your HD2 any more suseptable to being bricked than before it was JTAGed. And yes you can still flash custom ROM, MAGLDR, or cLK but you will have to flash HSPL again before you flash any of them because JTAG will only rewrite stock SPL to the HD2.
Click to expand...
Click to collapse
Yes you are correct my br ... i use riff to fix - write boot repair... one correction Br it writes hspl 2.08 not stock spl im talking for riff
ubejd said:
Yes you are correct my br ... i use riff to fix - write boot repair... one correction Br it writes hspl 2.08 not stock spl im talking for riff
Click to expand...
Click to collapse
Thanks for the info, I have never JTAGed a HD2 or any other device for that matter. I have though done a good bit of research on it and I thought it was a stock SPL. I learned something today.
Related
Hi guys,
Just a quick question, if I successfully install the Hard SPL onto my Touch HD, is it still possible to permanently brick my device when installing a ROM if something goes wrong with the install?
As i read on another forum this quote 'it's always advisable to install Hard SPL as it prevents you from bricking your device with a problematic ROM flash'
Thank you in advance,
Regards, Chris
Under usual circumstances with even least common sense you almost can't as you can always get to the tricolor boot screen and flash again. But if deliberate (force flash a different device ROM etc) then one possibly can..
Okay mate, thank you for the reply.
Regards,
Chris.
Ok.. 1 question from me... Even the USB is disconnected in half of flashing?
amarullz said:
Ok.. 1 question from me... Even the USB is disconnected in half of flashing?
Click to expand...
Click to collapse
That doesn't harm anything. As long as you are not going to flash the SPL (which can't be done with HSPL as it is write protected) you can't damage your device. You can still get to the tricolor screen and flash your ROM once again.
johnpatcher said:
That doesn't harm anything. As long as you are not going to flash the SPL (which can't be done with HSPL as it is write protected) you can't damage your device. You can still get to the tricolor screen and flash your ROM once again.
Click to expand...
Click to collapse
Great... Thanks for your info. For safety reason I will never upgrade or change SPL.
just flash the ROM as much as I want
i have htc hd2 stuck on white screen
i tried downloading the official rom from htc and flashing it in bootloader but it stopped at 0%
i tired flashing from the sd card but i got radio fail
i even tried to repair it using jtag and still the same plz anyone can help
current info:
pb81100 hx-bc
spl-1.42.0000 xe
You tried JTAG-ing it and it didn't work?
Try to HSPL then upgrade your radio.
after repairing it with jtag i cannot seem to flash hardspl it alwais hang after selecting 2.08 hspl
and when i flash radio from sdcard i get radio fail
You should've considered the JTAG as a last option
i did
before jtag i tried every thing
but i still wonder if there is something i can do
i won't give up
plz if u can help me i will really appreciate it
TBH, I don't believe that you actually have a jtag, or maybe you do but you're not very experienced in using it.
Because if you were you wouldn't have opened this thread
You have a jtag, even if you totally bricked your phone you can easily revive it
Indeed, I too am skeptical of you haveing used a J-TAG, and if you did it seems that you did it unsuccessfully. Is your MicroSD card formatted as Fat32?
plz don't ask about formating sd
and about reviving u can revive the bootloader not the radio part
and am not opening this thread to know my experience am opening it to ask if someone experience enough to help me
about the jtag i have the ort if u know what am talking about
Ok try to upgrade your spl to 1.66, and then try HSPL and then radio update
kawazaki said:
You should've considered the JTAG as a last option
Click to expand...
Click to collapse
yea Jtagging is only when you "brick" your phone, and your phone isn't bricked, And hopefully won't be.
I was running froyo off my SD card and was wanting to go with a NAND install. I was following steps in a HOW TO here: http://forum.xda-developers.com/showthread.php?t=939682
I had 3.14 installed, but my SPL was 2.10 (not 3.03 noted in the How To) so I didn't think i needed to change my ROM. I installed SPL-2.08.HSPL (and confirmed that it installed - all was fine) and then read further that android may not run right if I'm running 3.14. This may or may be true and I cant go back and find where I read that, but thats beside the point now.
SO, I download 1.66 as it instructs in the HOW TO, install it and it looks like it installed fine, but my phone shuts off and Windows 7 tries to install the driver and cannot find it. I try to reboot my phone and its dead/blank.... nothing. I'm pretty sure its bricked as its non-responsive to any button mashing and battery removal. I cant reinstall 3.14 since Win7 wont recognize the phone (no driver). What do I do? Thanks very much for any help!
FYI, I'm with t-mobile USA. Let me know if you need any more info. Thank you in advance!!
Yep, dead. 1.66 rom contains a ..51.. radio.
Sadly, you didn't need to do any of that, simply switching spl from 2.10.0000 to 2.08.hspl using hspl3 would have done the trick.
(For info, the tmous does NOT require spl 3.03 to run 3.14 roms, unlike the regular hd2 which is hugely unstable on 3.14 without spl 3.03, which is why its not uncommon to see tmous phones running fine with 3.14 and spl 2.x, )
So WHY is it in that Definite Guide?? Arg!
There is nothing I can do? Is it basically a very expensive paper weight now?
JTAG / new mainboard are the only options now.
chileheadcraig said:
So WHY is it in that Definite Guide?? Arg!
There is nothing I can do? Is it basically a very expensive paper weight now?
Click to expand...
Click to collapse
Contact me and I can put you in touch with someone that can JTAG your HD2.
Also I thonk what you read about Android not running good if you have the 3.14 ROM was concerning SD card builds cause if you flash to a NAND Android ROM Wimdows Mobile is not on the HD3 anymore at all.
The guide is really good but that part should not have been put in there as HSPL 4 supports SPL 3.03.0000. Which SPL 3.03.0000 is the reason HSPL 4 was made.
Probably just an older guide then... live and learn i guess. I located the JTAG guy from another post. Seems like the best option. Thanks!
whats a JTAG?
sarp_pasha said:
whats a JTAG?
Click to expand...
Click to collapse
JTAG is a means of having a direct connection to the processor and NAND chip on the main board. It os,the only way to reserect a truly bricked HD2. A truly bricked HD2 will not even turn on or allow you any kind of access to the device via USB port. The JATAG is used allong with a Riffbox, ORT, cables to connect the ORT to the Riffbox, a power suply if you do not use the battery to power the main board while JTAGing it,and special software for your computer to reserect the SPL of bootloader so uou can once again reload software onto the device. You have to take the main board out of the HD2 to do thos though so it is not for everyone.
Hello all,
I was running Android via NAND using magldr on my T-Mobile USA HD2. I wanted to restore it back to stock before selling it and followed instructions here: http://forum.xda-developers.com/showthread.php?t=893948 to flash a stock WinMo 6.5 ROM.
Before Android, I had HSPL2 on it.
The ROM I downloaded was the WWE 1.48 one from here: http://forum.xda-developers.com/showthread.php?t=577717. Is this Euro only by any chance??
Now the screen won't even turn on and it won't even go in to bootloader by holding down Vol Down + Power.
Did I completely brick it? Or is there a way back?
the7thson said:
Hello all,
I was running Android via NAND using magldr on my T-Mobile USA HD2. I wanted to restore it back to stock before selling it and followed instructions here: http://forum.xda-developers.com/showthread.php?t=893948 to flash a stock WinMo 6.5 ROM.
Before Android, I had HSPL2 on it.
The ROM I downloaded was the WWE 1.48 one from here: http://forum.xda-developers.com/showthread.php?t=577717. Is this Euro only by any chance??
Now the screen won't even turn on and it won't even go in to bootloader by holding down Vol Down + Power.
Did I completely brick it? Or is there a way back?
Click to expand...
Click to collapse
Sounds like you bricked it....
Dont know what rom you flashed but if it had the wrong radio not made for our TMOUS phone then it is quite possible.....
Did the flash complete successfully with no problems?
Dont know if it'll help but holding both vol up and down simultaneously while powering up is supposed to reset it....
Good luck
If its a tmous and you flashed that 1.4 rom you listed then yea, its dead. JTAG or new mainboard.
Can't believe I was so stupid.. It's been quite a while since I've done anything with the HD2 and I completely forgot the WWEs were no good for TMOUS. The ROM I flashed is this one:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
It did finish flashing successfully for what it's worth. Once it was done, even the splash screen won't come on, it's like the screen is completely dead. Holding vol up + vol dn + power doesn't seem to do anything either.
How can I go about with the JTAG process? Getting a new board is probably not an option as far as I can tell.
Thanks for the help guys.
the7thson said:
Can't believe I was so stupid.. It's been quite a while since I've done anything with the HD2 and I completely forgot the WWEs were no good for TMOUS. The ROM I flashed is this one:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
It did finish flashing successfully for what it's worth. Once it was done, even the splash screen won't come on, it's like the screen is completely dead. Holding vol up + vol dn + power doesn't seem to do anything either.
Click to expand...
Click to collapse
"its the radio wot dun it".
See the '51' ? well ANY radio with a 51 there will brick a tmous. (So will two of the lowest 50 radios, too, 2,05.50 and 2.06.50 i think they are from memory)
if it were just the rom part that was flashed, the phone wouldn't boot but it would start and be re-flashable, , , its the radio that kills them.
How can I go about with the JTAG process? Getting a new board is probably not an option as far as I can tell.
Thanks for the help guys.
Click to expand...
Click to collapse
you can either buy the jtag equipment (about a hundred dollars all in, with teh jtag box and hd2 processor jig) or find a repair shop that offers teh service. There are a few members here that offer a postal jtag service too, send a pm to t-macgnolia, he knows someone i think.
samsamuel said:
"its the radio wot dun it".
See the '51' ? well ANY radio with a 51 there will brick a tmous. (So will two of the lowest 50 radios, too, 2,05.50 and 2.06.50 i think they are from memory)
if it were just the rom part that was flashed, the phone wouldn't boot but it would start and be re-flashable, , , its the radio that kills them.
you can either buy the jtag equipment (about a hundred dollars all in, with teh jtag box and hd2 processor jig) or find a repair shop that offers teh service. There are a few members here that offer a postal jtag service too, send a pm to t-macgnolia, he knows someone i think.
Click to expand...
Click to collapse
Live and learn.. Guess i got a little too trigger happy and flashed the first stock ROM i found without really digging in to it a little.
Will PM him, thanks for the info, I really appreciate it.
Gents,
I am hoping someone can help me with an odd problem.
I have spent a fair few hours reading through the various threads and found a few similar issues, but nothing quite the same.
I have tried the various suggestion on those posts, but have unfortunately not getten very far.
Thought that perhaps the best option is to start a-fresh with a new thread that describes my issues with the HD2.
Needless to say I have a HD2. Originally came with WinMob6.5.
Last year I decided to flash with Android and flashed with UltimateDroid Rom which I very much loved. As it had SPL 3.03 0000. I read a few posts, and had no problem changing the SPL to (HSPL) 2.08.HSPL and MGLDR1.13.
I recently got myself a Desire HD and thought as I have two phones, it may be worth flashing one of the ICS Roms to the HD2 and have a play and see what it is like.
I flashed one of the ICS Roms and was fairly pleased with it, but did have a few bugs, and decided to flash back to a different Android Rom. I thought that the best way would be to first flash it back to the original HTC Stock Rom before I start.
I downloaded the file from the HTC website and flashed it. Ever since then It will not do anything other that boot and stay in the Bootloader screen.
I tried to flash it again with the HTC rom - it goes through the flashing procedure just fine, but when it reboots, yet again, all I get is the Bootloader screen.
I read a few threads and found suggestions that I flash it using the SD. I did that, and yet again, all it would do is boot to the Bootloader screen and do nothing else. The only issue I found with flashing from the SD is that it changed the SPL back to 3.03 0000.
I had no issue using the HSPL4 and changing it back to 2.08.HSPL. But yet again, will allow me to do nothing else.
Ive tried a veriety of suggestion like using task 29 and HD2ToolKit4.2.0.1 etc and I am getting absolutely nowhere.
The really frustrating thing is that when I run the RUU flasher, it detects the phone, and goes through the flash gets to 100%, tells me it is successfull, restarts the phone and I am back where I started - the continues Bootloader screen.
So, any advice and help would be very very much appreciated.
The Bootloader info:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0X05
CotullaHSPL 0X30
Thanks.
Faulty voldown button, perhaps? Registering permanently pressed?
samsamuel said:
Faulty voldown button, perhaps? Registering permanently pressed?
Click to expand...
Click to collapse
To test this if you have reflashed stock WinMo, hold volume up whilst it's booting and it might ask you if you want to hard reset. If this happens, then samsamuel is correct. If you're lucky, it might just bootup normally as well
Nigeldg said:
To test this if you have reflashed stock WinMo, hold volume up whilst it's booting and it might ask you if you want to hard reset. If this happens, then samsamuel is correct. If you're lucky, it might just bootup normally as well
Click to expand...
Click to collapse
Thanks for the reply, but unfortunately, not worked.
Holding the vol up button, does nothing.
It just boots right back to the bootloader screen.
The odd thing is that I can flash it just fine. Its detected by the pc, it flashes all the way through to the 100% and says it is successfull, but then on reboot, goes right back to the bootloader screen. Its well frustrating.
I am not sure if this makes any difference, but the phone was originally on the Virgin network and also Virgin branded software.
Thanks.
miller-might said:
Thanks for the reply, but unfortunately, not worked.
Holding the vol up button, does nothing.
It just boots right back to the bootloader screen.
The odd thing is that I can flash it just fine. Its detected by the pc, it flashes all the way through to the 100% and says it is successfull, but then on reboot, goes right back to the bootloader screen. Its well frustrating.
I am not sure if this makes any difference, but the phone was originally on the Virgin network and also Virgin branded software.
Thanks.
Click to expand...
Click to collapse
I don't think there would be any difference, except that of course being on Virgin your connection would be sh*t My brother and mum are on Virgin and get really poor connection everywhere
Nigeldg said:
I don't think there would be any difference, except that of course being on Virgin your connection would be sh*t My brother and mum are on Virgin and get really poor connection everywhere
Click to expand...
Click to collapse
I am really at a loss. The obvious question now would be, is the phone bricked? Or is there a solution somewhere?
I have tried absolutely everything I can think of.
Sent from my Desire HD using xda premium
Try to flash a Virgin network rom.
elias2204 said:
Try to flash a Virgin network rom.
Click to expand...
Click to collapse
I've tried.
The only one I can find is RUU_Leo_Virgin_Mobile_1.66.351.1_Radio_15.32.50.07U_2.07.51.22_2_Signed_LEO_Ship
I tried flashing it both via pc, and sd. Flashes fine, goes to 100% no issues, but on reboot, is back to the Bootloader screen.
Only noticible difference is that the SPL has changed to 1.42
Anyone have any ideas?
try hassling virgin for a replacement would be my advice. Youve tried all the sopftware options (most noteably flashing the stock rom) so i gotta suspect a hardware fault, whether a faulty key, or whatever. So long as the spl line says 1.42.0000 1.66.0000 or 3.03.0000 then its valid for a return (of course warranty is probably gone by now, but worth a try)
samsamuel said:
try hassling virgin for a replacement would be my advice. Youve tried all the sopftware options (most noteably flashing the stock rom) so i gotta suspect a hardware fault, whether a faulty key, or whatever. So long as the spl line says 1.42.0000 1.66.0000 or 3.03.0000 then its valid for a return (of course warranty is probably gone by now, but worth a try)
Click to expand...
Click to collapse
Thanks from the reply. I was starting to think that its bricked.
I've also tried as a last resort creating a goldcard, but to no avail.
Thanks for the suggestion with Virgin, I will give that a go.
Thanks again for the effort.
Sent from my Desire HD using xda premium