Database Info

[Q] CID

Hi ,
Wanting to get rid of 3 uk junk and flash to normal UK RUU
Do we need super CID?
My bootloader is unlocked , can't download the RUU from from the Dev section as all the slots are gone , or when it seems to work it errors out .
Has anyone got the latest UK RUU file they can share with me and can someone confirm if I need Super CID to run RUU to unbrand
Thanks in Advance

Just flash Modaco or the Virtuous roms through recovery, these are unbranded and really good.
You will need to flash a Recovery image first though.

Hi and thanks
Yes , I understand this but I want to just unbrand through RUU then re-lock my bootloader.
Do we need Super CID ?

Ok can someone remind me if I need S-Off to change the CID , playing around with ADB at the moment

If Im honest mate, no idea what you mean by CID...
But if you want a new rom, all that needs to be done is unlock bootloader, flash recovery, flash rom.
Thats all anyone has done in the dev threads, and worked fine for me (coming from a retail, unbranded unit).
You can 'lock' the bootloader again, BUT it never goes back to its true original state. This is as HTC designed their unlocking/locking process to be (and is stated in their terms when you go to their site to unlock).
Edit: OK, just read up on it. Possibly then! Depends how annoying 3 are I suppose... Probably best to ask one of the devs
Edit 2: CHeck the following, may be of help (though its for the One X)
http://forum.xda-developers.com/showthread.php?t=1594262
http://android.modaco.com/topic/353106-debrand-one-x/
Edit 3: If you're applying a flashable zip, does the CID limitiation on RUUs even come into play?

Hi thanks ,
Yea what I want to achieve is this .
My CID is HG3____001 this will need to be changed to a CID that is HTC UK specific usually HTC_____001
To find out your CID in ADB
Fastboot Getvar CID
To get to a retail version from a branded version , what usually needed to happen was this .
Unlock bootloader , change CID to 11111111 via ADB
Run the specific UK RUU.exe
Change your CID to the HTC_____001 which is the usual default for UK unbranded devices .
re-lock your bootloader and then you should receive OTA updates from HTC instead of your network supplier which can take months
I can't remember if S-off was needed to do this. I have just checked revolution site and One s is not listed , will play around tonight though and see
Thanks for the help so far

Hi, I know what CID is - coming from the Sensation.
I dont think its possible to change CID without S-OFF, you cant use advanced ADB functions with S-ON
Until revolutionary or someone else makes tool for S-OFF, we will just have to stick with HTCDev, Its not the best, but it allows to flash recovery and ROMs so its better than nothing.
Im pretty sure there will be some progress in the next few weeks, Once the phone is available worldwide

Ahh ok , thanks , yea this phone is set S- on , so S-off will be needed sooner or later

yeah, as development develops and more rights are needed from the phone, S-0FF will eventually be a MUST.
I wish it was available already, I hate the fact that HTC know i have tampered with my HBOOT and voided my warranty.
Luckily enough, if i have a problem, my provider fixes / repairs the phone, Not HTC, So i might just get off lightly

I think HTC will know if you have tampered with the phone period if they wish to look that far into it .
Unless you fry your processor where you have set it too high etc then shouldn't be a problem. If you have a hardware problem such as your screen fails , battery etc then should be fine .
As you say though , if you brought it through a retail unit then that is where it is returned so in some respects is a bit easier as they will use a third party repairer acting for HTC .

well with the sensation it was possible to return everything back to stock, Including the bootloader and S-ON..
There was no way it could be diagnosed as being tampered with, If you did it properly..
But with HTCDev. youve already submitted a code (which i assume contains serial number) so all they have to do is check whether that device matches anything on their database of tampered devices. Thats why i dislike it so much..
But i need root for most of my apps so there was no workaround for me...

I see on the One X forum S-off is under way . Can't wait to get this baby to true stock.
Just did another Google search for S-Off on the S but nothing as yet .

[Q] RUU to go back stock

I know there are several threads like this one but I prefer not to write another RUU request while you're answering to another user
So, I got a HTC One S S3 yesterday... I began to unlock it because I wanted to change its CID. I found that in the S3 version the CID can't be changed (still) when I had already installed the TWRP Recovery.
Now I'd like to go back to stock, but there is not a RUU compatible with my device: It has VODAP102 as CID, but the RUU for Vodafone AT here doesn't work. I found the kernel source for the same software version I have in htcdev.com, my question is: is it possible to build a RUU or at least a boot.img from it?
The sources can be found in htcdev /devcenter/downloads (sorry but being new I can't post direct links!), HTC One S as Device, Vodafone as Carrier and UK -
1.11.161.133 as software version. Actually I am in Italy, but the software and kernel version are exactly the same.
Thank you in advance.

Bump to first page and a little addendum:
I've read again all the possibilities I have with this phone, and if I have understood accurately then I'm forced to go back to stock, roms like the ThickDroid seem to require a non-branded CID, but that's the point... it is the CID that's compelling me to maintain this original Vodafone software, otherwise I would have already installed the HTC "basic" rom.
Am I missing something?
Thank you again!

Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM

mikejasonsmith said:
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
Click to expand...
Click to collapse
Yes I checked, but they have just unbranded RUUs, here in the forum there's one RUU for Vodafone but the region isn't the same as mine.

I've read that it is possible to flash an OTA update deleting the string that checks the CID - I'll have to take a look about that (moreover, it seems very difficult to find .zip OTA updates for this phone...).
Nevertheless I'd like to find this RUU update too - it is an important option too. So... bump to first page.

[Q] Warranty [How to?]

Hello I'm about to send my phone for a repairs to HTC. I'm currently rooted, tampered, s-on and with custom CID 111...
Any suggestions what I need to do? I mean I'll lock the bootloader and install stock RUU but is it enough? Or nothing will help they'll know that it was rooted?

Your bootloader will still show RELOCKED... The only way would be S-OFF.
And don't forget to replace the CID.

nor-ric said:
Your bootloader will still show RELOCKED... The only way would be S-OFF.
And don't forget to replace the CID.
Click to expand...
Click to collapse
So first of all I need to S-OFF and only then replace CID to stock?
Because to S-OFF it says "you must have supercid"

Exactly!

nor-ric said:
And don't forget to replace the CID.
Click to expand...
Click to collapse
But what do I change it to? Because unfortunately I don't remember my original CID
Because it used to say H3G (network code) and now I installed some european RUU

Is (was) your phone branded? Also, which country are you from?

nor-ric said:
Is (was) your phone branded? Also, which country are you from?
Click to expand...
Click to collapse
United Kingdom, if you mean was it bought from network provider then yes it's branded.
P.S. some people told me to do: fastboot oem writecid, is it correct, will it change it?

cikoleko said:
United Kingdom, if you mean was it bought from network provider then yes it's branded.
P.S. some people told me to do: fastboot oem writecid, is it correct, will it change it?
Click to expand...
Click to collapse
Yes, it's correct. I suggest that you use Hasoon's All In One Toolkit, though: it helps a lot automating things (avoiding command line) if you are not very familiar with these things. You can find it in the development subforum.
The point is writing the correct CID. Do you remember if your software was customized by your carrier (e.g. with carrier-related apps)? Do you have your carrier name physically printed on the phone? Not all phones sold by carriers are branded: for example, I bought it from H3G but it's unbranded.
If this wasn't the case, I would go with the generic UK CID (if exists), or with the international CID (that is HTC__001).

nor-ric said:
Yes, it's correct. I suggest that you use Hasoon's All In One Toolkit, though: it helps a lot automating things (avoiding command line) if you are not very familiar with these things. You can find it in the development subforum.
The point is writing the correct CID. Do you remember if your software was customized by your carrier (e.g. with carrier-related apps)? Do you have your carrier name physically printed on the phone? Not all phones sold by carriers are branded: for example, I bought it from H3G but it's unbranded.
If this wasn't the case, I would go with the generic UK CID (if exists), or with the international CID (that is HTC__001).
Click to expand...
Click to collapse
Phone is on contract and yes it had carrier apps but on the phone there is no signatures it just looks standard. But now I installed htcs european ruu so probably it doesn't matter.
So I've changed it to HTC__001.
P.S. my bootloader says: unlocked, do I need to lock it or it doesn't matter for a warranty?

I agree, about the cid matter.
About the bootloader, that's the most important part: you need to make it say "LOCKED", otherwise.they will probably deny your warranty. The issue is, if you now lock the bootloader it will say RELOCKED, so they'll know that you've actually unlocked. You need to s-off and then get back the LOCKED label. There's a walkthrough about it, you will easily find it.

Yes thanks for the help I found out how to change it

cikoleko said:
Yes thanks for the help I found out how to change it
Click to expand...
Click to collapse
If you now go back to s-on (it shouldn't be necessary for warranty but who knows...) be sure to use a ruu first.
And whenever you need to thank someone's posts, use the thanks button!

[Q] AT&T HTC ONE XL custom rom & recovery installed on locked phone

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.

New to HTC but not XDA ?s about unlocking s-off etc.

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