Database Users

OTA updates outside T-Mobile networks

I have a US T-Mobile G1, but am in Belgium, and we don't have T network here...
is the update coming to the devices, regardless of the network they're registered on, or do I really need to be in the US, on a T-Mobile network, to get the update?
Anyone from Belgium, or somewhere in Europe that has a G1 that is on another network than it was meant for?
Is there (going to be) any means of pulling the update manually, even on another network?
Thanks for sharing the info...

First, is your phone rooted or not?
Second, what firmware/rom are you running?
You do not need to be on T-mobile to get the update. Your phone checks with a server run by google. If there is an update for it it will get sent to your phone. If your phone is rooted it wont update due to running testkeys instead of releasekeys (unless you are running an ADP firmware).
Once the exact location of the file is known you can manually download it and update your phone if you dont want to wait.
Since you say its a US G1 you should be able to get the 1.5 update which should drop sometime between May 11th and the end of the month. Your location may prevent that from happening, however you can just use the zip file that will get posted on this site somewhere if that happens.

First of all, thanks for the quick response.
The phone is not rooted, it's a normal user phone, no hacks, no custom soft...
Current version is 1.1 RC33 126986 with the release keys intact...
I'll wait until the end of the month and see then...
Just need it to get SipDroid running... (www.sipdroid.org) Wanted to make it a 'cordless phone' for my asterisk server running at home...
Thanks for the info and help!
I'll let you know when I get the update.

Just to let you know, I'm currently abroad with my G1 (UK on T-Mobile), with data roaming turned off.
Connected my G1 to the internet over Wifi and the update was detected and downloaded over Wifi. So looks as though it shouldn't matter what you're connected over.

I have mine secondhand and i have no idea if its rooted or not. but i know i don't have any updates yet. btw im in turkey where no t-mobile service is avaliable.
my device's firware is like that, can you tell its rooted or not? I know im a real newbie. If its rooted how can i take it to original state that can pull the original cupcake
Firmware version 1.0
kernel version
2.6.25-01843-gfea26b0
[email protected] 6#
built number
kila-user 1.0 TC4-RC30 116143
ota-relkeys,release keys

saluk said:
I have mine secondhand and i have no idea if its rooted or not. but i know i don't have any updates yet. btw im in turkey where no t-mobile service is avaliable.
my device's firware is like that, can you tell its rooted or not? I know im a real newbie. If its rooted how can i take it to original state that can pull the original cupcake
Firmware version 1.0
kernel version
2.6.25-01843-gfea26b0
[email protected] 6#
built number
kila-user 1.0 TC4-RC30 116143
ota-relkeys,release keys
Click to expand...
Click to collapse
I think (thx to xda-develpers ) mine is not rooted right? Then why didn't I got the cupcake or the previous version which is newer than mine :/

Im just curious if i will receive the update OTA or not. I rooted my phone however it states that it is release keys and not test keys. Below is what the About Phone screen looks like
Firmware Version
1.1
kernel Version
2.6.25-01843-gfea26b0
[email protected] #1
Build Number
kila-user 1.1 PLAT-rc33 126986
ota-rel-keys, release-keys
Thanks for the help

To answer the actual question. Will you get the OTA T-Mobile update? No, you will not. T-Mobile is pushing it to their customers. T-Mobile and Google are not the same company and T-Mobile has no responsibility to update the "device" but rather to update their customers.
The reason the UK guy got the update is because he is in the customer database for T-Mobile UK. So as his phone is part of that network (regardless of roaming/not roaming) it came to him.
However, I am sure there will be some smart G1 user who, when getting the update downloaded OTA, will FIRST copy the update off their phone BEFORE installing it. Then uploading a copy of the update so those who still have not received it can download it and install it manually. (That is a hint to any US T-Mobile person on this forum who gets the update)

You should get the OTA updates. I bought a dev phone in december and in January I got the OTA ADP1.1h update. I'm not on T-Mo at all and never have. I am on AT&T and all was well and I would assume you should be too.

ExploreMN said:
To answer the actual question. Will you get the OTA T-Mobile update? No, you will not. T-Mobile is pushing it to their customers. T-Mobile and Google are not the same company and T-Mobile has no responsibility to update the "device" but rather to update their customers.
The reason the UK guy got the update is because he is in the customer database for T-Mobile UK. So as his phone is part of that network (regardless of roaming/not roaming) it came to him.
However, I am sure there will be some smart G1 user who, when getting the update downloaded OTA, will FIRST copy the update off their phone BEFORE installing it. Then uploading a copy of the update so those who still have not received it can download it and install it manually. (That is a hint to any US T-Mobile person on this forum who gets the update)
Click to expand...
Click to collapse
I beg to differ, I might be wrong but everyone was getting the previous updates because they aren't sent from T-Mobile. They are sent from Google. It is just a T-Mobile build so as long as you have internet it will download the update.

neoobs said:
I beg to differ, I might be wrong but everyone was getting the previous updates because they aren't sent from T-Mobile. They are sent from Google. It is just a T-Mobile build so as long as you have internet it will download the update.
Click to expand...
Click to collapse
I beg to differ your begging to differ! Google, from what I understand, has its own 1.5 cupcake update which is similar to the T-mobile version in just about every respect. However, while searching for cupcake I read an article that noted there were some differences between the two builds. Perhaps Google was responsible for the G1 update to 1.1, but from the sounds of it, that is not the case now.

ExploreMN said:
I beg to differ your begging to differ! Google, from what I understand, has its own 1.5 cupcake update which is similar to the T-mobile version in just about every respect. However, while searching for cupcake I read an article that noted there were some differences between the two builds. Perhaps Google was responsible for the G1 update to 1.1, but from the sounds of it, that is not the case now.
Click to expand...
Click to collapse
I am not saying that Google created it but rather it is hosted on Google Servers, this can't change because the update script pulls the update from Google servers. Maybe in 1.5 it will change but as of 1.1 it still checks Google for the update.
Basically as long as you can reach the google address it all will update.

You will NOT get an OTA.
You only get an OTA IF:
1) You have a G1 and are a tmobile customer. The update may come from google's servers, but the update is controlled by tmobile, and its user database. It is a tmobile phone.
2) You have an ADP, and have already *MANUALLY* updated to 1.1 firmware. Then, you will get the official google (via HTC) ADP 1.5 update. OTA functionality for ADP was only rolled out in the 1.1 firmware.
Other than that, no, you will NOT get the update, and you will need to root the phone and manually update to either the ADP release, one of the t-mobile releases or any of the 'cooked' roms on here.
Also there seems to be some confusion on the ADP vs. G1 versions. Infact, it is the exact same phone, and the *exact* same software, but the tmobile release has the t-mobile logo and all their spam apps (my favs etc). Otherwise, they are the same thing!
Hope this cleared some stuff up.

I bought the phone second hand and use it on orange and i got the update. im not a tmobile user, but the person i bought the phone off was. but have never personally used it on tmobile and received the 1.5 update fine. hope this helps

menov321 said:
I bought the phone second hand and use it on orange and i got the update. im not a tmobile user, but the person i bought the phone off was. but have never personally used it on tmobile and received the 1.5 update fine. hope this helps
Click to expand...
Click to collapse
You probably got the google generic 1.5 update and not the t-mobile specific update.

bakgwailo said:
You will NOT get an OTA.
You only get an OTA IF:
1) You have a G1 and are a tmobile customer. The update may come from google's servers, but the update is controlled by tmobile, and its user database. It is a tmobile phone.
2) You have an ADP, and have already *MANUALLY* updated to 1.1 firmware. Then, you will get the official google (via HTC) ADP 1.5 update. OTA functionality for ADP was only rolled out in the 1.1 firmware.
Other than that, no, you will NOT get the update, and you will need to root the phone and manually update to either the ADP release, one of the t-mobile releases or any of the 'cooked' roms on here.
Also there seems to be some confusion on the ADP vs. G1 versions. Infact, it is the exact same phone, and the *exact* same software, but the tmobile release has the t-mobile logo and all their spam apps (my favs etc). Otherwise, they are the same thing!
Hope this cleared some stuff up.
Click to expand...
Click to collapse
Where did you get your info? We had tons of users getting the update OTA for the 1.1 and even previous 1.0 builds. BTW there are 3 versions of software, 2 by t-mobile, 1 by google. The 2 t-mobile versions are US and UK which have different applications because of the way company each works.
ExploreMN said:
You probably got the google generic 1.5 update and not the t-mobile specific update.
Click to expand...
Click to collapse
Where did you hear there is a generic google version? So far only the ADP 1.5 has been made available to us, and we only know of the ADP and T-Mobile versions.

There is also this one, cupcake for holiday phone europe
http://android.clients.google.com/updates/signed-dream_gfh_eu-ota-147201.ea8cd686.zip
posted here
http://phandroid.com/2009/05/05/official-german-cupcake-url-leaks-for-developers/

I have a T-mobile G1 on Rogers in canada with a data plan,
YES, YOU WILL EVENTUALLY GET THE UPDATE.
Originally i believed that i do not get updates, so i manually upgraded fron RC29, to RC30,
one day, at work, i got a notification to go from RC30 to RC33 OTA.

petko64 said:
I have a T-mobile G1 on Rogers in canada with a data plan,
YES, YOU WILL EVENTUALLY GET THE UPDATE.
Originally i believed that i do not get updates, so i manually upgraded fron RC29, to RC30,
one day, at work, i got a notification to go from RC30 to RC33 OTA.
Click to expand...
Click to collapse
That could be because updates were stopped halfway through on one of the updates to make sure they fixed some security holes.

The last update I got before any T-mobile customers and I was on AT&T. I actually pulled the file off my phone and gave it to JesusFreke but by the time he got it the link had already been posted.

Update issues?

strangest thing, i confirm the update and it closes and thats it. It doesnt show a download in the status bar or anything. any ideas?

Mine still says it is already upto date even though I know the 2.3.3 update is out for almost everyone else?!?

FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.

Mozza2k11 said:
FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.
Click to expand...
Click to collapse
It's on Virgin Mobile, must be why?

FK1983 said:
It's on Virgin Mobile, must be why?
Click to expand...
Click to collapse
It doesn't matter which network the phone is on. If you got it direct from virgin or it has the virgin boot up screen then its virgin "branded". Until virgin or any other network decides to ok the update (and make any modifications they want) unfortunately you will be waiting. Unless you unlock your boot then you can flash the generic 2.3.3 that people with unbranded phones got.
P.s i said o2 since the o2 logo is under your name

Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.

Flava0ne said:
Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.
Click to expand...
Click to collapse
No this only applies to people with a branded phone and a locked bootloader. If you unlock your boot which you have done you can do as you did and flash the generic fw (without extra branded crap on just standard bloat) From now on you will just update using the fw posted here instead of waiting for rogers.

Cool, thanks for clearing that up a bit!
But I didn't unlock my bootloader, I can't because it came from my carrier. What I unlocked was the network and now I can use another SIM card from a different carrier on it if I wanted to. But I guess it's still the same since I was able to flash it with a generic fw already.

I had no issues with the updating itself.
But I noticed that the standard music player sometimes doesn't play sound at all. I first have to kill it with a program like 'Advanced Task Killer' and then it works again. Anyone else has this problem?

My Unlocked XP can download the update but fails on the install, its attempts to install, resets, unpacked update, then attempts to update (icon on screen goes from two dots and openbox icon, to three dots and phone with arrow above) then screen goes blank, phone boots as normal (takes about 2-3mins) then warns that update was unsuccessful after pincode entry.
Thought it might due to lack of internal space, so cleared 80 megs on application space and still no luck.
Sent from my R800i using XDA App

Bricked after OTA update
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.

I just checked for the update manually on my PLAY earlier today and it was able to find the update. But I'm not going to install it until you can root v2.3.3 on a locked bootloader.

ritap said:
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.
Click to expand...
Click to collapse
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore. You will have to flash the lastest fw onto the phone. See here to 2.3.3 firmware http://forum.xda-developers.com/showthread.php?t=1097591 also if you flash the first one you can then flash the rooted 2.3.3 http://forum.xda-developers.com/showthread.php?t=1098736 Same goes for Da22a since your XP is unlocked

So still no way to root 2.3.3 on a locked bootloader yet, only with an unlocked bootloader at the moment? Because it's not possible for my to unlock my bootloader on my PLAY because it was originally from my carrier.

Mozza2k11 said:
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore.(snip)
Click to expand...
Click to collapse
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .

I don't think SE speculated in making money here. It's a more like a 'here you go' now you have control over your phone to do almost what you like. The main target here I think is devs and flashaholics and such. There's always a risk involved with unlocking your bl and changing the S-ON to S-Off and such things. Ofcause you loose your warranty otherwise every john/jane does would come back and reclaim a new device when they bricked there phone. This comes from a demand within the android community that this is an option.
Further more I don't think SE knew about this. The .img to flash is not comming from We but from this community so they can't be held responsible for putting out an OTA that bricks your phone cause of what people might flash onto there phones. I hope that they will make some kind of check in the software updater similar to SEUS in the future or the ones who make flasheble .imgs will be able to disable OTA in the .imgs to come or upload a new one for people to use.
Regards Dousan...

ritap said:
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .
Click to expand...
Click to collapse
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Therefore, you should only unlock the boot loader of your phone if you are an advanced user with good knowledge of the technology and risks involved. We strongly recommend that standard users NOT unlock the boot loader, as it is not needed
Click to expand...
Click to collapse
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Note: We have seen in some forums that customers unlocking the boot loader on their phones have experienced problems when they accept a FOTA (Firmware upgrade Over The Air) update. The issue has been reproduced and we are working on a solution. For customers that have unlocked the boot loader please do not accept the Firmware upgrade OTA.
Click to expand...
Click to collapse

Rogers official one comes July 1st. (Canada Day)

Mozza2k11 said:
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Click to expand...
Click to collapse
You and Dousan may be right but indeed after unlocking the BL we didn't flash it; moreover, after that the phone has been working perfectly for more than a month, since the ota update of course: so it's their software which has bricked the phone, not us.
Moreover, it's true that we lost our warranty, and it's fair that those Johns/Janes won't get a new phone for free, but this doesn't allow then to spread around dangerous software and allowing free repair only to "warranty" customers.
I've already had a look at the fix described in this forum but it didn't fit, Blagus told me there was no solution, the payservers were down so i took the Play to SE...

Anyone know how to get flashtool to recognize the play? The only options are arc x10 x8 etc.
Same as this guy:
how did you guys even get the flashtool to work with the play? ive got the latest version and i keep getting an error saying it cant identify my device and the only options are for x10, x10 mini, x10 mini pro, x8 and arc, just curious
Click to expand...
Click to collapse

No 8.1?

My understanding is that Essential has made Android 8.1 available as an OTA update to all phones at this point.
But every time I check for an update, it says that I have the latest at 7.1.1
I am on Sprint, but it's my phone, not purchased through Sprint.
Is this common, or do I have a unique problem?

zomplit said:
My understanding is that Essential has made Android 8.1 available as an OTA update to all phones at this point.
But every time I check for an update, it says that I have the latest at 7.1.1
I am on Sprint, but it's my phone, not purchased through Sprint.
Is this common, or do I have a unique problem?
Click to expand...
Click to collapse
Everyone i know with PH1 got the OTA to 8.1 within a week of it being released, so i think it's a Sprint issue even though you got the phone yourself.
Sent from my PH-1 using Tapatalk

I'm pretty certain I read that Sprint customers got the 8.1 update like everybody else. You might want to contact Essential support to see if they have any recommendations. I'm assuming you've rebooted your phone at some point. Sometimes that's necessary before an update will show up. Hopefully Essential has a solution where you don't need to factory reset your phone but that might end up being your only option.
Just a tip in case you do end up doing a factory reset. It's a much better idea to choose the give your phone a fresh start option instead of restoring your phone from a Google Cloud backup. The cloud backup restores app and system data and can actually restore whatever was causing an issue on your phone.

I got a new OTA update just now!

zomplit said:
My understanding is that Essential has made Android 8.1 available as an OTA update to all phones at this point.
But every time I check for an update, it says that I have the latest at 7.1.1
I am on Sprint, but it's my phone, not purchased through Sprint.
Is this common, or do I have a unique problem?
Click to expand...
Click to collapse
Sprint needs to approve every update, so if they have not done so, that is why you have not received 8.1.
Manually flashing the latest 8.1 is the way to go. After doing this you will get all updates directly from Essential instead of Sprint.
F Sprint

coolmaster121 said:
Sprint needs to approve every update, so if they have not done so, that is why you have not received 8.1.
Manually flashing the latest 8.1 is the way to go. After doing this you will get all updates directly from Essential instead of Sprint.
F Sprint
Click to expand...
Click to collapse
I guess that's true. This is from the Essential site:
"Phone not downloading latest software update
When Essential releases a new software update, it will be available to all Essential Phones, except those using certain cellular networks.
Currently, devices on all networks except Sprint and TELUS will receive instant software updates (related article: Updating your phone's software).
Sprint and TELUS perform additional testing and verification at the time of our release, and will make the updates available to their customers once complete."

Yup... I'm with Telus and wasn't getting the update notification. I ended up swapping my Telus SIM card with a Roam Mobility SIM card, and then connected over wifi. I checked for the update again, and this time it appeared. For a small update (125MB), it took nearly 20 minutes to install.

As it happens, the 8.1 update came through for me a couple of days ago.

T-Mobile OS help

Forgive me if there is already an answer to this. I am very new to Android. By new I mean 2 weeks. I have been on Apple for many years now. Jailbreak and customizing is kind of a thing of the past. But to my question...
T+Mobile software is way behind and feels somewhat restricted. Is there a simple way of going to the full version of the latest OnePlus OS?
Thanks in advance for any help and insite.
Chris

wheeler77 said:
Forgive me if there is already an answer to this. I am very new to Android. By new I mean 2 weeks. I have been on Apple for many years now. Jailbreak and customizing is kind of a thing of the past. But to my question...
T+Mobile software is way behind and feels somewhat restricted. Is there a simple way of going to the full version of the latest OnePlus OS?
Thanks in advance for any help and insite.
Chris
Click to expand...
Click to collapse
By far, the best link to get you from T-Mobile software to the International ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-flashing-t-mobile-oneplus-6t-to-t3865966
I've got the T-Mo version and (once I got my phone and bootloader unlocked) was able to convert to the International ROM in less than 10 minutes.
NOTE: You won't be able to get OTA updates (as of yet) but the process of flashing the new updates is super easy.

I followed the how to linked here, updated to the .11 version manually using local update.
On the international Beta 2 now, and it works flawlessly.
brisseau said:
By far, the best link to get you from T-Mobile software to the International ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-flashing-t-mobile-oneplus-6t-to-t3865966
I've got the T-Mo version and (once I got my phone and bootloader unlocked) was able to convert to the International ROM in less than 10 minutes.
NOTE: You won't be able to get OTA updates (as of yet) but the process of flashing the new updates is super easy.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6013 using Tapatalk

brisseau said:
By far, the best link to get you from T-Mobile software to the International ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-flashing-t-mobile-oneplus-6t-to-t3865966
I've got the T-Mo version and (once I got my phone and bootloader unlocked) was able to convert to the International ROM in less than 10 minutes.
NOTE: You won't be able to get OTA updates (as of yet) but the process of flashing the new updates is super easy.
Click to expand...
Click to collapse
Thank you for the info. I will give it a shot in a few.

wheeler77 said:
Forgive me if there is already an answer to this. I am very new to Android. By new I mean 2 weeks. I have been on Apple for many years now. Jailbreak and customizing is kind of a thing of the past. But to my question...
T+Mobile software is way behind and feels somewhat restricted. Is there a simple way of going to the full version of the latest OnePlus OS?
Click to expand...
Click to collapse
If you've been on Apple devices for the past few years, isn't it a bit quick to jump to the conclusion that the T-Mobile branded version of OxygenOS is "way behind" and "feels restricted?"
The only "restrictions" on the T-Mobile version of the phone are the T-Mobile branded boot animation and the inclusion of the T-Mobile app and SIM Unlock app, both of which can be disabled (but not removed). It also doesn't support dual-SIM even though the hardware is there. Aside that there are no other differences.
The system updates are pushed much more slowly on the T-Mobile version. For example we just got the 9.0.2 update while OnePlus has recently released 9.0.11. So yes, the updates are "way behind" if you consider a 2-3 month delay to be a concern. There aren't any significant restrictions. The same restrictions apply to the non-Tmo variant, and in either case you can easily bypass them by rooting.
Now if you want the dual SIM capability, unbranded OS, and more recent system updates, then go ahead and convert. That's exactly why I'm doing it.
As for the OTA updates, I'm reading mixed reviews. Some claim they have successfully received OTA updates after converting. Its not clear if they were real OTA updates that were downloaded and installed automatically or if those users had to manually download and install (in which case it isn't an OTA update, some people just don't understand terminology) It is confirmed that after converting, it is most certainly possible to download the latest software update from OnePlus and use the local upgrade option (no need to manually flash via adb) which is fine by me.

bassic said:
If you've been on Apple devices for the past few years, isn't it a bit quick to jump to the conclusion that the T-Mobile branded version of OxygenOS is "way behind" and "feels restricted?"
The only "restrictions" on the T-Mobile version of the phone are the T-Mobile branded boot animation and the inclusion of the T-Mobile app and SIM Unlock app, both of which can be disabled (but not removed). It also doesn't support dual-SIM even though the hardware is there. Aside that there are no other differences.
The system updates are pushed much more slowly on the T-Mobile version. For example we just got the 9.0.2 update while OnePlus has recently released 9.0.11. So yes, the updates are "way behind" if you consider a 2-3 month delay to be a concern. There aren't any significant restrictions. The same restrictions apply to the non-Tmo variant, and in either case you can easily bypass them by rooting.
Now if you want the dual SIM capability, unbranded OS, and more recent system updates, then go ahead and convert. That's exactly why I'm doing it.
As for the OTA updates, I'm reading mixed reviews. Some claim they have successfully received OTA updates after converting. Its not clear if they were real OTA updates that were downloaded and installed automatically or if those users had to manually download and install (in which case it isn't an OTA update, some people just don't understand terminology) It is confirmed that after converting, it is most certainly possible to download the latest software update from OnePlus and use the local upgrade option (no need to manually flash via adb) which is fine by me.
Click to expand...
Click to collapse
Well you did leave a handful of features the TMO firmware does away with.
But yes, it's easy to "uncarrier" this phone, as i was given my unlock before i paid it off and before the 40 days, submitted to 1+, and in due time and no time fast forward to beta 2

Should I change my AT&T Rom?

I just bought an unlocked AT&T phone. I don't care about security updates. I do like performance improvements and certain changes when moving to a new operating system though. However I am not willing to make those changes if I sacrifice stability.
Should I switch my AT&T rom to U.S unlocked? Is the gains worth it? Do I gain anything other then "Android 9 pie" in the settings? How is performance?
Will I get OTA updates after that or will I still need to use LGUP?
Thank you
Edit: I think I answered my own question. The ability to use HDMI out is not available until after the December 2018 update. My phone is stuck in November.

Also, unless you're an AT&T customer there's no reason to want or keep AT&T firmware.
Curious-Octopus said:
I just bought an unlocked AT&T phone. I don't care about security updates. I do like performance improvements and certain changes when moving to a new operating system though. However I am not willing to make those changes if I sacrifice stability.
Should I switch my AT&T rom to U.S unlocked? Is the gains worth it? Do I gain anything other then "Android 9 pie" in the settings? How is performance?
Will I get OTA updates after that or will I still need to use LGUP?
Thank you
Edit: I think I answered my own question. The ability to use HDMI out is not available until after the December 2018 update. My phone is stuck in November.
Click to expand...
Click to collapse

ChazzMatt said:
Also, unless you're an AT&T customer there's no reason to want or keep AT&T firmware.
Click to expand...
Click to collapse
Would only flashing and no root/bootloader unlock allow me to keep the serial and imei in the phone? Or should I make alot of backups of files?

Curious-Octopus said:
Would only flashing and no root/bootloader unlock allow me to keep the serial and imei in the phone? Or should I make alot of backups of files?
Click to expand...
Click to collapse
Let's take one topic at a time.
Using Dev Patched LGUP to flash to NAO firmware for your carrier unlocked phone only gets rid of the AT&T bloat and allows you to update firmware while keeping AT&T firmware does not.
Nothing about that conversion touches serial or IMEI.
_____
Unlocking the Bootloader and rooting is a more advanced process which is harder. But that also normally shouldn't affect serial or IMEI. If you do lose serial or IMEI there's a method posted to write them back, I believe.

ChazzMatt said:
Let's take one topic at a time.
Using Dev Patched LGUP to flash to NAO firmware for your carrier unlocked phone only gets rid of the AT&T bloat and allows you to update firmware while keeping AT&T firmware does not.
Nothing about that conversion touches serial or IMEI.
_____
Unlocking the Bootloader and rooting is a more advanced process which is harder. But that also normally shouldn't affect serial or IMEI. If you do lose serial or IMEI there's a method posted to write them back, I believe.
Click to expand...
Click to collapse
Thank you!
I am new to all of this, but I have experience in computer so I am confident about my ability to do it.

With the talk of Android 10 available via OTA update on AT&T only, it might make sense for ppl who want Android 10 to stick with AT&T firmware because if you cross-flash there is no going back. Android 10 for other carriers is not out yet so if you cross-flash, you're stuck with Pie.
Sorry, nevermind, seems its coming out for all soon.

Android# said:
With the talk of Android 10 available via OTA update on AT&T only, it might make sense for ppl who want Android 10 to stick with AT&T firmware because if you cross-flash there is no going back. Android 10 for other carriers is not out yet so if you cross-flash, you're stuck with Pie.
Sorry, nevermind, seems its coming out for all soon.
Click to expand...
Click to collapse
For V35 on AT&T firmware, you won't get the OTA AT&T update unless you're an AT&T customer. Or AT&T MVNO Red Pocket customer.
Whereas you can flash to NAO Android 10 firmware when that is released via KDZ.
People, don't get hysterical like you did with the Pie update. All variants will get Android 10. All but AT&T will have full image KDZ which you can download and install.
NAO KDZ will be the best choice for those who are not Google Fi customer or AT&T customer.
Don't go trying to flash Korean carrier firmware like some did for Pie. Just be patient.

Stupid question... i bought one chep last year of course AT&T and i paid the unlock code, of course it came with Oreo and as later i found it couldn't get Pie. So i flashed it to the unlocked version, but as someone in other thread it seems that the firmware "official" has just been on Oreo, mine seems has security update of June and it has been updated this month with another security update...
Mine seems to work normally, however i could say it has three main flaws, first and most annoying for me is that do not disturb doesn't work properly even with rules established, only way to get it working is setting the alarm, which is a bit annoying considering that as for this virus situation i am not working since 2 months ago, and of course i don't want to get disturbed after 10:00 pm and also very early in the morning...
And second one is the signal which is worst than my previous V30+ converted to US998, funny because with other of my old phones as Z2 Force, Iphone 7 and of course US998 i could get easily 30MB+ at average using same SIM card and in the same area for more than two years, but since i have this V35 i can barely get 2MB at average and max 38MB, and max with the other ones mentioned i could get 45MB and in one time i got 60MB
And i don't know if mine has a weird battery but it can barely get around 15-16 hours of normal use.
Should i flash again to AT&T, flash the latest Pie with security update or just wait for the KDZ of Android 10?
And is that true that it now can be rooted?

This thread is widening in scope to the pros and cons of the various vendor roms and android levels. There are a couple of points to add toward that end. To my knowledge, all v35's on any existing rom can be rooted including the AT&T model. The difficulty with AT&T phones is that kdz's aren't released. You need to make your own backup before flashing to another rom if you want to return to AT&T firmware from say GFI/NA.
The next is about Oreo, at least the "h" NA/GFI build. Hotspot and tethering is broken. It may work once or twice after first setup, but it will stop working. That is a deal breaker for some. Everything (that matters to me) seems to work on Pie.
It will be interesting to hear reports on Android 10 on v35. Before taking the leap, it is important to know that ARB remains 0. An ARB change could lock you to Android 10. I don't recall reading about ARB changes on flagship LG phones in the past several years. Regardless, ARB or back-flashing is not yet reported and I do not know if qfil can overcome an ARB change. My suggestion is to be patient and watch for A10 v35 updates from the skilled, brave and sometimes foolhardy here on xda or tg.
tonochito said:
Stupid question... i bought one chep last year of course AT&T and i paid the unlock code, of course it came with Oreo and as later i found it couldn't get Pie. So i flashed it to the unlocked version, but as someone in other thread it seems that the firmware "official" has just been on Oreo, mine seems has security update of June and it has been updated this month with another security update...
Mine seems to work normally, however i could say it has three main flaws, first and most annoying for me is that do not disturb doesn't work properly even with rules established, only way to get it working is setting the alarm, which is a bit annoying considering that as for this virus situation i am not working since 2 months ago, and of course i don't want to get disturbed after 10:00 pm and also very early in the morning...
And second one is the signal which is worst than my previous V30+ converted to US998, funny because with other of my old phones as Z2 Force, Iphone 7 and of course US998 i could get easily 30MB+ at average using same SIM card and in the same area for more than two years, but since i have this V35 i can barely get 2MB at average and max 38MB, and max with the other ones mentioned i could get 45MB and in one time i got 60MB
And i don't know if mine has a weird battery but it can barely get around 15-16 hours of normal use.
Should i flash again to AT&T, flash the latest Pie with security update or just wait for the KDZ of Android 10?
And is that true that it now can be rooted?
Click to expand...
Click to collapse

cmrntnnr said:
This thread is widening in scope to the pros and cons of the various vendor roms and android levels. There are a couple of points to add toward that end. To my knowledge, all v35's on any existing rom can be rooted including the AT&T model. The difficulty with AT&T phones is that kdz's aren't released. You need to make your own backup before flashing to another rom if you want to return to AT&T firmware from say GFI/NA.
The next is about Oreo, at least the "h" NA/GFI build. Hotspot and tethering is broken. It may work once or twice after first setup, but it will stop working. That is a deal breaker for some. Everything (that matters to me) seems to work on Pie.
It will be interesting to hear reports on Android 10 on v35. Before taking the leap, it is important to know that ARB remains 0. An ARB change could lock you to Android 10. I don't recall reading about ARB changes on flagship LG phones in the past several years. Regardless, ARB or back-flashing is not yet reported and I do not know if qfil can overcome an ARB change. My suggestion is to be patient and watch for A10 v35 updates from the skilled, brave and sometimes foolhardy here on xda or tg.
Click to expand...
Click to collapse
Well my teher works, the phone itself has been good for the amount i paid $100, however those bugs or may be wrong flash? affects me a bit... i guess i should be patient and wait for the kdz.

Can anybody confirm this?
https://piunikaweb.com/2020/06/09/lg-v35-thinq-android-10-lg-ux-9-0-update-rolling-out/
Says that LG G7 Android 10 can be flashed to the V35...

tonochito said:
Can anybody confirm this?
https://piunikaweb.com/2020/06/09/lg-v35-thinq-android-10-lg-ux-9-0-update-rolling-out/
Says that LG G7 Android 10 can be flashed to the V35...
Click to expand...
Click to collapse
NO, that article doesn't say that. It doesn't mention LG G7 whatsoever at all. Seriously. You are just making stuff up?
Confirm what? That you can cross flash to Korean carrier V35 firmware to other V35 against our advice? Why would you want to do that? Just be patient!
Here's my reply from earlier in the thread. Please read it this time.
ChazzMatt said:
For V35 on AT&T firmware, you won't get the OTA AT&T update unless you're an AT&T customer. Or AT&T MVNO Red Pocket customer.
Whereas you can flash to NAO Android 10 firmware when that is released via KDZ.
People, don't get hysterical like you did with the Pie update. All variants will get Android 10. All but AT&T will have full image KDZ which you can download and install.
NAO KDZ will be the best choice for those who are not Google Fi customer or AT&T customer.
Don't go trying to flash Korean carrier firmware like some did for Pie. Just be patient.
Click to expand...
Click to collapse

ChazzMatt said:
NO, that article doesn't say that. It doesn't mention LG G7 whatsoever at all. Seriously. You are just making stuff up?
Confirm what? That you can cross flash to Korean carrier V35 firmware to other V35 against our advice? Why would you want to do that? Just be patient!
Here's my reply from earlier in the thread. Please read it this time.
Click to expand...
Click to collapse
i know but is kinda weird that even that article links to Reddit and some people on the video saying they flashed "successfully" their v35...

tonochito said:
i know but is kinda weird that even that article links to Reddit and some people on the video saying they flashed "successfully" their v35...
Click to expand...
Click to collapse
Yet again, we went all through this a year ago with Pie.
You can flash it "successfully" but you wipe all data, some of the menus are in Korean... Then a month or so later every other variant gets a KDZ (EXCEPT for AT&T). So then people have flash again to what they REALLY want -- which is a North American Open (NAO) carrier unlocked variant firmware. AND they lose data again and risk messing up their phone by cross flashing entirely different region yet again.
There's no need to do it. JUST WAIT. FLASH to NAO firmware when Android 10 is released for that variant.
If you're already on NAO firmware now, then when Android 10 is released for that variant, it would be simple "Upgrade" in Dev Patched LGUP (keep your data). If you're not yet, then it would be Partition DL or Refurbish mode to cross flash to NAO at that time. You would lose your data only once.
The people who are impatient are NOT going to stay on Korean carrier firmware long term. They will cross flash yet again to NAO when it comes out, because it's more desirable. They will be unhappy with the Korean carrier firmware. Many will mess up their phones. Don't be one those people!
Look it's your phone. Do what you want. But weeks ago I predicted this would happen and have cautioned people to not make the same mistakes again that were made last year during Pie rollout.

I just installed the korean ROM and it works... kinda good there are some minor bugs that may bother you if you pay too much attention or that are a bit annoying i am going to put here:
As soon you reboot your phone it is going to give you some warning about well some codes and stuff, i guess because the hardware is not the same?
Menu is in korean at set up but you can change it to your language
There are 3 apps that are in korean and you can't uninstall it, specially Q voice that is on korean language not working
LG Smart World does not work, but anyway i never used it, also Quick Help but it never worked on Pie too so its irrelevant
There is one app called DMB which does not work, don't know what it does but it just freeze when i try to open it
Some weird bug with the battery? It doesn't show up the estimated remaining battery, it just keep on calculating data
For some reason i haven't been able to find or change the data configuration, you know change LTE, 3G or 2G. Seems like it is on auto mode which is kinda annoying for me.
The only drawback i could say for me its dual apps... is not that easy as on Pie
And for some reason it fixed in my case the annoying but it had about do not disturb, which only worked when an alarm was set, but if there wasn't alarm it never worked
Seems the "AI" camera has been improved or fixed because when i selected AI cam it just never do anything relevant compared with my old V30+, now it recognize stuff such person and so on
Although i love stock music player i just hate the annoying purple tone with it, now it changes depending on the setup of the midnight menu. I think that on a rooted v30+ it could be changed but i am not interested on root it and doubt being on Android 10 could be rooted. But it has integraded FM app radio which i regulary use but being the american version of course it has been removed, so it has to be installed manually
What i like its that now it has integrated viedo screen recorder so good bye third party apps, which in my case i really don't like you know if you don't pay you have adds and stuff related.
But the drag menu is with a bug? i don't know how to explain it but it just goes with the hour and date long... instead of just taking a portion of the screen
I just did it and didn't wait because my v35 is broken so i need to change or leave it as secondary phone, around 20 days ago the fingerprint begun to be erratic and was hit or miss trying to unlock it, i have tried cleaning it but it worked as i mentioned on hit or miss. Right now seems i can't configure it. No idea why it just became erratic. And there was a little crack on top of the screen and it seems it got wet under the screen with a white spot, so i guess it is going to be progressively worst with time. Even i tried the old trick of putting on a zip bag but after i left it for the night, when i opened it in the morning it was just wet...
My only question could be if this can be flashed to the North America firmware...

tonochito said:
My only question could be if this can be flashed to the North America firmware...
Click to expand...
Click to collapse
People who flashed to Korean Pie last year were able to flash to North American Open (NAO) Pie when that was released a month or two later.
For most people, cross flashing from AT&T to NAO first and then waiting for Pie would (using Dev Patched LGUP Upgrade mode) have been the better decision. Instead of cross flashing twice -- to Korean, then again to NAO -- to different variant firmware. NAO was what they really wanted in the first place.
OR if already on NAO, just be patient. Android 10 is coming.

ChazzMatt said:
People who flashed to Korean Pie last year were able to flash to North American Open (NAO) Pie when that was released a month or two later.
For most people, cross flashing from AT&T to NAO first and then waiting for Pie would (using Dev Patched LGUP Upgrade mode) have been the better decision. Instead of cross flashing twice -- to Korean, then again to NAO -- to different variant firmware. NAO was what they really wanted in the first place.
OR if already on NAO, just be patient. Android 10 is coming.
Click to expand...
Click to collapse
Well it seems that when NAO kdz will be available i will have the G8, as for me the fingerprint stuff drives me nuts right now that is not working lol, it has been a fantastic phone just well i guess it's time to move on. At least is good that can be flashed to NAO easily and with no problems like other brands out there.

Hello everyone,
I cross-flashed Android 10 on my v35 following this guide everything went as expected.
* I restored my backup from original Android 9 without any problems.
* Overall the phone feels faster, the camera experience is better(not sure that it has any benefits in the quality), unfortunately we cannot change lens during video
* The gCam 6.2 that I was using and was previously kinda stable now cannot save the picture, installed a 5.2 version that was stable in G6 -> v30 and v35 and I will be using this one until the problems with 6.x or 7.x are resolved.
* There are some korean apps that can be hidden but it they do not create any problems.
* Gestures are exactly what I needed and far better than FNG (apart from the customization options that are completely missing)
* Battery is also considerably better, but must be tested in time.

Hello to everyone!
Recently i bought an unlocked AT&T LG V35 which i am using it in Europe without any issue.
I want to cross-flash it in NA ULM kdz cause i don't want the AT&T firmware,but after a lot of reading here and there about the way i have to flash,i am a little bit confused,so i have some questions in order to go on.
My phone came with Pie version AWM20c and security patch level July 1,2019.
1)Which version of NA kdz should i download from LG firmwares site?
I see 4 versions..AIO,GFI,AMZ and USA..Maybe the latter is the most suitable?
2)Should i first crossflash it to Oreo NAO firmware and after update to Pie,(like used to do with LG V30 US998 that we must first install Nougat),or going straight away to NAO Pie?
3)The method of crossflashing is the same like LG V30 from other carriers to US998,as it is in Frankenstein thread?
4)Which of 2 methods between Refurbish and Partition DL is better for my case?
I want a completely clean kdz install,because a weird fact happens to my storage capacity in System,which has 16GB of storage used,and i suppose that all this used capacity,is because of AT&T bloated firmware,in addition to my 2 LG V30's,one is AT&T unlocked and the other is open EU 930,that both have about 10 GB used storage from system.
Thank you all in advance for your answers.

Succesfully crossflashed ULM firmware NAO USA 20f,android 9,security patch level February 1,2020.
Previous software version was android 9,AWM20c,security patch level July 1,2019.
I followed the same procedure of Frankenstein LG V30,V30+.
I used the Partition DL mode to flash and everything went fine..just in the end of the process and after the phone rebooted for first time,i got a notification referring the below:
"Decryption unsuccessful
The password you entered is correct,but unfortunately your data is corrupt.
To resume using your phone,you need to perform a factory reset.When you set up your phone after the reset,you"ll have an opportunity to restore any data that was backed up to your Google Account.
Reset phone"
I don't know if this notification is something bad,but all looked normal after the reset.
No issues till now,no AT&T bloatware,LG logo when powering on,instead of AT&T logo.
As others mentioned,the software version form,remains AWM,instead of ULM.
The previous version from AT&T was AWM20c,now it is AWM20f despite the fact that i have ULM firmware.
I hope my infos can help others in future.
Of course a big thank you goes to everyone here that contributes with their knowledge,making all these useful guides.