yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] mustardseeds:
OK here is my process. I noticed an error on the phone I hadn't before, text is red.

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.

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 Tiny ADB & Fastboot

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) Magisk is still installed

15) Phone still says 'Couldn't install system update'

Other considerations: does it matter if USB debugging is enabled or disabled? Does it matter the location of the zip on computer when sideloaded? Should Tiny ADB & Fastboot be run with admin privileges?
[Google Pixel 6 Pro] jcp2:
usb debugging needs to be enabled. are you using platform tools v32.0.0?
[Google Pixel 6 Pro] RetroTech07:
First time I've ever heard of Tiny ADB lol.

As already mentioned; yes, USB debugging needs to be enabled, and I would suggest you use the latest platform tools for your machine instead.

To make sure things play nice with each other, drop your downloaded OTA file in the same directory that you're running ADB from.

I usually just create an ADB folder on my C:\ drive with the same name and run ADB from there; it makes the process much simpler when you run commands and load files.

I've read a few things about error code 7, and it could be a vast amount of things causing this to fail. I would verify the integrity of the package against the provided sha256 sum on the download portal.

Just to be sure, this link should be the file for your device. Give it a go again with proper tools and see how it works out.
[Google Pixel 6 Pro] V0latyle:
@mustardseeds As this is the 6 Pro thread, please move your questions for support to the proper thread here:

https://xdaforums.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/latest
[Google Pixel 6 Pro] lottarake:
Thank you for this thread. Just got my P6P today and went ahead and put on 12L and rooted it. After years of being on various OnePlus devices, I wasn't so sure I could apply the same methods on the pixel. Nice and concise instructions per method, much appreciated!
[Google Pixel 6 Pro] V0latyle:
In theory, this should work with all devices that comply with the recommended Android platform implementation. Pixel devices are, more or less, the prototypes of what Android devices should be.
[Google Pixel 6 Pro] ntegra:
So.. I don't know if after reading this entire thread I just skipped over all the successful "Automatic OTA/install to inactive slot" posts or if there hasn't been a single one.

I have now attempted the OTA process for the second time. When I tried from Jan to Feb, installing to inactive slot "corrupted" my P6P and I had to do a Google Flash Tool (because of where I was at the time).

This time I am attempting to install the 10MB patch that was just released. I...

1. restore images

2. take the OTA (optimize ran for 30mins or so)

3. no reboot. switch to magisk

4. flash inactive slot. reboot

phone restarts with root, I confirmed that it switched slots, however still on same version SQ1D.220205.003. and phone is telling me there is an update. when I go to the update screen it wants to reboot. I go back to magisk, restore image, flash inactive slot and reboot. phone comes back up with root on switched slot but still same version and android wants to reboot in updates (no install just reboot)....

Any ideas?
[Google Pixel 6 Pro] AverageLibrarian:
hey. im trying to get back into the rooting scene and am having a hard time finding a device. is this guide for all pixel 6 pro models? how can i know that the device i buy will be able to be unlocked and rooted? ive been searching for weeks for a new phone and finding a verizon compatible device that can be rooted and unlocked is very tedious.

i dont want to drop 500-1000 dollars on a device just to find out i cant root it. unrooted android is just boring. sorry if im being stupid here but any input would be appreciated. thanks
[Google Pixel 6 Pro] jcp2:
The procedures for unIocking bootloader and rooting are the same for pixel 6 / pro as long as you use the proper software. I believe all verizon phones are and have been for a few years - bootloader locked and unlockable. if you mean sim unlocked...then yes. I believe there is a 60 day wait to have a verizon phone sim unlocked to use on another network.
[Google Pixel 6 Pro] Nergal di Cuthah:
You have to get the google branded one to root it. It works on Verizon (including wifi calling and hotspot). You will have to shell out a lot but i believe google does financing (i wasn't approved so i paid 899 (i think) for the 128gb pro) but the savings on your Verizon bill woah daddy.
[Google Pixel 6 Pro] AverageLibrarian:
so if i get a factory unlocked one on ebay it should be rootable with this method? does android version matter? if i update to latest the moment i get it?

i buy my phones factory unlocked on ebay. i never pay full price for phones. so i would be buying a google factory unlocked unbranded one. all my phones have been unlocked. never been in contract.

for both of you. are there any other phones for rooting and verizon use you could recommend? im open to options since i have no brand loyalty.
[Google Pixel 6 Pro] jcp2:
if they are carrier and bootloader unlocked, then you have no problems on any network carrier. It will be rootable. As far as verizon goes, I'm in Canada and don't have any experience with US carriers. Hopefully more people with verizon experience will chime in.
[Google Pixel 6 Pro] Nergal di Cuthah:
@AverageLibrarian i'd get the imei before buying (which you should do anyway to make sure it's not stolen etc) and plug it in to

Check Your Device's IMEI | Bring Your Own Device to Verizon

Check your device's IMEI to see if it's compatible with Verizon's network. Need help finding your IMEI? We have instructions for your device type.

www.verizon.com

Mark you don't know for carrier on the second screen

You should get something like

If it says NVZW you can root it
[Google Pixel 6 Pro] foobar66:
Hmm ... so far Microsoft Intune and Microsoft Teams were working fine with root. Both were on the Magisk Denylist.

Yesterday I noticed that MS Teams would not work any more (it says my device is rooted). Not sure what has changed (besides me updating from sq1d.220205.003 to sq1d.220205.004).

If anyone knows a solution ...

Not a very big deal ... I barely use MS Teams on my phone ... I can still access it throug teams.microsoft.com (in 'desktop' mode).
[Google Pixel 6 Pro] Ultimoose:
As always, love you guys and gals for all you do to make updating and keeping root as painless as it can be.

Feb OTA update was failing so I did the factory image update to keep root and it worked just as expected.

For everyone who maintains this information, my everlasting thanks.
[Google Pixel 6 Pro] V0latyle:
Are you using Universal Safetynet Fix? Have you configured DenyList on the Play Store?

I appreciate it. I wouldn't call this a job but I have put a lot of time and effort into it, and since "thanks" is all I get, it goes a long way.
[Google Pixel 6 Pro] foobar66:
Yes, USNF 2.2.1 working fine.

Denylist on play store? Why do you think that will make a difference? I will try ...

I had put Play services on the Denylist but that did not help.

The weird thing is that the MS Teams starts normally, then a few seconds later shows the following screen:

That is with MS Teams version 1416/1.0.0.2022 and Intune version 5.0.5421.0
[Google Pixel 6 Pro] V0latyle:
Not Play SERVICES, Play STORE.

USNF disables DenyList on Play Services.
[Google Pixel 6 Pro] foobar66:
Nope, still does not work with Play Store on Denylist ... but thanks for the tip !
[Google Pixel 6 Pro] 93fuelslut:
Does anyone know how to flash the core patch? Supposedly a12 doesn't like different or changed signatures so it doesn't want those apps installed and the core patch deals with that.

But I'm not sure if you flash via magisk or you need riru or lsposed?

Pixel 6pro stock rom rooted
[Google Pixel 6 Pro] 93fuelslut:
If I already have magisk installed but my ota is currently in the position in my picture, can I follow the steps I posted in the other pic?
[Google Pixel 6 Pro] V0latyle:
Not sure what you mean. Core patch? Riru doesn't work with Magisk 23010+.

Hit Resume, and BEFORE you reboot, go back to Magisk and install to inactive slot.
[Google Pixel 6 Pro] 93fuelslut:
Turns out it's Lsposed not riru so now I gotta Google how to install that to install the core patch mod. Core patch is to let you install non Google apps or modified apps. Because on a12 the signatures have to match or something.

If I install magisk on the inactive slot, once it reboots, magisk will make it reboot to the rooted slot?
[Google Pixel 6 Pro] ScottIsMyName:
Have you checked to make that both Intune and MS Teams have all of their activities denied in the DenyList? That is, if you click the app in the DenyList, make sure all checkboxes that show up are checked. By default, not all of them get checked (which is kind of annoying).
[Google Pixel 6 Pro] foobar66:
Yes checked...all activities/services were checked.
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Don't mean to sound pedantic, I access my office email on phone. I would suggest to again clear cache and data from all your O365 applications first, then add all components of company portal to Deny list. I use teams on my phone for almost all my office meetings, and all my O365 apps work fine. Cheers.

Regards.
[Google Pixel 6 Pro] 93fuelslut:
Hey thanks for your help. Worked like a charm. Now I gotta do it again for the Feb. Just complete the same steps if I have Lsposed installed, or do I need to un install that as well?
[Google Pixel 6 Pro] V0latyle:
I honestly don't know about Lsposed, I only use 3 modules and none of them alter system.

As for updating, just use any method in the OP. I personally prefer to dirty flash the factory image because the OTA method seems to give some folks problems.
[Google Pixel 6 Pro] foobar66:
Thanks for the reply. It did work...for a few seconds. I cleared cache/data, reboot, signed into teams, got the main screen. Then about 5 seconds later I get the message that my device is rooted (both intune and teams have all services in the denylist).
[Google Pixel 6 Pro] Nergal di Cuthah:
Did you try renaming (hide) majisk before signing in to teams
[Google Pixel 6 Pro] foobar66:
Yes I do that always (one of my Banking apps checks for the Magisk package name). Thanks.
[Google Pixel 6 Pro] 93fuelslut:
You mean fastboot the boot, bootloader and radio img?
[Google Pixel 6 Pro] V0latyle:
4 pieces, actually.

First, extract and patch boot image.

Update bootloader (if newer version), reboot to bootloader

Update radio (if newer version), reboot to bootloader

Dirty flash (no wipe) factory image, reboot to bootloader

Flash patched boot image, boot to system.
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Lol sorry just being persistent to ensure that you get this thing fixed, try this, remove company portal and teams from deny list, delete data and cache from teams and company portal, force stop both apps, now go ahead and add just company portal (all modules) to Deny list, login to company portal, and add admin privileges and sign in to teams, phew, waiting for your confirmation
[Google Pixel 6 Pro] foobar66:
Thanks again. Unfortunately still no luck.
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Sorry, couldn't help. Have a good one.

PS: you could remove the attached device from company portal cos the certificate details are cached in and start all over again. If still no go, I rest my case lol
[Google Pixel 6 Pro] Dragon Kumera:
seems new pixel 6 pro beta update happened. Got a notification on my phone.
[Google Pixel 6 Pro] Lughnasadh:
It's for the QPR Beta 1.
[Google Pixel 6 Pro] Dragon Kumera:
what do you mean by qpr? I know it's a beta image from google but not sure what the abbreviations stand for.
[Google Pixel 6 Pro] Lughnasadh:
Quarterly Platform Releases. Good explanation here...

https://twitter.com/i/web/status/1501652625711931393
[Google Pixel 6 Pro] fil3s:
I don't want to risk doing an ota with root as others might feel the same.

Source

Google releases Android 12 QPR3 Beta 1 to start previewing June’s Pixel Feature Drop

Following the launch of Android 12L on Monday, Google today announced Android 12 QPR3 Beta 1 as part of a new, more frequent...

9to5google.com
[Google Pixel 6 Pro] fil3s:
I almost bricked my 6pro

I sideloaded the ota , tried to root and it bootlooped. I tried to flash the stock boot image again and was greeted with text in red writing

you're device is corrupt. It can not be trusted and may not work properly

I tried android flash tool, wouldn't connect , flash all.bat refused to flash

I tried to sideload the ota fresh again and root it by typing in terminal

fastboot boot <magiskboot.img>

But the magisk app 24.2 stable refused to initiate. No matter what I tried, the app would not launch and then delete itself , with a toast saying 'superuser rights denied' I tried canary, same result.

Finally I just flashed crdroid and couldn't be happier tbh.

This was with the recent March update for 12L beta
[Google Pixel 6 Pro] V0latyle:
You have to be in bootloader mode to flash.
[Google Pixel 6 Pro] fil3s:
Yes sir I tried fastboot
[Google Pixel 6 Pro] fil3s:
Wait a minute 🤔🤔 you mean one can not sideload the beta ota? 🤔
[Google Pixel 6 Pro] V0latyle:
The only beta I have experience with was the Android 12 Beta before the official release. Back then, a factory reset was required to root, but that also has a lot to do with Magisk needing some changes.
[Google Pixel 6 Pro] fil3s:
Yeah I'm a lil dubious of experiencing android beta. I'm loving crdroid too much 😁
[Google Pixel 6 Pro] Lughnasadh:
I had no problems rooting QPR Beta 1 (March) with Canary 24.201. Just patched the QPR boot image and fastboot flash boot <nameofpatchedbootimage>

I updated via flash-all but that shouldn't have made a difference in rooting.
[Google Pixel 6 Pro] pro_b:
I'm wondering if anyone can assist me too with what I may be doing wrong. I was on rooted 2nd Feb update. I let the 12L QPR3 install via over the air update (which made me lose root). I extracted the boot.img and patched with Magisk from my device then flashed it from my pc. Now my pixel will continue to bootloop. I have removed all magisk modules. If I flash the stock boot.img it'll boot back up. If I flash the magisk patched img it will loop. Is there a way to fix this without having to wipe everything?
[Google Pixel 6 Pro] Lughnasadh:
Just to be clear, you are using the boot image from 12L QPR3 to patch? Other than that, if you have removed all magisk mods beforehand, not sure why it isn't working. Maybe go into data/adb/modules to make sure all traces of your mods are removed. Did you also disable any Substratum overlays if you are using them?
[Google Pixel 6 Pro] pro_b:
Correct. I am using the boot image from the QPR3 to patch. Disclaimer though. I didn't remove any magisk stuff prior to installing the over air update (that was my fault for not knowing at the time). I did run the script (adb wait-for-device shell magisk --remove-modules) to remove everything though and it still will bootloop if I use a patched magisk boot.img.
[Google Pixel 6 Pro] V0latyle:
Maybe that's the whole problem - you're doing this on 12L. It's possible that Magisk may need additional updates to handle 12L properly. Has anyone been able to successfully root 12L with the current version of Magisk?

When Android 12 came out, Magisk 23 didn't properly patch the boot image; the workaround was the vbmeta issue. I would imagine that Magisk 24 should work just fine on the March update for the 6 / 6 Pro, but then again, it seems like Google has been tinkering with a lot of stuff under the hood....at first, Magisk 23015 worked on the November update, then the December update broke everything again because of fstab issues, which 23016 fixed.

I guess my point here is don't necessarily expect a new software flavor to work exactly the same way as everything else. Magisk hasn't caught up with 12L yet.
[Google Pixel 6 Pro] pro_b:
Actually, Magisk CAN properly patch 12L. I'm positive this will work if I wipe and install the QPR3 from scratch. However, I'm trying to avoid that since I have so many apps that I'd have to go through logging back in to again (a major headache).
[Google Pixel 6 Pro] V0latyle:
Do you know this for a fact? Have you looked at the image header before and after patching? There may also be new features introduced that throw a wrench into the mix. That's the point I've been trying to make. Magisk 23 worked fine on Android 10 and 11, but it didn't work on Android 12 because of the introduction of Boot Image Header version 4...until Canary 23016 included the necessary fixes.

Just because the image will boot and is rooted doesn't mean it's done properly.
[Google Pixel 6 Pro] pro_b:
Gotcha. Thanks for the info. Unfortunately, this still doesn't resolve my issue. I'll just try to wipe and install the QPR3 from the factory image. I'm sure that'll fix it. I do appreciate the assistance though.
[Google Pixel 6 Pro] Lughnasadh:
Magisk Canary 24201 & 24301, as well as Beta 24.2/.3 & Stable 24.3 work fine on Android 12L regular betas as well as the QPR3 Beta 1. Been using Magisk on both Android 12L Beta 3 and QPR3 Beta 1.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, you may have some stuff leftover that is causing this. One more thing to try is to boot into safe mode and then reboot. That will disable all your mods (in case something is still enabled for some reason). Then patch and flash and see if that works.
[Google Pixel 6 Pro] V0latyle:
I wouldn't commit to wiping just yet. Try sideloading the OTA, but don't flash the patched image until the device has booted and "settled" for a while.

Otherwise, I'd say try reflashing the factory image to both slots, but that probably won't fix the issue.

What causes a bootloop is usually either a kernel panic - the kernel encounters a fatal error and restarts; or, the system thinking the update failed following OTA. This usually happens if the reboot process is interrupted, or if something doesn't quite match what it's expecting to see after it reboots (this is called Rollback Protection).

For some reason the system tends to get this wrong with a patched boot image after OTA. I don't know of a way to manually "reset" the dm-verity mode so that it'll assume everything is good and boot up. The patched image isn't actually corrupted, and it can boot successfully - the issue is dm-verity just gets mad for some reason and stubbornly refuses to boot the patched image.

Note that dm-verity is bypassed when you live boot an image. So, if you reboot after automatic or sideload OTA without root, then live boot a patched image:

fastboot boot <patched boot image>

it should boot without any problems, with temporary root until a reboot.

More information about Verified Boot and verification errors
[Google Pixel 6 Pro] fil3s:
I softbricked after sideloading and using the boot image from the 12L factory image. I don't know if I did it right but I had major headache trying to fix it 😑

Edit: went back to stock stable.
[Google Pixel 6 Pro] spr33:
Hey all.

Finally got around to rooting my Pixel 6 Pro for V4A.

Bootloader unlocked just fine and the wipe happened too. However, after installing Magisk (canary) and downloading the Android 12L Factory Image (S3B1) and transferring the boot.img to the phone and attempting to patch it in Magisk failed.

Process error

Installation failed

The log isn't all too helpful but can post if necessary. Not sure what I'm doing wrong (if anything?) - I've been doing this since the OG G1 days.

Anyone know what I could be doing wrong/should try?

TIA!

Seems as though a reboot of the phone and retransferring the file has fixed this! Apologies, please ignore

I patched the file just fine, transferred it back to PC, renamed to 'master root.img', rebooted to bootloader and typed the command for it to fail. I've also rebooted into fastbootd where it also failed the flash

Bootloader error: FAILED (remote: partition (boot) not found)

Fastbootd error: FAILED (remote: No such file or directory)

Anyone got any clues?

Another edit:

Eventually got around to booting the patched boot image and patching using direct flashing in Magisk after it booted which has worked fine. Leaving this here for others if they see the same thing (nothing in OP mentions this).
[Google Pixel 6 Pro] fil3s:
I had to fastboot boot the magisk image then direct install. Fastboot flashing it didn't work for me
[Google Pixel 6 Pro] V0latyle:
Actually it does...this is the Live Boot method
[Google Pixel 6 Pro] spr33:
I was going from stock though.. so followed the guide from stock.
[Google Pixel 6 Pro] V0latyle:
If you're rooting for the first time, live booting is unnecessary and redundant. You should be able to flash the patched image.

You aren't the only one having trouble, especially on the Pixel 6 so don't feel bad
[Google Pixel 6 Pro] slogar25:
You can't have a space in your file name in fastboot(or really any Linux command). This is the reason for failure. Try using a dash or underscore in between 'master' and 'root' next time
[Google Pixel 6 Pro] spr33:
I named it masterroot.img ;) that wasn't the issue unfortunately.

Either way, I would have used " around it which would have also meant it being a non issue.
[Google Pixel 6 Pro] slogar25:
My bad. This confused me ;)
[Google Pixel 6 Pro] V0latyle:
For those of you having boot loops after updating, try disabling Magisk modules. You can do this through adb while booting the patched image (even if it bootloops)

adb wait-for-device shell magisk --remove-modules

Some updates break Magisk modules, so it's important to be aware of this. I personally only use Systemless Hosts, Universal SafetyNet Fix, and MagiskHide Props Config, and have never had issues with a bootloop after updating.

Speaking of which, those of you using any Magisk modules, please report which ones you're using and what you needed to disable to avoid a bootloop.
[Google Pixel 6 Pro] V0latyle:
For those of you running custom kernels: DO NOT attempt to update via OTA, and DO NOT try to reflash the custom kernel after OTA.

The best way to update while running a custom kernel is by dirty flashing the factory image. The OTA process checks to make sure the kernel matches the system; a custom kernel won't match, and you'll get the corrupted error.
[Google Pixel 6 Pro] tomahawk_k:
For some reason the pixel launcher keeps crashing when applying root after the most recent update. I revert back to the stock boot and I have no issue but as soon as I flash the patched img the error occurs.

I've tried clearing the storage and cache of Pixel Launcher but it didn't help

Edit: Fixed by reinstalling Quickswitch