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

Search This thread

dladz

Senior Member
Aug 24, 2010
14,985
5,340
Liverpool
Huawei Watch 2
OnePlus 10 Pro
Thanks!. Both are good options. The 10T has double the specs though

Do you think even though it doesn't have Hasselblade that it should take good photos etc?
I can only speak for the 10 pro, I've been impressed by the camera.. I wouldn't read too much into the hasselblad moniker, it's simply a badge, doesn't make it any better or worse.

As I've said before though, I really wouldn't buy a OnePlus device mate, they honestly don't deserve a penny and are going down a path similar to Huawei and we all know where that ended up.
 
  • Like
Reactions: Prant

az_r2d1

Senior Member
Feb 9, 2012
65
9
Just got my 10 pro and trying to unlock the bootloader.
I've done this before on my 6T and never a problem.
But with the 10 pro, I can do adb reboot bootloader and phone goes into bootloader.
But then... fastboot devices doesn't show any devices. There is also NO sign of the device in device manager. no unknown device, no android device... nothing.
OEM unlocking is set. USB debugging is set.
What could be wrong? model is NE2215_11_A_17
 
Last edited:
  • Like
Reactions: luckychukiye

luckychukiye

Senior Member
Jul 6, 2022
53
7
Just got my 10 pro and trying to unlock the bootloader.
I've done this before on my 6T and never a problem.
But with the 10 pro, I can do adb reboot bootloader and phone goes into bootloader.
But then... fastboot devices doesn't show any devices. There is also NO sign of the device in device manager. no unknown device, no android device... nothing.
OEM unlocking is set. USB debugging is set.
What could be wrong? model is NE2215_11_A_17
Which model of the 10 Pro do you got?
 

dladz

Senior Member
Aug 24, 2010
14,985
5,340
Liverpool
Huawei Watch 2
OnePlus 10 Pro
Just got my 10 pro and trying to unlock the bootloader.
I've done this before on my 6T and never a problem.
But with the 10 pro, I can do adb reboot bootloader and phone goes into bootloader.
But then... fastboot devices doesn't show any devices. There is also NO sign of the device in device manager. no unknown device, no android device... nothing.
OEM unlocking is set. USB debugging is set.
What could be wrong? model is NE2215_11_A_17
What computer OS? What cable are you using? Where USB port?

Has to be the original cable, has to be at least windows 10, should use USB 2.0 not 3.0 or 3.1.

Can you run fastboot reboot? Does it reboot?

If not then it's driver related..

There's a thread relating to this issue on your device already.

 

az_r2d1

Senior Member
Feb 9, 2012
65
9
What computer OS? What cable are you using? Where USB port?

Has to be the original cable, has to be at least windows 10, should use USB 2.0 not 3.0 or 3.1.

Can you run fastboot reboot? Does it reboot?

If not then it's driver related..

There's a thread relating to this issue on your device already.


Windows 10, latest update. Using original cable from oneplus 6t. This cable worked fine on the one plus 6t on this exact same computer. Yes, there's a powered usb hub in between. When I plug the 6t in when it's in bootloader screen, I hear a windows ding noise meaning it sees it. When I do fastboot devices it reports the 6t.
I can't use the supplied cable because it has usb-c on both ends. My desktop doesn't have that.

Now, when I plug in the 10 pro (which shows booatloader screen) it does NOT show in windows when I run 'fastboot devices ' command. As a result the 'fastboot reboot' does nothing either.
The thing that I noticed is that when I plug the 10 PRO in , I do NOT hear the windows ding noise (meaning it sees something plugged in).
Will windows10 see something plugged in when there is a driver issue ?
What I expect to see in device manager is some unknown device.... but there is NOTHING.

The URL you mentioned was an issue because he used powershell. I use CMD in admin mode.

IT is ALMOST like the phone disables the usb port when it is in bootloader screen.....?

Also, is the driver for the 6t different than the driver for the 10 pro ?
 

dladz

Senior Member
Aug 24, 2010
14,985
5,340
Liverpool
Huawei Watch 2
OnePlus 10 Pro
Windows 10, latest update. Using original cable from oneplus 6t. This cable worked fine on the one plus 6t on this exact same computer. Yes, there's a powered usb hub in between. When I plug the 6t in when it's in bootloader screen, I hear a windows ding noise meaning it sees it. When I do fastboot devices it reports the 6t.
I can't use the supplied cable because it has usb-c on both ends. My desktop doesn't have that.

Now, when I plug in the 10 pro (which shows booatloader screen) it does NOT show in windows when I run 'fastboot devices ' command. As a result the 'fastboot reboot' does nothing either.
The thing that I noticed is that when I plug the 10 PRO in , I do NOT hear the windows ding noise (meaning it sees something plugged in).
Will windows10 see something plugged in when there is a driver issue ?
What I expect to see in device manager is some unknown device.... but there is NOTHING.

The URL you mentioned was an issue because he used powershell. I use CMD in admin mode.

IT is ALMOST like the phone disables the usb port when it is in bootloader screen.....?

Also, is the driver for the 6t different than the driver for the 10 pro ?
The 6T cable is not the original cable, believe me it matters.

Being connected is one thing being able to use fastboot is quite another.

I've had this issue and was able to use everything but fastboot, I even reinstalled windows, turned off driver signing, nothing worked.

Grabbed the original cable and bing it worked.

It's possible that this may not be the cause and I wouldn't have believed it if I hadn't seen it myself but it's definitely possible I can promise you.

As there's no device listed in device manager I think that's the cause.

Grab some other cables (the higher the grade the better) 6T is extremely dated by now and as I said it will matter.

Drivers are different yes.

1. Try a tonne of cables.
2. Check hidden devices in device manager (although I think this won't yield any results)
3. Try another USB port.
4. Try another windows device, PC / laptop.
5. Verify you have installed the ADB /fastboot drivers.
 

az_r2d1

Senior Member
Feb 9, 2012
65
9
The 6T cable is not the original cable, believe me it matters.

Being connected is one thing being able to use fastboot is quite another.

I've had this issue and was able to use everything but fastboot, I even reinstalled windows, turned off driver signing, nothing worked.

Grabbed the original cable and bing it worked.

It's possible that this may not be the cause and I wouldn't have believed it if I hadn't seen it myself but it's definitely possible I can promise you.

As there's no device listed in device manager I think that's the cause.

Grab some other cables (the higher the grade the better) 6T is extremely dated by now and as I said it will matter.

Drivers are different yes.

1. Try a tonne of cables.
2. Check hidden devices in device manager (although I think this won't yield any results)
3. Try another USB port.
4. Try another windows device, PC / laptop.
5. Verify you have installed the ADB /fastboot drivers.

ok, I am going to have to mess around with it more. The adb part seems to work fine. USed the latest platform tools. What's the best place to get the fastboot drivers? I assume you mean the usb drivers for when the phone is in the bootloader screen.
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
14,985
5,340
Liverpool
Huawei Watch 2
OnePlus 10 Pro
ok, I am going to have to mess around with it more. The adb part seems to work fine. USed the latest platform tools. What's the best place to get the fastboot drivers? I assume you mean the usb drivers for when the phone is in the bootloader screen.
Yes I do mean USB which is what's required by fastboot.

My money's on the cable, same thing happened to me.
 

az_r2d1

Senior Member
Feb 9, 2012
65
9
The 6T cable is not the original cable, believe me it matters.

Being connected is one thing being able to use fastboot is quite another.

I've had this issue and was able to use everything but fastboot, I even reinstalled windows, turned off driver signing, nothing worked.

Grabbed the original cable and bing it worked.

It's possible that this may not be the cause and I wouldn't have believed it if I hadn't seen it myself but it's definitely possible I can promise you.

As there's no device listed in device manager I think that's the cause.

Grab some other cables (the higher the grade the better) 6T is extremely dated by now and as I said it will matter.

Drivers are different yes.

1. Try a tonne of cables.
2. Check hidden devices in device manager (although I think this won't yield any results)
3. Try another USB port.
4. Try another windows device, PC / laptop.
5. Verify you have installed the ADB /fastboot drivers.

wow wow wow.
You nailed it my friend. It was the cable ! The oem 6t cable is the culprit !
I tried with the new cable that came with the 10 pro on another pc that has a built in usb-c port. It recognized it right away.
Then I used an aftermarket usb-c cable that I bought about 2 years ago and used the usb hub I was attempting the unlock on earlier. It recognized it !

I know to be able to charge the 6t at warp speed you need a different cable. IS that what is the problem here now? Does the 10Pro no longer use a non standard usb cable to charge at max speed?

Thanks again man. it seemed hard to believe at first but the cable is exactly what the problem was !
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
14,985
5,340
Liverpool
Huawei Watch 2
OnePlus 10 Pro
wow wow wow.
You nailed it my friend. It was the cable ! The oem 6t cable is the culprit !
I tried with the new cable that came with the 10 pro on another pc that has a built in usb-c port. It recognized it right away.
Then I used an aftermarket usb-c cable that I bought about 2 years ago and used the usb hub I was attempting the unlock on earlier. It recognized it !

I know to be able to charge the 6t at warp speed you need a different cable. IS that what is the problem here now? Does the 10Pro no longer use a non standard usb cable to charge at max speed?

Thanks again man. it seemed hard to believe at first but the cable is exactly what the problem was !
No worries man. It is a crazy thing. It happened to me, I've no idea what science is at play in those cables but it definitely makes a difference.

Really happy you got it sorted man..

Good times 👍🏻
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    I made a magisk patched boot.img for C25 with latest magisk (25.2) ONLY FOR NE2213
    Enjoy ;)
    2
    Thanks Oneplus for releasing C26 the day after 😆🤪
    Here you go for C26 (available with Oxygen Updater), still ONLY FOR NE2213
  • 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