yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] gazdajezda:
Yes, it boots. First Bootloader unlocked warning, then normal Google logo then animation and after that shows G colored in purple, gray, light blue and dark grey combination. After a while screen went black and only long press works (shows those three options). There is something that system is not satisfied with it. Maybe too old Android, don't know.

Ok, when I will be at my comp, I will first flash stock boot image and hope for success.

If not, then dirty flash and if that also would not help, wipe will come to play (:sad).

And when I will doing that, just a question: is latest A13 rootable (Magisk)? Are there any problems with it? I just need to rooting it with Magisk with SN pass addon and for ad removal (AdAway).

Uff, Google Authenticator... I hope I will restore it...
[Google Pixel 6] V0latyle:
Considering it is booting, I think your chances of recovery are quite good. Start with the command I recommended; this will tell Magisk to disable any modules during boot, so if one of those is causing the problem, that should help.

Yes, Android 13 is rootable. Just make sure you use Magisk v24 or newer, latest 25.2 recommended.

SafetyNet has been replaced by Play Integrity, so you need to address whether your device passes Play Integrity attestation. It is possible to pass SafetyNet but fail Play Integrity. Most apps that require security guarantees such as banking/DRM have already switched to the Play Integrity API. I have provided more information in the OP.
[Google Pixel 6] gazdajezda:
Just to be sure, for flashing boot.img from current state I need to do:

connect phone with PC

then one of this:

start phone in Fastboot mode (PWR + vol. down) or select (with vol. keys) "Restart Bootloader" and confirm with PWRB?)?

or

on computer execute: fastboot reboot-bootloader (is this same as selecting it with vol. keys?)

Don't know why, but I think all that is same?

Then for ROM patching:

flash-all.bat (without -w for dirty and with it for real wipe)

or below command to only flash boot image:

fastboot flash boot <boot.img>

Really sorry for bothering, but I simpl forgot all those right steps, it's been a while when I last time doing it (half a year ago), just don't wanna get bricked device :)
[Google Pixel 6] gazdajezda:
I will and sincerelly hope so.

Ok, so Play Integrity is not beatable at the moment (i will read OP, not need to answer).

I will try today and will get back to report. Just need to clarify with commands I will need.
[Google Pixel 6] V0latyle:
You need to be in bootloader mode. How you get there doesn't matter.

I'm probably splitting hairs here...but "patching" means to update existing code with a bit of new code, like "patching fabric", so to refer to dirty flashing as patching is incorrect. Dirty flashing in this regard means we are rewriting the OS binaries to the device, without wiping user data (which would be a "clean" flash)

No worries. The only way you'll brick your device is if you screw up the bootloader.

Since this is a Pixel 6, I highly recommend you click the warning at the top of the OP and read. As this is your first time updating to Android 13, it is important you update both bootloader slots at the same time.

Also, be aware that there is no easy way to return to Android 12, as the new bootloader prevents downgrading. So, if you aren't absolutely sure you want to update to 13, don't.
[Google Pixel 6] gazdajezda:
Yes, my mistake. Don't know why i wrote "patching", it is "flashing". I know the difference :)

I will stay on 12 for now. Also, will return in few hours, hopefully with smile on my face :)

And, thank you!!!
[Google Pixel 6] gazdajezda:
Hi!

I tried to flash a patched boot.img, no sucess, same. Then with official boot.img, same. Also tried to disable Magisk modules, but ADB said device unknown or unpaired, so no go... Just finishing the dirty flash of my current system (oriole-sq3a.220605.009.b1), same. So only way for device to start working again is wipe... so let's go with that... Eh Gugl, damn you.
[Google Pixel 6] V0latyle:
What happened when you tried to flash the boot image? Copy and paste the output here, or take a photo. Make sure you're using the correct firmware - "oriole" for Pixel 6.

You could also use Pixel Flasher to make this a bit easier.
[Google Pixel 6] V0latyle:
Not really, other than the new Magisk fix. Can you confirm you have working root?

So from here on, you can update and root normally, and shouldn't have to worry about verity/verification.
[Google Pixel 6] pa.pn2:
Yes i have working root, i realy appreciate your help, realy glad that i dont have to start from scratch lol
[Google Pixel 6] V0latyle:
Glad to hear!
[Google Pixel 6] phaino00:
I updated magisk on .37.

Downloaded factory image.

Edited flash all file by deleting '-w' and replacing with '--disable-verity --disable-verification'

Flashed the .17 image.

Reboot to patch boot image in updated magisk (23016)

Reboot bootloader

Flashed patched image

Reboot system

Installed Raviole 1.4 kernel via FKM

All good. Looking forward to see the results on battery.

Took about 10 to 15 minutes. Wish I knew about the change to disabling verity and verification, might have saved some time.
[Google Pixel 6] V0latyle:
Disabling verity and verification is no longer necessary with Canary 23016.
[Google Pixel 6] phaino00:
I was reading that after I updated magisk and the firmware this morning. Should have read the forum first...🤦‍♂️
[Google Pixel 6] AethyrB:
I'm not sure what's going on. I was successfully rooted on the mid-Nov version (non-pro 6 to be clear), did the zygdisk/safety-net 2.2.0 (as seen in the pro 6 thread) and magisk hide. Adaway & tasker are my only 2 root apps. Now, to update, I did the recommended path in the first post, using the android flash tool from Chrome.

The selected build: SQ1D.211205.016.A1 (7957957)oriole-user (signed)12.0.0 (Android 12)API level 31Dec 2021 Security PatchDisable Verity, Disable Verification).

Downloaded, extracted each zip, and copied the boot.img from the dec oriole factory zip (yes, I checked the SHA256 hash, it matches the Dec 016.A1 hash).

Downloaded the latest canary magisk.

Uninstalled old version, reinstalled new magisk. Latest and installed both show 92546e8a (23016). Latest has a (23) at the end where installed doesnt. Doing the "install" doesn't seem to change this. Yes, it is pointed to the canary update channel.

Installed magisk by selecting the boot.img.

Copied the new magisk_patched-23016_2IyG2.img to my computer.

Rebooted to bootloader.

Run the fastboot flash boot --slot=all C:\adb\magisk_patched-23016_2IyG2.img

It shows Sending/Writing to both A & B slots.

Select "Start" in the bootloader to boot normally.

Rebooted a couple times just in case.

About Phone shows the newer .016.A1 patch level. Now magisk shows it can't get superuser, only giving me the option to install magisk or the app, just as if I was still unrooted.

Now the funny twist. AdAway shows it was granted superuser when I open it. I was able to update to the latest sources. Is the original root still working somewhere? If so, how do I point magisk to the functional version?
[Google Pixel 6] V0latyle:
If you were using Magisk Canary before, just update - no uninstall necessary.

If you were using the special release for the P6, then yes.

You did update Magisk before updating?

It shouldn't get stuck on "sending" when flashing boot, you should get a successful message. Make sure your PC configuration is good, including ensuring that ADB binaries (platform tools) is up to date.
[Google Pixel 6] AethyrB:
I had downloaded the new version instead of the update. Should work the same?

I think I did the uninstall/reinstall after I was on the new Dec patch.

It didn't get stuck on sending. This is what I get:

C:\adb>fastboot flash boot --slot=all C:\adb\magisk_patched-23016_2IyG2.img

Sending 'boot_a' (65536 KB) OKAY [ 1.608s]

Writing 'boot_a' OKAY [ 0.079s]

Sending 'boot_b' (65536 KB) OKAY [ 1.592s]

Writing 'boot_b' OKAY [ 0.078s]

Finished. Total time: 3.720s

It then boots up fine afterwords.
[Google Pixel 6] V0latyle:
Yes and no. If you're simply updating Magisk, you can either do so through the app, or install the new APK as an update.

If you're changing versions (stable to beta, beta to canary, special Pixel 6 fix to canary) you have to first use Complete Uninstall in Magisk to clean everything up. Once it's cleaned up and the phone reboots with everything restored to stock, you can install the new APK.

At what point did you patch the boot image? Before or after updating Magisk?

Hmm. There's an issue where Magisk sometimes loses its interface with root. I wish I had a better answer but there's no way to fix this without functioning root, other than wiping /data and starting over.

Since the boot image is already rooted, you'd just have to wipe data, set up your device, and install Magisk.

You could try uninstalling Magisk, then re installing the version you were using before.
[Google Pixel 6] AethyrB:
I patched the boot.img after the uninstall/reinstall of the newer magisk. I also have tried re-downloading/installing the newer magisk version and re-patching. Same thing.
[Google Pixel 6] V0latyle:
Uninstall Magisk and re install the version you were using before.

If that doesn't work, you're going to have to wipe data.
[Google Pixel 6] vandyman:
Did you originally have Magisk hidden?

Under a different name.

If so that could be the issue.
[Google Pixel 6] AethyrB:
Yes, I had it hidden. I don't have the original .apk available to me right now. I might have it saved on my home laptop.
[Google Pixel 6] AethyrB:
That actually reminded me to go see if the hidden /renamed version was still around. It was, updated it to the new version of magisk, and that worked. YASNAC showing it passed safetynet as well.
[Google Pixel 6] V0latyle:
Good stuff. I keep forgetting about hiding the Magisk app. I'll keep that in my brain box for the next time I see that question. Thank you!
[Google Pixel 6] AethyrB:
That's one of the problems with writing any kind of guide. Since there is many ways to skin a cat, it's hard to cover all scenarios. It's been a long time since I've played with root, so it didn't occur to me that I needed to update magisk before flashing.
[Google Pixel 6] c19932:
Hello,

My p6 is currently on Nov update, magisk alpha 23016. In order to update to dec update without wiping data, do I still need to disable verity and berification? I understand that messing with vbmeta is no longer necessary n

I'm asking because under OP's update method with factory image, the command is still

fastboot update --disable-verity --disable-verification image-codename-buildnumber.zip
[Google Pixel 6] chuppito:
I was able to update via the Flash tool. I still check Disable Verity and Disable Verification. Root successfully. The only problem is that it's long, I hope the OTA update will work again to save time
[Google Pixel 6] vandyman:
^^^^^^What does post #85 say?
[Google Pixel 6] gazdajezda:
Boot images were flashed ok, but after reboot it was same. Loading and black screen. I dont have a photo (only this on nonworking Pixel). Firmware is correct, at least checksum said so (i have a bakup of my phone on other disk and there was original boot.img and patched one, so I can check them with original one). Now P6 is start working, blank. So I need to setup all over again... First I will root it and then further.

About flasher: maybe next time, now it's over... phone is empty.
[Google Pixel 6] V0latyle:
Okay, so you went ahead with the data wipe. Is it at least working now? If it is, I have no idea why it wouldn't have worked with the unpatched boot image. Maybe something else got screwed up.
[Google Pixel 6] r00tcracker:
I know this is maybe a bit out of topic, but anyone updated to December image encountered any issues?? lost root, safetynet not passing, etc??

Just want to know before I jump the gun :)

Thanks
[Google Pixel 6] V0latyle:
SafetyNet has been replaced by Play Integrity. Please see the note in the OP.

How did you update?
[Google Pixel 6] r00tcracker:
Yeah, sorry my bad, wanted to say Play integrity :)
[Google Pixel 6] gazdajezda:
Yes, after wipe it work. I had a little mess with Swift Backup but now it's all ok. I lost my 2F seeds in Google Authenticator, but the rest seems ok.

Don't know why that happenede, i suspect an almost 4 months uptime and maybe there is some memory leak and after while strange things could happen. My opinion.
[Google Pixel 6] gazdajezda:
I will stay on 12. It works ok, also all banking apps, so I do not want to try to lose that. Also, do not wanna go to non-rooted rom never again.
[Google Pixel 6] gazdajezda:
How can I prevent automatic updates? Or at least prevent those notifications to pop-up... Thank you.
[Google Pixel 6] V0latyle:
Android 13 is rootable, and I'm using banking apps without a problem...

I'm not sure it is possible.
[Google Pixel 6] gazdajezda:
Great!

I found a solution (on Reddit), you just need to uncheck "System Update" notification of Google Play Services and this nag dissapear:

https://www.reddit.com/r/androidroot/comments/el1053
[Google Pixel 6] V0latyle:
Nice. I figured it would fall under the system notification category. Make sure you disable automatic system updates in Developer Options.
[Google Pixel 6] r00tcracker:
V0latyle, are you on the december update and with no issues with passing intregrity??

Also, if I am already on 13 (I'm on october release), do I have to flash the bootloader to both slots again, or I just can flash normally.

I'm editing the batch file.

Thanks
[Google Pixel 6] V0latyle:
I use a Pixel 5, but yes:

You can flash normally. It's only necessary to update both bootloader slots when you initially update to Android 13 on the Tensor devices.
[Google Pixel 6] r00tcracker:
Perfect!!! Thank you!!!
[Google Pixel 6] newkpt:
Hi!

I'm on oriole.t2b1.221118.006, and I've never rooted my phone before. I've been on the beta since the begining so I've made a few OTA updates.

I've followed the steps on the first post (unlock bootloader, patched the boot.img) and the output from "fastboot flash boot "master root.img"" is:

Sending 'boot_b' (65536 KB) OKAY [ 1.593s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 1.937s

On the magisk app (v.25.2), the "installed" stays "N/A".

Installed: N/A
Zygisk: No
Ramdisk: Yes

I've sideloaded the same OTA version that I'm on, repeated the flash boot, same result.

I've sideloaded the full factory image of the same version and the result is still the same.

I've also tried to boot and boot_b having the same result.

Am I missing something? What can I try next?

ty
[Google Pixel 6] Lughnasadh:
For now, you need to patch the Pixel 7 boot image and flash that patched image on your Pixel 6 to obtain root when running QPR2 Beta 1. John Wu is looking into why patching and flashing the Pixel 6 boot image on QPR2 Beta 1 isn't working to root Pixel 6 series' devices.
[Google Pixel 6] newkpt:
Couldn't find that information, thanks for sharing it worked!

Any known downside using the pixel7 instead of pixel6?
[Google Pixel 6] Lughnasadh:
I am unaware of any downsides at the moment.
[Google Pixel 6] gazdajezda:
Just week after wipe my phone get this notification. I'm sure that after install / reboot it will again go into that 'black' boot mode. Is there any way to prevent installing that updates? Automatic updates are disabled, what else I need to do to prevent updating the phone? Which apps need to be disabled? I just wanna have a rooted phone, that's all.
[Google Pixel 6] gazdajezda:
What should I do with that? Today instalation will be done, so shall I remove Magisk so instalation will proceed without error and later root again? Also, does that update mean that A13 will be installed? I know I'm bothering with that but this is so ofensive, I have unchecked updates installation and still is bothering with that...
[Google Pixel 6] V0latyle:
That's been a point of issue for a while now. I'm not sure how to completely disable updates.

You shouldn't have to remove Magisk completely, just Magisk > Uninstall > Restore Images. Then install the update, and when it's ready to reboot, Magisk > Install > Install to inactive slot.

What build are you currently on?
[Google Pixel 6] badabing2003:
I'm one of the lucky ones that never get these, however I read in another thread that if you freeze/disable the package responsible (I don't remember the name, sorry) then you don't get updates.

You can disable the notifications in Play services, but I'm afraid that just hides the notifications.
[Google Pixel 6] gazdajezda:
@V0latyle

June 2022 (see image). Deactivating Magisk, then doing OTA & after that installing to inactive slot was never succesfull for me in the past on P6. I can try again but Im almost sure that it wont work. Magisk is 25205, that procedure work with it? Also, this update is not to A13 or?

@badabing2003

Yes, but I don't know what I need to disable. That would be best solution, since I'm fully happy with phone and all. Those constant updating I'm not happy with.
[Google Pixel 6] V0latyle:
Yes, the latest update is to Android 13.

Because you have not updated yet, I actually would recommend you DO NOT try to patch the inactive slot, although it sounds like this hasn't worked anyway. We need to ensure you avoid a boot loop.

I would recommend you update via the factory image. Flash the new bootloader to both slots, flash the radio, then apply the update (doesn't have to be on both slots, just the active one). Manually patch the boot image (as in, extract it then patch in Magisk) and flash after the update.

Unfortunately this is the life of a Pixel user. Monthly updates will be part of the experience until such time as that device is no longer supported, generally after 3 years or so - the P6 and P6P will get Android version updates until Oct '24 and will continue to get security updates through Oct '26.
[Google Pixel 6] badabing2003:
I see the following package in the list

package:com.google.android.factoryota

Perhaps disabling that would do the trick.

adb shell pm uninstall -k --user 0 com.google.android.factoryota

Update:

Removed accidentally included package: part
[Google Pixel 6] gazdajezda:
So if I root A13, then banking apps (Revolut, N26, Coinbase, Binance, Bitstamp...) will stop working, since there will be play integrity?

Yes, that way never worked for me on my P6. Sadly, but true... On P2XL worked...

Does flashing work without -w parameter ? So I can retain my data partition intact?

Yes, but I wannt to have root and banking apps working (+ also other root apps of course - swift backup, power toggles widget, warden...).

If not else, I can install other ROM (Paranoid or smthng). I will miss Camera app but other apps will work, hopefully.
[Google Pixel 6] gazdajezda:
Unfortunatelly, does not do the trick:

e:\>adb shell pm uninstall -k --user 0 package:com.google.android.factoryota
Failure [not installed for 0]
e:\>

Grrr...

Can I run this somehow on phone directly? As root?
[Google Pixel 6] V0latyle:
Play Integrity is more or less independent of Android version. It was already on your phone and was included as part of a Google services update. You shouldn't need to worry about this - just use the USNF Displax mod and you'll be fine.

You aren't the only one, don't sweat it

Of course. Did you read the OP?

As I stated above, updating to Android 13 doesn't change anything in this regard. You're already on Play Integrity.

Yes, you'd just remove the "adb shell" part.

You can also elevate ADBD to root: adb root

This should restart adbd with root permissions
[Google Pixel 6] gazdajezda:
Doesn't work on the phone (image).

Ok, I believe you. Will flash latest A13 image (and say good bye to A12), I hope my apps will work. I have time till 22:00, around that time I get those update popups.

USNF Displax mod - this is Magisk module?
[Google Pixel 6] V0latyle:
What doesn't work on the phone?

Yes.
[Google Pixel 6] gazdajezda:
This:

pm uninstall -k --user 0 package:com.google.android.factoryota

I tried it as root, no success.

Yes, I read OP. Thanx.
[Google Pixel 6] gazdajezda:
Swift backup disable that package (seems so)... This is probably for downloading, in my case update is already on phone. Well see how will go.
[Google Pixel 6] badabing2003:
My bad, I updated my post above.

let us know if it works.
[Google Pixel 6] gazdajezda:
I manage to disable it with SwiftBackup. But now I enable it and try with your modified command, it returns "Success". So, your command work.
[Google Pixel 6] gazdajezda:
Well, yesterday popup about installing update appear and that was it. I reboot phone after that and still on same system. Will see how will that go further. Seems ok for now.
[Google Pixel 6] gazdajezda:
Aha, and I also disable (not uninstall yet) this one:

adb shell pm disable -k com.android.dynsystem

If naging will stop then this is it. Will report...
[Google Pixel 6] badabing2003:
If it is a system package, disable does not work. You have to use the uninstall command, which effectively disables it. It does not uninstall it.
[Google Pixel 6] gazdajezda:
Really? If I disable Play Store that way it's unavailable, non-working. And which command return / activate app back? If some troubles arise after 'uninstall'?

pm install -k com.android.dynsystem

?

Br
[Google Pixel 6] badabing2003:
If you used the disable command you'd use the enable command to enable it back.

If you used the uninstall command on a system package you'd use the install-existing command to enable it.

If you used the uninstall on a non system package, it's gone, uninstalled, you'd have to install it from apk again.
[Google Pixel 6] gazdajezda:
Thank you, really. I didn't know that.
[Google Pixel 6] kiwigi:
I have downloaded Factory images twice(from Google Server) and extracted the boot.img, patched it with Magisk-v25.1 , and then to find out when flashing for root an error :

the file has been transferred with adb push/pull.

Has anyone suggestions to overcome this hurdle?

Thanks
[Google Pixel 6] badabing2003:
Couldn't mount file?

That looks like a Windows dialog.

How are you even getting that? At what point are you getting that?

Why would Windows attempt to mount any file? Whatever that even means in this context.
[Google Pixel 6] V0latyle:
Yeah, @kiwigi you need to explain exactly what you're doing in detail, you're doing something wrong and we need to know what your process is
[Google Pixel 6] kiwigi:
Thanks @V0latyle and @badabing2003

Very much appreciated!

After extracting and patching the boot.img from the latest factory version twice, with following this guide, I suspected that I was doing something wrong. Possibly some wrong step with adb.

Consequently I thought that a dry run with the Pixel Flasher would not hurt and I tried it. Sure enough, all worked so I used Pixel Flasher to root.

Once more, thank you guys for making all this possible!
[Google Pixel 6] badabing2003:
Happy to learn that you're out of trouble now.

Although PF makes it easy for you, you really should understand how to do it manually, and where things went south, only then you would be able to get yourself out of trouble when thing go wrong.

In modding anything could go wrong anytime even to the most seasoned veterans, and understanding the mechanics (so to speak) is paramount.
[Google Pixel 6] kiwigi:
Thanks!

You are absolutely right what you are saying about learning the manual process. So I tried a couple of times, which isn't really a lot.

At some stage after searching the error(corrupt image error in adb) on the web some solution came up that the Android adb interface driver could possibly be missing. So I tried to install it, though the pc complained that it wasn't a 64 bit driver or something along these lines. Hence I moved to PF. No complaints during that procedure.
[Google Pixel 6] Thotho131097:
HI!

Kind of new :)

I've got 2 questions about this, I am using Pixel 6 - Paranoid Android ROM:

- Ive checked my bootloader version and A&B are both "slider-1.2-9152140"

Is this fine or should i change something?

- Will this rooting option and safetynet work with my installed rom?

If yes, will it clear my data (if successfull)?

Thanks!