Hi,
My LG5 850 is rooted and wiped, after testing another custom ROM. However, this time I can't reboot into recovery using the Vol-dwn/Power key-combination. Always ending-up in fastboot
Is there a command to take it from there?
Thanks a lot!
Bash:
fastboot reboot recovery
Should generally do the trick.
Unfortunately not:
LG5# fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Also tried:
LG5# fastboot flash recovery twrp-3.4.0-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (21124 KB)...
OKAY [ 0.681s]
writing 'recovery'...
OKAY [ 0.226s]
finished. total time: 0.907s
LG5# fastboot reboot twrp-3.4.0-0-h850.img
fastboot: usage: unknown reboot target twrp-3.4.0-0-h850.img
Related
Hello guys,
I've flashed TWRP for Nexus 9 2.8.6:
Code:
#adb devices
List of devices attached
HT4C3WV01363 device
#adb reboot bootloader
#fastboot devices
HT4C3WV01363 fastboot
#fastboot flash recovery twrp-2.8.6.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13208 KB)...
OKAY [ 0.744s]
writing 'recovery'...
(bootloader) Device State : Unlocked
OKAY [ 0.867s]
finished. total time: 1.612s
There's no way to continue into recovery without rebooting:
Code:
#fastboot reboot
rebooting...
finished. total time: 0.099s
#adb reboot recovery
... leads to a fallen Android! (see attached screenshot)
Any suggestion?
Fastboot flash TWRP recovery again.
After doing above, don't touch your PC again. Pick up your device and use volume button to navigate to hboot, then navigate to recovery and use power button to select.
Done.
Yes, thanks!
actionmystique said:
Yes, thanks!
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that...
Now that we have our own forum I figure I might as well put this here (taken from guide here).
1. Unlock the boot loader with the instructions / app from Asus
2. Download TWRP. Specifically twrp-3.1.0-0-Z01H-20170408.img ** [edit: also rename to twrp.img once downloaded]
4. Reboot to fastboot by rebooting the phone, and pressing the down arrow during the unlock screen.
5. Flash the recovery image `fastboot flash recovery twrp.img`
6. I had to power cycle the phone completely to get TWRP running.
Original post:
https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
C:\adb>fastboot.exe flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (33422 KB)...
OKAY [ 0.737s]
writing 'recovery'...
OKAY [ 0.454s]
finished. total time: 1.197s
It's not working, I have no idea why.
hi, have some difficulties to flash twrp.img
i try fastboot flash recovery recovery.img but i get this error
Code:
B:\Download\Compressed\platform-tools-latest-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (52396 KB)...
OKAY [ 5.923s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 5.947s
phone is unlock debug is enable and signature app verification is disable
P.S thx in advance
Try this
cappone said:
hi, have some difficulties to flash twrp.img
i try fastboot flash recovery recovery.img but i get this error
Code:
B:\Download\Compressed\platform-tools-latest-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (52396 KB)...
OKAY [ 5.923s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 5.947s
phone is unlock debug is enable and signature app verification is disable
P.S thx in advance
Click to expand...
Click to collapse
Hi there,
was wondering did you put the recovery file into the installation folder of ADB
yes, thats not the the problem, i manage to root my phone but cant to write TWRP, i get the same msg tried many toolkits and results is the same...
Since Oreo: Partition names have changed and "recovery" changed to "recovery_ramdisk".
Try:
fastboot flash recovery_ramdisk twrp.img
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!
I tried to install TWRP
fastboot flash a twrp.img
Sending 'a' (39892 KB) OKAY [ 0.929s]
Writing 'a' FAILED (remote: '(a_a) No such partition')
fastboot: error: Command failed
astboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 1.057s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 1.063s
The phone is stuck in fastboot.
I tried this:
c:\TWRP>fastboot flash boot_b twrp.img
target reported max download size of 804261888 bytes
sending 'boot_b' (39892 KB)...
OKAY [ 0.931s]
writing 'boot_b'...
OKAY [ 0.215s]
finished. total time: 1.148s
fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
I press power Volume Up but the phone boot in Fastboot
you have flashed a bad boot image. if you are on a11 stock i dont think twrp work 100% safe. los recovery is recommended and work without problems