Hi All,
I recently received my new Mi Pad 5 (nabu) and I've had some experiance unlocking the bootloader on Miui devices before, however this one has me stumped. I have been through developer settings, OEM unlocking, adding Mi Account through the "Mi Unlock Status" menu, it adds the account, but when I try to unlock, it's still asking me to add my account in MIUI's settings > Developer options > Mi unlock status.
Is this a recent firmware update issue or am I missing something here?
* Rebooted and reset everything
* Redownloaded update and installed "download latest package" method
* Different PC and Cable and Port etc
* Open to recommendations
vannblackwings said:
Hi All,
I recently received my new Mi Pad 5 (nabu) and I've had some experiance unlocking the bootloader on Miui devices before, however this one has me stumped. I have been through developer settings, OEM unlocking, adding Mi Account through the "Mi Unlock Status" menu, it adds the account, but when I try to unlock, it's still asking me to add my account in MIUI's settings > Developer options > Mi unlock status.
Is this a recent firmware update issue or am I missing something here?
* Rebooted and reset everything
* Redownloaded update and installed "download latest package" method
* Different PC and Cable and Port etc
* Open to recommendations
Click to expand...
Click to collapse
Did you wait for one week after adding the account before trying to unlock?
I have not, from experiance there is usually a prompt that say's you need to wait x amount of hours etc. Does this not happen with the Mi Pad 5? All I receive is this -
View attachment 5850443
Just a heads up, I also went down the python route - https://github.com/Canny1913/miunlock
And got the "Device is not bound to Xiaomi account. Please add it in the developer settings and try again"
vannblackwings said:
I have not, from experiance there is usually a prompt that say's you need to wait x amount of hours etc. Does this not happen with the Mi Pad 5? All I receive is this -
View attachment 5850443
Just a heads up, I also went down the python route - https://github.com/Canny1913/miunlock
And got the "Device is not bound to Xiaomi account. Please add it in the developer settings and try again"
Click to expand...
Click to collapse
I'm sure I received the 'wait 1 week ' message. I initially had problems binding the account from the UK, had to use a VPN while connected set to the US - could maybe try that
Choochter said:
I'm sure I received the 'wait 1 week ' message. I initially had problems binding the account from the UK, had to use a VPN while connected set to the US - could maybe try that
Click to expand...
Click to collapse
Just run through the same process connected to the VPN "US", but still no cigar. I also have been testing this out with multiple versions of the Mi Unlock app just to see if that was the issue.
Tried again tonight, using my partners mi account this time. Using the VPN, with or without, still getting the same error message. Tried using my desktop, laptop, work computer. I've factory reset this thing a couple of times now, toggled the OEM unlock switch, rebooted etc, still no dice.
However, I tried unlocking the bootloader with my old Redmi Note 8 Pro (I have a newer unlocked 10 pro), and guess what, the same issue! It give's me the "please add your account...." error the same as the Mi Pad even though it's added.
So whatever this is, maybe it's the account/s, PC's or hell for all I know maybe I've just caught the damn bootloader curse that seems to make it's way around. If anyone can enlighten me to the root cause, I'd love to know. I'd hate having to wait, only just to find out there was no point because it didn't work, patience is a virtue I guess lol
Edit - Forgot to mention my old phone is on Global FW 12.5.7
I have now tried the following
Steps taken
Different cables
Different ports
Different accounts (before and after the week timer)
Different login methods, ie - password, QR code etc
VPN used incase it was something regional (based in UK)
Updated firmware (currently on MIUI Global 12.5.8)
Turning find my phone on and off etc
Reset device
Tried using my desktop, laptop and work machine (same result)
Waited 7 days
Tried both the Mi Pad 5 and a Redmi Note 8 Pro (issue is persistent on both)
Ok, I just went and installed windows 10 instead of using 11, Issue persists.
Okay I went ahead and used a 3rd party tool, this is the error I get here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEBUG <12:10:42.666,T:24320> : getvar tokenversion -s 499cc3ff
DEBUG <12:10:42.710,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:10:42.710,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:10:42.710,T:24320> : tokenversion=0
DEBUG <12:10:42.712,T:24320> : oem get_token -s 499cc3ff
DEBUG <12:10:42.754,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.003s
INFO <12:10:42.754,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.003s
DEBUG <12:10:42.754,T:24320> : getvar token -s 499cc3ff
DEBUG <12:10:42.802,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.006s
INFO <12:10:42.802,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.006s
DEBUG <12:10:42.802,T:24320> : to check erase feature for 499cc3ff
DEBUG <12:10:43.831,T:24320> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG <12:10:44.658,T:23820> : User click unlock button!
DEBUG <12:10:55.740,T:24320> : -s 499cc3ff oem device-info
DEBUG <12:10:55.789,T:24320> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
finished. total time: 0.006s
DEBUG <12:11:00.745,T:24320> : VerifyDeviceInfo
INFO <12:11:00.745,T:24320> : product:nabu
DEBUG <12:11:00.745,T:24320> : getvar tokenversion -s 499cc3ff
DEBUG <12:11:00.789,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:11:00.789,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:11:00.789,T:24320> : tokenversion=0
DEBUG <12:11:00.789,T:24320> : oem get_token -s 499cc3ff
DEBUG <12:11:00.832,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.002s
INFO <12:11:00.832,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.002s
DEBUG <12:11:00.832,T:24320> : getvar token -s 499cc3ff
DEBUG <12:11:00.874,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.003s
INFO <12:11:00.874,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.003s
DEBUG <12:11:00.874,T:24320> : to sign token with key for device:nabu
DEBUG <12:11:02.465,T:24320> : sign result:{
"code" : 20031,
"descCN" : "请在MIUI上绑定账号后解锁：开发者模式下打开设置，搜索设备解锁状态，然后进行绑定",
"descEN" : "Please add your account in MIUI's Settings > Developer options > Mi Unlock status.",
"description" : "请在MIUI上绑定账号后解锁：开发者模式下打开设置，搜索设备解锁状态，然后进行绑定",
"uid" : "6351847669"
}
DEBUG <12:11:02.465,T:24320> : unlock return:11111 msglease add your account in MIUI's Settings > Developer options > Mi Unlock status.
Just in case anyone else follows this thread....
I had a similar experience when I used Miflash and didn't realise the default setting was to lock the tablet...
I used the official unlock tool (the unofficial tool doesn't work anymore) and waited patiently for the sms that never came.
Then prompted by a comment on another thread, I realised that there is an extra step and we are meant to enter the barely legible code/image on the unlock tool. Once that code is entered then the process proceeds and the sms is sent...
This step was not immediately obvious to me!
mikefnz said:
Just in case anyone else follows this thread....
I had a similar experience when I used Miflash and didn't realise the default setting was to lock the tablet...
I used the official unlock tool (the unofficial tool doesn't work anymore) and waited patiently for the sms that never came.
Then prompted by a comment on another thread, I realised that there is an extra step and we are meant to enter the barely legible code/image on the unlock tool. Once that code is entered then the process proceeds and the sms is sent...
This step was not immediately obvious to me!
Click to expand...
Click to collapse
Are you talking about the captcha? This post seems incrediably off topic for the type of issue I've outlined above.
Ok, so I just got back my Redmi Note 10 Pro from repair and I was able to unlock fine (had already been unlocked previously but relocked it when sending off). When I then went to unlock my Mi Pad with the same account, I got the "Can only unlock 1 device per month" message and was told to wait. So I thought sure, I'll switch over to the other mi account I have, nope back to the "Please add miui account in settings..." yada etc.
Something is definately funky here.
I have an update folks, and a good one.
So all this time I've been trying to unlock with a UK/GB account, created several. When creating a US account however, I FINALLY get the timer telling me to wait to unlock.
What a relief, thanks to those who commented and I hope it also helps any lurkers out there who are also experiancing the same issue. Make a new account with a different region (US) and you should get your wait timer, I also did this whilst connected to the US over VPN (tried before and didn't have any luck), just incase but the account region seemed to do the trick.
Xiaomi - sort it out please!
Related
So I have been trying to unlock my bootloader for four months, and have failed literally every time at the same step.
The step being, fastboot oem get_identifier_token
Waiting for device
Unknown command
Time taken 0.003 seconds.
If anyone can help me unlock my bootloader, that would be great.
Also, I am unable to enter into 'hboot', it directly goes to recovery mode. (volume down + home button). All my device drivers are installed (HTC sync manager recognised my phone once, but after it recognised all the music, it immediately showed no device found).
This is my current situation, please help me out here!
xxxCrimeDogxxx said:
So I have been trying to unlock my bootloader for four months, and have failed literally every time at the same step.
The step being, fastboot oem get_identifier_token
Waiting for device
Unknown command
Time taken 0.003 seconds.
If anyone can help me unlock my bootloader, that would be great.
Also, I am unable to enter into 'hboot', it directly goes to recovery mode. (volume down + home button). I am rooted right now, so I am able to enter into fastboot directly. All my device drivers are installed (HTC sync manager recognised my phone once, but after it recognised all the music, it immediately showed no device found).
This is my current situation, please help me out here!
Click to expand...
Click to collapse
1. Which page your device is in when you issue the command "fastboot oem get_identifier_token"? Are you in FASTBOOT USB?
2. Are you using HTCDev.com to unlock your bootloader?
3. Upload a picture of the display of your device; and a picture of cmd page.
Dr.Ghobar said:
1. Which page your device is in when you issue the command "fastboot oem get_identifier_token"? Are you in FASTBOOT USB?
2. Are you using HTCDev.com to unlock your bootloader?
3. Upload a picture of the display of your device; and a picture of cmd page.
Click to expand...
Click to collapse
1) Yes, I am in the fastboot page..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Yes, the HTCdev website..just past the step where they tell you to download the fastboot binaries and execute them..
3)
This <----
My phone is unrooted, obviously not bootlocker, flashed with stock firmware. I am also unable to enter into the hboot page. I never could do that, I tried it two months into buying the phone, yet I never could enter the hboot. Does HTC Desire 816G Dual Sim (d816h) even have a hboot page? All HTC phones have a hboot page right?
These are all my phone features - https://androiddevice.info/submission/21306/show (Have a look if necessary)
Thanks!!
xxxCrimeDogxxx said:
1) Yes, I am in the fastboot page..
2) Yes, the HTCdev website..just past the step where they tell you to download the fastboot binaries and execute them..
3)
This <----
My phone is unrooted, obviously not bootlocker, flashed with stock firmware. I am also unable to enter into the hboot page. I never could do that, I tried it two months into buying the phone, yet I never could enter the hboot. Does HTC Desire 816G Dual Sim (d816h) even have a hboot page? All HTC phones have a hboot page right?
These are all my phone features - https://androiddevice.info/submission/21306/show (Have a look if necessary)
Thanks!!
Click to expand...
Click to collapse
1. My FASTBOOT USB page looks like the picture I attach for you.
2. If you cannot get the Identifier Token of your device, as you said, you cannot proceed to Step 7 and submit the Identifier Token to htcdev. And so they cannot email you the "Unlock_code.bin" file.
3. Can you upload a clear picture of the page you enter by pressing vol down+power?
4. Are you sure your device is supported by htcdev? (your exact model is not listed on their to be selected. Ask htc.com via online chat whether your device is supported or not.)
Unlock Bootloader HTC Desire 816G Dual Sim Tutorial
xxxCrimeDogxxx said:
1) Yes, I am in the fastboot page..
2) Yes, the HTCdev website..just past the step where they tell you to download the fastboot binaries and execute them..
3) This <----
My phone is unrooted, obviously not bootlocker, flashed with stock firmware. I am also unable to enter into the hboot page. I never could do that, I tried it two months into buying the phone, yet I never could enter the hboot. Does HTC Desire 816G Dual Sim (d816h) even have a hboot page? All HTC phones have a hboot page right?
These are all my phone features - https://androiddevice.info/submission/21306/show (Have a look if necessary)
Thanks!!
Click to expand...
Click to collapse
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
I will try that now and post the results.
Thanks and regards
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
so im apparently unable to retrieve the modaco superboot file. stupid surveys. though there are many other superboots out there. is each superboot different for each phone?
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
okay so now, ive almost got it...i have a screen where my phone says, press volume up to unlock bootloader and press volume down to NOT unlock bootloader...im stuck at the screen where it gives this option, ive already pressed volume up and nothing's happened..ill still be waiting..
BUT A HUGE DARN THANKS TO YOU FOR MAKING ME REACH THIS STEP
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
okay, so it seems ive 'waited too long' according to my phone ...
this is what happened after my phone said that while in fastboot mode
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
so now ive figured out that my volume down button works pretty well (since it stops unlocking and goes back to another screen), but when i press volume up, nothing happens.. there is the " ... " on my cmd which waits indefinitely, but when i press volume down, the screen says unlock failed, and goes back to another screen which is supposed to let me choose whether to reboot, reboott bootloader or anyything, again there i cant use my col up button.... im pretty sure it isnt broken
xxxCrimeDogxxx said:
so now ive figured out that my volume down button works pretty well (since it stops unlocking and goes back to another screen), but when i press volume up, nothing happens.. there is the " ... " on my cmd which waits indefinitely, but when i press volume down, the screen says unlock failed, and goes back to another screen which is supposed to let me choose whether to reboot, reboott bootloader or anyything, again there i cant use my col up button.... im pretty sure it isnt broken
Click to expand...
Click to collapse
Look at this too:
How To unlock htc bootloader using one click method (all HTC devices)
http://www.bestandroidrootedapps.com/how-to-unlock-htc-bootloader/
Dr.Ghobar said:
Look at this too:
How To unlock htc bootloader using one click method (all HTC devices)
http://www.bestandroidrootedapps.com/how-to-unlock-htc-bootloader/
Click to expand...
Click to collapse
Tried this long back, got the same result...
Log below....Thanks!
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out:
fastboot: devices
fastboot out:
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno:
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: LCSH92_CWET_KK
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.002s
get_device_info_failed
xxxCrimeDogxxx said:
Tried this long back, got the same result...
Log below....Thanks!
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out:
fastboot: devices
fastboot out:
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno:
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: LCSH92_CWET_KK
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.002s
get_device_info_failed
Click to expand...
Click to collapse
I guess that the problem is the mode where the device is in.
1. In your device's "Developers options" is there two following options?
USB Debugging
OEM Unlocking
2. If yes, are both enabled?
Dr.Ghobar said:
I guess that the problem is the mode where the device is in.
1. In your device's "Developers options" is there two following options?
USB Debugging
OEM Unlocking
2. If yes, are both enabled?
Click to expand...
Click to collapse
I've gone through this before, I have only USB Debugging, and yes, that is always enabled for me.
Dr.Ghobar said:
I guess that the problem is the mode where the device is in.
1. In your device's "Developers options" is there two following options?
USB Debugging
OEM Unlocking
2. If yes, are both enabled?
Click to expand...
Click to collapse
His device is the Indian dual sim version (HTC Desire 816G / MT6592). The only way to flash any os on this device is using flashtool and this rom.
nukaru said:
His device is the Indian dual sim version (HTC Desire 816G / MT6592). The only way to flash any os on this device is using flashtool and this rom.
Click to expand...
Click to collapse
What about unlocking his device's bootloader?
nukaru said:
His device is the Indian dual sim version (HTC Desire 816G / MT6592). The only way to flash any os on this device is using flashtool and this rom.
Click to expand...
Click to collapse
Really? But why? And btw I have a d816h, not a d816g, as stated in the ROM you linked me to. I flashed this rom: http://www.needrom.com/download/htc-d816h/
Dr.Ghobar said:
What about unlocking his device's bootloader?
Click to expand...
Click to collapse
Precisely my question. Why am I unable to unlock my bootloader?
xxxCrimeDogxxx said:
Really? But why? And btw I have a d816h, not a d816g, as stated in the ROM you linked me to. I flashed this rom: http://www.needrom.com/download/htc-d816h/
Click to expand...
Click to collapse
What is the relation between these two specifications of your device: 816g and D816h?
(What is your getvar all information?)
Dr.Ghobar said:
What is the relation between these two specifications of your device: 816g and D816h?
(What is your getvar all information?)
Click to expand...
Click to collapse
my getvar all never seems to work like the others...it just shows partitions/permissions or some other word..
yes there is a difference i cant ye seem to find, but i know mine is a d816h because of the box which i received my phone in
Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)".
Is there a workaround for this?
Thanks for your help!
I also have this issue.
Same thing here. I loaded LineageOS and have decided to go back to factory. I can't figure it out either. Here are my results.
fastboot flashing lock
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.022s
fastboot flashing unlock
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
fastboot flashing get_unlock_ability
(bootloader) 0
OKAY [ 0.020s]
finished. total time: 0.020s
Ok all, I finally figured it out.
I had to download factory image 6.0.1 (MXB48J) go thru the instructions to flash this image.
Started up in android went thru the min setup to get into Settings and Developer Options. Turn on USB debugging and the OEM Unocking.
adb reboot bootloader
flashboot flashing lock
Prompted me about wiping the device.
Everything is good.
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
0sm1um said:
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
Click to expand...
Click to collapse
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
demonntlxda said:
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
Click to expand...
Click to collapse
Well sadly Xiaomi locked down EDL mode and that needs people working for Xiaomi to fix it.
Sadly a service center will not fix it because they will convince you to dump your phone in a rubbish bin and buy a new mi 11 because Xiaomi could earn more.
So that is a bummer but your phone needs a new motherboard.
Hi everyone i got a problem
I erased all data before unlocking my phone
now if i want install twrp i got this
Code:
C:\Windows\System32>fastboot boot "E:\Downloads\twrp-3.7.0_11-0-hanoip.img"
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.827s
when trying to unlock
Code:
C:\Windows\System32>fastboot oem unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.076s
but i cant get into android settings, what can i do??
ok, i used rescue and smart asistant and got my phone back
but now i cant switch oeum unlock in developer options, its saying i need to got internet access (got it by wifi)
any thoughts?
swatikingg said:
ok, i used rescue and smart asistant and got my phone back
but now i cant switch oeum unlock in developer options, its saying i need to got internet access (got it by wifi)
any thoughts?
Click to expand...
Click to collapse
It means your phone is not unlocked
yea i know that, but i cant unlock untill i change that in developer options
swatikingg said:
yea i know that, but i cant unlock untill i change that in developer options
Click to expand...
Click to collapse
It can take 3-14 days after connecting to internet, for allow unlocking to be available
thanks
u can close topic
You can also try switching to Mobile Data, and typing this in your dialer:
*#*#2432546#*#* (*#*#CHECKIN#*#*).
This will ping google and potentially help to activate the option.
Hi Folks,
I'm having issues where the linked account in Miui wont be detected when using the Mi Unlock Tool. The error I am getting is "Please add your Miui Account in Settings etc" however this is already done and is 100% the same account (I've checked more times than I can count). Just so you know, I have also enabled developer settings and debugging (works fine with ADB commands), I have also enabled OEM Unlocking in the developer menu.
At no point do I get a message telling me to wait 168 hours etc, I did wait a week just in case, no dice. All I get is the "please add your account etc" which is already done!
Steps taken
Different cables
Different ports
Different accounts (before and after the week timer)
Different login methods, ie - password, QR code etc
VPN used incase it was something regional (based in UK)
Updated firmware (currently on MIUI Global 12.5.8)
Turning find my phone on and off etc
Reset device
Tried using my desktop, laptop and work machine (same result)
Information
The only other thing I can tell you is that I am having the exact same issue on my Mi Pad 5. I figured this would mean it's something account based, but no, still no dice. I have tried 4 different accounts now and none of them work, they all give me the "Please add you miui account in settings etc" when trying to unlock.
The crazy thing is, I have a Redmi Note 10 Pro which I have unlocked fine no issues (last year). The last thing I want to do however is relock the bootloader and try unlocking it again.
Any ideas here would be much appreciated!
I've just tried using windows 10 instead of 11 and the issue persists.
Okay I went ahead and tried using a 3rd party tool, this is the error I get now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEBUG <12:10:42.666,T:24320> : getvar tokenversion -s 499cc3ff
DEBUG <12:10:42.710,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:10:42.710,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:10:42.710,T:24320> : tokenversion=0
DEBUG <12:10:42.712,T:24320> : oem get_token -s 499cc3ff
DEBUG <12:10:42.754,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.003s
INFO <12:10:42.754,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.003s
DEBUG <12:10:42.754,T:24320> : getvar token -s 499cc3ff
DEBUG <12:10:42.802,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.006s
INFO <12:10:42.802,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.006s
DEBUG <12:10:42.802,T:24320> : to check erase feature for 499cc3ff
DEBUG <12:10:43.831,T:24320> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG <12:10:44.658,T:23820> : User click unlock button!
DEBUG <12:10:55.740,T:24320> : -s 499cc3ff oem device-info
DEBUG <12:10:55.789,T:24320> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
finished. total time: 0.006s
DEBUG <12:11:00.745,T:24320> : VerifyDeviceInfo
INFO <12:11:00.745,T:24320> : product:nabu
DEBUG <12:11:00.745,T:24320> : getvar tokenversion -s 499cc3ff
DEBUG <12:11:00.789,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:11:00.789,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:11:00.789,T:24320> : tokenversion=0
DEBUG <12:11:00.789,T:24320> : oem get_token -s 499cc3ff
DEBUG <12:11:00.832,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.002s
INFO <12:11:00.832,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.002s
DEBUG <12:11:00.832,T:24320> : getvar token -s 499cc3ff
DEBUG <12:11:00.874,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.003s
INFO <12:11:00.874,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.003s
DEBUG <12:11:00.874,T:24320> : to sign token with key for device:nabu
DEBUG <12:11:02.465,T:24320> : sign result:{
"code" : 20031,
"descCN" : "请在MIUI上绑定账号后解锁：开发者模式下打开设置，搜索设备解锁状态，然后进行绑定",
"descEN" : "Please add your account in MIUI's Settings > Developer options > Mi Unlock status.",
"description" : "请在MIUI上绑定账号后解锁：开发者模式下打开设置，搜索设备解锁状态，然后进行绑定",
"uid" : "6351847669"
}
DEBUG <12:11:02.465,T:24320> : unlock return:11111 msglease add your account in MIUI's Settings > Developer options > Mi Unlock status.
Download official Mi Flash Tool and Mi Unlock Tool.
Open Mi Flash Tool and install drivers (For Android bootloader interface).
Download and install mtk drivers.
Turn off Wifi and turn on 3g/4g.
Add account in Developer settings.
Boot in Fastboot and check by Mi Unlock Tool (check if it show 168h or not).
If it shows 168h, DON'T EVER touch Developer option, don't add or remove account, don't update or format rom.
Just wait & countdown by boot in Fastboot and use Mi Unlock Tool.
Or else just unlock instantly by unofficial tool without data lost
None of this worked, I am on 12.5.8.0 RGGMIXM.
It DOES NOT show any sort of timer let alone the 168h countdown.
vannblackwings said:
None of this worked, I am on 12.5.8.0 RGGMIXM.
It DOES NOT show any sort of timer let alone the 168h countdown.
Click to expand...
Click to collapse
Kirasu2080 said:
Click to expand...
Click to collapse
Thanks, this worked, however I am still having issues making it so the "official" method works. If you check my other thread my Mi Pad 5 is still locked.
vannblackwings said:
Thanks, this worked, however I am still having issues making it so the "official" method works. If you check my other thread my Mi Pad 5 is still locked.
Click to expand...
Click to collapse
Check if your PC/Laptop is AMD or Intel. Some AMD got compatible issues with these kind of driver. You should Install new Window or Dual boot a new one or borrow another PC/Laptop.
Kirasu2080 said:
Check if your PC/Laptop is AMD or Intel. Some AMD got compatible issues with these kind of driver. You should Install new Window or Dual boot a new one or borrow another PC/Laptop.
Click to expand...
Click to collapse
I've got both, Laptop is intel, desktop is AMD. I previously unlocked a Redmi Note 10 Pro using the desktop no issues whatsoever. I even went as far as dual booting into windows 7 and 10 just to check.
vannblackwings said:
I've got both, Laptop is intel, desktop is AMD. I previously unlocked a Redmi Note 10 Pro using the desktop no issues whatsoever. I even went as far as dual booting into windows 7 and 10 just to check.
Click to expand...
Click to collapse
Did you add this?
Kirasu2080 said:
Did you add this?
Click to expand...
Click to collapse
Yeah, I am even using a fresh account and phone number. No timer no dice.
vannblackwings said:
Yeah, I am even using a fresh account and phone number. No timer no dice.
Click to expand...
Click to collapse
Maybe try watch a YouTube video and do step by step. I have both rmn8p and mi pad 5. All worked fine.
Kirasu2080 said:
Maybe try watch a YouTube video and do step by step. I have both rmn8p and mi pad 5. All worked fine.
Click to expand...
Click to collapse
Watched more YouTube video and step by steps than I care to remember, however the issue was resolved with the account region. Once I switched from a UK/GB account to a US one I now get a timer. Looks like something's borked because of that specifically, even when the firmware is EEA.
I'm getting this problem too - which account did you change to US and where is that setting?
Go to the mi account website, create a new account but make sure you select US as the region when you do.
smithbill said:
I'm getting this problem too - which account did you change to US and where is that setting?
Click to expand...
Click to collapse
Option is at the top once you click create account, then select the drop down etc
What a ridiculous almost circuitous process you have to go through to get this to work!
After reading your initial reply, i thought I could just log into my Mi account in a browser and change my region to US. But no, you cant change your region, so I had to create a new account using a browser and set the region to US, but then the Unlock Tool wouldn't let me set the International Dial Code to anything except +1 which i'm assuming would mean SMS verification codes wouldn't be received. I think I ended up using a Browser again to login to my new Mi account and then enter & verify my recovery phone number with +44 code.
In the end I think I had created three separate Mi accounts, each associating my phone number to different emails and Mi ID's etc and then requiring verification emails & codes sent to my phone number.
Eventually I got the 168 hour confirmation.
A completely ludicrous process - Xiaomi: if your listening - GET THIS FIXED!!!
(thank you @vannblackwings without who's help I would've struggled with this!)
Kirasu2080 said:
Click to expand...
Click to collapse
help me please!!! after unlocking the bootloader, I can not install twrp via fastboot! HELP ME PLEASE!!