• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][FASTBOOT]Xiaomi Mi A3 (laurel_sprout)

Search This thread

Typhus_

Senior Member
Jan 9, 2013
1,256
1,537
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
Hello!

On this thread we could keep a list of all fastboot ROMs that can be used to flash into Mi A3.

Version build number explained:

Example: 10.3.4.0.PFQMIXM

10.3.4.0 - Firmware version​
P - Android version (P-> Pie / Android 9).​
FQ - Smartphone model code (FQ = Xiaomi Mi A3).​
MI - Firmware build type (MI for Global | EU for Europe)​
XM - Firmware version code​


Global versions (PFQMIXM) or QFQMIXM):

device=laurel_sprout​
build_number=V12.0.11.0.RFQMIXM​
userdata_version=20210615.0000.00​

device=laurel_sprout​
build_number=V12.0.9.0.RFQMIXM​
userdata_version=20210506.0000.00​
device=laurel_sprout​
build_number=V12.0.8.0.RFQMIXM​
userdata_version=20210409.0000.00​


device=laurel_sprout​
build_number=V11.0.23.0.QFQMIXM​
userdata_version=20201124.0000.00​


device=laurel_sprout​
build_number=V11.0.22.0.QFQMIXM​
userdata_version=20201017.0000.00​


device=laurel_sprout​
build_number=V11.0.21.0.QFQMIXM​
userdata_version=20200917.0000.00​


device=laurel_sprout​
build_number=V11.0.20.0.QFQMIXM​
userdata_version=20200804.0000.00​


device=laurel_sprout​
build_number=V11.0.19.0.QFQMIXM​
userdata_version=20200717.0000.00​


device=laurel_sprout​
build_number=V11.0.16.0.QFQMIXM​
userdata_version=20200623.0000.00​


device=laurel_sprout​
build_number=V11.0.15.0.QFQMIXM​
userdata_version=20200507.0000.00​


device=laurel_sprout​
build_number=V10.3.16.0.PFQMIXM​
userdata_version=20200324.0000.00​


device=laurel_sprout​
build_number=V10.3.13.0.PFQMIXM​
userdata_version=20200116.0000.00​



device=laurel_sprout​
build_number=V10.3.9.0.PFQMIXM​
userdata_version=20191107.0000.00​


device=laurel_sprout​
build_number=V10.3.8.0.PFQMIXM​
userdata_version=20191012.0000.00​


device=laurel_sprout​
build_number=V10.3.4.0.PFQMIXM​
userdata_version=20190815.0000.00​


Europe versions (PFQEUXM or QFQEUXM or RFQEUXM):

device=laurel_sprout​
build_number=V12.0.7.0.RFQEUXM​
userdata_version=20210513.0000.00​

device=laurel_sprout​
build_number=V12.0.6.0.RFQEUXM​
userdata_version=20210415.0000.00​

device=laurel_sprout​
build_number=V12.0.5.0.RFQEUXM​
userdata_version=20210311.0000.00​
device=laurel_sprout​
build_number=V12.0.3.0.RFQEUXM​
userdata_version=20210129.0000.00​


device=laurel_sprout​
build_number=V11.0.10.0.QFQEUXM​
userdata_version=20201125.0000.00​


device=laurel_sprout​
build_number=V11.0.9.0.QFQEUXM​
userdata_version=20201019.0000.00​


device=laurel_sprout​
build_number=V11.0.8.0.QFQEUXM​
userdata_version=20200926.0000.00​


device=laurel_sprout​
build_number=V11.0.6.0.QFQEUXM​
userdata_version=20200817.0000.00​


device=laurel_sprout​
build_number=V11.0.5.0.QFQEUXM​
userdata_version=20200723.0000.00​


device=laurel_sprout​
build_number=V11.0.3.0.QFQEUXM​
userdata_version=20200611.0000.00​


device=laurel_sprout​
build_number=V11.0.2.0.QFQEUXM​
userdata_version=20200512.0000.00​


device=laurel_sprout​
build_number=V11.0.1.0.QFQEUXM​
userdata_version=20200424.0000.00​


device=laurel_sprout​
build_number=V10.3.17.0.PFQEUXM​
userdata_version=20200325.0000.00​


device=laurel_sprout​
build_number=V10.3.15.0.PFQEUXM​
userdata_version=20200220.0000.00​


device=laurel_sprout​
build_number=V10.3.14.0.PFQEUXM​
userdata_version=20200116.0000.00​


device=laurel_sprout​
build_number=V10.3.13.0.PFQEUXM​
userdata_version=20191211.0000.00​


device=laurel_sprout​
build_number=V10.3.12.0.PFQEUXM​
userdata_version=20191113.0000.00​


device=laurel_sprout​
build_number=V10.3.7.0.PFQEUXM​
userdata_version=20190814.0000.00​


A site with mirror links to all fastboot images released so far has been shared with us by @Codebucket. Thank him for this.

This SITE, by @yshalsager, has all download links for both Fastboot ROMs and Recovery packages. Great job. Don't forget to thank him for this.


NOTES:

The scripts included on the *.bat and *.sh files assume that your device is currently on slot a. If it really is, they will work with no issues. If it's not then you have 3 choices (choose only one of them):

  1. Before executing any of the bat (or sh if you're using Linux), change your active slot to a through fastboot (fastboot --set-active=a or fastboot set_active a)
  2. Open the *.bat (or *.sh) file that you want to run and, before the line where you see fastboot %* reboot, add a line with fastboot %* set_active a (on linux fastboot $* set_active a) and save the file.
  3. Open the *.bat (or *.sh) file that you want to run and find "system_other.img". Replace that with system.img and save the file.

Cheers!
 
Last edited:

Displax

Senior Member
Jan 19, 2015
247
724
25
Kyiv
My phone is stuck at erasing after flashing this stock rom
Becouse this fastboot images contain mistakes in *.bat scripts. It is need to set active slot "A" after flashing or flash system.img to slot "B" instead of "system_other.img".
So, here is pack of fixed *.bat.
 

Attachments

  • flash.zip
    3.4 KB · Views: 6,917

Typhus_

Senior Member
Jan 9, 2013
1,256
1,537
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
Becouse this fastboot images contain mistakes in *.bat scripts. It is need to set active slot "A" after flashing or flash system.img to slot "B" instead of "system_other.img".
So, here is pack of fixed *.bat.

Attention, the system_other.img file exists. And the scripts are flashing them to system_b (system partition on slot b). Not really sure what is this system_other.img but I guess it could be a dummy system.img just to not leave it blank.

Anyway, there isn't really a command to change slot to a...one could always perform that manually...but still. This is weird.

The stuck on erasing is not normal, I think.
 
  • Like
Reactions: ps000000

drozo8o8

Senior Member
Mar 2, 2018
95
17
Attention, the system_other.img file exists. And the scripts are flashing them to system_b (system partition on slot b). Not really sure what is this system_other.img but I guess it could be a dummy system.img just to not leave it blank.

Anyway, there isn't really a command to change slot to a...one could always perform that manually...but still. This is weird.

The stuck on erasing is not normal, I think.

Is there a way to flash over edl yet ? like I remember getting some programmer files for the chip.
 

XaviBest

New member
Mar 7, 2013
3
4
Attention, the system_other.img file exists. And the scripts are flashing them to system_b (system partition on slot b). Not really sure what is this system_other.img but I guess it could be a dummy system.img just to not leave it blank.

Anyway, there isn't really a command to change slot to a...one could always perform that manually...but still. This is weird.

The stuck on erasing is not normal, I think.

Just add this line fastboot %* set_active a before fastboot %* reboot and script will work.
 

drozo8o8

Senior Member
Mar 2, 2018
95
17
OKay so after flashign this and getting back to stock recovery where it did ask me to factory reset im getting an error whle formatting data

e:/sbin/mkfs.f2fs failed with status 255
e:format volume: failed /sbin/mkfs.f2fs on dev/block/bootdevice/by-name/userdata: no such file or directory
 

Typhus_

Senior Member
Jan 9, 2013
1,256
1,537
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
OKay so after flashign this and getting back to stock recovery where it did ask me to factory reset im getting an error whle formatting data

e:/sbin/mkfs.f2fs failed with status 255
e:format volume: failed /sbin/mkfs.f2fs on dev/block/bootdevice/by-name/userdata: no such file or directory
What? That's strange...the recovery does not "see" the userdata partition... That's not good.

I think that in EDL mode you could fix that. But I think you need the correct "prog_firehose" file for it to work.

I'm sorry I can't help you that much but it seems your userdata partition, or better yet, the symlink to your userdata partition is missing.

Enviado do meu Mi A3 através do Tapatalk
 

Top Liked Posts