How To Guide [GUIDE][UNLOCK][ROOT] How to unlock bootloader, flash ArrowOS v11.0 ROM and root Xiaomi Poco X3 Pro

[Th3 Ant]

Ok, so w/ Magisk flashed, how are you obtaining the boot.img necessary for patching?

I do not flash Magisk .zip or .img - I'm installing normal .apk and use it to create patched .img using boot.img taken from ROM .zip file

If I flash .zip or flash patched .img, I can't do anything anyway since it bootloops

Flashing the magisk apk as zip will always fail as mentioned in the tutorial.

Also btw, you're not supposee to flash img in recovery. They usually to be flashed in fastboot/bootloader.

Just to reconfirm, did you flashed the patched boot.img after or before you attempted to flash magisk.zip?

Yes I know - I literally said 3 times already I tried everything - flashing img in fastboot/bootloader and since that didn't work (like 10 times) I tried something else (which was just "legacy way")

I clean flashed whole ROM like 3 times already too just to confirm there is nothing about magisk - I tried flashing patched boot.img using fastboot/bootloader on completely cleanly flashed ROM first time I read this whole tutorial

That's why I've asked for help with this since it didn't work with any of tested ROMs



What I found out tho, after flashing patched .img (and when it's bootlooped) I can use "magisk" command in shell - "su" probably works too but I think it needs confirmation on phone screen as it just hangs and waits for some action (which I can't do since all I see on phone is boot animation...)

 

[urbanman2004]

I do not flash Magisk .zip or .img - I'm installing normal .apk and use it to create patched .img using boot.img taken from ROM .zip file

If I flash .zip or flash patched .img, I can't do anything anyway since it bootloops

That's not what I asked. I asked "...how are you obtaining the boot.img necessary for patching?"
Can you give me a step-by-step process so I can understand, similar to how I laid out my instructions in this guide for you and everybody else to understand.

 

[Th3 Ant]

That's not what I asked. I asked "...how are you obtaining the boot.img necessary for patching?"
Can you give me a step-by-step process so I can understand, similar to how I laid out my instructions in this guide for you and everybody else to understand.

1. Download .zip with ROM ex. Arrow-v11.0-vayu-OFFICIAL-20210507-GAPPS.zip from respectable XDA thread
2. Unpack downloaded .zip
3. Copy "boot.img" from that unpacked .zip onto phone memory/external SD card
4. Install Magisk Manager apk
5. Open installed Magisk Manager, choose "Install" > "select file to patch"
6. Select previously copied boot.img
7. Magisk Manager will create patched boot.img which should be in "Downloads" folder
8. Flash that patched boot.img (which is in "Downloads" folder) using fastboot/bootloader


And here is where my adventure ends - after successful flash, rebooting to system just bootloops and to get it working again I have to flash boot.img again from step 3. using fastboot/bootloader

I can even make YouTube video if that necessary...

 

[urbanman2004]

1. Download .zip with ROM ex. Arrow-v11.0-vayu-OFFICIAL-20210507-GAPPS.zip from respectable XDA thread
2. Unpack downloaded .zip
3. Copy "boot.img" from that unpacked .zip onto phone memory/external SD card
4. Install Magisk Manager apk
5. Open installed Magisk Manager, choose "Install" > "select file to patch"
6. Select previously copied boot.img
7. Magisk Manager will create patched boot.img which should be in "Downloads" folder
8. Flash that patched boot.img (which is in "Downloads" folder) using fastboot/bootloader


And here is where my adventure ends - after successful flash, rebooting to system just bootloops and to get it working again I have to flash boot.img again from step 3. using fastboot/bootloader

I can even make YouTube video if that necessary...

So my followup to that is as follows:

1. How are you flashing/updating your phone: is it by way of OTA update or are you manually flashing (after downloading it from the dev's website)?
2. Is the boot.img you're extracting coming from the same version of firmware that is being used to update?
3. Magisk is no longer a "Manager" anymore; it's just "Magisk" according to the dev of the apk.
4. The patched boot.img resulting from you using Magisk will have nomenclature similar to "magisk_patched-23000_rauu0" which is the boot.img file you should be using.

I don't usually do 'tech support' over these kind of issues since I tend presume members on XDA in these threads are somewhat familiar w/ flashing ROMS b/c it should be basic common knowledge being on a site like this otherwise you should just stick w/ stock firmware. Make of it what you will.

 

[xelrix]

4. Install Magisk Manager apk

May i know where did you get your magisk?
Also, did you patched any disable dm-verity patch?

 

[Th3 Ant]

So my followup to that is as follows:

1. How are you flashing/updating your phone: is it by way of OTA update or are you manually flashing (after downloading it from the dev's website)?
2. Is the boot.img you're extracting coming from the same version of firmware that is being used to update?
3. Magisk is no longer a "Manager" anymore; it's just "Magisk" according to the dev of the apk.
4. The patched boot.img resulting from you using Magisk will have nomenclature similar to "magisk_patched-23000_rauu0" which is the boot.img file you should be using.

I don't usually do 'tech support' over these kind of issues since I tend presume members on XDA in these threads are somewhat familiar w/ flashing ROMS b/c it should be basic common knowledge being on a site like this otherwise you should just stick w/ stock firmware. Make of it what you will.

It's not my first time flashing custom ROM (you can just look at my signature)
It's just first time I have issues with flashing magisk as it was always working without any issues (even on other Xiaomi phone... Note 7 btw)

I don't even know anymore how I can explain to you what am I doing - already wrote same thing like 5 times in this thread...

1. No, I DO NOT use any OTA - I literally unlocked bootloader 2 days ago and today flashed ArrowOS straight from .zip using TWRP (which you even linked somewhere)
2. Yes, IT'S SAME ZIP - I DO NOT use any other version of ArrowOS zip apart from that mentioned previously. Boot.img is TAKEN OUT of that .zip
3. And what does that have in common with my issue? Magisk is magisk - it was magisk manager before and for me it will stay that way - APK can be renamed to .zip and it can be flashed... zip can be renamed to .APK and it can be installed like any other app...
4. Yes, that's the "patched boot.img" I was talking about for like 6 post now...

Tech support? Dude... You asked me about same thing for 5 posts now - maybe I am stupid but if I didn't know what I'm doing, I wouldn't even unlock and flashed anything...
I asked a single question - "why does magisk bootloops if I flash patched .img"... I even provided logcat for anyone interested and for who definitely know more than me - I think it wasn't you tho...

Thanks for help tho but I guess we won't find solution talking like this....

 

[Th3 Ant]

May i know where did you get your magisk?

Release Magisk v23.0 · topjohnwu/Magisk

This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...

github.com

Also tried canary as some people said it sometimes work but it didn't change anything

 

[xelrix]

Release Magisk v23.0 · topjohnwu/Magisk

This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...

github.com

Sorry for the long winded and repeated questions.

And yeah, canary isn't necessary. I would even suggest staying on stable unless theres specific things in canary that you want to use/test.

Another thing, did you patch any disable dm-verity patch during installation?
If you did, I suggest that you try skipping it for now if you did, just for trial sake.
Besides, magisk already have its own disable dm-verity solution.

If you did not, sorry im out of suggestions.

 

[Th3 Ant]

Sorry for the long winded and repeated questions.

And yeah, canary isn't necessary. I would even suggest staying on stable unless theres specific things in canary that you want to use/test.

Another thing, did you patch any disable dm-verity patch during installation?

Nope, just straight up used "Select and patch a file" option to generate patched .img
Then just flashed that using

fastboot flash boot <patched.img>

and rebooted - nothing more, nothing less - didn't use any other .zips, modules or anything like that...

 

[urbanman2004]

Release Magisk v23.0 · topjohnwu/Magisk

This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...

github.com

Also tried canary as some people said it sometimes work but it didn't change anything

Last time I checked, my guide said to use the "latest version of Magisk" which was Magisk v22.1 at the time, not canary ¯\_(ツ)_/¯

 

[urbanman2004]

Tech support? Dude... You asked me about same thing for 5 posts now - maybe I am stupid but if I didn't know what I'm doing, I wouldn't even unlock and flashed anything...
I asked a single question - "why does magisk bootloops if I flash patched .img"... I even provided logcat for anyone interested and for who definitely know more than me - I think it wasn't you tho...

Thanks for help tho but I guess we won't find solution talking like this....

I actually wanna help you, but look throughout this whole thread: nobody else is reporting having the same issue as you. You can bring up all the experience you have under your belt, but in the grand scheme of things, we all are able flash Magisk w/o issue. Maybe try following my guide to the 'T' next time and using Pbrb instead of TWRP.

 

[xelrix]

Its a stretch but for the boot.img flash, did you use fastboot (reboot bootloader) or fastbootd (reboot fastboot)?
Calling it a stretch because if you have twrp, you would get to twrp version of fastboot, which i dont think is working yet for vayu.

If everything else fail, im thinking your partitions might be somewhat broken.
I would suggest you download the latest miui fastboot rom for your region and use the flash_all.bat script (dont relock obviously)
Then redo everything.
As it seems, you're doing everything accordingly so there shouldn't be anything wrong.

Last time I checked, my guide said to use the "latest version of Magisk" which was Magisk v22.1 at the time, not canary ¯\_(ツ)_/¯

He linked the latest stable release, which is fine.

Edit:

Just to share, i initially used uberman2004 tutorial from unlocking bootloader till rom installation (installed miui eu rom though) EXCEPT installing magisk nor patching disable dm-verity patch.
It works fine.

But for arrowos (a month later), i decided to start clean.
1. Enable adb in dev option
2. Boot into fastboot ([adb reboot bootloader])
3. Run flash_all.bat script from miui global 12.0.6 fastboot rom (yes my vayu is global)
4. [Fastboot flash recovery recovery.img] (which is latest nebrassy's twrp)
5. [Fastboot boot recovery.img] (on hindsight, [fastboot reboot recovery] should be fine)
6. Install latest arrowos with gapps from my sd card (didn't cross my mind to just use otg)
7. Format data
8. Reboot to system
9. Dash through initial setup
10. Install mixplorer
11. Open up the arrow os file and extract the boot.img to the root of my sd card
12. Install magisk v23.0 stable that i got from github
13. Patched the boot.img ive extracted just now
14. Transfer the patched boot.img from my phone to the adb folder in my pc
15. [Fastboot flash boot *patched boot.img*]
16. [Fastboot reboot]

And im done.

Note that i never install any dm-verity patch nor have i tried installing many custom rom on my phone prior.

 

[pl1992aw]

Someone uploaded a patched
miui global 12.0.6.0 magisk patched boot.img

Source:
https://xdaforums.com/t/how-to-root-poco-x3-pro-miui-v12-0-6-0-rjumixm-global.4268449/post-84958155

According to the date and the Magisk update, the Magisk this person use most likely is v22.1

As there's no complaint afterward when people seem to have use it, it might be a working patched boot.img

You can risk and try, but your decision to trust it or not.

There's a tool quite easy to use on PC, and I have use it to flash TWRP recovery, boot TWRP and flash patched boot.img. So it's easier to use and doesn't really need to always check if the code you are typing is correct or not.

XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools

The only concern is whether you trust using this PC program or not. This tool is also listed in the INDEX thread. In virus total it's all clean.

Few things to rule out the issue:
1) Do you have microSD card in your device? In the past, some people have problems when having microSD in their devices to bootup or other issues. If you have microSD inserted, remove it to see if it quit the bootloop.

2) When you turn on adb debug in developer setting, it should have a pop up. There's an option like: Always allow from this computer. Did you have it checked? If you did not allow it/trust the device, you'll likely have issue when using fastboot and adb.

3) Use the latest adb platform-tools.

4) Reboot your PC. Sometimes there's problem with the PC, causing errors.

 

[Th3 Ant]

So yeah... finally fixed my Magisk issue

I've decided to completely start from scratch (again) and flashed MIUI Global (even tho my stock was EU) using recovery, then ArrowOS and used TWRP to flash Magisk 22.1 (yes, it's not latest).
It didn't bootloop this time so I've checked Magisk app and it showed that Magisk was installed. I've updated it from Magisk app (using direct install) and after reboot, everything was still working fine - no more bootloops etc.

Thanks everyone for helping - I probably should've done that at start when it didn't work but I was really tired setting everything every time after flashing...

 

[urbanman2004]

So yeah... finally fixed my Magisk issue

I've decided to completely start from scratch (again) and flashed MIUI Global (even tho my stock was EU) using recovery, then ArrowOS and used TWRP to flash Magisk 22.1 (yes, it's not latest).
It didn't bootloop this time so I've checked Magisk app and it showed that Magisk was installed. I've updated it from Magisk app (using direct install) and after reboot, everything was still working fine - no more bootloops etc.

Thanks everyone for helping - I probably should've done that at start when it didn't work but I was really tired setting everything every time after flashing...

See how going back to the drawing board and starting over does wonders? Lol . On a serious note, although I did initially implore you to do that multiple times in an effort to isolate the root cause of your issue, I am really glad that you were finally able to get things working. Enjoy your newly Magisk rooted Arrow OS flashed Poco X3 Pro .

 

[Th3 Ant]

See how going back to the drawing board and starting over does wonders? Lol . On a serious note, although I did initially implore you to do that multiple times in an effort to isolate the root cause of your issue, I am really glad that you were finally able to get things working. Enjoy your newly Magisk rooted Arrow OS flashed Poco X3 Pro .

Yeah... I did that one time but it didn't fix it so I tried again and somehow it worked this time.
Maybe it was issue with EU MIUI... or maybe not.

Anyway - it works now. Just last question (hopefully) - any idea why JamesDSP makes ringtones sound distorted? Media sound works without any problems but ringtone and notification doesn't...
If I uninstall module, everything goes back to normal.

Should I try with V4A?

 

[urbanman2004]

Yeah... I did that one time but it didn't fix it so I tried again and somehow it worked this time.
Maybe it was issue with EU MIUI... or maybe not.

Anyway - it works now. Just last question (hopefully) - any idea why JamesDSP makes ringtones sound distorted? Media sound works without any problems but ringtone and notification doesn't...
If I uninstall module, everything goes back to normal.

Should I try with V4A?

Your inquiry is out of scope for the purposes of this guide. Maybe try hollering at the dev here.
I previously had an issue related to a call recording app I use that was causing my audio output from the speakers to sound distorted so I ended up troubleshooting the issue on my own till I successfully found the root cause of the issue as it pertains to this post here. Not sure if it could be somewhat related, but other than that, you're better off googling for a resolution.

 

[Skelos]

Seems as though you may have also overlooked the following detail within my instructions since you're attempting to replace "Pbrb (test3)" with TWRP: "8. Download the unofficial Pbrb (test3) recovery file (PitchBlack Recovery Project 3.1.0 unofficial) by Alex Besida and copy it into the ADB install folder and rename it to "recovery.img"."

You have reason, man. I'm sorry. I heve to read with more brain. :-(
I have other doublt. You talk about of two commands:

9. Flash custom recovery file in CMD, run commands:

fastboot flash recovery "recovery.img"
fastboot boot recovery.img

but same file recovery.img is useful for recovery and boot? I expectacing two different files...

 

[pl1992aw]

You have reason, man. I'm sorry. I heve to read with more brain. :-(
I have other doublt. You talk about of two commands:

but same file recovery.img is useful for recovery and boot? I expectacing two different files...

What doubt do you have? Why expecting 2 different files?

fastboot flash recovery "recovery.img"

to overwrite the recovery

fastboot boot "recovery.img"

to boot the file eg. recovery

You might have mistaken with

fastboot flash boot "boot.img"

 

[Th3 Ant]

You have reason, man. I'm sorry. I heve to read with more brain. :-(
I have other doublt. You talk about of two commands:

but same file recovery.img is useful for recovery and boot? I expectacing two different files...

fastboot boot recovery.img

Means that it's gonna boot into recovery without "saving" - to save you have to include "flash" command (fastboot flash boot <image.img>)

This allows you to boot using some other image without actually writing it to that partition