Okay, so I'm about to send my phone back in to HTC but I have s-off on it. I relocked it and it says that the software status is official. But I don't know how to get s-on. I can't find anything anywhere. Please help if you can
boot it into download mode and type: fastboot oem writesecureflag 3
Make sure, you have all original firmware and no more custom stuff on it =)
If you are not able to get S-On again, I don't think it matters to HTC. They'll take the phone and fix it before the send it out refurbished.
I sent my M7 back for the camera repair s-off but otherwise stock, and they did and said nothing about it.
As a a general rule, going back to s-on is a bad idea for many reasons, especially if you have made modifications to your phone (and even if you think you're back to bone stock). Going s-off allows you to make changes that would not be allowed under s-on, and if you forget something and go back to s-on, you can brick your phone or lock it into an unstable configuration with no way to fix it. I've seen many people do it.
S-off should be viewed as a one-way trip unless you've got a clear reason to go back.
Related
Hey, I've been reading up on what needs to be done to get my device back to stock everything so that they don't bill me for the repair (there's a dead pixel on the screen). I was only running the stock ROM with SuperSU and TWRP recovery. I've already returned the recovery back to the stock recovery I backed up, however my device still says *** TAMPERED *** on the HBOOT screen. I've looked up how to remove this flag, but all the info I have found assumes I have a device that came with a locked bootloader, and mentions something about S-OFF. Since I have the developer edition, I don't want to lock the bootloader since it was never locked to begin with. What steps should I take to remove the tampered flag? Do I still need to worry about S-OFF?
Dr.Preston said:
Hey, I've been reading up on what needs to be done to get my device back to stock everything so that they don't bill me for the repair (there's a dead pixel on the screen). I was only running the stock ROM with SuperSU and TWRP recovery. I've already returned the recovery back to the stock recovery I backed up, however my device still says *** TAMPERED *** on the HBOOT screen. I've looked up how to remove this flag, but all the info I have found assumes I have a device that came with a locked bootloader, and mentions something about S-OFF. Since I have the developer edition, I don't want to lock the bootloader since it was never locked to begin with. What steps should I take to remove the tampered flag? Do I still need to worry about S-OFF?
Click to expand...
Click to collapse
You need to be S-OFF to remove the tampered flag.
[how to] remove your "tampered" banner
Though I'll find it funny if they have issues with a tampered flag on a developer edition seeing as the bootloader comes unlocked already. Pretty obvious someone is gonna do some "developing" of some sorts on it. Anyways...
BerndM14 said:
You need to be S-OFF to remove the tampered flag.
[how to] remove your "tampered" banner
Though I'll find it funny if they have issues with a tampered flag on a developer edition seeing as the bootloader comes unlocked already. Pretty obvious someone is gonna do some "developing" of some sorts on it. Anyways...
Click to expand...
Click to collapse
Thanks. Firewater didn't work so I had to use Sunshine
You would think they wouldn't care but when I was on the phone with them they weren't sure. Since I opted to have them overnight me a replacement and have me ship them back my defective unit afterwards, I don't really get to negotiate any "out of warranty" issues, even if they are unrelated to the defect.
Hello fellow TMO brethren....
I just got the M8 maybe a week ago... I was busy and had to wait before I could pull up XDA and start reading about this phone (getting root, etc.). Before this, I unfortunately allowed a few updates (2 maybe?) to install, which I believe will prevent me from using Firewater for S-Off... but no big deal....will get sunshine when I need it. However, though firewater won't work, I had no problem using HTCDev to unlock the bootloader (didn't know of towelroot at the time), flashing TWRP 2.8.0.1, and installing SuperSU....so I am currently rooted with stock Rom...
Further...I have not touched any applications. And although I have unlocked the bootloader using HTCDev, my calculator and flashlight are still available. I have read in this M8 general forum that the flashlight and calculator are deleted when you unlock the bootloader using HTCDev... This did not happen to me. Does anyone know if this is this just a T-Mobile thing? or has this changed for all carriers?
Anyway, I am now getting notice for yet another update...So I might as well install it. As we all know, I need to re-flash the stock recovery to get the OTA. Here is where I am confused. My current firmware is 2.22.531.5. I don't know what firmware I had a week ago when the phone was purchased.
This was the info on the bootloader screen yesterday, immediately prior to unlocking the BL or rooting the phone:
[btw, can someone tell me how to do a info dump from the bootloader?? is it just an option I missed?]
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio-1.19.213311491.03G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.531.5
eMMC-boot 2048MB
Jul 16 2014,03:33:24.0
1. My first question is what version of the stock recovery do I use?? On the page that contains the stock recoveries, it only shows these two:
Stock Recovery - 1.12.531.19
Stock Recovery - 1.57.531.7
2. Secondly, and I am really irritated about this.... but I never went and accepted the Google Drive free 65GB promo offered by HTC. When I start google drive it states it cannot determine the user (or something like that). I read elsewhere that this is because I unlocked the bootloader. I will do whatever it takes to get HTC to give me this because I think it is pretty low that they would invalidate the offer to anyone who has unlocked the bootloader pursuant to their website, their instructions, and their so-called "open atitude". Obviously I can re-lock the bootloader, but I do not know if that will matter. Plus... if they say that I requested a token .bin file to unlock, I can say that I changed my mind and decided not too. OR, I can get Sunshine, get s-off, and use the s-off ability to relock the bootloader. Does anyone have any advice on any of this?
3. Any general advice from anyone based on the info above??? (lI don't want to foreclose any other options by upgrading or whatever... ).
Thank you very much in advance!
P
NB: Wanted to mention that last night I was about to use Titanium to freeze and/or uninstall some crap software I didn't want, and to that end, disabled Amazon, Facebook, Facebook for HTC, and Kid Zone (and uninstalled Amazon MP3, which is not a system app). Just an FYI... disabling one (or more) of these apps (maybe Kid Zone?) prevented Wifi calling from functioning correctly...it would not let me call and every in-call received while on wifi calling went straight to VM. I have renabled the above apps to get wifi-calling working again, but also because I want to install this update and figured that disabling/freezing any original stock apps might cause problems. I will look around for a thread on safely deleting apps after I get this udpate...
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
phil.culler said:
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
Click to expand...
Click to collapse
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
syntropic said:
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
Click to expand...
Click to collapse
It looks like you will need S-Off to factory lock the bootloader. S-Off allows you to make changes to otherwise protected areas of the file system. To clarify, I haven't tried this method myself as I haven't had a need to factory relock my device yet. I ran full stock for months before I rooted. As for HTC knowing whether or not you unlocked your bootloader, if you used the HTCDEV method then they have record of you receiving an unlock token from them but if they go into bootloader for any reason and see Locked instead of Relocked they shouldnt give you any trouble I would think. I believe you can also reset it to S-On but again I've never tried and I'm not sure its entirely safe. You'll have to look into that.
hi,
i have to return my phone guarantee because the speaker and jack input doesnt work.
i have already unroot device, flash stock recovery, (i was all the time s-on), flash stock rom and trying to lock bootloader but i cant make it LOCKED (it's RELOCKED). i was looking for any "how to" but im blind ...
can anyone help with making my bootloader LOCKED ?
pangapz said:
hi,
i have to return my phone guarantee because the speaker and jack input doesnt work.
i have already unroot device, flash stock recovery, (i was all the time s-on), flash stock rom and trying to lock bootloader but i cant make it LOCKED (it's RELOCKED). i was looking for any "how to" but im blind ...
can anyone help with making my bootloader LOCKED ?
Click to expand...
Click to collapse
are you s off?
no, im sON
Only way to put it back totally stock is to be S-off.
Magnum_Enforcer said:
Only way to put it back totally stock is to be S-off.
Click to expand...
Click to collapse
yeah, i dont even think about paying 25$ to s-off...
and i have one more problem: i got "Software status : Modified", i want it Official (Original), do i need s-off to make it ?
i was searching some threads and i found that flashing RUU can solve this problem but i can find RUU from my carrier (Plus, Poland)
Just a thought... 25 dollars to s-off could save you getting charged for your repair if they see you're "relocked" and deny your warranty. ?
Darth said:
Just a thought... 25 dollars to s-off could save you getting charged for your repair if they see you're "relocked" and deny your warranty.
Click to expand...
Click to collapse
i know but its a "mechanical" issue not the software so they should reapir it even bootloader is unlocked ;P but i want be sure they'll do it without any problems
is possible to make Software Status : Official from Modified ?
(S-ON)
Is 25$ s-off way , can be use multiply on my device ?
You'll need S-OFF to completely return to stock with no tampering signs.... But, if they don't send you back your same device , you would need to purchase Sunshine again unfortunately. Or stay s-on.
Sunshine license is for one device only.
If they send same unit back, yes, it will work again.
But switching back to s-on is really not necessary when you send it in. I've sent mine in with s-off and many others have without issue. But that's your call. ?
I have a carrier locked M8 that is rooted but S-On.
The vibrator motor on my phone quit and both HTC and my wireless provider have deemed it a hardware error that require repair. The device is under warranty. I need to send it in to get repaired. Given that it's still S-On, do I just need to restore the stock recovery and OS before sending it in?
Probably not safe to assume that because it's a hardware issue, the software doesn't matter?
A lot of times you can get away with sending in a modded phone. Most of those techs aren't smart enough (no offence) to notice things like that unless its major i.e the red text on the boot up screen, or a sense m8 running miui or maybe even GPE stuff. I would flash a sense ROM and a "no red text" bootloader before I send it in.
josh.walker.9242 said:
A lot of times you can get away with sending in a modded phone. Most of those techs aren't smart enough (no offence) to notice things like that unless its major i.e the red text on the boot up screen, or a sense m8 running miui or maybe even GPE stuff. I would flash a sense ROM and a "no red text" bootloader before I send it in.
Click to expand...
Click to collapse
But do you only get one shot at it? If they uncover its modded, surely they make record of it? Not like I could send it in, they send it back because it's modded, and then I could do a deeper clean (100% back to stock) before sending it back again, right?
Am I safer to clean it up entirely before sending it in?
djHandy said:
But do you only get one shot at it? If they uncover its modded, surely they make record of it? Not like I could send it in, they send it back because it's modded, and then I could do a deeper clean (100% back to stock) before sending it back again, right?
Am I safer to clean it up entirely before sending it in?
Click to expand...
Click to collapse
Correct, it would be safer to do a 100% cleasn stock restore just make a backup so you can slrestore it when you get it back.
josh.walker.9242 said:
Correct, it would be safer to do a 100% cleasn stock restore just make a backup so you can slrestore it when you get it back.
Click to expand...
Click to collapse
I'm following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2710735
It says I need to be S-Off to remove the red-text from the bootloader screen but then warns against switching back to S-On.
Is S-Off a flag to techs that the phone is tampered? Anything else I should consider before going S-Off without a way back or is S-Off really my only option to return my phone to a repairable/warranty-able state?
djHandy said:
I'm following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2710735
It says I need to be S-Off to remove the red-text from the bootloader screen but then warns against switching back to S-On.
Is S-Off a flag to techs that the phone is tampered? Anything else I should consider before going S-Off without a way back or is S-Off really my only option to return my phone to a repairable/warranty-able state?
Click to expand...
Click to collapse
This thread explains S-Off - http://forum.xda-developers.com/showthread.php?t=1680928.
Here's another good read - http://forum.xda-developers.com/showthread.php?t=2718106.
I would suggest going S-Off to flash the stock or no red text bootloader, then relocking the bootloader and going S-On until you get the phone back.
Back on the M7, there was this incredible software that not only returned the phone to S-On, but also lock the bootloader in such a way that it doesn't say "Relocked" but Actually just "Locked". Is there such a method for the M9?
shark0807 said:
Back on the M7, there was this incredible software that not only returned the phone to S-On, but also lock the bootloader in such a way that it doesn't say "Relocked" but Actually just "Locked". Is there such a method for the M9?
Click to expand...
Click to collapse
Yes, there are methods to return to "locked" instead of "relocked" and to change your software status back to "Original" but if you have made modifications to your phone, going back to s-on is a bad idea, potentially dangerous, and not necessary. Doing it is easy, but why would you want to?
What if someone wants to make use of a warranty repair, and it is important for him to make sure that the phone does not appeared to be "tampered"?
shark0807 said:
What if someone wants to make use of a warranty repair, and it is important for him to make sure that the phone does not appeared to be "tampered"?
Click to expand...
Click to collapse
I have sent HTC phones back for repair s-off and had no issues. HTC has explicitly stated that modded phones are eligible for Uh-Oh and similar protection, though not all CSRs got that memo.
If you feel you must go back to s-on for warranty repair, you need to follow the return-to-stock guides exactly or you risk brickage. You will have to do this manually; I am not aware of a toolkit that could do this and would never use it if there were. Too many variables on going back to full stock (different bases, etc.).