I have an AT&T HTC One that I have successfully bootloader unlocked and rooted.
I cannot get it to S-OFF
I have hboot 1.44 so I have tried both revone and Moonshine.
I have tried with the stock ROM (don't know what version): ./revone -P would give me error ID 2 and Moonshine would try 10 times with a failure of Don't drink and Shine!
I have tried with Android Revolution based on 4.4: ./revone -P would give me error ID 1 and Moonshine was unable to pass the 2nd ADB test (phone would freeze after rebooting)
I have tried with stock roms based on 4.2 and even on 4.1: ./revone -P would give me error ID -6 and Moonshine would try 10 times with a failure of Don't drink and Shine! I read that -6 was a matter of persistence, but I tried a hundred time on two different roms and had no success.
I read something somewhere that past a certain firmware, the exploit that allowed both revone and Moonshine to function was already patched. Is it impossible to S-OFF my phone now? I'm not 100% sure where to check my software version, but I am on the 4.1.2 Stock-based rom now and under About -> Software Information the Software number shows as 1.26.502.15
Anyone help?
ZippyDan said:
I have an AT&T HTC One that I have successfully bootloader unlocked and rooted.
I cannot get it to S-OFF
I have hboot 1.44 so I have tried both revone and Moonshine.
I have tried with the stock ROM (don't know what version): ./revone -P would give me error ID 2 and Moonshine would try 10 times with a failure of Don't drink and Shine!
I have tried with Android Revolution based on 4.4: ./revone -P would give me error ID 1 and Moonshine was unable to pass the 2nd ADB test (phone would freeze after rebooting)
I have tried with stock roms based on 4.2 and even on 4.1: ./revone -P would give me error ID -6 and Moonshine would try 10 times with a failure of Don't drink and Shine! I read that -6 was a matter of persistence, but I tried a hundred time on two different roms and had no success.
I read something somewhere that past a certain firmware, the exploit that allowed both revone and Moonshine to function was already patched. Is it impossible to S-OFF my phone now? I'm not 100% sure where to check my software version, but I am on the 4.1.2 Stock-based rom now and under About -> Software Information the Software number shows as 1.26.502.15
Anyone help?
Click to expand...
Click to collapse
have you tried rumrunner s-off
boroboy69r said:
have you tried rumrunner s-off
Click to expand...
Click to collapse
Of course I ran across rumrunner in my searches here http://forum.xda-developers.com/showthread.php?t=2488772
But according to this post, the hboot must be version 1.54 or 1.55. It specifically says I must use revone or Moonshine if I am running 1.44. So I haven't tried it yet but I guess it can't hurt ...
ZippyDan said:
Of course I ran across rumrunner in my searches here http://forum.xda-developers.com/showthread.php?t=2488772
But according to this post, the hboot must be version 1.54 or 1.55. It specifically says I must use revone or Moonshine if I am running 1.44. So I haven't tried it yet but I guess it can't hurt ...
Click to expand...
Click to collapse
Check date of bootloader, if it's before June 2013 then use the following ROM to get S-Off, using revone:
Android_Revolution_HD-One_9.4.zip 970.8 MB
https://mega.co.nz/#!aZkF2IIC!UIL4ww1y-bhTq4sQOEVjsi89pmI2GkwCPLMRDlNrrjM
MD5: 06c863ce41b0d5001290737a31e198a1
if the date of bootloader is June 2013 or later then it's a patched version, there's a downgrade method linked here: http://forum.xda-developers.com/showthread.php?t=2431515
nkk71 said:
Check date of bootloader, if it's before June 2013 then use the following ROM to get S-Off, using revone:
Android_Revolution_HD-One_9.4.zip 970.8 MB
https://mega.co.nz/#!aZkF2IIC!UIL4ww1y-bhTq4sQOEVjsi89pmI2GkwCPLMRDlNrrjM
MD5: 06c863ce41b0d5001290737a31e198a1
if the date of bootloader is June 2013 or later then it's a patched version, there's a downgrade method linked here: http://forum.xda-developers.com/showthread.php?t=2431515
Click to expand...
Click to collapse
Thanks so much nkk. Looks like that is exactly my problem. My hboot shows July 5, 2013, so off to follow that guide and I'll let you know what happens.
ZippyDan said:
Thanks so much nkk. Looks like that is exactly my problem. My hboot shows July 5, 2013, so off to follow that guide and I'll let you know what happens.
Click to expand...
Click to collapse
you can also RUU to android 4.3 hboot 1.55 sense your AT&T and then rumrunner will work
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
clsA said:
you can also RUU to android 4.3 hboot 1.55 sense your AT&T and then rumrunner will work
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I tried this but I kept getting error 155 when running the RUU program. I think that is because I had to relock my bootloader first and I didn't know that. Anyway, I got it working with hboot 1.44 now so I think that is better.
nkk71 said:
Check date of bootloader,
if the date of bootloader is June 2013 or later then it's a patched version, there's a downgrade method linked here: http://forum.xda-developers.com/showthread.php?t=2431515
Click to expand...
Click to collapse
Well with persistence I finally got this to work.
There is another link farther down in your link which I think has easier to understand instructions:http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
However, the real key comes in step 3.
I got stuck on step 3 for a while because your link shows three different options for downloading. I assumed that all three were the same. Actually option A and C are the same (http://d-h.st/qEY). They seem to be a TWRP backup. I checked the md5 of my download and unzipped this file to the TWRP backup directory on my phone. But no matter what I tried it always failed to restore.
I finally figured out that option B is a different download (https://mega.co.nz/#!vwJGhYjb!A6D3TjhtSxhPOQwYJZR373gH418YeN3hTfC6uSgJSZA) and it is actually a ClockworkMod backup even though it is labeled as TWRP. So I flashed ClockworkMod to my recovery and unzipped this download to the ClockworkMod backup directory on my phone. I was then able to successfully restore this backup and downgrade my phone to 1.26.502.10.
After that I just had to relock my bootloader, and use the RUU file to get to 1.26.502.12.
I then unlocked the bootloader again, flashed TWRP to my recovery again, and used that to root the 1.26.502.12 install.
I was then able to finally use revone successfully to S-OFF the phone, remove the tampered tag from the bootloader, and set my SUPERCID.
Finally, I installed Android Revolution 41 mod running Android 4.4 and everything is working great!
Thanks!
Related
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
skylineGTR_34 said:
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
Click to expand...
Click to collapse
Wait. So you were s off, then went s on, and are attempting to go s off again? What hboot are you on?
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
CoryTallman said:
Wait. So you were s off, then went s on, and are attempting to go s off again? What hboot are you on?
Click to expand...
Click to collapse
Yes exactly. I am using the same hboot version which is 1.44
Also hboot is still unlocked my be thats the problem ?
At what point in the process are you getting the error?
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
CoryTallman said:
At what point in the process are you getting the error?
Click to expand...
Click to collapse
./revone -P after this commad it waits about 2 seconds and says revone failed (error code -6)
skylineGTR_34 said:
./revone -P after this commad it waits about 2 seconds and says revone failed (error code -6)
Click to expand...
Click to collapse
I may be wrong, but if you've already s off'd, I don't believe you need to do that step. Try skipping on to:
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Click to expand...
Click to collapse
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
I tried every way, no luck.
similar problem
I'm also stuck with "error code = -6" following the ./revone -P step, but since buying the phone from new I've never had it s-off. I've followed every step to a T with absolutely no luck... not sure if there's any binary/kernal stuff that's stopping me getting s-off access...I don't know enough about all that yet.
Anyway if anyone has any advice or has found a way round this issue it'd be awesome to hear from you.
Cheers
Clough85 said:
I'm also stuck with "error code = -6" following the ./revone -P step, but since buying the phone from new I've never had it s-off. I've followed every step to a T with absolutely no luck... not sure if there's any binary/kernal stuff that's stopping me getting s-off access...I don't know enough about all that yet.
Anyway if anyone has any advice or has found a way round this issue it'd be awesome to hear from you.
Cheers
Click to expand...
Click to collapse
If the phone is new, there is no s-off exploit for it. Previous exploits have been patched. There might be hope if you have a US phone as there is a way to revert to earlier firmware provided you're still on hboot 1.44.
Grand rthrues
iElvis said:
If the phone is new, there is no s-off exploit for it. Previous exploits have been patched. There might be hope if you have a US phone as there is a way to revert to earlier firmware provided you're still on hboot 1.44.
Click to expand...
Click to collapse
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
reach777 said:
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
Click to expand...
Click to collapse
Yes it does, and if you took that update, even with hboot 1.44, the exploit has been patched and you have to wait until the revone team finds a new method.
skylineGTR_34 said:
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
Click to expand...
Click to collapse
1. Check that you have hboot 1.44
2. You can try 'Android Terminal Emulator' from PlayStore. and run the same commands there. you need to have the file on the root of your device.
reach777 said:
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
Click to expand...
Click to collapse
There may still be a way if your phone is on stock AT&T. I have not tried this but this might work for you.
http://forum.xda-developers.com/showthread.php?t=2398717
engage fica1di
dgtiii said:
Yes it does, and if you took that update, even with hboot 1.44, the exploit has been patched and you have to wait until the revone team finds a new method.
Click to expand...
Click to collapse
Thanks for the clarification.
iElvis said:
There may still be a way if your phone is on stock AT&T. I have not tried this but this might work for you.
http://forum.xda-developers.com/showthread.php?t=2398717
Click to expand...
Click to collapse
Thanks for the info but that sounds scary to do. I'm still a noob at this i think i'll wait for the rev team to find a workaround.
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
I have an at&t HTC One that I am trying to falsh the Google Play Edition RUU to. I have the bootloader unlocked via the HTC DEV website. I have TWRP Recovery installed. I am seeing **Tampered** when it boot into fastboot, and my phone is still showing that it is S-ON.
I have tried Revone and moonshine to make the device S-OFF but neither worked. I am thinking once I obtain S-OFF the **Tampered** will go away.
Is their another way to obtain S-OFF for this device, outside of Moonshine and Revone??
will54880 said:
I have an at&t HTC One that I am trying to falsh the Google Play Edition RUU to. I have the bootloader unlocked via the HTC DEV website. I have TWRP Recovery installed. I am seeing **Tampered** when it boot into fastboot, and my phone is still showing that it is S-ON.
I have tried Revone and moonshine to make the device S-OFF but neither worked. I am thinking once I obtain S-OFF the **Tampered** will go away.
Is their another way to obtain S-OFF for this device, outside of Moonshine and Revone??
Click to expand...
Click to collapse
What's your hboot version and date? If you're on 1.44 May 2013 or prior it should work, if you're on 1.44 June (ATT or T-Mob) there's a way to downgrade, and if you're on 1.54 then, sorry, but it won't work.
Check this guide: http://forum.xda-developers.com/showthread.php?t=2431515
nkk71 said:
What's your hboot version and date? If you're on 1.44 May 2013 or prior it should work, if you're on 1.44 June (ATT or T-Mob) there's a way to downgrade, and if you're on 1.54 then, sorry, but it won't work.
Check this guide: http://forum.xda-developers.com/showthread.php?t=2431515
Click to expand...
Click to collapse
I have 1.44 dated July 5 2013
I tried flashing through TWRP one of the stock recoveries but received FAILED
will54880 said:
I have 1.44 dated July 5 2013
Click to expand...
Click to collapse
That looks like the patched 1.44, if you're ATT or T-Mobile, there are ways to downgrade. I haven't used them, but many reported success: check the guide I posted above for the links to downgrade.
will54880 said:
I tried flashing through TWRP one of the stock recoveries but received FAILED
Click to expand...
Click to collapse
You can't flash recovery through TWRP, you must use fastboot.
nkk71 said:
That looks like the patched 1.44, if you're ATT or T-Mobile, there are ways to downgrade. I haven't used them, but many reported success: check the guide I posted above for the links to downgrade.
You can't flash recovery through TWRP, you must use fastboot.
Click to expand...
Click to collapse
I found an ATT RUU to use to get back to stock
I re-locked my bootloader, so now I show ***RELOCKED***
HBOOT version is 1.44.0000 dated May 3, 2013
What should be the next steps? This is my guess:
Unlock bootloader
Root device
S-Off using either moonshine or revone
will54880 said:
What should be the next steps? This is my guess:
Unlock bootloader
Root device
S-Off using either moonshine or revone
Click to expand...
Click to collapse
Just use revone to unlock and S-Off, it has a temproot exploit.
If that doesn't work, you can try your method.
will54880 said:
I found an ATT RUU to use to get back to stock
I re-locked my bootloader, so now I show ***RELOCKED***
HBOOT version is 1.44.0000 dated May 3, 2013
What should be the next steps? This is my guess:
Unlock bootloader
Root device
S-Off using either moonshine or revone
Click to expand...
Click to collapse
You can try without unlocking and rooting, it sometimes improves chances but you might as well try without first, could just work "straight of of the box" :fingers-crossed:
check these guides:
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2431515
and obviously the OP from http://forum.xda-developers.com/showthread.php?t=2314582
in case it doesn't work without unlocking & rooting, then yes, go ahead unlock via HTCdev again, flash a rooted Sense 5 Android 4.1.2 ROM, and try revone again until it succeeds. with hboot 1.44 May 2013 it should work
Good luck
BenPope said:
Just use revone to unlock and S-Off, it has a temproot exploit.
If that doesn't work, you can try your method.
Click to expand...
Click to collapse
I got the failed to map memory error when just using revone
I have a HTC One with unlocked bootloader and root and i'm trying to get s-off using revone. I'm on hboot 1.44 but when after i type ./revone -P it says
Segmentation fault (core dumped)
Click to expand...
Click to collapse
I have tried it a couple of times but the result is the same. Can anyone help me out and tell me what i'm doing wrong?
It'll only work if your hboot is dated May not June. Also, you need an older stock ROM, like, maybe 2.24 or older. Can't remember exactly.
Trying to do S-off using Revone and I keep getting segmentation fault <core dumped> when I set revone - P.
The phone is hboot 1.44 and firmware 4.1.2 with software number 1.27.531.11. Its not rooted.
Do I have to root to get this to work or what could be causing the fault? I ran it 6 or so times. Maybe I should try going to 1.27.531.8?
Thanks.
If your hboot is dated after May, yes, try the older ROM. I think the temproot hack broke around that time.
BenPope said:
If your hboot is dated after May, yes, try the older ROM. I think the temproot hack broke around that time.
Click to expand...
Click to collapse
I will see if I can find the older ROM. Would the temproot issue also be addressed by rooting first? I was trying to avoid that.
Or is better to upgrade to 1.54 and use rumrunner?
djayn said:
I will see if I can find the older ROM. Would the temproot issue also be addressed by rooting first? I was trying to avoid that.
Or is better to upgrade to 1.54 and use rumrunner?
Click to expand...
Click to collapse
1- you have a patched hboot, you can downgrade and use revone, using this: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318/
2- or you can use rumrunner, it also works on 1.44 as far as i know/seen
nkk71 said:
1- you have a patched hboot, you can downgrade and use revone, using the s-offdowngrade-12753111-to-1275318.
2- or you can use rumrunner, it also works on 1.44 as far as i know/seen
Click to expand...
Click to collapse
Sounds good. I will probably try the downgrade. Or is there a good reason to just root and go to rumrunner?
djayn said:
Sounds good. I will probably try the downgrade. Or is there a good reason to just root and go to rumrunner?
Click to expand...
Click to collapse
i guess it's two sides of the same coin.
the downgrade method (then revone) has been working fine from what i've seen on the forum.
djayn said:
Trying to do S-off using Revone and I keep getting segmentation fault <core dumped> when I set revone - P.
The phone is hboot 1.44 and firmware 4.1.2 with software number 1.27.531.11. Its not rooted.
Do I have to root to get this to work or what could be causing the fault? I ran it 6 or so times. Maybe I should try going to 1.27.531.8?
Thanks.
Click to expand...
Click to collapse
i always had issues with temproot on revone. I s-offed 3 phones and all 3 times i rooted phone first and then revone - always worked in that order (dont worget to su in adb shell)
Now that rumrunner exists I wonder if its best to just let HTC/Tmobile update the phone to 4.3 and then use rumrunner to S-off?
Probably not.
(question) Prep for S-off gives segmentation fault
Hello, First post..
Well I'm having the same error as quite a few have had; I hit ./revone -P and ends up shortly at the segmentation fault without an error and defaults back to the dir in adb shell.
I have:
hboot 1.44
1.26.502.15 - firmware
4.1.2
hboot date: July 5. 2013
This like old firmware since I see many newer firmware having this issue. My m7 is an AT&T variation, does this make a diff to revone?
Any ideas what I need to do? I've read other solutions but those use a new firmware than I have, so do I need to update the firmware to make this work? Hummm
Thanks for any help, much appreciated..