i used imcokemans unlocker (which i have done before) and blee0125's kitchen and really screwed up somewhere!
i cant get it past the "htc smart mobility" screen. it comes up, tells me the driver and radio versions, then those disappear like they are supposed to and...nothing else.
any suggestions would be great, plz im dying here!
i have tried hard and soft resetting and...nothing!
THANKS.
EDIT: just for those coming to this ancient and recently revived thread, this (my) problem has been solved. altho there are other people now with similar problems
Have you tried re-flashing?
jim256 said:
i used imcokemans unlocker (which i have done before) and blee0125's kitchen and really screwed up somewhere!
i cant get it past the "htc smart mobility" screen!! it comes up, tells me the driver and radio versions, then those disappear like they are supposed to and...nothing else.
can anybody help me???? PLZ im dying here!
i have tried hard and soft resetting and...nothing!
THANKS.
Click to expand...
Click to collapse
Do a camera power reset and try again.
i tried that and it didnt do anything at all. isnt that just where you hold the end key and the side camera key and stick the stylus into the hole?
if so, it have any different effect than the standard soft reset
AraqirG said:
Have you tried re-flashing?
Click to expand...
Click to collapse
and i did try...sort of. im not sure how to seeing as how i can never make it past the boot screen, and therefore cannot connect it to activesync.
THANKS.
jim256 said:
and i did try...sort of. im not sure how to seeing as how i can never make it past the boot screen, and therefore cannot connect it to activesync.
THANKS.
Click to expand...
Click to collapse
Hold down the power button and the camera button at the same time until the tri colored bootloader comes up. If that works, try flashing the stock rom for your carrier.
If that doesn't work try the same steps with the memory card removed.
If that doesn't work try to do a hard reset and see if that will take you to the bootloader.
Also, what are the numbers in on the bootloader...are you sure your device is unlocked? I believe it should say... SPL-00.40.coke... on the 2nd line if your unlocked.
You shouldn't need to connect to activesync to reboot. After you run ImCokeMan's unlocker you should be unlocked until you run it again.
As I said in the last post, all you have to do to get to the boot loader is hold down the power and camera buttons at the same time. This will put the phone into the boot loader and you should be able to flash back to the stock rom and start over.
It kind of sounds like you relocked the phone and then tried to boot a custom rom.
sorry i wasnt saying i needed to connect to activesync to reboot, i was saying i needed to connect to activesync to flash, and it wouldnt boot up so i couldnt get to activesync.
and i did to imcokemans unlocker, and everything went fine. when i was setting up the device (ie. setting password, time zone, calibration, etc...) i just decided that i didnt need to finish that as i was intending on flashing a custom rom anyway, and so any settings i put up the time to set would be erased.
having said that, i went ahead and starting flashing a custom rom right from the wm welcome screen that you get on a first boot.
thanks a LOT for your help, promptness, and attention
So are you back up and running?
well, now i am. i just took a 30 min drive down to the sprint store and got a replacement :S
thanks a lot for your help though, im scared i may really need to refer back to this thread later. but if i do, at least i know i should be able to fix it!
thanks.
well, i just did it again. i must be doing something wrong in the cooking of my ROMs...about to try out your solution..hope it works!!
wish me luck :S :S :S :S
well i was able to re-flash, but, unfortunately, it is stuck in the same "htc smart mobility" screen again. i think i have been able to narrow it down to the oemizer app. i must be doing something wrong in there.
oemizer http://forum.ppcgeeks.com/showthread.php?p=100746&referrerid=10115
ill keep cooking and trying tonight until i find what it is the problem is i guess, thx for your help guys. especially you 360discgolf.
well, after cooking and flashing too many times to remember this late, all i can do is ask for help when you guys wake up and check this thread.
in the last couple of builds i havent been doing anything with oemizer at all and it still hasnt been working, and i dont think i am doing anything extra in buildos that i havent done before in successful ROM images...it seems sort of erratic.
any suggestions/hints/comments would be great, thanks a lot.
you can't just hold the two buttons and press the reset. You have to hold the two buttons at the same time, then while holding them, use the stylus to hold the reset until it restarts. If you just tap the reset button while hold, it doesn't work.
360discgolf said:
You shouldn't need to connect to activesync to reboot. After you run ImCokeMan's unlocker you should be unlocked until you run it again.
As I said in the last post, all you have to do to get to the boot loader is hold down the power and camera buttons at the same time. This will put the phone into the boot loader and you should be able to flash back to the stock rom and start over.
It kind of sounds like you relocked the phone and then tried to boot a custom rom.
Click to expand...
Click to collapse
i'm having a similar problem. my attempt at flashing didn't go over that well and now when I turn off the device, I can't turn it on again unless I do a soft reset. I tried doing the power/camera thing but all it does is ask "are you sure, yada yada" and then the devices turns off. you were talking about a stock rom? where would I get one and how would I re-flash the rom (assuming that's the problem in the first place.).
Thanks!
vkolas said:
i'm having a similar problem. my attempt at flashing didn't go over that well and now when I turn off the device, I can't turn it on again unless I do a soft reset. I tried doing the power/camera thing but all it does is ask "are you sure, yada yada" and then the devices turns off. you were talking about a stock rom? where would I get one and how would I re-flash the rom (assuming that's the problem in the first place.).
Thanks!
Click to expand...
Click to collapse
what carrier are you?
EDIT: also:
1) what os version are you running? (build number)
2) what radio are you running?
3) what bootloader are you on? (can be accessed via holding power + camera button and poking reset hole)
4) what are the orange numbers in the very bottom right of the screen when you are booting up?
these kinds of things all need to kind of jive for the sleep function to work correctly
jim256 said:
i used imcokemans unlocker (which i have done before) ...
Click to expand...
Click to collapse
If you used the imcokemans unlocker a 2nd time, I believe you re-lock your phone.
You also mentioned that you tried to flash the ROM from the Welcome Screen. That certainly won't work. You have to be at the unlocked rainbow bootloader screen which will load when you run the RUU or when you press Power-Camera-Reset. If it doesn't go into bootloader then you've probably re-locked your phone.
denasqu said:
If you used the imcokemans unlocker a 2nd time, I believe you re-lock your phone.
You also mentioned that you tried to flash the ROM from the Welcome Screen. That certainly won't work. You have to be at the unlocked rainbow bootloader screen which will load when you run the RUU or when you press Power-Camera-Reset. If it doesn't go into bootloader then you've probably re-locked your phone.
Click to expand...
Click to collapse
haha sorry this is a problem that i had a VEERRRRY LONG time ago. have learned a lot since since then, now it is this other fella here we are trying to help him
thx tho!
Related
Hi guys:
Really strange thing. When trying to flash phone (activesync connected) the phone went to blank screen and RUU lost conection. After that there is no way to enter bootloader, but everything else is working ok.
Device has USPL installed, and been flashed many times.
Is there any way to repair bootloader?
Thanks.
Note: Actual ROM is official HTC WM6, with ext ROM modified to 2 Mb capacity.
how are you entering the boot loader
To enter the boot loader you have to either keep the voice record button held while doing a soft reset or keep the same button pressed while the device is starting
Yes, I Know
kganesh1234 said:
To enter the boot loader you have to either keep the voice record button held while doing a soft reset or keep the same button pressed while the device is starting
Click to expand...
Click to collapse
Thank you for your apreciation, but I have already done it.
I've been browsing this useful forum in order to learn a bit more about my artemis
hmmpp
RUU hehehe..
Take the SD card out then perform the procedures to get into the Boot Loader, it will work, otherwise you'll see white screen for 2-3 mins then the phone will say "Searching for SD Card..." then it will eventually get into the bootloader, if this solves your problem then please try the search feature next time because this has been discussed many times before...
digitalextremes:
Please go..... with "search button" text.
Everytime i see such text i wonder if U ever tried it!
nevertheless.
My Arte has the same problem, OS is launching properly, everything seems ok.
I want to flash a new ROM (Shady's last PLK) but i can't get into bootloader.
Thank U in advance for post with Voice-dial+Power+reset (stylus) or mentioning sim or SD, i tried all combinations.
If U have nothing to say, stay silent.
Everyone who can help, feel free, to do so.
THX I A
I had the same problem... to fix-it, just remove the SD Card...
Hi all,
i have a problem with one device here - Orbit II.
It is stuck on booting WM with volume controls on the screen. Usually it's not a big deal and can be solver with HR or by flashing a new rom, but the problem is that i cannot get it to do a HR: white screen with warning appears but when i press send buttong(the green one) - nothing happens, it doesn't react at all.
Ok, i was thinking to flash it, but another problem appeared: i can't enter bootloader(2 softbuttons+reset), same procedure works fine on my own device but this one just reboots and no bootloader...
I'm kinda out of options now.
Any help is appreciated.
Magnus23 said:
Ok, i was thinking to flash it, but another problem appeared: i can't enter bootloader(2 softbuttons+reset), same procedure works fine on my own device but this one just reboots and no bootloader...
I'm kinda out of options now.
Any help is appreciated.
Click to expand...
Click to collapse
press & hold camera button and make soft reset...
Thank you for the answer but i as said in first post, i have tried this, the white screen with the warning appears but pressing Send button does nothing, device does not react to this, so hard reset doesn't happen.
If someone could point to me any other way to enter bootloader - i can work my way from there.
I have also tried MTTY but USB connection doesn't appear in the list(yes, i have killed the activesync processes).
which screen
1st,
2nd, radio protocol version
3rd gif splash
4th wimo load screen
And also what rom have you got on atm.
It is stuck on 4th wimo load screen.
I have no idea about the actual WN version as it's not my device, but i assume it's the original O2 rom since there is still O2 splash screen.
Magnus23 said:
It is stuck on 4th wimo load screen.
I have no idea about the actual WN version as it's not my device, but i assume it's the original O2 rom since there is still O2 splash screen.
Click to expand...
Click to collapse
o well then i take its not hard-spl'd in which case i really do not get it, i have got into bootloader at the radio version screen so i dont get this one?? Is it still covered by o2 warrenty, it is 2 yrs long so best bet go to them and see what they say...
Thats if it has no hard-spl... If not take the battery out for a day and see if that brings it back to life, stranger things have happened seen that solve quite a few problems.
Well, device is not mine, a friend asked to look at it. I don't think he got a warranty left.
Well, the thing is, its not a big deal realy, it's not bricked or anything, i just need to get into bootloader, from there i can flash hardspl and the rest from SD... i just haven't seen this thing before... unable to enter the bootloader.
Is there any way to force the device to enter bootloader? I mean other than the standart procedures of Camera+reset?
I think i've seen somewhere a CustomRUU that could do that, even with incomplete WM boot. Like send some commands to the device to enter bootloader.
Does anyone know anything like this?
Hey guys. Out of nowhere, I started having this problem lately, and I was wondering if someone here might be able to shed some light on a solution. I have searched quite a bit on this particular problem, but have only thus far found a few bandaid solutions.
Basically, when I power-cycle/reset my Vogue (WM 6.1 when the problem started happening), it only seems to want to boot into the bootloader screen. My radio is up to date at 3.42.50 and I am currently using NFSAN's latest WM6.5 build with CoKe 2.31 bootloader. I can use my phone/data connection/GPS normally when I finally do gain access.
Bandaid solution one involves pulling out my battery, plugging in the charger cord, waiting 20 min, pulling out the charger cord, putting battery back in, powering on. This will get me out of bootloader mode, but next time I power-cycle/reset, im back into bootloader mode. Very hit or miss as it doesn't always work.
Bandaid solution two involves using ImCoKeMaN's titan_exitbl.rar uni_exitbootloader program. I read the entire thread on using the prog at PPC geeks, and I did make sure I was disabling ActiveSync/Mobile Device Center. Only seems to work on a specific XP machine (of two I have tried it on, and never worked on my Vista machine). Again, this will get me out of bootloader, but next time I power-cycle/reset, im back into bootloader mode. Works almost every try. Sometimes it takes two or three tries, unplugging and plugging the USB cable each time.
I would just say screw it and use the above methods to keep my phone working, but if im out on the road and I get stuck in bootloader mode, I would be in trouble. Plus, it just wouldn't be very stylish to have to tether an Windows XP box to my waist just restart my phone properly each time lol.
Anyways, I have tried flashing back to the latest stock Bell ROM and the problem has persisted.
I have flashed NFSAN's latest WM6.5 build onto my phone twice using ImCoKeMaN's 2.31.CoKe Unlocker to unclock the phone twice, and the problem has persisted.
Is it possible to change a value in the device's registry, or something such as that, to incorporate ImCoKeMaN's exitbootloader?? Is there some other file I could modify to ensure it restarts normally unless I soft-reset it into the bootloader on purpose? I am at my wits end on this one guys. Any other suggestions?
Thanks in advance guys!
jfaerr said:
Hey guys. Out of nowhere, I started having this problem lately, and I was wondering if someone here might be able to shed some light on a solution. I have searched quite a bit on this particular problem, but have only thus far found a few bandaid solutions.
Basically, when I power-cycle/reset my Vogue (WM 6.1 when the problem started happening), it only seems to want to boot into the bootloader screen. My radio is up to date at 3.42.50 and I am currently using NFSAN's latest WM6.5 build with CoKe 2.31 bootloader. I can use my phone/data connection/GPS normally when I finally do gain access.
Bandaid solution one involves pulling out my battery, plugging in the charger cord, waiting 20 min, pulling out the charger cord, putting battery back in, powering on. This will get me out of bootloader mode, but next time I power-cycle/reset, im back into bootloader mode. Very hit or miss as it doesn't always work.
Bandaid solution two involves using ImCoKeMaN's titan_exitbl.rar uni_exitbootloader program. I read the entire thread on using the prog at PPC geeks, and I did make sure I was disabling ActiveSync/Mobile Device Center. Only seems to work on a specific XP machine (of two I have tried it on, and never worked on my Vista machine). Again, this will get me out of bootloader, but next time I power-cycle/reset, im back into bootloader mode. Works almost every try. Sometimes it takes two or three tries, unplugging and plugging the USB cable each time.
I would just say screw it and use the above methods to keep my phone working, but if im out on the road and I get stuck in bootloader mode, I would be in trouble. Plus, it just wouldn't be very stylish to have to tether an Windows XP box to my waist just restart my phone properly each time lol.
Anyways, I have tried flashing back to the latest stock Bell ROM and the problem has persisted.
I have flashed NFSAN's latest WM6.5 build onto my phone twice using ImCoKeMaN's 2.31.CoKe Unlocker to unclock the phone twice, and the problem has persisted.
Is it possible to change a value in the device's registry, or something such as that, to incorporate ImCoKeMaN's exitbootloader?? Is there some other file I could modify to ensure it restarts normally unless I soft-reset it into the bootloader on purpose? I am at my wits end on this one guys. Any other suggestions?
Thanks in advance guys!
Click to expand...
Click to collapse
On the bootloader screen, in the upper right corner, does it say 'RUUNBH'?
nope. all i am seeing in the bootloader screen is
VOGU100 MFG
SPL-2.31.CoKe
CPLD-3
Serial
Click to expand...
Click to collapse
Trying running cokeman 0.40 then 2.31. You do no need run exitbl as it never ran when I flashed my vogue, which works without any problems, at least not that I have noticed.
jfaerr said:
nope. all i am seeing in the bootloader screen is
Click to expand...
Click to collapse
I assume your camera / power buttons aren't stuck? This seems strange to me. Is there and nbh or something on the root of your sdcard?
mrkite38 said:
I assume your camera / power buttons aren't stuck? This seems strange to me. Is there and nbh or something on the root of your sdcard?
Click to expand...
Click to collapse
After flashing NFSFAN's wm6.5, I soft-reset and pulled the SD card out. This problem persisted regardless of having an SD card in or not.
And yes, it is strange. But on a stranger note, the problem has seemed to correct itself. I was getting hunkered down and ready to reflash stock and NFSFAN's again, when I thought I would try restarting, and it worked! I have no idea how, as the only thing I have done with my phone since is use it normally, without resetting it for fear of getting stuck in bootloader. I have restarted and soft-reset my phone several times to verify that the problem is no longer there.
My power/camera/reset buttons were not stuck btw.
I also did a hard reset of NFSFAN's just to be safe.
jfaerr said:
After flashing NFSFAN's wm6.5, I soft-reset and pulled the SD card out. This problem persisted regardless of having an SD card in or not.
And yes, it is strange. But on a stranger note, the problem has seemed to correct itself. I was getting hunkered down and ready to reflash stock and NFSFAN's again, when I thought I would try restarting, and it worked! I have no idea how, as the only thing I have done with my phone since is use it normally, without resetting it for fear of getting stuck in bootloader. I have restarted and soft-reset my phone several times to verify that the problem is no longer there.
My power/camera/reset buttons were not stuck btw.
I also did a hard reset of NFSFAN's just to be safe.
Click to expand...
Click to collapse
That is really strange. Maybe you had a command from a previous flash stuck somewhere in memory (if that makes any sense). You see? When you run the RUU, there is a command that gets sent to the phone telling it to go into bootloader mode. Maybe this was pending somehow and now its gone ?
egzthunder1 said:
That is really strange. Maybe you had a command from a previous flash stuck somewhere in memory (if that makes any sense). You see? When you run the RUU, there is a command that gets sent to the phone telling it to go into bootloader mode. Maybe this was pending somehow and now its gone ?
Click to expand...
Click to collapse
Agreed. mtty may have shown us the answer but it's probably lost to history, now.
Glad it's (apparently) sorted.
mrkite38 said:
Agreed. mtty may have shown us the answer but it's probably lost to history, now.
Glad it's (apparently) sorted.
Click to expand...
Click to collapse
I spoke too soon lol.
Its back unfortunately. I remember reading that the titan_exitbl.exe program forced the phone to reboot with something like a "0 0 16" command vs. a "0 0 14" or something like that?
Is there some way to adjust the registry to run the "0 0 16" setting automatically unless I soft reset into bootloader (kind of like how I am assuming the phone should be anyways??)?
Would it be possible to adapt the titan_exitbl.exe script to run from a microSD card when it reads serial on the bootloader screen? as ridiculous as it sounds, at this point im prepared to carry around a 512mb sd card in my wallet in case I get stuck in bootloader away from my xp box if it will bypass the bootloader and start my OS.
Also, would I be able to reflash CoKe 2.31 without reflashing the existing OS, or would I have to reflash the OS if I reflash CoKe?
jfaerr said:
I spoke too soon lol.
Its back unfortunately. I remember reading that the titan_exitbl.exe program forced the phone to reboot with something like a "0 0 16" command vs. a "0 0 14" or something like that?
Is there some way to adjust the registry to run the "0 0 16" setting automatically unless I soft reset into bootloader (kind of like how I am assuming the phone should be anyways??)?
Click to expand...
Click to collapse
I have never had an issue with exitbl on the vogue... I guess if you can go into the code you could probably change the command, but again, it works fine for everyone else....
egzthunder1 said:
I have never had an issue with exitbl on the vogue... I guess if you can go into the code you could probably change the command, but again, it works fine for everyone else....
Click to expand...
Click to collapse
oh no, exitbl works perfectly fine on my XP machine. The problem is, I have to be at my XP machine.
I was just wondering if it would be possible to make titan_exitbl.exe "portable" so to speak, so I might be able to run it, or at least the "set 0 16" command, from a microSD card within the bootloader screen.
jfaerr said:
oh no, exitbl works perfectly fine on my XP machine. The problem is, I have to be at my XP machine.
I was just wondering if it would be possible to make titan_exitbl.exe "portable" so to speak, so I might be able to run it, or at least the "set 0 16" command, from a microSD card within the bootloader screen.
Click to expand...
Click to collapse
ahh, I am not certain that you could run anything from the bootloader as you don't have the ability to run any commands from the device itself (let alone run an executable). I guess if you name it something that the device would recognize and start it up by itself (like it does when you put an nbh with the name voguimg on it)... it might be possible.
$ HTCFlasher -p
set 16 0
ResetDevice
that is all.
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.
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