Hello, I have been trying to successfully flash this phone since i purchased it a few months ago now, and I have been unsuccessful in being capable of doing so... Does anybody know what this means and how I may resolve it?
This is the output...
Code:
[[email protected] Recoveries]$ fastboot boot boot.img
Sending 'boot.img' (8498 KB) OKAY [ 0.430s]
Booting (bootloader) Command is not support
FAILED (remote: '')
fastboot: error: Command failed
Also sideload on trying to use adb also says that it is unsupported or something. Is it possible that this phone is impossible to do any such type of thing with such as flashing its ROM?
Thanks...
It is a Motorola Edge 20 Fusion...
And this is what happens when I actually try sideload...
Code:
[[email protected] rooting]$ adb sideload UPDATE-SuperSU-v2-82-20170528234214.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Thanks...
1. You can't use Fastboot to boot into boot.img, but you can flash the boot.img:
Code:
fastboot flash boot boot.img
2. If ADB returns connection closed then try to force ADB to run in USB mode:
Code:
adb usb
.
Related
Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.
Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"
Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .
No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s
ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.
Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…
I'm on Linux Mint 18.3 and my G620S-L01 phone is on Android 4.4.4
I have downloaded minimal adb and fastboot tool.
First question, when issueing "adb devices" and "fastboot devices" command, shouldn't I get the same output? ( which is from what I understand the device serial number ). This is what I get:
Code:
./adb devices
List of devices attached
84dbac441b79 device
./adb reboot-bootloader
./fastboot devices
no permissions (user in plugdev group; are your udev rules wrong?); see [developer.android.com/tools/device.html] fastboot
sudo ./fastboot devices
3a226eb fastboot
Then when I issue any oem commands I tried, I always get "FAILED (remote: 'unknown command')" like for example:
Code:
sudo ./fastboot oem device-info
FAILED (remote: 'Invalid command')
fastboot: error: Command failed
I have read in some other thread, that to make oem commands working "OEM unlock" needs to be set up in Developer options. But from what I understand, this option is for >= Android 5.something. How to make those commands working on 4.4.4 version?
Edit:
I have then downloaded and installed full-blown Android studio. But the result is the same.
Hey, I have an alcatel 3 and I wanna see how I can root it. I'm trying to root it using magisk but fastboot keeps returning the error unknown command all the time.
when I do
fastboot flash ...
it sends the file but then writing produces an error.
I know that I can root it and that I've done it before using magisk. but now it doesn't work. btw i don't think i fully unrooted my device so that may be the issue.
Fastboot deals with phone's bootloader where it doesn't matter whether phone's Android got rooted or not.
If you get shown
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
or
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
means the bootloader wasn't unlocked properly.
Try this command sequence
Code:
fastboot devices
fastboot flashing unlock
fastboot flashing unlock_critical
What if
fastboot flashing unlock.
Returns command not found
If "command not found" is returned by Fastboot when trying to unlock bootloader then unlocking phone's bootloader is denied.
what if i have to run sudo to use fastboot could that be the problem
Fastboot deals with Android device's bootloader: So it's irrelevant whether Android is rooted or not.
Take note that Fastboot isn't Fastboot hence not all Fastboot commands do necessarily work as expected: it depends on how OEM implements Fastboot.
having the same problem with my qlink tablet but when using command fastboot flashing unlock
it returned fastboot oem operation fail: unknown cmd' : error: command failed This is my first time rooting anything help please?
hellp me ty pls!
Have you turned on "allow OEM to be unlocked" in developers option
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
i also try
fastboot oem unlock
it show
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??
chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Rename the patched boot.img to "boot.img", then place the patched .img in your fastboot folder on PC then type:
fastboot flash boot boot.img
When you place the file in your fastboot folder, you don't need to include the path to the file in the command, it automatically looks for the file in the fastboot folder by default when you do not enter a path. Renaming the file to "boot.img" isn't necessarily required, but, it does simplify things for fastboot and makes the command easier to remember and type.
The same applies if you want to flash a system.img, recovery.img, etc.. Just change the name of the file to "system.img" or "recovery.img" and place it/them in your fastboot folder and it simplifies your commands to:
fastboot flash system system.img
And
fastboot flash recovery recovery.img
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com
now i got same message
D:\platform-tools>fastboot flash boot boot.img
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Droidriven said:
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com
Click to expand...
Click to collapse
im already try this verify cmd location, install fastboot driver & boot fastboot mode nothing change.
Code:
D:\platform-tools>fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??
chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock
xXx yYy said:
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock
Click to expand...
Click to collapse
when i try
D:\platform-tools>fastboot flashing unlock
it show
Code:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
i use https://developer.android.com/studio/releases/platform-tools
what should i do ??
The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.
xXx yYy said:
The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.
Click to expand...
Click to collapse
i use mtp driver
update Portable Devices to MTP USB Device
but when i enter fastboot mode
it become Android Device Android Bootloader Interface.
where is extracted the driver package folder ?? https://www.xda-developers.com/download-android-usb-drivers/
I'm having simular issue with my specter 8 tablet. I unlock the bootloader and give me the normal prompt. I go back do everything else and will execute reboot devices ect. However won't flash patch_boot.img brings up message
FAILED (remote: 'Download is not allowed on locked devices').
I need the boot.img for the EU-Version. Can someone please help me? Thx in forward.
Here are both magisk patched and stock boot.img files
Using latest magisk 25.1 stable
Stock
Magisk Patched
Thank you. I've now read rooting is not possible because Mediatek. Is it true please? Will not break it.
I'm rooted on my Nord2T. Whoever said that does not know what they are talking about.
The original Nord 2 was also mediatek and has a few custom ROMs and everything
I'm not able to boot correct in bootloader. There is written at the display extreme small "Fastboot Mode". If I set command "fastboot oem unlock" there is no reaction and nothing written. Changing with up/down is nothing doing.
Pushing Vol- and Powerbutton ends in recovery. There it is only possible to choose language and then wipe, reboot and power off.
My firmware is: CPH2399_11_A.09
Wrong code not
Code:
fastboot oem unlock
The correct command is
Code:
fastboot flashing unlock
Sorry, can not unlock the bootloader
Both commands failed
PS C:\adb2> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb2> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\adb2>
Try using a different ADB and fastboot. I use official platform tools from here
Also what comes up when you type
Code:
fastboot devices
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
I had the same problem while opening Bootloader...Tried everything - Windows 10
I did the same on Windows 7 and immidiately bootloader open.
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
Did you enable developer options and select Enable OEM unlock first?
garylawwd said:
I'm rooted on my Nord2T. Whoever said that does not know what they are talking about.
The original Nord 2 was also mediatek and has a few custom ROMs and everything
Click to expand...
Click to collapse
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
cioce said:
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
Click to expand...
Click to collapse
It will if you flash kdragon safetynet fix in magisk
cioce said:
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
Click to expand...
Click to collapse
Don't rush and don't do it like me. Here boot images are for 09. So upgrade first.
Safety net passes with magisk module
Root easily hidden with lsposed and shamiko module.
Riski3Run said:
Did you enable developer options and select Enable OEM unlock first?
Click to expand...
Click to collapse
Yes
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
u should not be in fastbootd mode in adb type adb reboot bootloader
then type
fastboot flashing unlock
this should unlock your bootloader