How To Guide OnePlus 10 Pro NE2215 ***ROOTED*** - No Longer Being Updated - OTA instructions inside

Search This thread

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    For bootloader on OOS14 you must flash this abl.img via minimal adb fastboot tool on fastboot mode
    1
    Here's the clean boot img from 14.0.0.402(EX01).

    If no one else has posted it, I'll always make sure to upload it, just be aware I don't always update right away, I wait until I have a free weekend or some kind of a break.
    1
    Here is the stock boot.img for NE2215 14.0.0.500(EX01)
    1
    Is this from OOS13? I tried reflashing the abl partition on my 10T but used the latest abl.img from the most recent OOS14 update but it had no effect.

    Just wondering if this is the abl.img from OOS13.
    Yes from oos13
    1
    Now I used abl.img from OOS13 for 10T and it worked. Thank you!
  • 13
    This is for the NE2215 Rom.

    Step 1: Unlock your bootloader.

    Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary.
    https://github.com/topjohnwu/Magisk

    Step 3: You can use either patch the stock boot or use my patched boot rom.
    https://androidfilehost.com/?w=files&flid=333790
    NOTE: This is for the original stock image when the phone first came out. See below for updates and boot images.

    Step 4: Reboot to bootloader
    Code:
    adb reboot bootloader

    Step 5: BOOT the patched boot rom! DO NOT FLASH!
    Code:
    fastboot boot patched_boot.img
    
    * change patched_boot.img to whatever your filename is.

    Step 6: Open Magisk and perform a direct install.

    Step 7: Enjoy!

    Additional steps to pass safetynet:

    Step 8: Open Magisk, open the Settings menu, enable Zygisk, and reboot.

    Step 9: Download and install Universal Safetynet Fix (Zygisk) by @kdrag0n.
    https://github.com/kdrag0n/safetynet-fix/releases

    Step 10: I forget if you really need this or not, but install it anyways.
    MagiskHide Props

    Step 11: Reboot.

    Step 12: Enjoy!

    Netflix Error -93:
    WARNING: Netflix will not work after bootloader unlock. OnePlus's fault.

    Here's how to get Netflix to work, but DRM will drop from L1 to L3.

    Step 1: Uninstall Netflix.

    Step 2: Flash Shamiko in Magisk and reboot.

    Step 3: Install this version of Netflix.

    Step 4: Open Netflix and close the app.

    Step 5: Update Netflix from Google Playstore.

    Step 6: Open Netflix and log in and force close the app.

    Step 7: Open the app again and be greeted with error code 93, then force close the app.

    Step 8: Open the app again and enjoy Netflix.


    Updates:
    NE2215_11.A.12
    NE2215_11.A.13
    NE2215_11.A.14
    NE2215_11.A.15
    NE2215_11.A.16
    NE2215_11.A.17 Stock boot image and OTA. Thanks @mrdark5555
    NE2215_11.C.19 Stable Color/OxygenOS 13
    NE2215_11.C.20
    NE2215_11.C.21
    NE2215_11.C.22
    NE2215_11.C.26
    NE2215_11.C.30
    NE2215_11.C.53 (EX01). About damn time! READ BEFORE UPDATING!
    NE2215_11.C.54 (13.1.0.522(EX01))
    NE2215_11.C.55 (13.1.0.580(EX01))
    NE2215_11.C.56 (13.1.0.581(EX01))
    NE2215_11.C.57 (13.1.0.591(EX01))
    NE2215_11.C.58 (13.1.0.593(EX01))
    NE2215_13.1.0.597(EX01) boots only
    5
    This is good to know. I was unsure if the downgrade zips would fix a misflashed boot image, are you able to update from that downgrade zip to newer A12 images too? As in, both slots were fixed with the downgrade? (Did you flash both boot slots in the first place? I suppose.)

    Glad you got it working though, yeah OPPO is a bit different now. In the past OPlus devices were the best to mess around with, but now one wrong misstep and you're forced to pay for a recovery flash. It's a different world.

    Yeah so far so good on A12 currently which is even weird for me to say because I will be the first to admit I was extremely stubborn moving from A10 I just loved the UI on my 7T hahaha even on my 8T I had changed to A11 using crdroid. I just think it's the quick settings pull down for me like that should be edge to edge and the fact that like each release just keeps showing so much space bothers me idk it's weird but that's me lol.

    So what I did was this completely.

    From the very beginning with my 10 Pro I upgraded all the way to A13 then 13.1 like the latest. I flashed magisk patched boot from the thread here booted up got magisk installed just didn't like the UI and the delay and bugs so I grabbed the flashable boot from https://xdaforums.com/t/oneplus-10-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4572593/ for the NE2215 and installed via system update apk. It took the local update with no issues rebooted to recovery wiped it.

    Booted right up no issues at all. I then updated once more to I believe it's A.17 of 12.1 or 12 again grabbed the magisk patched img fastboot flash booted right up.

    Once I had root I made sure to block updates :LOL: just because right now Oxygen 13 is just not stable enough for what I am looking for just for personal reasons. Maybe 14 will change that hopefully lol.

    But for right now 12 is running great on here

    And yeah like I said been with OnePlus since the OnePlus One. Running custom roms and doing MSM tools are nothing new to me but sheesh after the 9 Pro series it really went downhill bad it seems which realllly sucks.

    It really keeps me guessing/thinking should my next device be a Pixel. I really don't like to think of that because I've been a huge OnePlus fan boy ever since the One (I still own one to this day lmao!)

    but just not sure what they are doing anymore and please if you haven't tried to contact OnePlus support yet do not try at all. You will get better results talking to a rock.
    4
    HOWEVER I did flash the boot image in fastboot.
    Afaik, you're in a bit of a dire situation with this device. You basically need to pull the matching version of your boot image, not patched, flash that back, and pray that it works. Golden rule with this phone is you should NEVER flash anything from fastboot to this device unless you REALLY know what you're doing.
    4
    NE2215_11.A.14 International Boot image & ROOT

    CAUTION!
    I do not know if are multiple OTA files for those still stuck on a previous versions before NE2215_11.A.13. I recommend just updating it through the system update. I updated through system update.

    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.A.14 OTA Incremental update:
    Official: https://android.googleapis.com/packages/ota-api/package/e443d7662829c933a0da968a62bf080aacab37c9.zip
    Mirror: https://www.androidfilehost.com/?fid=15664248565197176978
    SHA-1: E443D7662829C933A0DA968A62BF080AACAB37C9
    MD5: 3FD7A8DA16A1B6C85EC8B17E4A85C188

    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 (PENDING)
    International NE2215_11.A.14 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.A.14 boot images (For reference only. Download not required):
    Stock
    SHA-1: 94B61C7D2AA9400039B8E3BB77D2638532225912
    MD5: 7810AFEE1B4F1D4A5F69A485ACF1BD2B

    Patched
    SHA-1: 82001947F7B20C3B553C76CDC290B0B6C77DB338
    MD5: 6EAA24A02D3749567F8187DE40D2D0D1

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

    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.
    4
    NE2215_11.A.12 International Boot image & ROOT

    CAUTION!
    I do not know if are multiple OTA files for those still stuck on a previous versions before NE2215_11.A.12. I recommend just updating it through the system update. I updated through system update.

    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.A.12 OTA Incremental update:
    Official: https://android.googleapis.com/packages/ota-api/package/f99da5215db535177dabb71960ec6365a63af389.zip
    Mirror: https://www.androidfilehost.com/?fid=14655340768118454642
    SHA-1: F99DA5215DB535177DABB71960EC6365A63AF389
    MD5: F7D3D8498B61B131D36F0C93F5DCEBEC

    Or you can just use the full update package (PENDING)
    International NE2215_11.A.12 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.A.12 boot images (For reference only. Download not required):
    Stock
    SHA-1: 3BCFF2323A03F26FC94BB5A2196CC1B9611EEF53
    MD5: 8BEEB2BE49E4A0F40D750E44205F1636

    Patched
    SHA-1: 1676BEAD586662ADF4597CA0AB16A3064D13F633
    MD5: 978E7F85AE3AA239E022C69888ACCF98

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

    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.