Related
Before I begin, I've read through a lot of threads on different forums and have yet to find a solution (that's working for me.)
I could never get my device to S-OFF so simply dropped the task. Not in too big of a rush right now. That being said, I'd like to go back to GB for a bit just to try a few things out.
I never flashed the ICS firmware, therefor I've had to use the old firmware patches. So, I tried running the RUU for GB and it only encountered error after error and my phone stayed at the black HTC screen. Any ideas?
Phone works just fine, just rebooted while I was typing this post and went straight into my ROM.
Only way I found is S-off'd, I had to go back to GB after ICS since it came on the phone I bought and needed to return it. Everyone told me I had to S-Off then RUU
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Abu-7abash said:
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You can't downgrade with s on....
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
ericsignals said:
You can't downgrade with s on....
Sent from my Rezound
Click to expand...
Click to collapse
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Pick a Gingerbread based rom and flash. Try out Chingy's Ineffabilis gingerbread.
Chyrux said:
I never flashed the ICS firmware, therefor I've had to use the old firmware patches.
Click to expand...
Click to collapse
Wish you guys would read.
Abu-7abash said:
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If you never ran an ics ruu you still were on gb firmware....so you can run a gb ruu. When you run the same ruu that's not downgrading....sheesh :rolleyes . And its probably the easiest way to get back to a working phone if you are lost and don't really know what you are doing.
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
Tried that. RUU said "Could not update your phone at this time."
I came from stock GB originally in...April. Is there a specific RUU for that?
I've never used RUU's before so I'm lost.
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
Still only a soft brick. Would suggest trying the other of the two GB RUU .exe version packages if you only tried one of them, just a suggestion until someone else can help you and diagnose.
http://forum.xda-developers.com/showthread.php?p=19756694
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
If you can get to hboot It's not bricked. Which ruu were you trying
pwned3 said:
If you can get to hboot It's not bricked. Which ruu were you trying
Click to expand...
Click to collapse
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed
Try running that one again. It should work. You have to run it twice anyway
pwned3 said:
Try running that one again. It should work. You have to run it twice anyway
Click to expand...
Click to collapse
Tried. It's stuck on the "Verifying the information on your PDA Phone...Please wait..." screen.
EDIT: Nevermind, went into Fastboot, working now. Let you know how it goes. Thanks for the help so far.
I'm getting a bootloader version error. An ICS RUU should fix this, right? Granted, I know that means I can't go back until I S-Off, but I'd rather that than have a soft bricked phone
I am in the same boat - S-ON. I flashed Scott's ICS Rooted Stock Rom, along with the GB Patch. I downloaded the PH98IMG.zip and HBOOT doesn't recognize it. Trying the exe may resolve this?
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Chyrux said:
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
print.logic said:
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
Click to expand...
Click to collapse
With the new leak out, I haven't. However, I can still help.
Make sure there is no P98IMG file on your SD card.
1. Download the mainver fix from this post http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
2. Drop GB ROM of your choice onto SD card.
3. Flash the fix in recovery and reboot into bootloader.
4. Relock your phone by going into adb and typing in fastboot oem lock
5. Run GB RUU of your choice.
6. Use the HTCDev unlock on your bootloader
7. Download a recovery and push it to your phone by typing in fastboot flash recovery recovery.img
8. Boot into recovery, flash ROM, enjoy.
I'm trying to help a buddy of mine. He has a Thunderbolt, issued through work. It is stock, unrooted, locked, never modded. He recently got the ICS OTA update. Phone was functional, but laggy and a bit unstable. He did a factory reset, and initially the phone was fine for a few hours, then it was acting buggy. After a reboot it was fine for a bit, then froze. Usable time kept diminishing with subsequent reboots. He tried another factory reset, and the phone won't boot now. If you power it up, you get the white screen with the HTC logo, then a black screen, and nothing ever happens. I can get to Hboot. I can get to fastboot. Not sure if recovery does anything. I get the recovery screen, then a reboot, and then nothing.
I've been trying to read up on how to fix this, and I'm not sure how to go about it since the phone is currently locked, and won't boot. I looked at the Thunderbolt All In One tool, but it looks like it needs the phone to be booted to start the process.
My end goal is to get back to stock, unrooted, (Gingerbread, then OTA update I suppose), and S-on. But to do that, I need to obtain s-off first. Any info would be greatly appreciated.
I've attached a couple of pics.
Thank you.
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
cujo6801 said:
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
Click to expand...
Click to collapse
Good to know. Thank you. I think because it was employer issued, he's going to try to get a newer device if we can't get it running. But I just had to make some attempt to get it running.
Pm disconnecktie as you should be able to flash via abd beings you can get in to fastboot. He knows a lot about the workings of these phones.
Sent from my ADR6425LVW using Tapatalk 2
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Fastboot does work. I was able to do the "fastboot devices" command before, and saw the phone. I was also able to "fastboot flash zip" the file from post 12 from this tread (link below), BUT even though the file transferred from the computer to the phone, the actual flash failed... I'm assuming because the phone is locked.
http://forum.xda-developers.com/showthread.php?t=2120985&page=2
Try downloading the official ota zip over at the developer section. Put it on the root of your sd card and rename it to PG05IMG. Then run the update through fastboot. I seriously doubt this will solve the problem long term but it may work. I have doubts. I am beginning to think htc released the ota purely for development purposes. More and more people are popping in here with problems similar to this.
Sent from my ADR6400L using Tapatalk 2
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
SoundTech said:
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
Click to expand...
Click to collapse
You need to be rooted to use a rom
Sent from my Nexus 7 using Tapatalk 2
Yeah, that wasn't too swift of me, was it now?
I grabbed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2144326
Tried Hboot with the file renamed, same results as previous post. Tried fastboot flash zip, same results as above. No joy.
Going to try to see if HTCDev will get the bootloader unlocked in the current phone state.
Well since the ota isn't a downgrade I thought it may work. If HTC dev is able to unlock his bootloader maybe he can get further.
Sent from my personally built from source CM10.1 N7.
Bootloader is unlocked now, since it was all through fastboot. Still S-on. Tried with the OTA zip still on the SD card as "PG05IMG.zip." It loaded, started to check, started to parse for a moment, then went back to the Hboot screen, reboot got me nowhere. I need to go deal with the rest of life now. I'll try again tomorrow. I appreciate everyone's help today. Thank you.
At this point just s off and install a recovery then you can flash that ROM.
Sent from my Nexus 7 using Tapatalk 2
Use this guide here. Make sure you have plenty of time before hand and FOLLOW THE DIRECTIONS IN ORDER TO A T. It is very important that you don't skip over stuff. This is the only current method to get s off with ics.
Sent from my ADR6400L using Tapatalk 2
Long day at work, but back to it. Making sure the battery is charged up, and downloading files.
I'm looking at a post on ThunderboltForums. Making absolutely sure here: Is THAT the one I should be following?
Follow-up: At the end of step 28, after flashing the .19 ROM, is says to use the All-In-One tool. IF I plan to be stock, unrooted, locked, S-on, it seems I'm there at this point, and I can let the OTA update run. Is that correct?
Thanks again.
Looks like I'm on stock Gingerbread, S-off, re-locked, stock recovery. Heck, it finally boots! I'll see about trying OTA update tomorrow.
Thanks again.
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Huh. I never did use the tool. I went through the steps on the ThunderboltForums post all the way through flashing the .19 ROM. Unless I missed something or did something wrong, before the flash it said I would be re-locked and S-on. After the flash it said the phone should be "back to normal". The next step was the All-In-One tool. But the device actually booted into android with the .19 ROM. That was the first time I saw it boot since I got my hands on it. Perhaps the process in that thread helped repair whatever part of the system was buggered up to begin with?
Regardless, I tried the OTA update, and the phone took the ICS update through Verizon. It seems to be running better now than it did before. It's back in my buddy's possession, and he's in the process of getting his apps and data reinstalled.
He thanked me profusely for getting it running again. So I, in turn, pass his thanks on to everyone here that helped me out, the people that worked to get the Thunderbolt resources to where they are now, and to the forum in general for existing and doing what it does. Thank you all.
Hello, I desperately would like to see how to put my HTC Amaze back to stock. A couple of months ago I tried putting it back to stock because the energy rom kept rebooting on me and draining my battery life randomly. Anyways I was not successful and so I just kept the rom and the rebooting problems stopped anyways. Now, its happening again and I would really love for some one to help me get it back to stock so I can see if it improves and maybe get the thing S-OFF later. I am with Wind mobile.
Any help is greatly appreciated,
A frustrated amaze user.
rspierz said:
Hello, I desperately would like to see how to put my HTC Amaze back to stock. A couple of months ago I tried putting it back to stock because the energy rom kept rebooting on me and draining my battery life randomly. Anyways I was not successful and so I just kept the rom and the rebooting problems stopped anyways. Now, its happening again and I would really love for some one to help me get it back to stock so I can see if it improves and maybe get the thing S-OFF later. I am with Wind mobile.
Any help is greatly appreciated,
A frustrated amaze user.
Click to expand...
Click to collapse
Well since you're s on lock your bootloader and flash a wind ruu from bootloader you can find the necessary thread in development section
Sent from my HTC_Amaze_4G using xda premium
ravike14 said:
Well since you're s on lock your bootloader and flash a wind ruu from bootloader you can find the necessary thread in development section
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Hey thanks for the response. So I locked the bootloader and then got the wind RUU renamed it as PH85img.zip or w/e its supposed to be. And now when in the boot screen it cannot find my file I then tried another RUU but this time is used the exe wind one but that one failed as well and came up as an error saying the hboot version is older then what im flashing or something?
So I am stuck at this point. Do you know how to get around this?
Make sure the ruu is on the root of the sd card
Sent from my SGH-T999 using Tapatalk 2
rspierz said:
Hey thanks for the response. So I locked the bootloader and then got the wind RUU renamed it as PH85img.zip or w/e its supposed to be. And now when in the boot screen it cannot find my file I then tried another RUU but this time is used the exe wind one but that one failed as well and came up as an error saying the hboot version is older then what im flashing or something?
So I am stuck at this point. Do you know how to get around this?
Click to expand...
Click to collapse
well you cant flash a exe you have to connect your phone to the pc and run the exe from pc and bout the hboot whats your current version? :/
ravike14 said:
well you cant flash a exe you have to connect your phone to the pc and run the exe from pc and bout the hboot whats your current version? :/
Click to expand...
Click to collapse
Yeah it was connected via usb. I got somewhere, now but im am hoping you can tell me what i need to do now. I followed the second post here : http://forum.xda-developers.com/showthread.php?t=2167596 and now I have GB rom on my phone running unlocked. What do I need to do from here so I can S-off and super CID? PS I tried doing an OTA update from the phone and it wont work.
Looking into the S-off guide it says i must be on a stock RUU. is the one i got install a stock RUU. Also my hboot version is 1.93.0002 (Mar 15 2012) which is ice cream sandwich according to the Unlimited.IO site, but the RUU im on is definitely gingerbread. What can I do about this?
rspierz said:
Looking into the S-off guide it says i must be on a stock RUU. is the one i got install a stock RUU. Also my hboot version is 1.93.0002 (Mar 15 2012) which is ice cream sandwich according to the Unlimited.IO site, but the RUU im on is definitely gingerbread. What can I do about this?
Click to expand...
Click to collapse
What is your android version in settings?? Cuz what your telling is kinda weird
Sent from my HTC_Amaze_4G using xda premium
Adroid Version: 2.3.4
HTC Sense version: 3.0
Software number 1.43.531.3
am I completely screwed now? Cause it seems i wont be able to get S-off or CID off while not on this unsigned rom (t-mobile), i am with Wind. The OTA does not work while on the phone (settings > software update). Would locking my bootloader and then loading the latest OTA zip from wind on the SD card work? I am very stuck!
rspierz said:
am I completely screwed now? Cause it seems i wont be able to get S-off or CID off while not on this unsigned rom (t-mobile), i am with Wind. The OTA does not work while on the phone (settings > software update). Would locking my bootloader and then loading the latest OTA zip from wind on the SD card work? I am very stuck!
Click to expand...
Click to collapse
well you have ginger bread so try the jbear GB s off tool in ubuntu
but what about the hboot version being ICS? Do you think it should still work?
rspierz said:
but what about the hboot version being ICS? Do you think it should still work?
Click to expand...
Click to collapse
what bout your CID?
I havent done anything to the CID, so I believe it is still locked to wind?
rspierz said:
I havent done anything to the CID, so I believe it is still locked to wind?
Click to expand...
Click to collapse
well choice is yours your android version says GB hboot says ICS :/ i say try the GB s-off tool but do at your own risk...
well S-Off worked so thats good haha. Now i am trying to super CID. However, when uploading the proper hboot for doing so it wont let me because of the CID.
Ignore that last post. I figured it out so all is good. Now here is another question, should i flash CM10.1 or your rom that viper one? How would I go about flashing a rom. I remembered before you would just go into recovery and then format all execpt sd card and then install from zip. I tried that with the CM10.1 rom and when I rebooted it did not work.
went ahead and tried installing the Viper rom and after i reboot (when it said all was good) it show a black screen with green arrows. And its stuck on that. I do not know what to do now. Because I should have everything open. Was I supposed to flash something after doing the S-OFF?
This is what I am getting stuck on. I tried another rom too, same thing. I can boot into 4ext. But cant get past this on boot up.
rspierz said:
This is what I am getting stuck on. I tried another rom too, same thing. I can boot into 4ext. But cant get past this on boot up.
Click to expand...
Click to collapse
Now your s off BUT you have gb firmware so you have to flash a ruu 1st then flash a recovery then supersu or just flash any rom you want if you decide to stay with the ruu stock rom to gain root permission flash supersu
Sent from my HTC_Amaze_4G using xda premium
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
My LTE took a dump the other day. Started overheating like crazy, despite no changes.
Was running cynagenmod 10.2 and it was working well. S-Off HBOOT 2.09.4444, Radio 1.12.11.1119
Then these overheats kept going all day until I turned it off. Then started bootlooping, would fully launch one out of 10 times.
So I wiped using TWRP and gave that a try, no luck, still overheating and bootlooping.
So I wiped and restored a TWRP backup, nothing... the stock rom is bootlooping even harder than before and never fully launches now.
It got to the point TWRP wouldn't launch until I had to put a fresh version on the SD card.
Tried to install the newest stable CM10.2 image and as before locking up at boot splash screen of the rom after HTC "quietly brilliant" and looping.
So now I am stuck, downloaded the stock RUU from HTC website, however the devices needs to be recognized to use their exe.
Is there an image I can throw on the SD card and use TWRP to try a flash from that? Any other recommendations?
TIA.
syl2us said:
My LTE took a dump the other day. Started overheating like crazy, despite no changes.
Was running cynagenmod 10.2 and it was working well. S-Off HBOOT 2.09.4444, Radio 1.12.11.1119
Then these overheats kept going all day until I turned it off. Then started bootlooping, would fully launch one out of 10 times.
So I wiped using TWRP and gave that a try, no luck, still overheating and bootlooping.
So I wiped and restored a TWRP backup, nothing... the stock rom is bootlooping even harder than before and never fully launches now.
It got to the point TWRP wouldn't launch until I had to put a fresh version on the SD card.
Tried to install the newest stable CM10.2 image and as before locking up at boot splash screen of the rom after HTC "quietly brilliant" and looping.
So now I am stuck, downloaded the stock RUU from HTC website, however the devices needs to be recognized to use their exe.
Is there an image I can throw on the SD card and use TWRP to try a flash from that? Any other recommendations?
TIA.
Click to expand...
Click to collapse
What are you trying to achieve? Do you need an alternative RUU flash or find a new ROM so you won't get bootloops and heating?
I suggest going on CM11 or resort to Meanbean for stock sense 4.
If you're running a RUU I suggest using this method here.
http://forum.xda-developers.com/showthread.php?p=50523371
But before that please read the first 4 posts of this thread (especially Q&A) to get you updated on what's going on with the newest RUU.
http://forum.xda-developers.com/showthread.php?t=2639180
More questions? Just ask me.
Sent from my EVO using Tapatalk
lreyes said:
What are you trying to achieve? Do you need an alternative RUU flash or find a new ROM so you won't get bootloops and heating?
I suggest going on CM11 or resort to Meanbean for stock sense 4.
If you're running a RUU I suggest using this method here.
http://forum.xda-developers.com/showthread.php?p=50523371
But before that please read the first 4 posts of this thread (especially Q&A) to get you updated on what's going on with the newest RUU.
http://forum.xda-developers.com/showthread.php?t=2639180
More questions? Just ask me.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I am trying to get this phone into any working order if I can. I have reason to believe the hardware has been affected by the overheating. I need to get it to fully launch before I can declare that, so anything to stop it from bootlooping is what I am trying to achieve. Occasionally, when it would fully launch, I noticed none of the radios worked, no mobile data, no WiFi and no Bluetooth which were previously functioning fine.
The links are down to the two files needed in the first post you're referencing.
I believe my partitions are out of whack and need to be fixed. Everything I am seeing to repair partitions is while the phone can boot, can someone point me to some info that shows how to fix partitions while only recovery is achievable? Maybe I am going about this wrong, search not returning the results needed.
TIA
You can RUU from the bootloader, without having to be booted to the OS. I can confirm this works on both the 3.17 RUU and the latest 4.13 RUU, which I have both used. Make sure you have HTC Sync involved and use a Windows 7 machine and you shouldn't have any issues.
Sent from my EVO LTE
FinZ28 said:
You can RUU from the bootloader, without having to be booted to the OS. I can confirm this works on both the 3.17 RUU and the latest 4.13 RUU, which I have both used. Make sure you have HTC Sync involved and use a Windows 7 machine and you shouldn't have any issues.
Sent from my EVO LTE
Click to expand...
Click to collapse
You're saying you were able to get it recognized during Bootloader USB? The RUU will not recognize the device for me this way.
Yep, worked just fine connected via Fastboot USB mode.
Sent from my EVO LTE
FinZ28 said:
Yep, worked just fine connected via Fastboot USB mode.
Sent from my EVO LTE
Click to expand...
Click to collapse
Hmm, tried this on Win8, I'll give 7 a shot, thanks for the heads up!
How do I ensure my partitions are in proper order? Often when in TWRP and trying to run common commands, I get SD card unmountable and noticed what seems like multiple SD card nomenclature.