Hi,
After going through a lot of threads created this one. I'm from India and my HTC ONE is of x.xx.707.x region.
I recently S-off'ed my One hboot 1.54 with rumrunner guide (http://forum.xda-developers.com/showthread.php?t=2488772)
Then i updated my firmware to fw_3.62.401.1_custom that i got from Vomer's guide (http://forum.xda-developers.com/showthread.php?t=2365506)
I also flashed custom recovery (TWRP).
I then flashed the stock 3.62.401.1.zip rom that i got from ARHD thread.
My main concerns are
1. Can i downgrade the hboot anytime ?
2. Can i get back to 100% stock? With S-on ? if so any help regarding this is greatly appreciated.
3. I'm now new to S-Off thing, and is there anything that i should take care of from now? (like what firmware i should not flash, or Rom or radio restrictions)
Thanks.
the same questions
coolshritz said:
My main concerns are
1. Can i downgrade the hboot anytime ?
2. Can i get back to 100% stock? With S-on ? if so any help regarding this is greatly appreciated.
3. I'm now new to S-Off thing, and is there anything that i should take care of from now? (like what firmware i should not flash, or Rom or radio restrictions)
Thanks.
Click to expand...
Click to collapse
dingnangen said:
the same questions
Click to expand...
Click to collapse
With S-Off:
1- Yes you can downgrade/upgrade anytime you see fit.
2- 100% Stock with S-Off!! With S-On, you can get pretty close but you can't make your bootloader say "LOCKED" it will only show "RELOCKED"
3- no restrictions, you can flash pretty much anything with S-Off (obviously you should stay away from Sprint or Verizon stuff as they are not GSM)
4- don't go S-On!
nkk71 said:
With S-Off:
1- Yes you can downgrade/upgrade anytime you see fit.
2- 100% Stock with S-Off!! With S-On, you can get pretty close but you can't make your bootloader say "LOCKED" it will only show "RELOCKED"
3- no restrictions, you can flash pretty much anything with S-Off (obviously you should stay away from Sprint or Verizon stuff as they are not GSM)
4- don't go S-On!
Click to expand...
Click to collapse
4- can i downgrade to 1.44 then s-on using revone?(for warranty)after that,can I get s-off again using revone?
Sent from my HTC One using Tapatalk 2
dingnangen said:
4- can i downgrade to 1.44 then s-on using revone?(for warranty)after that,can I get s-off again using revone?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
If you really need to go S-On again (though many people send in their phones with S-Off, cause some actually ship from HTC S-Off), here are the steps:
1- change CID & MID back to stock (in case you changed them)
2- remove TAMPERED using either revone or http://forum.xda-developers.com/show....php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/show....php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU
5- AFTER YOUR ARE 100% SATISFIED OF ABOVE RESULTS (ie no more tampered, bootloader LOCKED, 100% stock)
"fastboot oem writesecureflag 3" to get S-On.
Hit the thanks button if I helped
Nkk71 I have a similar question
I s offed then restored a nandroid backup of 4.1.2 and removed tampered and locked bootloader. I ota'd right up to the latest 3.62.306.7 version soiit's stock Rom, stock recovery and hboot 1.55
Can I s on for warranty purpose now?
stovie_steve said:
Nkk71 I have a similar question
I s offed then restored a nandroid backup of 4.1.2 and removed tampered and locked bootloader. I ota'd right up to the latest 3.62.306.7 version soiit's stock Rom, stock recovery and hboot 1.55
Can I s on for warranty purpose now?
Click to expand...
Click to collapse
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
nkk71 said:
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
Click to expand...
Click to collapse
One last question. If i give you my flow of what I did can you help, as I don't want to s-on and mess it up...
1. Rumrunner to obtain s-off on hboot 1.54
2. Downgraded my hboot to 1.44 - this was a stock hboot, but I modified the android.info part so I could flash it onto my model
3. Changed CID to HTC__032 and ran "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed" which reset my hboot, bootloader etc and completely stock. At this stage my bootloader is LOCKED and still s-off
4. With bootloader still locked, installed CWM Recovery and restored a nandroid backup CID O2__102 1.27.206.1 and stock recovery
5. Changed CID back to O2___001
6. Installed the various OTA updates right up to current 3.62.206.1 software version and hboot is 1.54
Now can I s-on??
---------- Post added at 08:11 PM ---------- Previous post was at 07:26 PM ----------
nkk71 said:
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Does the cimmitno-bootloader: dirty-d959c75800 mean that if I s-on it will brick the phone as well?
nkk71 said:
If you really need to go S-On again (though many people send in their phones with S-Off, cause some actually ship from HTC S-Off), here are the steps:
1- change CID & MID back to stock (in case you changed them)
2- remove TAMPERED using either revone or http://forum.xda-developers.com/show....php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/show....php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU
5- AFTER YOUR ARE 100% SATISFIED OF ABOVE RESULTS (ie no more tampered, bootloader LOCKED, 100% stock)
"fastboot oem writesecureflag 3" to get S-On.
Hit the thanks button if I helped
Click to expand...
Click to collapse
when I get back my phone from HTC service center,i can get soff my phone(hboot1.44) again using revone,right?
Sent from my HTC One using Tapatalk 2
Now that I have latest updates but all of different region. I'm from x.xx.707.x but I have x.xx.401.x Rom and bootloader. The bootloader is custom so it says developer edition phone. I have a backup of just rom of my stock version.
What would be the best way to go to stock now. My current hboot version is 1.55 custom and rom is 3.62.401.1. I have rom backup of 2.24.707.3 that had hboot of 1.54.
Sent from my HTC One using xda app-developers app
guys no need for s-on for warranty and don't go s-on cause there can be a problem to go back to s-off.Secondly if u r concerned abt the service just flash 1.29 ruu use revone remove tampered lock ur bootloader and ota ur way to 4.2 update.Many guys have given their one with s-off and they got through service without a hitch.Hell even im gonna go on monday to service center cause my camera module has gone kaput and a dead zone in the mid section of touchscreen but with s-off , bootloader locked and everything stock and the red text doesn't come after u lock the bootloader . So what's the problem ???
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
coolshritz said:
Now that I have latest updates but all of different region. I'm from x.xx.707.x but I have x.xx.401.x Rom and bootloader. The bootloader is custom so it says developer edition phone. I have a backup of just rom of my stock version.
What would be the best way to go to stock now. My current hboot version is 1.55 custom and rom is 3.62.401.1. I have rom backup of 2.24.707.3 that had hboot of 1.54.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Be careful if u wanna go stock here's what u should do:
1.) First of all flash a non modified stock hboot doesn't matter what version but it should be unmodified since custom hboot can lead to hard brick when going back to stock.
2.) Now after flashing stock unmodified hboot just flash the 1.29 ruu use revone remove tampered if there lock bootloader and ota ur way to 4.2.2 the latest available for us indian users.But don't s-on cause its risky cause i don't know whether u can go back s-off after s-on so just leave s-off as it is.
That's it ur done
Slim Shady said:
guys no need for s-on for warranty and don't go s-on cause there can be a problem to go back to s-off.Secondly if u r concerned abt the service just flash 1.29 ruu use revone remove tampered lock ur bootloader and ota ur way to 4.2 update.Many guys have given their one with s-off and they got through service without a hitch.Hell even im gonna go on monday to service center cause my camera module has gone kaput and a dead zone in the mid section of touchscreen but with s-off , bootloader locked and everything stock and the red text doesn't come after u lock the bootloader . So what's the problem ???
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
Be careful if u wanna go stock here's what u should do:
1.) First of all flash a non modified stock hboot doesn't matter what version but it should be unmodified since custom hboot can lead to hard brick when going back to stock.
2.) Now after flashing stock unmodified hboot just flash the 1.29 ruu use revone remove tampered if there lock bootloader and ota ur way to 4.2.2 the latest available for us indian users.But don't s-on cause its risky cause i don't know whether u can go back s-off after s-on so just leave s-off as it is.
That's it ur done
Click to expand...
Click to collapse
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
stovie_steve said:
Does the cimmitno-bootloader: dirty-d959c75800 mean that if I s-on it will brick the phone as well?
Click to expand...
Click to collapse
No it will not brick, it's always "dirty", no worries.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
coolshritz said:
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
Click to expand...
Click to collapse
Yes you are right, the "Tell HTC" part will have the red text with S-Off and will only go away when you're 100% stock and then set S-On.
coolshritz said:
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
Click to expand...
Click to collapse
Yes It's solely because you're S-OFF. Your device has all security disabled, thus it acts like a test device. Once you go S-ON, the red text will immediately disappear. Well have u mended everything else except the s-off like remove tampered restoring mid and cid if changed.Update to 4.2.2 go to service center turn in ur device and if they by chance ask (generally they don't) abt s-off tell i don't know and it was like that only when u bought it and voila have ur phone repaired/replaced as the situation demands for it.
Going back s-on is really ur choice though not recommended cause if u get the same phone back repaired complications might arise in going back to s-off.
dingnangen said:
when I get back my phone from HTC service center,i can get soff my phone(hboot1.44) again using revone,right?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
yes, for hboot 1.44 (pre June 2013) you can use revone for 1.54 you can use rumrunner.
nkk71 said:
yes, for hboot 1.44 (pre June 2013) you can use revone for 1.54 you can use rumrunner.
Click to expand...
Click to collapse
I saw that : WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you will receive back a non-s-offable device... YOU HAVE BEEN WARNED
In this post : http://forum.xda-developers.com/showthread.php?p=45270020
Sent from my HTC One using Tapatalk 2
dingnangen said:
I saw that : WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you will receive back a non-s-offable device... YOU HAVE BEEN WARNED
In this post : http://forum.xda-developers.com/showthread.php?p=45270020
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I agree with the S-Off part, as some phones ship S-Off. The important parts are 100% stock rom, firmware, recovery, hboot; no TAMPERED or red text on boot. and LOCKED not RELOCKED.
However some people have been denied warranty because of S-Off (really depends on country, service center, and probably most important the person in the center).
As for "you will receive back a non-s-offable device" this is no longer the case since rumrunner can now achieve s-off on hboot 1.54 and 1.55.
It's locked, OTA 4.3 update with S-On but after i did this:"fastboot oem writesecureflag 3" to get S-On.
It's ***tampered*** again....
What to do, everything is back to stock now, no root..
nkk71 said:
I agree with the S-Off part, as some phones ship S-Off. The important parts are 100% stock rom, firmware, recovery, hboot; no TAMPERED or red text on boot. and LOCKED not RELOCKED.
However some people have been denied warranty because of S-Off (really depends on country, service center, and probably most important the person in the center).
As for "you will receive back a non-s-offable device" this is no longer the case since rumrunner can now achieve s-off on hboot 1.54 and 1.55.
Click to expand...
Click to collapse
it's means that if I get back my phone with 4.1(hb1.44,i will tell HTC don't update my system),I can also get soff using revone?
Sent from my HTC One using Tapatalk 2
Why did you do it when you already had S-On??
Hi all, i have htc one developer edition with
HBOOT- 1.55.0000,
Bootloader unlocked,
S-ON
Radio-4A.20.3263.16
Stock Rom: Android 4.3, Sense 5.0
How to S-off??
jimmy_coolguy2006 said:
Hi all, i have htc one developer edition with
HBOOT- 1.55.0000,
Bootloader unlocked,
S-ON
Radio-4A.20.3263.16
Stock Rom: Android 4.3, Sense 5.0
How to S-off??
Click to expand...
Click to collapse
Make sure you have root access and use Rumrunner s-off tool. If it fail to acheive s-off, flash the custom rom ARHD 31.6 and try rumrunner again (arhd 31.6 should have everything pre-installed to make rumrunner works i.e. root and unsecured kernel). then with s-off you will be able to run the dev edition ruu to restore your phone to stock firmware and still having s-off and possiblity to update ota to 4.06.1540.3
Yea!
alray said:
Make sure you have root access and use Rumrunner s-off tool. If it fail to acheive s-off, flash the custom rom ARHD 31.6 and try rumrunner again (arhd 31.6 should have everything pre-installed to make rumrunner works i.e. root and unsecured kernel). then with s-off you will be able to run the dev edition ruu to restore your phone to stock firmware and still having s-off and possiblity to update ota to 4.06.1540.3
Click to expand...
Click to collapse
I had the same problem, follow the steps, it worked! S OFF! :good: Tnx
I hoping I can get some clarification on this subject. I may have to take my phone into Sprint for either repair or new phone since it will not connect to the newly added 4G network in my area. So going back to stock my be needed for me to do so.
Since the RUU for the 4.4.2 update isn't available yet, is there a way to downgrade back to 4.3 so I can return back to stock? I did the OTA update in stock, then gained root access.
Does the process require me to turn S-Off? I'm currently S-On running Running Bad Boyz Sprint ONE KitKat v1.0.
If I go S-Off, is there a way to turn it back S-On? Not sure if Sprint will look at this setting.
Also, I have the update radio and hboot
HBOOT- 1.56.0000
RADIO- 1.00.20.1108
OS- 4.06.651.4
Will I have to downgrade my hboot as well?
Any help will be much appreciated
lihtsout said:
I hoping I can get some clarification on this subject. I may have to take my phone into Sprint for either repair or new phone since it will not connect to the newly added 4G network in my area. So going back to stock my be needed for me to do so.
Since the RUU for the 4.4.2 update isn't available yet, is there a way to downgrade back to 4.3 so I can return back to stock? I did the OTA update in stock, then gained root access.
Does the process require me to turn S-Off? I'm currently S-On running Running Bad Boyz Sprint ONE KitKat v1.0.
If I go S-Off, is there a way to turn it back S-On? Not sure if Sprint will look at this setting.
Also, I have the update radio and hboot
HBOOT- 1.56.0000
RADIO- 1.00.20.1108
OS- 4.06.651.4
Will I have to downgrade my hboot as well?
Any help will be much appreciated
Click to expand...
Click to collapse
You're S-On. Your only option is to perform a factory reset, flash the stock recovery and re-lock your bootloader.
Kraizk said:
You're S-On. Your only option is to perform a factory reset, flash the stock recovery and re-lock your bootloader.
Click to expand...
Click to collapse
Thanks
Do you forward me to a thread that has shows me how to do this? I have an idea on how to do it, just want make sure I do it correctly.
lihtsout said:
Thanks
Do you forward me to a thread that has shows me how to do this? I have an idea on how to do it, just want make sure I do it correctly.
Click to expand...
Click to collapse
unlock recovery
install custom recovery
root
s-off with firewater
downgrade hboot to 1.55
relock bootloader
run RUU 4.3.
Hboot files
ludatrick said:
unlock recovery
install custom recovery
root
s-off with firewater
downgrade hboot to 1.55
relock bootloader
run RUU 4.3.
Click to expand...
Click to collapse
hi I just came across one of the Sprint HTC Max on 4.4.2 with 2.49 hboot. I'd like to unlock the phone but can't find a hboot file to downgrade. Currently s-off, rooted, TWRP and unlocked. It would be great if you could help a brotha out...
Thanks,
Sonny
unlock bootloader
install custom recovery
root
s-off with firewater
downgrade hboot (check rumrunner website for hboot file)
relock bootloader
run RUU 4.3.
sonny5766 said:
hi I just came across one of the Sprint HTC Max on 4.4.2 with 2.49 hboot. I'd like to unlock the phone but can't find a hboot file to downgrade. Currently s-off, rooted, TWRP and unlocked. It would be great if you could help a brotha out...
Thanks,
Sonny
Click to expand...
Click to collapse
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
You will need s-off to reset the bootloader back to locked instead of re-locked
Sent from my HTC One using xda app-developers app
adoboFosho said:
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
Click to expand...
Click to collapse
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
raghav kapur said:
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
Click to expand...
Click to collapse
the instructions on firewater on their site probably doesn't work with what I have atm cant link to the site yet not enough posts..
what is the best course of action I take?
im running latest android not 4.3 with an m7 not m8 and unrooted
i tried temprooting using firewater just to get s-off didn't work since i have newest android
can someone tell me what to do from here? flash 4.3? root again?!
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded this RUU "RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
seklerek said:
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded this RUU "RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
Click to expand...
Click to collapse
if your phone was on a x.xx.401.x version originally, then use the 1.28.401.7 ruu, then remove *tampered* and *relocked* banner using guru bootloader reset tool by booting a custom recovery using "fastboot boot recovery.img". You can then turn back s-on and send your phone. Everything is described in nkk71's guide linked in my signature.
Don't forget to set back your original CID and MID if you have changed them to convert your phone to GPE before running the ruu
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
seklerek said:
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
Click to expand...
Click to collapse
not for warranty purpose cause you must be on hboot 1.44 or 1.54 to remove the "tampered" and "relocked" flags form bootloader.
4.x.401.x ruu is hboot 1.55
1.x.401.x ruu is hboot 1.44
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
seklerek said:
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
Click to expand...
Click to collapse
Ruu update everything, firmware and software.
Yes you'll be able to take ota update after but don't update before you have removed tampered and relocked from the bootloader. Follow instructions in the guide.
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
seklerek said:
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
Click to expand...
Click to collapse
If you are able to achieve s-off again yes.
They will probably update your phone so it might be more difficult to achieve when it comes back.
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
seklerek said:
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
Click to expand...
Click to collapse
do not update the phone now, just turn back s-on and send it for repair. Its easier to get back s-off on lower version so better not to take any ota, however they will maybe update your phone at the service center (hopefully not).