I have a Silver HTC one ,w/ TWRP
w/ s-on, Hboot 1.44, Radio 1.00.20.0315, Sprint Service
I have to send my phone in for repairs to HTC. can someone tell me STEP by STEP how to return my phone to stock. Is there a ROM i can flash or is there a process to follow.
http://www.android.gs/unroot-htc-one-relock-bootloader-restore-stock-jb-4-2-2/
I found this link will this removed the TAMPERED banner and The RED HTC build splash screen?
http://forum.xda-developers.com/showthread.php?t=2508907
Tiltmfc said:
I have a Silver HTC one ,w/ TWRP
w/ s-on, Hboot 1.44, Radio 1.00.20.0315, Sprint Service
I have to send my phone in for repairs to HTC. can someone tell me STEP by STEP how to return my phone to stock. Is there a ROM i can flash or is there a process to follow.
http://www.android.gs/unroot-htc-one-relock-bootloader-restore-stock-jb-4-2-2/
I found this link will this removed the TAMPERED banner and The RED HTC build splash screen?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=
Rumrunner to obtain s-off, then flash the 1.29 RUU
Sent from my HTCONE using Tapatalk
tonyrance said:
http://forum.xda-developers.com/showthread.php?t=
Rumrunner to obtain s-off, then flash the 1.29 RUU
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
No he has to use revone, rumrunner doesnt work on 1.44. However the rest of the process is the same. But he has make sure he only sets S-ON AFTER restoring the ruu, apparently a lot of people make that mistake, according to a guide I read anyway.
Related
Hi, so I got my HTCOne black edition and it had 4.2.2 Sense and I just saw that it has hboot 1.54 and s-on
I want to root but I want to be able to lock my bootloader (make it say locked and not relocked) incase I get into warranty problems...
So I came across this: http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
He shows how to get Sense on Google Edition but on Step two he says that you need to downgrade 1.54 to 1.44 for this to be able to work
He changes the cid to make the bootloader think he can downgrade it (he says)
So can I do the same thing by
1. Unlocking my bootloader, root and then downgrade the hboot?
2. Unlock bootloader, root and turn my phone into google edition --> Downgrade to 1.44 ---> Reinstall Sense RUU or Rom or whatever to get it back?
3. Any other way?
I searched a bit but could not find anything about this so I hope we can keep a nice discussion here for people like me who are stuck on 1.54 with s-on (thanks htc for sending me a new HTCOne, except that it is s-on and on 1.54 and on 4.2.2 :/ )
Thanks in advance
sopaj96 said:
Hi, so I got my HTCOne black edition and it had 4.2.2 Sense and I just saw that it has hboot 1.54 and s-on
I want to root but I want to be able to lock my bootloader (make it say locked and not relocked) incase I get into warranty problems...
So I came across this: http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
He shows how to get Sense on Google Edition but on Step two he says that you need to downgrade 1.54 to 1.44 for this to be able to work
He changes the cid to make the bootloader think he can downgrade it (he says)
So can I do the same thing by
1. Unlocking my bootloader, root and then downgrade the hboot?
2. Unlock bootloader, root and turn my phone into google edition --> Downgrade to 1.44 ---> Reinstall Sense RUU or Rom or whatever to get it back?
3. Any other way?
I searched a bit but could not find anything about this so I hope we can keep a nice discussion here for people like me who are stuck on 1.54 with s-on (thanks htc for sending me a new HTCOne, except that it is s-on and on 1.54 and on 4.2.2 :/ )
Thanks in advance
Click to expand...
Click to collapse
Changing CID (to allow RUUs that are not for your phone) is not possible with S-ON. So that guide requires S-OFF.... S-ON + hboot 1.54 = No S-OFF untill exploit is revealed. Sorry.
Thread for attempts to get S-OFF on hboot 1.54 -> http://forum.xda-developers.com/showthread.php?p=46263968
EDIT:
First comment on the guide you linked to states the following which is correct:
For #1, using your instructions, the CID will not change. it seems that i need to set S-Off....
Click to expand...
Click to collapse
sopaj96 said:
Hi, so I got my HTCOne black edition and it had 4.2.2 Sense and I just saw that it has hboot 1.54 and s-on
I want to root but I want to be able to lock my bootloader (make it say locked and not relocked) incase I get into warranty problems...
So I came across this: http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
He shows how to get Sense on Google Edition but on Step two he says that you need to downgrade 1.54 to 1.44 for this to be able to work
He changes the cid to make the bootloader think he can downgrade it (he says)
So can I do the same thing by
1. Unlocking my bootloader, root and then downgrade the hboot?
2. Unlock bootloader, root and turn my phone into google edition --> Downgrade to 1.44 ---> Reinstall Sense RUU or Rom or whatever to get it back?
3. Any other way?
I searched a bit but could not find anything about this so I hope we can keep a nice discussion here for people like me who are stuck on 1.54 with s-on (thanks htc for sending me a new HTCOne, except that it is s-on and on 1.54 and on 4.2.2 :/ )
Thanks in advance
Click to expand...
Click to collapse
Won't work, you already have to be S-Off to downgrade hboot, the tutorial should have stated that at the beginning. Sorry
TwinAdk said:
Changing CID (to allow RUUs that are not for your phone) is not possible with S-ON. So that guide requires S-OFF.... S-ON + hboot 1.54 = No S-OFF untill exploit is revealed. Sorry.
Thread for attempts to get S-OFF on hboot 1.54 -> http://forum.xda-developers.com/showthread.php?p=46263968
EDIT:
First comment on the guide you linked to states the following which is correct:
Click to expand...
Click to collapse
But... How did he get s-off with a Google Edition phone when he had 1.54? Mu thoughts are that Google Edition has s-off... So maybe if we root and turn our phone to a google edition phone and then do what he does...then put it back on sense?
I want to root so badly lol xd
GPe are s-on. He probably had an s-off device converted to GPe.
Sent from my One using XDA Premium 4 mobile app
CoryTallman said:
GPe are s-on. He probably had an s-off device converted to GPe.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well that sucks if its true :/
Do you think I should root anyway?
As of now I dont have any problems with my phone and by the time it takes for it to break, if it even breaks or defects or something, maybe someone has made some tool or have hacked 1.54... It cant take more than 1 year right?
They're looking for an exploit for hboot 1.55 not 1.54. And it may never come. No one knows till someone finds it. There's always the java card option though.
Sent from my 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!
Hello was hoping for some advice. need to return my phone to stock as selling it to make money for the HTC one max. Currently rooted with s-off using rumrunner it all looks pretty simple. Just want to make sure I get correct ruu.zip or ruu .exe as I want to get my radio kernel and firmware etc back to current stock. I was on 2.24.401.8 when started out with 1.54 hboot. I'm on cid htc_001. Now I'm running ARHD. Custom hboot 1.56 to remove red warning text when I have hopefully found a correct ruu can I flash this over custom hboot to get back to stock or will this brick the phone? Or will I need to flash hboot 1.44 first and which 1? also on 4.06.1540.2 I think it is. Help would be very appreciated. Thanks
Sent from my C6833 using Tapatalk
nathlynn22 said:
Hello was hoping for some advice. need to return my phone to stock as selling it to make money for the HTC one max. Currently rooted with s-off using rumrunner it all looks pretty simple. Just want to make sure I get correct ruu.zip or ruu .exe as I want to get my radio kernel and firmware etc back to current stock. I was on 2.24.401.8 when started out with 1.54 hboot. I'm on cid htc_001. Now I'm running ARHD. Custom hboot 1.56 to remove red warning text when I have hopefully found a correct ruu can I flash this over custom hboot to get back to stock or will this brick the phone? Or will I need to flash hboot 1.44 first and which 1? also on 4.06.1540.2 I think it is. Help would be very appreciated. Thanks
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
You will need to downgrade hboot to 1.44 before running the 1.28.401.7 ruu.exe
check your MID also match the ruu (PN0710000)
make sure you are not using windows 8.1
For more info follow instructions from nkk71's guide linked below.
alray said:
You will need to downgrade hboot to 1.44 before running the 1.28.401.7 ruu.exe
check your MID also match the ruu (PN0710000)
make sure you are not using windows 8.1
For more info follow instructions from nkk71's guide linked below.
Click to expand...
Click to collapse
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
nkk71 said:
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
Click to expand...
Click to collapse
It's cool I used ruu.exe and downgraded my hboot. Now I've got stock phone just can't get s -on says waiting for device
Sent from my C6833 using Tapatalk
Nevermind. Thanks guys looking good
Sent from my C6833 using Tapatalk
nkk71 said:
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
Click to expand...
Click to collapse
good, i'll go read your updated guide! thanks for the info.
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
You will need s-off to reset the bootloader back to locked instead of re-locked
Sent from my HTC One using xda app-developers app
adoboFosho said:
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
Click to expand...
Click to collapse
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
raghav kapur said:
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
Click to expand...
Click to collapse
the instructions on firewater on their site probably doesn't work with what I have atm cant link to the site yet not enough posts..
what is the best course of action I take?
im running latest android not 4.3 with an m7 not m8 and unrooted
i tried temprooting using firewater just to get s-off didn't work since i have newest android
can someone tell me what to do from here? flash 4.3? root again?!
It's really all in the title. I originally went S-OFF with rumrunner, set back to S-ON with the HTC1Guru guide for a charge port warranty repair, now I can't get back to S-Off
Running a rooted stock sense 5.5 android 4.3 WWE ROM, from HTC1Guru, unlocked bootloader, HBOOT 1.56. Tried Rumrunner, moonshiner, revone, firewater, all failed! Is there any way to get me back to S-Off?
It's an unlocked One BTW.
Another weird thing is that in HBOOT, my OS line shows up blank, no numbers.
j.gaynon said:
It's really all in the title. I originally went S-OFF with rumrunner, set back to S-ON with the HTC1Guru guide for a charge port warranty repair, now I can't get back to S-Off
Running a rooted stock sense 5.5 android 4.3 WWE ROM, from HTC1Guru, unlocked bootloader, HBOOT 1.56. Tried Rumrunner, moonshiner, revone, firewater, all failed! Is there any way to get me back to S-Off?
It's an unlocked One BTW.
Another weird thing is that in HBOOT, my OS line shows up blank, no numbers.
Click to expand...
Click to collapse
OS line showing up blank isn't quite an issue. However, 1.56 S-OFF is luck. Some succeed, some don't.
If it cant be S-OFF'ed on ARHD 31.6, im afraid you may have to wait a little longer for a solid exploit.
raghav kapur said:
OS line showing up blank isn't quite an issue. However, 1.56 S-OFF is luck. Some succeed, some don't.
If it cant be S-OFF'ed on ARHD 31.6, im afraid you may have to wait a little longer for a solid exploit.
Click to expand...
Click to collapse
Damn. You sure it's not possible?
j.gaynon said:
Damn. You sure it's not possible?
Click to expand...
Click to collapse
What is the exact error message in Firewater?
j.gaynon said:
Damn. You sure it's not possible?
Click to expand...
Click to collapse
you can send your phone to fonefunshop.com and they will s-off it using a java card.
raghav kapur said:
What is the exact error message in Firewater?
Click to expand...
Click to collapse
I get the whelp message, so there's no point following up on that.