Pixel 5 mdm lock

[Absolutely nothing]

Hi, my friends pixel 5 is MDM locked and automatically resets every 2 hours. I already have unlocked bootloader and I'm trying to flash official factory image
( developers.google.com/android/images ) but fail (i have latest version of platform tools installed).
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
I'll attach image of that.
Tried flashing manually .\flash-all an using .bat file. Have done tons of research today but nothing.
Any ideas what can i do?

 

[Absolutely nothing]

update
I flashed factory image successfully but it didn't help with mdm.

 

[swangjang]

Is this a second hand phone or a company issued phone?
If it's second hand, probably best to ask the seller for refund or replacement.
If it's a company issued phone, may have to take it back to the company to unlock it.
I haven't dealt with MDM before so I'm not entirely sure. There may be tools to force disable MDM but not sure.

 

[HT123]

First, it sounds like you have a stolen phone.

You managed to flash without errors?

The phone is registered at the mdm server and the 2 hours is how long it is taking to reregister the device and then wipe it because it was flagged.

I am not sure how it was registered at the server. You could try installing lineage and see if still resets after a couple hours.

If so, since you have root. That means you have two hours after a reflash to find the mdm process and disable it.

Good luck, let us know if you find it.

*also found this to try after you reflash.
Go to Settings > Security > Device Admin Apps, and disable whatever is in there. I would do this after a clean flash, without enabling any sort of data connection.

You can also try to freeze or remove com.google.android.apps.work.oobconfig

 

[Absolutely nothing]

First, it sounds like you have a stolen phone.

You managed to flash without errors?

The phone is registered at the mdm server and the 2 hours is how long it is taking to reregister the device and then wipe it because it was flagged.

I am not sure how it was registered at the server. You could try installing lineage and see if still resets after a couple hours.

If so, since you have root. That means you have two hours after a reflash to find the mdm process and disable it.

Good luck, let us know if you find it.

*also found this to try after you reflash.
Go to Settings > Security > Device Admin Apps, and disable whatever is in there. I would do this after a clean flash, without enabling any sort of data connection.

You can also try to freeze or remove com.google.android.apps.work.oobconfig

It's second hand device which previously was purchased from eBay.

What i did is, i flashed android 11 and after activating without internet rebooted into bootloader & used this adb commands: adb shell; pm uninstall -k --user 0 com.google.android.apps.work.oobconfig .
It temporarily removes mdm, after reseting device problem still persists, but otherwise all good. Haven't tried rooting it and searching for mdm.

 

[Absolutely nothing]

P.S.
11 seems like only android version on which it works

 

[V0latyle]

Normally, a MDM locked device is not bootloader unlockable; if the bootloader is indeed unlocked, performing a clean flash of Android with a full wipe should eliminate MDM entirely.

Just to be sure, boot into bootloader mode and post the output of fastboot flashing get_unlock_ability

Try using the Android Flash Tool. Make sure you check the Wipe device and Force flash all partitions boxes.

 

[Absolutely nothing]

Normally, a MDM locked device is not bootloader unlockable; if the bootloader is indeed unlocked, performing a clean flash of Android with a full wipe should eliminate MDM entirely.

Just to be sure, boot into bootloader mode and post the output of fastboot flashing get_unlock_ability

Try using the Android Flash Tool. Make sure you check the Wipe device and Force flash all partitions boxes.

I've unlocked bootloader and flashed official factory image from there. I couldn't make Android flash tool work though, it begins downloading and at certain point stops it & starts again.

 

[V0latyle]

I've unlocked bootloader and flashed official factory image from there. I couldn't make Android flash tool work though, it begins downloading and at certain point stops it & starts again.

USB debugging has to be enabled, and you have to have the ADB driver installed on your computer.

 

[Absolutely nothing]

USB debugging has to be enabled, and you have to have the ADB driver installed on your computer.

Of course I had them, otherwise how could i unlocked bootloader and completely rewrite factory image. Haven't tried installing custom ROMs, my friend prefered not to play with it too much and just stick with android 11 solution.

 

[V0latyle]

Of course I had them, otherwise how could i unlocked bootloader and completely rewrite factory image. Haven't tried installing custom ROMs, my friend prefered not to play with it too much and just stick with android 11 solution.

OEM Unlocking and USB debugging are separate. Both are enabled through Developer Options. USB Debugging is disabled after a data wipe.

If you're able to flash the factory image via ADB, try wiping both /system and /data using fastboot erase system (replace system with data for the data partition)

Using the Android Flash Tool is the most ideal option. I'm not sure where a MDM app/lock is installed on the device but I would think that completely reformatting it would be sufficient.

Does the MDM lock appear even if the device isn't connected to the Internet?

 

[HT123]

>Using the Android Flash Tool is the most ideal option.

What does the flash tool do that you can’t do from the command line?

 

[V0latyle]

>Using the Android Flash Tool is the most ideal option.

What does the flash tool do that you can’t do from the command line?

As far as I know, nothing. The trick is knowing which commands, so if you have some way to look at the commands coming from the WebADB interface, that would help. I know some of the commands, but I don't know what is used for "force flash all partitions"

Edit: I missed a rather critical detail:

I forgot that only one process can use ADB at a time, so if you've used ADB from command line, you have to use adb kill-server for the Flash Tool to work.

 

[HT123]

>As far as I know, nothing. The trick is knowing which commands,

the commands for installing a stock image are in the extracted ROM zip in my experience. Usually in the flashfile.xml