Hi
I had TWRP installed and installed Cm12.1-20150427 unoffical-yuga and Cyanogenmod wrote its own recovery.
If I try to install any zips such as
extract_elf_ramdisk-hack.zip
twrp-2.8-20150424-yuga.zip
I get the error:
E:footer is wrong
E:signature verification failed
If I try ADB
fastboot flash recovery recovery.img
I get
sending 'recovery' (10388 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.458s
I'm stuck any ideas?
Thanks
What i did and it worked really fine is to use the Rashr utility (free from Google Store) and just fhlash the twrp image.
Try it!
cramhead said:
Hi
I had TWRP installed and installed Cm12.1-20150427 unoffical-yuga and Cyanogenmod wrote its own recovery.
If I try to install any zips such as
extract_elf_ramdisk-hack.zip
twrp-2.8-20150424-yuga.zip
I get the error:
E:footer is wrong
E:signature verification failed
If I try ADB
fastboot flash recovery recovery.img
I get
sending 'recovery' (10388 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.458s
I'm stuck any ideas?
Thanks
Click to expand...
Click to collapse
Related
im stuck with this piece of sh*t phone and "waiting for any device". I flashed TWRP 142314 times on my phone, and today this bloody problem comes out and i cant f*king solve it. My drivers and everything is up to date, expect something named "S1 Boot Fastboot" (warning sing near that in device manager). I have no idea what the hell is that and i cant flash twrp and install custom rom. Any ideas, excpet that one about uninstalling win10 )))
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
nevenx said:
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Click to expand...
Click to collapse
You can't flash TWRP to the recovery partition on the Xperia Z. It doesn't use the recovery partition; instead, it uses the FOTAKernel partition, which is inaccessible by Fastboot. If you want to destroy your old stock firmware and install custom ROM, flash TWRP to boot partition. The phone should not boot to the firmware and boots straight to TWRP.
Hey guys,
I have ZTE Red Magic with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP. So I booted into the bootloader, entered "fastboot boot recovery.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.582s
The installation of recovery was successful as I typed the command "fastboot flash recovery recovery.img"
target reported max download size of 536870912 bytes
sending 'recovery' (26721 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.001s]
finished. total time: 0.583s
I have absolutely no idea what I'm doing wrong. pls help
boyDbest said:
Hey guys,
I have ZTE Red Magic with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP. So I booted into the bootloader, entered "fastboot boot recovery.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.582s
The installation of recovery was successful as I typed the command "fastboot flash recovery recovery.img"
target reported max download size of 536870912 bytes
sending 'recovery' (26721 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.001s]
finished. total time: 0.583s
I have absolutely no idea what I'm doing wrong. pls help
Click to expand...
Click to collapse
Did you unlocked bootloader?
methuselah said:
Did you unlocked bootloader?
Click to expand...
Click to collapse
Yes brother i did
I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.
That's normal. Just enable modifications and that's it.
kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?
I don't think so.
You're good to proceed.
I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.
No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Flash fastboot ROM
Setting current slot to 'a' OKAY [ 12.421s]
Finished. Total time: 12.517s
Rebooting OKAY [ 0.098s]
Finished. Total time: 3.115s
Rebooting, then back to FASTBOOT
Solved!!
I got help from Xiaomi support
Helen17 said:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Click to expand...
Click to collapse
i had the exact same problem, but someone on the site has solved the problem and repaired my phone on distance but against fee, if you want i can send you the link for him.
Helen17 said:
Solved!!
I got help from Xiaomi support
Click to expand...
Click to collapse
how to solved?
My phone is no flash,no root, no USB debugging. Can't boot after OTA update today, stuck at Fastboot Mode, can't start. the error message is "failed to load/verify boot images"
I download Redfin from Factory Images for Nexus and Pixel Devices, run flash-all.bat, error message:
Code:
Sending 'bootloader_a' (8762 KB) OKAY [ 0.328s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (149796 KB) OKAY [ 3.886s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: r3-0.4-8351081
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 09
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.169s]
Checking 'version-bootloader' OKAY [ 0.178s]
Checking 'version-baseband' OKAY [ 0.139s]
Setting current slot to 'a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Press any key to exit...
I run:
[ICODE]# fastboot flashing unlock
FAILED (remote: 'Error getting device locked state Not Ready')
fastboot: error: Command failed[/ICODE]
fastboot boot boot.img
Sending 'boot.img' (98304 KB) OKAY [ 2.400s]
Booting FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
fastboot devices
09aaaaaaaaaa fastboot
please help me
Have you tried simply re-flashing?
Sewdohe said:
Have you tried simply re-flashing?
Click to expand...
Click to collapse
yes, but it can't open, He still remains in "Fastboot Mode" and cannot be started
Barbet is Pixel 5a.
Redfin is Pixel 5
andybones said:
Barbet is Pixel 5a.
Redfin is Pixel 5
Click to expand...
Click to collapse
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Evolv X said:
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Click to expand...
Click to collapse
Did using the correct file fix your problem?
NO, and I use Google Online, Bug can't
V0latyle said:
Did using the correct file fix your problem?
Click to expand...
Click to collapse
Evolv X said:
NO, and I use Google Online, Bug can't
Click to expand...
Click to collapse
Could you be a bit more detailed? I don't understand.
Same, I don't understand. It appears you're trying to flash for the wrong phone...
If your bootloader is locked, you cannot flash anything in fastboot/bootloader.
Try sideloading the OTA again.
Getting this issue...are you able to fix it?