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

Search This thread

Prant

Senior Member
Jan 23, 2017
100
67
OnePlus 7 Pro
Got it! Thanks for fast reply and fixing my steps.

To unroot - on the phone; using magisk manager disable/delete modules ( i have only systemless hosts) uninstall magisk itself with red button, reboot to phone and it should be unrooted, right?

Also if im going to make new root, not keeping old one - so again i need to use payload dumper after downloading firmware via oxygen + (extracting the boot.img)
then installing firmware c22 with local oneplus apk -> copy boot.img to /sdcard (at this point i should reboot to phone to check clean no-root Android 13?)
then using magisk manager (latest version) to patch copied boot file / then flash patched_magisk.img to inactive slot aaand reboot to phone.

Are we no issues this scenario? :) And Im at c22 android 13 rooted? :)
Regards,
You seem to have the process understood. As long as by red button you mean inside the Magisk app itself, yes. It should give you the option to unroot via "restore images." After that and a reboot... Following that set of instructions should land you on C22 Android 13 unrooted, then you can reroot as you've said.
 

beatbreakee

Senior Member
Aug 10, 2015
269
321
Frisco
Samsung Galaxy S10
OK.. so i got a few questions here, cuz i THINK i have figured out exactly why FB enhance has bricked a few devices when used to flash... i used the guide EXACTLY step by step for flashing a payload.bin from the same region i was currently on, and it took my phone out completely to unresponsive and not even detected by windows... I had to open the back up and jumper the test points, then have some chinese dude flash it back to stock to get it revived.... But GOOD NEWS is, by doing so it successfully UNLOCKED Fastboot mode on my 10T (Tmobile) which we all know was had the perma locked bootloader, and fastboot mode disabled.... Well NO MORE... after i superbricked, having an EDL flash with msmtool, not only brought Fastboot mode back, (just press Vol - at boot now)... it also made my bootloader TOKEN-LESS! ... as in a simple "fastboot flashing unlock" immediately prompted me to unlock it. Yet my 10 pro had to have a token, BUT using MSMtool to flash that back to stock, left my bootloader still unlocked, and none of that Orange mode stuff... Overall im ecstatic, cuz dude flashed both phones for me back to back! (Yay)

So my question is... when using FB enhance to flash a rom, and the screen says "Your on slot B" .... and you continue to flash without changing anything, does it only write to a slot if its INACTIVE??? Meaning by being ON slot B, did it flash that Payload to slot A?... cuz that explains it if so.... The a/b partition scheme HAS TO have any modifications being done via fastboot/recovery ONLY flashed to the slot that is not being used at the time. Fastboot will have conflicts but will continue trying to overwrite the images on the partition you are using , if you dont specify a flag that instructs it to switch slots on reboot. I read that if you dont instruct it to switch slots then it cannot write over any files currently loaded/in use, so not doing that will guarantee a mismatched set of files when you reboot and almost ensure a brick.

can anyone just simplify one thing for me.... when running a STOCK , out of the box 10 Pro, what is on Slot A, and what is on Slot B? And if FB Enhance says im using Slot B, then does that mean everything im doing, is only modifying A?
 

teeniv

Member
Jun 2, 2012
24
3
I was running C21 and wanted to update to C22 and keep root. I turned off all mods in magisk and rebooted. I downloaded the full OTA within settings (not Oxygen Updater). I clicked on install, and then it instantly rebooted (didn't give me a chance to do anything else) and showed me the orange state screen. When the devices booted it was updated but not rooted. I booted the magisk patched image of C22. I now have root and all my mods are working fine.

HOWEVER - now every single time I reboot it shows the orange state screen. Is there any way of preventing this? This wasn't happening to me before.
 

beatbreakee

Senior Member
Aug 10, 2015
269
321
Frisco
Samsung Galaxy S10
I was running C21 and wanted to update to C22 and keep root. I turned off all mods in magisk and rebooted. I downloaded the full OTA within settings (not Oxygen Updater). I clicked on install, and then it instantly rebooted (didn't give me a chance to do anything else) and showed me the orange state screen. When the devices booted it was updated but not rooted. I booted the magisk patched image of C22. I now have root and all my mods are working fine.

HOWEVER - now every single time I reboot it shows the orange state screen. Is there any way of preventing this? This wasn't happening to me before.
imho i doubt it. in every other fw prior to android 12, and on every oneplus phone, having an unlocked bootloader always triggered the same warning screen. its just like the Yellow "!" with the bootloader unlocked warning on samsung, the "press power to continue" warning on google pixel, , or similar warning screens on most every other model device. I just believe Google made an oversight with Android 12 and either forgot to put in the trigger that activated these screens, or in the case of OnePlus, maybe with all the different versions they have of EVERY phone, they didnt wanna bother mapping 40+ different devices each their own separate trigger.

I mean think about it... theres 4 different 10T, 4 different 10 pro, 4 different 10 R, and thats not including the special china version of each respectively with the Ace, Ace Pro, 10 Pro Extreme.... If you follow our threads at all you will find out that there are certain STILL UNIDENTIFIED differences in the model specific fw on each of the 4 variants of all the prior mentioned devices, that are JUST DIFFERENT ENOUGH that using one or more of the other variants EXACT SAME fw version, is causing devices to bootloop , or in many cases completely render the phones into a state that does not power on at all ! I can honestly say that NEVER before in my experience with Android, (going on 12 years) have i EVER seen 2 different models of the SAME PHONE, have such a catastrophic failure as to render the device "full brick" simply by flashing the other models fw. I cant speak for every android phone, but lets look at Samsung... One of THE MOST heavily restricted devices of modern phone era, (Since Galaxy S7). This particular brand usually REQUIRED a "frankenstein" build rom, with bootloaders, system images, modems, and userdata partitions of up to 5 DIFFERENT pieces of fw from other countries, devices, and sometimes homemade modifications, ALL be stitched together like a jigsaw puzzle that had the wrong pieces but you still taped them together... then zipped up and signed with some unofficial package manager into a flash file labeled, "Samsung Galaxy S_ COMBO fw"... THAT is what we had to either build ourselves or wait months for someone brave enough to do it for us, if we wanted Root access , and even then it was usually GLITCHED root, with many self inflicted issues after flashing... but we were able to flash these crazy malformed packages to any variant of each respective model, without fear of an unrecoverable brick. That is just insane when you think about it, on the most restrictive mfg besides apple, that we could flash these ill advised, sometimes dangerous combo fw and the phone still booted.... But flashing a ne2213 fw to a ne2215 phone WITH THE EXACT SAME VERSION FW, and each phone having the exact same hardware... not one resistor different! Might make your phone go into infinite Bootloop, or worse the No power, no buttons work, no charge Uber Brick state!?!

Tell me that aint the most ridiculous thing ever. Now pair that with the fact that EVERY oppo/oneplus phone each has 4 different variants, and several models are competing with each other being released within the same generation... ALL having to individually have that "Orange state" trigger added to all of their android 12 fw packages.... Oppo, Realme, Vivo, OnePlus and iQOO all owned by BBK Corp... That means OPPO Reno 8, OPPO Reno 8 Pro, OnePlus Nord 2T, POCO F4 GT, Realme GT Neo 3T, Oneplus 10 Pro, Oneplus 10T, Oneplus 10R, Xiaomi, Oneplus Ace, and Oneplus Ace Pro (plus a few i missed) ALL were released THIS YEAR from an Oppo partnered company! Im surprised that the "Orange State" screen is the only official thing that was missing in all the Android 12 builds... with the train wreck of all those devices PLUS all the previous models still supported each needing their own flavor of A12. YIKES!
 

C4RP1ST

Senior Member
Aug 11, 2010
60
24
OnePlus 10 Pro
finally unlock! never was so hard on any but devices. once passed this problem the procedure is very well explained. thanks for your help
 

Arksuga

Senior Member
Sep 20, 2021
63
26
Is there any difference if my phone is the UK version or the eu version if the model is still NE2213??
 

Top Liked Posts

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

    NE2213_11_A.16
    Magisk Manager v25.2 (25200) Stable

    NE2213_11_C_20
    Masigk Manager v25.2 (25200) Stable

    NE2213_11_C_21
    Masigk Manager v25.2 (25200) Stable




    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 XX stable to XX+ stable whilst retaining root


    Guide

    **NOTE- Although this may work the system may be unstable, especially when changing bases, eg: Android 11-12 or 12-13, so if you encounter strange behaviour then a factory wipe is advised.

    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, the android 13 local update apk is also required for rolling back to android 12.

    Android 13 local update apk

    Android 12 local update apk

    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

    Oxygen OS NE2213_11_A.16 Stock boot image

    Oxygen OS NE2213_11_A.16 Patched boot image

    Android 13

    Oxygen OS NE2213_11_C_20 Stock boot image

    Oxygen OS NE2213_11_C_20 Patched boot image

    Oxygen OS NE2213_11_C_21 Stock boot image https://mega.nz/folder/LNVxTDYA#yly9xpjFjQhe4De_jqyzbw


    Oxygen OS NE2213_11_C_21 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: I'm back on stable so will be keeping timely updates and images as soon as they become available.

    Heres the (better late than never) stock and patched A16 boot images

    Oxygen OS NE2213_11_A.16 Stock boot image

    Oxygen OS NE2213_11_A.16 Patched boot image
    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)
    4
    NE2213_11_C20 :
    boot.img and magisk-patched-boot