[GUIDE] [ROOT] [MAGISK] How to Root Mi A3 with MAGISK without TWRP

[Typhus_]

Hello!

There's a guide already on XDA that covers this matter but in a general way and for all devices. That guide was based on the general info you may find on the original installation guide by @topjohnwu. So, all credits go to him.

Anyway, since there ins't a TWRP Recovery for Mi A3 (yet) and since I believe that many of you don't know about this, Iv'e decided to share here the steps I've done in order to root Mi A3.

NOTE: Now that we already have a working TWRP available for Mi A3, to root it you can now simply follow THESE steps after unlocking the bootloader.​

​

The guide present on this thread, of course, works as well, so I'll leave it here for those of you who don't want to permanently install TWRP to your device.​

1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:

• Enable developer options
• Enable the "OEM unlocking" option
• Enable USB debugging
• Have both adb and fastboot, from SDK Platform Tools available on your PC
• Connect your phone to your PC using the USB cable and run the following commands:

adb devices

(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)​

adb reboot bootloader

(so your phone will reboot into fastboot mode)​

fastboot flashing unlock

(after rebooting, boot the phone again into fastboot mode)​

fastboot flashing unlock_critical

(for full unlock)​

2 - Download Mi A3 stock boot.img that you may find later on this post, that matches your current build.

• Copy the boot.img to your phone internal (or external) memory
• Leave a copy of it on your PC (on the same folder you have adb and fastboot...we never know if we don't need to use it again in the future...you know, to restore the stock boot.img, aka revert to stock...)

If, for your current build, there isn't a stock boot.img released yet, you may get one yourselves. How? READ THIS.​

​

​

EU Build boot images:​

---Android 9---​

​

For all of you currently on 10.3.7.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 10.3.8.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 10.3.9.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 10.3.11.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 10.3.12.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 10.3.14.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 10.3.15.0 (EU) build, you may download stock boot.img HERE.​

​

---Android 10---​

​

For all of you currently on 11.0.1.0 (EU) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)​

​

For all of you currently on 11.0.2.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 11.0.3.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 11.0.5.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 11.0.6.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 11.0.8.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 11.0.9.0 (EU) build, you may download stock boot.img HERE.​

​

---Android 11---​

For all of you currently on 12.0.2.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.3.0 (EU) build, you may download stock boot.img HERE. (thanks to @lucoz )​

​

For all of you currently on 12.0.5.0 (EU) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.6.0 (EU) build, you may download stock boot.img HERE.​

Global Build boot images:​

---Android 9---​

​

For all of you currently on 10.3.8.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)​

​

For all of you currently on 10.3.14.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)​

​

---Android 10---​

​

For all of you currently on 11.0.7.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)​

​

For all of you currently on 11.0.11.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)​

​

For all of you currently on 11.0.14.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)​

​

For all of you currently on 11.0.15.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 11.0.22.0 (Global) build, you may download stock boot.img HERE.​

​

---Android 11---​

​

For all of you currently on 12.0.3.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.4.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.6.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.7.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.8.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.9.0 (Global) build, you may download stock boot.img HERE.​

​

For all of you currently on 12.0.11.0 (Global) build, you may download stock boot.img HERE.​

3 - Download latest Magisk Manager from HERE and install it on your phone

4 - Open Magisk Manager App and press:

• Install
• Install (again)
• Select and Patch a File
• Browse to the path where you saved stock boot.img and select it

Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img

5 - Copy the patched boot image from your device to your PC

• Store it on the same folder where you have adb and fastboot
• If you can’t find it via MTP, you can pull the file with ADB

adb pull /sdcard/Download/magisk_patched.img

6 - Uninstall Magisk Manager App from your phone (I'm not sure if this is really needed but I've done it anyway...)

7 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)

adb reboot bootloader

fastboot erase boot

fastboot flash boot magisk_patched.img

fastboot continue

(THIS IS IMPORTANT! USE CONTINUE INSTEAD OF REBOOT! You have been warned!!!)

8 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!

9 - Enjoy!


All credits goes to topjohnwu and it's incredible work with Magisk.

I cannot be responsible if you turn your phone into a brick. Your phone, your choices, your responsibility!

 

[sirzarmo]

Thanks!

Been waiting for someone to create a cannonical guide of how to root this phone.
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Also one would assume it disables the OTA update feature, probably better write it.

 

[Displax]

Saw someone with magisk who had WiFi problems, WiFi works ok you?

WiFi problems appears when you flash boot not from your ROM build. Use only the same boot.img to the build number of ROM.

Also one would assume it disables the OTA update feature, probably better write it.

It is. But you can still update via Magisk if you don`t touch system partitions. Else - flash manualy.

 

[seburton]

Wow,
Thank's a lot!
As you said, I didn't know this way to root a device.

 

[Typhus_]

Saw someone with magisk who had WiFi problems, WiFi works ok you?

That someone was me. But, I believe that happened because I've used boot.img from 10.3.4.0 branch on GitHub (instead of using boot.img from 10.3.5.0 branch) and, also, I've used "fastboot reboot" command instead of "fastboot continue". As soon as the 10.3.5.0 branch appeared online I've decided to test this method again and it worked, that's why I've decided to share this with all community.

Also one would assume it disables the OTA update feature, probably better write it.

I don't think it will disable OTA feature. Probably, as soon as a new OTA comes out it will be installed on Slot A (because up until now there's only been one update and it was installed on slot B...so everyone should now be on firmware V10.3.5.0 running on Slot B). So, if I'm not mistaken, the "worst" thing that could happen is to lose root (since the update will be installed on Slot A and boot.img on that Slot is still the stock one).

Cheers!

 

[sirzarmo]

Cheers!

Why thank you dear, I'll root now if so.

 

[Typhus_]

Hello!

Well, in fact, this method breaks OTA. It downloads but it doesn't install.

My guess is we need to flash stock boot.img and then apply the OTA update and then patch the new boot.img again.

I've noticed a new boot.img on GitHub today, hopefully it will be the correct one.

 

[Displax]

Hello!
Well, in fact, this method breaks OTA. It downloads but it doesn't install.

You can simply follow this guide, if you do not touch system partitions.
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#devices-with-ab-partitions

 

[Typhus_]

Tried it already. It ain't possible because of 2 reasons:

1 - The supposly boot.img backup doesn't exist. Probably Magisk only does it if installed through TWRP and not by patching boot.img

2 - The OTA package fails to install. "A problem has occurred"...while trying to initiate the install.

Enviado do meu Mi A3 através do Tapatalk

 

[ErriK89]

When do you think twrp will be released for mi a3?

 

[drozo8o8]

okay so I installed FDE magisk module now my phone is stuck at the bootscreen. Someone got a stock rom for me ?

 

[Typhus_]

You can change slot through fastboot. It will erase all user data (factory reset) but it's better than the phone not booting.

The other possible solution, I've sent you a PM (because external link).

fastboot --set-active=a (or b if you're now on a)

Enviado do meu Mi A3 através do Tapatalk

 

[drozo8o8]

An offcial stock rom wouldve fixed my problem in no time. I changed the partition and got to a menu where I could chosse to factory reset but its been sitting on formatting data for like half hour...

 

[Typhus_]

An offcial stock rom wouldve fixed my problem in no time. I changed the partition and got to a menu where I could chosse to factory reset but its been sitting on formatting data for like half hour...

It should be quite fast...guess you're out of luck for the time being my friend.

By the way, you've used fastboot reboot or fastboot continue after changing slot?

It should be fastboot reboot

Enviado do meu Mi A3 através do Tapatalk

 

[drozo8o8]

all i need is a proper flash all.bat since oyu gave me the OTA update link with a payload.bin which I extracted with payload_dumper

 

[Displax]

Tried it already. It ain't possible because of 2 reasons:
1 - The supposly boot.img backup doesn't exist. Probably Magisk only does it if installed through TWRP and not by patching boot.img

Manualy patch boot.img in MM and you'll get backup.

 

[Crosstyan]

This method is useful in Mi CC 9e. Thx

 

[Patrici0]

hello, install v10.3.5.0 over v10.3.7.0, now I don't have wifi and the sound does not work, instructions to fix it please ?, I am using the google translator to write here, thanks

 

[Typhus_]

You'll have to change slot and boot on that slot. You'll lose all your user data but the phone will boot ok and receive latest OTA. Either that or you have to wait for someone to dump you a stock 10.3.7.0 boot.img in order to fix those issues. On GitHub there isn't a boot.img for latest build yet.

Enviado do meu Mi A3 através do Tapatalk

 

[Patrici0]

You'll have to change slot and boot on that slot. You'll lose all your user data but the phone will boot ok and receive latest OTA. Either that or you have to wait for someone to dump you a stock 10.3.7.0 boot.img in order to fix those issues. On GitHub there isn't a boot.img for latest build yet.

Enviado do meu Mi A3 através do Tapatalk

Fixed, THANKS YOU very much