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.
I think it's taken a knock and now it won't boot. I just get a white screen. If I try a hard reset it gives me the text that I'll wipe all personal settings etc.
I've flashed to a duttys ROM and a 2.x.50.x radio and I'm on O2. Is there any way I can fix this as I'm guessing the ROm update voided the warrenty. As the Hard reset shows text I can see something is working but even plugging it into my PC via USB gets no response.
If anyone can help it would be a major relief.
Let it do the hard reset and see what happens. So you'll lose what ever MMS/SMS you didn't delete, the programs you have loaded since putting the ROM on, etc etc. Your not going to lose all your numbers unless they are stored on the actual phone and not the SIM card.
You could try doing a task29 on it and see if that helps. As for the warranty being voided it just depends on whether or not it can be wiped and loading with a OEM ROM back onto it with the correct HSPL before sending it back. You haven't bricked it if you can get into bootloader or hard reset.
I have tried the hard reset but no joy. It runs the reset but then on boot back to white screen. I'm not fussed about the contacts etc as it's all backed up. Have removed the SD card too.
Do a task29 on it. Flash a new radio and ROM(would suggest OEM) and then get back to us. Worst case something got knocked loose inside and it needs to go to HTC for repair.
craigpyro said:
I have tried the hard reset but no joy. It runs the reset but then on boot back to white screen. I'm not fussed about the contacts etc as it's all backed up. Have removed the SD card too.
Click to expand...
Click to collapse
i've encountered this lately for some strange reason ( being a flash junky) but found my way out of it.
flash your stock ROM via sdcard method, this will reset the spl to the original. (you can easily flash hspl anyway afterwards when you tire of the stock rom).
Ignore my post below. Have drained the battery overnight and this morning have been able to boot to:
PB81100 HX-BC
SPl-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
SERIAL
From here I'm hopeful I can do something.
_______________________________________________________________________________________________________
Sorry guys - but I don't understand how I am meant to do a task29 or ROM via SD card method when I cannot link by USB/ActiveSync or see anything on the screen.
craigpyro said:
....
Sorry guys - but I don't understand how I am meant to do a task29 or ROM via SD card method when I cannot link by USB/ActiveSync or see anything on the screen.
Click to expand...
Click to collapse
The microSD method does not require your phone to connect to the computer.
Here from the newbie guide to flashing a ROM:
Download a shipped Rom from *HERE*
- Rename the extension to .zip
- open it with winzip and extract the RUU_signed.nbh file to a folder
- Rename it to LEOIMG.nbh and copy it to the root of a microSD card thats been formatted to FAT32
- Insert your storage card into your phone
- Enter Bootloader and follow onscreen instructions to flash
This flashes your phone back to warranty status - it replaces the HardSPL, the ROM and the Radio.
Once your phone is repaired, you can always HardSPL your phone again.
I've tried using the HSPL tool to re-install back to 1.41 and other SPLs. The application says it's successful but when I restart the bootloader still reads:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
have tried Flashing ROMs and running Task29. Everytime the Bootloader switches to the updating progress bar then crashes out to Error [262].
I dont have a card reader to try from the SD card but even if I did I'm starting to feel doubtful.
are you sure, that the radio is compatible with the rom?
i'm pretty sure its the same fail.
DN41
OK - booting from FAT32 formatted microSD.
Stock ROM failed
Radio_2.08.50.05 failed
maybe a corrupt image file ? try downloading another one and see if that helps
I've tried 2 images. They get to different points at the radio install then fail. Try to get another img.
Starting to despair a little now. Trying to get just the radio on to start with.
This radio installs up to 100% (instead of about 20%) then reads:
00018003
LEOIMG.nbh - FAIL
Radio_V2Fail
Update Terminate
UPDATE FAIL
I really am getting desperate now having spent almost all day working on this.
Try using the supplied 2GB microSD card that came with the phone. Sometimes there are problems with using larger cards.
Thanks for the idea however I'm using a spare 1GB.
Silly question, but it is an O2 original ROM (assuming that is what your phone originally had on it) you downloaded and are flashing and not an HTC stock ROM (ie 1.66 WWE)?
I have tried both.
I am on the same issue here. Have read almost anything i could find to fix this. Am able to change spl through hspl2 successfully but showing the same spl 1.42 hspl in bootloader. The thing is only unable to flash radio. I can flash a custom rom with sd card but after flashing when it boot up only a white screen is showing. When i try to install a official stock rom it shows that the radio v2 not installed successfully. So its probably radio problem. Hope some one could help us fix this. I tried installing a radio with the sd card and still gets the radio v2 fail. Tried installing custom rom and radio with the usb but doest go beyond 0% and error shown in the pc. HELP HELP HELP
craigpyro said:
Starting to despair a little now. Trying to get just the radio on to start with.
This radio installs up to 100% (instead of about 20%) then reads:
00018003
LEOIMG.nbh - FAIL
Radio_V2Fail
Update Terminate
UPDATE FAIL
I really am getting desperate now having spent almost all day working on this.
Click to expand...
Click to collapse
With the steps I describe here I was able to recover the device.
http://forum.xda-developers.com/showthread.php?t=668347
But only if you follow the exact steps!
I tried many stock roms first and all were stuck on the radio.
Only the method I describe worked for me.
Good luck.
for you guys across the pond, don't you have to flash a .51 radio, not a .50 that you were using for the custom ROMs?
I've been hacking/modding/flashing for years with numerous devices and have never been this far down this path...I searched around and haven't found an answer or the same situation so I'm sorry if I overlooked a similar thread.
I've been running WP7 on my HD2 for a few months after running Android from the SD and NAND for a few months before that. Yesterday my touchscreen started getting VERY difficult to use, with it being both innacurate and unresponsive. It got progressively worse so this morning I reflashed the WP7 ROM without any problems. Even after that it continued getting worse to the point where the phone was unusable because the touchscreen would not respond to anything so I couldn't unlock the phone. The hardware keys worked fine. So I decided I would try to go back to WM6.5 in an attempt to isolate whether it was software or hardware. I'm on my work computer so it doesn't have the proper drivers for flashing, so I formated my SD card, put a TMO-US WM6.5 build on the root of the card, renamed it LEOIMG.nbh and put it back in.
I booted to the tri-color screen, pressed power to confirm the flash. It flashed the progress bar and then went to the loading screen. It stayed there for around 30 minutes so I pulled the battery out and attempted to try again, but then a screen comes up for a half second that says "Software update Failed! Please Try Again" and then it goes back to the loading screen. If I try to go back to the Tri-color screen it shows it for a second and says "ROM code error Please try again" then returns to the loading screen. Anybody have any advice? Anybody seen this before?
Got a full filename for the rom you flashed?
In bootloader what's the full spl line say?
What size SD card? The stock tmous one?
wow.. unless some how the flash to wm conflicted with magldr that should had worked...
When you start the phone holding down the volume key... Do you have the SDcard still in it and it just kicks you out of the bootloader? Technically ad long as the boot loader shows up it should be fixable but it kicks you out.. that a problem
samsamuel said:
Got a full filename for the rom you flashed?
In bootloader what's the full spl line say?
What size SD card? The stock tmous one?
Click to expand...
Click to collapse
This is the ROM I was flashing on the SD:
RUU_Leo_1_5_TMOUS_2.10.531.1_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.zip
I got it from here:
http://forum.xda-developers.com/showthread.php?t=655653
The bootloader says 2.08.0000 then MicroP something. It just flashes so it is hard to read too fast.
I am using an 8GB Class 4 card. I also tried it with the stock 16GB one but it did the same thing. When I tried flashing it, however, it was the 8GB card.
hakuchi18v said:
wow.. unless some how the flash to wm conflicted with magldr that should had worked...
When you start the phone holding down the volume key... Do you have the SDcard still in it and it just kicks you out of the bootloader? Technically ad long as the boot loader shows up it should be fixable but it kicks you out.. that a problem
Click to expand...
Click to collapse
That's what I'm gathering as well. In my experience I've never been afraid of bricking because I've always been able to get to the bootloader. In this case, I can get to it, but it won't let me stay in it.
I finally got the phone to stay in bootloader mode, however when I try to flash any ROM, whether Task29, radio, stock, or cooked 6.5 it goes through the ROM Update Utility steps and then it stops at 0% for a few minutes before giving me an update communication error. This is what the Bootloader says:
PB81120 SS-B3
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
Upgrade ROM code error
Please Try Again
Thanks again for the help.
YOU donT have HSPL... Thats why flashing a cooked rom isnt working aswell ad everything else... flash a stock rom to get it up and running
Sent from my HTC HD2 using XDA App
Yep, there's the problem. Any spl ending. 0000 is stock, you have 2.08.0000, you actually need 2.08.hspl.
Don't feel too silly though, its the most basic error there is, but still turns up daily.
When you flash a stock Rom from the SDCard it removes the HSPL... So you can try flashing a Stock ROM to see if the screen issues continue or put HSPL back on and flash something to it
also, what size is your SD card? Quite often, SD Cards over 2GB in size fail for rom updates via the SD Card method.
You could also go here: http://psas.revskills.de/?q=node/ and download the free version.
Run The program and select:
Menu-Hardware forensics-WINCE SD Utils and get your card serial number. (needs a windows mobile phone connected via activesync to the pc (with the card in it) to work though)'
Once you get the code, PM it to me and I will make a goldcard.img for you.
That way you can flash any rom without having hspl on the phone.
Again, this will only work with a card under 4gb. 1 or 2gb is recommended.
Andy
Hi folks,
I have a T-Mobile branded HD2 that gets stuck on bootscreen. Since this one is owned by the company I work for I should not flash custom ROMs or whatever. I got it from a colleague with this error.
What I did is downloading the latest official ROM from HTC with T-Mobile branding, extracted the .nbh file and stored it as LEOIMG.nbh on its SD card. I flashed the ROM, removed battery, put it back in and immediately did a hard reset. Still no luck it keeps stuck in the boot screen showing the ugly circle. No animation, no nothing.
Any ideas?
Regards,
Chris
What is the full name of the official ROM you got .and did I understand you correst you got it from the T-Mobile website? Also what does it say when you put it in BOOt loader?
Filename:
_HTC HD2_RUU_Leo_TMO_DE_1.72.111.4_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
Download from:
http://www.htc.com/de/supportdownloadlist.aspx?p_id=297&act=sd&cat=2
I am not sure what you mean with bootloader? VolDwn+Power?
PB1100 HX-BC
SPL-1.66.000 XE
MicroP(LED) 0x05
MicroP(Touch) 0x50
Let me know in case you need more details.
It gets even more weird...
I put the phone on charge (switched off). It suddenly switched itself on and then booted into windows. It came to the point where it asks for the PIN. I entered it and as soon as it accepted the code it rebooted again and is stuck on the same screen as ever.
Sorry I was changing my ROM, That is why it took a minute, Are you sure you have a T-Mobile HD2? Cause it says in the name of the ROM you posted that it has a 2.07.51.22 and that radio is deadly to a T-Mobile HD2.
Does it have a green send button and a red end button?
Also did you enter the serial number of your HD2 in the HTC site to verify that this ROM is for your HD2?
What you said about it rebooting when you plugged the charger in is weird.
I bought this HTC (and several others) all from T-Mobile, since we got some company agreement. When I first got it disfunctional it booted up with this circular bootscreen in T-Mobile colors. I personaly own a Desire HD, so I know about the uncustomized bootscreen.
This is T-Mobile for Germany, not UK or US. For the US version the radio won´t work since bands are different. I have heard about that...
This device does not have colored buttons.
Yes, I have entered the serial number on this site and it has been validated. Then I downloaded and unpacked it just the way it is described in this forum.
I also tried to download the original, latest, unbranded HTC ROM, but it did not validate my SN.
I have reformatted the original 2GB SD card with FAT32 and tried the same. After it says UPDATE SUCCESS it does nothing. Is this correct?
I took off the battery and after a couple of seconds back in, doing a hard reset. It then still got stuck on the bootscreen.
Ok do this download the Task 29 by ShaDrak from post #1 of the Task 29 thread here on XDA and run a Task 29 on the HD2 then download HSPL 4 (link in my sig) and flash HSPL 3.03. then try to flash your ROM again. If it flashes successfully then use the HSPL utility to reset y our correct SPL. I will have to go see if I can find the correct SPL for you if you don't know whioch one it is.
Thanks for your help, but I think I´ll rather return it for a new one then. This HD2 is for testing our mobile website, so one developer will need to wait a little longer for a replacement. This smartphone is 3 weeks old (half a week of use due to vacation), so I do not want to brick it and stick with it. Last time I did HSPL was with my old diamond, feels like a decade ago.
I am limited with downloads at my company due to firewall restrictions and I am not allowed to install programs. I am glad that I got USB allowed, though I am part of the admin crew
I´d even take it home, but I do not have windows running on any of my computers.
Ferrosti said:
I am not sure what you mean with bootloader? VolDwn+Power?
Click to expand...
Click to collapse
This is what I mean by bootloader, once you see the multicolor bootloader screen connect it to your computer via USB and wait for the Serial to change to USB and Right click the RUU for the ROM and run as administrator.
I understand you not wanting to brick it and your issue with downloads, that does suck. But the task 29 just does a wipe of the ROM partition of the NAND memory and reformats that partition. Task 29 is a very small download also, very very small, the same with HSPL 4. I suggested HSPL for as it will disable the CID check on the flash and allow you to flash a ROm that is not for that particular HD2. And all you have to do to revert back is run the HSPL again but pick the SPL not the HSPL you want, it ask you what version of HSPL or SPL you want to flash. Also you have a International HD2 and they are not as prone to bricking as the TMOUS because they can be flashed with any radio version for the HD2.
It comes to my mind that I have a damn old windows installation on my computer. Maybe I´ll give it a try at home over the weekend.
The phone does not even switch from serial to USB mode as you described. Could it be because there is no active sync installed? I tried it with my personal Desire HD and I got access to its SD card.
How do I find out which SPL to flash to have it back to its original state? Is it the 1.66.000 that was shown in bootloader? Where do I get it?
Go into the Bootloader and it should say the SPL version
Mines for example is
SPL-2.08.HSPL 8G XE
CotullaHSPL
If yours should say SPL-(version number) without the HSPL/Cotulla since it shouldnt have HSPL
If Windows has the drivers for the HD2 installed (Active Sync/Center installed) it will say USB as long as the plugs and the wire are good if it stays stuck on Serial that just means either the HD2 isn't detecting windows or Windows isn't detecting it
Ferrosti said:
It comes to my mind that I have a damn old windows installation on my computer. Maybe I´ll give it a try at home over the weekend.
The phone does not even switch from serial to USB mode as you described. Could it be because there is no active sync installed? I tried it with my personal Desire HD and I got access to its SD card.
How do I find out which SPL to flash to have it back to its original state? Is it the 1.66.000 that was shown in bootloader? Where do I get it?
Click to expand...
Click to collapse
Yes I think the SPL 1.66 is the SPL for the 1.72.111.4 ROM you are trying to flash. The phone is technically suppose to install the drivers when you connect it to a computer in bootloader, but I have had to download and install the ActiveSync and the Windows Mobile Device Center too to get a computer to recognize my HD2 in bootloader (two separate computers) so yes installing the latest ActiveSync on your computer can help as it has device USB drivers with it.
Dont install ANYTHING.
If the phone is only 3 weeks old, send the damned thing back for a replacement.
Had the same problem with a european t-Mobile HD2. Sometimes (rarely) let me boot into windows, but mostly didnt.
Sent it back to HTC and they fixed and returned it within a week. Actually they said on their site that they were fixing it, but I ended up with a new phone......
So... either return it to your supplier for replacement, or send it off to HTC
Andy
I don´t know how, but I got it running on the day we have been discussing.
If I only knew how it worked I´d let you know.
After all this I put it on the charger and retried a last time before I would have taken it home (read above). I flashed the new T-Mobile branded ROM and it just worked.
Thanks for your help!
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: