yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] freonchill:
Dahenjo

thanks for taking that one more step of clarification

reading the instructions for the "Update and Root OTA Sideload" in the OP, I got confused on item 6, that said "see note 1" as in downloading the OTA again, but in reality, its the factory zip that matches the OTA that we were to download. patch in magisk in the OS (unrooted), then reboot to the bootloader and fastboot the modified boot.img to get root back...

Like another post in this topic, i came from oneplus where the updates were just going to TWRP and installing the complete OTA.zip and rerunning the magisk installer.zip. where as on the pixel 6 (and assuming because of android 12, we don't have TWRP) there is the 2 step process of using adb sideload, then patching the new boot.img and then going back and updating the bootloader in fastboot since we "lose" root for the process where we have to boot back to system before loading magisk again.

(note - this is how I understand it right now, but I have not done the process - too much work to do tonight to take the time to fix it if I do something wrong...) maybe tomorrow night.
[Google Pixel 6] V0latyle:
If you're at the point where you're going to download the factory zip, just dirty flash it and don't bother with the OTA.
[Google Pixel 6] freonchill:
am I wrong on where to the boot.img that you have to modify with magisk and then flash to the bootloader?
[Google Pixel 6] V0latyle:
Yes, you never flash ANYTHING to bootloader except the bootloader image. To gain root, however, you would flash the boot image IN bootloader.

Bootloader and boot are NOT the same thing, and mixing the two up can brick your phone.
[Google Pixel 6] Dahenjo:
I'd heard there were ways to extract boot.img from the OTA but thought it was simpler to just get it from the factory image despite all the bandwidth & local storage needed.

However I found there's an easy & quick way to do that, described here:

Extract Payload.bin via Payload Dumper Go

Just tested it with the current OTA and it works fine, although I'm updated already, but now am set up to do this for the next OTAs with just the one download.
[Google Pixel 6] freonchill:
V0latyle

I apologize if I confused some of the terms.

boot.img is the boot image and it is flashed in fastboot bootloader, right?

boot.img is patched by magisk for root

for update and root OTA sideload

1. download feb ota zip

2. adb reboot to sideload feb ota

3. reboot into system and finish update (now updated to feb update)

4. get boot.img from matching feb factory zip & patch feb factory boot.img in magisk app

5. fastboot flash boot "patched boot.img" (as listed in OP, "reboot to bootloader")

6. reboot to system and rooted

right?

i definitely want to get it right, because I don't want to brick OR spend the time having to start over.
[Google Pixel 6] V0latyle:
You're not going to brick unless you do something dumb.

If you're not already rooted, then yes what you described is one way to accomplish what you're trying to do. But, again, since you'll be downloading the factory image, just update using that.
[Google Pixel 6] tensux:
uggh I did something wrong. When I got to step 3 and clicked install and I only had the options: direct install and patch image. I did direct install (knowing it would most likely not work) and have lost root. I am hoping to root without wiping like I ended up doing the last update.
[Google Pixel 6] V0latyle:
I assume you're using an older version of Magisk that does not support installing to inactive slot. Upgrade to Magisk 24.
[Google Pixel 6] bige93:
I decided to ditch root and uninstalled Magisk completely using built-in uninstaller. After that device failed to boot up.

I flashed latest stock full image (w/o wipe) - red Your device is corrupted and cannot be trusted message appeared. Google Pay stopped working.

Any idea how to fix this without full wipe?
[Google Pixel 6] V0latyle:
Maybe. I got this message (and a boot loop) on my wife's 5a after she screwed up the OTA. Don't switch slots, try sideloading the OTA. That's what fixed it for me.
[Google Pixel 6] bige93:
But the device already runs latest update. OTA should still install?
[Google Pixel 6] V0latyle:
Yes. OTA doesn't care what firmware is already on your device, as long as it isn't newer.

When that red screen appears, it means there is dm-verity corruption (see here)

Here's what I would do:

Reboot into bootloader, connect to PC

Launch command line in Platform Tools, then check active slot: fastboot getvar current-slot (If this doesn't work, use getvar all, you'll find (bootloader) current-slot: <slot> in the print) Take note of which slot is currently active.

Enter recovery, select Apply update from ADB

In the command line, use adb sideload <drag and drop the OTA zip>

When the update finishes, select Reboot now

Allow device to boot and complete update, then reboot to bootloader and go back to step 2 to see if your device switched slots.

If you don't get the red EIO screen anymore, go ahead and patch your boot image with Magisk.
[Google Pixel 6] mustardseeds:
I am unable to apply the update.

I have Pixel 6 (NOT pro) currently with build number SD1A.210817.036

I have root with Magisk. I am getting the message "couldn't update" when I try to do a system update. So I try to sideload as per the instructions on the first post here.

1) Download 12.0.0 (SQ1D.220205.003, Feb 2022) from https://developers.google.com/android/ota (resulting file is named oriole-ota-sq1d.220205.003-22e71d3d.zip )

2) Connect phone to computer with USB cable.

4) select 'use usb for file tranfer/android auto'

5) Open powershell in platform-tools folder

6) Run the command 'adb reboot sideload' from the terminal

gives

* daemon not running; starting now at tcp:5037

* daemon started successfully

7) Wait for phone to reboot

8) Now see 'Now send the package you want to apply to the device with "adb sideload <filename>"...'

9) From terminal run 'adb sideload oriole-ota-sq1d.220205.003-22e71d3d.zip'

10) Wait a minute for command to complete serving

Phone reads "supported API: 3 \ Finding update package... \ Verifying update package ..."

11) Terminal reads 'Total xfer: 1.00x' and phone is in recovery, with the text at the bottom

Update package verification took 149.1 s (result 0).

Installing update...

Step 1/2

Error applying update: 7 (ErrorCoded::kInstallDeviceOpenError)

E: Error in /sideload/package.zip (status 1)

Install from ADB complete (status: 1).

12) select 'reboot system now' by pressing power button on phone

13) phone reboots quickly

14) Sometimes I have to reinstall Magisk, other times it's already there

15) Phone still says 'Couldn't install system update' and has SD1A.210817.036

I also tried the "Update and Root Automatic OTA" but it didn't work.
[Google Pixel 6] mustardseeds:
I just tried Magisk, Restore Image. The OTA still failed. I went to "Install to inactive slot." (which probably was a mistake). Now my phone can't boot. It's stuck on the screen
[Google Pixel 6] airtower:
Try changing the boot slot by booting to fastboot and running

fastboot --set-active=a

If that doesn't work, dirty flash full image per instructions in OP.
[Google Pixel 6] mustardseeds:
Thanks the fastboot method worked. Maybe it should be added to the first post that if the system update fails not to restore Install to inactive slot in Magisk.
[Google Pixel 6] V0latyle:
Are you using the latest version of Platform Tools?

The thing is, you're having a unique problem. Chances are you are either doing something wrong or using the wrong software. Changing slots after an OTA can actually cause a bootloop.
[Google Pixel 6] lackalil:
Updated apps today (didn't check the list...it was 40 apps. Lost root. Also removed Magisk from my home page. Simple enough to reflash the boot image but still annoying. Anyone else run into this?
[Google Pixel 6] mustardseeds:
I agree. I keep getting

Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E:Error in /sideload/package.zip (status 1)

In cmd it seems to jump from 30% to 100% all of a sudden. Just to be certain, we flash the oriole-ota-sq1d.220205.004-36ba07e7.zip without making any changes to it? Could it be a device driver issue from the PC?
[Google Pixel 6] V0latyle:
There's a definite possibility, but I doubt it.

Sorry if this seems redundant, but have you managed to recover your device yet? There are a few more things you can try but it'll probably involve wiping data.
[Google Pixel 6] mustardseeds:
Yes my device is recovered, fully operational. Just wont update.
[Google Pixel 6] V0latyle:
Oh okay. Go back to the OP and follow the factory image method. It won't wipe your phone, and it should work. Just make sure you update your bootloader and radio if they aren't already.
[Google Pixel 6] mustardseeds:
What is meant by "update bootloader and radio"? How do I check this?
[Google Pixel 6] V0latyle:
When you are in bootloader mode, the device displays the bootloader and baseband versions. If the version number of the bootloader or baseband images don't match what is on the screen, you need to update them.
[Google Pixel 6] mustardseeds:
Thank you so much this worked for me!

The first couple times I tried to get root I got a bootloop. I managed to get it working by patching the boot from the factory zip in magisk, then flashing with

fastboot boot magisk_patched.img --slot all
[Google Pixel 6] V0latyle:
I'd like to point a couple things out:

Disabling verity/verification are no longer necessary

Using fastboot boot boots the image you send to the device but doesn't flash it to the /boot partition, so if the flashed boot image isn't patched, you'll lose root when you reboot. To actually flash the patched image you must use fastboot flash boot.

The --slot= argument has no function when live booting an image as described above. It's only for flashing to both slots.

I'm not sure why you were having trouble with bootlooping; are you sure you were using the boot image that matches the system update?
[Google Pixel 6] cammykool:
if i don't really need root for anything but is there any way to unlock my BL so i can flash to and from without worry but keeping safteynet working? or at that point should i root?
[Google Pixel 6] V0latyle:
Just to make sure I understand correctly, you're asking whether having an unlocked bootloader without root will pass SafetyNet?

The answer is no. The device will fail CTS Profile; this can be fixed using Magisk modules, but doing so requires root.

If you don't want root, why would you want to be able to flash your device?
[Google Pixel 6] cammykool:
Factory images mainly.
[Google Pixel 6] V0latyle:
Ah. Well...the easiest way to do this would be to use Magisk modules such as Universal SafetyNet Fix and MagiskHide Props Config to pass SafetyNet. You don't have to necessarily use root for anything. Personally I only use it for ad blocking (systemless hosts).
[Google Pixel 6] cammykool:
If I need to root maybe I will take advantage of like a kernel or something. I'm on 12L. Will that make a difference?
[Google Pixel 6] V0latyle:
Not really. However, with Android 12, custom kernels may not have proper boot image headers, requiring that you disable verity/verification.
[Google Pixel 6] catseyenu:
Tried the OTA coming from root SQ1D.220205.003 to SQ1D.220205.004.

Magisk 24.1

Followed instructions per capntrips post:

https://xdaforums.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/post-86443557

After trying to load my home screen for a second it reboots to recovery with "Cannot load Android system. Your data may be corrupt. If you continue to get this message. you may need to perform a factory data reset..." w/ 2 options: Try again (I did, no love) and Factory data reset.

Hoping to not have to reset... any chance I can sideload the OTA zip at this point?
[Google Pixel 6] V0latyle:
If you disabled verity/verification, you'll have to wipe data to continue. Otherwise, reflash vbmeta without the --disable arguments.
[Google Pixel 6] catseyenu:
I have never dealt with either verity or vbmeta. This phone was purchased and rooted after the newer Magisk came out and verity/vbmeta were not tampered with.

How would I reflash vbmeta without the --disable arguments?
[Google Pixel 6] V0latyle:
Same as you'd flash any other partition:

fastboot flash vbmeta vbmeta.img

But in this case I don't think this is the problem. Something went wrong somewhere.

Try this:

Download the factory image that matches the update you installed

Extract the boot.img and attempt to boot it:

fastboot boot <drag and drop boot.img>

If the device boots, follow the instructions in the OP under Initial Root to patch the boot image, then reboot to bootloader and flash it.

If the device does NOT boot and you end up in Rescue Party again (corrupted data screen), try sideloading the OTA.
[Google Pixel 6] catseyenu:
Thank you!

This is weird, the factory image that matches the update (oriole-ota-sq1d.220205.004-36ba07e7.zip) file structure is different from the first update (oriole-sq1d.220205.003-factory-a5a63f2a.zip) I extracted my boot.img from. I'm not seeing a boot.img file to work with.

Edit: Oops I suppose using the "factory image" instead of the OTA would help? Sorry, I'm coming from a rooted Sprint Note 4 that T-Mobile had to pry out my hands... it's been a minute. :D
[Google Pixel 6] V0latyle:
Yeah, the factory image and the OTA are not the same. You can extract the boot image from the OTA, but that requires a third party tool like Payload Dumper.
[Google Pixel 6] catseyenu:
Factory boot.img wouldn't boot, trying sideload gets me:

>adb sideload C:\Users\*\Documents\*\platform-tools_r32.0.0\oriole-ota-sq1d.220205.004-36ba07e7.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: 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.

I'm hating life about now.

Found "receive files via ADB" or something along those lines that allowed me to bypass authorization and initiate the file transfer.

https://xdaforums.com/t/device-unauthorized-in-recovery-mode.4232895/post-84998953

Any guesses on how long this should take?
[Google Pixel 6] airtower:
You have the same problem I (and others) have. I believe it has to do with flashed vs booted partitions getting mixed up, but as it doesn't seem terribly widespread there's not a lot of data to sift through for proof. I plan to log my failed OTA next week.

You can change the boot slot and that may get you back online, otherwise just full dirty flash the factory image.
[Google Pixel 6] catseyenu:
Thanks, I'm currently sideloading the OTA... I think. :cautious:

Phone screen seems stuck on "verifying update package" and cmd promt is stuck on 30%.
[Google Pixel 6] airtower:
I never got sideloading to work with the phone in that state
[Google Pixel 6] catseyenu:
How do I back out of this operation and where do I go from there?
[Google Pixel 6] airtower:
Not sure if you're in a state where doing so could cause a problem but, you boot fastboot with pwr+vol down.
[Google Pixel 6] catseyenu:
Pwr+vol down didn't do anything so I tried pwr+vol up and I now have a screen with a big "O"/circle and "installing update" text. Cmd prompt still stuck at 30%.

What happens if I pull the plug?
[Google Pixel 6] airtower:
No idea where you're at then. You vol+pwr dwn may only work from a powered off state, not sure.
[Google Pixel 6] V0latyle:
Not all that long.

What happened when you attempted to boot the factory boot image? You ARE using the boot image, not the bootloader image, correct?

Unfortunately there is no way to set the ADB authorization without booting into system...that I know of.

The only other way to apply an OTA update would be from storage, but you can't push anything to storage if adb isn't authorized...

At this point, I would dirty flash the factory image either via ADB or the Android Flash Tool.
[Google Pixel 6] V0latyle:
To reboot the device, you have to hold the Power button for at least 10 seconds. Holding Volume Down at the same time will boot into bootloader. Holding Volume Up will boot into recovery.
[Google Pixel 6] catseyenu:
Several hours stuck at 30%?

I pulled the USB and am back in the recovery menu now.

Rescue Party again.

Yes

See: https://xdaforums.com/t/device-unauthorized-in-recovery-mode.4232895/post-84998953

See above?

I'm open to what ever you suggest as the best way to move forward.
[Google Pixel 6] catseyenu:
Unit was unresponsive other than to switch between the 2 updating screens using pwr+vol up until I unplugged the USB cable.
[Google Pixel 6] V0latyle:
Well, I've been wrong before, and this won't be the last time!

Sideload the OTA again. Don't interrupt it or do anything but select "reboot" when the update is done. Should get you back into system.

If that doesn't work, dirty flash the factory image.
[Google Pixel 6] catseyenu:
Renamed "oriole-ota-sq1d.220205.004-36ba07e7.zip" to "ota.zip" and sideload completed in about 5 minutes with a steady progression.

Do I still need to proceed with steps 5-8 in your "Update and Root OTA Sideload" guide? /wipes sweat off brow
[Google Pixel 6] V0latyle:
Yes. Make sure you let it boot "naturally" and let it sit for a bit. While it's doing that you can patch the boot image so it's ready to flash.
[Google Pixel 6] pa.pn2:
Were there any problems with rooting feb 004 version? Just asking..
[Google Pixel 6] catseyenu:
I'm unsure of what let it boot "naturally" means, it seems to cycle through several screens with one requiring me to push the power button to continue IIRC. Maybe not letting it sit for a bit is why I'm now struggling to get it to take a patched boot image?

I copied the boot.img (from the extracted image-oriole-sq1d.220205.004.zip from the factory image) over to the phone, patched it, copied it back and flashed it as prescribed and it went into a bootloop.

3 times I've tried and every time it fails some how and I have to sideload the OTA to start over.

I'm starting to feel like either the phone or me is snake bit.

I have a working but unrooted phone and I'm calling it quits for the night.
[Google Pixel 6] V0latyle:
After the OTA completes, select Reboot to System, and once the device boots into system, let it settle.

Make sure the factory image you downloaded matches the OTA update you're using. I suggest just using the latest one.

And I assume you are using Magisk 24?
[Google Pixel 6] airtower:
@capntrips Looks like the update is imminent, and I'm ready to log my OTA process. However, what's different about those two commands other the output filename? Or did you intend for me to run logcat | grep "update_engine" while updating (update.log) and then again through the reboot after flashing to inactive (reboot.log)?
[Google Pixel 6] catseyenu:
Roger that.

SQ1d.220205.004 was the latest I saw..

Yes.

I've got the "Your Device is corrupted and cannot be trusted" screen, apparently that's not normal. Reading your thread on it now.

https://xdaforums.com/t/new-solutio...be-trusted-and-may-not-work-properly.4400091/

I'm considering flashing the factory image with AFT to get a clean install and wondering if I'll need to wipe or not to be sure this puppy is set right...

Much appreciated, doing my P6 and wife's Tab A7 lite after 8 years of riding the Note 4 has an interesting learning curve.
[Google Pixel 6] V0latyle:
The corrupted screen (aka Rescue Party) was what happened when we had to disable verity/verification prior to Magisk 23016. A data wipe was required to continue. But in this case, I assume you are just applying the OTA and trying to root, and haven't disabled verity and verification (you'd know if you did, you have to be deliberate).

I have no idea what is causing this issue. Maybe the February update broke something. Try the January update and see what happens? Maybe something is borked in Magisk. I really don't know.

If you don't mind wiping your data, you could try a fresh start. Use the Android Flash Tool to flash the February update; make sure the Force Flash All Partitions and Wipe Device boxes are checked, but none others. Then, just set up and root as normal.
[Google Pixel 6] capntrips:
Exactly. The first command is intended to be run before starting the upgrade all the way through to the reboot and the second starting after (assuming adb runs at all, you might need to have it waiting, in case it reboots quickly from a failure).

I would also like the output of a few bootctl commands through the process, which I mentioned on the other thread. Edit: Also, the Magisk log noted in the post you quoted.

I'll do the same, for comparison. Is the March update coming early? Last I saw reported was March 7.

When everything else fails, the flash tool always works for me. Using it, I haven't been forced to wipe, yet.
[Google Pixel 6] airtower:
Got it. I saw something earlier in one of my feeds reviewing the changes in the March update. I didn't bother reading the article, but rather went straight away to see if it was available for me. Then I got distracted by something and now I can't find it #millennial.
[Google Pixel 6] hypermetuljason:
Regarding Passing SafetyNet - does this imply GooglePay and other such restricted services work while rooted?
[Google Pixel 6] capntrips:
Yes, I can confirm Google Pay works with Universal SafetyNet Fix. All of my banking and video streaming apps work without issue, though I have seen people mention quirks here and there (lack of fingerprint login in the Chase app, for example).
[Google Pixel 6] mic3r:
I just finished updating to Feb 004 image.

First I tried it via "Update and Root Automatic OTA". No luck - it took very long (more than an hour) and failed at the end. I've decided to download full factory image, patch boot.img with Magisk 24200, fastboot update factory image, fastboot flash boot patched boot.img from this factory. So far all good, no issues.

Do I understand it well, that I can use this patched boot.img for the next update as well?
[Google Pixel 6] Lughnasadh:
You should patch the boot image of the build you are on. So for March, patch the March boot image.
[Google Pixel 6] V0latyle:
You can temporarily boot an older image for temporary root in most cases. It all depends how you want to re-root following an update. Some folks extract and patch the new boot image, then flash it after updating; others might not want to go to the trouble, so they update, then live boot the old image and perform Direct Install in Magisk.
[Google Pixel 6] Lughnasadh:
Yeah, but I don't think that person was talking about having temporary root. I think it's wise to always use the boot image for the build you are on. There are often kernel changes/fixes/updates when new security builds come out and if you use old boot images you won't be getting the benefits of those changes/fixes/updates. Just my opinion and preference...
[Google Pixel 6] capntrips:
I'll bet it is a reference to the "master boot image" mentioned in a few of the upgrade methods described in the OP (e.g. step 6 of the OTA sideload method).
[Google Pixel 6] V0latyle:
For temporary root, it doesn't matter.

But yes, you shouldn't flash an old boot image with a new update.
[Google Pixel 6] Lughnasadh:
Yep, think we're on the same page now 👍
[Google Pixel 6] lu270bro:
i did the update and root automatic OTA method in the first post, and now stuck on the Google Screen, wont move past that. Cant get it to recognize in adb to factory flash/reset etc. Tried to boot to bootloader, recovery, etc, just never gets past this screen. I also get the "red" corrupt device screen before it goes to the normal bootloader unlock warning screen then to the google screen in the screenshot. Anybody got any pointers?
[Google Pixel 6] lu270bro:
ok so finally got it to fastboot, holding the keys down. not sure why it worked this time and not the other times, but i can get it pull in adb now.
[Google Pixel 6] capntrips:
Edit: nvm, missed the follow up before posting

Edit 2: It looks like the March update is delayed for PIxel 6, in case anyone else was wondering why they didn't have the option to install it.