I have the 6 pro unlocked bought from Google. I use it on Verizon. I found out that when I got the phone and put the Sim in that the November update was not downloaded and installed. I factory reset the device and did not insert the SIM and I got the update. I now have SD1A.210817.036 installed. I this the correct version? I understand there is a November update 037 now but I don't see that. Now I am concerned that when the December update comes out that I wont get that either. Does anyone here know if Google and Verizon have fixed this issue?
Thanks
We don't know because it's just too early to tell. Word is they stopped pushing the .037 OTA at all, although I don't know that from personal experience. I've got the unlocked P6P running on AT&T and I got all the OTAs almost immediately. The next OTA should be out next Monday, but I believe Verizon variants have often lagged at least a little when though the OTA is available directly from Google for all variants at the same time.
Also commonly, after several updates the Verizon version of the firmware gets merged into a single universal firmware.
Regardless of any of this, you can flash either the Verizon version of the OTA manually, getting it directly from Google's site. You may even be able to flash the non-Verizon OTA manually, but there's no reason to avoid the Verizon version since you're using it with Verizon.
With the Pixel 5, unlocked but using Verizon as my service provider: there was a 50-50 shot on some sort of delay on updates. I think it has to do with their mmWave 5G and other providers (US and international) either do not use mmWave; or aren't as proprietary as Verizon.
Is there any benefit to running the Verizon version on an unlocked pixel 6 pro?
RVO27 said:
Is there any benefit to running the Verizon version on an unlocked pixel 6 pro?
Click to expand...
Click to collapse
The best answer is "maybe", leaning towards "probably".
For example, and probably a bad example but the only one I got. When I got my unlocked HTC 10 before I got the Pixel 1 in 2016, and I was still with Verizon at the time, I had no idea that I was going to have to jump through hoops to get Verizon's radio.img on my HTC 10, which was rooted so no big deal. Now maybe there was a whole Verizon firmware I could flash, but if I just wanted to use the regular unlocked HTC 10 firmware, I had to put the Verizon radio.img on there to even work on the network.
On the Pixels, I don't think it's ever been quite like that. I think you can use the regular firmware just fine on Verizon, but maybe, just maybe, it will work better with their proprietary bits that come with the Verizon version of the firmware.
Also, I know sometimes in the past that if you had the unlocked firmware on a device but used a Verizon SIM (or in other cases with some phones, an AT&T SIM, and probably applied to T-Mobile too), that you would then receive an OTA automatically to put you on their particular variant of the most recent firmware. So unless you disabled updates in Developer Options, you'd get the "proper" firmware for your usage anyway, and of course, being rooted is the ultimate method to avoid the proprietary variant of the firmware since OTAs will most likely refuse to even update a rooted device, although you should still turn automatic updates off since there's a chance it could instead soft-brick your device.
jjbender said:
I have the 6 pro unlocked bought from Google. I use it on Verizon. I found out that when I got the phone and put the Sim in that the November update was not downloaded and installed. I factory reset the device and did not insert the SIM and I got the update. I now have SD1A.210817.036 installed. I this the correct version? I understand there is a November update 037 now but I don't see that. Now I am concerned that when the December update comes out that I wont get that either. Does anyone here know if Google and Verizon have fixed this issue?
Thanks
Click to expand...
Click to collapse
I have an unlocked p6 (not pro) that I got from Amazon which I am using on Verizon. When I first set it up without a sim card it got the 36 update OTA without a problem. I put in the sim card and didn't receive the 37 update long after it was released. Finally I tried an inactive Mint sim (t-mobile network) and got the update when I checked for a system update using the settings menu. It probably would have worked without a sim also.
Rumors are that there will be a December update so I will be checking then. If I don't get it I will try without a sim or with an inactive sim. But that will mean that automatic updates don't work for unlocked p6s on verizon.
I did finally sideload the .037.A1 which is the Verizon version so I will see if I start getting the OTA updates.
Thanks all
sdbe said:
Rumors are that there will be a December update so I will be checking then.
Click to expand...
Click to collapse
For clarification, if you didn't know (forgive me if you did), the Pixel 6/Pro will receive an update every single month from the time it came out until five years later (so ~ October 2026). Especially some of the later years they might only be security updates - not Android version updates, but they will come like clockwork I believe the first Monday of every month.
Personally i wouldn't use the vzw firmware as there are hardware differences between the two especially radio
Related
Hi all
purchased a phone from an online store in AUS which claimed to be a sm-n910F note 4 but had hacked software, after some help from this site it was identified as being an Verizon SM-910V in cognito, long story short flashed it with original sm-n910V software, when it starts its says Verizon and works fine on the Australian network. I plugged it into KIES and upgraded to Marshmallow firmware but I am one of the 900 Million phones that has the QUALCOMM vulnerability and I want to patch it when the security patch is released in september but when I go to use the software update on the phone it says this service is temporarily unavailable assuming because its looking for the Verizon network and I am on virgin residing in Australia. When I go into KIES it tells me there is a firmware upgrade but its trying to install the full Marshmallow firmware again. Anybody know of a way to trick the phone into thinking its on the Verizon network so it will download updates or could I simply grab the security download when its released and install directly to the phone via ODEN. Lesson never buy a phone that's coming from over seas its a real headache if you end up with something dodgy, thanks to anybody who can offer advice
Wayne
Hi all
purchased a phone from an online store in AUS which claimed to be a sm-n910F note 4 but had hacked software, after some help from this site it was identified as being an Verizon SM-910V in cognito, long story short flashed it with original sm-n910V software, when it starts its says Verizon and works fine on the Australian network. I plugged it into KIES and upgraded to Marshmallow firmware but I am one of the 900 Million phones that has the QUALCOMM vulnerability and I want to patch it when the security patch is released in september but when I go to use the software update on the phone it says this service is temporarily unavailable assuming because its looking for the Verizon network and I am on virgin residing in Australia. When I go into KIES it tells me there is a firmware upgrade but its trying to install the full Marshmallow firmware again. Anybody know of a way to trick the phone into thinking its on the Verizon network so it will download updates or could I simply grab the security download when its released and install directly to the phone via ODEN. Lesson never buy a phone that's coming from over seas its a real headache if you end up with something dodgy, thanks to anybody who can offer advice
Wayne
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
tuxdreamerx said:
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
Click to expand...
Click to collapse
Verizon model is fine for what the phone is.
You shouldn't have any issues using it on T-Mobile USA . Verizon phones are sim unlocked . The only thing with the Verizon version is that if it had the update where they don't let the bootloader unlock then you can't unlock it and root. Besides that you can use it on TMobile as a regular Google phone.
Sent from my Pixel XL using Tapatalk
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
This is partially false, I'm using a Verizon pixel XL on TMO and when I dropped out of beta, Google rolled out the TMO branch to my phone.
If you can depixl8 it and unlock the bootloader, you can flash custom Roms or the factory images to your heart's desire with no issues. Just never relock the bootloader, since it won't be able to be unlocked again(if it truly is a Verizon pixel XL)
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
You can sideload updates to a locked device so OP could sideload a current ota from tmobile. It can in fact beneficial to run the tmobile software on tmo because of optimizations for network connectivity
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
STraver said:
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
Click to expand...
Click to collapse
Should be able to just pop in the ATT sim
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I guess that'll be the big question. If the phone was only a display model since it was released. I wonder if the display models get the updates pushed automatically... I will find out tomorrow.
Well the phone came with 7.1.2 so no fun for me. Thanks for the info from everyone.
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Grubling said:
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Click to expand...
Click to collapse
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
tuxdreamerx said:
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
Click to expand...
Click to collapse
Google points to that being a Verizon SKU. But with the build number being non-Verizon, you might be able to unlock it.
There may be some relevant information here: https://forum.xda-developers.com/pixel/help/bootloader-unlock-verizon-pixels-t3616101
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
Count your blessings, most of us with Verizon models are still locked on other carriers.
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
zfk110 said:
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
Click to expand...
Click to collapse
You can unlock the bootloader on Verizon.
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
I literally just did this 2 months ago. Got a pixel xl and it was a verizon phone but I have Tmobile. The phone can be unlocked, it can be rooted, it can be rommed, yes it can! Mine came with 711 or 712 cant remember but whatever doesnt matter. Just follow the guide in the other thread by @Homeboy76, it's a GREAT read and tutorial. It will put you from stock nougat to stock pie, but afterwards you can go to nougat, oreo, or pie. I know because after I did it, i went to an custom rom, then to a custom oreo rom, back to stock pie, back to custom pie lol. I would put a link up to the thread but idk how to do hyperlinks lmao, i skipped that day of school.
Got notification this morning for a 217mb update ending in ASGF. Pretty weird since we just got the July patch only two weeks ago, after not getting an update in over two months. Definitely not complaining though! Sorry if repost
I don't see that update on my G975U1
I got it too. August US unlocked
Just got the update!
is available via samfirm
Unfortunately i just switched over to carrier firmware for faster updates. Now Samsung finally does it right. At least carriers should be releasing it in a week or two.
Sent from my SM-G975U using XDA Labs
Whats new in this August update?
ultimatdan said:
Whats new in this August update?
Click to expand...
Click to collapse
No idea. There are no details listed on the Samsung website or in the notification popup. I mean the security patch has been brought up to date (August) but other than that, I can't say.
Got the notification today.... Hopefully someone can breakdown what is in the update because 200+mb is rather hefty right?
what sim are you guys using to get this ota update?
bklynsoulja said:
what sim are you guys using to get this ota update?
Click to expand...
Click to collapse
U1 updates are released by Samsung. One gets a U1 update as long as one has a existing U1 firmware irrespective of the SIM.
WhoIsJohnGalt1979 said:
U1 updates are released by Samsung. One gets a U1 update as long as one has a existing U1 firmware irrespective of the SIM.
Click to expand...
Click to collapse
yea but tmobile sim was causing a delay and alot of people even samsung reps recommend to use another sim to just update the U1 firmware
bklynsoulja said:
yea but tmobile sim was causing a delay and alot of people even samsung reps recommend to use another sim to just update the U1 firmware
Click to expand...
Click to collapse
I believe you have been misinformed. Please be patient and wait for the update to show up on your phone if you are already on U1 firmware or download the latest U1 firmware using Frija and Odin flash. All the very best.
Update is due to a exploit in the chip. Some one can take control of our phones if we are on the same wifi. Kudos for the fast update.
I updated and now I don't get icons on my lock screen for notifications. Anybody else have the same problem?
975u1 August Firmware Patch T mobile
Hello,
I have a US unlocked 975u1 and use Tmobile. No one seems to know what I am talking about with an Aug Update. I have spent time on the Phone with Samsung and Tmob customer service. Stuck on July patch ASCB. Night mode is still disabled. Samsung Switch has nothing on it as of this morning.
How do I get the firmware everyone else is on? If I get a sim card from another carrier, does that sim need to be activated in order to get the latest patch? I am clueless here.
phillyspecial said:
Hello,
I have a US unlocked 975u1 and use Tmobile. No one seems to know what I am talking about with an Aug Update. I have spent time on the Phone with Samsung and Tmob customer service. Stuck on July patch ASCB. Night mode is still disabled. Samsung Switch has nothing on it as of this morning.
How do I get the firmware everyone else is on? If I get a sim card from another carrier, does that sim need to be activated in order to get the latest patch? I am clueless here.
Click to expand...
Click to collapse
G975U1UES2ASGF is on Frija for SPR and VZW download one of them
phillyspecial said:
Hello,
I have a US unlocked 975u1 and use Tmobile. No one seems to know what I am talking about with an Aug Update. I have spent time on the Phone with Samsung and Tmob customer service. Stuck on July patch ASCB. Night mode is still disabled. Samsung Switch has nothing on it as of this morning.
How do I get the firmware everyone else is on? If I get a sim card from another carrier, does that sim need to be activated in order to get the latest patch? I am clueless here.
Click to expand...
Click to collapse
U1 firmware with the August security patch and Night mode is available and does end in ASGF.
Unless you flashed T-Mobile firmware on your U1 model or you purchased an unlocked U1 with T-Mobile firmware already installed (I'm not sure how to check that in the settings but U1 firmware doesn't come with any T-Mobile branded apps) you should be receiving OTA updates from Samsung rather than T-Mobile.
The U1 OTA update was pushed weeks ago making it the only OTA update we received before the carriers.
If you have T-Mobile firmware you could flash the U1 firmware manually and receive OTA updates from Samsung but you will lose T-Mobile branded apps that aren't available in the Play Store. The U1 firmware has also been receiving updates long after the carriers prior to August--in early July we were still on the May security patch.
If you manually flash VZW or SPR firmware as the other member suggested don't flash the User Data partition or you will also get Verizon or Sprint's apps and bloatware. If you do manually flash either of those you will no longer receive OTA updates and will need to keep manually flashing updates in the future.
So I bought my phone directly from Samsung. USA version with snapdragon processor and its non-branded to any carrier, basically an unlocked Galaxy S10+. Its model number is sm-g975u1. Sim card is from Tmobile, my cell phone carrier.. I have software from July 1st, g975u1ueu2ASGB
What do you recommend in my scenario.
Thank you
QUOTE=jhs39;80190022]U1 firmware with the August security patch and Night mode is available and does end in ASGF.
Unless you flashed T-Mobile firmware on your U1 model or you purchased an unlocked U1 with T-Mobile firmware already installed (I'm not sure how to check that in the settings but U1 firmware doesn't come with any T-Mobile branded apps) you should be receiving OTA updates from Samsung rather than T-Mobile.
The U1 OTA update was pushed weeks ago making it the only OTA update we received before the carriers.
If you have T-Mobile firmware you could flash the U1 firmware manually and receive OTA updates from Samsung but you will lose T-Mobile branded apps that aren't available in the Play Store. The U1 firmware has also been receiving updates long after the carriers prior to August--in early July we were still on the May security patch.
If you manually flash VZW or SPR firmware as the other member suggested don't flash the User Data partition or you will also get Verizon or Sprint's apps and bloatware. If you do manually flash either of those you will no longer receive OTA updates and will need to keep manually flashing updates in the future.[/QUOTE]
phillyspecial said:
So I bought my phone directly from Samsung. USA version with snapdragon processor and its non-branded to any carrier, basically an unlocked Galaxy S10+. Its model number is sm-g975u1. Sim card is from Tmobile, my cell phone carrier.. I have software from July 1st, g975u1ueu2ASGB
What do you recommend in my scenario.
Thank you
QUOTE=jhs39;80190022]U1 firmware with the August security patch and Night mode is available and does end in ASGF.
Unless you flashed T-Mobile firmware on your U1 model or you purchased an unlocked U1 with T-Mobile firmware already installed (I'm not sure how to check that in the settings but U1 firmware doesn't come with any T-Mobile branded apps) you should be receiving OTA updates from Samsung rather than T-Mobile.
The U1 OTA update was pushed weeks ago making it the only OTA update we received before the carriers.
If you have T-Mobile firmware you could flash the U1 firmware manually and receive OTA updates from Samsung but you will lose T-Mobile branded apps that aren't available in the Play Store. The U1 firmware has also been receiving updates long after the carriers prior to August--in early July we were still on the May security patch.
If you manually flash VZW or SPR firmware as the other member suggested don't flash the User Data partition or you will also get Verizon or Sprint's apps and bloatware. If you do manually flash either of those you will no longer receive OTA updates and will need to keep manually flashing updates in the future.
Click to expand...
Click to collapse
[/QUOTE]
I would look for the ASGF U1 firmware for U1 with Frija or SamFirm. I'm not sure why you didn't get the OTA.
New LM-G820UM (AT&T) purchased from ebay. Using on T-Mobile and have update question
Hi all,
Grabbed a G8 Thinq for my son off ebay (which scared me but it was cheap). It's an AT&T variant but it's working just fine with T-Mobile. However, the security updates are from July and I'd like to update. I tried LG Bridge and get a "cannot check software version" error. Before I send this thing back I wanted to check here. I understand that OTA updates are super slow to arrived when you unlock and switch carriers but will I ever get one? Is there another way to update this thing?
I'm pretty Android savvy but just haven't messed around on here since my Nexus 6P days. Thanks!
sahively said:
Hi all,
Grabbed a G8 Thinq for my son off ebay (which scared me but it was cheap). It's an AT&T variant but it's working just fine with T-Mobile. However, the security updates are from July and I'd like to update. I tried LG Bridge and get a "cannot check software version" error. Before I send this thing back I wanted to check here. I understand that OTA updates are super slow to arrived when you unlock and switch carriers but will I ever get one? Is there another way to update this thing?
I'm pretty Android savvy but just haven't messed around on here since my Nexus 6P days. Thanks!
Click to expand...
Click to collapse
There should be newer firmware kdzs that you can download and manually flash using lgup for Att variant just look it up.
antintin said:
There should be newer firmware kdzs that you can download and manually flash using lgup for Att variant just look it up.
Click to expand...
Click to collapse
Thanks, I'll do some reading on that. Appreciate the look.
Are AT&T KDZs even available? I can't find them anywhere that doesn't look like a complete scam site.
sahively said:
Are AT&T KDZs even available? I can't find them anywhere that doesn't look like a complete scam site.
Click to expand...
Click to collapse
AT&T is known not to release KDZs ever, and to only provide updates to postpaid AT&T customers. I assume that's true with G8 as well. I saw those unlocked AT&T G8 on eBay for $320, but I wouldn't expect any updates, nor would I expect warranty to be honored.
TheDannemand said:
AT&T is known not to release KDZs ever, and to only provide updates to postpaid AT&T customers. I assume that's true with G8 as well. I saw those unlocked AT&T G8 on eBay for $320, but I wouldn't expect any updates, nor would I expect warranty to be honored.
Click to expand...
Click to collapse
Welp, this baby's going back. Just ordered up a T-Mobile version for only $20 more so "hopefully" it will actually update. Thanks for the guidance.
sahively said:
Hi all,
Grabbed a G8 Thinq for my son off ebay (which scared me but it was cheap). It's an AT&T variant but it's working just fine with T-Mobile. However, the security updates are from July and I'd like to update. I tried LG Bridge and get a "cannot check software version" error. Before I send this thing back I wanted to check here. I understand that OTA updates are super slow to arrived when you unlock and switch carriers but will I ever get one? Is there another way to update this thing?
I'm pretty Android savvy but just haven't messed around on here since my Nexus 6P days. Thanks!
Click to expand...
Click to collapse
Sprint unlocked variant updates just fine on any carrier
sahively said:
Welp, this baby's going back. Just ordered up a T-Mobile version for only $20 more so "hopefully" it will actually update. Thanks for the guidance.
Click to expand...
Click to collapse
T-Mobile is pretty good with updates. I have T-Mobile V30 on Red Pocket GSMA (AT&T MVNO) and receive updates.
But T-Mobile phones are very hard to carrier unlock. They can only be unlocked with a T-Mobile Device Unlock app, which queries T-Mobile servers for approval. If the phone is relocked (such as after LG repair, or if you get a warranty replacement) you won't be able to unlock it again unless you're a T-Mobile customer and/or have had the phone on their service for some time (40 days postpaid, 1 year prepaid). It can't be unlocked with a code like other phones.
Like AT&T, Sprint also doesn't release KDZs, but as noted they are less restrictive about OTA updates. T-Mobile and Verizon release KDZs.
Carrier phones generally suck for the same reason that carriers generally suck: Everything they do is always designed to suck you
TheDannemand said:
T-Mobile is pretty good with updates. I have T-Mobile V30 on Red Pocket GSMA (AT&T MVNO) and receive updates.
But T-Mobile phones are very hard to carrier unlock. They can only be unlocked with a T-Mobile Device Unlock app, which queries T-Mobile servers for approval. If the phone is relocked (such as after LG repair, or if you get a warranty replacement) you won't be able to unlock it again unless you're a T-Mobile customer and/or have had the phone on their service for some time (40 days postpaid, 1 year prepaid). It can't be unlocked with a code like other phones.
Like AT&T, Sprint also doesn't release KDZs, but as noted they are less restrictive about OTA updates. T-Mobile and Verizon release KDZs.
Carrier phones generally suck for the same reason that carriers generally suck: Everything they do is always designed to suck you
Click to expand...
Click to collapse
Yeah we just wait for bootloader unlock now
sahively said:
Hi all,
Grabbed a G8 Thinq for my son off ebay (which scared me but it was cheap). It's an AT&T variant but it's working just fine with T-Mobile. However, the security updates are from July and I'd like to update. I tried LG Bridge and get a "cannot check software version" error. Before I send this thing back I wanted to check here. I understand that OTA updates are super slow to arrived when you unlock and switch carriers but will I ever get one? Is there another way to update this thing?
I'm pretty Android savvy but just haven't messed around on here since my Nexus 6P days. Thanks!
Click to expand...
Click to collapse
Have a look on this thread:
https://forum.xda-developers.com/lg...e-released-t3958979/post81261151#post81261151
I faced the precise same situation, I was able to get the updates by moving my # to ATT prepaid.
antintin said:
Yeah we just wait for bootloader unlock now
Click to expand...
Click to collapse
The T-Mobile V30 has official bootloader unlock, as the only North American carrier model. I believe the same was true with V20: Just Enable OEM Unlock in Developer Settings, boot into fastboot mode (Vol- while inserting cable with phone off) and enter fastboot oem unlock. The problem is the bootloader is neutered, with fastboot flash and fastboot boot commands stripped out. So even after BL unlock fastboot cannot be be used to flash or boot TWRP. But it still relaxes the secure boot chain. So once @runningnak3d found a way to flash TWRP using Download Mode (laf) we were golden.
Of course that laf vulnerability is long since fixed. And I am sure somebody must have already checked if the T-Mobile G8 has official bootloader unlock like earlier LG phones. Right? Or are we just assuming it doesn't because other carrier models don't? I only began following the G8 threads recently, so I wouldn't know.
TheDannemand said:
The T-Mobile V30 has official bootloader unlock, as the only North American carrier model. I believe the same was true with V20: Just Enable OEM Unlock in Developer Settings, boot into fastboot mode (Vol- while inserting cable with phone off) and enter fastboot oem unlock. The problem is the bootloader is neutered, with fastboot flash and fastboot boot commands stripped out. So even after BL unlock fastboot cannot be be used to flash or boot TWRP. But it still relaxes the secure boot chain. So once @runningnak3d found a way to flash TWRP using Download Mode (laf) we were golden.
Of course that laf vulnerability is long since fixed. And I am sure somebody must have already checked if the T-Mobile G8 has official bootloader unlock like earlier LG phones. Right? Or are we just assuming it doesn't because other carrier models don't? I only began following the G8 threads recently, so I wouldn't know.
Click to expand...
Click to collapse
No g8 has it