How To Guide Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro

[Nocturne Seigneur]

is there any way to unlock bootloader without enable OEM unlock in developer settings?

My device is stuck now, can't access settings, can't get past google account setup

 

[bs3pro]

is there any way to unlock bootloader without enable OEM unlock in developer settings?

My device is stuck now, can't access settings, can't get past google account setup

No. Just format data, start over.

 

[Nocturne Seigneur]

the thing is... after wipe data same thing happened, nothing is solved, it just stuck here

 

[adwinp]

Can someone with the device, with a (re)locked bootloader, please check & confirm, whether the following process works:
1: delete all fingerprints & disable unlocking via fingerprint (remove screenlock altogether or via PIN only)
2: unlock the bootloader via:

fastboot oem nubia_unlock NUBIA_NX669J

Please pay attention as this is different from the generic fastboot flashing unlock
3: enable unlock via fingerprint & report if the fingerprint sensor works, else, the issue with calibration persists.

 

[bs3pro]

Can someone with the device, with a (re)locked bootloader, please check & confirm, whether the following process works:
1: delete all fingerprints & disable unlocking via fingerprint (remove screenlock altogether or via PIN only)
2: unlock the bootloader via:

fastboot oem nubia_unlock NUBIA_NX669J

Please pay attention as this is different from the generic fastboot flashing unlock
3: enable unlock via fingerprint & report if the fingerprint sensor works, else, the issue with calibration persists.

Worth a shot, but I wouldn't expect anything different.

 

[dana8h]

I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!

Youtube Video Tutorial:

For all those websites that claim the RM6 can be rooted with Kingroot, Kingoroot, iRoot, SuperSU... They are MISLEADING you into downloading their software. In other words, they are full of BS and you should INGORE them at all costs as Magisk is the ONLY proper way to root the RM6.



DO NOT USE KINGROOT, iROOT, KingoROOT, or ANY OTHER THIRD-PARTY ROOTING TOOLS PLEASE!! They steal your DATA and sell it. Magisk does not steal anything.​

This procedure will require a wipe of your data.. TWICE! I'll explain why.

When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.

However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.

Requirments


1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!






Here are the steps!


​

1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"

2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip

3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:

Extract Android OTA Payload.bin File using Payload Dumper Tool

Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.

www.thecustomdroid.com

I ended up Downloading Termux from the playstore and extracting it with python on my phone.

When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!

4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.

Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.

5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop

6. Type fastboot flash boot magisk_patched.img

7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

8. From the bootloader, reboot into your recovery and perform another factory reset!

9. Reboot the phone and voila! You now have root access!



Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!

So far I've installed the Xposed Framework and some Magisk modules. All seems to work really well.

Happy Modding!

​

Thanks for sharing rooting
but i need TWRP for Redmagic 6 NX669J ?
if available please tellme?

 

[SpongeBobbbb]

Can someone with the device, with a (re)locked bootloader, please check & confirm, whether the following process works:
1: delete all fingerprints & disable unlocking via fingerprint (remove screenlock altogether or via PIN only)
2: unlock the bootloader via:

fastboot oem nubia_unlock NUBIA_NX669J

Please pay attention as this is different from the generic fastboot flashing unlock
3: enable unlock via fingerprint & report if the fingerprint sensor works, else, the issue with calibration persists.

I had done this with RM5G
but when try to unlock with RM6 pro
it shows that

fastboot oem nubia_unlock NUBIA_NX669J FAILED (remote: 'unknown command') fastboot: error: Command failed

 

[bob24260]

I used simple fastboot flashing unlock on mine and it worked fine. No adverse effects on fingerprint or anything else.

 

[adwinp]

I used simple fastboot flashing unlock on mine and it worked fine. No adverse effects on fingerprint or anything else.

Which version of the firmware did you execute this action?
Most users in the past confirmed the fingerprint scanner would stop working after unlocking the BL, which would mean that this behaviour got changed in a recent update.

 

[bob24260]

Which version of the firmware did you execute this action?
Most users in the past confirmed the fingerprint scanner would stop working after unlocking the BL, which would mean that this behaviour got changed in a recent update.

4.1.2. was the software I used. I had the US or as it's more commonly known as, Global version. I've not suffered any ill effects. I've unlocked, relocked and unlocked again with zero bad consequences.

 

[bob24260]

Which version of the firmware did you execute this action?
Most users in the past confirmed the fingerprint scanner would stop working after unlocking the BL, which would mean that this behaviour got changed in a recent update.

This is a screen recording of my fingerprint working. I'll be glad to answer any other questions you might have.

Screen Record_2021-05-09-15-41-29.mp4

drive.google.com

 

[adwinp]

This is a screen recording of my fingerprint working. I'll be glad to answer any other questions you might have.

That's great news, thanks for taking the effort in sharing the screenrecording!
I do have 1 request - can you please flash the latest PHH GSI & report if you're able to boot; if this is the case, whether the fingerprint works as well?
Once you download the image, you can flash it via fastboot (after uncompressing it with 7zip):
fastboot flash system downloaded_file.img
You will also probably need to factory reset to avoid bootloops:
fastboot -w

Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.

v4.12 is the same build you based your instructions on - maybe this was fixed with the monthly security update?
Have you applied any OTA since? If you did, & since you encountered issues with the fingerprint sensor, would you be in a measure of trying relocking/unlocking again, & confirming whether the fingerprint sensor works for you after rooting?

 

[bob24260]

That's great news, thanks for taking the effort in sharing the screenrecording!
I do have 1 request - can you please flash the latest PHH GSI & report if you're able to boot; if this is the case, whether the fingerprint works as well?
Once you download the image, you can flash it via fastboot (after uncompressing it with 7zip):
fastboot flash system downloaded_file.img
You will also probably need to factory reset to avoid bootloops:
fastboot -w


v4.12 is the same build you based your instructions on - maybe this was fixed with the monthly security update?
Have you applied any OTA since? If you did, & since you encountered issues with the fingerprint sensor, would you be in a measure of trying relocking/unlocking again, & confirming whether the fingerprint sensor works for you after rooting?

I can give all this a go later this evening. I'm currently out with wife for Mother's day and I'll have to wait until I get home. Glad to help any way I can.

 

[bob24260]

That's great news, thanks for taking the effort in sharing the screenrecording!
I do have 1 request - can you please flash the latest PHH GSI & report if you're able to boot; if this is the case, whether the fingerprint works as well?
Once you download the image, you can flash it via fastboot (after uncompressing it with 7zip):
fastboot flash system downloaded_file.img
You will also probably need to factory reset to avoid bootloops:
fastboot -w


v4.12 is the same build you based your instructions on - maybe this was fixed with the monthly security update?
Have you applied any OTA since? If you did, & since you encountered issues with the fingerprint sensor, would you be in a measure of trying relocking/unlocking again, & confirming whether the fingerprint sensor works for you after rooting?

I apologize for my tardiness in replying. Late night out. I restored my device to stock via flashing 4.1.2 over local update and relocked the bootloader. I then rerooted by patching boot with Magisk. Once I was up and running I checked fingerprint again and lo and behold my ability to use fingerprint was gone. I don't know what changed in the interim but the ability to use fingerprint was gone. I restored stock once more and relocked the bootloader then my fingerprint was back. Ive tried reproducing my initial steps to see if I'd done anything different to allow me to keep fingerprint and seems my ability to keep it after unlock is gone. As far as flashing a GSI, I believe I'm going to abstain from trying that until a suitable restore tool is available. Ive pushed my luck too far as it is and I don't want to end up with a $700 paperweight.

 

[adwinp]

I apologize for my tardiness in replying. Late night out. I restored my device to stock via flashing 4.1.2 over local update and relocked the bootloader. I then rerooted by patching boot with Magisk. Once I was up and running I checked fingerprint again and lo and behold my ability to use fingerprint was gone. I don't know what changed in the interim but the ability to use fingerprint was gone. I restored stock once more and relocked the bootloader then my fingerprint was back. Ive tried reproducing my initial steps to see if I'd done anything different to allow me to keep fingerprint and seems my ability to keep it after unlock is gone. As far as flashing a GSI, I believe I'm going to abstain from trying that until a suitable restore tool is available. Ive pushed my luck too far as it is and I don't want to end up with a $700 paperweight.

Thank you for taking the time to test again! The silver lining for us being the ability to restore FP by restoring stock.
If you ever feel the need, you can probably restore stock from a GSI by dumping the system.img partition with a payload dumper then flash it again via fastboot. Or dump the system partition with dd when in rooted/magisk mode, copy it from the sdcard to your PC & likewise, flash via fastboot to restore.

 

[bob24260]

Thank you for taking the time to test again! The silver lining for us being the ability to restore FP by restoring stock.
If you ever feel the need, you can probably restore stock from a GSI by dumping the system.img partition with a payload dumper then flash it again via fastboot. Or dump the system partition with dd when in rooted/magisk mode, copy it from the sdcard to your PC & likewise, flash via fastboot to restore.

I already have the dumped system image but I'm real leary about doing it because I'm reading where people are having issues flashing system via fastboot. My 6 pro is my daily and at the moment I don't have any back up devices. My financial status dictates that I don't flush my only phone down the proverbial toilet. If I had a suitable backup device I'd be a bit more adventurous with my modding but at this time it's not feasible for me.

 

[Rootmaster906]

I think this thread is a farce and it seems awfully dangerous. Patching your boot image can have its consequences

 

[adwinp]

I think this thread is a farce and it seems awfully dangerous. Patching your boot image can have its consequences

Why do you think it's a farce?

 

[Rootmaster906]

Why do you think it's a farce?

cuz having to patch a boot.img on a phone is a sign that a custom recovery cant be flashed. its typically dangerous to do this figuring you have nowhere to do a back up to. plus, look at the replies...only a few. seriously man?

 

[adwinp]

cuz having to patch a boot.img on a phone is a sign that a custom recovery cant be flashed. its typically dangerous to do this figuring you have nowhere to do a back up to. plus, look at the replies...only a few. seriously man?

Any person tampering with his/her device outside of the intended operating parameters should be aware of the risks. That person shouldn't be executing these activities if they don't even know what rooting is/means.
Moreover, there's a disclaimer in the OP of this thread, & you get another warning when unlocking the bootloader itself. We don't have a custom recovery yet, as it's a new device & no one took ownership of preparing a TWRP for the RM6 yet - again, not a problem.
That said, apart from the fact of wiping the userdata due to unlocking, there's not much risk.
You can, at all times, restore partitions by flashing the factory data from payload extracts.
In addition, you don't really need to flash the boot image - you can always just boot it via fastboot boot & if it works, commit the flash.