Related
I have a lot of questions about this stuff. If someone knowledgeable could quote each one and answer them it would be very much appreciated.
1. Currently I am S-Off via Revolutionary but I am not yet rooted and I havent flashed a recovery tool such as Clock work or Team Win. All I have done so far is got S-Off. What is my next step?
2. On the OG evo you just held the volume down and power button to get to the screen where you can flash roms and stuff. How do you get to it on the 3D? I havent flashed Team Win yet it that why it isnt working?
3. What exactly is the difference between S-Off and root? I thought S-Off meant you were rooted and could flash roms etc. What does root do for you that S-Off does not?
4. What do I need to back up? I didnt think of backing up before I got S-Off. Is that ok? What do I need to do to make sure that I can make my phone like it was out of the box with S-On if I need to? Should I Nandroid backup before I root? Was I supposed to back up before I got S-Off?
5. Are there any good Roms out yet? What are the best things I can do once I am rooted?
That is all for now thank you so much!
Go to revolutionary and read, the answers are there.
jedinegotiator said:
I have a lot of questions about this stuff. If someone knowledgeable could quote each one and answer them it would be very much appreciated.
1. Currently I am S-Off via Revolutionary but I am not yet rooted and I havent flashed a recovery tool such as Clock work or Team Win. All I have done so far is got S-Off. What is my next step?
2. On the OG evo you just held the volume down and power button to get to the screen where you can flash roms and stuff. How do you get to it on the 3D? I havent flashed Team Win yet it that why it isnt working?
3. What exactly is the difference between S-Off and root? I thought S-Off meant you were rooted and could flash roms etc. What does root do for you that S-Off does not?
4. What do I need to back up? I didnt think of backing up before I got S-Off. Is that ok? What do I need to do to make sure that I can make my phone like it was out of the box with S-On if I need to? Should I Nandroid backup before I root? Was I supposed to back up before I got S-Off?
5. Are there any good Roms out yet? What are the best things I can do once I am rooted?
That is all for now thank you so much!
Click to expand...
Click to collapse
I am nowhere near the level user you need but I will try a few;1. You need a recovery(twrp or clockwork....2.that will take you to fastboot same as if EVO.3.I think s-off has more to do with security,and root has to do with permissions.(don't quote me in that )4.I didn't backup either..you should be fine.you might have the network error ...(no bid deal.)5. Download titanium backup, and do a nandroid backup.(after recovery.)
Sent from my PG86100 using XDA Premium App
davec1234 said:
Go to revolutionary and read, the answers are there.
Click to expand...
Click to collapse
I did read all that. Not one of my questions were answered there.
Someone be kind and answer I know there are places to get this information but it is spread out and hard for me to find.
todah09 said:
I am nowhere near the level user you need but I will try a few;1. You need a recovery(twrp or clockwork....2.that will take you to fastboot same as if EVO.3.I think s-off has more to do with security,and root has to do with permissions.(don't quote me in that )4.I didn't backup either..you should be fine.you might have the network error ...(no bid deal.)5. Download titanium backup, and do a nandroid backup.(after recovery.)
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Ok so do I go ahead and put TWRP on my phone or do I backup first? Will I be able to return my phone to stock if I need to?
In some uncertain terms, S-OFF allows you to obtain root. Imagine root is like the administrator account on your Windows PC (i.e. when you right-click and "run as administrator" you're running a program as "root"). Root of course is the linux user name for the admin, head honcho, whatever. If you had S-ON, your phone would see that you're trying to up your lowly status from user to root, and stop you like a ton of bricks. Or if you managed to hack your phone and circumvent it, s-on would find out and **** you and your children up. (or just take away your root).
Anyway, you need to do 3 steps here to fully modify your phone.
1. Obtain S-OFF
2. Flash a custom recovery, because the default one sucks and doesn't let you do stuff.
3. Install a program that allows you to manage and grant superuser (root) access to programs that require it (such as wifi-tether).
You're on step 2.
You'll need the following. The android-sdk and also a recovery to flash. You can google the android-sdk. The newer one has made things a little complicated, so I will try to walk through that.
When you obtain and install the android-sdk, you'll need to download the platform tools for it. So start the SDK Manager.exe. It'll pop up with some "choose packages to install". Cancel that crap. Click on 'Available Packages' and expand 'Android repository' and select 'Android SDK Platform-tools, revision 6'. This will install ADB, which you may have used in the past.
Power off your phone (pull battery). Hold down the volume rocker and press power button. It should load into a white screen. From that white screen you can scroll down and select 'fastboot' with the power button. Fast boot is how we're going to flash a recovery, in this case TWRP. Get it here: http://forum.xda-developers.com/showthread.php?t=1192077
Throw that img file into your android-sdk\platform-tools directory.
Open up a command prompt and CD to your android-sdk\platform-tools directory.
You can flash the new recovery by entering the following command:
Code:
..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
What you're doing is running fastboot.exe (which is located in the android-sdk\tools directory, but requires and adb dll file located in platform-tools, hence the topsy turvery method here. You're telling it to flash a new recovery image, and then you're telling it where on your computer that image is.
Once it's done, you can reboot your phone, and now you have recovery. Next you'll need to obtain a super user program so you'll have root. People generally use, 'superuser'. I think the easiest way to grab this is to just download it's zip to your phone and flash it in recovery. Grab the zip for flashing from here.
You should be s-off'd, have a recovery and rooted by now. As a disclaimer, I assume no responsibility if this screws up your phone.
EDIT:
To answer some of your other concerns. You'll want to backup prior to flashing any ROMs. You won't really be able to backup anything of value prior to flashing recovery. If you need to return to stock there are RUU ROMS on the developer forum. If you flash that in recovery, you'll lose root (and I think s-off) and be cast into the world of yesterday. If you're still concerned at this point, I would refrain from attempting to root your phone and maybe have a buddy do it.
jedinegotiator said:
I did read all that. Not one of my questions were answered there.
Someone be kind and answer I know there are places to get this information but it is spread out and hard for me to find.
Click to expand...
Click to collapse
Must have not read the QandA very well..
And post QUESTIONS in the QUESTIONS and answers. Keep this forum nice and tiddy
jedinegotiator said:
Ok so do I go ahead and put TWRP on my phone or do I backup first? Will I be able to return my phone to stock if I need to?
Click to expand...
Click to collapse
yes,you need a recovery in order to do a nandroid backup........
sidepart said:
In some uncertain terms, S-OFF allows you to obtain root. Imagine root is like the administrator account on your Windows PC (i.e. when you right-click and "run as administrator" you're running a program as "root"). Root of course is the linux user name for the admin, head honcho, whatever. If you had S-ON, your phone would see that you're trying to up your lowly status from user to root, and stop you like a ton of bricks. Or if you managed to hack your phone and circumvent it, s-on would find out and **** you and your children up. (or just take away your root).
Anyway, you need to do 3 steps here to fully modify your phone.
1. Obtain S-OFF
2. Flash a custom recovery, because the default one sucks and doesn't let you do stuff.
3. Install a program that allows you to manage and grant superuser (root) access to programs that require it (such as wifi-tether).
You're on step 2.
You'll need the following. The android-sdk and also a recovery to flash. You can google the android-sdk. The newer one has made things a little complicated, so I will try to walk through that.
When you obtain and install the android-sdk, you'll need to download the platform tools for it. So start the SDK Manager.exe. It'll pop up with some "choose packages to install". Cancel that crap. Click on 'Available Packages' and expand 'Android repository' and select 'Android SDK Platform-tools, revision 6'. This will install ADB, which you may have used in the past.
Power off your phone (pull battery). Hold down the volume rocker and press power button. It should load into a white screen. From that white screen you can scroll down and select 'fastboot' with the power button. Fast boot is how we're going to flash a recovery, in this case TWRP. Get it here: http://forum.xda-developers.com/showthread.php?t=1192077
Throw that img file into your android-sdk\platform-tools directory.
Open up a command prompt and CD to your android-sdk\platform-tools directory.
You can flash the new recovery by entering the following command:
Code:
..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
What you're doing is running fastboot.exe (which is located in the android-sdk\tools directory, but requires and adb dll file located in platform-tools, hence the topsy turvery method here. You're telling it to flash a new recovery image, and then you're telling it where on your computer that image is.
Once it's done, you can reboot your phone, and now you have recovery. Next you'll need to obtain a super user program so you'll have root. People generally use, 'superuser'. I think the easiest way to grab this is to just download it's zip to your phone and flash it in recovery. Grab the zip for flashing from here.
You should be s-off'd, have a recovery and rooted by now. As a disclaimer, I assume no responsibility if this screws up your phone.
Click to expand...
Click to collapse
Thank you so much kind sir. Thanks given to you and todah Edit: Coffee too
Edit: Someone answered it very well before i had a chance to finish typing..
jedinegotiator said:
Thank you so much kind sir. Thanks given to you and todah Edit: Coffee too
Click to expand...
Click to collapse
i thank you too..
sidepart said:
In some uncertain terms, S-OFF allows you to obtain root. Imagine root is like the administrator account on your Windows PC (i.e. when you right-click and "run as administrator" you're running a program as "root"). Root of course is the linux user name for the admin, head honcho, whatever. If you had S-ON, your phone would see that you're trying to up your lowly status from user to root, and stop you like a ton of bricks. Or if you managed to hack your phone and circumvent it, s-on would find out and **** you and your children up. (or just take away your root).
Anyway, you need to do 3 steps here to fully modify your phone.
1. Obtain S-OFF
2. Flash a custom recovery, because the default one sucks and doesn't let you do stuff.
3. Install a program that allows you to manage and grant superuser (root) access to programs that require it (such as wifi-tether).
You're on step 2.
You'll need the following. The android-sdk and also a recovery to flash. You can google the android-sdk. The newer one has made things a little complicated, so I will try to walk through that.
When you obtain and install the android-sdk, you'll need to download the platform tools for it. So start the SDK Manager.exe. It'll pop up with some "choose packages to install". Cancel that crap. Click on 'Available Packages' and expand 'Android repository' and select 'Android SDK Platform-tools, revision 6'. This will install ADB, which you may have used in the past.
Power off your phone (pull battery). Hold down the volume rocker and press power button. It should load into a white screen. From that white screen you can scroll down and select 'fastboot' with the power button. Fast boot is how we're going to flash a recovery, in this case TWRP. Get it here: http://forum.xda-developers.com/showthread.php?t=1192077
Throw that img file into your android-sdk\platform-tools directory.
Open up a command prompt and CD to your android-sdk\platform-tools directory.
You can flash the new recovery by entering the following command:
Code:
..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
What you're doing is running fastboot.exe (which is located in the android-sdk\tools directory, but requires and adb dll file located in platform-tools, hence the topsy turvery method here. You're telling it to flash a new recovery image, and then you're telling it where on your computer that image is.
Once it's done, you can reboot your phone, and now you have recovery. Next you'll need to obtain a super user program so you'll have root. People generally use, 'superuser'. I think the easiest way to grab this is to just download it's zip to your phone and flash it in recovery. Grab the zip for flashing from here.
You should be s-off'd, have a recovery and rooted by now. As a disclaimer, I assume no responsibility if this screws up your phone.
Click to expand...
Click to collapse
thanked....
Maybe I should clean this document up and post a guide. I know there are a few already but they're a little kludgy if you don't know what you're doing.
Earned a thanks from me on that very well-done post, sidepart. Even though I'm not personally in need of the info therein contained, it was certainly a refreshing change from the self-absorbed useless replies typically found following a noob's request for guidance when diving into this root stuff.
Guide Posted: http://forum.xda-developers.com/showthread.php?t=1193680
GO FORTH! And Good Luck.
jedinegotiator said:
I have a lot of questions about this stuff. If someone knowledgeable could quote each one and answer them it would be very much appreciated.
1. Currently I am S-Off via Revolutionary but I am not yet rooted and I havent flashed a recovery tool such as Clock work or Team Win. All I have done so far is got S-Off. What is my next step?
2. On the OG evo you just held the volume down and power button to get to the screen where you can flash roms and stuff. How do you get to it on the 3D? I havent flashed Team Win yet it that why it isnt working?
3. What exactly is the difference between S-Off and root? I thought S-Off meant you were rooted and could flash roms etc. What does root do for you that S-Off does not?
4. What do I need to back up? I didnt think of backing up before I got S-Off. Is that ok? What do I need to do to make sure that I can make my phone like it was out of the box with S-On if I need to? Should I Nandroid backup before I root? Was I supposed to back up before I got S-Off?
5. Are there any good Roms out yet? What are the best things I can do once I am rooted?
That is all for now thank you so much!
Click to expand...
Click to collapse
1. Your next step would be to flash the recovery (twrp is a good option) through fastboot, and then run the permanent root.
2. volume down and power button will get you to hboot. from there (once you have flashed a custom recovery (twrp or clockworkmod) you just scroll to recovery, select it, and it will load up. and yes it isnt working because you havent flashed it yet.
3. S-off is security off on the write protected partitions of the phone basically. it allows you to flash custom recoveries, roms, kernals, etc. Its a lot deeper than than, but thats the gist of it. Root will allow you to run certain apps on your phone and give them heightened privileges.
4. there isnt really much you can back up before s-off. other than temp rooting and doing titanium backup for your apps. thats fine that you didnt do anything but there isnt a way to backup s-on. you can get back to s-on but it sounds like it is pretty complicated. i havent personally tried s-on again yet because i have no interest in having s-on haha. you can nandroid backup before you root, but i personally did it after root.
5. there are a few roms out, but if your not a flashaholic i would wait for a few days or a couple weeks for the roms to be refined. in the meantime just enjoy tweaking your device and not having to re-root every time your phone reboots haha.
Let me know if you have any more questions!
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, I have done all I could find on this site and others to no avail. I would be so thankful if there is just one person out there who can help me get this done! I have htc evo 4g lte with hboot 1.19, 2.13.651.1 and all I have been trying to do is get root with superuser. i tried to unlock and s-off too just to see if i could get closer to superuser and i am so stuck. i have windows 8 x64 and windows 7 x32 available to use. help! please! thanks!
This is the guide I used before s-off was available through dirtyracuns. It's pretty straightforward. If you're bootloader is unlocked already then all you need to do it flash the superuser zip from the guide through recovery.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
Sent from my EVO using xda app-developers app
I have nothing altered yet. i've tried that, and command prompt sat there forever waiting to see my device, which it never does. never got the token. also, in my device manager it doesn't read ADB Interface > My HTC-- it reads Android USB Devices > My HTC. not sure if that might be an indication of what is/isn't installed/configured [im]properly on my computer.
go here http://unlimited.io/dirtyracun.htm and follow the directions to a T on your win7x32 machine, you will be unlocked with s-off.
once you're done with that, go here http://teamw.in/project/twrp2/98 and download the openrecovery-twrp-2.3.1.0-jewel.img file to the RabiesShot_WIN folder that you just used to do your s-off (because the fastboot.exe is there, just use the command prompt from that folder like you did for the racun) and use the fastboot method (boot to bootloader, vol-dwn to fastboot, pwr, plug in usb, enter "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" command)
after that's done you can try to reboot to recovery, though mine always boots to system the first time after i've flashed recovery, to confirm it's there, or just let the phone boot to system, plug in your USB and download the CWM installable zip from the bottom of the OP in this thread http://forum.xda-developers.com/showthread.php?t=1538053 to your USB card someplace where you know you can find it.
then power off your phone, boot to the bootloader again, pwr-dwn to recovery, hit power button, welcome to TWRP, tap Install, browse the the zip you just saved, install, reboot to system, and you have root
dangle79 said:
go here http://unlimited.io/dirtyracun.htm and follow the directions to a T on your win7x32 machine, you will be unlocked with s-off.
once you're done with that, go here http://teamw.in/project/twrp2/98 and download the openrecovery-twrp-2.3.1.0-jewel.img file to the RabiesShot_WIN folder that you just used to do your s-off (because the fastboot.exe is there, just use the command prompt from that folder like you did for the racun) and use the fastboot method (boot to bootloader, vol-dwn to fastboot, pwr, plug in usb, enter "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" command)
after that's done you can try to reboot to recovery, though mine always boots to system the first time after i've flashed recovery, to confirm it's there, or just let the phone boot to system, plug in your USB and download the CWM installable zip from the bottom of the OP in this thread http://forum.xda-developers.com/showthread.php?t=1538053 to your USB card someplace where you know you can find it.
then power off your phone, boot to the bootloader again, pwr-dwn to recovery, hit power button, welcome to TWRP, tap Install, browse the the zip you just saved, install, reboot to system, and you have root
Click to expand...
Click to collapse
Thanks, im gonna have to try that tomorrow when i get to my win7 x32. Miss my good ol' evo, she was always good to me.
well then.. its unlocked, s-on. the ruu.zip was carried out just fine. gonna do it again in case i messed up
emwarf said:
well then.. its unlocked, s-on. the ruu.zip was carried out just fine. gonna do it again in case i messed up
Click to expand...
Click to collapse
remember you want to be locked after step 6 before running the RUU
pay attention to step 9 if you get that error message just do what it says, hit the up arrow to start the RUU process again. ( i had to do it twice before it actually completed fully )
I was actually able to re-use my original unlock token for step 11 from when i'd unlocked before.
so you'll lock
run RUU (will see a lot of output if it actually finishes, i think i even booted to system once to confirm)
then you'll unlock
then run the rabiesshot, which does take a while to run through completely and your phone will restart at least a half dozen times. just watch the command window and it'll say when it's totally finished
dangle79 said:
remember you want to be locked after step 6 before running the RUU
pay attention to step 9 if you get that error message just do what it says, hit the up arrow to start the RUU process again. ( i had to do it twice before it actually completed fully )
I was actually able to re-use my original unlock token for step 11 from when i'd unlocked before.
so you'll lock
run RUU (will see a lot of output if it actually finishes, i think i even booted to system once to confirm)
then you'll unlock
then run the rabiesshot, which does take a while to run through completely and your phone will restart at least a half dozen times. just watch the command window and it'll say when it's totally finished
Click to expand...
Click to collapse
MONEY! this is great. got my beloved evo back. miss being rooted so much. I was stupid and renamed a file when I downloaded it so I could identify it more easily. just had to call it the new name instead. big help you are! id still be fighting to find some updated rooting stuff on the net, or id be remaining blind to some stupid fault of my own. thank you!
took me months to find this thread. thank you jeebus. VERY HELPFUL! perhaps even sticky-worthy to nubs like myself.
in the past, using various phones, every time I flashed CM it would install SU automatically (i think)... so can I skip that step, put the chosen CM stable build on the SD card and be done with it?
richard head said:
in the past, using various phones, every time I flashed CM it would install SU automatically (i think)... so can I skip that step, put the chosen CM stable build on the SD card and be done with it?
Click to expand...
Click to collapse
correct. cm is already a rooted rom.
I like this thread. I'm going to give it a try when I get my hands on a 32 bit windows 7 PC, since I have no idea how to use liveCD.
sorry but ive been trying t unlock and root my rezound for months and no i know i have a great quide on phandroid but i cant get unlocking to work. i type the adb devices command and my phone shows up but then when i type"fastboot devices" my phone wont be recognized by my computer can someone help me asap. i have a windows 8 64bit laptop
I have unlocked on windows 8 64bit before. Same way as any other Windows. Go into your device manager and see if your phone is an unconfigured device and make sure adb on phone is turned on.
Sent from my HTC6435LVW using Tapatalk 2
Can you help me with that
Flyhalf205 said:
I have unlocked on windows 8 64bit before. Same way as any other Windows. Go into your device manager and see if your phone is an unconfigured device and make sure adb on phone is turned on.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
How do i do that and im new so i dont really understand alot but itrecognizes it when i do "adb devices" but not "fastboot devices"
Can you give me a link to how you unlocked and rooted your rezound please? up to date
I would start here:
http://forum.xda-developers.com/showpost.php?p=37515020&postcount=444
That'll give you an overview of what you will need to do to get a custom ROM on there. Also, there's a folder attached there that has what you need to use fastboot.
If you don't have your unlock token from HTC yet, go here:
http://www.htcdev.com/bootloader/
Here's a guide to unlocking:
http://forum.xda-developers.com/showthread.php?t=1416109&highlight=unlock
There's a link to "One Click Root" at the bottom but I don't know if that's current. I've never used it. You can just flash Amon Ra after unlocking. Get it here:
http://forum.xda-developers.com/showthread.php?t=1339679
Just download v3.16. Don't worry about the attached files. Just grab it from the v3.16 link right above the attachments. Put that in the same folder you're using for flashing and type this:
fastboot flash recovery {nameofrecovery}
Then navigate in there to developer section and root.
Then make a nandroid immediately and append it with "_stock" so you always have it to go back to.
Now you are ready to flash a custom ROM.
Since you are s-on you will need to flash the kernel from the ROM after you flash the ROM. Some ROMs create one on your sd card in which case you will probably end up at the bootloader with it asking if you want to update, say yes. If not, you need to pull it from the ROM, put it in the "android" folder and flash in fastboot. I would pull it out ahead of time in case so you're ready.
fastboot flash boot boot.img (or whatever the name of the kernel is)
I'll try to keep this as brief as possible. I've been trying to get S-Off so that I can downgrade my hboot so that I can install CM10.1. My bootloader is unlocked. My current hboot is 1.57. I am using 4ext recovery. I also cannot use the wire trick because I don't know how to install the adb driver or whatever you need for juopunutbear. I tried using the guide on htcevohacks, but it is almost two years old and the sdk pack has changed from what he is using. If anybody has any advice or know of any alternatives, it is appreciated. I am just wanting to try out a decent jelly bean rom. thanks.
S-OFF is fairly easy as long as you follow the steps. As for the adb drivers use this link: http://d-h.st/kba it includes what you need and nothing else (for working adb).Also use this for the jbear trick: http://unlimited.io/downloads/jb/shooter/ControlBearRelease_shooter_ICS_WIN.zip These are the steps i used to gain s-off and i was able to get it first try.
Read it once then read it again tho before you try it. just make sure you understand the steps before you try it and youll be fine
READ BOTH OF THESE! How-To/Main Instructions and Detailed instructions for HTC EVO 3D. It is IMPORTANT you read them to have an idea, watch the video. This is NOT hard, but keep in mind:
You are only tapping the wire a split second, don't hold it in place
You need to have an insulated cable. Do not TOUCH the cable/components with bare hands.
Patience, it may take in the first couple tries it may not, it took me over 15 tries to finally get it.
After you are ready, run "ControlBear.exe" from the JBear ICS Tool folder we downloaded
It may take several tries with the wire trick, once done correctly the program will move on. Otherwise it will repeat the message to do the wire-trick.
It is not necessary to install the custom HBOOT, when you are given the choice, decline. If you are curious about what this does, ask their support on the official page.
I don't have any screenshots for this, but its all pretty automated, and mentions a lot of "beer". It will also attempt a backup of boot, recovery, and sdcard.
If done successfully, you are now S-OFF! (You can confirm by turning phone off and Vol Down + Power key to check).
credits to crimsy and his excellent guide: http://forum.xda-developers.com/showthread.php?t=1813818 :good:
Thanks for the reply. How do I install the drivers? In my device manager the thing I see is "Android USB Devices" and in that is "My HTC". It doesn't show up as "ADB Devices" like it's supposed to. I have my phone on charge only and usb debugging.
Wait. Never mind. Apparently that is also right.
To setup adb all you need to do really now is extract the folder from the first link i gave you to a folder on C:\ (root of your harddrive) then open a cmd prompt as admin (run as administrator in right click menu) then type
Code:
cd C:\<folder name>
<folder name> = whatever you named the folder where you extracted the files. then you can run the adb commands such as adb devices