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!
Related
I am a new htc user, however not new to rooting and flashing. I have just recently considered rooting my One S but am not sure if I should just unlock the bootloader or wait for S-off. So my question is simply what are the cons of just unlocking the bootloader now and rooting or would it be better to wait for S-off and root then? Also, if I were to root now, what roms do you recommend?
S-OFF efforts are REALLY slow and it seems no serious attempts are going after it at the moment..
I'd imagine the only disadvantage of using HTC's current bootloader unlocking is that they know you did it and it could void some/all of your warranty. Of course, you also don't have full access to the ROM/HBOOT but you could still flash many things.. You also get a flagged device ("Tampered") if you flash anything which can only be removed with S-OFF AFAIK..
As for ROMs, there are plenty at the Dev section.. I tried a handful and most are good with varying degrees of stability. I am currently on TrickDroid since it is Sense based + extras.. Paranoid Android is my favorite CM-based and pretty stable overall.. AOKP is also good.. Haven't tried MIUI..
Really, it's up to you.. What do you prefer.. Just make sure you have a nandroid backup of your stock rom so you could revert back.
Pheroh said:
S-OFF efforts are REALLY slow and it seems no serious attempts are going after it at the moment..
I'd imagine the only disadvantage of using HTC's current bootloader unlocking is that they know you did it and it could void some/all of your warranty. Of course, you also don't have full access to the ROM/HBOOT but you could still flash many things.. You also get a flagged device ("Tampered") if you flash anything which can only be removed with S-OFF AFAIK..
As for ROMs, there are plenty at the Dev section.. I tried a handful and most are good with varying degrees of stability. I am currently on TrickDroid since it is Sense based + extras.. Paranoid Android is my favorite CM-based and pretty stable overall.. AOKP is also good.. Haven't tried MIUI..
Really, it's up to you.. What do you prefer.. Just make sure you have a nandroid backup of your stock rom so you could revert back.
Click to expand...
Click to collapse
So, contrary to what I've also heard here in several threads, returning to stock with the proper RUU (or even nandroid, however that works?) doesn't truly revert the device back to stock in the way that you retain full warranty? That actually is quite the roadblock for me to get a Jelly Bean ROM soon. That is, if HTC doesn't provide an update soon enough, which we all know is probably the case.
I forgot about RUU but I don't claim that I know if it removes the tampered flag or not.
Some people say that if you relock your bootloader you are good but I don't have any personal experience with HTC service with this regard.
Sent from my HTC One S
Pheroh said:
I forgot about RUU but I don't claim that I know if it removes the tampered flag or not.
Some people say that if you relock your bootloader you are good but I don't have any personal experience with HTC service with this regard.
Sent from my HTC One S
Click to expand...
Click to collapse
Even if you re lock the bootloader they can see it was tampered with. If you boot into the bootloader you'll see at the top it says tampered.
I wouldn't hold my breath for s- off. If you unlock and root your phone and then install TWRP you can just flash roms as though you do have s- off. TWRP will flash the boot.img. That way you don't need to hook your phone up to your pc and fastboot the boot.img. It's awesome Cuz you can just flash on the fly.
Sent from my HTC One S on Axiom S
Okay wel thank you for the help. Will this affect any updates that are put out by HTC or if I unlock the bootloader is there something I can do to revert back? And it sounds like there a couple different ways to unlock and root, what is the best way to go about it? Gosh rooting and flashing roms on the vibrant was significantly more simple
Sent from my HTC VLE_U using Tapatalk 2
cmrn89 said:
Okay wel thank you for the help. Will this affect any updates that are put out by HTC or if I unlock the bootloader is there something I can do to revert back? And it sounds like there a couple different ways to unlock and root, what is the best way to go about it? Gosh rooting and flashing roms on the vibrant was significantly more simple
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
I hear that you cannot OTA update stock ROMs after flashing a custom recovery unless you re-install stock recovery and relock your device.. It's a long process.. of course the important part to update is the radio and you could do it without going through all of that but you risk a permanent brick if something goes wrong..
As for the easiest way for rooting, check the all-in-one thread in dev forum.. I unlocked, rooted, and flashed recovery of mine using that application.. pretty noob friendly
i had plenty of battery life and was on 2.20 4.0.4 update prior to installing this OTA. now my phone wont even turn on after i did the update nor will it charge and have the light come on.. any ideas?
Let me guess. You had supercid??
Sent from my HTC One X using Tapatalk 2
if supercid gives problems on the at&t ota, then you should of been s-off cause i did ota fine with s-off and supercid.
idk i havent really heard of it but maybe. anyway to fix this now or ?
no fix
ps3kev said:
idk i havent really heard of it but maybe. anyway to fix this now or ?
Click to expand...
Click to collapse
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
enduser76 said:
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
Click to expand...
Click to collapse
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems. It could be, but given that some people don't have any problems, it could be anything.
tlazarus said:
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems.
Click to expand...
Click to collapse
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
romy134 said:
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
Click to expand...
Click to collapse
If you were S-Off and SuperCID then the OTA should not affect you.
But. WHY are people wanting the stock OTA? It's causing issues because some people don't know if it's going to brick their phones. Please just wait until custom ROMs come based on the OTA. It's much much much easier
redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
for the other images other then system that get updated, and with s-off now we don't really get screwed by anything so you might as well see if latest gives any improvements.
enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
People never listen or read up till its to late
Sent from my HTC One X using xda premium
enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
The guy at the service station didn't really ask me anything other than "what's wrong with your phone?" and I replied "it's not turning on." he said ok and plugged it into his machines and said he was going to run some tests and to take a seat. Five minutes later he said it's not turning on and he's going to replace it, I asked him what could've happen and he gave a few examples (including third party roms, etc) but that it could have been anything from a corrupt file to dropping it on the floor.
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
For me personally, I couldn't get most of the ROM's to work properly, if at all. I kept getting errors like " com.google.process.gapps has stopped working" or something similar and I'd have no phone service (for example) which is why I went back to stock.
DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
c5satellite2 said:
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
at&t customer service and even technical support have been badass for me last few years only issue is 110 bucks for my phone bill which imo should ive me the right to do whatever i want with my service and my phone without having to pay for tethering or getting throttled ever imo and cheaper early upgrades.
I bought my Htc one X in November through AT&T and I have never had to update it until today. I download and install and everything goes fine. Then it doesn't reboot. When I plug in to do ruu (checked forums) it couldn't recognize my phone. I never rooted my phone or unlocked the boot loader. Is there a way for them to tell at the store if it was at one point rooted? I have seen other posts about people bricking their phones with this update when they are rooted so I have to ask... Is their any solution to my problem before I go to the store tomorrow?
Sounds fishy
a box of kittens said:
Sounds fishy
Click to expand...
Click to collapse
It was fishy to me too... I just want my phone to work...
Chronic cross said:
I bought my Htc one X in November through AT&T and I have never had to update it until today. I download and install and everything goes fine. Then it doesn't reboot. When I plug in to do ruu (checked forums) it couldn't recognize my phone. I never rooted my phone or unlocked the boot loader. Is there a way for them to tell at the store if it was at one point rooted? I have seen other posts about people bricking their phones with this update when they are rooted so I have to ask... Is their any solution to my problem before I go to the store tomorrow?
Click to expand...
Click to collapse
If the phone doesn't turn on, they won't be able to check anything at the AT&T service station. Per my ow bricking of my HTC One X (which was rooted, unlocked then relocked).
enduser76 said:
If the phone doesn't turn on, they won't be able to check anything at the AT&T service station. Per my ow bricking of my HTC One X (which was rooted, unlocked then relocked).
Click to expand...
Click to collapse
Did they give you a new phone? I'm new to this stuff and I haven't had a problem (with any phone) until now... If not I'm sure they'll give me something.
a box of kittens said:
Sounds fishy
Click to expand...
Click to collapse
Chronic cross said:
Did they give you a new phone? I'm new to this stuff and I haven't had a problem (with any phone) until now... If not I'm sure they'll give me something.
Click to expand...
Click to collapse
Are you under contract with AT&T? Why are you so concerned? If you never rooted, and the OTA bricked your phone, you can get a new one.
If you're not under contract, they're going to tell you to get lost.
iElvis said:
Are you under contract with AT&T? Why are you so concerned? If you never rooted, and the OTA bricked your phone, you can get a new one.
If you're not under contract, they're going to tell you to get lost.
Click to expand...
Click to collapse
Yes I am under contract and I'm concerned if I did something wrong? I'm new to android so bare with me. I have seen posts of people bricking due to the fact that they had an unlocked boot loader. I'm guessing people are going to the stores a lot due to this.
Chronic cross said:
Yes I am under contract and I'm concerned if I did something wrong? I'm new to android so bare with me. I have seen posts of people bricking due to the fact that they had an unlocked boot loader. I'm guessing people are going to the stores a lot due to this.
Click to expand...
Click to collapse
There are ways to tell if you're rooted, but they almost never bother. If you never rooted, you've got nothing to worry about.
people bricked recently because they took the jb ota without being s-off and had supercid. if you are s-off with supercid you'd be fine. did you install the htc drivers? HTCDriver3.0.0.007.exe
to check if the the phone has been unlocked or rooted before volume down + power for a long time. should see ***Tampered,Unlocked, or Relocked***
iElvis said:
There are ways to tell if you're rooted, but they almost never bother. If you never rooted, you've got nothing to worry about.
Click to expand...
Click to collapse
DvineLord said:
people bricked recently because they took the jb ota without being s-off and had supercid. if you are s-off with supercid you'd be fine. did you install the htc drivers?
to check if the the phone has been unlocked or rooted before volume down + power for a long time. should see ***Tampered,Unlocked, or Relocked***
Click to expand...
Click to collapse
Phone won't even turn on so... My computer doesn't even recognize my phone (it gives the three dings of death) Lol ill just take it back in the morning. Thanks for the help guys.
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.
Is there a way to do this? I've gone through forums, and haven't seen anything concrete.
ericerk said:
Is there a way to do this? I've gone through forums, and haven't seen anything concrete.
Click to expand...
Click to collapse
If you're S-OFF (if not you can gain it by using Sunshine you can do an RUU, that will take you back to about as stock as you can get e.g stock firmware, stock ROM, stock recovery stock etc.
This thread will tell you most of the things you'd need to do.
I highly advise against attempting to go S-ON or re-locking your bootloader as S-ON has a high probability of failure and or bricking your device.
My personal recommendation would be to just take the RUU and if if I remember correctly you can make your ***UNLOCKED*** tag falsely show ***LOCKED*** instead, not sure though so if that interests you just Google it or ask.
EDIT: Here is the link to the tutorial on setting your UNLOCKED tag to LOCKED. Warning though I have not tested this or heard of anyone testing it so DO THIS AT YOUR OWN RISK.
S1L3nTShaDoWz said:
If you're S-OFF you can do an RUU, that will take you back to about as stock as you can get e.g stock firmware, stock ROM, stock recovery stock etc.
This thread will tell you most of the things you'd need to do.
I highly advise against attempting to go S-ON or re-locking your bootloader as S-ON has a high probability of failure and or bricking your device.
My personal recommendation would be to just take the RUU and if if I remember correctly you can make your ***UNLOCKED*** tag falsely show ***LOCKED*** instead, not sure though so if that interests you just Google it or ask.
EDIT: Here is the link to the tutorial on setting your UNLOCKED tag to LOCKED. Warning though I have not tested this or heard of anyone testing it so DO THIS AT YOUR OWN RISK.
Click to expand...
Click to collapse
I need to to return this device to Verizon.
ericerk said:
I need to to return this device to Verizon.
Click to expand...
Click to collapse
As far as I know they do not care if your phone is S-OFF or unlocked, only that it is running the stock firmware, ROM & recovery. Reason behind this is some of their phones are manufactured and shipped already S-OFF on 'accident', so as long as you do the RUU you should be perfectly fine, at least that is what everyone has said thus far.
S1L3nTShaDoWz said:
As far as I know they do not care if your phone is S-OFF or unlocked, only that it is running the stock firmware, ROM & recovery. Reason behind this is some of their phones are manufactured and shipped already S-OFF on 'accident'. So as long as you do the RUU you should be perfectly fine, at least that is what everyone has said thus far.
Click to expand...
Click to collapse
Are you willing to risk $800 bucks on this?
ericerk said:
Are you willing to risk $800 bucks on this?
Click to expand...
Click to collapse
Your risk not mine, if you're unsure then read through some other threads until you feel confident enough or wait for another person to answer.
& Sorry if I made you a bit unconfident with my last post, I have never had to return another phone to them so all I'm offering you is what I know and or have read from others who have done what you want to do. I'm quite sure that will work as many other people have claimed it worked for them but as with anything I could be wrong which is why I did not include a "*100% GUARANTEED!*" sign. Just offering support, always do your own research too, just as I had done to find that out.
S1L3nTShaDoWz said:
Your risk not mine, if you're unsure then read through some other threads until you feel confident enough or wait for another person to answer.
& Sorry if I made you a bit unconfident with my last post, I have never had to return another phone to them so all I'm offering you is what I know and or have read from others who have done what you want to do. I'm quite sure that will work as many other people have claimed it worked for them but as with anything I could be wrong which is why I did not include a "*100% GUARANTEED!*" sign. Just offering support, always do your own research too, just as I had done to find that out.
Click to expand...
Click to collapse
Bummer there's no official RUU's floating out there.
ericerk said:
Bummer there's no official RUU's floating out there.
Click to expand...
Click to collapse
I can vouch for the RUU I'm gonna link further in this post, I recently used it and successfully RUU'D my phone to stock.
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/2
ericerk said:
Are you willing to risk $800 bucks on this?
Click to expand...
Click to collapse
YOU have already done that the moment you modded your phone lol
S1L3nTShaDoWz said:
I can vouch for the RUU I'm gonna link further in this post, I recently used it and successfully RUU'D my phone to stock.
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/2
Click to expand...
Click to collapse
That's my ruu they link to. Stay on xda and get less shady stuff ?. Below is my thread on it..
http://forum.xda-developers.com/showthread.php?t=2727831
Amazing what some sites will do...
dottat said:
That's my ruu they link to. Stay on xda and get less shady stuff ?. Below is my thread on it..
http://forum.xda-developers.com/showthread.php?t=2727831
Amazing what some sites will do...
Click to expand...
Click to collapse
Since it's your RUU, is this RUU returning us to stock or stock-rooted?
tdnookhd said:
Since it's your RUU, is this RUU returning us to stock or stock-rooted?
Click to expand...
Click to collapse
Stock rooted.