Failed command write failed no error ошибка fastboot

Hi everyone, please help to solve the problem
Now my MIUI is 12.5 China Stable Rom, Now all google can’t use already, so i need come to EU Rom.
The Point is while using powershell/ cmd to do Fastboot Flash recovery twrp.img its show

target didn’t report max-download-size
sending ‘recovery’ (40948 KB)…
FAILED (command write failed (No error))
finished. total time: 0.009s

Can point out which one got problem, Thank You very much

Screensnip.png

4.4 KB

· Views: 167

katerpanne

Hi everyone, please help to solve the problem
Now my MIUI is 12.5 China Stable Rom, Now all google can’t use already, so i need come to EU Rom.
The Point is while using powershell/ cmd to do Fastboot Flash recovery twrp.img its show

target didn’t report max-download-size
sending ‘recovery’ (40948 KB)…
FAILED (command write failed (No error))
finished. total time: 0.009s

Can point out which one got problem, Thank You very much

Please can you list the files in the directory «c:… ADB and Fastboot» is there a file named «twrp.img»

Did you try to use another USB Port -> 2.0 or a HUB ?

Can you boot into TWRP: fastboot boot twrp.img ?

Please can you list the files in the directory «c:… ADB and Fastboot» is there a file named «twrp.img»

Did you try to use another USB Port -> 2.0 or a HUB ?

Can you boot into TWRP: fastboot boot twrp.img ?

Yup, I previous using USB 3.0, now i try 2.0, its work. Thank You

Источник

На чтение 3 мин. Просмотров 26 Опубликовано 15.12.2019

xiaomi MI5
C:adb>fastboot oem edl
.
FAILED (remote: Need to unlock the device to use this command)
finished. total time: 0.003s
В чем проблема подскажите?
Все делал по инструкции.
Еще если нужно инфы:

C:adb>fastboot oem device-info
.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.060s]
finished. total time: 0.061
перепрошивка не помогает, всё остаётся на логотипе mi фастбут и рекавери работают, но при любой команде, ничего не происходит, oem unlock тоже не помогает.

C:adb>fastboot oem device-info
.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false

Надо первести смартфон в режим EDL, потом через USB разблокируем кирпич с помощью старой версии Mi Unlock 2.2.406.5 это реально помог мне даже сам удивился.

потом у Вас уже будет
C:adb>fastboot oem device-info
.
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked:true
(bootloader) Charger screen enabled: false

А потом с официального сайта скачиваете прошивку и прошиваете

Если вы пытаетесь установить прошивку на ваш Andro >

Данный материал, подразумевает, что вы уже знаете, что такое Fastboot и как им пользоваться. Статья в большем случае рассчитана для устройств Nexus, но возможно подойдет и другим устройствам которые имеют поддержку Fastboot.

Ошибки при прошивки в Fastboot

Проблема может возникнуть из-за отсутствия драйверов, а также с какими либо проблемами с USB кабелями и портами, подробней читайте в статье waiting for devices.

Проблема связана с поврежденным или дешевым USB кабелем, либо же подключение выполнено через ХАБ.

Прошить каждую часть прошивки по отдельности, а не за один раз c помощью архива.

Не обращать свое внимание, так как это не является ошибкой.

Вначале удалить, перезагрузить компьютер и переустановить драйвера Nexus.

Для того чтобы устранить данную ошибку необходимо установить кастомное Recovery, после чего перейти в него и выполнить команду:

После чего перевести Android в режим Bootloader/Fastboot и прошить образ cache:

Вот и все! Оставайтесь с сайтом Android +1! Дальше будет интересней!

darksniper87

Members

Did anyone had any luck flashing the TWRP using Windows 10?

I have an unlocked Xiaomi Mi 8 CN phone.
I have installed the ADB drivers from Xiaomi and when I execute `fastboot devices` it shows my connected device.

But when I execute `fastboot flash recovery recovery-TWRP-3.2.3-0908-XIAOMI8-CN-wzsx150.img` but it fails with error
`FAILED (Write to device failed (Invalid argument))`
and the phone just goes black with a text press any key to shutdown.

I’ve been struggling all day trying various things (older TWRP versions, using USB 2.0 ports, using different fastboot) but no luck until.
My last attempt is to try using Windows 7 (need to download the iso) but I’d like to ask the forum if there is anything else I can try.

Источник

I’m having trouble flashing my smartphone via fastboot.

The smartphone in fastboot-mode is recognized:

sudo fastboot devices
BH905FBU9E  fastboot

but flashing results in no reaction until the usb cable is pulled :-(.

sudo fastboot flash recovery twrp-3.5.0-0-20210117-lilac.img

with no output until after pulling the cable:

Sending 'recovery' (33824 KB)                      FAILED (Write to device failed (No such device))
fastboot: error: Command failed

adb on the other hand is working fine!

What might be going wrong? Ubuntu 20.04 on another machine works fine!

Thanks in advance for ideas,
pheidrias

asked Oct 26, 2021 at 15:39

Could be your driver as an ADB device. Download and install the latest USB drivers with SDK manager on your Ubuntu machine.

Have you done this process yet?

First sudo apt-get update

Then sudo apt-get upgrade

After sudo apt-get dist-upgrade

After sudo apt-get install android-tools-fastboot

fastboot devices
fastboot reboot

Have you also turned on USB debugging? What processor of the computer that has Ubuntu vs the computer that it works on? Is it an AMD processor? Try a different port or a different cable on the machine too.

answered Oct 26, 2021 at 18:31

You say that it works on 20.04 but not 21.10 and all packages are up to date. It looks like you have different versions of fastboot with apt delivering version 1:8.1.0+r23-5ubuntu2 for 20.04 and version 1:10.0.0+r36-7 for 21.10. I would recommend downloading the SDK Platform-Tools directly, where fastboot is currently version 31.0.3-7562133. https://developer.android.com/studio/releases/platform-tools

I’m not sure how the binaries in the repos are versioned, but I have found that, for example, fastboot 1:8.1.0+r23-5ubuntu2 does not support dynamic partitions (i.e. fastboot delete-logical-partition product) while the the version from platform-tools does.

A note that may help others running into a similar problem: to flash recovery, you must use fastboot from the bootloader and not from fastbootd. Generally, for a powered up device, adb reboot fastboot will get you to fastbootd and then fastboot reboot bootloader will get you to the bootloader from where you can flash the recovery partition. More info: https://source.android.com/devices/bootloader/fastbootd

answered Dec 11, 2021 at 19:49

In my case on Ubuntu 20.04, it was a USB 3.0 port problem. It was detect device with fastboot devices but other commands does not has a response. My laptop hasn’t got a USB 2.0 port. Then I disabled internal USB 3.0 support in my BIOS and now fastboot is working normally. But all USB 3.0 support is stopped. It seems USB 2.0 hub is the better option. I will set back the BIOS setting later.

answered Oct 16, 2022 at 4:53

Almas DusalAlmas Dusal

7896 silver badges10 bronze badges

Источник

I’m trying to install TWRP in a Xiaomi Redmi note 5 but I can.
I have been trying a lot of stuff I have found on the internet but I don’t what to do now.

I have my device unlocked and I have USB debugging activated.

I got the following message:

C:Program Files (x86)Minimal ADB and Fastboot>fastboot devices

4357e24 fastboot

C:Program Files (x86)Minimal ADB and Fastboot>fastboot flash recovery xiaomi.img

target didn't report max-download-size

sending 'recovery' (42452 KB)...

FAILED (command write failed (No error))

finished. total time: 0.016s

The xiaomi.img is the name of my image of TWRP.