Related
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!
Hi guys, you have been a great help to me so far, but I just can't find anythign to help me with this now. I have a hermes100 with WM6 and i just flashed the radio to 1.54.07 and it gave me an option for hardSPL and said that it was recommended so i investigated and found the upgrade for it.
I ran the wrapper file and it goes to the stage where it puts my hermes into flash mode but it displays "spl1.09" on the screen yet when push the ok and power keys during reset it shows "spl2.03"
it goes through the screens until it puts my phone into flash mode and it says it is trying to read my device then i get error code (260) that it isnt connected. Anyone know a way to fix this?
Use sd card method, page 116 on here: http://forum.xda-developers.com/showthread.php?t=296722
Hope this helps...Cheers...
okay, i tried the sd card method and it does the same thing. after it gets to the bootloader screen i just sits there with
"HERM100
IPL-SSPL by des
HERM 100
SPL-109.ds
serial"
okay, nevermind, i just had to reinstall the drivers for when i was in bootloader mode. I got it to work, thank you for you help.
cheers :-D
No problem, now you should be able to flash any hermes rom to your hearts content with the knowledge you have a safety net if something does(and probably will, as you'll find flashing addictive, sooner or later) go wrong. Pleae remember though that Hard SPL ISN'T a guarantee that you will be able to fix you phone, it just makes it easier when something goes wrong... Cheers....and happy flashing...
samterry1234 said:
okay, nevermind, i just had to reinstall the drivers for when i was in bootloader mode. I got it to work, thank you for you help.
cheers :-D
Click to expand...
Click to collapse
how did you do this?
I have read and read and read. I have "bricked" my phone in the past and fixed it. I have used, tested, and flashed many roms from this site (Thanks to all cooks for their work!) but I still consider myself somewhat 'new' to troubleshooting.
I woke up this morning to make some important phone calls today and as luck would have it, my phone was stalled again. It's been doing that for a few weeks now. My last flash was Open Touch 5.0 UL I believe (either that or 5.2 biggy) and it has been working great except for the occasional freeze.
EDIT: Forgot to add, the actual problem is now it won't boot up after it froze this morning. Just sits at the boot screen
So I've tried my other methods of fixing it... /edit
Except this morning nothing is working. I have tried flashing with Orig. T-mobile ruu, tried SD flashing with the RUU_signed.nbh, tried restarting the computer, phone, removing battery and sim... NOTHING! When trying the sd flash (which I've never done before today, it reads and tells me to push the down button but then goes to bootloader screen and just sits there. With the RUU I'm getting err 300 but I'm using the SAME RUU (4.10...) that I've used in the past to reflash my phone AND tried the new one (4.26...)
Possible problem: Does it matter what kind of usb cable you use? I don't have the normal one I use as I am not home but I figured usb is usb...
I've read about it being a motherboard issue, how common is this?
I've read somethings about MTTY, would this apply to me??
Please help, anyone who has any suggestion, I'll try it!!
Stats:
IPL 4.10.0002
SPL 4.10.0000
NOT hard-spl'd
Wing w/ Open Touch Project 5.0 or 5.2
actualy the sd method needs hard spl thats all i can really provide
I appretiate it, that I did not know... I could barely find anything on how to do it even.
im having the same problem bt instead of freezing da screen jus goes different colors or jus goes gray and stays der
Thats basically what mine did. The colors would get messed up and no matter what button i pressed it would not do anything. My advice to you edrift, is BACK UP YOUR STUFF NOW and reflash it asap if you can still reboot. I can get into my phone at all now.
yea i tink i might jus throw my phone away.dis is jus gettin rediculous
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
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.