Database Users

Blackstone Busted?

Guys,
I have an interesting issue that I hope someone can help me resolve. I recently upgraded the rom on my blackstone, and it appeared sucessfull, at first. A few hours later, it looked like the phone had done its normal "screen blank" from non use, however, i could not get the display to return.
I have done everything I can think of to recover from this - removed the battery for DAYS at a time, replaced the battery with a new one, etc..
If I power up the phone, I can use the pocket Controller-Pro s/w to see the device, but i can not see the display on the device itself.
I think I need to restore the FACTORY boot loader and rom, but I am having problems finding a method.
Any Advice?

Beltic said:
Guys,
I have an interesting issue that I hope someone can help me resolve. I recently upgraded the rom on my blackstone, and it appeared sucessfull, at first. A few hours later, it looked like the phone had done its normal "screen blank" from non use, however, i could not get the display to return.
I have done everything I can think of to recover from this - removed the battery for DAYS at a time, replaced the battery with a new one, etc..
If I power up the phone, I can use the pocket Controller-Pro s/w to see the device, but i can not see the display on the device itself.
I think I need to restore the FACTORY boot loader and rom, but I am having problems finding a method.
Any Advice?
Click to expand...
Click to collapse
Personally I would try and get it into bootloader and flash back stock rom, but as you only have a black screen you can only guess its in bootloader. Either turn on device whilst holding vol down or let phone boot up and use SSPL-Manual-TouchHD.exe to force it into bootloader. Then restore stock SPL and stock rom. When phone is connected to pc via usb you'll know it's flashing by watching flash % on pc screen

Fallen Spartan said:
Personally I would try and get it into bootloader and flash back stock rom, but as you only have a black screen you can only guess its in bootloader. Either turn on device whilst holding vol down or let phone boot up and use SSPL-Manual-TouchHD.exe to force it into bootloader. Then restore stock SPL and stock rom. When phone is connected to pc via usb you'll know it's flashing by watching flash % on pc screen
Click to expand...
Click to collapse
Thanks. Does anyone remember/have a link to the "factory" spl? I have the stock rom for the phone, but im not sure about the spl.

Kind of a noob question but, does SSPL-Manual-TouchHD.exe work with other versions of HTC phones? I ask because while I have a Jade clone, I will soon be upgrading to a Blackstone clone.

Beltic said:
Thanks. Does anyone remember/have a link to the "factory" spl? I have the stock rom for the phone, but im not sure about the spl.
Click to expand...
Click to collapse
You don't actually need to go back to original SPL, just to a stock one, i.e. latest 1.54.0000 would suffice
Read bottom of first post in this thread. Stock SPL's can also be found in first post

Uh oh, HD2 might be bricked/broken?

Hi all,
Hoping someone can help!
OK, first of all I'll admit quite openly that my knowledge of flashing and so on isn't what you'd call strong so any accusations of being a n00b are warranted and accepted.
I got my HD2 in Jan and I'd flashed a few handsets before without issue so flashed the HD2 pretty much straight away and played with some ROM's and so on and settled on one (from memory Dutty ROM) and everything was fine, the phone was stable and everything was good.
Then 2 weeks the handset started acting oddly. I hadn't changed anything (as far as I'm aware) but the phone starting freezing, restarting and so on. I'd have to take the battery out to restart it (and sometimes leaving the battery out for a while before it'd boot up.) When it froze the area around the bottom of the battery would also warm up. I'd also notice that if I tried doing something on the handset it would restart - almost as if I was putting to much "strain" on the handset and it went *bang*.
I decided to hard reset the phone and it went back to original form. Now, I'll again admit this is probably down to my lack of knowledge, I assumed this put the handset back to a factory state but this is probably not the case (it certainly looked like it but some signs suggested it hadn't).
This seemed to improve things a little but the problems just came back. As I'd flashed it and put on the HSPL I thought the warranty was now invalid so thought I'd try and "fix" it myself.
Big mistake.
Or was it?
I think the phone has an issue with power or something like that as it freezes as I've said. And it did this while I was trying to flash a ROM. Panic then set in.
Basically my handset is now in a state where it'll boot into the bootloader (power and Vol down) three colour splash screen and it'll do the white HTC "normal" boot up screen but nothing else.
I can connect to the handset via RUU and I can run:
Task 29
however this doesn't run and finish gracefully most of the time. It'll stick on 99% or 100% or sometimes it'll moan about not being able to do this on this handset.
Any ROM I now try to flash on it using the exe's or RUU (I've not tried them all, granted!) starts and stick at a certain percentage. The Artemis ROM sticks at 12%, Official 1.43 WWE ROM sticks at 0% and Leon ROM sticks at 9%. Eventually they'll time out with an error. Unfortunately I left the handset at work so cannot state which error(s) I get when trying to flash a ROM.
So, after boring the hell out of you, is the handset terminally ill in your opinion? I really do think that there could be a faulty power button/general power issue with the handset (just a feeling I've got) but from my brief reading I'm not 100% sure.
Is there anything I could do? At the moment it's completely unusable so any suggestions on getting it into a working state? Ideally I'd like to get it into a state where I could return it to O2 UK and not have them flag the fact it's been flashed.
Any help gratefully received!

can you get into bootloader? if so, check the spl.
if it is 1.42.0000 or 1.66.0000 then the warranty is fine.
if the spl ends .hspl then connect to usb and run hspl 2.
choose whatever was your stock spl (one that ends 0000, 1.42.0000 most likely)
reboot to boot loader, and confirm the spl ends 0000 and you will be fine.

have same problem!
my hd2 freezed on startup screan, boot screan, sometime donot start - only black screan, after rom flash 99percent or 100percet once freezed when i return stock rom and spl,sometime dont want to boot with 1.42hspl, next time with 1.66, but my experinece is :
1.
-with 2.08hspl allways start
-uninstal your hd2 driver on your computer! restart your computer install after that, with windows update,
-same with bootloader mode, uninsta, driver on your computer,restart your comp, and install it
-turn off your antivirus protector when install any rom, and your run as administrator in windows 7,vista.
2. use other pc if this dont help
3. the problam can be with battery pins under cover.
some people write there with pins problem, they have screaved pins and hd2 dont want boot or start or have same problems
its my secondary problem
if u want u can use clasical gum ereaser and lightly clean pins and battery conectors...
its help for better contact
donot take the pins with wet hands!!
its can make litle corosi..
i belive its help to you
sorry for my english

lol its come to me on twitter
http://wmpoweruser.com/?p=16952

samsamuel said:
can you get into bootloader? if so, check the spl.
if it is 1.42.0000 or 1.66.0000 then the warranty is fine.
if the spl ends .hspl then connect to usb and run hspl 2.
choose whatever was your stock spl (one that ends 0000, 1.42.0000 most likely)
reboot to boot loader, and confirm the spl ends 0000 and you will be fine.
Click to expand...
Click to collapse
Samsamuel, you're an utter *star*.
Now back to 1.42.0000. I can blag O2 now if needs be in regards to the handset (tried upgrading to 1.72, USB cable came out, phones shagged, give me a new one, etc) without them getting funny about it if needs be.
Will try upgrading to 1.72 stock O2 ROM and see what happens.
Thanks again Samsamuel, I owe you a pint!

I have the exact same problem.
The screen freezes for a while, and then the device reboots.
Usually it's stuck on the white (with green "HTC") screen after that, the red text doesn't show up.
If I remove the battery and leave the device alone for a while (cool down?) it boots past the white screen (although it's highly likely that it crashes again when I enter my pin).
At first this was only happening when I was watching some video's with coreplayer, but now it's just happening all the time, even when it's in my pocket.
I just finished flashing a stock rom, but it's even worse now
9 out of 10 times it doesn't even make it to the pin screen, and I have spend about 2 minutes total actually in windows mobile.

Brood, it sounds like your issue is hardware related, I would contact htc too look into getting it repaired.

Just an update from OP.
Thanks for the link ilijan, very interesting.
I spoke to O2 business tech support yesterday and deliberately asked whether anyone else was complaining of this issue. They said no but I'm unsure whether I believe them and whether this was just the corporate line.
After setting my SPL back to 1.42.0000 I tried flashing to 1.72 stock and this did work. Every other ROM I tried wouldn't work. Even with the official ROM it's still freezing/restarting.
Getting a refurb today.
Thanks to all that responded/helped. Appreciated.

[Q] Bricked phone after task29 and rom flashing

Hello. First I want to thank all of you who develop roms and the like. I have had such a blast over the past month and a half customizing my phone in ways I never thought possible. Last night I ran flashaholicruu.exe on my HTC HD2 Leo. The task29 seemed to work properly, however when I attempted to flash the rom I received errors. I tried Leo_Radio_2.11.50.26.sfx, which had previously worked on my phone. It stopped at 96%. I did the recovery, however the phone now will not even boot the splash screen. It simply vibrates non-stop when I turn it on until I remove the battery. Does anyone have ANY advice at all? Am I able to load a ROM onto the SD card and directly boot from it while my phone is in this state?
I have removed the battery and reinserted it. Did not work.
I have also tried pressing the volume buttons and the power on button to get the bootloader, but just vibrates in the same manner as when I press on button.
Please help!
Thank you

happend to me with a friends phone...i jus replaced it under insurance

Nismo300zx said:
happend to me with a friends phone...i jus replaced it under insurance
Click to expand...
Click to collapse
Ahh. I wish. T-Mobile is giving me a hard time about replacing it because I was not the original owner of the phone. The phone is only about 3-4 months old though.

I had this happen to me.
Try to load it directly into bootloader by holding vol-down when you press power button, then flash another radio (i recommend 2.12.5) then try another ROM thru RUU.
Also, make sure your battery is place in there securely and that all 3 pins from the phone are sticking out.
I had a situation where one of the pins was sticking vertically and the battery was only hitting 2 (from doing too many battery pulls) and it did this weird vibrate splash screen boot sequence.

electrokitten said:
Ahh. I wish. T-Mobile is giving me a hard time about replacing it because I was not the original owner of the phone. The phone is only about 3-4 months old though.
Click to expand...
Click to collapse
You'll need contact details for the original owner, but by law they have to honor the agreement they put in place with them, regardless of whether you are that person or not.
Just get back onto T-Mobile and if they say no then speak to someone higher up. I know this to be the case after selling a palm pre to someone at the beginning of the year and it died on him shortly after.

johncmolyneux said:
You'll need contact details for the original owner, but by law they have to honor the agreement they put in place with them, regardless of whether you are that person or not.
Just get back onto T-Mobile and if they say no then speak to someone higher up. I know this to be the case after selling a palm pre to someone at the beginning of the year and it died on him shortly after.
Click to expand...
Click to collapse
Really? This is good to know. I contacted the original owner. I feel so bad and I hope he doesn't think I am trying to scam him. I just want a working phone and I think that T-Mobile should honor that.

orangekid said:
I had this happen to me.
Try to load it directly into bootloader by holding vol-down when you press power button, then flash another radio (i recommend 2.12.5) then try another ROM thru RUU.
Click to expand...
Click to collapse
I think the bootloader may be gone. Does the task29 remove this? I can't get even to the bootloader using the method above (I have tried many times).
orangekid said:
Also, make sure your battery is place in there securely and that all 3 pins from the phone are sticking out.
I had a situation where one of the pins was sticking vertically and the battery was only hitting 2 (from doing too many battery pulls) and it did this weird vibrate splash screen boot sequence.
Click to expand...
Click to collapse
Good to know, I will try this. I do have some bent pins.

No task 29 doesn't remove the bootloader, I always use it before flashing a new ROM...
Sent from my HTC HD2 using XDA App

copy the nbh file from the stock rom to the sd card..that usually fix it..

gabbs said:
copy the nbh file from the stock rom to the sd card..that usually fix it..
Click to expand...
Click to collapse
Good advice... Now if only he could access the bootloader he'd be sorted

gabbs said:
copy the nbh file from the stock rom to the sd card..that usually fix it..
Click to expand...
Click to collapse
Major_Sarcasm said:
Good advice... Now if only he could access the bootloader he'd be sorted
Click to expand...
Click to collapse
he needs to rename the .nbh file to LEOIMG.nbh and pair it with the RUU that came
with that same stock ROM
but then again, if he cant get into bootloader, the phone is definitely bricked

electrokitten said:
Hello. First I want to thank all of you who develop roms and the like. I have had such a blast over the past month and a half customizing my phone in ways I never thought possible. Last night I ran flashaholicruu.exe on my HTC HD2 Leo. The task29 seemed to work properly, however when I attempted to flash the rom I received errors. I tried Leo_Radio_2.11.50.26.sfx, which had previously worked on my phone. It stopped at 96%. I did the recovery, however the phone now will not even boot the splash screen. It simply vibrates non-stop when I turn it on until I remove the battery. Does anyone have ANY advice at all? Am I able to load a ROM onto the SD card and directly boot from it while my phone is in this state?
I have removed the battery and reinserted it. Did not work.
I have also tried pressing the volume buttons and the power on button to get the bootloader, but just vibrates in the same manner as when I press on button.
Please help!
Thank you
Click to expand...
Click to collapse
What exactly did you do to try and enter bootloader mode? You said you pressed the volume 'buttons' and the power button but that combination would initiate a Hard Reset and not bootloader mode..
How to get into your Bootloader
1. Turn your phone off
2. Press and hold the VOLUME DOWN then Press and hold the POWER button. After about 3 seconds the tri-coloured screen should appear.
3. To exit Bootloader you need to remove your back cover and pull the battery out for a few seconds, then replace it and press the power button to reboot your phone.
If you cannot get into the bootloader with the above instructions then it looks like you have bricked your device somehow but im not sure exactly how you could do it as task29 doesnt touch HardSPL.
If you can get into bootloader then you can flash a rom back to your device using the sd card method in my guide *HERE*.
Mark.

[Q] Help!

Hey guys,
Sorry to be a burden but I'm having a few issues with my hd2, and being a noob I didn't really know where to turn except this forum.
Basically my dad bought the hd2 from the UAE early this year and it all worked fine on stock settings for about 6 months. In the last few months, however, the phone started to lock up, and it got to the point where it wouldn't even boot properly.
In an effort to fix the problem I went with a hard factory restore, however, this seems to have caused more problems as now the phone is stuck in the bootloader.
I've been searching for hours, and have come to the conclusion that I need to update the flash? and then possibly install a new rom on the phone?
My major issue in doing this though, is that I can't seem to connect to activesync while the phone is in the bootloader.
Please help me sort this out.

First of all lets make sure that your trying perform the hard reset correctly.......
You need to hold down both volume buttons whilst the phone is turned off..... Then tap the power button and keep the buttons held down.......
Release them when you see the confirmation screen.........
Powering on while holding only the vol down button will take you to bootloader....
If you need to reflash the device then have a read of this thread here....
If its a "Tmous" HD2 (green and red call/hangup buttons) then you need to read this one
When connecting to the pc in bootloader you should see the word "serial" at the bottom of the screen change to "USB".......
Might be worth checking the text on you bootloader screen for any irregular looking characters, there have a few cases of people with corrupt bootloaders, usually these will display odd looking characters at the top. This is quite rare though.
If you want to flash another stock rom then you wont need to worry about HSPL just download the appropriate ROM and follow the instructions on screen.
Start off at the HTC site and input your serial number to see which ROM is suitable for your device.....
If none of that helps then hold out for some advice here from someone with better knowledge of these things.....

Ok well I've just tried to do the hard reset in the way you've described and had no response from the phone. I had to remove the battery from the back to actually power down the thing as nothing else seemed to work. I can't actually seem to start it up again now =S
Thanks for all the info, I'll keep trying to get it started. I'm downloading the stock rom from the htc site. Hopefully I will find a way to install that.
Also, when the bootloader was up, there weren't any odd characters that I could see. It all seemed pretty standard. It had the current rom driver which was 1.42 or something and a few other lines of info.
Thanks for the post.
edit: perhaps the battery is dead?

No problem.
Is it charging when plugged in and turned off?
If so let it charge while turned off for a while and then try to boot........
If you cant get to bootloader and establish a USB connection then you could try flashing the ROM from the SD card.
rename the rom to "LEOIMG.nbh" place it on the root of a freshly formatted (fat32) sd card and turn on the phone holding vol down..

conantroutman said:
No problem.
Is it charging when plugged in and turned off?
If so let it charge while turned off for a while and then try to boot........
If you cant get to bootloader and establish a USB connection then you could try flashing the ROM from the SD card.
rename the rom to "LEOIMG.nbh" place it on the root of a freshly formatted (fat32) sd card and turn on the phone holding vol down..
Click to expand...
Click to collapse
To be honest I have no idea if it is charging whilst turned off =S All I get is the bootloader when it decided to turn on and that gives no indication of power level so I really have no idea. It makes updating a rom pretty scary haha.
So I just attempted to install the default rom from teh htc site, but failed due to the lack of activesync. It was strange though because the updater managed to change the screen on the phone and get to 1%. It then crashed and I had to go through this recovery process.
I will have to try this SD card process I guess. Could you perhaps link me to a more in depth guide to how to do this?
Thanks a lot for your help I really appreciate it.

you should get a red light up near the earpiece to indicate that its charging........
try this video for flashing from sd card......

I am not getting a red light flashing? But it doesn't seem to be running out of charge. I'm still having lots of trouble
It would seem that I need to install this hspl before I do anything, however, I can't install that if I can only access the bootloader screen. Does this mean my phone is bricked?
I want to be able to set up a rom straight from SD, however, I have no idea where to start. That video just seems to send me in a big loop.
Perhaps you could link me to a simple rom that I can attempt to load via sd card?
edit:
I seem to have somehow fluked an install of HSPL 8G XE.
I have no idea how this happened or whether it is good or bad.. but at least something has happened.

Hmmm
installing hspl is covered here
as long as the word "serial" is changing to "USB" on the bootloader screen when you connect to the computer you should be ok.......
You dont need HSPL to flash via sd card but I think that video was directed more towards people installing cooked ROMS from XDA.
Installing a stock rom will automatically overwrite HSPL so unless your planning to flash a custom ROM then installing HSPL is pointless........
You might be better off installing a cooked rom. (Artemis, Dutty's)
They tend to run better than stock, if you get one running then it will be easier to get back to a stock rom (if you want to) than the situation your in now.....
This is from the flashing guide;
Flashing Via MicroSD Card
NOTE (PLEASE READ): If you flash a Stock Rom via microSD Card then it will overwrite your HardSPL with a stock SPL included in the nbh file. This does not apply to custom roms as they do not include an SPL. BE CAREFUL!!
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the LEO Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to LEOIMG.nbh
4. Copy the LEOIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Reset the device while pressing the volume down button to enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.

Reckon you could link me to one of those roms? I think we're getting pretty close now.
Your help has been great I can't thank you enough.

Your welcome
You can find Dutty's ROM here
or the Artemis ROM here
Have a quick read and see which one you think you'll prefer, to be honest I think they're both pretty similar to stock but with a lot of the crap taken out....
Just follow the steps in the first link I posted and you should be good to go.

Ok new problems.. Can you believe it.
I seem to have tried everything.
Basically I can install of a sd card, but when it gets to the end of the install and I restart instead of booting into a OS it boots to the tri colour screen, and starts the install process again.
Also, I have attempted to install via usb and have had varying success.
As I have already said, I am able to install hspl, however, when I try to flash I get to varying percentages below 30% before the whole thing freezes.
I now have an error that says Upgrade Rom code error Please Try Again.

Sorry i dont mean to hijack ! but will any of you be kind enough to help me here..
http://forum.xda-developers.com/showthread.php?t=879980
thanks !

Ok so I followed the steps and still to no avail.
I am able to boot using the sd card method, however, the same problem occurs with each rom version. Basically as soon as I reset the device it pretty much switches itself off, then I can't turn it back on, once I finally do turn it on, it restarts the process like it never happened.
The other issue is again the active sync problem.
With most of the the usb connections I am able to connect and get a little way through the install (most I've got is 15%) then it just freezes up and I get the 262 error

Your best bet is to try flashing with a freshly formatted (FAT32) 4gb, class 2 card.
I know, sounds pretty specific right?
You wouldn't think it would matter?
I have tried flashing with 16 gb class 2, failed at the radio step
Tried with a 8 gb class 6, failed at the radio
4 gb, class 2, flashed successfully.
Seems our HD2's are picky about what cards they'll take a ROM from for some reason.

Alright I'll try that, my next issue is which is the stock rom for the phone =S
It was bought in the UAE and I'm currently in Australia.
edit: Also I read somewhere that the constant bootloader screen can be caused by a bent battery pin?
Edit2: I have attempted to do that, however, now the bootloader will accept the card, then just sit on loading...
I'm pretty sure this thing is bricked.

tombm said:
Alright I'll try that, my next issue is which is the stock rom for the phone =S
It was bought in the UAE and I'm currently in Australia.
edit: Also I read somewhere that the constant bootloader screen can be caused by a bent battery pin?
Click to expand...
Click to collapse
I've heard of bent battery pins being a pretty common problem, causing usually just the phone not to charge properly. I've personally never heard of it causing constant bootloader, but it's definitely worth checking.
It's weird that it's such a common problem, my usb/charging port is broken, so I have to use an external charger. I change my battery on average twice every 24 hrs, and I've never bent a pin

Ok, new info, apparently because the device is for the middle east it does not support stock 3.14 roms. What does this mean for me? Am I bricked.
http://forum.xda-developers.com/showpost.php?p=9614007&postcount=30954
Click to expand...
Click to collapse
That's the post I found the info in. All of that info matches up to mine except my original image was 3.142 I think =S

Firstly, your phone is not bricked - a bricked phone is responsive as a brick.
Can we start from the begining?
What does the Bootloader Moder screen say (with and without the USB cable connected)?
What ROM (and if custom ROM, what RADIO) have you flashed and are trying to flash?

fred_up said:
Firstly, your phone is not bricked - a bricked phone is responsive as a brick.
Can we start from the begining?
What does the Bootloader Moder screen say (with and without the USB cable connected)?
What ROM (and if custom ROM, what RADIO) have you flashed and are trying to flash?
Click to expand...
Click to collapse
Alright from the beginning.
Basically about a month into using the phone in Australia it became very unresponsive to the point where it would not boot at all. We left the phone for a couple of months, however, after seeing a friend rom android I decided maybe it was time to attempt to fix this phone.
Some more info:
When I attempt to do any sort of ROM update there is nothing in the 'current image' part so for example it will say update to Dutty 3.6 but it's updating from nothing, does this mean there's no firmware there?
In the bootloader I have:
PB81100 HX-BC
SPL-2.08.0000 8G XE
MICROP(LED) 0X05
MICROP(TOUCH) 0X40
Without USB cable in I get Serial in the white part down the bottom, with the USB cable in + plugged into computer I get USB.
Just to further clarify. In regards to the ROM I have installed. I simply don't have anything installed. There is a bootloader, no image, no bootup. It boots up to the tri colour, that's it.

For a moment we will forget about going to 3.14 ROM: I don't know if that phone is entitled to an official upgrade to 3.14, if it is locked to a particular network, if it is branded, etc. If it is not entitled to a 3.14 ROM upgrade then you will have to go through GoldCarding, so we will leave it for now.
Make sure that the battery has had a good couple of hours charge in the charger or double that if connected to the computer.
Remove SIM Card and SD Card.
Switch on to Bootloader Mode, then connect to USB.
Download and run HSPL2 - ignore the instruction about connecting to ActiveSync etc, just proceed.
Download and install the HTC 1.66 WWE ROM - again, ignore the instructions, just proceed.
The reason for HSPL is because your phone may be operator locked (not SIM locked) and you aren't entitled to run the 1.66 WWE ROM.

[Q] Stuck at bootloader at boot

Hi
A friend of mine has a HD2, never HSPL or anything and still running on 1.42 rom.... Now everytime it boots it goes straight into the bootloader. Since its never been messed around with I find it odd, seen it before with people with other phones. Would this just be a corrupted ROM and therefore it goes there, would if poss a stock rom flash be able to restore the phone, if that is not the case then a warranty return is still valid, but obv not wanted.
What do you think, will this work? I did search but everyone's posts come up with I task 29 and now stuck... etc and not from a stock bootloader as well!
Cheers any help will be appreciated, my first thing I will get him to try is a rom reflash but that will be tonight, I'll update on the progress then!

First thing I would check is if his volume button is stuck for some reason. Second would be to see if it detects a USB connection, then hard spl and new rom from that point. Keep us posted.
Sent from my GT-P1000 using XDA App

chris10230 said:
Hi
A friend of mine has a HD2, never HSPL or anything and still running on 1.42 rom.... Now everytime it boots it goes straight into the bootloader. Since its never been messed around with I find it odd, seen it before with people with other phones. Would this just be a corrupted ROM and therefore it goes there, would if poss a stock rom flash be able to restore the phone, if that is not the case then a warranty return is still valid, but obv not wanted.
What do you think, will this work? I did search but everyone's posts come up with I task 29 and now stuck... etc and not from a stock bootloader as well!
Cheers any help will be appreciated, my first thing I will get him to try is a rom reflash but that will be tonight, I'll update on the progress then!
Click to expand...
Click to collapse
The post above me is correct check and make sure the volume down button is not stuck/Hung in the down position. If it is stuck in the down position like it is being held down at boot then this is the cause of it going straight to bootloader at boot up. If there is no problem with the volume down button then try a hard reset of the HD2. Warning this will reset your friends HD2 tolike it was fresh out the box so any photos, videos, documents, and etc that is not on the SD card they will lose. Also any contacts that are not backed up withan app like Microsoft My Phone will be lost. To do the reset while the HD2 is off bold the volume up and the volume down buttons down and press and bold the power button down. When you see the tri color screen come up release the volume and power buttons and follow the instructions on the screen (hint: you will want to press the vume up button). Now if after the Hard reset your friends HD2 still goes to bootloader at boot up then download and flash the stock ROM for their HD2 you can find it on HTC.com but make sure you varifiy that it is for their HD2 by entering the serial number of their HD2 you can find the serial number look under the battery. To flash the ROM let the HD2 boot up to the bootloader and then connect it to the computer via USB cable and wait for the Serial in the white bar of the boooader screen to change to USB and for your computer to show it recognize the pbone and then run the .exe or RUU wich everone the ROM has.

Never thought of the key being held done will try that first.
Also I won't HSPL'ing as its in warranty and a half HSPL'ed phone is well useless

OK so i feel like a bit of an idiot for this one. Turns out what I call a bootloader and he does is totally different. For me Its the tri-colour screen, for him its the red/orange windows boot screen. So it was all solved by a HR. Great..
Sorry for those who offered the advice but it really was not needed. but solid advice it was, you always can rely on help in here