[GUIDE] How to unlock the bootloader of Nokia 2.1 and 2.1V

Search This thread

hikari_calyx

Senior Member
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://xdaforums.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://xdaforums.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
 
Last edited:

avi_loveindia

Senior Member
Feb 6, 2012
55
10
bhopal
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
 

scaryguadian

Member
Dec 16, 2018
21
2
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working :confused: it have to be a driver issue but i tried a lot but no hope

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 ----------

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://xdaforums.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/

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
 

souhail sboui

Senior Member
Jan 18, 2015
80
31
Xiaomi Poco X3 Pro
Realme GT 2 Pro
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

thnx but it didn't work i still can't make the fastboot commands detect the device and am sure the drivers are right
 
Last edited:

singhnsk

Senior Member
Nov 11, 2012
214
81
www.techmesto.com
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
It won't work. Only very old bootloaders supported dm-verity.

Sent from my Nokia 8.1
 

Shmegma

New member
Jul 15, 2019
4
0
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
 

androidgeek79

Senior Member
Jul 31, 2016
70
9
Amazon Kindle Fire
It won't work. Only very old bootloaders supported dm-verity.
Can i downgrade then?

---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------

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
Still doesn't work, what update are you running
 

imprestness

New member
May 27, 2017
4
0
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://xdaforums.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://xdaforums.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/

Hi, what am I doing wrong?:rolleyes:

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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    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://xdaforums.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://xdaforums.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
    1
    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
    1
    Me too, I don't know what's up
    when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working :confused: it have to be a driver issue but i tried a lot but no hope
    1
    when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working :confused: it have to be a driver issue but i tried a lot but no hope
    Can someone suggest a driver we can use or a link to the WORKING nokia 2.1 drivers
    1
    So, what do you suggest I do??
    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