Will the new HTC One OTA update lock the Boot-loader on my Phone? I haven't Rooted, or ROM'd my phone yet, but i'm sure I will be soon. I just don't want this OTA update messing with my ability to MOD the phone in the future. Any help would be much appreciated.
Gracias
They may close the s–off exploit. Right now there is no root exploit necessary, just unlock via htcdev. Unless HTC starts blocking the One (unlikely at this point IMO), you don't need to worry about losing the ability to root and mod.
But if you think you'll want to s-off, do it now.
Sent from my Nexus 7 using Tapatalk HD
Wasn't the revone s-off available for every version currently available? So I think if you updated now you'd be fine.
Even if you couldn't get s-off anymore you'd still have official unlock, with which you can flash roms, kernels and mods. Only things you can't with S-on are getting rid of red text on boot, changing splash, getting supercid, and showing *** locked *** instead of *** relocked *** for warranty purposes
sent from my HTC One using Tapatalk 4 (VIP)
Could you clarify S on & off? I've flashed my galaxy s tablet and S2 plenty of times but I'm new to HTC.
S-on is security On,
S-off security off
When you buy the device, it's s-on but we already have exploits to get s-off.
We already explained what you can do with both ;p
sent from my HTC One using Tapatalk 4 (VIP)
Related
Hi everyone,
I have been using android for a couple of years now but first reasontly I got an interest for modifying the software.
After reading numerous of hours on the forums I still have´nt found a thread giving me all the answers for the bootloader setup and what do the different statements mean for you and your phone.
Ex. my One´s bootloader says following:
TAMPERED - Is this good or bad?
UNLOCKED - Why has it not gone back to locked after I flashed a custom ROM and why is S-ON back again.
S-ON - Any danger by keeping this S-OFF all the time? Before I flashed I believe it said "S-ON RL" Now it says S-ON RH?
HBOOT - Any good reasons to mess with this?
RADIO - Same question as above.
xtra:
OpenDSP-v26.120.276.0202 - Whats this?`
eMMC-boot - Whats this?
The date written is the date it was flashed by the vendor?
Thanks for any answers and I hope someone can help me clear my head!
Groovi80 said:
Hi everyone,
I have been using android for a couple of years now but first reasontly I got an interest for modifying the software.
After reading numerous of hours on the forums I still have´nt found a thread giving me all the answers for the bootloader setup and what do the different statements mean for you and your phone.
Ex. my One´s bootloader says following:
TAMPERED - Is this good or bad?
UNLOCKED - Why has it not gone back to locked after I flashed a custom ROM and why is S-ON back again.
S-ON - Any danger by keeping this S-OFF all the time? Before I flashed I believe it said "S-ON RL" Now it says S-ON RH?
HBOOT - Any good reasons to mess with this?
RADIO - Same question as above.
xtra:
OpenDSP-v26.120.276.0202 - Whats this?`
eMMC-boot - Whats this?
The date written is the date it was flashed by the vendor?
Thanks for any answers and I hope someone can help me clear my head!
Click to expand...
Click to collapse
Tampered means you have unsigned software running on your device
Unlocked means you unlocked you bootloader and won't change back until you relock it, and s-on will stay s-on unless you s-off your device
Stay s-on if you don't know the benefits of s-off, it increases your chance of bricking the device
Hboot-you couldn't mess with it if you wanted without s-off, don't mess with it
Radio-It's just best to stay with your stock radio firmware
Those others are just information about the device. Not really sure. These are things you need not worry about, just keep on flashing roms and you will be fine.
Sent from my HTC One using Tapatalk 4
superchilpil said:
Tampered means you have unsigned software running on your device
Unlocked means you unlocked you bootloader and won't change back until you relock it, and s-on will stay s-on unless you s-off your device
Stay s-on if you don't know the benefits of s-off, it increases your chance of bricking the device
Hboot-you couldn't mess with it if you wanted without s-off, don't mess with it
Radio-It's just best to stay with your stock radio firmware
Those others are just information about the device. Not really sure. These are things you need not worry about, just keep on flashing roms and you will be fine.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the fast reply Superchillpill.
I am using Trickdroid ROM, so this has to be signed by who in order to remove the TAMPERED from my phone?
Is there any point relocking the bootloader?
And do I not need to S-OFF again in order to flash another custom ROM?
Groovi80 said:
Thanks for the fast reply Superchillpill.
I am using Trickdroid ROM, so this has to be signed by who in order to remove the TAMPERED from my phone?
Is there any point relocking the bootloader?
And do I not need to S-OFF again in order to flash another custom ROM?
Click to expand...
Click to collapse
By HTC, the tampered isn't going to go away basically. Unless you s-off your device
No there isn't any point, you need an unlocked bootloader to flash custom roms.
S-off is not needed with an unlocked bootloader
Sent from my HTC One using Tapatalk 4
eMMC-boot, if I'm not mistaken, means the phone has booted from its onboard system rather than fastboot boot mode. This is something you don't need to worry about unless you're a developer or advanced user.
Open DSP is the digital signal processing framework. Again, nothing you need to worry about unless you're a dev.
Okay, so here goes...
A friend of a friend has a AT&T 64GB HTC One (in silver, if anyone cares...)
I, being the phone guru in the eastern parts of the GTA in Ontario (Yes, I am a Canadian, )
was contacted earlier this week to solve a rather confusing issue to which I find myself rather dumbfounded.
PROBLEM: Phone-owner rooted, unlocked the bootloader and s-off'ed using RevOne (before 1.54 hboot as not currently possible as of today). He attempted a Google Edition conversion with success or so he thought, now the phone works fine except for any carrier based service of any kind, sim is detected but, no service of any kind works. During the conversion he re-locked bootloader, flipped s-off to s-on and unrooted. Root has been re-achieved, and I'm looking into HBOOT version for s-off and the ability to re-unlock bootloader. TWRP is the currently installed recovery, when a sense-based rom is installed, it says sim is locked. I'm quite adept at android everything and this kind of stumps me and is my first take at HTC One development.
Any help greatly appreciated, thanks!
UPDATE: HBOOT is 1.54 and is S-ON
I don't have a solution but I remember reading on XDA that you will screw up your phone if you switch s-off to s-on after doing the conversion.
Sent from my HTC One using xda app-developers app
?
austriak said:
I don't have a solution but I remember reading on XDA that you will screw up your phone if you switch s-off to s-on after doing the conversion.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Any ideas on where you read this or if anyone knows, I'm eager to know as I was offered to buy the dilema-ridden HTC One.
Thanks
Sounds like he screwed up his phone like some others did who were not careful enough about the GE conversion. What he did was input a conflicting MID/CID then locked that bad configuration down.
From what I've heard, installing a 4.3 rom may solve the issue. You can't currently s-off because the 1.54 hboot closed the exploit.
You could be buying an expensive mp3 player, so be careful.
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
Hi all,
As the title suggests I need to get my HTC One back to S-On to send it back for repair, as I'm from Australia there is no RUU available for my Carrier but I have flashed back to stock using a Guru Nandroid, currently it's Bootloader is locked it's CID is OPTUS001 (default) and HBoot 1.55 S-Off which I need to get back to on and it's had it's latest OTA installed.
Earlier today I did achieve S-Off and locked but ended up with the tamper flag above locked which obviously couldn't be returned like that.
At the moment I am wondering if I need to downgrade just HBoot to 1.44 so I can S-On again but I'm worried it will show tampered again after I S-On like it did before, now in further if this is the only way to do it how can I get HBoot 1.55 back in after I S-On, I haven't found any firmware downloads out there at all specific to my device.
Thanks in advance for any help.
Just leave it s off its not a problem. As long as tampered is gone and boot loader is locked that is fine
Sent from my HTC One using XDA Premium 4 mobile app
Ok thank you for the reply, I have tried so many different things today and to be honest I'm surprised it's not bricked doing some of the things I have done, cheers.
Sent from my HTC One using Tapatalk Pro
Going from s off to s on is actually one of the easiest ways to brick your phone if your not careful. There really is no need. Some phones actually come out of the factory s off. And with warranty repairs I've heard of plenty of people with custom roms and unlocked bootloaders get it fixed no problem. Yours sounds fine
Sent from my HTC One using XDA Premium 4 mobile app
Sojourner353 said:
Hi all,
As the title suggests I need to get my HTC One back to S-On to send it back for repair, as I'm from Australia there is no RUU available for my Carrier but I have flashed back to stock using a Guru Nandroid, currently it's Bootloader is locked it's CID is OPTUS001 (default) and HBoot 1.55 S-Off which I need to get back to on and it's had it's latest OTA installed.
Earlier today I did achieve S-Off and locked but ended up with the tamper flag above locked which obviously couldn't be returned like that.
At the moment I am wondering if I need to downgrade just HBoot to 1.44 so I can S-On again but I'm worried it will show tampered again after I S-On like it did before, now in further if this is the only way to do it how can I get HBoot 1.55 back in after I S-On, I haven't found any firmware downloads out there at all specific to my device.
Thanks in advance for any help.
Click to expand...
Click to collapse
delete quote
I just got a replacement phone for my T-Mobile HTC One (had a mic issue). It says that the OTA update for Sense 6 is available. If I download and install it, will I be able to unlock, root, and s-off my phone to go back to ARHD afterwards?
Also, which method or guide is recommended to do so?
Thanks
I would probably unlock, root and s-off beforehand. If it updates your hboot, you may not be able to root it.
Sent from my HTC One using Tapatalk
Egrier said:
I would probably unlock, root and s-off beforehand. If it updates your hboot, you may not be able to root it.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You may not even be able to s-off it now.. but better now than later