yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] whatsisnametake2:
so using magisk canary, play integrity fix latest, shamiko, latest zygisk, I'm getting these results. the play integrity result I'm assuming is as it should be, but what about the check root results? how do I get rid of those fails? should also add I'm hiding renaming magisk and freezing it.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I honestly have no idea. @HipKat, do you have any input on this?

What's the screenshot of the following instructions say:
[Google Pixel 8 Pro] LLStarks:
PIF is in a back and forth fight with Google to keep device integrity. They may have lost for now.
[Google Pixel 8 Pro] roirraW "edor" ehT:
PIF 13.8 is working for me just fine at the moment. I went ahead and upgraded just after my post above, since there hadn't been any PIF updates for ~15 hours, give or take.
[Google Pixel 8 Pro] V0latyle:
Can't speak for the Pixel 8 but still passing here on my Pixel 5...
[Google Pixel 8 Pro] whatsisnametake2:
so for those of you who are passing, what does tb checker give you on the check root test like my screenshots? presumably you're not getting those fails? are you using magisk standard delta or alpha? shamiko?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I don't normally have it installed, but I get:
[Google Pixel 8 Pro] whatsisnametake2:
thanks for doing that. interesting so you're getting the same fails but not having a problem. what banking apps are you using?
[Google Pixel 8 Pro] roirraW "edor" ehT:
No sweat. I sincerely apologize, but due to my experiences, I'm not willing to share what banking apps I currently use. :)
[Google Pixel 8 Pro] cmh714:
when I read the post, I was like and include your PIN please.......or another reply may have been, you first! :)

my apps are all working too, including work junk like Okta....
[Google Pixel 8 Pro] HipKat:
I would ask why use Magisk Canary when Stable works perfectly fine for passing all of those that he mentioned.

@whatsisnametake2 Why Freeze Magisk?
[Google Pixel 8 Pro] HipKat:
It's passing on my P8P
[Google Pixel 8 Pro] Lughnasadh:
There shouldn't be any difference between the latest Stable (26.4) and the latest Canary (26401) as there hasn't been any new Canary releases since they were both released on Nov. 6.
[Google Pixel 8 Pro] HipKat:
I see.

Also, I never even heard of TB Checker before. Seems like it's looking for fails that have nothing to do with using Gpay, Wallet, etc
[Google Pixel 8 Pro] V0latyle:
It's just a more comprehensive root indicator. It can determine Play Integrity responses, indicate whether root is detectible, even detect Zygisk.

GPay/Wallet only rely on Play Integrity but many other apps use third party security engines for root detection.
[Google Pixel 8 Pro] whatsisnametake2:
has anyone here got santander working? I don't hold out any hope on my unit for mbna because it was failing on just bootloader detection with no root. so whatever I do with PIF etc, none of that is masking bootloader status, so its not going to get mbna working unless I'm missing something. I would settle for wallet and santander working tho, but both of those fail here as soon as magisk is installed, even with shamiko/enforce deny list and various versions of PIF USNF and hiding magisk. yes TBchecker root check throws up some fails, but so does it on other peoples phones who aren't having problems.
[Google Pixel 8 Pro] roirraW "edor" ehT:
From what I've always understood, it's impossible to hide that the bootloader is unlocked.
[Google Pixel 8 Pro] stu5797:
Thanks for all your help on this forum! I recently tried Google wallet and it did not work so just upgraded now to 13.8 PIF. What steps do I need to do to get Wallet working again? Do I need to delete wallet, Play store and Play services? I obviously want to do the minimum to get Wallet up and running again. Thanks so much
[Google Pixel 8 Pro] whatsisnametake2:
yeah exactly. thats why I think there's no way I can get mbna working. santander and wallet maybe, I just can't work out the combination yet.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome! I didn't have to do anything else other than update to PIF 13.8. There are some optional troubleshooting steps in post 2 in the SafetyNet steps section.
[Google Pixel 8 Pro] HipKat:
Not delete them, clear cache/data. In my case I do not have the Deny List enforced for those (and some other) apps.
[Google Pixel 8 Pro] Paz9:
Does anyone notice a notification delay when paying with gpay?

I don't see notifications for up to 5 mins
[Google Pixel 8 Pro] gettinwicked:
Why is this happening so much now? I've updated the integrity fix 3 times this week I believe? And. It looks like another one is needed. Is Google just all out fighting rooted devices using gpay?
[Google Pixel 8 Pro] Tomadock:
You need to add your own fingerprint now.

From GitHub:

"Google banned v13.9 fingerprint.

Now you must search a valid fingerprint, you must modify /data/adb/pif.json file to spoof a valid certified device."
[Google Pixel 8 Pro] gettinwicked:
Well, damn.. Anyone have a valid fingerprint handy to share?
[Google Pixel 8 Pro] Tomadock:
I just PM'd you one that was shared on Telegram by the dev. I'm not sure how long it's going to last, but passes right now.
[Google Pixel 8 Pro] gettinwicked:
Thank you!
[Google Pixel 8 Pro] kiekan:
Just upgraded to the 8P today. Followed the directions in the first post for Safetynet (using PIF v14). But the Play Store is showing "Device is not certified". I have enabled the developer settings in the Play Store and the integrity check shows [MEETS_BASIC_INTEGRITY].

I have tried clearing both data/cache on the Play Store and clearing the cache on Play Services.

Is there any way to resolve this so the Play Store marks my device as certified?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Try rebooting? Also, see above:

July 1, 2024 AP2A.240705.005 Global | .A1 Telus - Unlock bootloader / Root Pixel 8 Pro [Husky] Stable firmware / SafetyNet

Pixel 8 Pro [Husky] July 1, 2024: https://developers.google.com/android/images#husky https://developers.google.com/android/ota#husky https://flash.android.com/ https://support.google.com/pixelphone/community?hl=en...

xdaforums.com
[Google Pixel 8 Pro] Tomadock:
Just wanted to drop a guide osm0sis made to generate your own fingerprint for use with PlayIntegrityFix since this seems to be coming up now.

🔧 [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 8 Pro] kiekan:
Just a heads up: PlayIntegrityFix v14.1 has been released.

Flashing this following the provided directions solved my Play Store certification problem.
[Google Pixel 8 Pro] gpvecchi:
Jesus, still different software versions?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Not for October, at least yet. :)

Anyway, I think that's always going to be a thing, from time to time, since that has happened some months since the Pixel 1 (I never owned a Nexus, so can't speak to that).
[Google Pixel 8 Pro] Paz9:
My p8p comes in a few hours

Will be updating then (attempting) rooting immediately.

Pray for me 🤣
[Google Pixel 8 Pro] roirraW "edor" ehT:
Good luck!

Spoiler content hidden.
[Google Pixel 8 Pro] Paz9:
Question before rooting

When using displax safety net fix I pass both CTS and basic integrity

With kdragon I'm hardware backed attestation basic integrity pass but fail CTS

From what I understand hardware backed is better, is there a way to also pass CTS with kdragon?
[Google Pixel 8 Pro] HipKat:
Not sure what this is or what it means
[Google Pixel 8 Pro] Lughnasadh:
Android 14 may add an advanced memory protection feature to protect your device from memory safety bugs

Android 14 may add a new beta feature called "advanced memory protection" that can protect against memory safety bugs on compatible devices.

www.xda-developers.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
No, the CTS is more important. Stick with Displax USNF 2.4.0 Mod 1.3 (not Mod 2.0).

It's fine not passing Strong.
[Google Pixel 8 Pro] Paz9:
Got it

Stay tuned for results
[Google Pixel 8 Pro] Gilg@mesh:
how long does it usually take before custom roms appears?
[Google Pixel 8 Pro] roirraW "edor" ehT:
In the Pixel 7 Pro section, the earliest ROM thread I could find was from Nov 16, 2022. So, I would say month, month and a half. Note that the Pixel 7 Pro delivered later than the Pixel 8 Pro will, but I'm not going to track that info down, you'll have to do the rest of the work.

:D
[Google Pixel 8 Pro] Gilg@mesh:
so let's say if I unlock the bootloader and root the phone with stock ROM, I remember the old days it was possible to flash a custom rom over stock without losing any data, still possible?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I would never, ever, flash a custom ROM over stock unless the custom ROM was based on stock, and I don't think any custom ROM for Pixels in the last couple of years are based on stock. They're based on AOSP, which is indeed the base layer of the Pixel Android, but there is still some minimal but very important overlay when on the stock ROM.

But even if there was a custom ROM that's based on the stock Pixel experience (not just in behavior, but actually based on its files from the same month's firmware release), I still wouldn't flash a custom ROM over stock. I'm sure I did it many years ago. I would guess the last time might've been 2014 or 2015, or there might be a slight chance late 2016 on the Pixel 1 (but I don't think I did), but it's just asking for trouble.

With any luck, not huge trouble, but sometimes small trouble is the worst.

As usual, someone correct me if I'm wrong, because I definitely haven't bothered to flash a custom ROM on a Pixel since, at the latest, early 2017. These days, I just don't have time to be too experimental, so I stick to stock rooted with a handful of stable and well-maintained modifications.

If you haven't ever tried it, once you root your Pixel 8 Pro, try @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+.

That mod is just awesome, and keeps getting even better all the time. Couple that with @Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+ and @jorrik98's thread [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile, and last but not least, Nova Launcher Prime (although I'm sticking to v7.x for now), and you might change your mind about trying a custom ROM.

See Post #3 - Other, most important resources:

A list of other important apps

for other things I recommend.
[Google Pixel 8 Pro] simplepinoi177:
As unlocking the bootloader requires the device to be wiped, before setting up & customizing the device too much (and, of course, without root access yet, you wouldn't be able to save the data with any apps that absolutely no customizations could be saved outside of Google's Backup), I'd unlock it anyways. If, for whatever reason, rooting is a bad decision, having an unlocked bootloader still has a lot of recovery benefits (not just custom ROMs or kernels and, of course, rooting). The only reason I wouldn't is if you absolutely require using an app that detects an unlocked bootloader; and that's only if it's confirmed that no bootloader/root hiding method works on it....

Just my 2 cent suggestion....
[Google Pixel 8 Pro] Paz9:
P8pro in my hands now, updating then going to attempt root.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Awwww! You tease! When you were talking about SafetyNet a little while back, I thought maybe you already had it then. :)

Cheers, and good luck!
[Google Pixel 8 Pro] Paz9:
no just wanted to make sure everything is here before i begin tinkering... updating now , phone came with sept updating to oct before unlocking BL and disabling AVB/Veri, init_boot patched ready to flash... standby.
[Google Pixel 8 Pro] roirraW "edor" ehT:
This old man has to get to bed, unfortunately, but I expect to read about it in the morning, and congratulations on your new phone, and in advance for being the first to report back on the root experience.
[Google Pixel 8 Pro] Ultimoose:
Awesome, looking forward to seeing how it went.
[Google Pixel 8 Pro] Paz9:
rooted init.boot

flashed via adb

opened magisk app and got a notification "additional setup required"

restarted.

confirmed root is working safety net working too.
[Google Pixel 8 Pro] Paz9:
Will there ever be a solid fix to PIF? Instead of this car and mouse game
[Google Pixel 8 Pro] ysco:
For me it's also working but you must delete the included pif.json file if you don't want to add your own fingerprint. If you leave that file it will not pass safety net. Regards ysco..
[Google Pixel 8 Pro] kiekan:
Yes, this information is included in chiteroman's instructions on the release page for 14.1.
[Google Pixel 8 Pro] V0latyle:
It can be hidden in device props

BUT

since Android provides a native way for apps to check verified boot state, ultimately no...unlocked bootloader does not verify boot integrity and will not provide proof
[Google Pixel 8 Pro] V0latyle:
Most likely no, unless someone figures out a way to defeat PI without PI knowing it's been defeated

The only way we've been able to consitently defeat it is by spoofing props to make PI think it's on an older device that can't do hardware backed attestation, so it falls back to basic attestation, and from there it's easy to make PI think system is secure

The problem is Google has somehow been identifying the fingerprints that have been used, and blacklisting them where there's a mismatch, because they have the ability to trigger some sort of comparison between fingerprint/props as seen by other processes, and what PI sees

There's a possibility they've been monitoring this site and simply target whatever print is included in whatever latest fix, so it seems the safest strategy for now is to use a module that does NOT include a print (like v14 or @osm0sis fork) and instead supply your own print

problem is, it can be tedious identifying a print that works. It's a trial and error process - find a print, build the pif.json, run integrity check. if it fails, try again. And again, and again and again until you find one that works

This isn't appealing to most users because they want a "one size fits all, flashing this will fix the problem" solution, but it seems that whenever a print is in common use by a module that many people are using, that print gets banned quickly, so the only safe way is to find your own.
[Google Pixel 8 Pro] bosox284:
This is where I fit in with most users. It may only take about 30 minutes but I just don't have the time to dedicate (or the patience for that matter) to find a working print. Unfortunately, I may just revert to stock to get functionality back.

I hate it because I'm a firm believer that I should be able to root my phone if I desire, since I own it. I'm an adult and can accept the security risk.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android Security Bulletin—December 2023 | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] swieder711:
I deleted /data/adb/pif.json and now am passing SafetyNet on my new Pixel 8 Pro.

Play Integrity API Checker shows "Error getting token from Google" Calling app is making too many request ...

EDIT: I ran Check Integrity from the Dev Options in the Play Store app and it passed Basic and Device.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Pixel Update - Dec 2023 - Google Pixel Community
[Google Pixel 8 Pro] roirraW "edor" ehT:
December (Android 14 QPR1) update:

https://developers.google.com/android/images#husky

https://developers.google.com/android/ota#husky

https://support.google.com/pixelphone/community?hl=en

https://source.android.com/docs/security/bulletin/asb-overview
[Google Pixel 8 Pro] roirraW "edor" ehT:
A Google article specifically about the Android 14 QPR1 Stable release.

December 2023 Feature Drop - Google Pixel Community
[Google Pixel 8 Pro] GarnetSunset:
the OTA image for the latest doesnt exist yet :o
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're correct! Try some other languages for the page (upper right corner of Google's page). It happened before that it was available on a different languages' page before English - most commonly it's the other way around, English first, but sometimes different.

Thanks for the heads up.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Edit: NOW it's up on the English page.

Old:

Found it!
[Google Pixel 8 Pro] GarnetSunset:
Is that gonna change the language of my phone? :O
[Google Pixel 8 Pro] LLStarks:
No, just ignore selecting a language. It's up for everyone.

Wonder if we get qpr2 beta 2 today too since this is so early in the day.
[Google Pixel 8 Pro] roirraW "edor" ehT:
The OTA/factory image is the exact same no matter which language you set the page to. It just changes the language of the text on the page.
[Google Pixel 8 Pro] GarnetSunset:
not up on en
[Google Pixel 8 Pro] LLStarks:
It was up for me in English. Weird.
[Google Pixel 8 Pro] roirraW "edor" ehT:
NOW it's up on the English page.
[Google Pixel 8 Pro] Lughnasadh:
https://twitter.com/i/web/status/1732445279234736494
[Google Pixel 8 Pro] chill145:
Have had a strange issue I just noticed and I believe it's related to PIF and working fingerprints.

After finding a working fingerprints, once I unplug my phone, and plug it back in, I lose access to developer options, meaning it no longer shows up, and I can't change USB preferences as it's completely blank. The only way to get those back is through restarting the phone. Has anybody else experienced this? Updating to December's OTA didn't resolve it.
[Google Pixel 8 Pro] Santi3598:
Warning to everyone, before updating to the December build, DISABLE/UNINSTALL ANY VISUAL MODS LIKE ICONIFY AND PROJECT THEMER. Specifically anything that modifies the quick settings. Flashing the December build without doing so will result in bootloop.
[Google Pixel 8 Pro] paratox:
Is it possible to flash this without data wipe from the last QPR release?
[Google Pixel 8 Pro] roirraW "edor" ehT:
You'll have to be more detailed. By "last QPR release", do you mean the most recent QPR Beta, which was for QPR2 (which goes final in March)? Or do you mean from the last QPR1 Beta?

If you're on the QPR2 Beta, then the answer is no, not without wiping data, since the now stable December firmware is Android 14 QPR1 (Stable), therefore QPR2 Beta is considered to be an upgrade from Android 14 QPR1, so downgrading to QPR1 Stable from QPR2 Beta, you MUST wipe the phone. You'd be lucky if the phone even booted without a wipe in that case, and even if it did boot, things would not work correctly since you'd be using QPR1 Stable with QPR2 Beta's app data.

If you're on QPR1 Beta, then the answer is yes, since QPR1 Stable is an upgrade to QPR1 Beta.

Note that in either case, if you proceed to update to QPR1 Stable, then if you ever officially opted-in to the Beta program, you should opt-out, otherwise you'll continue to get QPR Beta OTAs.
[Google Pixel 8 Pro] cmh714:
Seems like the latest fix is working for me...the link to LLStarks post in the other thread..and one last note, for me, I had to install this module twice to get it working, unsure why, but there it is. GL!

[Guide] [January 3, 2024] Root Pixel 8 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More

[Guide] [January 3, 2024] Root Pixel 8 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More Android Security Bulletin—January 2024 Pixel Update Bulletin—January 2023 Introduction This Guide is for Pixel 8 Pro owners that want to...

xdaforums.com
[Google Pixel 8 Pro] fil3s:
Awesome stuff. 🙂
[Google Pixel 8 Pro] Gordietm:
Is it possible to get automatic updates without manuallly flashing an ota or factory image with an unlocked bootloader?
[Google Pixel 8 Pro] Homeboy76:
Yes, but lose root: Settings > System > Developer Options > Automatic system updates
[Google Pixel 8 Pro] roirraW "edor" ehT:
Unlocking the bootloader doesn't affect whether you can automatically update or not, at all. Only rooting affects whether you can automatically update.
[Google Pixel 8 Pro] Lughnasadh:
Aside from the other answers above, you can always try to use the "Install to Inactive Slot" method in Magisk to update and keep root. It's hit or miss, but has definitely worked for many on the Pixel 6 and 7 series and seen some reports where it worked on the Pixel 8 series as well.

There has also been several reports in the past where people successfully updated via OTA while rooted, but of course lost root afterward. Not a common occurrence though.
[Google Pixel 8 Pro] nummer:
but what about enabling them after the fact?
[Google Pixel 8 Pro] Santi3598:
To add to my previous post, any mod that modifies the QS Tiles, will break your UI. You can change stuff like the monet color if you want. So if you modify the Quick Settings tiles, before or after, your phone won't boot properly.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Due to the security issues that some malicious QR codes have, I wonder if Google will create some kind of QR code sandbox, allowing you or Google time to evaluate if the QR code is okay or not.

I wonder if Apple has implemented anything in that respect? Anyone know?
[Google Pixel 8 Pro] jdkruzr:
so, brand new P8Pro, first let it update OTA, everything was good, unlocked bootloader, followed directions for flash-all.sh and... dark screen blue Google logo bootloop. tried to go to recovery mode to clear user data etc and now in a white screen Google logo bootloop. how do I start over?
[Google Pixel 8 Pro] K1nsey6:
I have modified QS tiles using Pixel Xpert and I didnt experience any UI issues
[Google Pixel 8 Pro] rester555:
Did anyone have issues with better Internet tiles?
[Google Pixel 8 Pro] Santi3598:
That's awesome. I tried doing that with Iconify and project themer and both of them bootlooped. I guess I never tried Pixel Xpert, but I will now
[Google Pixel 8 Pro] jdkruzr:
so, either my phone was defective or I bricked it because of the "nothing in the second slot" problem. either way I got lucky, Best Buy replaced it. so what I don't know now is what the Right Way to root, specifically, a brand new device is. should I let it OTA update like it wants to?