Related
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
I am having the same problem, but I found a way around it. If I boot the kernel through fastboot it will boot up. (You'd need to re unlock). My hboot doesn't really work anymore..
------
3(d)vo one s
Newts my hero.
evo bryan said:
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
Click to expand...
Click to collapse
Im not even sure at this point how to re-unlock it. i am wondering if i should have flashed to an older ruu though.
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
wards.jfasa said:
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
Click to expand...
Click to collapse
flashimage gui is able to do it inside android, im guessing it stores it in a tempory folder, let me see if i can find the temp folder where it stores before rebooting to flash it...........brb
did you check this post http://forum.xda-developers.com/showthread.php?t=1627897
This helped me out when I was Juopunutbear S-OFF'ing my phone. But I was at Hboot 1.50.
http://androidforums.com/evo-3d-all...mware-upgrade-ruu-flash-unbricking-guide.html
Pretty good guide.
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
The security warning is because you are using a custom rom so will not be able to use the RUU through the bootloader.
What you need to do is download the RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00. 1216_signed.exe from here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
If you then run that exe while your phone is in fastboot and connected to your pc it will factory reset your phone and put you back on stock rom and kernel.
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
This Quick And Dirty Evo 3D/V Root & S-OFF (QADERSO) guide is for current Sprint and Virgin Mobile (VM) S-ON users, rooted or not, who want to get to a rooted S-OFF configuration of the Sprint or VM ICS stock ROM. There are many other ROM and bootloader options that can be pursued from there.
I know that there are similar guides available already, but this one is going to be simple with no choices. If you want another recovery or aren't on Sprint or VM go check out one of the other ones, because this is the "Model T" of guides and will get you exactly the following configuration, which I believe is the best base for the Sprint Evo 3D or Virgin Mobile Evo V at this time:
1. Rooted Sprint ICS build 2.89.651.2 or VM ICS build 1.13.652.2
2. 4EXT Recovery with Updater or Control App
3. JuopunutBear S-OFF with JBear Sprint ICS (1.58.5858) bootloader or JBear VM ICS (1.57.5757) bootloader
If you want to modify this configuration and know how, feel free, but I'm only documenting how to get from your current configuration, whatever that is, to the one above. I am providing tips and references if you get stuck, but please don't ask about other configurations, recoveries, etc., in this thread.
Should you decide to modify the procedure, please explain that in any post made in this thread for assistance. That's your choice, but it would help me and any one else trying to provide support in this and other threads to have that information.
There are tips and references for each step at the end of this post in case you get stuck, but if you read all the instructions and follow this procedure carefully, hopefully you won't need them.
Prerequisites:
1. Sprint Evo 3D or Virgin Mobile Evo V phone that is S-ON, on any ROM, rooted or not.
2. Windows PC or notebook to run the utilities and access the websites.
3. MicroUSB to USB cable to connect the phone to the computer.
4. Shielded wire for the JuopunutBear wire trick.
5. Something to drink while the RUU.exe runs for about 10 minutes.
Before you start, download the QADERSO-V2-S.zip (mirror) file (for Sprint users) or QADERSO-V2-VM.zip (mirror) file (for Virgin Mobile users) and unzip it to somewhere on a Windows PC. It includes all the software you need to complete this procedure.
If you would like a Microsoft Word version of this guide and detailed instructions for the JuopunutBear wire trick, you can download it from here. Thanks to mpgrimm2 for putting that together.
Flashing the RUU.exe in Step1 will reset all the partitions on your phone except those on the SD card so I'd also recommend backing up anything you want to keep to the SD card before starting. If you don't have root yet, MyBackup is a good alternative to Titanium Backup and other utilities that require root.
***Step1: Install ICS RUU
If you are using this guide with a new/replacement unrooted phone you can go to Step2 since flashing the RUU returns the phone to the same stock configuration. VM users should apply the OTA update from the "System updates" options in system settings before starting Step2 if it hasn't already been done since that requires a stock configuration.
VM users: If the November VM OTA update (1.14.652.0) was installed and the phone is rooted with a custom recovery and ROM, please see this post for instructions on how to prepare the phone to run the RUU.exe. If both the November and March OTA (2.95.652.5) were installed there is no way to flash the RUU so proceed to Step2, or if already rooted flash a stock rooted ROM from this post then go directly to Step3.
Sprint users: If the March OTA ((2.95.651.5) is installed and the phone is unrooted proceed directly to Step2. If the March OTA is installed and it's rooted see this post for instructions on how to prepare for flashing the RUU.
Click to expand...
Click to collapse
Start by installing the Sprint 2.89.651.2 RUU.exe or Virgin Mobile 1.13.652.2 RUU.exe from Windows. It doesn't take much longer than flashing a stock ROM and includes all the firmware so the phone will be totally in sync with the official ICS build. Flashing the RUU can also resolve problems with the HTC unlock process if the OTA was used to update to the official Sprint ICS version or a custom recovery and ROM have already been flashed.
If you are already HTC unlocked, relock the bootloader using the "fastboot oem lock" command. You should know how to run fastboot commands from a PC if you have already unlocked.
If you have never HTC unlocked or have relocked successfully, connect the phone to the PC via a USB cable in "fastboot USB" mode then run the RUU.exe from the /QADERSO/RUU directory in Windows. The program has a GUI interface and is pretty much self-explanatory, but there is a readme.doc in the same directory that covers the process and possible errors.
VM users: Now would be a good time to download and install the OTA updates since they will flash updated firmware and patches to the stock software, and cannot be installed once a custom recovery is flashed in Step2. Just go to Settings/System updates/HTC Software, press check now, then download each of the two OTA updates (November and March) and follow the instructions to install them. The software patches will be overridden once a custom ROM is flashed, but the firmware updates will remain and should improve radio reception.
Sprint users: Installing the March OTA at this point will avoid having to flash the firmware only zip file for that update after getting S-OFF. To do that go to Settings/System updates/HTC Software, press check now, then download the update and follow the instructions to install it.
Click to expand...
Click to collapse
***End of Step1
***Step2: HTC Unlock, flash 4EXT recovery and superuser
Navigate to the /QADERSO/Root directory and open a command prompt by clicking on the "cmd" file in that directory. If you have HTC Sync installed go to the Windows control panel and uninstall just the sync program but leave the drivers installed. This is required by the JuopunutBear utility in Step3. If you don't have the HTC Sync program or drivers installed and are not using Windows 8, double click the HTCDriver3.0.0.007.exe file in the /QADERSO/Root directory to install only the HTC USB drivers. If you are using Windows 8 and don't have the HTC USB drivers already installed a compatible .exe setup can be downloaded here.
If you have never done the HTC unlock procedure, go to htcdev.com and signup then follow the instructions to get your bootloader unlocked. The programs you need to do the HTC unlock procedure are already in the /QADERSO/Root directory, so you can skip step 5 on the htcdev website.
If you have already HTC unlocked, you know the routine and need to do it again after flashing the RUU. You can use the same unlock_code.bin from your previous unlock.
Put the phone in "fastboot USB" mode by removing/replacing the battery, holding Power+VolumeDown buttons until the bootloader starts up, highlighting the "fastboot" entry by using the VolumeUp/VolumeDown buttons to navigate, selecting it with the Power button, then connecting it to your computer. The "fastboot" status should change to "fastboot USB".
When the phone is in "fastboot USB" mode, enter the following commands from the prompt:
"fastboot devices" (should show the serial number of your phone, beginning with "HT")
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
After the phone reboots into 4EXT recovery, select the "toggle usb storage" menu item from 4EXT recovery and copy the SuperSU-v0.96.zip file from the /QADERSO/Root directory on the PC to the root of the SD card on the phone. Eject the SD card from the PC and go back to the main menu of 4EXT.
Flash SuperSU-v0.97.zip from 4EXT recovery using the "Install from sdcard" menu item and selecting it from the root of the SD card. Go back to the main 4EXT menu and select "reboot now" from 4EXT and perform the initial setup of the stock ICS ROM after the boot completes.
Your phone now has the 4EXT custom recovery and a rooted stock ICS ROM with SuperSU.
Once the procedure is complete and you've booted into your rooted, stock configuration, you need to install either 4EXT Recovery Updater from the 4EXT website, or better yet purchase and install 4EXT Recovery Control from the Play Store. Then use the update function in the app you chose to get the current version of 4EXT.
You should start the SuperSU app to make sure it is working properly and updated to the current version. BusyBox also needs to be installed from the Play Store for 4EXT and other root apps and I recommend the installer by Stericson.
***End of Step2
***Step3: Perform JuopunutBear (wire trick) to get S-OFF status
Important Note:
The unlimited.io team has withdrawn support for all Windows versions of the JBear utility (controlbear.exe). Do not go to their IRC channel for support while following this guide as they will not be willing to help anyone using Windows instead of Linux for the wire trick. If you are unable to get S-OFF using this guide you will need to flash the RUU again and go to the the unlimited.io website to download a Linux version and follow their procedures.
Since the JuopunutBear wire trick now requires Ubuntu Linux to use the supported procedure Evo 3D users might also want to consider unknownforce's Ultimate Recovery Tool 3.0 which has recently been updated and streamlined. Unfortunately it won't work for Evo V 4G users since there is no Virgin Mobile GB RUU that can be used as part of that S-OFF process.
Click to expand...
Click to collapse
The wire trick is not difficult, but it can be a little confusing. It would be worth spending a little time reviewing the tips and references for Step3 at this point so the process goes smoothly.
Connect the phone to your PC with your stock rooted ROM booted and the USB debug option on in the developer settings.
Navigate to the /QADERSO/JBear directory, right click on controlbear.exe and "run as administrator", and then follow the prompts on the PC and the phone screen. Make sure to have an insulated wire ready for the wire trick, and select the JBear version of the bootloader when that prompt comes up. Yes, it's really that easy to get S-OFF.
If you flash a stock bootloader later it will show ***LOCKED*** as the status, but that's usually not a problem if the phone is S-OFF. It's actually good since that means there is no indication that the phone was ever unlocked, unlike the ***RELOCKED*** status after doing the HTC unlock/relock. By selecting the JBear version of the bootloader, the same fastboot commands will be available from a PC as with an unlocked bootloader.
You may have to activate your phone again after performing the wire trick. That is normal and should be done automatically from the phone on your first boot if it is required.
***End of Step3
WARNING: When you are S-OFF, PG86IMG.zip files can be flashed from the bootloader without being signed, which means you can flash any bootloader or firmware you want. But be careful and always make sure the stuff you are flashing is designed for your phone, or you may have serious problems if you force something to flash that was designed for another carrier or phone.
If you need to change the bootloader (hboot) version to run GB or AOSP ROM's you can find them in post #7 of mpgrimm2's thread on bootloader differences. There are instructions in this post for how to flash another bootloader with this configuration in place if you used this guide.
The following informational posts have been added to this thread:
1. Troubleshooting RUU.exe problems
2. Security questions about rooting and S-OFF
3. S-ON versus S-OFF
4. Information for users already S-OFF
5. How to change bootloader (hboot) when S-OFF
6. Temp root for current GB users
7. Recovery Comparison: TWRP2 versus 4EXT
8. Returning to stock configuration
9. Information on the Aroma installer
10. Updating 4EXT Recovery
11. QADERSO Version 2 with Virgin Mobile added
12. OTA Updates for Virgin Mobile users
13. OTA Update for Sprint users
14. Information for Linux users
15. JuopunutBear update
Please post any suggestions for making this process simpler and easier in this thread, but I intend to keep this guide as barebones as possible.
Tips and References for Step1: Flashing the RUU.exe
Tips
1. Make sure to put the phone into "fastboot USB" mode in the bootloader by removing/replacing the battery and using VolumeDown+Power to boot into the bootloader. The RUU is also supposed to work if you connect the phone to the PC while booted into Android, but I've found fastboot USB to be more reliable.
2. If you get a 17x error it has something to do with the USB connectivity. Make sure your phone is properly connected to the PC and in "fastboot USB" mode and try again.
3. If the RUU.exe stops in the middle of flashing the update, it's OK to cancel the Windows utility and restart it. This has happended to me a few times when I've had custom bootloaders installed.
References
1. HTC Readme.doc for flashing an RUU.exe is in the /QADERSO/RUU directory.
2. Download for HTC driver installer compatible with Windows 8.
3. The mpgrimm2 guide for flashing RUU's.
Tips and References for Step2: HTC Unlock, Flashing 4EXT Recovery and Superuser
Tips
1. On current Windows systems you can open a command prompt in a specific directory by using Windows Explorer to navigate to that directory and pressing Shift+MouseRightClick on blank area, then selecting "Open a command prompt here".
2. Make sure the phone is in "fastboot USB" mode and the bootloader has been HTC unlocked after flashing the RUU.exe or the fastboot commands will fail.
3. If you need to manually boot into recovery it can be done from the bootloader.
References
1. The HTC unlock overview diagram is in the /QADERSO/Root directory
2. The mpgrimm2 guide for flashing recovery and superuser.
3. The HTC Developer website.
4. The 4EXT Recovery website and HTCEvoHacks installation instructions for 4EXT Recovery Updater with video.
5. Instructions for installing 4EXT apps.
6. The SuperSU XDA thread.
Tips and References for Step3: JuopunutBear (wire trick) S-OFF Method
Tips
1. Watch this zedomax video and this timing video before attempting the wire trick and it will be a lot easier.
2. Make sure to backup your SD card to a PC before using it for the wire trick.
3. Remove the back cover to prepare for the wire trick but make sure to watch the phone's screen for superuser requests that need to be approved.
4. Do not touch the uninsulated part of the wire with your fingers while performing the wire trick.
5. Only short taps are required for the wire trick.
6. If unsuccessful with the wire trick try a smaller capacity SD card.
7. If the SD card used for the wire trick gets corrupted it can be reformatted and restored from the backup on the PC.
References
1. JuopunutBear overview, basic instructions and prerequisites.
2. JuopunutBear instructions and downloads for the Evo 3D.
3. Troubleshooting and Support pages on the unlimited.io website.
4. JuopunutBear thread on XDA.
Thanks for the tutorial, I'll let you know if I run into any issues. This will be the first time I root my Evo3D.
Kiotofl said:
Thanks for the tutorial, I'll let you know if I run into any issues. This will be the first time I root my Evo3D.
Click to expand...
Click to collapse
OK, thanks and good luck!
I've updated the download file and the instructions to include the HTC USB drivers for those that don't have them installed already so everything should be in that file to get you to rooted and S-OFF.
ramjet73
Thanks for this!
you sir, are a god among men. I will try this tonight and post the results.
Thanks!
rino655 said:
you sir, are a god among men. I will try this tonight and post the results.
Thanks!
Click to expand...
Click to collapse
Just wanted to say big thank you for posting this guide!
I managed to get Hboot 1.58 S-off. I had 1 failure with JuopunutBear (wire trick) but after 2nd try I was able to succeed.
One advice I can give is to uninstall all drivers and HTC sync and install HTCDriver3.0.0.007.exe from QADERSO\Root folder.
Everything else went smooth.
I've installed MeanROM ICS v2.6 | Sprint 2.89.651.2 but WiFi tether still does not work it seems like its matter of finding correct profile.
JohnnyBeGood113 said:
Just wanted to say big thank you for posting this guide!
I managed to get Hboot 1.58 S-off. I had 1 failure with JuopunutBear (wire trick) but after 2nd try I was able to succeed.
One advice I can give is to uninstall all drivers and HTC sync and install HTCDriver3.0.0.007.exe from QADERSO\Root folder.
Everything else went smooth.
I've installed MeanROM ICS v2.6 | Sprint 2.89.651.2 but WiFi tether still does not work it seems like its matter of finding correct profile.
Click to expand...
Click to collapse
Thanks!
Are you using the WiFi Tether app that came with MeanROM ICS? What usually works with MeanROM ICS is the generic ICS profile with the routing fix checked. I believe the OP for MeanROM ICS says to check MSS clamping as well, but some of the newer versions of WiFi Tether don't have that option, and I've never needed it.
ramjet73
ramjet73 said:
Thanks!
Are you using the WiFi Tether app that came with MeanROM ICS? What usually works with MeanROM ICS is the generic ICS profile with the routing fix checked. I believe the OP for MeanROM ICS says to check MSS clamping as well, but some of the newer versions of WiFi Tether don't have that option, and I've never needed it.
ramjet73
Click to expand...
Click to collapse
I was trying to get WiFi Tether to work and it would not start correctly it would give "starting softap" and "WiFi interface" error is "Show Log".
I even uninstalled one that came with ROM and installed latest wifi_tether_v3_2-beta2.apk from their site and still would not work.
What worked for me is selecting Menu > Change Device-Profile and selecting Generic ICS/JB (wlan0) and of course selecting "MMS clamping" + "Routing fix"
I was just selecting "Generic" and it would not work.
Hope it helps out someone.
Nice guide Ramjet73. The way u put it together should get everyone around all the common errors.
I will definitely get this linked to my other threads as soon as I can.
Sent from my "Up all night, Sleep all day" EVO3D!
Thanks ramjet73.
This is quite thorough. Very nice.
I'm almost wondering if I might be able to automate some of this somehow. Don't hold me to it though. I don't have a whole lot of time, but if I can, I'll see if I can maybe do that.
I guess then, that I'll "hold" the tenth spot just in case.
Thanks,
~co~
Edit: What in the world am I doing? Sorry ramjet73. Still if I come up with something, I'll message you.
closeone said:
Thanks ramjet73.
This is quite thorough. Very nice.
I'm almost wondering if I might be able to automate some of this somehow. Don't hold me to it though. I don't have a whole lot of time, but if I can, I'll see if I can maybe do that.
I guess then, that I'll "hold" the tenth spot just in case.
Thanks,
~co~
Click to expand...
Click to collapse
That would be great!
It would be nice to have it as automated as possible.
ramjet73
ramjet73 said:
That would be great!
It would be nice to have it as automated as possible.
ramjet73
Click to expand...
Click to collapse
Beat me to my edit. I'll see if I can do something. but, no guarantees.
~co~
Edit: I reedited my edit and put back what was originally there, resulting in this post being edited from its original unedited state as well. <- Meta
This is exactly what I was looking for
I am also looking to do my first root. I am still reading other posts. But, my main questions are around restoring the phone back to stock. I have Best Buy protection and if things go bad, I plan to use them and I am trying to figure out what steps I need to take to ensure I can potentially return back to the stock state before going down this path.
Overall, this is probably the simplest guide I have seen so far. Thanks again.. if you have any pointers for me around EVO 3D on Sprint, please let me know.
Thanks.
rosahas said:
I am also looking to do my first root. I am still reading other posts. But, my main questions are around restoring the phone back to stock. I have Best Buy protection and if things go bad, I plan to use them and I am trying to figure out what steps I need to take to ensure I can potentially return back to the stock state before going down this path.
Overall, this is probably the simplest guide I have seen so far. Thanks again.. if you have any pointers for me around EVO 3D on Sprint, please let me know.
Thanks.
Click to expand...
Click to collapse
If you choose the JuopunutBear bootloader as recommended and leave the bootloader status as ***LOCKED*** going back to complete stock is as easy as running the same 2.89.651.2 RUU.exe again, then issuing the "fastboot oem writesecureflag 3" to set it back to radio S-ON. Verify that you have successfully flashed the stock 1.58 bootloader before issuing that command or you could brick the phone.
ramjet73
ramjet73 said:
If you choose the JuopunutBear bootloader as recommended and leave the bootloader status as ***LOCKED*** going back to complete stock is as easy as running the same 2.89.651.2 RUU.exe again, then issuing the "fastboot oem writesecureflag 3" to set it back to radio S-ON. Verify that you have successfully flashed the stock 1.58 bootloader before issuing that command or you could brick the phone.
ramjet73
Click to expand...
Click to collapse
Question... If you have hboot 1.4, and run flash the latest update that has the new hboot, you ARE S-OFF, but it says LOCKED... Correct? Also, if you were to write the secure flag thing to S-ON, and you have the latest hboot, you are TRULY S-ON like you just bought your phone or never had S-OFF and updated, correct? Or is my hypothesis wrong?
wwjoshdew said:
Question... If you have hboot 1.4, and run flash the latest update that has the new hboot, you ARE S-OFF, but it says LOCKED... Correct? Also, if you were to write the secure flag thing to S-ON, and you have the latest hboot, you are TRULY S-ON like you just bought your phone or never had S-OFF and updated, correct? Or is my hypothesis wrong?
Click to expand...
Click to collapse
Yes, that's pretty much true, assuming you never HTC unlocked the phone or the S-OFF method you used returned the bootloader to the ***LOCKED*** status. I know the JBear method does just that, but I've never done the 1.4 downgrade. At one point mpgrimm2 said his bootloader showed ***UNLOCKED*** and I know he did the downgrade to hboot 1.4 to get S-OFF, so I'm not sure that method resets the bootloader S-OFF status.
In the worst case, if your bootloader is currently ***UNLOCKED*** and your radio is S-OFF, you could flash the RUU then set S-ON, root and do the wire trick to get the bootloader status back to ***LOCKED*** but that's a lot of work. OTOH, if you don't do that you can only set the bootloader status to ***RELOCKED*** with the "fastboot oem lock" command and that leaves a flag to HTC/Sprint that your phone was rooted. That's why I always recommend using a custom bootloader instead of HTC unlocking the stock bootloader if you are radio S-OFF and want to run more of the fastboot commands.
The custom bootloaders will usually mask the bootloader locked/unlocked status with a name like "Revolutionary" or "JuopunutBear" so the only way to verify what you currently have for your bootloader status is to flash a stock bootloader.
ramjet73
I had to reread the middle paragraph 3 times to understand it, but that's my understanding too. My hboot does say unlocked/relocked (RL) on it because I did the HTC Unlock at one point, without the Jbear for s-Off.
Sent from my "Up all night, Sleep all day" EVO3D!
ramjet73 said:
When the phone is in "fastboot USB" mode, enter the following commands from the prompt:
"fastboot devices" (should show the serial number of your phone, beginning with "HT")
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
Click to expand...
Click to collapse
I try to enter "fastboot devices" in the Quaderso\root directory, and it tells me
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What is the problem? I spent 2 hours on something that I will have problems with. Great.
Found out I had to move the files back to the Root Directory. Thanks for an awesome guide!
RevolcFael4 said:
I try to enter "fastboot devices" in the Quaderso\root directory, and it tells me
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What is the problem? I spent 2 hours on something that I will have problems with. Great.
Click to expand...
Click to collapse
Sounds like you are not in the the \quaderso\root directory when the "fastboot devices" command is being issued from the prompt. See tip #1 for Step2 to open a command prompt in the \qaderso\root directory.
You can also Start/Run "cmd" then use the "cd" command to navigate to the \qaderso\root directory. Either way you should issue a "dir" command from prompt to make sure the contents of the directory are as follows:
C:\tmp\QADERSO\Root>dir
Volume in drive C is OS
Volume Serial Number is 6CF6-A9B2
Directory of C:\tmp\QADERSO\Root
09/16/2012 03:07 AM <DIR> .
09/16/2012 03:07 AM <DIR> ..
09/05/2012 05:52 PM 7,047,406 4EXT_Recovery_Touch_v1.0.0.5_RC6.zip
05/07/2010 12:48 PM 578,611 adb.exe
05/07/2010 12:48 PM 96,256 AdbWinApi.dll
07/16/2011 01:05 PM 183,651 fastboot.exe
07/30/2011 10:31 AM 13,783,568 HTCDriver3.0.0.007.exe
08/14/2012 05:09 PM 7,077,888 recovery.img
09/15/2012 05:53 PM 684,154 SuperSU-v0.96.zip
09/15/2012 06:48 PM 169,793 Unlock_Bootloader_Workflow.pdf
8 File(s) 29,621,327 bytes
2 Dir(s) 291,896,774,656 bytes free
ramjet73
mpgrimm2 said:
I had to reread the middle paragraph 3 times to understand it, but that's my understanding too. My hboot does say unlocked/relocked (RL) on it because I did the HTC Unlock at one point, without the Jbear for s-Off.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
Yeah... I NEVER ONCE ran htc dev on my Evo 3D. The moment I bought it, I declined all updates and waited until THIS DAY happened, and S-OFF'd immediately. I knew better than to update, after knowing about all the trouble people had with the shift and the og evo. Updates are bad, mmmk?
Anyways, I S-OFF'd that night and never looked back... Still have 1.4, and don't feel like giving up my virginity to HTC.
YOU KNOW YOU WANT TO CLICK ME!
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
Hello. So I've tried multiple times flashing ROMs to my device, and have always had problems somewhere along the line. The furthest I got was successfully flashing this ROM, but it ended up in a boot loop. I believed it was due to my device being S-ON, even though I've successfully rooted and unlocked my bootloader via HTCdev and thus I've been attempting to get S-OFF. I tried JuopunutBear but got an error message related to checking my adb and fastboot drivers (Which I'm fairly sure are up to date and working) and I think the problem is I am on HBOOT 1.57. I've been attempting to downgrade using this guide (Which uses Revolutionary to get S-OFF in which case I wouldn't need JuopunutBear). I only got a bit of the way in, however, before I got stuck. After relocking my device it tells you to put the RUU zip on your device, but my computer isn't detecting my device and I'm stuck in the bootloader. I've tried shutting it off, trying all the options in the bootloader, taking out the battery, entering commands into adb, and probably some other things I've forgot, but I'm still stuck on the bootloader and my device isn't detected at all on my computer (Either in command prompt or in the explorer window).
Essentially what I'm asking here is:
How do I get my phone unstuck from bootloader?
Do I need S-OFF to be able to flash ROMs?
If I don't need S-OFF, what was I doing wrong? Should I try a different ROM?
And I suppose I may as well ask if that's a worthwhile ROM. I want something that optimizes my device and allows for custom themes, but otherwise I'm not too picky.
Specs:
Windows Vista (With ADB and fastboot, as well as HTC Sync and other phone drivers. Essentially I think I have all the software I'd need installed.)
HTC EVO 3D CDMA with Virgin Mobile as the carrier.
HTCdev unlocked bootloader
S-ON
HBOOT 1.57
Stock ROM
4ext recovery
Any and all help would be greatly appreciated!
(Also I apologize if I didn't give all the information needed or if I posted this in the incorrect spot. I figured this would be the most appropriate spot since although I have issues with specific processes it's also a fairly general request for help.)
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
cj_302 said:
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Er, I'm not quite sure what you're saying here.
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
It will be your hboot causing the problems.
Most recoveries allow you to mount usb storage so you can use that option to connect to your pc and move the ruu across without removing your sdcard etc.
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup