Database Develop

help please/ recovery flash error

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

Deleted boot.img

I accidently deleted my boot.img on mi Mi 9 Lite (Mi CC9) by doing: fastboot boot "random file". What can I do now?

Can Someone please send me their boot.img or a link?
..

realseal3 said:
..
Click to expand...
Click to collapse
https://www.sendspace.com/file/nddami
:fingers-crossed:

Thank you very much but I get an error message:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

realseal3 said:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
What's the rom you have, miui version?

miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
lmt399 said:
What's the rom you have, miui version?
Click to expand...
Click to collapse

realseal3 said:
miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
Click to expand...
Click to collapse
Bootloader unlocked/locked?
Maybe it is better to flash the whole system through fastboot or mi flash tool.

..

It didn't work with the tool but I reflashed twrp and flashed the stock miui rom from there and it worked. Thank you anyway.

Download Fastboot rom and extract, then copy system.img to fastboot folder and also recovery, boot.img too...
Open fastboot:
Type: fastboot format system
Type: Fastboot flash boot boot.img version that you have when you brick device
Type: Fastboot flash system system.img
Type: Fastboot flash recovery recovery.img use wzsx1050 3.3.1-0709 version
Type :Fastboot boot recovery.img and device should reboot in recovery, without Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')

Can't install TWRP on my X2 Pro Fastboot Error

Hello I have this problem with my realme X2 Pro
I wanted to install TWRP on my phone using ADB and Fastboot after unlocking with success my bootloader The problem Is I first intalled with success TWRP BUT the touch was not working so I decieded to try a newer version but now this error apears
Sending 'recovery' (98304 KB) OKAY [ 2.354s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
I Tried to do adb push twrp-3.4.0-0-RMX1931-mauronofrio.img /dev/block/bootdevice/by-name/recovery but i did not work It got me this error
adb: error: failed to get feature set: no devices/emulators found
If anyone could help me it would very apreciated

I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img

Uqbar said:
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?

Farchyk said:
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Click to expand...
Click to collapse
Are you really really sure the twrp image is the right size?
Mauronofrio's one is exactly 81920 KB, not 98304 KB.
Also the official TWRP has the same size, AFAIK.
I would re-download it and maybe checksum it.

Question 'Your device is corrupt' message after failed Magisk A/B update. Flashed factory image, phone is now booting but message persists

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)

Question NO system partition?

I am feeling pretty lost.
I have flashed to stock boot.img and am in fastbootd, now trying to flash system.img
When I type "fastboot erase system" I get the error FAILED (remote: 'Partition doesn't exist')
When I type "fastboot flash system system.img" I get the error FAILED (remote: 'No such file or directory')
My phone only boots into fastboot or fastbootd at this point. What can I do?