Related
So When we root our phone are phone is automatically S-Off right?
and S-Off means the phone is unlocked and we can use it on other networks ?
Just want to clear everything up. I thought I needed to buy an unlock code for it to be unlocked but I just read that S-Off means its sim unlocked
The "S" in S-off stands for security, a stock bootloader comes S-on or security on. This is to make the device to where you can only install what is considered authorized software, or to be more specific, software that the OEM or the carriers release for the device. Now when you S-off your de ice you unlock it so that you can flash other software other than just the OEM's or carrier's software, this kind of software is refered to as custom software. This type of software includes custom recoveries, custom ROMs, and sometimes custom bootloaders.
Now to unlock your device so that you can use it with another carrier is referee to as SIM unlocking the device. And yes to SIM unlock your device you need a unlock code. You can generally get theses codes from the original carrier you purchased the device from or from different websites that charge for the code.
Rooting your device is something that allows you full control of your device and also allows you to use your device to it's full potential. It allows your ROM to have direct communication with the Linux kernel it is running on top of, which gives your device much more functionality. Certain bloatware apps have limited root access bit the ROM itself does not when the device is running stock software.
So I hope you have a little better understanding now of the three. I also hope this answered your question. Cheers.
T-Macgnolia said:
The "S" in S-off stands for security, a stock bootloader comes S-on or security on. This is to make the device to where you can only install what is considered authorized software, or to be more specific, software that the OEM or the carriers release for the device. Now when you S-off your de ice you unlock it so that you can flash other software other than just the OEM's or carrier's software, this kind of software is refered to as custom software. This type of software includes custom recoveries, custom ROMs, and sometimes custom bootloaders.
Now to unlock your device so that you can use it with another carrier is referee to as SIM unlocking the device. And yes to SIM unlock your device you need a unlock code. You can generally get theses codes from the original carrier you purchased the device from or from different websites that charge for the code.
Rooting your device is something that allows you full control of your device and also allows you to use your device to it's full potential. It allows your ROM to have direct communication with the Linux kernel it is running on top of, which gives your device much more functionality. Certain bloatware apps have limited root access bit the ROM itself does not when the device is running stock software.
So I hope you have a little better understanding now of the three. I also hope this answered your question. Cheers.
Click to expand...
Click to collapse
While, I knew this already, that was a great explanation and you've been thanked for it.
maybe this can help you.
http://forum.xda-developers.com/showthread.php?t=1232107
I have an AT&T HOX. Came stock with 1.85.
I rooted it using the "redbend" method described here (http://forum.xda-developers.com/showthread.php?t=1709296)
(More or less, the pulling SIM card business wasn't part of the steps when I used it, but the root was successful).
I am using SuperSU to manage root access by apps.
I have not done anything beyond that.
Now, I understand, at some point, AT&T is going to force a 2.20 update on me.
My primary concern is to avoid losing root.
(I have enabled the "preserve root across OTA" in SuperSU, but not sure if its effective or not)
I've looked at the howto's for SuperCID, unlocking the bootloader, etc, and I'm not sure which I NEED, and which are optional, and/or what the pros/cons are of each...
I'd like to stay as close to "stock" as possible, but I want to ensure that I can keep root.
I'm still within my AT&T contract, and would really prefer to avoid bricking the phone.
I'm wondering what the recommendations are as to the minimum steps I should take to keep root in the event the OTA is forced on me?
Can I pre-empty the OTA by installing this? ( http://forum.xda-developers.com/showthread.php?t=1812459 )
If so, what is the safest method for installing it?
FWIW, I am a linux user, and I am comfortable with adb as well as the command line on the phone itself.
I have no windows systems, so any special tools I'd need other than adb I'd have to find a linux version.
I don't need "one click" methods, in fact I'd prefer to see/perform the individual steps and understand what they are doing.
unlock your bootloader using this method http://forum.xda-developers.com/showthread.php?t=1672284 if you don't you wont get root again afterwards.
Dont have to unlock to flash roms?
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
My ATT HOX is currently rooted, and I now have SuperCID. I assumed I would need to unlock my bootloader, but I havent done that yet.
Can I install this:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Megadave123 said:
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
Click to expand...
Click to collapse
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Megadave123 said:
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
Click to expand...
Click to collapse
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Megadave123 said:
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Click to expand...
Click to collapse
SuperCID survives OTA. But the 2.20 OTA has a new hboot, which fixes the hole by which kernels and radios can be flashed from recovery, so my recommendation would be not to install the OTA.
redpoint73 said:
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Click to expand...
Click to collapse
FWIW, I didnt google that site. It was linked to from an XDA post. I't didnt seem right to me, which is why I asked here
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Click to expand...
Click to collapse
Ok, that is VERY good to hear.
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Megadave123 said:
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Click to expand...
Click to collapse
I think bypassing the user acceptance dialogues for the OTA install would be a violation of how Android fundamentally works. It would be a serious security issue, as it might allow rogue software to be installed on your device without your interaction. I seriously doubt AT&T would institute such a thing.
The user confirmation of the OTA might be a liability thing, too. If the performance of the device is adversely affected by the OTA (happens to some people) and the OTA was forced by AT&T without the owner having a choice, it would seem to me that AT&T has to accept the responsibility. People can claim its AT&T's fault, and demand a replacement device (since AT&T technically installed the software remotely). By making you confirm the OTA installation (and giving you the chance to opt out), you pretty much are volunteering to install the software and accept the consequences.
In theory, unlocking the bootloader voids you warranty. But more than a few folks on here have gotten warranty replacements from AT&T (after unlocking the bootloader), without issue. Sometimes in-store (within the first 30 days) without them even checking for the bootloader unlock. No guarantee that this will always be the case. But just throwing it out there. Its still up to you whether unlocking the BL is worth the risk in your own case.
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
18th.abn said:
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
Click to expand...
Click to collapse
The hoxl is officially supported by twrp and can be downloaded from goomanager. I do not know if you can install a custom recovery without an unlocked bootloader. I would be interested to know if this can be done as well.
Sent from my Nocturnalized One XL using Forum Runner
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Is there any harm in trying it?
If I install "goo manager", and let it do its thing, and the locked bootloader prevents it from doing so, there wont be any other side effects, will there?
If I come off as a complete noob at this - its because I am..
This is my first Android phone, and I *really* want to avoid bricking it, so I want to make sure I understand as much as possible before I go
trying to do anything to it.
Also I'm still wary of unlocking, mainly because of the whole "will erase your phone" bit.
I'm not yet fully comfortable that I know how/what to fully backup all of "my" data on the phone so as to facilitate easily putting it all back.
I'll answer some q's here.
1.) you cannot flash a custom recovery from hboot with a locked bootloader
2.) you CAN dd a custom recovery with a locked bootloader. However your device will be soft-bricked.
3.) you CAN install custom ROM's via dd right from android. This is how we did it back "in the day".
4.) you "might" be able to get away with dd'ing a custom kernel with locked BL, not not sure. In fact, I'd bet it will softbrick now that I think about it.
Anyways, the SAFEST way to do it is via unlocking the bootloader and installing your roms from custom recovery.
gunnyman said:
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Click to expand...
Click to collapse
Beaups pretty much already answered it. But this guy tried installing TWRP thru goomanager with a locked bootloader, and confirmed it doesn't work: http://forum.xda-developers.com/showthread.php?p=31220704#post31220704
Hi guys
I am new and never flash firmware on HTC before.
I have go HTC one XL from hongkong unlocked with JB (just recently got the official download) but not happy with the data connection speed and it is very slow for some reason. ICS was better than the Hongkong official JB release unfortunately.
Since I am in Australia I want to flash my firmware with the stock rooted Telstra [ROM] 01/01/13 Stock rooted odexed JB Telstra_WWE_3.17.841.2.
Can some one pls point me to the right direction - I am not sure where to start (previously I own SG2 and flashed firmware no issues).
I am aware that there are more options on how to flash in HTC I am abit worried that I might follow the incorrect steps
Thank you
Unfortunately, some changes were deployed in the official JB update which causes the touch screen to not function if you try changing to any ROM that is not also Sense JB. So currently, if you flash an ICS ROM, the touch screen will not work.
Devs may be working on this. But its more likely that it won't be solved until we have kernel source for JB. Until the issue is fixed, you are stuck with Sense JB ROMs.
If you still want to be able to flash custom ROMs, the proper sequence is:
- Unlock bootloader at HTCDev.com
- Install TWRP recovery
- Download custom ROM, and copy to phone's SD
- Flash ROM in TWRP
- Flash boot.img using fastboot
You can start reading here: http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
Unfortunately, some changes were deployed in the official JB update which causes the touch screen to not function if you try changing to any ROM that is not also Sense JB. So currently, if you flash an ICS ROM, the touch screen will not work.
Devs may be working on this. But its more likely that it won't be solved until we have kernel source for JB. Until the issue is fixed, you are stuck with Sense JB ROMs.
If you still want to be able to flash custom ROMs, the proper sequence is:
- Unlock bootloader at HTCDev.com
- Install TWRP recovery
- Download custom ROM, and copy to phone's SD
- Flash ROM in TWRP
- Flash boot.img using fastboot
You can start reading here: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Cheers for the reply.
Yes i still want to flash the telstra jb available hoping that performance is going to be abit better.
Do I still have to unlock my bootloader? Eventoughmy phone is unlocked? Sorry for the basic questions. I will have a read on the link as well. Thanks guys
Sent from my HTC One XL using Tapatalk 2
Hi guys
Been trying to read the suggested link. I am seriously confused.
Do I need to unlock my bootloader?
Is the any tutorial for complete newbie?
Thanks guys
Sent from my HTC One XL using Tapatalk 2
ardabelati said:
Hi guys
Been trying to read the suggested link. I am seriously confused.
Do I need to unlock my bootloader?
Is the any tutorial for complete newbie?
Click to expand...
Click to collapse
You need to read until it makes sense as a complete newbie will just end up bricking the phone.
You do need to unlock the bootloader. Your phone may be "unlocked" in relation to allowing any SIM from any provider, but that is 100% unrelated to unlocking the bootloader.
The Telstra 3.17 is unlikely to make any difference to the Hong Kong based 3.17. They are almost identical except for the few Telstra apps included.
Have you checked that your APN is set to telstra.wap so that LTE will function? The Hong Kong phones ship with incorrect settings for Telstra.
You could refer to this link for help, but ignore it's advise to set telstra.internet as that is incorrect(it is only for 4g modems, not phones) and will prevent some Telstra apps from working correctly:
https://support.mobicity.com.au/ent...up-the-htc-one-xl-on-telstra-s-4g-lte-network
Also you should check Telstras coverage as LTE is only available in limited areas.
http://www.telstra.com.au/mobile-phones/coverage-networks/our-coverage/mobile-broadband/
Beyond these suggestions you should take up your speed issues with Telstra.
ardabelati said:
Do I need to unlock my bootloader?
Click to expand...
Click to collapse
I already answered this in post #2 above. Don't know why you are asking the same question again.
Twisteddx beat me to answering your other questions, and I agree with all he said.
You're confusing unlocking the SIM versus unlocking the bootloader. SIM unlocked just means you can use SIMs for any carrier. Bootloader unlock removed write protection for certain partitions of the memory, allowing you to install custom recovery, custom ROMs, etc. SIM unlock and BL unlock are not related in any way.
I'm not a huge fan of simple tutorials. They invite you to try mods with a minimum of knowledge, which is really the opposite of what you should do. Read up, and learn as much as you can, as twisted mentioned, you will be performing things that can cause permanent damage to the phone if not done completely properly. You need to have a deep understanding of what you are doing before you start. Even if you follow the steps to the letter, things all-to-often go awry. And being armed with as much knowledge as possible is the best way to prepare for such events.
The amount of information can be daunting, for sure. But once you become more familiar with the terms and basic concepts, you will probably see its actually not that complicated. Maybe start with some of the "Misc Guides" at the bottom of the 1st post of my Index thread, such as the Terminology glossary. Look at other posts by similar users in Q&A, and go from there.
I'm sorry if this questions have been asked before. I read through many pages on the Q&A section of this phone and didn't come with clear answers to my questions.
This is the first time I will attempt to unlock, root and flash a ROM on an Android phone.
First of all, I've read and I still don't know if I can flash a custom ROM, or one of those Brazil/Orange JB images available and be able to have the phone unlocked to use with different carriers. Jelly Bean hasn't been released to this phone here in Mexico yet.
1.- I don't mind unlocking the bootloader with Motorola solution. Is this the best way to unlock it?
2.- Flashing a custom ROM or a stock one makes the phone unlocked so I can use it with different carriers?. If the answer is yes, what ROM do you recommend. Are those Brazil/Orange images good for any user or its better to stick with third-party ROMs?
3.- If the answer to number 2 is NO, what should I do in order to unlock the phone? I need to be able to use in Mexico (the phone if from Telcel) and also use it on the United States (with AT&T). I've read about modem files that had to do with carriers but I'm not sure if I need special files to unlock this phone? If this is needed, where do I start or where do I find this files?
4.- If there is something else I need to know (and I didn't asked here) about unlocking the phone and flashing a stock or third-party ROM and have it unlocked to work with other carriers, please let me know by replying.
What are you guys using to backup the factory image? I haven't fiddled with Android for a while after flashing a Kindle Fire many times. I got a Nexus 7 and I haven't needed to root, unlock or try third party ROMs. The last time I used TWRP to backup the image of the Kindle Fire I think.
Thanks in advance
ajua said:
I'm sorry if this questions have been asked before. I read through many pages on the Q&A section of this phone and didn't come with clear answers to my questions.
This is the first time I will attempt to unlock, root and flash a ROM on an Android phone.
First of all, I've read and I still don't know if I can flash a custom ROM, or one of those Brazil/Orange JB images available and be able to have the phone unlocked to use with different carriers. Jelly Bean hasn't been released to this phone here in Mexico yet.
1.- I don't mind unlocking the bootloader with Motorola solution. Is this the best way to unlock it?
2.- Flashing a custom ROM or a stock one makes the phone unlocked so I can use it with different carriers?. If the answer is yes, what ROM do you recommend. Are those Brazil/Orange images good for any user or its better to stick with third-party ROMs?
3.- If the answer to number 2 is NO, what should I do in order to unlock the phone? I need to be able to use in Mexico (the phone if from Telcel) and also use it on the United States (with AT&T). I've read about modem files that had to do with carriers but I'm not sure if I need special files to unlock this phone? If this is needed, where do I start or where do I find this files?
4.- If there is something else I need to know (and I didn't asked here) about unlocking the phone and flashing a stock or third-party ROM and have it unlocked to work with other carriers, please let me know by replying.
What are you guys using to backup the factory image? I haven't fiddled with Android for a while after flashing a Kindle Fire many times. I got a Nexus 7 and I haven't needed to root, unlock or try third party ROMs. The last time I used TWRP to backup the image of the Kindle Fire I think.
Thanks in advance
Click to expand...
Click to collapse
Unlocking BL doesn't change the unlocked status of the phone for carriers. If you want to unlock it to use with different carriers you'll have to pay the unlock fee to whoever you choose to unlock with.
1. Answered above.
2. Custom ROMs or ROMs from different carriers won't unlock the carrier.
3. I believe there is some sort of file modification to have it unlocked. Not sure what you have to do but if I remember correctly its risky and affects IMEI.
Sent from my RAZR HD XT925
saloums7 said:
Unlocking BL doesn't change the unlocked status of the phone for carriers. If you want to unlock it to use with different carriers you'll have to pay the unlock fee to whoever you choose to unlock with.
1. Answered above.
2. Custom ROMs or ROMs from different carriers won't unlock the carrier.
3. I believe there is some sort of file modification to have it unlocked. Not sure what you have to do but if I remember correctly its risky and affects IMEI.
Sent from my RAZR HD XT925
Click to expand...
Click to collapse
I know the bootloader won't change the locked status. As this is the first time flashing a phone, not a tablet, I thought that using a custom ROM or one from different carrier would work for this.
I've tried other SIMs on the phone (it's my sister's, not mine) but the phone didn't asks for a code when a SIM from a different carrier is inserted. I haven't bought any code because of this.
Anyone has a suggestion on what to do to have the phone unlocked to use with different carriers?
disclaimer!
*this thread is not intending to promote the sale of any particular service or cell phone reseller.
*this thread is intended to provide info only. any questions,please ask,some i may add to the FAQ.
*please abide by all forum rules in posting so this thread can remain open
this method uses an official htc java card to turn off the phones security data. the card exists as a legitimate tool for cell phone shops and re-sellers,primarily for the purpose of removing the phones simlock.
since this method of s off is somewhat unusual,this thread is intended to help support folks that are unsure of the differences and similarities. use this info at your own risk.
in this first post,i thot a few FAQs needed to be put in one place,as they are being asked over and over again in the thread.
Frequently Asked Questions
Q: what is s off?what does it do for me?
A: in a nutshell,s-off=security off. it removes all security checks and allows access to all partitions of the phone this means you can:
-change hboot
-change splash inage
-change radios
-flash unsigned files
-go backwards in firmware versions
-other things that maybe ill add later
Q: is this java card process legit??
A:yes,it is. as mentioned above,the java card is a legitimate tool used by some large cell phone repair shops and re-sellers.
Q: how does this work?
A:the java card is plugged into a USB On The Go cable,and plugged into the phone. the java card contains htc-signed diagnostic files wich are used to clear security data. when the phone is booted to hboot with the java card plugged in,it finds the diagnostic file and jumps to a mode where the user can clear "s58" data. this removes any simlock,changes the CID to a generic "supercid",and most importantly,turns off the phones radio secure flag. hooray!
this video of an htc one x will give you a good idea what the process looks like:
HTC One X S-OFF
Q: what exactly is a java card?
A: simply,a java card is an sd card with a microprocessor in it. if someone wishes to provide a more detailed definition,id be happy to put it here.
Q: can we clone the java card so everyone can have s off?
A: yes. but its complicated,and the card to begin with is expensive. there have been some technical discussions about this,but the simple answer is that it is not easy,or practical to clone the java card.
Q: why do i have to pay for this?? shouldnt s off be free?
A: if you have a prollem paying for this service,you are welcome to purchase your own java card and offer the service for free. as has been stated,the java card is expensive- upwards of $1000 depending how may credits are included.
further,even if a software exploit was available,it is good custom to donate to the devs who brought you the tool. remember,no one here owes you custom roms,s-off,etc. support your devs and what they bring you.
Q: is the card good forever?
A: NO! the java card has a limited number of uses.
Q: how do i use this service?
A: you will need to track down a phone shop or reseller that has a card. these are not common,but are available in most countries with some searching.
Q: if im allready unlocked,should i still get s off?
A: in my opinion,yes. wether done via a java card or software exploit,s off is better. it allows more options to recover soft-bricked devices,and allows access to all partitions. an s on phone is still doing plenty of security checks. it also allows a permantly installed recovery to install the boot image. the downside is that your phone WILL let you brick it if your not careful. know what your flashing and why. double check md5 sums to verify the integrity of your downloads. a corrupt bootloader ot radio can damage your phone,potentially unrecoverably. if you just asked "what is an md5sum?" stop and google it now. there are numerous md5summers avaialable for free on the vast interweb,download one and start using it.
Q: if im allready unlocked and running a custom rom and recovery,do i need to take any precautions?
A: yes. the diag file is designed to work on stock software and firmware. i would strongly recomend to:
-restore a bone stock nandroid,or flash a bone stock rom
-reflash your stock recovery
-reflash your stock boot image if you were running a custom kernel
-select 'factory reset' option from hboot
Q: will this wipe my phone?
A: yes it will. so back up your sd card to the pc,and be prepaired to have to re-set everything up when you get it back.
Q: does my phone need to be active?
A: no it does not.
Q: does my sim card need to be present?
A: no it does not.
Q: how do i activate a spare phone while mine is away?
A:it depends on the phone. if you have a gsm phone,or a 4g vzw phone,you can simply swap over your active sim. if the sim is larger in the spare phone,adapters do exist for extremely cheap on ebay and amazon. alternately,you can call vzw,sprint,or your other cdma carriers, or go to their website to activate an older 3g device.
Q: how do i activate my phone when it comes back?
A: like you normally would. s off by itself does not change anything about the phone or how it oporates. its what you do afterward/modify that can have an impact on "normal" operation. so if you moved your sim into another phone,just move it back. if you mailed your phone directly to a reseller with the protective film still on it,then take everything out of the box and activate just like you would if it had just come from htc or your carrier.
Q: if my phone was carrier blocked by htc dev,will i be able to unlock the bootloader if my phone is s off?
A: yes. when the phone comes back,it will have "supercid". this ignores the mid(model id) check that htcdev does on the phone,and will let you get a token and unlock.
Q: are there advantages to unlocking the bootloader?
A: you have a couple extra fastboot commands you can use:
fastboot flash partition imagename.img
and
fastboot boot imagename.img
these commands are useful to install recovery,and boot images into phone memory. with fastboot bootfor example,you can temporarily launch recovery on the phone to flash su if you dont want to permantly install it.
Q: so do i NEED to unlock the bootloader to install recovery?
A: no,you do not. you can install recoveries and all other partitions as zip files. more info on that later.
Q: does superCID give you any benefits?
A: in a word,maybe. on a gsm device where you have multiple carrier and regional firmwares that will work,supercid is of value. with a device on vzw sprint,or other cdma carriers using specific firmware,you can only use those specific ruus anyway. further,accepting an OTA with supercid could leave you unrecoverably bricked,plus it may interfer some some verizon functions(i remember inc 4g users having issue,but the details escape me)
IMO,after unlocking your bootloader,if you choose to do so,you should change your CID back to stock VZW__001 (thats 2 underscores- cid is always 8 digits),HTC__001(again 2 underscores) or whatever it happened to be.
Q: is my cid unique to my particulare phone?
A: no,it is not. it is unique to a carrier or region. all verizon phones ever made have a cid of VZW__001
Q: how do i change my cid back to stock?
A: with this fastboot command:
fastboot oem writecid xxxxxxxx
Q: why is my cid always present on the hboot screen?
A: i dont know htc's logic,but this is simply what the phone does while its s off. it will display whatever your cid is,and is not dependent of your bootloader being locked or unlocked.
Q: what about the TAMPERED and unlocked/relocked badges?
A: if your phone was unlocked when you sent it in, youll get it back factory fresh locked. the tampered badge,i am unsure of at this time,and will update as more info is obtained.
if you sent in a brand new phone,it obviously wont be different(with exception of s off)
one of the big advantages of s off,is that the tampered flag is not triggered by adding a custom recovery or kernel,and since s off removes the various write protections that exist,it is posible to reset either flag. more info on the lock status flag here
Q: will an OTA change my s-off or lock status?
A: it is possible. altho,it is highly unlikely since turning the radio secure flags on via an OTA would also do so on legitimate pre-release test phones.
however...
it really is not reccomended that you try and take an OTA while rooted. a custom recovery is unable to install HTC's OTA pacakage,and attempting to do so ca jam you up horribly. taking an OTA with bloat and system files remove will typicaly result in failure,and taking an OTA with supercid could lead to a processor "do not boot" mode,wich is very effectively a hard brick only recoverable via jtag. or a new device.
the best way to update a rooted device is to update the rom with a recovery-flashable zip file,and the firmware extracted from the OTA package. this will update you just like taking the OTA. there is nothing magical about over the air updates. please,just do it manually. leave the OTAs for the stock crowd.
last and not least!
Q:what do i do once i get back my stock,s-off phone?
A: please see post 2
once you have recieved your stock,s off device back,your basic steps are:
1)change CID/MID back to stock
2)install a recovery
3)install a rom or root access
you have 2 options to install recovery:
1)unlock the bootloader and use fastboot commands
2)leave the bootloader locked,and flash a recovery as a zip file in RUU mode
either way works. i personally always keep my bootloader unlocked so i can use fastboot commands,but that is a personal preference.
to "root by recovery" is not a new concept. once there are no write protections,its easy to install a custom recovery,and use that recovery to either insert the superuser files into the stock rom,or replace the rom entirely.
1) change cid back to stock
this is actually very easy. simply put the phone in fastboot,change to fastboot directory,and enter in a cmd window:
fastboot oem writecid xxxxxxxx
in the case of vzw:
fastboot oem writecid VZW__001
yes,those must be capital letters,and there are 2 underscores.
2) install a recovery
via one of these 2 methods:
1)unlock the bootloader
your phone has come back from sonic with "supercid",wich will allow you to unlock the bootloader natuarally via the htcdev website. see this post for a bit more info on that.
unlocking the bootloader is fairly straightforward,just make sure you use a vzw one specific image. download from one of the following threads:
*links provided when available
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
for example,recovery named CW_touch_recovery:
fastboot flash recovery CW_touch_recovery.img
the image must be in your fastboot working directory.
if you need more specific help with unlock/recovery flashing you can use this guide.
2) keep locked bootloader
the bootloader can stay locked for this method. you can in fact use this to install a new image to any partition,as long as the image is packed up in a proper file.
this assumes a working adb/fastboot and drivers installed. if you dont have these things,you can use this guide from above,downloading the files in post 1,and following the set up adb and prepair to root part in step 2.
once you have adb and fastboot working,download one of the following recovery zip files. do NOT unzip or extract.
*links provided when available
your zip file is flashed in the following manner:
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
Click to expand...
Click to collapse
3) install a rom or root access
this is a simple matter of using recovery to either flash superuser,or flash a new rom. in either case,MAKE A BACKUP OF YOUR STOCK UNROOTED ROM!
flash superuser just as you would a rom,after a cache/dalvik wipe. theres tons of info out there on using recovery,so im not going in to great detail on that here.
i dont have this device(well,i dont have the vzw version) so dont ask me whats the best rom to flash. browse the development and original development sections and pick a couple out to try.
if you wish to just run rooted stock,i perosnally prefer superSU to other versions of superuser. you can download it from this thread
_____________________________________________________________________________________________
optional:
if you sent in your phone with a custom recovery installed,and it still is displaying the tampered banner,see this thread to remove it:
*link provided when available
if you want to lock,or unlock your bootloader without messing with htcdev,see this thread for those directions:
*link provided when available
if you want to restore your supermid from 0P6B2**** back to stock ,see this thread:
http://forum.xda-developers.com/showthread.php?p=51677666
_____________________________________________________________________________________________
*work in progress. there will likely be some revisions,but i wanted to get something up for the folks whose devices are coming back
I'm serious considering doing this, if only just so I can have full root. I understand that there won't be any developer support or roms until someone achieves a software exploit. But it would be nice to be able to flash full root.
One question though: I don't have much experience with HTC devices as I always used Samsung before but I'm tired of their locked bootloaders. Basically my question is, one method of s-off is as good as another right? S-off is s-off? And it won't effect my ability to get s-on again? Or use other people's methods for recovery/root and s-off/s-on right?
nicholi2789 said:
I'm serious considering doing this, if only just so I can have full root. I understand that there won't be any developer support or roms until someone achieves a software exploit. But it would be nice to be able to flash full root.
One question though: I don't have much experience with HTC devices as I always used Samsung before but I'm tired of their locked bootloaders. Basically my question is, one method of s-off is as good as another right? S-off is s-off? And it won't effect my ability to get s-on again? Or use other people's methods for recovery/root and s-off/s-on right?
Click to expand...
Click to collapse
Once you are S-Off u are S-Off unless you really screw something up but I have NEVER had any issues and I have owned 4 HTC devices with S-Off via exploits. S-Off is where it's at! Period Will have mine early next week with a Java S-Off... :good: And, we will have a recovery soon enough for our variant so it's just a matter of time before you can flash full root from recovery and then you are good to go. We probably won't see much development until enough people or devs get S-Off or unlocked bootloader. Time will tell but it WILL happen.
shojus said:
Once you are S-Off u are S-Off unless you really screw something up but I have NEVER had any issues and I have owned 4 HTC devices with S-Off via exploits. S-Off is where it's at! Period Will have mine early next week with a Java S-Off... :good: And, we will have a recovery soon enough for our variant so it's just a matter of time before you can flash full root from recovery and then you are good to go. We probably won't see much development until enough people or devs get S-Off or unlocked bootloader. Time will tell but it WILL happen.
Click to expand...
Click to collapse
Thanks for the response. Yeah I've been reading up on S-OFF and all the things you can do to HTC devices since before I got the M8 and still had my S4. I just haven't done any of it yet. It really seems like S-OFF is the only way to go if you want to have complete device freedom. Never had to have anything special to flash radios on Sammy devices. Anyways, yeah I have full faith that we will get S-OFF via an exploit sooner or later. That's why I chose the M8. Because in the past, no matter what, HTC devices always have bootloader exploits it seems like, or at least some development.
This thread is on zero tolerance as of now and will be closed permanently with the next breach of forum rules.
NotATreoFan said:
This thread is on zero tolerance as of now and will be closed permanently with the next breach of forum rules.
Click to expand...
Click to collapse
shojus said:
Click to expand...
Click to collapse
i think they dont want a name given
it also might be the grey market that java cards are. 1/2 this FAQ is not factual, but what do I know? *wink*
dr_drache said:
it also might be the grey market that java cards are. 1/2 this FAQ is not factual, but what do I know? *wink*
Click to expand...
Click to collapse
What is not factual? I'd be happy to correct anything that is not.
Sent from my HTC6435LVW using Tapatalk
scotty1223 said:
What is not factual? I'd be happy to correct anything that is not.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
well, not to go too deep, javacards at the price you posted, are clones of real ones, sold on the grey market. not necessarily legal, using NDA covered files.
dr_drache said:
well, not to go too deep, javacards at the price you posted, are clones of real ones, sold on the grey market. not necessarily legal, using NDA covered files.
Click to expand...
Click to collapse
That number was for a small credit card from the UK. It was supposed to be legit, but I obviously can't prove or verify it.
Thanks for the info
For the record, my main intention is to provide info about the mechanics. Not really trying provide cost or purchase info
Sent from my HTC6435LVW using Tapatalk
scotty1223 said:
That number was for a small credit card from the UK. It was supposed to be legit, but I obviously can't prove or verify it.
Thanks for the info
For the record, my main intention is to provide info about the mechanics. Not really trying provide cost or purchase info
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
So, how do I know if my phone was S-Off'd via a java card or Firewater? What is the difference? TIA
shojus said:
So, how do I know if my phone was S-Off'd via a java card or Firewater? What is the difference? TIA
Click to expand...
Click to collapse
If it comes back supercid and supermid,then it was s offed via the java card. If cid and mid are correct you have no way of knowing for sure,since the cid and mid are easily restored
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
If it comes back supercid and supermid,then it was s offed via the java card. If cid and mid are correct you have no way of knowing for sure,since the cid and mid are easily restored
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure but from pics I seen of exploit don't it throw the tampered flag? As last time I used java card that was not the case
I know that can be restored. I'm guessing he restored cid mid because there were people complaining that he should change this back if you use his services. Just a total guess
Sent from my HTC6525LVW using XDA Premium 4 mobile app
scotty1223 said:
If it comes back supercid and supermid,then it was s offed via the java card. If cid and mid are correct you have no way of knowing for sure,since the cid and mid are easily restored
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
That's my dilemma here... Mine came back yesterday with cid and mid correct.
Tigerstown said:
I'm not sure but from pics I seen of exploit don't it throw the tampered flag? As last time I used java card that was not the case
I know that can be restored. I'm guessing he restored cid mid because there were people complaining that he should change this back if you use his services. Just a total guess
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the java card will not throw the tampered flag. the exploit... i dont think so,but im not 100% sure.
shojus said:
That's my dilemma here... Mine came back yesterday with cid and mid correct and I am a tad skeptical.
Click to expand...
Click to collapse
i would assume that he corrected the cid and mid in order to provide better service. sorry i cant think of any other ways to know for sure.
Me either but I will discuss this elsewhere . Thanks
scotty1223 said:
i would assume that he corrected the cid and mid in order to provide better service. sorry i cant think of any other ways to know for sure.
Click to expand...
Click to collapse
That is what he said to me he did.
Sent from my HTC6525LVW using XDA Premium 4 mobile app