Quick question, once one gains s-off would there be any reason one might need to turn it back on?
TIA
dug13 said:
Quick question, once one gains s-off would there be any reason one might need to turn it back on?
TIA
Click to expand...
Click to collapse
Only reason I would is if your sending it in for service/exchange.
Sent from my lunar powered Inverted EclipticONE using Tapatalk 2
JoeNeckbone said:
Only reason I would is if your sending it in for service/exchange.
Sent from my lunar powered Inverted EclipticONE using Tapatalk 2
Click to expand...
Click to collapse
I have s off, will anything automatically return my phone to s On status? Like doing a RUU, installing ROMs ota updates?
Will I be required to unlock the boot loader if I return to stock, or does s off ensure I won't need to?
TIA
dug13 said:
I have s off, will anything automatically return my phone to s On status? Like doing a RUU, installing ROMs ota updates?
Will I be required to unlock the boot loader if I return to stock, or does s off ensure I won't need to?
TIA
Click to expand...
Click to collapse
Once your s-off it stays that way. RUU does reinstall stock hboot & stock recovery however s-off remains. Most people that do s-off will never turn it back on unless the phone is going in for warranty service.
Sim-X said:
Once your s-off it stays that way. RUU does reinstall stock hboot & stock recovery however s-off remains. Most people that do s-off will never turn it back on unless the phone is going in for warranty service.
Click to expand...
Click to collapse
Thanks, Will RUU require me to unlock the bootloader with S off?
dug13 said:
Thanks, Will RUU require me to unlock the bootloader with S off?
Click to expand...
Click to collapse
If I remember correctly you may have to relock your bootloader to run an RUU. Think of it this way, once your s-off you can do whatever you want to do. Upgrade/Downgrade hboots, splash screens, radios, run any ruu you want it's way better. As long as it shows s-off your good to go & it shouldn't ever come back on unless you turn it back on. Although I heard it is possible that HTC may be able to trigger an s-on with say an OTA update but I have never heard of that actually happening on any model HTC that I'm aware of.
Sim-X said:
If I remember correctly you may have to relock your bootloader to run an RUU. Think of it this way, once your s-off you can do whatever you want to do. Upgrade/Downgrade hboots, splash screens, radios, run any ruu you want it's way better. As long as it shows s-off your good to go & it shouldn't ever come back on unless you turn it back on. Although I heard it is possible that HTC may be able to trigger an s-on with say an OTA update but I have never heard of that actually happening on any model HTC that I'm aware of.
Click to expand...
Click to collapse
Thanks, so S on, S off doesn't matter, you will still have to relock the boot loader to RUU, correct?
dug13 said:
Thanks, so S on, S off doesn't matter, you will still have to relock the boot loader to RUU, correct?
Click to expand...
Click to collapse
I have not ran an RUU on my ONE yet, but I have run MANY RUU's on other phones, you do NOT need to relock bootloader to run the RUU, you must be S-OFF to run an older RUU or to downgrade, after the RUU, your bootloader will be LOCKED but still remain S-OFF, this is how it worked for me on every other phone I have done, I can't imagine why the ONE would be any different....
Related
I was just wondering, I have the HTC ONE/ M7 and I was trying to root it but was never successful. I unlocked it with the HTCDev website and installed GOO on my phone but thats about as far as I got. Now my phone shows **TAMPERED** and **UNLOCKED** in the HBOOT menu, I was just curious as to how I would get those to go away.
THANKS!
I believe you have to wait for s-off so you can downgrade hboot to remove that message.
Flashing back the stock firmware (RUU) will remove the tampered but it will always say relocked if you locked the bootloader again.
What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
Sent from my HTC One using xda app-developers app
Tampered can be removed when you flash the official RUU.
Relocked cant be as of now. And I have no hopes for it to happen in device's life cycle as well.
So how would I flash it? Is there a general way or is it device specific?
Sent from my HTC One using xda app-developers app
Take a look through this:
http://forum.xda-developers.com/showthread.php?t=2265618
When you rooted your phone it added tampered and unlocked in bootloader menu.
If you want to take them out you will have to unroot your phone or wait for s-off (it will fully unlock the phone)
I didn't have the tampered message on my rooted OneX,it must be something new as well as the red warning in booting the phone that it's a dev phone that must not be sold
There is a thread with RUU archive for each device. Check for specific RUU for your specific carrier make or model.
But if you install RUU you will have phone that is as good as stock phone. You will lose root and will have to re-root it.
Dont bother with it unless you have to go back to factory condition.
There are also zipped versions of stock ROMs available so you can try those if you have CWM or TWRP installed successfully.
You dont really need to remove that tampered / unlocked status. It does not hinder your phone in any way. You have already lost your warranty and even if you relock your bootloader and remove Tampered message by flashing factory RUU, your phone will still show RELOCKED message. So point going back unless as I said you must have factory condition phone.
Hi~!
So does this mean the factory will always know that our phones are rooted with S ON?
TrueYears said:
Hi~!
So does this mean the factory will always know that our phones are rooted with S ON?
Click to expand...
Click to collapse
Yes HTC will know for sure the phone has been tampered with and unless s-off is achieved for the masses which does not involve taking the phone apart then it will always say tampered, unlocked, relocked.
Oh, okay, thank you, my phone has vibrating problems, with the intensity, in some hits, the vibrating just keeps going slowly fading in. I read somewhere that 1.29 fixes this but its isnt out around my region yet and I dont want to flash this 1.29 stock rom to find out its a hardware issue and lose my warranty
Spacky03 said:
What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Security-Off if what it officially means. Means you can write to the bootloader and mod things
Hi guys,
just one quick question. I have my phone stuck in S-ON after upgrading into new firmware (HBOOT 1.54). It is clear that revone (the one I used to S-OFF the first time) is currently unable to S-OFF my phone right now. Therefore now I'm considering S-OFF through HTC Dev. Will HTC Dev S-OFF work with 1.54 HBOOT?
Another question would be, apart from getting wiped and lose some application, what disadvantage will S-OFF through HTC Dev brings?
Thanks for the help
you can unlock the bootloader and install custom roms/kernels but no s-off, which might be a problem if you need to send your phone to warranty because they could deny warranty on the re/unlocked status of the bootloader.
flamechamp said:
Hi guys,
just one quick question. I have my phone stuck in S-ON after upgrading into new firmware (HBOOT 1.54). It is clear that revone (the one I used to S-OFF the first time) is currently unable to S-OFF my phone right now. Therefore now I'm considering S-OFF through HTC Dev. Will HTC Dev S-OFF work with 1.54 HBOOT?
Another question would be, apart from getting wiped and lose some application, what disadvantage will S-OFF through HTC Dev brings?
Thanks for the help
Click to expand...
Click to collapse
Why did you s-on in the first place? You can't s-off, you're stuck for now. HTC Dev can only unlock your bootloader.
redbull123 said:
Why did you s-on in the first place? You can't s-off, you're stuck for now. HTC Dev can only unlock your bootloader.
Click to expand...
Click to collapse
I didn't S-ON it on purpose. It went S-ON automatically after firmware update and few resets. I have no slightest idea why it went S-ON. So... it seems I'm doomed for now...
godutch said:
you can unlock the bootloader and install custom roms/kernels but no s-off, which might be a problem if you need to send your phone to warranty because they could deny warranty on the re/unlocked status of the bootloader.
Click to expand...
Click to collapse
how am I suppose to install custom ROMs when I'm S-On now? I can't even flash custom recovery right?
flamechamp said:
how am I suppose to install custom ROMs when I'm S-On now? I can't even flash custom recovery right?
Click to expand...
Click to collapse
with htc dev unlock bootloader method you can, you dont need s-off to flash custom recovery and roms.
I know that could be somewhat confusing, but seems like you did not read enough
flamechamp said:
Hi guys,
just one quick question. I have my phone stuck in S-ON after upgrading into new firmware (HBOOT 1.54). It is clear that revone (the one I used to S-OFF the first time) is currently unable to S-OFF my phone right now. Therefore now I'm considering S-OFF through HTC Dev. Will HTC Dev S-OFF work with 1.54 HBOOT?
Another question would be, apart from getting wiped and lose some application, what disadvantage will S-OFF through HTC Dev brings?
Thanks for the help
Click to expand...
Click to collapse
Yeah the word is devs are workingbpn that but I heard still long time away
SLver said:
with htc dev unlock bootloader method you can, you dont need s-off to flash custom recovery and roms.
I know that could be somewhat confusing, but seems like you did not read enough
Click to expand...
Click to collapse
Any links maybe? Because as far as I know I need custom recovery to flash ROMs and to install custom recovery S-OFF is needed.
99piotrek said:
Yeah the word is devs are workingbpn that but I heard still long time away
Click to expand...
Click to collapse
I do hope the REVOLUTIONARY team finishes their work quickly...
flamechamp said:
Any links maybe? Because as far as I know I need custom recovery to flash ROMs and to install custom recovery S-OFF is needed.
Click to expand...
Click to collapse
With the HTC ONE toolkit you can unlock your bootloader and flash a custom recovery.
Very easy. I'm in the same situation at this moment. hboot 1.54.
I also got a question about this.
When I'm in the toolkit and I want to use the mainver error fix I always get Device not Found. Is this also because i'm on hboot 1.54 or maybe not a correct setting somwhere (adb?).
haenraets said:
With the HTC ONE toolkit you can unlock your bootloader and flash a custom recovery.
Very easy. I'm in the same situation at this moment. hboot 1.54.
I also got a question about this.
When I'm in the toolkit and I want to use the mainver error fix I always get Device not Found. Is this also because i'm on hboot 1.54 or maybe not a correct setting somwhere (adb?).
Click to expand...
Click to collapse
Oh but I must unlock my RELOCKED bootloader to install the recovery right?
flamechamp said:
Oh but I must unlock my RELOCKED bootloader to install the recovery right?
Click to expand...
Click to collapse
Yes... That is correct and once you unlock it you can use the all in one kit to flash a recovery and then you can flash the rom of your choice
Sent from my ViperOne
flamechamp said:
Oh but I must unlock my RELOCKED bootloader to install the recovery right?
Click to expand...
Click to collapse
Yes, and you can do this with the toolkit.
leohdz148 said:
Yes... That is correct and once you unlock it you can use the all in one kit to flash a recovery and then you can flash the rom of your choice
Sent from my ViperOne
Click to expand...
Click to collapse
haenraets said:
Yes, and you can do this with the toolkit.
Click to expand...
Click to collapse
But through the toolkit, the unlocking process will use the HTC Dev method which erases the phone's internal memory and some part which contains some apps right? Any other cons which shouldn't I unlock through HTC Dev?
Here it is but be careful
flamechamp said:
Any links maybe? Because as far as I know I need custom recovery to flash ROMs and to install custom recovery S-OFF is needed.
Click to expand...
Click to collapse
Go there, register an account
http://www.htcdev.com/
after that click on the "developer center" button and right in the middle you will find a "unlock bootloader" button
click on it, follow instructions, but make sure you have a full backup of your storage cause it will be erased
S-OFF is a security flag that gives you permission to "play" with organic partitions of the devices system in a way
you don't need it for having custom recovery, after you unlock you can flash a recovery the exact same way you did with S-OFF or restore a backup you did before reverting to complete stock
S-OFF for most users is only a solution to not losing warranty after unlocking as unlocking actually voids your software warranty and in a way the hardware warranty as HTC can claim that the unofficial software you used actually damaged the device.
If I helped to make you understand in any way I am glad but please if you don't understand what these procedures do or how they work in a general sense it's better not to use/perform them, if you are in any way like me who spent the better part of a salary to buy this phone it would be a shame wasting all that money bricking it out of ignorance, if not, it's still a shame.
flamechamp said:
But through the toolkit, the unlocking process will use the HTC Dev method which erases the phone's internal memory and some part which contains some apps right? Any other cons which shouldn't I unlock through HTC Dev?
Click to expand...
Click to collapse
Yea it wipes everything so I suggest you back up anything important to you before you unlock... And there aren't any other cons except the fact that it will wipe EVERYTHING (apps, contacts synced with phone, music, pictures, etc.), thats the only con to it
Sent from my ViperOne
I think there is some confusion here for the OP.
First, S-off and unlocking your bootloader are 2 completely different things. To install custom recoveries, and therefore custom Roms and kernels, you need an unlocked bootloader (I am not sue what all the talk of relocking was about). The only way for you to unlock at this point is with HTCdev, and this will wipe your device unfortunately. Their are guides to unlocking and rooting your phone in this very forum
dgtiii said:
I think there is some confusion here for the OP.
First, S-off and unlocking your bootloader are 2 completely different things. To install custom recoveries, and therefore custom Roms and kernels, you need an unlocked bootloader (I am not sue what all the talk of relocking was about). The only way for you to unlock at this point is with HTCdev, and this will wipe your device unfortunately. Their are guides to unlocking and rooting your phone in this very forum
Click to expand...
Click to collapse
Yes, I got things mixed up. I got so frustrated with S-ON such that I forgot that the real problem is the RELOCKED status of my phone. Thanks for reminding me
But i do need S-OFF to flash splash screen right?
flamechamp said:
Yes, I got things mixed up. I got so frustrated with S-ON such that I forgot that the real problem is the RELOCKED status of my phone. Thanks for reminding me
Click to expand...
Click to collapse
No problem, glad to help.....
flamechamp said:
Yes, I got things mixed up. I got so frustrated with S-ON such that I forgot that the real problem is the RELOCKED status of my phone. Thanks for reminding me
Click to expand...
Click to collapse
??? There was no talk from anyone about 'relocking'. You were told about 5 times you had to unlock your bootloader.
Sent from my HTC One using xda premium 4
redbull123 said:
??? There was no talk from anyone about 'relocking'. You were told about 5 times you had to unlock your bootloader.
Sent from my HTC One using xda premium 4
Click to expand...
Click to collapse
no, I got it relocked to update my firmware last time. But can't have it unlocked now. But now I know that using HTC Dev method, it will be solved.
But I do need S-OFF to flash splash screen right?
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!
Alright, I've been through thread after thread and plenty of pages found on google.
Some say to Lock the bootloader BEFORE using the RUU and some say to lock it AFTER or you'll brick the phone?
I've got a T-mobile Variant of the HTC one M7 It's rooted, SuperCID and obviously the bootloader is unlocked.... I think it's on 1.55, not exactly sure, I'm currently backing up all my data.
I've got the new 5.14.531.1 RUU straight from the HTC website.
Since it's a Tmobile rom, I'm guessing resetting the CID to T-MOB010 before installing would be a good idea?
And what of the bootloader? running the RUU should install the new Hboot correct? from there I would just need to relock it or am I not understanding this?
~Out of all my phones I've NEVER returned one to stock, so this is all kinda new to me.
Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.
Click to expand...
Click to collapse
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
nkk71 said:
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
Click to expand...
Click to collapse
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Vonrottes said:
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Click to expand...
Click to collapse
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
nkk71 said:
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
Click to expand...
Click to collapse
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Vonrottes said:
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Click to expand...
Click to collapse
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
nkk71 said:
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
Click to expand...
Click to collapse
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Vonrottes said:
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Click to expand...
Click to collapse
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
nkk71 said:
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
Click to expand...
Click to collapse
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Vonrottes said:
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Click to expand...
Click to collapse
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
nkk71 said:
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
Click to expand...
Click to collapse
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Is it just the 1.55+ Hboot that throws the tampered when locked?
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Can't do the 1.44, My PC is running 8.1 and I've not played with Linux since 2009
Vonrottes said:
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Click to expand...
Click to collapse
In that case, I recommend you use a 1.xx RUU
(check my guide in my signature)
Vonrottes said:
Is it just the 1.55+ Hboot that throws the tampered when locked?
Click to expand...
Click to collapse
Unknown when/what exactly triggers the "tamper detected" or some people have been able to S-On and not get that, others have not, so I can't say if it will happen or not. but if you wanna play it safe, go for 1.xx ruu.
Vonrottes said:
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Click to expand...
Click to collapse
brick alert: Definitely NOT, that is a custom HBOOT, if you actually manage to S-On it with an unsigned hboot, you'll have an paperweight on your hands!! stay away from that.
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
rh92 said:
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
Click to expand...
Click to collapse
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Seanie280672 said:
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Click to expand...
Click to collapse
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
rh92 said:
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
Click to expand...
Click to collapse
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Seanie280672 said:
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Click to expand...
Click to collapse
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
rh92 said:
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
Click to expand...
Click to collapse
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Seanie280672 said:
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Click to expand...
Click to collapse
After installing the RUU how would I get s-on?
Thanks
rh92 said:
After installing the RUU how would I get s-on?
Thanks
Click to expand...
Click to collapse
don't s-on, never s-on simple as that.
Seanie280672 said:
don't s-on, never s-on simple as that.
Click to expand...
Click to collapse
Ok, I was just asking in case I needed to send my phone in for repair in the future.
rh92 said:
Ok, I was just asking in case I needed to send my phone in for repair in the future.
Click to expand...
Click to collapse
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Seanie280672 said:
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Click to expand...
Click to collapse
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
rh92 said:
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
Click to expand...
Click to collapse
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Seanie280672 said:
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
And after installing this RUU I can just download Sense 6 via OTA.
rh92 said:
And after installing this RUU I can just download Sense 6 via OTA.
Click to expand...
Click to collapse
yes, just accept the ota's one at a time.
Seanie280672 said:
yes, just accept the ota's one at a time.
Click to expand...
Click to collapse
Thanks for your help
I have an PN07200, how can I get sense 6, which will be the best RUU and CID?.... Thanks!
Enviado desde mi HTC One X+ mediante Tapatalk
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
gwaitsi said:
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
Click to expand...
Click to collapse
yup, change your cid to its original one, and find your service providers RUU and flash it.