How To Guide OnePlus 10 Pro NE2215 ***ROOTED*** (EX01 Update! READ BEFORE UPDATING)

[g96818]

1. Disabled all modules in Magisk.
2. clicked uninstall in Magisk, restored images, did NOT reboot.
3. Downloaded and installed OTA thru phones updater. did NOT reboot.
4. Switched over to Magisk, hit INSTALL and chose 3rd option to install Magisk to inactive slot. REBOOTED.
5. Phone bootlooped 4-5 times then finally booted but still on C.26 and without root.

Any ideas what I did wrong or could have went wrong?

might have been a bad update file. download the one i posted and update using the system updater app i uploaded. you can boot the patch boot afterwards and re-obtain root. Make sure "Automatic system updates" is on in developer options.

 

[tribulationwolf]

might have been a bad update file. download the one i posted and update using the system updater app i uploaded. you can boot the patch boot afterwards and re-obtain root. Make sure "Automatic system updates" is on in developer options.

Just wanting to make sure I'm understanding since I don't seem to be thinking at 100%.
Do I reboot after updating this way? and if so, then I go through the original post method to reobtain root again?

 

[g96818]

Just wanting to make sure I'm understanding since I don't seem to be thinking at 100%.
Do I reboot after updating this way? and if so, then I go through the original post method to reobtain root again?

yes. reboot, let it load, reboot to bootloader, boot the patched boot per the first post, and direct install magisk.

 

[Yaj00j]

1. Disabled all modules in Magisk.
2. clicked uninstall in Magisk, restored images, did NOT reboot.
3. Downloaded and installed OTA thru phones updater. did NOT reboot.
4. Switched over to Magisk, hit INSTALL and chose 3rd option to install Magisk to inactive slot. REBOOTED.
5. Phone bootlooped 4-5 times then finally booted but still on C.26 and without root.

Any ideas what I did wrong or could have went wrong?

this happened to me when updating from c22 to c26.. the solution was to fully remove root.. then update and then root again. i believe it was because my phone is 2210 running 2215.

 

[Bartx96]

Somebody help me I have latest firmware C.30 but when i try root every thinking is fine i have root but when I restart my phone I lost it :/

 

[g96818]

Somebody help me I have latest firmware C.30 but when i try root every thinking is fine i have root but when I restart my phone I lost it :/

Tell us what steps you did to root

 

[g96818]

Somebody help me I have latest firmware C.30 but when i try root every thinking is fine i have root but when I restart my phone I lost it :/

try use this version

magisk-files/app-release.apk at 0b9eca062198e568f9cc101eaf64bb5d9edb8a34 · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com

 

[mvincent2k]

try use this version

magisk-files/app-release.apk at 0b9eca062198e568f9cc101eaf64bb5d9edb8a34 · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com

So it it safe to upgrade or do we need to upgrade to this version of Magisk 1st?

Held off after seeing this.

 

[g96818]

So it it safe to upgrade or do we need to upgrade to this version of Magisk 1st?

Held off after seeing this.

you can use the latest. this was the last working version before it broke,

 

[mvincent2k]

you can use the latest. this was the last working version before it broke,

OK...

Getting "stock backup does not exist" when trying to restore images after installing latest magisk prior to upgrade.

Interesting. First time I have seen this and haven't touched since last update. Ideas?

 

[g96818]

OK...

Getting "stock backup does not exist" when trying to restore images after installing latest magisk prior to upgrade.

Interesting. First time I have seen this and haven't touched since last update. Ideas?

how did you root?

 

[mvincent2k]

how did you root?

Original method way back when from here. Been upgrading with method 1 for every update since release without issue.

On C.26 now rooted. That's why was thinking it had something to do with latest Magisk upgrade as that the only difference since lat time I upgraded. I updated to the latest magisk 26001.

Are there stock C.26 'restore images' I can use? Or does it look like I would need a complete uninstall? Would that even work or get same errors?

 

[g96818]

Original method way back when from here. Been upgrading with method 1 for every update since release without issue.

On C.26 now rooted. That's why was thinking it had something to do with latest Magisk upgrade as that the only difference since lat time I upgraded. I updated to the latest magisk 26001.

Are there stock C.26 'restore images' I can use? Or does it look like I would need a complete uninstall? Would that even work or get same errors?

I've had no issues with magisk and restoring. Try extract the attached zip file in the system/Data folder.
you can try restoring images after a restart.

no guarantee it'll work. That's the backup file magisk made on my phone, but idk how it references it when restoring.

 

[mvincent2k]

I've had no issues with magisk and restoring. Try extract the attached zip file in the system/Data folder.
you can try restoring images after a restart.

no guarantee it'll work. That's the backup file magisk made on my phone, but idk how it references it when restoring.

So it was interesting. That did not work and when I looked in the data folder the unpatched and patched files from all updates were already there, so should have worked.

The way I fixed it was full unroot, then used your patched C26 to boot and reinstall. Then did local update to C30 just to make sure I could 'restore just images' and that worked. Lost all my magisk modules but such is life.

I still think it had something to do with Magisk upgrade so sharing in case others come across this.

 

[g96818]

So it was interesting. That did not work and when I looked in the data folder the unpatched and patched files from all updates were already there, so should have worked.

The way I fixed it was full unroot, then used your patched C26 to boot and reinstall. Then did local update to C30 just to make sure I could 'restore just images' and that worked. Lost all my magisk modules but such is life.

I still think it had something to do with Magisk upgrade so sharing in case others come across this.

That's odd that the full unroot worked since it couldn't reference your saved backup to restore images, but good that it did.

 

[ProfEngr]

Fastboot decided that it doesn't recognize the phone in bootloader (it did a few reboots ago). Windows gives the 'ding' when I plug in the USB, but adb only shows the device ID when booted to the OS. I'm on C30.

 

[g96818]

Fastboot decided that it doesn't recognize the phone in bootloader (it did a few reboots ago). Windows gives the 'ding' when I plug in the USB, but adb only shows the device ID when booted to the OS. I'm on C30.

check if you need to update the drivers. maybe install a different driver.

 

[PedroCaseiro]

Color/Oxygen OS android 13 update

NE2215_11.C.30 NA Boot image & ROOT

CAUTION!
Not my fault if your phone breaks.

WARNING!!!
Issues I've seen on previous devices:
- A few people have had bootloop issues due to using the wrong rom on the wrong phone. (e.g. Installing the Global ROM on a EU, IN, or CN model)
- If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone.

I can't help you if your phone doesn't update properly.

-----------------------------------------------------------------------------------------

International NE2215_11.C.30 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/e7ca663c03b3642e8abe8df3be6d42fd472109a3.zip
Mirror: https://www.androidfilehost.com/?fid=4279422670115731599
SHA-1: E7CA663C03B3642E8ABE8DF3BE6D42FD472109A3
MD5: 597F5179C31C4E9C09F7FD9867FAFC9A

OnePlus Local Update Tool (OPLocalUpdate_For_Android12.apk)
Mirror: https://www.androidfilehost.com/?fid=15664248565197176984
SHA-1: 80707A75F7FA9E1864E84C7C7C270175A9FEC129
MD5: ADF932B2FD4C2A2B379C9427197B6B6A

Or you can just use the full update package (LOL)
International NE2215_11.C.30 full rom:
Official:
Mirror:
SHA-1:
MD5:

Two methods are available, PC and non-PC. I refer the non-PC method since it's much easier and it hasn't failed me yet so I'm just going to post instructions for that. You can look at previous update instructions if you want the PC method.

-----------------------------------------------------------------------------------------

NE2215_11.C.30 boot images (For reference only. Download not required):
Stock

boot_b.img | by Xi Jing Pooh for /e/OS supported models

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

SHA-1: D6E0283E5BC9DCF751D6B3FB77A7524045214335
MD5: 260EFDFBD21BCBCE902DC92897916113

Patched

magisk_patched-25209_5AO0N.img | by Xi Jing Pooh for /e/OS supported models

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

SHA-1: 62ADCB77B082F84535B09D429D32C29FED484035
MD5: E49B3AD1E094B9AB90AB5865BE90AE3D

-----------------------------------------------------------------------------------------

Non-PC Method

See Warning above.

Step 1: You must unroot first. You don't have to completely remove Magisk, just restore images. Open Magisk, click uninstall magisk, and only click restore images. DO NOT REBOOT!

Step 2: Install OTA update. DO NOT REBOOT!

Step 3: Open Magisk and install to inactive slot. Reboot. Boot up took about 30 seconds.

-----------------------------------------------------------------------------------------

If you rebooted on accident before patching, then do the following using your PC:


I recommend doing the following instead of just booting the patched file.

Step A: Patch the boot image above using Magisk and copy the patched boot image to your computer.

Step B: Reboot and BOOT the newly patched boot image. Your file name will be different than what I'm posting so make it match.

adb reboot bootloader
fastboot boot magisk_patched.img

Step C: Open Magisk and perform a direct install.

Step D: Reboot.

NOTE: I do not know if the patched file will work for everyone. I've previously had problems using someone else's patched file and had to redo the patch before the phone accepted it. It's highly possible that magisk preps the phone itself or does something during the patching to allow it to boot. The important thing is YMMV.

What do you mean by this? "- If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone."

patched boot vice?

 

[g96818]

What do you mean by this? "- If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone."

patched boot vice?

read post 1

 

[ProfEngr]

check if you need to update the drivers. maybe install a different driver.

was using the wrong command. ADB devices doesn't work in bootloader