Database Info

Help Please - Magic 32a stuck in RUU mode

Hi Guys,
Finally after playing with a lot of roms I decided to go back to stock. I was flashing back to stock using the RUU exe from HTC and something went wrong. Phone is now stuck in RUU mode whenever you turn on. Have access to fastboot but when I try to boot recovery etc getting remote not allowed. Any suggestions other then paying $450 aus for new board?
Thanks

well if you got fastboot then you got hboot. which is good. i am pretty sure you can run a stock .nbh and get reverted allllll the way back to total stock just like removing root. im not to sure but look into those options. if you can do that then you should be able to reroot and not have a $450 shinny brick. i bet someone will respond with a better answer after this is posted lol!

I don't know if this is a standard solution, however I had the same problem for the past few day, and I tried everything and as I am updating from HTC RUU I held the action ( track ball ) button pressed and it did the upgrading . . . I'm not going to try again, but that is what happened.
Hope that helps.
Cheers,
Andre

PLEASE Help - I think i bricked my phone. [SOLVED]

Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg

I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck

Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?

MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access

kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks

ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.

kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.

ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?

kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks

ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).

kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?

While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.

Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks

...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?

Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"

eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?

And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)

OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.

Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers

BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.

Dead sensation

Been trying to port miui to sensation.
At first it was good, booted up into miui, lot's of staff crashing and ****.
Then I thought I would port from G2X. Went through the kitchen and exported zip.
Flashed, it went rather quickly. Rebooted and nothing comes up. No light, no bootloader. Even led is off.
What the heck?
With it connected to computer throught usb cable, it detects QHSUSB_DLOAD device but no drivers
Can't get into bootloader
Can't see device from adb
Only detected device when plugged in is QHSUSB_DLOAD​

Ugh crap. I think I installed rom with boot.img from G2X
:| *facepalm*
I guess boot section is now effed? :\

Do I guess adb reboot won't help ?

awdlexusis said:
Do I guess adb reboot won't help ?
Click to expand...
Click to collapse
adb doesnt detect any devices.
I think I might have bricked the device with wrong boot.img (from G2X)
Problem: I had S-OFF so replacement/warranty is void

If I could find Qualcom HSUSB driver I could try flashing native bootloader, but yet I can't find drivers :|
Found 9008 driver, doesnt work :|
Would flashing bootloader help tho?
Added:
Please tell me /dev/block/mmcblk0p1 was a bootloader and s-off evidence is gone :|

I did something similar to what you did. I have not restored my Sensation, however, I do have the 64bit drivers. I've attached them. If you can tell me where to get and how to flash the native bootloader, I would be eternally grateful. I am willing to try anything. Altho, I have to admit, I'm not sure how it would be possible to reflash ANYTHING considering ADB can't see the phone...
On a side note, if the phone can't be turned on, then I don't think anyone would know it was rooted. I'm pretty sure HTC will just reflash the EMMC and send it off again as a refurb. I've already ordered a replacement from T-Mobile...

DarkShim said:
I did something similar to what you did. I have not restored my Sensation, however, I do have the 64bit drivers. I've attached them. If you can tell me where to get and how to flash the native bootloader, I would be eternally grateful. I am willing to try anything. Altho, I have to admit, I'm not sure how it would be possible to reflash ANYTHING considering ADB can't see the phone...
On a side note, if the phone can't be turned on, then I don't think anyone would know it was rooted. I'm pretty sure HTC will just reflash the EMMC and send it off again as a refurb. I've already ordered a replacement from T-Mobile...
Click to expand...
Click to collapse
I have two more sensations. SO I could backup them and restore on mine.
Had to do this with htc magic a while back.
But having hard time installing drivers. I might just get replacement.

I'm not really sure why you're having a hard time installing drivers... They loaded perfectly for me first time I tried.
Still, can you tell me what I need to do to reflash the phone's bootloader?

I can give you some half good news.
Having an engs-off demo phone and testing recoveries/roms etc before alpha rev I got used to bricking and restoring the device.
On the day alpha-rev came out I bricked my s-on unit in similar circumstances to you (no charge light, screen, fastboot, recovery etc) only a USB device without drivers (same as yours but with HEX after).
Sent it for repair claiming an OTA had bricked it. HTC replaced the phone.
Seems that if you are going to brick an s-off phone its best to super-brick it so they can't see what you have done!

jM2.me said:
Ugh crap. I think I installed rom with boot.img from G2X
:| *facepalm*
I guess boot section is now effed? :\
Click to expand...
Click to collapse
boot.img is not your bootloader. Bootloader file will be hboot_x.xxxx.nb0. Boot.img is part of your boot sector for your ROM.
You should still be able to get into bootloader with the wrong boot.img. Did you leave an hboot file in there also?

WiFi error's after flashing HTC unlock bootloader

Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.

droiddv said:
Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.
Click to expand...
Click to collapse
Personally i would just do the normal s-off method as it gives you a little more freedom compared to HTC unlocking method.
My wifi is dead too, but i have no way of fixing it at all, i've got a thread called "wifi is dead" in the q+a section of the sensation forum.
Let me know if you get yours working, i imagine that if you revert your phone back to stock again and then use the alpha rev method that you will have better luck.

1. You can Relock your bootloader using HTC site but this time u will see Relocked instead of Locked
2. No idea
3. Did you try resetting your router? Works for me. Also try flashing a different radio.
4. No idea
5. You can relock bootloader on HTC site but have no idea of you can unlock it with Revolutionary again.

Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo.
Sent from my HTC Sensation Z710e using XDA App

tinky1 said:
Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo again. You might need eng s-off, pm EddyOS, he should be able to help, I believe he's done it before.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Sent from my HTC Sensation Z710e using XDA App

[ Solved ] WiFi error , Radio flash Problem , and revert back to any Custom Rom
droiddv said:
Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON (security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
.
Click to expand...
Click to collapse
[Solved ] WiFi error , Flash Radio Problem , Install any Custom Rom without errors , Wrong S-on Brick
this is Solved and the wifi error is because of kernel included in Boot.img
you can use the following solution to install any custom rom without wifi errors
first read " how htc dev works " to have an understanding why this happened to you and why you are still S-on and why you can't flash Radio . link is here " Solve WiFi Errors , Radio Flashing Problem , Caused by htc Dev Unlock Method "
the solution itself is in the following link , Read title " Custom Rom Flash " and "[FONT=&quot][ Implementation ][/FONT][FONT=&quot] Successful S-OFF using my above method " . [/FONT]link is here " Successful S-OFF after brick (wrong S-ON) for ICS or GB , Downgrade OTA firmware "
this also solve wrong S-on Brick , hope that helps
Press the thanks Button for this Post

htc sensation z710e rom installation problem?

so i got a htc sensation z710e and works fine, network unlocked.
i have a smart watch but the thing wont work on ics ONLY above so i decided to stick a custom rom on to bring me up to the required android version to use said watch.
my phone has the 127.000 hbooot and it says s on but unlocked above in pink after i ran windroid and unlocked bootloader, it also had root and cm recovery 5.2.0.2 or watever number it was.
so on i went to try and install a custom rom. 1st i did cm-9.1.0-pyramid and it just hung on the cm9 boot up screen THEN i did cm-12-20141205-UNOFFICIAL-pyramid and it goot error 0 so never did nothing. and lastly i tried revolution 1.03 and it was promising went thru all the installation buff and jargon and then same again just hangs on the htc boot logo.
before i install zip files i wipe dalvaik. battery and data i think its called.
i can still get into recovery and hboot but cannot for the life of me get a rom to boot and tbh its draining the life out of me as i havent done a android in yrs.
tried looking for odin and download mode but im unsure if htc has them?
p.s just tried a factory wipe and still the same. hanging at the htc screen.
and advice would be great as i REALLY dont wanna tell the wife i need another 50 qwid for a new phone. she wont be chuffed.
cheers.
UPDATE-- managed to install-rmk-pyramid-stock_ics_3.32.401.3-v1 all working,well apart from no bloody wifi!!. known fault?
so now i think i will have to gain s-off and then move on,,, ??
UPDATE-- managed to gain s-off and that seemed to fix the no wifi? ha,,,, but i had to re unlock the bootloader, also got supser cid
so now im s-off with unlocked bootloader and looking for jelly bean, i think ima go with http://cm-10.2-20131028-albinoman887-pyramid.zip/
hopefully il just eed to exit into recovery and flash and il be golden.... kinda glad nobody replied as it made me batter my own mind working it out

hi, it didnt boot before when u were s-on because u need to flash the boot.img after u flashed the rom. but u got sorted in the end. :thumbup: