Develop Bugs

[Q] T-Mobile branded S3 somehow became AT&T.

When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.

GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?

Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.

GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.

No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.

GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.

I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.

GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.

Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction

GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.

Bummer. I'll leave it as is then. Thank you for all the help.

[Q] Note 3 User - Moving to LG G3 - Please Help?

Dear LG Friends,
Long time XDA member, coming from the Windows Phone days HTC, then to Android HTC, bunch of Samsungs, and am now thinking about the LG space. More specifically moving from the Note 3 (T-Mobile US) running on the AT&T US, to the LG G3.
Before I do, I need some help from you guys. Which variant should I go for? I know my primary choices will be the T-Mobile and the AT&T variants (I believe they are 851 and 850)? Based on what's important to me, below, can you guys advise which variant to get?:
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
2. This is related to # 1 - But I heard that only T-Mobile has the unlocked Bootloader? However, doing some research, I believe the AT&T and the Verizon and Sprint variants can also be unlocked? Is this true? If so, are they anymore limited than the factory unlocked T-Mobile variant?
3. LTE bands - I will most likely be using the phone on AT&T US, but if development options/support are higher on other variants, I might consider buying those models, even if they are missing some AT&T bands. For the Note 3 - T-Mobile is a Pentaband phone, meaning it had all the bands needed, so it could easily work on AT&T LTE, all the time. The reverse was not true.
And basically that is it. Initial instinct says to go chase the T-Mobile variant, based on my needs above. But please educate me and help me out if I have missed something. Thank you so much in advance!

Any input guys?

ProFragger said:
Any input guys?
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
Click to expand...
Click to collapse
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates and that means missing out on necessary fixes
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it. It essentially just makes installing TWRP easier since you dont have to root before installing it unlike other variants
Nevertheless Lollipop can be rooted on all US Variants right now really easily. But the only downside to it is that removing custom roms sometimes can be a pain since you have to use a way where it sometimes works and sometimes doesnt

itsbighead said:
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it
Click to expand...
Click to collapse
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !

ProFragger said:
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
Click to expand...
Click to collapse
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.

itsbighead said:
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
Click to expand...
Click to collapse
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!

ProFragger said:
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
Click to expand...
Click to collapse
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way

itsbighead said:
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
Click to expand...
Click to collapse
This is helpful, once again bud. So how would I downgrade back to KK? Would I have to run a stock firmware of some sort? In Samsung, he Flash a .Tar file through their flashing tool called the Odin. Would that be similarly done here?

AT&T Galaxy Note 4 N910A 5.1.1 Root for CM?

Hey,
Still a bit of a noob to the whole rooting process and navigating XDA forums, so I'm having trouble finding the information *I think* I should be looking for. Basically, my phone's just begun crashing periodically, multiple times a day: anything from Camera, Process System, Touchwiz Home Launcher, or Samsung Apps have "stopped working" / "not responding" before. Of course, my phone's warranty has expired, but my contract isn't up so an AT&T Store wont re-image it for me :crying:
Even I can tell, at this point, that it's either my OS that's failing, or it's my hardware. I figured the easiest way to test this would be to put some stable CyanogenMod on it.
The information I'm looking for is: "is this possible?"
AT&T Samsung Galaxy Note 4
SM N910A UCU2DOI2
Currently @ 5.1.1
Thanks for reading,
~Vita.

No it is NOT possible to use any form of custom firmware or to root this device. It has a locked bootloader that has yet to be cracked open and the future of that happening os very bleak to non existant.
As for reimaging the device go to the note 4 at&t general section on the forum and read up on using odin and the 5.1.1 image posted there it will wipe the phone and format yhe system and data partitions and reinstall it like a new phone just like at&t would do or the manufacturer if you sent it to them.
Good luck

Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.

Ricovita said:
Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.
Click to expand...
Click to collapse
Well the problem is the kernel the bootloader prevents the devs from using an unsecure kernel (one not created and signed by at&t) on the phone if one is used the phone stops boot and says it is an unsecure non at&t kernel and to take thenphone to at&t store.
Odin can only write the firmware versiom that is currently on this phone in this case it is 5.1.1 if you flash any other note 4 versoin such as 4.2.2 it will brick.
Sm-910a flash example
Update ver Official at&t 5.1.1 / currently on phone 5.0.1 or 5.1.1 = good
Update ver (downgrade)oficcial at&t 4.2.2 / currently on phone 5.0.1 or 5.1.1 = brick not good or odin fail
Update from another carrier such as tmobile or verizon for 910t 910v 910g = fail (do not attempt)
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.

giga8547 said:
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.
Click to expand...
Click to collapse
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.

Ricovita said:
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.
Click to expand...
Click to collapse
Look in odin files in progress thread.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Is it possible to downdraft from 5.1.1 to 5.0.1

firebird7880 said:
Is it possible to downdraft from 5.1.1 to 5.0.1
Click to expand...
Click to collapse
I think so, I don't know for sure but we've been able to Odin from various 5.0 Lollipop releases back to KitKat so should be fine.

downgrading from 5.1.1 or 5.0.1 to kitkat is possible but with many many problem but form 5.1.1 to 5.0.1 i don't know maybe phone will stuck or boot loop
thanks finitetime for your reply
other question are there any news about root for 5.1.1 n910a

help
my att note 4 is unlocked and it still won't let me install custom rom's

mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
I am sure that you are referring to a sim unlock. A sim unlock and unlocked bootloader are two completely different entities. To flash a custom rom you will need to have your bootloader unlocked, which is something that a few of us are currently working on. Until then, no custom roms can be flashed on the att variant Note 4s. Take care

the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?

mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
Your phone is SIM UNLOCKED which has NOTHING to do with root, bootloader, or custom roms.
Sent from my SAMSUNG-SM-N910A using Tapatalk

mouseman1 said:
the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?
Click to expand...
Click to collapse
Sorry, was off the forum for the weekend. Spexwood was correct, that is sim unlock. Qualcom is for the sim IE network. Take care.

Root is possible btw
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails

How?
Press Buttons said:
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails
Click to expand...
Click to collapse
How is root possible? What's the process ?

Modder Coming To Samsung From Nexus Environment, Comfused By Differences

I used to have a Nexus 7 (2012) and was rooted with TWRP and loved it. I was familier with fastboot, and liked how "open" everything was in the Nexus environment. But it cracked and I upgraded to the Tab S 16GB (Verizon). I wasen't about to hack my new $600 device, so I waited a while and have been out of the loop. Well I have been considering rooting it so I can install all apps fully to the SD card due to lack of space. And also maybe get a custom ROM based on android M.
It looks like Samsung devices don't have fastboot, and i stead have download mode, and ODIN. Are they the same thing? One time I got this tablet stuck in download mode, and it was really hard to get out.
Also, I don't see the stock ROM for the Verizon version online. I can only get it OTA. Is the ROM the same as the sprint version, just with different bloastware? Both are CDMA. I don't understand what carriers work with what ROMs.
Could you please get me back in the loop on the Samsung (non-Nexus) side? I will probably have a lot of basic questions at first.

Go to the developer section of this forum. We'll find rooting instructions, TWRP recovery and a working a working marshmallow aosp ROM that will make your S1 feel like a Nexus. Double check that others have had success with your model including LTE. Good luck.
Sent from my SM-T800 using XDA Premium HD

If you got the Verizon device, it is fully locked down and you cannot flash ANYTHING or root it at all.

Ditto on the above comment. The CDMA/cellular versions of the Tab S have the least amount of support. They don't have the same processor as the wifi versions (snapdragon in cellular, exynos in wifi).
I also have a Nexus 7 (2012) that's TWRP'd with a custom MM rom. I also TWRP'd and ROM'd a Nexus 4 and 7 (2013). Doing the same to a Samsung device is just as easy, except for KNOX (if you care about warranty).

You're only hope of root for that device is Kingroot.

Nandr0idC0nsumer said:
If you got the Verizon device, it is fully locked down and you cannot flash ANYTHING or root it at all.
Click to expand...
Click to collapse
What makes you think that? In what way is it locked that the WiFi version isn't? I don't care about tripping Knox. I remember hearing when I was researching which one to buy that the AT&T version was locked, but the verizon one wasn't. Which is why I bought it. But maybe they meant the SIM was unlocked, not the boot loader. Are any of the T807's really unlocked.
HKSpeed said:
Ditto on the above comment. The CDMA/cellular versions of the Tab S have the least amount of support. They don't have the same processor as the wifi versions (snapdragon in cellular, exynos in wifi).
I also have a Nexus 7 (2012) that's TWRP'd with a custom MM rom. I also TWRP'd and ROM'd a Nexus 4 and 7 (2013). Doing the same to a Samsung device is just as easy, except for KNOX (if you care about warranty).
Click to expand...
Click to collapse
Yeah, mine has the snapdragon 800, but I thought the AT&T version had the Exynos. I am doing more research and I see there is now an unlocked LTE model that even has native voice support (T805). Did this one come out later? I wanted an LTE one in 2014, but I thought you had to buy a T807 through either Verizon, AT&t, T-Mobile, or Sprint. So I got the Verizon one
ashyx said:
You're only hope of root for that device is Kingroot.
Click to expand...
Click to collapse
From what I understand, KingRoot, uses an exploit in the stock ROM to obtain root without tripping KNOX, or custom recovery. Correct?
Thank you everyone!

flyoffacliff said:
What makes you think that? In what way is it locked that the WiFi version isn't? I don't care about tripping Knox. I remember hearing when I was researching which one to buy that the AT&T version was locked, but the verizon one wasn't. Which is why I bought it. But maybe they meant the SIM was unlocked, not the boot loader. Are any of the T807's really unlocked.
Yeah, mine has the snapdragon 800, but I thought the AT&T version had the Exynos. I am doing more research and I see there is now an unlocked LTE model that even has native voice support (T805). Did this one come out later? I wanted an LTE one in 2014, but I thought you had to buy a T807 through either Verizon, AT&t, T-Mobile, or Sprint. So I got the Verizon one
From what I understand, KingRoot, uses an exploit in the stock ROM to obtain root without tripping KNOX, or custom recovery. Correct?
Thank you everyone!
Click to expand...
Click to collapse
If you're on Lollipop, it's unrootable. Verizon locks the bootloader

Nandr0idC0nsumer said:
If you're on Lollipop, it's unrootable. Verizon locks the bootloader
Click to expand...
Click to collapse
So when you say "locked", you mean ODIN will refuse to flash an unofficial ROM? Wouldn't that mean it's impossible to trip Knox then?

flyoffacliff said:
So when you say "locked", you mean ODIN will refuse to flash an unofficial ROM? Wouldn't that mean it's impossible to trip Knox then?
Click to expand...
Click to collapse
Correct. ODIN only allows stock, signed images to be flashed. Everything else will give a
Code:
secure check fail: recovery
or
Code:
secure check fail: kernel
and halt writing.
---------- Post added at 09:05 PM ---------- Previous post was at 08:57 PM ----------
Personally I recommend you
1) Get a Wifi-only model and suck it up, or
2) Live with a fully locked device and no root

Nandr0idC0nsumer said:
Correct. ODIN only allows stock, signed images to be flashed. Everything else will give a
Code:
secure check fail: recovery
or
Code:
secure check fail: kernel
and halt writing.
---------- Post added at 09:05 PM ---------- Previous post was at 08:57 PM ----------
Personally I recommend you
1) Get a Wifi-only model and suck it up, or
2) Live with a fully locked device and no root
Click to expand...
Click to collapse
T805 LTE(International) , T807T and T807P are all bootloader unlocked. There is also a T807R4, but you don't hear much of this device, so not sure if it's locked or not.
I think the T805 is the only truly unlocked device with no carrier restrictions and can make and receive calls and texts.

ashyx said:
T805 LTE(International) , T807T and T807P are all bootloader unlocked. There is also a T807R4, but you don't here much of this device, so not sure if it's locked or not.
Click to expand...
Click to collapse
Yes they are but he has Verizon so...

Nandr0idC0nsumer said:
Yes they are but he has Verizon so...
Click to expand...
Click to collapse
I know that I was just providing information.

Change rom?

Is it possible to flash a unlocked rom to a Tmobile version of the HTC 10? I've seen this done with SAmsung S7edge carrier to unlocked anf it worked. Guy said he hasnt had issues and this was on XDA.

BlackKnight23 said:
Is it possible to flash a unlocked rom to a Tmobile version of the HTC 10? I've seen this done with SAmsung S7edge carrier to unlocked anf it worked. Guy said he hasnt had issues and this was on XDA.
Click to expand...
Click to collapse
Sure can, just pick a ROM that support multi-carrier, such as Viper, Leedroid, ICE.
When you flash the ROM, in aroma you will be presented with an option to choose carrier, pick Tmobile and good to go. :good:

I actually meant flashing a stock us unlocked rom

BlackKnight23 said:
I actually meant flashing a stock us unlocked rom
Click to expand...
Click to collapse
Link?

http://forum.xda-developers.com/att-s7-edge/how-to/samsung-sm-935u-firmware-install-guide-t3411451
Again this is Samsung but I couldn't see it not working with HTC as well

BlackKnight23 said:
I actually meant flashing a stock us unlocked rom
Click to expand...
Click to collapse
To fully convert your device to us unlocked, you will need to s-off, using the paid sunshine app ($25). This is the only way you will be able to flash the US unlocked firmware. If you want to try keeping your tmo firmware and just try to use the US unlocked ROM, your best bet is to download a US unlocked backup and restore it with TWRP.
Stock backups are in this thread: http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
There isn't a 1.91 backup available yet, though. 1.80 is the best you can do.

So after I do this will it think my phone has beem untouched and allow for OTA? The person I spoke with about his Galaxy S7 he flashed the unlocked rom to from carrier says everything works as it was factory unlocked phone even samsung pay. I am hoping to do the same for my HTC

For instance direct firmware from HTC
http://www.htc.com/us/support/htc-10/news/
Hopefully it displays right but it has the direct download for the 1.91.617.1 or whatever the Unlocked one is. How would I flash this do my device amd make it think it's all factory to receive OTA updates still?

BlackKnight23 said:
For instance direct firmware from HTC
http://www.htc.com/us/support/htc-10/news/
Hopefully it displays right but it has the direct download for the 1.91.617.1 or whatever the Unlocked one is. How would I flash this do my device amd make it think it's all factory to receive OTA updates still?
Click to expand...
Click to collapse
To use that file, you need to fully convert, which means using sunshine to s-off, then changing your cid and mid to match the us unlocked. Then you will have a fully functioning us unlocked device.
If you just want the US unlocked rom, then just restore a stock us unlocked backup in twrp. This will be mostly fully functioning, but you will still be in T-Mobile firmware (shouldn't be a problem as long as your on the newest T-Mobile firmware already) and you won't be able to get ota.

Is that the way i can flash the htcs website firmware?

BlackKnight23 said:
Is that the way i can flash the htcs website firmware?
Click to expand...
Click to collapse
To use an RUU (ROM Update Utility) from HTC's website, you either have to use the one for your specific device OR you have to convert your device by using sunshine to s-off ($25) and changing your model id (probably not necessary as I'm 99% sure that TMO and US Unlocked use the same mid) and carrier id (definitely necessary) to match the RUU you want to flash.
Also, just for your education, I know Samsung people call everything firmware, but technically that's incorrect and in the HTC world, firmware refers to the actual firmware (like bootloader, modem, radio, etc) and ROM, or system, refers to the system files (like android framework, apps, system ui, etc).
There is a thread in the Guide section that details using Sunshine to S-Off.
And see post #3 in this thread about converting a device to WWE (World Wide Edition) using RUU. The steps to convert to US Unlocked are identical EXCEPT for the following:
Step 7:
CID for US Unlocked is BS_US001
MID for US Unlocked is 2PS650000
Step 8:
Get the US Unlocked RUU.zip from here
Once you do that, you will have a 100% fully functioning US Unlocked device. The only difference from a factory provided US Unlocked device will be the text on the rear housing.

Thank you all for helping I've only flased a few times and it still is complicated to me.

BlackKnight23 said:
Thank you all for helping I've only flased a few times and it still is complicated to me.
Click to expand...
Click to collapse
No problem. Can I ask what you would like to accomplish with the US Unlocked rom as opposed to T-Mobile? Just debloat?

I'm worried Tmobile has abandoned the 10. They don't list it online, most stores do not have stock anymore, and the ones that do have few left due to initial shipment. New roms have been out and Tmobile has yet to keep it updated, software only has a few added apps other than that unlocked vs Tmobile roms are the same. Both Roms support VoLTE, Band 12, and Wi-Fi calling. I want faster updates. I love my HTC 10 except it has a few bugs in radios i.e. wifi and LTE. I have no clue if Tmobile will continue to support it, they claim they will but have yet to update the device.

BlackKnight23 said:
I'm worried Tmobile has abandoned the 10. They don't list it online, most stores do not have stock anymore, and the ones that do have few left due to initial shipment. New roms have been out and Tmobile has yet to keep it updated, software only has a few added apps other than that unlocked vs Tmobile roms are the same. Both Roms support VoLTE, Band 12, and Wi-Fi calling. I want faster updates. I love my HTC 10 except it has a few bugs in radios i.e. wifi and LTE. I have no clue if Tmobile will continue to support it, they claim they will but have yet to update the device.
Click to expand...
Click to collapse
I hear you. Then you need to do the full conversion to accomplish that. Just follow the guide I linked to exactly and if you don't understand something, just ask before doing anything. It's not really novice level, but it's hardly rocket science and everything is pretty well laid out in writing. Good luck

I followed the s-off step, changed my cid, used HTCs RUU and flashed it. It's starting up now.

What does this mean? Cause I'm S-off? How do I S-on? I flashed by being s-off but locked should i have been unlocked?

Is this a good sign?

BlackKnight23 said:
What does this mean? Cause I'm S-off? How do I S-on? I flashed by being s-off but locked should i have been unlocked?
Click to expand...
Click to collapse
BlackKnight23 said:
Is this a good sign?
Click to expand...
Click to collapse
That's normal. Looks good. The Sunshine guys suggest locked is preferred.
Don't play around with going s-on until you need to return the phone or sell it. It's not necessary and if you don't do something right can brick the phone.

Anyone with a unlocked US HTC 10 is it typical for it to ask which carrier after inserting sum. Restarting?