[Nubia Red Magic 9 Pro] Arxgxmi:
Hello everyone, I am making this guide for the people that are either new to rooting or simply forgot how to ever since the old days, this thread will not cover already covered topics, I will more so link to them and add to them if I ran into any issues personally, you can PM me about your issues and I will see to it that they, and a fix, gets added here if need be.

We start off with @mvikrant97 's bootloader unlock thread, he doesn't have it in the required software but you need ZADIG too ideally before starting.

Alternatively you can use @cuynu 's guide for unlocking under linux. This guide will focus on the windows enviroment as I lack experience using the linux method.

YOU MAY RUN IN ANY OF THE FOLLOWING ISSUES: Messing up the flashing ( most likely disconnecting USB while flashing anything to the device OR flashing bad .img files to your partitions) can lead to a bootloop or the ZTE MemoryDump Mode, I will cover this at the end, linking to the appropriate threads.

During the bootloader unlock, you want to pull init_boot_a and init_boot_b from your phone and once back inside the operating system, install magisk, open it up and tap the top install button, select your init_boot_a and init_boot_b and you may want to note down which is which, drag the files to your PC and do

adb reboot bootloader

to put your phone into fastboot mode. Once in fastboot, you want to do

fastboot flash init_boot_a [path to your magisk file]
fastboot flash init_boot_b [path to your magisk file]

Once done, you can just reboot the device back into the OS and magisk may ask you to complete further set up.

READ THIS IF YOU CARE ABOUT YOUR PHONE WORKING ALMOST ENTIRELY AS INTENDED:

Once in magisk make sure to go to the app settings, enable the option for hiding the app, turn on zygisk, enable systemless hosts, get safetynet/play integrity fix module for magisk, enable deny list, configure deny list and just add all google apps in there. This will fix 90% of your root-caused issues.

This fixed G-Pay/Google Pay for me and it worked flawlessly.

IF YOU USE BANKING APPS OR ANY APP THAT DOES NOT WORK UNDER ROOT:

Just try adding it to the deny list, try opening it again and see if it works, if it doesn't just work right after attempt restarting.

If it still doesn't work maybe someone else can help you with that. As this was an instant fix for mine.

ISSUES I RAN INTO AND HAD TO DEAL WITH:

I had issues with adb working, just generally wouldn't do anything, it turns out it is because I was right clicking the folder and doing "open in terminal" like this:

View attachment 6114311

The terminal would open and I'd have a PS in front of the CLI line, like this:

View attachment 6114312

and for some reason, nothing worked for me within powershell (PS), so I had to copy path to my adb.exe folder and do cd (path) inside admin cmd.

View attachment 6114313

I had issues with fastboot not working due to the wrong driver being assigned to the device (or lack of fastboot driver).

I used this very helpful, easy to understand article, downloaded the fastboot driver, installed it as instructed within the article and everything worked just great.

IF AT ANY POINT FASTBOOT COMMANDS DO NOT WORK YOU EITHER HAVE TO REPEAT THIS STEP OR REPEAT THE BOOTLOADER UNLOCK LINKED ABOVE.

I tried reflashing original init_boot_a/b and it softbricked my phone, put me in ZTE MemoryDump Mode, it was very easily fixable like a lot of similar issues you may encounter, so the first step is to NOT PANIC, everything will be alright, just follow along.

I will give what I believe to be the easiest fix as this is what I had done, you will need:

1. Qualcomm USB Driver

2. QPST

3. Global EDL (courtesy of @ErdilS )

4. Firehose also attached in the thread linked above.

I also recommend reading the thread linked above for a little more insight into how to do this, but it is very simple as you will see.

I will be using this image provided by @Mr nerd in the thread above to be able to explain things.

First, you want to make sure the program is set up before touching your phone at all, it's just good practice otherwise you might trigger an error along the lines of "SAHARA FAIL" due to timeout. You have 30 seconds to press the download button once your phone gets into EDL (Emergency Download Mode).

To set everything up, you want to select the following: Flat build, Select programmer and get to the firehose file you downloaded, Select flat build and use the build you downloaded right before the firehose file, click load xml next and you can actually ctrl+click here to select all of them in order, make sure it's in order, from 0 to 5, do the same for the patch files, then make sure your storage type is UFS, once all of the above is done, you may plug in the phone if it is not already, reboot it and hold volume up + down just like in the bootloader unlock guide, you should hear a usb connect sound and the screen should be black, the download button should light up, if it does not go to "Select port" and select your phone, click the download button ASAP and wait until the program says it is done. Once done you should be able to get back into the OS.

FOR PEOPLE THAT ARE ON EU ROM AND WANT TO RESET DEVICE TO EU ROM:

THIS WILL TAKE UPWARDS OF 30 MINUTES AS YOU HAVE TO FLASH MORE THAN 38 PARTITIONS BY HAND UNLESS YOU USE MACROS TO NOT HAVE TO TYPE

fastboot flash

OR EDIT PRIOR COMMANDS.

You can do this using fastboot. either download the EU OTA update from redmagic's website and dump it yourself using payload-dumper-go, or alternatively download my dump from here.

Do

adb reboot bootloader

then in fastboot do

fastboot reboot fastboot

to get into fastbootd, inside fastbootd you have to do

fastboot flash [partition name] [path to partition name.img]
fastboot flash [partition name_b] [path to partition name.img]

You have to do this for all .img files in the dump, as you do not know which partitions have a "_b" variant or not, I also did not write them down because trust me when I say that most of them do.

Once you are fully done with this navigate the recovery screen you are inside while this is happening and reset your phone (wipe data button inside the menus), after rebooting your phone should have the EU ROM.

I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU CAUSE YOUR DEVICE, I STILL WOULD NOT RECOMMEND THIS DEVICE FOR ANYONE THAT WANTS A ROOTED PHONE OR A PHONE THAT CAN MAKE USE OF CUSTOM OPERATING SYSTEMS.

I'D LIKE TO THANK @mvikrant97 , @Mr nerd , @ErdilS , @cuynu FOR ALL THEIR HELPFUL THREADS.

I WANT TO GIVE SPECIAL THANKS TO @BotchedRPR AND ESPECIALLY @DarkestSpawn for having helped me the most.

IF YOU HAVE ANY QUESTIONS REGARDING THIS THREAD YOU MAY PM ME AND I WILL MAKE APPROPRIATE CHANGES OR SIMPLY ANSWER YOUR QUESTION(S).