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

Search This thread

morgan76

Member
Dec 27, 2020
13
3
in the end i uninstalled magisk image then flashed stock recovery from fastboot then forced local update then android 13 local update then extracted boot.img from payload and updated with magisk loaded from fastboot and the phone is perfect!!! rom c.26 phone passed from 2210 to 2215 with 5g working perfectly!!!
 
  • Like
Reactions: g96818 and Prant

g96818

Senior Member
Dec 27, 2014
880
383
Hello I have Null imei in my oneplus 10 pro , can I repair my imei after the root? . I don't have any backup of my device :(,
How did you lose it? Are you rooted? I’m leaning towards no, but you can try perform a system reset to see if it comes back. If you are rooted, then you want to perform a complete unroot first.
 
Jul 23, 2012
43
3
Haven't rooted in years and wanted to make sure I do this correctly. I am on build NE2215_11_C.26 stock. This is the first time rooting this phone. Which files do I need and do I still follow the process given in the original post here.
 
Jul 23, 2012
43
3
Use C.26 boot image with the original instructions.
So this patched boot image here or the stock one will be fine?

Patched
www.androidfilehost.com

magisk_patched-25206_r3ZRg.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: 2BA2B71020B7431B80D884E800D83984E90C7233
MD5: 48E01D8F2599DADDF1EB771F4C417D42
 

g96818

Senior Member
Dec 27, 2014
880
383
So this patched boot image here or the stock one will be fine?

Patched
www.androidfilehost.com

magisk_patched-25206_r3ZRg.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: 2BA2B71020B7431B80D884E800D83984E90C7233
MD5: 48E01D8F2599DADDF1EB771F4C417D42
You can use that or patch the original yourself. It should still work, but it is 4 magical canary builds ago. Current canary build is 25210. Use 25209 if you can find it since 25210 has some issues.
 

thommic

Senior Member
Jun 20, 2006
132
4
FFM
I did a mistake during OTA update. Is there anyone out who can provide me with a patched c30 boot.img? My device is a ne2213. Thanks in advance!
 

Swap_File

Senior Member
Apr 12, 2016
75
47
Anyone know of a payload dumper tool that works with incremental OTAs and doesn't get LZMAErrors on OnePlus bins? I want to extract NE2215's C30 boot.img
 

Swap_File

Senior Member
Apr 12, 2016
75
47
Can’t extract from ota zips. I’ll put up the c30 update files in a couple hours

Thanks, that would be helpful. In the past, with my 8 Pro, I was able to download the last full rom, extract it with this tool, and then apply each incremental OTA to get a current boot.img.


Unfortunately, this tool now errors out with LZMAErrors, and no other tool that I can find supports applying incremental OTAs.

I have the old NE2215 C22 full, C26 incremental, and C30 incremental, and was planning to extract them all together (until I started getting LZMA Errors).
 

g96818

Senior Member
Dec 27, 2014
880
383
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
SHA-1: D6E0283E5BC9DCF751D6B3FB77A7524045214335
MD5: 260EFDFBD21BCBCE902DC92897916113

Patched
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.
 
  • Like
Reactions: Swap_File
Jul 23, 2012
43
3
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
SHA-1: D6E0283E5BC9DCF751D6B3FB77A7524045214335
MD5: 260EFDFBD21BCBCE902DC92897916113

Patched
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.
With the Non-PC method on step 3 what am I installing for that step after installing the OTA?
 
Jul 23, 2012
43
3

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?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    2
    So what I did because again Oxygen OS 13.1 has just been way to buggy for me. I actually am not really impressed with what OnePlus has been doing as of late. I've owned OnePlus products since the very first OnePlus One. I have a ton of OnePlus Phones. I have a 8T as well I've flashed MSM tool custom rom you name it I've done so I'm definitely familiar with running custom and fixing issues on these phones :) which is why I always fastboot flash but again I thank you much for the reply.

    What I actually ended up doing was grabbing downgrade zip going back down to 12 completely for a multitude of reasons. I'll list them below. Wiped completely upgraded one update and going to stay away from OS 13.1 for now.

    The reason I wanted to go to 13.1 was because I also recently picked up the OnePlus Pad and to basically enable cellular data sharing you're going to need to be on 13.1 (whenever the hell that happens lol)

    My biggest gripes about the 10 Pro oxygen 13.1 is the delay in screen on time like with raise to wake or double to wake or power button and I've also turned off the other gestures and just did power button and still found myself waiting like 5 seconds for it to turn on. Some times it works other times it doesn't

    Also maybe not even a big gripe as it is with me but the quick settings pull down area. Why the heck would OnePlus leave so much space on either side there is so much space there it bothers the heck out of me. I just feel like comparing OS 10,11 and even 12 to this version is a severe step back and that is again IMHO only. Hopefully these other issues get resolved or EVENTUALLY MAYBE ONE DAY a custom rom comes along lol (holding out hope secretly)

    But again thank you very much again for everyone taking time to reply and chime in it is appreciated but yes I am aware on what am doing as well :)
    2
    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://forum.xda-developers.com/t/...a-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.
    2
    @Markus214 you can look on post 1 to find the corresponding stock boot image. I also recently started uploading the stock recovery on afh.
    2
    I'm fully updated and re-rooted btw, thank you again for the work and help on this.
  • 10
    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
    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
    Color/Oxygen OS android 13 update

    NE2215_11.C.19 International 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 should be able to use this since it's the full installation package.

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

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

    International NE2215_11.C.19 full update:
    Official: https://android.googleapis.com/packages/ota-api/package/6812ccee9a8a891032af1e053e3217731ac7ad92.zip
    Mirror: https://www.androidfilehost.com/?fid=14871746926876835870
    SHA-1: 6812CCEE9A8A891032AF1E053E3217731AC7AD92
    MD5: 1A63783851148E4566A255FE8FCDC4F8

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

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

    NE2215_11.C.19 boot images (Download required):
    Stock
    SHA-1: BDBD8D1130B076D1DE26A45C37A773452F1BE817
    MD5: B758030A6E30EDAAA4D914F5D026DC40

    Patched
    SHA-1: D0CF6F2F9214F07E4EAAE1279A1B390F04DDEE0C
    MD5: 964965E5AA7E38105EACAAEB86048073

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

    PC Method

    You all know I prefer the non-PC method since I pioneered it and was the first to bring it to XDA, BUT I DO NOT RECOMMEND THIS FOR MAJOR SYSTEM UPGRADES! READ STEP 6.

    I have always run into issues and recommend you to follow this modified non-PC/PC method.

    See Warning above.

    Step 1: Put the update zip and stock boot files in your base directory.

    Step 2: Recommend you unroot first, but not necessary. 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 3: Open the system update app and install the update. DO NOT REBOOT!

    Step 4: Open Magisk, click "Install", and "Select and Patch a File" to patch the stock boot. Reboot.

    Step 5: Copy the patched file to your PC.

    Step 6: Reboot. You will lose root at this point, but you are guaranteed to update properly and not end up in a boot loop.

    Step 7: 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

    If you get a waiting for device error, then you need to update your bootloader/fastboot driver.
    Right click your PC iicon and click "Device Manager".
    Click on "Drivers"
    Look for the Android item with a yellow triangle.
    Right click and select "Update Driver"
    Click "Browse my computer for drivers"
    Click "Let me pick....."
    I installed the Google Bootloader driver, but maybe another will work for you, so just keep installing until you find one that works.

    Step 8: Open Magisk and perform a direct install.

    Step 9: 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. 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.