Database Develop

[Untested][Linux/ Mac] Fastboot package for Oreo January update

Hi all,
this one is for the brave, as it is still untested.
Nevertheless, please find here some information what I did:
Got the latest full OTA package here from xda
Extracted payload.bin into the fastboot compatible .img files
Adapted the "flash_all_except_storage script" in order to automate the flashing and included it
As I have right now (just my luck) an issue with fastboot not detecting my phone, I cannot test right now. Will try again myself in the evening though, at least that is the plan.
In the meantime any brave (no guarantees, no warranties) are welcome to test it. Apart from the above mentioned changes, it is the update as it was distributed by Xiaomi/ Google including the January security patch:
Android 8.0.0 [OPR1.170623.026.8.1.10]
link removed as official version is now available here
I am looking forward to your feedback.
P.S.: For more information how to use it, please have a look here
UPDATE: system.img seems to be not flashable right now and I have no more ideas right now what I could do about it. So sorry guys, back to waiting for Xiaomi again.

downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?

i dont have a Mac, windows 10. how do i flash it ?

soeschelz said:
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
Click to expand...
Click to collapse
Rawwr said:
i dont have a Mac, windows 10. how do i flash it ?
Click to expand...
Click to collapse
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot set_active a
fastboot reboot

majamee said:
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still either flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
Click to expand...
Click to collapse
cant you make a script ? it is hard to enter every code at once

@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
Code:
fastboot flash system_a system.img
I got the following error:
Code:
invalid sparse file format at header magi
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker

soeschelz said:
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
I got the following error:
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
Click to expand...
Click to collapse
Thank you for your helpful feedback. I will see if I can do something about it, except waiting for xiaomi to finally release the fastboot image themselves or I get my ota without reading play services data.

Can you explain me how you extracted payload.bin to .img files

ramesh1686 said:
Can you explain me how you extracted payload.bin to .img files
Click to expand...
Click to collapse
I can tell you the basic instructions, but for the details I have to ask you to please have a look yourself how to do it for your Operating System.
So,
You download both python scripts from here: https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
You make sure you have installed python and google-protobuf binding for python
You open a terminal/ shell/ cmd and navigate via the "cd" command to the directory the payload.bin and the both .py scripts are
run the following command "payload_dumper.py payload.bin"
I personally did these parts on a Linux system as it was at least for me the easiest way to have python and protobuf set up in no time.
----
Btw. I had another look, if I can do something about the system.img not being flashable at the moment. Nevertheless no luck so far, I begin to wonder if the OTA package is really a full OTA, due to that or just a very big update as it is intended to update Android N to O...
Sorry, for the failed attempt, at least it was worth a try.

I had issue with "invalid sparse file format at header magi" before (also extracted image from OTA), but it flashed successfully. Flashing just took longer than usual. However I had issues with failed video recording and the only fix for me was to use full flash of stock fastboot ROM. There might be something missing in extracted images from OTA package.

I have unpacked the latest payload.bin file from Android 8.0.0 [OPR1.170623.026.8.1.10] and the size of the system.img is 3.2 GB . This is too much?
The system partition has a size of 3072 MB. It's some error of unpacking?

Fastboot ROM is available http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Source: http://en.miui.com/thread-1596182-1-1.html

Clean (re-)install full ROM pack on an A2?

Seems like I somewhat bricked my brand new A2, trying to root it – see my post in another thread.
Being careless, I used a boot image from a different version ROM. While I got the device to boot again, WLAN doesn’t work anymore. Furthermore, system updates via Android’s settings fail.
Now, on miui.com, there is a page with the latest stable ROM for download. Also there is a flashing guide. However, it looks like the flashing guide is for turning the Mi 6X into an A2: It mentions MIUI update mechanisms that are not available on stock Android (naturally). How can I install the downloaded ROM on the A2? Can I simply flash all the included image files to the respective partitions manually?

I'm facing the "same problem" can't boot at all.
I think the easiest way is to restore in TWRP some working backup with Magisk fully functional.

Cagixxx said:
I'm facing the "same problem" can't boot at all.
Click to expand...
Click to collapse
How did that happen?
I think the easiest way is to restore in TWRP some working backup with Magisk fully functional.
Click to expand...
Click to collapse
AFAIK there is no TWRP for the A2/6X. Also, I do not want to install ROMs from unofficial sources.

i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2

I did run the script, see my post in the Magisk forum. To avoid error messages, the trick is to also do fastboot flashing unlock_critical.
Furthermore, as documented in that post, I managed to install the boot.img patched by Magisk. But: To boot into Android, the boot loader needs to remain unlocked. Otherwise I get an error message that the installation cannot be trusted. For security reasons, using a production device with an unlocked boot loader is a very bad idea!.
Update: Looks like I bricked the rooted device by disabling OEM unlock in the settings plus locking the boot loader. It’s documented in that other thread.
Any idea how to fix the A2 if the boot loader is locked and it doesn’t boot into Android?
When I try to enter Recovery by pressing power plus volume-up, I also just get the message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
I tried all kinds of button combinations, such as pressing only volume-up on reboot, or pressing volume-down plus volume-up, or pressing power plus both volume keys. Always I get the above message. I can enter Fastboot though, by pressing power plus volume-down on start.

feklee said:
I did run the script, see my post in the Magisk forum. To avoid error messages, the trick is to also do fastboot flashing unlock_critical.
Furthermore, as documented in that post, I managed to install the boot.img patched by Magisk. But: To boot into Android, the boot loader needs to remain unlocked. Otherwise I get an error message that the installation cannot be trusted. For security reasons, using a production device with an unlocked boot loader is a very bad idea!.
Update: Looks like I bricked the rooted device by disabling OEM unlock in the settings plus locking the boot loader. It’s documented in that other thread.
Any idea how to fix the A2 if the boot loader is locked and it doesn’t boot into Android?
When I try to enter Recovery by pressing power plus volume-up, I also just get the message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
I tried all kinds of button combinations, such as pressing only volume-up on reboot, or pressing volume-down plus volume-up, or pressing power plus both volume keys. Always I get the above message. I can enter Fastboot though, by pressing power plus volume-down on start.
Click to expand...
Click to collapse
Your tried copy in the ADB folder the images ROM downloaded, in CMD "fastboot flash boot_a boot.img" "fastboot flash boot_b boot.img" "fastboot flash system system.img" when flash end "fastboot reboot" in screen of phone follow screen indications for Factory Reset.
My english is very bad, sorry.

tzadkiel2 said:
"fastboot flash boot_a boot.img"
Click to expand...
Click to collapse
Thanks for the suggestion, but I can’t flash because my A2 is locked:
$ fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
Sending 'boot_a' (28632 KB)...
OKAY [ 1.264s]
Writing 'boot_a'...
FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.271s
And I can’t unlock the device because OEM unlocking is disabled in the Android developer settings:
$ fastboot oem unlock
FAILED (remote: Flashing Unlock is not allowed
)
Finished. Total time: 0.001s
And I can’t enable unlocking because Android doesn’t boot.

What is used, Linux???? I used Windows
Linux I do not use it for this, sudo/su??? $ # this is what should appear if I remember correctly
it has worked for me as indicated and I have had it in a very similar way to yours even though I had already unlocked bootloader
P.d. my english is very basic I have to help the translator I only speak expañol

tzadkiel2 said:
What is used, Linux?
Click to expand...
Click to collapse
Yes.
Linux I do not use it for this, sudo/su?
Click to expand...
Click to collapse
sudo/su are not needed if permissions are set up correctly.
even though I had already unlocked bootloader
Click to expand...
Click to collapse
Having an unlocked device is a huge difference. With an unlocked device, I know how to flash it successfully.
My device, however, is OEM locked. This is the problem!
The next thing that I tried is booting into EDL mode from fastboot: $ fastboot reboot emergency
But this does not work either. Briefly the screen flashes with a message, before it tries to boot Android which doesn’t work. I had to video record the reboot process to be able to read the message. It says: “Your device software can’tbe checked for corruption.Please lock the bootloader.” [SIC]
Sadly, this is a bogus error message. I wish it was true and the bootloader was not locked.
P.d. my english is very basic I have to help the translator I only speak expañol
Click to expand...
Click to collapse
De nada. Puedo entender. (but please don’t start speaking in Spanish – mine is super basic )

I do not even remember when it was the last time I used Debian; so I remember almost nothing about Linux; but you should have unlocked the bootloader first to try what you're saying, right?; I seem to remember that there are two rom to download here, use the one of MIUI or the last one, it will not be for an antirollback
-------------------------
Yo pude instalar TWRP pero ahí me quedé ya que ni recuperaba Backup con Restore (System no se podía montar Invalid Argument) al instalar Magisk no iniciaba el Sistema (No System OS) por OTG solo discos duros (HDD) y no había manera así que tuve que deshacer todo lo hecho, y me bastó con lo que te he indicado.
No recuerdo como se abren las carpetas en Linux, pero me parece recordar que al abrir el directorio queda en #

When I try to flash system.img it give an error: cannot load "system.img".
webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse

Cagixxx said:
When I try to flash system.img it give an error: cannot load "system.img".
Click to expand...
Click to collapse
And did u try to start up the phone ?

webmasterone said:
And did u try to start up the phone ?
Click to expand...
Click to collapse
Phone boot to recovery (twrp).
I wipe system partition via TWRP. Now the only way is to flash a ROM in recovery or restore from a complete backup.

Success! I was able to flash a clean install on my A2 by using the test point method, which required opening the device. How I proceeded is documented in my thread: Which test points to short to flash locked device?

There is no other way to force test point or download mode without open the phone? xD
EDIT: I found cable to enter EDL mode. "Deep Flash Cable Repair Tool For Xiaomi"

webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
I'm experiencing same problem and i knew about what you wrote but for most of fastboot commands i get " remote: flashing is not allowed for Critical Partition " message
EDIT:
Solved
All tho phone show message bootloader is unlocked it wasn't so command " fastboot flashing unlock_critical " do the trick

HUGE thanks to you. I was stuck in a bootloop and I tried many things until this saved me. Again, thanks A LOT!!
webmasterone said:
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Click to expand...
Click to collapse

webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
thank you so much! you save me
---------- Post added at 06:43 AM ---------- Previous post was at 05:44 AM ----------
I have received some errors of: "remote: "flashing is not allowed for Critical Partition" but the system has gone up normal. its okaY?

i have the same problem...but what next ?
How i can return in stock ?

Thanks
webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
Thank you for the guide there are .bat files I think it would be easier to than running each one but newbie here
Thankfully you saved my device tho

Mi A2 stuck on TWRP Screen after phone reset.

Hello, I was using Mi A2 with TWRP and magisk installed with boot-loader unlocked. I was on Andriod Pie Oct 2019 updated. Today, i moved to Realme XT and reset the A2 from setting. Now my phone stuck on TWRP Logo Screen. I tried restarting so many time but it still comes back to same twrp screen.
I also try flashing recovery using mi flash method but still no success. It shows "Flash devcfg_a error"
One more thing, i want to add here is that before phone reset, Nov 2019 security update was failing to installed. I installed the TWRP after Oct 2019 update.
Please help me in resolving this issue. This is first time, i am using xda forums. If i failed to follow the procedure of creating thread, i apologized. Please guide me.

imubad said:
Hello, I was using Mi A2 with TWRP and magisk installed with boot-loader unlocked. I was on Andriod Pie Oct 2019 updated. Today, i moved to Realme XT and reset the A2 from setting. Now my phone stuck on TWRP Logo Screen. I tried restarting so many time but it still comes back to same twrp screen.
I also try flashing recovery using mi flash method but still no success. It shows "Flash devcfg_a error"
One more thing, i want to add here is that before phone reset, Nov 2019 security update was failing to installed. I installed the TWRP after Oct 2019 update.
Please help me in resolving this issue. This is first time, i am using xda forums. If i failed to follow the procedure of creating thread, i apologized. Please guide me.
Click to expand...
Click to collapse
Issue resolved. After following below guide that i find online outside of XDA.
Below are the Steps on How to manually Install Official Android Firmware on your Xiaomi Mi A2 via Fastboot -
1) Extract the Fastboot Firmware and Open Images folder where you'll find all the System, Boot, and other Image files.
2) Extract and paste the ADB and Fastboot files to the Fastboot Firmware Images folder, which you extracted in Step 1.
3) Open Fastboot via CMD and Paste all the below Commands -
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash userdata userdata.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
4) Enjoy!

imubad said:
Issue resolved. After following below guide that i find online outside of XDA.
Below are the Steps on How to manually Install Official Android Firmware on your Xiaomi Mi A2 via Fastboot -
1) Extract the Fastboot Firmware and Open Images folder where you'll find all the System, Boot, and other Image files.
2) Extract and paste the ADB and Fastboot files to the Fastboot Firmware Images folder, which you extracted in Step 1.
3) Open Fastboot via CMD and Paste all the below Commands -
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash userdata userdata.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
4) Enjoy!
Click to expand...
Click to collapse
Now, my phone is on 9 (pkq1.180904.001.v10.0.2.0.pdimifj) and Dec 5, 2018 patch. I am still having installation problem with March 2019 update.

imubad said:
Now, my phone is on 9 (pkq1.180904.001.v10.0.2.0.pdimifj) and Dec 5, 2018 patch. I am still having installation problem with March 2019 update.
Click to expand...
Click to collapse
Download November 2019 official fastboot image for stock ROM 10.0.17.0 and flash it in fastboot using "falsh_all_except_data.bat".
All necessary instructions are here in "Xiaomi Mi A2 Guides, News, & Discussion" forum, just try to search in xda instead of going outside.
E.G. link to official fastboot image 10.0.17.0 was first published in https://forum.xda-developers.com/mi-a2/how-to/november-2019-security-patch-available-t4002373 (what a surprise?), and then added to OP of https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 storing links to previous existing official images (getting stranger and stranger, is not it?)

Question I am stuck in boot loop

after I installed a wrong indian rom my original ROM is NE2215 10 then I upgraded to NE2213 12 and it worked fine then i upgraded to A13 then i wanted to downgrade again then i installed a wrong indian ROM then I tried to get back to NE2213 and I flashed it
but I got stuck in a boot loop now so any help ?
btw my phone isn't bricked and I can go recovery and fastboot

What happens if you recover using the built in recovery??

Wait…what? Try booting the boot file from bootloader

Did you upgrade to the android 13 beta or Indian rom A.13?

g96818 said:
Wait…what? Try booting the boot file from bootloader
Click to expand...
Click to collapse
He's downgraded dude.... Not sure a boot image will help him.... This is a situation that MSM was made for tbh.
Can try the boot image, but for what ? 13 or 12? EU or Indian?
Bit of a mess.
Edit: from the OP, it would seem he's on the EU firmware. But no way to tell what firmware is currently taking up the majority of his devices system between 12 or 13
I would try recovery, but yea sure booting an image shouldn't hurt.

I mean... You said the problem is that you flashed the wrong firmware: if you can boot in recovery and Fastboot, just download and flash the right firmware

g96818 said:
Did you upgrade to the android 13 beta or Indian rom A.13?
Click to expand...
Click to collapse
both android 13 first

AmazDev said:
I mean... You said the problem is that you flashed the wrong firmware: if you can boot in recovery and Fastboot, just download and flash the right firmware
Click to expand...
Click to collapse
I cant find NE2215 the original out of the box firmware

dladz said:
He's downgraded dude.... Not sure a boot image will help him.... This is a situation that MSM was made for tbh.
Can try the boot image, but for what ? 13 or 12? EU or Indian?
Bit of a mess.
Edit: from the OP, it would seem he's on the EU firmware. But no way to tell what firmware is currently taking up the majority of his devices system between 12 or 13
I would try recovery, but yea sure booting an image shouldn't hurt.
Click to expand...
Click to collapse
can you tell me the steps of what to do ?

moro700 said:
can you tell me the steps of what to do ?
Click to expand...
Click to collapse
Hey,
It really depends mate, but for me if I've had a bad flash and my recovery is still intact then I'd boot to my bootloader, then recovery, then just do a full wipe from there, this pops the operating system back in there and gives you a functional OS back..plus you bypass the need to identify what OS is indeed installed meaning you aren't attempting to identify the OS and by and large making a mistake, unless you can categorically identify it, something you may not be able to do without it booting.
Few things to note, I don't know how far the last firmware change you made got to.... So this could fail, but I cannot see it making things worse, I've not a had a problem with this method before but I've not been in the exact situation you're in so there is always an inherent risk.
You could go ahead and attempt to boot the boot image from the last firmware you had in a working state and see if that works, bare in mind I'm saying boot via fastboot, do not flash, I mean boot, if it fails, just reboot and you're back to where you are now.
If that works then fantastic, you're back in business, if not then you could either attempt the recovery wipe like I said OR go down the fastboot a full firmware method.
That should also work but that would be my last thing to do, it would mean extracting a firmware image by image from payload.bin then flashing each image over.
Apparently it's possible via fastboot enhance, but (sorry I know it's not too helpful) I have not had to do this myself, I was going to but recovery wipe worked for me instead.
Hope this helps mate, if you're unsure then let us know before you commit.

moro700 said:
I cant find NE2215 the original out of the box firmware
Click to expand...
Click to collapse
try flashing the downgrade rom, above the post that says WARNING. BOOTLOOP.

Fastboot Enhace
Make sure you check the box that says allow incremental or else it won't let you extract the downgrade rom.

moro700 said:
can you tell me the steps of what to do ?
Click to expand...
Click to collapse
I'm not sure if you can flash the downgrade rom through recovery or not, but you can try the following as a last resort. I am not responsible if you end up breaking your phone and this should only be used as a guide that you need to modify yourself since this script came from a oneplus 9RT fastboot rom.
Code:
@echo off
ECHO ###################
ECHO # Formatting data #
ECHO ###################
fastboot format userdata
fastboot format metadata
@echo off
title OnePlus 9RT Fastboot ROM Installer by abhinavgupta371 and HELLBOY017
ECHO #######################################################################
ECHO # Oxygen OS Flasher For OnePlus 9RT by abhinavgupta371 and HELLBOY017 #
ECHO # updated by Va1d3m #
ECHO #######################################################################
ECHO #################################
ECHO # Flashing firmware into slot A #
ECHO #################################
fastboot --set-active=a
ECHO #################################
ECHO # Flashing bootloader img's #
ECHO #################################
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all modem modem.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
ECHO ##########################
ECHO # Rebooting to fastbootd #
ECHO ##########################
fastboot reboot fastboot
ECHO #################################
ECHO # Flashing fastbootd img's #
ECHO #################################
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cpucp cpucp.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all engineering_cdt engineering_cdt.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all mdtp mdtp.img
fastboot flash --slot=all mdtpsecapp mdtpsecapp.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all oplus_sec oplus_sec.img
fastboot flash --slot=all oplusstanvbk oplusstanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all qweslicstore qweslicstore.img
fastboot flash --slot=all shrm shrm.img
fastboot flash --slot=all splash splash.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all vm-bootsys vm-bootsys.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
ECHO ###############################
ECHO # Resizing logical partitions #
ECHO ###############################
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
fastboot delete-logical-partition my_carrier_a
fastboot delete-logical-partition my_carrier_b
fastboot delete-logical-partition my_company_a
fastboot delete-logical-partition my_company_b
fastboot delete-logical-partition my_engineering_a
fastboot delete-logical-partition my_engineering_b
fastboot delete-logical-partition my_heytap_a
fastboot delete-logical-partition my_heytap_b
fastboot delete-logical-partition my_manifest_a
fastboot delete-logical-partition my_manifest_b
fastboot delete-logical-partition my_preload_a
fastboot delete-logical-partition my_preload_b
fastboot delete-logical-partition my_product_a
fastboot delete-logical-partition my_product_b
fastboot delete-logical-partition my_region_a
fastboot delete-logical-partition my_region_b
fastboot delete-logical-partition my_stock_a
fastboot delete-logical-partition my_stock_b
fastboot delete-logical-partition odm_a-cow
fastboot delete-logical-partition odm_b-cow
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition system_b-cow
fastboot delete-logical-partition system_ext_a-cow
fastboot delete-logical-partition system_ext_b-cow
fastboot delete-logical-partition product_a-cow
fastboot delete-logical-partition product_b-cow
fastboot delete-logical-partition vendor_a-cow
fastboot delete-logical-partition vendor_b-cow
fastboot delete-logical-partition my_carrier_a-cow
fastboot delete-logical-partition my_carrier_b-cow
fastboot delete-logical-partition my_company_a-cow
fastboot delete-logical-partition my_company_b-cow
fastboot delete-logical-partition my_engineering_a-cow
fastboot delete-logical-partition my_engineering_b-cow
fastboot delete-logical-partition my_heytap_a-cow
fastboot delete-logical-partition my_heytap_b-cow
fastboot delete-logical-partition my_manifest_a-cow
fastboot delete-logical-partition my_manifest_b-cow
fastboot delete-logical-partition my_preload_a-cow
fastboot delete-logical-partition my_preload_b-cow
fastboot delete-logical-partition my_product_a-cow
fastboot delete-logical-partition my_product_b-cow
fastboot delete-logical-partition my_region_a-cow
fastboot delete-logical-partition my_region_b-cow
fastboot delete-logical-partition my_stock_a-cow
fastboot delete-logical-partition my_stock_b-cow
fastboot create-logical-partition odm_a 1
fastboot create-logical-partition odm_b 1
fastboot create-logical-partition system_a 1
fastboot create-logical-partition system_b 1
fastboot create-logical-partition system_ext_a 1
fastboot create-logical-partition system_ext_b 1
fastboot create-logical-partition product_a 1
fastboot create-logical-partition product_b 1
fastboot create-logical-partition vendor_a 1
fastboot create-logical-partition vendor_b 1
fastboot create-logical-partition my_carrier_a 1
fastboot create-logical-partition my_carrier_b 1
fastboot create-logical-partition my_company_a 1
fastboot create-logical-partition my_company_b 1
fastboot create-logical-partition my_engineering_a 1
fastboot create-logical-partition my_engineering_b 1
fastboot create-logical-partition my_heytap_a 1
fastboot create-logical-partition my_heytap_b 1
fastboot create-logical-partition my_manifest_a 1
fastboot create-logical-partition my_manifest_b 1
fastboot create-logical-partition my_preload_a 1
fastboot create-logical-partition my_preload_b 1
fastboot create-logical-partition my_product_a 1
fastboot create-logical-partition my_product_b 1
fastboot create-logical-partition my_region_a 1
fastboot create-logical-partition my_region_b 1
fastboot create-logical-partition my_stock_a 1
fastboot create-logical-partition my_stock_b 1
ECHO ###############################
ECHO # Flashing logical partitions #
ECHO ###############################
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_manifest my_manifest.img
fastboot flash my_preload my_preload.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
ECHO #######################
ECHO # Rebooting to system #
ECHO #######################
fastboot reboot
pause

How To Guide Unbrick Mi 11 Ultra via fastboot commands (softbrick/boobloop)

Download and extract model specific firmware zip to the fastboot folder.
Enter fastboot by turning the device off and then turning it on using pwr+vol down for few seconds.
If it doesn't turnoff, then let the battery drain out on its own and then retry to enter fastboot.
Execute each of the below commands in the CMD window, one at a time. If you get any errors after executing any of these commands, then don’t leave the process mid-way. Rather continue executing the rest of the commands and then check the results.
Fastboot commands​fastboot erase boot_ab
fastboot flash xbl_ab xbl.elf
fastboot flash xbl_config_ab xbl_config.elf
fastboot flash abl_ab abl.elf
fastboot flash aop_ab aop.mbn
fastboot flash tz_ab tz.mbn
fastboot flash featenabler_ab featenabler.mbn
fastboot flash hyp_ab hypvm.mbn
fastboot flash modem_ab NON-HLOS.bin
fastboot flash bluetooth_ab BTFM.bin
fastboot flash dsp_ab dspso.bin
fastboot flash keymaster_ab km41.mbn
fastboot flash devcfg_ab devcfg.mbn
fastboot flash qupfw_ab qupv3fw.elf
fastboot flash uefisecapp_ab uefi_sec.mbn
fastboot erase imagefv_ab
fastboot flash imagefv_ab imagefv.elf
fastboot flash shrm_ab shrm.elf
fastboot flash multiimgoem_ab multi_image.mbn
fastboot flash cpucp_ab cpucp.elf
fastboot flash qweslicstore_ab qweslicstore.bin
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash rescue rescue.img
fastboot flash storsec storsec.mbn
fastboot flash spunvm spunvm.bin
fastboot flash rtice rtice.mbn
fastboot flash vendor_boot_ab vendor_boot.img
fastboot flash vm-bootsys_ab vm-bootsys.img
fastboot flash super super.img
fastboot flash cust cust.img
fastboot flash dtbo_ab dtbo.img
fastboot flash vbmeta_ab vbmeta.img
fastboot flash vbmeta_system_ab vbmeta_system.img
fastboot erase metadata
fastboot flash metadata metadata.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot flash boot_ab boot.img
fastboot flash logo logo.img
fastboot set_active a
fastboot reboot
If the device is still boot looping, fastboot -w (as the final option) and repeat all the above commands step-by-step.