Xiaomi is reputed for offering impressive devices with exceptional features at a fairly reasonable price. In fact, the latest offering from Xiaomi will definitely give several flagships a run for their money. Further, the device is also pretty impressive when it comes to the custom scene.
However, to get access to the mods and tweaks waiting for you, you’ll first have to root your phone via Magisk. If that’s exactly what you’re looking to do, this guide will be of great help to you. In this guide, you will get to know how to root your Xiaomi 13 Pro using Magisk Patched Init_Boot.
How to root your Xiaomi 13 Pro using Magisk Patched Init_Boot
Step 1: Install Android SDK
Firstly, you’ll need to install the Android SDK Platform Tools on your PC. It’s the official ADB and Fastboot binary offered by Google. You’ll need to download it and extract it to a convenient location on your PC.
Step 2: Enable USB Debugging and OEM Unlocking
To start off, you’ll need to enable Developer Options on your smartphone. Go to settings -> About Phone -> tap on build number 7 times -> return to Settings -> system -> advanced -> developer options -> finally enable USB debugging and OEM Unlocking.
Step 3: Unlock the bootloader
There is often an element of confusion regarding this step but to put it into perspective, you’ll need to unlock the bootloader on your device. Remember, unlocking the bootloader on your Xiaomi device will mean wiping off all the data on your phone and nullifying the device’s warranty.
Guide: How to Unlock bootloader on Xioami, Redmi and Poco Phones (MIUI Unlock Bootloader Guide)
Step 4: Download Xiaomi 13 Pro Firmware
Then, you’ll have to download the Fastboot ROM for your Xiaomi 13 Pro smartphone. Ensure that you’re downloading the same version that is currently installed on your smartphone. As far as the downloading source is concerned, you can get it by visiting the official MIUI site or a third-party website like Xiaomi Firmware Updater.
Step 5: Get Stock Init_Boot.img for Xiaomi 13 Pro
- To start off, you’ll have to download and install the 7ZIP software on your computer
- After that, right-click on the Fastboot ROM TGZ file before selecting Open With -> 7ZIP File Manager
- Once the extraction is done, you’ll get another file in TAR format
- Now, right-click on the TAR file before selecting 7ZIP -> Extract Here
- You’ll get all the extracted firmware files with the partition files that are present in the Images folder
- Head over to the Images folder and copy the init_boot.img and transfer the file to your device
Step 6: Patch Init_Boot using Magisk
- Download and install the Magisk app
- Launch it and tap on the Install button beside Magisk
- Then, you should choose “Select and Patch a File”
- Navigate to the stock init_boot file before selecting it
- Tap on the “Let’s Go” option at the top right
- The init_boot file will be patched and placed under the Downloads folder
- Transfer the file to the platform-tools folder on the PC
Step 7: Boot your device to Fastboot Mode
- Connect your phone to the PC via a USB cable
- Ensure that USB debugging is enabled
- After that, head over to the platform-tools folder, type in CMD in the address bar, before hitting Enter
- It’ll launch the Command Prompt
- Type in the following command in the CMD window for booting your device to Fastboot Mode
adb reboot bootloader
- Then, type in the below command to verify the Fastboot Connection
- If you’ve got a device ID followed by the fastboot keyword, the connection will be successful
Step 8: Root your device via Magisk Patched Init_Boot
- Type the following command in the CMD window for flashing the patched init_boot.img file –
fastboot flash init_boot magisk_patched.img
- Ensure that you’re replacing magisk_patched.img with the appropriate name of the patched init_boot.img file
- If this command didn’t work, you’ll have to manually flash the init_boot to both slots via the below command –
fastboot flash init_boot_a magisk_patched_boot.img fastboot flash init_boot_b magisk_patched_boot.img
- Your smartphone will boot to the rooted OS
- If this doesn’t happen, you should manually do this using the below command –