How To Guide OnePlus 10 Pro NE2215 ***ROOTED***

Search This thread

Nixeus2

Senior Member
Mar 11, 2020
185
31
Hello, my phone is 2215 and tried to flash your boot image. Phone boot but only some shortcurt with black wallpaper...have to rollback. Pretty weird.
 

NinoLatif

Senior Member
Mar 10, 2018
66
25
My NE2215 does not let me unlock the bootloader, it says it failed after using using: fastboot oem unlock command. I've tried everything, what should I do? I've already enabled unlock oem in developer settings
 

NinoLatif

Senior Member
Mar 10, 2018
66
25
First of all you shouldn't use fastboot oem unlock but fastboot flashing unlock. The previous command doesn't work on newest devices like oneplus 10 pro or pixel.
I am seconds away from throwing this device out of the window, with the new command given it says:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlock unknown partition 'unlock' error: cannot determine image filename for 'unlock'
 

mvk-wayne

Member
May 8, 2022
7
0
Hey guys,

I am a bit confused after reading most of the posts.

Is this rooting procedure working as described for the global version or not? for all versions or just for later versions than NE2215_11.A.12?

the only issue is the netflix app?

it would great if someone could put in short words the current situation. Thanks.

regards
mvk
 

mvincent2k

Member
Nov 19, 2018
29
6
OnePlus Nord N200 5G
Hey guys,

I am a bit confused after reading most of the posts.

Is this rooting procedure working as described for the global version or not? for all versions or just for later versions than NE2215_11.A.12?

the only issue is the netflix app?

it would great if someone could put in short words the current situation. Thanks.

regards
mvk

I can confirm...
1) Netflix fully works with workaround up to current Android 13 C.22 version just released this week.
2) Disney+ & Hulu do NOT work on Android 13 on this phone per my extensive testing with many variations of Magisk Hide/Shamiko or using LSPosed/HMA. Believe this needs an update from Magisk to correct detection on this device.

Good luck
 

mvk-wayne

Member
May 8, 2022
7
0
does it something to do with rooting using this procedure or it is a bug of this phone on Android 13?
 

mvincent2k

Member
Nov 19, 2018
29
6
OnePlus Nord N200 5G
FYI: Getting a bug on C22 that is reproducible and wanted to share for others. While on (usually an incoming) call screen will stay black and not come back on even if pressing side buttons or tapping screen.

Once call is ended, full functionality returns. Very annoying as you cannot search/use phone while on phone. Are others experiencing as well after upgrading as well?
 

g96818

Senior Member
Dec 27, 2014
724
298
FYI: Getting a bug on C22 that is reproducible and wanted to share for others. While on (usually an incoming) call screen will stay black and not come back on even if pressing side buttons or tapping screen.

Once call is ended, full functionality returns. Very annoying as you cannot search/use phone while on phone. Are others experiencing as well after upgrading as well?
That is annoying. The only bugs I ran into are fingerprint is not the default login method since C19 and the swipe down from the top sometimes stops working unless I turn off the screen and turn it back on since C22.
 

mvk-wayne

Member
May 8, 2022
7
0
This is for the Global 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

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
Hi,

some vendors named the EU Version as "EU Global version". Is this rooting procedure working with the Global EU version numbered "NE2213"? Thanks
 

beatbreakee

Senior Member
Aug 10, 2015
268
319
Frisco
Samsung Galaxy S10
My OP10 is NE2215. But how can I know if it is the Global Rom or not?
The 10 Pro series is as follows:
2210 China (Color OS)
2211 Indonesia (Color, Oxygen, or Hydrogen OS)
2213 Europe - Global (Oxygen OS)
2215 North America - (Oxygen OS)
2217 T-Mobile Exclusive

The only real difference is in the 2210, and the 2217. The 2210 has an OPPO proprietary OS, meaning it does NOT come with Google Play ANYTHING.. it uses a chinese store and service known as Heytapp ... The 2217 has a T-Mobile baked Bootloader, and Oxygen OS, with a hidden security bit that detects if the region changes. If that bit is triggered it can blow the RPMB fuse (it doesnt always) but this will trigger the " One-Plu-BaLoo!", my special nickname for the INFINITE BOOT LOOP! Further attempts to outsmart the phone instead of flashing the OEM stock shipped FW, will flip that "security bit" and your phone will go into an unresponsive state, where the only way to detect it by PC, is to open it and short out the Test Points. (Be Warned!) It CAN be circumvented as i have done a running count of 23 phones now, all T-Mobile without bootloop or brick. I have only bricked 1 T-Mobile which was mine, at the beginning which is how i learned in detail about this specific model. (Advice: If you have ANY desire or inclinations toward the possibility of modding/unlocking/rooting your phone, I would HIGHLY advise NOT purchasing the 2217 ... both the 2217 10 Pro, and 2419 10T are T-Mobile Exclusives, and both have special coding customized into their OS, to make their models the MOST locked down devices possible). To attempt doing ANY level of modification to one of these devices on Android 12, or 13 is a VERY VERY high stakes dice game, where the winning numbers are chosen by T-Mobile and the rulebook does not exist! I have seen IN PERSON, 3 of the exact same 2217 all pulled straight from the boxes, with IMEI in the same 100 batch, and every one on the 11_a.08 fw:
1 had direct fastboot access right out of the box,
1 could reach fastboot ONLY after setup then adb enabled and fastboot via command line,
Then the 3rd required setup ----> enable adb -----> MUST first boot to FASTBOOTD ----> Then you could command line boot to Fastboot.
(W . T . O . M .G . F?)

So bottom line is, if you can, just avoid the 2217. The only benefit of the 2217 is the "IP68" standard. It is the only of the variants that have it. The 2213 EU/Global has the MOST versatility, as it has ALL bands readily available of all the other variants combined! Otherwise I would have not kept either of these yet i have both 2217 and 2419, and i got both of them FREE thru Dad's executive discount. I still considered returning them! Great phones... Dont bend them, and Dont sit with em in your pockets and they will be awesome. I get nearly 30+ hours on both, plus the 10T goes from 2% to 100% in barely 20 min. 10 Pro Camera is better ... 10T seems a bit sturdier... but neither have the potential of the older brother, 9R as it is easily rooted, unlocked, and region swapped PLUS if you brick it, you can fire up MSM Tool and recover it. Brick either of the 10/Pro/R/T series, and you will be paying some one from a foreign country to log into your computer, and hopefully not rip you off.

Just some information for those who might be interested.

Cheers
 

g96818

Senior Member
Dec 27, 2014
724
298
Hi,

some vendors named the EU Version as "EU Global version". Is this rooting procedure working with the Global EU version numbered "NE2213"? Thanks
oneplus playing games since US-China relations are not good. The NA version was always the global model. this guide was made before oneplus repleased a eu "global" version. None of the files I'm posted here will work with 2213. You can refer to this post for your phone. https://forum.xda-developers.com/t/...r-magisk_patched-guides-ne2213.4429711/unread
 
  • Like
Reactions: Prant

Strawboy

Senior Member
Mar 21, 2011
102
15
Salt Lake City
The 10 Pro series is as follows:
2210 China (Color OS)
2211 Indonesia (Color, Oxygen, or Hydrogen OS)
2213 Europe - Global (Oxygen OS)
2215 North America - (Oxygen OS)
2217 T-Mobile Exclusive

The only real difference is in the 2210, and the 2217. The 2210 has an OPPO proprietary OS, meaning it does NOT come with Google Play ANYTHING.. it uses a chinese store and service known as Heytapp ... The 2217 has a T-Mobile baked Bootloader, and Oxygen OS, with a hidden security bit that detects if the region changes. If that bit is triggered it can blow the RPMB fuse (it doesnt always) but this will trigger the " One-Plu-BaLoo!", my special nickname for the INFINITE BOOT LOOP! Further attempts to outsmart the phone instead of flashing the OEM stock shipped FW, will flip that "security bit" and your phone will go into an unresponsive state, where the only way to detect it by PC, is to open it and short out the Test Points. (Be Warned!) It CAN be circumvented as i have done a running count of 23 phones now, all T-Mobile without bootloop or brick. I have only bricked 1 T-Mobile which was mine, at the beginning which is how i learned in detail about this specific model. (Advice: If you have ANY desire or inclinations toward the possibility of modding/unlocking/rooting your phone, I would HIGHLY advise NOT purchasing the 2217 ... both the 2217 10 Pro, and 2419 10T are T-Mobile Exclusives, and both have special coding customized into their OS, to make their models the MOST locked down devices possible). To attempt doing ANY level of modification to one of these devices on Android 12, or 13 is a VERY VERY high stakes dice game, where the winning numbers are chosen by T-Mobile and the rulebook does not exist! I have seen IN PERSON, 3 of the exact same 2217 all pulled straight from the boxes, with IMEI in the same 100 batch, and every one on the 11_a.08 fw:
1 had direct fastboot access right out of the box,
1 could reach fastboot ONLY after setup then adb enabled and fastboot via command line,
Then the 3rd required setup ----> enable adb -----> MUST first boot to FASTBOOTD ----> Then you could command line boot to Fastboot.
(W . T . O . M .G . F?)

So bottom line is, if you can, just avoid the 2217. The only benefit of the 2217 is the "IP68" standard. It is the only of the variants that have it. The 2213 EU/Global has the MOST versatility, as it has ALL bands readily available of all the other variants combined! Otherwise I would have not kept either of these yet i have both 2217 and 2419, and i got both of them FREE thru Dad's executive discount. I still considered returning them! Great phones... Dont bend them, and Dont sit with em in your pockets and they will be awesome. I get nearly 30+ hours on both, plus the 10T goes from 2% to 100% in barely 20 min. 10 Pro Camera is better ... 10T seems a bit sturdier... but neither have the potential of the older brother, 9R as it is easily rooted, unlocked, and region swapped PLUS if you brick it, you can fire up MSM Tool and recover it. Brick either of the 10/Pro/R/T series, and you will be paying some one from a foreign country to log into your computer, and hopefully not rip you off.

Just some information for those who might be interested.

Cheers
Thank you for the information provided. It is helpful. However, I'm still not sure how I can tell if I'm on the Global ROM or if I'm just on the US Rom. How can I verify?
 

beatbreakee

Senior Member
Aug 10, 2015
268
319
Frisco
Samsung Galaxy S10
Thank you for the information provided. It is helpful. However, I'm still not sure how I can tell if I'm on the Global ROM or if I'm just on the US Rom. How can I verify?
if you are on 2215, then its not global. The Global fw has ALL bands accessible. This honestly is nothing more than a fw "flex" on the EU model. There is nothing restricting the 2215 from accessing all the extra bands, except a few bits being flipped in the efs. I was able to trace down exactly which file and where it was located in the EFS, and using ONLY diag mode i opened the file, and saw exactly where they blocked those bands from activation. Its kinda a chump move that they pulled, because the Global fw is the one that gets the MOST attention, and always gets the most feedback when it comes to new release beta builds! In the US we actually help the development of all Global fw,, because that version is usually the one that is universal for all of our carriers here, so you end up with a lot more diversified input being that in every state we have at least 6+ carriers, therefore we torture test the networks and can identify problems in a much shorter time! But to cripple the device capability just over a GLOBAL label is drastic for ANY popular phone, and thats exactly what they did, cuz the main difference between the NA and EU is only the 6 disabled 4g bands, (which are primarily for those in china... indonesia). And honestly the extra 6 bands are all 4g, so there isnt much purpose for them unless you are in china. While they do have 5g access over there, it is highly prioritized, and thus throttled after paid data limits, due to the higher density & saturated areas of their much larger population. That plus smog factor seriously hampers data transfers as ive been told, so for them they need those bands to hit more towers or they drop to 2g speeds. (yikes!) .... But to answer your question again, no unfortunately if your model is currently flashed and showing 2215 then you my friend are on the US/NA fw.

I have been recently toying with QPST and specifically the EFS explorer, now that i have a proper 200+ page guide to every single tab/option/function/tool that is related and interacts with it, and it bewilders me as to why individual carriers choose to handicap a device, simply because they can. There are a ton of random little features, that are just disabled for no justifiable reason. But i will save that for another thread.

oneplus playing games since US-China relations are not good. The NA version was always the global model. this guide was made before oneplus repleased a eu "global" version. None of the files I'm posted here will work with 2213. You can refer to this post for your phone. https://forum.xda-developers.com/t/...r-magisk_patched-guides-ne2213.4429711/unread
Yeah bro, i hear you... Also they went stupid with the numbering system for no good reason other than to confuse ppl... The 10 Pro series all stem from a 2210 base model, and were released as (NE) 2210, 2211, 2213, 2215 and 2217 , Ch, In, Eu, Na, Tmo .... but the 10R is the (CPH) 2411 <all region> ... and the 10T starts (CPH) 2413, 2415, 2417, 2419, In, Eu (Global again), Na, Tmo... but THIS TIME "In" stands for India, whereas the 2211 "In" is actually for Indonesia. For the 10T India got their own build, while China got the same phone, under a completely different name, "Oneplus Ace Pro". The 10R hadnt even been released til late October this year, so why didnt they just kick the 10T series in starting with 2411? Then it would be easier for people such as myself who have BOTH phones. (During a VERY SLEEPY session where i was going to drastic measures, trying to revive my 2217, after it went unresponsive, I literally spent over 2 hrs trying to make QFIL work, once i opened it up and jumpered the Test Points... And then i realized one reason it was failing to even attempt to run was because i had loaded all the 2417 files! Not paying attention because the official fw only have the model #, and not the beginning letters, I finally stared at the file on my screen wondering,

"Who uploaded this fw to the server? Because they really need to watch the typos when they name the file... I mean 2417? Come on... That's like a whole different phone... .... Wait... Wha?" 😲

Thank god the firehose wouldnt take.... otherwise i might have been the 1st one here in this forum, with a WHOLE NEW kinda brick!, lol. 🤔
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    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
    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.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.
    3
    Hello, did you get the boot.img from the original firmware or did you extract from your device. If you have the full flash file for NE2215 please post a link. Thanks
    Got it from my device. I'll try to see if I can dump the files tomorrow.