yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T Guides, News, & Discussion] Fredator:
Thanks @Devtick.

I have the A13 Rom from Oxygen updater too, and already backed up the boot.img from it on the computer

Your sentence, do you mean "You can use Magisk to install to inactive slot when the (rom) INSTALLATION finishes and before tapping on REBOOT" ?

If so, then it's perfect i get it, last thing i have to figure out is how to update magisk from 23 to 25 first, without f** up everything

I'm not sure if i can safely "direct install" magisk 25.2 over an already rooted magisk23 rom (?)

Thanks a lot guys
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Would you please share the link to that quote of mine because it is actually incorrect.

Please see section C. in the OP for the correct statement:

"When Magisk patches the boot image using either Magisk>Magisk Install>"Direct Install (Recommended)" or Magisk>Magisk Install>"Install to inactive slot" it creates a backup of the original stock boot image in a directory named /data/magisk_backup_<SHA1 of stock image>."
[OnePlus 8T Guides, News, & Discussion] mingkee:
The writer missed some critical parts:

1. Use command to pull stock boot after OTA (or MSM read back). This will have a stock boot if reverting in Magisk doesn't work

2. Flash patched boot in fastbootd

BTW, I have yet decided to install A13 due to apps compatibility with rooted environment especially Netflix and cable TV apps
[OnePlus 8T Guides, News, & Discussion] zander21510:
FYI, step 4 on B2.1 is wrong for Android 13 NA, I followed the steps installing to inactive slot before clicking "install now" from the MyApplication2 app in Android 12, it did end up prompting to reboot so the initial extraction does not install the boot partition, or whatever is done is overwritten during the install process.

Now my phone is f*cked as it won't boot to the old Android 12 slot..not blaming anyone but just FYI if anyone is attempting to go from rooted A12 to A13 Global using that method, make sure to install to inactive slot AFTER clicking Install Now and BEFORE rebooting...

Edit: thankfully since A13 is a full update and not incremental, if anyone runs into the same issue it's easy to patch the boot.img from the OTA using the payload dumper in the OP, boot from the patched boot, and then direct install to retain root for future OTAs.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
The sentence after the one about EU/IN is referring to EU/IN, not NA.

I'll change it to make it clearer.
[OnePlus 8T Guides, News, & Discussion] zander21510:
Yeah only realized after I did it, my fault for not stopping when it didn't auto reboot.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
But it was good that you were able to get things fixed using payload dumper.
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
Hi

I have 8T KB2003 with android 13 F.13 and I want to install F.15 (full download with Oxygen Updater).

7 days ago I did a hard reset.

I follow the guide in point B.2.1 but in point 3 (Magisk>Uninstall Magisk>Restore images) Magisk tells me it can't find stock boot images (probably due to hard reset).

How can I fix it?

Thank you
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Firstly you'll need a copy of the stock F.13 boot image.

Then you'll need to manually install it to the active slot. You'll find the necessary command in B.2.3 step 3.

Fyi, I tried using B.2.3 (my preferred method) to install the INCREMENTAL update and the system wouldn't boot. It took me a really long time to get back to F.13.

But you're using a full download so B.2.1 may work for you.
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
Ok. I have it.

Ok. I'm using Adb.

My active slot is _b

Is this the correct commad ?

"adb shell dd if=boot.img of=/dev/block/by-name/boot_b (or boot.img_b ???)"

(boot.img is in the adb folder)

I'm sorry but I'm not very practical

Thank you in advance
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Shell commands on the phone (which is what you're running) don't have access to files on your PC.

If you pushed the boot.img to your phone's sdcard then you could use adb shell dd if=/sdcard/boot.img of=/dev/block/by-name/boot_b

Alternatively you could use fastboot commands in bootloader mode.

But providing scripting help is off topic for this thread. If you need more help, pm me.
[OnePlus 8T Guides, News, & Discussion] bertmag:
<Moderator Edit>: Removed off-topic content.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
@bertmag This is a how-to thread for rooting, not an archive of boot images.

Please put your helpful post in a more appropriate thread.
[OnePlus 8T Guides, News, & Discussion] mingkee:
I finally update the old 8T updated to T.

However, the ROM from updater seems to be different because boot causes Wi-Fi problem.

Fortunately, I managed to get patched boot from another thread, and Wi-Fi is working now.

However, now it shows "orange status" on boot, but Integrity Checker still shows 2/3 passed.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
The Orange State is again showing in OOS 13 (as it was in OOS 11, but not on OOS 12) if your bootloader is unlocked.
[OnePlus 8T Guides, News, & Discussion] mingkee:
I will have new 8T updated to T tonight. I feel comfortable enough to update.

This time I will pull out stock F13 and F15 boot and post them

A side note: TV out is not working still
[OnePlus 8T Guides, News, & Discussion] BillGoss:
The whole point of the OP is to show you how to do things for yourself.

You can get a copy of the new boot image by using shell commands if you are rooted after installing the update and before rebooting.

Or you can install the update and reboot and lose root (which is ok) and then use the MSM tool to get a copy of the new boot image.

And then you can use Magisk to patch the new boot and then root your phone again.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
See https://xdaforums.com/t/guide-root-and-keeping-root-options.4387977/post-87964141

Also, please use English in your posts or provide an English translation for it. See point 4. in https://xdaforums.com/t/xda-developers-forum-rules.4200559/
[OnePlus 8T Guides, News, & Discussion] mingkee:
Tip:

If you're stuck when update to F15, enable "automatic system update" in Developer Setting", and restart the update fixes the problem
[OnePlus 8T Guides, News, & Discussion] mingkee:
A side note: you can get USNF 2.4 and it can pass 2/3 play integrity

Kudos to @kdrag0n
[OnePlus 8T Guides, News, & Discussion] elwholo:
So i made a mistake and didnt perform a backup of the stock recovery of oos13 where can i get the stock recovery for A13 ?
[OnePlus 8T Guides, News, & Discussion] elwholo:
I succefully updated to F15 using this guide thank you very much
[OnePlus 8T Guides, News, & Discussion] zeus_r6:
Has anybody successfully obtained root starting from OOS13 on their KB2005?
[OnePlus 8T Guides, News, & Discussion] elwholo:
Yes im running the latest update thanks to this guide im using kb2005 too
[OnePlus 8T Guides, News, & Discussion] zeus_r6:
Did you start from an unrooted 2005 with OOS 13 A13?
[OnePlus 8T Guides, News, & Discussion] elwholo:
Yes I rooted a13 with TWRP but it can also be rooted through patch boot img method
[OnePlus 8T Guides, News, & Discussion] karib97:
When I try to launch Msmsdownloadtool It gaves me Software image not exist (on Win 11).

What could be the problem ? my bootloader is unlocked, my boot partition is _a

I'm on one plus 8 pro 2025-F15
[OnePlus 8T Guides, News, & Discussion] BillGoss:
This is a rooting thread, not an MSM support one.

Ask you question in https://xdaforums.com/t/op8t-oos-kb...l-to-restore-your-device-to-oxygenos.4180837/
[OnePlus 8T Guides, News, & Discussion] slewis1972:
Trying to do latest update and keeps saying unverified using full and My Application 2. Any ideas way round it, do I need to edit the zip update? Am rooted etc
[OnePlus 8T Guides, News, & Discussion] The Apostle:
@BillGoss, If I decided to not worry about losing root, can I just install the OTA through the device via system--->system updates?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Did you enable Settings>Developer options>Automatic system updates?

If you had read the OP Community F.15 update post (https://community.oneplus.com/wap/thread/1227746046743412744) you would have seen this mentioned in the pinned reply.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
If you are rooted, then you can't just install the update because F.15 is an incremental updates so it expects to find a stock boot (and recovery) partition.

So, as long as you make sure that both of those partitions are stock, then you can use the system install (but also see the post just above yours). That's essentially what B.1 does, except that it doesn't mention the recovery partition.
[OnePlus 8T Guides, News, & Discussion] The Apostle:
Thanks. I'm still on 11.0.13.13 and I was hoping to avoid B.1. Guess that's not an option.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Since your on OOS 11, then the update will a be full image, so no need to restore stock images.

So you can just install it, turn airplane mode on (to avoid loosing Play verification) and then do a first time root.

There are always options. It all depends on what you want to do. Which is why the OP is so long and needs pictures 😄.
[OnePlus 8T Guides, News, & Discussion] slewis1972:
Yep, got that already enabled. Think it's possibly due to incremental update. May need to wait till full.
[OnePlus 8T Guides, News, & Discussion] The Apostle:
Wouldn't I need to enable airplane before the install?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Not if the system needs to download the file.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
After my rather messy update to F.15 (see https://xdaforums.com/t/guide-root-and-keeping-root-options.4387977/post-87960237) I'm very pleased to say that the update to F.62 was a breeze.

Here's what I did:

I didn't wait for the update to get to my phone. Instead I downloaded the incremental update for KB2003 using Oxygen Updater.

Then I followed process B.2.3 CLI because it's my preferred method since no PC is required. Note, however, that I make really sure that my phone (including TWRP backups) are synced to my PC before I start in case anything goes seriously wrong.

And, I'm happy to say, it worked like a charm! Simple!
[OnePlus 8T Guides, News, & Discussion] Gyalist:
I downloaded the full update using Oxygen Updater and followed B.2.1 Local Install. It went perfectly even though I forgot to backup my phone!
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
I confirm.

B.2.1 is the best and fastest way to update
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Interesting post in OnePlus Community: https://community.oneplus.com/wap/thread/1274315994487586816

I had the boot loop issue when I rebooted from the Magisk reboot screen. I got the phone into bootloader, switched slots, rebooted, and it came up on F.15. I went to the Updater screen and it showed me that it was ready to install. I tapped on the Install button and it rebooted and came up on F.62.

On my other 8T, I rebooted from the Updater screen (NOT the Magisk screen) after installing Magisk to the inactive slot and that worked perfectly.

I have no idea what holding down the Vol Up key does to make a difference to the boot looping.
[OnePlus 8T Guides, News, & Discussion] TheNewHEROBRINE:
I found this inside Magisk code. Pressing volume up seems to disable system-as-root. However, I'm not sure about the implications of this.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Interesting! But, like you, I also have no idea what this means.
[OnePlus 8T Guides, News, & Discussion] elwholo:
I once again updated to F62 using B.1 Thanks again !
[OnePlus 8T Guides, News, & Discussion] Victroid:
Hello @BillGoss,

We have talked in the past and you helped me upgrade from A12 to A13. You recommend me to use the TWRP Orange Fox. This time I need your advice again, I am in F13, do you think I could go up to the F62 again flashing from OrangeFox the complete F62.

A thousand thx
[OnePlus 8T Guides, News, & Discussion] BillGoss:
This thread is about rooting and keeping root. This is NOT an upgrade thread. Ask the question in an appropriate thread or send me a PM.
[OnePlus 8T Guides, News, & Discussion] Victroid:
Sorry Bill I forgot to tell you that I have it rooted and they want to go up to F62 keeping it. When you helped me to get to Android 13, you recommended me to do it with OrangeFox, having previously downloaded the full version of OxygeUpdater and the process was quick and easy. Do you think I could apply it again this time? Thank you very much and sorry for the inconvenience.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I think you have enough information to make your own choice now as to which method you want to use. Scary, but at some point you have to bite the bullet.

Just make sure you back things up so that you can restore your current systems and data in case you end up having to use the MSM Tool.
[OnePlus 8T Guides, News, & Discussion] Rootk1t:
I presume, this section needs and update concerning OOS13, as this should have been already tested on OOS13.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
You would thinks so, but given that the update is available in Oxygen Updater a lot earlier than in the system update, I've always ended up manually downloading the update 😄
[OnePlus 8T Guides, News, & Discussion] Victroid:
Thx for all finally did it with OrageFox for upgrade and rooting again. Maybe new method ;)
[OnePlus 8T Guides, News, & Discussion] GIutton:
Has anyone else had their contacts app no longer sync after rooting? Any fix for this?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I've thought about using TWRP/OF to keep root with an update, but it gets rather complicated if you're installing an incremental OTA. That's why I've not provided details for the process - I want it to be a solution that works irrespective of the type of update.
[OnePlus 8T Guides, News, & Discussion] Victroid:
Indeed, this process with TWRP or OF only works when the OTA is free

completely and it is not an incremental update.
[OnePlus 8T Guides, News, & Discussion] Zeryth:
Hey I wanted to point out that on EU OOS 13 once you get the update notification local install gets greyed out due to the scheduled update. To fix it you need to find the software update app in your apps and clear data to re-enable the local install option. think that would be good to add for the people who run into the same problem.
[OnePlus 8T Guides, News, & Discussion] Rootk1t:
Do you just flash full OOS13 ota via TWRP/OrangeFox and install Magisk straight afterwards?
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
@BillGoss, 👋

Thanks, as always, for maintaining this thread. I tried to update to F.62 today using the B1 method (which has generally worked for me) but I hit a snag when I get to the final reboot step, after re-patching the boot image and putting the phone in airplane mode. At this point, using the restart button from system update actually continues the update process and I end up with the following errors:

03-16 07:59:59.682 5345 14754 I SystemUpdate: [Execution,SynchronizedUpdateEngine] Slot switch operation completed with non-success code: 20
03-16 07:59:59.686 1950 1950 I update_engine: [0316/075959.686864:INFO:metrics_reporter_android.cc(159)] Current update attempt downloads 0 bytes data
03-16 07:59:59.689 5345 14754 W SystemUpdate: [Execution,AbRebootAction] Failed to switch boot slot.
03-16 07:59:59.689 5345 14754 W SystemUpdate: cdlp: Failed to set slot switch to: true Update engine error code: 20

Any ideas what I'm doing wrong? The update appears to succeed up to this point. I'm wondering whether putting the phone in airplane mode is part of the issue, not sure.

I've encountered failures in past updates that happened before this point, which required restoration of a specific image dumped from the update's payload.bin, but this looks like something new.

Thanks
[OnePlus 8T Guides, News, & Discussion] BillGoss:
As I mentioned in post #347 above, I've not actually tested B1 on OOS 13 yet.

So, a few of questions for you:

Did your installation process start off by saying "Extracting...] and then finish this step and show you an "Install" button?

At which point did you take a copy of the new boot image? After the Extracting process finished?

Is your phone now successfully updated to F62, despite the errors?.
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
Ah, sorry, I misinterpreted what's written in the OP. I looked at the various methods, and decided to stick with B1 because it's worked for me before (including on OOS 13, I thought).

To answer your questions:

It ran as I remember it used to, extracting and installing in one fell swoop, then showing me a "Restart" button at the "end" (or what I thought was the end)

I took a copy after all of the above, then patched that and copied over to my laptop, as I've always done. But because of the failure, I haven't used it, and I don't know how to verify it's the updated image

No, the update failed. It's odd, because it seems to be telling me it's done (the "Restart" button showing up), but clicking "Restart" triggers yet another step, and that's where it fails. At this point, it also shows me a "Reset update" button. I tried this all twice, and the first time I restarted the phone using the physical button, and it was clear the update hadn't taken. After that, I've used the "Reset update" button to clear out what was downloaded and confirm I just want to be back at my last stable version (which I am, with no issues).
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
Oh, wait. This appears to be the same issue I've run into before, only in a different place

Old 'xbl_lp5' partition verification failed.
03-16 07:59:59.072 1950 1950 E update_engine: [0316/075959.072096:ERROR:filesystem_verifier_action.cc(489)] This is a server-side error due to mismatched delta update image!
03-16 07:59:59.072 1950 1950 E update_engine: [0316/075959.072131:ERROR:filesystem_verifier_action.cc(491)] The delta I've been given contains a xbl_lp5 delta update that must be applied over a xbl_lp5 with a specific checksum, but the xbl_lp5 we're starting with doesn't have that checksum! This means that the delta I've been given doesn't match my existing system. The xbl_lp5 partition I have has hash: pwJlw0oG9NP7bi61rppl1Jlhoz29quHvCizU6Tdt4cI= but the update expected me to have 237cBdH6CSPRVDsSiVEPSlVoN2kDR2oOq0R1wNgKPmQ= .
03-16 07:59:59.072 1950 1950 I update_engine: [0316/075959.072248:INFO:filesystem_verifier_action.cc(502)] To get the checksum of the xbl_lp5 partition run this command: dd if=/dev/block/bootdevice/by-name/xbl_a bs=1M count=4005888 iflag=count_bytes 2>/dev/null | openssl dgst -sha256 -binary | openssl base64
03-16 07:59:59.072 1950 1950 I update_engine: [0316/075959.072294:INFO:filesystem_verifier_action.cc(508)] To get the checksum of partitions in a bin file, run: .../src/scripts/sha256_partitions.sh .../file.bin

Guess I need to look at using payload dumper to get the original partition from the last OTA and flash that again. I don't know why this keeps happening to me between updates, but I think it happens more often than it doesn't.

I also wish I could just force updates to work without checking the deltas, but maybe that would be catastrophic, IDK.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Incremental updates (which is what the system updates invariably are) check the current partitions haven't been tampered with, and fails if they have been changed from what it expects.

That's why we restore the stock boot image (modified by Magisk), and recovery (if using a custom recovery) before starting.

But if you've installed an old xbl image to avoid getting the "The device has been unlocked and can't be trusted" message during boot, then you also need to restore that partition back to stock.

The only way to avoid all of this checking is to use a full installation zip, not an incremental.
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
Thanks, @BillGoss

I've only ever reinstalled previous partition images to fix this issue, based on instructions you gave me a while ago. How they become "tampered with" I don't know. My current version, KB2005_11_F15, was itself an OTA, incremental update, AFAIK, and I think it installed without this problem (could be wrong). I'm pretty sure the full upgrade from 12 to 13 worked without a hitch. But I almost always run into this problem with the incremental updates, and I don't know why.

FYI, I have never installed a custom recovery on this device (booted one, but not installed it)

I do get the warning message on boot - always have, and have never tried to suppress it.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Hmm, then I would suggest you either:

Let the system update do it's thing normally and reboot. And then use the new Magisk-patched patched boot image you have to root the phone as though it was the first time. You'll need to clear storage from Google Play Services and Play Store and reboot again.

Fyi, I had to do this when I updated to F15 (see https://xdaforums.com/t/guide-root-and-keeping-root-options.4387977/post-87960237)

Do a local install using a full image zip from Oxygen Updater.

Updated.
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
Wow, I didn't realize how easy this would be. I went with your option #2. But for clarity (and maybe a small edit to the OP?), here's how it went for me on a global / KB2005 (no TWRP)

Download with Oxygen Updater (downloads straight to /sdcard

Magisk -> Restore image

Install using System Updater (aka, for me, English apk) - i.e., click the little cog in the upper, right-hand corner, it finds the zip, and I hit the "Install" button

When it finishes, it shows a "Reboot" button, but I don't reboot

Magisk -> Install -> Direct Install (don't reboot)

Magisk -> Install -> Install to Inactive Slot (After OTA)

Reboot (I used reboot in System Updater)

I then verified the update succeeded in Settings -> About Device -> Version. And I'm rooted.

For some reason, directly after reboot, my Settings -> About Device -> OxygenOS widget, when I clicked on it, still showed an update available. I thought about trying to repeat the whole thing, installing to the other, now inactive slot (this may make no sense, but that was my thinking). At this point, System Updater didn't show an installable zip (I assume because it matched the currently running OS). Then, when I went back to Settings -> About Device -> OxygenOS, it said I was up-to-date, so done.

EDIT: Just used this same approach to update again, and I simply rebooted once directly after the upgrade and re-rooting, then again after the "System upgrade finalizing" UI finished up. This seems to get you to the point where the phone's aware that the upgrade has been completed, and you aren't prompted again to download the update.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Glad you've successfully updated. But, based on your description, you used the B.2.1 Local install if you used the APK to install the downloaded zip. This is very similar to using Settings>About device and tap on OxygenOS then tap on the 3-dot menu and select Local update.

When I say "System update" I mean Settings>About device and tap on OxygenOS and start the update without going via the 3-dot menu option - process B.1.

The two process behave quite differently and I've always had problems with System update and keeping root.