Related
Hello,
I accidentally flashed a Test ROM w/ an MFG SPL (Leo_1_5_TMOUS_2.03.531.6_Radio_Signed_15.30.50.07U_2.06.50.23_3_Test) and meant to flash 2.13 shipped rom and now I am stuck with 2.02/2.03.0000 Engineering SPL and can't seem to flash any official/shipped roms to get back to 2.08/2.10 spl..
In other words how can I flash an SPL that is compatible with HSPL3 Utility..
(SPL 1.42.0000, SPL 1.62.0000, SPL 1.66.0000, SPL 2.07.0000, SPL 2.08.0000, SPL 2.10.000)
Please help!
Thanks.
Solution Found!
Lexx_xda said:
We have modified the installer HSPL3 Cotulla and added the ability to install HSPL 2.08 SPL 2.02. This version is not suitable for installation on SPL 2.07, on the other can.
On this ImaSoft me right, I give you a file and password for the archive.
Password: 96EF2E24-B657-4ebe-BB66-D2697FDEC815
Those wishing to thank ImaSoft:
WebMoney: Z392411566318; R371997483121; U774668296579
Click to expand...
Click to collapse
If this helped you out of SPL 2.02 please remember to thank these guys for working this out.
Info about MFG SPL:
Why can't I change the SPL with these test ROMs?
- These stock ROMs have an MFG SPL which cannot be overwritten in any way, not by flashing stock ROMs from SD, HSPL utility, SSPL or goldcard. The only successful way has been to drop the SPL with mtty (and has only been done once or twice).
- Good new is you can still use your HD2 and switch between 2.02 and 2.03 test ROMs..
What is an MFG SPL?
- MFG SPL = Engineering SPL
xmoo said:
Guys, MFG SPL allowes you to use some extra commands using JTAG which you wouldn't be able to use on normal SPL.
I remmeber back in the days there was this user "Leoni" who was stuck on 0.67MFG SPL.
Comonex helped him dropping it. I tried to contact him several times for you guys.
But he never responded back to me.
So spam pm him
Click to expand...
Click to collapse
Scabes24 said:
In other words how can I flash an SPL that is compatible with HSPL3 Utility
(SPL 1.42.0000, SPL 1.62.0000, SPL 1.66.0000, SPL 2.07.0000, SPL 2.08.0000, SPL 2.10.000)
Click to expand...
Click to collapse
this happened to several people some months ago.
goldcard may work, yes, but if not then sspl should get you flashing roms, but you can't change radio with sspl.
look for thread started by xmoo around february or march.
I thought I had tried sspl.. could I have done it wrong?
I found it here: http://forum.xda-developers.com/showthread.php?t=606713
I put the shipped 2.13 (also tried 2.05, 2.07, 2.09, 2.10, 2.11 stock and test roms) rom nbh from here: http://forum.xda-developers.com/showthread.php?t=655653 in a folder with the SSPL.exe and then run .exe but the progress bar stays at 0%
I also tried creating a goldcard, but not quite sure how it works. do I put an nbh on the card with it and boot from sd? or use CustomRUU?
The only ones I can flash back and forth are 2.02 and 2.03 test roms. I'm so annoyed!
Thanks
Nevermind the device wont even turn on anymore
2.02 is a MFG SPL.
Engeniering SPL. You have to drop it using mtty (but if you do it the wrong way, you may brick ur phone!)
Someone flashed 2.10.0 with sspl and sent it back for warrenty. When it came back it had 2.13 with SPL 2.10 on it....
xmoo said:
2.02 is a MFG SPL.
Engeniering SPL. You have to drop it using mtty (but if you do it the wrong way, you may brick ur phone!)
Someone flashed 2.10.0 with sspl and sent it back for warrenty. When it came back it had 2.13 with SPL 2.10 on it....
Click to expand...
Click to collapse
Well for some reason I tried flashing to the 1.01 test from the 1.03 to see if it would change from the MFG spl and I wasn't really paying attention to the progress bar but when I looked back it said (on PC) "ROM Update sucessful" but the phone didn't boot and won't even charge now?
What happened? and can I still send it in for warrenty?
Thanks for the help!
Scabes24 said:
Well for some reason I tried flashing to the 1.01 test from the 1.03 to see if it would change from the MFG spl and I wasn't really paying attention to the progress bar but when I looked back it said (on PC) "ROM Update sucessful" but the phone didn't boot and won't even charge now?
What happened? and can I still send it in for warrenty?
Thanks for the help!
Click to expand...
Click to collapse
Well if the phone isn't powering on, they probably can't check the spl...
So mayb yes. There are some other people who have done the same ish, and returned there phone. Ask them first.
xmoo said:
2.02 is a MFG SPL.
Engeniering SPL. You have to drop it using mtty (but if you do it the wrong way, you may brick ur phone!)
Click to expand...
Click to collapse
I am badly looknig for an MFG SPL.
Can someone point me where this is located pls? thanks!
Sry. please ignore my questions, I asked too fast...
Even MTTY does not remove the SPL 2.02.0000
Any solution for this yet? The test ROMs 201 to 209 are not intended for the TMOUS devices there for it is making it hard to remove the watermarked SPL.
I recontructed the ROM without the watermark but it will not install on the device. Anyone has an idea of how to remove the watermark? The SPL used form that ROM is the cause of the block...
Anymore thoughts on this issue?
I bought an eBay "for parts only" HD2 that the seller said sometimes booted into windows 6.5 but most of the time froze at the stick-together screen and never fully booted. Sounded maybe fixable to me, so I took a chance on it. I've never seen it try to boot into winmo 6.5 and when I check the bootloader info I see this:
PB81120 SS-B3
SPL-2.02.0000 XE
MicroP(LED) 0x05
MicroP(Touch) 0x50
The SPL-2.02.0000 was how I found this page. I've read many other pages about HSPL3 etc., but this phone is not recognized at all by two different WinXP machines w/ActiveSync. I don't get any messages regarding Qualcomm or anything like that. It's as if it isn't plugged in except the charge light does go on.
The only thing I can do is flash from the MicroSD card. But, haven't found any other ROMS other than the one that is on it already, that will actually flash. The others get stuck at a white screen that says Loading... and it just hangs there.
When the phone powers up it shows:
R 2.06.50.23......3 (the ...... is actually a squiggly looking line, not actually dots)
G 15.30.50.07u
D 2.03.75592 8G
then it just hangs there forever and goes into what looks like a screensaver mode (parts of the screen get darker and the stick together moves around as well).
If it's dead/bricked, what part inside would need replacing to get it running again (i.e. the motherboard)? This phone looks brand new. It's it fantastic condition. I've seen terrible looking HD2s on eBay that still work. So, I'm curious if there is something I could take out of an ugly phone and swap into this pristine HD2 and have it work.
As I see it, my only other options are to contact HTC and find out what they charge to repair it, or sell it for parts - again.
Since last post have discovered if I manually put phone into bootloader mode then plug it in via USB to my PC I hear the confirmation from the PC that the device is plugged in. Activesync does not fire up, but bootloader changes from serial mode to USB mode. I can start the ROM update utility, the black htc screen with 0% shows on the phone but eventually times out with an error [262] that the recovery process doesn't fix.
runningtiger said:
Since last post have discovered if I manually put phone into bootloader mode then plug it in via USB to my PC I hear the confirmation from the PC that the device is plugged in. Activesync does not fire up, but bootloader changes from serial mode to USB mode. I can start the ROM update utility, the black htc screen with 0% shows on the phone but eventually times out with an error [262] that the recovery process doesn't fix.
Click to expand...
Click to collapse
The person who owned that previously probably did the same thing I did and flashed one of the test roms with MFG SPL (2.02 or 2.03) Just don't try to flash 2.01, it'll most likely brick it. tomorrow the unbricking attempt on my device will begin.. but I guess you have to drop the SPL using mtty. talk to xmoo
I'll be very interested to read how your unbrick attempt turns out. I tried the MTTY instructions here: http://forum.xda-developers.com/showthread.php?t=668347
But, that post starts out saying "Before you start one note, this method only works if you succesfully flashed HSPL", which of course my HD2 does not have. Mine used to have 2.02.0000, but after many different tries at a fix - now has 2.00.1000. This is no better a situation to be in as it never gets past the "stick together" screen either.
I tried the create a goldcard.img info found here:
http://forum.xda-developers.com/showthread.php?t=591314
However, the directions for QMAT are outdated. But, I did download the new PSAS software offered at the site linked to in the above post and believe I got my 1GB MicroSD card's serial number but when I tried to "generate HTC goldcard" for Leo it gives a message that says "Goldcard for newer devices isn't implemented in this unregistered version" and it looks like it cost 30Euros to register. I'd pay if I knew for a fact this was going to work. But, I have my doubts because in step 2 you need to change the security permissions policies on the HD2. I have no access to the registry since there is no activesync connection possible at this point and I can't launch any programs like PHM.
The fix (if there is one even possible) has to come completely from the SD card as far as I can tell.
Good luck with yours! I hope something works and you come back here and post the sequence.
runningtiger said:
I'll be very interested to read how your unbrick attempt turns out. I tried the MTTY instructions here: http://forum.xda-developers.com/showthread.php?t=668347
But, that post starts out saying "Before you start one note, this method only works if you succesfully flashed HSPL", which of course my HD2 does not have. Mine used to have 2.02.0000, but after many different tries at a fix - now has 2.00.1000. This is no better a situation to be in as it never gets past the "stick together" screen either.
I tried the create a goldcard.img info found here:
http://forum.xda-developers.com/showthread.php?t=591314
However, the directions for QMAT are outdated. But, I did download the new PSAS software offered at the site linked to in the above post and believe I got my 1GB MicroSD card's serial number but when I tried to "generate HTC goldcard" for Leo it gives a message that says "Goldcard for newer devices isn't implemented in this unregistered version" and it looks like it cost 30Euros to register. I'd pay if I knew for a fact this was going to work. But, I have my doubts because in step 2 you need to change the security permissions policies on the HD2. I have no access to the registry since there is no activesync connection possible at this point and I can't launch any programs like PHM.
The fix (if there is one even possible) has to come completely from the SD card as far as I can tell.
Good luck with yours! I hope something works and you come back here and post the sequence.
Click to expand...
Click to collapse
2.03 has the mfg spl 2.02.0000 and i think 2.01 or 2.02 test ROMs have 2.00.1000. Least thats what I remember..
runningtiger said:
But, I have my doubts because in step 2 you need to change the security permissions policies on the HD2.
Click to expand...
Click to collapse
that part is only necessary to find the ID No. of the sd card. If you can get access to a working WM phone for a few minutes, you can use the other device to find the ID No.
There are alternate ways to get the ID, such as a linux boot disk on a laptop that has a built in SD card slot, but the slot must be directly mounted on the computers PCI bus, if it runs through a usb header it will give you the ID of teh USB header and not the card.
I'm trying to find a way for HSPL3.exe to disable the SPL version check.
This way you can directly flash other HSPL versions....
Thanks for looking into this..
xmoo said:
I'm trying to find a way for HSPL3.exe to disable the SPL version check.
This way you can directly flash other HSPL versions....
Click to expand...
Click to collapse
Is there anything I can do to help?
I think it's taken a knock and now it won't boot. I just get a white screen. If I try a hard reset it gives me the text that I'll wipe all personal settings etc.
I've flashed to a duttys ROM and a 2.x.50.x radio and I'm on O2. Is there any way I can fix this as I'm guessing the ROm update voided the warrenty. As the Hard reset shows text I can see something is working but even plugging it into my PC via USB gets no response.
If anyone can help it would be a major relief.
Let it do the hard reset and see what happens. So you'll lose what ever MMS/SMS you didn't delete, the programs you have loaded since putting the ROM on, etc etc. Your not going to lose all your numbers unless they are stored on the actual phone and not the SIM card.
You could try doing a task29 on it and see if that helps. As for the warranty being voided it just depends on whether or not it can be wiped and loading with a OEM ROM back onto it with the correct HSPL before sending it back. You haven't bricked it if you can get into bootloader or hard reset.
I have tried the hard reset but no joy. It runs the reset but then on boot back to white screen. I'm not fussed about the contacts etc as it's all backed up. Have removed the SD card too.
Do a task29 on it. Flash a new radio and ROM(would suggest OEM) and then get back to us. Worst case something got knocked loose inside and it needs to go to HTC for repair.
craigpyro said:
I have tried the hard reset but no joy. It runs the reset but then on boot back to white screen. I'm not fussed about the contacts etc as it's all backed up. Have removed the SD card too.
Click to expand...
Click to collapse
i've encountered this lately for some strange reason ( being a flash junky) but found my way out of it.
flash your stock ROM via sdcard method, this will reset the spl to the original. (you can easily flash hspl anyway afterwards when you tire of the stock rom).
Ignore my post below. Have drained the battery overnight and this morning have been able to boot to:
PB81100 HX-BC
SPl-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
SERIAL
From here I'm hopeful I can do something.
_______________________________________________________________________________________________________
Sorry guys - but I don't understand how I am meant to do a task29 or ROM via SD card method when I cannot link by USB/ActiveSync or see anything on the screen.
craigpyro said:
....
Sorry guys - but I don't understand how I am meant to do a task29 or ROM via SD card method when I cannot link by USB/ActiveSync or see anything on the screen.
Click to expand...
Click to collapse
The microSD method does not require your phone to connect to the computer.
Here from the newbie guide to flashing a ROM:
Download a shipped Rom from *HERE*
- Rename the extension to .zip
- open it with winzip and extract the RUU_signed.nbh file to a folder
- Rename it to LEOIMG.nbh and copy it to the root of a microSD card thats been formatted to FAT32
- Insert your storage card into your phone
- Enter Bootloader and follow onscreen instructions to flash
This flashes your phone back to warranty status - it replaces the HardSPL, the ROM and the Radio.
Once your phone is repaired, you can always HardSPL your phone again.
I've tried using the HSPL tool to re-install back to 1.41 and other SPLs. The application says it's successful but when I restart the bootloader still reads:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
have tried Flashing ROMs and running Task29. Everytime the Bootloader switches to the updating progress bar then crashes out to Error [262].
I dont have a card reader to try from the SD card but even if I did I'm starting to feel doubtful.
are you sure, that the radio is compatible with the rom?
i'm pretty sure its the same fail.
DN41
OK - booting from FAT32 formatted microSD.
Stock ROM failed
Radio_2.08.50.05 failed
maybe a corrupt image file ? try downloading another one and see if that helps
I've tried 2 images. They get to different points at the radio install then fail. Try to get another img.
Starting to despair a little now. Trying to get just the radio on to start with.
This radio installs up to 100% (instead of about 20%) then reads:
00018003
LEOIMG.nbh - FAIL
Radio_V2Fail
Update Terminate
UPDATE FAIL
I really am getting desperate now having spent almost all day working on this.
Try using the supplied 2GB microSD card that came with the phone. Sometimes there are problems with using larger cards.
Thanks for the idea however I'm using a spare 1GB.
Silly question, but it is an O2 original ROM (assuming that is what your phone originally had on it) you downloaded and are flashing and not an HTC stock ROM (ie 1.66 WWE)?
I have tried both.
I am on the same issue here. Have read almost anything i could find to fix this. Am able to change spl through hspl2 successfully but showing the same spl 1.42 hspl in bootloader. The thing is only unable to flash radio. I can flash a custom rom with sd card but after flashing when it boot up only a white screen is showing. When i try to install a official stock rom it shows that the radio v2 not installed successfully. So its probably radio problem. Hope some one could help us fix this. I tried installing a radio with the sd card and still gets the radio v2 fail. Tried installing custom rom and radio with the usb but doest go beyond 0% and error shown in the pc. HELP HELP HELP
craigpyro said:
Starting to despair a little now. Trying to get just the radio on to start with.
This radio installs up to 100% (instead of about 20%) then reads:
00018003
LEOIMG.nbh - FAIL
Radio_V2Fail
Update Terminate
UPDATE FAIL
I really am getting desperate now having spent almost all day working on this.
Click to expand...
Click to collapse
With the steps I describe here I was able to recover the device.
http://forum.xda-developers.com/showthread.php?t=668347
But only if you follow the exact steps!
I tried many stock roms first and all were stuck on the radio.
Only the method I describe worked for me.
Good luck.
for you guys across the pond, don't you have to flash a .51 radio, not a .50 that you were using for the custom ROMs?
Hi all,
I would really appreciate if someone can help me reverse this process. I have an HD2 that i need to restore it back to factory ROM/condition and return it to US T-Mobile. I previously have WP7 on nand, Android on SD, Radio 2.15, with Mgldr 1.13 with HSPL 3.
I followed the procedure for flashing through SD as it will remove the HSPL. So i downloaded the ROM from TmoUS website, renamed the file to LEOIMG.nbh, and put it on a 4gb class 2 (FAT32) card. Enter bootloader mode by holding down volume/power button. Then it said loading and ask if I want to write over the image, select yes ... then it start the process. Though, half way through i receive the error message! Now when i turn the phone on i can't get past the bootloader mode. Just the error message even when I try to flash again via SD (the process doesnt even start - just said "loading" then "not allow" error message). When i get it plugged in to flash via desktop, the device is not recognized by the update utility. I'm not sure what could have gone wrong .. but any help or tips to reverse this process is greatly appreciated.
Thanks guys!!
What does it say in bootloader now?
If i just power it on I get the blank screen that said "error installing rom" with the triangle and the exclamation mark in the middle. If I boot into bootloader mode it will first get to the screen where it said "loading" then shortly it will say "error" and "not allow" then take me back to the bootloader mode. though, I noticed that the SPL is now 3.03 instead of 2.08 .. but other than that, I couldnt find a way to flash it by SD or USB. Any suggestion on this? Thanks for your help Macgnolia!
Sounds like it flashed the correct SPL and may be failing on the ROM flash, it sounds like it may be flashing the correct radio too.
What I would do is keep your phone completely off for about 3 hours, then turn it back on into bootloader, then try the flash again.
It might have some random overheat thing going on or something. Since you're back to stock SPL, go ahead and flash via RUU instead of SD and see if that does anything, it should let you since it's a stock ROM you're flashing.
Yeah I am with Orangekid here it might help to let your HD2 rest for a while so the internal temp is reduced as it my be some kind of freak heat issue right now. The HD2 hates heat incase you did not know this. I would still like to know what the top line of your bootloader says so we will know if you have the right device I.D. and that you are not one of the unlucky people to get a their device I.D. mysteriously screwed up by a stock ROM flash.
I'm at work and can't really play with it but definitely I will try it again jz to see if its the heat issue. Also, you think it could be the issue with the card by any chance? I was reading on flashing with SD and there were some conflicting opinions about the class and format for SD. And this is my wifes hd2 .. she'll probably freak out .. hehehe ... Thanks guys '-)
Sent from my HTC HD2 using XDA App
qdochemistry said:
I'm at work and can't really play with it but definitely I will try it again jz to see if its the heat issue. Also, you think it could be the issue with the card by any chance? I was reading on flashing with SD and there were some conflicting opinions about the class and format for SD. And this is my wifes hd2 .. she'll probably freak out .. hehehe ... Thanks guys '-)
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
card shouldn't matter as long as it's 8gb or less from my experience. Once it's off for a few hours just try to reflash stock via RUU and see what happens.
And yeah, go ahead and load up bootloader first to see what the top line says.
I just tested it again .. same problem! at the top right corner it says "RUUNBH" then the series of lines in the red portion of the screen as follows:
PB81120 SS-B3
SPL-3.03.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
Upgrade ROM code error
Please try again
and if I just power it on it goes to the error message .. then "loading" screen .. then "error" .. then "not allow" .. then back to bootloader mode but the third line now say MicroP-Wrong Platform (0x0)
any suggestion guys??
I thought it might have been that the download rom was corrupted .. went to tmo and download another one .. I tried to flash again .. get from bootloader mode .. then to loading mode .. and just stuck there ..
qdochemistry said:
I thought it might have been that the download rom was corrupted .. went to tmo and download another one .. I tried to flash again .. get from bootloader mode .. then to loading mode .. and just stuck there ..
Click to expand...
Click to collapse
Have you try with different micro sd card?
battery pin check, whether it is bent.
Battery capacity should at least 50%
Did you rename the RUU_signed.nbh to leoimg.nbh?
When you transfer it to sd card, did you using card reader?
Anything is possible. Please take a look of the above check list
I'd be tempted to try a full change of spl, use hspl4 to drop spl from 3.03.0000 down to 2.08.0000 or 2.10.0000, then try first the 2.13 rom and then the 3.14 rom over USB again.
samsamuel said:
I'd be tempted to try a full change of spl, use hspl4 to drop spl from 3.03.0000 down to 2.08.0000 or 2.10.0000, then try first the 2.13 rom and then the 3.14 rom over USB again.
Click to expand...
Click to collapse
Done!! THANK YOU!!!!!
For some odd reasons, my laptop (win7 ultimate) always seems to have connection issues even with chevron for wp7. I plugged it in to my wife's laptop (vista ultimate) and it connects. I was reading your comment on a similar issue in another thread and along with your suggestion here .. I figured it must be HSPL issue. I first used HSPL4 to reinstall 2.08 and immediately mgldr popped up. Then i flash the Tmo stock ROM over it. Then use HSPL4 to flash over (twice) with 3.03 (the one without the HSPL).
It took away the Energy boot screen, now I'm on 3.14 with 2.15 radio. I checked bootloader and it saids the following:
PB81120 SS-B3
SPL-3.03.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
Which is a problem because I checked on the refurbished device they sent and it has SPL 2.10. And so, I put HSPL 3.03 back on there to flash via SD again. Now i run into the same problem I orginally did .. about 20% into the update process and it stops and said update error. Could this be something obvious that I'm doing wrong? and also is there a way to get spl 2.10 without SD flash??
Thanks bud
Edit: I did it again a couple times via SD and it worked! I checked bootloader and it said spl 2.10 so I guess everything is back to stock now. I guess I'm gonna throw it back in the box and send it off. Thank you everyone for the fast reply and for all the help on this issue ... you guys are awesome! Thanks
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.
I have a 512mb hd2 and today, when i reboot my phone, magldr shows fatal hit 1 and it wont boot into android or enter cwm.
Therefore, i did a task29 and flashed a stock winmo rom using usb cable. However it wont boot into winmo. It shows the htc logo and it stucks there. Sometimes it show htc logo with rgb at the bottom and it will stuck there. I never get into winmo.
Then i tried flashing the stock winmo rom using the sd card method. However, when the phone say that the process is finished, i plugged out the battery. i didnt know that i have to press the red button.
Now, the phone will only boot into the tri coloured screen and the screen shows this:
e??????u HX-BC
(upside down "e" followed by some unknown and indescribable characters followed by a "u")
SPL-142.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
I cannot do anything else. I can't flash anything at all. It will end up in an error.
When i try to flash stock winmo rom using sd card, it will say loading... , then it will say checking... then this red numbers: 0058002 will appear on top then it will go back to the tri coloured screen again.
When can i do?
corrupted modelID, (the e??????u HX-BC bit)
I think JTAG is the only way out, and i've not actually seen hard confirmation that JTAG will fix it. there certainly isn't any flashing solution that i've seen, and we've seen this problem a fair few times.
Unlucky. Got warranty?
yes, its still under warranty. Would the warranty be void?
munchyzoo said:
yes, its still under warranty. Would the warranty be void?
Click to expand...
Click to collapse
Hi,
Unless you can flash an original WM ROM,warranty will be void.
You need to revert back to orginal... HSPL is a hack and your warranty is void.
Go to HTC site>support>download>ROM upgrade and choose appropriate ROM upgrade for your phone
Extract with winrar or 7z the RUU_Leo_HTC_****************************_Ship.exe
find the larger *.nbh file and rename it to leoimg.nbh and place this file on an sd card that is 4gb or less
and reboot to bootloader (the one with 4 colors,hold volume down button)
follow the instructions from there
That way you will have your original software with SPL restored and ready to send it for repair
No need for PC drivers etc.
Don't panic, faced this situation before.. create a goldcard .. follow this thread
Really? Goldcard ignores modelid? You sure? Cos that would imply that you could use a hd2 Goldcard to flash any winmo rom to any winmo phone, which you can't. I'll be interested in anyone confirming absolutely that a phone with a corrupted modelid in bootloader can be flashed from Goldcard.
@op. Yes warranty is valid If your boooader shows a valid spl, ending 0000,because you tell them you woke up and it was on the charger, hot, and in bootloader, screen on, that top line looks wrong, you tried to flash the stock rom but it fails. So long as the spl is good is usually enough for warranty.
Yes with goldcard you can put any HD2 rom on any HD2 phone, debrand .. make it chinese or whatever.
And that's my slightly sarcastic point,,,,, if the modelid is corrupt the Goldcard won't recognise it as a hd2.
munchyzoo said:
Now, the phone will only boot into the tri coloured screen and the screen shows this:
e??????u HX-BC
(upside down "e" followed by some unknown and indescribable characters followed by a "u")
SPL-142.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
When can i do?
Click to expand...
Click to collapse
I saw on the bottom Mr Samsamuel is here, he point me a lot of help to revive my HD two days ago, now my hd2 is up and running. First you failed with MAGLDR, and you did to revive with stock rom. what stock rom did u use. More info will help many hd2 guru here
I believed before you flash anything (as I understood from own experience) flash HSPL, do task29, flash Radio. Just try and let us know. alert : do not do this on Virtual Machine
I have step by step edited copy tutorial to install cLK on hd2, it also can be use to revive brick hd2 (at some level of brick) PM me I will send by email
let us have coffee
the stock rom I use is hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
but the problem is I can't do anything with my phone at all. i can't flash hspl or any rom at all...
Buy anyways i have gotten my phone back from htc and now its working. i am now afraid of installing magldr as i fear the same problem (fatal hit 1) will happen again.
I am now considering the old sd card method of running android.... (i think this is safer)
Not sure if clk would have a similar error or something... i have not try it before.
I have googled the magldr fatal hit 1 error and quite a few people have this problem but i can't seem to find a real solution to it. I remember reading somewhere that someone say it is caused by many bad blocks on nand due to excessive flashing. (not sure what this means and how to deal with it)
Since got back ur live hd2. It will no fun anymore. No singgle software 100% safe or bug free. Clk is almost same with MAG both are boatloader. Your bootloader from htc also not bug free.
Running os from sd card is slow. Its same as ur pc booting from live cd/usbstick or external hdd. That for emergency only, rescuing fail software etc. Just do everything carefully read all instruction asking forum and google. You will safe and have a lot of fun
Sent from my HTC Incredible S using XDA App