[GUIDE] How to root OnePlus Nord

[Some_Random_Username]

Devices that started to be received today have Oxygen OS 10.5 out of the box.
No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted.

You then need to update to a newer build first. You can do so from my OxygenOS builds repo thread.

Once done, enable developers options and enable OEM unlock.
Reboot to fastboot (enable USB debugging in dev options and use adb reboot bootloader)
Type fastboot oem unlock and accept to unlock bootloader (warning: as a safety measure Android will wipe your userdata)
Go through OxygenOS setup
Install Magisk Manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
Move stock boot.img to your phone internal storage (please open spoiler)

For your convenience, 10.5.2 stock boot.img for EU and India have been extracted
EU download: https://drive.google.com/file/d/18aPqErEMbRqmN4BpdvHE4OKgizDcEbou/view?usp=sharing
India download: https://drive.google.com/file/d/1ZIEYWH2PYkKyojq_S_i_onBstejHKDTJ/view?usp=sharing

For future builds, you can use payload dumper (Windows) , (Linux ) to extract stock boot.img

Click on Install
Choose "Select and patch a file"
Select your stock boot.img
Wait until Magisk patches your boot.img, and once patched it can be found in the Downloads folder
Copy that patched boot.img (which should be named magisk_patched.img) to your computer
Boot into fastboot again
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Reboot to OxygenOS

Open Magisk Manager and your device should now be rooted.

TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.

Credits:
@topjohnwu for making Magisk
/u/Jisifus for testing on his device and for screenshots

 

[Deleted member 5408779]

TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.

Great to see it works this way and thanks for the tip.:good:

 

[Knightrid3r]

do u lose all data while rooting?

#edit1
nevermind, cannot read right

 

[dansou901]

OK, will give this a try asap,have the device here now...

 

[Knightrid3r]

I gave it a try, works like a charm! Thanks for this! Small tip, unlock bootload before u copy your files

now my phone is a bit laggy. with magisk on it.. i will test it later if its getting better

 

[Displax]

Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.

You can simply type "fastboot flash boot magisk_patched.img" - it flash boot to current active slot. Just for note.

 

[dansou901]

Can confirm that it works, just tried it myself

 

[Lossyx]

If WiFi/data does not work (usually happens when you flash wrong version, but can also happen if you flash correct one), fastboot boot the image, then do a direct install in Magisk Manager.

Also, big thumbs up for adding tips for persist backup, I see too many people needing to send their device back because they messed it up somehow.

 

[jmwengineering]

Failed for me

Hi and thanks for the tips.

Running 10.5.2 (latest build) and Bootloader is unlocked.

1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).

Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.

Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.

 

[Lossyx]

Hi and thanks for the tips.

Running 10.5.2 (latest build) and Bootloader is unlocked.

1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).

Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.

Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.

The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.

 

[Deleted member 5408779]

Hi and thanks for the tips.

Running 10.5.2 (latest build) and Bootloader is unlocked.

1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).

Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.

Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.

And that's why it's recommended to boot the patched image first.

 

[jmwengineering]

Thanks

The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.

Thanks for confirming file size - Preserve Force Encryption and Preserve AVB 2.0/dm-verity were ticked during the patching process. Guess I'll have to wait until TWRP is verified as Nord compatible.

---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------

And that's why it's recommended to boot the patched image first.

Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!

 

[Deleted member 5408779]

Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!

Nah, instead of flash the patched boot image you can boot it only. Not sure why it's not working for you. But usually it should work.

Command: fastboot boot "patched boot image"

Edit: that's also what lossyx said. Boot image and than install it with magisk manager.
And if you boot the image and something went wrong you aren't bricked or anything. It's a safe way to test something.

 

[jmwengineering]

Thanks for the advice - will boot the image file on my PC rather than flashing first.

Sent from my AC2003 using Tapatalk

 

[KakatkarAkshay]

Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P

 

[DIR49DNOR0N]

..

 

[Deleted member 5408779]

Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P

Yeah I guess when you unlock your phone it will break L1 as always.

---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------

I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?

https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085

 

[Matteo]

I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?

No, keep the bootloader unlocked if your phone is modified, else it can cause some issues.

Btw when you lock/unlock the bootloader, data will be wiped. apps will be reinstated again so that's useless

 

[CozaMcCoza]

The guide worked perfectly and I'm up and running with Root!

One thing I have noticed is that the Google Play store is no longer Play Protect Certified.

I've tried registering my device with Google using this XDA guide but I haven't found any change to the Play Store certification.

I should probably wait for a while to see if the registration takes some time. I also couldn't use the adb commands that Google recommends and I had to use the Device ID app to get the Google Service Framework (GSF).

I've read in a few places that it may be because the Bootloader is unlocked and I'm wondering if I should re-lock it now that I have root. Not sure how/if that will affect my ability to keep root when future updates come out though.

Anyone have any thoughts/experience with this?

 

[ultimate artem]

Possible TWRP without waiting?

Can anyone use this and try? Might be used as an alternate Method for Rooting via TWRP

https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013