Related
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%.
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="][ Implementation ][/FONT][FONT="] 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
Hi guys just wondering if someone could maybe shed some light on my situation, Im trying to flash the latest european ruu 1.50 and when it gets as far as sending it, it gives me error saying i need the latest update utility. ive searched but cant find any help.
Regards Tony
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1228648
That is no help at all to the problem.
To the OP, reboot your phone into 'fastboot', connect to your PC and then run the RUU again. It should then work
Before you try it, though, what ROM are you currently running on?
Hi,
I'm trying to get a One S back to stock for a friend but failing...
The phone is unlocked, S-ON, hboot 1.14, 02_01 CID, has CWM recovery and rooted Cyanogenmod 10.1 installed, battery 100% and runs fine as is...
So, first of all I re-lock ready to run this RUU:
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed
but every time half way through it fails with the following errors in the attached screen shots...
A point to add is as soon as I re-lock the phone, it then will not boot but goes straight into hboot every time which I thought was strange..?
Anyway, some guidance would be very welcome to get this One S back to stock,
EDIT: Just flashed S4 Stock Recovery and the RUU still fails half way through, any ideas..?
Can anyone give me links to O2__01 HTC One S RUU files, can't find any live one anywhere..??
Thanks
Getting a RUU to run correctly is very hit and miss. The page below is a useful guide to double check the basics:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Post 9 details that with s-on you can't flash a RUU with a radio version older than the one you are on already. This may be your problem as I think your radio version will be 1.06 and the one in the RUU you are trying to run is 0.16. The problem with s-on is you can't flash radio's to do anything about that.
The RUU that should work is the one listed below, but I can't find any decent download links for it, like you said. Just try googling it and see if anything turns up.
RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed.exe
rosswhite said:
Getting a RUU to run correctly is very hit and miss. The page below is a useful guide to double check the basics:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Post 9 details that with s-on you can't flash a RUU with a radio version older than the one you are on already. This may be your problem as I think your radio version will be 1.06 and the one in the RUU you are trying to run is 0.16. The problem with s-on is you can't flash radio's to do anything about that.
The RUU that should work is the one listed below, but I can't find any decent download links for it, like you said. Just try googling it and see if anything turns up.
RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed.exe
Click to expand...
Click to collapse
Thanks rosswhite, I think you are right about the radio and no I can't find any download links that work either...
Another thought, does anyone have or know where to get a nandroid backup of O2_01..?
topcat888 said:
Thanks rosswhite, I think you are right about the radio and no I can't find any download links that work either...
Another thought, does anyone have or know where to get a nandroid backup of O2_01..?
Click to expand...
Click to collapse
Your other option of course is to S-OFF the device. You can then flash any radio or RUU you want.
Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.
Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita
So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.
Did you check the md5 of the recovery download?
Sent from my Evita
timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.