How To Guide OnePlus 10 Pro NE2215 ***ROOTED*** (13.1.0.591(EX01) Update)

Search This thread

Markus214

Senior Member
Jan 22, 2009
440
49
Philadelphia
Google Pixel 2 XL
Anyone else having issues with system update failed? Doesn't matter if I grab the update from OnePlus directly downloading or oxygen updater or downloading the mirror above and installing via system update local update each version gets close to the end then fails.

Also does this new version hopefully solve the whole delayed response time when screen is off? Like when device is off if you press power button or double tap to wake or raise to wake sometimes it takes a good 5 seconds to actually wake up. I can confirm this is happening on another 10 Pro I have too both NE2215

Both after updating all the way to 13.1 EX01
 
  • Like
Reactions: Prant

Prant

Senior Member
Jan 23, 2017
152
114
OnePlus 7 Pro
OnePlus 10 Pro
Also does this new version hopefully solve the whole delayed response time when screen is off? Like when device is off if you press power button or double tap to wake or raise to wake sometimes it takes a good 5 seconds to actually wake up.

Yeah, this bug still exists. It's a bit better but, still there. It's worse with a different launcher than the stock one, feels like sone sort of OPPO thing tbh.
 

g96818

Senior Member
Dec 27, 2014
1,011
441
Anyone else having issues with system update failed? Doesn't matter if I grab the update from OnePlus directly downloading or oxygen updater or downloading the mirror above and installing via system update local update each version gets close to the end then fails.

Also does this new version hopefully solve the whole delayed response time when screen is off? Like when device is off if you press power button or double tap to wake or raise to wake sometimes it takes a good 5 seconds to actually wake up. I can confirm this is happening on another 10 Pro I have too both NE2215

Both after updating all the way to 13.1 EX01
I don't have that problem, but I have noticed pocket mode is buggy since 13.1. sometimes it triggers in broad daylight and i can't unlock the phone.
 

Swap_File

Senior Member
Apr 12, 2016
93
57
Samsung Galaxy J7
Google Pixel 2
Anyone else having issues with system update failed? Doesn't matter if I grab the update from OnePlus directly downloading or oxygen updater or downloading the mirror above and installing via system update local update each version gets close to the end then fails.

Also does this new version hopefully solve the whole delayed response time when screen is off? Like when device is off if you press power button or double tap to wake or raise to wake sometimes it takes a good 5 seconds to actually wake up. I can confirm this is happening on another 10 Pro I have too both NE2215

Both after updating all the way to 13.1 EX01

I haven't had any issues with "System Update Failed" in a long time, but I also turn on "Automatic system updates" in Developer Options before I apply the update (and then shut it back off once it's installed). Not sure if it still matters or not, but having it off used to cause problems.

I have not noticed any problems with wakeup time via the power button, but I do not have raise to wake or double tap to wake turned on. Maybe one of those two settings are buggy? You could try turning one or the other (or both) off for a while, and see if the problem goes away.
 

Markus214

Senior Member
Jan 22, 2009
440
49
Philadelphia
Google Pixel 2 XL
Thanks to all who have replied greatly appreciate that! So it gets to about 84% then system update fails. Not sure what the issue is happens with any update and automatic updates on or off. I really feel like OnePlus has gone downhill ever since this Oppo crap too. ColorOS was absolutely garbage. Ive been switching back and forth between this 10 pro and my 8T lately because stability. Wanted to use the 10 pro with my OnePlus pad for cellular data sharing whenever that comes 😂 but idk if it's worth it

Again seriously appreciate all the replies
Screenshot_2023-06-07-08-32-02-78_81acaadf7dd4290b3f605946fc8268aa.jpg
 

Markus214

Senior Member
Jan 22, 2009
440
49
Philadelphia
Google Pixel 2 XL
I believe this is because either A, you didn't unroot before installing. Or B you've, in the past, flashed a boot image and/or possibly TWRP directly to the phone and that's blocking it.


Ah that makes more sense now. So yes I did unroot completely before uninstalling HOWEVER I did flash the boot image in fastboot.

So I'm guessing what would be needed essentially is a complete wipe then install the updates all the way
 

Prant

Senior Member
Jan 23, 2017
152
114
OnePlus 7 Pro
OnePlus 10 Pro
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.
 

Markus214

Senior Member
Jan 22, 2009
440
49
Philadelphia
Google Pixel 2 XL
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 :)
 
  • Like
Reactions: Prant and g96818

g96818

Senior Member
Dec 27, 2014
1,011
441
I also wanted to seriously say THANK YOU to you for taking the time so QUICKLY each time to put together the boot img and patched boot img you are a freaking rockstar!!
If you have T-Mobile, then add dun to your apn to get free tethering.

You might need to create a new apn if you can't edit it.
 

Attachments

  • Screenshot_2023-06-07-08-06-24-98_426a5588c5110cd01d5af17e47adb223.jpg
    Screenshot_2023-06-07-08-06-24-98_426a5588c5110cd01d5af17e47adb223.jpg
    175.9 KB · Views: 40
  • Like
Reactions: zefyx and Markus214

Squidd

Member
Nov 27, 2019
29
11
New Jersey
squidds.tv
Google Pixel
Everyhing is honestly surprisingly smooth after upgrade and re-root. Biggest gripes coming from a P6 are-

Task switching, task overview, close all- the Pixel 4 & 6 did this flawlessly. It was buttery smooth to switch back and forth between apps by just swiping left and right the very bottom of the screen. Experience swiping the bottom fo the 10 pro is not great at all. It's glitchy and not consistent. The task overview on the 10 pro is slow and wack. "Close all" doesn't really close all, at all.

The camera- It takes decent pictures when the conditions are right. But if the light is a little low or the subject/landscape has a little too much movement then it's not great at all. I'd guess this is probably because OnePlus can't hold a candle to Google's postprocessing software.

Screen responsiveness- I picked up the otter box screen protector. Maybe it sucks and is causing the screen to seem comparatively less responsive at times. Maybe it's why the fingerprint reader doesn't seem amazing. The reader has about 30% worse consistentcy than the pixel. I haven't owned a screen protector from otter in the past but I don't think it's worth $35. I've had a no-name from Amazon that was less than $10 on my Pixel for over a year and it's still perfect I don't think it's possible to place the otterbox protector without getting bubbles under it.

The screen itself is amazing, it's bright, the colors are great, the animations are very pleasing to look at. Nova Launcher beta is amazing on this device. It was great on the Pixel too, but it's really amazing on here. I am not sure why it's still in beta, it doesn't seem to have a single bug.

The performance on the device is amazing. I installed proot-distro in termux and installed xfce desktop and it's the smoothest experience, it usually is a lot slower than what I'm seeing here. I like to be able to use vscode and sometimes need to view a full desktop version of a webpage and this is the best way to do that on any phone.

This menu is super cool-

Screenshot_2023-06-07-21-58-46-50_3822ac0e29cfec8970059bb21d01f05e.jpg


I still can't figure out if it's full compatible with my network (Xfinity so basically Verizon)
 
  • Like
  • Love
Reactions: Prant and g96818

Prant

Senior Member
Jan 23, 2017
152
114
OnePlus 7 Pro
OnePlus 10 Pro
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.

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.
 
  • Like
Reactions: Markus214

Markus214

Senior Member
Jan 22, 2009
440
49
Philadelphia
Google Pixel 2 XL
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.
 

muschiu35bv

Senior Member
Oct 19, 2013
260
33
OnePlus 10 Pro
Hello! I have oneplus 10 pro global version with latest version of oxygen os 13.1.0.522.
I have downloaded the stock boot img for NE2215 and patch img using Magisk Manager and fastboot boot patch image and latest in magisk manager i did direct install. The device has rooted but behavior it is wired. I don't get notifications for Gmail Google app Instagram on notification status bar pulling. But they appear in notification history only. And tasker not receiving permission for external storage. Even if I grant that permission I get error. Do you know how do i fix notifications not showing?
 

g96818

Senior Member
Dec 27, 2014
1,011
441
Hello! I have oneplus 10 pro global version with latest version of oxygen os 13.1.0.522.
I have downloaded the stock boot img for NE2215 and patch img using Magisk Manager and fastboot boot patch image and latest in magisk manager i did direct install. The device has rooted but behavior it is wired. I don't get notifications for Gmail Google app Instagram on notification status bar pulling. But they appear in notification history only. And tasker not receiving permission for external storage. Even if I grant that permission I get error. Do you know how do i fix notifications not showing?
Not sure. Never heard of it before. Might be something unrelated to the root.

Try perform a complete magisk removal to see if the problem persists. If it does, then try perform a factory reset. Make sure you're completely uprooted before performing the factory reset.
 

muschiu35bv

Senior Member
Oct 19, 2013
260
33
OnePlus 10 Pro
Not sure. Never heard of it before. Might be something unrelated to the root.

Try perform a complete magisk removal to see if the problem persists. If it does, then try perform a factory reset. Make sure you're completely uprooted before performing the factory reset.
i just did unroot by uninstall complete magisk and now everything is working. I will try to root again and see if same thing happens i will reset to factory settings
 
  • Like
Reactions: Squidd

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Color/Oxygen OS android 13.1 update

    NE2215_11.C.57 (13.1.0.591(EX01)) 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.57 OTA Incremental update:
    Official: https://android.googleapis.com/packages/ota-api/package/af566e789554f3b5dd025ae955f7faf6d391e566.zip
    Mirror: https://www.androidfilehost.com/?fid=10620683726822076082
    SHA-1: AF566E789554F3B5DD025AE955F7FAF6D391E566
    MD5: 505E87F83A18B67BA4C05403FE1803E0

    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.57 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.57 boot images (For reference only. Download not required):
    Stock
    SHA-1: 010AAA872687811DB472643ED9F0D975CA0BA1EC
    MD5: 5F704F5F7A61FA565355937B55D13D72

    Patched
    SHA-1: EE0EE521CAF91C53D1A3646CD6ED5E0E0EA3A3B6
    MD5: 49622B2F0AB48658F7EA568A254C5600

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

    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.
    1
    Thanks, it worked for me.

    What i did was flashed stock recovery for current software version (in my case its c.53) only and then reboot.
    Then unroot (restore image in magisk), patch stock boot in magisk then reboot.
    Then fastboot boot patched boot, reboot.
    Direct install magisk then reboot.

    After that i follow your step when upgrading for c.54 and so on until c.57.

    So far so good. Thanks.
  • 12
    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))
    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.