[Redmi Note 8] Unable to boot to recovery or fastboot (System has been destroyed)

Search This thread
Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.

Here are the set of commands I ran just after unlocking the bootloader:


PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices


What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?
 

Attachments

  • Log.png
    Log.png
    119 KB · Views: 8
Last edited:

loopypalm

Senior Member
Jul 8, 2016
1,070
1
292
Osaka
Is there any way to do it now? without having to go into EDL mode & stuff?
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want

now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
 

Attachments

  • vbmeta.img
    4 KB · Views: 11
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want

now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try 😓.
 
Last edited: