Bought Unlocked Pixel 3 From Google, & T-Mobile Crammed an App Onto the Phone Anyway!
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
packetfire said:
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
Click to expand...
Click to collapse
I noticed the same thing on my pixel 3 xl and I'm on Google Fi and I can't uninstall that app to unlock my phone, I can only disable the app
lavin40 said:
I noticed the same thing on my pixel 3 xl and I'm on Google Fi and I can't uninstall that app to unlock my phone, I can only disable the app
Click to expand...
Click to collapse
What's worse is that the app itself claims that you CAN remove the app, after it has (correctly) determined that the phone is not locked.
Is your app also a "T-Mobile" app with a pink icon, or is it a variant that is branded for the Google FI service?
packetfire said:
What's worse is that the app itself claims that you CAN remove the app, after it has (correctly) determined that the phone is not locked.
Is your app also a "T-Mobile" app with a pink icon, or is it a variant that is branded for the Google FI service?
Click to expand...
Click to collapse
The app is pink I believe I got a Verizon pixel 3 xl cause the OEM unlock option is greyed out so I can't even root the phone
During the initial setup, there is a "sneaky" screen that asks if you want to finish (or something, I forgot). But if you expand that screen, there are several apps that Google intends to install, and you can opt out right there. Duo is definitely one of the apps, and several T-Mobile apps (I'm on TMO) as well as some others. I opted out and don't have any TMO apps.
Just like the above comment, it's in your 'additional-apps' section of the initial setup. If you uncheck? It doesn't install.
jbarcus81 said:
Just like the above comment, it's in your 'additional-apps' section of the initial setup. If you uncheck? It doesn't install.
Click to expand...
Click to collapse
Yep. This. If the app(s) are installed it's because you let the setup install them. They (Google/T-Mobile) didn't install them on the phone without your consent. You just missed where you have the option to not install them.
ktmom said:
During the initial setup, there is a "sneaky" screen that asks if you want to finish (or something, I forgot). But if you expand that screen, there are several apps that Google intends to install, and you can opt out right there. Duo is definitely one of the apps, and several T-Mobile apps (I'm on TMO) as well as some others. I opted out and don't have any TMO apps.
Click to expand...
Click to collapse
Well, that must be how it was done - anyway, the app is gone now, all by itself, so it appears to be yes, an undetectable silent install of an undelete-able "system app", but it seems that once you are verified as "unlocked", it self-deletes.
But I got nothing but the "unlocker", no Duo installed for me. (I like Google Authenticator - 2FA without anything else to carry, and SIM-swap-proof).
So this was the paternalistic Google trying to be helpful, but creeping people out yet again with their presumptuousness.
packetfire said:
Well, that must be how it was done - anyway, the app is gone now, all by itself, so it appears to be yes, an undetectable silent install of an undelete-able "system app", but it seems that once you are verified as "unlocked", it self-deletes.
But I got nothing but the "unlocker", no Duo installed for me. (I like Google Authenticator - 2FA without anything else to carry, and SIM-swap-proof).
So this was the paternalistic Google trying to be helpful, but creeping people out yet again with their presumptuousness.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.tmobile.pr.mytmobile
Tmobile silently installed this app on my unlocked pixel 3xl from best buy just yesterday after I set up my playstore account!
As a User app though.
packetfire said:
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
Click to expand...
Click to collapse
Just to show that it was indeed installed to the device...
dirtyreturn said:
Just to show that it was indeed installed to the device...
Click to expand...
Click to collapse
As stated in this thread, you accepted the install of the T-Mobile app during the setup process.
ktmom said:
As stated in this thread, you accepted the install of the T-Mobile app during the setup process.
Click to expand...
Click to collapse
That's just exclusive to the pixel 3? Stock Rom?
Just wondering since it's a first that this happened for me. Being on the same carrier with previous phones this did not happen.
dirtyreturn said:
That's just exclusive to the pixel 3? Stock Rom?
Just wondering since it's a first that this happened for me. Being on the same carrier with previous phones this did not happen.
Click to expand...
Click to collapse
I think I had to disable TMO apps during setup on my PH-1. I'm sure that Google has agreements with the carriers who offer the device. Even (esp?) when the device comes straight from Google.
And yes, stock ROM.
Related
Hi Folks,
So I'm posting in the Tmobile side since I picked up a Tmobile S4 even though I'm using it on AT&T to see if its a Tmobile thing, maybe some conflict from running on AT&T or just doesn't work at all...
I setup and have created/logged in with a Samsung account in the accounts pane and when I go online to try to find the phone I get two things. The first is the site says its not available in my region. And the second is following some details on their site about enabling it on the phone aren't working. It says add a Samsung account (done), go to settings, more, security then remote management (or remote control) then more steps but there is no remote management or remote control listed under settings.
Is this working for anyone at all?
re: signing in
Screwbal said:
Hi Folks,
So I'm posting in the Tmobile side since I picked up a Tmobile S4 even though I'm using it on AT&T to see if its a Tmobile thing, maybe some conflict from running on AT&T or just doesn't work at all...
I setup and have created/logged in with a Samsung account in the accounts pane and when I go online to try to find the phone I get two things. The first is the site says its not available in my region. And the second is following some details on their site about enabling it on the phone aren't working. It says add a Samsung account (done), go to settings, more, security then remote management (or remote control) then more steps but there is no remote management or remote control listed under settings.
Is this working for anyone at all?
Click to expand...
Click to collapse
Signing up and logging in to your tmobile, google or AT&T accounts are optional
and have nothing to do with how or if your phone will work.
You don't need to sign on to any of these three for your phone to work properly.
If your Tmobile M919 Galaxy S4 is NOT UNLOCKED it will not work on any network
except Tmobile.
It will not work with AT&T unless the phone is UNLOCKED.
Either way, the main thing I was trying to say is whatever your problem is it has
nothing to do with signing into tmoble or AT&T or gmail.
All three of those things are optional and have no effect on the phone working properly.
Awesome good to know. Now the only question is has anyone else gotten it to actually work if they have tried?
Screwbal said:
Awesome good to know. Now the only question is has anyone else gotten it to actually work if they have tried?
Click to expand...
Click to collapse
It's difficult to say if it will work or not since I have NO idea of what the problem is to start with.
All I know is that you have an Tmobile Galaxy S4 cell phone.
I don't even know if you ever tried a Tmobile sim card in it or whether the phone is unlocked and so on.
So I don't know how to be more helpful to you.
Misterjunky said:
It's difficult to say if it will work or not since I have NO idea of what the problem is to start with.
All I know is that you have an Tmobile Galaxy S4 cell phone.
I don't even know if you ever tried a Tmobile sim card in it or whether the phone is unlocked and so on.
So I don't know how to be more helpful to you.
Click to expand...
Click to collapse
No, I just mean the feature in general on the phone. Does anyone have the find my phone function through Samsung working or at least have tried and can confirm that it does work for you, or that you too can't set it up?
Screwbal said:
No, I just mean the feature in general on the phone. Does anyone have the find my phone function through Samsung working or at least have tried and can confirm that it does work for you, or that you too can't set it up?
Click to expand...
Click to collapse
You still are very unclear in what your really want to know, I still do not even know if your phone ever worked properly for you.
I still don't even know if your phone is UNLOCKED or not and I don't even know if you have a at&t sim or a tmobile sim card.
You never mention these things in any of your posts so how can anyone confirm anything you are asking to be confirmed?
If you use your phone on the Tmobile network you will have the option of free wifi calling which does not count against cellular minutes.
On the AT&T network there will be no option at all for wifi calling.
All the other features and options on the Galaxy S4 whether it's on the AT&T network or Tmobile network will be exactly the same.
You will not see or find any differences at all except for the wifi calling which I wrote about.
Anyway I am a bit busy, so I cannot help you anymore but I am sure there will be a lot of other people
here who can help you even more than I can.
Perhaps a mind reader will give you a hand if your lucky enough to find one.
The question is clear. Has anyone had this option ever work for them?
To be honest I am not sure how the option works but it maybe GPS related if Samsung is controlling it and not the carrier.
Wayne Tech Nexus
zelendel said:
The question is clear. Has anyone had this option ever work for them?
To be honest I am not sure how the option works but it maybe GPS related if Samsung is controlling it and not the carrier.
Wayne Tech Nexus
Click to expand...
Click to collapse
The question has nothing to do with whether the phone is network locked or not; or what carrier's sim card is installed. It has to do with whether a specific function in an app works or not for AT&T users with a TMO device. I have an unlocked TMO version on AT&T network, I'll try what you are talking about and get back with you. I'm reverting back to my stock backup to check. I can't seem to find the particular app you're using through Samsung apps and it doesn't appear to be present on the debloated stock ROM I'm using.
re: function
lordcheeto03 said:
The question has nothing to do with whether the phone is network locked or not; or what carrier's sim card is installed. It has to do with whether a specific function in an app works or not for AT&T users with a TMO device. I have an unlocked TMO version on AT&T network, I'll try what you are talking about and get back with you. I'm reverting back to my stock backup to check. I can't seem to find the particular app you're using through Samsung apps and it doesn't appear to be present on the debloated stock ROM I'm using.
Click to expand...
Click to collapse
You must be the mind reader I was talking about........ LOL
Have a great weekend...
Misterjunky said:
You must be the mind reader I was talking about........ LOL
Have a great weekend...
Click to expand...
Click to collapse
I just happen to have nothing but time on my hands.
---------- Post added at 02:59 PM ---------- Previous post was at 02:19 PM ----------
lordcheeto03 said:
I just happen to have nothing but time on my hands.
Click to expand...
Click to collapse
My experience so far is that I also cannot access the feature. You are correct in the fact that the "Remote Control" tab doesn't exist under Settings->More->Security. It should be below "Encrypt Device" but it isn't. The website findmymobile.samsung.com says that once you activate/register your Samsung account on the device, that menu will automatically be enabled; but from my experience (and yours as well apparently) that is definitely not the case.
I did a little research, and within a few minutes I was directed to a thread here on XDA from the SIII forums talking about this particular problem. Apparently, the carriers themselves have removed the ability to use Samsung's built-in mobile location features in preference of the carrier's own mobile location apps and services.
dumb! but I figured out that lookout can do it. going on 24 hours since I picked it up and dusting off my android cobwebs still for how I used to get by a year ago. Was trying to have to install some 3rd party app that I didn't know so tried the built in stuff with no luck but with lookout pre installed and I already know it I figure that should work just fine for me. Thanks folks for the feedback and conversation!
re: finally I understand...............
lordcheeto03 said:
I just happen to have nothing but time on my hands.
---------- Post added at 02:59 PM ---------- Previous post was at 02:19 PM ----------
My experience so far is that I also cannot access the feature. You are correct in the fact that the "Remote Control" tab doesn't exist under Settings->More->Security. It should be below "Encrypt Device" but it isn't. The website findmymobile.samsung.com says that once you activate/register your Samsung account on the device, that menu will automatically be enabled; but from my experience (and yours as well apparently) that is definitely not the case.
I did a little research, and within a few minutes I was directed to a thread here on XDA from the SIII forums talking about this particular problem. Apparently, the carriers themselves have removed the ability to use Samsung's built-in mobile location features in preference of the carrier's own mobile location apps and services.
Click to expand...
Click to collapse
AH, so that's what the guy was looking for, I just could not make much sense of what he was asking after reading his posts.
There are several apps at the play store which have the same or similar capabilities.
Here is a link to one of them, it's called "find my phone" it's a free app which finds phones which have been stolen or lost etc.
https://play.google.com/store/apps/...DEsImNvbS5mc3AuYW5kcm9pZC5waG9uZXRyYWNrZXIiXQ..
Misterjunky said:
AH, so that's what the guy was looking for, I just could not make much sense of what he was asking after reading his posts.
There are several apps at the play store which have the same or similar capabilities.
Here is a link to one of them, it's called "find my phone" it's a free app which finds phones which have been stolen or lost etc.
https://play.google.com/store/apps/...DEsImNvbS5mc3AuYW5kcm9pZC5waG9uZXRyYWNrZXIiXQ..
Click to expand...
Click to collapse
Yeah, but if it's supposed to be provided by the manufacturer it would stand to reason that it would be available to everyone who bought the device. Apparently though, our carriers tend to believe their own software is far superior to that of those who manufactured the device... I personally don't even use that stuff as I never turn GPS on in the first place; so in the event that my phone is stolen or lost, that kind of software won't do me any good to begin with.
Hey guys- in poking around with my phone in the first 24 hour of ownership, I found that the software status says "modified", instead of "official". Stopped in the local vzw store that I bought it through, and they had nothing for me. Had me take my sd card out and restart. Stayed the same(surprise), so they emailed their own tech support and I havent heard from them since. I do have dev options showing, but I have also heard that some folks have official with dev options activated.
Anyone else have a "modified" software status? Any idea what could be modified?
Just checked mine, same thing. Modified. I do not have dev options active.
The NSA is really slipping up.
tourbound129 said:
The NSA is really slipping up.
Click to expand...
Click to collapse
Definitely was a thought! Until I can find out what is modified, I dont really want to get another one.
Yeah probably Verizon changing it out of the box
Sent from my LG-H811 using Tapatalk
I have a VS986 and it says "Official" under "Software Status."
Mine says modified. Any apps frozen/disabled? Wondered if that's what it was on my end.
danaff37 said:
Mine says modified. Any apps frozen/disabled? Wondered if that's what it was on my end.
Click to expand...
Click to collapse
May be a good call, I also disabled some apps.
I have apps disabled and dev options and says official
Sent from my G4 using your mom
Dennisg34 said:
I have apps disabled and dev options and says official
Sent from my G4 using your mom
Click to expand...
Click to collapse
Same here
jackwagon06 said:
May be a good call, I also disabled some apps.
Click to expand...
Click to collapse
Mine is the same way, Modified right from the get go.
I'm thinking that covers the basics of what we could have done without root. Modified sub forum! Lol
I have a TON of disabled apps and mine says "Official".
Pre Ordered and shipped from Verizon.
Mine also says Official. Maybe we can start looking into differences here..Does anyone that says modified have screen tapping issues? Or any other issue?
Its a reach..I know.
Mine says Official (blue from Best Buy )
Mark me down as modified. Metallic gray prettier preordered from Best Buy... haven't even activated it yet, but have disabled all the Verizon bloat.
Edit...I do have Developer Options enabled.
Apps disabled...
Caller Name ID
Cloud
DT Ignite
Message+
My InfoZone
My Verizon Mobile
NFL Mobile
Support & Protection
Verizon Location Agent
Verizon Login
VZ Navigator
Best Buy pre order and mine says official
I would try a factory reset if it says modified
Modified here. Software version 10B, Build LMY47D. Phone was shipped directly from VZW.
scrillakev said:
Mine also says Official. Maybe we can start looking into differences here..Does anyone that says modified have screen tapping issues? Or any other issue?
Its a reach..I know.
Click to expand...
Click to collapse
I would say that I may have screen tapping issues(modified). Its enough to notice, but it will always work on the second tap. I dont know if its me fat fingering the thing.
[SIM unlocked] LG D693n Stylus turned "partially" SIM unlocked after Super-Sume
I think this is weird enough for a new thread: I recently got this G3 Stylus and, as usual, I proceeded on rooting. This time using KingRoot. Done easily, I must admit. Now, since KingRoot installed some unwanted and "unreadable" stuff, I've turned my sight over Super-Sume (you know what it does)... Super-Sume performed it's job as expected, replacing everything it has to with Supersu. Following the process and right after reboot, something weird happend: my installed SIM card appeared as an "invalid SIM card". Rebooted again and still the same message. Turned off the phone, took the SIM card out, reinstalled, turned on again... same message. Device had lost network connection, but it was able to send and receive data!!!... started research about the particular issue, but found nothing similar anywhere. Then I've tried three SIM cards from different carriers and they worked flawlessly. Installed the "invalid SIM card" again (which is from the phone's original carrier, BTW) and the issue was still there. Then, about 12 hours later, data was lost as well and SIM became useless in this phone. Tested another card from the very same carrier and it was useless to; however, this two cards worked perfectly on three different phones, so not a card issue. Contacted Super-Sume developer and he told me there's NO relation between his app and such kind of issue. OK. Contacted carrier and they know nothing. OK. Next, I resolved to look for some hint at "Replace Kinguser with SuperSu" XDA thread, where fellow member "CVangelo" suggested to check if phone asks for unlock code. Well, it does. So the phone is SIM locked after all, but JUST FOR ONE CARRIER!!! which happens to be the phone's original carrier. Not to blame Super-Sume for the mess. Perhaps is a "gift" left from KingRoot due to getting rid of it. Or perhaps is just coincidental. Point is, this is clearly a weird issue as most of you can see; at least until somebody rises her/his hand with an explanation. Who's first?
CNK80Q3MX said:
Point is, this is clearly a weird issue as most of you can see; at least until somebody rises her/his hand with an explanation. Who's first?
Click to expand...
Click to collapse
Only thing I would say is that it is network locked but in the exact reverse of what you would expect. Never heard of such a thing or knew it was even possible. Is there anyone with experience in network locks who can explain exactly what kind of network lock this? It may help explain what might have happened and how.
Sent from my Nexus 7 using XDA Free mobile app
CVAngelo said:
Only thing I would say is that it is network locked but in the exact reverse of what you would expect. Never heard of such a thing or knew it was even possible. Is there anyone with experience in network locks who can explain exactly what kind of network lock this? It may help explain what might have happened and how.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Hey... no one seems interested. I'm assuming no one will until someone else have the same issue. Though, I've been making some questions to some other "lock acquainted" people and most say it is kinda "blacklisted" lock "for sure". In such cases, the original carrier locks first; if you try another network carrier SIM, it will work for typically 3 to 5 more days and up to 8 (no more than that) then, that carrier will lock as well, and so on. Thing is, this phone IS NOT "blacklisted" (I've already made an inquiry for that in the global page) and there's about 17 days since original carrier network became locked. So... weirdness remains. On the other hand: How is that you're using "XDA free app"? I'm forced to use "Premium" because "Free" simply didn't work anymore on my devices. I like free version because it has more options and you can sign and stuff...
CNK80Q3MX said:
Hey... How is that you're using "XDA free app"? I'm forced to use "Premium" because "Free" simply didn't work anymore on my devices. I like free version because it has more options and you can sign and stuff...
Click to expand...
Click to collapse
Really? I didn't even know there was Premium version. What's even the point of that? Lol. Whaddaya mean, the Free version didn't work anymore? Mine just keeps on ticking...but I only started using it after I had been signed up on the website and participating on XDA via the desktop browser for ages. Had you signed up on the website, or only on the app?
BW, do you have the apk of the free app? I can send it to you if you don't.
Sent from my Nexus 7 using XDA Free mobile app
CVAngelo said:
Really? I didn't even know there was Premium version. What's even the point of that? Lol. Whaddaya mean, the Free version didn't work anymore? Mine just keeps on ticking...but I only started using it after I had been signed up on the website and participating on XDA via the desktop browser for ages. Had you signed up on the website, or only on the app?
BW, do you have the apk of the free app? I can send it to you if you don't.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Well, signed both... "Premium" was once the paid app, as far as I know. I wasn't using "Free" app for a month or so; then when I required it again, it just didn't open. So I checked the store and they've turned "Free" into an earlier android versions app, thus it won't work for me anymore. Had to download "Premium" (now "Free") to keep going. If you can send the "Free" apk, I'll give it a try... Thanks!
I'm using esim on my p6p and i never installed a sim card in it so why do I keep getting this notification?
Did you check out what the Device Unlock app had to say?
I can't find that app plus the device isn't unlocked, I'm still paying it off through TMobile and using it on TMobile esim
What does clicking on the notification do? Have you tried contacting T-Mobile about the issue?
Clicking it does nothing, haven't contacted TMobile yet. I didn't have this issue till I updated to 12L beta so idk if that has anything to do with it
spart0n said:
Clicking it does nothing, haven't contacted TMobile yet. I didn't have this issue till I updated to 12L beta so idk if that has anything to do with it
Click to expand...
Click to collapse
Could be, and since 12L Beta 3 wouldn't be considered "supported" since it isn't stable, they probably couldn't help anyway. I didn't know you were on 12L at all. That's an important detail.
spart0n said:
I can't find that app plus the device isn't unlocked, I'm still paying it off through TMobile and using it on TMobile esim
Click to expand...
Click to collapse
The T-Mobile Device unlock app (GOOGLE PIXEL ONLY) is available in the Google Play Store:
T-Mobile Device Unlock (Google - Apps on Google Play
Request a Mobile Device Unlock from T-Mobile without calling Customer Service
play.google.com
It should work on your device,as it does on mine w/Android 13 installed.
Mine is unlocked,so,I'm not sure what kind of messaging/code it will give you,guessing something related to the unlocked/still financed state of your phone.
FYI,if you're considering the temporary unlock option for B/L unlock status,I'm certain this is not sufficient for doing so.
If your main objective is to just simply make the notification go away permanently,IDK if there's anything accessible in Android 12L's settings for notifications to disable it.
Try long pressing on the notification,it may expand to present an option to silence this particular notification.
Also,is your phone otherwise working w/the e-SIM?
It appears so,as I see the LTE icon in your status bar........
Hi all,
My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.
I've contacted T-Mobile. They've given the green light on their end to unlock.
When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."
TMobile is saying there is nothing they can do, and google is telling me the same thing as well.
Any ideas? Just looking to get this device back to Android 12.
AwkwardUberHero said:
Hi all,
My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.
I've contacted T-Mobile. They've given the green light on their end to unlock.
When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."
TMobile is saying there is nothing they can do, and google is telling me the same thing as well.
Any ideas? Just looking to get this device back to Android 12.
Click to expand...
Click to collapse
What device unlock app?
What happens when you:
Connect to wifi.
Enable OEM Unlocking in developer options.
Download latest platform-tools
Run the fastboot command: fastboot flashing unlock
A second hand work phone Pixel 6 Pro that's already on 13. That phone has seen some **** in a very short time.
T-Mobile pushes the unlock to you. If you downloaded the app from the Play store, it's the wrong one. Using the sim unlock one in T-Mobile sim settings also doesn't seem to work.
Alekos said:
What device unlock app?
What happens when you:
Connect to wifi.
Enable OEM Unlocking in developer options.
Download latest platform-tools
Run the fastboot command: fastboot flashing unlock
Click to expand...
Click to collapse
It's connected to WiFi, but the oem unlocking item is greyed out.
I haven't tested running the command in fastboot yet. Was worried what would happen.
LLStarks said:
A second hand work phone Pixel 6 Pro that's already on 13. That phone has seen some **** in a very short time.
T-Mobile pushes the unlock to you. If you downloaded the app from the Play store, it's the wrong one. Using the sim unlock one in T-Mobile sim settings also doesn't seem to work.
Click to expand...
Click to collapse
They asked me to download the device unlock app from the app store. I did, and used it.
They said that they have approved the unlock on their end.
I'm quite confused. This is my first carrier locked pixel.
AwkwardUberHero said:
Hi all,
My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.
I've contacted T-Mobile. They've given the green light on their end to unlock.
When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."
TMobile is saying there is nothing they can do, and google is telling me the same thing as well.
Any ideas? Just looking to get this device back to Android 12.
Click to expand...
Click to collapse
If you get a second hand phone from work that has experimental beta software installed from a previous owner, which is clearly a massive issue for a work phone in several regards (security just one) why don't you just give it back and demand a new one? Not sure how your company acts, but mine would instantly seize that phone, there is not knowing what might have been installed on it, it might even be a non-genuine A13 build. It's simply a risk most companies would never take, at least if they have some credibility.
This is clearly not your problem to deal with. It's noble that you invest so much of your "free" time for this, but it's a waste of time imho. It's not your job to make that phone work properly. If it's not in a working, proper state at the moment of delivery from employer to employee, you need to demand a working model.
AwkwardUberHero said:
It's connected to WiFi, but the oem unlocking item is greyed out.
I haven't tested running the command in fastboot yet. Was worried what would happen.
Click to expand...
Click to collapse
If it's greyed out, the Bootloader is still locked. You'll need to contact them (either through your work or TForce) in order for them to unlock it. But corporate devices (from T-mobile) might have different policies on unlocking. Best to contact your IT Dept.
But as the @Morgrain has suggested, this phone should have been wiped and factory reset by your employer to a proper working state. It wasn't. That's concerning. Many of us have worked for companies who are, shall we say, less than competent, at IT. But it's 2022 - there's no excuse.
Alekos said:
If it's greyed out, the Bootloader is still locked. You'll need to contact them (either through your work or TForce) in order for them to unlock it. But corporate devices (from T-mobile) might have different policies on unlocking. Best to contact your IT Dept.
But as the @Morgrain has suggested, this phone should have been wiped and factory reset by your employer to a proper working state. It wasn't. That's concerning. Many of us have worked for companies who are, shall we say, less than competent, at IT. But it's 2022 - there's no excuse.
Click to expand...
Click to collapse
I was going to give it one last shot before trading it back in. TMobile said that they have set it to be unlocked on their end, and that factory resetting it and checking it again to see if the bootloader is allowed to be unlocked might be a solution.
I've flashed roms, rooted and such for many years, but I've never had one like this. If TMobile did flip the switch in their end for the permission to unlock the bootloader, then it should show this, even in a developer preview software build, right?
I doubt that factory resetting this and trying it again will do any good, but I guess it's worth a shot.
AwkwardUberHero said:
They asked me to download the device unlock app from the app store. I did, and used it.
They said that they have approved the unlock on their end.
I'm quite confused. This is my first carrier locked pixel.
Click to expand...
Click to collapse
Don't use the play store app. It doesn't work. The phone has a built in app. It doesn't work either.
The unlock doesn't need to be approved. It has to be pushed to your phone. Your phone will alert you that it's unlocked without doing anything. T-Mobile cannot be the one telling you it's unlocked. After that, you reboot and bootloader unlock should no longer be grayed out
You got a bad rep who doesn't know what they are doing.
Your IT also had no business giving you a phone this compromised.
To be clear - T-Mobile wouldn't unlock your bootloader or be able to toggle the OEM unlocking themselves, they would only make your phone carrier unlocked. It just so happens that on T-Mobile devices (and maybe some others but definitely not Verizon), that carrier-unlocking a phone permanently usually also makes it so that you can toggle OEM unlocking. It's also possible that corporate management of your phone prevents it from ever having the OEM Unlock toggle be ungrayed, but on the other hand, I would think they would have it locked down to where someone can't opt the phone into a Beta program, and it's also strange that T-Mobile would do, or attempt to do anything regarding the phone since you don't own it or pay for the phone service.
As several have said, it's not your phone, it's not your responsibility, I wouldn't even think your work would want you to be messing with it even though you're capable.
I would also add that unless your work has the capability to make their phones have OEM Unlocking ungrayed out, and re-grayed out at will, they'd never be able to fix the Android 13 DP/Beta situation themselves - they would have to go to T-Mobile et cetera, although after they fix it, I would expect them to want to toggle it back and make it so that no one else can toggle it again. I guess your work just doesn't manage their associate's phones very closely.
LLStarks said:
Don't use the play store app. It doesn't work. The phone has a built in app. It doesn't work either.
The unlock doesn't need to be approved. It has to be pushed to your phone. Your phone will alert you that it's unlocked without doing anything. T-Mobile cannot be the one telling you it's unlocked. After that, you reboot and bootloader unlock should no longer be grayed out
You got a bad rep who doesn't know what they are doing.
Your IT also had no business giving you a phone this compromised.
Click to expand...
Click to collapse
So, they approved the carrier unlock.
The app does that part. I've done that a few times. But, the oem unlock is still greyed out.
Morgrain said:
If you get a second hand phone from work that has experimental beta software installed from a previous owner, which is clearly a massive issue for a work phone in several regards (security just one) why don't you just give it back and demand a new one? Not sure how your company acts, but mine would instantly seize that phone, there is not knowing what might have been installed on it, it might even be a non-genuine A13 build. It's simply a risk most companies would never take, at least if they have some credibility.
This is clearly not your problem to deal with. It's noble that you invest so much of your "free" time for this, but it's a waste of time imho. It's not your job to make that phone work properly. If it's not in a working, proper state at the moment of delivery from employer to employee, you need to demand a working model.
Click to expand...
Click to collapse
Yes and no. Not everybody works for high security big bank or government. Depends on the employer and depends on the job for the employer.
One piece of good news is that it is VERY unlikely that its a non-original A13. After all, its locked still. That means that the build had to be signed by the appropriate keys in order to install.
roirraW edor ehT said:
To be clear - T-Mobile wouldn't unlock your bootloader or be able to toggle the OEM unlocking themselves, they would only make your phone carrier unlocked. It just so happens that on T-Mobile devices (and maybe some others but definitely not Verizon), that carrier-unlocking a phone permanently usually also makes it so that you can toggle OEM unlocking. It's also possible that corporate management of your phone prevents it from ever having the OEM Unlock toggle be ungrayed, but on the other hand, I would think they would have it locked down to where someone can't opt the phone into a Beta program, and it's also strange that T-Mobile would do, or attempt to do anything regarding the phone since you don't own it or pay for the phone service.
As several have said, it's not your phone, it's not your responsibility, I wouldn't even think your work would want you to be messing with it even though you're capable.
I would also add that unless your work has the capability to make their phones have OEM Unlocking ungrayed out, and re-grayed out at will, they'd never be able to fix the Android 13 DP/Beta situation themselves - they would have to go to T-Mobile et cetera, although after they fix it, I would expect them to want to toggle it back and make it so that no one else can toggle it again. I guess your work just doesn't manage their associate's phones very closely.
Click to expand...
Click to collapse
So, TMobile said for me to down load the device unlock app. I did that, and ran it. It told me it was carrier unlocked.
The OEM unlocking portion is greyed out in develope options though still, and saying to connect to the internet or contact my carrier. Which confuses me. If it's sim unlocked, then I should be able to unlock the bootloader, right?
AwkwardUberHero said:
So, TMobile said for me to down load the device unlock app. I did that, and ran it. It told me it was carrier unlocked.
The OEM unlocking portion is greyed out in develope options though still, and saying to connect to the internet or contact my carrier. Which confuses me. If it's sim unlocked, then I should be able to unlock the bootloader, right?
Click to expand...
Click to collapse
As I said, your work may have more control over your phone since it's their phone, not yours. They may have something in place that keeps OEM Unlocking disabled, no matter what. I'm just speculating, I don't know if that's the case. I really couldn't guess any further why it's still grayed out for you. I wouldn't even bother spending any further effort on it. If it happened to me, I would tell work about it and let them deal with it.
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.
Then again, so does Apple and Intune not being thorough enough.
LLStarks said:
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.
Then again, so does Apple and Intune not being thorough enough.
Click to expand...
Click to collapse
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?
Last attempt before I give up on it.
LLStarks said:
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.
Then again, so does Apple and Intune not being thorough enough.
Click to expand...
Click to collapse
I know with regards to non-phone Google things at the very large corporation I'm at - where we've used Google for everything (except for phones) for a decade - that some things that are under the control of our internal Google Admins in our IT department slip through and then later get corrected.
As regards to phones, I don't have a corporate phone, but they used to supply some Samsung models for a brief period where they experimented with allowing both iPhone and Android devices, but they stopped probably because it was just more work for them to manage both iPhone and Android devices. I can't speak as to whether they had the capability to keep people from unlocking their bootloader or keep folks from opting in to DPs/Betas, but that was also ~6 years ago.
AwkwardUberHero said:
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?
Last attempt before I give up on it.
Click to expand...
Click to collapse
If you can't toggle the OEM Unlocking (it's still grayed out), then you can't unlock the bootloader.
I mean, this kinda depends on whom you work for. Some companies that give out work phones choose Android as they can customize the build and can view the phone's usage. I can't remember if it was the FBI or the police somewhere who mentioned doing this exact thing in order to visibly track what is being done on these phones. So if your company is knowledgeable (which I suppose is a rarity nowadays, haha) and deals with some information that must be kept secure, then I would just confront someone in the IT department and ask them what the deal is "as the phone isn't running a stable and secure version of Android". Because if it's customized for phone usage tracking, then doing what you are doing could get you into some trouble.
Not worth taking such risks with something that isn't yours. Where I work in IT, people always mess with (and too frequently break) devices that they are borrowing - and then complain about having to pay $250 for cracking the display or destroying the case of a laptop that they are simply borrowing.
It seems that nobody reads the contracts that they are signing or has enough common sense to not destroy something that isn't theirs.
AwkwardUberHero said:
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?
Last attempt before I give up on it.
Click to expand...
Click to collapse
To be fair, I would do anything and everything to unlock the device because I like messing with technology (even if it comes from work).
The Toggle is greyed out right - but is it on or off - because when the device is unlocked, the toggle will be greyed out (but toggled to the on position). When you boot into fastboot, does it say device state locked?
Do a factory reset in recovery mode and check again.
Alekos said:
To be fair, I would do anything and everything to unlock the device because I like messing with technology (even if it comes from work).
The Toggle is greyed out right - but is it on or off - because when the device is unlocked, the toggle will be greyed out (but toggled to the on position). When you boot into fastboot, does it say device state locked?
Do a factory reset in recovery mode and check again.
Click to expand...
Click to collapse
It's greyed out and off.
I haven't checked it in fastboot yet.