I was trying to do some fastboot commands on my Galaxy devices (Galaxy S4, 9515, 4Tab4). I started with fastboot devices and I am getting nothing (after adb reboot bootloader). Is there any problem with fastboot on Samsung devices?

I have tried to access the voice command on the Talkback menu. I have tried to use adb/fastboot. All o no avail Outlast 5g

I am trying to install latest Lineageos for mata on Essential ph-1. It is stuck at fastboot flash boot boot.img with the warning about avb, boot partition size of 0. Boot image size: 33673216 and fastboot getvar partition-size:boot returns partition-size:boot: 0201d000. The boot image is larger than the partition. The boot image (33673216 bytes) is larger than the reported boot partition size (33671168 bytes, which appears as '0' in the fastboot warning due to an error). How do I fix this and get lineage OS installed on Essential ph-1?

As described in [this answer by @irfan-latif](https://android.stackexchange.com/a/203913/18559) , I am trying to boot (without flashing) my Google Pixel 3a into TWRP via the following command: fastboot boot twrp-3.5.2_9-0-sargo.img This failed with the following messages:

Sending 'boot.img' (65536 KB)                      OKAY [  2.028s]
Booting                                            FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed

The only things I found on this topic are: * [A thread on Reddit](https://www.reddit.com/r/Pixel3a/comments/ga7l5h/twrp_not_booting_in_android_p/) which wasn't really solved as they moved from booting to flashing which eventually worked for them, but I'm interested in booting only at this point. * [A thread on XDA Dev](https://forum.xda-developers.com/t/attempted-to-boot-twrp-error-verifying-the-received-boot-img-invalid-parameter.4019469/) which basically ended with ["TWRP for Pixel 3/3XL on Adroid 10 does not work and will not until they release a compatible version"](https://forum.xda-developers.com/t/attempted-to-boot-twrp-error-verifying-the-received-boot-img-invalid-parameter.4019469/post-81198795) . Note also that this may not apply to me as I have Android 11 (RQ3A.210605.005 to be precise) and a newer TWRP version. * [A Github issue](https://github.com/TeamWin/android_device_google_crosshatch/issues/5) from 4 Sep 2020, closed with the message "android 11 is not supported yet." (though this is for a slightly different device). What caused the error, can it be resolved, and if so, how? ## P.S. Further details:

$ adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
$ fastboot --version
fastboot version 31.0.2-7242960

* I have unlocked the bootloader. * I also tried booting the LineageOS recovery which appears to work, but continues starting Android normally instead of TWRP:

$ fastboot -v boot lineage-18.1-20210608-recovery-sargo.img
Sending 'boot.img' (65536 KB)                      OKAY [  2.004s]
Booting                                            OKAY [  7.085s]
Finished. Total time: 9.156s

I have OnePlus 3 (A3003). I installed a custom ROM. Since then, I can't get to recovery mode. If I try booting into it, my phone gets stuck on the OnePlus logo. I tried flashing it with fastboot,

C:\...\Android\android-sdk\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 442499072 bytes
sending 'recovery' (18964 KB)...
OKAY [  0.580s]
writing 'recovery'...
OKAY [  0.144s]
finished. total time: 0.726s

And also I tried flashing it with the TWRP app, it gave me an error telling me that I have already installed it. What is the problem?

i'm trying to flash gsi firmware to my tablet. - enabled OEM unlock - enabled USB debug - device is visible in fastboot devices

% fastboot devices

T812128GB25105680652     fastboot

% fastboot flashing unlock

ERROR: could not clear input pipe; result e00002d6, ignoring...
ERROR: could not clear output pipe; result e00002d6, ignoring....
ERROR: usb_read failed with status e00002ed
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed

- fastboot version 36.0.0-13206524 (latest) - macbook air m1 - macOs 15.5 (24F74) (latest) Anyone knows what's that and how to fix this?

I am trying to root my Vivo V11 with Android 10. The bootloader is unlocked. It says so in the dev settings, and I have to go through the warning prompt every time I reboot my device. When I run the fastboot command to flash the patched_boot.img file, it returns:

C:\Program Files\Minimal ADB and Fastboot>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.002s

C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot patched_boot.img
target reported max download size of 134217728 bytes
sending 'boot' (38579 KB)...
OKAY [  1.269s]
writing 'boot'...
FAILED (remote: Verify state locked)
finished. total time: 1.276s

Things I've tried to troubleshoot: Running cmd as Administrator (im using win10) Confirmed OEM unlocking is turned on in the dev settings (it is, it says "bootloader is already unlocked" Confirmed USB debugging is on Disabled "Verify apps over USB" and "Verify bytecode of debuggable apps" in the dev settings. Confirmed file transfer is enabled from my PC and my Phone (it is, I can transfer files back and forth between them) Tried a different USB cable [EDIT]

PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\adb devices
List of devices attached
ZDIBLVIRY5DIJBEI        device

PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\adb reboot-bootloader
PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\fastboot devices
ZDIBLVIRY5DIJBEI        fastboot
PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\fastboot flash boot patched_boot.img
Sending 'boot' (38579 KB)                          OKAY [  1.272s]
Writing 'boot'                                     FAILED (remote: 'Verify state locked')
fastboot: error: Command failed
PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB)                            OKAY [  0.009s]
Writing 'vbmeta'                                   FAILED (remote: 'Verify state locked')
fastboot: error: Command failed
PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB)                            OKAY [  0.010s]
Writing 'vbmeta'                                   FAILED (remote: 'Verify state locked')
fastboot: error: Command failed
PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools> .\fastboot --disable-verification flash vbmeta vbmeta.i
mg
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB)                            OKAY [  0.009s]
Writing 'vbmeta'                                   FAILED (remote: 'Verify state locked')
fastboot: error: Command failed
PS C:\Users\Himanshus\Downloads\platform-tools_r30.0.5-windows\platform-tools>

My Alcatel Android decided not to boot. It starts and says "Alcatel" then just flashes "enjoy now" about 60 times until Android Recovery. TCL/5003D_EEA/Curie 8.1.0/0PM2.171019.012/5003D_ALGB_V2.3 If I click "try again" I get Android Error and it then starts the reboot process again. I can access Android Recovery by removing and reinserting the battery, holding down Power Button, both Volume Up and Volume Down all together, once it says "Alcatel" releasing all of them, it then enters Android Recovery. I have tried "reboot now, I have tried Wipe Cache partition". What is my next move please? Are the recovery logs useful for anyone to help me?

So I was going to root this (previsouly healthy) BQ A4.5. Unlocked the bootloader and flashed [TWRP from here](https://twrp.me/bq/bqaquarisa45.html) :

$ fastboot oem unlock
(bootloader) Start unlock flow

OKAY [ 32.954s]
Finished. Total time: 32.960s
$ fastboot flash recovery downloads/twrp-3.3.1-0-dendeone.img
target reported max download size of 134217728 bytes
Sending 'recovery' (11342 KB)...
OKAY [  0.378s]
Writing 'recovery'...
OKAY [  0.335s]
Finished. Total time: 0.727s
$ fastboot reboot bootloader
rebooting into bootloader
OKAY [  0.003s]
Finished. Total time: 0.058s
$ fastboot reboot
Rebooting...

Finished. Total time: 0.058s

The first reboot to bootloader didn't do anything. Now it's on a bootloop which states:

Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

Pressing _Volume Up + PowerOn_ used to work for recovery (that's how I got into fastboot mode). Now, pressing _Volume Up/Down/Up+Down + PowerOn_ doesn't do anything, fastboot stands indefinitely `, and adb always responds with error: no devices/emulators found` regardless of when it's run. If I press _Volume Up+Down_ it turns off. Plugging in USB it turns on. Nothing else seems to respond. dmesg states:

[32774.364937] usb 2-7: new high-speed USB device number 59 using xhci_hcd
[32774.514434] cdc_acm 2-7:1.0: Zero length descriptor references
[32774.514450] cdc_acm: probe of 2-7:1.0 failed with error -22
[32774.554519] cdc_acm 2-7:1.1: ttyACM0: USB ACM device
[32777.142205] usb 2-7: USB disconnect, device number 59

The disconnect happens before the bq logo appears. Trash bin time?

I was trying to unlock the bootloader of an old Redmi Note 4x, Downloaded fastboot and adb. I first enabled developer option and turned on USB debugging. I tried finding OEM unlock option which was not present on the phone. After few hours of searching about it online, I finally concluded it is not available for the phone. So I went on and fired up my terminal \[in administrator mode\];

$ adb devices
> List of devices attached
> 8H4DZP69S44DQOEM        device

then I rebooted my device in bootloader (fastboot)

$ adb reboot bootloader

My Phone restarted in bootloader, then I went back to my terminal and checked if the fastboot was working or not;

$ fastboot devices
> 8H4DZP69S44DQOEM        fastboot

After confirming that the fastboot is running, I tried unlocking OEM;

$ fastboot oem unlock
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

which.. well... failed and I don't know why. I tried searching this very error code online but failed to find anything close to it. My other attempts like unlocking flashing failed in similar fashion;

$ fastboot flashing unlock
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

$ fastboot flashing unlock_critical
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

Nothing seems to be working, Please help!

A friend gave me an Alcatel phone to fix it, the phone updated automatically and when it starts up, this happens: > dm-verity corruption > > Your device is corrupt. > It can't be trusted and may not work properly. > Press power button to continue. > Or, device will power of in 5s 5 seconds after the message is displayed, it restarts and displays the same message. I tried putting it into fastboot to do what they tell me to do with this error, but the phone reboots by disconnecting from the PC. Even to put it in fastboot, I have to use the volume up arrow and the power button, I choose the fastboot option, and when I choose fastboot, the phone does not show a terminal like they do in the tutorial, it seems as if it was turned off. I connect it to the PC and the same thing happens, it restarts every 5 seconds and adb does not recognize it. I do not know what to do.

I want to unlock the bootloader of my Moto X4 running Android 9 and get the unlock code. My computer is a Linux Mint Ideapad 3 (so should have USB-3 ports (referring to this post )). My device gets displayed when I type fastboot devices However, none of the 3 USB ports give me a response when I type fastboot oem get_unlock_data nor does the command finish. The bootloader logs say on the phone cmd: oem get_unlock_data. "**Allow bootloader get unlocked**" is enabled in developer options, and so is USB debugging. I need the unlock data to request on the Motorola page the unlock key.

Currently when a new update is out, 1. I download it through the Settings → Update Dialog. 2. Then, after it's downloaded, I Export it 3. Then I patch it using the Magisk app. It takes the zip, patches it, and produces an .img. 4. Then I adb pull the image down. 5. Then I boot into fastboot 6. Then I fastboot flash boot .img Is there a way to automate steps 2-6 so that it's included with just a regular install and doesn't require human interaction, fastboot, and another PC.

My device has terrible adb support. Can I install a ROM without using adb?

I am trying to boot twrp.img on my LG G6 ThinQ using adb and fastboot. I reboot into fastboot mode and do:

boot ../users/******/downloads/twrp.img

and then it says

downloading 'boot.img'...
OKAY [  0.500s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.524s

My phone doesn't have root or bootloader unlocked and platform-tools is version r26 Note:

-c "lge.kcal=0|0|0|x" boot ../users/******/downloads/twrp.img

also doesn't work

I'm trying to solve a problem that is affecting a **Moto G 2014 XT1069** device. What has happened is that the device did shutdown, then when trying to power it up again, it stayed stuck on the Motorola logo for some time. Another person trying to help, said that it was needed to format the cellphone and rebooted into recovery mode. The point is that when trying to factory reset an error appeared. This person then said that the device was bricked and needed to do something to correct it. Then using fastboot through a computer, I don't know what she did but the situation got somehow worse. The first thing is that she unlocked the bootloader. But after all the procedure what happens is that when the device powered up, it just got stuck in a screen with a message **WARNING BOOTLOADER UNLOCKED** and it *doesn't progress any further*. On that same screen it is possible, by pressing **PWR** + **VOL DWN** to access the bootloader, but even if we select "Normal Powerup" or "Recovery", the device just gets back to the screen **WARNING BOOTLOADER UNLOCKED** and nothing more happens. Furthermore, it seems that the battery became somehow "mad". After a *quite long* time interval charging, the device got to 29% of battery and after just a few minutes trying to correct all this mess, the battery got to 6%. I don't know what they did and how all of this happened. How can I fix this mess? How can I make the cellphone boot and make everything right again? If possible I want to avoid flashing the factory image for the reason that I don't have access to the image from the official source and I feel quite uneasy to get from one untrusted source, since it might compromise confidential data. What can I do to solve this? I believe there has to be a way to correct all of this.

I tried to flash the most recent android pie update to my pixel 2 only for it to fail writing partitions even though I followed a recent guide to my best ability. Now, the phone is stuck in the bootloader with no way to boot into android or any way to access the recovery options (throws an error and takes me back to the bootloader info page) Neither fastboot nor ADB can recognize the phone, I think this is because the USB debugging must have turned off somehow even though I turned it on, as before I WAS able to access it through fastboot. But now I can not, plugging it into the Windows machine, windows doesn't see any change in Device Manager when the phone is plugged in and out. I reached out to a google supports rep and they told me since there is no way to access the recovery options, the phone needs to go through warranty, but is this really the only way? Is there some driver I am missing?

I updated everything, bcs its samsung I found this driver " SAMSUNG_USB_Driver_v1.7.56.0 " but thats for widnows. I tried to search it from recovery mode or bootloader, but nothing. Im using OS: Linux Mint 20.3 x86_64 Lsusb could identify it, Adb same, Fastboot and sudo fastboot nothing Any suggestions? By term bootloader I meant this mode, it can be case, that it has name Download mode as Andrew wrote Another mode is recovery, but I think that recovery mode wouldnt help

I am trying to root my Xiaomi MI A2 phone with **Android 10**. I followed the steps to install **TWRP** which was successfully done. After that, I tried installing **Magisk** to get root access. After following the installation guide and performing patching images, I am now stuck in a fastboot/TWRP loop where I can switch between fastboot and recovery using the volume up and power button only. My PC cannot detect the device in either mode, although it had no issue detecting it before. I also alternated between A and B partitions. How do I get out of this loop so I can do a fresh installation of ROM?

I am trying to install Lineage OS 16.0 on my Moto 4X. I unlocked the OEM bootloader. But when I enter the command 'fastboot reboot bootloader' it shows ''. There it stays until I break. The next day it suddenly worked and I booted TWRP, install Lineage OS, G-Apps 9.0 micro and started the phone following the instructions at https://wiki.lineageos.org/devices/payton/install . Lineage seem to work fine, but the G-Apps are nowhere to be found. I remember during the installation there was an error like 'can't access date/media., such a Directory does not exist' but it worked, or I thought that it did. I wanted to reinstall it all. Now I have the same problem again. C:\adb>adb devices List of devices attached ZY224KGGGC device C:\adb>fastboot reboot bootloader USB debugging is enabled, the drivers on the PC are the newest from the Motorola website. I used every USB port on my PC. I tried my PC and two other laptops, all Windows 10. Also I tried CMD, Powershell, and GIT-Bash for the commands. It’s always the same response. So I don't know what to do right now. Does someone know where that problem came from?