Related
So I guess I just don't know what I'm doing anymore, and I need some help getting S-OFF on my One. I installed a 4.3 ROM and wanted to upgrade my firmware to 3.06.1700.10. To do this though, I saw I needed to have S-OFF.
I attempted S-OFF with both methods posted in the sticky. The revone method gave me "error code = 1", and the moonshine method fails to connect to ADB.
So I figured maybe I needed to revert to a compatible ROM to be able to get S-OFF. So I tried running the appropriate AT&T RUU utility, and it tells me the update failed and freezes on the HTC logo.
So both S-OFF methods failed, and the RUU failed. What do I need to do in order to get S-OFF so I can upgrade my firmware?
Forget it.
Mike
I posted in the Verizon forums a day ago, but have received little to no help. Now I hope that someone can help me here.
Original post http://forum.xda-developers.com/showthread.php?t=2599610
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.
I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
sweetnsour said:
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
Click to expand...
Click to collapse
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
geeibara said:
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
Click to expand...
Click to collapse
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
sweetnsour said:
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
Click to expand...
Click to collapse
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
geeibara said:
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
Click to expand...
Click to collapse
to be able to reflash twrp you need to unlock your bootloader that is why you are getting signature fail error
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
pc010121 said:
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
Click to expand...
Click to collapse
you can use this then take the OTA updates
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
pc010121 said:
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
Click to expand...
Click to collapse
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Edit: I am relocked as I am S-ON. I can't update firmware as the signature check fails. Flashing the 3.04.651.2 zip has a signature verify fail, as well.
Hope this helps
cheesesoda said:
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Click to expand...
Click to collapse
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
pc010121 said:
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
Click to expand...
Click to collapse
Actually, it seems that the phone is wiped; I can't boot my recovery. As a result, I can't really get S-OFF. I'll try the 4.06 RUU, but would it make a difference that it's .4 and not .9?
EDIT: I'm talking out of my ass right now. Long day, and this isn't helping. I am figuring it out; unlocked the bootloader, and now things seem to be functional. Well, except CM doesn't seem to want to boot any longer, but that shouldn't matter for long.
EDIT 2: How can I get S-OFF without enabling debugging? As of right now, CM is just in a boot loop.
Sim Unlock Sprint HTC One Max
I almost cannot believe how many different ROMs I've tried to flash after wiping out my original ROM.
Bootloader unlocked and rooted I managaged to relock the bootloader while trying to fastboot flash a stock ROM, which also failed.
Beleive it or not, I've have found a couple that will boot up with my Sprint HTC One Max . I was able to re-unlock the bootloader, flash a new rom and even recover user data I had backed up to my PC via adb backup.
All this for not, as I still cannot find a Sense ROM that will flash on my device and allow me to unnlock the Sim via Sim Unlock Helper.
Any help would be greatly appreciated!!!
TAMPERED
UNLOCKED
Sprint HTC One T6WL S-OFF
CID-SPCS_001
HBOOT-2.49.000
RADIO-1.48.50.0425
I recall reading somewhere that the Unlock Sim Helper should work on Sense 4.1.2 ROM. ????
Hi,
I'm totally Helpless.... Im trying do perform sim unlock on my sprint HTC One for four days... My phone is rooted, custom recovery (TWRP), S-Off, Hboot is downgraded from 1.57 to 1.55, my bootloader is relocked, but i cant perform downgrade to 4.3 or 4.1... can anyone help me?
If I try to flash RUU, it says Error 155 and if I try to flash it via CMD it shows me FAILED (remote: 32 header error)...
I'm totally HOPELESS now
Try THIS
Thanks for reply,
I already tried (i think) All of guides here on XDA or other sites... link u provide shows me error" FAILED (remote: 32 header error)" while "pushing" rom into device...
SkopiX said:
Thanks for reply,
I already tried (i think) All of guides here on XDA or other sites... link u provide shows me error" FAILED (remote: 32 header error)" while "pushing" rom into device...
Click to expand...
Click to collapse
Did you re-lock your bootloader?
Did you use the correct RUU zip (decrypted)
Yea, my bootloader is RELOCKED and I think Yes, im using correct RUU
*** TAMPERED***
***RELOCKED***
s-OFF
CID- 11111111
HBOOT- 1.55
Radio- 1.00.20.0626 (i think i tried flash radio [some guide told me])
this is what I can see when i go to bootloader
//edit 2: finally succes i downloaded another RUU from htc1guru and finally it worked
//edit 3: now all works
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Cazrelleum said:
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Click to expand...
Click to collapse
nope your pretty much done, you could have run over it with a truck ..same effect
http://forum.xda-developers.com/showthread.php?t=2664757
Cazrelleum said:
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Click to expand...
Click to collapse
GPE bootloader 1.54+ can not be unlocked (the well known GPE bootloader bug)
You did the final blow when turning it back S-ON.
Now that you can't boot it, you can't achieve s-off anymore and the only work around for the GPE bootloader unlock bug require S-OFF.
So you are stuck with a non-bootable, non s-off'able, non-unlockable phone, well, a brick with written proof that you have caused it yourself (tampered flag in the bootloader)
Sorry :crying:
Now time to send your phone for repair or to buy another one.
Try this
http://forum.xda-developers.com/showthread.php?t=2363516
Thread closed and cleaned up at OP's request.