• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root S-OFF, root, & Fix Everything All-in-One!

The worst I've seen, and it happened to me as well, is the phone went completely unresponsive. No charge light or anything. I left mine plugged in overnight per instructions from unlimited. Still nothing happened. Then I pulled the battery and put it back in and it was finally responsive.

I think I've only heard of one case where the phone was not recovered from an s-off emergency, and even then, I'm not sure they tried the more difficult recovery options.

Obviously there is some risk, but if you follow the instructions as closely as possible, you should be pretty safe.

Two pointers:
1.) Backup your SD card contents to your PC. There is a risk of damaging your SD card with the wire trick and losing everything. If it's backed up you can at least restore it to a new sd card if necessary.

2.) watch this video to help with the timing which is probably the most crucial part: http://htcevohacks.com/htc-evo-...evo-3d-using-wire-trick-juopunutbear-s-off/
 
Yea I have ready watched it iam just new with this phone an scard If it does mess up i wont know what to do but soon as I get brave iam give it a try. I tryed to.flash a rom last week an it wouldnt boot an wouldnt restore a back up an boot I had to fastboot the boot img an took me all Night to figure that out
 
Ah yes. Once s-off you won't have that issue anymore. Also, even while s-on, if you use 4ext recovery with smart flash enabled, you can flash roms without having to flash the boot.img separately.
 
Brian706 said:
The worst I've seen, and it happened to me as well, is the phone went completely unresponsive. No charge light or anything. I left mine plugged in overnight per instructions from unlimited. Still nothing happened. Then I pulled the battery and put it back in and it was finally responsive.
Click to expand...

Same thing happened to me when I was going through the S-OFF procedure. For a second, I thought I bricked my phone.
 
So wnen i try an s off an it does bad first try an pull the battery an c If it comes back then since I cant run the ruu what would I try next I just to know what all to try an do to fix it before I try an off it
 
Where did you find them? Are you going directly to the source? There is only one vm download at unlimited and they say to use a live Ubuntu cd. I'd highly suggest doing this as opposed to the old windows version. Far less chance of something going wrong.
 
If you really want to use the windows version, I would follow remamifest's guide. He did a thorough job on it specifically for the EVO V. I've seen it work countless times. :)

Once again though I would recommend the live cd and downloading the juopunut bear software from unlimited, but it's your call. ;)
 
Ok If they are for 157 hboot an i have 158 do u think it work without any problem an for now I was just Gonna not install the j bear boot an stay with 158
 
Oh man. As far as which roms you can flash, 1.57 and 1.58 will both allow the same roms.

I'm almost 100 percent sure that people on hboot 1.58 (March ota) have been successful following remamifest's guide. The problem is, nothing is guaranteed. Some people have issues, some don't. The best advice I can give is to follow the directions as written by the developer of the s-off exploit.

I just want to be clear, the live cd is the safest way to go. That's what I recommend... I think you could get away with us in either of the two guides but, well, I won't beat a dead horse about the live cd anymore.
 
Can u give a Link of roms safe to flash with the vm evo 3d 158 h boot I think iam stay s on to scard ill brick it an not know how to fix it every Link I can find.with roms dosent say with h boot to have or as just as long as it the same andriod verson I have now are they the roms that will work
 
Guys, Please help. I get stuck here when screen goes to JuopunutBear & does not go any further. Thanks in advance!
Starting up......
Connecting to device...
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (8/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (11/60)** daemon still not runningerror: cannot connect to daemon
Waiting ADB.... (12/60)** daemon still not runningerror: cannot connect to daemon
Waiting ADB.... (13/60)** daemon still not runningerror: cannot connect to daemon
Waiting ADB.... (14/60)** daemon still not runningerror: cannot connect to daemon
Waiting ADB.... (15/60)** daemon still not runningerror: cannot connect to daemon
Waiting ADB.... (16/60)
Click to expand...
 
MArcelloMayhem said:
Guys, Please help. I get stuck here when screen goes to JuopunutBear & does not go any further. Thanks in advance!
Click to expand...

Try going into task manager and kill the adb process. Then try again.

Also try disabling any possible interfering software (HTC sync, iTunes, etc)
 
Hello,

First of all, i want to thank you for this great guide! :D
It was very easy to follow and the results are a warranty.
Unfortunately, I am having a few problems with my phone after I followed this guide!
Well it might had been the other things I did after I was done with the guide! xD

Anyway, I followed the guide: I got S-off, rooted, flashed 4ext, and flashed Harmonia 3.17 rom.
After I was done, I flashed anthrax kernel to try to overclock my phone.
Then I noticed that my usb debugging did not work, and my phone does not detect wifi signals. Those are the two main problems that I had noticed up to now.
Are those problems normal on the rom I am using, or is my kernel not compatible with this rom (I found my kernel here http://androidforums.com/4878439-post1.html)?
Does anybody else have similar problems? How can I solve this?

Also this might sound silly, but i am a little confusing and I do not know it this step took place on this guide: I want to obtain better signal. My question is, did we flash a new radio on this guide! I read on other guides that you need to flash a new radio in order to obtain a stronger signal.
I might follow this guide in order to get better signal http://androidforums.com/evo-v-4g-a...ng-turning-your-phone-into-evo-3d-thread.html
 
So I had an unlocked phone with S-on. I had a custom rom installed. I was attempting to revert it back to stock with this guide and first I downloaded and flashed the setmainlowversion, then I went to the bootloader with usb plugged in and did the fastboot oem lock command. I downloaded the ROM update utility and attempted to run it, it kicks back a USB error on my PC and does not proceed. I spent quite awhile making sure I had the most recent drivers for the evo v 4g, I downloaded and installed htc sync (I quit sync while attempting to run rom update) my htc appears in device manager under the phones connection. My phone is now stuck on the bootloader/fastboot screen. When i power it off, it just turns itself back on. volume dwn+pwr does not work, I can not get my sd card to mount from here and I do not know what to do. I am not really sure how the RUU works really. Im guessing it will download the factory rom?(hoping) My sd card got wiped awhile ago and I do not ahve a factory backup as it has been around 18 months since I flashed my phone and I have forgotten a lot of what exactly I did. Please help!

***RELOCKED***
***Security Warning***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.06.00.0426
OpenADSP-v02.6.0.2226.00.0217
eMMC-boot
Apr 20 2012

FASTBOOT
BOOTLOADER
REBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
 
Glad you got everything sorted, Win 8 is really hit or miss with the drivers being able to detect your device properly. :rolleyes:
OB
 
I'm currently stuck on the step where i need to unlock bootloader. I am in bootloader (i have the white screen), but when I type in "fastboot oem get_identifier_token" in the command, its just says ""<waiting for device> " I'm sure my device is connected to the computer because I used the command to put it into bootloader, so i don't think the problem is the driver or that my phone isn't connected to the computer. Can someone please help me out? thanks in advance for any suggestions!
 
Im have problems during the S-Off procedure - while im running the controlbear execution, everything's going swimmingly, the phone reboots to the bootloader page, the cmd says a few things, but then I start getting messages saying 'failed to start daemon' etc... with a count-down of 60, by which time it gives up. Where have I gone wrong and what do I do!? Thank you!
 
You must log in or register to reply here.
Back
Top Bottom