How To Guide (Guide) Rooting, payload dumper, magisk_patched guides NE2213

Search This thread

dladz

Senior Member
Aug 24, 2010
14,025
4,625
Liverpool
Huawei Watch 2
OnePlus 8
Brilliant, not sure if I'm happy or sad or feel a bit used. Kind of sly is you're making money off other people's work in all honestly.

But tbh, he could have found this himself and said nothing, I wouldn't have known.

Ethically though, shouldn't be charging to root a phone.

Be quite funny if they want to return to stock...I shall remember the name
 
  • Like
Reactions: Duncii and g96818

Duncii

Member
Feb 11, 2015
11
4
groningen
You're very welcome mate, happy to help


Ok so here's my two cents on it.

You are talking about zRAM, any device that has 4GB or more simply does not need zRAM or swap memory.

Performance, stamina, speed is increased especially gaming performance as you don't have to rely on slower memory, the difference is massive on slower devices.

So yep, there is an option for it. But you genuinely do not need it, I promise you.

If you really want it on you can use Franco's kernel manager, click memory then zRAM and turn it on, but I have to say I really wouldn't; you don't stand to benefit from it at all, swap memory is just a lot slower and genuinely not needed.

Hope this help

Yeah google made a big deal out of it. it would be amazing and all.
But i share your 2 cents i was jus wondering if other people found the same when just looking for the extra ram. alltough it's not needed, I'm just wondering why it's disabled after the whole process. and if it's disabled after unlocking the bootloader or actually after you've rooted.
Because for me it's a first that I found out that things are blocked after rooting on oneplus. And that doesn't sit right with me.
 
  • Like
Reactions: dladz

Duncii

Member
Feb 11, 2015
11
4
groningen
No i never said i got paid for it.
I dont get paid for rooting.
This is the first time I actually need a guide because in my full OTA there wasn't a boot.img. And I couldn't find a solution that quick. i wasactullylooking for a TWRP just to boot. but it's nowhere to be found. So a little 4am google search later and I ended up here.
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
14,025
4,625
Liverpool
Huawei Watch 2
OnePlus 8
Yeah google made a big deal out of it. it would be amazing and all.
But i share your 2 cents i was jus wondering if other people found the same when just looking for the extra ram. alltough it's not needed, I'm just wondering why it's disabled after the whole process. and if it's disabled after unlocking the bootloader or actually after you've rooted.
Because for me it's a first that I found out that things are blocked after rooting on oneplus. And that doesn't sit right with me.
I think they maybe realised that 12GB is more than most laptops and for a phone it's sort of insane.. so yea. I really don't think it's necessary and hopefully neither do they.

I had 12 on my old phone (8 pro) barely used 7GB

I would always turn it off just for performance myself but I found that I never needed to on the 10, it was already done for me, I honestly can't remember if it was present prior to unlocking and rooting, if they're disabled zRAM when you root, I actually find that to be pretty innovative but I'm genuinely not sure if it was in or off before hand, soz man.
 
Last edited:
  • Like
Reactions: Duncii

Duncii

Member
Feb 11, 2015
11
4
groningen
I think they maybe realised that 12GB is more than most laptops and for a phone it's sort of insane.. so yea. I really don't think it's necessary and hopefully neither do they.

I had 12 on my old phone (8 pro) barely used 7GB

I would always turn it off just for performance myself but I found that I never needed to on the 10, it was already done for me, I honestly can't remember if it was present prior to unlocking and rooting, if they're disabled zRAM when you root, I actually find that to be pretty innovative but I'm genuinely not sure if it was in or off before hand, soz man.
The laptop im on now has only 8GB its a trasty workhorse and thats about it.
I currently own the OP8Pro myself with 12/256GB my biggest bottleneck is internal storage.
reset it a couple of months back and already used 112GB.
have a nice day mate, Goodluck at work
 
  • Like
Reactions: dladz

fma388

Member
Aug 27, 2014
21
5
Samsung Galaxy S8
Huawei P30 Pro
Hi guys,

I'm on NE2213_11_A.12 (EU version) rooted with latest Magisk.

The update NE2213_11_A.13 (it's an incremential update not full) is available since today on Oneplus Updater, so I would like to know what I have to do to apply it and keep the root ?

Do I have to follow the procedure of this guide "Update from 12 stable to 12+ stable whilst retaining root" ?

Thanks a lot
 
Last edited:

mystery007

Senior Member
Aug 21, 2010
235
110
Magisk-Patched for NE2213-11-A13 (OxygenOS 12.1, Android 12, NE2213_11_A.13)
Only boot via ADB not flash!
 

Attachments

  • magisk_patched_a13.img
    50 MB · Views: 29
Last edited:
  • Like
Reactions: dladz and trax69

Top Liked Posts

  • 1
    Hi! I'm stuck here because the tutorial from the second part no longer agrees, namely there is not the option in Magisk "Install to Inactive slot (After OTA)" but only the option "Select and Patch a file"! After I used the APP OnePlus local install apk to install the 4GB firmware that I downloaded with the oxygen updater.

    I have so far only unlocked the bootloader, copied the necessary files to the smartphone and created the pachted boot.img with Magistk 25.1 and copied it to the PC.

    any ideas?
    Install to inactive slot only shows when you're already rooted. Now that you copied the patched image to the PC, you want to run: fastboot boot nameof.img

    Once it boots, open Magisk, choose install, direct install.
    1
    ok, that means if i do the tutorial for the first time and had not rooted i can miss part 2 and go to part 3.
    thx
    I just told you what to do, it's extremely easy once you have that boot image patched.
  • 5
    OP UPDATED: Stock and patched boot images using magisk 25

    Oxygen OS NE2213_11_A.14 Stock boot image

    Oxygen OS NE2213_11_A.14 Patched boot image


    If they don't work (they will :) but if for whatever reason they don't) @spevil07 has been so kind to extract and patch and upload for you too, 2 posts up from here so drop the lad a thanks (y)

    Please use magisk 25 as it retains root and has a lot of under the hood fixes and tweaks for efficiency.

    Cheers (y)
    2
    Stock and patched Boot images for NE2213_11_A. 14
    Patched with stable Magisk 25.0
    1
    2nd

    Update from 12 stable to 12+ stable whilst retaining root


    Guide

    1. Download the relevant firmware for your device via oxygen updater

    2. Open Magisk and remove all the modules you have installed, then reboot

    **NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model

    3. Install the OnePlus local install apk listed below in downloads. Click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.

    4. Click install and allow it to go through the process

    **NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"

    5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)

    6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.

    7. Once your phones booted back up your system / files should all remain as they were and you should have root access.

    You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
    Tested to update from A.12 to A.13.

    Working perfectly (y) , thanks
    1
    Stock and patched Boot images for NE2213_11_A. 14
    Patched with stable Magisk 25.0
    Nice mate, will have to get them myself anyway. But yep, great that they're now here 👍🏻 appreciate it
    1
    Thank you fot thr files, but i dont know to do with them, am really bad.
    Patched i dont know, boot puts in the end. Thanks for the help.
    Then can i have that NE2213_11_A. 14 on my 2210?
    They're in the OP and also instructions on how to use them, have you managed to change region on your phone?
  • 17
    Hi all,

    Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself

    Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!

    Stock and patched images are UK/ EU NE2213 but the guides are universal and could be used on multiple devices.

    :)

    NOTE:

    For these guides the versions used are:
    Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:


    NE2213_11_A.12
    Magisk Manager v24.3 (24300) Stable


    NE2213_11_A.13
    Magisk Manager v24.3 (24300) Stable

    NE2213_11_A.14
    Magisk Manager v25 (25000) Stable this version retains root after a restart, more stable version over previous iterations.


    1st

    Extracting a boot.img using Fastboot Enhance

    Pre-requisites


    A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:

    A Windows 10 computer / laptop
    A full update downloaded firmware zip for your model (recommend oxygen updater)
    Payload dumper program for Windows.
    The local System Update Installer : normal local system update will not allow a reboot during installation, the one I've linked will.



    Process

    On your computer

    1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.

    Download from here: https://github.com/libxzr/FastbootEnhance/releases

    2. Download the firmware of your choice and open it using Winrar or a similar zip program, extract the file called payload.bin a folder of your choosing.

    3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents will now be shown.

    4. One of the files will be called boot.img, this is the file we'll be patching, click extract then copy this to your phone, root of storage which is called /sdcard.

    On your phone

    5. Open up Magisk and click Install / Update, if you don't see update then change channel, so this by changing the channel in magisk settings, it'll then show the install/ update buttons.

    6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" (which will be in the Downloads folder)

    You now have a patched boot.img ready to flash to either slot with fastboot or boot via fastboot, would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone may bootloop.

    NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed,so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.

    If you intend to follow the guide below with your own patched img then you shouldn't need to patch twice but it won't hurt if you do.

    ;)






    2nd

    Update from 12 stable to 12+ stable whilst retaining root


    Guide

    1. Download the relevant firmware for your device via oxygen updater

    2. Open Magisk and remove all the modules you have installed, then reboot

    **NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model

    3. Install the OnePlus local install apk listed below in downloads. Click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.

    4. Click install and allow it to go through the process

    **NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"

    5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)

    6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.

    7. Once your phones booted back up your system / files should all remain as they were and you should have root access.

    You can now install all your modules again so long as they're compatible with the firmware you've just updated to.



    3rd

    Rooting using fastboot commands


    Method 1

    Booting the patched image

    1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer

    **NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.

    2. Reboot your phone to fastboot
    and connect to your computer.

    3. Boot the magisk patched img

    fastboot boot magisk_patched (or name of your patched boot img)

    Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.

    4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.

    5. Select Direct install (recommended) then click ok.

    6. Allow magisk to permanently root your device then click reboot.

    You should now boot and remain rooted.



    Method 2

    Flashing to both slots


    1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer

    **NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop

    2. Reboot your phone to fastboot and connect to your computer.

    Command: adb reboot bootloader

    3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.

    4. Type the following.

    fastboot flash boot_a magisk_patched

    Press enter.

    fastboot flash boot_b magisk_patched

    Press enter

    fastboot reboot

    Press enter

    6. Your phone should now boot, open magisk and verify you're rooted.





    Troubleshooting

    If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.

    1. Connect your phone to your computer.

    2. Reboot the phone, then during the boot animation enter this command via ADB.

    adb wait-for-device shell magisk --remove-modules

    3. Allow to boot, modules will be removed and root should then be active.




    If there is no magisk install / update buttons.

    1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions

    2. Make sure that the update channel is on canary, then force close magisk and then re-open

    3. If it still doesn't work then update magisk using canary

    4. Last method to check would be to change to the beta channel in magisk settings, then install it.

    Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.




    Window's version

    Windows 7 will not work with fastboot, please use Windows 10

    USB

    Use USB 2.0 not 3.0 or 3.1

    ADB

    These are the files i use for ADB (1st in the below list) tested these on fresh installs of windows on several windows machines, all win 10

    Place them into the root of C so it reads C:\ADB much easier to navigate to that way.

    Bootloader unlock

    Boot to the bootloader with adb reboot bootloader

    type fastboot flashing unlock

    Agree to unlock - allow to boot.

    If you can't see the device using ADB

    Make sure USB Debugging is turned on

    Connect your cable to your phone and computer, when asked what you want your phone to do, click on transfer files, a driver will be installed.

    After this reconnect your phone and it'll prompt you with a disclaimer with a check box, check the box and click ok, ADB / Fastboot should now work.



    Files:

    Local System update APK, this must be used as the local OnePlus 10 Pro one will not allow a reboot during the installation, so you cannot install the Magisk boot image during an upgrade:


    ADB Files for Windows 10:

    Payload dumper program for Windows-
    https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ

    Oxygen OS NE2213_11_A.12 Stock boot image

    Oxygen OS NE2213_11_A.12 Patched boot image

    Oxygen OS NE2213_11_A.13 Stock boot image

    Oxygen OS NE2213_11_A.13 Patched boot image

    Oxygen OS NE2213_11_A.14 Stock boot image

    Oxygen OS NE2213_11_A.14 Patched boot image
    5
    OP UPDATED: Stock and patched boot images using magisk 25

    Oxygen OS NE2213_11_A.14 Stock boot image

    Oxygen OS NE2213_11_A.14 Patched boot image


    If they don't work (they will :) but if for whatever reason they don't) @spevil07 has been so kind to extract and patch and upload for you too, 2 posts up from here so drop the lad a thanks (y)

    Please use magisk 25 as it retains root and has a lot of under the hood fixes and tweaks for efficiency.

    Cheers (y)
    4
    OP UPDATED: Better late than never, both the boot image and patched boot images are up.

    Oxygen OS NE2213_11_A.13 Stock boot image

    Oxygen OS NE2213_11_A.13 Patched boot image

    Finally managed to get this horrific PC working where i am, turned out to be a cable that was failing on fastboot but not on adb? who knows, all i know is it took me over a day and 4 windows installations, bloody brutal.

    Anyway, i have everything i need now so the second another firmware drops it'll be here in a timely fashion, apologies for the wait.

    (y)
    3
    OP UPDATED:

    Added the local system upgrade APK as the built in one cannot be used, I do apologize if you've fallen foul of this ridiculous change.

    Please only install new updates using the OP system updater APK, listed at the bottom of the guide.

    Modified the guide to reflect changes.

    Here it is also:
    3
    Ok, you are very active here. are you moderat?
    Lol no mate, just like to be a part of a good community, seeing toxic, or unhelpful users is a bad thing to see. So if I can help change that for the better then I will.

    Plus the guides I make, my knowledge isn't anything special, but I like to simplify guides for users to keep this type of modding strong, my worst fear is android heading down the closed source road.

    Huawei have basically done that. Even after XDA partnered with them and really did help boost their sales (I read that somewhere) then they basically quit allowing users to unlock bootloaders, literally killing the modding scene for Huawei and honor devices..

    I think OnePlus is probably one of the last great open books amongst android devices, the pixel is probably in the same class in regards to modding, not sure on Sammy and my all time favourite HTC are a dead stick now, wouldn't touch Sony ever again, I think LG has gone the way of HTC just like many others.

    Plus I kind of make a lot of guides in work too, helps me learn and gives others a start point.

    👍🏻

    PS: not sure it would be a good idea to make me a mod 😂 I'd be like an angry child with a gun. 🔫 🤬