yashsingh1/xdaforums huggingface dataset:
[OnePlus Pad] XDAnonymus:
Thanks, thats good news, really.

I assume that you had unlocked the bootloader before that. How had you done that?

OEM unlock on in developer options, and after that?

Do we need any additional drivers for the pad for the fastboot commands on Windows?
[OnePlus Pad] poofdragon:
Yes, all of the normally required steps to enable OEM unlock. I use Linux, so I have no idea what the requirements for Windows drivers are. This is what I did, but I'm recalling from memory so YMMV.

Enable developer mode (Settings > About > tap Build number 7 times)

In Developer Settings

Enable USB debugging

Enable OEM unlocking

Connect a USB cable and authorize adb

adb reboot-bootloader
fastboot flashing get_unlock_ability # verify device can be unlocked
fastboot getvar unlocked # verify bootloader is locked
fastboot flashing unlock # unlocks the bootloader
fastboot reboot # if required

Rebooting the device will wipe all data

Proceed to complete the new device setup

Repeat steps 1-3

Get the patched boot.img

from https://xdaforums.com/t/root.4582847/post-88601695

OR get a copy of the full OTA from OxygenUpdater, and extract using https://github.com/ssut/payload-dumper-go. Then follow the directions for patching the boot.img using Magisk https://topjohnwu.github.io/Magisk/install.html

adb reboot-fastboot
fastboot devices
fastboot flash boot_a ./magisk_patched-26100_6jGPY.img
fastboot flash boot_b ./magisk_patched-26100_6jGPY.img
fastboot reboot
[OnePlus Pad] XDAnonymus:
It worked, thank you for your help!
[OnePlus Pad] Cmindo:
I'm on Windows, I'm able to boot into Bootloader but Fastboot is not recognizing my pad. I tried to workaround this by manually installing the OnePlus USB drivers via Device Manager but to no avail. This process works just fine for my OnePlus 9 Pro though...

Anyone able to interface with the Bootloader on Windows?
[OnePlus Pad] XDAnonymus:
I had the same problem, try on another usb port or another windows device or usb cable.
[OnePlus Pad] Cmindo:
Gave up on it, thankfully I have a Linux setup though, was able get my Pad rooted.

Thanks!!
[OnePlus Pad] trax69:
Can anyone share boot.img of OPD2203_11_A.13 version? Tnx
[OnePlus Pad] poofdragon:
I just upgraded to OPD2203_13.1.0.544(EX01) and found that Magisk would not patch the boot partition for some reason (unrecognized image format or some such). I believe what is happening based on block device ID is that Magisk is trying to patch init_boot_(a|b) and fails. I'm including the OTA boot image and patched boot image.

DO NOT REBOOT AFTER INSTALLING THE OTA if you intend to make a copy of your own boot partition as you will not have root to make an image.

I was able to capture an image of the non-init boot device anyway using dd:

dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img

After I had this boot image, I patched it in Magisk using the file patch method. For some reason I was unable to write back to the boot device using dd, so I rebooted to the bootloader / fastboot and flashed from there. Upon reboot I still had root.

Follow the commands in step 9 here swapping out the boot image file (you should only patch the boot device for the OTA, not the active boot device):
[OnePlus Pad] ichimei:
Anyone bought the pad from Aliexpress? I cannot unlock the bootloader on my device. The model is OPD2203 in the regulatory, and the ROM is global version.

I've turned on OEM unlocking and USB debugging in the developer options, then reboot with adb reboot fastboot. I'm able to enter the fastboot mode, but when I run fastboot oem unlock, it says FAILED (remote: Unable to open fastboot HAL).

I've also tried downloading the full image from oxygen updater and performing a local installation, but it says "verification failed" when I choose the downloaded image.

I suspect that the model from the Aliexpress official store is slightly different from those sold on the official website...
[OnePlus Pad] kouzelnik3:
First of all, try to use

fastboot flashing unlock

instead of

fastboot oem unlock

.

Don't forget to turn on OEM unlocking on developer options too.

For local update, use this app OP Local Update for A13 where you can install the update from.
[OnePlus Pad] ichimei:
I'm sure that OEM unlocking is enabled in developer options (have toggled and rebooted for several times).

fastboot flashing unlock doesn't work either. It says

FAILED (remote: 'Unrecognized command flashing unlock')

Thanks for the app, now I'm able to perform a local upgrade. Although this doesn't seem to help with unlocking... (tried unlocking with the full images of both EU and India versions, the errors remain the same)
[OnePlus Pad] ichimei:
I think I found where the problem is. Instead of fastboot mode, I should probably enter the bootloader mode. These two different modes are behaving differently on OnePlus Pad.

This might sound weird so let me explain. adb reboot fastboot enters an interface saying "Fastbootd Mode" which looks like the recovery mode, where you can touch the screen to perform some simple operations, like selecting the language and formatting data.

View attachment 5931617

In this fastboot mode, Windows (and the fastboot command) can recognize the pad, but it is unable to unlock the bootloader.

View attachment 5931613

However, adb reboot bootloader enters another interface which looks like the boot screen (oneplus logo & "powered by android"), but also shows a tiny line of [Fastboot Mode] (note that it is actually the bootloader mode).

View attachment 5931625

In this bootloader mode, Windows (and the fastboot command) is not even able to recognize my pad, as others have said.

View attachment 5931615

But I think there is a good chance to unlock the bootloader in this mode, so I'll find a Linux device and try it out.
[OnePlus Pad] kouzelnik3:
Mhm, interesting news. Let us know later, if you were successful in unlocking bootloader then, and how.
[OnePlus Pad] ichimei:
Good news! I have successfully unlocked the bootloader and rooted my pad.

Just as I expected, the first step is to enter the bootloader mode. (bootloader cannot be unlocked in the fastboot mode)

adb reboot bootloader

Next, execute the fastboot command from a Linux device. Windows won't recognize the pad in the bootloader mode.

fastboot flashing unlock

As soon as you execute this command, some instructions (which looks really tiny) appear on the screen of the pad.

View attachment 5931985

This step is important: Press Volume Up (or Volume Down)

in 5 seconds

!

If timeout, the unlocking will be cancelled, but the Linux shell will still show OKAY in this case. To confirm the unlocked status, run

fastboot getvar unlocked # should output "unlocked: yes"

Then you can reboot now.

fastboot reboot

The data will be wiped, and you should see the welcome screen soon.

To root the device, I flashed the magisk patched boot image (provided by @poofdragon above), just like other Android devices.

If you don't have Linux on the computer, you can use a Live CD instead of actually installing a Linux distribution. I booted from the Ubuntu CD image and installed the android-sdk package on it.
[OnePlus Pad] kouzelnik3:
Well, that's kinda strange that you cannot unlock it from Windows and you must event unlock it within 5 seconds from executing that command. Well, thank you for this info!
[OnePlus Pad] phenonymous:
Did you really mean "adb reboot bootloader" not "adb reboot fastboot"? Because that boots into fastboot and not fastbootd.

I tried to unlock the bootloader in fastboot mode and got stuck in a bootloop. On the oneplus forum there was someone who had the same problem with oneplus 9 and it was solved by locking the device again and redo the unlocking. It's not clear if this was done in fastbootd.

Anyway I tried that too but it still bootloops and now I can no longer access the bootloader. Holding vol up/down/both just boots into recovery.
[OnePlus Pad] phenonymous:
You can access it from Windows but you have to manually select the correct driver from the device manager. I don't recall which one I selected but just try until you find the correct one. Just make sure you have the latest adb and fastboot drivers from google.
[OnePlus Pad] ichimei:
Thanks so much! I'm able to run fastboot commands from Windows now.

What I did: In the device manager, select the device with the yellow mark, then select "update driver", select "browse my computer for drivers", select "let me pick from a list of available drivers", select "Android Device", select "Android Bootloader Interface", then it's done.

I run some simple fastboot commands like flashing unlock, and it works exactly the same as when from Linux.

Not sure if I installed fastboot drivers from Google before, I'm not downloading any drivers this time.

Sorry for multiple screenshots.

View attachment 5933097

View attachment 5933095

View attachment 5933093
[OnePlus Pad] ichimei:
Yes, unlocking is only possible under "reboot bootloader". The naming is really confusing...

According to the test on my device, I'm not able to unlock under "reboot fastboot" (fastbootd). "oem unlock" failed with "unable to open fastboot HAL", and "flashing unlock" failed with "unrecognized command flashing unlock". The message is the same even after I unlocked my device.

The bootloop is weird. Did you flash the magisk patched image immediately after the unlocking (before the rebooting and the factory reset)? Not sure if this is possible but, it is the only case I could think of that causes a crash.

I guess there may also be differences in the pads sold in different regions. May I know where (and which country) you bought the pad from? I bought from Aliexpress, so mine is probably a global, or Indian variant.
[OnePlus Pad] kouzelnik3:
So basically the unlocking and rooting proccess is the same as on previous phones, but you need to have proper drivers, right?

OEM unlock in Dev options, then "adb reboot bootloader", "fastboot unlocking unlock", confirm, then after reboot, "adb reboot bootloader" and there boot magisk patched image, once it reboots, then install directly, right?
[OnePlus Pad] ichimei:
For unlocking, it is the same except for "adb reboot bootloader" (some phones can be unlocked in the fastbootd mode), and press volume up (or down) to confirm in 5 seconds. Yes, you need to select a driver so that Windows can recognize the pad (downloading a driver is not necessary, I think).

For rooting, unfortunately I cannot boot the magisk patched image without actually flashing it. If I run "fastboot boot patched.img", it fails with "remote: 'unknown command'". It also fails in the fastbootd mode, with "remote: 'Unrecognized command boot'".

So the only way is to extract boot.img from a full image (which is available from the oxygen updater), send to a phone, patch it, send the patched file to the computer, and flash it.

By the way, there are two ROMs, Europe and Indian, right? Just realized that flashing a wrong boot.img could also cause a crash...

Update: I extracted boot.img from both ROMs and compared them. They are exactly the same, also the same as @poofdragon 's uploaded version.
[OnePlus Pad] phenonymous:
Yeah that's what I thought.

No I never flashed anything, just rebooted after unlock and it bootlooped immediately. Locked and unlocked again and fastboot was gone. My only theory right now is that used the wrong driver.

I bought my pad from oneplus store and it's the europe version.
[OnePlus Pad] ichimei:
Well, I don't feel like it's caused by the driver, as the fastboot program on the computer just acts like a terminal, and unlocking is just sending the "flashing unlock" command to the pad. As long as the command is correctly sent, the pad will unlock itself (without data exchange with computer). The problem is more likely to come from the pad.

Seems like the bootloader mode on some variants is buggy... since someone has encountered a bootloop right after rebooting from the bootloader, even without unlocking. May need reports from more guys.
[OnePlus Pad] kouzelnik3:
To be honest with all these strange behavior of the Pad that I am reading all along, I am not sure if I want to unlock the bootloader (even if I had every device, which I owned, bootloader unlocked and rooted).
[OnePlus Pad] Markus214:
Has anyone rooted and unrooted the OnePlus Pad yet successfully? I have rooted and am setup with magisk but not yet unrooted yet didn't want to take that chance yet lol
[OnePlus Pad] poofdragon:
Latest boot images and some updated instructions for difficult boot partitions:

replace boot_b with your inactive boot partition, and the if= path as appropriate

# su
:/data/data/com.termux/files/usr/bin # dd of=/sdcard/boot.img if=/dev/block/by-name/boot_b
# patch boot image with magisk
:/data/data/com.termux/files/usr/bin # blockdev --setrw /dev/block/by-name/boot_b
:/data/data/com.termux/files/usr/bin # dd if=/sdcard/Download/magisk_patched-26100_jgWIr.img of=/dev/block/by-name/boot_b
131072+0 records in
131072+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 8.87825 s, 7.6 MB/s
:/data/data/com.termux/files/usr/bin #
[OnePlus Pad] poofdragon:
I'm not sure what, if anything, would be a consequence of uninstalling root. I've accidentally done this by not properly patching the boot partitions, but the only issue is that you can't act as root upon reboot. The only thing related to rooting that would change your device in a meaningful way is oem lock / unlock as it forces you to factory reset.
[OnePlus Pad] kouzelnik3:
In which case you would need to use this? I am planning to root the Pad soon and I don't want to screw it. 😄
[OnePlus Pad] kouzelnik3:
So I succefully rooted my OnePlus Pad today. It is weird that now FKM constantly saying that CPU has more than 50 °C, but who knows, how accurate it is. It was saying for a while that it has 70 - 90 °C, but I can freely touch the Pad which wouldn't be possible if it has this temperature.

EDIT: Because of that - I downloaded other app for CPU and battery temperature and it is saying approximately 30 °C on both while FKM is somewhere between 40 and 90, so FKM is not optimised for Pad. Just to let you know. :)

Anyway, process of rooting was quite simple.

Via oxygen upader I downloaded latest full zip OTA,

then via fastboot enchance I extracted boot.img via built-in Payload dumper and with my OnePlus 10 Pro, which is rooted, I patched that boot.img

In Developer Option, I enabled OEM Unlocking and USB Debugging

Connected to PC, via ADB I send command "adb reboot bootloader"

Installed fastboot drivers for the Pad (the same as I installed for OP10P months ago, but OK)

"fastboot devices" detected the device then

After that I did "fastboot flashing unlock", then Volume Up for confirming it.

It brings back the fastboot mode after a seconds. Then I did "fastboot reboot"

Set-up the device

When it was set-up, again rebooted to fastboot ("adb reboot bootloader")

Just checked via "fastboot devices" that it is connected and recognised.

Then, when I had placed patched boot.img to the ADB folder, I tried "fastboot boot magisk_pad_592_boot.img" but I got "remote unknown command error" or something like that, which was surprising for me

So I did:

"fastboot flash boot_a ./magisk_pad_592_boot.img"

"fastboot flash boot_b ./magisk_pad_592_boot.img"

"fastboot reboot"

Done, did additional Magisk settings and my own settings, installed modules etc, but I was successful

I have included patched boot.img in the attachment which is applicable for EU Pad model for the OOS version 13.1.0.592. Enjoy and if you got any questions, feel free to ask.
[OnePlus Pad] bigtweety:
Hi @kouzelnik3,

Thanks for this recap of all steps to root the pad.

I have indeed succeeded by running just about the same process.

What troubles me however is that even though indeed, all seems ok, running direct install of magisk to patch the current boot image, fails with the following "unsupported/unknown image format" error.

Could you confirm whether you have the same issue on your install?

This for me is/will be an issue as soon as we receive an update and need to patch the inactive slot before reboot.

This means we will need to redo the whole extraction of boot img and offline patching until this is fixed.

Cheers.

BigT.
[OnePlus Pad] kouzelnik3:
When this error appears? It you are receiving update and trying to update after OTA? Or are you patching the boot image after a booting temporary?

Because I wasn't able to boot it temporary due to a strange unknown command, so I had to flash it directly via adb.

And in case of any future updates, I am not sure yet as I haven't received any update after I have rooted my Pad. We will see in few weeks!
[OnePlus Pad] bigtweety:
Hi,

I get this error from direct install on a flashed modded boot (same error as you when trying temp boot) without any os update.

I'm just trying to patch on top of itself which normally works well.

Would you kindly try it ?

Cheers.

BigT
[OnePlus Pad] kouzelnik3:
Same erorr for me.

I think this error can be caused because you are currently on one slot and because you probably didn't install the same update on second slot (which is currently lower version, than you current one). That's the logic of A/B partittions somehow.

But Patching the image itself is ok and working. Dunno about patching after OTA. This one we will see once an update is availlable.
[OnePlus Pad] bigtweety:
Hi,

Ya, thanks for testing it out.

Unfortunately I do not share your confidence on the results.

I just tested the exact same step on my op10t and it happily applied the direct install on top of the already flashed modded boot, where there was no current upgrade and therefore the inactive slot was indeed harbouring an older version.

I do strongly believe that we're going to have to patch externally when installing our next upgrade, but I guess only time will tell.

Cheers.

BigT
[OnePlus Pad] kouzelnik3:
Mhm, then something is different with oneplus pad's software and add you said, we will see later what's gonna happen after a new update.
[OnePlus Pad] phenonymous:
It turns out it was faulty hardware. So even if you'd normally void warranty by unlocking the bootloader, the problem wasn't caused by user error. So I will get a replacement board covered by warranty.
[OnePlus Pad] bigtweety:
Hi @kouzelnik3,

I received the latest update a week or so ago but it rebooted without giving me time to patch on top, so now I'm unrooted and can't re-root as I'll be traveling for a week.

Did you receive the update as well and were you able to patch it directly via magisk app ?

I think I'll try to swap to the previous boot slot and rerun the upgrade process and attempt the direct patching, but if you have already failed at it, it'll save me the trouble.

Cheers.

BigT.
[OnePlus Pad] kouzelnik3:
Hi! Thank you for your message. I have received the update too (or Oxygen Updater gave it to me), but as you are mentioning, I wasn't able to patch it directly via Magisk unfortunately. Pad has to be patched with PC as of now :(
[OnePlus Pad] bigtweety:
ah, thanks for your feedback.

we have no permanent solution then.

let's keep an eye out for a better solution and if found, summarize it here.

Rgds.

BigT
[OnePlus Pad] bigtweety:
@kouzelnik3, unfortunately, I can't seem to successfully reflash a boot.img (original from latest update or patched) without going into a bootloop.

Did you do anything different this time around ?

Rgds.

BigT.
[OnePlus Pad] kouzelnik3:
Nope, I didn't do anything different. I was rooted and when update appeared, I let the Pad update. Magisk direct flash to the other slot didn't work, so I updated the Pad and then I lost root. Before that I dumped the boot image and patched it before, and this image I flashed via ADB when Pad rebooted after the update and when I rebooted to fastboot after the first reboot after that update. Now it is working fine.
[OnePlus Pad] Nouts:
Hi everyone, I bricked my OnePlus Pad (stuck in BootLoop) while was trying to extract the payload bin from this tutorial : https://droidwin.com/how-to-flash-rom-unbrick-oneplus-via-fastboot-enhance-tool/

I was following the first (wrong) part which is "How to Flash ROM & Unbrick OnePlus via Fastboot Enhance Tool" instead of the 2nd part and I realized it at 8. where you flash payload.bin then my computer asked me for a file so I realized I was doing the wrong operation, I clicked cancel then I clicked on Reboot to System and then I end up having bootloop.

I'm pretty new to android rooting and I managed to do the first steps where your device gets detected in Fastboot mode by installing drivers for the ADB cmd and stuff but I guess I did a mistake right here ...

I tried to format data in the recovery mode but nothing changes, so right now I am trying to use MSM MTK Client (since Mediatek CPU) because my device is now undected on the PC so I can't use adb anymore ...

If any of you have to tips to help, that would be greatly appreciated !!!!

Thank you in advance ...
[OnePlus Pad] bigtweety:
Hi @Nouts, if you have access to fastboot, you should try to switch the boot slot to get back to your previous firmware :

fastboot getvar current-slot
fastboot --set-active=a

Good Luck.

BigT.
[OnePlus Pad] XDAnonymus:
Since the latest update (EX01), LSposed stopped working. Even after reinstalling the module, Magisk says the LSposed module is activated and I did not see anything unusual on the Magisk logs, but the LSposed manager app says that LSposed is not installed, and all the LSposed modules are not working. Ive used the latest zygisk realase LSposed, but also tried older versions and they dont worked either.

Any guesses what could cause the problem?
[OnePlus Pad] kouzelnik3:
I had this issues too, updating the LSPosed from the Telegram group helped me.

Try this link: https://t.me/LSPosedArchives

And use eg. version 1.8.6.6961 zygisk. It should work!
[OnePlus Pad] XDAnonymus:
That worked for me, thank you
[OnePlus Pad] altwu:
thanks for all the work trying to find a way to root the oneplus pad. i just upgraded from a oneplus 7 pro to a oneplus 11 phone and pad. i just went through the process of unlocking the bootloader and rooting the phone but not the pad yet. the process for the oneplus 11 is different than how it was with the 7 pro. on the oneplus 11, there's a boot partition and something new called an init_boot partition. magisk works with the init_boot partition, at least on the 11. maybe the pad is the same?

this is the guide for rooting the onplus 11.
[OnePlus Pad] kouzelnik3:
I had tried init_boot but it seems there is an issue with that partition. I was discussing with magisk developers and it seems this partition is empty or fake on the Pad, or there is another issue. Look at here

Direct Install fails on some MediaTek/Unisoc devices due to empty init_boot partition · Issue #7231 · topjohnwu/Magisk

Magisk cannot be installed directly on the OnePlus Pad. Device: OnePlus Pad Android version: 13 Magisk version name: ee34f77 Magisk version code: 26105 magisk_install_log_2023-08-13T17.05.25.log - ...

github.com
[OnePlus Pad] bigtweety:
Yes,

so for the time being, no direct install via the app nor temp flashing via fasboot is working.

The only way to root is fastboot flash even when upgrading on existing root.

If it's MTK/partition related, we can hope Magisk takes it into account at some point and fixes it (the direct patch at least) for us.

I wouldn't hold my breath for it though.

Rgds.

BigT.
[OnePlus Pad] teeniv:
Did the new magisk update fix anything?
[OnePlus Pad] kouzelnik3:
I haven't tried that yet, but when I tried patching boot image (not a direct install) it went through, so it seems something has changed.
[OnePlus Pad] teeniv:
I'm a bit confused now. What are the steps to root a fresh oneplus pad, and how do I keep root after OTA? Is it any different vs a oneplus phone?
[OnePlus Pad] kouzelnik3:
Stick with the guide in one of first posts. Updating steps are still the same. After you update the magisk to the latest canary, direct install and patching the second slot respectively might start working, too. If so, let me know, or I will test it, too, and then eventually edit the guide.
[OnePlus Pad] altwu:
post deleted