yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Divine Bicycle:
I see, ok. I'm downloading Kirisakura's kernel now.
[Google Pixel 6 Pro] ginfest:
Stupid ??

Is this method still valid to go from 12--13? I usually flash the whole image "-w" after processing the boot.img in Magisk and then fastboot the Magisk patched boot img.
[Google Pixel 6 Pro] V0latyle:
The only stupid question is the one you don't ask...well, except for the ones you ask when you already have the answer in front of your face

Yes, the process is exactly the same. The only difference I would suggest is due to the anti-rollback in the bootloader, make sure you flash the bootloader to both slots.
[Google Pixel 6 Pro] ginfest:
Great, thanks!
[Google Pixel 6 Pro] squidbutt:
I did and had no problems. The only modules I have are saftynet fix and bcr
[Google Pixel 6 Pro] squidbutt:
I flashed android 12 stock(coming from protonos)

Rooted(only patched the boot img and flashed it)

Then enabled zygisk and magisk direct installed.

When I was given the option to update to android 13

I downloaded and installed everything DID NOT REBOOT

Then went to magisk and flashed to inactive slot and rebooted

Root retained with bcr and saftynet fix installed.

Hope this helps
[Google Pixel 6 Pro] Dragon Kumera:
how because when I tried it never works or corrupts the boot. I can only succeed when dirty flashing the factory image and or ota.
[Google Pixel 6 Pro] V0latyle:
What version of Magisk did you use? This doesn't seem to be working for everyone using the latest Canary or Stable.
[Google Pixel 6 Pro] dilligaf56:
Dumb question - my phone is threatening to perform an OTA update to the August version; it's never threatened to actually do the update before, just nagged me because I have automatic updates turned off in Developer Options. Will it override this setting and actually do the OTA update even though I have that toggled off? I will eventually do it via the factory image method but wanted to wait a week or two and see how it's working for everyone else...!

Thanks!
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you're rooted, the OTA won't work no matter what. If you're not rooted, I want to know what exactly you mean by:

It's requesting permission from you to download and install the OTA, correct? I don't believe it will automatically do anything without you telling it to do so. I'm familiar with that occasionally an OTA notice somehow slips by the Developer options toggle for Automatic Updates. I've seen others report this from time to time, and it just happened to me earlier this month before Android 13 came out, but after the second round of July updates came out and I never updated to. In my case, I just left the OTA notice hang out in the notifications for the week or two it was there. I had rebooted once or twice in that time for other reasons and besides the notification coming back each time, nothing automatically tried to download and install.

Of course, I'm rooted, so installation would've been unsuccessful, anyway. I have no idea if the Android 13 OTA behaves any differently than all other OTAs regarding waiting for your permission to download and then install. My wife's unrooted Pixel 6 Pro finally got the OTA to Android 13 today, but she doesn't have the Developer option toggle set to disable automatic updates, so I don't know what you should expect for sure.

Good luck!
[Google Pixel 6 Pro] V0latyle:
I believe the developer options toggle just controls whether the system will automatically apply system updates when the device restarts. It does not control whether the updates are downloaded or installed - just whether the update is completed when the user taps the Restart Now prompt, or when a manual restart is commanded.
[Google Pixel 6 Pro] dilligaf56:
I am rooted, so hopefully you're right!

I usually do the manual updates with my laptop, but after a recent airline trip on which I was forced to leave my laptop in checked baggage, the Linux partition boots but the Windows one doesn't. I have a backup of the Windows NTFS and recovery partitions, but it's a couple of months old, so looking for other fixes first; once I get everything fixed, will do the update via the factory image method.

Thanks!
[Google Pixel 6 Pro] Namelesswonder:
I was on the first July update until jumping straight to Android 13, and I would get hourly notifications that the update failed to install as I am rooted. Still had automatic updates turned off. Ended up blocking that notification, but would still get the daily popups that my device was X days out of date and need to install the update. So I believe it does attempt to install the update in the background and just pops a notification that you need to reboot, similar to Windows except as far as I understand it doesn't automatically reboot like Windows does.
[Google Pixel 6 Pro] roirraW "edor" ehT:
OTAs depend on the software you're running being 100% stock, including the kernel (boot.img), but when rooted these days, the boot.img is modified by Magisk, so the OTA would fail.

Gotcha. Good luck with fixing the Windows portion of your laptop!

It seems after all, that I had either manually attempted to install the OTA just for the heck of it even though I knew it would fail, or what you said - that it tried to install on its own. I actually have a screenshot from immediately after I installed Android 13 (the first time / i.e. before installing it to the second slot) via the full factory image. After I unlocked the phone right after installing Android 13, I noticed the OTA notification was still there, but before much longer it did disappear, of course.

Looking at the screenshot, I remember the other reason I took it, which was the interesting "Updating repositories" progress notification, which I don't recall ever noticing after an update before.

Spoiler content hidden.
[Google Pixel 6 Pro] roirraW "edor" ehT:
True - it's just odd that 90% of the time, I never get any OTA notice, and sometimes I haven't gotten around to installing a new update for at least a couple of days. And it sounds like it's similar for a lot of other people since when they do get an OTA notification, they're surprised they got one. Oh well, just one of those technological things.
[Google Pixel 6 Pro] Lughnasadh:
Since the Nexus 5, I've never gotten an OTA notice. Lucky I guess...
[Google Pixel 6 Pro] V0latyle:
Same. I have never seen an update notification on my Pixel 5. Sometimes it will still report up to date even when an update is available.
[Google Pixel 6 Pro] Nergal di Cuthah:
I had that i think it was the secret july part two, it stopped asking when i flashed that img
[Google Pixel 6 Pro] CRXed:
Hi, I wanna ask the same question.

I am rooted with Magisk, I am on the latest Android 12 image (12.1.0 (SQ3A.220705.001.B2, Jul 2022, EMEA) and I get a nagging Android 12 update notifications that is now prompting me (see screenshot) that my phone will reboot automatically in 2 days.

What OTA could this be and will it be successful if I reboot?

Or will it break my settings/root?
[Google Pixel 6 Pro] V0latyle:
Updates will always remove root, because our root solution is a patched boot image, which is overwritten during the update.

Follow the guide at the beginning of this thread to update and re-root.
[Google Pixel 6 Pro] Lughnasadh:
If you're rooted, the update should fail.
[Google Pixel 6 Pro] CRXed:
So it's safe to try the reboot?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No way of knowing for sure - could be the second July Android 12 OTA or could be Android 13.

No. OTAs only succeed if you're 100% stock. Since your kernel (boot.img) is modified with Magisk in order to be rooted.

I always suggest not even attempting to take an OTA when rooted because a long time ago on a different phone, at least, trying to take an OTA could temporarily brick your phone. It isn't likely these days but since there is zero percent chance trying to take the OTA will be successful, no use even bother trying.

As @V0latyle said, just follow his instructions on the OP to update the normal way we update when we're rooted.
[Google Pixel 6 Pro] CRXed:
Yeah well this is the tricky bit: the phone is FORCING ME to reboot!

So how can I not take it?

That's how I updated to the last A12 image that is listed, it's how I always update....

I have Automatic System Updates disabled.

I don't need A13 yet, there is no newer A12 to download...and yet it still want to update to "a" version of A12 (it specifically says A12).

Now I am afraid to reboot or what will happen if the counter reaches 0.
[Google Pixel 6 Pro] Lughnasadh:
Is it 2.02 GB in size? Because there was an A12 OTA update of this size that was for a GPS fix.

Google Pixel 6 getting 'Introducing Android 12' update

Many Google Pixel 6 series users are confused due to an 'Introducing Android 12' update ahead of Android 13, here is what's happening.

piunikaweb.com
[Google Pixel 6 Pro] CRXed:
Yes, that's the one!

But I am already on that build SQ3A.220705.001.B2
[Google Pixel 6 Pro] Lughnasadh:
Yeah, I don't think you can download that one.
[Google Pixel 6 Pro] CRXed:
Yeah you can, that's how I installed it

https://dl.google.com/dl/android/aosp/raven-sq3a.220705.001.b2-factory-2ee23ef4.zip

But still it's forcing the update on me.
[Google Pixel 6 Pro] Lughnasadh:
Ah, I didn't check the download page.
[Google Pixel 6 Pro] roirraW "edor" ehT:
The update won't work since you're not rooted, so don't worry about it. Reboot, and probably get nagged about it again after or later - at least until you actually do update manually.
[Google Pixel 6 Pro] squidbutt:
I install canary then update through the magisk app. idk it worked well and Ive had not problems.
[Google Pixel 6 Pro] CRXed:
I am rooted

Can't update manually to a build I am already on.

It's trying real hard.....
[Google Pixel 6 Pro] roirraW "edor" ehT:
I meant update to the latest update that's available - not to what you're currently using.
[Google Pixel 6 Pro] CRXed:
I am already on the latest A12 that is available.

Phone has completed the 2GB download and is now forcing me to reboot within a day.
[Google Pixel 6 Pro] CRXed:
Okay so I bit the bullet and did the reboot:

Apparently, Google wants me to be on the Global version of the latest A12.

I was on EMEA SQ3A.220705.001.B2

After the reboot I am on Global SQ3A.220705.004

Which are the same version, just different territory.

Google be confusing me ...
[Google Pixel 6 Pro] Lughnasadh:
So you were rooted and the OTA updated successfully?
[Google Pixel 6 Pro] CRXed:
Yes.

I lost root after the reboot of course, but I patched the boot image and now root is back.
[Google Pixel 6 Pro] Lughnasadh:
Strange. It should have failed. I think you're the 2nd person I've seen in the last day or so who has successfully updated an OTA while rooted. Makes me wonder if something has changed 🤔
[Google Pixel 6 Pro] CRXed:
Thanks for all your replies to guide me @Lughnasadh and @roirraW "edor" ehT
[Google Pixel 6 Pro] Lughnasadh:
You betcha!
[Google Pixel 6 Pro] dilligaf56:
"Gotcha. Good luck with fixing the Windows portion of your laptop!"

@roirraW "edor" ehT : restored the SSD from the clone backup, updated both OS. All is good when you have backups.

Did the update to 13 this morning (with --slot=all on the bootloader flash). I'm rooted and everything appears to be good so far!

Thanks for the excellent support!
[Google Pixel 6 Pro] kip256:
Lost root when updating to A13. I installed Magisk manager, patched the boot.img, fastboot flashed it.

Issue I am having is Magisk will not install. I do not have the option to install within Magisk Manger. I have downloaded Magisk.apk to my phone, changed to a zip and then flashed it. But still, Magisk is not installed.

Am I missing something?
[Google Pixel 6 Pro] Nergal di Cuthah:
Maybe a screenshot of what you mean magisk won't install. Magisk and the manager are the same arn't they?
[Google Pixel 6 Pro] kip256:
I have installed Magisk 25.2.

I can't install the part of Magisk that allows for Root.
[Google Pixel 6 Pro] Nergal di Cuthah:
How does your screen differ from this
[Google Pixel 6 Pro] kip256:
Right below Magisk, it says Installed N/A
[Google Pixel 6 Pro] Nergal di Cuthah:
Ok then the problem is you need to flash boot.img as a file first you can't do direct install until you have a rooted boot you seem stuck on
[Google Pixel 6 Pro] kip256:
I already flashed the patched boot.img. I followed the steps in that image prior to posting.

The problem is I am on step 9, and instead of seeing "Installed <Magisk build number>", I see "Installed N/A"
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! I'm glad it ended up making some sense that you were receiving an OTA. Indeed strange about the OTA while rooted.

Awesome, you're welcome!

Edit: maybe you should start with a fresh non-rooted stock boot.img, to start from a known good configuration.

Do:

adb reboot bootloader

Once it's rebooted into bootloader, do:

fastboot flash boot boot.img

Using the fully stock original, unrooted boot.img.

After that...

Copy the boot.img from the full factory image zip of the same version you currently have installed, to the phone.

Run Magisk, select Install beside Magisk, and choose Select and Patch File. Direct it to the boot.img you just copied over to the phone.

Magisk will create a differently named, but patched boot.img - it'll have Magisk in the filename along with some "random" numbers and letters.

Copy that Magisk'd file back to the computer.

Then do:

adb reboot bootloader

Once it's rebooted into bootloader, do:

fastboot boot boot magisk_patched_12345abcde.img

Replacing:

magisk_patched_12345abcde.img

with the filename of your Magisk-patched boot.img.

It will boot the phone with your now rooted kernel, but...the rooted kernel isn't flashed to your phone yet. This was just a test to make sure your rooted kernel will boot your phone fine. If not, no harm at all because it's not flashed to your phone.

If it booted fine, unlock the phone, launch Magisk and choose Direct Install. Direct Install uses your (temporally) booted rooted kernel to root your already installed stock boot.img.

Hope this helps.
[Google Pixel 6 Pro] Nergal di Cuthah:
What you're describing is the patched boot not being installed. Follow @roirraw"edor"ehT steps precisely and you'll be fixed
[Google Pixel 6 Pro] kip256:
I previously downloaded the OTA A13 update from Google and extracted the boot.img from it, then patched it, and did all the other steps. I don't have a direct install option. I just tried fastboot flashing it again, still don't have a direct install option.
[Google Pixel 6 Pro] Nergal di Cuthah:
Don't flash boot

Fastboot boot

(i mean i flash but i know the steps above make a few more steps than i take)
[Google Pixel 6 Pro] roirraW "edor" ehT:
I never fool with the OTA method as it seems to mess up more often for folks than using the full factory image.

I was under the impression that you have to use the boot.img from the full factory image, not the one from the OTA, but as I said, I'm not knowledgeable about the OTA method. I do the full factory image every month.
[Google Pixel 6 Pro] kip256:
Tried to start with a fresh non-rooted boot.img. I did fastboot flash boot boot.img per @roirraw"edor"ehT steps.

I get this:

fastboot flash boot boot.img

target reported max download size of 261095424 bytes

error: cannot load 'boot.img': No error
[Google Pixel 6 Pro] kip256:
Not OTA method. I downloaded the OTA file from this developers.google.com page. Which is what I have done in the past.
[Google Pixel 6 Pro] Nergal di Cuthah:
The OTA or the full image. Iirc the ota doesn't have a boot.img
[Google Pixel 6 Pro] kip256:
Full. I extracted the boot.img from it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
What you linked to is the OTA files. I know that some users prefer that method, but from what I've observed over the last six years on Pixel phones is that it's more finicky - sometimes it's sensitive to updates that might be needed in Magisk before a new months' OTA will work with that method.

I prefer the full factory image zip, which as far as I know is the only place to get the proper boot.img file from. I know I'm repeating myself, and I very well might be wrong. Since I never use the OTA method, I just don't know the intricacies other than basic concepts of it.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Edit:

Now I'm just confused, because you linked to the OTA files, whereas the Full Image files are available at the link at the left on that page, above OTA that you linked to.

Edit 2: I see it labels the OTAs as Full OTA, so I assume this is what you're referring to. Factory Image is what I recommend.
[Google Pixel 6 Pro] Lughnasadh:
What are you using to extract the boot image from the OTA? Payload Dumper? Probably be best to do as @roirraW "edor" ehT said and extract the boot image from the factory image rather than the OTA. And don't change the Magisk app from .apk to .zip and try to flash it. Just install the Magisk app as you would any other app and patch the boot image from inside it.
[Google Pixel 6 Pro] kip256:
Downloaded full factory. Used the boot.img to patch and fastboot. Still nothing.

But I did notice that when I fastboot boot, it says downloading 'boot.img' not sending.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I forget what version of Magisk you're using. Although I've had no problem with Magisk Stable v25.2, maybe you should try the latest Canary version from GitHub. I know there's a newer Canary version today or recently.

The only other thing I can think to try next is start from scratch - not wiping the phone, but remove the -w from the flash-all.bat, run it to update the phone, then follow the steps again to root the boot.img and flash the rooted boot.img.

Then you could always try

Official Google Android Flash Tool

, making sure the following options are unchecked: to wipe, to force flash all partitions, and to lock the bootloader. Repeating: make sure those options are unchecked.

The

Official Google Android Flash Tool

has solved weird issues for many users including myself, that even the factory image wouldn't solve.

Very last ditch effort is to go with the wipe, having made sure to back up anything important off your phone.

That's probably normal since you're booting the boot.img directly from the copy of the boot.img that's on the computer, instead of flashing it.
[Google Pixel 6 Pro] Lughnasadh:
Are you using the latest Platform Tools?
[Google Pixel 6 Pro] kip256:
Yes, 33.0.2
[Google Pixel 6 Pro] Nergal di Cuthah:
Can you paste the output (and commands) of fastboot boot boot magisk.img from command line/terminal
[Google Pixel 6 Pro] Nergal di Cuthah:
Ok so it's booting correctly now can you direct install in magisk now?
[Google Pixel 6 Pro] kip256:
No. Magisk still says it isn't installed
[Google Pixel 6 Pro] Lughnasadh:
fastboot flash boot magisk_13.img
[Google Pixel 6 Pro] Nergal di Cuthah:
Because it's not installed yet click install
[Google Pixel 6 Pro] kip256:
Adding a 2nd boot gives an error
[Google Pixel 6 Pro] kip256:
This is what I see when I click install. I do not have the ability to Direct Install
[Google Pixel 6 Pro] Lughnasadh:
Are you putting the patched boot image in your Platform Tools folder and opening up the command line from the Platform Tools folder?
[Google Pixel 6 Pro] kip256:
No, just had the Platform Tools folder in the Pixel Root folder. I moved the patched boot into the platform tools folder and tried again. This time it did send the boot.img (before it was downloading). But when the phone restarts and I open Magisk, still says it is not installed and still do not have the option to Direct Install.
[Google Pixel 6 Pro] Lughnasadh:
Try fastboot flash boot magisk_13.img
[Google Pixel 6 Pro] V0latyle:
Having the patched image in the same directory as platform tools is unnecessary. When flashing or booting a file, simply type the command you're going to use - for example, fastboot flash boot --slot=all, then drag and drop the image you're using into the command window from anywhere on your PC, and the path will auto populate.

@kip256 your problem is definitely baffling!
[Google Pixel 6 Pro] Lughnasadh:
Having the patched image in the Platform Tools folder and typing the command or copying and pasting the name is perfectly fine and one way of doing it.

Dragging the file to the command line is another way.

Personal preferences... just like if you want to flash it to your active slot or both slots. Personally I never flash a patched image to both slots. Like to have one slot with a stock boot image as a fallback.
[Google Pixel 6 Pro] CRXed:
This is the incorrect command "fastboot boot"

It should be "fastboot flash boot <patched.img>"
[Google Pixel 6 Pro] V0latyle:
I'm not trying to argue superiority of anything. Personally, I like to keep everything segregated - after unzipping the factory package, I keep the boot image in that folder, so I don't mistake one version for another, and I find it simpler to just drag the file I'm trying to flash into the command window. To each his own indeed, I just prefer to keep things as simple as possible. The only files in my ADB tools folder are the ADB tools themselves.

It's also worth noting that neither ADB/fastboot nor the device care what the files are named, as long as the images are correct; so, one could rename files as necessary (e.g., August boot.img)

Not incorrect.

Without "flash", the device loads the image directly from ADB - essentially a "live boot". This can be useful if one wants to preserve the original boot image for a Magisk backup - don't flash the patched boot image, but instead live boot the patched image, and perform direct install in Magisk, so that Magisk is able to create a backup of the original.

Again for clarity:

fastboot boot <boot image> does not flash the boot image to the device, but instead commands the device to boot that image. Useful for testing or direct install in Magisk.

fastboot flash boot <boot image> flashes the boot image to /boot and does not command the device to load it.
[Google Pixel 6 Pro] CRXed:
Of course you are absolutely correct, but he does not have the Direct Install option, so he should Fastboot flash.

Either that, or

- he is not using a correct stock boot image to patch

- he is not flashing a patched boot image
[Google Pixel 6 Pro] V0latyle:
The only difference between booting a patched image and flashing one is where the device loads the image from, and what happens when the device is rebooted. Root access, and the ability to perform Direct Install, should be available either way.

As you described, the issue must be using the wrong image.
[Google Pixel 6 Pro] CRXed:
Or maybe incompatible Magisk app?

I am still using 24310 without issues.
[Google Pixel 6 Pro] V0latyle:
He's using 25.2, as many others are without a problem.

@kip256 the only thing I can really suggest is make sure you're starting fresh.

Download and unzip the factory update package. Keep the contents in their own distinct folder.

Open the contained update image and unzip only the boot image. Name this something unique - Aug13 or something.

Connect your phone to your PC and open the device storage; search for and delete all leftover images. Clear out your Downloads folder. Even better, create a new unique folder on the device where you'll put the stock boot image.

Copy the Aug13 image to the folder described above.

Open Magisk, and before you patch the boot image, go to Settings > Download Path. Select the folder you stored the stock boot image in.

Browse to the folder with the Aug13 image. Select and patch it. The patched image should now be in the same folder as the stock image.

On your PC, browse to that folder and copy the newly patched image back to the factory update folder. Keep that folder open.

Start a command line in your ADB tools folder, and command your device to reboot to bootloader.

Live boot the newly patched image:

fastboot boot <Drag and drop the patched boot image into the command window>

Device should boot with root. Open Magisk; it should state the Magisk ID next to Installed.

Select Install in the Magisk section > Direct Install. Reboot when prompted.
[Google Pixel 6 Pro] kip256:
At work, will try this tonight when I get home. Thank you.