Database Info

[WIP][DEV] S-Off [off-topic discussion prohibited]

Hi All,
OK, bootloader is unlocked, I am working on recovery, so the next challenge is....................S-OFF!!! Aw, f%@ck, I thought i had my life back...
I invite all users with ideas and/or knowledge to jump in and tell me what they think I am doing right and what makes me a moron. I have no pride, so lay it on me.
I will post progress reports in Post #2.
Anyway, here's to getting this done quickly.
Steve
Moderator Edit
This Thread has been moved back to the development section in an effort to put an end to the off topic discussion.
Given the size of this thread I'm going to suggest that you USE the Search thread feature located at the top to make sure your suggestion or idea has not been attempted already.
ANY OFF TOPIC POSTS WILL BE DELETED!​

Progress Reports
Just starting out...

One More
This is just in case...

Excellent.

JSLEnterprises said:
Excellent.
Click to expand...
Click to collapse
Thought I'd get out of your thread and the root thread....

sk806 said:
Thought I'd get out of your thread and the root thread....
Click to expand...
Click to collapse
I had to send another message to red not to reopen the think tank thread (title would have been edited obviously), but to still go ahead with the cleanups... lol

Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.

you have to use this unlock method for the bootloader so why would it screw anything else up? It opens up all possibilities, not close them.

killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
Nope. I have flashed CWM recovery at least 4 times on an international One X AFTER unlocking the bootloader. I wish that were it....
I think you may be thinking of firmware, which is a real mess, because unlocking your bootloader can set your CID to "none", and thus, you can't flash different firmware (i.e., an EU firmware on an Asian phone)...not that that would matter for these carrier-branded phones...

Good job and great progress. Unfortunately, none of us AT&T users can join in on the fun.

killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.

JSLEnterprises said:
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
Click to expand...
Click to collapse
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...just THINK TANKING is all

LNKNPRKFN said:
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...
Click to expand...
Click to collapse
I understand what you mean
I wonder if the fact that its new proprietary qualcomm chip is the reason why its being 'limited'... so we may have to rethink the whole initialization process.
we cant even get to the point that the logcat is able to start logging. So we're flying blind.
We've extended the time between loading to the soft reboot after the flash... but that doesnt tell us much.

I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/

killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernel development on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX, althoug i read it again, anf maybe they are talking about more than that. I am not sure that the article is saying that there is something different with the Rogers version vs other versions, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve

sk806 said:
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernels being flashed on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX. I am not sure that the article is saying that there is something different with the Rogers version, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
Click to expand...
Click to collapse
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.

killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Here is the actual rootzwikk article
http://rootzwiki.com/news/_/articles/dear-htc-can-we-have-our-phones-back-r709

JSLEnterprises said:
The fastboot boot command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Whoa, very interesting. I was certain it did not on the Int one x.

JSLEnterprises said:
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Just to be clear, you are not referring to fastboot flash boot, right?
Edit, nevermind, jut looked at Paul's post, it is fastboot boot. Wow.

killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Again thanks for this. Back to the drawing board!!!!

htc sensation china mobile

Hi I just get a htc sensation, the problem is such that I can not unlock it is still in s-off
my android phone is 4.0.3 and has the Rom of china mobile
h-boot is 0.87.0000 I can not use the revolutinary, because the heads h-boot versions of the latter is 1.XX.XXXXX
please someone can help me

Hboot is 0.87? With a May 2012 date?
Something is screwy. Are you sure this isnt a knockoff?
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)

Get it working?
I think you and I are having the same problem. I got my bootloader unlocked but I can't get it s-off. We have the same h-boot version, and when I reboot into bootloader our my screen is identical to your .jpg
Did you ever get yours rooted? if so PLEASE tell me how.
Thank you.

nhines said:
I think you and I are having the same problem. I got my bootloader unlocked but I can't get it s-off. We have the same h-boot version, and when I reboot into bootloader our my screen is identical to your .jpg
Did you ever get yours rooted? if so PLEASE tell me how.
Thank you.
Click to expand...
Click to collapse
I hate to break it to you, but I don't think you have a real HTC Sensation. That means that none of the rooting methods listed in this forum are going to work. You seem to have a boot loader that is designed to look sort of like the HTC boot loader, but its not the HTC boot loader. That means its got am different design so the rooting methods shown here won't find the same exploits to gain root access and s off. Double unfortunately, even if you could get it rooted, none of the Sensation ROMs would work on it.
Sorry, dude.
Sent from my GT-P5110 using xda app-developers app

ugh
Skipjacks said:
I hate to break it to you, but I don't think you have a real HTC Sensation. That means that none of the rooting methods listed in this forum are going to work. You seem to have a boot loader that is designed to look sort of like the HTC boot loader, but its not the HTC boot loader. That means its got am different design so the rooting methods shown here won't find the same exploits to gain root access and s off. Double unfortunately, even if you could get it rooted, none of the Sensation ROMs would work on it.
Sorry, dude.
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
How disappointing.... ****.

enstore said:
Hi I just get a htc sensation, the problem is such that I can not unlock it is still in s-off
my android phone is 4.0.3 and has the Rom of china mobile
h-boot is 0.87.0000 I can not use the revolutinary, because the heads h-boot versions of the latter is 1.XX.XXXXX
please someone can help me
Click to expand...
Click to collapse
Does your device have a simcard slot? Just out of interest?
tapped out from my sexy sensation XE

China Mobile Sensation
nhines said:
How disappointing.... ****.
Click to expand...
Click to collapse
yes. It's GSM. The biggest problem is the HBoot version is not supported by anything programs like Revolution or Superoneclick that I can find.

nhines said:
yes. It's GSM. The biggest problem is the HBoot version is not supported by anything programs like Revolution or Superoneclick that I can find.
Click to expand...
Click to collapse
You are unlikely to find anything that supports it becuase it's not a real sensation. And again, if you did manage to unlock it it wouldn't get you anywhere because all ROMs, Recoveries, and Firmwares for the Sensation are made for hardware that your phone simply doesn't have. Any attempt to use software made for the Sensation runs a serious risk of bricking the phone you've got. And there is a decent chance that something might actually be able to be installed because who knows how 's-on' that bootloader really is. But if it installs, it will almost certainly brick the phone.
It'd be the same as if you tried to install Samsung firmware on an HTC device. Wrong radio, wrong bootloader, boom...dead.
So if the phone you have works at all for your daily purposes, leave it alone. Just about anything you try to do to modify it will likely kill it.
That being said, most android apps should work on it. It's probably running real Android since Android is open source.

Thanks
Skipjacks said:
You are unlikely to find anything that supports it becuase it's not a real sensation. And again, if you did manage to unlock it it wouldn't get you anywhere because all ROMs, Recoveries, and Firmwares for the Sensation are made for hardware that your phone simply doesn't have. Any attempt to use software made for the Sensation runs a serious risk of bricking the phone you've got. And there is a decent chance that something might actually be able to be installed because who knows how 's-on' that bootloader really is. But if it installs, it will almost certainly brick the phone.
It'd be the same as if you tried to install Samsung firmware on an HTC device. Wrong radio, wrong bootloader, boom...dead.
So if the phone you have works at all for your daily purposes, leave it alone. Just about anything you try to do to modify it will likely kill it.
That being said, most android apps should work on it. It's probably running real Android since Android is open source.
Click to expand...
Click to collapse
Thanks all

S-OFF - What can I do?

So I am a noob to HTC phones. I understand what S-Off is but I am not entirely sure what I could with my phone with it that I can't do now. I am trying to understand whether I should go through the process since there is always the risk of bricking. Thanks!

I have no idea what S-Off is :/ i need some enlightenment
Sent from my One XL using Tapatalk

S-Off is the main thing that allows u 2 root yr phone...
Sent from my GT-I9300 using xda app-developers app

a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do

mrjayviper said:
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
Click to expand...
Click to collapse
I did do that. It said that I could flash ROMs, Radios, stop my bootloader from saying unlocked. Most of this things with the exception of the last I can already do. I was just wondering if there is something that I could be missing out from. Thanks!

Contrary to popular belief, s-off actually has very little to do with your phone being rooted. S-OFF stands for Security-Off, which basically allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions.
Very simply put, that's what it is. There is a lot more to it that you guys can probably look up. For a user on an hboot below 1.14 it really doesn't do all that much, but it's very useful for devs and people post-hboot 1.14

I'm not totally sure what it will do for us, but it was easy enough for me to go through with it, took about 5 minutes if you've already got ADB/Fastboot set up.
I heard it could take away that stupid red paragraph when I boot and that was all I needed to hear haha

I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?

I know I sound like a broken record but
I'd love to see someone create a dual boot program for our phone.
Sent from my HTC One XL

BobbyDukes707 said:
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
Click to expand...
Click to collapse
You got to wait for the new tools to be released. Nothing happens automatically AFAIK.

You can flash ROMs on newer hboot without fastboot
Sent from my One X using Tapatalk 2

so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)

31ken31 said:
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
Click to expand...
Click to collapse
Things will come, just have to give the devs a chance since we just got s-off.

SouL Shadow gave an excellent response to the question here:
http://forum.xda-developers.com/showpost.php?p=38169711&postcount=2462
But as already indicated, things will come in the future, it really doesn't gain much at the moment. Especially for those still on pre-1.14 hboot (and can already flash radios, kernels from recovery).

[Q] Return to as close to stock as possible

Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.

Tersanyus said:
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Click to expand...
Click to collapse
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.

exad said:
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
Click to expand...
Click to collapse
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium

31ken31 said:
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.

exad said:
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
Click to expand...
Click to collapse
I forgot about su access prompt. That could be a shocker lol
Sent from my HTC One X using xda premium

exad said:
I would leave just the bootloader unlocked and S-OFF and RUU.
Click to expand...
Click to collapse
I agree. Couple reasons (both related to RUU). If the new user for some reason needs to recover the phone, and runs the RUU (not unheard of, HTC support will sometimes direct customers to do this), that person will either:
1) Brick the phone, if its left as SuperCID and S-on
2) If S-on (but CID is changed back), and bootloader is left unlocked, the RUU won't run. The person will have no idea why, and will likely be stuck.
S-off solves both of these potential issues. If you are at all worried about the next user. I would S-off, then run the RUU to return the phone to stock. The only thing that would be "not stock" is unlocked bootloader and S-off. But neither of these will mean anything or affect a less experienced user.

I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.

iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.

iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.

redpoint73 said:
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
Click to expand...
Click to collapse
I didn't mean leaving it supercid--that is obviously a risk.
exad said:
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
Click to expand...
Click to collapse
That's kind of my point. Selling it rooted is fine, just represent it for what it is. You shouldn't give a modified phone to someone who doesn't know what that even means.

The phone is going to a friend who has a Pantech Burst currently. As someone mentioned I didn't want them to get a SuperSU prompt for root access and have no idea what that means. I tried a stock rooted rom but it kept rebooting. I did factory reset/data wipe and reloaded the rom twice but still kept doing it. I thought it odd too. Cleamrom is acting just fine though.
After hard bricking a Droid DNA which I don't know if it was due to being unlocked and such I'm starting to feel rooting and custom roms isn't for me anymore. The Droid DNA was replaced and the replacement was never unlocked (and since it has most recent software it couldn't be unlocked. Don't get me wrong, I love not running stock devices. It's such a great feeling to get rid of all that carrier added bloat that I most liked.
I've actually moved on from the DNA as well. I'm on a One now from AT&T as my primary phone. And I so hate all that AT&T bloat in there. It's all disabled but still seeing it there just sends chills down my spine.
So now I am not so sure what to do about the One X now. My original thought was RUU back to factory and relock the bootloader and keep S-ON. That way if someone did look they'd only see "RELOCKED".
Makes me miss the easy days when I used a Captivate and Note 1. Those were so easy to use custom roms on.

iElvis said:
I didn't mean leaving it supercid--that is obviously a risk.
Click to expand...
Click to collapse
Your previous post didn't explicitly say anything about that, one way or another. So I was just clarifying for the benefit of the OP. I knew what you meant, but wanted to make sure the OP did, too!

why you should NOT turn s-on!

i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.

Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.

thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk

People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?

l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk

scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.

l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.

scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.

l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk

scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk

dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2

How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse

Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk

scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk

Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.

nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2

scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.

dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2

I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.