Database Info

Upgrading Magisk... Want to confirm how

I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!

amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
I don't remember the actual choices, since mine is already updated, but I do it straight from Magisk Manager app. I think I choose update then the direct install (recommended) option. I believe it then shows the log as it updates and once done gives option to reboot. Once it reboots, you should be on latest (15.3) version of Magisk, and you still have root and pass Safety checks. It has never caused any boot loops for me, just smooth and simple.
HTH!

amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
like the other response, i am able to upgrade magisk directly from magisk manager (direct install method)
one caveat, i don't know if it's still true, i had an issue upgrading a month or two back and someone on here recommended i set my magisk to the "beta" channel (settings -> update channel). i suspect this is no longer needed, but i left it on the beta channel and have had no issues upgrading magisk every time it notifies me of a new update

Ok, so I can upgrade directly from the app. Great! I guess I was overthinking...
Thanks!

[UPDATE/KEEP ROOT GUIDE] OCT 2020 (RP1A.201005.004) "CORAL" Magisk/Stock Boot Images

[UPDATE/KEEP ROOT GUIDE] OCT 2020 (RP1A.201005.004) "CORAL" Magisk/Stock Boot Images
PLEASE NOTE: I STILL HAVE NOT UPDATED TO ANDROID 11 YET, SO PLEASE FLASH AT YOUR OWN RISK AS ASSISTANCE FROM ME WILL BE VERY LIMITED. PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! AND SORRY FOR THE LATE POST. JUST GOT BACK FROM A LONG WEDDING WEEKEND, AND THE 8-HOUR DRIVE (EACH WAY) WITH A 9 MONTH OLD BABY WAS... QUITE AN ADVENTURE.
PLEASE DROP A THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:​
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.201005.004, Oct 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557936
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557937
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675557938
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.

EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RP1A.200720.009, Sep 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rp1a.200720.009-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682933260
coral-rp1a.200720.009-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682933258
October 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.201005.004-5e85d0f7.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rp1a.200720.009-factory-boot.img
3. fastboot flash dtbo coral-rp1a.200720.009-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.201005.004-5e85d0f7.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.201005.004-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.

Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16

I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!

i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.

bb709394 said:
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
Click to expand...
Click to collapse
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.

i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.

i5lee8bit said:
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
Click to expand...
Click to collapse
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.

@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.

WorldOfJohnboy said:
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
Click to expand...
Click to collapse
I still haven't bothered with TWRP since the HTC U12+ days, and I actually found that I prefer it that way. Pretty sure TWRP needs to be updated for each (or at least most) monthly update btw. But thanks for the info, looks like 64mb is now the normal way Magisk outputs the patched boot image.
Morgrain said:
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
Click to expand...
Click to collapse
Yeah, I only backup/restore certain apps (data or apps not on app store) when switching phones because there are always those little glitchy problems and what not if relying on TiBu / Swift too much. I'll use the built in backup/restore for certain apps (like Nova), but other than that when doing a clean install, while Android has better built in features to make it easier to migrate compared to a few years ago, it is still a major PITA.
blue2018 said:
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
Click to expand...
Click to collapse
Thanks for the info! Just updated the OP so there isn't a huge scary caution, lol. I figured it would be fine when I tested with August patched with v21.0 and still came out to 64mb, but thanks for the confirmation.

Silly Question Maybe
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?

I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?

xclaim494 said:
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
Click to expand...
Click to collapse
Sorry about the late response, but maybe this info might help (it's a post I made on slickdeals.net regarding b/l unlocking the P4 series): https://slickdeals.net/f/14385296-x...e-399-free-shipping?p=140865899#post140865899
Also important to note, there is a difference between SIM unlocking (so you can use with T-Mobile) and oem/BL unlocking (so you can modify / root the phone).
tl;dr on my slickdeals post: SIM unlock status controls the oem (bootloader) unlock toggle status. Verizon is known to be the only variant where they fully prevent BL unlocking. XMo is an MVNO off of Verizon. Nobody has reported yet whether it can be done on XMo variants even after SIM unlocking. So you might be screwed.
smithilberry said:
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
Click to expand...
Click to collapse
Did you follow the OP / 2nd post exactly? And made sure you're sideloading the correct, Oct 2020 ota zip? Should work fine with the given instructions and links. Make sure you downloaded (or just redownload) all the correct files.
Tbh it sounds like you're just reinstalling the Sept update and boot files.

The November update is out. Anyone here already got the new files?

Morgrain said:
The November update is out. Anyone here already got the new files?
Click to expand...
Click to collapse
I do... not sure if there's a separate thread as this is for the October update.
Side note, I apparently can no longer BOOT to TWRP to flash the Magisk Zip as even the TWRP Coral Beta doesn't decrypt Android 11. So, looks like I'm stuck manually patching the Boot and flashing via bootloader.

How to Root OnePlus 8T Build 11.0.6.8.KB05AA

I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.

rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.

Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.

Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.

You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.

alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.

Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.

rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot

Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!

rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"

Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!

I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.

How To Guide How to Update OOS 12 with Root

Hi Everyone, there seems to be a lot of bits and pieces in regards to updating OOS 12 and Root so I thought I put together this guide on the way I do it while retaining Root. Unless something changes, this method should work for all future OOS 12 OTA updates.
Please read through all of the steps below before attempting. I will take no responsibility if something goes wrong, this works for me on my OnePlus 9 LE2115 and it should work for other OnePlus 9/Pro models.
1. Install Oxygen Updater app from the Play Store
2. Download the Full OTA.
3. Download and install the OP Local Update app ( apk).
4. Use the OP Local Update app to flash the Full OTA (you will lose root and custom recovery).
Optional - Retaining Root
DO NOT REBOOT if you want to keep Root
5. Open Magisk and in the Magisk section, tap 'Install'.
6. Select ' Install to Inactive Slot (After OTA)'.
7. Tap ' LET'S GO', let it run and then reboot.
After the system boots back up, check to make sure you have retained Root. You will not lose any data doing it this way.

What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)

I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.
I was previously under the impression that this app was to replace the missing system updater in OOS12.

Nick James said:
What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)
Click to expand...
Click to collapse
This guide is for updating OOS 12, i have not tested it from OOS 11 to 12. It looks like you just need to flash the patched boot.img again.
Also, just to make sure, you didn't reboot the phone after flashing the Full OTA? After flashing Full OTA, you need to go straight into Magisk as per instruction.

gorilla p said:
I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.
I was previously under the impression that this app was to replace the missing system updater in OOS12.
Click to expand...
Click to collapse
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.

Z-Blade said:
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.
Click to expand...
Click to collapse
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.

Nick James said:
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Click to expand...
Click to collapse
Ah, right. From the other thread. Good to hear it's all sorted out.

If you are looking for the boot.img for a OP9 (not pro) LE2115_11_C.47... here you go:
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
This is valuable if you get stuck in a position like I did on C.47 without root. Patch this file with Magisk and follow the instructions as you normally would when flashing for root:
Installation
The Magic Mask for Android
topjohnwu.github.io

Nick James said:
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Click to expand...
Click to collapse
So, how did you get from e.13 to c.47 with root?
1. Download c.47
2. Install it via updater - no resart
3. install the patched_boot.img in inactiv slot
4. restart
Correct?

AxelM said:
So, how did you get from e.13 to c.47 with root?
1. Download c.47
2. Install it via updater - no resart
3. install the patched_boot.img in inactiv slot
4. restart
Correct?
Click to expand...
Click to collapse
I uninstalled Magisk (restored images).
Rebooted (I shouldn't have done this)
Updated via OTA; rebooted.
Confirmed I was on the new version; indeed I was... completely new UI... did not lose any data or apps
Used the update app to redownload the OTA, copied it to my computer, used payload dumper to get the boot.img. Moved that back to my phone, patched with magisk and reflashed and voila.
I'm not sure on the exacts in terms of versions that I was on before but I did back up the kernel prior to all this (force of habit) and it was 11.2.10.10.

Thank you, i will try
1. I will just restore the normal boot.img
2. Update via OnePlus Update app from device
3. reboot
4. install the patched_boot.img in the inactiv slot
5. restart
Done!

So to be clear, we can now upgrade like we used to, by downloading full image From Oxygen Updater, using system update complete the upgrade, then go to magisk and install to inactive slot and reboot?
I tried this with the earlier 12 release and it went poor.
Luckily, I realized before trying this, is this only for 12 to 12 udpates and not 11 to 12? If the former, it may be best to clarify.

I am not sure. But like I understood you have to unroot before...
@Nick James am I right?

AxelM said:
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
Click to expand...
Click to collapse
I dont think so. It says if you wanna keep root, follow #5, 6, 7

AxelM said:
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
Click to expand...
Click to collapse
Honestly this OS sucks. I wouldn't waste your time. I'm going to factory reset tomorrow. It's that bad.

The steps I provided is only OOS 12 to OOS 12. I have not tried these steps from OOS 11 to OOS 12. My assumptions is it should still work since you are flashing the Full OTA, it pretty much overrides everything including boot.img. This is why you shouldn't reboot after flashing the OTA if you want to keep root.
However, this is just an assumption, if someone who is currently on OOS 11 can test it out and report here, that would be great.

gorilla p said:
I dont think so. It says if you wanna keep root, follow #5, 6, 7
Click to expand...
Click to collapse
You are right for OS12 but not OS11. Therefore I assume you have to do my mentioned steps, but like @Z-Blade wrote, anyone has tested here yet...

Hello I tried it today. Like this:
1. I will just restore the normal boot.img
2. Update via OnePlus Update app from device
3. install the patched_boot.img in the inactiv slot
4. restart
Everything seems normal, but I am ony able to connect to the internet when in wlan...

I went from OOS 11 to 12... I wouldn't say the upgrade went smooth thus why I have to reinstall the OS to see if that clear things up. This OS is still really buggy from what I can see but it could be due to not clean flashing. Just beware is all I'm sayin'

So, my internet is back to live...after some reboots it works well

[GUIDE] Pixel 3a XL "bonito": Unlock Bootloader, Update, Root, Pass SafetyNet

If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.
First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.
Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.
Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.
Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?
Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?
Thanks again for the guide!

Cheetah_Bear said:
Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.
First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.
Click to expand...
Click to collapse
Without root, there is no way to do a full backup including app data. The best you can do is sync your Pixel with your Google account.
Cheetah_Bear said:
Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.
Click to expand...
Click to collapse
"Bonito" is Google's internal name for the device and has little to do with the software. The Pixel 5 is "redfin", the 5a is "bramble", the Pixel 2 was "walleye".
As far as rooting your device, yes - if you follow this guide, you will gain root on the stock OS. I am currently using my Pixel 5 with the OEM firmware, patched with Magisk.
Cheetah_Bear said:
Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.
Click to expand...
Click to collapse
This guide is not sequential; I provided different instructions for different scenarios. The downloads are simply the resources you will need. To attain root, simply follow the instructions under "Initial Root". When the June update is released, you can update using your method of choice, and follow the relevant instructions to regain root.
Cheetah_Bear said:
Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?
Click to expand...
Click to collapse
I personally do not like using third party tools, and I simply use adb/fastboot. The Android Flash Tool is simply for flashing factory firmware and cannot flash custom images.
Cheetah_Bear said:
Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?
Click to expand...
Click to collapse
No worries. It sounds like you have a lot to learn but you're at the right place; XDA is full of knowledgeable people who can help you out.
Cheetah_Bear said:
Thanks again for the guide!
Click to expand...
Click to collapse
Thank you for your appreciation.

Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.
I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.
Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking.
Thank you again.

Cheetah_Bear said:
Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.
I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.
Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking.
Thank you again.
Click to expand...
Click to collapse
Make sure you're using USNF and MHPC; DenyList alone won't do it.
You may also have to block the Play Store due to Play Protect.

Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?

BadRx said:
Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?
Click to expand...
Click to collapse
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.

V0latyle said:
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.
Click to expand...
Click to collapse
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.

BadRx said:
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.
Click to expand...
Click to collapse
I'm talking about bootloader unlock. It is a well known fact, having been established since the original Pixel (if not the Nexus series) that Google devices sold through carriers such as Verizon are not bootloader unlockable. This is why if you want a completely unlocked device, you must buy directly from Google.
As far as carrier unlock...that depends on the carrier. If you bought your device from Google, it's already carrier unlocked. But if you bought it through a carrier, they may or may not unlock it depending on their own policies. I don't know what Verizon's is, but most US carriers will allow carrier unlock as long as 1) there is no lien on the device (it's paid off) and 2) your account is not under contractual obligations.
It may seem weird to you, but they're protecting their investments. You can't reasonably expect a carrier to provide you a device at a discount with no restrictions. Either buy used from Swappa, or new full price from Google, and use the carrier only as a carrier. If you buy a phone through them, don't expect the same freedom.

Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?
thank you
Alex

4L3xN3t said:
Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?
thank you
Alex
Click to expand...
Click to collapse
Did you read the OP?

V0latyle said:
Did you read the OP?
Click to expand...
Click to collapse
yes, I spent much more time on reading it and preparing the needed stuff than doing the process
if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.
anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting
Alex

4L3xN3t said:
yes, I spent much more time on reading it and preparing the needed stuff than doing the process
if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.
anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting
Alex
Click to expand...
Click to collapse
What Android build are you on? Did you update?
What version of Magisk are you using?
What process did you use to root?

V0latyle said:
What Android build are you on? Did you update?
What version of Magisk are you using?
What process did you use to root?
Click to expand...
Click to collapse
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).
I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.
Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.
Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.
Maybe something related to the two boot_a and boot_b slots?
reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.
So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.
thank you

4L3xN3t said:
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).
I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.
Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.
Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.
Maybe something related to the two boot_a and boot_b slots?
reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.
So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.
thank you
Click to expand...
Click to collapse
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.
When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?
Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.
I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.
Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.

V0latyle said:
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.
When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?
Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.
I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.
Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.
Click to expand...
Click to collapse
ok, sorry, you're right, I lost something.
I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).
about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.
I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.
partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?
Did you have anything in mind about this?
thank you

4L3xN3t said:
ok, sorry, you're right, I lost something.
I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).
about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.
I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.
partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?
Did you have anything in mind about this?
thank you
Click to expand...
Click to collapse
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.
Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.
Were you rooted before?

V0latyle said:
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.
Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.
Were you rooted before?
Click to expand...
Click to collapse
The last update was done in May, so I think I waited way more than 10minutes
I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.

4L3xN3t said:
The last update was done in May, so I think I waited way more than 10minutes
I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.
Click to expand...
Click to collapse
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.

V0latyle said:
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.
Click to expand...
Click to collapse
when I flash the factory image (as I did l 2days ago), I use the "flash-all.bat" included in the original zip after I delete the "-w" from "fastboot -w update imagexyz.zip" and this way it doesn't wipe the phone.
I'll try again in the nex days (hope to have time in the weekend) doing some screenshot
stay tuned.
thank you