Database Users

ERROR: could not clear input pipe; result -536870163

Trying to use fastboot to get back to factory default and I get this on the first step "erase userdata"
david-ln-imac:~ David$ /Users/David/fastboot-mac devices
HT036P900126 fastboot
david-ln-imac:~ David$ /Users/David/fastboot-mac erase userdata
ERROR: could not clear input pipe; result -536870163< waiting for device >

ERROR: could not clear input pipe; result -536870163< waiting for device >
Just bringing this old post back to life as I've run into the exact same problem. My N1 only boots into the multi-coloured X and there is no option to go into recovery. I previously had this issue when trying to push a CM rom onto it and solved it by going back to stock. But this time this error appears when trying to push a stock rom onto the phone:
"ERROR: could not clear input pipe; result -536870163< waiting for device >
"
Can someone help, please? The whole string looks like this:
MSM:~ m$ cd desktop
MSM:desktop m$ cd fastboot
MSM:fastboot m$ ./fastboot-mac
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
MSM:fastboot m$ ./fastboot-mac devices
HT09GP801010 fastboot
MSM:fastboot m$ ./fastboot-mac update signed-passion-img-FRG83_0923.zip -w
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not clear input pipe; result -536870163< waiting for device >

Can't boot into recovery - phone just restarts
Odd, after a few more attempts the N1 is now able to boot as normal. But I no longer have access to recovery. My Market keeps force closing and I therefore wanted to flash the market again, but every time I try to go into recovery the phone just reboots. I've tried:
- Flashing CWM 25.1.0 in RomManager and booting into recovery
- Manually booting into recovery by holding vol down and power button
- via Quickboot
I can see that CWM is on the SD card but can't seem to be able to boot into it. Any suggestions?

[Q] Fastboot?

Ive modified the android_winusb.inf to show the correct device ID 0FCE for windows 7 x64 installed it and thats gone fine.
Now trying devices gives me nothing reboot-bootloader gives me <waiting for device> cant make a decent boot.img backup to inject Root, anyone got any ideas how we can connect fastboot, the bootloader is unlocked but unconfirmed.
Until we can get a decent boot.img we cant really start the development.
fastboot.exe -i 0x0fce getvar version connects and displays fine.

are you starting your phone in bootloader mode?
power off
hold <search> + plug into usb
I was able to issue fastboot commands from there such as fastboot reboot. If your bootloader is unlocked you should be able to use any of the below commands. You can also modify the boot.img from the recovery image from the bundled software. And boot to it on sd without writing to nand.
I've been pretty busy or else I'd try it myself, I just played with it enough to unlock my bootloader myself and that's where I stopped. If you need some help let me know.
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
EDIT: if you are having issues with "fastboot devices" and you are entering bootloader correctly, you may need to restart your workstation

Yeah done all that im sure the bootloader is now unlocked it erased the blocks and reset my phone, ill boot into ubuntu and try it from there. Windows wont let me issue any commands
Sent from my R800i using XDA Premium App. the keyboard auto correct function is mental it changes all my words got to turn that off

waz000000 said:
Yeah done all that in sure the overloaded is now unlocked it erased the blocks and reset my phone, ill boot into ubuntu and try it from there. Windows wont let me issue any commands
Sent from my R800i using XDA Premium App
Click to expand...
Click to collapse
I tried downloading the "repair" image and it sees that we modified the bootloader and won't download the image and the only files on SE website is for the update software not the image which I think is kinda bullsh*t but whatever.
so... if someone that *HAS NOT* unlocked the bootloader can download and mirror the file it downloads, should 100+ mb somewhere on your computer possibly in your %temp% directory if you are on a windows based workstation

I had the same problem cant restore major over sight by sony if our software breaks any time soon....
We need the unmodified boot.img only problem is i have another play ones got to go back that one is fresh in the packet but with the bootloader locked we cant issue commands with fast boot. catch 22
Sent from my GT-P1000 using XDA Premium App

waz000000 said:
I had the same problem cant restore major over sight by sony if our software breaks any time soon....
We need the unmodified boot.img only problem is i have another play ones got to go back that one is fresh in the packet but with the bootloader locked we cant issue commands with fast boot. catch 22
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
also the /proc/mtd for the boot partition is hidden in case anyone suggests we just pull for a backup.
Another reason I won't be doing much tinkering untill someone can provide us with a recovery image (note not just /system dump)

Bootloader Lock, Android 8.0 Please help One Plus 5

Hello Ladies and Gents
so I want to upgrade to Android 8.0 Oreo but it asks be to lock the bootloader I have tried everything I was able to find all the guides and commands, when I did "fastboot ome lock" I ended up in a boot loop and so I had to unlock it again, when I do "fastboot flashing lock" nothing happens no Failed attempts or anything else only this comes up
PS C:\Users\User> fastboot flashing lock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
I am really not sure what to do I tried unrooting and doing it and also doing it while rooted because one of the guides said I need to be rooted, I tried flashing stock recovery and doing it but still nothing, can someone please help, thank you :laugh:

Follow this.
Make sure oem unlocking option is on in dev options. Then use fastboot oem lock command to lock bootloader.. this will wipe everything and start booting process.. now if it's not booting press and hold power and volume down button to go to recovery. In recovery go to advanced option and select power off. Wait 2-3 minutes and just simply power on your device. It'll boot.
This works for me everytime.
Never try to lock bootloader when device is rooted. It may brick your device.

ASB41 said:
Follow this.
Make sure oem unlocking option is on in dev options. Then use fastboot oem lock command to lock bootloader.. this will wipe everything and start booting process.. now if it's not booting press and hold power and volume down button to go to recovery. In recovery go to advanced option and select power off. Wait 2-3 minutes and just simply power on your device. It'll boot.
This works for me everytime.
Never try to lock bootloader when device is rooted. It may brick your device.
Click to expand...
Click to collapse
okay so I did what you said and in fastboot the Device State - Locked and its in red and im still in a boot loop but now It doesnt even show the One Plus logo. I did unroot and flashed stock recovery.

Th3Pr0MaQ said:
okay so I did what you said and in fastboot the Device State - Locked and its in red and im still in a boot loop but now It doesnt even show the One Plus logo. I did unroot and flashed stock recovery.
Click to expand...
Click to collapse
Did you flashed firmware properly in twrp ?
Like this :- wipe system/storage/catche/data & then format data. Flash official firmware and reboot.
Use otg adaptor to flash firmware.
You have to flash full firmware to fully unroot.

ASB41 said:
Did you flashed firmware properly in twrp ?
Like this :- wipe system/storage/catche/data & then format data. Flash official firmware and reboot.
Use otg adaptor to flash firmware.
You have to flash full firmware to fully unroot.
Click to expand...
Click to collapse
I dont quite understand, I dont have TWRP anymore so do I need to get it back then use the clear cache and data? and then flash zip file from OP website? I cant flash firmware bcs of that oem lock thing thats why I want to lock it so I can upgrade to Android 8.0

Ok let me explain.
You unlocked bootloader and rooted your device with magisk or supersu.. now you want to unroot and lock the bootloader..
For that:-
You must flash full firmware zip from OnePlus website in twrp to unroot your device.
But
You just unrooted your phone somehow and locked the bootloader without flashing firmware. Which is completely wrong. That's why your phone is not booting.
Now you need to unlock the bootloader again.
Flash twrp in fastboot.
Wipe everything including data.
And flash official firmware using usb & reboot.
And then after successfully booting you can lock bootloader again.
(Make sure you download the correct firmware)

ASB41 said:
Ok let me explain.
You unlocked bootloader and rooted your device with magisk or supersu.. now you want to unroot and lock the bootloader..
For that:-
You must flash full firmware zip from OnePlus website in twrp to unroot your device.
But
You just unrooted your phone somehow and locked the bootloader without flashing firmware. Which is completely wrong. That's why your phone is not booting.
Now you need to unlock the bootloader again.
Flash twrp in fastboot.
Wipe everything including data.
And flash official firmware using usb & reboot.
And then after successfully booting you can lock bootloader again.
(Make sure you download the correct firmware)
Click to expand...
Click to collapse
okay so I flashed twrp im unrooted I wiped the data and cache with twrp and now Im trying to flash http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_5.0.1/ android 8.0 as I cant find the one im on now 7.1.1 but im getting following error in TWRP when im trying to install zip with TWRP "Updater Process ended with ERROR 7"

I never tried directly upgrading official firmware from twrp.
I'm mean from nougat to oreo.
But if you gonna flash android oreo. You'll need oreo compatible twrp. Flash latest version of blu-spark twrp(oreo version).
Download v8.61 -
https://forum.xda-developers.com/devdb/project/?id=21949#downloads

ASB41 said:
I never tried directly upgrading official firmware from twrp.
I'm mean from nougat to oreo.
But if you gonna flash android oreo. You'll need oreo compatible twrp. Flash latest version of blu-spark twrp(oreo version).
Download v8.61 -
https://forum.xda-developers.com/devdb/project/?id=21949#downloads
Click to expand...
Click to collapse
I've done it Thank you so much for your help :laugh:

[HELP] ADB "Waiting for device"

Hi,
I was on Resurection Rom 7.1.2, but decided to go back to stock today.
I am after wiping caches, data and system from my phone, so I can only access bootloader and twrp.
I have installed mini adb on Win10, and also Clockworm UniversalAdbDriver but none of them seems to work for me. My phone is not visible in devices manager or in adb commands. I can only see "Waiting for device" , adb devices returns nothing.
I am stuck without the phone
Any advice would be most welcome.
Thanks!

Do you have the Motorola usb drivers installed on your PC?

pablo102 said:
Hi,
I was on Resurection Rom 7.1.2, but decided to go back to stock today.
I am after wiping caches, data and system from my phone, so I can only access bootloader and twrp.
I have installed mini adb on Win10, and also Clockworm UniversalAdbDriver but none of them seems to work for me. My phone is not visible in devices manager or in adb commands. I can only see "Waiting for device" , adb devices returns nothing.
I am stuck without the phone
Any advice would be most welcome.
Thanks!
Click to expand...
Click to collapse
ADB isn't available in the bootloader, you have to use fastboot. Try running "fastboot devices"while connected to your PC and in bootloader mode.
Sent from my Moto G (5) Plus using Tapatalk

riggerman0421 said:
ADB isn't available in the bootloader, you have to use fastboot. Try running "fastboot devices"while connected to your PC and in bootloader mode.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Tried that, but Moto is not seen by Windows. I had Motorola Device Manager but it did not help.
Actually, in Windows Device Manager, in hidden devices, I can see Mot Composite ADB Interface.
Can I use other's phone sd card and install from there? Do I need to mount it in twrp?

Make sure you only have one instance of ADB/Fastboot installed. If Motorola Device Manager installed the drivers correctly, [I had to use Motorola Mobile Drivers Installation 6.4.0 gui.] then tey
Code:
fastboot devices
Also be sure USB debugging is on in developers option on your phone.

I have found the problem in in cable/usb socket. It's fine for charging, but somehow the cable needs to be pushed more into the port for windows to see the device.
Enjoining Android again
Thanks for all support!

PS C:\> cd adb
PS C:\adb> fastboot devices
ZY224LGV2S fastboot
PS C:\adb> fastboot recovery twrp-3.3.1-0-potter
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>
what to do now

bambamishere said:
PS C:\> cd adb
PS C:\adb> fastboot devices
ZY224LGV2S fastboot
PS C:\adb> fastboot recovery twrp-3.3.1-0-potter
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>
what to do now
Click to expand...
Click to collapse
What are you trying to do would be my first question?

Wolfcity said:
What are you trying to do would be my first question?
Click to expand...
Click to collapse
Seems trying to flash the recovery, but using wrong the command. It must be fastboot flash recovery twrp.img

riyan65 said:
Seems trying to flash the recovery, but using wrong the command. It must be fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Seems to me like all this happens in ADB mode which has to be (as you mentioned) in fastboot mode.
So @bambamishere:
Bring the device to fastboot (not ADB) mode, type
Code:
fastboot devices
(you should receive a serial number then)
Then type
Code:
fastboot flash recovery "name of recovery.img"
where "name of recovery.img" stands for the real name like twrp.img or however it's named.
Make sure that the image is in your ADB & fastboot folder on your PC.

Help !! please my phone crash and now fastboot appears

well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please

Frost817 said:
well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please
Click to expand...
Click to collapse
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me

Frost817 said:
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me
Click to expand...
Click to collapse
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I tried the method but just send me this
[LEFT]commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]

Frost817 said:
I tried the method but just send me this
[LEFT]commands:
update reflash device from update.zip
flashall flash boot + recovery + system
flash [ ] write a file to a flash partition
erase erase a flash partition
format format a flash partition
getvar display a bootloader variable
boot [ ] download and boot kernel
flash:raw boot [ ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s specify device serial number
or path to device port
-l with "devices", lists device paths
-p specify product name
-c override kernel commandline
-i specify a custom USB vendor id
-b specify a custom kernel base address. default: 0x10000000
-n specify the nand page size. default: 2048
-S [K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]
Click to expand...
Click to collapse
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?

Frost817 said:
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs

sd_shadow said:
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result

Frost817 said:
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result
Click to expand...
Click to collapse
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs

sd_shadow said:
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
well don't use the fb_mode_set but it keeps sending me Failure
failed flashing process 1/24 flash partition gpt.bin -> phone returned Fail
bootloader logs:
cmd: getvar- max sparce size
cmd: getvar- max download size
cmd: download 0000b600
cmd: flash: partition

after seeing your post I also believe my phone moto g5 XT1686 failed not able to start, the same issue I tried everything all tools and commands. In a final conclusion Buying Motorola devices is a waste of money.
feeling dishearted...