Hi Everybody,
I need help regarding Bootloader Unlocking of Xiaomi Mi Max Prime(128gb).
I`ve all the prerequisits :
1. Unlocking Permission
2. ADB and Fastboot Drivers Installed
3. Mi Acoount activated
4. Usb Debuging, OEM Unlocking, Usb Debugging(security Settings) Options - ON.
5. Mi Cloud - Find Device - ON
6. Device Located (Both in Device and PC).
7. MiFlash Unlock Tool - Account verified for Permission.
But can`t Add Device and Account through Mi Unlock Status option in Device - It always shows "86012 with some chainis languages".
I`ve tried FlyVPN too to add the device and account, but can`t add.
It always shows "Couldn`t verify device - Current account is different form the account info on the device" - when I use any Old version of MiFlash Unlock Tools (i.e MiFlashUnlock_1.1.1111.1_en, MiFlashUnlock_1.1.0317.1_en etc).
And it always shows "Current account is not bound to this device"
In the "Settings -> Developer options -> Mi unlock status" binding account and equipment
" - when I use the latest version of MiFlash Unlock Tools (i.e miflash_unlock-en-2.2.406.5 ).
I really don`t understand, what I`m missing ?
It`s being 6 days I`ve got the permission, can`t even yet unlock the bootloader.
Would anyone help me to unlock the device?
Any suggesstions/advice will be highly appreciable.
I recently have the redmi note 8, I was able to send the confirmation message that comes out at the moment of turning on the phone, when going to the developer options and enabling the corresponding options, I get the message: it could not be added, error n ° 20033, I closed my account and put it back but the problem persists, I have not found information about this error on the internet, someone to help me how to overcome this error and to be able to unlock the bootloader
Engineering mode not work on oos12.. And diag port not opening. Anyone have solution plz tell me.
This way...
Secrecy unlock
WARNING - THIS (ORIGINAL) METHOD IS NOT WORKING WARNING - BE CAREFULL REGARDING (your) IMEI SHARING ! You need to enable Developer Options and USB Debugging in the Phone Download the Oppo_Free_Unlock_v1.0.zip Secrecy Auto Unlocker : Open the...
forum.xda-developers.com
AndroPlus said:
This way...
Secrecy unlock
WARNING - THIS (ORIGINAL) METHOD IS NOT WORKING WARNING - BE CAREFULL REGARDING (your) IMEI SHARING ! You need to enable Developer Options and USB Debugging in the Phone Download the Oppo_Free_Unlock_v1.0.zip Secrecy Auto Unlocker : Open the...
forum.xda-developers.com
Click to expand...
Click to collapse
but not repair imei anytool on andriod 12
How can i unable diag oneplus android 12
hesham hameed said:
How can i unable diag oneplus android 12
Click to expand...
Click to collapse
Adb uninstall
PROBLEM:Under certain scenarios, enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
If your phone is in this state, here's three possible fixes:
Spoiler: Possible Solution #1
POSSIBLE SOLUTION #1:
Thanks to Caligastia's post, here's another option to resolve.... (quoting from his post)[/B]
Just use the adb command...
Code:
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Spoiler: Possible Solution #2
POSSIBLE SOLUTION #2:
Revert to settings_system.xml.fallback file. Do not follow this guide UNLESS your phone is in this vibrate over and over / impossible to login state.
Note: This only works if you have USB debugging enabled on your computer with root enabled. This will not work if you haven't performed adb shell as root before ( com.android.shell ). Doesn't hurt to try!
Boot up phone to system/normal mode.
Type the following in command prompt:
Code:
adb shell
su
ls /data/system/users/0/settings_system.xml
If it says:
Code:
/data/system/users/0/settings_system.xml
Then this fix should work! Otherwise, this probably won't work.
Finally, type...
Code:
mv /data/system/users/0/settings_system.xml /data/system/users/0/settings_system.xml.old
cp /data/system/users/0/settings_system.xml.fallback /data/system/users/0/settings_system.xml
reboot
Your phone will reboot and the issue should be fixed!
By applying this method you may lose a few recently changed system settings, but nothing major.
Spoiler: Possible Solution #3
POSSIBLE SOLUTION #3:
Go to bootloader/fastboot mode on your phone.
Type
Code:
fastboot --set-active=a
fastboot reboot
if it doesn't boot right still, go back to bootloader/fastboot and type
Code:
fastboot --set-active=b
fastboot reboot
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
I'm referring to the setting called Quick Unlock.
Password and Security > Lock Screen Password.
But what this option do ? ( Quick unlock )
asheroto said:
PROBLEM:Enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
DO NOT ENABLE QUICK UNLOCK!
Click to expand...
Click to collapse
On my LE2123 OnePlus 9 Pro I do not face this issue with quick unlock. I made a test now once and no issue. Just FYI. I an not rooted.
K1nsey6 said:
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
Click to expand...
Click to collapse
This option appears if you select Alphanumeric password, using the regular keyboard instead of number pad. Quick unlock will unlock your phone immediately once you enter the password without having to press the enter key.
Interesting, I have the LE2125 with alphanumeric enabled.
I edited the original post to say "Under certain scenarios".
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
blxyy said:
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
Unfortunately you have to allow the host (your computer), but you can't do that unless you can tap on the popup.
Can you get in with TWRP or anything else? If so you could edit the file that way. Otherwise, try booting to the other slot.
How to check the current slot:
How to Check if You're on Partition Slot A or Slot B? - KrispiTech
Android phones can now have an A and a B partition system for the OS and we can use this fastboot command to check and see which slot is currently active.
krispitech.com
How to change the active slot:
adbcommand.com - adbcommand Resources and Information.
adbcommand.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, adbcommand.com has it all. We hope you find what you are searching for!
adbcommand.com
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
@bixyy
Just saw this, hope i'm not too late to help.
If adb shows "unauthorized" it just means that usb debugging permission was revoked between your phone and computer. here's what to do: (assuming you're on windows)
-Unplug your phone from pc. Disable Usb debugging and turn off "disable timeout"
-on your pc, go to C:/users/<username>/.android (it's a hidden folder) and delete adbkey.
-reboot both phone and pc to make sure it takes effect.
-plug your phone again, turn on usb debugging and you should get a new prompt to allow authorization.
adb devices should return your serial number now.
Added possible alternate solution
I ran into the same issue, OP was very helpful.
A bit more info here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Caligastia said:
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Thanks for that man! I updated the original post to include your solution and linked to your post for credits!
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
_147 said:
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
Click to expand...
Click to collapse
can you help me i cant seem to get adb to recognize my phone
Hi,
Is there any possible solution for us who don't have USB-Debugging enabled?
The goal is to not have to wipe the whole phone and loose all data.
Possible solution #1 fails: Wont work because USB debugging is disabled which prevents us from getting adb-shell and run the "
locksettings clear --old [PASSWORD]" command. When trying to figure out how to enable USB debugging from remote it seems to require some fastboot option which would wipe the phone.
Possible solution #2: Same - requires shell, and we cant enable usb debugging because of the bug
Possible solution #3: I can access fastboot but not run the specific commands:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
fastboot --set-active=a
Setting current slot to 'a'
FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Unlocking boot to install TWRP and enable debugging to use ADB shell would wipe the phone as I understand it.
Any suggestions please?
Is your phone locked when you're doing that?
asheroto said:
Is your phone locked when you're doing that?
Click to expand...
Click to collapse
Developer options enabled
OEM bootloader unlock enabled
USB debugging enabled
Default USB Configuration file transfer
Non-TMO variant = boot to bootloader, then fastboot OEM unlock...wipes device. No other way. Unlock bootloader will wipe device period.
Hello everyone.
I've been digging through forum to find a solution to my problem. I have forgotten lock screen pattern to Xiaomi 5A, I would keep on going and try to enter and remember which combination I used, but every attempt is followed by 4min lock up. I've stored there a password in a notepad which I must retrieve.
I have an access to MI account. USB debugging mode is off.
I've tried few things already.
Method 1#:
https://forum.xda-developers.com/t/...ing-android-password-pattern-face-pi.2620456/ - Doesn't work, as USB debugging mode is off.
To enable usb debugging I found one method. Using MI unlock software LINK to enable fast boot and then follow with the steps from above. However on MI UNLOCK I'm showing "After you unlock the device, it will become less secure. Your personal data may be leaked or lost.". Could any one confirm that this process won't wipe the data?
Method 2#:
Secret codes - none of them work.
*#*#6484#*#*
*#*#3646633#*#*
*#*#4636#*#*
Your help will be greatly appreciated and the right solution rewarded. Please let me know if you have any ideas how to access the phone.
Thanks!
unlock your device didnt erase your data
SzatanSzarlatan said:
Hello everyone.
I've been digging through forum to find a solution to my problem. I have forgotten lock screen pattern to Xiaomi 5A, I would keep on going and try to enter and remember which combination I used, but every attempt is followed by 4min lock up. I've stored there a password in a notepad which I must retrieve.
I have an access to MI account. USB debugging mode is off.
I've tried few things already.
Method 1#:
https://forum.xda-developers.com/t/...ing-android-password-pattern-face-pi.2620456/ - Doesn't work, as USB debugging mode is off.
To enable usb debugging I found one method. Using MI unlock software LINK to enable fast boot and then follow with the steps from above. However on MI UNLOCK I'm showing "After you unlock the device, it will become less secure. Your personal data may be leaked or lost.". Could any one confirm that this process won't wipe the data?
Method 2#:
Secret codes - none of them work.
*#*#6484#*#*
*#*#3646633#*#*
*#*#4636#*#*
Your help will be greatly appreciated and the right solution rewarded. Please let me know if you have any ideas how to access the phone.
Thanks!
Click to expand...
Click to collapse
Unlocking bootloader should erase your data