I know at least 2 other people have had this happen so I wanted to make a central thread to troubleshoot and maybe fix it. Chime in with what you've tried and (hopefully) what worked.
After a failed attempt at downgrading my hboot, I'm stuck with no picture on the screen. I can only access my phone in fastboot and the official RUU .exe. When I try to run the exe, I can get as far as the phone rebooting into bootloader but then it just times out. In fastboot I have tried to flash a new hboot or boot image but get "failed image error" or somethng.
Any other ideas/solutions?
Did you try flashing a recovery through fastboot? There is a link to amon ra's thread in my sig that has directions on it
Sent from my PC36100 using XDA App
I had the same problem this weekend.
http://forum.xda-developers.com/showthread.php?t=839155
Apparently nobody knows what to do because I didn't get it fixed.
EDIT
That being said, today I gave up and took it to Sprint, said HTC told me to use a program to restore it to factory defaults (I was very vague about the RUU, tried to sound as unknowledgeable as possible), and it stopped midway (which is sort of the truth). The guy at Sprint tried to restore it using their program, but it wasn't working. He asked if it was rooted, I played dumb, and I'm getting a new one sent to me through the warranty for free.
If your NAND is locked again (S-ON) you will only be able to flash an update signed by HTC.
I'm assuming you had the 2.02 hBoot? If so place this on your SD card, rename it to PC36IMG.zip and then put it back in your phone. Hold vol down and boot into your bootloader like normal, and after a full minute push vol down. If all goes well it will flash everything the RUU would normally.
3.30.651.2_PC36IMG.zip
xHausx said:
If your NAND is locked again (S-ON) you will only be able to flash an update signed by HTC.
I'm assuming you had the 2.02 hBoot? If so place this on your SD card, rename it to PC36IMG.zip and then put it back in your phone. Hold vol down and boot into your bootloader like normal, and after a full minute push vol down. If all goes well it will flash everything the RUU would normally.
3.30.651.2_PC36IMG.zip
Click to expand...
Click to collapse
he wasnt getting into the bootloader...I had a phone that did this...I was able to recover using unrevokeds hboot drivers and the 3.30 ruu on a 32bit windoes 7box
Related
Hello,
I need major assistance, I have been running third party roms on my phone for a while as well as S-Off (alpharev's iso). My phone provider has recently released the OTA update so I was trying to go back it seemed to run fine but now when I boot my phone all I get is a short vibrate and the Alpharev splash screen then the phone reboots. I have tried to power up with the Vol- and power button and nothing happens, I have tried to use fastboot from the command line and all I get is Waiting for Device. I really need help please.
Devin
UPDATE:
I can now get into Android system recovery but when I try to apply a new rom it keeps saying "failed to verify whole-file signature" "signature verification failed". Does anyone have any ideas?
Have you tried installing a working RUU? That will get your phone back to working state and you can root it once again.
Note: Use the proper RUU. Flashing a AMOLED ruu will cause a display brick if you have a SLCD desire.
Edit: Also you cannot flash a custom rom from android system recovery. Only a .zip file that is signed by htc can be flashed I think. Search and download a htc rom and flash from recovery if the above mentioned method does not work.
careful while running the ruu on a s-off device. i had a s-off device and flashed a amoled ruu instead of a slcd one and ended up bricking my screen -- fixed it later though but it caused major panic. so, run the ruu only once you're very very sure.
secondly, each ruu extracts a rom.zip file when run in a temp directory. if your ruu doesn't work because it throws a hboot or a cid error, you can try searching and flashing for this rom.zip file from fastboot and it should ideally flash the stock rom -- since it is signed by htc. you will lose root though.
Thank you for your response, do you know of a way to extract an 'update.zip' from an RUU exe file? The latest RUU from my carrier has been posted and I can't run through the normal update process as it doesn't detect my phone.
put your phone in fastboot -- switch off phone. press back button+power and try running ruu again. Once it detects, search for rom.zip on your comp temp file location.
i don't know any other way unfortunately
Sorry if it seems like I'm being stupid.
I found the rom.zip, I tried renaming it to update.zip and it fails signature verification. So right now I'm sitting at a black screen with the picture of the phone and the triangle and when I type 'adb devices' into my terminal I get the S/N and Offline. Any assistance would be great, I'm doing this on OS X if it makes a difference.
You need to rename it PB99IMG.zip as it needs to be found when you first turn the phone on in HBOOT. Any 2.2-based RUU will be fine on an SLCD screen
Obviously flashing a ROM this way will reset the phone back to stock and delete ALL data
I renamed the file, it worked!! I Have a functional phone!!
Thanks so much to everyone who helped me out in the this thread. I love this community so much.
may i ask how you got into recovery? because it looks looks like i have the same problem.
dragonithe said:
may i ask how you got into recovery? because it looks looks like i have the same problem.
Click to expand...
Click to collapse
switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery.
What I did power on the phone holding the back and power buttons until the menu opened.
hi can you please have a look on this as well
http://forum.xda-developers.com/showthread.php?p=9097558#post9097558
Regards
hey i am at exactly where your problem was
i tried to update telus 2.2 OTA and i've bricked it
now i actually don't know which rom.zip to use what did you use?
since we are from the same service
i tried a wrong rom.zip and it said wrong modal ID
SOOO CLOSE PLEASE HELP ASAP
SPENT ALL DAY LOOKING FOR A SOLUTION
Here is the link to my dropbox with the PB99IMG.zip for Stock Telus Froyo rom I used to fix the problem.
PB99IMG.zip
I need to reset my Evo to stock ROM so I can send it in to Sprint. When I tried flashing the PC36IMG.zip in the bootloader, it unexpectedly stopped mid-flash. Now whenever I try to boot the phone, it goes straight to fastboot, whether or not I press the volume buttons.
How can I fix this?
BTW: I've seen this thread: http://forum.xda-developers.com/showthread.php?t=808707 which has the exact same problem as me... including what he said in his second post (the third post on the page) that nobody replied to. I used the same PC36IMG linked in that page, in fact. It loads the ZIP but then it goes back to the bootloader.
vonStemmington said:
I need to reset my Evo to stock ROM so I can send it in to Sprint. When I tried flashing the PC36IMG.zip in the bootloader, it unexpectedly stopped mid-flash. Now whenever I try to boot the phone, it goes straight to fastboot, whether or not I press the volume buttons.
How can I fix this?
BTW: I've seen this thread: http://forum.xda-developers.com/showthread.php?t=808707 which has the exact same problem as me... including what he said in his second post (the third post on the page) that nobody replied to. I used the same PC36IMG linked in that page, in fact. It loads the ZIP but then it goes back to the bootloader.
Click to expand...
Click to collapse
You need to flash a kernel, if you check netarchy's thread in my sig I believe there will be a link to the stock kernel in it.
Okay, how do I flash the kernel? When I tried last time, I couldn't connect to my phone via adb. And while trying to flash the stock ROM, it overwrote clockworkmod recovery, so now I just have normal recovery .
vonStemmington said:
Okay, how do I flash the kernel? When I tried last time, I couldn't connect to my phone via adb. And while trying to flash the stock ROM, it overwrote clockworkmod recovery, so now I just have normal recovery .
Click to expand...
Click to collapse
eww, ok. What does the first two lines in your hBoot say? Should be something like Supersonic Prod S-OFF or something like that
Supersonic EVT-2-3 Ship S-On
HBOOT-2.02 0000
I'm wondering why you still have S-on.
http://forum.xda-developers.com/showthread.php?t=829045
You need to have S-off in order to flash anything other than pc36img iirc.
I think S-on came back on after I tried to flash PC36IMG to get back to root. I've been flashing stuff all the time before, so S-on couldn't have been on..
Okay, if I take this to the Sprint Repair Centre in this condition, and say that HTC told me to use the HTC RUU installer, and this happened about midway through (pretty close to the truth) do you think they'll take it? I needed to take the phone back for a replacement anyway.
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.
I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)
if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.
The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck
If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot
What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.
nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code
illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error
The incredible will go into hboot but the recovery, factory reset, clear storage all send it into a boot loop. It is S-off and should have cwm (the root was done by unrevoked) but I cant get it into recovery mode to fix the problem. the up vol + power will cause it to vibrate 3 times but the screen stays black.
I am use to samsung phones where I can just odin it back to stock but have little experience with Htc. Any help on reverting it back to stock or just help me get into recovery so i can flash a custom rom would be great. thanks
btw
hboot is .92
Radio 2.15.00.07.28
If you are s-off I would first try reflashing cwm thru hboot as a PB31IMG.zip
Here is the CWM 5.0.2.0 PB31IMG.zip
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Just place it on the root of your sd and then boot into hboot (hold vol down and power) it should find the file and prompt you to press vol up to install. If that works then install the su binary found below thru recovery.
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
thanks for the quick reply after updating with the PB3 file it still wont go into recovery mode, just the boot loop. any other ideas?
I would say your next step would be to do an ruu of froyo 2.2 wich you can fiNd here http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip and if that dosent work I would try an ruu exe with your pc.
Thanks for your quick response, this phone is wack! I ran the ruu exe from my pc it did its thing and successfully updated the Rom but to my surprise when it rebooted it was stuck in a boot loop!
I had a similar problem a few days ago, and the only solution I found was to update CWM through RomManager. I'm thinking that the problem may have been caused by RomManager in the first place, which is why this is the only method that worked for getting CWM working.
You could try flashing an older version of cwm like 3.0.0.8 thru hboot. Mabey cwm 5 is whats causing your troubles. Or try flashing amon ra recovery.
Cwm 3.0.0.8
http://dinc.does-it.net/Recoveries/CWM_3.0.0.8/PB31IMG.zip
Amon_ra 3.02
http://dinc.does-it.net/Recoveries/AmonRA_3.02/PB31IMG.zip
I flashed both recovery's, also an ruu of a stock rom, and I also tried doing an ruu exe through the computer. all of them succeeded but in every case I am still stuck in a boot loop and cant get the phone to boot up
jordonlm1 said:
I flashed both recovery's, also an ruu of a stock rom, and I also tried doing an ruu exe through the computer. all of them succeeded but in every case I am still stuck in a boot loop and cant get the phone to boot up
Click to expand...
Click to collapse
Can you get into recovery yet or are the hboot options still not working?
Mabey your hboot got corrupted somehow you can try reflashing it.
hboot 0.92
http://dinc.does-it.net/Hboots/Hboot_0.92/PB31IMG.zip
Then try flashing a recovery again and see if you can get into it.
None of the hboot options work. I have flashed all the files you have given me. and I have done the ruu exe of both froyo and gingerbread. they all say they have completed successfully but nothing has fixed the problem. Still cant get into recovery and it wont but up at all. Im not sure what else it could be
Im not sure then if none of those options work im at a loss of what else you could do. Mabey someone with more experince can chime in with some other options. Have you tried reformating your sdcard or using a different one? Thats the only other thing I can think of.
jordonlm1 said:
None of the hboot options work. I have flashed all the files you have given me. and I have done the ruu exe of both froyo and gingerbread. they all say they have completed successfully but nothing has fixed the problem. Still cant get into recovery and it wont but up at all. Im not sure what else it could be
Click to expand...
Click to collapse
When you say "flashing" are you literally flashing these .zip files in CWM or are you renaming these files to PB31IMG.zip and installing thru HBOOT? There is a difference between the two.
Marcismo55 said:
When you say "flashing" are you literally flashing these .zip files in CWM or are you renaming these files to PB31IMG.zip and installing thru HBOOT? There is a difference between the two.
Click to expand...
Click to collapse
He cant get into recovery thats one of the issues.
ya i guess not flashing just running the PB31 file in hboot. I think im done working with it though. Im doing it for some guy who tried flashing it from verizon to another carrier but it didnt work and it only goes into hboot now. but thanks for all your help especially cmlusco. I'm still open for ideas but It's not going to my priority anymore. I learned a lot about htc phones if anything
cmlusco said:
He cant get into recovery thats one of the issues.
Click to expand...
Click to collapse
So the OP is S Off and can't flash the PB CWM file in HBOOT? Ccould be a bad file too. Make are you are checking md 5s
Sent from my Droid Incredible HD using Tapatalk
He can flash any PB31IMG file sucessfully but the phone will not boot and selecting any of the options in hboot leads him to a splash bootloop, and requires a battery pull. It's all above.
Marcismo55 said:
So the OP is S Off and can't flash the PB CWM file in HBOOT? Ccould be a bad file too. Make are you are checking md 5s
Ya it is s -off
I have flashed the pb CWM file no luck and also the other recovery (cant remember the name)
I also tried flashing th pb hboot file no luck
I flashed the pb ruu froyo no luck and also gb no luck
i then tried doing it through my computer using stock froyo exe and also a gb one with no luck (In every case the phone said it was "successful" in updating the roms and/or the recoverys)
But nothing ever changes it will only boot into hboot but nothing works in the hboot everything just sends it into a boot loop on the white htc screen
Click to expand...
Click to collapse
jordonlm1 said:
ya i guess not flashing just running the PB31 file in hboot. I think im done working with it though. Im doing it for some guy who tried flashing it from verizon to another carrier but it didnt work and it only goes into hboot now. but thanks for all your help especially cmlusco. I'm still open for ideas but It's not going to my priority anymore. I learned a lot about htc phones if anything
Click to expand...
Click to collapse
Thats probably the issue it was attempted to be switched to another carrier wich is a fairly complicated process. He may have changed some settings below rom level that cant be fixed by flashing an ruu. Im not sure if there is a fix with qpst or not but if there is I have no clue how to do it.
Been seeing some odd issues lately. I had a problem, and it would just go to a black screen and vibrate five times.
If the USB was plugged in to my PC, it would boot and operate fine, as soon as I unplugged it, it would crash again.
Check this out, it may be related.
http://forum.xda-developers.com/showthread.php?t=695243
I've been having almost this exact problem and have been working on it since 5:30 last night. As my phone is also my modem, I am currently at the library on wifi... FML.
The only difference is that I did not try to switch carriers, I was just using my phone normally and then yesterday morning I had a bunch of FCs, and yesterday evenings began the boot loops when I unlocked to make a phone call, again, FML.
The timing is very bad, only about two weeks till my new-every-two. Please help, I need my phone and don't really have the money to spare for a new one.
Thanks in advance.
Your pal,
-H
I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.