OK, so I jumped ship and bought a G3 (for $1 ), and am going to let my daughter have my One. It's unlocked and S-Off. I just ran the latest RUU for it, so outside of being S-Off and unlocked, it's stock.
At first I was going to S-On and re-lock, or vice versa, just to prevent anything bad happening, but got to thinking, if she's running a stock, unrooted ROM, without SU, there's little risk of her creating any issues, right?
Secondly, will it be OK to take an OTA? I know generally taking OTA isn't good, but she won't be running custom or rooted ROM, anyway, so nothing should break, Right?
Thanks in advance!
to get into the bootloader you need to hold down the two seperate buttons so if she doesnt know about bringing it into bootloader and recovery I doubt she could do anything to it and without SU on the rom there isnt much she could do to it other than forgetting a password then all you have to do is get into recovery and flash a new rom.
toad6386 said:
OK, so I jumped ship and bought a G3 (for $1 ), and am going to let my daughter have my One. It's unlocked and S-Off. I just ran the latest RUU for it, so outside of being S-Off and unlocked, it's stock.
At first I was going to S-On and re-lock, or vice versa, just to prevent anything bad happening, but got to thinking, if she's running a stock, unrooted ROM, without SU, there's little risk of her creating any issues, right?
Secondly, will it be OK to take an OTA? I know generally taking OTA isn't good, but she won't be running custom or rooted ROM, anyway, so nothing should break, Right?
Thanks in advance!
Click to expand...
Click to collapse
Well, just so you know, there is a reason bootloaders are locked on delivery. If your daughter loses her phone, it is entirely possible for someone to extract data out of it via fastboot.
I would at the very least lock the bootloader, just for the peace of mind.
S-Off and unlocked do not affect how the phone operates whatsoever. They only affect what can be modified on the phone on a broader scale (radio, recovery, system, boot partitions).
If the phone is unrooted, and she doesn't have access to ADB, then there is no way she can break the phone, rest assured.
sauprankul said:
Well, just so you know, there is a reason bootloaders are locked on delivery. If your daughter loses her phone, it is entirely possible for someone to extract data out of it via fastboot.
I would at the very least lock the bootloader, just for the peace of mind.
Click to expand...
Click to collapse
Excellent point! Thanks!
Related
Hey Guys,
So I am need of a bit of help and guidance. I currently have a HTC One 32Gb Silver from T-Mobile (US). I need to return my phone for warranty exchange but so far I have put several different roms, TWRP recovery, perm root, and obv unlocked bootloader. I need to return everything to how it was out of the box. I made a backup of my stock rom way back in May after I unlocked the bootloader. I know generally people would use an RUU but I do not think there is one for T-Mobile US. So I just need some guidance on how to put back factory recovery, and then relock bootloader without T-Mobile it was ever unlocked. I believe this can be achieved thru S-OFF then S-On back on again after you fix the "re-locked" and "tampered". If someone can walk me through how to properly do this and the files I would need I give you huge gratitude.
-TAB
theamazingbeat said:
Hey Guys,
So I am need of a bit of help and guidance. I currently have a HTC One 32Gb Silver from T-Mobile (US). I need to return my phone for warranty exchange but so far I have put several different roms, TWRP recovery, perm root, and obv unlocked bootloader. I need to return everything to how it was out of the box. I made a backup of my stock rom way back in May after I unlocked the bootloader. I know generally people would use an RUU but I do not think there is one for T-Mobile US. So I just need some guidance on how to put back factory recovery, and then relock bootloader without T-Mobile it was ever unlocked. I believe this can be achieved thru S-OFF then S-On back on again after you fix the "re-locked" and "tampered". If someone can walk me through how to properly do this and the files I would need I give you huge gratitude.
-TAB
Click to expand...
Click to collapse
I can't walk you through the steps, but you'll find more assistance in the T-Mobile HTC One forum. The official T-Mobile RUU is actually available now and can be found here:
http://forum.xda-developers.com/showthread.php?t=2375223
Sent from my Nexus 7 (2013) using XDA Premium
theamazingbeat said:
Hey Guys,
So I am need of a bit of help and guidance. I currently have a HTC One 32Gb Silver from T-Mobile (US). I need to return my phone for warranty exchange but so far I have put several different roms, TWRP recovery, perm root, and obv unlocked bootloader. I need to return everything to how it was out of the box. I made a backup of my stock rom way back in May after I unlocked the bootloader. I know generally people would use an RUU but I do not think there is one for T-Mobile US. So I just need some guidance on how to put back factory recovery, and then relock bootloader without T-Mobile it was ever unlocked. I believe this can be achieved thru S-OFF then S-On back on again after you fix the "re-locked" and "tampered". If someone can walk me through how to properly do this and the files I would need I give you huge gratitude.
-TAB
Click to expand...
Click to collapse
Gain Soff
Turn off the tamper stuff
Flash RUU
Everything will appear stock
once the new revone comes out you can go back to s-on and it really is all stock
BableMan said:
Gain Soff
Turn off the tamper stuff
Flash RUU
Everything will appear stock
once the new revone comes out you can go back to s-on and it really is all stock
Click to expand...
Click to collapse
So let's say I already called T-Mobile and I need to return my phone within 7 days what do I do now?
theamazingbeat said:
So let's say I already called T-Mobile and I need to return my phone within 7 days what do I do now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2381817
Look at second post and follow his instructions...worked like a charm S-OFF and put back to S-ON is available now
I got my phone back from repair and I'm confused ass to what to do next. I'm set to 'relocked' bootloader, but s-off without recovery or su apparently on 4.3. Every guide I find requires me to do something that causes things to come to as halt. Unless I'm doing something wrong I can't flash a recovery due to some error, then can't flash anything through recovery obviously, and I tried rumrunner but that stalls out after some point saying 'device is not rooted AND unsecure kernel'. What do I do next? Will HTCDev work? That's how I originally unlocked at release.
Really need help here, leaving the country for 3 weeks thursday morning and want to be back in business.
included pic of bootloader
yeah unlock again at htc dev then you will be able to flash a recovery
Or look here
[how to] lock/unlock your bootloader without htcdev(s-off required)
Thanks, had a feeling I needed to HTCDev again but didn't want to risk it given my limited time. Took some tinkering but looks like I'm unlocked and rooted again. Thanks BD.
Is the following going to be what I need to get my phone in for warranty? Do I need to go back to S-ON or does S-OFF not void warranty if everything else is stock?
What I did:
1) Make a full TWRP backup and copy it to my HD from the phone.
2) Remove my “tampered flag” (thank you scotty1223)
3) Do a “Wipe” in TWRP.
4) Downloaded the “1.54.651.8-Stock.zip” and flashed that using TWRP (thank you Rydah805).
5) Downloaded the “Stock Recovery From 1.54.651.8 OTA" from the same thread.
6) Manually flashed the recovery.img above in fastboot using the command “fastboot flash recovery recovery.img”
7) Relock the “lock status flag” to lock my bootloader using this thread (thank you again scotty1223).
At this point I had a completely wiped system on reboot. I don’t know how but SuperSU was still on my device when I powered it back on but everything else was wiped. I then went in to SuperSU “settings” and then did the “Full unroot” to uninstall SuperSU.
Is this all I need to do to send in for warranty on my cracked screen or do I need to remove S-OFF on the bootloader also?
Thank you to all.
did you use htcdev to unlock?
Sent from my 831C using Tapatalk
Zzz73 said:
did you use htcdev to unlock?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Yes, I initially used the HTCDEV to unlock which voids the warranty. There are ways to revert from that though and that is what I am trying to accomplish by going back to stock everything.
I don't know if I need to flash the full firmware or not after I installed the stock nandroid backup from step 4).
Thank you for the reply.
oh OK. of you know a way around. i thought it registered your serial with HTC...
Sent from my 831C using Tapatalk
murf43143 said:
Is the following going to be what I need to get my phone in for warranty? Do I need to go back to S-ON or does S-OFF not void warranty if everything else is stock?
What I did:
1) Make a full TWRP backup and copy it to my HD from the phone.
2) Remove my “tampered flag” (thank you scotty1223)
3) Do a “Wipe” in TWRP.
4) Downloaded the “1.54.651.8-Stock.zip” and flashed that using TWRP (thank you Rydah805).
5) Downloaded the “Stock Recovery From 1.54.651.8 OTA" from the same thread.
6) Manually flashed the recovery.img above in fastboot using the command “fastboot flash recovery recovery.img”
7) Relock the “lock status flag” to lock my bootloader using this thread (thank you again scotty1223).
At this point I had a completely wiped system on reboot. I don’t know how but SuperSU was still on my device when I powered it back on but everything else was wiped. I then went in to SuperSU “settings” and then did the “Full unroot” to uninstall SuperSU.
Is this all I need to do to send in for warranty on my cracked screen or do I need to remove S-OFF on the bootloader also?
Thank you to all.
Click to expand...
Click to collapse
I would put it back to s-on as well.
FlowingAway said:
I would put it back to s-on as well.
Click to expand...
Click to collapse
Thank you for the reply.
I was under the impression that S-OFF did not void warranty on its own and in fact I read on many of the threads I posted that they recommend not to go back to S-ON.
I need to find that out I suppose. Thanks again.
murf43143 said:
Thank you for the reply.
I was under the impression that S-OFF did not void warranty on its own and in fact I read on many of the threads I posted that they recommend not to go back to S-ON.
I need to find that out I suppose. Thanks again.
Click to expand...
Click to collapse
The only reason I say that is because I had a bad experience last year with my M7 being sent back to HTC.
If I was confident I could get s-off again when the phone cane back I would do it just to make sure it wouldn't be denied. Of course that's just me. Definitely try and find some more people's experience before you do anything.
I don't think anyone here can give you a definitive answer to your question because people have all had different experiences when it comes to HTC's warranty department. Some get denied for tampering and voiding the warranty while another customer with almost an almost identical issue breezes through without even un-rooting.....
It is very likely they have some other means of telling whether the stock firmware/software has been replaced at some point that we have no clue about. If they wanted to be hardarses about this kind of thing I'm sure they are quite capable of doing so but I do not think it is in their best interest as a company to get that kind of PR when you have Google and Motorola offering warranties (guaranteed or something like that I read somewhere?) despite tampering. 'Power users' like most of the members on XDA, are a huge market who often have multiple devices and a high level of influence with friends, relatives, coworkers etc when it comes time for their upgrades...You can see where that train of thought ends up I hope.^^
Anyway, sorry for the ranting, haha. My point is that you should take every precaution you can including going back to S-On, "Locking" the bootloader again, and ensuring your device is as exactly like it was when you first got it if you want to minimize your chances of getting denied your warranty. You can always look back on it and go, well maybe I didn't have to go through all that trouble but sure glad it got fixed! That's a much better alternative than the regret you'd have if something as simple as S-Off is to fix(or faux fix) resulted in your claim getting denied.^^
Best of luck, whatever you decide!
So, my still rooted and S-On Sprint HTC M8 just received a notification that an update is available.
I AM going to eventually root and s-off this thing, but I am going to be going on a few trips soon so I figured it would be best to wait until after just in case something goes wrong so I won't be out of a phone while not at home.
Just wanted to know if anybody can confirm if the current firewater S-Off and/or Weaksauce temproot methods still work if you install these on an unmodified Sprint M8.
Cyber Akuma said:
So, my still rooted and S-On Sprint HTC M8 just received a notification that an update is available.
I AM going to eventually root and s-off this thing, but I am going to be going on a few trips soon so I figured it would be best to wait until after just in case something goes wrong so I won't be out of a phone while not at home.
Just wanted to know if anybody can confirm if the current firewater S-Off and/or Weaksauce temproot methods still work if you install these on an unmodified Sprint M8.
Click to expand...
Click to collapse
I think you're rolling the dice there. Even if you find one that can be S-Off'd with the new firmware on it that doesn't necessarily mean that the next person will get the same result as we have seen phones that are identical in software and firmware both fail and succeed at obtaining S-Off. In short, I think the it's always great to get a sampling of results but I do not believe we would be able to make any accurate conclusions, regarding S-Off anyway, from the data.
I suppose I am interested in knowing whether even a single M8 with the new firmware is able to S-Off with firewater but that's just the curiousity inside me.^^
slimbrady said:
I think you're rolling the dice there. Even if you find one that can be S-Off'd with the new firmware on it that doesn't necessarily mean that the next person will get the same result as we have seen phones that are identical in software and firmware both fail and succeed at obtaining S-Off. In short, I think the it's always great to get a sampling of results but I do not believe we would be able to make any accurate conclusions, regarding S-Off anyway, from the data.
I suppose I am interested in knowing whether even a single M8 with the new firmware is able to S-Off with firewater but that's just the curiousity inside me.^^
Click to expand...
Click to collapse
Well, I'm about to give up on achieving S-Off. Being that I don't tinker with my device the way that I messed around with my previous device, I might be throwing in the towel. I'm possibly even giving up root. This is my first device that truly didn't need to be rooted.
But then again....there's free tethering....
AarSyl said:
This is my first device that truly didn't need to be rooted.
Click to expand...
Click to collapse
The whole **** with how KitKat limits your SD card access alone is enough to get me to root.
Cyber Akuma said:
The whole **** with how KitKat limits your SD card access alone is enough to get me to root.
Click to expand...
Click to collapse
Riiight....forgot about that.
Sent from my 831C using Tapatalk
Go root or go home. (Sorry, couldn't resist)
If you're already at home....well...you're cheating and you should feel bad....so bad that you might as well root anyway because things can't get much worse for you!
Just to let you all know....
Went back to a stock Rom, locked my bootloader, then received the .13 update(could only find .9 stock to use) then the .15 update and was able to unlock my bootloader again with the same .bin file I received from HTCDev, flash a custom Rom, and restore my root with no problems at all.
Tried Firewater again for the heck of it and it actually chugged one bottle....but then whelped me again! =/
slimbrady said:
Just to let you all know....
Went back to a stock Rom, locked my bootloader, then received the .13 update(could only find .9 stock to use) then the .15 update and was able to unlock my bootloader again with the same .bin file I received from HTCDev, flash a custom Rom, and restore my root with no problems at all.
Tried Firewater again for the heck of it and it actually chugged one bottle....but then whelped me again! =/
Click to expand...
Click to collapse
For next time, I don't think you need to lock the bootloader to receive the OTA.
rhe12 said:
For next time, I don't think you need to lock the bootloader to receive the OTA.
Click to expand...
Click to collapse
Hmm well I'd done everything else except for that and it failed so locked it and it worked. Maybe it was just a fluke but either way only took a couple seconds to both lock and unlock again. =)
Edit: Yeah pretty sure you do have to lock it if you're stuck S-On like I am. S-Off most definitely doesn't need to though.
slimbrady said:
Just to let you all know....
Went back to a stock Rom, locked my bootloader, then received the .13 update(could only find .9 stock to use) then the .15 update and was able to unlock my bootloader again with the same .bin file I received from HTCDev, flash a custom Rom, and restore my root with no problems at all.
Tried Firewater again for the heck of it and it actually chugged one bottle....but then whelped me again! =/
Click to expand...
Click to collapse
Has the new radio helped your reception?
I can't s-off either. Big pain to go stock to get OTA's.
Wait, I admit I haven't kept up much on S-Off news, so you mean it's random if your M8 will be able to S-Off or not?
im also failed when want to s-off
how i want to unlock gsm my sprint harman kardon edition if cannot s-off ?
is there any method to unlock gsm without s-off ?
comstar said:
Has the new radio helped your reception?
I can't s-off either. Big pain to go stock to get OTA's.
Click to expand...
Click to collapse
Well I noticed that in certain areas I actuallly start picking up the Spark network where I never exceeded 3G speeds in the past so that is somewhat exciting. Didn't really have any reception issues persay previously but I would say it has been slightly improved overall.....or at least it seems that way to me. Could just be towers too I suppose but meh =)
Cyber Akuma said:
Wait, I admit I haven't kept up much on S-Off news, so you mean it's random if your M8 will be able to S-Off or not?
Click to expand...
Click to collapse
Pretty much....We've discounted "batches" being the case by virtue of serial number comparisons and, as far as I am aware, no one has been able to identify any kind of pattern to it.
You would think that the newer the phone the less likely you could s-off with it...and perhaps that is the case....but we've seen people as recent as this week go in and get one, take it home and firewater s-off with it while I've had mine for much longer and can't...maybe the ones people are getting were sitting around for a long time I guess...All pretty much educated (or not educated) guessing at this point.
Hey there,
my phone is broken, it won't load or do anything on the usb port while the system is up, when the phone is off/fastboot or recovery it seems to charge (very slow) and i have no problems accessing it through fastboot or adb.. but even when the battery is fully charged i cannot use it for more than an hour or so before its discharged again..thats what my problem startet with, over the night the phone won't charge and i couldn't use ADB etc while the OS was up...
i think it is a hardware problem, the last thing i did was updating the firmware, but after that i used the phone like 2 weeks or, without problems and changing anything......
first i thought about it could be a bug with the new firmware, so i downgraded to an old stock version and update it through OTA to the latest version but nothing changed..
then i thought of sending it in and i tried to lock my bootloader and restore everything before doing this but the only way to access the phone via adb was in recovery, so i did that and S-ONed the phone and locked the bootloader, not thinking about that i cannot restore the old recovery with locked BL.
since i knew that i am kind of an idiot, not thinking about what exactly i did at this point i thought i pay my rent by buying SunShine an S-On it again (i didn't find another way to root/unlock BL since i was on last HTC-Android version). and replace the recovery with the original one
now i have my phone with stock recovery and everything but i cannot lock/s-off the bootloader again because i have no adb access.
Does anyone have an idead how i can prepare my phone for sending it in?
I thought about rooting stock firmware, replace recovery with stock recovery, write a script that locks the bootloader execute it after replacing recovery and unroot the phone from within SuperSU. then S-OFF it again.
I guess this should work, but since i didn't think about everything the first time i thought i might ask here if someone has a better idea.
smokey_joe said:
Hey there,
my phone is broken, it won't load or do anything on the usb port while the system is up, when the phone is off/fastboot or recovery it seems to charge (very slow) and i have no problems accessing it through fastboot or adb.. but even when the battery is fully charged i cannot use it for more than an hour or so before its discharged again..thats what my problem startet with, over the night the phone won't charge and i couldn't use ADB etc while the OS was up...
i think it is a hardware problem, the last thing i did was updating the firmware, but after that i used the phone like 2 weeks or, without problems and changing anything......
first i thought about it could be a bug with the new firmware, so i downgraded to an old stock version and update it through OTA to the latest version but nothing changed..
then i thought of sending it in and i tried to lock my bootloader and restore everything before doing this but the only way to access the phone via adb was in recovery, so i did that and S-ONed the phone and locked the bootloader, not thinking about that i cannot restore the old recovery with locked BL.
since i knew that i am kind of an idiot, not thinking about what exactly i did at this point i thought i pay my rent by buying SunShine an S-On it again (i didn't find another way to root/unlock BL since i was on last HTC-Android version). and replace the recovery with the original one
now i have my phone with stock recovery and everything but i cannot lock/s-off the bootloader again because i have no adb access.
Does anyone have an idead how i can prepare my phone for sending it in?
I thought about rooting stock firmware, replace recovery with stock recovery, write a script that locks the bootloader execute it after replacing recovery and unroot the phone from within SuperSU. then S-OFF it again.
I guess this should work, but since i didn't think about everything the first time i thought i might ask here if someone has a better idea.
Click to expand...
Click to collapse
You have stated a lot of things but most of them are contradictory.
What is the status of your phone? Locked or Unlocked?
Are you S-ON or S-OFF?
What recovery do you have on the phone? Stock or Custom?
What specifically are you trying to accomplish?
If you have stock rom, stock firmware with stock recovery, bootloader is locked and you are S-ON then you are back to stock. However, if your bootloader states "Tampered" and/or "Relocked" then the service facility will know that you tampered with the phone. To remove those items:
Unlock bootloader
Follow the steps in nkk71's SuperGuide in my signature on:
--Gain S-OFF
--Custom recovery
--Removing "Tampered" & "Locked"
--Install stock firmware
--Gain S-ON
majmoz said:
You have stated a lot of things but most of them are contradictory.
What is the status of your phone? Locked or Unlocked?
Are you S-ON or S-OFF?
What recovery do you have on the phone? Stock or Custom?
What specifically are you trying to accomplish?
If you have stock rom, stock firmware with stock recovery, bootloader is locked and you are S-ON then you are back to stock. However, if your bootloader states "Tampered" and/or "Relocked" then the service facility will know that you tampered with the phone. To remove those items:
Unlock bootloader
Follow the steps in nkk71's SuperGuide in my signature on:
--Gain S-OFF
--Custom recovery
--Removing "Tampered" & "Locked"
--Install stock firmware
--Gain S-ON
Click to expand...
Click to collapse
thanks for your reply.
i guess i was to confused to see that i can remove the tampered and unlocked flags, then restore the stock bootloader and then s-off the phone...i thought i have to remove tampered/unlocked and then s-on the phone in the same step....i guess i have no problem when i can do it like that