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
Related
Hey, I'm kind of a noob here. Where do I get fastboot.exe from? Im stuck on step 11 in the "[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev" thread
you need to download the android sdk, it has it in there as stated in the htcdev unlocking instructions
Thanks, I was able to get it to work once the one click unlock tool was posted.
Sent from my HTC One X using Tapatalk 2
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
xeper said:
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
Click to expand...
Click to collapse
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
HydroSkillet said:
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
Click to expand...
Click to collapse
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Maybe, who knows on the "tampered" and yea you void your warranty so if you are afraid of hardware failure then don't do it, or but insurance on it. That's what I have, if I brick it cost me 100.00 rather than 600.00.
"Waiting for device"
Every attempt and different ways always brings me to that part. I have does the oneClick supercid program and I've even gone through the HTCDEV website 6 times now. after it reboots into boot loader mode and I direct it to the folder with the 3 files in it through cmd and I get to the final step to where it says "Waiting for device" trying to get the cid codes for my phone and nothing. I am at the end of my ropes of how to unlock codes. if anyone can help me or walk me through via text or video I would be so happy. I just want this thing finally unlocked and over with.
I take it your on this step?
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
12. Next type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there. Choose "All other supported models" from the dropdown menu.
If so, Step 11 is kinda tricky worded after you type the command to reboot the device. Just don't even wait put the second line in "fastboot oem readcid" the batch file will wait for the phone. I hope this helps ya I had the same problem before And booted the phone back up and tried again but last time I just rebooted with the command then right after than put in the second command.
xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Devs will find a way to remove tampered label once we find S-OFF. After the device has been "tampered", if your phone breaks and you send it to HTC warranty, they will not replace your phone if you have flashed a custom ROM on it. How they know you've flashed a custon ROM, I'm not sure.
SuperCID is the development CID designed to work on HTC phones. It allows you to unlock your bootloader through HTCDev.com. It also allows you to flash RUUs, because RUUs check CIDs on phones to determine whether the RUU is a valid ROM for your phone. However, it has been said this is hit/miss.
Don't take my exact word for it, use GOOGLE.COM.
I waited for the one-click tools, and I'm glad I did.
Forgot to mention
my Main computer is my iMac and I have a windows 7 laptop I switch to for my flashing/rooting etc... because I am not good with terminal or adb steps after a few seizures I've had recently. So shell stuff is completely useless to me. I can follow the steps on the briefmobile website then I have the HTCDEV account. but still at a lost.. for some reason.
I never got a 1111111 or whatever message
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
hazmatik said:
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
Click to expand...
Click to collapse
You should just use the one-click Super-CID tool in the Developers section, it's much faster and hassle free.
Thanks but that option never succeeded
I finally got it to unlock and get past that "Waiting for device issue" it seems even though I had my device plugged in and all the android and HTC drivers installed, it never registered that it could sense android 1.0 plugged in. so I had to manually right click and force it to install the drivers and it finally found device. low and behold it clicked and I got my email instantly right afterwards. So now I need how on installing CWM any ideas how to? be I am wanting to try out Team nocturnal's Rom for a little bit to see what it has to offer. Thanks for comment also by the way.
i just want a stock rom and also want the htc logo in the beginning not to display for development purposes only. can someone point me to the right direction?
You should look for one of the RUU's in the dev forum that's specific to your carrier. Past that, you're going to be best off looking at how other custom boot animations are done, and see if you can divine any information from that process that might help you just remove the HTC one. I don't know of anyone that's just straight removed the animation without replacing it.
trunicated said:
You should look for one of the RUU's in the dev forum that's specific to your carrier. Past that, you're going to be best off looking at how other custom boot animations are done, and see if you can divine any information from that process that might help you just remove the HTC one. I don't know of anyone that's just straight removed the animation without replacing it.
Click to expand...
Click to collapse
i meant just remove the words that say this is for development purposes only and something about legal action
You'll need to grab a stock RUU pertaining to your carrier and relock your bootloader through fastboot oem lock, though if you want the bootloader unlocked and the message removed, you'll need S-OFF, which hasn't been achieved for the S4 One X yet.
Protogon said:
You'll need to grab a stock RUU pertaining to your carrier and relock your bootloader through fastboot oem lock, though if you want the bootloader unlocked and the message removed, you'll need S-OFF, which hasn't been achieved for the S4 One X yet.
Click to expand...
Click to collapse
I don't think this is true. If you just unlock and manually debloat e message does not appear. However if you install any time of a custom ROM you will get this message
To the OP:
adb reboot bootloader
Go into fastboot hook up a USB cable
fastboot oem lock
At this point the phone will reboot and go into a bootloop, this is normal do not panick
Run the appropriate RUU
Root the phone junlock etc per guide in sticky in dev forum
Debloat MANUALLY I usually do it with TWRP in recovery mode
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
This is my first post here, and I'm hoping somebody could help me with some questions I have.
I have recently bought a "new" HTC one s on ebay, which may seem to have been a bad idea. I have later discovered that it is not a z520e (snapdragon s4), but the cheaper z560e (snapdragon s3) version, or villec2 running android 4.0.3.
Anyway, I have tried to upgrade the phone to the latest android version, using the built in phone function. However, this did not work and I got an error message telling: "We have determined that your phone may be running modified version of its system software...". In other words, I have the feeling that the phone is tampered with. Maybe the seller have unlocked in a way that makes it impossible to upgrade. Is there anything I can do to check this? And is there anything i can do to upgrade to android 4.1.1. ? I have tried a factory restore (phone function) with no luck. Or is the update only available to Asia?
Any information is very appreciated. I would like to know what the seller have done with this phone, information which I can use against the seller. Thanks!
staldor said:
Hi
This is my first post here, and I'm hoping somebody could help me with some questions I have.
I have recently bought a "new" HTC one s on ebay, which may seem to have been a bad idea. I have later discovered that it is not a z520e (snapdragon s4), but the cheaper z560e (snapdragon s3) version, or villec2 running android 4.0.3.
Anyway, I have tried to upgrade the phone to the latest android version, using the built in phone function. However, this did not work and I got an error message telling: "We have determined that your phone may be running modified version of its system software...". In other words, I have the feeling that the phone is tampered with. Maybe the seller have unlocked in a way that makes it impossible to upgrade. Is there anything I can do to check this? And is there anything i can do to upgrade to android 4.1.1. ? I have tried a factory restore (phone function) with no luck. Or is the update only available to Asia?
Any information is very appreciated. I would like to know what the seller have done with this phone, information which I can use against the seller. Thanks!
Click to expand...
Click to collapse
When the phone is off, press and hold volume down then press power button (don't hold).
This will let you enter bootloader.
Top of the screen if it says unlocked, that is why you cannot update.
I'm guessing you do not know about fastboot commands/ adb commands and are not interested in learning to root and load custom ROMs to your phone.
But if it is unlocked and you want to relock it you just need to type in a command prompt: fastboot oem lock
that is assuming that the stock recovery hasn't been changed. (which isn't hard to flash)
In this guide you would want to download that fastboot.rar file
http://forum.xda-developers.com/showthread.php?t=2175411
As this is a question, I've moved this thread to the Q&A, Help & Troubleshooting section.
In future, please remember to ask any questions in this section rather than in General.
Thanks
Sent from my HTC One using XDA Premium 4 mobile app
tivofool said:
When the phone is off, press and hold volume down then press power button (don't hold).
This will let you enter bootloader.
Top of the screen if it says unlocked, that is why you cannot update.
I'm guessing you do not know about fastboot commands/ adb commands and are not interested in learning to root and load custom ROMs to your phone.
But if it is unlocked and you want to relock it you just need to type in a command prompt: fastboot oem lock
that is assuming that the stock recovery hasn't been changed. (which isn't hard to flash)
In this guide you would want to download that fastboot.rar file
http://forum.xda-developers.com/showthread.php?t=2175411
Click to expand...
Click to collapse
First of all, sorry for the posting in the wrong category.
You have right that i have no experience rooting android phones. However, i managed to jailbrake an iPhone 1st gen in the old days.. Anyway, my main concern is to try to find out what this phone is running, and if I should send it back or not. I paid 260 usd, so I would like the phone to be ok/not too much tampered version.
I got into fastboot / Hboot, and it says unlocked. What does unlocked actually means? I also got some red text when i started the phone afterwords telling that it was some non officially software that were not allowed to be distributet (went a bit fast).
I guess this is the reason why I cant update. Is there some more information I can take out of this Hboot? (I tried to find a hboot guide.) Any ideas why the seller sold me an unlocked phone? And is there something i should make sure of before I decide to keep the phone? I might send it back if there is some tampered things here.
Thanks again for you feedback!
staldor said:
First of all, sorry for the posting in the wrong category.
You have right that i have no experience rooting android phones. However, i managed to jailbrake an iPhone 1st gen in the old days.. Anyway, my main concern is to try to find out what this phone is running, and if I should send it back or not. I paid 260 usd, so I would like the phone to be ok/not too much tampered version.
I got into fastboot / Hboot, and it says unlocked. What does unlocked actually means? I also got some red text when i started the phone afterwords telling that it was some non officially software that were not allowed to be distributet (went a bit fast).
I guess this is the reason why I cant update. Is there some more information I can take out of this Hboot? (I tried to find a hboot guide.) Any ideas why the seller sold me an unlocked phone? And is there something i should make sure of before I decide to keep the phone? I might send it back if there is some tampered things here.
Thanks again for you feedback!
Click to expand...
Click to collapse
HTC allows to unlock the bootloader from their website. You are sent an unlock bin code. Unlocked means you can root the phone, you can put on a custom recovery to make backups of your phone and put custom ROMs on it.
If yours said unlocked, and right below that if it did not say tampered, then i believe you still have the stock recovery.
you just need to download fastboot files to your pc then you can lock your bootloader.
you go back into bootloader and plug your phone into computer (phone will change from fastboot to fastboot usb)
from your fastboot folder you hold down shift and right click the mouse, choose the option to open a command prompt.
from there you just type
fastboot oem lock
tivofool said:
HTC allows to unlock the bootloader from their website. You are sent an unlock bin code. Unlocked means you can root the phone, you can put on a custom recovery to make backups of your phone and put custom ROMs on it.
If yours said unlocked, and right below that if it did not say tampered, then i believe you still have the stock recovery.
you just need to download fastboot files to your pc then you can lock your bootloader.
you go back into bootloader and plug your phone into computer (phone will change from fastboot to fastboot usb)
from your fastboot folder you hold down shift and right click the mouse, choose the option to open a command prompt.
from there you just type
fastboot oem lock
Click to expand...
Click to collapse
Thanks for the reply!
Yes, i cannot see any "tampered" below the *** unlcoked *** line in HBOOT.
I tried the recovery in the HBOOT but got a red triangle. I guess i need to to this from an PC (I have macbook at home, or do I need the Andorid SDK on my computer maye..), and download the right android image etc. I also guess the factory reset will not help me either (probably the same function I can choose from the settings menu in android.).
Now my question is if I should try to change it to a z520e. I guess i will get some more battery life with the snapdragon s4. But not sure how much, and if its worth the hassles with return shipping etc.
Anyways, thank you very much for the information!
please help me. i dont know what to do with this cell... anyhow i managed to get it into this screen...
it would keep restarting after displaying htc quietly brilliant.
i have no idea what was done to this cell as i got it lying around in my closet.
What do you mean you got it lying around in my closet? You don't know what you did to it in the past?
Sent from my Evita
no actually my cousin might have screwed up my cell and kept it back...
timmaaa said:
What do you mean you got it lying around in my closet? You don't know what you did to it in the past?
Sent from my Evita
Click to expand...
Click to collapse
Well I think the first thing you should do is talk to your cousin and find out exactly what he did to the device, then you can report back here.
Sent from my Evita
is there any other way through which we can come to know what can be done??? such as an odin thing which i used to do in my samsung note 1 or 3???
timmaaa said:
Well I think the first thing you should do is talk to your cousin and find out exactly what he did to the device, then you can report back here.
Sent from my Evita
Click to expand...
Click to collapse
To know what needs to be done I need to know the history of the device. Odin is Samsung only, there is no HTC equivalent. Who got the phone to this point, you or your cousin? You need to find out what he's done.
Sent from my Evita
Well, one problem is that the screen is cracked.
Seriously though, the phone for some reason or other cannot load into the OS, and is stuck in bootloader. Other than that, not much else can be determined if you don't know the history of what was done.
pvirus86 said:
is there any other way through which we can come to know what can be done??? such as an odin thing which i used to do in my samsung note 1 or 3???
Click to expand...
Click to collapse
Nope. You need to know the history of the device. There is an HTC-specific recovery utility. But running it on a device with unknown history can brick the phone permanently. Particularly since the device is definitely tampered (as shown on the first line of the screen).
Also, the phone's IMEI is personal information, and should not be posted on the internet. You should edit the photo to hide the IMEI.
Unlock your bootloader. Sometimes if you have custom installed or fragments of a custom ROM on the device it will boot directly into your bootloader. After unlocking your bootloader you can install a recovery image and sideload a ROM.
yes i asked my brother and he is saying he doesnt remember what he had done to it... if anyone can show me a way to do something ill try it... or else should i take it to some shop to get it fixed.... which would cost me... but first i wanted to get my hands over d expert advise of u all
Return the phone to stock and never let your brother touch any electronic device of yours again.
Sent from my Evita
but can you let me know to revert it to stock. and will i have to do it from windows 7 or my mac os wud work???
pvirus86 said:
but can you let me know to revert it to stock. and will i have to do it from windows 7 or my mac os wud work???
Click to expand...
Click to collapse
This phone is in a dangerous state.. Running the RUU in this state could brick the phone (make it permanantly unusable without a jtag). Though typically that is how one would return a phone to stock.. to be honest, the safest thing to do would be to unlock the bootloader, flash a rom, S-OFF and then return it to stock. If these seem like foreign terms to you, you have a lot of reading to do. Your phone is in a tough spot right now ESPECIALLY not knowing the history regarding what was done. You would need the bootloader unlock token to reunlock that phone if you don't have it, there's very little chance of safely returning that phone to stock.
pvirus86 said:
yes i asked my brother and he is saying he doesnt remember what he had done to it...
Click to expand...
Click to collapse
Brother or cousin, or both? It seems you don't even know who has been messing with your phone. And the person(s) messing with it don't have a clue what they are doing. So its no wonder the phone is in the state it is.
Agree with above that RUU is risky. Better to s-off the phone first.
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader n turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
pvirus86 said:
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader not turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
Click to expand...
Click to collapse
There are detailed instructions available at htcdev for unlocking your bootloader. Once you've done that you need to flash a custom recovery, then you can flash root, then you can get s-off. Check my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita
pvirus86 said:
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader n turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
Click to expand...
Click to collapse
Every device manufaccturer/model has different root methods. If you want to root the phone, you have to put the time in to learn the correct process. There is no shortcut. You won't find a step-by-step guide for the entire process, because of the different carrier version and firmware updates (root method, etc. differs for each). But all the resources you need are sticky at the top of either this Q&A forum section, or General section.
hi i tried to get to unlock the bootloader from the HTCDEV site. first of all the HTC ONE X wasnt on the list so i selected other supported devices
then followed the steps and got the following error
Error Code: 160.
Error Reason: MID Not Allowed.
now what does this mean??
That means you have the original CID still, which means you should be able to run the 3.18 RUU without any problems. Check your CID by issuing this fastboot command:
Code:
fastboot oem readcid
Sent from my Evita
yes i had issued this command after finding it in one of the websites and this was the result which i got
cid: CWS__001
or cid: c??__001
i forgot the exact two letter after C. i think it was CWS
You have the original at&t CID. That means you can run the 3.18 RUU without having to unlock the bootloader and get s-off first.
Sent from my Evita