Related
After (I think) successfully upgrading to WM6, I've had a few problems...
1) I can't seem to soft reset anymore (holding down Power at the top + the reset button)...it seems the only way I can now reset my unit is by physically removing the battery...
2) I can't access the bootloader SERIAL mode...I can access the options for the kernel hive and formatting storage, but no success being able to get into USB mode to reflash my unit
Any help or suggestions would be greatly appreciated - I only bought this phone on Friday
1. This was hard reset in WM2003 - for soft reset just press the reset button
2. You need to press and hold power+reset+record(WMP) buttons at the same time
I suggest you read WIKI first before asking questions which are answered a million times
Thank you for the prompt reply.
I can understand your frustration with many people constantly asking these questions, but please don't make me feel like an idiot when I've actually read the Wiki and tried Googling the problem prior to posting.
To clarify, I know *how* to access the SERIAL option (I had to do it to upgrade from 2003 to WM6 to begin with). My point is that holding Reset+Power+Record doesn't work anymore. It just continues the boot process and goes straight to the Windows Mobile splash screen. The reset button, in and of itself, does nothing at all. I've tried everything from just tapping it a few times to pressing and holding it for upwards of 30 seconds...but it doesn't seem to do anything for me.
Try to hold and press power+record+cam buttons then press reset while holding those buttons.
Yeah, it does nothing...I have a feeling that the actual reset button is no longer working on the unit...not sure if that's to do with the upgrade to WM6, or if it's a hardware problem and just happens to be coincidence :-/
don't take xplode's advise wrongly. it's just that reading AND understanding the WIKI is important especially for beginners like yourself.
if you think you've successfully upgraded to WM6, it's probably because of the "Congratulations" message that was displayed... well, you're almost there, though not quite.
try to fully understand the no/yes/yes instruction in the WIKI... the reset+power+record combination is NOT what you should be doing. it has been replaced by another... here's the thread that could guide you... http://forum.xda-developers.com/showthread.php?t=327978&highlight=kitl
and here's the pertinent wiki page...
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4
good luck and welcome to the BA community.
Anyway if this that you try to explain is that the hardware buttons no longer work, you can try the MTTY method, if you have read the wiki you already know what exactly to do
Thanks raymonds, I will try not to, but I just don't want people thinking I'm yet another new member that doesn't read anything before posting, because I know how much I hate that too...I tried reading up on my problems for 4 hours last night before deciding to post because I couldn't find anything else to help.
I have successfully upgraded to WM6 and went through the no/yes/yes steps - the issue is that I want to go back to WM2003 or WM5...they seemed far less problematic for my phone for some reason..one problem I'm facing now is that my BA, pure and simple, no longer recognizes that I have a cellular carrier at all, making it essentially useless as a phone. When I try to go into SIM Manager, it hangs for a while, then goes into the screen saying that only emergency calls can be made...but when I try to put in my PIN, it says "Unknown SIM error", though the SIM works fine in my other phone...
I'm trying to use the Power/Reset/Record to either try reflashing in the hopes that'll resolve my issues, or downgrade...either way, it's not allowing me to do so, and I obviously can't do this while the phone is booted into WM6. It just seems like the reset button is no longer working, since neither combination that uses it (Power+Reset or Power+Camera+Reset) works anymore.
try to downgrade with MAUpgradeUT_NOID.exe, and then reupgrade, another thing you can do is to reflash the radio rom. The MTTY method resets bootloader settings which may be the solution to your problem.
MTTY under Windows XP is explained HERE
xplode, mtty requires one to do the power+reset+record combination, which he currently cannot do.
is this a second-hand unit?
Hm, there was another way to put your device into bootloader mode but i have never tryed it, in most of the WM2003 upgrades there was EnterBL.exe, and when you copy it to the device and execute it the device goes to bootloader mode...
but it also creates problems - read here
Also i had problems in the past with the latest version of MTTY (1.45) and used previous one 1.01 which worked like a charm
Sweet - thanks xplode and raymonds for your time.
Unfortunately I can't try these as I am at work right now, but I do appreciate the suggestions and will try them as soon as I get home.
If I can't get it to work, oh well - off to the service depot and a (probably) expensive lesson learned.
Please keep us updated, about your issue
Thanks guys...
So, I'm taking it that the radio stack is now corrupt, since it's no longer even showing a version number on my BA. I tried the methods xplode suggested - when I enter the unit into KITL mode, I take it I'm supposed to use USB Active as the transport method, since MTTY won't recognize a device otherwise, and my phone just boots into Windows from that point.
When I try to run MTTY though, all it does is display "kITLª" over and over again...I'm not sure if that's normal, or even how to enter a prompt of some kind...
I'm starting to wonder if maybe I should just take it to the depot, pay the $75 I was quoted, and learn my lesson... :-/
Any other suggestions, or am I just totally doing what you suggested wrong?
You do not need to enter KITL because this is used to debug your WM build using Platform builder
Just try to put your device to botloader mode and then use MTTY to instruct the bootloader what to do, or just reflash radio and then new rom
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!
hey, i have a stock Orange SPV M3100 ie htc Hermes 100, flashed successfully with Black Satin a while ago now, no major problems and running much less glitchy than the stock rom. yesterday when i checked my phone it was on the bootloader (tri-colour). it wont leave it, soft reset hard reset. cant flash a new rom or anything as it wont connect with active sync obviously. when i reset for a second on the boot screen it says 'no image found'
tried the mtty program but cant type in it? cant press enter for it to start or whatever, prob being retarded im sure but i couldnt get it to work. pluuus on the initial open port setting menu theres no option for usb? yet the guide says select usb.
help pleeease =]
it actually says 'no image file' not found but yes anyone have any ideas?
Flash your unit with the OEM ROM using the SD Card...
hmmm have done so then soft reset and it seems to have made no difference, getting hold of a different rom to see if thats more successful...
CRCinAU said:
Flash your unit with the OEM ROM using the SD Card...
Click to expand...
Click to collapse
is there a particular rom to be lookign for? tried two dfferent ones that have installed successfully but when i reset just loads up in boot screen again?!
gah most frustrating
Try looking for and then (if need be) repairing bad blocks with MTTY. Then reflash os if bad blocks were found and repaired. Remember that sometimes the carrier actually "brands" handsets with bad blocks that CANT be repaired. Hope this helps....
I have received one elf with is stucking on calibration menu,everytime that i press all the 5 positions again it keeps on asking for it and i cant get to the phone.
Phone is detected by activ syn ,i want to upgrade the rom but as i'm having this problem i cant upload cert and enabl files.I cant do hardspl nothing.
Is there anyway i can repair this phone.It has got 2.26.00 spl.
Regards
I had the same problem.... but I just hard reset my phone with the styles and started my phone again and then pu it fast on my computer and started the upgrade to 2.28 and the my phone worked correctly.
Maybe I've made some mistakes but that's because im 13 and I live in Holland
I hope its good information for you!
hi sonkar read this thread http://forum.xda-developers.com/showthread.php?t=445666
i agree with marcbrug .. try to do a hard reset .. that is by holding the End & the Call Buttons and soft reseting the phone.. when the confirmation msg appears press the "Middle" (the largest) button..
hope that helped...
I have already done the hard reset,it's the first thing i did but still facing same problem.
sonkar said:
I have already done the hard reset,it's the first thing i did but still facing same problem.
Click to expand...
Click to collapse
It's happened to me a couple of times. I just re-flashed the ROM (hard reset did not work).
Can you explain how i can flash the rom?
Cos as the phone gets stuck in calibration i cant install cert and cab files in the phone.So i cant do hardspl and neither flash the rom.My spl is 2.26.00.
Regards
sonkar said:
Can you explain how i can flash the rom?
Cos as the phone gets stuck in calibration i cant install cert and cab files in the phone.So i cant do hardspl and neither flash the rom.My spl is 2.26.00.
Regards
Click to expand...
Click to collapse
You could probably still install it manually if you are able to connect to ActiveSync during the screen calibration.
First, try installing "myMobiler" which allows you to access the phone from your PC (like in Remote Desktop). See if you can get any further than the calibration screen with that.
Otherwise, download the "itsutils" package from here:
http://www.xs4all.nl/~itsme/projects/xda/tools.html
Then, use "prun" to remotely launch the CAB file from the DOS window:
e.g. C:\> prun.exe \Windows\myfile.cab
I have never tried this command with CAB files but it worked with Windows Mobile EXE files.
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.