yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] simplepinoi177:
Yes, uninstall Magisk from within; the standard Android uninstall method would simply uninstall the Magisk Manager app, not remove Magisk completely.

As the uninstall from the Magisk Manager app completely removes all Magisk (the folders in the root folder), it will unroot the phone and you'd have to repatch it (i imagine). But Magisk makes it a bit easier to patch -- I'm not fully read up and aware of how, but Direct Install ("basic reinstall") may now work.

I imagine “Beta” is essentially getting on Canary, but I’ve never ran Canary variant version myself before so I’m not too sure. I imagine it’s essentially the same thing. If not, getting it from the Github (there’s a link to where you can download the Canary files) is another possibility.

So, basically in a simpler sense, TB Checker is an app that is meant primarily for users who are hiding certain apps & services; it’s goal is to “check” if those things are detectable – so you “pass” if it’s not detected, and “fail” if it is. So in the case of Magisk or Lucky Patcher, unless you made it a point to hide those and made specific action to hide them (like HMA), they will be detected – which is a “fail” as it did not “pass” in hiding or not being detected.

If you didn’t know; many apps will detect root & potential modification against their intentions/setups by detecting Magisk and other rooted apps (namely in your instance, Lucky Patcher).

Hope this explains it a bit better.

Definitely he deserves those “kudos” because that’s exactly what is “pull[ed]…off”!

And the “flash first the update followed by patched init_boot in one shot” will be automated for you that all it will take (at the last step) is just press of a button!

And that’s one of the most impressive things I like about the program vs. manually flashing – that it will keep from rebooting so you can patch the init_boot partition before loading up the OS (apps & services not having root popping up errors). That and the double-checks so it keeps users (me; but I don’t use PF because I like being hands on with the manual) from messing up.

Hope these answers helps!
[Google Pixel 7 Pro] vurtomatic:
Thank you for this!
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome. Cheers!
[Google Pixel 7 Pro] simplepinoi177:
Thought this was interesting...found it on Pixel's subreddit...I've been seeing it a lot on my Google feed about how they've "massively improved" OTA installation...

I wanted to dig into exactly how Google has massively sped up OTA installation in Android 14 beta QPR2. Here's what the Google team responsible for the crazy speedups told me [@ArtemR]​
[Google Pixel 7 Pro] justDave:
"All of these combined take a ~25 min install time down to around 6 minutes."

🤯 /s

Seriously though, will we see PixelFlasher upgrade times of 90 seconds?
[Google Pixel 7 Pro] simplepinoi177:
You know what....i thought the same thing honestly....

Not in that thread, but briefly read an article (like I mentioned, it's been popping up in my Google Feed for the past couple of days) that had the same observations and publishing of Google's announcement on it...and all I could think about was how poor people who do not have their bootloaders unlocked and cannot/do-not fastboot/sideload updates......

I did it once when my wife first insisted on not being rooted (right after manually updating mine) and it was hair pulling....

But at least it's more "seamless" for those who do incremental OTA's i guess....
[Google Pixel 7 Pro] justDave:
... and maybe it will inspire the good folks over at LineageOS.
[Google Pixel 7 Pro] badabing2003:
They should still be able to do full OTA (stock), if they enable developer options and USB debugging, just not factory or any flashing involving fastboot.
[Google Pixel 7 Pro] Lughnasadh:
You shouldn't even have to have USB Debugging enabled to sideload a Full OTA. As far as I know, when you select "Apply Update from ADB", adb is automatically enabled on most Pixel stock recoveries. I believe adb sideload ota.zip is also enabled by default. You would need USB Debugging enabled, however, to use adb commands while the OS is running, so in this case you would have to manually boot into recovery.

Of course, you can also just download the Full OTA.zip to your phone and install it from there in stock recovery as well without USB Debugging enabled.
[Google Pixel 7 Pro] niko26:
I can confirm. PIF v12.3 worked for a few days and it stopped working. V13.0 working fine again.

I don't understand the reason it has stopped. Does @chiteroman use one unique fingerprint for all instances? So if user A installs PIF and then user B installs it - it will use the same fingerprint, which then can be blacklisted by Google?
[Google Pixel 7 Pro] bird333:
Quick question. Can we still use platform tools 33.0.3 going from A13 to A14?
[Google Pixel 7 Pro] synesthete:
Yes, I flashed A14 with v33.0.3 and had no problems. I have read that the latest platform tools seems to be working well now, though. I just haven't got around to updating.
[Google Pixel 7 Pro] kornball:
I am sure this has been confirmed multiple times, but to add another data point: I updated to the Nov 2023 system images using platform tools 34.0.5 and Magisk 26.4 patched init_boot. I uninstalled USNF, installed PIF 13.1, and rebooted. After deleting Google Play Store cache/data, my device was once again certified.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Edited the SafetyNet instructions in the OP, replacing the two third-party Play Store apps with:

The Play Integrity pop-up that appears should say:

[MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]

Sometimes, clearing app cache and/or data for apps like the Google Play Store, GPay, Wallet and others (and then rebooting) after these steps may help pass SafetyNet as well.
[Google Pixel 7 Pro] Ghisy:
So I've had something weird happen to photos on my P7P: some of them got stuck on processing and only saved locally whenever my phone was online again much later. I did lose one (unimportant but still) picture a couple of days ago.

Isn't that odd? It never happened to me before. Is Google up to something there? I need to see if there's an updated version of the camera app, just in case. (although I'm probably on the latest stable from the Play Store)
[Google Pixel 7 Pro] phoinix_gr:
Integrity Check failed again.

Did the following for a fix:

1. Updated to https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v14.1

2. rm -f /data/adb/pif.json

3. reboot
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android Security Bulletin—December 2023 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] madmuthertrucker:
I don't get this :

rm -f /data/adb/pif.json

Where do I type it in at?
[Google Pixel 7 Pro] synesthete:
In the terminal. You will need a terminal emulator app. I suggest Termux.
[Google Pixel 7 Pro] madmuthertrucker:
I got it to run the command but I'm still failing cts.
[Google Pixel 7 Pro] UberNorse:
I'm imagining the monthly update will be uploaded tomorrow as I just had a slew of Google app updates from the Playstore.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've been assuming today as well.

Google Pixel Update - Dec 2023 - Google Pixel Community
[Google Pixel 7 Pro] roirraW "edor" ehT:
December (Android 14 QPR1) update:

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

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

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

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

December 2023 Feature Drop - Google Pixel Community
[Google Pixel 7 Pro] roirraW "edor" ehT:
The Full OTA zip is only available on the Russian language of the page that I've seen so far. Change the language in the upper right corner of Google's page. The Factory image is indeed available on the regular English page.

Edit: NOW it's up on the English page.
[Google Pixel 7 Pro] UberNorse:
******READ BEFORE UPDATING WITH ICONIFY INSTALLED OR ANY OTHER QS TILE MODS******

Just a heads up, flashing (Android Flash Tool) and rooting (platform-tools-34.0.5) went fine but when I enabled my modules I got a strange boot-loop I haven't seen before and recovery stated my data was corrupt. Re-flashed and it booted fine. Wasn't able to get to my modules to disable and the adb command didn't work to remove them. Re-rooted (Magisk Canary 26402) and instantly got the same bootloop since my modules were never disabled. Going to uninstall Magisk Canary, reflash new update and install Stable to see if that helps and will report back.

QS TILE SHAPE MODIFICATION POSSIBLY CORRUPTS SYSTEM ON THIS UPDATE. I USED ICONIFY TO DO SO BUT MAY NOT BE LIMITED TO ONE APP. DISABLE ANY QS TILE MODIFICATION IF USING ICONIFY WHEN UPDATING.

UPDATE 4 - Hopefully this is the last update. I can confirm that altering the QS tile STYLES with Iconify was the culprit. I installed nearly every module with no problems but the second I touched a QS STYLE setting it rebooted to recovery with the data corrupt message. So if you use Iconify and are updating to the last update I advise you disable, uninstall, or something similar unless you want to have this problem. I would also be very careful of any other QS tile modifications, I can't comment on them all as some may work fine I'm just warning you of my problem. I cannot confirm if this is the only bug or not so don't blame me I was the canary here.

I have opened an issue on GitHub with the developer.
[Google Pixel 7 Pro] Ghisy:
It's disgusting Google is intentionally blocking some features on the P7P in favor of the P8P... Sounds like something Crapple would do. I'm sure the P7P can do everything the P8P can. That's petty Google!
[Google Pixel 7 Pro] roirraW "edor" ehT:
NOW it's up on the English page.
[Google Pixel 7 Pro] Lughnasadh:
https://twitter.com/i/web/status/1732445279234736494
[Google Pixel 7 Pro] Ghisy:
Thanks for posting that!

I only use the color engine tweak to have the pitch black AMOLED theme in Iconify, would that be a problem?

I also have Better Internet Tiles for the Wi-Fi QS tile. I wonder if this could be problematic as well...
[Google Pixel 7 Pro] UberNorse:
I cannot confirm either way but I can say that I had made a few changes before touching the QS tiles and not a problem. I think it may be related to the QS tiles specifically but I'm not willing to put my name on that without further investing more time into it. For now, I just uninstalled Iconify totally as I have been at this since update dropped.

@Ghisy I just enabled AMOLED pitch black and used the color engine with no issues. I believe this is QS tile related for now. The color engine changed the QS tiles and had no issue. I had specifically tried to change the QS tile shape.
[Google Pixel 7 Pro] bradhoschar:
For all my T-mo peeps, just got the phone a couple hours ago, and already they unlocked me! Told them I was a 8-yr customer, and they had my phone unlocked in 30 seconds. If you haven't had service that long, feel free to try the ole 'going out of the country' trick and see if that works.

Good luck, and happy rooting!
[Google Pixel 7 Pro] Ghisy:
Dang, that's concerning! Anyone else tried Swift? I was gonna use it but not ready to transfer my apps just yet.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm glad I primarily use Goggle's cloud backup, but only use Swift for the few apps that Google doesn't restore the app data for.
[Google Pixel 7 Pro] Ghisy:
I actually @ the Swift Backup dev on his Telegram support group. We'll see if he responds.
[Google Pixel 7 Pro] mcj108:
In case you haven't got a reply yet, I can confirm Network Signal Guru does not work on the 7 at this time. It runs but all the screens are blank.
[Google Pixel 7 Pro] i5lee8bit:
Got my wife and I's Pixel 7 and Pixel 7 Pro's today. Haven't rooted yet, so here are the UNROOTED getprop outputs from each phone, attached.

Just in case checking OEM unlocking (but not yet actually unlocking bootloader yet) changes anything, I toggled it off and rebooted before pulling the getprop output. So it should be bone stock, unrooted.

I also haven't installed the Day 1 firmware update yet, so they're both onTD1A.220804.009.A2. Let me know if you want/need me to update to the new version and getprop again.

Btw @Displax, thanks for everything you do!
[Google Pixel 7 Pro] bosox284:
Unrooted and relocked the bootloader. Wasn't able to use su in adb shell but this was the output.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you. I plan on refining it a little more as time allows. Just got our phones in the last couple hours.

See below. I haven't tried it yet but plan to.

Indeed, I wasn't confirming in either direction. It's been so crazy busy in here and I insist on reading everything, so I was mostly just marking that I had seen it. Apologies!
[Google Pixel 7 Pro] badabing2003:
See this

I would also like to know the exact process.

boot_patch.sh extracts both the kernel and the ramdisk

You pull those to the pc and do this?

fastboot boot KERNEL ramdisk.cpio
[Google Pixel 7 Pro] stroke55:
I restored Classic Power Menu (apk and data) and Aquamail data & external data without any problem.
[Google Pixel 7 Pro] johnha:
Is anyone else getting "Device is not certified" for their Play Protection certification?
[Google Pixel 7 Pro] V0latyle:
Do you have the USNF Displax mod installed?
[Google Pixel 7 Pro] johnha:
Yes, I installed this version from Post #2:

Release v2.3.1-MOD · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Release v2.3.1-MOD · Displax/safetynet-fix

github.com

Force stopped Google Play app, then cleared storage/cache and restarted it. No joy...
[Google Pixel 7 Pro] stroke55:
Yes, not certified, I also used the mod-version.
[Google Pixel 7 Pro] johnha:
Interesting. I wonder if anyone is getting a "Device is certified" notice then.
[Google Pixel 7 Pro] rlewis312010:
I am not new to the rooting game but I last had a Pixel 3. Samsung is easy to use Odin but this is all new to me. Here is where I'm at and would like helo:

1. I have a 7 Pro I bought today from US Cellular. The only store that had them in town.

2. On the ride home I went in and toggled the OEM unlock! That wasn't an option on the VZN Pixel 3 lol so this shocked me. Immediately disabled updates in developer options and went into airplane mode.

3. I was able to get the bootloader unlocked and here is where I am stuck.

I have the A2 update, how can I safely update without losing my bootloader unlock? Will flashing the factory image somehow get rid of it? For my S20+ I couldn't update the bootloader to keep it unlocked.

Is there an easier guide? Some of the links in the OP cannot be clicked so I'm at "How do I get to the newest update safely?" Yes I reviewed these forums and glanced over like 20 pages in this thread. I already extracted what I need from the firmware to go forward with Magisk but it's actually the easiest part. On the warranty check link (very useful) it had "Fi" below the phone type so I'm guessing somehow I was given a Fi version? Or at least the phone is whitelisted so it allowed me to do it (thinks it's a Fi version). Crazy luck and here I am. Please be kind haha.
[Google Pixel 7 Pro] rester555:
The 73 MB OTA when you go into system update will essentially OTA the phone to .031 correct?
[Google Pixel 7 Pro] Annie the Eagle:
I am using MOD version of USNF and I don't have "not certified" but I also don't have "certified". The play protect certification is just not there anymore :)
[Google Pixel 7 Pro] bowtokrazy:
Quick question - If I unlock the OEM bootloader (for future use) , but do not perform any rooting / mod - will it cause any issues with OTA updates / apps (any consequences?) ... Or its best to leave it locked and just hard reset?
[Google Pixel 7 Pro] NepoRood:
You, as the user, decide when to unlock and re-lock your boot loader. Be careful of using the online flash tool, there is an option to relock after flashing, but it's kinda hidden so shouldn't be an issue
[Google Pixel 7 Pro] UberNorse:
Have not been able to dig around the new QPR1 update due to issues but right off the bat I noticed this. A mode to basically protect your apps and data while phone isn't in your possession. Also a battery diagnostics mode.
[Google Pixel 7 Pro] Ghisy:
Awesome, thanks for confirming! 👍
[Google Pixel 7 Pro] Fishawy:
Thanks for the heads up, I'm currently using both UI Roundedness and QS Tile Size. Before updating, are you able to pinpoint which one was the culprit (or both)?
[Google Pixel 7 Pro] UberNorse:
I did not, no. It's actually the QS panel tile style that gave me an issue. I can't comment on the other mods as I spent hours tracking just this one down and am hesitant to enable anything QS related. 😂
[Google Pixel 7 Pro] Fishawy:
Understandable. I'll probably just play it safe with Iconify.

Just in case, you only rebooted to bootloader and reflashed, right?
[Google Pixel 7 Pro] UberNorse:
Yes. I would allow it to reboot and hold power and vol dn to enter fastboot mode and used Android Flash Tool to re-flash
[Google Pixel 7 Pro] Fishawy:
Has anyone else had similar problems with Iconify on the December update?

Just trying to double-confirm and isolate.
[Google Pixel 7 Pro] Ghisy:
@roirraW "edor" ehT, did you update to December stable? Any problem with the latest Better Internet Tiles beta?
[Google Pixel 7 Pro] UberNorse:
It's actually stated in the Iconify thread, https://xdaforums.com/t/app-root-12-0-iconify-customize-boring-android-ui.4641061/ that it causes this exact issue on the QPR1 beta and I guess they still haven't found a fix for it.
[Google Pixel 7 Pro] Fishawy:
Wow thanks for the confirmation. Definitely not doing this until it's fixed.

Thanks again.

All is well here. December update + Better Internet Tiles beta.
[Google Pixel 7 Pro] UberNorse:
No problem, I completely missed this report on the bug and even opened a issue on GitHub which I assume now was probably already being handled. It never even crossed my mind to check first. Hopefully they get it worked out but I'm okay without that specific mod for now. I do like it though!
[Google Pixel 7 Pro] Ghisy:
From what I've read, they need to be able to access the source code for the December update to fix it. I don't know if Google has made it available yet.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I haven't updated yet. I might later today, if I have time. Glad to hear that @Fishawy has reported no issues.

Edit: I did not have time to update yet. Maybe today or sometime this weekend.
[Google Pixel 7 Pro] Ghisy:
I just updated, things went smoothly!

I just can't get the Play Store to be certified again for some reason. I usually hide Magisk again after updating then delete data for the Play Store and it becomes certified. Not this time apparently. No big deal but it's odd.
[Google Pixel 7 Pro] vurtomatic:
Do we know if it's specifically Iconify or does PixelXpert cause problem too?
[Google Pixel 7 Pro] weriwd:
I initially intended to wait for the December update to flash over the currently installed one (October) with Android Flash Tool. However, I'm currently hesitant about proceeding because I want to avoid losing my root access and potentially experiencing a bootloop or any worse... Any guidance or advice on how to navigate this situation would be greatly appreciated. It's worth noting that I received this notification approximately 25 days ago, and I haven't restarted my device since then.
[Google Pixel 7 Pro] UberNorse:
I'm using Pixel Expert 3.2.0 but I haven't modified anything QS related with it.
[Google Pixel 7 Pro] kornball:
Are you using PlayIntegrityFix v14.2? I'm hoping to update to the December system image too. I am currently on v13.8, which obviously no longer works.
[Google Pixel 7 Pro] Ghisy:
I'm still on v13.8 as well. Maybe I should update to v14.2? To be honest, this whole cat and mouse game has been annoying.
[Google Pixel 7 Pro] synesthete:
I haven't had time to update yet, but it is my understanding that you might need to find and supply your own fingerprint with the latest PIF module.

This post has some info about doing that:

🔧 [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 7 Pro] pp085ster:
I have both PixelXpert 3.2.0 and Iconify 6.6.0 and have had no issues updating to the December update without deactivating any modules. I don't mess with QS settings anyhow, so no worries for me there.

With PIF 14.2 you don't need a custom fingerprint, I am currently using and passing 2/3 without that.
[Google Pixel 7 Pro] synesthete:
Thanks, good to know! I did realize that my current setup has eventually failed and wallet isn't working (last version of PIF) as a a few days ago. So maybe the custom fingerprint helps ensure more stability. I know some others have their device integrity fail after working for a while.
[Google Pixel 7 Pro] UberNorse:
The real stability IMO is with @osm0sis' fork and a custom mined fingerprint. I got my first one last week and haven't had to update the module nor my json file.
[Google Pixel 7 Pro] Homeboy76:
I'm not sure the Android Flash Tool will allow you to update and keep root. Try @badabing2003 Pixel Flasher. I think you can update your firmware and keep root using his tool.
[Google Pixel 7 Pro] weriwd:
Thank you! I will try later today using the Pixel Flasher. Is there any chance the device could get stuck in a bootloop if the auto update is potentially installed in another slot A/B?
[Google Pixel 7 Pro] Homeboy76:
I don't think you'll get stuck in a bootloop if you take the Automatic system update. AFAIK, the Automatic system update is installed to the inactive slot. Example: Your active slot is A the Automatic system update will install to your inactive slot B.

You will lose root because it will flash the stock (unpatched) init_boot.img to the inactive slot.

However, several XDA members are reporting not ...disabling or uninstalling any visual mods like iconify and Project Themer. Specifically, anything that modifies the quick settings... will cause bootloops.

So, if you're rooted disable all modules before before updating. You never know what modules a new firmware update will break.

I think Pixel Flasher also disables modules.
[Google Pixel 7 Pro] I7210I:
Where I can find the latest image? at the link at the first thread it os not available

I mean here for the december for pixel 7 pro

Thanks
[Google Pixel 7 Pro] Homeboy76:
This is the link in the OP where the latest image is:

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

This is your link:

https://developers.google.com/android/images?hl=he#cheetah

Why did you change the link in the OP or post a link different from the one in the OP?

Maybe you need to set the language to English.
[Google Pixel 7 Pro] roirraW "edor" ehT:
PixelXpert removed all theming-related options when they released I think it was 3.0.0 Stable or 3.1.0 Stable, probably due to them keeping up with the QPR1 Betas, so they knew what was coming down the line as far as compatibility difficulties.

Besides @Homeboy76's excellent advise, just a note that navigating the situation with updates is no different no matter which old firmware you're on. i.e. Updating from October -> December is just as easy as updating November -> December.

As far as keeping root, I just use the Full OTA Zip method outlined in Post #2. I don't technically keep root - I reapply it, but it all ends up just the same as if I did.

You probably have to change the page language, possibly to English. Google is known for sometimes providing the updates on some languages before others. This time, actually, English didn't come first, but within an hour or two, the English page was updated.

You can use Chrome or another browser that automatically translates the English version of the page to your language, if necessary, and you should see December's firmware then.