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

Search This thread

foamerman

Senior Member
Sep 1, 2010
404
84
B-town
Hey guys got a question. I have a NE2215 I'm on 13 beta 2. Now when I use payload dumper to pull all the img files There Isn't a boot.img file the only one I can find is vendor_boot.img file. Now is that the one 1+10 uses for the boot.img?
 

g96818

Senior Member
Dec 27, 2014
655
240
Hey guys got a question. I have a NE2215 I'm on 13 beta 2. Now when I use payload dumper to pull all the img files There Isn't a boot.img file the only one I can find is vendor_boot.img file. Now is that the one 1+10 uses for the boot.img?
no. there should be a boot image.
 

demianrey

Member
Dec 9, 2009
28
0
hello, I already have my OnePlus 10 pro repaired again after ruining the bootloader haha.... is there already a solution for streaming applications after unlocking the bootloader?
 

g96818

Senior Member
Dec 27, 2014
655
240
NE2215_11.A.16 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.15. 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.16 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/792aa30c6b6e97630dc65389bd53d283dfb36c7c.zip
Mirror: https://www.androidfilehost.com/?fid=15664248565197209300
SHA-1: 792AA30C6B6E97630DC65389BD53D283DFB36C7C
MD5: 285A229285579EB78A38DFCEE1FF6336

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.A.16 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.16 boot images (For reference only. Download not required):
Stock
SHA-1: 87B0CAEDA1928F5746340FF446865B3419003752
MD5: 077ADC255B505CF8FF8590D16BFE472D

Patched
SHA-1: 4B143C6DE77353DBF8741FAD4A09756F31B3D98B
MD5: 21E1A215DB989CAE352E1D46AD02F494

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

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.
 

PickleRickHN

New member
Aug 31, 2022
1
1
Tegucigalpa
NE2215_11.A.16 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.15. 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.16 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/792aa30c6b6e97630dc65389bd53d283dfb36c7c.zip
Mirror: https://www.androidfilehost.com/?fid=15664248565197209300
SHA-1: 792AA30C6B6E97630DC65389BD53D283DFB36C7C
MD5: 285A229285579EB78A38DFCEE1FF6336

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.A.16 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.16 boot images (For reference only. Download not required):
Stock
SHA-1: 87B0CAEDA1928F5746340FF446865B3419003752
MD5: 077ADC255B505CF8FF8590D16BFE472D

Patched
SHA-1: 4B143C6DE77353DBF8741FAD4A09756F31B3D98B
MD5: 21E1A215DB989CAE352E1D46AD02F494

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

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.

Thanks a bunch for taking your time to upload all this information and files am always rooted thanks to you my friend!! thanks!!
 
  • Like
Reactions: g96818

Xpid3r

Senior Member
Feb 10, 2014
958
424
27
Hello,
Thanks for the Guide and Image files,
I successfully Rooted using magisk boot image,
But after Direct installing Magisk it removes Ram Expansion Feature..



Screenshot_2022-09-01-13-38-44-44_fc704e6b13c4fb26bf5e411f75da84f2.jpg
 

kobba89

Member
Jun 26, 2022
7
1
opened Magisk clicked uninstall > Restore images. Says "Restoration done" but I'm still rooted. Checked root checker to confirm and it says that I am. Didn't have this issue last time.
 

EtherealRemnant

Senior Member
Sep 15, 2007
4,379
1,715
38
Denver, CO
Google Pixel 7 Pro
Ah right. Ive tried both methods of updating and they both give "installation failed"
Seems like lots of people are running into this. I ran into it on my 9 with C.62 when trying to go to C.63 too and had to roll back to 11 and re-upgrade all over again to fix it. I have seen multiple posts about this problem now. I'm not sure if something from Magisk is breaking or what is going on but I wasn't able to fix it any other way.
 

SMcC2

Senior Member
Feb 22, 2014
287
142
Texas
OnePlus 6T
OnePlus 10 Pro
NE2215_11.A.16 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.15. 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.16 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/792aa30c6b6e97630dc65389bd53d283dfb36c7c.zip
Mirror: https://www.androidfilehost.com/?fid=15664248565197209300
SHA-1: 792AA30C6B6E97630DC65389BD53D283DFB36C7C
MD5: 285A229285579EB78A38DFCEE1FF6336

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.A.16 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.16 boot images (For reference only. Download not required):
Stock
SHA-1: 87B0CAEDA1928F5746340FF446865B3419003752
MD5: 077ADC255B505CF8FF8590D16BFE472D

Patched
SHA-1: 4B143C6DE77353DBF8741FAD4A09756F31B3D98B
MD5: 21E1A215DB989CAE352E1D46AD02F494

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

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.
Thank you for your post!
After multiple attempts the only way I was able to update was to patch the stock boot img with my own phone. I'm now successfully on 11.A.16 with root and with all my data and apps working properly.
 
  • Like
Reactions: g96818

g96818

Senior Member
Dec 27, 2014
655
240
Thank you for your post!
After multiple attempts the only way I was able to update was to patch the stock boot img with my own phone. I'm now successfully on 11.A.16 with root and with all my data and apps working properly.
Looks like you fell into the group where the patched file doesn't work. Glad it worked out for you.
 

g96818

Senior Member
Dec 27, 2014
655
240
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.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Upgraded to C.21 and everything went perfectly. (g96818 is the Man!) Followed instructions to get Netflix working so all good there.

    Problem:
    Disney+ and Hulu do not work anymore. Guessing they need a fix like Netflix. Hulu looks like it will play but never starts video. D+ gets error code 83 which is the unsupported device error when unlocked/rooted.

    What I have tried:
    -Uninstalled/Reinstalled
    -All permissions granted.
    -Have them both in Magisk denylist and tried with the Enforce option both On and Off.
    -Also tried using liboemcrypto module as well. No luck.

    Also zygisk is enabled and Shamiko is installed. It passes all safetynet checks as well.

    Any ideas on how to fix these?
    1
    Reboot out of safe mode if you haven't yet. Then enable all the modules in Magisk that you had enabled before except for Enhance mode for HMA (I think we don't need it at all for HMA to work). Then, reboot, enable the LSPosed module of HMA, check that the Magisk module stays disabled, reboot again and finish following the guide.
    So same issue with it active and working. I had to get the latest ver from git for service to run on 13 as it is specifically made as a fix for 13. Screenshots attached.
    1
    It might just be me, but I got c.21, followed the instructions (the same way I've been doing it for a long time now) and my phone rebooted into crashdump mode. I'm gonna try again tomorrow but I figured you might want a warning.

    I was able to switch my current boot slot to get back into my phone though.
    This has happened to a few people before. the only thing we could guess is that they phone downloaded a corrupt ota file. Try downloading it manually and use the oxygen updater to install.
    1
    Cool. What's the easiest way to get to C21 ? Do I need to re-lock bootloader?
    Nope, but if you're rooted I'd suggest unrooting, updating, and re-rooting by patching the latest rom. I'd recommend using Oxygen Updater to get the C21 package, and use local upgrade to install. Since local upgrade is "hidden" in OOS12/13, you will need a separate (official OnePlus) app to do it. It's explained in the oxygen updater app.
    1
    May still work.


    Last few posts
  • 5
    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
    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.