Hi folks,
I´ve an Xiaomi Poco F1 with an unlocked bootloader. Usb debugging is enabled and no password is set. If I run
HTML:
fastboot flash recovery twrp.img
the error
HTML:
Sending 'recovery' (31000 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
appers. Any ideas why this happens?
Count_Omega said:
Hi folks,
I´ve an Xiaomi Poco F1 with an unlocked bootloader. Usb debugging is enabled and no password is set. If I run
HTML:
fastboot flash recovery twrp.img
the error
HTML:
Sending 'recovery' (31000 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
appers. Any ideas why this happens?
Click to expand...
Click to collapse
Under linux, I get a success
HTML:
target reported max download size of 536870912 bytes
sending 'recovery' (6 KB)...
OKAY [ 0.010s]
writing 'recovery'...
OKAY [ 0.003s]
finished. total time: 0.013s
and
HTML:
fastboot boot twrp.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.008s]
booting...
OKAY [ 0.051s]
finished. total time: 0.059s
runs along. But it doesn´t get through to the twrp screen.
some weeks ago i read on forum that miui10.0.3 or 4 has some fastboot errors,
for example if you have flashed miui10.0.3 or 10.0.4 and then try to write recovery it will give error in fastboot
i would suggest flash miui10.0.1 or earlier via miuiflasher fastboot rom and then try!
Related
Hello everyone. I have some issues with Fastboot. whenever I try to flash recovery.img i get this error. my device is Cherry Mobile Touch xl 2 with android 6.0 and mt6580.
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash flash recovery.img
target reported max download size of 134217728 bytes
sending 'flash' (10678 KB)...
OKAY [ 0.266s]
writing 'flash'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.281s
When I try to just boot into custom recovery, everything goes well except that the phone just reboots. it does not boot into custom recovery. I heard it from somewhere that fastboot boot recovery.img command did not work anymore. Is this true?
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.281s]
booting...
OKAY [ 0.063s]
finished. total time: 0.344s
Thank you for your help.
After several searches on the net, unlock the bootloader and to do
the ROOT this phone Huawei y 6 2018, but now they are stranded
in the installation of the Twrp recovery.
Fastboot gives me this error:
Code:
PS D:\Cellulare\adb-and-fastboot> fastboot flash recovery twrp-3.2.1-1.img
target reported max download size of 535822336 bytes
sending 'recovery' (14638 KB)...
OKAY [ 0.453s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.469s
PS D:\Cellulare\adb-and-fastboot>
How do I solve?
same probleme
Hello,
Im trying to flash TWRP on my LG G5.
The installation is successful but i cant boot into it.
I already unlocked my Bootloader.
It keeps telling me this:
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (19132 KB)...
OKAY [ 0.443s]
writing 'recovery'...
OKAY [ 0.203s]
finished. total time: 0.646s
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.418s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.449s
When i try to get into recovery with the button method i get the stock recovery.
Pls help...
That means that the bootloader is unlocked right?
PS C:\adb> fastboot getvar unlocked
unlocked: yes
finished. total time: 0.000s
Phone: Oneplus 3T
Recovery: TWRP 3.3.0-1
OS: LOS 16.0
Flashed a bad emmc_appsboot.mbn and now my phone loops as soon as it gets to the 1+ logo.
Cannot get into recovery.
Can get into fastboot.
Bootloader has been unlocked for years. After getting the "not allowed" error, I did a "fastboot oem unlock" again, successfully.
Code:
$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
$ fastboot flashing unlock
(bootloader) Device already : unlocked!
$ fastboot flashing unlock_critical
(bootloader) Device already : unlocked!
$ fastboot flash recovery twrp-3.3.0-1-oneplus3.img
target reported max download size of 440401920 bytes
erasing 'recovery'...
OKAY [ 0.010s]
sending 'recovery' (27405 KB)...
OKAY [ 0.721s]
writing 'recovery'...
OKAY [ 0.199s]
finished. total time: 0.930s
$ fastboot flash aboot firmware-update/emmc_appsboot.mbn
target reported max download size of 440401920 bytes
sending 'aboot' (1584 KB)...
OKAY [ 0.062s]
writing 'aboot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.082s
$ fastboot flash devcfg firmware-update/devcfg.mbn
target reported max download size of 440401920 bytes
sending 'devcfg' (50 KB)...
OKAY [ 0.038s]
writing 'devcfg'...
FAILED (remote: Partition flashing is not allowed)
Every partition other than recovery gives the "not allowed" error. And flashing the recovery doesn't help.
I'm stumped. I haven't been able to find any other reports online of the same problem, only people with locked bootloaders getting that error.
I know about EDL and I've been working on that angle, but getting fastboot flashing working would be easier.
Ideas? Suggestions?
Hello xda.
I am having a big problem with trying to flash a recovery image for my LG Aristo 2.
Whenever I execute the command "fastboot flash recovery recovery.img", it comes up with this.
Code:
target reported max download size of 262144000 bytes sending 'recovery' (16954 KB)... OKAY [ 0.539s] writing 'recovery'... FAILED (remote: unknown command) finished. total time: 0.543s
I tried "fastboot boot recovery.img" and it gave me this.
Code:
downloading 'boot.img'... OKAY [ 0.538s] booting... FAILED (remote: unknown command) finished. total time: 0.542s
Why does it say this? Please help. I just want to root my phone.
Sidenote: This is my first time actually being able to root.