Related
Been lurking for sometime learning things here and there, but now I've got an issue of my own I been pulling hair out over for the last 6 hrs.
I Upgraded to 2.11.605.9 Verizon OTA release today... attempted to use the revolutionary tool to re-root after the upgrade. Well that didn't work. I just get the message "Zerging Root... this might take a minute or so.. Failed to get Root! "
I have tried http://forum.xda-developers.com/showthread.php?t=1009423 the non root users section. With no luck.
Pretty new at this stuff, so if someone can let me if its possible to get s-off, i'd just like to downgrade to an earlier pg05img and NOT get the latest update So i can use revolutionary root.
Thanks in advance.
Nick
Try this..
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
CaptainStrange said:
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
Click to expand...
Click to collapse
I've rooted multiple times using the method above, but since the update, I can't get past the Zerging Root step, even following the posts from the first link you sent
Flashed the Pg image using .androidpolice.com/2011/10/24/exclusive-gingerbread-build-2-11-605-5-for-the-htc-thunderbolt-fixes-several-issues-from-the-previous-leak/[/url] and it works, I was able to re-root using the rev.
Capt....
I am having the same problem as him. After I got this warranty replacement yesterday, no matter what I tried, I can't get past "zerging root". Cannot gain root access. I see you said to flash that image, but how do you do that if you cannot get s-off. I have also rooted thunderbolt several times using the "one click method" (which is also not working for this new 2.11. 605.9 build) and revolutionary. Any suggestions or instructions?
You dont need S-off to load that image... Simply download the file and rename it pg05img.zip and put it on the root of your SD card. Reboot the phone and hold down the vol down + power button to access the bootloader, push the volume button and it will search the sd card for the pg05img.zip file and load it. Just keep in mind it will reload it to factory settings, so back anything up that you have. It takes about 15 mins, but it does work. Once you have that image loaded from the link above you can use the revolutionary root. Let me know if you need help.
Rooting after 2.11.605.9 on TB solution
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING
So if I unroot and my phone takes the latest 2.11.605..9 update, all I have to do is flash the 2.11.605.5 RUU, put phone into airplane mode as soon as it boots, then I can root again?
I am not sure if I missed something but I followed those steps. When I went into boot, it said my version is "older- failed" and won't revert to the .5
I am miserable here with stock. I want to be rooted again.
Any thing else I can do?
Not sure why it wouldn't let you revert to an earlier RUU. Have you tried other earlier versions other than .5? The RUU I used was 2.11.605.3. Try that one. What version bootloader do you have? Also is there Pink letter at the top that says LOCKED?
I have not tried an earlier version... Yet. Will try and will update you. But the bootloader says "***locked***" s-on on the main screen. So I am not sure any older one will work. I read other people were able to accept a downgrade so I am hopeful.
Bootloader 1.5 and yes... It is ***locked*** sigh...
Try loading the 2.11.605.3 If it works just make sure you disable wireless connections when it boots, so OTA doesn't push the upgrade
Even if the OTA comes up before you disable any wireless connection it will download the OTA but then ask if you want to accept or defer. Just hit defer and proceed with the Revolutionary method to root and gain s-off.
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Ok guys hold on now, this is kind of misleaing... so did the OP have s-off for the downgrade ? Revolutionary has a password protected HBOOT that was designed to maintain s-off during an OTA or upgrade RUU, hence the reason a downgrade would be possible... Is the OP able to confirm they had S-OFF during the upgrade or S-ON. If i upgrade to 2.11.605.9 on a stock phone S-ON, am i going to be able to downgrade with ease ? I would say no.. not without tricking the bootloader into thinking its an older version which is what the commands are for:
adb push misc.img /data/local/
adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
However you can't do this without a temporary root shell.
on build 2.11.605.9 there is no exploit for temporary root shell currently..
Please clarify.. ?
rberry88 said:
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Click to expand...
Click to collapse
No matter how far out you pick, the limit is 5 days. Picking anything longer, the phone will tell you that.
Like I was saying before the OTA came out, this OTA patches zergRush.
Bootloader has always been locked, this is not new.
I have a few vulns found, and erishasnobattery and I have a couple working exploits done.
However I am on vacation and wont be home until late tonight, once I am we will get something packaged and released for root.
Until then (this isn't the one we are going to release)
Awesome, i just bought my wife a t-bolt Friday and it did an OTA (that i just assumed was the same old gingerbread update that my buddy got but apparently it wasn't because i could not root. Thanks jcase for working on this for us.
I was able to get root with 2.11.605.9
I was already on 2.11.605.5 with root and S-OFF (revolutionary). Perhaps you can try one of the earlier releases such as MR2? This is what you do to get root with 2.11.605.9 if you can get your phone back to 2.11.605.5 or older:
1. Reinstall 2.11.605.5 stock (no root). I got the file from Android Police. I had to rename the file as PG05IMG.zip and run it from the bootloader.
2. Obtain S-OFF with Revolutionary after 2.11.605.5 has installed. Do not install clockworkmod or super user yet.
3. Allow the 2.11.605.9 OTA to be installed. Let the phone do it's thing, the update took my phone awhile.
4. Install Clockwork Recovery (again rename it as PG05IMG.zip and run it from the bootloader)
5. Boot into bootloader again and select Recovery. Install superuser.
6. Reboot and enjoy.
PS. I stumbled upon this on another thread here.
So I'm on a new phone that just did the .9 update about 10 minutes ago and then I find this thread after failing to root. So I'm s on stock everything. I can't revert can I? I'm screwed. I hate stock phones. Adds everywhere. No tether boring no options. I want my skyraider back.
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
bri.kwong94 said:
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
Click to expand...
Click to collapse
Well you are on T-mobile so you have two choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then re-unlock again. but remember flashign this without s-off may prevent you from getting s-off later on.
Ray196 said:
Well you are on T-mobile so you have to choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then reunlock again.
Click to expand...
Click to collapse
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
bri.kwong94 said:
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
Click to expand...
Click to collapse
you can if you lock your boot loader and revert the phone to stock.
Ray196 said:
you can if you lock your boot loader and revert the phone to stock.
Click to expand...
Click to collapse
Well, how do i revert it to stock and reroot it exactly?
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
i think you can use this. http://forum.xda-developers.com/showthread.php?t=1493905
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
Pretty sure you just use fastboot to lock, open a command prompt with your phone attached in debugging mode, type in fastboot oem lock, then install the stock rom listed in the development section. (If I am wrong on this, someone please feel free to correct me.)
I have a rooted Rezound running the OTA ICS. I also have Amon Ra recovery. The newest Firmware update keeps downloading. Once it does the phone shuts off and goes straight to Amon Ra which does not install new firmware. So I reboot the phone and the download process starts all over again. Is there any way to get this new firmware with having to factory reset? Thanks in advance!
xCOOLHWIPx said:
I have a rooted Rezound running the OTA ICS. I also have Amon Ra recovery. The newest Firmware update keeps downloading. Once it does the phone shuts off and goes straight to Amon Ra which does not install new firmware. So I reboot the phone and the download process starts all over again. Is there any way to get this new firmware with having to factory reset? Thanks in advance!
Click to expand...
Click to collapse
If you want the OTA to go you need to flash stock recovery.
- "Is it dark in there?"
drynyks said:
If you want the OTA to go you need to flash stock recovery.
- "Is it dark in there?"
Click to expand...
Click to collapse
Thanks. I was hoping that wouldn't be the case. Do you know of anyway of getting rid of the update? I would rather not have the update than flash back to stock. But my phone shutting off every few hours is pretty annoying. Thanks again.
xCOOLHWIPx said:
Thanks. I was hoping that wouldn't be the case. Do you know of anyway of getting rid of the update? I would rather not have the update than flash back to stock. But my phone shutting off every few hours is pretty annoying. Thanks again.
Click to expand...
Click to collapse
Remove otacerts... Don't remember the exact location and I'm on my phone, a search on that should turn it up.
Sent from my ADR6425LVW using Tapatalk 2
mjones73 said:
Remove otacerts... Don't remember the exact location and I'm on my phone, a search on that should turn it up.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
\etc\security\otacerts.zip
same problem here
hgoldner said:
\etc\security\otacerts.zip
Click to expand...
Click to collapse
I cant seem to find the otacert on my htc resound. I have tried every way to update the new radios and nothing works. I have tried everything but a hard reset and relocking the bootloader. I would rather shut the stupid auto update off. My phone resets at 12:30 am and again at 4am. considering I need the alarm clock on my phone it renders it useless. Any help is appreciated. I am Rooted running stock OTA ICS with Amon Ra.
xander5680 said:
I cant seem to find the otacert on my htc resound. I have tried every way to update the new radios and nothing works. I have tried everything but a hard reset and relocking the bootloader. I would rather shut the stupid auto update off. My phone resets at 12:30 am and again at 4am. considering I need the alarm clock on my phone it renders it useless. Any help is appreciated. I am Rooted running stock OTA ICS with Amon Ra.
Click to expand...
Click to collapse
In confused why don't you just flash stock recovery and let the OTA go? Problem solved. Oh you'd have to relock also.
drynyks said:
In confused why don't you just flash stock recovery and let the OTA go? Problem solved. Oh you'd have to relock also.
Click to expand...
Click to collapse
I have relocked the bootloaderb and gone back to stock 605.12 now it won't download the ota updates. I'm a little stuck on this one
xander5680 said:
I have relocked the bootloaderb and gone back to stock 605.12 now it won't download the ota updates. I'm a little stuck on this one
Click to expand...
Click to collapse
Are you going to settings> software update> check new?
From 605.12 you should get a small OTA first then the big one after that one is done. I just did same procedure in the last week on my wife's phone.
Btw might want to be on WiFi if you aren't already for the download.
Having the same issue here as OP and been searching forums for days looking for help...
First, I'm on 605.13 already, stock ROM, rooted with Amon ra. I realize the steps I need to take but can't find any specifics.
Could someone please spell out the specifics of how to flash the stock recovery, and if I can use the 605.12 RUU to do this being on .13 already. I keep seeing others posting about just renaming a file to recovery.img and pushing using fastboot, but I'm not sure how to obtain the correct file.
Do you relock bootloader first or flash stock recovery first and the relock? BTW I'm s-on stil. Thanks in advance
drynyks said:
Are you going to settings> software update> check new?
From 605.12 you should get a small OTA first then the big one after that one is done. I just did same procedure in the last week on my wife's phone.
Btw might want to be on WiFi if you aren't already for the download.
Click to expand...
Click to collapse
I have tried your suggestions. It goes to download the small update and never downloads it. It says unable to download after about 3minutes.
fixed
xander5680 said:
I have tried your suggestions. It goes to download the small update and never downloads it. It says unable to download after about 3minutes.
Click to expand...
Click to collapse
For some apparent reason the 605.13 update downloaded this afternoon and the 605.14 updated. Its all set after a frustrating 2 weeks of digital torture. thanks to all that helped. I had to scour all these resources and forums to get this done but this is what worked for me. I relocked the bootloader then I used the 605.12 RRU.exe program. After about a day I checked for the updates and they downloaded and installed successfully.
Xander, since you just got this working, can you please confirm the process - I'm about to do this myself and want to verify the steps...
1) Reboot into hboot > fastboot and relock bootloader via fastboot oem lock
2) download 3.14.605.12 RUU.exe (I'm currently on 3.14.605.13)
3) Reboot phone into hboot > fastboot usb
4) run RUU.exe from PC
Is that it? Anything I'm missing here or am I on the right path?
mattman37 said:
Xander, since you just got this working, can you please confirm the process - I'm about to do this myself and want to verify the steps...
1) Reboot into hboot > fastboot and relock bootloader via fastboot oem lock
2) download 3.14.605.12 RUU.exe (I'm currently on 3.14.605.13)
3) Reboot phone into hboot > fastboot usb
4) run RUU.exe from PC
Is that it? Anything I'm missing here or am I on the right path?
Click to expand...
Click to collapse
U have step 1 and step 2 correct. Step 3 would be to connect the phone to the computer and run the 605.12 ruu.exe tool. After that u are now back to a stock phone. After the initial setup of adding your gmail account and contacts you can now go into system settings and check for update. As I stated before my phone would not download the update for some odd reason. I tried it a couple more times without success. Today on a whim I went to check for the update again and it started to download. After the small 6mb file was complete the next update for 605.14 downloaded without anny issues. Make sure you delete any zip files off your external SD card labeled ph98img.zip if u tried that method.
Step1 relock boot loader
Step2 run 3.14.605.12 ruu.exe
Step3 check for updates
Step4 unlock phone if you want to
I hope this helps anyone. Let me know if you have any questions.
Thanks.. Got it! And I got both the 13 and 14 updates almost immediately afterwards. I appreciate the confirmation about the process...
Sent from my ADR6425LVW using Tapatalk 2
xander5680 said:
U have step 1 and step 2 correct. Step 3 would be to connect the phone to the computer and run the 605.12 ruu.exe tool. After that u are now back to a stock phone. After the initial setup of adding your gmail account and contacts you can now go into system settings and check for update. As I stated before my phone would not download the update for some odd reason. I tried it a couple more times without success. Today on a whim I went to check for the update again and it started to download. After the small 6mb file was complete the next update for 605.14 downloaded without anny issues. Make sure you delete any zip files off your external SD card labeled ph98img.zip if u tried that method.
Step1 relock boot loader
Step2 run 3.14.605.12 ruu.exe
Step3 check for updates
Step4 unlock phone if you want to
I hope this helps anyone. Let me know if you have any questions.
Click to expand...
Click to collapse
Can anyone point me to where to find the 3.14.605.12 ruu.exe? I didn't want to spend all day flashing my phone, but ok, I guess I can to get rid of this annoying update.
digitalmofo said:
Can anyone point me to where to find the 3.14.605.12 ruu.exe? I didn't want to spend all day flashing my phone, but ok, I guess I can to get rid of this annoying update.
Click to expand...
Click to collapse
Check the march 10 2013 thread titled rezound in trouble please help. The download link is there. Its under the vigor section.
Here is the RUU I used without issues:
shipped-roms.com/index.php?category=android&model=Vigor
(http removed from link due to forum limitations)
3rd from the bottom...
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
hunteditor said:
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
Click to expand...
Click to collapse
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Wow, that was fast.
synisterwolf said:
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Click to expand...
Click to collapse
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
hunteditor said:
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
Click to expand...
Click to collapse
you should be good to do the update.
ruu using this zip http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
(place on root of sd card, rename PH98IMG.zip)
it will run 2 times. once with be bootloader and recovery, second time will be the full rom.
this will get you to stock OTA should show up a little while after its all installed and connected to the network.
EDIT:
If updated doesnt show up in a day you should be able to update with this zip: http://forum.xda-developers.com/showpost.php?p=40768590&postcount=35
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
hunteditor said:
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
Click to expand...
Click to collapse
once on root of external sd card. reboot the phone into bootloader
power off device hold vol - and power till you see hboot
hboot will detect it and run for you.
make sure you have 70+ battery before trying this. and do not pull the battery or loose power or it will birck.
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
hunteditor said:
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
Click to expand...
Click to collapse
wow, thank you kindly. Any time you need help just ask, thats how we all learn.
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
hunteditor said:
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
Click to expand...
Click to collapse
just like the ruu rename it to PH98IMG.zip and flash in hboot. again make sure you have enough battery
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