yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Homeboy76:
Those are old post, the latest factory & OTA images for the Pixel 6 "oriole" are: 12.1.0 (SP2A.220405.004, Apr 2022). Also the latest SDK Platform-tools is 33.0.1.

What is the current problem you are having with your Pixel 6?
[Google Pixel 6] squidbutt:
I'm getting this error

reported max download size of 261095424 bytes

sending 'boot' (65536 KB)...

OKAY [ 1.853s]

writing 'boot'...

FAILED (remote: partition (boot) not found)

finished. total time: 1.869s
[Google Pixel 6] Homeboy76:
Did you try changing USB Port/Cord?
[Google Pixel 6] Homeboy76:
Update

Magisk Canary

24306
[Google Pixel 6] squidbutt:
No I haven't I'll try that and get back to you
[Google Pixel 6] Lughnasadh:
For everyone's information: This version fixes the bootloops that were occurring on the Pixel 6 series when updating to the April 12.1 build via OTA "Install to Inactive Slot" method, even when using Stable Magisk, among other things.
[Google Pixel 6] squidbutt:
i tried two different cables and ports with the same outcome
[Google Pixel 6] capntrips:
Can you share the issued command that generated the error?
[Google Pixel 6] squidbutt:
ive also tried the factory image and the ota with the same results
[Google Pixel 6] Homeboy76:
Two Questions:

1. Are you using Magisk Canary?

2. Did you patch the SP2A.220405.004, Apr 2022 boot.img?
[Google Pixel 6] squidbutt:
yes and yes
[Google Pixel 6] Lughnasadh:
Are you using the latest Platform Tools (33.0.1)?
[Google Pixel 6] capntrips:
Is your device booting normally (outside of attempting to get it rooted)? Have you tried to fastboot boot the patched image, rather than fastboot flash? Just to confirm something odd hasn't happened, is the size of your patched image 64mb?
[Google Pixel 6] Binary Assault:
I'm having the same issue and have the latest platform tools. I upgraded to Magisk Canary 24306 with no luck

I'm running into the same, or at least similar issue.

I manually flashed OTA via sideload (latest April as of last night). Took just fine. Let phone start, once finished and update finished, rebooted.

Dumped the boot.img via payload dumper, moved it to the phone like normal, patched in Magisk (size: 65mb), rebooted to bootloader and issued fastboot boot <patched image>.img

Starts up, gets to google logo for a bit, then reboots and starts up with stock boot image.

Same issue happened in the March update, haven't been able to root since (had it previously).

For fun, tried stable Magisk and same results.
[Google Pixel 6] Lughnasadh:
Although this doesn't happen too often, sometimes boot images can get corrupt while using the file transfer method from phone to pc. That is why in John's instructions he says to use ADB pull instead. Having said that, not sure if that is your issue, but thought I would just throw that out there.
[Google Pixel 6] Binary Assault:
I explicitly use adb pull/push due to the speed difference when using a standard file explorer with the MTP protocol. So for me, unfortunately is not the case.
[Google Pixel 6] capntrips:
Does it ever drop from the Google logo to the G logo? Do you ever have adb? If so, adb logcat might be helpful for diagnosing the issue.

If you really want to get your hands dirty (no pun intended), you can run the dirty pipe exploit from here, and grab the ramoops on the subsequent boot into stock:

cp /sys/fs/pstore/console-ramoops-0 /sdcard/Download

Edit: Did you have any Magisk modules enabled? If so, it might make sense to try to disable them.
[Google Pixel 6] badabing2003:
I'm assuming that you're bootlooping right?

Because you're flashing to the active slot and it is not finding the boot partition.

Have you tried flashing factory to both slots? on one it probably would fail, but if the other is intact it probably would work fine.

Have you tried Android Flash tool ? It is reported to have saved some phones.
[Google Pixel 6] Homeboy76:
@squidbutt ,

Did you get your phone rooted?
[Google Pixel 6] squidbutt:
I did. It turns out I was skipping the flashing of the ota and or factory

I got it rooted but spent all day trying to install the pixel add-ons for magisk.

One time I tried the snow cone custom rom mentioned in op but all it did was unroot my phone and change the boot screen. The rest was stock

Then I tried to just root that and got boot loop

The only module I've had any luck with is the force call recording option and that's a root app

I never have any luck booting into safe mode..could never get it to work so I ended up wiping,reflashing,rooting etc over and over trying to get these modules to work lol

But yes it's rooted
[Google Pixel 6] Homeboy76:
We're Glad you got the factory image installed and rooted. (y)

Some Magisk modules require updating before you can use them with a NEW factory image.

Why?

Sometime, Google makes changes to the new factory image that breaks modules. A broken module, usually, causes bootloops will not work until the Developer of the module updates it for the new factory image. That is why I recommend disabling/removing all modules before flashing and rooting a new factory image.

Please be careful when installing a Custom ROM or removing a Custom ROM to return to stock.

Why?

Several members have bricked their phone by not installing/removing a Custom ROM correctly.
[Google Pixel 6] Mason_lee:
thank you for this!!
[Google Pixel 6] ratrat420:
Hi guys, my phone is bootlooping when I am trying to root through the latest Magisk Canary app, (tried the stable magisk version and it didn't work either). If I flash the stock boot image, the phone loops into the system just fine.

I am using the latest platform tools(33.0.1) and my active boot slot is 'b'. I am on (SP2A.220405.004, Apr 2022) build.

Could someone post a video or detailed instructions on rooting through OTA? I have no clue how to do it?

If there is any other method also, I'd be willing to try. Please help me!
[Google Pixel 6] Homeboy76:
Try booting 'Safe mode' then reboot and flash the magisk patched boot.img

fastboot flash boot magisk_patched_boot.img

...rooting through OTA...

OP, Part II - Instructions, 3. Take the OTA...
[Google Pixel 6] badabing2003:
This is probably because the magisk_pacthed.img is not good, which could be due to how you transferred it to the phone, I have seen many reports that transfer through file manager is not always very reliable.

In addition to what @Homeboy76 suggested, you can also try transferring the boot.img through adb.

Test it first before flashing to see if it boots to root ok (without the flash option)

fastboot boot magisk_patched_boot.img

One last thing, make sure when using Magisk canary (recommended) you set the channel to canary.
[Google Pixel 6] kengel1969:
Hello all, ok so coming from pixel 3 with Fi service, I bought new pixel 6 and just wondering if i should boot up, copy data and activate or root first before doing anything else ?

will it be any different setting up and transferring data over from pixel 3 after it is rooted ?

thank you in advance
[Google Pixel 6] capntrips:
If you're going to root, do that first, as you'll have to wipe the device's data to unlock the bootloader. I've had good success with device to device transfer, though some apps and settings will have to be redone.
[Google Pixel 6] manjaroid:
I might be confused, but when I used Canary before it updated automatically and I don't remember specifying a channel. Right now I'm using beta/stable 24.3 and Update Channel options are Stable, Beta and Custom. If it's the same for Canary is this the correct URL to use in the custom field?

https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
[Google Pixel 6] badabing2003:
magisk-files/app-debug.apk at canary · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com
[Google Pixel 6] manjaroid:
What I couldn't remember is that 24.3 has just the three channels minus Canary, but once Canary is installed its channel comes pre-configured.
[Google Pixel 6] badabing2003:
True
[Google Pixel 6] Homeboy76:
Update

Magick Canary 24307
[Google Pixel 6] rfgamaral:
Hey folks. I'm a bit confused about the procedure to take an OTA and keep root, and would really appreciate some pointers.

I have patched my boot.img as per the initial instructions (extracted boot.img from factory image, patched with magisk, and flashed it with fastboot).

It's my understanding that to take the May OTA (I'm on the April one) I have to:

Go to magisk, uninstall, remove images

Install the OTA (both steps, DO NOT REBOT)

Go to magisk again, install to inactive slot

Reboot the device

Is that it?

What's confusing me is that the instructions for this on the OP (which link to the official instructions) says that "install to inactive slot" has been removed because Google changed how OTAs are taken, and that magisk does not quite have support for that. However, I'm using magisk 24.3, and the option is there. So, I'm bit unsure if it's safe to do this procedure or not.

Some pointers in the right direction would be really appreciated.

P.S. I disabled automatic system updates in the developer settings, but I opened the system updates screen in the settings, and now it says that the update will resume when the device is inactive. Is the update going to be automatically installed during the night? I hope not, until I figure out the right procedure to keep root.
[Google Pixel 6] badabing2003:
If I were you, I'd forget about OTA update, just follow the guide for dirty flashing, with full factory image (Keep data) and you're good to go.

I'd also switch to Magisk Canary.

Good luck
[Google Pixel 6] spasecowboi77:
I'd wait till the community gets more info on the update
[Google Pixel 6] badabing2003:
I have the update running all good on my main phone. (dirty flashed)

As easy as all the previous updates.
[Google Pixel 6] badabing2003:
deleted, wrong thread
[Google Pixel 6] Lughnasadh:
That note you are referring to in the instructions is old and there is currently a Pull Request to remove it, so you can ignore it as Magisk has been updated to support "Install to Inactive Slot" on Pixels. You may want to use Canary 24307 though. This method did not work with Stable 24.3 on the April build but was fixed with Canary 24306/7.

However, this method is really hit and miss, to be honest.
[Google Pixel 6] rfgamaral:
That method feels like a pain to do every time there is an update, isn't the "OTA method" supposed to make this easier?

I'm still worried my phone will update automatically over night. How can I prevent that?
[Google Pixel 6] rfgamaral:
Too bad because I used to do a similar method on my previous phone (OnePlus 7 Pro) and it worked every time. It's an easy method, and the dirty flash takes more time, needs to be re-rooted, and needs a computer to do it. What bummer.

Say that I try the OTA method instead after updating to the Canary version, and the phone boot loops, is it easy to recover from that without losing data?
[Google Pixel 6] Lughnasadh:
If it fails you can "probably" either flash the factory image via the flash-all method in fastboot with the -w removed from the flash-all.bat script (to keep data) or sideload the OTA (will also keep data).
[Google Pixel 6] badabing2003:
I don't have an answer on why you are getting updates even though you have disabled it, it has never happened to me.

As for dirty flashing vs OTA, I guess it's a personal choice what you find easier.

One thing for sure, you'd find a lot more people running into issues with OTA updates than with dirty flashing.
[Google Pixel 6] Nightf0x_007:
hello something off topic need help here, i accidently flashed may update with wiping my device is there any way to retrieve the data that was on my storage ? thanks
[Google Pixel 6] Homeboy76:
If you backed up your data prior to flashing with the -w.
[Google Pixel 6] Nightf0x_007:
no i didnt
[Google Pixel 6] Homeboy76:
Then there is no way, that I know, to retrieve your data. :(
[Google Pixel 6] capntrips:
For me, it's more about not having to break out the computer just to install an update. Worst case, if it fails, you end up doing the exact same procedure you would have done without attempting the OTA.

As long as you don't restore images in Magisk, the update will fail. There is no fallback to the full OTA, as there at least used to be for OnePlus updates.
[Google Pixel 6] rfgamaral:
I just went to Settings > System > System Update, and now I see this screen:

I'm just afraid that rebooting will install this update automatically...

How can you find it "easier" to have to plug your phone to the computer every time you want to update the system, vs using the OTA mechanism? Honest questions, because I don't see how anyone can find this "easier". If you mean "safer", sure, I can understand that. But it's definitely not "easier" with the many manual steps that are involved, requiring a PC, command line access, etc.

As for people running into issues, maybe they didn't do all the steps in the right order, or maybe magisk had a few bugs (and maybe it still does), I don't know.

I don't mind doing the dirty flash once in a while, but doing it every time there's an update? That's just painful. The OTA method exists for a reason, to make things easier, as long as it works flawlessly, of course.

Anyway, I'm just really concerned that my phone will update overnight automatically or during a reboot that I happen to do. Because I don't want to update the device right now, and like I said, I can do the dirty flash method, I just won't have the time to do it in the coming days, and I don't want my device to brick because the update installed automatically. I really hope that doesn't happen.
[Google Pixel 6] rfgamaral:
If I'm understanding your first paragraph correctly, you're saying that you prefer the OTA method, right? When was the last time you did that one? Which magisk version were you doing at the time, and which update was that for?

I haven't done anything anywhere, yet, so here's hoping the update fails if it decides to update automatically anyway. But do you think it's safe to reboot device if I need to?
[Google Pixel 6] spasecowboi77:
Some of us experienced after rooting pixel 6, device is corrupted message I wonder if this went away with this update
[Google Pixel 6] capntrips:
Yes, I much prefer the OTA method. I did it this morning for the May update using Magisk 24307.

Yes, the update can't install if you've modified the boot partition (i.e. rooted with Magisk). The first thing the update does is match the checksum of the existing partition against expected, which will be different due to the patches that Magisk applies.
[Google Pixel 6] capntrips:
I experienced that with the March and April updates. This one went smoothly for me.
[Google Pixel 6] badabing2003:
Like I said, to each its own,

It literally takes me under 3 minutes to be updated and fully rooted.

I find it much less confusing, much less problematic and honestly quicker.

The only plus I see with OTA is being decoupled from a PC, but at a higher cost, if you're not in front of the PC, and anything goes wrong, which sometimes does with OTA (Google changes things, Magisk bugs, bad modules ...) , or if you don't the the exact dance sequence, you're bootlooping, what do you do then? You're not in front of a PC and you're out without a phone.

I'm not trying to convince you, you should do what you feel most comfortable.

if you're rooted, OTA will not install, so make sure you remain rooted if you don't want to get the update.
[Google Pixel 6] Slim2none4u:
I just use this to update.

https://xdaforums.com/t/pixelflashe...rooting-managing-pixel-phones.4415453//unread
[Google Pixel 6] rfgamaral:
@badabing2003 It's not about being in front of the PC or not (which I am during my day job, although not this week), but I just find a procedure where you have to press a few buttons in order on your phone much easier and convenient, than:

Download latest factory image

Extract files

Edit them to remove the -w flag

Reboot to bootloader

Run flash-all script

The phone reboots

Push boot.img to phone

Patch file with magisk

Pull patched file to PC

Reboot to bootloader (again)

Flash patched boot

Reboot the phone

This procedure has a lot more steps, and I honestly can't see how all this can be done under 3mins. Maybe you're referring to different/easier procedure?

I know you're not trying to convince me, and I'm not looking to be convinced of doing either option. I'm just tring to understand how do you see the procedure above faster/easier than doing the OTA one. If we take "less error-prone" out of the equation, the OTA procedure would be the way to go, it's just more convenient. Don't you think?
[Google Pixel 6] tom1807:
I still use Magisk Stable 24.3 and use now the Pixel Flasher (that's not an advertisement ;) ). It simply just works and the whole process (incl. root) took roughly 5 minutes. Positive side effect, I don't have to see the screen for ages that my device is optimizing.

Cheers

Tom
[Google Pixel 6] Homeboy76:
Update

Magisk Canary 24308
[Google Pixel 6] Binary Assault:
Although its been a while, I have still not been able to root. I just updated to the latest May update and I cannot root (same as my original post above). I also can't install the latest canary build which is funky. I went back to 23406 and that installed, but flashing the modified boot.img (rebuild with 23406) gives me a bootloop. I get to the google logo, it does its animation and goes to the 'G' with a progress bar. I hear the chime for USB connection (so I can probably get a logcat) then it reboots to the unmodified bootloader.

I tried safe mode -> bootloader -> boot patched and still failed. Since I took the May update (manually sideloaded), looks like the dirty pipe exploit was patched.
[Google Pixel 6] Homeboy76:
Did you patch the may boot.img with Magisk Canary 24306?
[Google Pixel 6] Binary Assault:
Yes. I just ran a logcat and it looks like it's still loading modules. Is there a more full proof way to remove modules besides safe mode? Didn't seem to work.
[Google Pixel 6] capntrips:
From the FAQ:

magisk --remove-modules from an adb shell should do it.
[Google Pixel 6] Homeboy76:
when I asked did you patch the May 2022 boot.img with Magisk Canary 24306.

I meant did you download the Magisk Canary 240306 App, Install it and patch the stock bootimg from the May 2022 factory image.

If you did that it is not possible for magisk to be installing with modules.

My guess is you flashed the May 2022 OTA image without disabling/removing the Magisk modules and uninstalling Magisk.

Suggestion

After, you've remove the modules, backup your data, dirty flash the May 2022 factory image, and patch the stock boot.img with Magisk Canary 24306 and flash it to root.
[Google Pixel 6] Binary Assault:
I'll give it a whirl. Thanks

Thank you
[Google Pixel 6] Jammo2k5:
Hey quick question. Is there a reason why step 16 of Root/Re-root is Flash the boot image directly and not use

fastboot boot magisk_patched-{XXXX}.img

and then using magisk manager to install magisk directly?

The benefits i see with this method are:

1. If the boot.img is bad it will fail to boot without flashing and wont brick the device.

2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the device only without any extra steps.

This is the method I used to re-root after the may update because I flashed the boot image directly when I rooted last month.
[Google Pixel 6] Homeboy76:
The step 16 you are referring to in the OP actually starts in the OP , ~~~ Part II Instructions ~~~, 2. Install/Update Factory Image

keep data

or

wipe data

,

Flash Factory Image Keep Data

or

Flash Factory Image Wipe Data

, • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, •

Patching the boot.img

- to root/reroot.

I've never read of one instant of a Google Pixel phone that was bricked because they used fastboot flash boot magisk_patched-....img.

Yes, the phones have boot looped.

Why did the phone boot loop instead of booting to the OS?

The main reason the phones were boot looping instead of booting the OS is the Magisk modules were not disabled/removed before pataching the boot.img.

One way to stop the boot looping is flashing the stock boot.img to both slots.

"2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the d

evice only without any extra steps."

Are you saying flashing the patched Magisk boot.img with fastboot flash boot magisk_patched-....img will not back up the stock boot.img so it can be restored?
[Google Pixel 6] Jammo2k5:
With my recent attempts, once the device has boot looped so many times it will refuse to boot with a device corrupt message even if I flash the stock boot.img. I had to flash the entire ROM with the -flag disabled to recover the device.

Saying bricked was the wrong phrasing for that.

Secondly yes flashing the magisk boot image using fastboot will not allow magisk to backup the image as it has no access to it and it won't backup when you patch an image to regular storage.

However if you boot with the patched image using the fastboot boot command and then patch directly using the recommended option it will backup the images for restoration and will allow the ota method of restore, update, re magisk without reboot method to work.

Im asking if there is a reason why that shouldn't be done because I don't want to **** up my device because something happens in the background I am not seeing.
[Google Pixel 6] Homeboy76:
First, my reply to your original post was not meant to dismiss your view of temporarily booting a Magisk_patched...img: fastboot boot magisk_patched....img.

I was explaining why step 16 is fastboot flash boot magisk_patched....img.

Second, I wanted to understand what you meant when you wrote:

"2. the stock images are backed up by magisk using this install method which allows for

restoring and OTA updates using the device only without any extra steps.

"

The only reference to OTA in this Guide is in the OP ~~~ Part II - Instructions, 3. Take the OTA Update and Maintain Root
[Google Pixel 6] Homeboy76:
Update

Magisk Canary 24309

Pixel 6 Android 13 Beta 2 support is here!
[Google Pixel 6] Homeboy76:
Update

Magisk Canary (c11ccbae) (24310)
[Google Pixel 6] Homeboy76:
Update

Magisk Canary (756d8356) (24312)
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release (8dfb30fe) (24313)

or

app-debug (8dfb30fe) (24313)

Note

"Debug builds should only be used if you are actively developing Magisk, or if you want to submit bug reports"
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release (bf04fa13) (24314)

or

app-debug (bf04fa13) (24314)

Note

"Debug builds should only be used if you are actively developing Magisk, or if you want to submit bug reports"
[Google Pixel 6] humb13:
Hey guys,

Currently I have a Oneplus 8. Unfortunately the battery is swollen and about to go. I believe it might be a better idea to upgrade the phone instead of spending money to replace the battery. I'm looking into a Google Pixel 6 and reading Homeboy76's root instructions. They're not all that different from the Oneplus with the following differences I'd like to inquire about:

It's says to extract the kernel (boot.img) and a flash-all.bat file. I'm not seeing anything explaining what to do with the batch file after extracting it.

Homeboy76 recommends a clean flash in order to perform a major upgrade (e.g. 12.00 to 12.1). What's the best way to back up your data (apps & media) before performing the upgrade? To my knowledge a clean flash wipes everything. Speaking of upgrades, Oneplus performs them OTA. We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?

The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?

Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?

Thanks for your help.