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.
I am a rooted htc rezound user and am in desperate need for help. My rezound is rooted and the bootloader is unlocked. I just recently tried the new ICS (sense 3.5) rom that was released yesterday. Before i used the rom i did a nandroid backup and then a factory reset. Once i was finished with the rom (because of the bugs it carried), i went to restore my phone using the nandroid backup. When the phone booted back up, after it hit the HTC splash screen, it freezes. The phone is still on, but stuck on a black screen.
I have tried everything. Restoring the nandroid backup multiple times. Flashing a stock rom of the htc rezound in the recovery and also (changing the name to PH98IMG) and the tried flashing it through bootloader/hboot. I also took the stock kernel and did the same exact thing. Ive also downloaded the automatic (.exe) RUU update of the stock rom, from Scott's Roms, but that just kept giving me an "Update Fail" message.
Please help me!
.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore or install a rom of your choice.
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
Anyway. To restore the stock kernel, I am building a special PH98IMG.zip right now. DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
Omg, thank you sooooooooo much. It worked beautifully! Thank you times a million!
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
Anyway. To restore the stock kernel, I am building a special PH98IMG.zip right now. DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
As stupid as it was that I installed that PH98IMG.zip without looking further into it, or if I had just used fast boot, or cleanFLASH I wouldn't be in this mess. I mainly blame it on having the Eris, INC1, and INC2 all S-OFF, esp my latest phone before the Rezound inc2, was perma S-OFF thanks to the XTC clip so I could flash just about anything without repercussion. But you live and you learn. The Eris had crazy 2.1 leaks and people got stuck on some bad builds, and not only that they were unable to root when root finally came out, because they flashed the 2.1 leak.. I thought I learned my lesson then but with this I didn't know any better. Learn something new everyday. but I disagree with this part. "It is possible you WILL NOT be able to EVER use an RUU to restore in the future."
Jcase has assured me this is not true.
Ignore This and the next post plz
I need ten post in order to post on development forums. I am just going to use my thread so plz ignore this.thnks
I need ten post in order to post on development forums. I am just going to use my thread so plz ignore this.thnks
ggggggggggggggg
hhhhhhhhhhh
Don't give up now! You're almost there...
Lol.. i had to do same to be able to post to the appropriate threads and forums ...
Careful about that. If a mod's having a bad day your posts could be deleted.
Just sayin'.
Sent from my Unlocked/Rooted Rezound running CleanROM 2.0/AmonRa
Sounds like you haven't gotten a hang of flashing a ROM with this device. Try the following.
1 - Download Cleanflash to computer
2 - Download ROM you want to install.
3 - Using a ZIP program, look in the ROM and copy the boot.img file and put in the Cleanflash folder.
4 - Open the back cover, pull battery, wait 10 seconds, put back battery and cover.
5 - Press and hold Vol-, then power for 2 seconds, release power, wait for hboot screen, then release vol-
6 - Connect phone to computer
7 - Make sure HTC Sync is not running on computer
8 - Run CleanFlash and use option 2 to flash boot.img to phone
9 - On the phone, use vol keys to go to recovery (I assume you have Amon Ra recovery already installed)
10 - Follow the menu to mount your sd card
11 - From the computer, your phone's sd card should now show up as a drive
12 - Copy ROM (entire zip file) to sd card, while your at it make sure there is no other ZIP file on the card. You should also mount the internal card and make sure there are no zip files there either.
13 - Unmount the card and disconnect from computer
14 - Now flash the new ROM
15 - reboot phone
feralicious said:
Don't give up now! You're almost there...
Click to expand...
Click to collapse
LOL (I hope an LOL is not cause for banishment)
Sent from my ADR6425LVW using XDA App
Considering I can't post in the development forum yet, I'll try asking here first. I've been reading up for the past few days on flashing recovery and ROMs for my new Rezound, mostly on ADB today to get a feel for the very basics. Right now I'm trying to get Amon Ra onto my device, only to run into the command prompt telling me, "error: cannot load 'recovery-ra-vigor-3.12b-gnm'. The recovery.img is in the root directory where the fastboot and adb executables are located. What am I missing? It's likely a simple fix, but as of yet my searches aren't finding the results I'm after.
Also, when I tried using fastboot to reboot the device to the bootloader (fastboot reboot-bootloader) I got a < waiting for device > message. I ended up just doing a battery pull to get into the fastboot menu on the phone. And as I've seen it asked previously, I did install the drivers when I was going through the unlock process last night. Any suggestions?
canned karma said:
Considering I can't post in the development forum yet, I'll try asking here first. I've been reading up for the past few days on flashing recovery and ROMs for my new Rezound, mostly on ADB today to get a feel for the very basics. Right now I'm trying to get Amon Ra onto my device, only to run into the command prompt telling me, "error: cannot load 'recovery-ra-vigor-3.12b-gnm'. The recovery.img is in the root directory where the fastboot and adb executables are located. What am I missing? It's likely a simple fix, but as of yet my searches aren't finding the results I'm after.
Also, when I tried using fastboot to reboot the device to the bootloader (fastboot reboot-bootloader) I got a < waiting for device > message. I ended up just doing a battery pull to get into the fastboot menu on the phone. And as I've seen it asked previously, I did install the drivers when I was going through the unlock process last night. Any suggestions?
Click to expand...
Click to collapse
Recovery img has to be in the same folder as the fast boot file. Second...you must make sure too add the file ext for that file. Should be .img for a recovery file.
Sent from my ADR6425LVW using XDA App
I hadn't added in the file extension, that did the trick nicely. Thanks!
i love
lamp and rezound
Can i use the PH8 zip to return my Rezound to stock? I am on Scotts leaked ICS rom. It works and all but i want to restore my phone to stock. Im on a Mac so i can't use a RUU. Is there a zip of the latest RUU i can flash in Hboot?
There is a stickied post with the stock vigor RUU's that the phone's came with . Shouldn't have an issue since you used Scott's version he altered the mainver to avoid issues with going back to stock.
Need to relock then run RUU though FYI.. just in case you weren't clear about that.
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Ryoma Echizen said:
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Click to expand...
Click to collapse
You don't need to upgrade to ics to get a custom ics rom, if that's what your asking. Reunlock, and check out the development forums and find an ics rom that works with 2.17 (eg, cool sense, meanrom, homebrew, common sense [my rom lol]). Go ahead and flash one, and enjoy ics
Stay on 2.17 though, first rule: NEVER accept ota. It's kinda rule of thumb. I learned the hard way.
Sent from my EVO 3DMA with a little "common sense"
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Wikd said:
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Click to expand...
Click to collapse
Yeah I checked out some other threads (none for the 3d though) and they said pretty much that it did have to do with the custom recovery like you said. And you are right on the other two counts, but no, it didn't upgrade me to 1.58, I'm still on 1.5.
Alright, thanks! I'll try to re-unlock using the HTC method(I'm assuming ill need to get another unlock_code.bin since the one I used isn't working anymore for some reason). I'll post again and let you know how it goes.
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
The tampered just means you have a custom recovery like Amon Ra installed.
Sent from my ADR6425LVW using xda app-developers app
oatlord said:
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
Click to expand...
Click to collapse
4.03.605..2 is the latest vzw build.
jbh00jh said:
4.03.605..2 is the latest vzw build.
Click to expand...
Click to collapse
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
oatlord said:
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
Click to expand...
Click to collapse
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
to reinstall the RUU, first make sure you have fastboot on your PC and your phone is in the fastboot menu of the bootloader and connected to your PC. It should say "fastboot USB". (If you don't have the HTC drivers installed, download HTC Sync 3.0 and that should install it. I haven't gotten it to work on Windows 8 so if you use Windows 8 use these drivers)
Open a command prompt, change the directory to where your fastboot.exe is (example: cd c:\fastboot_directory). Type in 'fastboot oem lock'. Your phone will restart, then boot up. Turn it off, reboot to the bootloader and make sure it says *RELOCKED* on the top. Then, go back to fastboot and in your cmd window, type in 'fastboot oem rebootRUU'. Your phone will reboot and show a black screen with a grey HTC logo. Copy the RUU (doesn't matter if it's named PH98IMG.zip or something else) into the same folder as fastboot.exe and type in 'fastboot flash zip ruu_zip_name.zip' (obviously replacing ruu_zip_name.zip with the zip's actual name). The terminal will start sending the zip and details will be displayed on your computer screen. Your phone will also have a progress bar. Once the terminal on your computer says it's finished, you can reboot your phone.
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock recovery here's a link http://www.mediafire.com/?wb21d2gdurui2c6 then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
famouscollin said:
Flash stock recovery here's a link (removed cause I'm too new) then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Click to expand...
Click to collapse
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
WookieFan said:
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're s-off you shouldn't have to unlock.
---------- Post added at 07:17 PM ---------- Previous post was at 07:11 PM ----------
oatlord said:
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
Click to expand...
Click to collapse
The bootloader is the hboot. You power on holding vol down to get there.
The stock recovery does not allow you to create backups, or do much at all I'm pretty sure. That is why we have custom ones.
If i helped throw me a thanks
iamwalterwhite said:
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
Click to expand...
Click to collapse
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
xxtsxx said:
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
Click to expand...
Click to collapse
Sorry that you never got an answer to this. Yes, you should flash both recovery (stock) and the RUU as PH98IMG zip files. Wait to start this process until you have a pc/sd card reader available. Trying this without those basic tools is going to make this a frustrating process for you.
Sent from my ADR6425LVW using Tapatalk 2
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
xionchen4628 said:
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
Click to expand...
Click to collapse
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
gav-collins1983 said:
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
Click to expand...
Click to collapse
Hi. Thanks for replying. Please bear with me as I am more of a casual user who barely have any inkling of why he is doing something, only how to get to S-Off, rooted through developers who provided step-by-step guide for "Dummies who want to Root their Phone". I have been in contact with Ramjet73 who is really kind to answer my questions but I am trying not to bother him too much hence I am trying to pass on any further questions that I have to other users such as yourself. So...thank you in advance.
From what Ramjet73 told me, I can just run the RUU.exe for 2.89.651.2 (Sprint ICS build) since I am S-Off. However he then inform me that I need to download a custom bootloader and custom recovery. This supports your comments that I will lose recovery and root after update? Ramjet 73 suggested a custom bootloader from ENG or JBear. How is that different from the bootloader that you suggested in your reply?
I assume that after I update both the ICS RUU and the custom bootloader, I will remain S-Off and rooted with superuser status and apps such as titanium backup and wifi tethering operational?
As for custom recovery, Ramjet 73 suggested 4Ext Recovery which I assume is 4Ext Recovery Updater (if I want a free version) or 4Ext Recovery Control if I am willing to pay for more options. Now in the past, I haven't really install any custom recovery other than what was installed when I used Revolutionary's tool to turn my phone to S-Off. I believe that installed Clockworkmod which I access when I boot to it using Power+Vol Down. Is Rom Manager the newest equivalent to that? What is your opinion on 4Ext Recovery vs Rom Manager.
So to summarize, I run the RUU.exe for ICS upgrade. Then I flash a bootloader like you recommended in your reply or one of the custom bootloaders from ENG or JBear. Then flash a custom recovery and I am all set? Sorry for all these questions and I hope you can help. Thanks.
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Sent from my EVO using xda premium
sullivan7221 said:
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Click to expand...
Click to collapse
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
ramjet73 said:
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
Click to expand...
Click to collapse
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
ramjet73 said:
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Click to expand...
Click to collapse
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
xionchen4628 said:
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
Click to expand...
Click to collapse
Okay, final update for those looking at this thread. I now have stock ICS, remained S-OFF and have superuser access. Basically I followed ramjet who was helping me out. The first thing that someone in my same position who wants to do the same thing, should navigate to ramjet's guide: (http://forum.xda-developers.com/showthread.php?t=1889438). Download his file (QADERSO.zip) and unzip it.
1) I turned on USB debugging on my phone and connected to my pc using "charge only" option.
2) I clicked on RUU.exe file in ramjet's QADERSO\RUU folder which then update my phone to ICS. When I access the bootloader, it now said "Locked", then "shooter xc ship s-off RL" and finally "Hboot1-58.5858". So now i have ICS, still S-off but with an upgraded locked bootloader.
3) Then I copied the custom bootloader "PG86IMG_jb_hboot_Sprint_ICS.zip into the root directory of my sd card (the zip file can be found in another of ramjet's post (http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7) and renamed it PG86IMG.zip. Once you go into the bootloader, the zip file will automatically update. Now instead of "Locked" on the top, you should have "JuopunutBear".
4) First remove the previous zip file from the directory. I put the "SuperSU-v0.96.zip" from the QADERSO\Root folder in the root director of my sd card again. then i access my bootloader once again.
5) I went into fastboot and then connect to my Pc with usb. It should now say "Fastboot USB".
6) you can now flash any recovery img that you want. This is where I differ from ramjet's suggestion of 4ext as I did a backup of my system before all of this with clockworkmod recovery.
7) once the recovery of your choice is installed, then just install the supersu.zip file from your sd card and you should have a rooted phone.
Thanks to ramjet for his guide and his help. Now onto my next problem. going back to the state I was before updating to ics. Posting another thread about it. Anyone who can help out, please do. Thanks.
xionchen4628 said:
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
Click to expand...
Click to collapse