After having problems restoring my Lineage OS (TWRP Restore), I found a guide that recommended to do a "fastboot flashing lock" and "fastboot flashing unlock" to delete the data partition. In a fit of mental derangement I did exactly did that. Well, at least the the first part. Stupid move - really. Now I'm stuck with a locked bootloader. I can't unlock it via fastboot commands:
c:\fastboot flashing unlock
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Same results for "fastboot oem unlock".
Fyi:
c:\fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
The Mi Unlock tool gives me a charming "Please add your account in MIUI's Settings > Developer options > Mi Unlock status." Which isn't possible because I had Lineage OS running and I can only get into Fastboot now. If I try to boot regularly the phone says "The system has been destroyed".
Well, I almost accepted that I have to dismantle the phone to get into EDL mode, but then I discovered hints that I might need some kind of authorization to update the phone via EDL mode. And a lot of shady offers to do exactly that ...
Did I brick my phone for good, or is there any hope to fix it?
Thanks a lot!
Hi, did you solved it?
If not, try to ut the phone in fastboot mode, then download exactly stock firmware (global, india, china,...etc) version for this phone, then flash it via Miflash.
Related
For all who are waiting for unlocking permission, you don't need to - if you'd like to root and install twrp.
Warning do not flash xiaomi.eu global or any other unofficial rom this way !
Good news - there is now patched aboot with installation instructions
I bought my redmi 4 pro from geekbuying and it came with preinstalled google play and semi mutlilingual (fake) Miui global 8.0.5.0.0(MBECNDG)
It seems geekbuying has installed a modifyed aboot (android bootloader), if you overflash it with xiaomi stock your device will check the rom for valid signing.
So you probably could flash unofficial rom if you don't flash aboot, but I can't test it anymore :/
btw I did this using linux and I used adb from Flashtool
As I still needed root so I tryed to unlock using fastboot :
First enable developer options by clicking on miui version in about phone menu
Go to Systems & Device > Additional Settings > Developers options
allow oem unlock and usb debugging
connect to the computer and allow access
turn off device
hold vol down and power - device reboots to fastboot
fastboot oem device-info
fastboot oem unlock-go
fastboot oem device-info < again, to check if its unlocked
restart device
Redo the setup and use browser to download supersu
get Recovery Flashable.zip
now download twrp to the computer
and follow the instructions how to install twrp.
Twrp started in chinese use, settings menu is second up from the right and last tab is language.
Flash supersu
I'll try this when I receive my Redmi 4.
Thanks for sharing!
It's that simple ?
I remember that my Redmi Note 3 Pro made some trouble with "unofficial" unlocking, when it comes to different ROMs...
Thanks anyway!
who checked this method?
Not working
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.016s
Click to expand...
Click to collapse
Hi just to say this worked fine for me. Had a new Redmi 4 Prime bought from Gearbest. Fake global rom version exactly same as mentioned above. I used vanilla Minimal ADB and Fastboot.
NB when device arrived no setup ie fake ROM had already been installed and configed (presumably to install play store).
Went straight in and tried the instructions above. Worked fine. Fastbook unlock then TWRP then supersu. Dumped Chinese CM13 ROM on and we're all good.
Not sure why works for some and why doesn't. Perhaps the exact version of the global rom? Perhaps the fact hadn't done anything with ROM and dived straight in with the unlock?
Tx for kentaurest for the tip!
J
Did you check if bootloader was locked before? Maybe it was unlocked by Gearbest when flashing ROM?
PS. I'm waiting for delivery and I will check your method
mulat666 said:
Did you check if bootloader was locked before? Maybe it was unlocked by Gearbest when flashing ROM?
PS. I'm waiting for delivery and I will check your method
Click to expand...
Click to collapse
Yeah so device-info before unlock was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Afterwards it was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Screenshot here: https://photos.google.com/share/AF1QipMnl4IHWqsJ60emRL-bLFsPdzSRN3EQ-LO9aBR3KgdtH8OVBplWE_AKXuQva_05CA?key=T2dOREx6N2w0SE10SmV6NEJuWHlSWEVJaXUwNU1B
J
Tried with my Redmi 4 Pro who came straight stock from china. It worked. Be sure to install good adb and fastboot drivers and be sure to check the correct developers options.
jontseng said:
Yeah so device-info before unlock was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Afterwards it was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Screenshot here: https://photos.google.com/share/AF1QipMnl4IHWqsJ60emRL-bLFsPdzSRN3EQ-LO9aBR3KgdtH8OVBplWE_AKXuQva_05CA?key=T2dOREx6N2w0SE10SmV6NEJuWHlSWEVJaXUwNU1B
J
Click to expand...
Click to collapse
One interesting thing is mine device which is unlocked with miflash shows the second line like this
(bootloader) Device critical unlocked: true.
I've just received phone with the same ROM as in first post. Could you please share ADB drivers? With universal I had:
Code:
fastboot.exe oem unlock-go
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.030s
The same issue on Ubuntu 16.04
Yeah mine is still "device critical unlocked: false" even after flashing other ROMS and mucking around.
Not quite sure what the issue is - did some quick google as maybe its some key system stuff still locked or because I didn't officially flash thru edl mode or something?
Not going to worry about it too much as I seem to be able to flash ROMs and stuff just fine (just flashed XPosed framework as well, FYI). Don't plan to go back to MIUI at any point anyhow - not really my cup of tea.
Would be interested if someone can explain more about this though. What am I missing out on?
PS Just for fun I ran the same fastboot device-info on my old redmi 3 (unlocked the official way) and it didn't have the "device critical unlocked" line at all (true or false..)
It is dangerous, you can install supersu and twrp this way, but don't flash non official roms.
Xiaomi roms should relock the bootloader.
Also don't try to install xposed, it didn't work for me.
After xposed made my phone bootloop I installed unofficial global and ended up with "bricked phone" left only with fastboot or black screen (qualcomm diagnostics interface 9000E) and couldn't turn off the phone.
I made deep flashing cable - usb cable where you can short GND and D+
http://xiaomitips.com/media/2016/08/Deep-FLash-Cable-Architecture-680x318.jpg
Connected phone to the computer (don't short the cables yet), used "fastboot reboot" to restart phone.
Quickly shorted GND and D+ for a few seconds, then windows installed HS-USB QDloader 9008 driver
and I could use Mi Flash to restore the phone, this time to the china developer rom
(fastboot version ends with .tgz) with clean all and locked options.
I was quite happy with fake global, twrp and supersu, pity xposed ruined it.
mulat666 said:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.030s[/CODE]
Click to expand...
Click to collapse
Use deep flashing usb cable to get to EDL (downloader) mode.
@kentaurest I have a cable, would it work with the same fastboot commands?
mulat666 said:
@kentaurest I have a cable, would it work with the same fastboot commands?
Click to expand...
Click to collapse
Use windows and Mi Flash... as I described or use official unlocking method.
Hi Kentaurest tx for this. Forewarned is forearmed I guess.
So I assume it was the fake global ROM you were having trouble with re: Xposed - you hadn't flashed and other ROMs right?
(I have Xposed working on the 25/11 CM13 ROM from the China MIUI forums... But I guess its something of a crapshoot which ROMs do and don't break the device..)
To clarify (for future) - when you say "don't flash unsupported non xiaomi roms" do you mean any third party ROM, or ROMs now built specifically for the redmi 4?
Tx
J
jontseng said:
To clarify (for future) - when you say "don't flash unsupported non xiaomi roms" do you mean any third party ROM, or ROMs now built specifically for the redmi 4?
Click to expand...
Click to collapse
To my understanding bootloader checks if the system is signed with xiaomi key or not... so all xiaomi stuff will load, but xiaomi.eu unofficial global would not.
Also there is special Xposed for Miui, which I didn't try, last pages in the thread seem to suggest to use v86.2
http://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634
kentaurest said:
It is dangerous, you can install supersu and twrp this way, but don't flash non official roms.
Xiaomi roms should relock the bootloader.
Also don't try to install xposed, it didn't work for me.
After xposed made my phone bootloop I installed unofficial global and ended up with "bricked phone" left only with fastboot or black screen (qualcomm diagnostics interface 9000E) and couldn't turn off the phone.
I made deep flashing cable - usb cable where you can short GND and D+
http://xiaomitips.com/media/2016/08/Deep-FLash-Cable-Architecture-680x318.jpg
Connected phone to the computer (don't short the cables yet), used "fastboot reboot" to restart phone.
Quickly shorted GND and D+ for a few seconds, then windows installed HS-USB QDloader 9008 driver
and I could use Mi Flash to restore the phone, this time to the china developer rom
(fastboot version ends with .tgz) with clean all and locked options.
I was quite happy with fake global, twrp and supersu, pity xposed ruined it.
Click to expand...
Click to collapse
Some others used this method instead. for 900E problem. https://www.youtube.com/watch?v=j27x5iJSS40, seems to work for th. Just read it from other forums
kentaurest said:
To my understanding bootloader checks if the system is signed with xiaomi key or not... so all xiaomi stuff will load, but xiaomi.eu unofficial global would not.
Click to expand...
Click to collapse
Hmmm. Funny the CM13 ROM runs then.
I suspect given kernal sources haven't been released they are just using the official build kernel, hence it passes any checks?
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
I'd double check that Allow OEM Unlock in dev options is actually on
ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!
Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?
Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.
PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.
It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.
hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same
Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.
I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.
its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"
Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data
I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.
gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.
Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me
Hello everyone,
I unlocked BL, flashed twrp and a xiaomi.eu rom. Booted all fine. Afterwards I flashed havoc os, but now my phone doesn't boot into android or twrp. It just boots into fastboot mode or shows me the redmi logo over and over. I've already tried to flash this rom: https://forum.xda-developers.com/k20-pro/how-to/rom-miui-10-3-1-0-global-eea-fastboot-t3962880 with fastboot. Accidentally chose "clean all and lock" ,but luckily that didn't work I guess, because when I type "fastboot oem device-info" I get this: \
c:\adb> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.008s]
Finished. Total time: 0.008s
So when I try to flash the room with the flash tool I get an error after approximately "flash crclist error". Tried a few times and it flashed, but the phone still doesn't boot into android.
What should I do now?
Please help
Have you tried using a short folder name for the unzipped rom? Like C:\Mi. I had a fastboot bootloop yesterday too and all guides said you should use a short path.
I messed up trying to root my phone but i found a way to fix by flashing to a newer firmware and the phone worked!
I tried to root again but this time i didnt enable developer option/usb debugging and now im stuck at bootloader screen
i cant enter recovery mode and i cant start the device.
im getting Slot _a is unbootable error message
i tried fastboot set_active _b but still getting same error..
fastboot flashing unlock doesnt work anymore because i dont have usb debugging ON
fastboot oem unlock -- getting this message
...
FAILED (remote: unknown command)
finished. total time: 0.004s
fastboot oem device-info ----------- (bootloader) Device unlocked: false
am i completely screwed?
sorry for the bad english
edit: im on version 1908,25 Global
EDIT: solved by this guide https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042 THANK YOU SO MUCH
Hi, i wanted to relock my Bootloader again. I deinstalled Magisk per app , did a factory reset and now i should be able to do Fastboot oem Lock in adb or not ? Cause i get failure every Time i try that its an unknown command. Can someone Help me mabye?
Edit like that, Reboot Bootloader work but then from there on not.
C:\adb2>adb reboot bootloader
C:\adb2>fastboot oem lock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
We used fastboot flashing unlock to unlock bootloader so I guess you need to use
Fastboot flashing lock
yes that was it thank you much