Related
Hi,
I was just wondering if it is absolutely REQUIRED to unlock the bootloader to flash a rom on the nexus s and why? Can I use Clockwork recovery image without unlocking the bootloader?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1060974
Thanks,
but what are the advantages of unlocking the bootloader instead of using some other exploit like this?
Thanks!
Unlocking the bootloader deletes all user data on your device and resets it to factory defaults.
Hi,
But what is the advantage of losing that data and unlocking the bootloader than using the exploits?
Sent from my Nexus S using XDA App
None that I can tell. If you stay on stock rom, I would consider it an advantage NOT to lose all data and settings.
If you want a different rom like cyanogenmod, then you will likely have to wipe your device anyway to avoid random problems. Then you can unlock the bootloader, too, while you are at it, because you have to backup everything (you don't want to lose) anyway.
Unlocking the bootloader allows you to flash stuff directly on the phone from your computer, things like a custom recovery, radio image, fully stock roms and so on.
This in turn allows you to root of flash another rom.
Otherwise, rooting without unlocking probably entails exploiting a security flaw of your device, something I'm not too uncomfortable with.
Before 2.3.2 though you could boot a custom recovery from a file on your computer without unlocking. This was fixed as it was a big privacy and security issue...
Sent from my Nexus S using Tapatalk
So does that mean if I don't unlock the bootloader, I can't use Clockwork mod and flash a rom like cyanogenmod?
Not exactly. You can gain temporary root and install clockwork recovery by means of various exploits of security holes.
You can then use that to install any rom you like.
So pretty much unlocking the bootloader is the easy and safer route.
Sent from my Nexus S using XDA App
Exactly. Since you should backup your data anyway before you tinker with your rom, you might do it anyway.
You can lock the bootloader after you finish flash a new ROM
Yeah, but with clockwork mod you can run a nandroid with or without an unlocked bootloader, so what's the point?
Sent from my Nexus S using XDA App
patrixl said:
Before 2.3.2 though you could boot a custom recovery from a file on your computer without unlocking. This was fixed as it was a big privacy and security issue...
Click to expand...
Click to collapse
Everybody with an USB cable has full root access to any Nexus S running CM7 (using CWMs ADB capability) and nobody seems to care?
1st: You don't need CWM for CM7, AFAIK.
2nd: The same is true for any NexusS with unlocked bootloader.
3rd: The attacker could also use the gingerbreak exploit or similar to gain root access and neither a locked bootloader nor stock recovery will protect you.
It is the same as with your computer. Someone who has physical access to the machine usually can do anything he wants.
The solution is quite simple too: don't give anyone unsupervised access to your phone. That includes of course not losing it...
So its safer to unlock it?
Sent from my Nexus S using XDA App
Yes and no. It depends on what kind of security you mean, too. The unlockable bootloader is a feature. Using it is the standard way to go.
An exploit could install keyloggers or spyware or whatever without you knowing.
However, an custom rom from somewhere could have keyloggers or spyware preinstalled, too.
Basically you have to decide yourself, how much risk you are willing to take.
I still can't get the advantages of unlocking it.
Sent from my Nexus S using XDA App
I mean, can you flash clockwork mod with a locked bootloader?
Sent from my Nexus S using XDA App
Only with certain versions of the bootloader, not all. It was a security hole like others have mentioned. It was later fixed.
Full guide here: http://forum.xda-developers.com/showthread.php?t=1232107
Revolutionary achieved radio S-OFF for Sensation (among other devices) which means you can practically do whatever you want with your phone (like actually owning it..). This means it makes it vulnerable to all sorts of schemes including sim-unlocking. This can be done various ways (check forums), but I find the following quite efficient and easy to do!
Requirements: owning a Sensation S-Off’ed using this;
1. download this file and put it on the root of your sdcard
2. reboot your phone in hboot and let it do its job: load the file you’ve just downloaded from sdcard and run it. That file is a diagnostic utility and serves various purposes given various conditions.
3. you’ll enter a menu from which you can choose to check your device’s info or reset s58 data.
4. Reset s58 data. This actually resets some things including your sim-lock status.
Now you’re free to go! Bear in mind, though, that in certain circumstances you’ll lose your data connectivity or network signal. You’ll just have to check your APN, network type & so on; I guess this varies with each case.
Credits go to you all, XDA community, but best you should thank revolutionary team!
WARNING!!!
Backup all your settings/apps/sms/etc, network unlocking by using this method also involves wiping your data!
The best things in life are free!
Click to expand...
Click to collapse
+1 rep....
is this reversible? i just got a bnb sensation from the warranty and i need to know if i can restore it to "vodafone" default if i need to send it to warranty again
fuinhu said:
is this reversible? i just got a bnb sensation from the warranty and i need to know if i can restore it to "vodafone" default if i need to send it to warranty again
Click to expand...
Click to collapse
I would assume that SIM-unlocking does not void warranties.. but please correct me if I'm wrong. I realize this is a hacked method of achieving SIM-unlock, but I do not think it would matter how SIM-unlock is achieved.
Sent from my HTC Sensation 4G using XDA App
maff1989 said:
I would assume that SIM-unlocking does not void warranties.. but please correct me if I'm wrong. I realize this is a hacked method of achieving SIM-unlock, but I do not think it would matter how SIM-unlock is achieved.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
not to mention, those of us on t-mo can just ask for the code. They've
always gladly given it to me. They wouldn't give you something that would
void the warranty.
maff1989 said:
I would assume that SIM-unlocking does not void warranties.. but please correct me if I'm wrong. I realize this is a hacked method of achieving SIM-unlock, but I do not think it would matter how SIM-unlock is achieved.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
well that makes sense but it only works with s-off so if it leaves clues the htc repair can simply refuse to repair the phone since s-off void the warranty
This method also Changes the cid for you to 11111111 and sim unlocks it
heres the rard file
http://forum.xda-developers.com/showpost.php?p=16952166&postcount=101
has anybody successfully been able to use the phone on AT&T after doing this??
yes. the other thread a person said they wiped using that file and then called his wife with his buddies ATT sim card
skygear said:
yes. the other thread a person said they wiped using that file and then called his wife with his buddies ATT sim card
Click to expand...
Click to collapse
GUIDE IS NOW ONLINE IN DEV SECTION
http://forum.xda-developers.com/showthread.php?t=1232107
OP YOU CAN UPDATE YOUR POST TOO ALL CREDITS TO YOU FOR THIS!
has anyone confirmed that this method will unlock a sensation with the SH17 s/n?
Yes, it was confirmed. It should work with any Sensation.
Cool. thanks!
Unlocking doesnt work in my HTC Sensation 4G
xl VipeR lx said:
GUIDE IS NOW ONLINE IN DEV SECTION
http://forum.xda-developers.com/showthread.php?t=1232107
OP YOU CAN UPDATE YOUR POST TOO ALL CREDITS TO YOU FOR THIS!
Click to expand...
Click to collapse
Hi sieempi! I tried the guide you developed on unlocking my HTC sensation which is locked to TMobile but it didnt work. My phone doesn't recognize the PG58DIAG.nbh code. Any other alternative to this?
What do you mean it doesn't recognize? Post your hboot messages.
ok I just did it. I didn't give me the option to reset the s58 data but to clean the s58 data, so I ran that, and now I'm running the nandroid backup I did before this process. I can use my mom's AT&T Sim to see if it worked or now I'll report back in a bit when I see if it worked or not.
It works fine but with that can´t do the normal updates anyone can help me??
I only have the s-off and that program, and i want to do the new update.
It's possible to do a roll back and put the sensation like he comes stock?
Thanks
awesome!
sieempi said:
Full guide here: http://forum.xda-developers.com/showthread.php?t=1232107
Revolutionary achieved radio S-OFF for Sensation (among other devices) which means you can practically do whatever you want with your phone (like actually owning it..). This means it makes it vulnerable to all sorts of schemes including sim-unlocking. This can be done various ways (check forums), but I find the following quite efficient and easy to do!
Requirements: owning a Sensation S-Off’ed using this;
1. download this file and put it on the root of your sdcard
2. reboot your phone in hboot and let it do its job: load the file you’ve just downloaded from sdcard and run it. That file is a diagnostic utility and serves various purposes given various conditions.
3. you’ll enter a menu from which you can choose to check your device’s info or reset s58 data.
4. Reset s58 data. This actually resets some things including your sim-lock status.
Now you’re free to go! Bear in mind, though, that in certain circumstances you’ll lose your data connectivity or network signal. You’ll just have to check your APN, network type & so on; I guess this varies with each case.
Credits go to you all, XDA community, but best you should thank revolutionary team!
WARNING!!!
Backup all your settings/apps/sms/etc, network unlocking by using this method also involves wiping your data!
Click to expand...
Click to collapse
hey thanks a lot for this method, it worked for my sensation like a charm, give me your paypal address so i can buy you a beer!
NOTE!
OP is NOT the person who worked on this. If you're going to buy anyone a beer it should be the dev xl VipeR lx
Click the link in the OP's first post, then buy the person who really helped you a beer.
I am running cm10 with CWM recovery. I am looking to make my phone secure in the case it gets stolen. Pretty much everything is accessible through the recovery what can be done about it? Can we put a password on the recovery? Can i go back to stock recovery using cm10?
I know there is no such thing as fool proof but i would atleast want it to be a little difficult for a thief to get into my phone.
Sent from my Nexus S using xda app-developers app
Have you tried looking at the encryption option? I think once enabled you will need a password even before getting into recovery.
Sent from my Nexus S
anshumandash said:
Have you tried looking at the encryption option? I think once enabled you will need a password even before getting into recovery.
Sent from my Nexus S
Click to expand...
Click to collapse
I did.
It says it needs an hour to complete and that one cannot go back. Does it have any drawbacks to the user itself? Or is it just whenever you reboot the phone that it needs a password?
Gambler_3 said:
I am running cm10 with CWM recovery. I am looking to make my phone secure in the case it gets stolen. Pretty much everything is accessible through the recovery what can be done about it? Can we put a password on the recovery? Can i go back to stock recovery using cm10?
I know there is no such thing as fool proof but i would atleast want it to be a little difficult for a thief to get into my phone.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Put pin, password or pattern and relock bootloader. That's the only real secure way. With an unlocked bootloader there's always a way.
polobunny said:
Put pin, password or pattern and relock bootloader. That's the only real secure way. With an unlocked bootloader there's always a way.
Click to expand...
Click to collapse
Have already put pattern but locking the bootloader seems too much no? Is it even possible with CM10?
And I keep USB debugging off so no one can use adb.
Gambler_3 said:
Have already put pattern but locking the bootloader seems too much no? Is it even possible with CM10?
And I keep USB debugging off so no one can use adb.
Click to expand...
Click to collapse
Even if you keep the bootloader locked if you got a custom recovery, it is not safe. The only way to make it real safe is to flash stock recovery, lock bootloader and then put a pin or pattern password.
Gambler_3 said:
Have already put pattern but locking the bootloader seems too much no? Is it even possible with CM10?
And I keep USB debugging off so no one can use adb.
Click to expand...
Click to collapse
Too much? It takes someone knowledgeable 5 minutes to destroy a password, pattern lock or pin if the bootloader isn't locked.
Say you flash back to stock recovery. That's fine, but with an unlocked bootloader I can flash back to a custom recovery, get full adb access, mount your SD card, peruse your stuff, remove the lock and boot the phone if I want to. If you lock the bootloader, I can't flash a custom recovery.
The downside is pretty evident. With a locked bootloader + a stock recovery, you can't update your custom ROM, not without unlocking the bootloader. And if you do that, you wipe your stuff.
I'm with polo on this. Like he said, someone with a minimal amount of skills can do whatever. If your phone gets stolen, the phone would get blacklisted and if it's gsm it might work on another carrier. If you had lookout, you can find the phone through gps on their site and remotely wipe it.
Sent from my Nexus S 4G using xda app-developers app
Thanks alot guys. Okay i know how to lock the bootloader but can someone tell me how i flash back stock recovery? As in where to find the file?
I know the not being able to flash anything without reset is the bummer but i will still be able to update the cm rom through ota right?
Sent from my Nexus S using xda app-developers app
Gambler_3 said:
Thanks alot guys. Okay i know how to lock the bootloader but can someone tell me how i flash back stock recovery? As in where to find the file?
I know the not being able to flash anything without reset is the bummer but i will still be able to update the cm rom through ota right?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Your better off not doing it, is just to much hassle for what? A thief doesn't care about your data so it doesn't matter to them about passwords etc. They'll just wipe the phone and sell it.
Sent from my GT-I9000 using xda premium
Cerberus App
How about installing the Cerberus app, you can do a remote format/wipe
NIMBAH said:
Your better off not doing it, is just to much hassle for what? A thief doesn't care about your data so it doesn't matter to them about passwords etc. They'll just wipe the phone and sell it.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I guess you guys are right I might be taking this too seriously. I dont keep any confidential pictures on my phone and I unlinked my google account from my phone with a simple change of password from the desktop just to check if it really works. So all my accounts will be protected. Whatsapp will be taken care of by blocking the sim.
Thanks anyways everyone.
NIMBAH said:
Your better off not doing it, is just to much hassle for what? A thief doesn't care about your data so it doesn't matter to them about passwords etc. They'll just wipe the phone and sell it.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Depends what kind of data you have. It's not about the thief and if that person cares about your data. It's about if YOU care about your data. Some people have critical information on work projects or similar on their phone, and the worst thing that could happen is for that information to get published/shared.
Personally, I keep nothing too important on my phone, I have a remote wipe installed, pattern lock, but my bootloader is unlocked and i have a custom recovery. It's good enough for my needs, but I understand it's not the ultimate security either.
Ultimate solution I've found. I have a small amount of c4 inside the battery compartment linked to my unlock code. Wrong code.... BOOM!
Sent from my Nexus S 4G using xda app-developers app
n2d551 said:
Ultimate solution I've found. I have a small amount of c4 inside the battery compartment linked to my unlock code. Wrong code.... BOOM!
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
I prefer thermite.
polobunny said:
Depends what kind of data you have. It's not about the thief and if that person cares about your data. It's about if YOU care about your data. Some people have critical information on work projects or similar on their phone, and the worst thing that could happen is for that information to get published/shared.
Personally, I keep nothing too important on my phone, I have a remote wipe installed, pattern lock, but my bootloader is unlocked and i have a custom recovery. It's good enough for my needs, but I understand it's not the ultimate security either.
Click to expand...
Click to collapse
The only really personal thing on my phone is my convo with my girlfriend but i am no celebrity so i am sure it won't be published.
And i have always been very particular about not keeping compromising photos or videos on my phone or pretty much anywhere. See them once on the big screen and then destroy the SD card if you know what i mean.
Sent from my Nexus S using xda app-developers app
install security software, i remember there was a Reddit thread
Install any secure app like lookout so that you can wipe remotely. Also, record your IMEI so that if your phone gets stolen, you can call your carrier and block it.
Sent from my Nexus S using xda app-developers app
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!
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.