Please help, my devices after instal rom globe can not enter to recovery mode . .
And try reinstalling it TWRP not responding/unavailable
And try reinstalling TWRP recovery to devices in command ,
Failed ( remote : Failed to load/authenticate boot image : Load Error)
Related
Hi,
I tried to flash TWRP to my phone using the command: "fastboot flash recovery twrp-3.0.2-0-titan.img"
This failed and gave me a message saying "mismatched partition size (recovery)"
What can I do?
Greetings
I'm trying to flashe recovery TWRP and it gives me an error
"FAILED (remote: image verification error)"
What should I do?
The botlauder is open
i have zenfone 4 A400CG(kitkat) always display error facebook, system ui, youtube etc. now i flash with same rom.
on adb folder i type in cmd : fastboot flash boot boot.img(success) but when i type fastboot flash fasboot fastboot.img
"Failed (remote : flash_cmds error !" can u help me ?
flash cmds error solve problem, now i flash error : "fail: no enought DATA space,please free 998 MB at least"
i try flash raw file in SD Download, after that stuck Asus logo. help me...
I have unlocked my phone.
Then I downloaded twrp-3.4.0-0-vienna.img from twrp.me, and flash it into recovery_ramdisk.
When I press Vol+ to boot twrp, the screen shows :
Code:
ERROR MODE :
Attention !
Please update system again
Error !
Func NO : 11 (recovery image)
Error NO : 2 (load failed)
Please help me
this is the only working version : P9-VIE_EVA-8.0.0-TWRP-v4.img
decryption not working (you can not access data partition)
I didn't realize that Pixels didn't work with Magisk's A/B update method, so I tried it, and afterwards I received the 'Your device is corrupt' on startup and the phone wouldn't boot.
I ended up flashing the December factory image (sans -w flag), and the phone now boots, but I still am receiving the 'Your device is corrupt' message on startup.
I did flash the patched init_boot, but the message existed before then.
Would anyone know of any steps I can take to get rid of this message? Preferably without data loss?
Thanks in advanced for any help.
Hmm. Try sideloading the OTA, see if that fixes it. Somehow, dm-verity got stuck in EIO mode. More details here
Edit: Did a little more research. In a ADB terminal (either recovery or system) you can use adb reboot "dm-verity enforcing"
Thanks for the reply.
Trying to sideload the OTA with adb sideload image.zip gives me the following error on my phone:
ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
I have verified the .zip hash matches the hash on the factory images site.
_____
If I try to run adb reboot "dm-verity enforcing" it gives me a "too many arguments" error in my terminal.
I did find this command, which seems the newer way of doing this:
fastboot flash vbmeta –disable-verity –disable-verification vbmeta.img
... but running that with the vbmeta.img from the OTA zip gives me this weird error:
fastboot: error: cannot load 'ûdisable-verity': No such file or directory (û character included)