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"
Related
Hi guys,
Need some help with unlocking bootloader.
Anyway, after unlocking bootlader sucessfully and restarting, tablet doesn't load, it gets stuck after Sony and Xperia logo and keeps restarting over and over again, also after this I tried to flash boot.img of different firmwares, it doesnt boot up and doesn't go to recovery mode either.
What could be the problem?
P.S. though after this, tried to flash stock ROM with flashtool in flash mode, tablet loaded up and started working, but of course, if I try to flash any boot.img, it won't load up again...
Try looking for is it unlockable
Good day, can you try the following to check whether your tablet is unlockable?
You flash the stock firmware back,
then enter the service code in your tablet.
Then check whether it is unlockable.
The way to enter the service code is:
1) Open the Contact App,
2) Go to setting,
3) Long press the bottom area of the tablet, for maybe 10 sec?
4) After you release your finger, a dialer will come out.
5) Enter: without the quote "*#*#7378423#*#*"
6) I get this from Sony website:
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
Guide: How to enter Service Menu by XperiaBlog
If it show Yes, means that we need to find out other solution.
If No, then your tablet is not unlockable.
I'm Malaysian, I don't know what kind of Tablet cannot be unlocked in other region.
Trevor Chuah said:
Good day, can you try the following to check whether your tablet is unlockable?
You flash the stock firmware back,
then enter the service code in your tablet.
Then check whether it is unlockable.
The way to enter the service code is:
1) Open the Contact App,
2) Go to setting,
3) Long press the bottom area of the tablet, for maybe 10 sec?
4) After you release your finger, a dialer will come out.
5) Enter: without the quote "*#*#7378423#*#*"
6) I get this from Sony website:
Guide: How to enter Service Menu by XperiaBlog
If it show Yes, means that we need to find out other solution.
If No, then your tablet is not unlockable.
I'm Malaysian, I don't know what kind of Tablet cannot be unlocked in other region.
Click to expand...
Click to collapse
Hi,
Thanks for quick response. Yes bootloader is unlockable. Just to be more precise, it's SGP321
giosal said:
Hi,
Thanks for quick response. Yes bootloader is unlockable. Just to be more precise, it's SGP321
Click to expand...
Click to collapse
Okay. Now when you boot into fastboot mode,
you enter the command: fastboot devices
what does it come out?
Trevor Chuah said:
Okay. Now when you boot into fastboot mode,
you enter the command: fastboot devices
what does it come out?
Click to expand...
Click to collapse
This comes out:
Code:
C:\***>fastboot devices
CB5A1UV0GY fastboot
C:\***>
So, obviously, it sees it, right?
giosal said:
This comes out:
Code:
C:\***>fastboot devices
CB5A1UV0GY fastboot
C:\***>
So, obviously, it sees it, right?
Click to expand...
Click to collapse
Yes, it sees it.
Okay, the unlock key is expired once used.
I think maybe you can retrieve the key again from Sony website?
Sony Unlock
The following is a note in my own guide for unlocking
Maybe you try the getvar version before unlock.
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the phone is correctly connected
Click to expand...
Click to collapse
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
After unlock, try reboot it directly with
"fastboot reboot"
Trevor Chuah said:
Yes, it sees it.
Okay, the unlock key is expired once used.
I think maybe you can retrieve the key again from Sony website?
Sony Unlock
The following is a note in my own guide for unlocking
Maybe you try the getvar version before unlock.
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
After unlock, try reboot it directly with
"fastboot reboot"
Click to expand...
Click to collapse
Got the unlock key from Sony website, checked var version, unlocked bootloader. This is the output:
Code:
C:\*>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.037s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 3.681s]
finished. total time: 3.681s
C:\*>
Which is pretty strange, why doesn;t it succeed from first try?
After reboot it's the same: keeps restarting over and over again...
giosal said:
Got the unlock key from Sony website, checked var version, unlocked bootloader. This is the output:
Code:
C:\*>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.037s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 3.681s]
finished. total time: 3.681s
C:\*>
Which is pretty strange, why doesn;t it succeed from first try?
After reboot it's the same: keeps restarting over and over again...
Click to expand...
Click to collapse
Yup, it is weird, why not succeed for the first time.
Now is it rebooted?
Trevor Chuah said:
Yup, it is weird, why not succeed for the first time.
Now is it rebooted?
Click to expand...
Click to collapse
No, it just keeps restarting over and over... Although if I connect in fastboot mode and after connect to charger, it displays the charging progress.
giosal said:
No, it just keeps restarting over and over... Although if I connect in fastboot mode and after connect to charger, it displays the charging progress.
Click to expand...
Click to collapse
Have you try to let it restart and restart?
Maybe eventually it will successfully rebooted?
Trevor Chuah said:
Have you try to let it restart and restart?
Maybe eventually it will successfully rebooted?
Click to expand...
Click to collapse
I left it to restart over and over, it restarted already more than 10 times, still restarting...
giosal said:
I left it to restart over and over, it restarted already more than 10 times, still restarting...
Click to expand...
Click to collapse
I never have this problem.
Have you try fastboot other ROM's boot.img?
Not only boot.img with recovery, but real CustomROM.
Maybe you can try CyanogenMod or OmniROM.
Download it and extract it's boot.img.
Then try fastboot flash it and see.
I'm using OmniROM.
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
I never have this problem.
Have you try fastboot other ROM's boot.img?
Not only boot.img with recovery, but real CustomROM.
Maybe you can try CyanogenMod or OmniROM.
Download it and extract it's boot.img.
Then try fastboot flash it and see.
I'm using OmniROM.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
gonna try it now. is recovery included in OmniROM?
giosal said:
gonna try it now. is recovery included in OmniROM?
Click to expand...
Click to collapse
Yes. It include TWRP.
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
Yes. It include TWRP.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
OK, cool, actually gonna try CM11 for now, it downloaded much faster
this is what I get:
Code:
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.345s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
C:\*>
If I unlock bootloader again, it will write it....
Unlocked again, this is output:
Code:
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.047s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 0.391s]
finished. total time: 0.391s
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.344s]
writing 'boot'...
OKAY [ 0.516s]
finished. total time: 0.875s
C:\*>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\*>
Obviously, it doesn't boot now at all...
giosal said:
this is what I get:
Code:
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.345s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
C:\*>
If I unlock bootloader again, it will write it....
Unlocked again, this is output:
Code:
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
FAILED (remote: Command did not succeed)
finished. total time: 0.047s
C:\*>fastboot -i 0x0fce oem unlock 0x*
...
OKAY [ 0.391s]
finished. total time: 0.391s
C:\*>fastboot flash boot boot_CM.img
sending 'boot' (10664 KB)...
OKAY [ 0.344s]
writing 'boot'...
OKAY [ 0.516s]
finished. total time: 0.875s
C:\*>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\*>
Obviously, it doesn't boot now at all...
Click to expand...
Click to collapse
Hmm.....
After flash the cm boot.img, reboot, have you see Sony logo with purple led light on? No led light at all?
Maybe after boot up, you keep pressing volume up, until it enter recovery.
Btw, it is not necessary to enter fastboot unlock command each time. Just assume it has been unlocked.
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
Hmm.....
After flash the cm boot.img, reboot, have you see Sony logo with purple led light on? No led light at all?
Maybe after boot up, you keep pressing volume up, until it enter recovery.
Btw, it is not necessary to enter fastboot unlock command each time. Just assume it has been unlocked.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
That's the thing, I guess it doesn't unlock... Because unless I do it everytime before flashing, it fails the flashing as you can see in the output.
When I try to turn on tablet after flashing there is nothing at all, LED blinks once white and that's it. If I keep power button pressed, it keeps blinking. And it doesn't go into recovery, even though I keep pressing volume up button
giosal said:
That's the thing, I guess it doesn't unlock... Because unless I do it everytime before flashing, it fails the flashing as you can see in the output.
When I try to turn on tablet after flashing there is nothing at all, LED blinks once white and that's it. If I keep power button pressed, it keeps blinking. And it doesn't go into recovery, even though I keep pressing volume up button
Click to expand...
Click to collapse
I have no idea now...
Have you try install any recovery when you were at stock ROM?
And, you use flashtool to flash back the stock ftf file?
Did you untick all the ta files?
Sent from my SGP311 using XDA Free mobile app
Trevor Chuah said:
I have no idea now...
Have you try install any recovery when you were at stock ROM?
And, you use flashtool to flash back the stock ftf file?
Did you untick all the ta files?
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I did try, but it didn't work either... Could you give me a link to the recovery?
Yes, I use flashtool to flash back the stock ftf, but I never unchecked the ta files. What do they do? Let me try it now. Which files should I exclude and how exactly?
Hi! I wan't to unlock the bootloader with fastboot on adb but it don't work i tried two command:
"fastboot flashing unlock"
"fastboot oem unlock"
but i get the same error :
"FAILED: (remote: unknow command)
Can you help me?
Oméga-WiWi said:
Hi! I wan't to unlock the bootloader with fastboot on adb but it don't work i tried two command:
"fastboot flashing unlock"
"fastboot oem unlock"
but i get the same error :
"FAILED: (remote: unknow command)
Can you help me?
Click to expand...
Click to collapse
Hello the right command would be this ..... fastboot-modaco-windows oem unlock ... this command does not even work because there is not one between the commands of the stop
https://postimg.org/image/trqen63un/
---------- Post added at 03:20 PM ---------- Previous post was at 03:19 PM ----------
Did you manage to unlock?
Hi,
Please share the details to unlock bootloader and root Nokia 1 TA-1066
Nokia has released the kernel source code which is available at https://www.nokia.com/en_int/phones/opensource
Thank You!
-Mayur
The bootloader unlock method is totally the same to Nokia 3.
As for root method... not yet.
hikari_calyx said:
The bootloader unlock method is totally the same to Nokia 3.
As for root method... not yet.
Click to expand...
Click to collapse
I tried to unlock boot loader of Nokia 1 using Nokia 3 procedure. It is not working.
1. Take one IMEI number (there are two IMEI No as its a dual sim )
2. Generate key using https://passwordsgenerator.net/md5-hash-generator/
3. Bootloader unlock failed. Below are the steps I used
>fastboot.exe -i 0x2e04 oem key <key>
OKAY [ 0.003s]
finished. total time: 0.005s
>fastboot.exe -i 0x2e04 oem unlock
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7001)
finished. total time: 6.323s
JainMayurD said:
I tried to unlock boot loader of Nokia 1 using Nokia 3 procedure. It is not working.
1. Take one IMEI number (there are two IMEI No as its a dual sim )
2. Generate key using https://passwordsgenerator.net/md5-hash-generator/
3. Bootloader unlock failed. Below are the steps I used
>fastboot.exe -i 0x2e04 oem key <key>
OKAY [ 0.003s]
finished. total time: 0.005s
>fastboot.exe -i 0x2e04 oem unlock
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7001)
finished. total time: 6.323s
Click to expand...
Click to collapse
I have unlocked the bootloader successfully. Below are the steps to unlock bootloader for nokia 1
>adb get-serialno
Generage hash key using https://passwordsgenerator.net/md5-hash-generator/
fastboot.exe -i 0x2e04 oem key <xxxxxxxxxxx>
fastboot.exe -i 0x2e04 oem unlock
bootloader unlocked
Thank You!
-Mayur
Unlock bootloader
1. Get Phone Serial No
>adb get-serialno
2. Generage hash key using https://passwordsgenerator.net/md5-hash-generator/
3. Unlock bootloader
>fastboot.exe -i 0x2e04 oem key <xxxxxxxxxxx>
>fastboot.exe -i 0x2e04 oem unlock
Root Nokia 1
1. Flash recovery image
>fastboot flash recovery TWRP-3.2.1-frt-20180506.img
> Fastboot reboot
> Copy Magisk-v16.4.zip to the phone
> adb reboot recovery
2. Install Magisk-v16.4.zip in the recovery mode
3. Reboot and your phone will be with root previledges
No OS. Need firmware
I did a system format by mistake and now no OS is installed in my Nokia 1. I cannot find the stock firmware anywhere.
Can someone please send me the link for firmware of Nokia 1 TA-1066 or any custom rom. Please I beg of you.
MyTH30 said:
I did a system format by mistake and now no OS is installed in my Nokia 1. I cannot find the stock firmware anywhere.
Can someone please send me the link for firmware of Nokia 1 TA-1066 or any custom rom. Please I beg of you.
Click to expand...
Click to collapse
I added this zip you can use in twrp Link
Twrp
Do you have the file of this version TWRP-3.2.1-frt-20180506.img? The latest version TWRP-3.2.3-frt-20180802.img can’t install/flash any zip files.
Error:
“Checking for Digest files
Skipping Digest check: no digest file found”
hi everybody,
unknowing i flashed my nokia 1
now it is stuck in fastboot mode
i dint on usb debugging nor i on developer mode
i am unable to flash nor get serial no pls help
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
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)