yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] iwearthebelt:
So I can tell you that you don't need to do a factory reset in order to get root back. I've made a few errors myself as of lately including forgetting to unhide magisk. Can't remember specifically what I did but I did lose root and used Pixel Flasher to dirty flash the latest factory image over the current slot I was using and it worked flawlessly. It went right back to where I was prior to losing root, even kept all my modules enabled and my settings intact. So just patch the bootloader, flash the latest image (or whatever one you were using) and you should be good to go.
[Google Pixel 6 Pro] snovvman:
Thanks. I've tried everything, using Platform Tools 33.0.3:

Flashing patched boot using Magisk 25205 and 25206

Dirty flashed image and flashed patch boot

Fastboot boot <patched boot>

Nothing is working. When I boot with the patched boot, Direct Patch is not an option.

Any other ideas?

By the way, is the disable verity thing still a requirement? Previously, unless that was done before first boot after flashing and flashing patched boot, root is lost and factory reset is required.
[Google Pixel 6 Pro] Nergal di Cuthah:
That hasn't been needed since before 13. i think at most 6 months into P6/P6P release but don't quote that it may be way off but no that's not needed. Though that you asked makes me wonder if you're missing a step in the steps to root. Are you allowing the update to fully finish (boot phone fully up without root) then patch the boot.img in your downloads folder then fastboot flash the results of that. Those steps have proven successful for me.
[Google Pixel 6 Pro] iwearthebelt:
If it comes to not having any other options, before you decide to do a factory reset, give Badabing2003's Pixel Flasher a try. Just follow the instructions to use the program. Everything you need is available within the program, download the December release, patch boot.img with the latest magisk and flash it to the current slot that you were using I have a feeling this will bring you right back to where you were before you lost root. If you haven't already used it, I think you'll be pretty impressed with it.
[Google Pixel 6 Pro] snovvman:
Thanks. I too have read in many instructions where one should allow a full boot after flashing an update before flashing patched boot, but I never have. I have always immediately flashed the patched boot in bootloader after flash-all. It has worked for years among every phone I rooted. I did try what you suggested tonight but still got the same results--no root.

Thank you. I just tried Pixel Flasher. Very nice tool, but same result--no root after going through the process. I followed the directions, and still no joy. This is puzzling as I have never lost root before. I think something happened during the December update, I just don't know what. I have removed all traces of Magisk, including the hidden one, still nothing.

I'm hoping that someone has seen this problem before and can shed some light.

Edit please see my post below #1487 apparently the latest QPR was the issue.
[Google Pixel 6 Pro] snovvman:
@kip256 did you ever find a solution to your loss-of-root issue? I'm seeing the same thing and went through your same steps, but have yet to find a fix. Thanks.

Edit please see my post below #1487 apparently the latest QPR was the issue.
[Google Pixel 6 Pro] snovvman:
Thanks for this post. I followed the bread crumbs and solved my loss-of-root issue.
[Google Pixel 6 Pro] V0latyle:
Are you sure you don't have two instances of Magisk installed? If you've hidden Magisk, it's possible to install it again, and because of the security features in Magisk, only the original app gets root access. This is done to ensure that Magisk alone has the authority to grant root permissions.

No, this has not been required since Magisk 23016. It -may- be required with some custom kernels, but most of them either have patched vbmeta images you can flash, or have correctly updated their boot image headers.

Glad you got it fixed, might be a good reason to go back to Stable. I used to use Canary too, but decided that there wasn't really any point because I just want things to work, so I've been using Stable 25.2 on my P5 with no issues.

That's not to say there might still be issues with Tensor devices, though.
[Google Pixel 6 Pro] Lughnasadh:
Oh, you are on QPR2 Beta 1? Your original post said you were on "December's QPR" so I think people assumed you were on the stable December QPR1 build, not the beta build. If you are indeed on the QPR2 Beta 1 build, then yes, as of now, the QPR2 Beta 1 build on the Pixel 6 series needs a patched boot image from the Pixel 7 series. Clean flashing the QPR2 Beta 1 build and then patching the Pixel 6 boot image (instead of the Pixel 7 boot image) may prove successful as well. Magisk team is investigating the issue.

Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk

After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...

github.com
[Google Pixel 6 Pro] snovvman:
Thanks for this. I did see your earlier post about this and I eliminated that. Obviously, my issue was that strange December. QPR release.

This was lucky for me. Otherwise having lost root, I might have had to wipe!

There was a time when Canary was needed to get root with whatever the release of the time. I guess that's not the case any more. I will look into it. Thanks again!
[Google Pixel 6 Pro] snovvman:
Yea, sorry I was not clear. Before I first posted, I started reading around the August 2022 posts, but did not find a solution. I guess I should have read more recent posts (like we tell all the noobs lol). Losing root was not fun as many of my functions stopped working. This has been a good thread--people are helpful and knowledgeable, unlike some threads that tend to get toxic. Anyway, thanks to all the help. I am back with root!
[Google Pixel 6 Pro] V0latyle:
Yeah, that was Canary 23016 - 23010 was supposed to support Android 12, but the proper fixes weren't implemented until 23014; the Tensor specific fixes were committed in 23016. So, Stable 24.0 had everything necessary.

There's been a few more fixes along the way, so 25.2 should be sufficient, but there's some weird stuff with the beta that hasn't been figured out yet. I would suggest following the delta channel commits to see when the Tensor beta fix is implemented.
[Google Pixel 6 Pro] dyval:
Is this way of preserving root would work for future updates? Anyone using this method? Thanks

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.

Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update

Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.

You should now be updated with root.
[Google Pixel 6 Pro] V0latyle:
I believe it has been working, although I personally have never updated that way.

If it doesn't work properly, one of two things will happen:

It will boot, but you won't have root

It will bootloop back to the "old" slot, without root

In either case, you can easily regain root by reflashing a patched boot image.
[Google Pixel 6 Pro] dyval:
I appreciate your response brother. 👍🏻
[Google Pixel 6 Pro] dyval:
When you say bootloop back to the old slot that means I'll boot to the older build without root? Not endless bootloop? Thanks again.
[Google Pixel 6 Pro] V0latyle:
The way seamless updates are supposed to work, the update engine updates whatever the "other" slot is (inactive at the time), then once the write is successful, requests a reboot to that slot. If a boot failure occurs, the device will automatically recycle to the last known good configuration, which would be the "old" slot you're running on when you took the update.

If the boot process gets far enough before a kernel panic, it is possible for the device to get stuck in an endless bootloop. In this case, command boot to bootloader, and reflash the stock boot image.
[Google Pixel 6 Pro] silocybin:
My P6P doesn't get the OTA updates is it safe to sideload the update and just reroot?
[Google Pixel 6 Pro] Lughnasadh:
Yes. You can also use Android Flash Tool, Pixel Flasher, flash-all, etc. to update since your bootloader is unlocked.
[Google Pixel 6 Pro] silocybin:
i will look into pixel flasher it seems interesting thank you
[Google Pixel 6 Pro] snovvman:
Does the January QPR patch still have the boot issues like December?
[Google Pixel 6 Pro] Lughnasadh:
If you're asking if you need to use a patched Pixel Pro 7 boot image to root on QPR2 Beta 2.1, then yes.
[Google Pixel 6 Pro] snovvman:
Thank you for 1) clarifying my question and 2) answering my question. If I can hit like twice I would lol.

I guess I'll also download the P7P image and patch its boot for my P6P.
[Google Pixel 6 Pro] snovvman:
This is one of the best threads on XDA. Mostly because the people here are helpful, patient, and knowledgeable. I appreciate it.
[Google Pixel 6 Pro] Tombay1969:
Hi all, I installed the Bliss 16.3 yesterday, it is rooted with Magisk. Now I have an update available in System -Updater and wanted to install it with root. I am on Magisk Uninstall-Restore Image. Then I installed the update since it hasn't restarted yet, went to Magisk and click Install on inactive slot and click Let's go in the top right and the device reboots. When it starts, it doesn't install anything and where it has restarted, there is still a new update available under System Updater Bliss 16.3 from 01/14/2023. I've tried it 3 times today but the update is always there. What am I doing wrong? somehow the update doesn't seem to grab it.
[Google Pixel 6 Pro] V0latyle:
This thread is for the stock firmware, we do not provide support for custom ROMs
[Google Pixel 6 Pro] silocybin:
FAILED (remote: partition (boot) not found)

i get this error when trying to flash the patched boot.img
[Google Pixel 6 Pro] Nergal di Cuthah:
Can you show a screen shot of the command you are using? Are you using the recent version of adb that came out this week?
[Google Pixel 6 Pro] silocybin:
I figured it out but is there a fix for Play Protect Certification?
[Google Pixel 6 Pro] Lughnasadh:
It would be helpful to let others know what you did to fix your initial problem.

For certification, you can try this.
[Google Pixel 6 Pro] silocybin:
Right i have the safetynet fix installed but im still failing cts profile and google play store play protect certification is not certified
[Google Pixel 6 Pro] Nergal di Cuthah:
Do you have today's modded version of safetynetfix by displax
[Google Pixel 6 Pro] V0latyle:
If you're having issues with the Universal SafetyNet Fix module, please ask your questions in that thread:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823
[Google Pixel 6 Pro] silocybin:
it only let me download the kdragon fix not the modded version that you have?
[Google Pixel 6 Pro] Nergal di Cuthah:
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88132825

Edit right link now
[Google Pixel 6 Pro] MartinN6:
Link for safetynet-fix-v2.4.0-MOD_1.0.zip

(Hope it os ok to post the link)

Releases · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com
[Google Pixel 6 Pro] silocybin:
my issue is fixed sorry about that
[Google Pixel 6 Pro] MartinN6:
"safetynet-fix-v2.4.0-MOD_1.0.zip"

Works pretty good at my device
[Google Pixel 6 Pro] silocybin:
Thank you everyone for your patience
[Google Pixel 6 Pro] Nergal di Cuthah:
Yasnac is for depricated safety net you should check pi with something like integrity checker https://github.com/1nikolas/play-integrity-checker-app
[Google Pixel 6 Pro] Dragon Kumera:
So has anyone else had google pay just stop working one day? I havent been able to use it since a month now. Did everything I could think of. Did google change something?

Updated what I did the next post down.
[Google Pixel 6 Pro] Nergal di Cuthah:
That provides us with zero information. Please tell us what you've done
[Google Pixel 6 Pro] Dragon Kumera:
Very sorry. I meant to add that in the post but forgot. I will update soon. (if it helps December update for p6p worked fine but I updated to the February one and updated magisk and thats when the problem began).

I have saftey net fix 2.4 installed.

clear storage for google play services and google play store to get that check to pass after updating and re rooting. Google play is certified but it seems play services check is not passing.

I do have developer options enabled and debugging off so my banking app works.

I did the integrity api check and it reports the top and bottom as fails.

meets device integrity = fail

meet basic integrity = pass

meet strong integrity = fail

The other security check app said cts profile fail or something like that. Weird thing is on first boot of the app after a phone reboot it passes but then relaunching the app says it fails.
[Google Pixel 6 Pro] StanWiz:
There is a new saftey netfix( 2.4.0mod _1.2 I believe) - that should fix your problem.
[Google Pixel 6 Pro] V0latyle:
Questions regarding Play Integrity should be posted either here or here
[Google Pixel 6 Pro] Dragon Kumera:
Any chance you have a link? I just updated it last night.
[Google Pixel 6 Pro] Dragon Kumera:
Thank you. I just thought since I have a pixel 6 pro it was specific to that device.
[Google Pixel 6 Pro] dilligaf56:
This seems to work for me; I had the same problem after updating to the February firmware. After installing this module, it passes the needed two out of three Play Integrity checks. Still have to see if Google Pay works. Unfortunately Lookout still finds Magisk, even though it's "hidden"...I just ignore the warning, but it didn't find it before last month.

Here is the link to the updated module:

Release v2.4.0-MOD_1.2 · Displax/safetynet-fix

Changelog: v2.4.0-MOD_1.2 Fix crash and endless tests loop/failing on Android < 9.0 (bug from original version 2.4.0). Do not unpatch (revert) changes. To prevent possible tests failing after a wh...

github.com
[Google Pixel 6 Pro] darkness4every1:
Mine stopped working as well, can't make any contactless payments, can't add cards on my watch anymore.

I'm on latest Universal SafetyNet Fix 2.4.0 Mod 1.2, tried clearing cache/ data for play services, play store, wallet, wear os. Wallet is hidden in magisk.

Everything was fine before FEB update.
[Google Pixel 6 Pro] Dragon Kumera:
I just updated to the mod v1.2 was released recently and was able to finally setup google pay again. Will test it monday to see if it works. (pm me so we dont clutter chat here). I can help you fix it or attempt to after I test to make sure it does work.
[Google Pixel 6 Pro] V0latyle:
Any other mods?

I haven't had to use DenyList on any Google apps.

Stock fingerprint, USNF 2.4.0 Mod 1.2, DenyList only on non-Google apps. No issues on my Pixel 5
[Google Pixel 6 Pro] darkness4every1:
A lot of mods. After clearing cache/data I can add cards and stuff for a few minutes but then I get the "Something went wrong, try again later" error.

Before updating to 1.2 I'd get an error when trying to pay contactless, after 1.2 I'm getting no error (or something went wrong) but payment is being declined
[Google Pixel 6 Pro] V0latyle:
What other mods? Have you altered device fingerprint/profile in any way?

Please continue these questions here as this thread is only intended for issues with software updates
[Google Pixel 6 Pro] darkness4every1:
Haven't changed fingerprint, not using magisk props config.
[Google Pixel 6 Pro] V0latyle:
I suspect your xPosed/lSposed modules may be to blame but this isn't the place to ask...see my previous post
[Google Pixel 6 Pro] Dragon Kumera:
Tested google pay Monday and it worked fantastic. I am running stock though no other modules besides the ones required to get it working.
[Google Pixel 6 Pro] triggerhappy_:
Hey all! Tryna do the Feb update by following the steps "Update and Root Factory Image" but can't!

archive does not contain 'vendor_other.img'

Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

fastboot: error: Command failed

I've done this tons of times. What's wrong and what should I do?

p.s. platform tools and all drivers are up to date.
[Google Pixel 6 Pro] V0latyle:
Are you using the correct factory image for your device? It should have "raven" in the file name.

Also, Platform Tools 34.0.0 is known to have problems. Use 33.0.3
[Google Pixel 6 Pro] triggerhappy_:
Yeah, I definitely know what I'm doing. Installing 33.0.3 has completely resolved the problem. Thank you for help, you're the MVP.
[Google Pixel 6 Pro] Lughnasadh:
FYI, Platform Tools 34.0.1 still has the fastbootd problems as well so don't update to that.
[Google Pixel 6 Pro] ermintrude:
Installing the March update today via the factory image and fastboot (as I usually do) I found that patching and flashing boot.img as I usually do didn't work: it booted OK (albeit slower than usual), but no root.

I eventually realised that this is the release-candidate issue mentioned above, now affecting regular updates (so beware!)

After a lot of fruitless experimentation with Pixel 7 boot images etc (none of which worked), I discovered to my relief that the latest Alpha of the Magisk app does the trick fine (usual method: patch boot.img on the device and then boot from it or flash it with fastboot as normal.)

I hope this saves somebody a bit of time (and that it solves the problem for them too.)

Apparently it may not get fixed in Magisk proper, as the issue seems to be a screwup by Google.
[Google Pixel 6 Pro] digger16309:
Interesting but haven't seen that elsewhere (yet) and curious if this can be confirmed.
[Google Pixel 6 Pro] snovvman:
To what release-candidate issue are you referring? I was on QPR beta, and just flashed the March (release) update on P6P. Did my usual thing, patch the boot, flash-all, flash the patched boot, got root, no issues. I'm on Magisk 25210.

I have my own unrelated issue that I've seen in the past few months--after flash-all and flash patched boot, restart takes me to an corrupted image. To fix it, I simply re-flash again and everything works.

Add me to the list of those who DID NOT have the issue @ermintrude had.
[Google Pixel 6 Pro] ermintrude:
Not a release candidate at all, but the *regular* March update from Google's factory image site: it's

raven-tq2a.230305.008.e1-factory-def2deef.zip

What I was saying was not that I had installed a release candidate, but that I had run into the same problems with a regular update as those who *had* installed a release candidate.

It was posted on Google's site very late: only a day or so ago.
[Google Pixel 6 Pro] iwearthebelt:
This is the first time I've ever run into issues updating the monthly on my P6P, Part my fault because I forgot to unhide Magisk (although I didn't think this would cause issues as it hasn't in the past) but somehow I lost root. Not all that big of a deal as I uninstalled Magisk and patched the new update and that fixed the issue but for some strange unknown reason I'm now showing Magisk Delta (which is what I installed), but I'm also showing the icon for the hidden Magisk app which I uninstalled prior to re-rooting. I'm guessing that one of the files must have been left behind. Strangely, everything is working perfectly, Passes root check and integrity, all my modules are there and working as well. Seeing everything is working as it should and I'm not having any issues I'm just going to leave it as is. I think if I try to uninstall the old Magisk app it might take a file with it that shouldn't be uninstalled and I don't feel like doing a full wipe if I don't need to. Anyone else have an issue similar to this please let me know.
[Google Pixel 6 Pro] TheKum:
Following the OP Updated to Android 13 QPR3 beta T3B1.230224.005, lost root .

Tried several times with patching factory boot img without success.

Then I patched stock boot img from pixel 7 pro QPR3 beta, rooted without no problem.

Everything is working fine. Hope this helps.
[Google Pixel 6 Pro] digger16309:
Edit - Definitely a cable issue - apologize for multiple edited posts.

Device version-baseband is 'g5123b-107485-221101-B-9242015'.

Update requires 'g5123b-112825-230302-B-9675756'.
[Google Pixel 6 Pro] V0latyle:
Double check and make sure you're using the correct files for your device. Remember, Pixel 6 is oriole, 6 Pro is raven. Try a different USB cable. Make sure you're using a type A to type C cable, as C to C cables don't seem to work correctly.
[Google Pixel 6 Pro] digger16309:
I'm definitely using Raven. I don't know what to do. It's throwing an error looking for an updated radio I can't flash. -9675756.

I guess I could try updating OTA since I'm completely unrooted...
[Google Pixel 6 Pro] digger16309:
Thank you! This was it! I changed cables and ports on my PC.
[Google Pixel 6 Pro] V0latyle:
Just as a matter of information, if you wanted to force the system update to ignore the bootloader and radio versions, you'd use the --force flag: fastboot update --force image-device-buildnumber.zip
[Google Pixel 6 Pro] Annil:
For me update on latest march update is not going to sucess with Root unfortunately :(

Till now I was using Magisk Delta and used Pixelflasher - worked everytime like a charm.

Now after march update I lost root and am not able to regain it. I patched boot image with Delta Magisk but when booting (live or flash), root is not present.

When selecting Canary Build from Magisk, Pixelflasher is telling

WARNING! Problematic Magisk Manager Version: 981ccabb:25210 is installed. Advised not to use this version.

Anyone facing similar issues and is able to help to regain Root?

Edit:

There seems to be an issue between latest Magisk and March update...

I had to downgrade from 25210 to 25206 which works now flawlessly as usual.
[Google Pixel 6 Pro] pa.pn2:
Btw, how do I downgrade correctly?

I downloaded 25206, uninstalled the magisk 25210 version and installed the app-release.apk.

When I launch magisk, it prompts directly an update to 25210...
[Google Pixel 6 Pro] Annil:
I downgraded by renaming the lower version apk file to magisk.zip and installed this then as "new module install from zip file" in Magisk - this way always works for me easiest/fastest and is desribed in FAQ of Magisk.
[Google Pixel 6 Pro] StanWiz:
Good to know - I've always used the original C to C cable without issues. Guess it depends on the pc (my is fairly recent)
[Google Pixel 6 Pro] iwearthebelt:
I had the same exact problem, on delta and using PixelFlasher. After some trial and error I figured out how to get it back to where it was. It's actually really simple. Just uninstall any instance of the Magisk app you have installed, including any hidden magisk app you may have forgotten to unhide (uninstall them just like any other app by long pressing on the app and dragging it to the top where it says uninstall). Once you have all instances of the Magisk app uninstalled, just use PixelFlasher like you normally do. Download the March update, process and patch it, flash it and let PixelFlasher do it's thing. Thats it, you're back to where you were before you lost root except now you're on the March release. All your modules will still be there and enabled (just remember to keep data when flashing). Let me know how it goes.
[Google Pixel 6 Pro] dilligaf56:
Hmmm. I'm still on the February update, rooted, with Magisk 25210. Given the issues above, I'm wondering if I should just wait until the issue with Magisk is resolved before updating to March (or April, when it's available)...right now everything works fine other than some screen weirdness (flashing) after a day or so, which resolves after a reboot. Is there any pressing reason to update to March at this point?