Develop Bugs

A must read for Google Wallet users on the Nexus.

Remember that Google Wallet exploit from a few days ago? The one that would allow*'brute-force' PIN attacks, but only on*rooted*Android devices? Well, another PIN-related security hole was discovered soon after, putting even non-rooted Androids at risk. As*Android Central points out, should your phone make its way into the wrong hands, your Google Wallet PIN number could be reassigned, allowing access to the prepaid account attached to the phone itself --*yikes. As such, the folks at Mountain View have taken action, shuttering provisions to prepaid cards until it finds a permanent fix for the problem. Despite the troubles, Google is sticking by its original tune, stating that Google Wallet offers multiples levels of protection (when used on*official*builds of Android) that go beyond traditional plastic cards, including your phone's lock screen. There's no estimate on when things will be back to normal, but you'll find Google's assessments and assurances about this situation at the source link below.
http://m.engadget.com/default/artic...n-related-securi/&category=classic&postPage=1
Via :*Android CentralSource :*Google*
Sent from my SAMSUNG-SGH-I727 using xda premium

Sigh, and if you lose your wallet what happens?

Anyone using their phone to make payments SURELY has a pin or pattern lock to protect their phones data... Right?

Would this be why I couldnt' use my "Wallet" tonight? Said it couldn't connect to the bank to get my account number. (the guy at McDonald's sure was looking at me funning trying to pay with my phone LOL)

Broken said:
Sigh, and if you lose your wallet what happens?
Click to expand...
Click to collapse
Exactly
Sent from my Nexus S 4G using xda premium

That second exploit has been posted in tons of forums almost since day one. Nothing new to report.
Sent from the third terrestrial planet in the system Solar from an electronic communications device.

Broken said:
Sigh, and if you lose your wallet what happens?
Click to expand...
Click to collapse
I rather lose my phone than my wallet.
Sent from my Galaxy Nexus using Tapatalk

it appears the the bank in charge of the prepaid cards has pulled its authorizations, just tried to set my wife's Wallet up on her phone and got the message:
"Prepaid is unavailable at this time. Please try again soon."

swiping my card is much more faster than turn on, unlock, tap, enter pin, tap, and then hit sent.

chevihemi said:
it appears the the bank in charge of the prepaid cards has pulled its authorizations, just tried to set my wife's Wallet up on her phone and got the message:
"Prepaid is unavailable at this time. Please try again soon."
Click to expand...
Click to collapse
Yeah, when I sign in to my wallet account it says "Cannot contact bank" under "user id"
*sigh*
of course there are attacks for this. they should make pinning your phone mandatory for wallet. just like when you encrypt your device, it forces you to use either pin, password, or pattern, no slide or face. just copy that...

zeke1988 said:
swiping my card is much more faster than turn on, unlock, tap, enter pin, tap, and then hit sent.
Click to expand...
Click to collapse
I just fully enjoy the look on the cashier's faces when paying with phone, not all that convenient but quite entertaining. Its the small things in life that bring joy, right??

hacky486 said:
they should make pinning your phone mandatory for wallet. just like when you encrypt your device, it forces you to use either pin, password, or pattern, no slide or face. just copy that...
Click to expand...
Click to collapse
Absolutely. If I am forced to use a pattern/pin/password lockscreen in order to store my VPN credentials, Wallet should require the same - in addition to any security within the app.

codesplice said:
Absolutely. If I am forced to use a pattern/pin/password lockscreen in order to store my VPN credentials, Wallet should require the same - in addition to any security within the app.
Click to expand...
Click to collapse
Google's lockscreen PIN setup sucks. There should be an option to automatically unlock the phone once the correct PIN has been entered, without having to press OK.

Evangelion01 said:
Google's lockscreen PIN setup sucks. There should be an option to automatically unlock the phone once the correct PIN has been entered, without having to press OK.
Click to expand...
Click to collapse
That is an option on most community ROMs... but then you would be rooted and breaking the First Rule of Wallet -whoops!
I use the pattern anyway. Works just like a PIN (think of the grid as a number pad) and sliding a finger across the screen is almost as quick as slide-to-unlock.
Come on, Google, let me use Wallet again!

Gotta love having money online that you can't use, access, or transfer. I just transferred a nice chunk of my paycheck onto google wallet right before this happened.

thunder2132 said:
Gotta love having money online that you can't use, access, or transfer. I just transferred a nice chunk of my paycheck onto google wallet right before this happened.
Click to expand...
Click to collapse
yea this is a serious annoyance. luckily i only have like 12 bucks left on my prepaid card but I dont have a citi master card so its rather bs

codesplice said:
That is an option on most community ROMs... but then you would be rooted and breaking the First Rule of Wallet -whoops!
I use the pattern anyway. Works just like a PIN (think of the grid as a number pad) and sliding a finger across the screen is almost as quick as slide-to-unlock.
Click to expand...
Click to collapse
Remove the root, relock bootloader. When you feel the need to update, do an adb backup, unlock and flash, restore backup, lock.

chirea.mircea said:
Remove the root, relock bootloader. When you feel the need to update, do an adb backup, unlock and flash, restore backup, lock.
Click to expand...
Click to collapse
Me, I'd rather just keep the root. That's kind of the point of a Nexus device to me

Can you force both a Fingerprint & a password to unlock your phone?

I've always been a privacy advocate and been knowledgeable about those law that protect us. After finding out judges can compel you to use your fingerprints to unlock your phone but compel you to give your password to unlock your phone/ your information, I've been looking to see if you can combine the two. I haven't found any yet but I thought someone here might now.
Is there a way require both a fingerprint and password/pattern/pin to unlock your phone every time? Would I have to download an app or something else? Is this even possible without me doing the coding myself?
Thanks in advance to anyone who answers or offers advice on how to achieve this.

Google gives you the option when you set up on initial boot .:good:

Icon000 said:
I've always been a privacy advocate and been knowledgeable about those law that protect us. After finding out judges can compel you to use your fingerprints to unlock your phone but compel you to give your password to unlock your phone/ your information, I've been looking to see if you can combine the two. I haven't found any yet but I thought someone here might now.
Is there a way require both a fingerprint and password/pattern/pin to unlock your phone every time? Would I have to download an app or something else? Is this even possible without me doing the coding myself?
Thanks in advance to anyone who answers or offers advice on how to achieve this.
Click to expand...
Click to collapse
I wouldn't be at all worried about being ordered to unlock a device with the finger print for various reasons.
- 3 wrong attempts locks the device via password
- rebooting the devices forces a password entry
- every 48 hours the device will require a password entry
So as you see there's no way that anyone could be sure that your device will be unlockable with your fingerprint, and just because you have a fingerprint sensor doesn't mean you've set it up to unlock your device.
Even if you happen to suddenly find yourself in some dystopian universe with a big brother government somehow being able to prove you use the finger print sensor, it would be child's play to simply reboot the device (can even be done in your pocket without looking at the screen) or to use your wrong finger 3 times, or for 48 hours to pass, etc.

How to store fingerprint, but not to unlock phone. HELP!

Hey everyone. Does anyone know how I can store a fingerprint on this but NOT use it to unlock the phone?
I want to be able to use it for apps like LastPass, or payments, but I do not want it able to unlock my phone. Can someone please tell me how to set that up? Thanks!

I don't have a solution for you, but I am very curious why you don't want it to unlock the phone?

skaforey said:
I don't have a solution for you, but I am very curious why you don't want it to unlock the phone?
Click to expand...
Click to collapse
Because of Security / privacy. Police or government personnel are allowed to force you to unlock your phone if it is only locked with a finger print.
However, if you lock your phone with only a pin or password (Something you KNOW), it is protected by the 5th Amendment, and they can't make you open your phone.

Drashnar said:
Because of Security / privacy. Police or government personnel are allowed to force you to unlock your phone if it is only locked with a finger print.
However, if you lock your phone with only a pin or password (Something you KNOW), it is protected by the 5th Amendment, and they can't make you open your phone.
Click to expand...
Click to collapse
This is not true at all. Also when you use a fingerprint you still have a passcode or pin that has to be set up.
Either way is it THAT big of a deal. What kind of situation would you get into that the police would ever want to get into your phone?? Even if they did.. what's on your phone that you would care if they saw...
I don't get people.

skaforey said:
I don't have a solution for you, but I am very curious why you don't want it to unlock the phone?
Click to expand...
Click to collapse
aholeinthewor1d said:
This is not true at all. Also when you use a fingerprint you still have a passcode or pin that has to be set up.
Either way is it THAT big of a deal. What kind of situation would you get into that the police would ever want to get into your phone?? Even if they did.. what's on your phone that you would care if they saw...
I don't get people.
Click to expand...
Click to collapse
Yes, you set a pin. But as long as you have your fingerprint, it no longer requires that pin to be used.
And it isn't a matter of what a person does or doesn't have on their phone. It's a matter of I don't want them on my phone without my permission, period.
As for it being true, it IS true. In addition to various court rulings, I was taught when I went for my CISSP Cert.
http://gizmodo.com/cops-can-make-you-fingerprint-unlock-your-phone-and-th-1653984192
http://www.latimes.com/local/california/la-me-iphones-fingerprints-20160430-story.html
------------------------
Anyway, this thread can be locked / deleted.
I used the support / chat feature on the phone to speak with a Google Rep. The functionality I want isn't present, but being of a security/privacy nature, has been escalated for inclusion in a future build. Thanks everyone.

This thread is to discuss how to accomplish the requested, not a discussion on whether or not you should be able to from a moral/legal standpoint.
That being said, I would love to know how to do this, but for a different reason entirely.

The closest thing I can offer is to reboot the phone if you have reason to believe you might be in a situation where the fingerprint could be used against you. When the phone boots, the PIN is required the first time instead of the fingerprint. If you press and hold the power button for about 10 seconds or long press for 1-2 seconds and tap restart, there are no other steps to reboot. It doesn't prompt or confirm the reboot.

I don't use fingerprint security at all.
But Doesn't Google have access to our pin codes and passwords.
That have to be used with biometric security?
If so a simple court order gets that done quickly.

Drashnar said:
Yes, you set a pin. But as long as you have your fingerprint, it no longer requires that pin to be used.
And it isn't a matter of what a person does or doesn't have on their phone. It's a matter of I don't want them on my phone without my permission, period.
As for it being true, it IS true. In addition to various court rulings, I was taught when I went for my CISSP Cert.
http://gizmodo.com/cops-can-make-you-fingerprint-unlock-your-phone-and-th-1653984192
http://www.latimes.com/local/california/la-me-iphones-fingerprints-20160430-story.html
------------------------
Anyway, this thread can be locked / deleted.
I used the support / chat feature on the phone to speak with a Google Rep. The functionality I want isn't present, but being of a security/privacy nature, has been escalated for inclusion in a future build. Thanks everyone.
Click to expand...
Click to collapse
When the police bist in just reset the phone... First login has to be a pin or password not a fingerprint.

If you're don't want you're phone used against you then take the ultimate plunge and smash that on the ground.
Or don't use the fingerprint scanner. Lol

Google Home does not let me add devices

I have been trying to set up a few devices (Roku, Smart Outlets primarily) on my 2XL using Google Home. However, after I enter my account details and click to Authorize, Google Home simply returns to the list of manufacturers and does not actually add anything. I have cleared cache and data from the Home app, restarted my phone etc. Nothing makes any difference.
The issue does appear to be with the phone though, as I was able to add the devices using a tablet where they immediately got linked to my Home account and let me assign a room.
Any ideas what could be causing it on the phone? My phone is not rooted, but was once, it does have an unlocked bootloader. Using a Root Checker it says "Sorry! Root access is not properly installed on this device" I am actually not concerned about having root either, as it was causing issues with Samsung Pay IIRC. While not the end of the world as I can set devices up on my tablet, is there any way I can get it working on the phone?
Thanks.

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.