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.
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!
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
Hello mates,
My i-mate Jasjar doesn't start any longer. Here's how I got here. I tried to flash my jasjar with Crossbow ROM using ROMUpgradeUt.exe but it didn't do anything. So I went into the Country_ID_Error folder on the computer and executed MaUpgradeUt_noID.exe. My jasjar froze after this and everytime I restarted it just hung on the bootscreen that says i-mate.
So I tried using mamaich method using mtty and now I can't even get to the i-mate bootscreen. So nothing just happens when I try to power up the phone (I'm sure the battery isn't dead).
All I can do is just enter the bootloader mode. That is the only thing that I can do that I know.
Please suggest something. I'm lifeless without the i-mate.
Thanks and regards,
Aditya More.
i had this same issue, i task28?'d my device, whatever command that resets the flash structure, then booted into bootloader, and flashed this file:
http://rs507.rapidshare.com/files/184081773/JASJAR_WWE_11353_137_10301.zip
that should fix you up real good, hopefully.
Well thanks a lot. But it doesn't help. It gives me a connection error when everything is fine. USB is connected, ActiveSync USB connection is disallowed.
I forgot to mention, that when I task 28'd my device, nothing showed on the device. It just showed USB at the top and v2.01 at the bottom for ever, which means the task 28 wasn't probably successful or I ain't sure what.
Yeah, I had to ask you how if the above given file will work if the phone is in bootloader mode.
To fill you on more details, my phone somehow strangely starts. I'll explain how.
When the phone is switched off, and when I press the reset button, nothing actually happens, no activities can be observed.
When the phone is switched off and I connect it to the computer via USB, it shows the charging light. Now when I press the reset button with the phone connected to the USB, the charging light goes off and the USB detection sound sounds on the computer and the computer shows "USB Device not recognized". This means the phone started.
But strangely in both the above cases, none of the two lights on the phone indicate anything and display of the phone shows absolutely nothing.
The only thing I can do with the phone now is enter bootloader.
Also, since I compromised so much, is it possible that I can still flash it with WM6? Because going back to WM5 will make me feel miserable.
Thanks.
@cheapusenet:
I tried flashing with that file. It flashed successfully, but the screen is all smudged. I soft reseted the phone too (using reset+two soft keys) but it keeps displaying that same smudged screen.
Good news is it did something.
Bad new is that it didn't make the mate work.
Please help. I'm dying without the phone.
Thanks and best regards,
Aditya More.
is it possible you can get a picture of what screen its showing? I THINK it happened on mine as well, did you let it sit for 10 or so minutes? if i recall the bootscreen was all corrupted but it started into WM5 just fine.
and regarding wm6, i'd attempt to get the device working before you try and get fancy. is the device cid unlocked? mine was and thats what was causing the issues.
Originally Posted by mamaich
if you can enter bootloader - use "task 28 55aa", this would restore DOC to its original layout.
If you cannot - contact service center.
if you didnt run that exact command, it's probably a good idea.
and you could try reflashing that stock imate rom?
This is all that happens.. I have waited for 5 minutes. I'll wait for 20 minutes now.
i waited for 30 minutes.. no go..
yap it did that EXACT same thing to mine.
reflash it, i think that fixed mine.
if that doesnt work, attempt flashing some custom roms.
is it CID unlocked?
i flashed it twice.. no go..
what's CID unlocked?
CID
Read the Wiki on my sig link
cid unlock allows flashing of roms that don't match your device branding.
i don't remember what brought me back from that, i may have flashed a custom rom with the imate cid settings in it? i don't remember.
i'll post a rom that i think may have helped in a few hours, I have slow upload speed. until then, just keep tinkering.
also, you should only be flashing nk.nbf. not the ms, or radio nbfs.
http://milfweed.info/UNI_AKU3_2_WWE_IVAN_beta_4_extrom_public.rar
try that rom.
hey man.. Flashed the rom with Ranju's ROM of WM6.1.. it worked.. But I can get the phone to be turned on. i mean device turns on but I can't make or receive calls or text. Let me check the thread of that rom. Thanks a ton for your support. Really appreciate it.
Hello XDA.
Huge problem over here.
I can't flash anything on my device (HD2, Europe) anymore.
Newest Radio-Rom, SPL-2.08.HSPL.
Tried everything listed in the forums, event tried to flash stock leoimg.nbh from sd. nothing.
Whenever I try to flash via USB, the screen is stuck at 0 % (independent from what I try to flash).
HSPL won't let me reflash it, get an error msg.
When flashing from sd, stuck at "loading..."
Hardreset (VolUp+VolDown+Power) works, but doesn't change anything.
I really tried E-VERY-THING, nothing seems to work.
Bootloader is starting up, even the white screen with the green HTC logo is showing up, but then: nothing.
Worked my ass of through hundreds of threads in dozens of forums.
This is my last chance.
Anybody? Thank you!
schousta said:
Hello XDA.
Huge problem over here.
I can't flash anything on my device (HD2, Europe) anymore.
Newest Radio-Rom, SPL-2.08.HSPL.
Tried everything listed in the forums, event tried to flash stock leoimg.nbh from sd. nothing.
Whenever I try to flash via USB, the screen is stuck at 0 % (independent from what I try to flash).
HSPL won't let me reflash it, get an error msg.
When flashing from sd, stuck at "loading..."
Hardreset (VolUp+VolDown+Power) works, but doesn't change anything.
I really tried E-VERY-THING, nothing seems to work.
Bootloader is starting up, even the white screen with the green HTC logo is showing up, but then: nothing.
Worked my ass of through hundreds of threads in dozens of forums.
This is my last chance.
Anybody? Thank you!
Click to expand...
Click to collapse
If you've tried literally everything as you claim, then nobody can possibly help you. Have you tried flashing a stock ROM via the SD card?
schousta said:
SPL-2.08.HSPL.
.......
the screen is stuck at 0 %
Click to expand...
Click to collapse
are you 100% sure its 2.08.hspl and not 2.08.0000?
also, tried different usb ports? different PC even, if possible? (not 64 bit either, if you can manage it, , , an xp machine is perfect)
Probarly your phone is bricked yes.
You say you tried everything and nothing worked, then i think there is no option left. Maybe put it in the fridge or something for like 10 minutes?
To all:
I'm sure, its hspl 2.08, pic of bootloader on its way.
I tried Stock ROM from sd. Stock oben AND provider one.
Tried 2 different PCs. Will try XP 32bit when possible.
Please tell mehr, that here's a german Euthanasie a jtag device... or pleeeeease name another option...
Thanks...
Oh my god, Not "Euthanasie" i'm so sorry...
Damn autocorrect... meant "with"...
Have you tried this version: http://forum.xda-developers.com/showpost.php?p=5279236&postcount=4
to reflash HSPL2.08
Please fill in the blank(s):
Your device was working fine, and you could flash anything. But recently you _________________ and now you can't flash anything.
Dblfstr said:
Have you tried this version: http://forum.xda-developers.com/showpost.php?p=5279236&postcount=4
to reflash HSPL2.08
Click to expand...
Click to collapse
Tried it. Outcome:
:/
Marvlesz said:
Please fill in the blank(s):
Your device was working fine, and you could flash anything. But recently you _________________ and now you can't flash anything.
Click to expand...
Click to collapse
... recently I tried to flash a whole new ROM. RadioROM was ok.Task29 went good, MAGLDR had problems. First time stuck at 4 % (Connection Error 262 (?)), second time at 96 % (also connection error), third time I held the data cable in the port, not too strong, but it worked this time. MAGLDR booted, but didn't show any options, just the header. So i did another Task29. From this time on, nothing worked anymore. :/
Anyone?
Thanks in advance!
EDIT: Also trying another sd-card atm, doesn't seem to work...
Sorry for double-posting,
but i was able to re-flash radiorom via sd. maybe this helps.
Drowzz said:
Probarly your phone is bricked yes.
You say you tried everything and nothing worked, then i think there is no option left. Maybe put it in the fridge or something for like 10 minutes?
Click to expand...
Click to collapse
This is the most stupid bit of dangerous "advice" I've ever heard. Not only is a phone not "bricked" as long as the bootloader is working, but more importantly, "put it in a fridge" has never done anything good. It's an urban legend. If you feel like it you can try it on a broken harddisk right before getting out the black candles and the chicken blood, but it's completely useless.
schousta said:
but i was able to re-flash radiorom via sd. maybe this helps.
Click to expand...
Click to collapse
Have you tried a different USB cable? Everything points to the connection, maybe your phone's USB port is shot.
Wouldn't this have been solved when flashing over sd-card?
RadioROM worked this way, whole stock package does not.
Tried different usb cables, different pcs. and different stock roms over sd.
so chances are good it's not bricked, if the bootloader works? I mean, it even boots to the green htc logo on white bg....
thanks
EDIT: Also, usb-port worked fine before flashing, it also works now, bootloader recognizes "USB".
EDIT2:
MTTY changed nothing. Task29 was succesfull (it seems), tried task 2a (that should format the WHOLE thing, like i unterstood) and 28, too, seemed succesfull, too, but my problem remains.
and why the hell can i flash a radio from sd but not a full stock rom? sd card is formatted in fat32 and 2 gig sized... tried all official roms...
and hspl still throws this error....
EDIT3:
Set up a VM with Win XP 32 bit. HSPL doesn't throw an error now, but it seems to take forever to install. Almost 10 Minutes and counting.
is this normal?
Didn't work.
Dont know what else to try, if nobody answers...
Think about sending it in to get JTAGed (Bootloader rewritten...)
Dr_Grip said:
This is the most stupid bit of dangerous "advice" I've ever heard. Not only is a phone not "bricked" as long as the bootloader is working, but more importantly, "put it in a fridge" has never done anything good. It's an urban legend. If you feel like it you can try it on a broken harddisk right before getting out the black candles and the chicken blood, but it's completely useless.
Click to expand...
Click to collapse
Why? I've seen it working. A friend bought a broken HD2, the seller said he couldn't flash anything and he had problems with camera and games before. So after dozens of tries, he put it into the fridge for half an hour and managed to flash magldr and a new rom. Well, the motherboard was faulty and he couldn't do almost anything because the phone suffered constant freezes and restarts when doing anything else than looking at the homescreen, but well, the fridge helped him a bit.
USB Port on the phone, USB Port on the computer, USB Cable, Drivers in the computer, Firewall or similar host security software on the computer - these are some of the things I'd double-check.
But a ROM in nbh format should still flash from SD- what exactly happens, does it not find it or not complete the flash? Does it throw any error code?
And did you see any bad blocks while on mtty?
ph03n!x said:
USB Port on the phone, USB Port on the computer, USB Cable, Drivers in the computer, Firewall or similar host security software on the computer - these are some of the things I'd double-check.
But a ROM in nbh format should still flash from SD- what exactly happens, does it not find it or not complete the flash? Does it throw any error code?
And did you see any bad blocks while on mtty?
Click to expand...
Click to collapse
No bad blocks, will check it again.
As said, USB-Port on phone seems ok to me, used 2 different drivers on 2 different pcs with 2 different data cables and 2 different OS. Firewall and Antivir disabled.
When flashing from SD leoimg.nbh seems to be found but it gets stuck at the grey screen with the blue "loading...". forever. no error code, not even an option to confirm or cancel the flash. cancelling the loading process with voldown failed. tried three different sd cards and all official stockroms that could possibly come in question for my phone.
But why was I able to flash the latest radiorom again?
schousta said:
No bad blocks, will check it again.
As said, USB-Port on phone seems ok to me, used 2 different drivers on 2 different pcs with 2 different data cables and 2 different OS. Firewall and Antivir disabled.
When flashing from SD leoimg.nbh seems to be found but it gets stuck at the grey screen with the blue "loading...". forever. no error code, not even an option to confirm or cancel the flash. cancelling the loading process with voldown failed. tried three different sd cards and all official stockroms that could possibly come in question for my phone.
But why was I able to flash the latest radiorom again?
Click to expand...
Click to collapse
Beats me. How long it you wait for the full ROM to flash though? I know you have tried a bunch, and am sure you would have waited long enough, but asking just in case. It might take as much as 10 minutes or more.
But ya, at the moment JTAG seems to be your best bet.
waited for almost 1,5 h now for an sd flash...
jtag seems more and more acceptable...
If tag is available, go for it.
There are a few variants of this problem, that I think of under the umbrella name of "stuck radio"
Usually its the radio that gets stuck, but sometimes the spl gets stuck too, or sometimes just the spl. Either way, some types of flash work whilst others don't (radio works hspl doesn't for example, or custom roms flash stock rooms dont ), or a flash seem to work but nothing changes, (hspl gives hacked it but spl doesn't change,or the flash hangs...
My guess is two causes, some being corruption of the software, some actual hardware...bad blocks at a critical area of memory perhaps.
There are one or two success threads with this family of problem, but hundreds with no successful outcome. Sometimes just flashing the oldest correct rom from SD does it, sometimes freezer trick works, (not an urban myth), sometimes just trying again and again works. Often though, nothing does, so if jtag is an easy option I'd take it.
Be warned though, it could be hardware, in which case it may not work.
schousta said:
... recently I tried to flash a whole new ROM. RadioROM was ok.Task29 went good, MAGLDR had problems. First time stuck at 4 % (Connection Error 262 (?)), second time at 96 % (also connection error), third time I held the data cable in the port, not too strong, but it worked this time. MAGLDR booted, but didn't show any options, just the header. So i did another Task29. From this time on, nothing worked anymore. :/
Anyone?
Thanks in advance!
EDIT: Also trying another sd-card atm, doesn't seem to work...
Click to expand...
Click to collapse
^This.................. with that v
samsamuel said:
If tag is available, go for it.
There are a few variants of this problem, that I think of under the umbrella name of "stuck radio"
Usually its the radio that gets stuck, but sometimes the spl gets stuck too, or sometimes just the spl. Either way, some types of flash work whilst others don't (radio works hspl doesn't for example, or custom roms flash stock rooms dont ), or a flash seem to work but nothing changes, (hspl gives hacked it but spl doesn't change,or the flash hangs...
My guess is two causes, some being corruption of the software, some actual hardware...bad blocks at a critical area of memory perhaps.
There are one or two success threads with this family of problem, but hundreds with no successful outcome. Sometimes just flashing the oldest correct rom from SD does it, sometimes freezer trick works, (not an urban myth), sometimes just trying again and again works. Often though, nothing does, so if jtag is an easy option I'd take it.
Be warned though, it could be hardware, in which case it may not work.
Click to expand...
Click to collapse
Looks like we have a winner ....
You said "flashing a Radio was OK" .. so we shouldn't be having a problem there. Also, a task29 went good, too.
You started having those problems during MAGLDR, but after you held the cable, everything went fine.
So in other words, during attempt 1 & 2 of MAGLDR flashing, you pulled the cable.
I know that pulling the cable midst a radio flash will 99% cause a brick.
Same with ROM with a Radio (but less chance).
But MAGLDR, I don't really know, maybe sam will help ?
Hello there!
I got HD2 today, it has windows installed on it and its Swedish.
Ive spent half of day trying to get it done but nothing worked.
I cant install HSPL to go on with the installation, Ive tried everything.
I connect my HD2 to PC and activesync does its work, I can see my mobile phone connected, adding new files works both on local and sd storage.
The problem comes in when I try to install HSPl so I could flash my phone and continue with the installation. Whenever I start HSPL isntallation my HD2 losses its connection with the PC and nothing happens. What could be the problems.
Whats the easiest workaround for this? I really want to install the android os on my phone, I dont like the windows one.
(I have searched the forums, nothing helped me)
MY DEVICE:
ROM v 1.o
Radio T8585
1024Mhz Cpu
Ram 576 Mb
Nand 1024 Mb
32 bit bus
Win mobile 6.5 pro
16 Gb mem card
Is there any other way to install android? Anything?
----------------------------------------------------
So I have tried doing same things today. I tried entering the bootloader using vl down and power up, ol down and reset key, left arrow and power key and the phone just starts my windows nothing. But when I press vl up, dwn and pwr key I get into 4 colour mode and it give me error: Copying file from SD card failed, system will shut down.
I will try to play around it a little bit, maybe try nativeSD somehow, but I dont think Ill manage anything. Help
----------------------------------------------------
When I use clrcad and haret on SDc it starts booting linux, progress bar goes to the end and stays there. Every time. Ive been waiting for some time for it to boot, but it jsut stays there.
Is there a way to get rid of this windows mobile crap easily? Do you think that mobile shops are willing to do this sort of stuff for you?
Try installing HSPL from the bootloader.Turn off phone, hold volume down rocker and boot up.
Marvlesz said:
Try installing HSPL from the bootloader.Turn off phone, hold volume down rocker and boot up.
Click to expand...
Click to collapse
Cant get into the bootloader, as said. I dont know why & whats causing it, but nothing is working as it should be
Ah, forgive me for skipping that part. I know this problem, and I've seen it many times.
Usually, I am not the one who fixes them, so here is one solution:
http://forum.xda-developers.com/showpost.php?p=25940714&postcount=3
Here's another:
http://forum.xda-developers.com/showpost.php?p=36420418&postcount=20
There are many, you need to search for them. I don't know which will work for you.
No help there, its still the same, no bootloader, nothing.
+
I cant seem to find fastboot anywhere in my settings.
+ My mobile is whole Swedish, I dont understand a thing, but I do manage to get around, but I still cant find fastboot like the one poster said that it might be the problem.
Im not sure whats the problem in the end. I feel that this phone is somehow locked, wont let me do such stuff, but I might be wrong, Im not really the kind of guy thats interested in developing phones, so I dont know most of stuff. Hope some more advices might come in.
Wait.. If it's swedish, why not go into settings and change language to yours (or to English)?
Also, you said "no help there". You mean the windows mobile application didn't let you boot into bootloader? I am quite sure you didn't even try it. It should work, trust me
But the question is: Once you're in the bootloader, and get rid of Windows Mobile, how are you going to go into bootloader again? (since there's no longer an app, or windows to RUN that app)
Marvlesz said:
Wait.. If it's swedish, why not go into settings and change language to yours (or to English)?
Also, you said "no help there". You mean the windows mobile application didn't let you boot into bootloader? I am quite sure you didn't even try it. It should work, trust me
But the question is: Once you're in the bootloader, and get rid of Windows Mobile, how are you going to go into bootloader again? (since there's no longer an app, or windows to RUN that app)
Click to expand...
Click to collapse
Well, for the language, I have been trying to change it, but I dont think its possible + Ive found multiple threads on forums about changing lng on windows mobile phone and they said that its not possible.
And for the bootloader, its not working. Seriously, I have been trying to do it for 2 days now. Using buttons, using random apps Ive found here on forums and none of them got me into the bootloader (expect the VL UP, VL DWN, PWR pressed together, which got me into four colour screen (which should be bootloader if Im right), but it turns off straight away if not connected with usb cable. If it is connected it stays at error as said in my first post). I wish I could get rid of the windows somehow so the bootloader would ask me for another rom or however that works, Im not much into it as said.
I somehow managed to get past the verifying the usb connection for HSPL installation, progress bar shows but it goes nowhere & after some time appears this error
buhamuha said:
... (expect the VL UP, VL DWN, PWR pressed together, which got me into four colour screen (which should be bootloader if Im right)...
Click to expand...
Click to collapse
No, that combination should get you into hard resetting your device and not into bootloader. Even if it does get you into the bootloader for a fraction of unit time, it won't allow you to flash anything. Volume down only is to get into bootloader
What happens when you follow this post? And by "what happens" I mean what error EXACTLY do you see?
Marvlesz said:
No, that combination should get you into hard resetting your device and not into bootloader. Even if it does get you into the bootloader for a fraction of unit time, it won't allow you to flash anything. Volume down only is to get into bootloader
What happens when you follow this post? And by "what happens" I mean what error EXACTLY do you see?
Click to expand...
Click to collapse
I have tried that thing yesterday. Didnt work. Tried it right now - it does nothing. I run the app and my phone just goes black (like when you tap the power button, lock or something) and it will stay like that without doing anything until i tap the pwr button to unlock it. Nothing really happens
I want to advise you install a ROM from sd card using the LEOIMG.nbh method. But I am not sure which ROM is for which device. (I never actually flashed my phone from sdcard). That might make the bootloader boot up (?). Also, can you confirm that the volume rockers work fine under windows mobile?
To be honest, I am out of solutions. We should wait for other people's.
Sorry I couldn't help.
Marvlesz said:
I want to advise you install a ROM from sd card using the LEOIMG.nbh method. But I am not sure which ROM is for which device. (I never actually flashed my phone from sdcard). That might make the bootloader boot up (?). Also, can you confirm that the volume rockers work fine under windows mobile?
To be honest, I am out of solutions. We should wait for other people's.
Sorry I couldn't help.
Click to expand...
Click to collapse
No problem man, thank you for trying.
Yes, my vol buttons work jsut fine, its just the thing I cant get into the bootloader, no matter which way I try.
LEOIMG method needs bootloader too, right? Or does it go with the clrcad and haret method? Haret doesnt work for me, starts booting stuff and than jsut stays at it
do exactly as i say and tell me what happens:
remove battery
remove sd card
plug in to pc via usb
hold volume down
put battery in
now you should be seeing the tricolor bootloader, right?
gilbert32 said:
do exactly as i say and tell me what happens:
remove battery
remove sd card
plug in to pc via usb
hold volume down
put battery in
now you should be seeing the tricolor bootloader, right?
Click to expand...
Click to collapse
I have no SD card slot, I think Its hidden somewhere under since its reading it both on PC & phone.
I have tried doing it without the sd card removal but nothing happens.
Where could I look for the sd card, its not on any side, its not under the battery, its not udner the other 2 romovables
--------------
UPDATE:
So I have opened my HD2 up and foudn the sd card under and I have removed it. DId everything you said and still nothing, my HD2 just boots up normally. No bootloader or anything. It seems like my bootloader is hidding somewhere
buhamuha said:
I have no SD card slot, I think Its hidden somewhere under since its reading it both on PC & phone.
I have tried doing it without the sd card removal but nothing happens.
Where could I look for the sd card, its not on any side, its not under the battery, its not udner the other 2 romovables
--------------
UPDATE:
So I have opened my HD2 up and foudn the sd card under and I have removed it. DId everything you said and still nothing, my HD2 just boots up normally. No bootloader or anything. It seems like my bootloader is hidding somewhere
Click to expand...
Click to collapse
this is really confusing. starting to sound like an hd2 clone to me...
can you open the back cover, remove battery and take a photo of the phone, then upload it here? (remove imei/serial/sensitive stuff from picture, using paint or some software )
gilbert32 said:
this is really confusing. starting to sound like an hd2 clone to me...
can you open the back cover, remove battery and take a photo of the phone, then upload it here? (remove imei/serial/sensitive stuff from picture, using paint or some software )
Click to expand...
Click to collapse
mhm could be the clone. Is there any way to do something about it if its a clone?
gilbert32 said:
this is really confusing. starting to sound like an hd2 clone to me...
can you open the back cover, remove battery and take a photo of the phone, then upload it here? (remove imei/serial/sensitive stuff from picture, using paint or some software )
Click to expand...
Click to collapse
buhamuha said:
mhm could be the clone. Is there any way to do something about it if its a clone?
Click to expand...
Click to collapse
I knew it!! I was going to say it might be fake, but deleted that line for some reason. Anyway, with those double sims trays, it's definitely a clone (unfortunately). How much did you pay for it?
Edit: Nope, not that much that can be done with a clone. You'd be lucky if you were able to even change the Windows Mobile ROM.
Marvlesz said:
I knew it!! I was going to say it might be fake, but deleted that line for some reason. Anyway, with those double sims trays, it's definitely a clone (unfortunately). How much did you pay for it?
Edit: Nope, not that much that can be done with a clone. You'd be lucky if you were able to even change the Windows Mobile ROM.
Click to expand...
Click to collapse
Got it for free, my aunt gave it to me. I dont know how much she paid for it. So I should leave it as it is, there is no possible way to change it?
As far as I know (and as my searching abilities go) no, you can't do much. I hope someone proves me wrong.