Database Develop

[Q] Unable to use fastboot

After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.

I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s

antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.

g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!

antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too

g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!

antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?

g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry

1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.

Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .

fastboot error!!

I'm using LGv40 (lmv405ebw). I installed the latest minimal adb and fastboot driver 1.4.3. The adb command works fine. But when I do `fastboot oem device-id` i'm getting into some error. Couldn't figure it out.
C:\Users\ranji>adb reboot bootloader
C:\Users\ranji>fastboot devices
LMV405EBWxxxxxxxxx fastboot
C:\Users\ranji>fastboot oem device-id
...
FAILED (command write failed (Unknown error))
finished. total time: 0.004s
What is this error? How to solve it?

va2ranjith said:
I'm using LGv40 (lmv405ebw). I installed the latest minimal adb and fastboot driver 1.4.3. The adb command works fine. But when I do `fastboot oem device-id` i'm getting into some error. Couldn't figure it out.
C:\Users\ranji>adb reboot bootloader
C:\Users\ranji>fastboot devices
LMV405EBWxxxxxxxxx fastboot
C:\Users\ranji>fastboot oem device-id
...
FAILED (command write failed (Unknown error))
finished. total time: 0.004s
What is this error? How to solve it?
Click to expand...
Click to collapse
Try with USB 2.0

can anyone help me if I run fastboot oem unlock it says failed remote unknown command

can anyone help me plz when i run fastboot oem unlock it say failed remote unknown command
here is my full command line
Microsoft Windows [Version 10.0.18362.900]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
"my imei" device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
"my imei" fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell getprop ro.serialno
"my imei"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem key "my imei through a md5 hash generator"
...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>"fastboot --version
'"fastboot --version' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem help
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar info
getvar:info FAILED (remote: GetVar Variable Not found)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>

FireHeart_Max said:
can anyone help me plz when i run fastboot oem unlock it say failed remote unknown command
here is my full command line
Microsoft Windows [Version 10.0.18362.900]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
"my imei" device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
"my imei" fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell getprop ro.serialno
"my imei"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem key "my imei through a md5 hash generator"
...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>"fastboot --version
'"fastboot --version' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem help
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar info
getvar:info FAILED (remote: GetVar Variable Not found)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
use this command:
fastboot flashing unlock
you will see a message on your phone asking for yes or no to unlock flashing,
press volume + button and boom! flashing is now unlocked.
but you can only use this command after turning on OEM Unlocking in Developer Options.
see this thread below for more help.
Root Nokia 1 (TA-1066) (MT6737M) (Android 9 - Pie)
So, after trying more than a few methods I finally gained root on my TA-1066. 😴😪 If you also wanna root, here is how: 👇 To Root Nokia 1 (TA-1066) (Pie - Android 9) (Dual SIM) What you're gonna need: Working PC, 💻 Some Packet Data, 🌐 Some...
forum.xda-developers.com

(solved) Can't either unlock OEM or install recovery (Preflash validation failed)

Hello
I just purchased a cheap new Moto G7 Plus, only to install LineageOS on it. The phone is brand new and I just upgraded it to the latest Android 10.
I followed all instructions so far, and I am stuck, can't unlock the bootloader and/or install a recovery.
To unlock the bootloader I carefully followed instructions on the LineageOS wiki
Then I followed instructions on Motorola website
I received an email from Motorola with the unlock code
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
Despite the fact that it says OKAY, when I reboot in fastboot flash mode, I still see the message "oem_locked". So I am not totally sure that the unlock succeeded.
Then whatever I try, I can't install TWRP, see below :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
Z*****F5RR fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.4.0-0-lake.img
target reported max download size of 536870912 bytes
sending 'boot' (30080 KB)...
OKAY [ 0.686s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-lake.img
downloading 'boot.img'...
OKAY [ 0.686s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I obviously googled a few time but can't find any working solution. Some says its because my OEM is still locked, others because the USB port or cable might be problematic. I tried on 5 USB ports and a USB hub and I have the same issue, and my cable is brand new. I also restarted the whole unlocking procedure, received another mail from Motorola, with exactly the same unlock key, unlocked 10 times, nothing changes.
Any hint ?
Cheers

Ok forget it, its solved. I am an idiot I forgot to activate developer mode in the settings

Fastboot boot twrp 3.4 infinitely?
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!

same
Richard2707 said:
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
Click to expand...
Click to collapse
trying on my xt1965-2 and having this same issue, did you manage a workaround?

The twrp file needs to be in the correct location and the name needs to be exact.
I use linux so check up on which locations to use in windows.
But on linux I open a terminal in the folder where twrp is located.
So if the filename for twrp is for instance "twrp-3.3.1-0-lake.img", the command needs to be:
fastboot boot twrp-3.3.1-0-lake.img (NO spaces in the file name!)
Fastboot then pushes the file to the phone and boots it.

Flashing back to stock ends with errors

I was trying to go back to stock 10 from latest official lineage as I did few times before, but what I get is errors like below:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY225F37PD fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot flash partition gpt.bin
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
Then the flashing process hangs.
Has anyone have an idea what may be causing this behavior?
I tried different cables, different PC's (windows and linux), phone boots to lineage, fastboot mode states flashing unlocked, boots to TWRP or lineage recovery so all seems to be fine but obviously isn't.
Anyone else experienced a problem of this sort?

[SOLVED] If anyone is interested I came to this last idea and dug out the oldest laptop we have at home and it came through with minimal adb and fastboot!
No idea why, my bet is that this has to do with USB on three other computers I had used being 3.0 only and a 2.0 on the old ASUS.
Anyways, I'm happy I made it and hope this can help someone looking for a solution to a similar problem.