Related
Hi all,
I tried to reflash a Nexus 9 with official volantis-lrx22c, the bootloader was updated (3.43.0.0114) but the flash of the other partitions failed and now the device can only boot fastboot mode in locked and unlockable state.
When I try to reflash:
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
And when I try to fastboot oem unlock, I get:
(bootloader) ability is 0
(bootloader) Permission denied for this command!
I cannot boot android, so I cannot enable the the "Enable oem unlock"
Before this, I could falsh a recovery and backup, but the recovery disappeared and I cant flash anything anymore...
Any solution? Any way to force the oem unlock or the flash?
I saw this guy, Jonathan Levin, (I cannot post the link) that checked the effects of this "Enable oem unlock" on PST partition and saw one bit was set after, I was wondering if I could use "fastboot oem i2cw" + correct parameters to flip the corresponding bit, but I dont know if it's possible and what are the parameters to pass...
Thanks,
Pierre
I'm in the exact same position today. It's the first time I really fear about a soft-bricked Nexus thanks to the new "Enable OEM Unlock" option.
What has happened afterwards, pierrestone? Did you find a solution? :-|
EDIT: This was likely the article you were talking about. It looks interesting, maybe somehow its possible to enable OEM unlock from an ADB Shell.
newandroidbook.com/Articles/Nexus9.html
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 am trying to unlock the bootloader for my device (it's a cheap Chinese phone) and then root using Magisk. The first problem is that OEM Unlock option is not available in developer options, so I got no choice other than try unlocking using fastboot. Now the second problem is that fastboot doesn't show anything at all. Normally there is a Fastboot written at the top left corner of the device but in my case there is no output but the blank screen, and I do verify that my device is in fastboot mode because when I do fastboot devices, it show's the output:
Code:
C:\Users\Mujtaba>adb devices
List of devices attached
Y3123A0310Q0100020953 device
C:\Users\Mujtaba>adb reboot bootloader
C:\Users\Mujtaba>fastboot devices
Y3123A0310Q01000209 fastboot
Since fastboot was responding (partially), I tried to unlock the bootloader using different commands but each time I get read/write failed error.
Code:
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.011s
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 80.886s
Alas, I got the same results with fastboot oem unlock-go and fastboot flashing unlock as fastboot is not accepting (at least I think) any command except fastboot devices.
I read the official guide and there I found that:
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the unlock_ability to 1).
Click to expand...
Click to collapse
My device supports unlocking bootloader because I've checked the build.prop file using adb shell getprop and it includes the properties stated below:
The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device suppports flashing unlock, set ro.oem_unlock_supported to 1. If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0. If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or 0 if unlocked.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
Click to expand...
Click to collapse
Code:
C:\Users\Mujtaba>adb shell getprop
[ro.oem_unlock_supported]: [1]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.flash.locked]: [1]
[sys.oem_unlock_allowed]: [0]
.
.
Someone on reddit did this to find the OEM unlock state, mine of course returned 0 as you can see above.
Code:
adb shell getprop sys.oem_unlock_allowed
Device Specs:
CPU: ARM Cortex-A-7 @ 1.20 Ghz
GPU: Mali-400 MP
Board: sp7731cea (Unisoc aka Spreadtrum)
Build: Q Infinity C_MP_26_01
Treble: NA
Seamless update (A/B): NA
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
jwoegerbauer said:
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
Click to expand...
Click to collapse
Yes I know that and I already found a method but again it uses oem get_identifier_token to get Identifier token and when I do that fastboot returns nothing.
There are other methods as well, like getting a PAC file for your device then extracting boot.img from it, patching it with magisk manager and then flashing that single partition (in this case BOOT partition) using SPD Research Tool but it gives me error as well.
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
jwoegerbauer said:
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
Click to expand...
Click to collapse
I have installed SPD drivers and Google USB drivers however the problem is not with drivers because I can use the following commands without an issue:
Code:
fastboot devices
fastboot reboot
fastboot reboot bootloader
The problem occurs when using:
Code:
fastboot oem unlock
fastboot flashing unlock
Google's USB driver is only suitable to Google devices like the Pixel / Nexus.
As already said: Install the Android USB Driver matching your phone!
Take note that OEM's Fastboot implementation isn't always same as AOSP 's Fastboot.
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
BTW: I no longer participate this thread.
jwoegerbauer said:
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
I've already included this property in the post. It returned 1
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Hello and good morning, @roberto167
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Is that your phone? https://forum.xda-developers.com/c/alcatel-1.8103/
joke19 said:
È il tuo telefono? https://forum.xda-developers.com/c/alcatel-1.8103/
Click to expand...
Click to collapse
mine is model 1b with 2gb ram and android 11
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
aIecxs said:
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
Click to expand...
Click to collapse
as said already done and gives me the said error, enter fastboot mode
fastboot oem unlock
FAILED (remote: 'unknown command')
did you actually notice the difference between what I wrote and what you did?
aIecxs said:
did you actually notice the difference between what I wrote and what you did?
Click to expand...
Click to collapse
also given that command and also
fastboot flashing unlock
so what was the error message then
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
aIecxs said:
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
Click to expand...
Click to collapse
it seems very complicated as a procedure, being never done
usual error message looks like this
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
Click to expand...
Click to collapse
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
aIecxs said:
usual error message looks like this
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
Click to expand...
Click to collapse
even if it appears with the command fastboot devices, with these commands it remains waiting for any devices
Alcatel 1B Stock ROM / SIM unlock / etc....
ALCATEL 1B MEGATHREAD ( veken/seoul/TCL L7)...
forum.xda-developers.com
"UNLOCKING BOOTLOADER / ROOTING
For now, it is not possible... However mentions of secret key is spread all around the phone partitions (mainly abl file)
So if you have any experience editing bootloaders you can unlock...."
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)