Forum Discussion
Enabled FRP and now I'm stuck
We're building an Emm solution so while testing I enabled FRP and thought of giving it a shot.
So, after factory resetting all i can see is a google window asking me to verify with the account that was previously in the device. What I cannot understand is there was no account signed in except the one google created ( the managed account with the briefcase thingy ).
I'd like to understand how can i recover it now? i do have some of the device details on enterprise.devices.get endpoint.
Any help would be much appreciated!
Rino.
3 Replies
- MoombasLevel 4.1: Jelly Bean2 months ago
I would never setup FRP especially not without providing allowed login google accounts to unlock the device again. But in general i abvoid this feature completely just because of the risk you encounter now (and which doesn't fit our use case tbh).
As you don't know the Google account used for this device (as it was a generic one) and you seem not to be able to enroll it to the (not finally existing?) EMM, you can only send it to repair with the invoice but with just a low chance they replace the board (and maybe need to pay for as it's self-inflicted) so you can reuse it afterwards again.
There's a small chance now you can scrap it instead.
Never play with things (especially risky security features) you don't understand completely.
- Emilie_BGoogle Community Manager2 months ago
Hi rinojames007 - sorry to hear about your issue.
We're a few days after you posted so, I wanted to check in and see if you had found a solution. Let us know :)
- Emilie_BGoogle Community Manager2 months ago
I thought I'd check with the team to see if we could advise you further.
They've asked if there is any way for you to disable FRP?
When FRP on a device is enabled with a managed Google Play account for which there is no password, it could lock out the FRP.
You can try "preserveFrp": True / False, and see if that removes you from the lock state
https://developers.google.com/android/management/reference/rest/v1/enterprises.policies#wipeaction
Could you give the above a go and let us know if that worked for you?
Related Content
- 12 months ago