Can I go s-on with the latest 3.62 firmware or do I need to go back to 2.24.401.1 first?
Better one more stupid question then a bricked phone.Do I need s-on to send it to repairing the camera?
jaypeg123 said:
Can I go s-on with the latest 3.62 firmware or do I need to go back to 2.24.401.1 first?
Better one more stupid question then a bricked phone.Do I need s-on to send it to repairing the camera?
Click to expand...
Click to collapse
Nope. Just lock your bootloader using revone (it just shows the locked tag) and remove Tampered flag, you won't lose any data (I used Hasoon2000 toolkit for revone). This makes the phone look like it was bought that way.
Besides HTC doesn't pay so much attention to S-OFF, it's just the unlocked bootloader and tampered flag that may void your warranty
Once you S-OFF, I don't see a reason why you will S-ON again.
HussainQ said:
Nope. Just lock your bootloader using revone (it just shows the locked tag) and remove Tampered flag, you won't lose any data (I used Hasoon2000 toolkit for revone). This makes the phone look like it was bought that way.
Besides HTC doesn't pay so much attention to S-OFF, it's just the unlocked bootloader and tampered flag that may void your warranty
Once you S-OFF, I don't see a reason why you will S-ON again.
Click to expand...
Click to collapse
Ok thank's I have read about people sending it in with s.off and get it s-on in return. But do you know the drill about the s-on, Is it nessesery to have the original 2.24.401 installed to get it right. I did update it OTA so It is 100% now, just forgot about the s-off.
jaypeg123 said:
Ok thank's I have read about people sending it in with s.off and get it s-on in return. But do you know the drill about the s-on, Is it necessary to have the original 2.24.401 installed to get it right. I did update it OTA so It is 100% now, just forgot about the s-off.
Click to expand...
Click to collapse
I don't really know if they S-ON the device or not. OTA is fine since it is official. Just in-case, I would check rumrunner S-Off compatibility with your firmware. And check your HBOOT version as well.
Related
I need to return my One for warranty purposes (I am in the Netherlands). I am wondering if I should leave my device s-off or s-on it because I am sure I will receive my One back with stocj 2.24.401.1 firmware and hboot 1.54, which isn't s-offable as easily or just lock the bootloader and leave it s-off?
godutch said:
I need to return my One for warranty purposes (I am in the Netherlands). I am wondering if I should leave my device s-off or s-on it because I am sure I will receive my One back with stocj 2.24.401.1 firmware and hboot 1.54, which isn't s-offable as easily or just lock the bootloader and leave it s-off?
Click to expand...
Click to collapse
It depends on what repair you need doing... if it's a mainboard replacement then they're going to flash new anyway.... they may reflash anyway.
If you leave it s-off they could refuse a warranty claim and either charge you for the repair or return it unrepaired unless you can successfully argue that it was like that when you got it.... I think I've seen somewhere that a few s-off devices made it into the supply chain.
Not an easy decision... I think on balance if it was me then I'd relock and s-on. You can still flash roms when returned and hopefully the revone team will find a way to s-off again.
http://forum.xda-developers.com/showthread.php?t=2358738
This guide will help you
Sent from my HTC One™
godutch said:
I need to return my One for warranty purposes (I am in the Netherlands). I am wondering if I should leave my device s-off or s-on it because I am sure I will receive my One back with stocj 2.24.401.1 firmware and hboot 1.54, which isn't s-offable as easily or just lock the bootloader and leave it s-off?
Click to expand...
Click to collapse
Being S-Off could potentially invalidate your warranty. It's all up to you if you want to risk being charged for any repairs but if I wanted to return mine and not get charged, I would be erasing any trace that I'd modified anything ... I'd rather not have S-Off, for a while maybe, than get lumped with a bill for repairs because my warranty was void.
If you decide to return to stock and wipe the "Tampered" flag, return to S-On etc, there are guides on here I believe.
rider5512 said:
It depends on what repair you need doing... if it's a mainboard replacement then they're going to flash new anyway.... they may reflash anyway.
If you leave it s-off they could refuse a warranty claim and either charge you for the repair or return it unrepaired unless you can successfully argue that it was like that when you got it.... I think I've seen somewhere that a few s-off devices made it into the supply chain.
Not an easy decision... I think on balance if it was me then I'd relock and s-on. You can still flash roms when returned and hopefully the revone team will find a way to s-off again.
Click to expand...
Click to collapse
I decided to send it it s-off locked, because we can only hope revolutionary will be able to gain s-off on hboot 1.54, hopefully they will not notice it. Yesterday there was an announced that HTC unjustifiably denied warranty to people with unlocked bootloaders.
I had decided to send in my device s-off but with locked bootloader and on the repair tracker website I can see that they replaced a part apparently under warranty. I hope I'll get my device back s-off and repaired....
Ok so i have searched but unable to find an answer to my question.
I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.
So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.
As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
broli-zn said:
Ok so i have searched but unable to find an answer to my question.
I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.
So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.
As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
Click to expand...
Click to collapse
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.
Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)
BTW purple camera is just software whitebalance problem not a hardware problem
You just need to downgradethe firmware. It contains the hboot.
But as @godutch said, it's not necessary.
Sent from my One using XDA Premium 4 mobile app
Ok cool, thanks guys, so I just need a flash a firmware zip containing 1.44 Hboot and im good to go?
Basically i just want to get rid of the tampered flag.
Iv done the 4.3 upgrades with supposedly fix the camera but its made no effect on mine :crying: so the only other option I have to try and get them to change the camera module.
Thanks again guys. Much appreciated. You will get a thanks each
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.
don't do stupid thing's
i removed tampared flag with revone -t
criszz said:
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.
don't do stupid thing's
i removed tampared flag with revone -t
Click to expand...
Click to collapse
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
broli-zn said:
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
Click to expand...
Click to collapse
it does but you need to be s-off and rooted for it to work but you don't have to do what you are trying to do and you will regret it later....
just try with 1.54 , multiple times
hboot 1.55
godutch said:
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.
Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)
BTW purple camera is just software whitebalance problem not a hardware problem
Click to expand...
Click to collapse
I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
amauryaa said:
I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
Click to expand...
Click to collapse
not recommended, as far as i've seen, going from s-off to s-on (on 100% stock everything), after a few reboots, has a high chance of resulting in "tamper detected - rebooting" and the TAMPERED sign is back.
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!
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Your good
Ali812 said:
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Click to expand...
Click to collapse
If you have changed your CID back to your carrier specific code you should be OK.
However, with the 4.4 update, there have been a few issues with the Bootloader not unlocking again, if you are sending your phone back under warranty for repair or replacement then your good to S-On, if you just want to set S-on for the hell of it (like me) I would hold fire for now.
Its will be your only remaining access to unlock the phone in one way or another.
Ali812 said:
I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
Click to expand...
Click to collapse
Like I said, no bricks involved, but read below too.
zeushacker said:
if you are sending your phone back under warranty for repair or replacement then your good to S-On
Click to expand...
Click to collapse
if he tries to go s-off to s-on on hboot 1.55, then there is a high probability, that after a few reboots "tamper detected - rebooting" -> and the TAMPERED sign is back.
I wrote the guide in a specific order 1, then 2, then 3, etc, because of that reason.
If the OP wants to give it a shot, he can go ahead, maybe the "tamper detected" won't happen; if it does, he will have to s-off using rumrunner, and start the procedure again.
s-on is not needed on waranty, there are always some devices shiped from factory with s-off. my advice is to keep s-off.
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
You can go S On again any time
He advised you should not make it S On
because keep your SOff is beneficial
your phone is GPE so that's had firmware problem after 1.55 locking Bootloader it cant be unlocked if you are on S On that time
if you keep S Off you can Unlock your phone easily
as you know 1st time you need Unlock Bootloader then you make S Off but if you update Hboot then Lock Bootloader then S On its quiet hard to make it S Off again and using root custom Roms etc
IF YOU NOT UNDERSTAND ANSWER DONT WRITE A NEW THREAD ASK AGAIN IN SAME THREAD WE WILL HELP YOU THERE
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
clsA said:
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
Click to expand...
Click to collapse
OK just to clarify - it originally wasn't a GPE. I converted it to GPE, and now I converted it back to stock (incl HBOOT, recovery etc.). Btw, in the post I mistakenly asked if it meant I could never go S-ON again. What I meant to ask was if I couldn't get S-OFF again!
But you say I have to pay to get S-OFF again. Is that because Sunshine is the only way to get S-OFF with HBOOT >= 1.57? Any chance that a free tool will come out that works as well?
Thanks
Moderator Information,
I will keep this thread open as you are getting help on it, but in future can you please keep to one thread per topic.
Thanks.