Hi there! i am facing an issue and that is i am having the current image (boot/recovery) have been destoryed and can not boot,
but I am able to boot into fastboot with power + volume buttons and i am able to flsah recovery as well i have tried three recoveries twrp, orangefox, and stock and they all flash successfully but after that it agian shows above mentioned message i am unable to go into recovery below is the code of my console log
C:\Users\hp\Downloads\platform-tools_r31.0.3-windows\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
C:\Users\hp\Downloads\platform-tools_r31.0.3-windows\platform-tools>fastboot devices
b4e38ae3 fastboot
C:\Users\hp\Downloads\platform-tools_r31.0.3-windows\platform-tools>fastboot flash recovery orangefox.img
Sending 'recovery' (35408 KB) OKAY [ 0.961s]
Writing 'recovery' OKAY [ 0.171s]
Finished. Total time: 1.181s
C:\Users\hp\Downloads\platform-tools_r31.0.3-windows\platform-tools>fastboot boot orangefox.img
Sending 'boot.img' (35408 KB) OKAY [ 0.783s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\Users\hp\Downloads\platform-tools_r31.0.3-windows\platform-tools>
Same ERROR, did you find any fix?
Related
Also i get bootloop
My phone rooted with Kingoroot - sorry for advertisement
ANDROID VERSION 4.2.2 Jelly bean
This is code from CMD
Code:
fastboot flash recovery recovery.img
Code:
C:\Users\windows\Desktop\ADB & Fastboot Toolkit>fastboot flash recovery twrp.img
sending 'recovery' (10368 KB)...
OKAY [ 0.307s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.328s
C:\Users\windows\Desktop\ADB & Fastboot Toolkit>
What to do now? plz i need get the answer.
Code:
C:\Users\windows\Desktop\ADB & Fastboot Toolkit>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\Users\windows\Desktop\ADB & Fastboot Toolkit>fastboot oem unlock
...
(AND ALL THE TIME ...)
So I've gotten in a position where I can only get into FASTBOOT&RESCUE MODE on my Honor 9, so no TWRP, no eRecovery and no Android. I got here when I tried to install STF_RECOVERY_OREO_NoCheck.img from the terminal in TWRP.
From my Ubuntu (17.10) PC I can see the device in fastboot, but trying to flash TWRP (or any other image) gives me an error:
sudo fastboot flash recovery twrp-3.1.1-oreo-stf.img
target reported max download size of 471859200 bytes
sending 'recovery' (20336 KB)...
OKAY [ 0.651s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.656s
In FASTBOOT&RESCUE MODE it says:
PHONE Unlocked
FRP Lock
The device doesn't show up in ADB. It shows up in "lsusb" as a Google device, so I tried both Google as Huawei USB drivers.
Hi there, so I've just bricked my RNE_L21 when trying to flash system image from Pixel Experience.
I wan't to flash stock recovery images to make it work again but it stops me at all of the recovery images (ramdisk, vendor, etc.):
target reported max download size of 471859200 bytes
sending 'ERECOVERY_KERNEL' (24576 KB)...
OKAY [ 0.725s]
writing 'ERECOVERY_KERNEL'...
FAILED (remote: Command not allowed)
finished. total time: 0.745s
Bootloader is fully unlocked and i have all fastboot and ADB drivers updated, TWRP installed
Please help, thanks
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!
Adroid One 10
Unlock solved and installed the lineage OS a several times in twrp with success according to the given instruction here:
https://raw.githubusercontent.com/RaghuVarma331/changelogs/master/crossdevelopment/abcrins.txt
but the phone didnt boot the OS after restarting neither in slot A nor B. In twrp u could read that there was "no OS installed" (??).
In the last try i changed the slot before installing and now the phone hangs in a restart loop with download mode and i connot turn down the phone or get back to twrp. Trying to connect it by adb to restart twrp is not working....
=========================
My errors while trying to get out:
=========================
fastboot boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot B:\Various\Nokia\TWRP\twrp.img
downloading 'boot.img'...
OKAY [ 0.969s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.011s
fastboot flash recovery twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery B:\Various\Nokia\TWRP\twrp.img
target reported max download size of 402653184 bytes
sending 'recovery' (42412 KB)...
OKAY [ 0.953s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.968s
So right now I'm at the end with my rudementary skills here.
Any idea how to get back to the point with twrp and installing an OS?
Thanks.
In case that no one else answers but someone else have the same problems , I write my solutions here.
.......
I got back to twrp by changing the slot in ADB
fastboot --set-active=a
unfortunately the restart loop doesn't end and no OS starts wether in slot a or b.