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
Related
Hi there,
I really need help!
I wanted to flash my phone with a nbh file, but I could not enter my bootloader.
I had installed HSPL3.
Now someone told me to use Flashaholic ROM update utility.
I did this, and a black screen with a % indicator appeared, not too long, it restarted, and went into a white screen with htc in the middle.
Restarting with volume down button pushed doesnt bring me into bootloader.
What can I do now?
I really need help!
Unfortunately, if you can't get your HD2 to boot into the bootloader, there's not much to be done.
Are you sure you had HSPL installed? Because from what I have heard, HSPL is there to always allow you to use it for flashing stuff, regardless of the integrity of other software parts such as the radio or the ROM, so reaching the bootloader should not be a problem for anyone.
Can you connect it to your PC via USB? If you manage to get a connection, you might just have a chance to flash another radio/ROM.
anrabi4 said:
Unfortunately, if you can't get your HD2 to boot into the bootloader, there's not much to be done.
Are you sure you had HSPL installed? Because from what I have heard, HSPL is there to always allow you to use it for flashing stuff, regardless of the integrity of other software parts such as the radio or the ROM, so reaching the bootloader should not be a problem for anyone.
Can you connect it to your PC via USB? If you manage to get a connection, you might just have a chance to flash another radio/ROM.
Click to expand...
Click to collapse
I installed HSPL3, and it said it was succesfull so...
After that I installed a custom rom with an utility that came with it (Dutty's)
So far I know, I cannot get any connection, but I try to download a stock rom (an utility exe) from HTC.com.
But I think this won't work right? because you have to sync.
You could try and flash a stock ROM via the SD Card, see if that works. There are some instructions here on XDA in the ROM Development section, check it out there.
Basically, once you have downloaded an official ROM from htc.com, extract it as if it were an archive and get the ruu_signed.nbh. Rename it to LEOIMG.nbh. Then take your SD Card, format it to FAT32, place the LEOIMG.nbh on the card and put it in your phone. While holding down the volume down button, boot the phone and a white Loading... screen should appear and the flashing process should begin.
I`m afraid this won't work either, as the bootloader is supposed to show up in order for you to be able to flash anything, but it's better than doing nothing, so...
anrabi4 said:
You could try and flash a stock ROM via the SD Card, see if that works. There are some instructions here on XDA in the ROM Development section, check it out there.
Basically, once you have downloaded an official ROM from htc.com, extract it as if it were an archive and get the ruu_signed.nbh. Rename it to LEOIMG.nbh. Then take your SD Card, format it to FAT32, place the LEOIMG.nbh on the card and put it in your phone. While holding down the volume down button, boot the phone and a white Loading... screen should appear and the flashing process should begin.
I`m afraid this won't work either, as the bootloader is supposed to show up in order for you to be able to flash anything, but it's better than doing nothing, so...
Click to expand...
Click to collapse
Does not work, still hangs in htc bootscreen.
What I have to do now? =(
I hope you have any more suggestions for me.
I will read it within 20 min, because I have to go soon for 20 min.
I really need my phone fixed =(
Hi, if I remember correctly, you already said in the Artemis-thread, that the VOL DOWN button is broken. If this is the case, I fear there is not much you can do...
Have the same problem too.
I've installed a few roms with no worries, tried one about an hour ago that performs a Task 29 and i'm also now stuck at the white HTC screen...
it says the task29 was succesfull and then got stuck on the white HTC screen and the rom failed to load as the laptop did not detect a usb connection...
I've downloaded a stock rom and put it on the SD card named LEOIMG.nbh and tried pressing the vol down button, the Red,green,blue,white screen appears i can see
PB81100 HX-BC
SPL 2.08.Hspl 8g XE
0x05
CotullaHSPL 0x30
Then "serial" at the bottom or if i have the phone connected to the pc then "USB" appears.
If i hold both buttons and perform a Hard reset the phone asks to press Vol up button then says restored really quickly then freezes at the white HTC screen..
Any suggestions
Cheers
Actually got it sorted now, the rom had the Flashaholic utility built in which i haven't used before.
As we speak the rom is now installing phew (stop sweating now)...
Thought i had bricked it...
MaxKaul said:
Hi, if I remember correctly, you already said in the Artemis-thread, that the VOL DOWN button is broken. If this is the case, I fear there is not much you can do...
Click to expand...
Click to collapse
It's not broken, it just worked before I did the task29.
The phone is empty, and has no bootloader, and no ROM.
wakers said:
Have the same problem too.
I've installed a few roms with no worries, tried one about an hour ago that performs a Task 29 and i'm also now stuck at the white HTC screen...
it says the task29 was succesfull and then got stuck on the white HTC screen and the rom failed to load as the laptop did not detect a usb connection...
I've downloaded a stock rom and put it on the SD card named LEOIMG.nbh and tried pressing the vol down button, the Red,green,blue,white screen appears i can see
PB81100 HX-BC
SPL 2.08.Hspl 8g XE
0x05
CotullaHSPL 0x30
Then "serial" at the bottom or if i have the phone connected to the pc then "USB" appears.
If i hold both buttons and perform a Hard reset the phone asks to press Vol up button then says restored really quickly then freezes at the white HTC screen..
Any suggestions
Cheers
Click to expand...
Click to collapse
task29 DELETES the ROM. You NEED to install a ROM. A Radio-ROM should be installed automatically with task29. If this isn't the case, you need to install a Radio-ROM too. You can either install the HTC ROM or you can install a custom ROM like forum.xda-developers.com/showthread.php?t=612580
Suggestion: Enter bootloader -> connect USB -> install ROM with CustomRUU
MaxKaul said:
task29 DELETES the ROM. You NEED to install a ROM. A Radio-ROM should be installed automatically with task29. If this isn't the case, you need to install a Radio-ROM too. You can either install the HTC ROM or you can install a custom ROM like forum.xda-developers.com/showthread.php?t=612580
Suggestion: Enter bootloader -> connect USB -> install ROM with CustomRUU
Click to expand...
Click to collapse
Do I have to repeat it again? there is NO BOOTLOADER
joshoon said:
Do I have to repeat it again? there is NO BOOTLOADER
Click to expand...
Click to collapse
If you'd read the entire post, you'd notice, that I quoted the user "wakers", who seems to be able to enter bootloader.
MaxKaul said:
If you'd read the entire post, you'd notice, that I quoted the user "wakers", who seems to be able to enter bootloader.
Click to expand...
Click to collapse
Well im not able to.
I did a HSPL before then I putted a custom ROM Dutty's on the device.
After that I putten a Stock ROM on it again, and then I used Flashaholic, and after task29 it got stuck.
Well no bootloader means no HSPL which is good news for your warranty coverage..
Just go to HTC service and play dumb " uhm i was playing around websites with a flash game and uhm my phone uhm rebooted and is like stuck ever since in uhm HTC logo"
Now if the case for not being able to load the bootloader is a broken volumedown button, yeah ur pretty screwed, prepare to dive in ur wallet.
Were do you live? If you need help and there's one living nereby maybe we can help (p.e. a full battery) I live in the eastern part of the Netherlands (Overijssel) PM me if you can come.
On the Kaiser (my previous phone) I also had a problem I couldn't enter the bootloader anymore, but I can't remember why or what I did to recover it.
- If it was an allmost empty battery and recharged it?
- If I have used a special tool to connect?
I really can't remember.
If I read your story, I think you have loaded a corrupted NBH thru SDCard method, otherwise i think you cannot wipe your bootloader. Task29 only wipes the ROM area not the bootloader.
Have you tried to contact Bepe or Cotulla, cause i think they know everything about (H)SPL.
Otherwise you can start building a new house (you've got your first brick )
have you checked you battery connections, the middle one is notorious for getting bent out of shape at which point the battery will not charge and you can't flash you ROM.
chris2busy said:
Well no bootloader means no HSPL which is good news for your warranty coverage..
Just go to HTC service and play dumb " uhm i was playing around websites with a flash game and uhm my phone uhm rebooted and is like stuck ever since in uhm HTC logo"
Now if the case for not being able to load the bootloader is a broken volumedown button, yeah ur pretty screwed, prepare to dive in ur wallet.
Click to expand...
Click to collapse
I'm 100% sure it's not the volumebutton, and yes Im gonna play a bit dumb ofc, but I already have another story.
henk-jan said:
Were do you live? If you need help and there's one living nereby maybe we can help (p.e. a full battery) I live in the eastern part of the Netherlands (Overijssel) PM me if you can come.
Click to expand...
Click to collapse
It's costs a lot for a trip to there.
Btw, I tried a full battery too, didn't work. (I have two)
webpatrick said:
On the Kaiser (my previous phone) I also had a problem I couldn't enter the bootloader anymore, but I can't remember why or what I did to recover it.
- If it was an allmost empty battery and recharged it?
- If I have used a special tool to connect?
I really can't remember.
If I read your story, I think you have loaded a corrupted NBH thru SDCard method, otherwise i think you cannot wipe your bootloader. Task29 only wipes the ROM area not the bootloader.
Have you tried to contact Bepe or Cotulla, cause i think they know everything about (H)SPL.
Otherwise you can start building a new house (you've got your first brick )
Click to expand...
Click to collapse
I think it's bricked man, my bro is looking for the papers soon, and then im going to the KPN shop (the provider), because the phone has been ordered from there.
nrfitchett4 said:
have you checked you battery connections, the middle one is notorious for getting bent out of shape at which point the battery will not charge and you can't flash you ROM.
Click to expand...
Click to collapse
All the connections look fine.
Okay here is the rundown:
1. Bought HD2 phone from ebay that had "freezing problems". Phone would freeze on "Stick Together" screen even after hard reset. Cleaned and made sure battery pins were straight. Removed SIM and sd card during the entire process.
2. Attempted to flash T-Mobile 2.13 update by sd card. (Formated card FAT32 and changed .nbh file to leoimg.nbh). Waited a day and then hard reset the phone and phone froze again.
3. Flashed HSPL and attempted to run Task29. (Right click on run as administrator but the program never completes). I've tried the version that requires a radio. I attempted to extract the Task29 that doesn't require the radio but for some reason the computer is unable to do so.
4. Tried to run T-Mobile update again but now that program cannot finish. Says something about radio failure.
I can still get into the bootloader screen but if I start it up normally it reads "System update failure". Needing any help I can get. I'm not an expert at this (obviously) so please try to use "noob" terminology for my benefit if possible. I'm using Vista and I'll try to give whatever information that may be needed in order to resolve this matter. Thanks in advance for your help.
What does it show in bootloader exactly?
And, after you flashed 2.13.531.1 stock did the phone boot past the splash screen (Stick Together screen)? Have you tried flashing via Activesync?
In bootloader in the upper right hand corner it says RUUNBH
then shows the following lines
PB81120 HX-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
Upgrade ROM code error
Please try again
Once I flashed stock ROM it went pass the splash screen once (and that was after many MANY hard resets without SIM and sd card).
I tried activesync also but it doesn't complete. It keeps failing when it gets to installing the radio.
try to flash just a radio....Just make sure its compatible with the phone...you can only use one series of radio for the tmous hd2....
Manually put phone into bootloader..
Connect to computer via usb
Run RUU...
Cant hurt...just to see if you can flash a radio to it..since thats where your getting your errors...
bossb2525 said:
Okay here is the rundown:
1. Bought HD2 phone from ebay that had "freezing problems". Phone would freeze on "Stick Together" screen even after hard reset. Cleaned and made sure battery pins were straight. Removed SIM and sd card during the entire process.
2. Attempted to flash T-Mobile 2.13 update by sd card. (Formated card FAT32 and changed .nbh file to leoimg.nbh). Waited a day and then hard reset the phone and phone froze again.
3. Flashed HSPL and attempted to run Task29. (Right click on run as administrator but the program never completes). I've tried the version that requires a radio. I attempted to extract the Task29 that doesn't require the radio but for some reason the computer is unable to do so.
4. Tried to run T-Mobile update again but now that program cannot finish. Says something about radio failure.
I can still get into the bootloader screen but if I start it up normally it reads "System update failure". Needing any help I can get. I'm not an expert at this (obviously) so please try to use "noob" terminology for my benefit if possible. I'm using Vista and I'll try to give whatever information that may be needed in order to resolve this matter. Thanks in advance for your help.
Click to expand...
Click to collapse
hello there...
this is known issue with some t-mobile hd2's..
this happens mostly when you get refurbished..but i'm not sure
almost same thing happens look here --> http://forum.xda-developers.com/showthread.php?t=795554
go ahead, flash stock rom, get replacement from t-mobile
Thas not gonna help
JackH said:
hello there...
this is known issue with some t-mobile hd2's..
this happens mostly when you get refurbished..but i'm not sure
almost same thing happens look here --> http://forum.xda-developers.com/showthread.php?t=795554
go ahead, flash stock rom, get replacement from t-mobile
Click to expand...
Click to collapse
He stated quite clearly he bought the phone on eBay - Hows he gonna get a replacement from T-Mobile without a warranty?
Okay - if you can get to the Bootloader consistently, you have that going for you at least. Did you try just flashing a Radio? If thAT fails, Next thing I would try is a task 29, then flash a stock ROM afterwards. Alternately, you COULd try reflaching HSPL, in the event that it's corrupted in some way. You have some options still, just preceed cautiously, and don't flash anything you are unsure of. Let us know what happens!
i have the same exact issue too, see: http://forum.xda-developers.com/showthread.php?p=8434282#post8434282
I am using windows 7, and mine installed the regular spl and rom, but not the radio from the memory card.
I hope someone figures it out.
simplest way
hi brother.....i m facing the same problem nd i dnt hav the bill from t mobile also, so cnt replace the **** back..nyways...what i did was gave it to a htc service center they chekd the fon...nd said hav to replace the mainboard... fuk.....now its stil ther since 3 weeks.....lets c wat happens
Sorry, I just realized XDA went down one night and all my updated information that I posted on here was erased. Anyway, I was successful in running task29. I also successfully updated the phone to the 2.13 software from t-mobile. In the end my phone still froze and would occasionally go past the splash screen. Since I can't get any consistency with the phone (and since I've been working on this phone for almost 3 weeks) I just finally gave up on it. Hope somebody can find a solution for the rest of you experiencing this problem. I will continue to check back at the other threads to see if anyone finds the magic fix. Thanks for everybody who tried to help me.
Hi got a problem with my HD2 which i got a couple of months ago, it came with WinMo 6.5 as standard, so i decided to put Android on it, so i flashed all the MAGLDR and clockwork mod stuff on, and loaded HyperDroid GBX onto it, this ran brilliantly up until yesterday when i briefly browsed facebook, then i locked the phone and put it back in my pocket, next time i tried to use it the touch screen would not respond whatsoever. Only the physical buttons worked, so i pulled the battery out and reset it but that has not helped.
Any reason why it suddenly failed like that? Very annoyed
Hi!
Try to return back to stock WM, it might help.
When I turn on the phone with the power button the touch screen doesn't work so I have to use any other button and it works. Running the same rom as you.
Yeah i noticed that too, when ever i unlocked the phone with the power button most of the time it didnt respond but any other button worked fine.
i sent it to repair.they will change the whole screen
Go back to a WM6.5 stock ROM, if the screen still does not work, then you may want to consider having it repaired. If it is under any sort of warranty make sure you un-HSPL it.
What happens if they find out that I have run Android and Energy rom on it?
Now it has SPL-3.03 0000 and I think the latest ROM.
Can I send it in like this? Is the spl original?
10Buron said:
What happens if they find out that I have run Android and Energy rom on it?
Now it has SPL-3.03 0000 and I think the latest ROM.
Can I send it in like this? Is the spl original?
Click to expand...
Click to collapse
Once latest official ROM is installed and phone booting normally, nobody cares what OS was installed on it before You can have even SPL 2.08.000, it will pass check-in. And yes, SPL 3.03.000 is the latest official one.
Hope you are right, because I don't want to end up in jail for having messed with the copyright....
My phone won't open, the screen is not responding. But I know I have the 3 14 0466 ROM(?) and spl-3.03.0000
the multi-coloured screen says:
PB81100 HX-BC
SPL 3.03.0000 XE
MicroP (LED) 0x05
MicroP(TOUCH) 0x40
Did You tried to flash through SD card?
It's easy. Just unpack somewhere downloaded ROM, rename file RUU_signed.nbh to Leoimg.nbh, copy it to your SD card and go to tri-color screen. Then you will be asked to flash the phone and after after pressing Vol+ key it will start to reflash. Hope it helps, goodluck!
thx
was that last one for me? I think I have the correct Rom and SPL, the screen is not functioning, so I am planning to send it in for repair.
I have tried sd-flashing, and it didn't help. Used different sd-cards and LEOIMG.n...
but I managed to get it to the spl and rom as mentioned.
Planning on sending it in, bad plan?? or good plan??
10Buron said:
was that last one for me? I think I have the correct Rom and SPL, the screen is not functioning, so I am planning to send it in for repair.
I have tried sd-flashing, and it didn't help. Used different sd-cards and LEOIMG.n...
but I managed to get it to the spl and rom as mentioned.
Planning on sending it in, bad plan?? or good plan??
Click to expand...
Click to collapse
If it is still under warranty, go on
In what circumstances your touch stopped working? Was it dropped ground, placed in wet conditions (eventually steam or mist or submerged)?
no reason really. Never dropped it, had it since last March.
Ran Android and Energy-Rom on it since october...
No Idea why it stopped working
10Buron said:
no reason really. Never dropped it, had it since last March.
Ran Android and Energy-Rom on it since october...
No Idea why it stopped working
Click to expand...
Click to collapse
It doesn't work all time or only after standby/block? I've had same kind problem with touch not working after standby, with Artemis WinMo ROM. Solved after HR but after few days repeated. I installed one of the latest NRG ROMs and it solved this trouble. If touch doesn't respond all the time then it may be dead because of controller failure and should be replaced IMHO.
it is totally blocked. nothing works on the screen. buttons are ok, but the phone is locked, so i can only see the unlock-slider...
IMHO?
10Buron said:
it is totally blocked. nothing works on the screen. buttons are ok, but the phone is locked, so i can only see the unlock-slider...
IMHO?
Click to expand...
Click to collapse
It's My Humble Opinion
Heheh, thanks. I am sending it in then. Hoping they can fix it. Can't be that expensive, if the warranty isn't valid. If warranty covers it, I am glad...
Thanks for your 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.
Hi everyone,
I'm totally lost with the HD2 my brother didn't want any more. I think he installed an android os but it couldn't launch or function correctly so I tried to have it back to his original state.
I tried the hard reset but it didn't work, the phone didn't launch.
I used the Task29, it worked and cleaned the phone. Then I tried to install the official rom 3.14 found on the htc support's page. The loading get stuck at 1% and stop to move until I get the 262 error.
I read a bit and try to understand how all of this work but I still don't get it. I tried the older version of the official rom, it worked a bit better since now the loading bar get stuck at 6 or 8 % randomly.
So now when I power on the phone it says : "Software update failed! Please try again" which I tried all yesterday long.
When I hold volume down and power on what I get on the red green blue white screen is this :
RUUNBH
PB81100 SS-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
Upgrade ROM code error
Please try again
I don't know what to do to resolve my situation. I'll be grateful for any help or hints you can give me.
Looks like you are trying via USB.
You could have a corrupt nand in a wrong area or some sort of hardware error.
Just to eliminate hardware, re-download the 3.14 ROM (in case you got a corrupt file)
and extract it, put the NBH file on the root of your SD card and make sure it's called leoimg.nbh disconnect from your PC and boot into bootloader and flash from SD
btw this is a tmobile phone right?
Maywiki said:
Hi everyone,
I'm totally lost with the HD2 my brother didn't want any more. I think he installed an android os but it couldn't launch or function correctly so I tried to have it back to his original state.
I tried the hard reset but it didn't work, the phone didn't launch.
I used the Task29, it worked and cleaned the phone. Then I tried to install the official rom 3.14 found on the htc support's page. The loading get stuck at 1% and stop to move until I get the 262 error.
I read a bit and try to understand how all of this work but I still don't get it. I tried the older version of the official rom, it worked a bit better since now the loading bar get stuck at 6 or 8 % randomly.
So now when I power on the phone it says : "Software update failed! Please try again" which I tried all yesterday long.
When I hold volume down and power on what I get on the red green blue white screen is this :
RUUNBH
PB81100 SS-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
Upgrade ROM code error
Please try again
I don't know what to do to resolve my situation. I'll be grateful for any help or hints you can give me.
Click to expand...
Click to collapse
Hello Maywiki,
task29 doesn't delete HSPL, that causes your troubles. May I cite from HSPL4 by Dark Forces Team:
"5) Uninstallation
Only way to remove the HSPL is to flash an original SPL from SD card.
- Take any "RUU_signed.nbh" from a ship ROM and copy it to SD card.
- Rename it to "leoimg.nbh"
- Reset the device while pressing the volume down button."
Be sure your battery is charged.
For future flashing experiences I advice you to not only "read a bit" but digging deep into it - and then re-read again.
Have fun
Getrid …
Getrid said:
Hello Maywiki,
task29 doesn't delete HSPL, that causes your troubles. May I cite from HSPL4 by Dark Forces Team:
"5) Uninstallation
Only way to remove the HSPL is to flash an original SPL from SD card.
- Take any "RUU_signed.nbh" from a ship ROM and copy it to SD card.
- Rename it to "leoimg.nbh"
- Reset the device while pressing the volume down button."
Be sure your battery is charged.
For future flashing experiences I advice you to not only "read a bit" but digging deep into it - and then re-read again.
Have fun
Getrid …
Click to expand...
Click to collapse
task29 did not cause any of his issues, after he did taask29 he tried to do what you say and flash the stock ROM but it hangs on the flash.
At no time from the bootloader should a flash just stick like that. I personally think it's a hardware failure, bad nand or something, or even a bricked radio if it keeps hanging near 1%, but you never know, the ROM he's using might be corrupt.
I still suggest you download the ROM again, put the .nbh file on your sd card like stated above and try a flash from SD.
If that fails maybe you can try to flash a custom ROM that does not include a radio and if that flashes we know we cannot flash a radio because that is what is hanging the flash.
Thanks for all your replies.
Yes I try via usb.
orangekid said:
btw this is a tmobile phone right?
Click to expand...
Click to collapse
Nope, it was bought in Belgium and it's not tied to an operator.
That's the name of the file I downloaded from the htc site : RUU_Leo_S_HTC_FRA_3.14.406.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
The problem is that I can't access the sd card. The pc knows that an htc device is connected but I can't acces the device (it doesn't show up anywhere) and the sd card. The windows mobile app doesn't find a device connected too. Could it work if I pass via another phone to put the file on the sd card ?
For future flashing experiences I advice you to not only "read a bit" but digging deep into it - and then re-read again.
Click to expand...
Click to collapse
The thing is, it's not my phone at the start. I wouldn't launch myself into flashing without a lot of reading but since I got the phone in this state it's hard to find where am I.
Maywiki said:
I tried the hard reset but it didn't work, the phone didn't launch.
Click to expand...
Click to collapse
hard reset doesnt do anything when magldr clk are there, only when winmo 6,5 is there.
The loading get stuck at 1% and stop to move until I get the 262 error.
Click to expand...
Click to collapse
it worked a bit better since now the loading bar get stuck at 6 or 8 % randomly.
Click to expand...
Click to collapse
thats bad, 8/9 is the time the radio is being flashed, and is a primary indicator of a stuck radio (which also covers stuck spl, , corrupt spl/radio/bootloader basically)
The first time, the 1% hang, is the point where a stock rom tries unsucessfully to flash the spl for the first time, either triggering teh corruption, or the first time a flash has been attempted and so teh first time bootloader notices it's corrupted, (hence the RUUNBH at teh top of bootloader, it has tried to start flashing, and encountered an error, and not dropped out of flashing mode, as you would expect for a normal failed flash)
From here on, chances are you will either
1-never get anything to flash
2-possibly get winmo custom roms (no radio, see) to flash but nothing else
3-things like task29 and hspl appear to flash, but nothing changes
try No 2 first, and then try the freezer trick,chill teh phone right down, and have an sd card ready with the leoimg.nbh ready on it ready to flash as soon as you take it out of teh freezer.
Just occasionally, people get past this type of error, probably meaning the issue was corrupt software, but usually there is no fix (except JTAG, and even that isn't always successful) possibly meaning hardware corruption of a critical area of nand.
Also, if it DOES work in the freezer, that probably means you have an overheating device.
Maywiki said:
Could it work if I pass via another phone to put the file on the sd card ?
Click to expand...
Click to collapse
yes, any method you like to copy the leoimg.nbh to the sd card is fine.
samsamuel said:
hard reset doesnt do anything when magldr clk are there, only when winmo 6,5 is there.
thats bad, 8/9 is the time the radio is being flashed, and is a primary indicator of a stuck radio (which also covers stuck spl, , corrupt spl/radio/bootloader basically)
The first time, the 1% hang, is the point where a stock rom tries unsucessfully to flash the spl for the first time, either triggering teh corruption, or the first time a flash has been attempted and so teh first time bootloader notices it's corrupted, (hence the RUUNBH at teh top of bootloader, it has tried to start flashing, and encountered an error, and not dropped out of flashing mode, as you would expect for a normal failed flash)
From here on, chances are you will either
1-never get anything to flash
2-possibly get winmo custom roms (no radio, see) to flash but nothing else
3-things like task29 and hspl appear to flash, but nothing changes
try No 2 first, and then try the freezer trick,chill teh phone right down, and have an sd card ready with the leoimg.nbh ready on it ready to flash as soon as you take it out of teh freezer.
Just occasionally, people get past this type of error, probably meaning the issue was corrupt software, but usually there is no fix (except JTAG, and even that isn't always successful) possibly meaning hardware corruption of a critical area of nand.
Also, if it DOES work in the freezer, that probably means you have an overheating device.
yes, any method you like to copy the leoimg.nbh to the sd card is fine.
Click to expand...
Click to collapse
Yeah exactly where I was going with this.
Use a USB SD card reader thing to put it on SD card, or even another phone if you have to.
Try a custom ROM maybe.
If you are running 2.15.00 you don't need to flash another radio anyways, and since you have HSPL you don't need another SPL either, so you're not quite as screwed as some others even if you've got a bad radio/no flash situation.
So I did what you said (except put the phone in the freezer).
The installation went ok. Once finished it said nothing so I guessed I had to restart the phone.
Now the phone gets stuck in a white screen with htc in green on it.
Did I make something wrong ?
Maywiki said:
So I did what you said (except put the phone in the freezer).
The installation went ok. Once finished it said nothing so I guessed I had to restart the phone.
Now the phone gets stuck in a white screen with htc in green on it.
Did I make something wrong ?
Click to expand...
Click to collapse
No, either your flashed task29 then no rom or it's not loading the ROM,
try the SD flash again with the CORRECT rom and see what happens.
orangekid said:
No, either your flashed task29 then no rom or it's not loading the ROM,
try the SD flash again with the CORRECT rom and see what happens.
Click to expand...
Click to collapse
I tried again with the 3.14.406.2 from the support site, the update goes without a problem :
RADIO_V2 - OK
RCUST - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
CONFIGDATA - OK
RUU_WALLPAPER1 - OK
RUU_WALLPAPER2_ OK
Update Complete
UPDATE SUCCESS
When I reset, the phone vibrate seven times and stay on the white page with the htc logo on it.
What do I have to do now ? Try another rom ?
Hmmm, radio_v2 OK, ,, that's unexpected, but doesn't necessarily change anything.. .
Give the freezer trick a few goes.
Maywiki said:
I tried again with the 3.14.406.2 from the support site, the update goes without a problem :
RADIO_V2 - OK
RCUST - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
CONFIGDATA - OK
RUU_WALLPAPER1 - OK
RUU_WALLPAPER2_ OK
Update Complete
UPDATE SUCCESS
When I reset, the phone vibrate seven times and stay on the white page with the htc logo on it.
What do I have to do now ? Try another rom ?
Click to expand...
Click to collapse
Sounds like your chip is overheating, not good. You need a main board replacement or maybe this:
http://forum.xda-developers.com/showthread.php?t=982454
or see if this guy will donate his
http://forum.xda-developers.com/showthread.php?t=1890582
That's what I think is wrong.
Take out the battery and put it and the phone in a baggy in the freezer for 15 minutes, then put in the battery and turn on the phone. It should load WM6.5 before freezing again...
samsamuel said:
Hmmm, radio_v2 OK, ,, that's unexpected, but doesn't necessarily change anything.. .
Give the freezer trick a few goes.
Click to expand...
Click to collapse
Ok, now I need an explanation. How the hell does this trick work ? I did what you said and now the phone works. What's the mystery behind this ?
Is it permanent or it will need to be done frequently ?
orangekid said:
Sounds like your chip is overheating, not good. You need a main board replacement or maybe this:
http://forum.xda-developers.com/showthread.php?t=982454
or see if this guy will donate his
http://forum.xda-developers.com/showthread.php?t=1890582
That's what I think is wrong.
Take out the battery and put it and the phone in a baggy in the freezer for 15 minutes, then put in the battery and turn on the phone. It should load WM6.5 before freezing again...
Click to expand...
Click to collapse
Thanks for the tips, but I got the phone for free and it was mean to be left alone somewhere on a desk. If the problem come again, I'll get a new phone. And I'm not ready to change a main board by myself, I have two left hand.
Maywiki said:
Ok, now I need an explanation. How the hell does this trick work ? I did what you said and now the phone works. What's the mystery behind this ?
Is it permanent or it will need to be done frequently ?
Thanks for the tips, but I got the phone for free and it was mean to be left alone somewhere on a desk. If the problem come again, I'll get a new phone. And I'm not ready to change a main board by myself, I have two left hand.
Click to expand...
Click to collapse
The trick works because your chip is overheating. This is a common HD2 problem. When you freeze the phone the chip cools enough to boot the OS, and it may run fine for a few minutes. Play a video or do anything that heats up the processor at all and it will reboot and get stuck on bootloader again. It is a hardware issue that can only be solved by one of the methods I mentioned above.
orangekid said:
The trick works because your chip is overheating. This is a common HD2 problem. When you freeze the phone the chip cools enough to boot the OS, and it may run fine for a few minutes. Play a video or do anything that heats up the processor at all and it will reboot and get stuck on bootloader again. It is a hardware issue that can only be solved by one of the methods I mentioned above.
Click to expand...
Click to collapse
Yep you're right, it can't stand a video. Thank you anyway :good: