I tried a while ago to unlock my bootloader using HTCDev when it first came out, would get to the part where the confirmation screen should pop up on your phone screen to unlock the bootloader but the screen never showed after multiple attempts, so frustrated, I gave up and told my self I'd come back later. Well later came around a few days ago and I attempted to unlock the bootloader again with the same results as the first time, get to the point where I'm supposed to confirm on my phone screen but it never shows. Did some research to find out the OTA version of the update to ICS could have possibly been the problem, but before I went any further I did a full backup of my phone using Carbon, then did a factory reset from the fastboot menu. Now the problem is, after I did the factory reset my computer no longer recognizes my phone when I plug it in. It can't find HTC sync on my computer even though it is, adb devices shows nothing, same with fastboot devices in fastboot mode. My computer recognized the phone just fine up until the factory reset. So I guess my question is, what caused this to happen and how can I fix it? Also, maybe some help unlocking my bootloader? I think I have to flash the RUU but my phone is 2.95.651 and I don't think it lets you go backwards unless you are S-OFF?
Edit: I guess I should mention that I've tried uninstalling and reinstalling the HTC drivers, usb debugging is enabled and Fast Boot in the power options is disabled, I'm also using the USB cord supplied with my phone, tried different USB ports, performed a second factory reset, made sure all my SDK stuff was up to date, and scoured these forums for 2 days now trying to figure it out (apologies if I missed the one thread with all the answers I need, I did try though). Additionally, in fastboot when I plug in my USB cord it switches to fastboot usb, but nothing shows up on devices, which I find really odd.
Anybody have any ideas/solutions for this?
Yep,
http://androidforums.com/showthread.php?p=5810229
I used srs root to gain a root shell followed scotty85's instructions to set mainver low via adb shell then used the brick downgrade hboot method and followed it up with 1.13 ruu and finished with revolutionary
Post #50 is my instructions and scotty85 are a few posts back
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
embersanenders said:
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
Click to expand...
Click to collapse
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
thewraith420 said:
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure if they use the same hboot or not. I was able to flash 2.89 RUU in the temproot state on hboot 1.58.0000. After the flash I retried unlocking the bootloader through HTCdev and it worked flawlessly. Then I was able to root it and juopnutbear s-off, which applied juopnutbear hboot 1.58.5858. It seems like temprooting the phone using your method and flashing a 2.89 RUU might be the workaround for people who have trouble using HTCdev due to the OTA update.
I should also mention someone suggested this method on phandroid forums (scott actually, I believe) on a different thread and so I tried it. I was going to link his post here but I haven't met the link post requirement yet. So as a disclaimer, this isn't my idea, it just worked so I posted here.
Now that I'm home from work I figured I could give a more detailed list of what I did to root my Evo 3D, I feel the information above gets a little confusing with so many different places to go. As previously stated I had trouble unlocking my bootloader using HTCdev, it would get to the step where you confirm on your phone the unlock but never show up, I found this was usually caused by updating your phone to ICS using the OTA as compared to an RUU. Somehow something gets messed up and your phone never wants to confirm, hopefully this will help people who don't want to brick/downgrade hboot in order to be able to root their phones but can't unlock from HTCdev do to this error. Anyway, on to it.
1. Download SRSRoot
A 2.89 RUU
The files from [Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)
2. Run SRSRoot
3. SmartRoot
4. Follow the steps until your phone restarts and you just have a status bar at the top (this is your 'temproot')
5. Close SRSRoot (you may have to kill in the task manager, or at least I did to get it to completely quit mid-steps)
6. Navigate to the folder where the files from the 'QnD' guide and open the cmd link in the Root folder.
7. Type, or copy & paste the following in order (not the stuff in brackets like this, these are notes);
adb devices (should return your phones serial number, indicating drivers are working, and you're connected)
adb push misc_version /data/local/tmp/misc_version
adb shell (should change your prompt to a #, if not, have your phone awake and watch the screen to grant superuser permissions when you enter su (not likely applicable here))
chmod 777 /data/local/tmp/misc_version (have your phone awake and be watching it, in case superuser needs you to grant permission (again, not likely applicable))
/data/local/tmp/misc_version -s 1.00.000.0
exit (exit again if your prompt changes to a $)
8. Run your 2.89 RUU exe (it should run and reinstall 2.89 to stock, you may lose information, unsure about that though, so back ups are always recommended)
9. Restart your phone after the install if it doesn't happen automatically
10. Retry unlocking using HTCdev method
Hopefully at this point the bootloader actually unlocks for you and you can start at Step 2 of the 'QnD' guide to get root access and S-Off.
Big thanks to thewraith420 for the temproot method and scotty85 over at phandroid for the mainver change directions.
The reason I asked if 2.89 used the 1.58 hboot is just to further understand why it worked I think that setting the mainver is what let you run the ruu. And it didn't complain about the hboot because they use the same one. Nicely done getting the info together.
Sent from my PG86100 using Tapatalk 2
misc_version location
embersanenders said:
adb push misc_version /data/local/tmp/misc_version
Click to expand...
Click to collapse
I was encountering the same issue as you for the HTC bootloader unlock, so thanks so much for this info, it worked like a charm. It might be helpful for others to know that you can find the misc_version referenced by downloading the file scotty85 mentions in his post on guide-how-manually-downgrade-firmware-build-6-01-605-05 (Sorry, I'm unable to post the link)
Related
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
So, over 80 views and no-one has an answer for this?!
ratedr75 said:
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
Click to expand...
Click to collapse
ratedr75 said:
So, over 80 views and no-one has an answer for this?!
Click to expand...
Click to collapse
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
joeykrim said:
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
Click to expand...
Click to collapse
ratedr75 said:
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
Click to expand...
Click to collapse
I've quoted my previous post to highlight the steps outlined. I never mentioned anything about another ROM.
If the theory holds, as it was true for unrevoked's method of s-off and some members of unrevoked are now part of AlphaRevX releasing the revolutionary tool, you only need to flash a custom recovery through fastboot or bootloader.
If you have adb setup, it would literally take you 10 seconds to issue the fastboot command and another 10 seconds to reboot into recovery to see if t worked.
Currently, when you boot into recovery and you see the triangle, that is the stock recovery. Sometimes on the stock recovery screen, if you want to activate the menu, pressing vol up + pwr *should* work in stock recovery but sometimes manf like HTC change this function in the version of recovery they distribute.
Once you use the command: fastboot flash recovery c:\android\cwm-recovery.img , you should be able to boot into recovery and see the custom recovery load.
If that method doesnt work, the other method to attempt is loading a PG86IMG.zip file on the root of the sdcard with the custom recovery inside the PG86IMG.zip. Upon booting into the bootloader, it should scan this file and ask to update. If you select yes to update, the bootloader should flash and you should have a custom recovery.
If neither of those two methods work, you'll likely have to use the HTC unlock method. But I think those methods should work as your device still shows S-OFF.
Good luck!
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
ratedr75 said:
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
Click to expand...
Click to collapse
The issues you're experiencing are due to HTC's complex locking method to deter root access. There are many Android devices which come stock with no locking protection or must less sophisticated locking protection.
If you're not able to properly setup adb, then the PG86IMG.zip method should be more convenient for you. All you need to do is put a PG86IMG.zip file onto the root (main dir) of your sdcard and holding vol down + pwr (boot into the bootloader). From here, it will scan the PG86IMG.zip and prompt if you want to load. Choose yes and this will flash the custom recovery.
Once the custom recovery is loaded, you should be able to flash a rooted ROM from, flash superuser .zip file or adb push su binary to restore root.
HTC intentionally makes this process difficult and it is relatively more difficult than other Android devices. All the resources are here at your disposal but HTC requires a bit more work/effort/learning to accomplish what is easier on some other Android devices. Although, even the Google Nexus S requires using fastboot to unlock t he device.
Nobody wants to see anybody give up and abandon. Hope that helps!
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off. You need to put the custom recovery in a zip and name it PG86IMG then flash it from the bootloader and it will work.
fyi you should always be able to run a stock RUU (even new ones) because Revolutionary for the evo 3D gave you actual radio s-off and not just fake s-off with a patched hboot which is how Revolutionary worked on most phones. radio s-off pretty much means your phone will never go back to s-on even with a stock RUU. that is why you were able to upgrade the hboot and still keep s-off.
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
patrick92260 said:
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off.
Click to expand...
Click to collapse
fastboot commands don't work on the EVO 3D? even for recovery?
I haven't seen this complaint on the Q&A board. Majority of users seem to have plenty of success using fastboot to flash kernels and custom recoveries. Although, majority of people posting on the Q&A board recently have the latest hboot and can only use HTC's unlock method. Perhaps this is only an issue on revolutionary s-off devices?
ratedr75 said:
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
Click to expand...
Click to collapse
I went to google.com and typed in the phrase, "twrp PG86IMG.zip" and the second link looks to be the quickest to obtaining the file:
http://teamw.in/project/twrp/67
I have heard pretty decent reports of Sony being fairly support of developers and allowing their devices to be unlocked and rooted.
Good Luck!
Thanks guys. Again. Now would anyone be interested in purchasing the EVO 3D GSM sim free from myself?
hi I am in the same position as the OP, just got my phone 2nd hand..want to flash LeeDroids Rom, my phone is GSM version, please advise how to get custom recovery..thanks
OK so I'm trying to downgrade my phone from Honeycomb to gingerbread. Thus far I've unlocked the bootloader, installed super user, well anyway I'm at the point of installing the RUU. According to globaltrons guide, my flyer which is a 16 gig wifi US only model, should use one of the brightstar firmwares. Well I tried both and I get an UNKNOWN ERROR 1555 telling me I have the wrong RUU. Now my flyer is sitting here draining the battery and I can't get it to turn off. And can someone just tell me what RUU I need? I'm sure all 16 gig us flyers are the same anyway. Its the refirb from buy.com. Anyone else who bought one probably has the same RUU
Alright help just isn't coming fast enough so I finally got it to shut off. I just remembered the 3 button trick from my captivate and waddayaknow it worked on the flyer. Now I'm going to try again and see what RUU i'm supposed to run.
Alright now that I'm out of that mess I checked the CID again and its BS_US001, and according to the guide, I should use a brightstar RUU. Well there are 2 and I tried both and both told me I'm using the wrong one. So what the hell?
i would try following this guide
http://forum.xda-developers.com/showthread.php?t=1358758
If you need to get to fast boot you should be able to do that by holding power and volume down for around 20 seconds
Do you have the Fastboot drivers installed?
I should have fastboot drivers installed. I mean I've connected it fastboot and ran many adb commands...doesn't that mean fastboot drivers are installed? Also the RUU gets to "signature verification" and fails every time!! I actually went back through and changed the version number to the version number of the other brightside ruu and same issue! Globaltron's guide must be wrong.
Anyway my tab is running right now on stock honeycomb, just no progress is being made here and its frustrating the hell out of me! I've been stuck on the same damn step for 2 days now!
the link for the BASE RUU you need is http://hyuh.net/files/flyer/RUU_US_WIFI_B10.zip
This will get the device charging again, howver you will then have to flash a custom ROM,
Globatrons Guide will show you how to use the light version i have linked to.
Any questions just as as i have done the process lots of times
Give me the details of where you started from and what you did. I think you missed a couple steps
Alright cool, but does it turn off security? I still got S-on as I need that RUU installed so I can disable it.
Cor-master said:
I should have fastboot drivers installed. I mean I've connected it fastboot and ran many adb commands...doesn't that mean fastboot drivers are installed? Also the RUU gets to "signature verification" and fails every time!! I actually went back through and changed the version number to the version number of the other brightside ruu and same issue! Globaltron's guide must be wrong.
Click to expand...
Click to collapse
Ok well boot the device into fastboot then put the file i have linked tointo the same folder as your fastboot normall C:/android/Android-skd-windows/Tools
Then run the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <downloaded file name>
Flashing will fail with Error 90 first time due to hboot change (this is normal)
fastboot flash zip <downloaded file name>
The on screen indicator on the phone will not reach fully to the right end of the progress bar, this is ok
fastboot reboot
---------- Post added at 12:42 AM ---------- Previous post was at 12:38 AM ----------
Cor-master said:
Alright cool, but does it turn off security? I still got S-on as I need that RUU installed so I can disable it.
Click to expand...
Click to collapse
Ahhh, with it being S-ON Nots ure this will work. :/ Sorry Dude
MCNord Any ideas ?
mcord11758 said:
Give me the details of where you started from and what you did. I think you missed a couple steps
Click to expand...
Click to collapse
I first unlocked the tablet through HTC developers. Then I followed step by step and installed revolutionary, and then used revolutionary to install super user permissions. I then ran this command:
fastboot getvar cid
To get the CID. The CID came back as BS_US001. So I looked at Globaltrons guide and according to it, the ones that say "Brightstar" are the ones I need. 2 came up, but the numbers that were supposed to match, matched on both, so I just picked one. the download was capped so bad from that file sharing site that I just let it download overnight and went to bed.
So today I resumed my work. I next ran these commands
adb push misc_version /data/local/misc_version
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s (whatever the version number was)
and then I rebooted into fastboot, ran the first RUU and UNKNOWN ERROR
So I repeated the last steps with the other RUU and UNKNOWN ERROR...
Cor-master said:
I first unlocked the tablet through HTC developers. Then I followed step by step and installed revolutionary, and then used revolutionary to install super user permissions. I then ran this command:
fastboot getvar cid
To get the CID. The CID came back as BS_US001. So I looked at Globaltrons guide and according to it, the ones that say "Brightstar" are the ones I need. 2 came up, but the numbers that were supposed to match, matched on both, so I just picked one. the download was capped so bad from that file sharing site that I just let it download overnight and went to bed.
So today I resumed my work. I next ran these commands
adb push misc_version /data/local/misc_version
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s (whatever the version number was)
and then I rebooted into fastboot, ran the first RUU and UNKNOWN ERROR
So I repeated the last steps with the other RUU and UNKNOWN ERROR...
Click to expand...
Click to collapse
Are you S-Off Yet ?
If yes try the file i suggested, its quick and easy and then allow you to flash custom roms
p.s. i will be able to stop up until you get this sorted. So we will try it now
I'm not because if I read correctly I have to be on gingerbread to turn it off. And thats where I'm at now. The tablet has stock Honeycomb 3.2 installed. I'm basically just trying to get from stock honeycomb, to honeycomb with S-off if that helps.
Were you on hc or gb, does your bootloader say soff, what is your end game here
I got my tablet on February 29th and did the ota update to honeycomb as soon as I had it. I've kept it stock till now. My end point is honeycomb with S-off basically. If I can get to honeycomb S-off without going back to gingerbread first than I'm all for it, but if I read correctly, you have to be on gingerbread with s-off to go to honeycomb with s-off.
After all that I figured I might install leedroid.
Cor-master said:
I'm not because if I read correctly I have to be on gingerbread to turn it off. And thats where I'm at now. The tablet has stock Honeycomb 3.2 installed. I'm basically just trying to get from stock honeycomb, to honeycomb with S-off if that helps.
Click to expand...
Click to collapse
Ok i understand where you are now , firstly are you still getting the problem where your device isn't charging ?
And the RUU you have downloaded is definitely correct ?
Man do I miss my captivate. It was as simple as #1. Plug in computer. #2. Install super one click, and you could install any rom you wanted... but it didn't have a security lock, nor did it ever have a locked bootloader either.
ioiwillioi said:
Ok i understand where you are now , firstly are you still getting the problem where your device isn't charging ?
And the RUU you have downloaded is definitely correct ?
Click to expand...
Click to collapse
Oh sorry, no I got my tablet to reboot. Its sitting on my desk idling in stock honeycomb right now. And it charges fine. I just can't get an RUU to run. There are 2 brightstars so I downloaded both, and neither work. Maybe there's a third one , but according the CID the brightstar one SHOULD work, it just doesn't. According the readme with the RUU the error I"m getting means incorrect RUU.
Ex captivate user here as well, yea this is a bit more
Did you relock bootloader prior to attempting ruu
Cor-master said:
Oh sorry, no I got my tablet to reboot. Its sitting on my desk idling in stock honeycomb right now. And it charges fine. I just can't get an RUU to run. There are 2 brightstars so I downloaded both, and neither work. Maybe there's a third one , but according the CID the brightstar one SHOULD work, it just doesn't. According the readme with the RUU the error I"m getting means incorrect RUU.
Click to expand...
Click to collapse
Just tried downloading them to check the RUU and the link seems to be broken, did your deffinately download ok ?
Whats the filesize, GLobatrons guide has been spot on for hundreds of users
no its still unlocked. I just had a thought here. 2 ideas actually. #1. I don't have an sd card currently in, as I never bought one for my flyer. On the steps that required an sd card I just pulled the one from my phone. I dunno maybe the RUU wants to copy itsself to the SD-card but can't because its not there. Also #2. I did reinstall my apps last night so I could use my tablet today, which are all in the internal storage. If I wipe my tablet and put an SD-card in, might that fix the problem?
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!
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
Hello guys,
I apologise if I have created a duplicate thread for this issue-but I HAVE looked everywhere to find a solution to this. I am not a 100% expert so please excuse me if I am being a time-wasting nerd.
However, in a few words, the problem I am having is:
I bought HTC DROID DNA (from the states-brand new) and I managed to unlock the bootloader (S-Off) using the info from these threads and for some really silly reason I decided and managed to relock it. Now it is showing ''Relocked'' and ''S-ON''.
I have tried everything I could find so far to unlock the bootloader (i.e. S-Off) (rumrunner,moonshine, traditional method(since I ve got the original unlock token)).
Can anyone please, please let me know how to S-Off as I would like to install a custom ROM since I can't get any updates in the UK-(which I don't see coming anytime soon anyway.)
Thanks very much.
Harry
stifer said:
Hello guys,
I apologise if I have created a duplicate thread for this issue-but I HAVE looked everywhere to find a solution to this. I am not a 100% expert so please excuse me if I am being a time-wasting nerd.
However, in a few words, the problem I am having is:
I bought HTC DROID DNA (from the states-brand new) and I managed to unlock the bootloader (S-Off) using the info from these threads and for some really silly reason I decided and managed to relock it. Now it is showing ''Relocked'' and ''S-ON''.
I have tried everything I could find so far to unlock the bootloader (i.e. S-Off) (rumrunner,moonshine, traditional method(since I ve got the original unlock token)).
Can anyone please, please let me know how to S-Off as I would like to install a custom ROM since I can't get any updates in the UK-(which I don't see coming anytime soon anyway.)
Thanks very much.
Harry
Click to expand...
Click to collapse
Why don't you look at the sticky at the top of the Q&A section. It is the same section you posted your question in!
RLGL said:
Why don't you look at the sticky at the top of the Q&A section. It is the same section you posted your question in!
Click to expand...
Click to collapse
I have. I tried to do what it says there, i.e. CID shows 1111111 and then trying to flash the unlock token but it is not working, it says Error for some reason.
stifer said:
I have. I tried to do what it says there, i.e. CID shows 1111111 and then trying to flash the unlock token but it is not working, it says Error for some reason.
Click to expand...
Click to collapse
tried firewater?
RLGL said:
tried firewater?
Click to expand...
Click to collapse
Thanks, I have just tried that, but get stuck at ''su'' step. I 've looked it up and it says that you need some sort of temp root? which I don't understand what exactly it is. So still stuck.
stifer said:
Thanks, I have just tried that, but get stuck at ''su'' step. I 've looked it up and it says that you need some sort of temp root? which I don't understand what exactly it is. So still stuck.
Click to expand...
Click to collapse
it took 30 seconds to find the following using the search function:
Default [Guide] Firewater S-Off
Disclaimer
License: Firewater S-Off is the result of many hours of hard work by beaups and fuses. The firewater binaries you download may not be shared, rehosted, bat’d, integrated into a one-click, repackaged, hotlinked, or otherwise distributed or reused. The source code and methods in firewater are closed and private.
Temproot is a hack-up build of android_run_root_shell which appears to be a work of hikezoe and fi01. Original source can be downloaded HERE, our modified mess will be made available on this website soon.
This software is provided free of charge for personal non-commercial use. For commercial use or redistribution a WRITTEN agreement with the authors is required.
Support: support for firewater s-off is available at #firewater on the freenode and andirc networks. Please make sure you meet all of the requirements before contacting support.
Official website: http://firewater-soff.com/
Welcome to Firewater
What firewater can do for you:
S-Off your HTC device
Unlock yout bootloader
There are two methods which can be used to achieve S-Off:
Method n.1: to be used with and HTCDev unlocked/rooted device;
Method n.2: temp-root method, to be used if you don't want to unlock your device through HTCDev (it may not work with all devices);
Prerequisites
Working adb on your PC (Windows, Linux, OSX, etc. are all supported);
HTC drivers installed and working
HTC sync removed (not closed - REMOVED)
All other phone software removed or disabled (Samsung Kies, PDANet, etc.)
A working internet connection on your device (Wifi, 3G, 4G, etc. are all supported). There is no way around this requirement, don’t ask;
USB debugging enabled on your device;
Your device must be HTCDEV unlocked/rooted or have a working temproot. A temproot that works with many modern (not all) HTC devices is provided below;
Do not attempt to run firewater from a terminal emulator on your device. You MUST use adb along with a PC;
A supported device. Firewater *should* work with most modern QUALCOMM based HTC devices, including (but not limited to) the HTC One, HTC Droid DNA, HTC One S, HTC One Max and many others.
Instructions: method n.1 (normal, rooted device method)
Once you confirm you meet the above pre-requisites, it’s time to get started.
Ensure device is booted to android with usb debugging enabled
USB 2.0 ports are preferred. You should not be connected using any hubs which may cause connectivity issues;
Ensure that lock screen security is disabled on your device (no passcode lock, no pattern lock, no face lock);
Download Firewater Search the download from the official site;
Push, prepare and execute Firewater:
Code:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with;
Allow the exploit to do its work;
Profit.
Instructions: method n.2 (temp-root method)
This method may allow firewater to work on a fully stock/HTCDev locked device. This method is being provided as a convenience. Do NOT seek support if this temproot does not work for you.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred. You should not be connected using any hubs which may cause connectivity issues;
Ensure that lock screen security is disabled on your device (no passcode lock, no pattern lock, no face lock);
Download firewater Search the download from the official site;
Download temproot Search the download from the official site;
Push, prepare and execute temproot and Firewater:
Code:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
/data/local/tmp/temproot
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with;
Allow the exploit to do its work;
Profit.
Donate
Donate to Firewater developers
Donate to me (if you appreciate the guide; thank you!)
Thanks for that. I did try that, and now it says '' Tampered'' and ''Relocked'' and ''S-ON''. I don't understand why this is happening.
I had a similar issue. To resolve, I used the PC to RUU back to stock then started over with firewater.
Good luck.
Icyman said:
I had a similar issue. To resolve, I used the PC to RUU back to stock then started over with firewater.
Good luck.
Click to expand...
Click to collapse
Thanks again for your reply. I tried that just now. Still showing tampered, relocked and s-on. This is unbelievable. I don't think I 'll ever be able to unlock this bootloader and I don't know why!c
stifer said:
Thanks again for your reply. I tried that just now. Still showing tampered, relocked and s-on. This is unbelievable. I don't think I 'll ever be able to unlock this bootloader and I don't know why!c
Click to expand...
Click to collapse
Did you use the unlock bin from HTC?
Icyman said:
Did you use the unlock bin from HTC?
Click to expand...
Click to collapse
The first time I unlocked it which was almost a year ago I used the unlock key, tried the same two weeks ago but did not succeed. I hope this is the answer to what you asked me. (sorry if I misunderstood- I am not an expert)
thanks very much Icyman
stifer said:
The first time I unlocked it which was almost a year ago I used the unlock key, tried the same two weeks ago but did not succeed. I hope this is the answer to what you asked me. (sorry if I misunderstood- I am not an expert)
thanks very much Icyman
Click to expand...
Click to collapse
You need to use the same bin file after ruu.
But I think firewater should work too.
I used firewater on 4 phones. I only had problems when I missed a step. Try again from the beginning. From stock after ruu.
Icyman said:
You need to use the same bin file after ruu.
But I think firewater should work too.
I used firewater on 4 phones. I only had problems when I missed a step. Try again from the beginning. From stock after ruu.
Click to expand...
Click to collapse
Hi Icyman, That is what I did, I flashed the original RUU and then deactivated fast reboot, enabled debug. mode, installed weaksauce-1.01 and finally went ahead with firewater. (device always hungs with firewater in the end and I have to hold the power button down for 60s as it says-not sure if that makes a difference)
Will try again as you suggest though.
I really appreciate your help. Thanks very much.
stifer said:
Hi Icyman, That is what I did, I flashed the original RUU and then deactivated fast reboot, enabled debug. mode, installed weaksauce-1.01 and finally went ahead with firewater. (device always hungs with firewater in the end and I have to hold the power button down for 60s as it says-not sure if that makes a difference)
Will try again as you suggest though.
I really appreciate your help. Thanks very much.
Click to expand...
Click to collapse
I never used weaksauce on DNA. Maybe that's the problem.
Icyman said:
I never used weaksauce on DNA. Maybe that's the problem.
Click to expand...
Click to collapse
That's the only way I can apply temproot and then firewater, I can't find the original temproot file anywhere and I thought that weaksauce is the updated version of the temproot file. If you could send me the temproot file somehow that would be great,-just to see if it could work...
Any further advice guys? Please?!!! I've got this phone but the outdated software makes it useless.