yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] V0latyle:
If Pixel Flasher worked, that's not the problem because PF uses the same ADB tools and interfaces.

Questions about Paranoid ROM should be asked in the Paranoid ROM thread.

As for your bootloader version, I do not know off the top of my head what the Android 13 bootloader is. Since you're using a custom ROM this shouldn't be an issue.
[Google Pixel 6] badabing2003:
Perhaps it wasn't the drivers, but rather the Android Platform Tools.

When using PF, you select the directory where Android Platform Tools are installed and PF hard codes that full path in the generated flash_all script along with the selected device's ID, hence avoiding any potential of picking up any other Android Platform Tools in the system path.

It's not uncommon for people to have several old versions of adb lingering in their system and some unfortunately added to their system environment.

If it was a driver issue, you are absolutely correct, PF would have ran into the same issue.
[Google Pixel 6] devilsshadow:
Updated to the latest jan5 build using the factory image and pixel flasher. Everything went beyond smoothly (shoutout to badabing2003). Kept root, all my modules are there and working.Overall great. Only one thing I've run into that I have a question about:

Google wallet is now prompting me about detecting root. It only prompts me once in a while when entering the app. Now here's the thing: when I go to app>tap to pay setup, all the items on the list are checked, including the "your phone meets security requirements" part.

Now my question is, will this prompt disappear on its own? Is this a known thing? Anybody else run into this after updating? I tried clearing cache/appdata, but I'm still getting the prompt.

Using latest Magisk canary, zygisk, universal safetynet fix modded by displax, enforce deny list with google wallet and google play store on the deny list (as well as google play protect service).

I was on the october update prior to updating, with the same magisk setup and didn't have this issue back then. Any help or suggestions would be greatly appreciated, thanks!
[Google Pixel 6] V0latyle:
What does Integrity Checker or TB Checker say?
[Google Pixel 6] devilsshadow:
Good call, thanks, looks good i think:
[Google Pixel 6] V0latyle:
Yeah, everything looks good. Maybe clear data for Wallet? It won't remove your cards
[Google Pixel 6] HtcDesire2:
Did anyone get qpr2.1 OTA on rooted P6 with p7's patched boot.img?

I am still on qpr 2 and check for update is of no use.

Is this just me?
[Google Pixel 6] GrandAdmiral:
I'm going to give this a shot as mine literally stopped working yesterday without having any problems prior to then. I installed the latest security update a few days after it first became available.
[Google Pixel 6] Lughnasadh:
There are several reports of people having problems with Google Pay/Wallet in the last couple of days. If you are not using it, try Displax's mod.
[Google Pixel 6] GrandAdmiral:
Yeah, I've been running it.
[Google Pixel 6] V0latyle:
For those of us on the stock ROM, USNF 2.4.0 should work fine. Displax's mod changed fingerprints too, which shouldn't be necessary for those of us already on a valid fingerprint
[Google Pixel 6] Lughnasadh:
May have to clear Play Services and Play Store data as well Pay/Wallet.
[Google Pixel 6] Lughnasadh:
There have been several reports over the last couple of days that USNF 2.4.0 wasn't working for them anymore.
[Google Pixel 6] GrandAdmiral:
Can both mods be run simultaneously?

Or better yet, is it wise to do so?
[Google Pixel 6] Lughnasadh:
Don't do that.
[Google Pixel 6] GrandAdmiral:
Figured that was the answer.
[Google Pixel 6] V0latyle:
Yeah, only use one module of a type at a time. You can use USNF 2.4.0 with MHPC, although the latter is no longer being developed to my knowledge
[Google Pixel 6] GrandAdmiral:
Got Displax's mod working. USNF 2.4.0 is definitely broke right now unless you're using MHPC (didn't want to go that route since it's not supported anymore).

Now... do I want to update the latest GPay that just rolled out? :ROFLMAO:
[Google Pixel 6] V0latyle:
USNF 2.4.0 works for me on my Pixel 5.
[Google Pixel 6] badabing2003:
it works for me on p7p as well.

@GrandAdmiral definitely is the wrong adverb in this context.
[Google Pixel 6] Lughnasadh:
Seems to be an "intermittent" problem (within the last week) with USNF 2.4. Many people have reported that GPay/Wallet no longer works for them using USNF 2.4 and they had to revert to Displax's 2.3.1-MOD_2.1 to get it working again. On the other hand, others seem to have GPay/Wallet working just fine with 2.4.

Definitely is definitely the wrong adverb 🙃
[Google Pixel 6] V0latyle:
I think Wallet randomly stopped working for me but I had changed something in Magisk, so after enabling DenyList on all subprocesses of Wallet/GPay and clearing data on Wallet, it works fine.
[Google Pixel 6] GrandAdmiral:
I got it. I got it. Lol
[Google Pixel 6] phaino00:
I can say the lastest gpay update caused gpay not to work with USNF 2.4, at least for me. Reverted to Dispax's MOD 2.1 and cleared data of gpay app and gpay is working again.
[Google Pixel 6] r00tcracker:
Any issues updating to Feb image? Everything still working fine? Passing integrity, root etc?

@V0latyle I know you update your phone every month, do you think it would be a good idea to add to the OP something like "no issues reported, passing integrity, root, etc after (Month) update" ?
[Google Pixel 6] Graddy01:
I installed feb update yday but USNF 2.4.0 wasn't passing integrity anymore but there is 2.3.1 mod 3.0 fix already out which is working
[Google Pixel 6] V0latyle:
Who what? Huh?! I wasn't there that day, you can't prove anything....Oh.

Nah. The assumption should always be that things are working as they should, and whoever is reading the thread can take note of the last few posts at the end.

Completely unrelated: Magisk 25.2 works on the 14 Developer Preview...but Zygisk doesn't work for some reason
[Google Pixel 6] sadmansajid07:
is ota still coming while rooted? its not coming for me.
[Google Pixel 6] V0latyle:
Pretty common for OTAs to not work while rooted. Either use the factory method or sideload OTA
[Google Pixel 6] sadmansajid07:
okay. but they used to come before, is it not coming now? sideloading is the only way?
[Google Pixel 6] msaiko239:
I have not rooted an Android device in years so I apologize for the inexperience.

I have an unlocked Pixel 6

Android 13 Nov 2022 software release.

I have unlocked the boot loader, installed Magisk, patched the proper boot file, transferred it back to my pc and then ran `fastboot boot <imgname>.img`

my device loads and reboots on its own.

Once it reboots I go to Magisk and it is stil N/A so not rooted.

I am not sure what I might be missing I have checked a couple of guides and all have the same process.

Thank you for the help
[Google Pixel 6] V0latyle:
Something about the root patch seems to interfere with normal automatic OTAs. This happens to a lot of people. For some reason the system doesn't check for and download the update.

The update methods that work are described in the OP.

What version of Magisk are you using?

Try flashing the patched image to /boot.
[Google Pixel 6] msaiko239:
I am using the latest version of Magisk downloaded today.

I can try the boot dir
[Google Pixel 6] msaiko239:
I am assuming the command you are telling me to run is

fastboot flash boot <imagname>.img
[Google Pixel 6] msaiko239:
I have tried multiple version of Magisk now. 25.1 and 25.2

Here is the error I get when trying to flash

I downloaded the factory image of my Android release matching the build numbers from Nov 22.

Thanks
[Google Pixel 6] V0latyle:
Correct

What version of Platform Tools are you using?
[Google Pixel 6] msaiko239:
Platform tools are r33.0.3 on linux.
[Google Pixel 6] badabing2003:
Are you sure you are flashing a correct boot.img file?

Did Magisk patching work?

file size of 98304 does not sound right
[Google Pixel 6] V0latyle:
It does at least for the Pixel 5, I'm not sure what the boot image size for the P6 is
[Google Pixel 6] V0latyle:
Oh yep.

@msaiko239 You're using the wrong firmware. The firmware zip should have "oriole" in the filename.
[Google Pixel 6] msaiko239:
Yes, I should have caught that. What happened was I searched the build number and it matched on the wrong version...Thank you for the catch...
[Google Pixel 6] msaiko239:
Thanks @V0latyle and others, I am rooted. Now on to messing with 5G and ims settings.
[Google Pixel 6] iSupakilla:
Man, I've literally never struggled this much to root a phone before. Out the box, I was having issues with not being able to switch the device that was in control to my pc to allow me to transfer files (which im praying is the case cause i have a new USB-C 3.0 Cable coming just in case) I've done all the steps up to getting the bootloader unlocked and flashing then renaming the boot image but now no matter what I do in deleting, installing, or updating drivers. it wont detect my device while in fastboot mode to flash boot the img file.

I know this is a bit old but any help please?

Android 13.0.0 Slider-1.2-8895132
[Google Pixel 6] V0latyle:
Imgur makes it hard to see the images, you can just upload them directly to your post.

Make sure you're using an USB A to C cable. Don't use USB C to C.

You may be missing the fastboot driver. Get it here
[Google Pixel 6] iSupakilla:
Updated the image,

I did try a USB C to C cable to see but i've mainly been using the one that came with it in the box as well as one i already had and on all the USB ports i have. I have a 3.0 Cable coming in to see if that fixes anything

Unfortunately, I do have those drivers already installed prior to the process
[Google Pixel 6] V0latyle:
So it's not showing up under fastboot devices when in bootloader mode?
[Google Pixel 6] iSupakilla:
No, after it enters fastboot mode i get no connection to it through my PC whatsoever
[Google Pixel 6] V0latyle:
Sounds like a driver issue honestly. Check device manager when in bootloader mode and see if your computer recognizes an unknown device
[Google Pixel 6] iSupakilla:
Oddly enough.. I didn't do anything different today. I quite literally did the exact same steps as i was doing yesterday just to open the device manager to see what was showing to take a screenshot to post here and the process just... worked. flashed, Magisk shows installed and Root Checker confirms. Also, I did end up using a C to C cable and it worked.
[Google Pixel 6] arvylas:
Anyone having problem with device integrity and gpay/wallet after updating to February image? Everything was working flawlessly and stopped after the Feb update. I tried updating to usnf 2.4.0 but still no luck.
[Google Pixel 6] V0latyle:
Use 2.3.1 Displax mod 3.0. Make sure you aren't using other props/fingerprint mods at the same time.
[Google Pixel 6] arvylas:
It worked at last. Thank you very much
[Google Pixel 6] xabier-bo:
I went crazy while, after a failing update, fastboot didn't see my device via USB-C to USB-C cable.

Then, by chance, I tested a USB-A to C, and it worked.

After that, can't tell you why, fastboot works fine again with the USB-C to USB-C cable. In my case no need to update drivers
[Google Pixel 6] Nightf0x_007:
Im failing device play integrity & cts profile safetynet tests here, i didnt do anything apart from updating to february update, im using magisk delta (riru)
[Google Pixel 6] V0latyle:
Questions regarding Play Integrity should be asked in this thread, for Universal SafetyNet Fix see this thread
[Google Pixel 6] kiwigi:
I have missed out on the January update due to being away a lot and have now the following questions;

Do I need to update each month's or the latest (February)only?

Or would be there be somewhere the update only, which could be flashed?

If I update with an OTA image, does it mean I have to reinstall apps which I have additional to the standard( Signal and others)?

As much as I remember I need to disable the Magisk modules before starting the process?

Thanks!
[Google Pixel 6] V0latyle:
The latest release includes all previous updates, you don't have to install them consecutively

No. OTA update keeps data and updates the inactive slot. The only thing that will cause a data wipe is if you use the flash-all script in the factory update; if you flash the image without using the script, data wipe is up to you

Not always but it's generally a good idea
[Google Pixel 6] kiwigi:
I have started the process of updating with PixelFlasher and as there is a "flash to inactive slot" I am not sure if I tick that or not?
[Google Pixel 6] V0latyle:
Since you're flashing the factory image, no. Flash to current slot.
[Google Pixel 6] kiwigi:
Super, worked perfectly, Thanks a million!
[Google Pixel 6] lackalil:
I have an unlocked phone on Mint (T-Mobile network). Regarding the 20230205 update, I wasn't sure whether to go with the standard build or the T-Mobile/T-Mobile MVNO version. But the release notes say Google Fi rather than MVNOs in general. https://support.google.com/pixelphone/thread/200738915/google-pixel-update-february-2023?hl=en

Anyway, I decided to try the normal version first and am not having any issues. Does anyone have any idea what the difference is? There's a T-Mobile variant on all Pixels from 4a 5G on so it must have been somewhat significant.
[Google Pixel 6] V0latyle:
The only difference is in the modem firmware. The system image should be the same.
[Google Pixel 6] devilsshadow:
Are people still getting OTAs on their rooted phones? Once again google is telling me there are no new updates available when I check
[Google Pixel 6] V0latyle:
Pretty common issue
[Google Pixel 6] pa.pn2:
Anyone else got a magisk canary update, but won't open after installation?
[Google Pixel 6] devilsshadow:
yes and apparently it's a known "issue" that occurs when you blindly tap on the update notification without unhiding magisk first. No clue how to fix, will try with pixel flasher.

EDIT: not fixed after updating to feb update via pixelflasher. No clue how to restore magisk atm.

EDIT 2: known issue with the latest canary build. Either install the debug build for now, or wait for a fix.
[Google Pixel 6] Lughnasadh:
The bug in Canary Magisk 25207 has been fixed. Hopefully a new build will be released soon.

Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk

Fix #6637

github.com
[Google Pixel 6] Xpargas:
I'm having trouble rooting my pixel 6.

I rooted it a long time ago, but then I had to wipe it and it hasn't been rooted since.

Bootloader is still unlocked.

I extracted and patched the boot.img for the build I currently have installed (TQ1A.230205.001.D2, Feb 2023, T-Mobile, T-Mobile MVNOs).

Transferred the patched boot.img back to my computer, rebooted to recovery, and then did the fastboot flash boot command.

After rebooting, the phone just boot loops. I'm able to flash the stock boot.img back and it boots again.

I've tried it several times and with Pixelflasher, but I just keep going into a boot loop. Not sure what i'm doing wrong.

Thanks.

Edit: Forgot to add that i'm using the latest Debug build of magisk. Tried the stable build also.
[Google Pixel 6] aimsjahan:
Just get the boot.img from factory zip (same build version of course, i.e. qpr or monthly) of Pixel 7. Patch it and flash usually.
[Google Pixel 6] Lughnasadh:
You should be in fastboot mode, not recovery, to flash the patched image, but I'm assuming you are since you were able to flash the stock boot.img.

Do you happen to have any Magisk mods still installed? If you have one that needs updating, that will cause a bootloop.
[Google Pixel 6] Lughnasadh:
You only need the Pixel 7 boot image for A14 DP1 or earlier QPR2 beta builds, not the stable February A13 build that person is on.
[Google Pixel 6] Xpargas:
THANK YOU.

Forgot I had some old modules installed. Did adb wait-for-device shell magisk --remove-modules and it booted and is rooted.
[Google Pixel 6] freonchill:
FYI - if anyone is having a problem

Installed 13.0.0 (TQ1A.230205.002, Feb 2023) via pixel flasher and was running magisk canary and couldn't get magisk to properly do roof. uninstalled canary and installed debug to get root working.
[Google Pixel 6] badabing2003:
Canary 25207, 25208, 25209 and 25210 have issues. You can use 25206 or the stable version.
[Google Pixel 6] freonchill:
Yea, got root back, but having issues with ad away for systemless hosts...
[Google Pixel 6] pa.pn2:
Anyone using substratum can confirm it's not working anymore with recent magisk update?
[Google Pixel 6] Lughnasadh:
Canary Magisk 25210 has a bug where it is failing to load modules. It's been fixed and hopefully a new build will be released soon. Until then, Canary 25206 is the last version without a "bug", although the module loading issue is not present in Canary 25209 and lower.

EDIT: I think 25209 may be ok.

25210 breaks module loading · Issue #6688 · topjohnwu/Magisk

Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...

github.com
[Google Pixel 6] GrandAdmiral:
I apologie if I'm posting to the wrong thread. If so, please let me know. While I would suspect that the March update will be released soon, I was looking at putting on the February update. There are several out there, one for T-Mobile MVNOs, which I have with Google Fi. But since I'm using both SIM slots (the other being AT&T), I should just stick to the regular image right?
[Google Pixel 6] V0latyle:
It won't really matter. You can just skip the February update and go straight to March.
[Google Pixel 6] pa.pn2:
Did someone updated to March build alleady?

If yes, which SDK works now, 33.3 or 34.1?

Im not sure which i should pick

And can someone please link or upload magisk canary 2506 please, im too stupid to download from github....
[Google Pixel 6] phaino00:
34.0.1 is not working. It does not switch to fastbootd to flash product.img and other images. Had to downgrade to 33.0.3 to install March build.
[Google Pixel 6] Lughnasadh:
magisk-files/app-release.apk at 5b2934603f979d7133e67bbc30c6ce3fa0d8e31e · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com
[Google Pixel 6] Admiral2145:
On pixel 6 a/b is there away to flash both slots at the same time with fastboot?
[Google Pixel 6] Lughnasadh:
With Pixel Flasher you can. To do it manually you'll need to flash one slot, set the active slot to the other slot and then flash again.
[Google Pixel 6] deusfaux:
1. If I (in Canada) waited for the OTA system update - which of the 2 different March updates would it choose for me?

2. What exactly is a fork like this even doing? What if I spend my time on Canadian and American cellular networks?

3. What happens next month if there is only a single global update? Does that mean the Canada specific changes in the March version got folded into the April update?
[Google Pixel 6] V0latyle:
TBH I'm not sure how OTAs are allocated. When the update becomes available check the build number against the OTA files on the Pixel images page.

Fork? Do you mean a carrier specific version?

The only difference that I'm aware of is in the radio firmware. System update and bootloader are the same as the global update

The bootloader and radio are not updated every month, only when an update becomes available. Still, if there's a global update after a carrier specific update, I would assume that the radio firmware includes whatever improvements were in the last update.
[Google Pixel 6] deusfaux:
Ok so if there's only a global update for April, is it possible the radio component could be the same better or worse than the March Canada radio?

Like, do I need to definitely apply the March update on the possibility it is a superior radio for Canada that the following update doesn't include or improve upon?

I've been a Nexus/Pixel user since Nexus S and have never seen a Canada specific update so this is all fairly opaque
[Google Pixel 6] V0latyle:
Just update to April when it comes out.
[Google Pixel 6] DarkH2O:
From what I was able to find by searching, I can't root the Verizon version of the Pixel 6?
[Google Pixel 6] Admiral2145:
That's correct afaik.... Always buy directly from Google.
[Google Pixel 6] gazdajezda:
Hello guys!

My problem is back again, damn... I have a P6 with A12 Security Update: 5. june 2022 and for all flashing till now I used a "Version 33.0.2-8557947" of platform tools. Also, phone is rooted - I'm totally happy with it, really! Also there is still old pre A13 boot loader - the one without flash version counter.

Aha, I also have all AUTO-UPDATE options disabled, so system is not allowed to download it. But, that doesn't work. On friday I get a system message that my apps were using much more data than usual. When I look into "Mobile data usage", there is "System Updates" with 1,94 GB data used. So, i presume there have been system update downloaded which will be installed soon. Today, half an hour ago I get a banner message that there is update available which will be installed after reboot. %$@#pissed off#"#$%

So, what can I do now? I'm perfectly happy with current setup, all apps (including banking) works great, root, no ads... evertything is perfect. But as it stands, after reboot update will be installed (presumably to last version of A13) and I already know that phone won't boot normally - few months ago was the last time when similar 'update' happened and phone booted into some special mode where only Shutdown menu worked. At that time I flashed back the current A12 version factory image, root again & set phone as it is now. But obviously this is a no win situation, get tired of repeating it every few months. So maybe I need to flash last version and live with it. It seems there is no other way with G rom.

Is current last version of Android (13) for P6 root-able and apps like Revolut, N26 work ok or they detect root and don't wanna work? Because I need it and as far as I see, staying on A12 is kind of not allowed anymore from Google. Thanx for any helpfull hint.

Sorry, if this post is not suitable here please delete it.
[Google Pixel 6] V0latyle:
Rooting Android 13 works exactly the same way as Android 12. I'm not sure about Revolut, it's possible that they use independent root detection methods, and I know of at least one user whose Play Store kept telling them the app wasn't available, but they were also on an older Android version.

For most apps, the only things you should have to do is use Universal SafetyNet Fix MOD and DenyList in Magisk. But that's more a problem for the Magisk/Universal SafetyNet Fix threads, not so much this one.

The only way I know of to (try to) disable automatic updates is the Automatic System Updates toggle in Developer Options. However, it seems like the only thing this does is prevent the system from automatically updating when the device restarts.

It's odd enough that you get update notifications. I never do on my Pixel 5; even when updates are available, it still won't find and download the updates, so I always have to update manually. This really seems to be a mixed bag among rooted Pixel users; some people are able to get OTA updates, some like me can only do manual updates.
[Google Pixel 6] gazdajezda:
Ok, thank you! Yes, I do have Automatic System Updates toggle disabled, but ... Now I need to see what are proper Magisk, SNF version files for A13 and then I will update. God I hope root will work and I will be able to restore all my apps with Swift.

My current versions now:

Magisk: a468fd94 (25205) with modules:

Systemless Hosts 1.0 by Magisk

Universal SafetyNet Fix v2.3.1 by kdrag0n

Those working 3 (root, systemless hosts and USNF) functionalities are what I need in new ROM. Others can be restored. I just don't know how to update, with reboot or sahall I download latest A13 Factory Image and flash / root it. If that way, I need to patch both slots with new boot image so new bootloader will 100% be installed, according to your other thread.