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

[dladz]

Hey
if I get a 10T 16GB RAM / 256GB Model. The process of rooting the phone is the same as 10 Pro correct?

Yes.. The process for rooting without twrp is the same for pretty much any android these days

 

[luckychukiye]

Yes.. The process for rooting without twrp is the same for pretty much any android these days

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?

 

[dladz]

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.

 

[dladz]

UPDATE: I've downloaded the update but not at my computer at the moment, will upload stock and patched images for C_21 ASAP

 

[dladz]

Furthermore if you're already rooted on 19 or 20 just follow the updating whilst retaining root guide in the OP.

It'll be tomorrow morning when I upload otherwise.

 

[az_r2d1]

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

 

[luckychukiye]

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?

 

[az_r2d1]

Which model of the 10 Pro do you got?

NE2215, 8/128

 

[luckychukiye]

NE2215, 8/128

Great! How do you like it?

 

[az_r2d1]

Great! How do you like it?

Great phone. Just need to get it unlocked

 

[dladz]

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.

OnePlus 10 Pro Bootloader Unable to unlock [NE2215]

Hi, I am trying to unlock the bootloader as it show status as "Device Lock" When I try to use the command "fastboot oem unlock", it showed " ... FAILED (remote: unknown command) finished. total time: 0.001s I then tried "fastboot flashing...

forum.xda-developers.com

 

[dladz]

OP UPDATED: C_21 stock and patched boot images made with 25.2

Please report back if found to be working.

cheers

 

[az_r2d1]

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.

OnePlus 10 Pro Bootloader Unable to unlock [NE2215]

Hi, I am trying to unlock the bootloader as it show status as "Device Lock" When I try to use the command "fastboot oem unlock", it showed " ... FAILED (remote: unknown command) finished. total time: 0.001s I then tried "fastboot flashing...

forum.xda-developers.com

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]

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]

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.

 

[dladz]

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]

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 !

 

[dladz]

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

 

[msohail_7]

it depends on how you rooted. If you "FLASHED" the magisk boot, then you cannot use OTA. You can only use OTA if you "BOOT" the magisk boot and performed a direct install from magisk app.

I have booted patched img. Could u guide me to update A18 and keep ROOT?

 

[dladz]

I have booted patched img. Could u guide me to update A18 and keep ROOT?

It's in the OP dude.