Related
hey please help i am unable to unlock boot loader of my coolpad note 5 which has snapdragon 617 soc, no unlock code type help or instruction on official forum and no help there because all command returns as unknown command ,
i tried many command except these two command all return unknown command ,
fastboot devices works shows device no
fast getvar all works showing something
i checked all driver installed properly and pc showing it on device manager as fastboot device even fastboot recognized it as a fastboot devices, also i allow oem unlocking on developer setting and enabled usb debugging
after this all command like
fastboot oem unlock
fastboot oem unlock-go
fastboot boot
fastboot reboot
fastboot flashing unlock
fastboot oem device-info
fastboot flash
all and more i found i net returns unknown command remote
i tried with vendor id but no result
i checked fastboot getvar all returns its kernal as lk
so do little kernel has problem , i have its firmware package but not found aboot.c
please help its unrooted
attached error command screenshot in zip
I am facing same issues
Sent from my Andromax A16C3H using Tapatalk
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
corkiejp said:
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
Click to expand...
Click to collapse
thanks @corkiejp for your reply
I agree with you for fastboot instead of adb but the result is the same.
I cannot go inside the tablet to change parameters
Some forum said that I can Unlock in recovery mode
Is it true?
when my tablet is in recovery mode (On/off + Vol Up)
the tablet show me device state : locked
I am in state HBOOT
the on my computer I do that
C:\Users\maison>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.015s]
finished. total time: 0.018s
after I go in FASTBOOT mode then :
C:\Users\maison>fastboot oem unlock
< waiting for device >
what can I do to have the Key to unlock
No you need fastboot mode to unlock the bootloader!
Is the command "fastboot devices" listing your device. If not check your drivers for your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT4B6JT00881 fastboot
after that i try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload volantis-ota-n9f27m-ad1aee0f.zip
loading: 'volantis-ota-n9f27m-ad1aee0f.zip'adb server is out of date. killing...
* daemon started successfully *
serving: 'volantis-ota-n9f27m-ad1aee0f.zip' (~0%) * failed to read command: Invalid argument
i think tablet i now connected to computer
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.011s]
finished. total time: 0.014s
As suspected the option to unlock is not selected in developer options.
If your successful in sideloading an OTA image in recovery mode (not fastboot mode), you will still encounter FRP on booting the device.
Edit: - As said before ADB commands do not work in fastboot mode. And fastboot commands do not work in Recovery mode!
As said before your only hope is to remember your account and password used (or the very last account you used on the device might work).
If you haven't updated the rom in the last year, you maybe able to use FRP Bypass trick.
jackvig said:
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
Click to expand...
Click to collapse
You should not have factory reset if you do not know the account password. It is protected by "factory reset protection". To prevent it from being used if it is stolen. You are most likely going to need the password for the account that was logged in when you reset.
Flashing is not going to help. And as mentioned previously, you cannot unlock the bootloader now since you cannot go into developer options and turn on oem unlocking.
I just have small question, like tittle:
How to check bootloader was locked or unlocked on Thor ?
I searched a round but cant find any anwers.
Mark2014 said:
I just have small question, like tittle:
How to check bootloader was locked or unlocked on Thor ?
I searched a round but cant find any anwers.
Click to expand...
Click to collapse
Fastboot oem idme ?
- or -
Fastboot -i 0x1949 oem idme ?
You won't get a response if the bootloader is locked. Be sure to validate fastboot communication with 'fastboot devices' before issuing idme.
Davey126 said:
Fastboot oem idme ?
- or -
Fastboot -i 0x1949 oem idme ?
You won't get a response if the bootloader is locked. Be sure to validate fastboot communication with 'fastboot devices' before issuing idme.
Click to expand...
Click to collapse
Best answer. Many thanks :fingers-crossed::fingers-crossed::fingers-crossed:
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'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
mayberandomparable said:
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
Click to expand...
Click to collapse
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
TNSMANI said:
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
Click to expand...
Click to collapse
080293723C004560
Does this qualifies as having distinct drivers? I'm not too sure.
mayberandomparable said:
080293723C004560
Click to expand...
Click to collapse
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Code:
C:\>fastboot devices
C:\>fastboot getvar version
C:\>fastboot getvar all
TNSMANI said:
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Click to expand...
Click to collapse
I tried the commands, but one stood out because of the output it given. Fastboot getvar all returned nothing for all. And I did try the official Android platform-tools, but it's still the same results, I'm afraid.
Beside that, getvar version given a 1.0 version. Checked the device ID on both modes, they're the same.
Also, I did extensively search for any sliver of documentation on the fastboot of this device, but I basically got nothing, since this device is still fairly new.
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Renate said:
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Click to expand...
Click to collapse
I might picking up what you're putting down here.
The first 3 getvar(s) returned empty, partition-size:boot returned a failure, but boot_a and boot_b returned the same 0x4000000
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Renate said:
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Click to expand...
Click to collapse
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
TNSMANI said:
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Click to expand...
Click to collapse
Got stuck.
(ignore me listening to PATD, forgot for a moment)
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
You made me watch that video of PATD. It's kind of violent, eh?
Renate said:
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
Click to expand...
Click to collapse
Oh shoot, yeah it is.
Well, we're going in circles now.
mayberandomparable said:
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
Click to expand...
Click to collapse
So, is this operation possible?
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Renate said:
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Click to expand...
Click to collapse
Hardly a Qualcomm thing, since this is using UNISOC.
Also, yes, it does have a fastbootd mode. Found on a whim!
Edit: Just tried EDL, sent straight back to the regular reboot command.
So... Does this other fastboot react at all differently?
Renate said:
So... Does this other fastboot react at all differently?
Click to expand...
Click to collapse
Oh I got something! The flashing unlock didn't work, guessing the manufacturer changed it. But OEM works flawlessly!
The last time I tried to do anything on fastbootd, platform-tools didn't even recognized the device, but now it works!
mayberandomparable said:
... but now it works!
Click to expand...
Click to collapse
So, can you fastboot erase fishheads
Renate said:
So, can you fastboot erase fishheads
Click to expand...
Click to collapse
Oop- still got a locked error, unfortunately.