Related
I have tried to use Android pay at several locations with no luck at all. Works fine at these locations with my other phones. NFC has been tested and working, just not with Android pay. Called customer service, but they said I should email, so that's what I did.
The phone vibrates as though it is working, but I then get a screen telling me to unlock to use Android pay. Even after using the fingerprint scanner again, it does not work. Android pay was a big reason why I chose this phone, hopefully there will be a fix.
arampapaz said:
I have tried to use Android pay at several locations with no luck at all. Works fine at these locations with my other phones. NFC has been tested and working, just not with Android pay. Called customer service, but they said I should email, so that's what I did.
The phone vibrates as though it is working, but I then get a screen telling me to unlock to use Android pay. Even after using the fingerprint scanner again, it does not work. Android pay was a big reason why I chose this phone, hopefully there will be a fix.
Click to expand...
Click to collapse
Looks the issue was with the fingerprint scanner. Android pay only works with a pin on this phone. Kinda lame.
Update: It does not work with a pin either. Had multiple failed attempts trying to unlock with a pin.
arampapaz said:
Looks the issue was with the fingerprint scanner. Android pay only works with a pin on this phone. Kinda lame.
Update: It does not work with a pin either. Had multiple failed attempts trying to unlock with a pin.
Click to expand...
Click to collapse
yesterday Google had a Android Pay update I have the same phone using Chase Bank cards it works on my blade V8 only after entering the phone unlock pin code then you have to place the phone to the pay terminal again or you can press the power button and unlock your phone pin code before taping the pay terminal fingerprint reader don't work on Android Pay now I already have call ZTE to fix this problem:crying::laugh:
I tried again last night and could not get it to work no matter what I did. Finally took out my card after 5 failed attempts.
arampapaz said:
I tried again last night and could not get it to work no matter what I did. Finally took out my card after 5 failed attempts.
Click to expand...
Click to collapse
Try a MC Donald's or a Duanereade store sometimes that one pay terminal is not working in the store
matthewtech770 said:
Try a MC Donald's or a Duanereade store sometimes that one pay terminal is not working in the store
Click to expand...
Click to collapse
I've tried in lots of locations. Locations where I have successfully used Android pay with other phones. The issue is definitely with this phone. I've had lots of phones and have never had an issue with Android pay with any of them.
arampapaz said:
I've tried in lots of locations. Locations where I have successfully used Android pay with other phones. The issue is definitely with this phone. I've had lots of phones and have never had an issue with Android pay with any of them.
Click to expand...
Click to collapse
:laughK Android operating system can be a monster sometimes strange your phone is not working properly well you can try this before trying to return your phone boot phone into recovery mode holding the volume up + power button and do a factory reset and set up again and see if that works maybe the factory firmware on your phone got corrupted:laugh:
matthewtech770 said:
:laughK Android operating system can be a monster sometimes strange your phone is not working properly well you can try this before trying to return your phone boot phone into recovery mode holding the volume up + power button and do a factory reset and set up again and see if that works maybe the factory firmware on your phone got corrupted:laugh:
Click to expand...
Click to collapse
Thanks for the suggestion, but I had to reset the phone already to fix the DND issue, and android pay didn't work before or after the reset. I am going to try with the Capital One app and see if the issue is with the phone or Android Pay.
Am I the only one having this issue? Does everyone have success with Andrid Pay?
Thanks!
So yesterday I used my phone to pay at 2 terminals with the Capital One app set as my default app and I had success both times. Unlocked with my fingerprint and the payment went through instantly. It appears the issues are with Android Pay and not the phone. I am going to change the default pay app to Android Pay today and see if I have any luck, if not I will stick with the Capital One app.
Mine works
Sounds like the app compatibility was the problem. I have an LG G Stylo that refuses to work in a food store no matter what. My ZTE Blade V8 Pro worked with no problem EVERYWHERE that I went that Accepted Android Pay
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.
Is there a way to downgrade the Google app? I have tried to uninstall on titanium backup but it will not fully uninstall. It will only downgrade to what I would assume is the stock version the phone came with. I then tried to install my older version but to no avail and the one that came stock on the phone is newer so it can't "update" with a older version of the app.
The reason why I want you to is to use Google voice to unlock the phone perform all tasks. I purposely kept a older version on my previous phone because of this reason. Or is there another way to enable it on a newer version of Google?
as far as I'm aware all versions of google allow voice unlock if you have taught the app to recognise your voice, I just had to stop using it as the phone would recognise my dads voice as me, so it's been a year or so since I used it, since my dad using google home and such when I was there would trigger my phone as well as the google home.
Belimawr said:
as far as I'm aware all versions of google allow voice unlock if you have taught the app to recognise your voice, I just had to stop using it as the phone would recognise my dads voice as me, so it's been a year or so since I used it, since my dad using google home and such when I was there would trigger my phone as well as the google home.
Click to expand...
Click to collapse
No it actually doesn't fully unlock the phone. Because it doesn't it doesn't perform version tasks you ask it too. Unless I'm missing something here. Please feel free to fill me in. I have included a screen shot of my old phone with this option.
Well it seems it will not let me add my screen shot
Bump....
Anyone?
Hi to all,
I have encounter a boring problem with op9 pro paired with bluetooth headset (more than one).
every time I said on assistant by my bluetooth headsets (aftershokx aeropex, oneplus bullets wireless Z) any commands like "call mom" "open garage Stefano" "turn on stairs light", and so on, assistant telle me to unlock phone first (????). On assistant the option of "personal results on lockscreen" and the one relative to bluetooth devices is activated, but: "[...]yes, but first you need to unlock the phone.".
on my op7 pro i try same commands without any problems. So... which is the problem?
It's very boring, expecially driving, unlock the phone to use it to make a simple call or to open my garage door.
+1
Turn on smart lock -> trusted devices
craznazn said:
Turn on smart lock -> trusted devices
Click to expand...
Click to collapse
This is not the solution... Is a workaround that I don't want to use for security reasons at work.
Don't use the screen lock.
Treat your phone like your hand and you don't need it.
Please reply with intelligent solution...
stefal639 said:
Please reply with intelligent solution...
Click to expand...
Click to collapse
I tried... for you, none.
You want security yet look what you're doing
Bank, g pay and other apps want security lock to function... So it's obvious that security lock screen need to be applied.
stefal639 said:
Bank, g pay and other apps want security lock to function... So it's obvious that security lock screen need to be applied.
Click to expand...
Click to collapse
I see what you mean... sorry.
I don't use any of those apps and especially voice assistant. Bixby is even worse.
Try this:
How to Use Google Assistant Without Unlocking Your Android Phone
Google Assistant is a handy companion to have on your Android smartphone or tablet. To really get the most out of Assistant’s hands-free features, you’ll want to make sure it can work even when your device is locked.
www.google.com
blackhawk said:
I see what you mean... sorry.
I don't use any of those apps and especially voice assistant. Bixby is even worse.
Try this:
How to Use Google Assistant Without Unlocking Your Android Phone
Google Assistant is a handy companion to have on your Android smartphone or tablet. To really get the most out of Assistant’s hands-free features, you’ll want to make sure it can work even when your device is locked.
www.google.com
Click to expand...
Click to collapse
It's yet activated...
stefal639 said:
It's yet activated...
Click to expand...
Click to collapse
Try clearing Goggle Play Services data.
Clear system cache.
Try a network reset (can't hurt).
You may have to delete/recreate the account if nothing else works.
Play with it... eventually you'll get it working.
made it, also clean flash of last ota...seems that something goes wrong with assistant because the problem still stay here also before a clean install.
stefal639 said:
made it, also clean flash of last ota...seems that something goes wrong with assistant because the problem still stay here also before a clean install.
Click to expand...
Click to collapse
Check permissions, notifications and make sure no power management is enabled.
Possible conflict with another app.
Lol, sounds like it's settings could be screwed up by default.
Try searching Google for the same issue even on different makes/models as you're no alone... someone has found the solution.
OK Google [to do that you need to unlock your phone] - Google Assistant Community
Seems that is a problem that appear randomly from 2 years (expecially on OP).
no solution from google
stefal639 said:
OK Google [to do that you need to unlock your phone] - Google Assistant Community
Seems that is a problem that appear randomly from 2 years (expecially on OP).
no solution from google
Click to expand...
Click to collapse
You can try contacting Google tech support. Occasionally they can be quit helpful... if they choose to.
A Bing search etc may yield better results.
I really try to keep my use of Google apps to a bare bones minimum.
I don't trust them... they earned it.
here is how i solve similar problem that not exactly the same but when i ask google assistance to turn flashlight for example it ask to unlock the screen 1st
1-open google app and press MORE
2-setting
3-google assistant
4-personalization
and final check every toggle on that screen (personal result, lock screen, etc. )
that should not ask to unlock the screen again check and let me know how it gose
yosry said:
here is how i solve similar problem that not exactly the same but when i ask google assistance to turn flashlight for example it ask to unlock the screen 1st
1-open google app and press MORE
2-setting
3-google assistant
4-personalization
and final check every toggle on that screen (personal result, lock screen, etc. )
that should not ask to unlock the screen again check and let me know how it gose
Click to expand...
Click to collapse
Still don't work
stefal639 said:
Still don't work
Click to expand...
Click to collapse
Why it look different so you use custom rom
yosry said:
Why it look different so you use custom rom
Click to expand...
Click to collapse
it's the latest OOS11, no custom rom. (italian language)
I am clueless did you did the voice match thing
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.