Develop Bugs

Using Mfastboot.exe to Flash a Motorola device

Mfastboot
Although Mfastboot.exe works with most Motorola Devices, the exact files and flash commands may vary, best to see specific forum/threads for the device.
I haven't updated this thread for a while.
Mfastboot still works, but the flash commands have changed for newer devices.
See Guide: Motorola Firmware
Motorola devices only.
Can be used with Windows/Linux/Mac but this thread will only have instructions for Window (10)
Instruction for using Mfastboot on Linux/Mac should be similar as standard Fastboot for Android
[UNIX][mFastboot] mFastboot on Linux and Mac OS X, and how to use it by danieliop
The Easiest Way to Install Android's ADB and Fastboot Tools on Any OS - lifehacker
Watch Videos
[Video]Using Mfastboot.exe to Unbrick a Motorola device
How to Firmware Restore your Motorola Device on Windows 10 without RSDlite by RootJunky
Download
Motorola Drivers
Mfastboot files: Mega - AFH - XDA - Drive - DevHost no longer Safe -
Firmware for your Device
Verify Files
Compare File Size with file size form download site
Use Hash Checksums
mfastboot-v2.zip (1.36 MB) MD5 Sum: 83650a3589d2ecd7c8115ce860d45a23
Install Moto Drivers
Extract files from zip
Run Motorola_End_User_Driver_Installation_....msi
Reboot PC
Setup Mfastboot.exe
Extract mafastboot.zip to a local drive
Example - C:/Mfastboot
Open start menu and type CMD
Right click on CMD > select open file location
Find cmd.exe, right click and copy
Paste into Mfastboot folder
Show known File Types
Open C:/Mfastboot folder
Select View>options>Change folder and Search options
In Folder Options Select Tab View
Uncheck Box: Hide Extensions for Known file Types
Select OK
Short Version - Flashing System Only
In some cases only System.img is necessary
Type commands
Code:
mfastboot flash system system.img
and
Type commands
Code:
mfastboot reboot
Press enter
if Device does not boot try Long Version
Long Version -Using Mfastboot to Flash Firmware
Note: The exact files needed will very by device model
Extract files from Firmware xml.zip
Copy
Code:
NON-HLOS.bin
system.img
boot.img
recovery.img
to Mfastboot folder
Boot Device to AP Fastboot Mode (Power Off, Hold Volume Down, Press power button for 2-3 secs then release)
Note Click here If you see Low Battery, Click here if you see Fastboot Reason: Sticky bit factory_fastboot
Run cmd.exe in Mfastboot folder
Type commands
Code:
mfastboot flash modem NON-HLOS.bin
Press enter
Type commands
Code:
mfastboot erase modemst1
Press enter
Type commands
Code:
mfastboot erase modemst2
Press enter
Type commands
Code:
mfastboot flash system system.img
Press enter this may take several minutes to finish and be flashed in several segments.
Type commands
Code:
mfastboot flash boot boot.img
Press enter
Type commands
Code:
mfastboot flash recovery recovery.img
Press enter
Type commands
Code:
fastboot erase cache
Press enter
Optional Data Wipe: Type commands
Code:
fastboot erase userdata
Press enter
Type commands
Code:
mfastboot reboot
Press enter
Device should boot normally, If not see RSD Lite or House of Moto

Troubleshooting
Q1: Error: Cannot load system.img: Not enough space.
Solution: try flashing system.img in chunks with
Code:
mfastboot flash system system.img -P
- Thanks to @Merconium for the tip​
Error: UTAG "bootmode" configured as fastboot
Solution 1:
Code:
fastboot oem fb_mode_clear
fastboot reboot
Solution 2:
Code:
fastboot erase motoboot
fastboot flash motoboot motoboot.img
fastboot reboot

Credit: [GUIDE][FAQ][KK] How to Root, Boot Unlock & More by ATTACK

Saved #4

Saved #5

AndroidDude7 said:
Ah okay, will you send a link to me when you do?
Click to expand...
Click to collapse
Video up
[Video]Using Mfastboot.exe to Unbrick a Motorola device

sd_shadow said:
Video up
[Video]Using Mfastboot.exe to Unbrick a Motorola device
Click to expand...
Click to collapse
Thanks so much!

sd_shadow said:
Video up
[Video]Using Mfastboot.exe to Unbrick a Motorola device
Click to expand...
Click to collapse
So I just did as you showed in the video but it said unable to partition 'system.img' or something like that

AndroidDude7 said:
So I just did as you showed in the video but it said unable to partition 'system.img' or something like that
Click to expand...
Click to collapse
I would try RSD Lite.

THANK YOU very much!!!!!!!! You saved my life, when I didn't know what else to do (RSD lite didn't recognice my device and I coudn't flash anything by twrp). You're amazing and I can't comment your video so... Awesome post

Sadly to say, but seems like mfastboot is outdated for now. I get error trying to flash SU6-7.7 ROM for Droid Maxx. RSD Lite 6.2.4 is ok.
e:\Motorola\XT1080\QLOAD_firmwares\CFC-obakem_verizon-user-4.4.4-SU6-7.7-release-keys.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
sending sparse 'system' (768973 KB)...
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
OKAY [ 49.390s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.967s
Click to expand...
Click to collapse

s5610 said:
Sadly to say, but seems like mfastboot is outdated for now. I get error trying to flash SU6-7.7 ROM for Droid Maxx. RSD Lite 6.2.4 is ok.
e:\Motorola\XT1080\QLOAD_firmwares\CFC-obakem_verizon-user-4.4.4-SU6-7.7-release-keys.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
sending sparse 'system' (768973 KB)...
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
OKAY [ 49.390s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.967s
Click to expand...
Click to collapse
I may need to update thread
to something like this
http://forum.xda-developers.com/showthread.php?t=2542219
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot[/QUOTE]
Sent from my XT1080 using XDA Labs

sd_shadow said:
I may need to update thread to something like this
Click to expand...
Click to collapse
LOL. I found the cause. Being Moto enthusiast I'm using mfastboot of latest version renamed to "fastboot.exe" for very long time, but recently copied foreign file and mixed up with mine, so that was the cause
Thanks for the hint!

added How to Firmware Restore your Motorola Device on Windows 10 without RSDlite
Rootjunky.com

I have to start the phone manually
I´ve made my phone run, but when I turn it on, it boots in bootloader mode and I have to start the phone manually

UTesla said:
I´ve made my phone run, but when I turn it on, it boots in bootloader mode and I have to start the phone manually
Click to expand...
Click to collapse
no errors?
what is after boot reason?
which device?

But my phone's ROM doesn't have a system.img file. The files in it are shown in the picture.

But my phone's ROM doesn't have a system.img file. The files in it are shown in the picture. Please help quick...

YM_SNIPER22 said:
But my phone's ROM doesn't have a system.img file. The files it have are shown in the picture. Please help quick...
Click to expand...
Click to collapse
Change the file extension for system_signed so it's
system_signed.img
Sent from my sailfish using XDA Labs

Thanks sd_shadow!!!!!!!!!!!! You saved my phone again!!!!!

[Help] Pixel 3 xl stuck in twrp

i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Update: solved. I had to run the command window and admin and it flashed just fine. Thanks spotmark!

superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.

superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Try flashing Magisk again in TWRP.

spotmark said:
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image

superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
.
Plz read line #1 on post #1 for twrp . . . ( hint ) it'll tell you that the twrp team has "not" yet got adb sideload working. . We all have to be patient !
.
And the good News is . . . if you use the usb-C adapter in the box and plug in a usb-A thumb drive into the pixel when running twrp . . . . you can see and grab stuff off that thumb drive. . . . . it worked for me 1

superbean83 said:
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
You need to flash the boot.img not the bootloader.

superbean83 said:
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
Fastboot flash boot --slot all boot.img

airmaxx23 said:
You need to flash the boot.img not the bootloader.
Click to expand...
Click to collapse
Do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app

Update Pie (December)

Hi all!
I installed PIE using the VPN method in the beginning of the month. Now, the update (about 90mb) was released but I'm getting an error message.
I tried several networks, WiFi or cellular but the error persists.
Does any one has an idea on what I can do? I don't have a working windows computer unfortunately.
Regards!

How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,

Gregor250385 said:
How on earth did you turn on the battery % in the status bar??
Click to expand...
Click to collapse
asking the real questions!

Gregor250385 said:
How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,
Click to expand...
Click to collapse
You can use: https://play.google.com/store/apps/details?id=com.bryancandi.android.uituner
This is what I used and is working without issues.
I'm just not able to update to the lastest version rolled out today. Damn it!

well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.

senntennce said:
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.
Click to expand...
Click to collapse
Well you can try to use vmware workstation and emulate windows, theoretically it would work but dont forget to install the drivers otherwise it wont be recognized.
Edit : platform tools exists also for mac os.

reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though

DrEzkimo said:
reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though
Click to expand...
Click to collapse
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!

senntennce said:
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!
Click to expand...
Click to collapse
Just do what i told it will be fine, as i said there is a version of platform tools for mac os, if you need further help i ll be here.

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.

Does this version have the bug as vpn version? For example flash of screen (normale/black)?

croccio said:
Does this version have the bug as vpn version? For example flash of screen (normale/black)?
Click to expand...
Click to collapse
Nope, works perfectly, 0 bugs.

i have problems with wifi
can't connect to any of my saved wifi
tried to reset wifi twice, but it doesn't work

Hakkinan said:
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.
Click to expand...
Click to collapse
I'm currently downloading those files.
The commands that I need will be:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Correct?
Thanks

Well, for my case i would rather remove everey thing and start from scratch for a fresh start with only One command and zero risk, if you get the same result with fastbooting go ahead.

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
XIaomi specifically warns you about NOT reverting to Oreo once you are on Pie.

After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Edit: Yeah, after reading some more, it seems that it is required to have the boot loader unlocked and I don't have it. Bummer.

senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
I'm not sure about MacOS (since i don't have one) but in Windows/Linux this happens when you use an older version of fastboot.

senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
Since your windows is down, can you try it on a virtual machine (vmware workstation) ?

fastboot problems?

edit3: managed to flash orangefox back(MTP now works in recovery) i should be able to flash a stock rom now
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
edit: i don't have access to an intel machine nor an usb hub(i have a ryzen cpu)
edit2: for some reason i have 3 different errors i can get
Code:
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1.911s

You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it

SunilSuni said:
You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it
Click to expand...
Click to collapse
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp

ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz

SunilSuni said:
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz
Click to expand...
Click to collapse
that's the file i downloaded and tried

ijheaven said:
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
Click to expand...
Click to collapse
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem

Sidgup1998 said:
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem
Click to expand...
Click to collapse
i'll try that thanks!

or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.

gursewak.10 said:
or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.
Click to expand...
Click to collapse
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s

ijheaven said:
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
Click to expand...
Click to collapse
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly

gursewak.10 said:
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly
Click to expand...
Click to collapse
bootloader is unlocked and reinstalled adb still no luck

ijheaven said:
bootloader is unlocked and reinstalled adb still no luck
Click to expand...
Click to collapse
Its working , but khmmm use miui flash tool... stop using adb, becouse you don't know what are you doing..You gonna brick it and than you'll cry again.??
Tip: dummy file. ?
Good luck.
Sent from XDA Labs

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

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?

Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
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

loopypalm said:
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
Click to expand...
Click to collapse
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 .

Rocker_2102 said:
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 .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?

No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.

Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.

Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...

loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)

bro how did you booted into fastboot i also in same situation

how did you fixed i also in same situation

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;

Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.