This guide exists next to [GUIDE] Extracting the latest firmwares from ROM update package and they supplement eachother.
General word about firmware updates:
A lot of people know of the importance and benefits of keeping your device firmware updated, just like you keep your custom ROM updated. If you don't keep them updated, you might not get the best out of your custom ROM (like: more bugs, system stability and performance problems/less speed.. also, vendor components, e.g Qualcomm and other chips, have security patches in the firmware.. "Vendor patch level" vs Android "Security patch level").
Besides incremental firmware updates from each OxygenOS release with a small changelog, too many people are missing out on huge jumps such as that they are running an Android 11 custom ROM, while their firmware was never updated so it remained a firmware originally shipped with an Android 10 (or earlier) OxygenOS release. Staying behind on huge jumps like these, causes the biggest list of problems with stability and performance. Therefore it is advisable to keep your firmware updated, and note that even small incremental updates (based on the same Android version) tend to give performance, security and stability benefits.
Prerequisites
For flashing the latest firmware, you need to have the firmware files (NOT the ROM update .zip file.. but a bunch of .img's) first. You can get them in multiple ways:
- Look for someone on XDA that has shared them, after they extracted the firmwares from the ROM update .zip file. This saves you time, but if you want to do it by yourself then first follow the "Extract firmwares" guide. An example of a reason for doing it yourself is: you want to be sure of the authencity, completeness and integrity of firmware files (that is everything but guaranteed if you DL it from another user)
- Do it yourself, as described above, and for this use the guide linked above
So after this stage, you have the firmware .img files, as required to proceed:
GUIDE STARTS BELOW THIS LINE
1) Get adb and fastboot from https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2) Extract the above (adb and fastboot) to a folder named "FW update". We assume that's the location all of the extracted firmware (.img) files are, like they would be if you followed the "Extract firmwares" guide to get them
So, now that your adb and fastboot are in the same folder as all required firmware files, you can proceed.
3) Actual flashing instructions, a very simple process
Code:
1) Boot to Recovery
2) Enter Fastboot (e.g for LineageOS recovery: "Advanced" > "Enter Fastboot")
3) Connect phone to PC with USB cable
4) Open cmd (command prompt) in your adb / fastboot binaries location folder (in cmd, enter cd [location of your "FW update" folder.. or alternatively copy cmd.exe from system32 to "FW update" folder & open it there),
5) Start flashing..
Enter commands 1 by 1:
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 cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot
Done, now your phone will boot up with the updated firmwares.
What's the command to flash system IMG? Can I use this process to flash A11 update from A9 MSM tool?
Doesn't this give can't flash on critical partitions error? Or am I missing something?
Related
Guys i have bricked MY mi3 16gb.
I was using Bitti opticancro build with extended partitiion.
as i want to go to miui v6. i flashed stock partition zip
Then i flashed miui stock recovery and tried to flash the miui latest rom
i forgot to rename the rom zip to update .zip so i couldnt insatll the miui rom.
the i tried to flash using fast fastboot mode but it is showing error as remote size too large.
now i am stuck with miui recovery and fastboot error.
pls help me to get back my phone.
If you can enter fastboot mode, then you can flash miui rom manually.
First unzip miui fastboot rom, place adb and fastboot files into the folder you just extracted. (ex. located in cancro_global_images_V6.4.3.0.KXDMICB_4.4_global\images)
And then press shift while in this folder to open terminal, type these one by one.
Code:
fastboot devices
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem1 NON-HLOS.bin
fastboot flash system system.img
fastboot flash system1 system.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash boot1 boot.img
fastboot flash userdata userdata.img[B] (optional, need backup first, but I recommended to flash this if you want to use gapps)[/B]
fastboot reboot
You're done!
Android ADB Fastboot files is given if you don't have one.https://www.dropbox.com/s/ndud98a4ek3fvxg/Android_ADB_FASTBOOT.zip?dl=0
Or you can just fastboot flash TWRP recovery and then flash whatever you want from USB or something...
1)Install CWM recovery
2) Download restore-stock partition zip file from here http://www.htcmania.com/showpost.php?p=17750021&postcount=144
3) Flash it.
4) Now get in fastboot mode.
5) Get fasboot images from MIUI Forums
6) Flash it via MiFlash or use command line given by 2nd comment
7) Grab a coffee and you will be on miui in no time
8) use miui
Edit: http://xiaomi.eu/community/threads/5-5-8.27542/page-8#post-246332
There is modified flash_all.bat for Mi2, i beleive same works for cancro.
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition" && exit /B 1
Add this line after getvar and before flash lines in flash_all.bat and then MiFlash it like usually.
Flash cwm via fastboot, use "fastboot flash recovery recoveryname.img" and don't use this title, its not completely bricked.
Never run stock recovery until u manage to flash a stockrom.. Better remember that.. Save twrp or cwm.. In my case, on last monday, on twrp, i've accidentally wipe internal storage.. Luckily got 6 type of rom in usb-otg..
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
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img
wedgehog said:
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img
Click to expand...
Click to collapse
with XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml at least for me dirty flash failed, rom didn't boot
did a backup of /data/ to external storage from TWRP with internal storage decrypted (had to boot TWRP from fastboot a couple of times before the decrypt password prompt were shown on boot of TWRP)
did also a backup of internal storage over MTP with TWRP to computer.
then flashed again with below commands, WHICH WILL ERASE INTERNAL STORAGE
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Thereafter successfull boot, reboot to flash mode, boot TWRP again, restore internal storage over MTP from TWRP, restore of data from backup to external storage which were made above
all apps and settings back, and on latest moto firmware.
any chance of capturing the delta OTA's to make them twrp-flashable?
Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
Would probably be doable as in almost all other devices in general and older motorola devices in particular have had that. I for one do not have the knowledge of how to do that (and not the time available even if I had that knowledge =) )
I can confirm that at least for me, a dirty flash like the one described in post 1 in this thread worked again with the latest OTA/firmware for RETEU - XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC, when written over the second latest (XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
I did however have trouble booting the latest twrp twrp-3.3.1-0-v5.1-lake-jlb from fastboot, phone rebooted after it was sent over adb boot instead of booting twrp it went straight back to fastboot. Tried many times with rebooting to phone home screen in between. But adb fastbooting the older twrp-3.3.0-lake worked straight away, and thereafter installing twrp-3.3.1-0-v5.1-lake-jlb with it's zip worked straight away.
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
SvenHee said:
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
Click to expand...
Click to collapse
Doesn't seem likely, date is 2009
For reference, here is the line where I found this url:
Code:
12-06 14:19:06.869 5831 14719 D OtaApp : UpdaterEngineHelper:applyPayload, applying payload with downloadUrl = https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/*lots-of-stuff*%3D offsetvalue = 9258 fileSize = 107713236
Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
It would be no problem to catch them and make them TWRP flashable. But it's strongly not recommended to do that!! Do an OTA-update only if your device is fully on stock! Otherwise the OTA-update will override incorrect blocks of your partitions and this could crash your entire system irreversible.
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?)
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Don't Lock your device bootloader.
1.) First of all you need
laptop,
Usb data cable,
Minimal adb & fastboot setup,
firmware.
MCT ofp extractor tool.
and Your device.
Download below files.
Firmware link:
https://rms01.realme.net/sw/RMX3081export_11_C.19_2022072820470000.zip
MCT OFP extractor tool:
https://drive.google.com/file/d/1-MgGdT9fxi2LtJ1DIOxLVSM67thj9EpG/view?usp=drivesdk
Minimal adb & fastboot setup:
https://ava4.androidfilehost.com/dl/OqBAMk5-7QCuTzL-IhX9ZA/1661345244/10763459528675595887/ADB+&+FASTBOOT.rar
2.) Extract the ofp file package by mct ofp extract tool.
3.) Request to unlock your device bootloader by in-deapth test apk, once approved then you can start deep testing and unlock bootloader.
4.) connect your device with laptop.
5.) Open minimal adb & fastboot terminal.
and flash this images files by below cmd.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash metadata metadata.img
fastboot flash opporeserve2 opporeserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
Note: Flash this only 3 super images
fastboot flash super super.0.c5548a43.img
fastboot flash super super.1.bbada0de.img
fastboot flash super super.2.1400563f.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
Your device will reboot to system.