Database Develop

[Q] Unlocked AT&T HTC One Update

Hi,
I'm new to the community, and I registered for XDA because I haven't been able to find the answer to this question so far.
If I unlocked my AT&T HTC One using an unlock code I bought online, and now I am using it for T-mobile, will I receive the AT&T updates or the T-Mobile updates? Or neither? If neither, how can I receive the updates without rooting and flashing firmware?

Removing the SIM lock does not change how you receive updates.
You'll get the AT&T update.

HTC One won't update
BenPope said:
Removing the SIM lock does not change how you receive updates.
You'll get the AT&T update.
Click to expand...
Click to collapse
I've tried to scan for the updates, but nothing shows up. I even tried setting the time to October 9th, when the update was released for At&t. Do you have any suggestions?

[Q] Unlocked (bootloader) Moto-X to Developper

Hi,
I currently own and HTC One (from Rogers in Canada) that I converted to dev edition so I can get update faster from HTC (Rogers is taking forever to release updates). It works flawlessly after gaining S-OFF.
I'm now looking at getting a Moto-X (again from Rogers) and for the same reason would like to convert it so I can get OTA updates from Motorola instead of Rogers. I know I can unlock the bootloader on a Moto-X if it comes from Rogers but can I fully convert it the same way I did for my HTC.
I did a lot of reading/searching and can't find an answer
Thanks all

I don't know if S-OFF actually stops updates on HTC phones.
Unlocking the bootloader on Motorola phones does not stop OTA updates: if you modify recovery or the system files, it might prevent OTA updates, but just unlocking the bootloader doesn't have any effect on the functionality of the phone.
Unlocking the bootloader gives you the ability to change the phone to the point where it won't accept updates. By itself, though, it doesn't change anything.

binary visions said:
I don't know if S-OFF actually stops updates on HTC phones.
Unlocking the bootloader on Motorola phones does not stop OTA updates: if you modify recovery or the system files, it might prevent OTA updates, but just unlocking the bootloader doesn't have any effect on the functionality of the phone.
Unlocking the bootloader gives you the ability to change the phone to the point where it won't accept updates. By itself, though, it doesn't change anything.
Click to expand...
Click to collapse
Thanks for the reply but I was trying to understand if I will be able to received update from Motorola (instead of Rogers). I'm not looking at running custom roms, just want to run latest firmwares ASAP.
Thanks again

IronJoce said:
Thanks for the reply but I was trying to understand if I will be able to received update from Motorola (instead of Rogers). I'm not looking at running custom roms, just want to run latest firmwares ASAP.
Thanks again
Click to expand...
Click to collapse
with unlocked bootloader you can always flash the latest releases of firmware, even leaks. There's no need to be dev edition if u already have unlocked bl.

waiflih said:
with unlocked bootloader you can always flash the latest releases of firmware, even leaks. There's no need to be dev edition if u already have unlocked bl.
Click to expand...
Click to collapse
I understand that, but since this will be my wife's phone it would be nice if she would be able to get automatic upgrades from Motorola. This is why I want to "convert" it.
Cheers

If you unlock the bootloader you can flash the retail/tmobile full flash on to the Rogers Moto X and you will get the same updates that the GSM developer edition does. You may lose Band 7 LTE(2600 Mhz) but that is unlikely to matter much as you will still get AWS LTE. You will get the same updates direct from Motorola that a developer and tmobile user will get.

Steve-x said:
If you unlock the bootloader you can flash the retail/tmobile full flash on to the Rogers Moto X and you will get the same updates that the GSM developer edition does. You may lose Band 7 LTE(2600 Mhz) but that is unlikely to matter much as you will still get AWS LTE. You will get the same updates direct from Motorola that a developer and tmobile user will get.
Click to expand...
Click to collapse
Thank you, this is the answer I was after
Cheers

[Q] Question about updates

My Moto X was locked to AT&T. However I got it unlocked from a website. Everything works fine to my knowledge. However I was curious if it will receive firmware updates? Does unlocking the phone mess up anything with the carrier? Any help is much appreciated. Thank you.

dhru1405 said:
My Moto X was locked to AT&T. However I got it unlocked from a website. Everything works fine to my knowledge. However I was curious if it will receive firmware updates? Does unlocking the phone mess up anything with the carrier? Any help is much appreciated. Thank you.
Click to expand...
Click to collapse
There can be some confusion when it comes to unlocking.
There are 2 things you can unlock. You can SIM-Unlock your phone, which will allow it to be used on any GSM carrier. This is what you are referring to. It does not affect the software or system in any way. You will continue to receive updates without issue.
You can also unlock your 'bootloader'. This allows you to root your device and flash custom software. AT&T does not allow Moto to give bootloader-unlock codes out for any AT&T branded phones, but there is a guy from china who is -selling- bootloader-unlock codes.
If you were to obtain a bootloader unlock code, and root your device, then you would have to take special steps anytime a new software update comes out. If you are not interested in root, none of this is important.
Assuming you have only SIM-Unlocked your phone, you have absolutely nothing to worry about. No it does not 'mess anything up' with the carrier.
Good Luck

Having issue with 4.2.2 JB. update need help

Just got my Moto x Verizon branded and came with 4.2.2 JB. For some reason when I hit the update it says I'm on the latest firmware. Any idea what's going on here. Im currently situated in Dubai but not sure how that would have anything to do with it. Any help?
Sent from my XT1060 using Tapatalk

yes, update moto update services via playstore. I dont own a vz X but I suggest you check your bootloder unlock option if interested before updating.

Yes root and unlock it now, because 4.4.4 root isn't quite ideal yet.
Sent from my XT1060 using Tapatalk

bushako said:
Just got my Moto x Verizon branded and came with 4.2.2 JB. For some reason when I hit the update it says I'm on the latest firmware. Any idea what's going on here. Im currently situated in Dubai but not sure how that would have anything to do with it. Any help?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Did you buy it used? If yes, then its possible that the previous owner rooted and disabled the OTA update check. Especially if this is NOT a Developer Edition for Verizon.
Now, if it was purchased new, or the original owner didn't disable the OTA update check, then its likely because you are not on Verizon's network. I've seen this happen on my BB Z10, galaxy S4 and S5, and my Moto X, when running wth my t-mobile sims or on wifi. They will always say either no update found (90% of the time), or Update service not available (10% of the time). I must put my Verizon SIM in to download the update.
Since both the Developer and Non-Developer XT1060 for Verizon use the same ROMs you can download and manually flash the SFB/FXZ files from Moto Directly... -> HERE If you have the Non-Developer XT1060 and you want to unlock the bootloader, do NOT flash anything newer than 4.4.2!!
Use the link in my signature about the Risks of Downgrading to confirm your phone's bootloader version to get a better understanding of your phone's state.
IF you want to root and disable write protection going forward, you need to unlock the bootloader, and you do NOT have the developer edition for Verizon, the only option for that would be to use Sunshine to unlock the bootloader BEFORE you upgrade it to 4.4.4 or higher. For more... see HERE

KidJoe said:
Did you buy it used? If yes, then its possible that the previous owner rooted and disabled the OTA update check. Especially if this is NOT a Developer Edition for Verizon.
Now, if it was purchased new, or the original owner didn't disable the OTA update check, then its likely because you are not on Verizon's network. I've seen this happen on my BB Z10, galaxy S4 and S5, and my Moto X, when running wth my t-mobile sims or on wifi. They will always say either no update found (90% of the time), or Update service not available (10% of the time). I must put my Verizon SIM in to download the update.
Since both the Developer and Non-Developer XT1060 for Verizon use the same ROMs you can download and manually flash the SFB/FXZ files from Moto Directly... -> HERE If you have the Non-Developer XT1060 and you want to unlock the bootloader, do NOT flash anything newer than 4.4.2!!
Use the link in my signature about the Risks of Downgrading to confirm your phone's bootloader version to get a better understanding of your phone's state.
IF you want to root and disable write protection going forward, you need to unlock the bootloader, and you do NOT have the developer edition for Verizon, the only option for that would be to use Sunshine to unlock the bootloader BEFORE you upgrade it to 4.4.4 or higher. For more... see HERE
Click to expand...
Click to collapse
I got it brand new sealed box cost approx $122 16GB, so no chance of it being rooted. I'm glad that it's still JB, read that part of 4.4.4 being not unlockable at the moment. So I just made the payment for Sunshine now waiting for either of the devs to wake up and send me those sweet digits to unlock. The phone came with a Verizon sim card in it but I get a message saying its unrecognizable but that's okay It's customs roms all the way for me from here.
Sent from my XT1060 using Tapatalk

@bushako @hbenz2008 @metaljr81 @KidJoe
You are all now in a new thread.

Verizon SIM, T-Mobile ROM, when should I expect OTA updates?

Sorry, i'm not sure how the OTA's work on the Nexus devices, so I have to ask (and haven't found the right discussions which talk about this)...
I have an ATT branded Nexus 6 which has been bootloader unlocked, OEM partition wiped, and flashed with the "for T-Mobile" LYZ28J image. I am using a Verizon SIM in it.
Since there are posts of T-Mobile pushing LYZ28K I was wondering, will get get this OTA? if so when (i.e. does it it matter than I have a Verizon SIM in there when it comes to OTA's? Or do I manually need to load it?

It doesnt matter that it has a vzw sim in it. If youre stock, you may get it, and you can apply it - but when? Nobody can tell you that, you'll get it when you get it.
If you are waiting for Tmo specific firmware on VZW service, that isn't going to happen - you'll never get that since...well...you dont have TMo service...

Lol what's the reason behind an AT&T branded phone with T-Mobile Rom and Verizon sim? Personally I would just manually do it, like the dude with the hilarious name above me said you may get it you may not. If you want it just go manual.

^^ exactly.
Thats what I've always done - if i want it (and since I'm never stock) I have to manually flash the firmware, make my own no-enforced encryption boot.img (kudos to the kitchen) flash that, and start all over.
Thats how it is, I'm used to it. OTA are too slow, IMO, anyway.
EDIT:
I use this name universally online - any forum you see it, XBL, GitHub, reddit... it's me. lol

The Stig 04 said:
Lol what's the reason behind an AT&T branded phone with T-Mobile Rom and Verizon sim?
Click to expand...
Click to collapse
Long story short... its a work supplied device. I asked for unlocked/unbranded and got the ATT branded (but sim unlocked). My primary work line is Verizon, backup/test line is T-MO.
We have others that will likely be in the same boat (ATT branded, sim unlocked, but using other provider).. who are not techie. So rather than flashing or side loading the OTA (which I easily could), I'm waiting to see what happens.
I'm more curious *IF* I should get the update in this state. and if the mix of rom vs sim might cause any delays/issues.

Bottom Line. Verizon and ATT don't usually OTA for 3 months after update release. Once the factory image for Sprint, USC, International drops you can fastboot flash that They gonna use the same and it will work. T-Mobile and FI work better with their drop just because of WiFi calling.

I'd say that because you're using VZW service, it makes absolutely no difference what branding the phone has and doesn't matter what carrier it was purchased for.
If it uses VZW service, you'll only get OTAs that are for that service. You won't get Tmo specific OTAs for a device being used on VZW - when the OTAs are pushed out they are done so by the service the device is registered as using. I don't think you would ever get said OTAs since the device wouldn't need them.

iRub1Out said:
I'd say that because you're using VZW service, it makes absolutely no difference what branding the phone has and doesn't matter what carrier it was purchased for.
If it uses VZW service, you'll only get OTAs that are for that service. You won't get Tmo specific OTAs for a device being used on VZW - when the OTAs are pushed out they are done so by the service the device is registered as using. I don't think you would ever get said OTAs since the device wouldn't need them.
Click to expand...
Click to collapse
Thank you. And that is what I'm thinking, and why I'm asking... because I'd also seen talk about the SIM in the Nexus 6, or the carrier the phone is on, impacting some of the Nexus 6 updates in the past.
But I also remember my Sister-In-Law using an XT1053 on ATT, who did get XT1053 updates.. SO I wasn't completely sure how the nexus updates worked.

Yes. If leave the sim in will get the Verizon OK'd OTA. That has been up to 3 months after the image was posted. Either remove sim and try to force OTA from Google or manually flash the image. We end up always manually flashing due to having root.. 3-5 minutes tops.

iRub1Out said:
It doesnt matter that it has a vzw sim in it.
Click to expand...
Click to collapse
That's not accurate.. On every other android phone it is accurate but not in the nexus 6.
Usually with a GSM phone, the update is pushed by the oem and your current build determined which update you got.. For example, my Three UK s3 would get the Three UK branded rom update. Even if I had an O2 UK sim in it.. If I then flashed a Vodafone UK rom, I would then get those updates.
With the nexus 6 though, this has changed.. For Verizon and T-mobile users, Google now uses the sim to identify which update to get.. They both were sent with an unbranded stock rom then later on, depending on the simcard, got either a t-mob or vzw update.
The problem is though, that each update will only install on a specified build.. So a vzw update will never install on a t-mob rom or vice versa, so it does matter if the build is one carrier and the sim is another as it will never get an update.

That's what I meant, I probably should have worded that differently.
I meant that even though it is using Verizon service you only get updates for Verizon service. If it's branded for X carrier that won't matter - the service its using is what you'll get updates for.
I apologize about that that was a poor choice of wording on my part.

And just an update.... tonight, I got prompted for a 28meg update. After the update I'm on LYZ28K.
So I guess to answer my own question...
Yes, an ATT Branded Nexus 6 flashed T-Mobile ROM with VZW SIM installed will get updated, and stay on the T-Mobile rom.
That is good.

KidJoe said:
And just an update.... tonight, I got prompted for a 28meg update. After the update I'm on LYZ28K.
So I guess to answer my own question...
Yes, an ATT Branded Nexus 6 flashed T-Mobile ROM with VZW SIM installed will get updated, and stay on the T-Mobile rom.
That is good.
Click to expand...
Click to collapse
Should get the Verizon/ATT (Generic ) rom if have Verizon sim. Hopefully you unlocked before taking update. If locked and it bootloops your only option is RTA.

prdog1 said:
Should get the Verizon/ATT (Generic ) rom if have Verizon sim. Hopefully you unlocked before taking update. If locked and it bootloops your only option is RTA.
Click to expand...
Click to collapse
Yup. I unlocked. Actually when I got it, I unlocked it, rooted, cleared the OEM partition (backed it up first), then flashed the T-Mobile rom.... and left it unlocked (but not rooted since I'm using for work)