Related
Please please forgive the newb question, but once the bootloader is officially unlocked by HTC's method (basically entering a token you pull from your phone, and then flashing a .bin file they send you based on that token), is it reversible? I.E. is it possible to re-lock it back to factory status? I'm assuming not, but can't find any hard evidence one way or the other...
Apparently someone has said you can re-lock it but I've not used it. Better using Revolutionary IMO
Well you can do a "simple" re-lock just to ensure noone else can make changes to it with "fastboot oem lock" - but it's not the factory lock. The bootloader simply says "re-locked" instead of "unlocked", or compared to the factory "locked".
But I was thinking in terms of reverting it truly back to factory status. Again, I don't think it's possible (without HTC's intervention anyway), given the nature of how it was locked, but need someone smarter than me to confirm that suspicion.
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
jntdroid said:
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
Click to expand...
Click to collapse
I flashed the android revolution rom with my device unlocked through htc website, I cannot flash back to stock, I tried the RUU to bring me back to 1.27 and 1.29 and error'd on both of those. I am not sure how to get back to stock. I tried several times. I also cannot get my security to turn off in the bootloader after I unlocked through htc. Has anyone figured out how to do this? I tried the revoltionary.io tool and successfully used the tool only to reboot and see the S-ON in bootloader mode. CRAZY I suggest for anyone to turn their S-OFF using revolutionary.io before they ever attempt to unlock the bootloader through htc. What I am experiencing is error under the wifi switch I cannot seem to get wifi working with any of the roms, probably due to the kernel or not having s-off in bootloader. I tried different and stock kernels only to have the same problem.
Read this if you want more info: http://forum.xda-developers.com/showthread.php?t=1290395
Has ANYBODY tried the goldcard method to reflash to stock? Take the rom.zip from RUU and flash in bootloader
So ive gone back to stock htc orange ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Gold card doesn't work, otherwise we could've used it before S-OFF
gtcalder said:
So ive gone back to stock htc tmobile ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Click to expand...
Click to collapse
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
droiddv said:
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
Click to expand...
Click to collapse
Hi, list of CIDs for each ROM..
http://forum.xda-developers.com/showthread.php?t=1195475
I am wanting to interop unlock my hd7 running latest mango. i tried the htc unlock xap and the connection setup app (which tells to use interop unlock as country) but to no avail. has anyone been able to get interop unlocked on htc hd7 ?
fearlessdolphin said:
I am wanting to interop unlock my hd7 running latest mango. i tried the htc unlock xap and the connection setup app (which tells to use interop unlock as country) but to no avail. has anyone been able to get interop unlocked on htc hd7 ?
Click to expand...
Click to collapse
Do you have it developer unlocked first?
HTC Have 2 OEM Update after Mango
if you updated your Phone with Second OEM Update, you can not Interop Unlock your phone
yes i have a dev account from app hub.
how do i find out if im running second oem? do you have the build number handy? the os version i have is 7.10.7720.68
It's not the OS build number, people. HTC controls the firmware number, not the OS number (that's Microsoft code). 7720.68 just means the RTM release of Mango. I swear, I write this so often...
If the third digit grouping of your firmware starts with 4 - that is, if your firmware version matches *.*.4XXXX.* - or lower, you can use the HTC Interop Unlock XAP. It *might* even be possible with *.*.50XXX.*, but I don't think so, and it certainly isn't possible with *.*.51XXX.* or newer.
well that helps a lot, ya my firmware shows 51004. so are there any workarounds as of yet?
The only work-around I know of is to downgrade. You can roll back a Zune restore point from before the firmware update(s) was installed, interop-unlock, and then reinstall the updates if you want (I've elected to semi-permanently keep my phone a few versions outdated on firmware). You could also flash a stock ROM that includes an older firmware. Be aware, however, that either option will lose some data - everything newer than the backup if you restore, everything on the phone if you flash a stock ROM.
GoodDayToDie said:
The only work-around I know of is to downgrade. You can roll back a Zune restore point from before the firmware update(s) was installed, interop-unlock, and then reinstall the updates if you want (I've elected to semi-permanently keep my phone a few versions outdated on firmware). You could also flash a stock ROM that includes an older firmware. Be aware, however, that either option will lose some data - everything newer than the backup if you restore, everything on the phone if you flash a stock ROM.
Click to expand...
Click to collapse
Hey thanks for the information, I was wondering if there were any guides you can point me to on how to flash from a stock ROM. I have an HTC HD7.
Thanks again for your help. i know sometimes its tiring explaining the same thing over and over, but it is much appreciated.
Go to the HD7 ("Schubert") portion of the XDA-Devs wiki (http://forum.xda-developers.com/wiki). I'm pretty sure you can find the download links for stock ROMs there. You could also try the HD7-specific forum section. You'll download a tool called a RUU (ROM Update Utility) that will have some image files (extensions like .NBH and .NB) along with it. You put the phone in bootloader mode (four bars of different color - you have to boot the phone while holding the Volume Down button). It should have yellow text, and at the bottom should say "Serial". Connect the phone to USB. Your PC will need to install a driver (normally this will happen automatically, if not, use Device Manager to tell the computer to search Windows Update for the driver). Once the driver is installed, the "Serial" will be replaced by "USB". You can now run the RUU program.
I *strongly* recommend creating a backup first! The RUU will wipe all data on the phone, and if the flash fails for whatever reason, you'll be unable to boot the phone again.
Ok Thanks, That was helpful. i read a few guides and I think Im ready to try. i just wanted to ask a quick question before diving in. Hope you dont mind. Some threads make refrences to certain Bootloaders being unable to go through the downgrade process (by flashing a Stock Rom). Is this correct? My bootloader version is:
5.10.2250.0(132968)
If it doesnt matter than are there any other things that would prevent me from doing this process?
And one more question and I promise to leave you alone lol. I plan on backing up my phone before beginning, but if the flash fails for whatever reason and the phone is unable to boot again as you warned, will I still be able to connect it to Zune and restore my backup? Thanks again. Hopefullyone day I can give more to the community once I get used to it.
Booting the phone while holding the Camera button will put it in backup/restore mode. If you connect the phone to the PC while it is in this mode, and the Zune software is running, it should automaticlaly try to restore.
Your bootloader (SPL) version is too high to install HSPL (needed for custom ROMs), and it's high enough that it won't automatically downgrade just by installing a stock ROM. However, you should be able to install the other parts of a stock ROM (in particular, the firmware) just fine.
If needed, there are a couple ways to downgrade the SPL; search the dev&hacking sub-forum for info. I would generally recommend GoldCard, but that will require a little bit of equipment. Apparently, "SLSPL" flashing will allow you to downgrade the SPL safely as well, though I haven't tried it. These are mostly for preparing to install a custom ROM, though - stock ROMs should be installable on any SPL version.
it not work with my trophy verizon
GoodDayToDie said:
Booting the phone while holding the Camera button will put it in backup/restore mode. If you connect the phone to the PC while it is in this mode, and the Zune software is running, it should automaticlaly try to restore.
Your bootloader (SPL) version is too high to install HSPL (needed for custom ROMs), and it's high enough that it won't automatically downgrade just by installing a stock ROM. However, you should be able to install the other parts of a stock ROM (in particular, the firmware) just fine.
If needed, there are a couple ways to downgrade the SPL; search the dev&hacking sub-forum for info. I would generally recommend GoldCard, but that will require a little bit of equipment. Apparently, "SLSPL" flashing will allow you to downgrade the SPL safely as well, though I haven't tried it. These are mostly for preparing to install a custom ROM, though - stock ROMs should be installable on any SPL version.
Click to expand...
Click to collapse
Hey thanks again! Im going to try it out today, cross fingers, Ill let you know how it all went. I appreciate the help.
Well?? Did it work? Would really like to know before I attempt the same
Thanks
did it work ????
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.
Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?
Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.
you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.
srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers
srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?
Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita
Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Have you checked your APNs?
Sent from my Evita
srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.
It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers
Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.
Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.
Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......
So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.
I just picked up an HTC One A9 open box off of Amazon that was labeled as an unlocked phone. After receiving it, it is actually an AT&T branded phone. I'm contemplating returning it, but if I can get it to work like a normal unlocked device I'll keep it. I am on AT&T for my service but despise having any carrier branded devices. I'm coming to the A9 from a Nexus 5 and a Moto X Pure. I got sick of the huge size of the MXP and have been back on my Nexus 5 with the last nightly of CM before it shutdown. I picked the A9 for a few specifics. I got it cheap, it has fingerprint sensor, FM radio (I have a farm in rural OK that has poor cell so the FM radio was a big incentive to buy), smaller screen and expandable storage.
So, I've been reading the A9 sub-forum here and have a few questions if anyone could be kind enough to help me out and clear things up.
1. How can I tell if the device I got is carrier unlocked?
2. Can I unlock the bootloader like normal and install other ROMs?
3. Can I download the official HTC Firmware for unlocked/developer A9 and flash it on what appears to by my AT&T device?
4. S-Off, not sure where to begin. Is this required to flash other ROMs, or just to flash other radios, recoveries etc? If I'm going to have to pay $25 for additional software I'll most likely be returning the device.
5. CyanogenMod now Lineage OS - I was running this on my Nexus and want to do the same with the A9, or at least try it out. Is S-Off required to run CM/LineageOS?
6. FM radio - did AT&T remove the app from their device? I just downloaded NextRadio Free Live FM Radio from the app store and it looks to be able to access the FM tuner and work, but I'd prefer the stock HTC app.
Sorry for so many questions, but it looks like the community here on XDA for this device is pretty small with sparse/spread out information and I'm having trouble finding what I need.
Any help is greatly appreciated!
Sympl3x said:
I just picked up an HTC One A9 open box off of Amazon that was labeled as an unlocked phone. After receiving it, it is actually an AT&T branded phone. I'm contemplating returning it, but if I can get it to work like a normal unlocked device I'll keep it. I am on AT&T for my service but despise having any carrier branded devices. I'm coming to the A9 from a Nexus 5 and a Moto X Pure. I got sick of the huge size of the MXP and have been back on my Nexus 5 with the last nightly of CM before it shutdown. I picked the A9 for a few specifics. I got it cheap, it has fingerprint sensor, FM radio (I have a farm in rural OK that has poor cell so the FM radio was a big incentive to buy), smaller screen and expandable storage.
So, I've been reading the A9 sub-forum here and have a few questions if anyone could be kind enough to help me out and clear things up.
1. How can I tell if the device I got is carrier unlocked?
2. Can I unlock the bootloader like normal and install other ROMs?
3. Can I download the official HTC Firmware for unlocked/developer A9 and flash it on what appears to by my AT&T device?
4. S-Off, not sure where to begin. Is this required to flash other ROMs, or just to flash other radios, recoveries etc? If I'm going to have to pay $25 for additional software I'll most likely be returning the device.
5. CyanogenMod now Lineage OS - I was running this on my Nexus and want to do the same with the A9, or at least try it out. Is S-Off required to run CM/LineageOS?
6. FM radio - did AT&T remove the app from their device? I just downloaded NextRadio Free Live FM Radio from the app store and it looks to be able to access the FM tuner and work, but I'd prefer the stock HTC app.
Sorry for so many questions, but it looks like the community here on XDA for this device is pretty small with sparse/spread out information and I'm having trouble finding what I need.
Any help is greatly appreciated!
Click to expand...
Click to collapse
1- you will need another sim card
2- yes. But you will most likely need to s-off and convert to USA unlocked to get newer firmware. USE ONLY 1.57! Do not upgrade to nougat if you would like to use custom roms or have root.
3-yes, but s-off must be purchased from HTTP://www.theroot.ninja
4-yes you will most likely need to pay the $25 utility from the website above.
5-yes, unless you want to run the one from January 2016
6- yes at&t did remove the app BC they are stupid, you also cannot access it from CyanogenMod or lineagos
Also, I think you can still download CyanogenMod from get.cm. if not hmu, I have a copy.
If you want to know how to convert to USA unlocked, I can help you.
Boot logo is not mean the carrier lock, try your sim it may work.
Try booting into download mode and check the cid and mid. And see if they match the AT&T model, Also see if it is s-off or not. Chances are it is a converted phone. If not then follow the steps mentioned above
The_scam said:
1- you will need another sim card
2- yes. But you will most likely need to s-off and convert to USA unlocked to get newer firmware. USE ONLY 1.57! Do not upgrade to nougat if you would like to use custom roms or have root.
3-yes, but s-off must be purchased from HTTP://www.theroot.ninja
4-yes you will most likely need to pay the $25 utility from the website above.
5-yes, unless you want to run the one from January 2016
6- yes at&t did remove the app BC they are stupid, you also cannot access it from CyanogenMod or lineagos
Also, I think you can still download CyanogenMod from get.cm. if not hmu, I have a copy.
If you want to know how to convert to USA unlocked, I can help you.
Click to expand...
Click to collapse
Thanks for all the info. I was able to unlock the bootloader but it seems like that was fairly pointless. I downloaded the TWRP and when I try to flash from fastboot it is unable to write the new recovery because S-on. So really there is no way to flash custom ROMs even with an unlocked bootloader without S-off. Am I correct? Before I purchase the S-off tool I'm going to contact Amazon and see what they can do since they clearly mislabeled the item listing. Thanks again for the help. I'll let you know if I decide on doing the conversion.
anunknwon said:
Boot logo is not mean the carrier lock, try your sim it may work.
Click to expand...
Click to collapse
I have an AT&T sim so all is fine. I took the Amazon listing as a fully unlocked device but it looks to just be a AT&T carrier unlocked device.
MGfusion said:
Try booting into download mode and check the cid and mid. And see if they match the AT&T model, Also see if it is s-off or not. Chances are it is a converted phone. If not then follow the steps mentioned above
Click to expand...
Click to collapse
In download mode I have the following info. I don't see any CID or MID numbers.
*** UNLOCKED ***
htc_hiaeul PVT S-ON
LK-1.0.0.0000
RADIO-1.0.U00297.1[email protected]
OpenDSP-6.8.5.00190-8952_1013
OS-1.27.502.5
Nov 12 2015,15:40:38(656287)
Sympl3x said:
Thanks for all the info. I was able to unlock the bootloader but it seems like that was fairly pointless. I downloaded the TWRP and when I try to flash from fastboot it is unable to write the new recovery because S-on. So really there is no way to flash custom ROMs even with an unlocked bootloader without S-off. Am I correct? Before I purchase the S-off tool I'm going to contact Amazon and see what they can do since they clearly mislabeled the item listing. Thanks again for the help. I'll let you know if I decide on doing the conversion.
I have an AT&T sim so all is fine. I took the Amazon listing as a fully unlocked device but it looks to just be a AT&T carrier unlocked device.
In download mode I have the following info. I don't see any CID or MID numbers.
*** UNLOCKED ***
htc_hiaeul PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-6.8.5.00190-8952_1013
OS-1.27.502.5
Nov 12 2015,15:40:38(656287)
Click to expand...
Click to collapse
You don't flash things from fastboot/bootloader. If you want to flash use "ADB reboot download" or boot while holding power+volume down
Sympl3x said:
Thanks for all the info. I was able to unlock the bootloader but it seems like that was fairly pointless. I downloaded the TWRP and when I try to flash from fastboot it is unable to write the new recovery because S-on. So really there is no way to flash custom ROMs even with an unlocked bootloader without S-off. Am I correct? Before I purchase the S-off tool I'm going to contact Amazon and see what they can do since they clearly mislabeled the item listing. Thanks again for the help. I'll let you know if I decide on doing the conversion.
I have an AT&T sim so all is fine. I took the Amazon listing as a fully unlocked device but it looks to just be a AT&T carrier unlocked device.
In download mode I have the following info. I don't see any CID or MID numbers.
*** UNLOCKED ***
htc_hiaeul PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-6.8.5.00190-8952_1013
OS-1.27.502.5
Nov 12 2015,15:40:38(656287)
Click to expand...
Click to collapse
It is an unlocked phone, but not converted. That is still running the AT&T software and still s-on. Lime I said, the steps are posted above to convert. If you have anymore questions feel free to ask
Did you try to flash recovery in bootloader mode? in my case download mode doesnt work either but when I flash in bootloader mode it went through (without s-off)
The_scam said:
You don't flash things from fastboot/bootloader. If you want to flash use "ADB reboot download" or boot while holding power+volume down
Click to expand...
Click to collapse
Sorry, yes I was in download mode. I wasn't thinking clearly though and was trying to flash recovery before unlocking the bootloader through HTCDev. I got TWRP installed successfully earlier today.
MGfusion said:
It is an unlocked phone, but not converted. That is still running the AT&T software and still s-on. Lime I said, the steps are posted above to convert. If you have anymore questions feel free to ask
Click to expand...
Click to collapse
Good news is I was able to contact Amazon support and tell them about the incorrect item listing. I talked them into giving me a 25% refund on my purchase for the mistake. With that credit I got Sunshine purchased and have succesfully installed SuperSU and completed S-OFF on the latest RUU for AT&T. This evening I'll see if I can complete the conversion process and get over to the unlocked/developer RUU.
anunknwon said:
Did you try to flash recovery in bootloader mode? in my case download mode doesnt work either but when I flash in bootloader mode it went through (without s-off)
Click to expand...
Click to collapse
See above. I forgot to unlock bootloader first. Once I did that I was able to flash via ADB just fine.
Thanks again to everyone for the help.
Cool, and you are so lucky
Sympl3x said:
Sorry, yes I was in download mode. I wasn't thinking clearly though and was trying to flash recovery before unlocking the bootloader through HTCDev. I got TWRP installed successfully earlier today.
Good news is I was able to contact Amazon support and tell them about the incorrect item listing. I talked them into giving me a 25% refund on my purchase for the mistake. With that credit I got Sunshine purchased and have succesfully installed SuperSU and completed S-OFF on the latest RUU for AT&T. This evening I'll see if I can complete the conversion process and get over to the unlocked/developer RUU.
See above. I forgot to unlock bootloader first. Once I did that I was able to flash via ADB just fine.
Thanks again to everyone for the help.
Click to expand...
Click to collapse
One thing!! Don't flash the nougat RUU. Just flash the 1.57 RUU if you want to use custom roms, as anything above 1.57 is newer firmware that is not compatible with custom roms at this time and is not downgradeable.
The_scam said:
One thing!! Don't flash the nougat RUU. Just flash the 1.57 RUU if you want to use custom roms, as anything above 1.57 is newer firmware that is not compatible with custom roms at this time and is not downgradeable.
Click to expand...
Click to collapse
Noted! Thanks