Related
Good day!
Im trying to unlock bootloader to root the tab. Generally, i have followed a guide in a thread posted in this site (rooting zenpad c7 z170c) which was claimed to work with z370 by some. There were no problems encountered when using the method except when im already in fastboot, commands i enter like "fastboot oem unlock" return a "failure unknown command " from the prompt. I tried another command "fastboot flashing unlock" but the prompt returned "failure remote failure".
After that, i tried using "fastboot getvar all" and showed that bootloader is secured and still locked. I even tried "fastboot boot [root image name].img" but would cause an error since device is still locked.
I used win7 while doing this and got the adb installer 1.4.3 from a thread here.
All help is greatly appreciated.thanks
Hello Friend! I also problema? yourself have solved? can you help me?
Inviato dal mio ASUS_Z00A utilizzando Tapatalk
Check out what worked for me!
alexjesse said:
Good day!
Im trying to unlock bootloader to root the tab. Generally, i have followed a guide in a thread posted in this site (rooting zenpad c7 z170c) which was claimed to work with z370 by some. There were no problems encountered when using the method except when im already in fastboot, commands i enter like "fastboot oem unlock" return a "failure unknown command " from the prompt. I tried another command "fastboot flashing unlock" but the prompt returned "failure remote failure".
After that, i tried using "fastboot getvar all" and showed that bootloader is secured and still locked. I even tried "fastboot boot [root image name].img" but would cause an error since device is still locked.
I used win7 while doing this and got the adb installer 1.4.3 from a thread here.
All help is greatly appreciated.thanks
Click to expand...
Click to collapse
In this LINK: http://forum.xda-developers.com/and...-c-7-0-z170c-p01z-root-method-t3311752/page21
---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------
... even though my experience (in:http://forum.xda-developers.com/and...-c-7-0-z170c-p01z-root-method-t3311752/page21 ) of not having to lose my data, apps and settings was a BONUS, do BACK UP your data, in case something different turns up for you.
good luck!!!
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 have a generic device when i can't check the status with "*#*#7378423#*#*" it doesn't bring anything up. When i use adb to reboot into the bootloader if i run "fastboot oem device info" or "fastboot oem unlock" it returns "..." never finishing.if i unplug the device i get failed (status read failed (too many links)) i think that's normal from searching but not sure anyways does anyone know an alternative method to check the bootloader status and something i could do to unlock it if its locked?
Edit another question i know recoveries can be flashed with a locked bootloader at least sometimes because i've done it but i can't find out if that is always the case, can they always or basically always be flashed if you have root? also if there are any exceptions to this and can they be flashed from adb, i used an app to do so and another one lol can recovery imgs have spaces in their name if i wish to rename
This is the case with roms too
I can't think of a way to get bootloader status other than fastboot (not all devices have access to fastboot)
download adb & fastboot for windows
Click Win+R >> Type "cmd"
connect your device with a good USB cable
Type: cd c:\adb
Type: adb reboot fastboot
Type: adb reboot bootloader
if nothing special happens (if it restarts normally and does not enter a special screen or something) then your device doesn't have fastboot access
if your device enters a new screen then it is probably in fastboot state (then you can continue)
Type: fastboot devices
(you should see your device listed)
Type: fastboot oem device-info
Hit Thanks :good: if this helped!
NHK said:
This is the case with roms too
I can't think of a way to get bootloader status other than fastboot (not all devices have access to fastboot)
download adb & fastboot for windows
Click Win+R >> Type "cmd"
connect your device with a good USB cable
Type: cd c:\adb
Type: adb reboot fastboot
if nothing special happens (if it restarts normally and does not enter a special screen or something) then your device doesn't have fastboot access
if your device enters a new screen then it is probably in fastboot state (then you can continue)
Type: fastboot devices
(you should see your device listed)
Type: fastboot oem device-info
Click to expand...
Click to collapse
It should be
Code:
adb reboot bootloader
And if you are using a MTK device, you can check bootloader status by
Code:
fastboot getvar all
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
ARandomNoob said:
I have a generic device when i can't check the status with "*#*#7378423#*#*" it doesn't bring anything up. When i use adb to reboot into the bootloader if i run "fastboot oem device info" or "fastboot oem unlock" it returns "..." never finishing.if i unplug the device i get failed (status read failed (too many links)) i think that's normal from searching but not sure anyways does anyone know an alternative method to check the bootloader status and something i could do to unlock it if its locked?
Edit another question i know recoveries can be flashed with a locked bootloader at least sometimes because i've done it but i can't find out if that is always the case, can they always or basically always be flashed if you have root? also if there are any exceptions to this and can they be flashed from adb, i used an app to do so and another one lol can recovery imgs have spaces in their name if i wish to rename
Click to expand...
Click to collapse
If you have MTK device, using adb and fastboot you can check bootloader status
Code:
fastboot getvar all
Augustoandro said:
It should be
Code:
adb reboot bootloader
And if you are using a MTK device, you can check bootloader status by
Code:
fastboot getvar all
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
If you have MTK device, using adb and fastboot you can check bootloader status
Code:
fastboot getvar all
Click to expand...
Click to collapse
You're right
I always write fastboot instead of bootloader when typing fast
I don't even have fastboot on my galaxy s5 so i'm sorry for typing something wrong lol
i will fix my reply
---------- Post added at 12:14 PM ---------- Previous post was at 12:04 PM ----------
Augustoandro said:
...
Click to expand...
Click to collapse
and how to get bootloader status on a samsung device without fastboot?
"adb reboot bootloader" enters download mode (only detected in odin, no fastboot or adb)
NHK said:
It should be
And if you are using a MTK device, you can check bootloader status by
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
If you have MTK device, using adb and fastboot you can check bootloader status
You're right
I always write fastboot instead of bootloader when typing fast
I don't even have fastboot on my galaxy s5 so i'm sorry for typing something wrong lol
i will fix my reply
---------- Post added at 12:14 PM ---------- Previous post was at 12:04 PM ----------
and how to get bootloader status on a samsung device without fastboot?
"adb reboot bootloader" enters download mode (only detected in odin, no fastboot or adb)
Click to expand...
Click to collapse
I don't know how to do it.
If you find a way to get bootloader status without fastboot, inform me about it.
Augustoandro said:
I don't know how to do it.
If you find a way to get bootloader status without fastboot, inform me about it.
Click to expand...
Click to collapse
that's a real bummer .. I'm programming an app that has a part which needs to check bootloader status...
but i can't find any way to do it on samsung (at least on my phone)
I mean for other devices it is just a matter of writing the code, because i know how to do it.. but on samsung it does not work this way
---------- Post added at 06:52 AM ---------- Previous post was at 06:36 AM ----------
Hey, check this out
https://android.stackexchange.com/q...loader-status-on-galaxy-s5-and-below-using-ad
On Samsung devices, if there is no OEM unlock in the Developer Settings, then the bootloader is unlocked by default. OEM lock is enabled on carriers models only.
Moreover Samsung devices don't have fastboot, they have a proprietary protocol instead.
Click to expand...
Click to collapse
So I guess i'll have to program my app to either check for the existence of that option in settings, or use fastboot if available
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
Hi, I tried unlock oem to root my devies but when run command fastboot.exe oem unlock-go i get "FAILED (remote: 'oem unlock is not allowed')". The WeChat post tell that only way to unlock in newest ZUI is downgrade. Anyone success downgrade from 13.5.870 and unlock the bootloader ?
abbytan3108 said:
Hi, I tried unlock oem to root my devies but when run command fastboot.exe oem unlock-go i get "FAILED (remote: 'oem unlock is not allowed')". The WeChat post tell that only way to unlock in newest ZUI is downgrade. Anyone success downgrade from 13.5.870 and unlock the bootloader
Click to expand...
Click to collapse
Hi there,
The response itself says that you have not allowed your oem to be unlocked. Turn on the Developer option, then enable oem unlocking and try again.