yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Link2811:
I just used this method, (same one described on Magisk website here https://topjohnwu.github.io/Magisk/ota.html) and it worked perfectly, both root and safetynet.

Can someone explain to me why you see all kind of guide to update which are far more complicated than that ?
[Google Pixel 6 Pro] Lughnasadh:
Because there are many methods to update and people have different preferences, depending on what they are used to or most comfortable with. One may find one method complicated while another may not. Just a matter of preference.
[Google Pixel 6 Pro] niko26:
Are you 100% sure?

Cause topjohnwu said that OTA patching from within Magisk was broken for Pixel devices.

See here

https://twitter.com/i/web/status/1303574238796808192
[Google Pixel 6 Pro] V0latyle:
Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.

Part of it is also due to user preferences. Some people, like me, prefer to update using the factory images, instead of OTA.

And part of it is probably a bit of misinformation mixed in with anecdotes, where people who don't fully understand how the process works, but they declare that something has to be done a certain way because of what worked for them.

I try to stick to the first two. I've spent a lot of time learning about how Android works, so I make a point of providing instructions that align with how everything is supposed to be done, while accommodating alternatives for those who want them.

Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.

I have been following the commits closely, so when 23017 was released, I announced it in my guides. Had you read back a couple pages, your question has been answered.

If you don't believe me, check the commits here.
[Google Pixel 6 Pro] Nekromantik:
i followed guide and booted with root the stock boot img with magisk 24.1 and then flashed custom kernel which dev said supports the no need to disable verity but now got corrupt message and need to format!!
[Google Pixel 6 Pro] V0latyle:
That issue is outside the scope of this thread. Please post in that kernel's development thread.
[Google Pixel 6 Pro] niko26:
Thanks. I missed that there was an update to this issue.

However, when trying to go your way Magisk complained that it didn't find the original/plain bootloader. How would I fix this for the next time?
[Google Pixel 6 Pro] V0latyle:
Do you mean boot image? Bootloader is a completely separate entity.

I haven't seen that error but I know a couple people have. I don't have any more information on that, sorry. The best I can suggest is reflash the unpatched boot image, but at that point you may as well just sideload the OTA or dirty flash the factory image. Either way you'll lose root and will have to manually patch the boot image again.
[Google Pixel 6 Pro] niko26:
Yeah, I meant the boot image. I always mix up the terms, sorry about that.

I have just read your linked discussion where you said if I had only read that part ;) First of all... I feel your pain repeating the same stuff again and again from being a mod myself. However, now I am on the other part of the fence and keeping up with topics is not that easy. To be fair I think you'd agree that the linked discussion was not so clear whether it was working or not ;)

Anyway, thanks for your efforts.

From what I think... Magisk does not kwow the original boot.img because if Magisk being flashed manually (dirty flash). I would assume that I would have to flash the boot.img from within MAgisk... But Magisk needs root for being able to flash - right?
[Google Pixel 6 Pro] Nekromantik:
did you wipe or just re flash the full factory with stock boot ?

did the corrupt message go away?
[Google Pixel 6 Pro] Lughnasadh:
Go into /data and see if you see copies of your boot image(s). They should be named "magisk_backup_xxxxx". If you don't see any there that may be the problem.

EDIT: Which reminds me of another reason why you shouldn't use patched boot images from another person. You have to patch the boot image with your own device in order to preserve the stock boot image.
[Google Pixel 6 Pro] V0latyle:
No problem.

Not really. Magisk patching works the same, so it doesn't matter how you patched it - whether you patched the boot image then flashed it, or used temporary root to patch it. Either way, Magisk is able to recognize the patch in the image and remove it, essentially restoring the image to stock. I don't know if it actually creates a backup.
[Google Pixel 6 Pro] niko26:
Doh! Makes sense.

I have used my own patch, didn't download them. I'll try it the next time.
[Google Pixel 6 Pro] pavelcheto:
I got the corrupt message when I tried to boot via adb my old patched boot.img from the January update. Then I got the error that the data was corrupted. I rebooted the phone normally and everything worked. First I tried to install the OTA via the system app but it kept failing, so I followed the OTA sideload guide.
[Google Pixel 6 Pro] Nekromantik:
Do you still get the corrupt message or is it gone?
[Google Pixel 6 Pro] pavelcheto:
It is gone, I only got it when I booted the patched boot.img from January update via adb.
[Google Pixel 6 Pro] Nekromantik:
oh ok
[Google Pixel 6 Pro] Dragon Kumera:
I heard the February update resets all preferences. Is this true for the p6p?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No reset preferences for me, unless you or someone means specifically for taking the actual over the air update as opposed to manually flashing the full firmware zip like I did. I haven't seen anyone else here who reported updating to February mention reset preferences, either.
[Google Pixel 6 Pro] Lughnasadh:
Not sure what preferences you are talking about, but my settings, etc., were not reset.

Can you be more specific about what preferences you are talking about? Magisk preferences?
[Google Pixel 6 Pro] Dragon Kumera:
OTA updates. Here a link that of someone who posted on reddit about it. I dont think they have a pixel6 pro but since the update February patch I was thinking it might have the same effect on pixel 6 pro.

https://www.reddit.com/r/GooglePixel/comments/sntv5w
[Google Pixel 6 Pro] Lughnasadh:
Nope. Haven't seen that behavior with the February update on my phone. I updated via flash-all method.
[Google Pixel 6 Pro] Dragon Kumera:
I downloaded the images but want to try the ota magisk method to see if it works. But I think i might hold of for a bit.

Decided to give it a try. It refused to update like the january ota. Kept saying check connection. I uninstall magisk and restore image then tried again and it working now. But optimizing device is taking forever.

Once done will see how flashing to second slot works in magisk app.

Ok tried rebooting and it still saying January update even though restart appeared on system update. (did the install through magisk app and rebooted through that app). Then I went through system menu to restart since it was on January still and it errored out.

Will try again and see if it works.

Ok I had to do the old fastboot recovery flash ota update manually. I am not sure what happened but boot image got corrupted trying to go through ota. I just had to redo the whole magisk setup but now im on February update with root. Though I am not sure if the next update will fix the other slot that got corrupted or if I should switch and manually do it.
[Google Pixel 6 Pro] DaKing1512:
I'm trying the OTA method but for some reason the updater can't install the update

I restored the image in magisk, as per the steps mentioned, but I keep getting the "couldn't install" error, I removed all magisk modules, still get the same error

Any help?
[Google Pixel 6 Pro] s3axel:
Got a custom kernel installed?
[Google Pixel 6 Pro] DaKing1512:
Nope, everything is stock
[Google Pixel 6 Pro] V0latyle:
Since a lot of folks are having issues with the OTA update, I recommend everyone stick to the methods we know will work for sure - either OTA sideload or dirty flash factory image. In both cases you'll need to manually patch the boot image.
[Google Pixel 6 Pro] Lughnasadh:
Did you modify /system or /vendor in any way? Doing this will tamper with the block verification and make the install fail.
[Google Pixel 6 Pro] DaKing1512:
I'm not sure what causes this kind of modifications tbh, everything I do is within magisk which is supposed to be systemless, I use lsposed but all modules are disabled
[Google Pixel 6 Pro] General_Mayhem:
I ran into this today. No matter what I tried, I could not get the OTA to install. Kept getting the install error. I'd disabled the plugins, uninstalled Magisk. No dice.

I read somewhere (I can't recall where) that if you use flash-all, that's why (although I have no idea if that's the reason). But literally every guide I've seen says to use this method. I don't know if we're supposed to pick a specific slot or what that command would be. And if we are, I don't how to get to that point without nuking from orbit and starting over. Again.

I also consistently run into a No Command screen trying to boot into recovery via fastboot. Every. Single. Time.

I ended up side-loading the OTA which gave me an error and was forced to do a factory reset as part of the OTA process, re-patch and set my phone back up how I had it. Weird thing was, after being forced to do this I had Magisk already installed somehow.

This is what I *tried* to do:

1. Download the OTA.

2. Reboot to recovery and sideload the OTA:

Code: adb reboot sideload

3. Once in recovery:

Code: adb sideload ota.zip

4. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".

5. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.

6. Reboot to bootloader.

7. Boot the master root image:

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. Do not flash an older boot image after updating.

8. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.

9. Reboot your device. You should now be updated with root.
[Google Pixel 6 Pro] Dragon Kumera:
did you hold the power button and press volume up button in recovery?

I got the ota to install that the thing. But reboot didnt work right even when done in magisk.

Then boot images both slot a and b borked themselves so had to do the ota sideload through recovery to fix it.
[Google Pixel 6 Pro] IvanPTachev:
Edit: Ignore, I guess I should have tried first uninstalling the app before asking.

Hi all, I've been out of the rooting for quite a while and wanted to give it a try. Ran my rooted phone for a week or so and flashed the factory image for the 12L beta today. I had magisk hidden and the new app frozen as I kept having issues with my bank app and that solved it. However now because I have no root, I cant unfreeze the app and delete magisk. Is there any way of removing it without re-rooting the device?
[Google Pixel 6 Pro] DaKing1512:
that defeats the purpose of being able to OTA update your phone without the need to use your computer. I did the ota sideload before, as well as the flash from android flash tool. I just wish that the OTA feature works so I can just update without the need for a PC, like its mentioned in OP
[Google Pixel 6 Pro] Lughnasadh:
To unfreeze it try:

adb shell

pm enable <hidden package name of Magisk manager>
[Google Pixel 6 Pro] General_Mayhem:
I know, but given the fact that even with the modules disabled and Magisk uninstalled, the OTA sans computer wouldn't install. Had that actually worked, none of what I did would have been required.

Trust me, when I try to take an OTA I don't want to have to use my computer to do it.
[Google Pixel 6 Pro] dilligaf56:
Perhaps slightly OT, but I have heard that the February update breaks Wi-Fi on some phones. Anyone here seen that? Holding off on updating for now...as it is, when I turn on Wi-Fi on my phone now (rooted January update), after some random time the cellular connection drops.
[Google Pixel 6 Pro] roirraW "edor" ehT:
No problems here with Wi-Fi. I haven't had that other problem with Wi-Fi causing cell connection to drop either, though.
[Google Pixel 6 Pro] General_Mayhem:
Same. No issues with wifi.
[Google Pixel 6 Pro] Dragon Kumera:
no issues with wifi either
[Google Pixel 6 Pro] thejunkie:
no issue, i just got my pixel 3 days ago, from a s21 ultra. only issue im having is the screen goes up and down on brigtness, and the lockscreen is mad ugly.
[Google Pixel 6 Pro] RetroTech07:
I'm just waiting for a fix that's for that one fix, that was supposed to fix that other fix, but it also fixes everything else. I heard it might be a while, though. /s

The word "fix" has now lost all meaning and sounds weird when I say it now. 🤕

Sorry, just tossing in some humor lol.
[Google Pixel 6 Pro] mustardseeds:
When I try to sideload it's as if nothing happens. In fastboot mode I run

adb sideload oriole-sq1d.220205.003-factory-a5a63f2a.zip
Total xfer: 0.00x

I'm flashing the zip downloaded from https://developers.google.com/android/ota
[Google Pixel 6 Pro] Lughnasadh:
You don't sideload in fastboot mode. You do it from recovery.
[Google Pixel 6 Pro] V0latyle:
Yep.

The easiest way to do this is use the command adb reboot sideload when in Android system.

If you're already in bootloader, you can use fastboot reboot recovery. Rebooting directly to sideload is not possible in bootloader.

Or, you can use the Volume keys to select Recovery on the right, then Power to enter.

Once the Recovery screen comes up, hold Power, then click Volume Up.

Use the Volume keys to select Apply update from ADB and click Power. Then, issue the sideload command on your PC.
[Google Pixel 6 Pro] mustardseeds:
I misspoke - I thought adb reboot sideload was fastboot for somereason. I do this in recovery and nothing happens. After the transfer is complete do I go straight to reboot or do I need to apply update from adb in recovery?
[Google Pixel 6 Pro] V0latyle:
I'm not entirely clear on what you're asking. I gave clear instructions, which you quoted. Simply follow them.

Once the update is complete, you'll be taken back to recovery, where you can select Reboot system now. Make sure you don't interrupt the reboot process after updating via OTA.
[Google Pixel 6 Pro] JetBlackfrost:
Is anyone else having an issue where you have OEM unlocking enabled in the developer options, your device is recognized, you're not getting any "failed" messages, yet when you run "fastboot flashing unlock" it doesn't actually do anything and you simply get the rundown of what every command does?
[Google Pixel 6 Pro] fil3s:
I just use

.\fastboot flashing unlock
[Google Pixel 6 Pro] V0latyle:
Are your Platform Tools up to date? Have you tried a different USB cable or port?
[Google Pixel 6 Pro] daveseris:
I'm hoping someone has had this happen and remedied it or just has an idea what may be wrong. I have successfully regained root after several factory image updates (no wipe) with no problems by using the patched boot.img . The latest factory image applied with no problem, but I cannot get Magisk (Canary 24102) to patch the boot image. I get to the install screen which only has select and patch as an option. I select the boot.img but when Magisk returns to the install screen, "Let's go" is greyed out. The Select and Patch a file radio button is lit. I'm hoping someone has an idea to avoid the dreaded wipe install.
[Google Pixel 6 Pro] Dragon Kumera:
kinda double post here. I posted my reply in the other thread for p6p.
[Google Pixel 6 Pro] v2.2v:
Holy crap I've been out of the game for a looooong time. Thinking about rooting but not sure what the most stable custom rom available is. Anyone want to point me in the right direction? I'll take it from there. Thank you!
[Google Pixel 6 Pro] roirraW "edor" ehT:
What @fil3s said. Sounds like you're using PowerShell instead of Command Prompt. PowerShell requires the ".\" in front of every command.

And what @V0latyle said is always good to check, too.
[Google Pixel 6 Pro] JetBlackfrost:
Thank you! I can't believe that after rooting 3 phones I goofed on something so basic lol
[Google Pixel 6 Pro] mustardseeds:
I'm trying to apply the update with root. When I try to sideload it I run

1) adb reboot sideload

2) adb sideload full-ota-image.zip

but nothing happens. The command prompt instantly gives "Total xfer: 0.00x"
[Google Pixel 6 Pro] RetroTech07:
Let's try a different way. With your phone connected to your PC and you're booted into windows, go into recovery mode.

adb reboot recovery

From there you should be presented a menu of options. Use the volume keys on the right to select "apply update from ADB" and then press the power button to select it.

Then, try sideloading the file by using

adb sideload your-file.zip

At this point the file should be transferring and updating your system.

Report back if that works.
[Google Pixel 6 Pro] pcriz:
Shouldn't the first command be

Adb reboot recovery
[Google Pixel 6 Pro] mustardseeds:
Got

error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

Tried deleting adbkey and adbkey.pub and running adb kill-server'. The keys were created but still got the unauthorized error. I've also tried revoking and toggling USB debugging in the Android settings.
[Google Pixel 6 Pro] Lughnasadh:
Try...

Unplug phone from computer

Revoke USB debugging authorizations in Developer options

adb kill-server

Connect phone to computer

adb devices

You should get a popup to authorize
[Google Pixel 6 Pro] V0latyle:
No, this is a shortcut. Takes you straight to sideload mode instead of having to go through recovery options.
[Google Pixel 6 Pro] RetroTech07:
I'm curious if your phone is even listed when you run the command "adb devices". If not, there are some other things I could have you try as it may be related to windows and not necessarily your phone.
[Google Pixel 6 Pro] Koss4c:
nice! how goes thhe Kernal now? no issues? main reasons for changing from stock?
[Google Pixel 6 Pro] jcp2:
No issues. Custom kernels are almost always better to run because they are more up to date on things. I'm not a kernel expert by any stretch of the imagination, I've just been running custom kernels on my phones for years with no issues at all.
[Google Pixel 6 Pro] mustardseeds:
Yes it was, I think the download was corrupt or I was trying to add the wrong one or something...
[Google Pixel 6 Pro] mustardseeds:
I followed the steps to sideload the OTA and install Magisk successfully. But when I check for updates it still says an update is needed and it fails the same way "Couldn't update". Is this expected? Just to be clear the newest is 12.0.0 (SQ1D.220205.003, Feb 2022) ?
[Google Pixel 6 Pro] V0latyle:
Yes. Glad you were able to update.
[Google Pixel 6 Pro] mustardseeds:
It still didn't work. Build number is SD1A.210817.036 instead of SQ1D.220205.003. There were no errors while sideloading and Magisk had to be reinstalled. I wonder what I'm doing wrong.

Does this procedure only work on the pro version of Pixel 6?
[Google Pixel 6 Pro] s3axel:
My apologies if this seems like dumb question, but what is the name of the OTA file you downloaded starting with (oriole/raven)?
[Google Pixel 6 Pro] mustardseeds:
oriole-ota-sq1d.220205.003-22e71d3d.zip is the file name
[Google Pixel 6 Pro] RetroTech07:
No, this works for both phones.

Just for clarity, can you list everything you've done thus far, step-by-step including any errors? What version of Magisk are you using? Start from the beginning and be as detailed as you can.

There's a lot of info spread out it would help to have it all in one place since it seems like you've done so many steps and had a few hiccups.
[Google Pixel 6 Pro] Az Biker:
Which device do you have?

Unless I'm mistaken, oriole is for the Pixel 6, and raven is for the 6Pro.
[Google Pixel 6 Pro] V0latyle:
You're using the wrong file. "oriole" is the Pixel 6. "raven" is the Pixel 6 Pro.

Other than that, the process is the same.

Correct, look at the top of this thread
[Google Pixel 6 Pro] Az Biker:
This was my attempt at being subtle, and seeing if the user had a 6 pro but trying to flash a Pixel 6 factory image :D
[Google Pixel 6 Pro] V0latyle:
Well, I have about as much subtlety as a GBU-43.
[Google Pixel 6 Pro] Az Biker:
Anyone order an instant LZ????
[Google Pixel 6 Pro] roirraW "edor" ehT:
My unsolicited assumption 😁: Since @mustardseeds asked "Does this procedure only work on the pro version of Pixel 6", I take that to suggest that they do have a Pixel 6 (Oriole), although it's definitely not a definitive answer yet.
[Google Pixel 6 Pro] Dragon Kumera:
I also am thinking that as well. I dont think their pixel 6 (if they dont have a pro) likes what they are doing to it with wrong factory image
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think the opposite. I think they are using a Pixel 6 (not Pro), and they're using the right file, but something else is going wrong.
[Google Pixel 6 Pro] Dragon Kumera:
that is also a possibility. I would suggest a redownload of the full image or ota and try again.

edit. I see you moved up in rank congrats :).
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oh, thank you! :) :)
[Google Pixel 6 Pro] dilligaf56:
Got a bit of a scare when updating to the February factory image today.

After updating the bootloader and the radio, during the image update, it failed after 6 of the first set of 11 files. The phone went into a bootloop, but I was able to get into fastboot mode...tried the .zip update again but somehow it had reverted to an old (77xxxxxx) bootloader version. Reinstalled the bootloader and radio again, and then had a couple of more image updates fail again, but after a different number of files had been written out. After the first one I thought that perhaps I had a bad download, but it failed in different places on subsequent attempts.

Finally it completed, I was able to reboot using the January patched image file, then ran Magisk and all is good. Whew!!

I was using a known-good cable with the same laptop I've used for quite a while with no issues. Wondering what else might have caused this problem...?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Wow, glad you got it recovered. That troublesome Loki. (not the very old Android exploit allowing rooting of some otherwise unrootable phones, and later an unwanted trojan)
[Google Pixel 6 Pro] dilligaf56:
As in Loki, the trickster Norse god....yeah, must have been him - nothing else makes sense!