The overall procedure is too simple, let me tell you how.
UPDATE: Looks like it's also applicable on Nokia 2.1 V by analyzing aboot. So previous NB1-Collision reserved as reference of EDL method, in case HMD may block it soon.
Please let me know if it doesn't work on your current firmware version. I'm working on make the overall procedure much more stable.
UPDATE: Looks like NB1-Collision is the only way to unlock the bootloader. Please read this topic to acquire the tool and attempt to unlock it: https://forum.xda-developers.com/showthread.php?p=79825293
If Android 9 firmware installed, phone disassembly and wire trick required.
So we recommend users unlock the phone immediately once bought.
Following procedure is archived.
Step 1: Download firmware which consists the service bootloader file
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download E2M-0390-0-00WW-B02 one in this case. If you're using Android 9, download E2M-108C-0-00WW-B01.
Then, extract E2M-0-0390-00WW-1-2-emmc_appsboot_service.zip to get service bootloader file, and the extract password is "WLBGFIH123".
Step 2: Boot your phone to Download mode (Fastboot mode)
You can execute following command then connect your phone when powered off, or use any other method you're familiar with:
Code:
fastboot oem alive
Step 3: Flash service bootloader
Code:
fastboot oem dm-verity (md5_of_serial_number)
Surprised huh? This command is still usable on Nokia 2.1, even on Android 9 basis, not sure why.
For example, if your Serial Number is E2MGAHIKARICALYX, the md5 checksum is 0ab1b1e9f3aacc85849341cd5fb21412, then command will be:
Code:
fastboot oem dm-verity 0ab1b1e9f3aacc85849341cd5fb21412
You can simply Google a website to calculate md5 checksum of a string.
And flash service bootloader:
Code:
fastboot flash aboot /path/to/E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
fastboot reboot-bootloader
Step 4: Unlock the bootloader
Your phone will reboot to service bootloader. Then grant unlock permission with following commands:
Code:
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
Then unlock the bootloader:
Code:
fastboot oem flashing unlock_critical
When your phone is erasing userdata, then:
Code:
fastboot oem alive
(wait for triggering to download mode)
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this method, you can use EDL method to downgrade aboot partition from this article: https://forum.xda-developers.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
Many thanks,,
I think it would be too much to ask right now for Nokia 8.1 , but as 8.1 is very popular Nokia device right now and it's launched in many countries too,,,is it possible that we would see smthng like this for Nokia 8.1 tooo
I'm stuck on a locked bootloader on my 6.1 plus
Would this work on a Nokia 2?
Hey... How to I unlock NOKIA 2 Bootloader?... TA-1029
so i manually rebooted my nokia 2.1 to download mode but fastboot commands not working cuz my windows does not detect my phone i tried installing drivers manually but after fastboot commant it's stuck at <waiting for device> ,plz help guys
souhail sboui said:
so i manually rebooted my nokia 2.1 to download mode but fastboot commands not working cuz my windows does not detect my phone i tried installing drivers manually but after fastboot commant it's stuck at <waiting for device> ,plz help guys
Click to expand...
Click to collapse
Me too, I don't know what's up
scaryguadian said:
Me too, I don't know what's up
Click to expand...
Click to collapse
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working it have to be a driver issue but i tried a lot but no hope
souhail sboui said:
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working it have to be a driver issue but i tried a lot but no hope
Click to expand...
Click to collapse
Can someone suggest a driver we can use or a link to the WORKING nokia 2.1 drivers
souhail sboui said:
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working it have to be a driver issue but i tried a lot but no hope
Click to expand...
Click to collapse
oh, its already working for me, just disable signature driver if you are on window 8, 8.1 or 10 and reinstall the drivers thats all.
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
hikari_calyx said:
The overall procedure is too simple, let me tell you how.
UPDATE: Looks like it's also applicable on Nokia 2.1 V by analyzing aboot. So previous NB1-Collision reserved as reference of EDL method, in case HMD may block it soon.
Please let me know if it doesn't work on your current firmware version. I'm working on make the overall procedure much more stable.
Step 1: Download firmware which consists the service bootloader file
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download E2M-0390-0-00WW-B02 one in this case. If you're using Android 9, download E2M-108C-0-00WW-B01.
Then, extract E2M-0-0390-00WW-1-2-emmc_appsboot_service.zip to get service bootloader file, and the extract password is "WLBGFIH123".
Step 2: Boot your phone to Download mode (Fastboot mode)
You can execute following command then connect your phone when powered off, or use any other method you're familiar with:
Code:
fastboot oem alive
Step 3: Flash service bootloader
Code:
fastboot oem dm-verity (md5_of_serial_number)
Surprised huh? This command is still usable on Nokia 2.1, even on Android 9 basis, not sure why.
For example, if your Serial Number is E2MGAHIKARICALYX, the md5 checksum is 0ab1b1e9f3aacc85849341cd5fb21412, then command will be:
Code:
fastboot oem dm-verity 0ab1b1e9f3aacc85849341cd5fb21412
You can simply Google a website to calculate md5 checksum of a string.
And flash service bootloader:
Code:
fastboot flash aboot /path/to/E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
fastboot reboot-bootloader
Step 4: Unlock the bootloader
Your phone will reboot to service bootloader. Then grant unlock permission with following commands:
Code:
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
Then unlock the bootloader:
Code:
fastboot oem flashing unlock_critical
When your phone is erasing userdata, then:
Code:
fastboot oem alive
(wait for triggering to download mode)
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this method, you can use EDL method to downgrade aboot partition from this article: https://forum.xda-developers.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
Click to expand...
Click to collapse
thanks a lot. I have followed the above instructions, but when I tried the second command, I got an error, here is my log
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot devices
E2MBA81107001697 fastboot
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem alive
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem dm-verity 6e4b6d5
21a65f379bd4ebf94d462005e
...
FAILED (remote: unknown command)
finished. total time: 0.036s
scaryguadian said:
oh, its already working for me, just disable signature driver if you are on window 8, 8.1 or 10 and reinstall the drivers thats all.
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
thanks a lot. I have followed the above instructions, but when I tried the second command, I got an error, here is my log
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot devices
E2MBA81107001697 fastboot
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem alive
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem dm-verity 6e4b6d5
21a65f379bd4ebf94d462005e
...
FAILED (remote: unknown command)
finished. total time: 0.036s
Click to expand...
Click to collapse
thnx but it didn't work i still can't make the fastboot commands detect the device and am sure the drivers are right
scaryguadian said:
oh, its already working for me, just disable signature driver if you are on window 8, 8.1 or 10 and reinstall the drivers thats all.
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
thanks a lot. I have followed the above instructions, but when I tried the second command, I got an error, here is my log
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot devices
E2MBA81107001697 fastboot
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem alive
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem dm-verity 6e4b6d5
21a65f379bd4ebf94d462005e
...
FAILED (remote: unknown command)
finished. total time: 0.036s
Click to expand...
Click to collapse
It won't work. Only very old bootloaders supported dm-verity.
Sent from my Nokia 8.1
singhnsk said:
It won't work. Only very old bootloaders supported dm-verity.
Click to expand...
Click to collapse
So, what do you suggest I do??
scaryguadian said:
So, what do you suggest I do??
Click to expand...
Click to collapse
The unlock can only be done via any of the two:
1. Disassemble > Trigger EDL mode.
2. The paid remote unlock service.
Sent from my Nokia 8.1
thnx for the guide man keep it up
some one posted the same problem : after the "fastboot oem dm-verity (md5_of_serial_number)" command it shows "FAILED (remote: unknown command)" ,any solution so i can continue unlocking my device ??
im also getting "FAILED (remote: unknown command)"
EDM not working either
singhnsk said:
It won't work. Only very old bootloaders supported dm-verity.
Click to expand...
Click to collapse
Can i downgrade then?
anyone who had the "FAILED (remote: unknown command)"
try typing your serial number in uppercase, that worked for me, but now im stuck on "fastboot oem fih on" i get the remote error
singhnsk said:
It won't work. Only very old bootloaders supported dm-verity.
Click to expand...
Click to collapse
Can i downgrade then?
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
Shmegma said:
anyone who had the "FAILED (remote: unknown command)"
try typing your serial number in uppercase, that worked for me, but now im stuck on "fastboot oem fih on" i get the remote error
Click to expand...
Click to collapse
Still doesn't work, what update are you running
hikari_calyx said:
The overall procedure is too simple, let me tell you how.
UPDATE: Looks like it's also applicable on Nokia 2.1 V by analyzing aboot. So previous NB1-Collision reserved as reference of EDL method, in case HMD may block it soon.
Please let me know if it doesn't work on your current firmware version. I'm working on make the overall procedure much more stable.
UPDATE: Looks like NB1-Collision is the only way to unlock the bootloader. Please read this topic to acquire the tool and attempt to unlock it: https://forum.xda-developers.com/showthread.php?p=79825293
If Android 9 firmware installed, phone disassembly and wire trick required.
So we recommend users unlock the phone immediately once bought.
Following procedure is archived.
Step 1: Download firmware which consists the service bootloader file
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download E2M-0390-0-00WW-B02 one in this case. If you're using Android 9, download E2M-108C-0-00WW-B01.
Then, extract E2M-0-0390-00WW-1-2-emmc_appsboot_service.zip to get service bootloader file, and the extract password is "WLBGFIH123".
Step 2: Boot your phone to Download mode (Fastboot mode)
You can execute following command then connect your phone when powered off, or use any other method you're familiar with:
Code:
fastboot oem alive
Step 3: Flash service bootloader
Code:
fastboot oem dm-verity (md5_of_serial_number)
Surprised huh? This command is still usable on Nokia 2.1, even on Android 9 basis, not sure why.
For example, if your Serial Number is E2MGAHIKARICALYX, the md5 checksum is 0ab1b1e9f3aacc85849341cd5fb21412, then command will be:
Code:
fastboot oem dm-verity 0ab1b1e9f3aacc85849341cd5fb21412
You can simply Google a website to calculate md5 checksum of a string.
And flash service bootloader:
Code:
fastboot flash aboot /path/to/E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
fastboot reboot-bootloader
Step 4: Unlock the bootloader
Your phone will reboot to service bootloader. Then grant unlock permission with following commands:
Code:
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
Then unlock the bootloader:
Code:
fastboot oem flashing unlock_critical
When your phone is erasing userdata, then:
Code:
fastboot oem alive
(wait for triggering to download mode)
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this method, you can use EDL method to downgrade aboot partition from this article: https://forum.xda-developers.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
Click to expand...
Click to collapse
Hi, what am I doing wrong?
Code:
C:\adb>fastboot oem dm-verity ca5943eaee14c601267c58d289f50dd2
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\adb>fastboot flash aboot E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
Sending 'aboot' (954 KB) OKAY [ 0.032s]
Writing 'aboot' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Related
I want to install twrp recovery in mobile me, I have to do all the tutorial that is in Google and YouTube, I am very difficult time at the CMD, from the early look good, I enter format fastboot flash recovery twrp.img, but in fact, there are writing failed (remote: partition flashing is not allowed), how do I fix this, I haven't unlock bootloader, in the setting My mobile, I have activated OEM unlock the developer option, My Mobile : xiaomi redmi note 3 pro (Kenzo)
You have to unlock bootloader first if you want to install twrp
I have a Le(Letv) LeEco 2 smartphone.
The bootloader is selected unlocked,as is usb debugging selected.
But I fail to install the TWRP recovery rom.
The excerpt after running in ADB is shown below :--->
E:\ADB+Recovery>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
E:\ADB+Recovery>fastboot flash recovery twrp-3.0.2-0-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17234 KB)...
OKAY [ 0.563s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.584s
E:\ADB+Recovery>fastboot reboot
rebooting...
finished. total time: 0.000s
E:\ADB+Recovery>
Click to expand...
Click to collapse
How do I install TWRP successfully.
mar.ur said:
You have to unlock bootloader first if you want to install twrp
Click to expand...
Click to collapse
Does this error occur ONLY when the bootloader is locked ??? In other words, does this error mean the bootloader is locked?
SameerSohrab said:
Does this error occur ONLY when the bootloader is locked ??? In other words, does this error mean the bootloader is locked?
Click to expand...
Click to collapse
Yep your bootloader Is locked
Use command "fastboot oem unlock" or "fastboot oem unlock-go" to unlock bootloader.
After that "fastboot flash recovery ~/recovery.img"
Fastboot error unlocking
sebastian1978 said:
Use command "fastboot oem unlock" or "fastboot oem unlock-go" to unlock bootloader.
After that "fastboot flash recovery ~/recovery.img"
Click to expand...
Click to collapse
I used commands "fastboot oem unlock" or "fastboot oem unlock-go". but i still get
errors:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.046s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.040s
Hi, How I use this comand? On cm prompt?
Thank you
Same Problem
thierryrojas said:
Hi, How I use this comand? On cm prompt?
Thank you
Click to expand...
Click to collapse
did you solve the problem, I have the same issue with my phone?
@The_Joker after fastboot oem unlock i get: FAILED (remote: Token verification failed, reboot the device)
Same problem
the same worry. my redmi 4 does not even turn on. I think that I have deleted the system bad luck. he does not want to turn on and the booloader stays locked on miUnlock and per cmd.
what can i do?
Chiko Tridipa said:
I want to install twrp recovery in mobile me, I have to do all the tutorial that is in Google and YouTube, I am very difficult time at the CMD, from the early look good, I enter format fastboot flash recovery twrp.img, but in fact, there are writing failed (remote: partition flashing is not allowed), how do I fix this, I haven't unlock bootloader, in the setting My mobile, I have activated OEM unlock the developer option, My Mobile : xiaomi redmi note 3 pro (Kenzo)
Click to expand...
Click to collapse
partition flashing is not allowed if the bootloader is locked. U have to unlock ur bootloader in order to modify anything.
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
Server16 said:
the same worry. my redmi 4 does not even turn on. I think that I have deleted the system bad luck. he does not want to turn on and the booloader stays locked on miUnlock and per cmd.
what can i do?
Click to expand...
Click to collapse
unlock bootloader officially.
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
catalinrcd said:
@The_Joker after fastboot oem unlock i get: FAILED (remote: Token verification failed, reboot the device)
Click to expand...
Click to collapse
u cannot unlock bootloader by normal cmd command line. U have to use the official MI unlock for unlocking the redmi note 3.
pritamdutt said:
partition flashing is not allowed if the bootloader is locked. U have to unlock ur bootloader in order to modify anything.
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
unlock bootloader officially.
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
u cannot unlock bootloader by normal cmd command line. U have to use the official MI unlock for unlocking the redmi note 3.
Click to expand...
Click to collapse
The phone does not turn on. and I have already received the SMS from the unlocking MI before,
but my concern is that the phone will not turn on anymore. barely the MI logo appears and goes off
NB: I have already tried the flash cable qualcomm but still nothing
It's here : http://en.miui.com/unlock/
Hi! Where I should write these cmds? Answer pls
Server16 said:
The phone does not turn on. and I have already received the SMS from the unlocking MI before,
but my concern is that the phone will not turn on anymore. barely the MI logo appears and goes off
NB: I have already tried the flash cable qualcomm but still nothing
Click to expand...
Click to collapse
If it is blinking red probably you can flash through EDL mode.
you guys know there's an unofficial method to unlock bootloader right? the thread is currently hot:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
Oem unlocking
FAILED (remote: oem authentication failed,please get right authentication f)
finished. total time: 0.003s
I have this error message please help me
Hi the correct command on a A2 Lite is:
fastboot flash boot twrp.img
as in ... recovery is now "boot"
I bought the Asus ZenFone 8 Flip with the bootloader unlocked, it is not running a custom ROM. How do I lock the bootloader? Thank you
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
maicol07 said:
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
Click to expand...
Click to collapse
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Kiribro02 said:
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Click to expand...
Click to collapse
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
maicol07 said:
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
Click to expand...
Click to collapse
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Kiribro02 said:
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Click to expand...
Click to collapse
No, just follow these steps:
Make a backup of your phone!! Unlocking/Locking the bootloader erases all your data partition (so all your stuff will be gone!)
Install ADB on your PC if you don't have it (check how to install it: https://www.xda-developers.com/install-adb-windows-macos-linux/).
Plug in your device via USB with Debug USB setting enabled (in Developer Settings)
Open a terminal prompt on your PC
In the terminal run adb devices. If you see your device I the list then you're fine. Otherwise, you have mistaken something in the previous steps.
Run adb reboot fastboot (or adb reboot bootloader if it doesn't work) to reboot into fastboot mode
Run fastboot oem lock to lock the bootloader
Run fastboot reboot to reboot the system
Your device is now locked!
DISCLAIMER:
I'm not responsible of any data loss, damages and/or bricks you make to your device(s) by following this guide!
Click to expand...
Click to collapse
To update the system when a new version is out, since you won't receive OTAs:
Go to Zenfone 8 Flip support page: https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8-Flip/HelpDesk_Download/
Choose Android as OS and scroll down to "Firmware"
Download the latest zip
Put it in the internal storage (in the root directory, not inside another folder!)
Two paths:
If you put the zip from PC via USB simply unplug the USB cable
If you downloaded the zip and put it manually via file manager from the phone reboot the system
A notification should pop out, notifying you there is a firmware package to install!
Just follow the notification message and you'll be done!
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Kiribro02 said:
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Click to expand...
Click to collapse
Oh that's an issue I have all the times with Asus devices. There's a simple one-time fix though: just install the official Asus ADB drivers.
Download them from this page (I know it's the smaller Zenfone 8 page, but they work with every Asus device): https://www.asus.com/it/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Download/
Choose your windows version (for 10 and 11 choose 8.1)
Download the USB driver
Extract the archive somewhere in your PC
Open Device manager in your PC (search it in start menu) while the phone is connected via USB and in fastboot mode
You'll notice an unknown device with a yellow/orange warning icon at the top of the devices list. Right click on it and choose Update drivers.
Choose "Search driver in the PC" (the second option (don't choose the first one since it searches the driver automatically on Windows update))
Choose the folder you extracted
Click "Next"
Drivers should be installed and fastboot should recognize your device (to test run the command: fastboot devices)
Sorry for the late reply, but I didn't get any notification from XDA
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Kiribro02 said:
When I try to update the drivers it says that windows was unable to install your and then it says the device.
Click to expand...
Click to collapse
Do you installed the drivers when the phone is in fastboot mode?
Also, I've noticed some steps are not clear (and one is doubled), I'll clean it
Kiribro02 said:
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Click to expand...
Click to collapse
Try all the two, I don't remember which one works (I think the Composite worked for me), but try also with the other ones
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
b4rbaar said:
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
Click to expand...
Click to collapse
Hi, yes you should create a new thread since it's a different topic
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
wyktron said:
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
Click to expand...
Click to collapse
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
maicol07 said:
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
Click to expand...
Click to collapse
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
wyktron said:
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
Click to expand...
Click to collapse
Try this one:
Code:
fastboot oem asus-csc_lk
maicol07 said:
Try this one:
Code:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
wyktron said:
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
Click to expand...
Click to collapse
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
maicol07 said:
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
Click to expand...
Click to collapse
@maicol07 there's no OEM unlock in my developer options, only the USB debugging (which is already on)
besides this oem method, is there another way to lock it? perhaps through the zenfone flash tool (I have it installed and it detects my phone, but never used it)
Getting super frustrated!
Using ADB Debuging. Here are my steps.
1. adb devices
2. adb reboot bootloader
3.fastboot devices.
4. fastboot oem unlock
Then I get this...
FAILED (remote: unknown command)
finished. total time: 0.005s
after so many attempts I finally check adb devices and nothing shows up! It's like it automatically disconnects with adb debugging but it does not. Because I am able to to put fastboot reboot.
Can someone please help me with this! Thank you!
Use the fast boot command
Fastboot flashing unlock
Only this works on A12 devices
fastboot flashing unlock
oem unlock has been deprecated for awhile, manufacturers were just slow to implement changes.
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
mayberandomparable said:
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
Click to expand...
Click to collapse
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
TNSMANI said:
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
Click to expand...
Click to collapse
080293723C004560
Does this qualifies as having distinct drivers? I'm not too sure.
mayberandomparable said:
080293723C004560
Click to expand...
Click to collapse
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Code:
C:\>fastboot devices
C:\>fastboot getvar version
C:\>fastboot getvar all
TNSMANI said:
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Click to expand...
Click to collapse
I tried the commands, but one stood out because of the output it given. Fastboot getvar all returned nothing for all. And I did try the official Android platform-tools, but it's still the same results, I'm afraid.
Beside that, getvar version given a 1.0 version. Checked the device ID on both modes, they're the same.
Also, I did extensively search for any sliver of documentation on the fastboot of this device, but I basically got nothing, since this device is still fairly new.
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Renate said:
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Click to expand...
Click to collapse
I might picking up what you're putting down here.
The first 3 getvar(s) returned empty, partition-size:boot returned a failure, but boot_a and boot_b returned the same 0x4000000
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Renate said:
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Click to expand...
Click to collapse
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
TNSMANI said:
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Click to expand...
Click to collapse
Got stuck.
(ignore me listening to PATD, forgot for a moment)
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
You made me watch that video of PATD. It's kind of violent, eh?
Renate said:
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
Click to expand...
Click to collapse
Oh shoot, yeah it is.
Well, we're going in circles now.
mayberandomparable said:
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
Click to expand...
Click to collapse
So, is this operation possible?
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Renate said:
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Click to expand...
Click to collapse
Hardly a Qualcomm thing, since this is using UNISOC.
Also, yes, it does have a fastbootd mode. Found on a whim!
Edit: Just tried EDL, sent straight back to the regular reboot command.
So... Does this other fastboot react at all differently?
Renate said:
So... Does this other fastboot react at all differently?
Click to expand...
Click to collapse
Oh I got something! The flashing unlock didn't work, guessing the manufacturer changed it. But OEM works flawlessly!
The last time I tried to do anything on fastbootd, platform-tools didn't even recognized the device, but now it works!
mayberandomparable said:
... but now it works!
Click to expand...
Click to collapse
So, can you fastboot erase fishheads
Renate said:
So, can you fastboot erase fishheads
Click to expand...
Click to collapse
Oop- still got a locked error, unfortunately.
first of i apologise if i have bad english
ok so i had this device for some time and decited to root it (my first time rooting a phone). And i need to unlock bootloader to flash stuff and i have all necessary things on my pc (platform tools,drivers,) everything seems to be working but as soon as i get into bootloader the only command that works is "fastboot devices" Any other commands dont work. I tried everything online and this is my only other thing left to do. I've been researching for 2 days at this point and i am almost certain that the commands are disabled by the company itself (like huawei) did anybody else ever root/unlock bootloader for this device because i didnt find any actual root guide for the particular device (besides from the auto generated ones like https://rootguia.com/how-to-flash-caterpillar-cat-s31/ https://mobilewithdrivers.com/unlock-bootloader/cat-s31-16gb-2gb-ram )
The exact error is:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(and this error is for every single command that uses fastboot besides from fastboot devices. Adb works just fine)
I tried:
reinstalling drivers
installing drivers that are "prepared" for the cat s31
changing cable
changing port to usb 2.0
reinstalling platform tools (from official google site)
checking device manager for the device (it shows up as android bootloader interface)
trying alternative oem unlock commands (fastboot oem unlock, fastboot flashing unlock and 2 other commands that i cant remember rn)
having oem unlocking and usb debugging enabled from the developer options
in my opinion the only explanation is the commands being disabled by default and even if it was it wouldnt be known if it was since most people dont root or purchase this device
please help me out here
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
aIecxs said:
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
Click to expand...
Click to collapse
sorry i forgot to mention im running android 8.1 oreo on this device and devinfo partition method will not work according to what i read
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
aIecxs said:
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Click to expand...
Click to collapse
what do you mean by dump phone into edl mode do i download one of these https://ministryofsolutions.com/2022/01/cat-s31-edl-firmware-android-8-1-official-rom.html and install it from recovery mode and try to get it in edl mode and will it not work if i dont dump
just extract that ROM you found
aIecxs said:
just extract that ROM you found
Click to expand...
Click to collapse
and do what. im new to the rooting stuff
find the file aboot.mbn (or similar) and analyze for fastboot commands
aIecxs said:
find the file aboot.mbn (or similar) and analyze for fastboot command
Click to expand...
Click to collapse
so i downloaded the file and these are the things in the firmware file (attachement)
i cant find a file that looks or resambles aboot.mbn
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
aIecxs said:
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
Click to expand...
Click to collapse
sooo turns out win11 strings commands are kinda different or broken (probably not im just dumb) i just used notepad with ctrl+f and couldnt find anything besides the text that says are you sure you want to unlock bootloader but that is probably not related since i didnt find any commands or anything. So im actually going to attach the emmc_appsboot.mbn i know it looks sketchy you dont have to download it its totally understandable but if you do please do give it a check and respond. I want to get this done one way or another its 1 am i want to sleep ;(
could it be true that they made a truly un unlockable unrootable device
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
Click to expand...
Click to collapse
trust me i have tried many many many many times and only got a
FAILED (remote: 'unknown command')
fastboot: error: Command failed
edit: the only place oem unlock is mentioned is a text that says oem unlock not allowed which might be default text by android or whatever but cat devs somehow messed it up somehow??
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
Click to expand...
Click to collapse
just saw the edit i will check now
nope nothing related no oem unlock no fastboot no flashing no flash nothing is mentioned ill attach it if you want to look
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
aIecxs said:
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
Click to expand...
Click to collapse
from recovery using the flash firmware with adb option??
edit: i meant apply update from adb
edit2: what if i hard reset from recovery would that reset the firmware?
edl firmware cannot flashed from recovery. power off phone, press both volume keys and plug in usb-cable. check VID/PID from windows device manager. if you see device ID (05c6:9008) the phone is in EDL mode. you can now use EDL tool (post #2) and backup current ROM. then you can flash other ROM.
aIecxs said:
It's edl firmware cannot flashed from recovery
Click to expand...
Click to collapse
so what do i download that can be flashed from recovery