I get the following error when trying to s-off with rumrunner
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
but adb can see a device, run commands and linux does not require dirvers.
Debugging is on.
Battery Power saver, sleep mode and Fastboot is off.
adb works when booted and fastboot works in the boot loader.
adb logcat will Alarm manager will show a Partial wake lock form time to time. Not sure if the partial wake lock is normal or not.
Reboot ur phone to see if it helps
Child's Play said:
Reboot ur phone to see if it helps
Click to expand...
Click to collapse
Thanks for the reply
I rebooted several times, used different cables, usb ports, directories and set PATH too.
Ever since I ran the HTCdev unlock binary I have been getting a strange error on reboot.
HTML:
Unfortunately, Virgin - Apps We love has stopped.
<OK>
Should I do a factory reset re run HtcDev unlock or???
conductive said:
Ever since I ran the HTCdev unlock binary I have been getting a strange error on reboot.
HTML:
Unfortunately, Virgin - Apps We love has stopped.
<OK>
Should I do a factory reset re run HtcDev unlock or???
Click to expand...
Click to collapse
So you did the HtcDev unlock, dumb question, but did you get root before trying to run rumrunner?
(ADB can see the device, but perhaps since it doesn't have access to root, it's not allowing the exploit to run is what my logic is)
jwlawhorn said:
So you did the HtcDev unlock, dumb question, but did you get root before trying to run rumrunner?
(ADB can see the device, but perhaps since it doesn't have access to root, it's not allowing the exploit to run is what my logic is)
Click to expand...
Click to collapse
I jumped through HTC hoops for the unlock. I tried to flash twrp-2.8 and did not get root. I was told by another user that root is another process so you need to run rumrunner.
I currently have
*** TAMPERED ***
*** UNLOCKED ***
zara_cl PVT SHIP S-ON RL
HBOOT-2.22.00
157
conductive said:
I jumped through HTC hoops for the unlock. I tried to flash twrp-2.8 and did not get root. I was told by another user that root is another process so you need to run rumrunner.
I currently have
*** TAMPERED ***
*** UNLOCKED ***
zara_cl PVT SHIP S-ON RL
HBOOT-2.22.00
Click to expand...
Click to collapse
Yes, root is another process then achieving S-Off, but if you don't already have root, you're going to have trouble getting S-off with rumrunner.
If your setup couldn't get a custom recovery to flash (Assume you used http://forum.xda-developers.com/desire-601/orig-development/recovery-twrp-2-8-0-0-touch-recovery-t2874948 specifically modified for kitkat) , you're probably not going to achieve S-off with this method.
HTML:
It is starting to become obvious that htcdev hosed me
conductive said:
HTML:
It is starting to become obvious that htcdev hosed me
Click to expand...
Click to collapse
Should I relock and unlock or will a factory reset do the trick. My phone never had errors before all the htcdev BS
jwlawhorn said:
Yes, root is another process then achieving S-Off, but if you don't already have root, you're going to have trouble getting S-off with rumrunner.
If your setup couldn't get a custom recovery to flash (Assume you used http://forum.xda-developers.com/desire-601/orig-development/recovery-twrp-2-8-0-0-touch-recovery-t2874948 specifically modified for kitkat) , you're probably not going to achieve S-off with this method.
Click to expand...
Click to collapse
rumrunner instructions say "ur device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
Related
These steps will get you completely back to stock.
I want to first say thanks to the unlimited.io team for making S-OFF possible.
Secondly, by following these instructions you are acknowledging that should something go wrong and you brick your device, I am not at fault nor are the developers of the S-OFF method for the HTC RUBY. Follow these instructions at your own risk! I am NOT a dev, just stupid enough to be the first one (I think) To try this. I am not going to give instructions on how to use fastboot, if you are S-Off, then you should already know.
Third, you WILL be able to re-unlock your bootloader and regain S-OFF after you have followed these instructions. If you want to do so, there are other threads on how to do that.
And 4th, I have only tried this on a tmobile branded device. I have no idea if this works on any other device. I think it should, but I don't know for sure. If anybody wants to give it a try and let me know, then i will update the OP.
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
That's it!
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
kaabob said:
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
Click to expand...
Click to collapse
I should have clarified, the steps are if you want to go completely stock, will update the OP.
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
bjcolema said:
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
That's good to know. Thanks.
Sent from my HTC_Amaze_4G using XDA
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
Thanks for replying.
This is correct, my phone said locked, not relocked.
I would like to stress that YOU NEED A FULL RUU, not a stock nandroid backup. Otherwise, you are going to need that link on my sig
Sent from my HTC Sensation using XDA
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
electronicrice said:
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
Click to expand...
Click to collapse
If you are S-Off, then following this guide will put you back to stock gingerbread.
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
I dont know a way for going back to stock without being s=off. You could possibly flash the newest official release (ics, one that hasnt been modified) then relock your bootloader, but i think that it will show relocked rather than locked. Worth a try though.
Okay thanks for the input guys. It isn't a huge deal, I just didn't think there was enough "goodies" rom-wise for ICS, but there are some hardworking devs on here. Looking forward to the Sense 4.0 rom.
dcmtnbkr said:
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Click to expand...
Click to collapse
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
frodoboy said:
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
Click to expand...
Click to collapse
When s-on, you can't go back to s-off by writing the security flag again . You have to do again the juopunutbear procedure including the wire trick
Sent from my HTC Sensation Z710e
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
3oudreaux said:
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
Click to expand...
Click to collapse
This one would be best: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
I spent 3 hrs trying to solve the relocked and locked issue until finally I got it resolved. with the manual option to lock with hasoon tool, places *** RELOCKED *** in hboot, which clearly and obvious for any technician to see you tampered with the hboot files from stock. my reason for doing this to get my warranty back.
how did i fixed "RELOCKED" to show as *** LOCKED *** ? after the hasoon tool 3.2 relocked the bootloader i was challenged, but decided the first step would be switching the security off and on (s-off/ s-on)
first return to stock RUU through boot loader, then adb command fastboot oem writesecureflag 3 to enable s-on. *toggled it on
i reinstalled juopunutbear s-off again carefully following the instructions. with a paperclip grounding the phone and selecting for juopunutbear's modified files "y" enter.
then your *** RELOCKED *** shows as *** juopunutbear *** in hboot. (at first i thought I dig myself a bigger hole)
I used Hasoon tool 3.2 again to RELOCK bootloader, with the intention of reinstall the stock RUU again. however it still showed as *** juopunutbear *** with the message its already locked.
Now I installed the the Stock RUU again from bootloader. once complete back to the hboot, to show *** LOCKED *** and s-off Progress!!!
repeat enable s-on instructions by writing adb: fastboot oem writesecureflag 3,
now shows
*** LOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-02.6.0.2226.00.0202
eMMC-boot
a step closer for the warranty being back to the device, without a dispute with the warehouse/ carrier
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
aoakes said:
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
Click to expand...
Click to collapse
No need to get rid of that. New phone from T-Mobile with HBOOT 1.93 and it had that line it . It looks like 1.90 is the one that doesn't have that line. Because my wife's phone is on 1.90 and she doesn't have it.
I'm going to be following the method in a few days. Can you guys confirm this all works as it should?
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
K.AuthoR said:
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Click to expand...
Click to collapse
Have you tried to re s-off?
I believe the firewater and romrunner tools in the int. One forums should be able to s-off that hboot.
I haven't personally gone s-off, but my understanding is that once s-off you can change your sid (super sid maybe?) And run just about any ruu.
Search up on that stuff.
Sent from my HTC One using xda app-developers app
K.AuthoR said:
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Click to expand...
Click to collapse
you will have to s-off to repair the phone or hope for a new GPE RUU
whats the fastboot getvar all results (minus the serial no and IMEI )
I see a few mistakes. First, never go S-On and/or lock the bootloader once they've been unlocked. There's no reason for this unless returning to stock for warranty purposes. And if you do, ensure the phone has the software it's supposed to (AT&T in this case).
Secondly, if you have GPE, you must downgrade to hboot 1.44 first. And to do this, you must be S-Off.
Since the phone is currently S-On, the course of action depends on what is on the phone. If your CID is currently GOOGL001 or 11111111, try flashing the latest GPE RUU to restore the phone to working condition. Then go to HTCDev and unlock the bootloader. After that, you can use Firewater to S-Off.
Assuming all is successful, search for and flash hboot 1.44, then change the CID to CWS__001 (that's two underscores) and flash an AT&T RUU. And whatever you do, don't go S-On or lock the bootloader again. There's nothing to be gained by doing this.
If you're returning the phone to AT&T software because the person didn't like GPE (which I don't blame them), use the Dev Edition. By far the best choice to get the same Sense version of Android without all of the AT&T sh*tware. And things like AT&T Visual Voicemail work, along with any other AT&T app if the person wanted to download it from the Play Store for free.
Good luck.
I apologize in advance if there is already a thread on this subject. I checked but did not find anything.
I'm trying to switch my phone from s-off to s-on.
I'm following a guide from wonder how to (cannot post link)
When I type "adb push revone /data/local/tmp/" and click enter I get this message:
"adb is not recognized as an internal command"
My phone is an HTC One (M7 AT&T)
Have USB debugging on
Fastboot checked off
Windows 7 (64 bit)
Running 4.1.2
I had to factory wipe/reset my phone because it was fully encrypted. I'm just trying to unroot and relock my device.
Any help would be greatly appreciated. Thank you
Nace112 said:
I apologize in advance if there is already a thread on this subject. I checked but did not find anything.
I'm trying to switch my phone from s-off to s-on.
...
I had to factory wipe/reset my phone because it was fully encrypted. I'm just trying to unroot and relock my device.
Any help would be greatly appreciated. Thank you
Click to expand...
Click to collapse
You don't need to go s-on to unroot or relock bootloader. If you read any of the horror stories threads about bricked devices you'll find that many of them begin with the phrase I went back to s-on and then (insert story about brick...). It sounds like you're kind of a novice at this, which is ok, but do yourself a favor and leave the phone s-off.
Now if you're trying to return to stock, there's and excellent thread by @nkk71 on the subject here.
If you give us some details on what exactly you are trying to accomplish we can point you in the right direction.
cschmitt said:
You don't need to go s-on to unroot or relock bootloader. If you read any of the horror stories threads about bricked devices you'll find that many of them begin with the phrase I went back to s-on and then (insert story about brick...). It sounds like you're kind of a novice at this, which is ok, but do yourself a favor and leave the phone s-off.
Now if you're trying to return to stock, there's and excellent thread by @nkk71 on the subject here.
If you give us some details on what exactly you are trying to accomplish we can point you in the right direction.
Click to expand...
Click to collapse
I'm used to working with iOS devices so android is still a bit new to me. I don't even remember how I rooted and unlocked my phone. I just remember I had a lot of issues and a little luck.haha
Basically I'm trying to return the phone to stock. I looked up multiple guides and most of them said to first turn s-off to s-on (that's why I thought I had to do that.)
I looked at the guide and I don't know the steps of what to do from here.
My bootloader screen says:
TAMPERED
UNLOCKED
PVT SHIP S-ON
HBOOT- 1.44.000
it doesn't say my CID or MID.
Nace112 said:
Basically I'm trying to return the phone to stock. I looked up multiple guides and most of them said to first turn s-off to s-on (that's why I thought I had to do that.)
I looked at the guide and I don't know the steps of what to do from here.
My bootloader screen says:
TAMPERED
UNLOCKED
PVT SHIP S-ON
HBOOT- 1.44.000
it doesn't say my CID or MID.
Click to expand...
Click to collapse
Well your bootloader says that your already s-on, so the only way to remove the tampered and unlocked flags is to s-off, probably using revone since you have 1.44 hboot, and then using revone to lock and remove tampered. There's an entire thread on revone that outlines how to do that, just search for it.
cschmitt said:
Well your bootloader says that your already s-on, so the only way to remove the tampered and unlocked flags is to s-off, probably using revone since you have 1.44 hboot, and then using revone to lock and remove tampered. There's an entire thread on revone that outlines how to do that, just search for it.
Click to expand...
Click to collapse
I have it already but my command prompt keeps giving me this error:
adb is not recognized as an internal command or external command
Nace112 said:
I have it already but my command prompt keeps giving me this error:
adb is not recognized as an internal command or external command
Click to expand...
Click to collapse
Grab Android Terminal Emulator from the play store and run the command directly on your phone.
https://play.google.com/store/apps/details?id=jackpal.androidterm
Nace112 said:
I have it already but my command prompt keeps giving me this error:
adb is not recognized as an internal command or external command
Click to expand...
Click to collapse
Sorry to barge in, you're in excellent hands with @cschmitt already, just a few comments to save some trouble (in case you run into any):
you can get the mini-sdk for windows from here: http://www.androidfilehost.com/?fid=23329332407585867
and you need to be in the folder you extracted these files, to be able execute to adb/fastboot commands.
revone works great with this ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
Note, that bootloader date has to be before June 2013, otherwise it's a patched 1.44 version and revone will not work.
in which case you either have to use rumrunner and/or firewater, or even the old ATT downgrade method: http://forum.xda-developers.com/showthread.php?t=2394155
Hi,
Is it possible to remove the tampered flag without unlocking the bootloader through htcdev? The phone is S-ON again, but still has root. I ask, because somehow after locking bootloader and reverting to S-ON after downgrade to JB, the tampered flag appeared. I wouldn't like to go through the htcdev unlock process because it factory resets the phone and I got it all setup again.
Thanks.
Yes u can do it with s-off. http://forum.xda-developers.com/showthread.php?t=2808912
Child's Play said:
Yes u can do it with s-off. http://forum.xda-developers.com/showthread.php?t=2808912
Click to expand...
Click to collapse
So is there a way for me to gain S-OFF without actually unlocking the bootloader, now that I have root?
rocky7x said:
So is there a way for me to gain S-OFF without actually unlocking the bootloader, now that I have root?
Click to expand...
Click to collapse
Rumrunners website claims you only need htcdev unlock "or" root. Everyone seems to have different results though. Would be worth giving it a shot.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Yes but dont know if its possible to get s-off again. Try it
Child's Play said:
Yes but dont know if its possible to get s-off again. Try it
Click to expand...
Click to collapse
Hmmm I've just read on a HTC One related forum that tampered flag is set because of root. And since I don't want to scrap root, I think that even if I used rumrunner, got S-OFF, then did the revone stuff and locked it back to S-ON, the tampered would jump up again, because of root with stock bootloader. Not really sure if that is somehow related - does anyone have a stock Jellybean with everything stock (bootloader, recovery etc), bootloader locked and S-ON AND with root? Does it show tampered?
It has nothing to do with root. It appears when u unlock the bootloader.
Remove the tampered banner- http://forum.xda-developers.com/showpost.php?p=47576052&postcount=7&nocache=1&z=8527302977163345
Recovery, roms, hboots, etc- http://forum.xda-developers.com/des...x-roms-mods-recoveries-backups-tools-t2804427
Child's Play said:
It has nothing to do with root. It appears when u unlock the bootloader.
Remove the tampered banner- http://forum.xda-developers.com/showpost.php?p=47576052&postcount=7&nocache=1&z=8527302977163345
Recovery, roms, hboots, etc- http://forum.xda-developers.com/des...x-roms-mods-recoveries-backups-tools-t2804427
Click to expand...
Click to collapse
Hi, OK so I've tried it and unfortunately I couldn't get S-OFF. Rumrunner just crashed after message:
Code:
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
So I guess it's not possible to get S-OFF without unlocked bootloader (only with root).
U need to grant supersu permission. Try again
Hi all,
I have installed a custom recovery on my ATT HTC One M8. It is rooted and I am trying to install an OTA update. I am fairly new to this and I need help. I can try provide any information necessary. I am currently on 4.28.502.1 and the OTA update is 4.28.502.2. I keep getting ERROR 155 and I don't know what I am doing wrong. Thank you
Not for the M8.....it might help.
http://forum.xda-developers.com/showthread.php?t=1655832
I downloaded MyAndroidTools and actually shut down my HTC DM service. There are 2 of them. I went into HTCDM and unchecked DmService . I no longer see the update prompt.
I am waiting a few days to see how this pans out.... I really don't feel like unrooting and relocking.
Kelvala said:
Not for the M8.....it might help.
http://forum.xda-developers.com/showthread.php?t=1655832
I downloaded MyAndroidTools and actually shut down my HTC DM service. There are 2 of them. I went into HTCDM and unchecked DmService . I no longer see the update prompt.
I am waiting a few days to see how this pans out.... I really don't feel like unrooting and relocking.
Click to expand...
Click to collapse
I need to have S-OFF to relock my bootloader, but I can't find a program to help me achieve that. There was firewater and that has become discontinued. There is SunShine ( I think that is what its called ) which you have to pay $25 for. I don't know if it's worth it.
Error 155 is because of unlocked bootloader. Only way to have unlocked and run an ruu successful is with s-off. Just relock and ruu you can always unlock again via HTCdev. Type the command below to relock when s-on.
Fastboot oem lock
It will show relocked, so it won't help with warranty, but if you are planning to unlock again, it will work.
Uzephi said:
Error 155 is because of unlocked bootloader. Only way to have unlocked and run an ruu successful is with s-off. Just relock and ruu you can always unlock again via HTCdev. Type the command below to relock when s-on.
Fastboot oem lock
It will show relocked, so it won't help with warranty, but if you are planning to unlock again, it will work.
Click to expand...
Click to collapse
Are you sure I can relock my bootloader with S-ON? I've looked all around and it says I need to be S-OFF.
Give it a shot. If the ruu is the same version or higher, you can ruu easily with s-on
Uzephi said:
Give it a shot. If the ruu is the same version or higher, you can ruu easily with s-on
Click to expand...
Click to collapse
Do I just run that command in cmd? Or there is something else ?
xChaosLegion said:
Do I just run that command in cmd? Or there is something else ?
Click to expand...
Click to collapse
You just run it in cmd while the phone is in fastboot mode
Ok, so new to HTC and all this s-off/on stuff....If I have my bootloader unlocked now and am stock rooted, all I need to do is buy Sunshine, s-off and I can install the OTA update without losing my apps and homescreen setting etc...?
Kelvala said:
Ok, so new to HTC and all this s-off/on stuff....If I have my bootloader unlocked now and am stock rooted, all I need to do is buy Sunshine, s-off and I can install the OTA update without losing my apps and homescreen setting etc...?
Click to expand...
Click to collapse
/system has to be unmodified. This means most things that require root to change (E.G. removing system apps, changing build.prop, xposed, etc) have to be reverted to stock for an ota to work. You do not need s-off to take an ota. Just uproot, put /system back to stock and flash the stock recovery.
xChaosLegion said:
Are you sure I can relock my bootloader with S-ON? I've looked all around and it says I need to be S-OFF.
Click to expand...
Click to collapse
You need s-off to make it say LOCKED. With s-on, you can only make it RELOCKED.
The only reason to make it LOCKED is for warranty purposes through HTC (AT&T warranty actually doesn't care of the phone is modded).