Database Info

sprint RUU

can i take a CDMA hero for GCI Wireless / Alaska Digitel and use the RUU to make it work on sprint? i just want to make sure before i get it that it works

i think the bootloader is different. pretty sure you will get an error running the ruu

thedudejdog said:
i think the bootloader is different. pretty sure you will get an error running the ruu
Click to expand...
Click to collapse
is there a way to reprovision to make it work?

thedudejdog said:
i think the bootloader is different. pretty sure you will get an error running the ruu
Click to expand...
Click to collapse
You could have them check the bootloader version from fastboot (hold vol down when turning the phone on).
Version 1.41.0000 is the one that works with the 1.56 RUU.

afaik this is the reason they don't have root yet.
all they would have to do is flash a sprint ruu, root, flash recovery, and then flash whatever rom they wanted. but the Alaskan Digital guys got root-patched. the bootloader is newer than ours. a few months ago they were trying to root and most all of the non-sprint hero's are rooted. all but alaskan digital.

Thread
read this... it says on the first post it will mess with the pri i think it may turn it into a sprint phone. (the 2.1 ruu)
Sprint 2.1 RUU - Supposedly a Sprint 2.1 RUU has been floating around. Until we hear otherwise, DO NOT APPLY IT. Specifically, problems have been reported with GCI Wireless / Alaska DigiTel: "it can break roaming, possibly cause data connection issues, and of course it could adversely affect the bill." and "If someone updates with an RUU we currently have no way to fix their phone." Even if you're with Cellular South or someone else, I suggest not applying it.
Click to expand...
Click to collapse

i have found that and looked it over. i just dont want to make it a paper weight and not have a phone

then your best bet will be to get it and run the 2.1 ruu and hope for the best.. lol.
(almost) anything that you do can be recovered. except a gsm radio flash. so don't flash any of those and you'll be fine.

You need to have a goldcard setup but flashing Sprint's 2.1 RUU over any other carriers Hero will work so long as the bootloader is not newer. Currently, the Sprint 2.1 RUU that's floating around has the newest bootloader I know of so it will flash over anything at this point.
Just a warning though, you can't go back to another RUU after because everything else has an older bootloader. Which doesn't matter so much because the Sprint 2.1 RUU floating around is a dev rom and rooted so you can flash the custom recovery and go to whatever ROM you want.
EDIT: If you are not on Sprint and you use a Sprint RUU you DO have to program your carriers PRL after using QPST or CDMA Workshop
@curtis8523 I know I sent this to you via email already but I wanted to make sure it's searchable on XDA.

navalynt said:
Just a warning though, you can't go back to another RUU after because everything else has an older bootloader. Which doesn't matter so much because the Sprint 2.1 RUU floating around is a dev rom and rooted so you can flash the custom recovery and go to whatever ROM you want.
Click to expand...
Click to collapse
This is a good point. You could flash the 2.1 test RUU to get it to Sprint. If you want to run the 1.56 ruu you can flash everything 1.5 except the hboot by following the instructions here >> http://forum.xda-developers.com/showthread.php?t=657086

[Q] HTC One X (AT&T) manual update

Hello folks, sorry for the dumb questions but this is new for me. I have HTC One X (AT&T) phone, bought in USA. This is my first android phone and I barely know android as a software. I unlocked the phone buying an unlock code from ebay and I am using the phone on another carrier. My question is, how can i manually update my phone (what is the newest update?) since AT&T is not a carrier in my country and I cannot update automatically.
At the moment my software information are:
Android version 4.0.3
HTC Sense version 4.0
Software number 1.85.502.3 710RD
Kernel version 3.0.8-01155-gca24d1eroo[email protected] # SMP PREEMPT (why is there root in the kernel version, my phone has never been rooted?)
Build number 1.85.502.3_R2 CL63811 release-keys
Doing this manual update if possible will the phone be locked to AT&T again, or my phone will remain unlocked?
I'm sorry for my bad english and sorry if there is already a question like this (I watched the noob video and did use the search button)
Thank you in advance

If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459

redpoint73 said:
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
Click to expand...
Click to collapse
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?

StoleMacuk said:
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
Click to expand...
Click to collapse
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237

redpoint73 said:
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
I have a doubt. As I'm no from USA, I'll have no option to update the firmware over the air. How must I proceed in this part of the manual method?
Won't I have any issues with this?
Thank you guys in advance...

galitore said:
How must I proceed in this part of the manual method?
Click to expand...
Click to collapse
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.

iElvis said:
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
Click to expand...
Click to collapse
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!

galitore said:
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
Click to expand...
Click to collapse
Whoops! Sorry about that.
As far as I know, the only way is to flash a custom rom with the base you want, or to run the RUU for that base, which will leave you relocked and unrooted.

[Q] Is there stock recovery for a Rogers S One with RUU 1.84?

I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.

tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto

Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.

you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want

Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.

I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium

Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder). If I locate the Rogers 1.84 RUU, can I run it without downgrading?

don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network

Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.

if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work

Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.

factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery

donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again

Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.

tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.

Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?

tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link

I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?

Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Thanks again.

for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network

Flashing OTA

I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks

dx99 said:
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
Click to expand...
Click to collapse
I would just flash TWRP back onto the phone, then flash Turge's stock T-Mobile Sense 5 ROM posted in Development. Install the 2.15 firmware if you experience signal drops or random reboots.
My typical recommendation is to stay away from official OTAs if you are modded.

I just don't want to flash anything on my phone that's not official. That's why I'm asking, I want to keep my phone stock and just get an official update not a rom from another source.

Your phone is already far from stock, with SuperCID and S-off. You're already down the rabbit hole. And putting an OTA for another version is also not going to be "stock" or "official" for your phone.
The stock ROM is just from the OTA dump, completely unmodified (not even rooted, in fact). Its what is on my phone, and is running great.
Running the OTA might be risky. OTA does not necessarily have all the components. For instance, the T-Mobile 5.05 OTA does not have all the hboot modules. It assumes you are coming for the most recent T-Mobile RUU or OTA. So depending on what is currently on your phone, you can brick.
In theory, I think what you are proposing will work if you RUU to the most recent T-Mobile Germany RUU, than T-Mobile Germany Sense 5 OTA.
But again, you're making it more complicated than need be. What is exactly the issue with "unofficial" ROMs? If you don't trust the devs here, you would not have done SuperCID and s-off to begin with.

It's not that I don't trust the devs I just want to use official carrier updates. I know my phone isn't stock what I meant is using stock/original files from carriers. So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?

dx99 said:
So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
Click to expand...
Click to collapse
Yes, the only thing stopping the RUU from running would be the carrier ID check and hboot version check (might be some other checks). But since you have s-off, all security checks are bypassed by definition.

Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.

dx99 said:
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
Click to expand...
Click to collapse
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".

redpoint73 said:
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
Click to expand...
Click to collapse
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?

dx99 said:
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
Click to expand...
Click to collapse
I think its possible, but its needlessly complicated and possibly risky. If you do it wrong, you might brick.
I don't personally recommend it, and its my personal opinion that you don't have a particularly valid reason for going that route when simpler methods exist. So if you proceed, its at your own judgement and you take all responsibility if something goes wrong.

If it does manage to work so you think there might be compatability issues with the play store or region specific things?

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