Related
Just need a bit of advice here. Was just wondering if I sent my phone to repair (HTC UK Service Center) under warranty, for the camera issue.
Would it affect my warranty claim if I just locked the bootloader and left it s-off?
The reason I ask is because I really don't want to lose the ability to s-off again when the device is returned repaired with the 1.54 hboot.
Please advise
Has anyone tried getting a repair done in this way yet?
Thanks in advance.
Sent from my HTC One using XDA Premium 4 mobile app
should be fine, as long there's no TAMPERED or RELOCKED on the screen, they wont say anything. however they could S-ON the device before returning it, i saw a post somewhere where that happened to a user.
Just send it in with your carrier stock ruu stock recovery non rooted so stock ruu just leave it s-off and you will be fine
Sent from my HTC One using XDA Premium HD app
Ok, thanks for the info Will give it a go, and see what happens...
Just to clarify, it should be fine to send the device in with:
1) A LOCKED bootloader
2) No TAMPERED flag
3) and S-Off still intact?
Is this for definate? Or will the fact that it's still S-Off void the warranty?
Is there a way to edit hboot to be s-off while showing on screen s-on?
Mike
sp5it said:
Is there a way to edit hboot to be s-off while showing on screen s-on?
Mike
Click to expand...
Click to collapse
Decided to revert back to s-on after what I've read over on twitter (https://twitter.com/HTC_UK/status/303902576687079424), just to be on the safe side.
It's not all bad though, at least the phone is good enough on the stock ROM for me and can't afford the extra expense at the moment of paying for repairs. Ah well, S-OFF was good while it lasted
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Stephen304 said:
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Click to expand...
Click to collapse
Its not important at all
Sent from my HTC One using xda app-developers app
With S-off you can flash everything you want on your phone . Downgrade is a most comun reason.
Sent from my HTC 802w
Stephen304 said:
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Click to expand...
Click to collapse
Some carriers are the only users option in their area.
Like for me, that carrier would be Verizon. They have great coverage.
But they also happen to be evil and had HTC block our HTC One's MID from being able to use the HTC Bootloader Unlock bin file.
It will fail the initial checks after getting the token from you.
We also have the 1.54 hboot as stock, so there is no using moonshine, or facepalm, or any other previous method as of yet.
So in order for poor folks with carriers that strongarm smaller companies like HTC into doing things against their wishes and our wishes,
S-off allows us to then change CID,MID, etc,...as well as then go and unlock the bootloader as we should be able to do by choice.
That's why they built it and added in a warranty void warning, so we could make that choice if we so choose.
Anyway, that should make it more clear to you now at least, sorry for the extra carrier rant, lol.
Plus the obvious other advantages of flashing radios, kernels, etc,...without doing fastboot.
Ah okay. So S-off does similar to the HTCDev unlock? If I used S-Off instead could I get rid of the ugly warning text on boot?
Htc dev unlock only needed partitions. S-off unlock ALL
Sent from my HTC 802w
Stephen304 said:
Ah okay. So S-off does similar to the HTCDev unlock? If I used S-Off instead could I get rid of the ugly warning text on boot?
Click to expand...
Click to collapse
Yes you could get ride of the warning text with s-off, with s-on you cannot.
Everything what's said above + more , for example if htc one windows version ever gets ported s-off users can have it , we can also convert our device into ge edition / dev edition / flash whatever comes thru your mind , even splash screens , use modified bootloaders , we can also unlock bootloader without need of HTC official unlock process , we can lock it as well ( s-on can only relock it ) we can also completely hide we ever were rooted / unlocked for warranty reasons while s-on can't.
We can also use super cid which allows us to flash any ruu or use any region / carrier roms.
We can also downgrade bootloader or flash any other.
That's mainly it , also for example us with s-off have writeable partitions while for example s-on users still don't on 3.22 base.
And at the end maybe a good thing for you and some less advanced or less knowledgeable ppl s-on is a good thing since with s-on phone is practically indestructible software-wise , while with s-off small mistake even in fastboot could brick the device.
Sent from my HTC One using XDA Premium 4 mobile app
santod040 said:
Plus the obvious other advantages of flashing radios, kernels, etc,...without doing fastboot.
Click to expand...
Click to collapse
With the HTC One, you can flash radios and kernels in the recovery if you unlock the bootloader...
>> Sent from the abyss <<
Stephen304 said:
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Click to expand...
Click to collapse
To get official OTA with updates to firmware, hboot and everything you have to get them from your carrier, and this depends on your CID. You cannot change this on S-ON. So basically your are bound to your carrier for life, they may but also may not release updates (like for ex. carriers in USA skipped 4.2 if I am not mistaken). You can of course flash custom ROM using dev unlock, but it won't update the firmware.
Ah okay thanks for the info! I have one more question about S-OFF if you don't mind: If I S-OFF and disable the red warning (flashing an unsigned fw), then S-ON again, would the warning come back?
If you do s-on with modified hboot will result an instant and forever brick. Dont do that.
Sent from my HTC 802w
Stephen304 said:
Ah okay thanks for the info! I have one more question about S-OFF if you don't mind: If I S-OFF and disable the red warning (flashing an unsigned fw), then S-ON again, would the warning come back?
Click to expand...
Click to collapse
Why exactly would you want to go back to S-ON?
Sent from my HTC One using Tapatalk 4
I have an HTC one running 4.3 google play I want it to be back to stock so I can sell it. It was originially running Bell mobility but I could not find an RUU for Bell but I found some OTA's for bell. how would I go about this, is it possible? Can I use another RUU and then flash the OTA for bell would that work?
If anyone has a bell RUU that would help alot thank you.
(Canada)
If you fully converted to GPe, then you have s-off. Change the CID and flash a WWE Developers Edition RUU.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
If you fully converted to GPe, then you have s-off. Change the CID and flash a WWE Developers Edition RUU.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't have s-off I checked in the recovery mode it says m7_UL PVT SHIP S-ON RW.
How do I change CID?
iBillz said:
I don't have s-off I checked in the recovery mode it says m7_UL PVT SHIP S-ON RW.
How do I change CID?
Click to expand...
Click to collapse
You can't with s-on. Flash a backup of your carriers stock rom and a stock recovery. Your phone will still say Tampered and Relocked.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
You can't with s-on. Flash a backup of your carriers stock rom and a stock recovery. Your phone will still say Tampered and Relocked.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The goal is for it to go back to a stock HTC one what should I do from here?
iBillz said:
The goal is for it to go back to a stock HTC one what should I do from here?
Click to expand...
Click to collapse
If you never S-off before then you haven't changed your CID. If that's the case then follow @Mike1986 guide to going back to stock. Use method 3.: http://forum.xda-developers.com/showthread.php?t=2265618. Grab the CWM stock Nandroid for your device from here: http://forum.xda-developers.com/showpost.php?p=45187010&postcount=1. [deleted]
That should work as long as you haven't changed your CID before.
Correction: That nandroid should have the stock recovery in it, if it's not then you'll have to search for it and flash it via fastboot. My apologies.
farang4u said:
If you never S-off before then you haven't changed your CID. If that's the case then follow @Mike1986 guide to going back to stock. Use method 3.: http://forum.xda-developers.com/showthread.php?t=2265618. Grab the CWM stock Nandroid for your device from here: http://forum.xda-developers.com/showpost.php?p=45187010&postcount=1. It has the stock recovery in it.
That should work as long as you haven't changed your CID before.
Click to expand...
Click to collapse
Will following what you said make the root untraceable. Meaning the warranty will be unvoided?
iBillz said:
Will following what you said make the root untraceable. Meaning the warranty will be unvoided?
Click to expand...
Click to collapse
No, because your bootloader will indicate "Re-locked" instead of "Locked". Also, your IMEI was registered in HTC's database when you unlocked the bootloader via htcdev website. Only way to cover some of your tracks is to S-off the device by Revone if possible and using their lock command. It involves some risk. Rooting the phone doesn't always void the warranty, many times they'll will honor it if it's a genuine hardware issue.
.
flashing bell firmware help
hi, i wanted to know if there is any way of fixing a touchscreen problem after flashing a firmware, the system is all fine, i have s-on, bootloader locked and also stock recovery with stock rom, but the touchscreen does not work, wondering if i could get some help ( firmware 1.29.666.17 bell canada). thank you.
farang4u said:
No, because your bootloader will indicate "Re-locked" instead of "Locked". Also, your IMEI was registered in HTC's database when you unlocked the bootloader via htcdev website. Only way to cover some of your tracks is to S-off the device by Revone if possible and using their lock command. It involves some risk. Rooting the phone doesn't always void the warranty, many times they'll will honor it if it's a genuine hardware issue.
Click to expand...
Click to collapse
When I try and flash the Nandroid backup it says failed? am I missing something? I ran a factory reset before hand
iBillz said:
When I try and flash the Nandroid backup it says failed? am I missing something? I ran a factory reset before hand
Click to expand...
Click to collapse
You don't flash a nandroid. You unzip it and use the restore function.
Sent from my HTC One using XDA Premium 4 mobile app
Hello everyone,
I have several issues with my HTC One and so I've got to send it to HTC. But for this I have to reset it back to stock so I have the right to claim warranty. Now I proceeded every step from using a RUU and setting the locked state to installing every OTA update. But now the only thing that has to be removed is the S OFF. I heard that you can instantly brick your device if you "fastboot writesecureflag 3" and you have a custom hboot. So now I have the stock hboot 1.55 recieved OTA. Is it secure the turn my phone back S ON? Or do I have to downgrade the hboot 1.44?
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
really? It would just.. be ... f***ing awesome And if they say s off voided my warranty i'm gonna punch them... thanks..
And is it true that some devices are shipped s off by mistake?
LibertyMarine said:
really? It would just.. be ... f***ing awesome And if they say s off voided my warranty i'm gonna punch them... thanks..
And is it true that some devices are shipped s off by mistake?
Click to expand...
Click to collapse
Yeah its true.. keep in mind your warranty can still be voided by requesting an unlock token from HTCDev
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Yeah its true.. keep in mind your warranty can still be voided by requesting an unlock token from HTCDev
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I know but they don't have any evidences that I used the unlock_code.bin so I think i am on the safe side... At least I hope so...
altimax98 said:
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
why not go son？
Sent from my HTC One using Tapatalk 2
dingnangen said:
why not go son？
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
stovie_steve said:
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
Click to expand...
Click to collapse
hmm.. that's crappy... do you know a thread where this particular problem is mentioned? I searched for it.. but didn't find anything
LibertyMarine said:
hmm.. that's crappy... do you know a thread where this particular problem is mentioned? I searched for it.. but didn't find anything
Click to expand...
Click to collapse
It's happened with myself despite being completely stock and to someone else in an earlier thread today
Only way I could bypass this was by basically starting from hboot 1.44 and then installing an RUU before going s on, then taking the ota s right up to the latest hboot
stovie_steve said:
It's happened with myself despite being completely stock and to someone else in an earlier thread today
Only way I could bypass this was by basically starting from hboot 1.44 and then installing an RUU before going s on, then taking the ota s right up to the latest hboot
Click to expand...
Click to collapse
So this basically means you locked and untampered your phone after installing the RUU? And another question: Did you also flash this stock hboot before installing the RUU?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
But I decided not to go back s on because they won't void my warranty for that and if they say that will void it, I am gonna argue with them until they accept the only fair option: SOFWARE MODIFICATION CAN'T CAUSE ANY HARDWARE DAMAGE except overclocking can melt your phone^^
LibertyMarine said:
So this basically means you locked and untampered your phone after installing the RUU? And another question: Did you also flash this stock hboot before installing the RUU?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
But I decided not to go back s on because they won't void my warranty for that and if they say that will void it, I am gonna argue with them until they accept the only fair option: SOFWARE MODIFICATION CAN'T CAUSE ANY HARDWARE DAMAGE except overclocking can melt your phone^^
Click to expand...
Click to collapse
This is how I did it
http://forum.xda-developers.com/showthread.php?t=2519259
My method was for a carrier branded phone (o2 UK) but this guide can be changed to suit unbranded phones. The problem I had, as well as others, was getting back to s on and once writesecureflag 3 was performed on hboot 1.55 tamper was detected. Guess it may be a patch in latest hboot. I had to go s on with hboot 1.54 or earlier and then upgrade to hboot 1.55 via ota once I was happy everything was stock
stovie_steve said:
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
Click to expand...
Click to collapse
my phone is son unlock with hb1.54 now,i want to go soff using RumRunner ,then flash 4.1 ruu and back to 100% stock(s-on) using revone for warranty,can i get soff Using revone again?
dingnangen said:
my phone is son unlock with hb1.54 now,i want to go soff using RumRunner ,then flash 4.1 ruu and back to 100% stock(s-on) using revone for warranty,can i get soff Using revone again?
Click to expand...
Click to collapse
As long as your using it on a downgraded hboot ie 1.44. Rumrunner will only work on hboot 1.5x
To run the 4.1 RUU you will have to downgrade the hboot or it will give error 155
stovie_steve said:
This is how I did it
http://forum.xda-developers.com/showthread.php?t=2519259
My method was for a carrier branded phone (o2 UK) but this guide can be changed to suit unbranded phones. The problem I had, as well as others, was getting back to s on and once writesecureflag 3 was performed on hboot 1.55 tamper was detected. Guess it may be a patch in latest hboot. I had to go s on with hboot 1.54 or earlier and then upgrade to hboot 1.55 via ota once I was happy everything was stock
Click to expand...
Click to collapse
Sorry that this question seams to be very simple.. but did you go s on with this version of bootloader?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Because I really don't want to risk anything by going s on again..
Or did you go s on again with the 1.54 hboot from the OTA?
LibertyMarine said:
Sorry that this question seams to be very simple.. but did you go s on with this version of bootloader?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Because I really don't want to risk anything by going s on again..
Or did you go s on again with the 1.54 hboot from the OTA?
Click to expand...
Click to collapse
When I ran the RUU after downgrading the hboot I was on android 4.1.2 and hboot 1.44
I restored a nandroid backup then for my o2 carrier. Although the recovery was stock, it wasn't 100% stock for my carrier. I knew this would be fixed with the OTA so that's why I went s on then with hboot 1.54 as EVERYTHING was stock
If you are going to an unbranded model, you can change the CID to run the RUU if you have to, then once completed change the CID back, push revone for locking bootloader, remove tampered etc then when satisfied you can s on again. Just don't s on with hboot 1.55!
Hi guys
i want to send back my phone due to faulty camera. I have to questions:
do i have to back it to stock? I am s-off with custom rom (ARHD), custom recovery etc. If not i wont bother myself.
If they will replace to a new one or reset my current one, what kind of software will I have? Will I be able to s-off and root it? As they probably will install the newest official rom.
cheers,
terragady said:
Hi guys
i want to send back my phone due to faulty camera. I have to questions:
do i have to back it to stock? I am s-off with custom rom (ARHD), custom recovery etc. If not i wont bother myself.
If they will replace to a new one or reset my current one, what kind of software will I have? Will I be able to s-off and root it? As they probably will install the newest official rom.
cheers,
Click to expand...
Click to collapse
Yes you need to return to full stock,, ie locked not relocked, tampered removed stock recovery installed. Can't give an answer if you should be S-On or stay S- Off. Some have reported that warranty was void others have said HTC repaired it with S-Off.
Follow this thread to return to full stock
http://forum.xda-developers.com/showthread.php?t=2541082
Has for OS.. Think I could be potluck to which one you get back.
Sent from my HTC One using XDA Premium 4 mobile app
terragady said:
Hi guys
i want to send back my phone due to faulty camera. I have to questions:
do i have to back it to stock? I am s-off with custom rom (ARHD), custom recovery etc. If not i wont bother myself.
If they will replace to a new one or reset my current one, what kind of software will I have? Will I be able to s-off and root it? As they probably will install the newest official rom.
cheers,
Click to expand...
Click to collapse
1) You will have the exact same software as the one you gave your phone in. The max HTC will do is install the OTA's. NO alterations to the software will be made if you give the phone to them with the correct MID, CID and bootloader condition as it was out of the box
2) Yes, I gave in my phone after RUU'ing it because of the purple tint issue. After I got it back, bootloader unlock, root, S-OFF were perfectly achieved the same way I did initially
3) In some countries, free repair is done even if S-OFF. Others aren't so lucky. I would recommend that u go back S-ON to prevent headaches later. Otherwise, ask any person who has given their phone for warranty repair in your country
4) The person above has given the link to the guide. I trust you know which RUU to flash
raghav kapur said:
1) You will have the exact same software as the one you gave your phone in. The max HTC will do is install the OTA's. NO alterations to the software will be made if you give the phone to them with the correct MID, CID and bootloader condition as it was out of the box
2) Yes, I gave in my phone after RUU'ing it because of the purple tint issue. After I got it back, bootloader unlock, root, S-OFF were perfectly achieved the same way I did initially
3) In some countries, free repair is done even if S-OFF. Others aren't so lucky. I would recommend that u go back S-ON to prevent headaches later. Otherwise, ask any person who has given their phone for warranty repair in your country
4) The person above has given the link to the guide. I trust you know which RUU to flash
Click to expand...
Click to collapse
ok i did it today. I didn't remember my original CID so i put HTC__32, im like 90% that it was this one, sounds familiar
I flashed RUU for Europe for this CID, looks like stock now so its fine
terragady said:
ok i did it today. I didn't remember my original CID so i put HTC__32, im like 90% that it was this one, sounds familiar
I flashed RUU for Europe for this CID, looks like stock now so its fine
Click to expand...
Click to collapse
ok i have one problem, i flashed RUU 1.20.401.1 but now i can not do any OTA updates, its telling me that phone is up to date
I think it depends on your country. I left my phone S-Off and unlocked and they noticed but did not care. Someone in UAE had the opposite experience. What's the law and what are the customs around purchases with minor manufacturer defects in your country?
terragady said:
ok i have one problem, i flashed RUU 1.20.401.1 but now i can not do any OTA updates, its telling me that phone is up to date
Click to expand...
Click to collapse
well, in the guide, it does say: ---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead
nkk71 said:
well, in the guide, it does say: ---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead
Click to expand...
Click to collapse
reflashes 1.28 and its fine now
I am from Germany. Now I have completely stock so I think I dont have to worry about warranty
terragady said:
reflashes 1.28 and its fine now
I am from Germany. Now I have completely stock so I think I dont have to worry about warranty
Click to expand...
Click to collapse
Just check your bootloader. Make sure it says locked not relocked and there is no tampered warning..
Sent from my HTC One using Xparent Skyblue Tapatalk 2
bored_stupid said:
Just check your bootloader. Make sure it says locked not relocked and there is no tampered warning..
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes its locked, s-on etc. Everything should be fine, I already sent the package with phone hope I will get it soon, and hopefully new one!
ok i got my phone back.
Unfortunately its not new
I wrote them that camera has pink effect and USB socket is not working properly, What they replaced is: camera (actually now works good), back cover and now its kinda strange, mat (unpolished) weird in touch and Audio Speaker, i dont know why. Probably they damaged back cover and audio during camera replacement, but they forgot about USB socket.
terragady said:
ok i got my phone back.
Unfortunately its not new
I wrote them that camera has pink effect and USB socket is not working properly, What they replaced is: camera (actually now works good), back cover and now its kinda strange, mat (unpolished) weird in touch and Audio Speaker, i dont know why. Probably they damaged back cover and audio during camera replacement, but they forgot about USB socket.
Click to expand...
Click to collapse
Little ot:
Did you have used htcdev or temproot for the bootloader unlock? I do return here in Italy and I don't now if sent it relocked or use htcdev and set it like locked
I did back to stock tutorial, so there was just LOCKED in bootloader.
terragady said:
I did back to stock tutorial, so there was just LOCKED in bootloader.
Click to expand...
Click to collapse
Ok but in the past, when did you unlock your bootloader for the first time, do you have used htcdev for obtain the token or other tools without htcdev?
.:Moro21:. said:
Ok but in the past, when did you unlock your bootloader for the first time, do you have used htcdev for obtain the token or other tools without htcdev?
Click to expand...
Click to collapse
I did htcdev firstly and then I used some soft from here to obtain S-OFF, actually without HTCdev you can't do S-OFF, can you?
terragady said:
I did htcdev firstly and then I used some soft from here to obtain S-OFF, actually without HTCdev you can't do S-OFF, can you?
Click to expand...
Click to collapse
until a few days ago you could use the temproot method and then s-off with firewater.. but with the new hboot, some user can't unlock!!!