Develop Bugs

Root for the Pixel Xl from the google store?

Has anyone made anything that roots the pixel xl, the variant from the google store with the unlocked bootloader? I want to root my device, no need for custom recovery and install a system wide adblocker.

lovenokia said:
Has anyone made anything that roots the pixel xl, the variant from the google store with the unlocked bootloader? I want to root my device, no need for custom recovery and install a system wide adblocker.
Click to expand...
Click to collapse
Not yet. Partitions are different on the Pixel compared to other phones which is going to create a different method for root. It will happen when the devs figure it out. I am looking forward to tinkering with my new Pixel.

lovenokia said:
Has anyone made anything that roots the pixel xl, the variant from the google store with the unlocked bootloader? I want to root my device, no need for custom recovery and install a system wide adblocker.
Click to expand...
Click to collapse
Chain fire is waiting for his to be delivered to his country. Once he gets it then he will start working on root. He says it will be a little harder so it will take a little longer. Also the dev beanstown is on the waiting list for November so we will start seeing root and custom Roms by December I bet.

lovenokia said:
Has anyone made anything that roots the pixel xl, the variant from the google store with the unlocked bootloader? I want to root my device, no need for custom recovery and install a system wide adblocker.
Click to expand...
Click to collapse
Have you tried Adguard, no root needed and easy to toggle on/off, I started using it on my work phone and have found that it works very well, enough that I've switched to it on my personal phone and on the desktop.
Local link: http://forum.xda-developers.com/android/apps-games/adguard-ad-blocker-doesnt-require-root-t2958895
If you find a need for the premium functions googling "adguard stacksocial" will give you a much cheaper option for multi device usage.

rgbc said:
Have you tried Adguard, no root needed and easy to toggle on/off, I started using it on my work phone and have found that it works very well, enough that I've switched to it on my personal phone and on the desktop.
Local link: http://forum.xda-developers.com/android/apps-games/adguard-ad-blocker-doesnt-require-root-t2958895
If you find a need for the premium functions googling "adguard stacksocial" will give you a much cheaper option for multi device usage.
Click to expand...
Click to collapse
This is totally speculation, but since Adguard appears to use the android VPN to block ads, I imagine this may have some kind of negative affect on Wi-Fi assistant (if you have it enabled). I would test it, but honestly I don't trust that this company is tunneling all the traffic of all your apps through them. Seems a bit sketchy to me, but to each their own.
EDIT: Seems I misunderstood how the application functions. I'll still be waiting for root, but thanks to rgbc for the info.

bigbabys said:
This is totally speculation, but since Adguard appears to use the android VPN to block ads, I imagine this may have some kind of negative affect on Wi-Fi assistant (if you have it enabled). I would test it, but honestly I don't trust that this company is tunneling all the traffic of all your apps through them. Seems a bit sketchy to me, but to each their own.
Click to expand...
Click to collapse
The app sets up a local (on-device) VPN for ad filtering, web traffic isn't being routed through Adguard's servers.
I don't use wifi assistant (traffic routed through Google's servers) as I use a third party VPNfor all public wifi however when Adguard senses a remote VPN connection being setup it disabled it's self automatically. It also has a root option for alternative filtering methods for use with VPNs.
Cheers,
Rob

rgbc said:
The app sets up a local (on-device) VPN for ad filtering, web traffic isn't being routed through Adguard's servers.
I don't use wifi assistant (traffic routed through Google's servers) as I use a third party VPNfor all public wifi however when Adguard senses a remote VPN connection being setup it disabled it's self automatically. It also has a root option for alternative filtering methods for use with VPNs.
Cheers,
Rob
Click to expand...
Click to collapse
My bad, as I said total speculation. Didn't mean to spread mis-information. I'm probably still going to wait for root, but it's nice to know there is an alternative.

How to get mock GPS and pogo working on the Pixel XL?

As the title states, I want to be able to play Pokemon Go and use an app to spoof GPS. I do not care about Android Pay. I am really looking for advice on what to do, not how to do it. I am happy to do the legwork of figuring out how to install whatever is recommended.
I know I'm new here, so in an effort to show I've at least tried before creating a thread, here is what I've done so far:
- I tried various methods on a Verizon Samsung S4, but ultimately failed because the bootloader is locked. I learned a lot though, which was great (including never to buy phones from Verizon).
- I tried everything I could find on a Galaxy Tab S2. I got TWRP installed and tried every combination of SuperSU, suhide, rootswitch, Magisk, xposed, etc. Everything installed but pogo failed to start. I believe I need a different Kernel (although I can't remember specifically why), and there are not many options for that device.
- I got TWRP RC1 installed on my Pixel XL (purchased from Google, not Verizon), and successfully got dual boot working with a stock image in one slot, and rooted the other slot. I previously thought I needed to wait for Xposed to be released for Nougat, but I now think that may not be the case.
So, if my goal is strictly to manipulate GPS on my Pixel and still have pogo run, what is the path of least resistance? If I want to play without spoofing I can just boot my stock image.
This post by @Fenny (https://forum.xda-developers.com/showpost.php?p=70201392&postcount=106) says: "Really want to cheat at Pokemon go? Just patch the location service to always report that mock locations are off."
Could anyone elaborate on that? As I mentioned I don't care about Android Pay (although that would be a nice benefit). Is there perhaps a kernel for the pixel that will report mock locations as off, and still let pogo run? I am not familiar with how to patch the location service otherwise. I'd be willing to learn but I expect it is not a good starting place a for a newbie.
I also realize in the thread I linked above other people have reported they got pogo to run on a rooted Pixel using the patched files in that thread combined with suhide and rootswitch. If I do that, can I mock GPS locations without xposed? Or will I just be able to run pogo without spoofing?
Thanks for reading!

I've been able to spoof my gps and use a joystick app with pogo for a few months with just using Magisk and Magisk hide.. But now with the new update to pogo it will not allow you to use mock locations.. The pogo app loads but nothing shows on the maps(pokestops, Pokemon) and it says "failed to detect Location". Even with pogo running it says that and as soon as you stop the mock location app from spoofing it goes back to normal. Until someone makes an app that hides mock locations from pogo you won't be able too spoof.. I've even tried xposeds hide mock location module and it doesn't work as of now.
Sent from my HTC6545LVW using Tapatalk

So this is a definite no chance as soon as you take the march update
and if you dont you get stuck dealing with the pixel draining your data by redownloading the update over and over again forcing you to installit and loose the ability to spoof gps ffs

Can I add tethering without breaking apps that detect root?

I have a new Pixel 2 XL (google play edition) that I just received as a warranty replacement. I'm on a Verizon grandfathered (real) unlimited plan which disables tethering immediately, but that is a deal break for me. Before someone attacks me for "stealing" from Verizon, I would gladly pay for tethering if they would let me add it to my unlimited plan, but they won't.
My goal is to have my device work with apps that detect root and refuse to function (for example the USAA or ADT apps). As far as I know there's no way around this, but I'm hoping someone knows something I don't (other than modifying the apps APK). Other than enabling tethering I have no reason to have root access or access to the bootloader.
Thanks
Dan

those apps work with Magisk Hide? I know i have a couple apps that still throw a warning message about having dev tools etc enabled, but they still work. Not sure about the apps you listed.

pvtjoker42 said:
those apps work with Magisk Hide? I know i have a couple apps that still throw a warning message about having dev tools etc enabled, but they still work. Not sure about the apps you listed.
Click to expand...
Click to collapse
I totally forgot about magiskhide, I'll give it a shot. Thanks!

Bought Unlocked Pixel 3 From Google, & T-Mobile Crammed an App Onto the Phone Anyway!

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.

Question Work phone was enrolled in a13 without BL unlocked.

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.