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

Search This thread

Strawboy

Senior Member
Mar 21, 2011
102
15
Salt Lake City
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.


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. 🤔
Thanks BeatBreakee. I guess then I'm curious why the thread is a root tutorial for NE2215, but the OP states that this is for Global Rom. I'd like to root my device, but want to have 100% confidence going in first before I start messing around with things.

EDIT: Holy smokes, now I'm confused. I just looked at the OP again, and it appears the dialogue has changed. It no longers states that this if for global rom....maybe it was fixed by the individual who started the thread? hmm
 

beatbreakee

Senior Member
Aug 10, 2015
287
415
Frisco
Samsung Galaxy S10
Thanks BeatBreakee. I guess then I'm curious why the thread is a root tutorial for NE2215, but the OP states that this is for Global Rom. I'd like to root my device, but want to have 100% confidence going in first before I start messing around with things.

EDIT: Holy smokes, now I'm confused. I just looked at the OP again, and it appears the dialogue has changed. It no longers states that this if for global rom....maybe it was fixed by the individual who started the thread? hmm
No worries bro... as i stated in my reply, OP made a rather confusing conundrum out of the model numbers... they just have too many devices being crammed into the "2000" series... i just found a CPH 2421, and 2423 and those arent even OnePlus phones! Those jump right back to Oppo... But for the OP its understandable because the 10T Global is 2415... and i have found SEVERAL completely wrong fw identifications by a few "less english" speaking websites! But ive found em as well labeled wrong in the Oneplus Community pages, where the poster 1st called the CHP2417 10T the "Chinese - Global Variant" 😲 then a few posts down he called the 2413 the "European - Global Variant" 🤨 ... That's a whole lot of Oneplus 10T "Global Variants" considering its 100% verified ==> 2415 Eu Global Variant... but that guy was just posting as confident as if he had a 'PHD in Global Variantology' 🙃. So without someone who has literally torn apart the whole FW package, looking at everything inside as if i just broke a pinata, and all those files fell out, instead of candy... 👀 then it would be kinda ruckshot with identification of each. Every region wants the claim of "Global" because that fw will get the most 3rd party DL, and thus will have the most active development when it comes to feedback and making the mfg get to fixing whats broken. But seriously, i would not steer ANYONE in the wrong direction when it comes to stuff removed from stock fw.... 2213 and 2215 are almost identical, & you wont notice the difference unless you live in China. The ONLY extremely troubling thing i have found about ALL the 10 series, is that the T-Mobile variants ALL have hidden, undocumented, and never before heard of "Trip wires" in their builds! What i mean by never before heard of "Trip Wires", is: Processes, Actions, Flags, and Bin commands that a Google, Yahoo, Duck Duck Go, AND Bing search, yielded not 1 match for them! And when you type them into either an ADB shell, or directly in the terminal, they yield completely different error responses than a normal command that is wrong. ( "Function Undefined - Segment Variable Must Have "2" [Arg] ) <-- That one hurt my head!

I dont wanna dwell on it, cuz a few commands literally will disable a single antenna, or turn off your mic, and there isnt any commands that i fuzzed which would reverse the process, so accidently running them would require an MSM Flash to fix. But the "Trip Wires" are like traps set, just to brick your device. For instance, when flashing your BL to root your phone, on the T-Mo roms, ONLY A FEW are set up with an instruction that tells the phone to flip to the other slot on reboot. (Make sure to always have updated FB and ADB, along with tested magisk builds, cuz magisk should always install itself to the correct partition/flags when allowing the app to do the install! Manual flashing CAN accidentally break something! And google constantly changes variables or add new flags, which if your script calls for it, and it aint there, could cause a command to fail, but the script continues and your device reboots with a mangled flash... no good!) So when you're flashing to the inactive slot you let magisk do the work, after BOOTING a rooted boot.img. This is the CORRECT and safest way to go. But the 1st drop of TMO fw (11_A.03 on IN) literally has a control command set, for if the Aboot partition is accessed by any unsigned app, even if just to read or pull the file, then any reboot will auto flip BACK to the same slot, but it will allow the rest of the script to complete after booting. I really cant grasp that one, but it is kinda like the OS will grant system permissions to the script, but the commands will be sent at the stock files, so if they are system files, then it would brick your phone! Cant mess with system partition, really or secure boot & trust zone will stop the system from completing boot.... if I am correct then you would have PARTIALLY modified UN-PATCHED system files, and then a hard stop or panic when the secure boot fails... that is straight up malicious because they refuse to provide us an Unbrick option... yet they are making it happen to begin with. Bottom line is, that IF you get a T-Mobile model. and its working properly after modifying for Root.... Region... whatever.... 1st, go buy a lottery ticket... and then STOP making any changes to your file system, because TMO has an "Override_Developer_Mode_User_Opt" command embedded in the EFS file system, and for the life of me i could not find a reference as to what procedure can call it! But i do know that there are a few ppl incl myself who have met it in person! lol. The ones who have all know what im talking about... Every App on your phone gets locked, except settings... adb is removed from the "property:sys.usb.config=XX" function, and wireless adb is revoked.... all you can do is open settings, and stare at your phone when it rings... THAT is the command being called, when that happens, but it literally does not exist in ANY binary in the whole fw.

But TMO also uses "trick naming" schemes to place entire groups of command strings, and their arguments, pre-formatted inside system processes that you cant disable, or if stopped they auto re-enable themselves, or crash your device instantly. They even went as far as to alter the normal ussd dialer codes, and make a couple of them look as if they didnt work... but instead they actually signaled the phone to wipe the cache or initrd is instructed to force re-load a system file from a snapshot from hours earlier... i dunno, i just lost a lot of respect for tmobile, cuz if they are gonna go that far, either they have some nefarious plans coming in the near future for their devices, like some sort of Apple style encryption restricting all their devices... or some seriously ticked off programmers went rogue and set up all this crazy crap, then resigned & took the signing keys with them.. Whatever..... sorry for the long post.... i just really feel that when malicious intent is identified by a trusted carrier, someone needs to have it documented SOMEWHERE, so the next ME...YOU... WHOEVER steps up to the challenge, has a good set of notes on what has already been attempted, & what to avoid.

But if you arent using a TMO phone, then all youre missing is 6 bands that have 4 which are not even active in the US, and the other 2 are 3g here. Minus that, if you want Google services stay away from the 2211 fw, cuz you get "Heytapp" instead 😳
... and if you ARE on a TMO phone, just be careful and follow every instruction with no deviation, only after several ppl confirm it to work! Rumors brick phones....Old methods brick phones... Brand new, single target successful methods brick phones that are barely different! Your 100% safest way to do ANYTHING with a TMO phone (only the 10 series so far) is to get your sim UNLOCKED , and bootloader UNLOCKED properly, before doing a cannonball off that cliff into the TMO ocean!

"Thar be sum jagged rocks, and feral creatures that materialize outta nowhere, looking ta mess u up bad, when ur guard is down for a min!"
og.jpg
 
Last edited:
  • Like
Reactions: Prant

BeachNYC

Senior Member
Sep 1, 2014
107
41
Google Pixel 6 Pro
I'm on 2215 c22, and am unable to install lsposed. While the app installs without issue, the module, when installed, causes the screen to flicker on and off and repeatedly go to the lock screen. I then have to boot into safe mode, then reboot and re-enable all the modules in magisk except for lsposed.

Does anyone have any suggestions for how to get the lsposed module installed correctly? Many thanks for your help.
 

g96818

Senior Member
Dec 27, 2014
1,011
441
I'm on 2215 c22, and am unable to install lsposed. While the app installs without issue, the module, when installed, causes the screen to flicker on and off and repeatedly go to the lock screen. I then have to boot into safe mode, then reboot and re-enable all the modules in magisk except for lsposed.

Does anyone have any suggestions for how to get the lsposed module installed correctly? Many thanks for your help.
First off, LSposed does not have a stand alone app to install so uninstall whatever you installed and run a virus scan.

Make sure you're downloading and installing the correct version for your needs. Riru or Zygisk. Make sure you enable Zygisk in Magisk if that's what you're installing.

 
  • Like
Reactions: doc.K

BeachNYC

Senior Member
Sep 1, 2014
107
41
Google Pixel 6 Pro
First off, LSposed does not have a stand alone app to install so uninstall whatever you installed and run a virus scan.

Make sure you're downloading and installing the correct version for your needs. Riru or Zygisk. Make sure you enable Zygisk in Magisk if that's what you're installing.

Thanks for the information. I've attached two screenshots from the Lsposed "app." It's bizarre; I have it installed on my Pixel 6 Pro and Lsposed works with it perfectly. I'm going to try as you suggested and see if I have better luck. Thanks for taking the time to respond.



messages_0 (2).jpeg
.

UPDATE: Your diagnosis was exactly on point. Removed the app, and Lsposed works perfectly. Thanks so much!
messages_0 (1).jpeg
 
Last edited:
  • Like
Reactions: g96818

g96818

Senior Member
Dec 27, 2014
1,011
441
Thanks for the information. I've attached two screenshots from the Lsposed "app." It's bizarre; I have it installed on my Pixel 6 Pro and Lsposed works with it perfectly. I'm going to try as you suggested and see if I have better luck. Thanks for taking the time to respond.



View attachment 5785955 .

UPDATE: Your diagnosis was exactly on point. Removed the app, and Lsposed works perfectly. Thanks so much!
View attachment 5785947
glad it worked out for you. you should still run a virus scan.

lsposed had a standalone app in the past, but it is no longer required with the current lsposed module.
 

g96818

Senior Member
Dec 27, 2014
1,011
441
Hello. I am wondering how to patch my stock boot as it is quite different from yours.
I have the NE2215_11_c.22
Step 3: You can use either patch the stock boot or use my patched boot rom.
https://androidfilehost.com/?w=files&flid=333790
that's the initial release. you need to look at the post for the specific update https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/page-16#post-87796105

Either way
Step A: Patch the boot image using Magisk and copy the patched boot image to your computer.
Open Magisk, click install, and chose "Select and Patch a File" and click LET'S GO.
Select your boot image and patch it.

Step B: Reboot and boot the newly patched boot image. Your file name might be different than what I'm posting.

adb reboot bootloader
fastboot boot magisk_patched.img

Step C: Open Magisk and perform a direct install.

Step D: Reboot.
 

Desertio

Senior Member
Sep 11, 2011
390
39
Houston, TX
OnePlus 10 Pro
that's the initial release. you need to look at the post for the specific update https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/page-16#post-87796105

Either way
Step A: Patch the boot image using Magisk and copy the patched boot image to your computer.
Open Magisk, click install, and chose "Select and Patch a File" and click LET'S GO.
Select your boot image and patch it.

Step B: Reboot and boot the newly patched boot image. Your file name might be different than what I'm posting.

adb reboot bootloader
fastboot boot magisk_patched.img

Step C: Open Magisk and perform a direct install.

Step D: Reboot.
Thank you for your help. Worked out great.
 
  • Like
Reactions: g96818

Yaj00j

Senior Member
Oct 1, 2013
243
42
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.
 

Attachments

  • Screenshot_2023-01-31-17-41-43-63_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-01-31-17-41-43-63_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    204.3 KB · Views: 20

g96818

Senior Member
Dec 27, 2014
1,011
441
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.
 

Attachments

  • Screenshot_2023-01-31-04-35-04-42_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-01-31-04-35-04-42_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    123.2 KB · Views: 15
  • Like
Reactions: Yaj00j

Yaj00j

Senior Member
Oct 1, 2013
243
42
Need help. Tried to OTA update to NE2215_11_ C.26 and I have messed up.

Here's what i did:
Disabled all the Magisk modules
Uninstalled Magisk (restore Images)
Downloaded the new OTA let it install.. DID NOT REBOOT from OTA Window.
Came back to magisk > Install > 3rd OTA option
Reboot from magisk..
phone went into bootloop (kept reseting to orange state screen)
Power+vol-up and it finally booted.
The update was not installed.
(there was an issue preparing to restart. please try again later... with "reset update" option on the bottom) on the OTA section/page.
Root appears to be gone even though the magisk app is still there. clicking install only has one option (select and patch file)
Bootloader is still unlocked.
(the ram extension is back though :D so it was either magisk or lsposed that was causing it to bug out)

possible reasons for this mess up:
I forgot to disable all the phone security locks and fingerprints.
I had unchecked "apply system updates automatically on restart" in developer options.

any tips on where to go from here? should I just do the update to c.26 and then root again? or can i still salvage the root and do the ota again while keeping the root?
 

Attachments

  • Screenshot_2023-01-31-23-43-50-49_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-01-31-23-43-50-49_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    343 KB · Views: 25
  • Screenshot_2023-01-31-23-42-35-16_785cfb1f0fb0c9a2030c9b38a1c3479a.jpg
    Screenshot_2023-01-31-23-42-35-16_785cfb1f0fb0c9a2030c9b38a1c3479a.jpg
    264.9 KB · Views: 23
  • Screenshot_2023-01-31-23-42-43-82_785cfb1f0fb0c9a2030c9b38a1c3479a.jpg
    Screenshot_2023-01-31-23-42-43-82_785cfb1f0fb0c9a2030c9b38a1c3479a.jpg
    243 KB · Views: 23
  • Screenshot_2023-01-31-23-43-14-72_f7aa348215f5d566f9e4ca860f474209.jpg
    Screenshot_2023-01-31-23-43-14-72_f7aa348215f5d566f9e4ca860f474209.jpg
    287.8 KB · Views: 27
Last edited:

g96818

Senior Member
Dec 27, 2014
1,011
441
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.
 
  • Like
Reactions: Yaj00j

Yaj00j

Senior Member
Oct 1, 2013
243
42
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.

Thankyou for the quick reply, so is this what I do now:

Bootloader is already unlocked.
reset to bootloader
flash the c22 patched boot img
install magisk normally..
reboot
enable the update on restart setting (since update is already downloaded enabling it any earlier will install the ota before root/magisk)
uninstall magisk (restore images)
install magisk (option 3- ota)
reboot again (with the setting enabled this time)..

update:
followed the steps.. still got bootloop.
pwr+volup boot up same way to C22 without root.. partial magisk..
rooted again normally.
but now it says i need to download the ota again and it gives couldn't update installation problem error everytime. can't find the ota folder to delete either.
phone and root seem to be working fine even after rebooting. Any other method available other than factory reset?
 

Attachments

  • Screenshot_2023-02-01-03-29-33-56_f7aa348215f5d566f9e4ca860f474209.jpg
    Screenshot_2023-02-01-03-29-33-56_f7aa348215f5d566f9e4ca860f474209.jpg
    292.3 KB · Views: 18
Last edited:

g96818

Senior Member
Dec 27, 2014
1,011
441
This is why it messed up.

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

Thankyou for the quick reply, so is this what I do now:

Bootloader is already unlocked.
reset to bootloader
flash the c22 patched boot img
install magisk normally..
reboot
enable the update on restart setting (since update is already downloaded enabling it any earlier will install the ota before root/magisk)
uninstall magisk (restore images)
install magisk (option 3- ota)
reboot again (with the setting enabled this time)..

update:
followed the steps.. still got bootloop.
pwr+volup boot up same way to C22 without root.. partial magisk..
rooted again normally.
but now it says i need to download the ota again and it gives couldn't update installation problem error everytime. can't find the ota folder to delete either.
phone and root seem to be working fine even after rebooting. Any other method available other than factory reset?
Did you "Flash" or "Boot" the C.22 image?
Just unroot and update for now. I'll post the C.26 boot image in a bit.
 

Yaj00j

Senior Member
Oct 1, 2013
243
42
Did you "Flash" or "Boot" the C.22 image?
Just unroot and update for now. I'll post the C.26 boot image in a bit.
sorry.. i meant used the 'fastboot boot patchedboot.img' in adb, your version, which works perfectly fine, (it does break ram extension for me as soon as i install magisk even when all the modules are off)...

ota page from about device seems to be broken/corrupted now.. will removing root fix it? should i try the other method? (will it wipe the data?)
 

g96818

Senior Member
Dec 27, 2014
1,011
441
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.
 
  • Like
Reactions: Prant and Drethis

g96818

Senior Member
Dec 27, 2014
1,011
441
sorry.. i meant used the 'fastboot boot patchedboot.img' in adb, your version, which works perfectly fine, (it does break ram extension for me as soon as i install magisk even when all the modules are off)...

ota page from about device seems to be broken/corrupted now.. will removing root fix it? should i try the other method? (will it wipe the data?)
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
 

Yaj00j

Senior Member
Oct 1, 2013
243
42
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.
 
  • Like
Reactions: g96818

Yaj00j

Senior Member
Oct 1, 2013
243
42
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.
 
  • Like
Reactions: g96818

Top Liked Posts

  • There are no posts matching your filters.
  • 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.