yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] badabing2003:
I could be wrong, but this is what I know.

I don't use APatch because I pass everything I need to with Magisk.

Pif makes you pass PI,

Sailfish is the current active print, and wallet works with it.

I prefer @osm0sis fork, over constantly changing PIF, much more stable and I don't need a new module each time Google pokes at us. At worst I change the print which doesn't even require a reboot.

RCS does not work with current public print, even though PI passes device and wallet works.

But RCS works with non public print, which I use.

Things that could break RCS and wallet are custom ROMs that are unsigned, or kernels with vanity name that is in a banned list, obviously stock ROM / kernel does not have that issue.

As for APatch, there are reports that it works with RCS,

Zygisk based modules would require zygisk next module, and there are some reports that, it breaks RCS.

Like I said, I'm not speaking from experience, just what I have read, and my knowledge could be outdated.
[Google Pixel 8 Pro] roirraW "edor" ehT:
@Dopamin3, take a look at this new post in my Pixel 7 Pro thread (all of the same thing should apply to the Pixel 8 Pro), thanks to @UberNorse. I hope this helps:

I honestly thought when I bought my Nest that it could only be just improved from my previous basic Wi-Fi experience with the cheap HoneyWell I had, plus of course, I didn't know at the time that the Learning feature just wouldn't be for us.

It looks good. The actual thermostat display/interface is neat, although it, too, could stand improvement. Oh yeah, I forgot about a (to me) major surprise compared to my old thermostat that for example, when I have air conditioning set to 73 F, then it waits a good while after the temperature has reached 74 F for it to start, and then it cools it down to 72 F.

With my old thermostat, it was straight forward. Set to 73 F and the temperature is 74 F? Turn on air conditioning until it reaches 73 F (including blowing the fan longer once the actual air has shut off, to still take advantage of the remaining cool air in the system - which the Nest does too), but the old thermostat did not insist on taking the temperature down to 72 F before shutting off.

I know, or believe, that this is to save energy, and I'm sure it does. But it was very annoying, new to me, and I had to get used to it.

Edit: And I'm glad to know I'm not the only one annoyed by this lack of feature and development.

Thanks for sharing that information, @badabing2003! And good point - I guess I don't have much motivation for experimenting with APatch since Magsik is working well for me.

For what it's worth, @chiteroman's PIF includes "playcurl", which checks and changes the fingerprint as necessary, without the need for a new version of the module. I was previously using an older version of their module along with the separate playcurl module.

I still haven't fooled with private fingerprints, though.
[Google Pixel 8 Pro] badabing2003:
I could be wrong, what he's saying is that his latest module embeds a print hence you don't need playcure to fetch it, because it is already embedded.

When Google bans Sailfish arround the end of the month, (or sooner) you'd need to update module to one that embeds what might be public at that point.

I know his module probably should custom print, but still knows which version does, be keeps on flip flopping.

With the fork, I could install v5 or probably even older and still pass, the only additions that are in the newer versions is to support older Androids, and improved migration scripts and features alike, which really don't apply to newer pixels.

I'm not trying to discourage anyone from using PIF, I personally like the stability and reliability of the fork.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Playcurl was the module that I used to use in combination with PIF. Playcurl would automatically check if Basic and Device were passing integrity, and would download a new fingerprint when they weren't passing. So I used to advise users to install both PIF and the separate playcurl module, but when I mentioned that, chiteroman's chimed in that their PIF now includes playcurl, so you no longer have to use the separate module.

I understand, and I definitely don't discourage anyone from using the same solutions as you do. In a way, I'm embarrassed that I haven't found the time and motivation to create my own private fingerprint, but I just can't find the time to dig into that so far.
[Google Pixel 8 Pro] HipKat:
Sailfish?
[Google Pixel 8 Pro] HipKat:
Which Thermostat did you get, the White one wit the plastic housing that doesn't physically turn (1st Generation) or the metallic housing that actually turns to adjust (3rd generation)?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Pixel 1 codename.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

I still have two Pixel 1s. :)

3rd generation, got it in 2018. I forgot that I heard about the ones that didn't actually turn.
[Google Pixel 8 Pro] HipKat:
Those are the ones the Utility companies usually hand out for free, along with the Ecobees.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Ah. I don't remember for sure at this point, but I think I got a rebate on mine at the time. My step-nephew really likes his Ecobee, but I've never taken a look at them, since I didn't hear about them until he got his.
[Google Pixel 8 Pro] rester555:
I have an ecobee3 and will never go back to Nest. The metrics and the options are far better in my opinion. Nest lacks a lot of information and metrics. Especially for super cooling. Unless it's improved in the last 3 years there.
[Google Pixel 8 Pro] HipKat:
I think I still have mine in a box somewhere
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks!

Just assume that nothing has changes with any Nest Thermostats...possibly ever. I'm sure there's been something, but nothing remotely memorable, if so. Like changing the app UI. :D
[Google Pixel 8 Pro] HipKat:
Nothing's changed with mine, that's for sure. TBH, we stopped installing them because of the issues with Heat Pumps and Geothermal.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Updated with Telus .A1 images at:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Release v16.0 · chiteroman/PlayIntegrityFix

WORKING TEE = STRONG PASS

github.com

"WORKING TEE = STRONG PASS"

Hmmmm....

Edit: There's already been a newer pre-release, though (up to 16.2 right now), so I like to hold off for a week without new activity before upgrading to the latest Stable release.
[Google Pixel 8 Pro] Lughnasadh:
Already replied in the Pixel 7 Pro thread, so I guess this is for others 🙃

This is changing by the minute, lol. Probably best to wait and see how things shake out. His latest message....

Sailfish fingerprint is banned for RCS, so even passing Strong it won't work.

But now you have a valid certificate chain, you can use more fingerprints, including newer ones.

Also you can use your device fingerprint 😊

ONLY IF YOUR TEE IS OK
[Google Pixel 8 Pro] rester555:
Is a new fingerprint created through re-installing the ROM every time and it registering server side with Google?
[Google Pixel 8 Pro] Lughnasadh:
Not exactly sure what you mean, but if it's the same build it should have the same fingerprint.
[Google Pixel 8 Pro] Lughnasadh:
Google System Release Notes June 2024​

Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google announces early August 13 event for Pixel 9 and Pixel Watch 3

Google this morning announced that its annual Pixel hardware event will be taking place on August 13. This is incredibly...

9to5google.com
[Google Pixel 8 Pro] Ghisy:
It would be nice to have the new hardware in September this year. I'll be traveling abroad in October so this would be better for me if I decide to upgrade my P7P and OG PW. 😁
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google's Pixel 9 Pro and Pixel Watch 3 Get a Crazy Early Official Date

Google is going to announce the Pixel 9 Pro and Pixel Watch 3 much earlier than expected. We should know pricing, release date, and more in August.

www.droid-life.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Wallet adds support for hotel keys

When Google Wallet relaunched in 2022, the goal was to replace your physical wallet and work towards that continues with hotel keys...

9to5google.com
[Google Pixel 8 Pro] Kennyeni:
Am I the only one that feels like the rooting scene is changing by the minute with all the conversations around TEEs, RCS, PIF, patch, kernel patching, etc?

Im currently running on the May patch, with:

Kitsune. An app I care about detects root with regular Magisk

PIF. vanilla

Playcurl. To keep FP up to date

Currently, root is working and all apps, including Wallet work pretty well, and it has been that way for the last 6 months. I'm unsure if RCS works but I don't need it.

What would you say is my best path forward? I have been thinking about using apatch to replace Kitsune, as it seems to have better maintainability going forward, but maybe I'm missing something.
[Google Pixel 8 Pro] Pekempy:
Having issues getting the June update rooted. I stupidly rebooted before flashing the OTA in magisk app so trying to do it manually.

- Extracted init_boot from update package

- Patched in Magisk 27000 update

- Moved to PC

- Flashed in fastboot slot a and b

- Rebooted

Magisk is still showing its not installed

The patch log looks fine minus a few cp ownership errors

Spoiler content hidden.
[Google Pixel 8 Pro] roirraW "edor" ehT:
By any chance, is it possible you have two copies of the Magisk app on your phone? A normal one and a hidden one? Had you hidden the Magisk app previously and left it hidden before flashing the update?
[Google Pixel 8 Pro] Pekempy:
I only have one installed - com.topjohnwu.magisk (The hidden usually shows as `Settings` with default icon, and that's not in my app list anywhere. Not too sure if I unhid before reboot or not (it was a couple of days ago).

If that was the case, and its now uninstalled, would there be a way of restoring it when unrooted?

Also tried canary (Magisk 27002) and same result

Edit: Not sure what was different, but I just did it again for the 80th time

`adb reboot fastboot` to get into fastbootd

`fastboot flash init_boot init_boot_magisk.img`

`fastboot reboot` and it's done, now rooted. 🤷‍♂️
[Google Pixel 8 Pro] roirraW "edor" ehT:
Another update:

Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm glad to hear it worked out. So strange. Similar things have happened to me and others over the years. It's so bizarre and impossible to figure out what happened.
[Google Pixel 8 Pro] gpvecchi:
How do you get this? The option under system updates can't find anything, I'm still on May patch.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm sure like other things, they're rolling out gradually. I just manually checked for a Play system update, and it didn't find any beyond the May 1, 2024 (while on the June firmware).

I don't normally bother checking for updates to it, or pursue installing them early by obtaining them somewhere else, I just checked out of curiosity to see if I had the same results as you.

For anyone who doesn't yet know:

Check & update your Android version - Pixel Phone Help

To troubleshoot software update issues, you can use our self-help flow. Fix your software update issue Important: It's normal for your Android device

support.google.com

Edit: Or, looks like you can click the blue button near the top of the page at that link:

Fix your software update issue

Clicking on it brings me to a screen that says:
[Google Pixel 8 Pro] Lughnasadh:
To add to the GPSU discussion...(per Mishal Rahman)

Thanks to Project Mainline, Google has been able to push out updates to your Android device's time zone database since Android 10. This is useful to quickly address changes in time laws that happen from time to time. However, before 2023, tzdata updates were "still bundled with other Mainline changes, sometimes leading to testing complexities and slower deployment." Google says that in 2023, they made "further investments in Mainline's infrastructure and decoupled the tzdata module from the other components." This isolation allows Google to release tzdata updates to Android users outside of the established release cadence.

(These out of band tzdata updates may be why some of the Google Play System Updates you've received haven't bumped the GPSU version. The GPSU version is only bumped when the Module Metadata APK is updated with a newer version name. This only happens when Google rolls out a new monthly Mainline train.)
[Google Pixel 8 Pro] Lughnasadh:
Canary Magisk has been updated to 27003

Magisk (45fa1fce) (27003)​

[General] Support 16k page size

[MagiskPolicy] Preserve sepolicy config flag after patching

[MagiskPolicy] Optimize patching rules to reduce the amount of new rules injected

[Core] Remove unnecessary mirror for magic mount

[DenyList] Support enforcing denylist when Zygisk is disabled

[Resetprop] Improve implementation to workaround several property modification detections

[Resetprop] Update to properly work with property overlays

Diffs to v27.0​

[General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

[MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

[MagiskBoot] Support spliting kernel images without decompression

[App] Support patching Samsung firmware with images larger than 8GiB

[App] Use user-initiated job instead of foreground services on Android 14
[Google Pixel 8 Pro] onesolo:
I'm on the Canary Debug and I can't install the new update!!! I get this error:

Any ideas??
[Google Pixel 8 Pro] Lughnasadh:
Are you using Direct Install? You say you are using "Canary Debug"...which one? Canary or Debug? Either way, are you using the same you were on to update?
[Google Pixel 8 Pro] onesolo:
I'm using, Debug channel (which is basically Canary with Debug, right?). I tried to install using direct install as I always do when there is a new build update. Isn't that the right procedure, to use the direct install?? Never had any problem with direct install
[Google Pixel 8 Pro] Lughnasadh:
Sounds similar to this issue and this. Did you go from 27002 to 27003? If so, maybe that's why (see issues linked). Looks like there's a Pull Request for this issue.

I had no problems going from 27001 to 27003, so maybe downgrade to 27001 and then update from that if you indeed went from 27002 to 27003, or start from scratch with 27003 (flash patched image instead of direct install).
[Google Pixel 8 Pro] onesolo:
Ok, thkx for the heads up. I think I won't be need to manually flash this for now. Not having any major problem with root
[Google Pixel 8 Pro] onesolo:
I tried to manually patch the init boot but not even that I was able to do!!!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android Security Bulletin—July 2024 | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Well, I'm surprised since Android 15 Beta 3.1 came out today that the July Stable firmware also came out for the Pixel Watch 1 and 2. We'll see if the Stable firmware comes out for the phones, too. Nothing yet.
[Google Pixel 8 Pro] Ghisy:
I'm guessing tomorrow at this point.
[Google Pixel 8 Pro] roirraW "edor" ehT:
The first July 2024 Google Play System update:

Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com

Note that there were additional June Play System updates after the most recent post here about it.
[Google Pixel 8 Pro] Lughnasadh:
July images are up.
[Google Pixel 8 Pro] roirraW "edor" ehT:
July 1, 2024

:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Android Flash Tool

flash.android.com

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] Lughnasadh:
A New FCC Rule Could Force Carriers to Unlock Phones After 60 Days

The move could have big implications for AT&T and T-Mobile.

www.cnet.com
[Google Pixel 8 Pro] onesolo:
I was able to update magisk canary and patch init boot by unhide magisk
[Google Pixel 8 Pro] Kennyeni:
Does anyone know if Kitsune still works with June or July Pixel update? Regular Magisk doesn't work for some of my apps.
[Google Pixel 8 Pro] gpvecchi:
No issues with Kitsune for me
[Google Pixel 8 Pro] roirraW "edor" ehT:
Another Google Play Services update:

Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com

Edit: Oh, this text was added to the top, too:
[Google Pixel 8 Pro] weriwd:
Hi guys, I just updated from the Pixel 7 Pro (P7P) to the Pixel 8 Pro (P8P). As usual, the first thing to do is getting the root job done. :)

From what I've read, the rooting process is slightly different. For the P7P, I used to flash the Factory Image, while for the P8P, it's highly recommended to use the Full OTA Zip method, which I have never done before.

My fear arises from the fact that I want to avoid bricking this brand new device, as it's mentioned in the #2 post that you need to flash on both slots.

So far what I have done:

Updated to the latest available update using the device Software Updater (240705.005).

Unlocked the bootloader.

Installed Magisk.

Copied the latest update, already installed on the device, husky-ota-ap2a.240705.005-53506844.zip.

Patched the OTA with Magisk, generating a patched boot image (magisk_patched-27000_NUwYI.img) into the download folder.

In the platform tools folder, placed the husky-ota-ap2a.240705.005-53506844.zip along with the magisk_patched-27000_NUwYI.img

Now I'm wondering how I should proceed, since I have already installed the latest available update for the device. I want to ensure that both slots are bootable to avoid bricking.
[Google Pixel 8 Pro] roirraW "edor" ehT:
The process is exactly the same. A little over a year ago (I'm guesstimating) I modified the instructions in my Pixel 7 Pro how-to-guide to recommend the Full OTA Zip method, but you can use whichever of the two (factory image or Full OTA Zip) you like.

Each time you flash the Full OTA Zip, just with a real over the air update, it flashes to the "other" slot. Your currently active slot becomes your inactive slot, and vice versa. It doesn't hurt to flash the same OTA on top of itself, anyway, but there's no reason to in this case, either.

So if you flash the Full OTA Zip, it'll flash to your currently inactive slot, and that slot will become your newly active one. Of course, if you want both slots rooted (there's rarely any reason to leave one slot unrooted, since without root mitigations, secure apps will fail to work with the bootloader unlocked), then you should go ahead and flash the Magisk'd init_boot.img to your current slot, and then flash the Full OTA Zip, then you'll want to flash the Magisk'd init_boot.img again to your newly active slot.

It sounds like you've got a decent understanding of the process, so I think you're good.

Edit: Forgot to add, welcome to the Pixel 8 Pro world! :)
[Google Pixel 8 Pro] BillGoss:
Be aware that on the P8P you patch init_boot not boot. So your patched "boot" image is not a boot image but an init_boot image.

Don't ever try to manually flash it to the boot partition.
[Google Pixel 8 Pro] Ghisy:
You also patch the init_boot on the P7P FYI.
[Google Pixel 8 Pro] weriwd:
Thank you for your prompt response as always, and thanks to the other members as well!

It appears that I have been doing it the "dangoeuros way" since my P7P, using the factory image method.

So far, I have flashed the patched init_boot, and everything seems to be fine!

For upcoming monthly updates, I will stick to the "Full OTA Zip" method.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome! I used the factory image method exclusively, starting with the Pixel 6 Pro, and continued for at least half a year with the Pixel 7 Pro. I'm glad you've gotten rooted fine.
[Google Pixel 8 Pro] BillGoss:
Well, after reacting to the use of factory images as being a "dangerous way" and reading the OP properly (for the first time!), I'll now need to explain why I disagree with what the OP says (use full-image OTAs).

To do this I'll need to remind you (I love how English leaves it ambiguous as to whether I'm referring to you [the OP] or you [all of you reading this] that the A/B system design is there to enable INCREMENTAL OTA updates. The design is specifically to allow the currently running system to continue to be used while an update is processed and for a failed update to be "rolled back".

And this update is an incremental update which reduces both the cost of the phone by avoiding creating two full copies of the system files (odm,, product, system, system_ext, and vendor, which are all stored together as logical partitions in the physical super partition) and the network bandwidth needed to send the update.

In summary, an incremental update:

- Allows the phone to continue to be used whilst the update is processed

- Can be rolled back if the update fails to boot properly

- Reduces both network and hardware costs

And the really cunning bit in this, is the use of temporary files (copy-on-write or COW files) that avoid overwriting the current system files in the super partition until the phone has booted properly on the updated system. I admit freely that I've never REALLY understood exactly how they work. I got lost trying to make sense of the actual way the incremental update allows the new system files to be created on the fly when the phone first boots the update.

Now we can talk about full image OTAs. Since these are in the same format as an incremental OTA, but include the full images of ALL partitions (including system files), it is impossible to flash one of these while the system is running and then roll back the change if the update fails. That's because the current system files in storage (the super partition) will have been overwritten - remember, there's not enough room in the super partition (the area where the system files are physically stored) to hold two full copies of the system files.

And there you have it - a full-image OTA and a factory image update both result in an overwritten super partition leaving you with a phone that won't boot if the update is flawed. The only real difference is that the OTA gets applied to the inactive slot, while the factory image gets applied to the current slot. But both of them overwrite the single super partition (remember it's not big enough to hold two sets of system files).

If your brand new phone has taken just one incremental OTA update, then the original inactive set of slots will have been populated. But that's irrelevant because, if you've been using full-image OTAs, you can never get back to a working system if the update won't boot properly.

Here's the bottom line: full-image OTAs are just as "unsafe" as factory images because neither will let the phone recover from a bad update. The only TRULY safe update is the incremental OTA.

So feel free to use either full-image OTA files or factory image files. They are both equally "unsafe"! :)