How To Guide (Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet

[Tilde88]

Have the exact same problem. So how does one update the system? There appears to be no full c26 stock rom, only the OTA. How to proceed?

Flash recovery_a and recovery_b with original recovery. Restore unlatched kernel/ram disk while youre at it. GG

 

[amomp3]

You do not want to flash this device without local update apk, that will usually lead to more issues than it's worth. Here are the downgrade packages. Make sure to use them as they say, take the rollback zip in Local Update APK. That's the safest way I know of to return your phone to as close aa stock as possible.

Thank You !

a)
Have you made this procedure yourself?

b)
Is not a risk the fact that i am in NE2215_11.C.22, rooted and with TWRP in borh slots ?

c)
I mean: this way will flash an image that overwrites ALL partitions of the phone including both recovery partitions?
c.1)
it also include data partition so we must not leave anything we care inside the phone before making this procedure ?

d)
So, from that OnePlus Forum post you shared:
We must use this app:

https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk

to load this file:

https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip

Thank You!

 

[Sparta de Astom]

how can i root my gl tools

 

[Prant]

Thank You !

a)
Have you made this procedure yourself?

b)
Is not a risk the fact that i am in NE2215_11.C.22, rooted and with TWRP in borh slots ?

c)
I mean: this way will flash an image that overwrites ALL partitions of the phone including both recovery partitions?
c.1)
it also include data partition so we must not leave anything we care inside the phone before making this procedure ?

d)
So, from that OnePlus Forum post you shared:
We must use this app:

https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk

to load this file:

https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip

Thank You!

Hey, sorry about the timing. I hope the process went well for ya.

I've not done this myself, I just have seen that this is the best and only official way to get your phone to as close to stock as possible. I'm not sure if it will flash the recovery's as well, you may need have the original images for those. But it will wipe data partition for sure. And lastly, yeah. Use that app to take the rollback package.

 

[amomp3]

Hey, sorry about the timing. I hope the process went well for ya.

I've not done this myself, I just have seen that this is the best and only official way to get your phone to as close to stock as possible. I'm not sure if it will flash the recovery's as well, you may need have the original images for those. But it will wipe data partition for sure. And lastly, yeah. Use that app to take the rollback package.

Thank you very much for answering, i was really waiting your input...

I did not had the guts to do it before your answer and i don't know if i have them now...

You "saw" like in other posts that someone(s) did it and worked for him/them ?

Fear to brick if this procedure does not flash recoveries a and b and if i flash them separately one tiny bit change and broom...

Besides the fear... I would really like the ability that TWRP provides of doing backups !! This is for what i installed it! He has been protecting us since it came out!

It would be awesome if someone reply to really know if someone was actually able of restoring a TWRP backup and then boot system normally!

Maybe i am doing something wrong putting all the checks in all partitions and modem, etc and is not needed to include all and therefore it will not restore all and won't get stuck at boot-animation ?

 

[Prant]

Yes. You can do your own research if you want, it's all here or on the sister forum the mods don't like mentioned. That rollback zip is the safest and officially released way to revert back to close stock. I'm not sure if it flashes recoveries, as I haven't seen that question asked before tbh.

I've only seen one guy here claim to restore a TWRP backup and have it working on this device and that's @Canuck Knarf iirc, (apologies if I got the user wrong, I'll cross reference when I get home from work) he's got a psuedo bypass for engineering mode from a successful TWRP backup.

I, myself, have decided TWRP isn't worth it on this device since it must be flashed to the device and I've seen multiple people create backups that lead them to bootloops. Not worth the hassle.

 

[dladz]

Twrp Christmas gift , dladz told me it would never will be and I understand his frustration. I just got the 10 pro so it's great. Thanks for the work of the devs and now we will hope that the development section fills in ... Have you ever seen a oneplus with no dev project? Thanks for your tuto

I do stand by this statement.. but I'd be glad to be wrong.

 

[dariodamico]

How to keep root after OTA update C30

 

[dariodamico]

How to keep root TWRP after OTA update to C30?

 

[mrk2815]

now there is a unofficial twrp build , now how hard to keep a twrp officially updated for this device.AS well begin the process for building roms for the device.just wondering.

 

[asadurrehman]

Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.

Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.

Warning
This has only been tested on Android 13. This guide may not work for other Android versions.

Prerequisites

1. Unlocked Bootloader
2. Magisk 25.2 Installation ZIP (see attached files)
3. TWRP Image (download from GDrive)
4. ADB and Fastboot tools are installed on your machine. Please see this guide
5. Android 13

Spoiler: Step 1 - Unlocking Bootloader

Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging

1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command

adb devices

The output should be something similar to this:
View attachment 5792895
(note the device name on the left will not be the same)

Reboot into the bootloader by entering the following command:

adb reboot bootloader

1.C - Unlock
Once entered, enter the following command:

fastboot flashing unlock

WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE

Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:

fastboot reboot

You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader

Spoiler: Step 2 - Flashing TWRP

Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader

2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post

This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:

fastboot flash recovery_a twrp.img

fastboot flash recovery_b twrp.img

fastboot reboot recovery

You should notice you are in TWRP.
You may need to change the language to English.

2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.

2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery

Spoiler: Step 3 - Flashing Magisk

Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:

adb reboot recovery

3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device

3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!

Spoiler: Fixing Data Backup [Optional]

If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap

The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.

Spoiler: Bypassing Safetynet [Optional]

Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted

B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"

C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device

E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot

F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!
View attachment 5795089

Does it work on pixel 5?

 

[Ph0nysk1nk]

Does it work on pixel 5?

Baffling how comments like these end up here. This isn't even a pixel 5 XDA page.

 

[rmedure]

Hello everyone.
Had OP2 with the excellent MoKee 6.0.1 tocino and
OP 5T with out of the box rom rooted and with TWRP super tweaked...

I just bought the 10 pro NE 2215 (unlocked international) straightly from oneplus website and i am a little concerned about several things i read on all of this thread. I hope the community (we) be able to sort this new ridiculous kinda "locks" which are indeed the absolute opposite of why we buy OnePlus devices!

I had read almost all posts from the 3 threads about rooting OP 10 Pro and it seems really challenging as it is very dynamic and changes little things between each build update.

I really appreciate the time and efforts all of you are putting into help others and document your findings.

So, to start, my first question is:

Seeing that my actual build number NE2215_11_A.10 and hardware version NE2215_11 are the same as @g96818 (on this post) I assume that rooting is possible AND safe in this actual state of my still untouched device... so:

a) should I update officially till the maximum possible and then see what build I ended and start the rooting procedure from there
or
b) should I root now and then don't update (i'm on android 12) or look for how to update after root (or it will too much hassle because I will have to unroot every time before update?)

Thank YOU all Very much!

You can always (as far as I know) upgrade and keep magisk root. Basic procedure is unroot in magisk manager app, upgrade/update Android, do NOT reboot, use magisk manager app to install root to other slot (which is where the update was installed), then reboot, enjoy.

 

[rmedure]

You can always (as far as I know) upgrade and keep magisk root. Basic procedure is unroot in magisk manager app, upgrade/update Android, do NOT reboot, use magisk manager app to install root to other slot (which is where the update was installed), then reboot, enjoy.

Oh and disable all magisk modules first, just to be safe ...

 

[ues_t]

I think I need help, I have nothing to do these days I tried to make twrp's common and tree with the help of files that github has, but I found that I messed them up and kept reporting errors, I don't know how to solve these Question, I hope someone can improve it, I am using the C13.1 file, the link is belowoneplus10pro twrp tree and common