How to Root Infinix Zero X Neo and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all your data before performing these steps. It’s also important to understand that not following the steps correctly may result in a bricked phone so make sure you know how to recover your phone back to its original state in case you end up in a situation like that.

Furthermore, Magisk may cause issues with a few banking and payment-related apps so if those are absolutely vital to you, proceed with caution.

 

How to Unlock the Bootloader on Infinix Zero X Neo

Unlocking your bootloader is the first step towards rooting your Android phone and installing custom ROMs. It’s also the place where most people run into trouble—not because it’s especially difficult, but because phone manufacturers and network carriers don’t want you to unlock it. It’s not unlike Android rooting, another superuser practice that manufacturers discourage. Here’s how to do it.

note:Some phones require an additional unlock code from the manufacturer to unlock the bootloader.

How to Enable OEM Unlock

Before you can actually unlock your phone, you need to enable the OEM unlocking developer feature in Android.

1.Open the Settings app on your device.

2.Select About phone.

3.Near the bottom of the screen, you see the Build number. Tap it seven times to enable the developer options. You may be prompted to enter your password to continue.

4.Go back and choose System in the Settings app.

5.Locate and select Developer options.

Developer options are likely in the Advanced section. Tap the down arrow to open those options.

6.Find the OEM unlocking option, and toggle the switch on.

7.Scroll down and locate USB debugging. Toggle the switch on.

How to Install Android Tools view

How to use fastboot to unlock

1.Plug your phone into your computer with its USB cable.

2.In the terminal (or Command Prompt), run the following command to connect your phone.

adb devices

3.You’ll see a message requesting access on your phone. Check the box to always allow the connection, and confirm.

4.You’ll see a message requesting access on your phone. Check the box to always allow the connection, and confirm.

5.Run the following command to reboot your phone into the bootloader.

adb reboot bootloader

6.Wait for your phone to reboot. You’re now ready to unlock with Fastboot. On newer devices and Google devices, run the following command:

fastboot flashing unlock

On devices that require a code—or, possibly, some older devices—run this command:

fastboot oem unlock 

Omit the code, if you don’t need one.

You may be asked to confirm. Do so.

After your see a confirmation message that your bootloader is unlocked, you can reboot it with Fastboot.

fastboot reboot

As your phone reboots, you’ll probably see a warning that your bootloader is unlocked, and that it isn’t secure. Continue booting. Your bootloader is unlocked, and you’re ready to continue on to flashing custom recovery and rooting your device.

Step 1: Identifying the type of boot image

Download  Magisk 

After installing, open the Magisk app. You should see a screen like this:

Now, we need to note down the values of the following parameters:

Ramdisk
A/B
SAR

Step 2: Locating the boot image

In order to patch the boot image for your device, you need to extract it from the official firmware packages. In case you’re using a custom ROM like LineageOS, the flashable ZIP file contains the boot image.

Case I: You have access to the recovery-flashable ZIP file

If you have a device that still uses the A-only partition scheme, you can find the ‘boot.img’ right inside the recovery-flashable ZIP file. Just extract it using a suitable archiver program.

However, if your device utilizes the A/B partition scheme, then the boot image and other partition images are further packed inside a file named payload.bin as shown below.

Known as ‘payload-dumper-go’, this fork even allows end-users to extract a single partition image without unpacking the whole payload.bin, which is particularly useful for this usage scenario.

First, use the -l parameter to list the partition images inside the payload.bin

payload-dumper-go -l payload.bin

Then use the -p parameter with the name of the boot image (commonly stored as “boot”) to extract it.

payload-dumper-go -p boot payload.bin

Step 3: Patching the boot image

Now we have the boot image in hand, we should proceed with the patching part.

Case I: The value of the “Ramdisk” parameter is “Yes”

Copy the boot image to your device. In fact, you can patch it on a different Android device than the target one, but you need to install the Magisk app on the secondary device as well.

Press the Install button on the Magisk card.

Choose Select and Patch a File under method, and select the stock boot image.

The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB

adb pull /sdcard/Download/magisk_patched_[random_strings].img

Flash the patched boot image to your device. For most devices, reboot into Fastboot mode and flash with the following command:

fastboot flash boot /path/to/magisk_patched.img

Reboot and enjoy Magisk!

Case II: The value of the “Ramdisk” parameter is “No”

In this case, you need to locate the recovery.img file from the factory image of your device instead of boot.img file. This is because Magisk needs to be installed in the recovery partition, which means you’ll have to reboot to the recovery mode every time you want to access Magisk.

Copy the recovery image to your device (or a secondary device with the Magisk app installed).

Press the Install button on the Magisk card.

Choose Select and Patch a File under method, and select the stock recovery image.

The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB

adb pull /sdcard/Download/magisk_patched_[random_strings].img

Flash the patched recovery image to your device. For most devices, reboot into Fastboot mode and flash with the following command:

fastboot flash recovery /path/to/magisk_patched.img

Reboot.

At this stage, there are three possible scenarios:

Power up normally: You’ll end up with no Magisk.

Recovery Key Combo → Splash screen → Release all buttons: The system should boot with Magisk.

Recovery Key Combo → Splash screen → Keep pressing volume up: To access the stock recovery mode

Now you have Magisk installed, it’s time to try out some nice Magisk Modules. You can find lots of modules for specific purposes, and since Magisk gives you root access, you can even install some of the best apps for rooted devices. So install whichever apps and modules you like and get tweaking!

Related Posts

How to Root Infinix Note 10 Pro NFC and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all…

How to Root Infinix Hot 10i and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all…

How to Root Infinix Zero X and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all…

How to Root Infinix Zero X Pro and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all…

How to Root Infinix Hot 11 and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all…

How to Root Infinix Hot 11s and Unlock Bootloader

Disclaimer: Unlocking the bootloader will wipe all the data on your smartphone and in some cases, may even void your warranty. It’s advisable to back up all…

Leave a Reply

Your email address will not be published. Required fields are marked *