I have a Motorola Atrix MB860 that someone has attempted to unlock to many time and exceeded the unlock attempts. The phone is asking for the Motoblur email address and password. I spoke with the client and he has given me the swipe sequence but has no idea what the email address or password he used for setting up Motoblur. Does any one know how to reset the pass code attempts allowing the swipe sequence to be entered?
Thanks in advance.
This is the password reset page. Maybe your client can run through that and see what they can come up with.
I assume that you have no access to a commercial system (like Cellebrite etc.) that support the bypass lock for this device.
Since this seems to be an android phone
The current "State" of the lockscreen is often saved in sqlite database files on the device. You would need to edit these files to change the corresponding values.
But for that you need root access to the file system.
Though its a bit risky (depending on the phone) but one way could go like this - its just a generic description and may be different for some devices.
in case the phone is non-rooted and has deactivated USB-Debugging
- Flash an unlocked bootloader with root exploit to get access to the data partition.
- edit the specific files (for the lock-settings) on the device via adb (e.g. data/com.providers…./settings.db)
- This way you can either reset the "no more swipes allowed state" or completly remove the passcode.
This method does involve some deep research for your specific device. The XDA-Developers forum is of great help.
There are important things you need to make sure before you start
- Look up how to put your device in "Download Mode" and find the right Tool for flashing or use a SD-Card (Some use "update from SD" to unlock)
- Check if your phone does support flashing a new bootloader without wiping itself
- Check where your phone stores the lockscreen settings. There are different tables and fields for some phones.
- Check if your phone does allow editing these files. Some store backup files on encrypted partitions and restore the databases (or wipe) in case they detect a mismatch.
The best way, of course, would be to test it on an identical device first.
Hope that helps.