Database Info

[Q] flashing to t-mobile?

Heyo
Recently bought an S3 for the main purpose of using it with softcard (the t-mobile and verizon versions are supported). I have a T-mobile SIM and from what I've read it should work without any modifying. However, softcard wants to be a stick in the mud and is not even letting me download it from google play because it's "not compatible".
I've tried changing the build.prop to the t-mobile S3, but that didn't do anything.
Is there a t-mobile rom that needs to be flashed?

If it's a VZW S3 do not flash a rom from the T-Mobile variant, you will hard brick it. As far as flashing to T-Mobile I'm not truly sure how that works
From my S3 running BlissStalk

ShapesBlue said:
If it's a VZW S3 do not flash a rom from the T-Mobile variant, you will hard brick it. As far as flashing to T-Mobile I'm not truly sure how that works
From my S3 running BlissStalk
Click to expand...
Click to collapse
Duly noted.
After trying to replace (to) the original build file, it went FUBAR. I ended up re-flashing CM 11. Made sure to make a fresh backup this time.
Any suggestions for at least getting the app to see if it will even load? or masking the device/product/whatnot?
(It's really odd; despite the fact that it's a qualified verizon phone, the verizon version of softcard does not show up in the store. IE. it says it's not compatible.)
https://play.google.com/store/apps/details?id=com.isis.mclient.verizon.activity
https://play.google.com/store/apps/details?id=com.isis.mclient.tmobile.activity
Something must have gotten "through" with one or more of the various things I tried since a few different devices showed up in device manager (like an HTC something which I have never used). I don't know if market helper was any help or not considering all it did was freeze.
I'm going to try copying the verizon version apk from another phone I can get it on, to the S3, and see if it will open....either with the t-mobile sim or a verizon one.

trgr said:
Duly noted.
After trying to replace (to) the original build file, it went FUBAR. I ended up re-flashing CM 11. Made sure to make a fresh backup this time.
Any suggestions for at least getting the app to see if it will even load? or masking the device/product/whatnot?
(It's really odd; despite the fact that it's a qualified verizon phone, the verizon version of softcard does not show up in the store. IE. it says it's not compatible.)
https://play.google.com/store/apps/details?id=com.isis.mclient.verizon.activity
https://play.google.com/store/apps/details?id=com.isis.mclient.tmobile.activity
Something must have gotten "through" with one or more of the various things I tried since a few different devices showed up in device manager (like an HTC something which I have never used). I don't know if market helper was any help or not considering all it did was freeze.
I'm going to try copying the verizon version apk from another phone I can get it on, to the S3, and see if it will open....either with the t-mobile sim or a verizon one.
Click to expand...
Click to collapse
Never used tap to pay whether it was ISIS(now softcard) or Google wallet. I know there have been certain roms people have gotten to work and some have had both positive and negative results. It seems to be touch and go from what I've read
From my S3 running BlissStalk

anybody else?

difference in verizon pixel and pixel direct from google

What the difference? I've heard people saying different apps installed but I have zero Verizon apps on my device even first boot didn't have them.

BlackKnight23 said:
What the difference? I've heard people saying different apps installed but I have zero Verizon apps on my device even first boot didn't have them.
Click to expand...
Click to collapse
Zero difference in software until you put a Verizon SIM in it. Then it downloads the VZ software. Google version does the same.
But after you let a VZ update to 7.1.1 you can no longer unlock the bootloader.
Sent from my Pixel XL using XDA Labs

To clarify @TonikJDK 's response, if you have a Verizon Pixel and it has a 7.1.0 build on it such as NDE63X, and if you put a non-Verizon SIM in, the phone then "updates" to the latest non-Verizon Pixel build, which at that time would've been NDE63V, and which would then not have the Verizon apps included.
Likewise, if you had the Google Edition on NDE63V, it was reported that if you put a Verizon SIM in, it would "update" to the latest Verizon image (again, at that time NDE63X). I can personally attest to this because I have a Verizon Pixel and I happened to 1. unlock my bootloader using DePixel8, 2. I flashed the NDE63V non-Verizon image, and 3. Re-inserted my Verizon SIM (which I'm actually using in an HTC 10 right now) and I mistook an update that was offered shortly after as being 7.1.1, but instead it was NDE63X, the Verizon build. I ended up taking the SIM back out and reflashing NDE63V, which has since updated to NMF26O and then NMF26Q.
One question I've been wondering about and haven't noticed if it's been addressed anywhere, the 7.1.1 builds are all the same for Verizon and non-Verizon. They're all NMF26O for the first release of 7.1.1 and NMF26Q for the second OTA of it.
So I'm wondering if putting a Verizon SIM in does anything anymore if you're on a stock 7.1.1 image. I could relatively easily find out, but it's not a huge priority.
Also, as long as you already unlocked the bootloader, nothing will re-lock it, even Verizon OTAs, unless you manually do so.
No idea if there'll be Verizon-specific builds again later.
Edit: Might soon find out, reportedly there's a new update for Verizon soon: NMF26U. It's not on Google's page, at least yet. http://forum.xda-developers.com/pixel/how-to/verizon-update-nmf26u-t3527199/post70281819#post70281819
Reference for factory image revisions: https://developers.google.com/android/images

I'm on NMF26O

So if you buy a Google Play Pixel and use a Verizon SIM you risk the chance of being screwed by Verizon by getting their builds pushed?
Sent from my Nexus 6 using Tapatalk

Bloodcrav said:
So if you buy a Google Play Pixel and use a Verizon SIM you risk the chance of being screwed by Verizon by getting their builds pushed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What do you mean screwed by Verizon? A Verizon phone and Google phone are different and the sim won't change that.

bobby janow said:
What do you mean screwed by Verizon? A Verizon phone and Google phone are different and the sim won't change that.
Click to expand...
Click to collapse
If I get a Google Play Pixel and use my Verizon SIM I'll be getting Verizon OTAs instead of the Google version.
Sent from my Nexus 6 using Tapatalk

Developer options, turn off automatic system updates. Install them yourself from Google's developer page.

Bloodcrav said:
If I get a Google Play Pixel and use my Verizon SIM I'll be getting Verizon OTAs instead of the Google version.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm not sure that is true, but even so they are the same. The updates are not what defines the device. Something else does and no one is saying or perhaps know.

Bloodcrav said:
So if you buy a Google Play Pixel and use a Verizon SIM you risk the chance of being screwed by Verizon by getting their builds pushed?
Click to expand...
Click to collapse
Bloodcrav said:
If I get a Google Play Pixel and use my Verizon SIM I'll be getting Verizon OTAs instead of the Google version.
Click to expand...
Click to collapse
bobby janow said:
I'm not sure that is true, but even so they are the same. The updates are not what defines the device. Something else does and no one is saying or perhaps know.
Click to expand...
Click to collapse
You get the Verizon OTAs if you don't disable the option for automatic updates, but there's nothing screwing about it. The Google Play Pixel can be unlocked at any time so you can do anything you want to your phone. The only people screwed are those who are on 7.1.1 on a Verizon Pixel with a locked bootloader.

roirraW "edor" ehT said:
You get the Verizon OTAs if you don't disable the option for automatic updates, but there's nothing screwing about it. The Google Play Pixel can be unlocked at any time so you can do anything you want to your phone. The only people screwed are those who are on 7.1.1 on a Verizon Pixel with a locked bootloader.
Click to expand...
Click to collapse
That being said, when I first boot up my new Pixel XL 128 on Verizon, I need to immediately go to developer options and shut down auto updates. I'm assuming I'll have to activate developer mode with the multiple taps one the build or something like that in ABOUT.
They pre-installed a SIM. So, I assume I'll have to rush to developer mode before it connects to Verizon. Although, I think I may have to call Verizon to activate the new SIM first.
Am I on the right track to avoid having bootloader locked?
Sent from my Nexus 9 using Tapatalk

bigsyd said:
That being said, when I first boot up my new Pixel XL 128 on Verizon, I need to immediately go to developer options and shut down auto updates. I'm assuming I'll have to activate developer mode with the multiple taps one the build or something like that in ABOUT.
They pre-installed a SIM. So, I assume I'll have to rush to developer mode before it connects to Verizon. Although, I think I may have to call Verizon to activate the new SIM first.
Am I on the right track to avoid having bootloader locked?
Click to expand...
Click to collapse
You have to remove the SIM before bottling. Then skip connecting to wifi

So if I'm already on the 7.1.1 update, there is literally nothing I can do to revert back to 7.1?
I am from VZ

iamjerry123 said:
So if I'm already on the 7.1.1 update, there is literally nothing I can do to revert back to 7.1?
I am from VZ
Click to expand...
Click to collapse
If you have the Verizon Pixel and you didn't unlock your bootloader before you got on 7.1.1, then correct.

aholeinthewor1d said:
You have to remove the SIM before bottling. Then skip connecting to wifi
Click to expand...
Click to collapse
Thank you. I will give it a shot today.
Sent from my HTC6525LVW using Tapatalk

roirraW "edor" ehT said:
To clarify @TonikJDK 's response, if you have a Verizon Pixel and it has a 7.1.0 build on it such as NDE63X, and if you put a non-Verizon SIM in, the phone then "updates" to the latest non-Verizon Pixel build, which at that time would've been NDE63V, and which would then not have the Verizon apps included.
Likewise, if you had the Google Edition on NDE63V, it was reported that if you put a Verizon SIM in, it would "update" to the latest Verizon image (again, at that time NDE63X). I can personally attest to this because I have a Verizon Pixel and I happened to 1. unlock my bootloader using DePixel8, 2. I flashed the NDE63V non-Verizon image, and 3. Re-inserted my Verizon SIM (which I'm actually using in an HTC 10 right now) and I mistook an update that was offered shortly after as being 7.1.1, but instead it was NDE63X, the Verizon build. I ended up taking the SIM back out and reflashing NDE63V, which has since updated to NMF26O and then NMF26Q.
One question I've been wondering about and haven't noticed if it's been addressed anywhere, the 7.1.1 builds are all the same for Verizon and non-Verizon. They're all NMF26O for the first release of 7.1.1 and NMF26Q for the second OTA of it.
So I'm wondering if putting a Verizon SIM in does anything anymore if you're on a stock 7.1.1 image. I could relatively easily find out, but it's not a huge priority.
Also, as long as you already unlocked the bootloader, nothing will re-lock it, even Verizon OTAs, unless you manually do so.
No idea if there'll be Verizon-specific builds again later.
Edit: Might soon find out, reportedly there's a new update for Verizon soon: NMF26U. It's not on Google's page, at least yet. http://forum.xda-developers.com/pixel/how-to/verizon-update-nmf26u-t3527199/post70281819#post70281819
Reference for factory image revisions: https://developers.google.com/android/images
Click to expand...
Click to collapse
Just setup 2 phones without updating from current version (7.1) by using the remove SIM/Bypass WiFi method. Updated them directly to 7.1.1 NMF26O and activated. Was done last night, and haven't had and VZW apps pushed to this point. Both rooted with TWRP RC1. Wonder if the newest build will push the apps. For my first Pixel, I had dropped down X and allow VZW to push out apps, the side loaded up to NMF26O. Either way, all 3 pixels work flawlessly.

b00ster23 said:
Just setup 2 phones without updating from current version (7.1) by using the remove SIM/Bypass WiFi method. Updated them directly to 7.1.1 NMF26O and activated. Was done last night, and haven't had and VZW apps pushed to this point. Both rooted with TWRP RC1. Wonder if the newest build will push the apps. For my first Pixel, I had dropped down X and allow VZW to push out apps, the side loaded up to NMF26O. Either way, all 3 pixels work flawlessly.
Click to expand...
Click to collapse
You know, I probably got the VZ apps because I have my Google account set to restore apps.... And I had them on my previous phone.
Not a big deal since any that are unwanted can be uninstalled.

b00ster23 said:
Just setup 2 phones without updating from current version (7.1) by using the remove SIM/Bypass WiFi method. Updated them directly to 7.1.1 NMF26O and activated. Was done last night, and haven't had and VZW apps pushed to this point. Both rooted with TWRP RC1. Wonder if the newest build will push the apps. For my first Pixel, I had dropped down X and allow VZW to push out apps, the side loaded up to NMF26O. Either way, all 3 pixels work flawlessly.
Click to expand...
Click to collapse
Hi, how's it going?
NMF26O and NMF26Q are used by both Google and Verizon, whereas there were Verizon-specific builds before NMF26O. It's rumored Verizon is going to have a NMF26U, and I have no idea if Google will have the same one or if Verizon's will once again be different than Google's. Also, if you have automatic updates turned off for OTAs in Developer Options, nothing will be forced on you. If NMF26U or a later build will be Verizon only, you could get OTA prompts unless you have that disabled.

roirraW "edor" ehT said:
Hi, how's it going?
NMF26O and NMF26Q are used by both Google and Verizon, whereas there were Verizon-specific builds before NMF26O. It's rumored Verizon is going to have a NMF26U, and I have no idea if Google will have the same one or if Verizon's will once again be different than Google's. Also, if you have automatic updates turned off for OTAs in Developer Options, nothing will be forced on you. If NMF26U or a later build will be Verizon only, you could get OTA prompts unless you have that disabled.
Click to expand...
Click to collapse
Going well "old" friend! Made the jump to the VZW variant while the jumping was good. FREE was a good price.
Spot on with the latest builds. I have APK backups of the VZW apps and can always add them into the other 2 phones, if needed.

Just fyi when I bought mine from Verizon it had 7.1. On it. I put SIM in it. I just made sure i didn't hit the new software update. I didn't have any problems. But it would be really easy to accidentally hit that update button

Bootloader unlock on NEW Verizon Pixels

Hey everyone,
I wanted to share a bit of a test that I just did on three Verizon Pixels. Specifically, when I got them from Verizon I did so via direct fulfillment (not a retail store). Doing this method I was able to boot loader unlock all three Verizon Pixels out of the box. The last one was about five minutes ago.
Here's what you'll need:
A new, in box Verizon Pixel - Important: Must be new in box!
A non-Verizon SIM card.
A Laptop
So, here's the rub. With these tests I was able to confirm that the Pixel does in fact use the SIM inserted into the phone at initial boot to determine boot loader lock ability. Long story short, if the Pixel is booted the first time with a Verizon SIM then the phone will be boot loader locked, and the OEM Unlock Toggle grayed out.
To unlock each of them I did the following:
Take the phone out of the box and inserted a co-workers AT&T SIM.
Booted the phone for the first time, and skipped all of the setup steps.
Enabled Developer Options, USB Debugging, and OEM Unlocking.
Accepted the RSA key and issues the command "adb reboot bootloader".
In bootloader mode issued the command "fastboot oem unlocking".
Flashed TWRP, and root.
Profit
The key to success here is ensuring the phone never gets booted initially with a VZW SIM inserted. This isn't so much phone hack as really a life/policy/process hack. Hope this helps!

Update: I've talked to a few knowledgeable folks on the topic who think the phones I got may have been part of a batch that wasn't loaded correctly. Having said that, Im sharing my experiences and would be curious to see what everyone else's experiences are. I'd also be curious to see the following, if anyone wants to try:
Place a non VZW SIM in the phone, factory default it, and see if its enabled again.
Take a brand new out of box VZW phone and ensure it doesn't connect to ANY network, rather it be wifi or Cell. See if OEM unlock is enabled.
Also, another added benefit is that the phones don't auto-download the few Verizon turdware apps.

Interesting...

Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.

deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?

deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.

TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.

deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.

deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.

TonikJDK said:
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.
Click to expand...
Click to collapse
What if you take a Google version, put in a VZW sim, connect, update. With it be grayed out? I doubt it.
Sent from my Pixel using XDA-Developers Legacy app

JAYNO20 said:
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.
Click to expand...
Click to collapse
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.

TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.

JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?

TCPDump said:
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.
Click to expand...
Click to collapse
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.

TonikJDK said:
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.
Click to expand...
Click to collapse
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.

TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Either way, long story short - Always check your pixel.

TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Excellent thought. Maybe they are tired of VZ's too and are faking all these mistakes. That would be cool.
But yea, with the 2 comming this fall maybe they night be getting​ nervous.

TCPDump said:
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?
Click to expand...
Click to collapse
Nope. Pulled the Sim before boot.

I had the exact same luck.
I had to sadly RMA my perfect rooted Pixel due to charger no longer functioning fully expecting a locked bootloader and 7.1.2. Verizon sent me one overnight. It had 7.1.2 but in developer options it had the same Allow OEM Unlocking slider NOT greyed out. I was then able to adb restart bootloader and adb bootloader unlocking and the phone prompted me and that was that. Adb booted to TWRP, installed RR Rom, vendor image, magick, TWRP, root. Can not believe the incredible luck.
Also wanted to say that I used my Verizon SIM card to do this and connected to WiFi on initial setup and I STILL managed to unlock it in time before anything locked itself.

deadlydecision said:
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.
Click to expand...
Click to collapse
What does it say on your my Verizon account?

google pixel on verizon won't OTA???

Was with ATT, no issues updating. Went over to Verizon Pre-paid. Phone will not OTA. Have spent 6 hours on phone with Verizon and google, nobody can figure it out. Not rooted, ever. We removed sim, no OTA. Wiped Network settings, nope. Safe boot, nope, factory reset, nope. My nexus 6p with "no carrier" (wifi calling only) updating perfect, my wife's 5x on cricket updating perfect, but not the pixel. Refuses ever since put on Verizon.
My theory is since Verizon sells a pixel, Google knocked me off OTA thinking Verizon supports it. Verizon says they didn't sell it, unlocked, so they won't push updates. Getting nowhere.
Anyone have thoughts or experience doing this same thing?

What about pulling the SIM and manually check for updates via wireless? If that fails you could also ADB sideload it.
https://developers.google.com/android/ota
Or flash the whole image if you arw unlocked.

Sideload it. Then you'll get next months OTA.
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
Sideload it. Then you'll get next months OTA.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
This will work.
Sent from my Pixel using Tapatalk

Side load may work. Will try it "next" time. After 2 mores hours with Google and Verizon, new sims, No sims, reboots... Google is sending a new phone. REally strange only started when put Verizon pre-paid sim in.

MLT2004 said:
Side load may work. Will try it "next" time. After 2 mores hours with Google and Verizon, new sims, No sims, reboots... Google is sending a new phone. REally strange only started when put Verizon pre-paid sim in.
Click to expand...
Click to collapse
They are sending you a refurbished phone. If you like your original device why not sideload the OTA now before you replace it. You can return the refurb if the ota sideload works. Seems to me like you had a very nice working Pixel until you didn't get one security update. Throwing the baby out with the bathwater? Just an opinion, do as you feel necessary.

Well, it also refused Oreo 8 update, and some other minor issues, and yea, I want to keep it, but my phone is watched/tracked by my broker-dealer (securities licensed) and I am forbidden to side load or root. This is to protect Clients. real bummer. Equifax has no repercussions, but I'm so locked down on cell phones and computers you can't believe it.

MLT2004 said:
Well, it also refused Oreo 8 update, and some other minor issues, and yea, I want to keep it, but my phone is watched/tracked by my broker-dealer (securities licensed) and I am forbidden to side load or root. This is to protect Clients. real bummer. Equifax has no repercussions, but I'm so locked down on cell phones and computers you can't believe it.
Click to expand...
Click to collapse
Oh, that's another story then. So they pay for your phone, usage and any replacements? Might be time to get a personal device with your own phone number. I'd never trust that kind of stuff. So when you get another device then they won't want to track that one? Didn't you say that it was on ATT and everything including updates was working fine? I think I'm missing some of the story. Either way, good luck with the replacement.

bobby janow said:
Oh, that's another story then. So they pay for your phone, usage and any replacements? Might be time to get a personal device with your own phone number. I'd never trust that kind of stuff. So when you get another device then they won't want to track that one? Didn't you say that it was on ATT and everything including updates was working fine? I think I'm missing some of the story. Either way, good luck with the replacement.
Click to expand...
Click to collapse
I'm an independent and pay 100% for all expenses. I loose my ability to do business if I don't let them control my electronics. I have a nexus 6p for personal on ATT, updates perfect. I wanted to move all svc to Verizon since I travel a lot to areas ATT has no coverage.

Got ya. Let them control the 6p and keep the Pixel pristine! Lol. Hope it works out for you. Curious, let us know.
Sent from my Pixel using XDA-Developers Legacy app

MLT2004 said:
Well, it also refused Oreo 8 update, and some other minor issues, and yea, I want to keep it, but my phone is watched/tracked by my broker-dealer (securities licensed) and I am forbidden to side load or root. This is to protect Clients. real bummer. Equifax has no repercussions, but I'm so locked down on cell phones and computers you can't believe it.
Click to expand...
Click to collapse
I had a very similar situation...I am on VZW and regularly got OTAs until about 6 months ago then they stopped. I also use a SIM from Project FI when I travel abroad. Somehow switching between the two caused OTAs to be ignored. My device is unrooted, bootloader locked and for corporate security purposes we have Aiwatch Agent to monitor violations. I am able to sideload via ADB and it is quite easy....it is definitely not the security risk that flashing a ROM is on an unlocked phone. Might be worth a shot.
Weirdly, OTAs came back to me after I registered for the O beta. Good luck.

LG Q7+ MetroPCS Update

Check your system update page in Settings, or download the KDZ here:
http://pkg02.lime.gdms.lge.com/dn/d...VA3XB91F9GO9/Q610MA10h_00_MPCS_US_OP_0823.kdz
Model: LMQ610MA
Software Version: Q610MA10H_00
OS Version: OMR1
Security update is August 1, 2018.

jlink38 said:
Check your system update page in Settings, or download the KDZ here:
http://pkg02.lime.gdms.lge.com/dn/d...VA3XB91F9GO9/Q610MA10h_00_MPCS_US_OP_0823.kdz
Model: LMQ610MA
Software Version: Q610MA10H_00
OS Version: OMR1
Security update is August 1, 2018.
Click to expand...
Click to collapse
Any chance you know how to get a link for the tmobile version?

kc6wke said:
Any chance you know how to get a link for the tmobile version?
Click to expand...
Click to collapse
I've been trying so I can convert my MetroPCS one to T-Mobile. I've been checking daily for an update.

Got a T-Mobile link. Enjoy.
http://pkg02.lime.gdms.lge.com/dn/d...96E0F9KQ6/Q610TA10h_00_TMO_US_OP_0823.kdz.kdz

How do you convert it from MetroPCS to T-Mobile and what are the benefits?
Reason I'm asking is I am looking to pick this phone up this weekend.
Thanks
jlink38 said:
Got a T-Mobile link. Enjoy.
http://pkg02.lime.gdms.lge.com/dn/d...96E0F9KQ6/Q610TA10h_00_TMO_US_OP_0823.kdz.kdz
Click to expand...
Click to collapse

kraftyland said:
How do you convert it from MetroPCS to T-Mobile and what are the benefits?
Reason I'm asking is I am looking to pick this phone up this weekend.
Thanks
Click to expand...
Click to collapse
It's actually pretty easy.
Wipe your device first to ensure there aren't any compatibility issues.
Then make sure you have LG USB drivers installed, and download the firmware I posted as well as this: https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Run the LG UP in there and select "Partition DL." Select the T-Mobile firmware to the file path area, and put the phone into download mode. Flash the phone. Once that is done, then boot your phone and wipe it once you're at the home screen. If you see that the available storage is something weird (like a negative number or only 8GB) then load the LG UP again, boot the phone into DL mode and then select "Refurbish" and load the T-Mobile firmware again. Once it boots, do a wipe from the phone, and you should be all set.
Also, if you get hit with the secure start up password, just put random characters in 30 times to wipe the phone clean. The tries have to be more than a few characters to register so keep that in mind.
Note: I have no idea how this will affect OTAs. If anyone has an idea, please let us know.
No benefits to flashing, I just have a T-Mobile SIM and like when it meshes up. It looks like the MA and TA versions of the phone get updated at the same time anyway.

Update: I got the latest update OTA from T-Mobile. The Q7 is now on September 1, 2018 security.

Benefits
So is there any benefits to switching to the T-Mobile version? I just swapped from Sprint to MetroPCs and went with Q7+

Edit: er, nevermind... I just saw someone's explanation above abt having a SIM. Don't see a delete option
~~~~~~~~~~~~~
Yeah, why? I got a Q7 from Metro ~3 wk ago and am really happy with the upgrade from my Aristo. (Except there seems to be no option to root yet, which, I admit, is a big one)
What would be the advantage of converting it to T-Mob? Personally I got kinda mad @ T-Mob's financing setup & I like the Metro benefits like G1 & Prime. It took a little effort to get the Q7 deal since T-Mob owns Metro, but it can be done

I think I found a benefit but not 100%. The metro version has widevine l3 which prevents from streaming in hd quality on anything such as Netflix. From what I heard this is purely software and the TMobile one allows it, would.be great if one of you that flashed can confirm. This app will tell you https://play.google.com/store/apps/details?id=com.androidfung.drminfo

Androider767 said:
I think I found a benefit but not 100%. The metro version has widevine l3 which prevents from streaming in hd quality on anything such as Netflix. From what I heard this is purely software and the TMobile one allows it, would.be great if one of you that flashed can confirm. This app will tell you https://play.google.com/store/apps/details?id=com.androidfung.drminfo
Click to expand...
Click to collapse
I wait on a reply to this as well. He'll im considering opening app on demo phone at tmobile lol

So I have successfully installed Tmobile
Firmware in my metro pcs Q7+ and it runs alot smoother and more responsive without all of the bloatware. Alot happier with phone now buy widevine is still Version 3. From what i know LG would of had to jump thru more hoops to certify a better encryption before they could even entertain the idea of vs one

Androider767 said:
I think I found a benefit but not 100%. The metro version has widevine l3 which prevents from streaming in hd quality on anything such as Netflix. From what I heard this is purely software and the TMobile one allows it, would.be great if one of you that flashed can confirm. This app will tell you https://play.google.com/store/apps/details?id=com.androidfung.drminfo
Click to expand...
Click to collapse
I have a T-Mobile Q7+ and it also is widevine l3.

It's security update time for the LG Q7+. Now I'm supposing it's for metro which service I use but recently flashed a T-Mobile firmware which is why I have the message from TMobile