yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] V0latyle:
That's the best way to do it - to patch the new boot image every time and flash that.

But to make things easier, you can live boot an older patched image, then in Magisk select Install > Direct Install, and Magisk will patch the new boot image that's already in /boot.

Pixel Flasher helps streamline everything and is a great tool but I'm trying to help explain how this works because knowing the "why" is very important even when you have tools that automate the process
[Google Pixel 6] Mepsipax:
Thanks. That's helpful. I will try out the live boot way when I get around to it.
[Google Pixel 6] V0latyle:
Whatever works for you. I use Pixel Flasher personally as it's pretty easy and intuitive
[Google Pixel 6] Mepsipax:
Hey, so I just tried the live boot way and failed. I did:

1. adb reboot bootloader

2. fastboot boot "master root.img" (my old boot.img)

3. Then the phone told me that it couldn't boot. I could either choose "Try again" or "wipe user data"

4. I chose "Try again" and it booted into system

5. Opened Magisk and selected Install.

6. "Direct install" was not an option. Only "Select file and patch"

So I stopped. I assume it's not possible to boot from my master root and it went back to the unrooted boot. I guess you advice now would be to try PixelFlasher, right?
[Google Pixel 6] badabing2003:
You would be able to boot from master boot if it is from a matching OS version, that should never be an issue.

But booting with an older boot, it's a different story.

Also make sure you are using Android Platform Tools 33.0.3 and not 34.x
[Google Pixel 6] Mepsipax:
Good to know, I need to upgrade the tools, then. I'll do that and try my luck with Pixel Flasher. My old boot.img is from version 230505.002, wich I guess is too old, it seems.
[Google Pixel 6] V0latyle:
Patch the new boot image manually and flash it. Sometimes system doesn't like the old image.
[Google Pixel 6] statuquo:
Hi all,

I'm currently using the august 2023 version, can I downgrade to a previous version, for example the april version, using the sideload method and without deleting the data?

Sorry for asking this stupid question...
[Google Pixel 6] V0latyle:
You cannot sideload older OTAs.

You can flash the April factory image.
[Google Pixel 6] statuquo:
Thanks for your answer.

What I read on the PF thread finally discouraged me from downgrading without wiping the data.

I don't think I'm going to downgrade, hoping that the next updates will fix my problems: phone overheating and proximity sensor not working. And I'm not even sure that the April version will fix them.
[Google Pixel 6] badabing2003:
Good idea,

Check your apps / modules, specially root apps, one of those could be the culprit.

I'm on August release and have no issues.

I did a quick test of redfin, I had perfectly bootable two slots on August release.

I flashed factory July on active slot and the device would get stuck in recovery mode and wouldn't boot.

PS: I didn't try sideloading July OTA after that error, I would assume it would have accepted the flashing considering that it was on July at that point, but I didn't try it, something that could be tried.
[Google Pixel 6] statuquo:
Yes thanks. I might have the same problem on P6 if I downgrade, so I won't.

The reason why the proximity sensor is not working could also be hardware related.
[Google Pixel 6] badabing2003:
I did quite a bit of testing, and no matter what I tried I couldn't downgrade from Aug 2023 release to July 2023 release on Redfin.

I tried many different approaches, OTA, Factory, various combinations of the two, Multiple tries, switching slots ...

None worked (did not attempt any wipe), I would always get the corrupt message and get stuck in recovery.

The good thing is that flashing Aug OTA again gets the phone operational and no wipe is required.
[Google Pixel 6] V0latyle:
Rollback protection working as intended.

If you were to wipe data, you'd be able to successfully boot.
[Google Pixel 6] r00tcracker:
Hey @V0latyle , quick question for Android 14 (October 2023).

Do we need to flash the bootloader to both slots like when we went from A12 to A13?

I will be using the flash-all.bat so the line should look like this.

"fastboot --slot all flash bootloader bootloader-etc-etc-etc.img"

Thanks in advance.
[Google Pixel 6] V0latyle:
I haven't heard of any anti-rollback incrementation since the August 2022 release so it shouldn't be necessary, but you certainly can just to be safe. I always flash to both slots on my Pixel 5 even though I don't need to.
[Google Pixel 6] lukypuie:
Have you been able to update LineageOS OTA's without losing gapps?

I have to double flash manually the NiKGAPPS full every time.

Otherwhise I get tons of crashes.
[Google Pixel 6] V0latyle:
That's a question for a LOS thread. This thread is only for the factory firmware.
[Google Pixel 6] gazdajezda:
It took me a while, but yesterday I done it. First i patch new (A13 boot image). Then i found out that Magisk somehow lost original image, so Magisk Un-install via swap images wasn't succesfull. So I flashed (old v. 12) factory image over (without -w) to get a proper (non-root) system back. Then I do 2 time OTA sideload and after that flash patched boot image. All ok, everything works flawlessly for now. Thanks!
[Google Pixel 6] badabing2003:
I don't think you need to flash old factory image.

With full OTA, you don't need to be on stock, that it's only necessary for incremental (delta) OTA.
[Google Pixel 6] gazdajezda:
Great to know. I was not sure if that works and files was still there on disk already, so just to be sure I flashed it. Is 14 also rootable and do same Safety Net solution works on it? Thankx
[Google Pixel 6] V0latyle:
The process for Android 14 is exactly the same, the only caveat is you must use at minimum Magisk 25.2; previous versions do not support Android 14.

As for SafetyNet, please see this post:

[INFO] Play Integrity API - replacement for SafetyNet

THIS IS NOT A SUPPORT THREAD. For questions and support regarding how to fix your Play Integrity verdicts, see the Play Integrity Fix thread. ⚠️BEFORE YOU ASK A QUESTION, READ THIS POST AND THE FAQ!⚠️ ****Update 12/11/23**** Google has been...

xdaforums.com

Once you've read and understood it, see this FAQ:

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com

Lastly, since you're upgrading from Android 12, make sure you read this:

PSA: Android 13 Bootloader Anti-Rollback

***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Pixel 6 devices, regardless of whether or not you're rooted! This does NOT affect other Pixel...

xdaforums.com

I highly recommend you flash the OTA twice before doing anything regarding root. If something goes wrong and you've only updated one slot, your device could brick.
[Google Pixel 6] gazdajezda:
V0latyle: thank you (as always). I updated Magisk to 27.0 yesterday. Will upgrade to last 13 first and then read all that and then upgrade to 14. I was perfectly happy with 12 until I get aware that my Toyota (car) BT problem is fixed in 13 (and it is, now all works perfectly). Otherwise I believe I would still use 12. Thanx again!
[Google Pixel 6] V0latyle:
No need. Just download the latest OTA and flash it twice. You don't have to upgrade to Android 13 first, you can go straight to the latest update.
[Google Pixel 6] gazdajezda:
Well, yesterday I flashed A13 (feb 2023) OTA 2 times, so I think I'm good regarding boot loader. Today will upgrade to last 13 ver. since (if I understand correctly) A14 needs other solution to spoof SN, PI system. I started reading thread you send about that and after few pages I realize that eventually we are f#%&d. So, since now literally everything works perfectly for me, I will stay for some time on this and rather get through those SN, PI threads. And yes: what a bull**** this "secure computing" is...

Regards!
[Google Pixel 6] V0latyle:
I'm on Android 14, using @osm0sis Play Integrity Fork, passing with a custom fingerprint. It's really not that hard. It makes no difference if you're on Android 12, 13, or 14. You might be passing SafetyNet but you're probably failing Play Integrity.
[Google Pixel 6] gazdajezda:
Yes, just like now. But in case of 14 I need to understand how to create / setup a proper pif file - since atm this is totaly new to me. On the other side I currently have fully working phone. Will switch to 14, definitely, but later - when I get familiar with all that cave eats. I'm lazy, I know :ROFLMAO:
[Google Pixel 6] V0latyle:
Again...You're going to know how to do this no matter what, because Play Integrity has already replaced SafetyNet, and it makes no difference what version of Android you are on, even if you don't update to Android 14.
[Google Pixel 6] gazdajezda:
I understand that. But funny, most of the time I have Google Play disabled (so there is no automatic app / Play subsystem updates). But all my banking / crypto apps working. How, if GPlay control that (PI token etc.)? But this is out of scope of that thread, so I will stop with that. Thank you for all!

Edit - I just find answer to my question: it seems that many apps only do the check once or once in a montnh due to heavy server usage and safetynet his default quota limit of 10,000 the month.
[Google Pixel 6] V0latyle:
My point was, if everything is working now, it should continue to work even if you update to Android 14. It's possible the apps you are using don't use Play Integrity.

As for default quotas, I believe most apps will check upon first launch, but I'm also not an app developer so I wouldn't be able to say.

Regardless, you -should- be able to update to Android 14 without breaking anything. Up to you, my friend.
[Google Pixel 6] gazdajezda:
Aha. So, if I upgrade straight to 14, my apps will work as they work atm with Universal SafetyNet fix 2.4.0 (Displax mod) I use now? If that is true, then I will go to 14 and slowly start to 'study' PIF material, heh.
[Google Pixel 6] V0latyle:
Right. The Displax mod works in much the same way the current fixes do - by "spoofing" properties from an older device build so that Play Integrity thinks it's running on an older device. This works regardless of the Android version you're running on. The build fingerprints Displax was using have long since been flagged for mismatch so they don't work for Play Integrity anymore. I would guess that if you were to check your Play Integrity verdicts, you are probably passing BASIC and failing DEVICE. The fact that your apps are still working tells me you probably aren't using any that depend on Play Integrity, like Google Wallet.

Just for the sake of argument, would you mind checking your verdicts and let me know what the outcome is?
[Google Pixel 6] gazdajezda:
Yes, exactly. Only BASIC and SN (which is now meaningless).

"Critical" app's i'm using are: N26, Revolut, Bitstamp and from our local bank. So far they all work. I would be very happy if that stays that way :)
[Google Pixel 6] V0latyle:
Right. Upgrading to Android 14 shouldn't make any difference, If your apps needed DEVICE_INTEGRITY they wouldn't work.

If you decide to upgrade and USNF MOD isn't working for you anymore, just reach out in the Play Integrity Fix thread and we'll help you out.
[Google Pixel 6] gazdajezda:
I will, definitely. So far all good!

Thank you, you really are THE MAN & XDA is phenomenal!
[Google Pixel 6] gazdajezda:
Yes, just like you said. There is no difference. I upgrade to latest Android now (A14 from 5.2.2024). All apps works. Now I need to correct PI to Device integrity. After long time I have a latest system on my P6 :cowboy:
[Google Pixel 6] V0latyle:
Awesome!

This is what I suggest for fixing DEVICE_INTEGRITY:

Use @osm0sis module https://github.com/osm0sis/PlayIntegrityFork

Use Pixel Flasher to find a random print:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

Basic instructions:

Install Play Integrity Fork in Magisk, allow reboot

Connect phone to PC and open latest Pixel Flasher

Make sure it detects your phone, then click PIF Manager button

Click Get Random PIF

Output section will populate with PIF values

Click Smart Paste

this copies the Output section into "Active PIF" with tweaks if necessary

Click Update PIF.json

this pushes the PIF to your device and automatically kills Droidguard (the process that performs integrity checks)

Check your Play Integrity verdicts. If you only pass BASIC, go back to step 4 and keep trying until you find one that passes BASIC and DEVICE.

The Xiaomi PIF is currently working, but since it is being shared by many people, it will probably get broken soon. It is better to find a random PIF.

I already have a working PIF that I found, but just so that I practice what I preach, I just found a working print using this method after about 12 tries.
[Google Pixel 6] gazdajezda:
Will try & post results (tommorow).
[Google Pixel 6] V0latyle:
Please post your results in this thread as it is the main PIF discussion:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Google Pixel 6] JEANRIVERA:
on step 4 "Get Random PIF" the app does nothing I get no output after multiple clicks
[Google Pixel 6] V0latyle:
I don't think it works anymore because the library it pulled from is gone. All the prints got burned anyway so they're useless.

Best you can do is just use the latest Play Integrity Fix.
[Google Pixel 6] Sk007777:
hi

i cant unlock oem using the ui - im stuck in between recovery mode and fastboot mode

I have even tried

fastboot flashing unlock

Fastboot OEM unlock

This is the error is get

FAILED (remote: 'flashing unlock is not allowed')

fastboot: error: Command failed

please help
[Google Pixel 6] V0latyle:
The OEM Unlocking toggle in Developer Options cannot be bypassed. It controls the property get_unlock_ability value; 0 means "off" and prohibits bootloader unlocking while 1 is "on" and allows bootloader unlocking. Think of it like a safety.

Since you are able to boot into recovery mode, try sideloading the OTA. See OP for instructions.
[Google Pixel 6] userwaldo:
I have confirmed that these instructions also work on the Pixel 6a. You obviously need to make sure to use the Pixel 6a images.
[Google Pixel 6] V0latyle:
Yes, the instructions are the same for all Pixels, the only exception being the Pixel 7 and up require patching init_boot
[Google Pixel 6] ibex333:
I followed the guide to the dot, and yet in the end it tells me that it couldn't boot the phone and gives me an option to restore to factory.
[Google Pixel 6] V0latyle:
Can you clarify? Picture of the screen or something? I suspect you made a mistake somewhere.

Some information gathering:

How up to date is your Pixel 6? Did you update to the latest build?

What version of Magisk are you using, and where did you download it from?

What process did you follow to root the device?

What was the last thing you did before the device failed to boot?
[Google Pixel 6] rbouza1:
Yeah thanks for responding. The boot goes thru successfully. It's patched with that canary with fstab fix. Just won't complete the boot. Maybe I'll try flashing the boot instead of live boot. I didn't check anything when I flashed with Android tool, so maybe I'll try a factory install
[Google Pixel 6] V0latyle:
Android Flash Tool flashes the factory image; the only difference between using the tool vs using ADB commands (or the flash-all script) is that it's a web GUI interface. That's literally the only difference.

Yeah, flash the patched boot image to both boot slots and see what happens. It's working for almost everyone else so it's odd you're having an issue.
[Google Pixel 6] rbouza1:
What's the slot all cmd ?
[Google Pixel 6] V0latyle:
fastboot flash boot --slot=all <drag and drop patched boot image here>
[Google Pixel 6] GuinnessX:
I bought my Pixel 6 from the legacy Sprint part of T-Mobile and had to wait 40 days to unlock the eSIM. Just did that dove too quickly into this process, in my desperation to finally root... I downloaded the wrong factory image, so I ended up patching and flashing a mismatched boot.img. When I realized my error, I assumed I should be able to extract the correct boot.img from the factory image with bootloader and baseband versions that match my device's fastboot screen (oriole-sd1a.210817.036-factory-297ee25a.zip) and flash it back to normal, but my phone still throws a corrupt warning, then just sits with the Google logo forever... What can I do to recover and start again?
[Google Pixel 6] rbouza1:
I have magisk in my ramdisk from when I had it hidden. Thing is I couldn't uninstall from magisk because it wasnt working. Hm what to do. Seems like I need to reset
[Google Pixel 6] Slim2none4u:
If you have flashed the proper firmware. At the warning screen select factory reset.
[Google Pixel 6] V0latyle:
Have you removed all Magisk apps from your phone, including the one that was hidden?

Magisk reports Installed: N/A, Ramdisk: Yes?

If you have already removed Magisk completely, but Magisk 23016 says "N/A for installed, then yes you will most likely need to wipe data.

If your bootloader is unlocked, you can try using the Android Flash Tool to dirty flash the latest firmware - do not check any of the boxes. If you still get a corrupt warning after that, you probably need to wipe data.
[Google Pixel 6] rbouza1:
I've flashed several builds over this. And yes magisk says that , I'll bite the bullet and just wipe data
[Google Pixel 6] V0latyle:
Sorry man, I wish I had a better answer for you.
[Google Pixel 6] rbouza1:
It's like I'm flashing wrong boot, but I've triple checked. I did update from Nov to latest Dec build also
[Google Pixel 6] V0latyle:
Re-download the factory image and try again. It's easy to get the files mixed up.

What I usually do is extract the factory image, then keep that folder open in a window while I'm working. I just drag and drop into the command line.
[Google Pixel 6] rbouza1:
I got it after a wipe. I appreciate the help, been using adb since geesh htc m7 days and never like boot imgs. Something strange happened this time idk.
[Google Pixel 6] V0latyle:
Make sure your Platform Tools are up to date. Latest version is 31.0.3, Aug '21.
[Google Pixel 6] lame.exe:
Thanks for your work to keep the how to updated, unfortunately I'm still confused about the update process from November to December release.

I'm currently running SD1A.210817.037 with Magisk Canary 23015 and I want to Update to December Release and keep root.

Do I have to install Canary 23016 first and then create the so called "master root image" or should I patch the bootloader with my current Canary 23015 and then follow your steps?

Thx
[Google Pixel 6] V0latyle:
I would do the second option.

Update Magisk to 23016

Download and extract the December update

Patch the boot image; save this as a "master" for future use

Install the December update

Flash the patched boot image

Reboot to system, you should boot into December release with root.

For future updates:

Install the update

Reboot to bootloader and boot the "master" patched image (don't flash it)

Perform Direct Install in Magisk

Reboot
[Google Pixel 6] lame.exe:
Thx for reply, but I'm still not sure about the steps.

I just updated the 23016 "App" , but "Magisk" still shows 23015. Should I also update "Magisk" or will it break root?
[Google Pixel 6] Slim2none4u:
yes
[Google Pixel 6] t-ryder:
Now @lame.exe you decide... either "yes, you should update" or "yes, it will break root".
[Google Pixel 6] lame.exe:
What is your choice?

Still wondering about the meaning of the "Magisk" version. Is that the version of the current bootloader that was patched with Canary 23015? I would suggest to add these steps to the first post to make it more clear for everyone else who needs a cook book like I do :)
[Google Pixel 6] mic3r:
I'm in exactly the same situation like you, now about to update from Oct to Dec image. I just updated Magisk from 23014 to 23016 and rebooted, root is not broken.
[Google Pixel 6] lame.exe:
I justed patched the boot.img from december factory image and the result is "magisk_patched-23016_xELJv.img".

Therefore I will proceed as follows:

- Install december update with OTA sideload

- Flash the "magisk_patched-23016_xELJv.img" via fastboot

- Reboot to system
[Google Pixel 6] mic3r:
I did the same, following steps in the first post "Update and Root OTA Sideload".

Booting `fastboot boot magisk_patched-23016` didn't work for me. I patched the boot.img again just to be sure and flashed it via `fastboot flash boot xxx`. Now I have root and all seems to be fine.
[Google Pixel 6] lame.exe:
For me it was the other way round, I had to boot the patched Bootloader via fastboot and then I had to install Magisk with direct installation as described in the first post.

Reason was because fastboot flashed the bootloader to slot a, but the phone booted afterwards to slot b for any reason...
[Google Pixel 6] V0latyle:
Bootloader = / = boot image. The two are distinct and should not be confused.

As for Magisk...

The top part is the version of the boot image patch.

The bottom part is the app.

When there is an update, you update the app first, then you update the patch - tap Install, then Direct Install.
[Google Pixel 6] lame.exe:
Thank you for the explanation, I just googled that the boot.img contains the kernel and ramdisk which makes sense.

Do you think it is worth it to add those detailed steps about app update first, then patching the boot.img to your first post?
[Google Pixel 6] jenneh:
"""Bootloader = / = boot image. The two are distinct and should not be confused."""""

This is useful knowledge early on haha, i wish i had properly Understood.. very happy to follow this mod, they provide A LOT of useful knowledge~!
[Google Pixel 6] V0latyle:
I generally write my guides for somewhat experienced users, as I like to keep things short and sweet, but I may include some of these concerns as points of note so as to help prevent new users from making mistakes.
[Google Pixel 6] acefan:
Currently I have the November update and Magisk 23015 installed.

Is it 'safe' to dirty flash the Dezember patch?

Which method from the original post should I use for this?
[Google Pixel 6] t-ryder:
You could update to Magisk 23016 canary first (app and boot.img installation), download the factory image package, Magisk patch the new Dec. '21 boot.img with 23016 and use my updater from post #101 ... it's pretty convenient and easy to use. It's safe and the Dec. '21 update fixes like hundred of bugs and stuff.
[Google Pixel 6] V0latyle:
Start by updating Magisk. You can do this from within the app.

As for updating, you can do this any way you want. Yes, you can dirty flash the December factory image. Make sure you extract and patch the boot image after updating Magisk.
[Google Pixel 6] acefan:
Thanks for your replies.

I tried the method from post #101, but I missed to copy the image.zip to the folder.

Bootloader and radio were updated as intended and also the patched boot image was applied.

After that, the phone was stuck at the Google Logo loading screen.

I managed to get into fastboot mode again and flashed the new image.zip manually.

The phone then booted normally, but the root is gone now.

Unfortunately the 0riole-Flasher_v2 cleans up all the files, including my previously Magisk patched boot image.

What should I do now to re-gain root?

Patch boot image again in Magisk and flash? Or will this cause a need to wipe all data?

Edit: I do still have the magisk_patched.img from the november release if this is of any help here.