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?
Can anyone help me please... I'm trying to upgrade the rom to the latest HTC HD2 rom for O2. I connect the phone via USB, sync it and then run the RUU program from HTCs website. The phone starts the process and boots the phone to the 4 colour screen and then to the black HTC progress screen and then it hangs on 0% for a few minutes until the utility finally tells me its lost connection with the phone (Error 262). I've done soft resets and hard resets. Disabled firewalls. Tried on another machine. Even ran the utility under XP SP3 compatibility. Still no joy. Can anyone help?? Thanks
Sounds like you might have a bad USB cable or that you are having timing out problems. First forget about the ActiveSync. All ActiveSynce does is help insure hour HD2 is ready to be flash by checking the battery level and such. Power your HD2 on but hold the volume down button down while powering on. When you see the tri color bootloader screen connect hour USB cable and wait for the Serial in the white bar of bootloader to change to USB and then right click the RUU of the ROM and select run as administrator. If this still does not work I would try another USB cable.
T-Macgnolia said:
Sounds like you might have a bad USB cable or that you are having timing out problems. First forget about the ActiveSync. All ActiveSynce does is help insure hour HD2 is ready to be flash by checking the battery level and such. Power your HD2 on but hold the volume down button down while powering on. When you see the tri color bootloader screen connect hour USB cable and wait for the Serial in the white bar of bootloader to change to USB and then right click the RUU of the ROM and select run as administrator. If this still does not work I would try another USB cable.
Click to expand...
Click to collapse
Thanks for this... i followed your instruction and used 2 different cables. No joy.
Anything else I can try that doesn't involved the device suffering a sudden impact with the nearest wall??
Cheers
could it have anything to do with the phone being locked to O2... its the latest ROM for O2 that I'm trying to install.
mr_bacon said:
could it have anything to do with the phone being locked to O2... its the latest ROM for O2 that I'm trying to install.
Click to expand...
Click to collapse
hmm....if you are trying to flash stock rom which is not intended for your device, you need HSPL or Gold card.
There are threads in Windows Mobile 6.5 section that will guide you on installing HSPL or making a Gold Card.
Good luck
silverwind said:
hmm....if you are trying to flash stock rom which is not intended for your device, you need HSPL or Gold card.
There are threads in Windows Mobile 6.5 section that will guide you on installing HSPL or making a Gold Card.
Good luck
Click to expand...
Click to collapse
Well here's the thing, my phone is locked to O2. I'm trying to install the latest ROM from HTCs website for O2 customers. For the life of me I cant get it to install. I did install HSPL a few months ago when I tried to run Android from the SD card. That didnt work either. Like I say, I've done a hard reset. Could the HSPL thing be causing an issue. How do I get rid of it.
I hate being a noob sometimes!!
mr_bacon said:
Well here's the thing, my phone is locked to O2. I'm trying to install the latest ROM from HTCs website for O2 customers. For the life of me I cant get it to install. I did install HSPL a few months ago when I tried to run Android from the SD card. That didnt work either. Like I say, I've done a hard reset. Could the HSPL thing be causing an issue. How do I get rid of it.
I hate being a noob sometimes!!
Click to expand...
Click to collapse
To get rid of HSPL you just have to run the HSPL Utility avain and choose the correct SPL version for your ROM when it asks what version you want to flash. Remember HSPL has the stock SPL versions to, click on the link in my sig to download HSPL 4. Hint thecstock SPL versions all have four zeros at fhe end and the HSPL version do not.
You said you are getting error 262, this usually means you don't have the right SPL or HSPL one of the two atleast that is if I remember correctly. What ROM are you trying to flash and what does it say in bootloader right now?
T-Macgnolia said:
To get rid of HSPL you just have to run the HSPL Utility avain and choose the correct SPL version for your ROM when it asks what version you want to flash. Remember HSPL has the stock SPL versions to, click on the link in my sig to download HSPL 4. Hint thecstock SPL versions all have four zeros at fhe end and the HSPL version do not.
You said you are getting error 262, this usually means you don't have the right SPL or HSPL one of the two atleast that is if I remember correctly. What ROM are you trying to flash and what does it say in bootloader right now?
Click to expand...
Click to collapse
Hi... Been away so only just got this reply.
The rom I'm trying to install is a stock rom update from the HTC website:
O2 (UK): 3.14.206.1
For the record, my phone is an O2 phone.
As for Bootloader? It currently says:
PB81100 HX-BC
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
Hope that helps. Really bugging the arse off me this is.
get hspl2,
put phone into bootloader manually first and connect usb lead
(thats why it was timing out on you ((error 262)) because the connection takes too long to reconnect when it reboots from winmo into bootloader, , if you do it yourself first, that solves this error 99% of the time.)
when 'serial' changes to 'usb' run hspl2, choose 1.66.0000 (i recommend this because 2.08.0000, whilst stock, is a tmous stock, so 'may' give problems, , totally unconfirmed, but i had issues recently removing android/magldr whilst spl was 2.08.0000, i switched to 1.66.0000 and it worked straight away, i have a slight hunch that spl 2 doesnt like to be downgraded in some circumstances, , if you preffer you could use hspl4 and go straight for 3.03.0000, since that is whjat your 3.14 rom will install anyway when you flash it)
when it reboots saying its done, immediately hold voldown to re-enter bootloader
when serial changes to usb, run your 3.14.exe
samsamuel said:
get hspl2,
put phone into bootloader manually first and connect usb lead
(thats why it was timing out on you ((error 262)) because the connection takes too long to reconnect when it reboots from winmo into bootloader, , if you do it yourself first, that solves this error 99% of the time.)
when 'serial' changes to 'usb' run hspl2, choose 1.66.0000 (i recommend this because 2.08.0000, whilst stock, is a tmous stock, so 'may' give problems, , totally unconfirmed, but i had issues recently removing android/magldr whilst spl was 2.08.0000, i switched to 1.66.0000 and it worked straight away, i have a slight hunch that spl 2 doesnt like to be downgraded in some circumstances, , if you preffer you could use hspl4 and go straight for 3.03.0000, since that is whjat your 3.14 rom will install anyway when you flash it)
when it reboots saying its done, immediately hold voldown to re-enter bootloader
when serial changes to usb, run your 3.14.exe
Click to expand...
Click to collapse
Thanks for this but can I ask a favour... Can you give me an 'idiot guide' as to what to do? I'm a compelete noob to this kind of thing and don't wanna brick my phone.
Cheers
mr_bacon said:
Thanks for this but can I ask a favour... Can you give me an 'idiot guide' as to what to do? I'm a compelete noob to this kind of thing and don't wanna brick my phone.
Cheers
Click to expand...
Click to collapse
Ignore that..
Mate - you're a genius. Followed your instructions and it worked like a charm.
Cheers pal. You saved my brain
Erm, not sure how much more basic i can make it. (Ignore my descriptions, just follow the steps)
Power off, hold voldown,power on keeping voldown held,, see multi striped coloured screen, that's bootloader, you can flash from this screen.
First you should try without bothering to change the spl.
Enter bootloader and connect USB, run the 3.14 you downloaded. That's it.
If it doesn't work, try changing spl as in my previous post by entering bootloader, and instead of running the 3.14 you run hspl instead.
As for writing a guide, you already read the various "how to flash.." guides (there are several) and watched the (also several) YouTube guides before you even started this thread,,, didn't you? Didn't you?? If not then shame on you!
Post back and ill check tomorrow.
Hey XDA
Hope someone out there have got some good advice. We have some HD2s where i work and i have been sent one that is acting kinda weird.
I simply can not get it to flash a rom (_HTC HD2_RUU_Leo_S_HTC_DAN_3.14.403.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship) - we only use normal HTC roms. When i try to flash it nothing happens, it boots into the bootloader and just sits there at 0% until i disconnect the cable, if i dont it will sit there untill it runs out of battery. Tried a few times now and same result.
i have also just tried a restore, to see if its the internal flash rom that is broken and the restore also fails. My own HD2 restores in like a few seconds but this one just sits there again, like when i try to flash a rom to it.
So is it totally dead or is there something i should try?
Have you tried to use task29 (via computer) , then flash (via nbh) the htc rom?
hmm just tried task29 and it did nothing, it booted the phone to the bootloader but no progress screen did show up. Tried it again and the phone just shut off again after showing the bootloader for a few seconds.
beginning to think this phone is toast.
Gonna try a HSPL update later and just flash a non HTC rom to see if that works.
dkwolf said:
hmm just tried task29 and it did nothing, it booted the phone to the bootloader but no progress screen did show up. Tried it again and the phone just shut off again after showing the bootloader for a few seconds.
beginning to think this phone is toast.
Gonna try a HSPL update later and just flash a non HTC rom to see if that works.
Click to expand...
Click to collapse
HSPL 2.08 & reflash original HTC ROM via PC USB.
Do you get any error codes from the flash utility ?
could be CID related but you should see error code.
Yes, trying it with HSPL seems like a good idea to me, too.
Because then you can also try other ROMs.
will try this stuff on monday - i just cba to do more work today
thx for the advice
Build a gold-card and flash from the SD slot. If that doesn't work, put it in a zip lock bag and then into the freezer for 10 minutes. After 10 minutes, boot the phone and try flashing again immediately in it's chilled state. If it get's ANY further, you have a bad overheating NAND and need a new main board.
got HSPL2.08 flashed and a Dutty 3.14 rom but phone refuses to reboot sometimes and boot just shows the white HTC background and does not show the radio/os versions in the bottom. So i am just gonna toss this one out, since its can not be serviced (supplier has gone bust).
But still havn't gotten any error codes from the phone or flash programs, other then "USB connection failed". So i think its nand is kinda broken now.
dkwolf said:
got HSPL2.08 flashed and a Dutty 3.14[/COLOR] rom but phone refuses to reboot sometimes and boot just shows the white HTC background and does not show the radio/os versions((edit - the RGD screen)) in the bottom.
Click to expand...
Click to collapse
first, you can't run 3.14 roms on anything except spl 3.03.0000 or 3.03.hspl
Second it isn't booting because it almost certainly needs an updated radio, 2.15.50 for instance. You probably still have a 2.xx.51 from the original stock, and so wont show rgd screen till you change radio, won't run smoothly till you correct the spl with hspl4
But still havn't gotten any error codes from the phone or flash programs, other then "USB connection failed". So i think its nand is kinda broken now.
Click to expand...
Click to collapse
Put phone into bootloader manually, don't use front mounted USB ports, be sure and update win mo dev center to latest ver ..... all the usual USB connection error advice. Trying another PC with a different windows variant often helps if its available.
samsamuel said:
first, you can't run 3.14 roms on anything except spl 3.03.0000 or 3.03.hspl
Second it isn't booting because it almost certainly needs an updated radio, 2.15.50 for instance. You probably still have a 2.xx.51 from the original stock, and so wont show rgd screen till you change radio, won't run smoothly till you correct the spl with hspl4
Click to expand...
Click to collapse
hmm you sure? The dutty download page says -
Things to Know how about my ROMs:
* Radio 2.15 Recommended
* HSPL 2.08 Recommended
* HSPL 3.03 doesn't support 576 RAM enabled
But i'll try to flash a 3.03HSPL and find out what happens. I did flash 2.15.50.14 radio before i flashed the Dutty rom. But gonna give it one last try.
samsamuel said:
Put phone into bootloader manually, don't use front mounted USB ports, be sure and update win mo dev center to latest ver ..... all the usual USB connection error advice. Trying another PC with a different windows variant often helps if its available.
Click to expand...
Click to collapse
Have tried two pc's now, both running Win7 32bit - its all we have now.
Ahhh gitcha, then the dutty rom mustnt be 100% 3.14 rom (I didn't check) it must use a 2.x base to enable 576ram.
In which case, if stock roms don't flash but custom did, it could be stuck radio syndrome, which you can test for with (correct, get it using your serial from HTC.com) stock rom flash from sd card (4gb or smaller, fat32). Look out for "rsa radio fail" or similar on screen.
Edit, oh you said you flashed a radio, and that went ok?
samsamuel said:
Ahhh gitcha, then the dutty rom mustnt be 100% 3.14 rom (I didn't check) it must use a 2.x base to enable 576ram.
In which case, if stock roms don't flash but custom did, it could be stuck radio syndrome, which you can test for with (correct, get it using your serial from HTC.com) stock rom flash from sd card (4gb or smaller, fat32). Look out for "rsa radio fail" or similar on screen.
Edit, oh you said you flashed a radio, and that went ok?
Click to expand...
Click to collapse
yeah HSPL2.08, HSPL3.03 and Radio is flashing just fine. The roms i have tried also flashes perfect its just will not boot afterwards. I can usually do a hardreset on it and it will boot one time. If you then shut it off and try to turn it on again it fails with the white HTC screen again.
I am toally clueless on what is wrong with it, so gonna try to figure out if we have some kind of warrenty left on it and get it switched over to another one.
First, sorry if I post the kind of question that has been already asked 1000 times, I'll understand if my post is deleted.
here is the story: I still have an HD2, but got a Sensation almost one year ago.
Now my HD2 is still WinMo 6.5 with Android from the SD card.
Yesterday, one of my pupils (yes, I'm a teacher, and my pupils know I'm into smartphones....!) gave me his HD2 because his father kinda bricked it.
I haven't been using my HD2 or reading XDA HD2 section or a long time (I'm too busy flashing my Sensation, so reading Sensation threads ), but I thought I could give it a try to unbrick it, I'm not a noob after all (selfish guy!!!!!!!!!)
I think this HD2 was somehow bricked while trying to install Android into NAND, or installing MAGDLR, as far as my pupil can tell from his dad
So this Sensation can't boot and has this, written in the 3 colours screen
PB81100 HX-BC
SPL-2.08.00 8G XE
MicroP(LED) 0x05
icroP(TOUCH) 0x40
Upgrade ROM code error
Please try again
Click to expand...
Click to collapse
Here is the state I had this HD2, unable to boot, just able to get into bootloader with the message above.
I tried to flash latest Dutty ROM (because I was using Dutty creme of the creme at my HD2 time!)
=> through USB, flash freezes sometimes at 2%, sometimes 75%
=> through SD card: it flashes, says it's successful, but the device doesn't boot, back to three colors screen, or white screen with error message if trying to boot normally
I tried task29: full of errors, not better after flashing a ROM
I tried flashing a shipped "official" ROM => same as custom ROM, says success, flashed through SD card, but never boots to something else than 3 colors screen..
I tried factory reset, said successful, but still no boot!!
I tried flashing a Radio ROM=> flash successful, but still no boot
I tried flashing HSPL again, 2.08 and previous versions: it flashes OK, can see the changes in three colours screen, but no success flashing a ROM after
I noticed that sometimes, this HD2 vibrates 7 times quickly in a row, which my own HD2 had never done, and I suppose it's a very bad signal
I'm not a noob at all, but really can't follow every thread, and tried the search function with no real luck.
Is this HD2 definitly bricked? Is there something I can do?
Sorry again to seem so noob, I would have flammed someone posting like me, when I was following HD2 development everyday, before having my Sensation (and a Moto Defy for my wife)
see the line ''SPL-2.08.00 8G XE'' (you actually mean 2.08.0000) well teh .0000 tells you its NOT hspl, its a stock spl, so nothing will flash.
run hspl 2,3 or 4 and choose ''2.08.hspl''. Flashing, task29, magldr, all that will now flash.
THANKS!
how stupide I am (or too long away from WinMo)
I had tried hspl2 that was unable to do the job, hspl4 did it
So now I have spl 2.08.hspl
...but face other problem:
task29 fails: it launches OK but my HD2 disconnects from USB as soon as task29 starts its process
if I try to flash a custom ROM (the dutty one my own HD2 is still using), via usb, same, usb disconnects (it wasn't before I flashes hspl 2.08)
If I try flashing as a LEOIMG with microSD, it feezes at about 2/3 of the process
trying to flash a shipped ROM leads to errors, back to three colors screen with "Upgrade ROM code error Please try again"
...not to mention each time it replaces the hspl by stock spl
Any idea?
i900frenchaddict said:
THANKS!
how stupide I am (or too long away from WinMo)
I had tried hspl2 that was unable to do the job, hspl4 did it
So now I have spl 2.08.hspl
...but face other problem:
task29 fails: it launches OK but my HD2 disconnects from USB as soon as task29 starts its process
Click to expand...
Click to collapse
don't run flashes from running winmo, enter bootloader manually, when serial --> usb, run your flash/task29 or whatever. (Gorget about task29, it isnt necessary)
alternatively, if you do run it from running winmo, then once the phone has restarted and the usb has timed out, simply run teh flash program again, and dont touch teh phone, since it will now be in bootloader, and my above note takes over.
if I try to flash a custom ROM (the dutty one my own HD2 is still using), via usb, same, usb disconnects (it wasn't before I flashes hspl 2.08)
If I try flashing as a LEOIMG with microSD, it freezes at about 2/3 of the process
Click to expand...
Click to collapse
not a good sign, but ignore that for now.
trying to flash a shipped ROM leads to errors, back to three colours screen with "Upgrade ROM code error Please try again"
...not to mention each time it replaces the hspl by stock spl
Any idea?
Click to expand...
Click to collapse
because that's the way to remove hspl, , flash a stock rom from sd. Step 1 of sd flashing is the spl gets flashed, removing hspl, the phone then restarts and tries to flash the stock rom, but now that hspl has gone it fails, since you aren't using the correct stock rom for that particular phone.
Try this, get the stock 3.14 rom ( filename will be RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship )
EDIT - you dont have a tmous, right? if you do, dont do this!)
phone into bootloader
use hspl4 to set 3.03.hspl
phone into bootloader
flash the 3.14 rom over usb.
report back.
Man, I'm on the good way!
3.03.hspl seems to be the key, when 20.8hspl wasn't
While the stock 3.14 ROM finished to download, I could run a Task29 till the end, no more USB disconnecting.
Crossing fingers!
I'll edit this post once I've tried to flash the stock 3.14 ROM
Huge thanks to you !!!!
2.x spl is not a stock spl for regular hd2's, only tmous, so whilst it does work, it does introduce the odd problem. for example you cant sd flash stock roms with 1.x versions when you are currently on 2.x.
SO, with a regular hd2, any time you wanna return to stock or are having flashing troubles of some kind, it is always worth using hspl.exe (2,3 or 4 , doesnt matter) to remove the 2.x spl/hspl.
For me, I always go back to 1.66.0000 using hspl2 before i even try to flash a stock rom. Since i choose a 0000 ending, it will be updated as required by the stock rom.
Fingers crossed it helped.
samsamuel said:
Try this, get the stock 3.14 rom ( filename will be RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship )
EDIT - you dont have a tmous, right? if you do, dont do this!)
phone into bootloader
use hspl4 to set 3.03.hspl
phone into bootloader
flash the 3.14 rom over usb.
report back.
Click to expand...
Click to collapse
This worked for me...Thank you so much.
Hi everyone!
I am very sorry for such a n00b-post, but I really cannot find a solution.
The problem:
I recently got a HD2 of a friends who did not use it anymore, because Android suddently stopped working. Now it's stuck at a black screen [A] saying:
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07
by Cotulla 2011
I tried resetting the phone using the red button near the battery, but it did not solve the problem. I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".
I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].
Is this phone useless? What can I try to revive it?
What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.
andrejazzz said:
The problem:
Android suddently stopped working. Now it's stuck at a black screen [A] saying:
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07
by Cotulla 2011
I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".
I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].
What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.
Click to expand...
Click to collapse
Since you're unable to connect to PC, then you can't re-flash HSPL.
HSPL needed to force flash any shipped WM6.5 ROMs to HD2.
Then the only way is to flash original WM6.5 ROM for your device from uSD.
If you're not sure what CID, just download any HD2 shipped ROMs and try to flash from uSD.
Just be careful not to flash EU's ROM on T-Mobile device!
Extract the ".exe" file, then rename the ".nbh" file into "leo.nbh", copy that to root of uSD.
Power up your device while pressing vol down button.
Don't worry if the ROM refuse to flash, it's just a wrong CID.
But to make sure, connect your device to another clean PC (without android drivers inside, just WMDC), preferably a PC sets for syncing WP7/WP8 devices.
And make sure your device turns on by itself when charger is connected (auto turn on from off state).
That's just to make sure that usb connector is not damaged.
HD2 vibrate 1x at power on, it's normal.
Vibrate 5x after magldr shows up, I suspect something wrong with magldr or the ROM itself (corrupted or something).
Another possibility is some NAND bad blocks.
But if it's vibrate 5x at power on, then you have a bad luck.
The point is, flash the original ROM first.
If it's success, then flash HSPL.
After that, the rest is up to you..
Firstly, I want to thank you very much for your quick and extensive answer!
But I have only one tiny question: are these the ROMS which I can find at http: //www . 4shared . com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html#dir=MGRa1Cen ? And you mean I should just pick one and try?
You can also find HD2 shipped ROMs here.
Anything that has "TMO" are T-mobile ROMs, otherwise it's EU.
Again, don't flash EU's ROM on TMO devices!
The first 3 digit are the ROM version (1.66, 1.48. etc.), 3.14 is the latest WM6.5 ROM.
The next 3 digit are CID code (207, 404, 707, etc.).
Like I've said, if you don't know which CID for your HD2, then just download all ROMs from different CID then flash it one-by-one using uSD.
Thanks!
So far I have tried the 404 and 162 (edit: and 161, 911), but so far without luck. I'll keep you posted!
Tiny question: is it normal that I cannot shutdown in Recovery Mode?
Perhaps some useful info shown in Recovery:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
Correct me if I'm wrong, but it looks like an EU HD2, TMO HD2 are rarely using hynix nand, made around late 2009 or early 2010.
Just try to flash ROM with CID for your friend's country first.
If failed, then try another CID.
There should be one or two info about CID number vs. country somewhere around.
Good luck!
Sent from my Windead Phone 7 using xda app-developers app
At this moment I have tried all the NLD roms with no result. Also I have tried roms from several european countries, but none of them works:/ Might it help if I give the serial number?
And what might be worth saying: my phone turns on when connected to AC power / wall-charger; when connected to charger the "serial" disappears...
Thanks for all your help!!!
Have you try connect to other PC?
When flasing ROM from uSD and failed, what error message you got?
If it's "CID mismatch" or something like that, than it's definitely a wrong CID.
If it's "ROM update error bla bla bla", it's most likely corrupted flash image or the uSD itself (use a small sized uSD, 1gb would be fine).
Even if you flash the correct CID, without removing HSPL first, it would still throw an error message "ROM update error bla bla bla" during flashing Radio.
Then it will restart and retry to flash again on it's own.
By the way, I don't know if there are ways to flash HSPL from uSD.
Or guide on how to make a "gold card".
I sugest you search it.
Worth to try if you couldn't find the correct CID for your device.
CID from serial number?
Yes, back in 2010/11 HTC site provides s/n checking for download the correct ROM.
But now it's gone.
Sent from my Windead Phone 7 using xda app-developers app
Thank you very, very much for helping such a newbie ^^
At this moment, I am able to get into the update-menu: I changed the filename to LEOIMG.nbh. The only problem is that all the Dutch images give the same error: 00018003 : Radio (V2) - FAIL.
What could I do to solve this error? Use the freezer-trick or wouldn't it make any sense?
edit: it does boot when I connect to another W7 pc with WMDC (replies " Not connected" ), only it automatically starts the update-procedure (which fails).
There are no such thing as newbie, that's why we need to learn.
Error 00018003 during Radio flash?
I have no idea what error is that.
But first, are you sure that your friend bought the phone on local shop?
I mean, not imported, or when he/she travel overseas, or has the mainboard swapped at HTC service center.
It happens to me when my second HD2 suddenly has no signal, about 2 years ago.
Brought it to local service center and they swapped the mainboard without telling me.
And the swapped mainboard has CID from 404 (europe), the original was 707 (indonesia).
Okay, back to error something.
WMDC won't recognize the phone unless it's a working WM6.5 device, or a working WP7 device with WP7 SDK + Zune installed on your PC.
Just put the phone into bootloader screen (3 color screen), then connect it to a clean PC.
Does the "Serial" changed to "USB"..?
If it does, reflash HSPL 2.08 using HSPL4 package.
Then flash Radio ROM only, 2.15.50.14 is a good one.
Again, an EU HD2 can use either EU's Radio ROM or T-Mobile's Radio ROM.
But a T-Mobile HD2 can only use a T-Mobile's ROM..!
If the "Serial" doesn't change to "USB" but on your PC makes sound like something is plugged in, open device manager and look for an unknown device (no drivers loaded).
Expand it, what does it says?
To be honest: I am not 100% sure that it is an European (Dutch) phone. What I saw when I opened the phone's back was that the warranty-seals on the screws were molested. I don't think he got the motherboard replaced: way to expensive in relation to a new phone...
The bootloader screen gives now the following text:
RUUNBH
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0X05
CotullaHSPL 0x40
Upgrade ROM error
Please try again
When I connected it to a clean pc, the phone booted and gave another upgrade-error, only this time on a black screen (I got the uSD out the phone).
After booting the phone and connecting to a pc the "serial" does not change to "usb"...
When I tried to install WMDC I get the error "Installationpackage not supported by processor". Seems like bullcrap, but there it ends. No yellow exclamation marks in Device Manager...
I have yet not tried to flash a T-Mobile ROM to the phone. I have tried all the NLD ROM's: 1.66.404 ; 1.48.404 ; 1.66.404 ; 3.14.404 ; 1.66.404 ; 1.43.404
I have yet not tried the other ROMs I downloaded, but I will tomorrow. To start 161 does not work.
Also: I cannot shutdown when in bootloader or MAGDLr, is that correct?
What colour are your call & end key buttons !
if white you have standard EU type model. T-Mobile EU models are same as any EU model & can flash any ROM/Radio
If green & red you have a T-Mobile USA model (TMOUS) & need correct ROM (found in HD2 Wiki)
T-Mobile USA model needs care as if flash wrong radio version you can brick it.
Flashing via SD card should be last choice as first stage of a SD card flash is install of the SPL to standard SPL from the nbh which means you have no CID bypass as HSPL gone.
ideally you need a Windows 7 32bit machine with a known working WMDC setup & try flashing a suitable rom once decided on EU or TMOUS device.
As you have HSPL on your HD2 already it will bypass CID if flash via PC so you can flash any CID code rom.
Try connecting device to PC (with known good WMDC) and use reset button on HD2 to boot to bootloader & see if get any luck in running ROM installer from PC.
If lucky the USB flash issue is PC & drivers rather than hardware on HD2.
I would suspect you have nand issues on HD2 or perhaps worse, if nand sometimes you can get it back if persistent & get something to flash completely.
Thanks MisterB for adds up.
So am I, suspected a nand issue.
The reason I want him to revert back to original SPL & Radio is to make sure that it's a nand related problems, not radio hardware problems.
If he managed to find the correct CID for his phone, he could easily reverts back in case somethings wrong in the future after playing with custom ROMs.
This also happens to my friend's phone a couple months ago.
But in her case, the bad blocks are definitely located where magldr resides, and many more on data partition.
She can flash shipped ROMs completely, but it refuses to boot.
Can't flash a WP7 ROM because magldr freezes when it's loading, can't even bring the menu screen.
She can run a native sd android build for a couple weeks, but then it acting strange again.
Then finally she just gave up and bought another phone.
@andrejazzz:
You can't shutdown on bootloader (3 color) screen.
Remove the battery is the only way to shutdown, or press the reset button to restart.
But you can shutdown/restart or anything else on magldr menu screen.
Press & hold power key right when magldr loads up (before it's start to "go go go").
In addition, you can download WMDC x86 version here, and x64 version here..
He may indeed need try SD flash but I would exhaust all options of USB cable flash via PC first as retaining HSPL will be useful to start with as any generic HTC ROM could be used for the USB cable flash.
If that is not possible then flashing via SD is only viable option & indeed many times only way get over bad boot/nand issues but with all the CID versions for HTC regions & operator branded regions you have a hard job knowing the right one, you could even try the right ROM & as it does not flash overlook it for further testing.
I see he has tried SD flashing but still has HSPL so either SD card is not best suited for nbh flashing or nand/hardware that bad even first stage of flash is not possible.
If I was testing this device & trying recovery I would probably try freezer test to cool device prior flashing & make good effort on USB flash before going on to SD card.
Most well used Android HD2s these days have nand or bga issues to some degree as android works the hardware so much harder than WM6.5.
You really need be sure PC & driver are known good for flashing & if going to SD flashing that SD card is suitable or you will waste a lot of time & effort.
Loads of links & tips for all the software & some threads are in the HD2 Wiki
I apologize for replying so late, but I have had no time: I had a few tests at school
@Mister B: I have a black HD2 with white icons, so I have a european model.
I have installed installed the X86 on a clean 32-bit system, but it does not recognize the phone. I have reinstalled the WMDC on my W7 64-bit system, but still it does not recognize the hd2. I have no other Windows Phones, so I am not able to verify the WMDC-installations.
When I connect to a pc, the phone boots and shows: "Software update failed! Please try again"
@Shadow_Nexus: Correct, that is exactly what happens. I do not completely understand what you mean with "Press & hold power key right when magldr loads up (before it's start to "go go go")", could you please explain?
@Mister B: How could I check if the SD-card might be the problem? It is a 16GB Class 4 Kingston SD. I have tried all the NLD-roms and other versions (random countries, not TMOUS). I have tried the freezer trick with a NLD-rom on a mSD, but it did not work.
Thanks for all your help!
Best using a 2gb or 4gb (8gb max) card for nbh flashing & do a proper fat32 format with something like hp format tool before using it.
link below may help:
http://forum.xda-developers.com/showthread.php?t=681317
Again, thank you very much for your reply. But: do you have any clue what ROM's I should try? I am asking this, because I have already tried all the NLD ROM's I found on the site @Shadow_Nexus gave in post #4, but every one of them returns the same error. Should I switch to another country and try, for example, all German ROM's?
I got my hands on another HD2 and when I connect that one to my pc it show up, named "HTC Sync". The bricked one still does not respond:/ Should I retry all the non-TMO roms I can find?
Edit: My brother "helped" me out and sold the phone...