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

Search This thread

TheNewHEROBRINE

Senior Member
Aug 26, 2021
72
31
20
Italy
OnePlus 8T
Followed the above....
Rebooted nd now stuck on logo red dot with two dots circling....Is this the bootloop?

how an I recover?
Force reboot and hold down volume down until the phone finished booting. This will boot into safe mode and when you restart you will have all magisk modules disabled. By any chance did you install the "Enhance mode for HideMyApplist" module?
 

mvincent2k

Member
Nov 19, 2018
31
7
OnePlus Nord N200 5G
Force reboot and hold down volume down until the phone finished booting. This will boot into safe mode and when you restart you will have all magisk modules disabled. By any chance did you install the "Enhance mode for HideMyApplist" module?
when i start holding vol down it goes directly to fastboot
Having the Magisk module enabled while having the LSPosed module disabled is known to cause a bootloop, however the author of HMA discontinued the project and so it's unlikely that we will ever get a fix for this.
any way to get gata back? I have pics and other files installed
 

TheNewHEROBRINE

Senior Member
Aug 26, 2021
72
31
20
Italy
OnePlus 8T
whew...ok that worked...

rebooted and back in. What are the next steps?
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.
 

aNGERY

Senior Member
Aug 6, 2017
290
108
OnePlus 7 Pro
OnePlus 9 Pro
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.
 

unsafe8989

Member
May 14, 2011
40
17
Samsung Galaxy S4
OnePlus 6T
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.
Try doing all the steps again but when you install magisk onto the other slot OTA don't reboot using magisk when it prompts you too after flashing the inactive slot., go back to the system updater app and use that to "reboot" or "finish installation" and it will reboot successfully.
 

mvincent2k

Member
Nov 19, 2018
31
7
OnePlus Nord N200 5G
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.
 

Attachments

  • Screenshot_2022-11-03-02-27-43-59_084ab3bc34f7aa7ccff83653f52abafc.jpg
    Screenshot_2022-11-03-02-27-43-59_084ab3bc34f7aa7ccff83653f52abafc.jpg
    189.2 KB · Views: 42
  • Screenshot_2022-11-03-02-30-44-17_ebfa97b027035e61fe3517b303462652.jpg
    Screenshot_2022-11-03-02-30-44-17_ebfa97b027035e61fe3517b303462652.jpg
    297.7 KB · Views: 41
  • Screenshot_2022-11-03-02-30-18-63_aa90d5c381d1285e5f0a79a44c517696.jpg
    Screenshot_2022-11-03-02-30-18-63_aa90d5c381d1285e5f0a79a44c517696.jpg
    282.8 KB · Views: 41
  • Screenshot_2022-11-03-02-27-02-39_084ab3bc34f7aa7ccff83653f52abafc.jpg
    Screenshot_2022-11-03-02-27-02-39_084ab3bc34f7aa7ccff83653f52abafc.jpg
    274.6 KB · Views: 40
  • Screenshot_2022-11-03-02-28-45-23_6b8d254452bc4a3798e188525542e357.jpg
    Screenshot_2022-11-03-02-28-45-23_6b8d254452bc4a3798e188525542e357.jpg
    318.7 KB · Views: 41
  • Screenshot_2022-11-03-02-29-21-33_6b8d254452bc4a3798e188525542e357.jpg
    Screenshot_2022-11-03-02-29-21-33_6b8d254452bc4a3798e188525542e357.jpg
    140.5 KB · Views: 39
  • Screenshot_2022-11-03-02-29-46-95_6b8d254452bc4a3798e188525542e357.jpg
    Screenshot_2022-11-03-02-29-46-95_6b8d254452bc4a3798e188525542e357.jpg
    285 KB · Views: 41
  • Like
Reactions: TheNewHEROBRINE

mvincent2k

Member
Nov 19, 2018
31
7
OnePlus Nord N200 5G
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.
Ok so testing a bit. In HMA Stopped service and let it clear app cache in app. Rebooted and now get this for both...

Interesting they are opposites. D+ and Hulu Apps still do not work
 

Attachments

  • Screenshot_2022-11-03-03-00-37-25_aa90d5c381d1285e5f0a79a44c517696.jpg
    Screenshot_2022-11-03-03-00-37-25_aa90d5c381d1285e5f0a79a44c517696.jpg
    307.9 KB · Views: 32
  • Screenshot_2022-11-03-03-01-03-88_ebfa97b027035e61fe3517b303462652.jpg
    Screenshot_2022-11-03-03-01-03-88_ebfa97b027035e61fe3517b303462652.jpg
    296.7 KB · Views: 32

TheNewHEROBRINE

Senior Member
Aug 26, 2021
72
31
20
Italy
OnePlus 8T
Ok so testing a bit. In HMA Stopped service and let it clear app cache in app. Rebooted and now get this for both...

Interesting they are opposites. D+ and Hulu Apps still do not work
This never happened to me. Previously you were able to get green marks on those checks so probably there is a solution. If it can help, I'm not using Shamiko but only Universal Safety Fix with Enforce DenyList enabled.
 

g96818

Senior Member
Dec 27, 2014
732
305
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.
 
  • Like
Reactions: aNGERY

mvincent2k

Member
Nov 19, 2018
31
7
OnePlus Nord N200 5G
This never happened to me. Previously you were able to get green marks on those checks so probably there is a solution. If it can help, I'm not using Shamiko but only Universal Safety Fix with Enforce DenyList enabled.
Just tried that now too. Same results.
Just confirming are you saying to use HMA wirh Enforce or just Enforce without HMA at all?

Have you tried D+ and Hulu and do they work for you?

What exact modules do you have installed? Can you screenshot

Thanks
 

TheNewHEROBRINE

Senior Member
Aug 26, 2021
72
31
20
Italy
OnePlus 8T
Just tried that now too. Same results.
Just confirming are you saying to use HMA wirh Enforce or just Enforce without HMA at all?

Have you tried D+ and Hulu and do they work for you?

What exact modules do you have installed? Can you screenshot

Thanks
I'm saying to use:
- Universal SafetyNet Fix
- HMA
- Enforce DenyList enabled
- No Shamiko
I don't use D+ or Hulu but if it doesn't require login I can check.
I attach the screenshot of my modules (although some of them are unrelated).
 

Attachments

  • IMG_20221103_130936.jpg
    IMG_20221103_130936.jpg
    516.1 KB · Views: 43

az_r2d1

Senior Member
Feb 9, 2012
65
9
I just got a new 10 pro. I have done the oem unlock. The rest is stock, so no root yet.
Currently still on A17. (2215)
Does anyone have a full A17 image so I can extract boot.img and patch it with magisk.
I do have an incremental update for A17 but the boot.img extracted seems a lot smaller than what it should be?

Second question: I noticed oxygen update showing me C21 and it downloaded the full update (close to 5Gig). Is 13 stable enough to switch yet?

Thanks and sorry if I asked for the obvious. I didn't see A17 on the first page.
 
Last edited:

g96818

Senior Member
Dec 27, 2014
732
305
I just got a new 10 pro. I have done the oem unlock. The rest is stock, so no root yet.
Currently still on A17. (2215)
Does anyone have a full A17 image so I can extract boot.img and patch it with magisk.
I do have an incremental update for A17 but the boot.img extracted seems a lot smaller than what it should be?

Second question: I noticed oxygen update showing me C21 and it downloaded the full update (close to 5Gig). Is 13 stable enough to switch yet?

Thanks and sorry if I asked for the obvious. I didn't see A17 on the first page.
 
I just got a new 10 pro. I have done the oem unlock. The rest is stock, so no root yet.
Currently still on A17. (2215)
Does anyone have a full A17 image so I can extract boot.img and patch it with magisk.
I do have an incremental update for A17 but the boot.img extracted seems a lot smaller than what it should be?

Second question: I noticed oxygen update showing me C21 and it downloaded the full update (close to 5Gig). Is 13 stable enough to switch yet?

Thanks and sorry if I asked for the obvious. I didn't see A17 on the first page.
People have been saying A13 is performing a lot better than A12. I'm currently rooted on C21 and it does seem better than A12 in terms of battery at least
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Color/Oxygen OS android 13 update

    NE2215_11.C.26 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.26 OTA Incremental update:
    Official: https://android.googleapis.com/packages/ota-api/package/836c1138806f3f77658b417546ab1808b9e2aa49.zip
    Mirror: https://www.androidfilehost.com/?fid=4279422670115714150
    SHA-1: B368B528D2152FD9CC966F228402EFB480B7B643
    MD5: 2B2D5608C8B553549326122E1FA878C2

    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.26 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.26 boot images (For reference only. Download not required):
    Stock
    SHA-1: C68E7787180FE0C2FB0ECA0552805F897C303048
    MD5: CEFCAD2D846C192892C84DC463DC599D

    Patched
    SHA-1: 2BA2B71020B7431B80D884E800D83984E90C7233
    MD5: 48E01D8F2599DADDF1EB771F4C417D42

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

    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.
    1
    I rooted my NE2215_11_C22 using this method and it seemed to have worked fine. installed lsposed and modules such as call recorder enabler and core patch.
    However just yesterday i noticed that Ram Extension in 'about phone' has been disabled and does not work. even after restarting.
    Is it because of root or did i disable something while debloating?

    i could only find this reddit post about it:

    https://www.reddit.com/r/oneplus/comments/xfbtbr
    anyone else who rooted having this issue or tried this fix?

    you can see in the attached file that it doesn't show the added ram.
    If we were still on Android 12, then root disables ram expansion, but I thought oppo fixed that in Android 13 since mine works again.

    Wait for the next update to see if it gets fixed.
    1
    I had unchecked "apply system updates automatically on restart" in developer options.
    This is why it messed up.

    Turn that setting back on.

    Root your device as normal on c22, then do the same steps to update via ota.

    If you do the ota first, then you’ll need to wait for me or someone to upload the boot image.
    1
    you seem to be having issues updating so just try updating while unrooted. You can download the update file and the system updater from the update post above this post
    thankyou once again for your help :)

    I uninstalled magisk completely and updated successfully through OTA after reboot. (had downloaded the manual ota and apk just incase but didn't need it).
    will root it again using the c26 patched boot img and post results soon.
    1
    update:
    this time i patched the stock boot img from magisk and used that to fastboot from adb.
    I had 'disabled' all the modules before fully uninstalling magisk before i did the ota.
    after magisk install i found that shamiko module was already installed and enabled.
    worked fine. however ram extension is broken again. i think it breaks right after either the bootimg patch from fastboot or when you install magisk after the fastboot.
  • 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
    NE2215_11.C.26
    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.