I have s-off. I relocked my boot loader to flash T-Mobile's latest 4.4.4 ota manually.
My unlock code bin will not work.
It's says "remote: unlock token check failed".
Now I'm stuck with locked boot loader and no root.
But I'm still s-off.
Any ideas?
you need a new unlocktoken. do the htcdev.com/bootloader unlock procedure again and when it's done, leave it open. it doesn't matter if your device is un-/locked in terms of OTA updates. especially not, when s-off.
seadersn said:
you need a new unlocktoken. do the htcdev.com/bootloader unlock procedure again and when it's done, leave it open. it doesn't matter if your device is un-/locked in terms of OTA updates. especially not, when s-off.
Click to expand...
Click to collapse
Well ****. This is why you don't do things late at night. Thanks for bump starting my brain.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Related
While there are plenty of guides describing how to root and flash recovery + a custom rom none of them seem to state how to without htcdev since we're now locked out of it. I would prefer root but mostly just want a rom other than stock. Did some searching and couldn't find anything I could be sure was current. Any help would mean a lot, thank you.
vpxf said:
While there are plenty of guides describing how to root and flash recovery + a custom rom none of them seem to state how to without htcdev since we're now locked out of it. I would prefer root but mostly just want a rom other than stock. Did some searching and couldn't find anything I could be sure was current. Any help would mean a lot, thank you.
Click to expand...
Click to collapse
You can't install another ROM until you do have root access. Search in the various Verizon HTC One Subforums for "rumrunner".
jpradley said:
You can't install another ROM until you do have root access. Search in the various Verizon HTC One Subforums for "rumrunner".
Click to expand...
Click to collapse
Oh, I saw that but I thought that was for something else. So that is the safest method for root these days? Weird needing root to flash a ROM when usually you just need a recovery..
vpxf said:
Oh, I saw that but I thought that was for something else. So that is the safest method for root these days? Weird needing root to flash a ROM when usually you just need a recovery..
Click to expand...
Click to collapse
Rumrunner if you are on the pre-4.3 software. Otherwise you will have to wait for rumrunner to be updated. Rumrunner does both s-off and root in one shot.
Sent from my Nexus 7 using Tapatalk 4
It's not about root. To flash custom roms you need an unlocked boot loader. Since HTCDev is not an option for the Verizon HTC One, you need to use Rumrunner. Rumrunner gives you S-off and unlocks your bootloader. Once your bootloader is unlocked, you can flash a custom recovery and you are set to start flashing custom roms, rooted or not rooted.
Sent from my Nexus 7 using xda app-developers app
xenakis said:
It's not about root. To flash custom roms you need an unlocked boot loader. Since HTCDev is not an option for the Verizon HTC One, you need to use Rumrunner. Rumrunner gives you S-off and unlocks your bootloader. Once your bootloader is unlocked, you can flash a custom recovery and you are set to start flashing custom roms, rooted or not rooted.
Click to expand...
Click to collapse
Not quite. Rumrunner just does the S-OFF & Root portion. I remember quite distinctly thinking Rumrunner would do everything, but after Rumrunner I still couldn't fastboot flash a custom recovery.
I had to change my CID to the SuperCID, then grab an unlock token from HTCDev so I could unlock the bootloader before I could use fastboot to push in a custom recovery. Pretty tedious, but not difficult and now I'm fully unlocked everywhere.
The important thing to remember is that we sort of operate backwards from most HTC devices. Most people just get to do an HTCDev unlock and then an S-OFF exploit afterwards is optional. S-OFF lifts the restriction on super-important places like the radio on bootloader. A bootloader unlock will let you mess with /system, recovery, and sometimes the kernel.
I used rumrunner and did not have to use HTCDev unlock token or change CID in order to unlock bootloader to fastboot flash custom recovery. Rumrunner unlocks the bootloader for you, so no need for HTCDev. Did your rumrunner process complete successfully without any hitches?
Sent from my HTC6500LVW using xda app-developers app
I have used Rumrunner on 5 different VZW HTC One phones. Once complete, you just need to flash the recovery of your choice. Nothing else is needed.
Rumrunner is an amazing tool but can be kind of finicky to finally get S-off. Just make sure you follow the directions EXACTLY and if you have Windows 8.1, good luck. I suggest using a Windows 7 machine or Ubuntu using Live USB if you don't have a native Ubuntu machine. VMware is NOT supported for Rumrunner.
Well, no matter I'm on JellyBean 4.3 and it would seem, as mentioned, that I'm out of luck for now. The information may come in handy later, or may change even.
Just becoming quite annoyed with Google Now always popping up because I slid my finger wrong Also, can't help but wonder how much longer my battery would potentially work with full root access to remove some of the background data bloat.
Okay so I used firewater exploit to get unlocked boot loader and s-off I'm on google play edition ROM can I put s-on and leave boot loader unlocked without issues????
Sent from my HTC One using XDA Free mobile app
gonzalezb said:
Okay so I used firewater exploit to get unlocked boot loader and s-off I'm on google play edition ROM can I put s-on and leave boot loader unlocked without issues????
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
if you do s-on you will need to flash boot.img with fastboot and not with recovery.
I get that but will it work or will something go wrong if I do it on Verizon variant since it was unlocked via exploit. And I'm not on original firmware I've since upgraded that to latest.
Sent from my HTC One using XDA Free mobile app
synisterwolf said:
if you do s-on you will need to flash boot.img with fastboot and not with recovery.
Click to expand...
Click to collapse
Stupid xda app didn't reply when i posted this.
I get that but will it work or will something go wrong if I do it on Verizon variant since it was unlocked via exploit. And I'm not on original firmware I've since upgraded that to latest.
gonzalezb said:
Stupid xda app didn't reply when i posted this.
I get that but will it work or will something go wrong if I do it on Verizon variant since it was unlocked via exploit. And I'm not on original firmware I've since upgraded that to latest.
Click to expand...
Click to collapse
Unless you need service on the phone, it would be best to stay S-0ff and unlocked.
If you S-0n, you're very restricted on what you can do.
You'll miss out on newer issues of custom roms, if nothing else.
Be verrry sure you have a stock hBoot in it
before you S-0n if you're going to do that.
gonzalezb said:
Stupid xda app didn't reply when i posted this.
I get that but will it work or will something go wrong if I do it on Verizon variant since it was unlocked via exploit. And I'm not on original firmware I've since upgraded that to latest.
Click to expand...
Click to collapse
nope, unlock is unlock no matter how we got it. if the bootloader says UNLOCKED on the top it good to go. you can turn the phone back to s-on if you like and flash everything rom related inside recovery. you would need to extract the boot.img and flash with fastboot. with s-on you wont be able to update firmwares, radios, splash screens, ect. even if it is an update to what you have because with s-on it looks for HTC signature, if it returns as null it wont apply.
with s-on, you cant ruu unless its an incremental updated ie. if you are version B but want to go to A you cant. Also if version B is acting up and want to ruu, you cant just ruu to version B you would need to wait for version C.
there really isnt a need to S-on unless you want to return it back to VZW. As long as you are careful on what you flash you shouldn't need to worry about bricks. Just check MD5 sums when flashing roms or kernels and you will be good to go.
EDIT:
i would also like to add, the new sunshine S-off app was updated to 2.0 to gain s-off on the newest firmware. if you do decide to go back to s-on but keep unlocked bootloader you can. but you will have to pay $25 for the s-off license key within the sunshine app.
IMO, unless you are sending your phone in for warranty service, there is no reason to ever put it back to s-on. You are just limiting your options as to what you can do with it.
Edit - this phone is very hard to actually brick also.........most problems I have seen have been people putting themselves back to s-on, THEN ****ing something up, and not being able to RUU because they went back. heh
I have an AT&T M8 with 4.4.3
Its unlocked and rooted, firewater was unsuccessful with this error....****** device patched by HTC, you are out of luck *********.
Is there any way to return to stock without S-Off?? If so could someone please point me in the right direction?
I'm a newbie with htc and very aggravated with this phone.
skullymullins said:
I have an AT&T M8 with 4.4.3
Its unlocked and rooted, firewater was unsuccessful with this error....****** device patched by HTC, you are out of luck *********.
Is there any way to return to stock without S-Off?? If so could someone please point me in the right direction?
I'm a newbie with htc and very aggravated with this phone.
Click to expand...
Click to collapse
Can you provide me with the link that says you need to be S-OFF to get your phone back to stock, where you clearly didn't have to be S-OFF in order to take it away from stock in the first place?
I'm asking this because you are one of many that I've seen recently that comes on here asking the same question, can I go back to stock while I'm still S-ON ? "Should I be S-OFF in order to restore a nandroid backup?" etc...I would really like to know where you guys get this information from?
The only thing that you'll need S-OFF for(when going back to stock) is to fix the tampered flag in the bootloader and to have it show "locked" instead of "relocked" when or if you locked the bootloader.
That being said, going back to stock from where? Did you flash custom ROMs? Or are you only rooted and unlocked?
My phone is stock, but unlocked with root, my main goal is to reload the original recovery, relock and unroot.
I was watching a video on how to use RUU and according to the instructions you had to be S-Off.
Anyone
Sent from my HTC One_M8 using XDA Free mobile app
skullymullins said:
My phone is stock, but unlocked with root, my main goal is to reload the original recovery, relock and unroot.
I was watching a video on how to use RUU and according to the instructions you had to be S-Off.
Click to expand...
Click to collapse
You need S-Off only when you want to remove TAMPERED and RELOCKED flags.
Other than that, you don't need S-OFF
You have AT&T device, AT&T forum is where you'll find more info.
Try this one : http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
Important note :
S-On - you need to relock bootloader first before running it. So read and read the instructions
and there are many more guides on AT&T forum
skullymullins said:
Anyone
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You could use the AT&T RUU that is available on the AT&T forum.
At&t 2.23.502.3 - 4.4.3 Bootable RUU - No PC required - Mac friendly
Like the OP there said, if you are S-ON you should lock the bootloader first before using the RUU. I think that should take care of most of the other issues you have, like unrooting etc. Make a backup of any personal stuff you have on phone.
Or
Download unsupersu, flash it in custom recovery to unroot device. If you use SuperSU you can also go into settings for SuperSU and use Full Unroot. Reboot phone, can then uninstall SuperSU. Should be unrooted.
Flash back stock recovery for your device.
Relock bootloader - fastboot oem lock
Will this also restore the factory recovery instead of twrp that is on the phone now?
skullymullins said:
Will this also restore the factory recovery instead of twrp that is on the phone now?
Click to expand...
Click to collapse
That's also in that very same thread we linked you to!
Post number 7
Post number 15
But I take it you didn't read at least the first 2 pages...
It'll take you back to stock completely, like the OP said in Post 15.
Just remember to relock your bootloader seeing as you're S-ON.
Thanks for your patience and help,
it worked flawlessly.
I have an A5chl model 816 flashed with a nightly CM12
build. Its also rooted.
What I'd like to do is unroot, restore the stock recovery,
relock the bootloader and keep CM12 for the up to date security
patches.
I tried relocking the bootloader once and was locked into
only being able to boot into the bootloader (Was thankful to
find out relocking a previously unlocked loader doesn't
initiate any wipes!).
Is there any way to do this? Security-wise it seems the
best possible setup outside of someone owning a
Nexus device which has the latest fixes stock.
I read of a hack for HTC M8 devices which allow
relocking and unlocking the bootloader and reseting
the tampered flags, etc via adb shell commands.
I still have S-On, but something like this for the 816 would
be very welcome.
With all the Android security loopholes, going back to Stock seems
somehow less secure to me, even with a locked
bootloader.
Anyone?
reSpock said:
I have an A5chl model 816 flashed with a nightly CM12
build. Its also rooted.
What I'd like to do is unroot, restore the stock recovery,
relock the bootloader and keep CM12 for the up to date security
patches.
I tried relocking the bootloader once and was locked into
only being able to boot into the bootloader (Was thankful to
find out relocking a previously unlocked loader doesn't
initiate any wipes!).
Is there any way to do this? Security-wise it seems the
best possible setup outside of someone owning a
Nexus device which has the latest fixes stock.
I read of a hack for HTC M8 devices which allow
relocking and unlocking the bootloader and reseting
the tampered flags, etc via adb shell commands.
I still have S-On, but something like this for the 816 would
be very welcome.
With all the Android security loopholes, going back to Stock seems
somehow less secure to me, even with a locked
bootloader.
Anyone?
Click to expand...
Click to collapse
If you're gonna still use cm12, then there is no point flashing stock recovery, as it is useless without stock software. Also, in order to lock and unlock like you say, you must pay 25$ to get the s-off. Although, I think your fine without relocking the bootlader. Good luck!
Sent from my 710C using Tapatalk
the_Victorian said:
If you're gonna still use cm12, then there is no point flashing stock recovery, as it is useless without stock software. Also, in order to lock and unlock like you say, you must pay 25$ to get the s-off. Although, I think your fine without relocking the bootlader. Good luck!
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
So there's no other way to get S-Off except using Sunshine or trying to
adapt the M8 adb hack to the 816?
I'm not interested in using recovery for backup and
restoration purposes really. It's about being more
secure. Everywhere I've read says CWM is pretty
insecure and having an unlocked bootloader even
more so.
Why do you think it's fine having an unlocked bootloader?
BTW, if I were to flash stock recovery and relock the bootloader
would it be possible for me to preserve root or somehow reroot
via one of the rooting softwares without unlocking again?
I have this same phone and the only root method I've found to work is flashing a custom recovery and then flashing the superSU zip that you would have previously installed in the root of your SD card from that custom recoveries file Explorer. As for custom recovery over stock and one being more secure than the next, you went way past secure the minute you set up your developer account with HTC, like I did, to unlock your bootloader in the first place and gain root access . Yes it's more secure to keep your bootloader locked and relocking it after reflashing your stock recovery seems to be what your want to do and you can do it. I wouldn't on mine but it sounds like your not comfortable with yours so go for it. I sincerely hope you don't end up regretting it later. Good luck!
Sent from my 710C using XDA Free mobile app
---------- Post added at 08:23 PM ---------- Previous post was at 08:13 PM ----------
Also the Sunshine app worked great for me and the money's not bad for what they do for the phone and the access it gives you.
Sent from my 710C using XDA Free mobile app
So i have the tmobile htc 10 and i had it unlocked and S-on but rooted. then i decided to s-off to change cid and install the unlocked versions firmwares. but when i used the sunshine app to get s-off it gave me the option to get s-off and Locked. so i did that one since it was recommended. and now i can flash twrp but every time i flash supersu no app shows up and keeps saying my device is not rooted. I have tried reflashing the rom through ruu and zip files and nothing. will i have to re-unlock my bootloader even though im already s-off to get root?
Think you might need to download the super SU app from the play store too.
Sent from my HTC 10 using XDA Labs
ErickF said:
So i have the tmobile htc 10 and i had it unlocked and S-on but rooted. then i decided to s-off to change cid and install the unlocked versions firmwares. but when i used the sunshine app to get s-off it gave me the option to get s-off and Locked. so i did that one since it was recommended. and now i can flash twrp but every time i flash supersu no app shows up and keeps saying my device is not rooted. I have tried reflashing the rom through ruu and zip files and nothing. will i have to re-unlock my bootloader even though im already s-off to get root?
Click to expand...
Click to collapse
I selected the other option (unlocked S-off) and I had to re-flash supersu. After that, it's worked fine. I don't think sunshine does anything to re-lock the bootloader, but I could be wrong.
charlatan01 said:
I selected the other option (unlocked S-off) and I had to re-flash supersu. After that, it's worked fine. I don't think sunshine does anything to re-lock the bootloader, but I could be wrong.
Click to expand...
Click to collapse
Fixed it. Since i chose the option to s-off but locked in the sunshine app it wouldnt let me reflash the supersu. I had to unlock the bootloader again and it now works perfectly