yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] simplepinoi177:
@JoshuaUB78 , Just a bit of explanation why it isn't rude to not (or a good idea for users to) publish the fingerprints that get them to pass....

because this is what chiteroman had been doing in Play Integrity Fix, and with tens of 1000s of users all using the same fingerprint, it was easy for Google to notice and they had to do was ban that single fingerprint and everyone would fail. So publishing publicly what fingerprint one uses is just exponentially increasing the chance of Google seeing it (because even if Google themselves don't see it, other users might and start using and passing it around and having it get on Google's radar) and it could potentially be banned in no time....

Then everyone has to start from scratch once again....
[Google Pixel 7 Pro] phoinix_gr:
Couldn't have said it any better.
[Google Pixel 7 Pro] JoshuaUB78:
Yes, I understand the specifics for not giving away the fingerprint. I was not clear in my wording. The intent of my earlier question was more along the lines as to what process/steps were sucessfully used?
[Google Pixel 7 Pro] phoinix_gr:
You can DuckDuckGo (not google :) ) something in the lines of "script android pif.json" . First page should have the information you need.
[Google Pixel 7 Pro] ikhelladi10:
Hello,

I have successfully rooted phones in the past, including my current Pixel 7 Pro. However, even though I'm following the steps given perfectly, I still fail the device check. I was told it was because of some fingerprint stuff, however, I'm utterly lost regarding that. I don't know what it is and even following steps, I don't know how to perform such a task.

Does anyone have a simple way of passing device check?

Thanks
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi, welcome. You've looked at the last few posts (including on the previous page)?

Also, just making sure you've looked at the SafetyNet section of Post #2.
[Google Pixel 7 Pro] ikhelladi10:
Yes, I have checked the last few posts, that's how I knew it had to do with fingerprints.

I have checked the post #2, that's actually the guide I followed, which failed.
[Google Pixel 7 Pro] simplepinoi177:
try this guide, it's not concise, but it has all the foundational information you would need to understand it all (especially if you need it in plainer-speak)...

How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #2's SafetyNet section:

Also for reference, @simplepinoi177's thread How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)
[Google Pixel 7 Pro] Schroeder09:
Does manually flashing with ADB as described in post one still work with the lastest January update?
[Google Pixel 7 Pro] simplepinoi177:
i don't know if it's just semantics, but just want to confirm so you don't accidentally inadvertently go about it the wrong way....

ADB is when you sideload (not flash) and it's the OTA image file; flashing will be the Full Factory image file....

I mean, you could go about trying to flash the OTA (instead of sideload) and it just simply wouldn't work, but just in case to save you from going through a process because absentmindedness...
[Google Pixel 7 Pro] Lughnasadh:
From Mishaal Rahman:

"Maybe hold off on applying the January 2024 GPSU if you have a Pixel phone and have multiple user profiles? Seeing a lot of reports about internal storage access issues, similar to the ones from a few months ago."
[Google Pixel 7 Pro] Lughnasadh:
https://twitter.com/i/web/status/1749892981232943138
[Google Pixel 7 Pro] simplepinoi177:
dang...what is it about multiple profiles on Pixels....

I can't recall, was it resulting in any hard-bricks the last time? I remember it was like a whole month before the issue was fixed (was addressed for weeks though)
[Google Pixel 7 Pro] Lughnasadh:
"As always with these feature drops, they’ll begin rolling out to some Pixel hardware owners as early as Thursday, with others following “over the next few weeks.”

Google’s latest Pixel feature drop adds Circle to Search, Magic Compose, and more

The Pixel 8 Pro’s thermometer can now take your temperature.

www.theverge.com
[Google Pixel 7 Pro] simplepinoi177:
Google Pixel phones unusable after January 2024 system update

Google Pixel smartphone owners report problems after installing the January 2024 Google Play system update, being unable to access their devices internal storage, open the camera, take screenshots, or even open apps.

www.bleepingcomputer.com

@roirraW "edor" ehT maybe adding this to the OP and/or title and/or your usual PSA message when something potentially damaging happenings
[Google Pixel 7 Pro] antoniro:
Hello everyone!

I am having an issue after rooting: I followed the Full OTA Zip method to root my Pixel 7 pro, and everything worked well. However, from the instructions, it seemed that by using that method, I would be able to boot on the other slot, and not have root.

My issue is that when I tried setting the active slot to b, then boot, I get the error message saying that my device is corrupted. When I press the power button to continue, my phone gets stuck on the Google logo. After holding the power button to force shutdown the phone, then botting into fastboot again (power + vol down) and changing the slot back to a (the rooted one), the phone boots up without any issue.

Secondly, I followed all the steps, but still can't pass the integrity check. I'm only getting the basic one.

My goal is to be able to boot from both slots (one with root, the other without root). Any help would be appreciated. Thanks!
[Google Pixel 7 Pro] Ghisy:
Do we have to wait for these to drop whenever Google feels like it? I mean, there won't be a factory image to flash to get them on the P7P? Their communication isn't clear.
[Google Pixel 7 Pro] badabing2003:
Did you flash the OTA zip twice in a row?

You have to apply the same OTA on both slots for it to work.

Did to the nature of OTA which always flashes to the other slot, you don't have to change slots between the two flashes. Just do it twice.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Since it's a Google Play System Update, yes, we have to wait for Google to push it to us. As far as I'm aware, these aren't available via any other method.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Done, thanks. Does it affect the Pixel 6 Pro, too?
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, I've seen it reported on Pixel 5, 6, 7, 8, and Fold series devices.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! Added to my 6 Pro thread, then, as well.
[Google Pixel 7 Pro] antoniro:
Thanks for pointing this out. I don't think it was mentioned in the guide, or maybe I missed it...

So now I have more questions. I already transfered everything over from my old phone, and it took about an hour to do so. If I sideload the OTA again, will I lose all my data? Also can I just follow the instructions on how to update and re-root to be able to re-apply the same OTA twice?

Thanks
[Google Pixel 7 Pro] Ghisy:
Did Google fire all of their QC team members or what? 🤔

This should not happen...

Ah, it sucks! 😕
[Google Pixel 7 Pro] roirraW "edor" ehT:
Starts with step 13:

The rest (except fastboot reboot at the end) is optional, if you want to update the other slot.

Actual OTAs and sideloaded OTAs will never wipe your phone data.

If you're still having the corruption issue, temporarily flash a boot.img from an OLDER firmware update to your current slot. Then try to boot it. It won't boot, but that's not important. After it won't boot, then re-flash the correct boot.img.

Since you manually changed slots at least once, I would recommend sideloading the OTA twice again instead of trying to figure out if you need to do both slots or not. When you sideload the OTA, it changes slots immediately (before updating), just like an actual over the air update does.

There are at least 2-3 reasons why you have to sideload the same OTA twice to be able to "dual-boot", so to speak, but those details aren't really important right now, but if you want to know, I'll detail them.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I agree. Especially after it happened once already, although it's possible the under-the-hood details are different enough. I doubt it, though.
[Google Pixel 7 Pro] simplepinoi177:
sorry....I meant to post that in the Pixel 6 thread too (as I did in the Pixel 8 Pro one), but I couldn't find it....didn't occur to me that I should've checked Pixel 6 PRO....

EDIT: scratch that....I

did

post in the P6P...!

But glad you are posting your very vital guides...!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've had plans to update my Pixel 6 Pro thread OPs to be the same as the 7 Pro and 8 Pro ones for a year or more, but just haven't gotten around to it. :D
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, according to Google we'll get the features through Google Play Store, which is good since they stopped the January Google Play System Update until they fix their shenanigans...

Do I have to update my phone to receive these new features? Why am I being prompted with multiple updates?

For this Feature Drop, updates will be available in-app only through Google Play Store. The regular February software update will begin rolling out to Pixel users in early February.
[Google Pixel 7 Pro] avid_droid:
Maybe the update would constitute those of us on locked bootloader to go through Google directly for a swap out of phones instead of paying a warranty through carriers like VZW to get a replacement being that it is a Google error? That's it I'm sabotaging my phone haha
[Google Pixel 7 Pro] simplepinoi177:
I tried doing this when mine broke when I was able to get, using a loophole, a global variant under Verizon on my Pixel 2 XL... Google will just send back a VZW carrier variant back (it's what they did on mine; i'm betting they check the IMEI and send the corresponding variant)... 😩😭
[Google Pixel 7 Pro] Ghisy:
I was gonna post that: https://9to5google.com/2024/01/25/january-pixel-feature-drop-update/

Now I wonder if spoofing the Pixel 8 on my P7P would unlock the features, hmm... 🤔
[Google Pixel 7 Pro] avid_droid:
Dang it. It's okay. Waiting to pay off the phone,switch carriers cause vzw is adding the $4 to each line(I have the top tier plan but no 5G here in Alaska), and buying unlocked direct from manufacturers.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Release Iconify v6.7.0 · Mahmud0808/Iconify

Iconify v6.7.0 has arrived! It has the following new changes: Feature Changes: QS Panel Tiles: Fixed bootloop on android 14 QS Text Color: Fixed bootloop on android 14 Icon Shape: Added for...

github.com

Who is going to be the first to test and report back? :)
[Google Pixel 7 Pro] sawdoctor:
Don't think it's compatible with QPR2 beta unfortunately, can't install the necessary overlays still
[Google Pixel 7 Pro] Ghisy:
I saw the update almost immediately when it was posted on TG but I'm not going first! 😜
[Google Pixel 7 Pro] simplepinoi177:
Been waiting for this!

I'll see if I want to be brave....I hate re-installing all the magisk mods. But according to @Lughnasadh , there's a way if you give adb su properties or shell properties or something where I could simply remove just the iconify module specifically/only....I'll have to look into it if I go be the test dummy....
[Google Pixel 7 Pro] BunnyPig1:
I just tried this on December update and it's working flawlessly!

Can't give any info on QPR2 Beta but QS Tiles and the rest is working fine.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google starts rolling out Quick Share on Pixel, non-Samsung devices

Following the CES announcement at the start of this month, Google is now rolling out Quick Share on Pixel and other non-Samsung devices.

9to5google.com
[Google Pixel 7 Pro] rester555:
I think your device will be google play store uncertified since you have the bootloader unlocked. So some apps will not show up in the store.
[Google Pixel 7 Pro] johnha:
there are many steps.. but I'll take a stab from memory:

- turn on developer options

- turn on unlock and debugging from dev options

- adb reboot bootloader

- fastboot flashing unlock

- verify which firmware you're running and download that one (unzip it and unzip the embedded zip inside)

- copy the init_boot.img file to your phone: adb push init_boot.img /sdcard/

- install magisk on the phone (get it from the github repo's releases section)

- open magisk and install and patch file, choosing the init_boot.img that's on the phone

- magisk will create a new file in /Downloads, copy that file down to your computer: adb pull /sdcard/Downloads/magisk_patched_file.img .

- adb reboot bootloader

- fastboot flash init_boot magisk_patched_file.img

- fastboot reboot

- download the safetynetfix .zip file mentioned above to your computer

- adb push that file to your phone

- open magisk and install that file as a module

- in magisk turn on Zygisk and Enforce Denylist (you may need to reboot here)

- in magisk Configure Denylist and add your apps that need it

- in magisk find Systemless Hosts and install it if you need it (for things like Adaway)

- umm.... hopefully I got all the steps, hope this helps
[Google Pixel 7 Pro] johnha:
Bummer. Works perfectly on Pixel 6 Pro though - it says certified.
[Google Pixel 7 Pro] rlewis312010:
Right, it's that flashing part with the factory firmware to update part. I tried to unzip the folder and literally all of the files into that platform folder. It says the .bat command isn't recognized. The rest I feel perfectly fine with. There is a tool to update but then I need to basically re-root from what I'm reading right? It sounds dumb but I'm trying to get through that one step lol. Really dumb.
[Google Pixel 7 Pro] bowtokrazy:
that sucks, if that is the case, I will leave the bootloader locked. Don't want to deal with uncertified play store issues
[Google Pixel 7 Pro] johnha:
not sure which part exactly you're referring to
[Google Pixel 7 Pro] johnha:
not sure you can root with the bootloader locked, so... wrong thread?
[Google Pixel 7 Pro] V0latyle:
Shouldn't necessarily be an issue but we may be dealing with something "new" on the P7. I'm still on a P5 so I can't test
[Google Pixel 7 Pro] rester555:
Some people have used a modded magisk file in this thread from a user named named Displax where they can install all the apps even though app store says not certified... It's post #291... Post #291 in this thread
[Google Pixel 7 Pro] bowtokrazy:
Not wrong thread, I am just not going to root at this time, was planning to unlock the bootloader for future use, but if unlocking bootloader causes issue with play store - i rather not deal with it at this time
[Google Pixel 7 Pro] johnha:
cool, thank you for your comment - reduces my discomfort
[Google Pixel 7 Pro] rester555:
I shouldn't have installed the OTA... **** takes FOREVER
[Google Pixel 7 Pro] rlewis312010:
I

I have A2, I'm trying to get to the latest build without losing the bootloader unlock. Can I simply use that Google Flashing tool to get to the version without messing anything up? Then I would follow the other steps. Or, do I need to go through platform tools and try to flash with commands? That's where I am really stuck. It's best to be sure than speed through and mess something up.
[Google Pixel 7 Pro] Namelesswonder:
Click the edit icon once you have selected a build.

Then untick wipe device and untick lock bootloader.

Done.

If you use fastboot then you will never have your device locked unless you somehow manage to mash on your keyboard and perfectly type out fastboot flashing lock and in this episode also manage to bump your device to hit up on the volume button and then hit the power button to confirm the lock.
[Google Pixel 7 Pro] Namelesswonder:
@roirraW "edor" ehT

Also a little tip for anyone trying to enable OEM unlocking on a device and it is grayed out, you can force the phone to check for eligibility by connecting to the internet in whatever way, going to the dialer, and dialing *#*#2432546#*#* (CHECKIN).

You should receive a notification from Google Play services with "checkin succeeded" and OEM unlocking should be available immediately if the device is eligible.

Google account not needed, SIM not needed, no other setup required. Works on completely-skipped-setup-wizard. Just need to make sure to connect to the internet and select the connection as metered to avoid any updates.
[Google Pixel 7 Pro] Paz9:
Device uncertified in play store but apps still appear, probably some bug.

Also wallet works and banking apps
[Google Pixel 7 Pro] MetroWestMA:
I remembered when I rooted my P6P I could still install and run everything and someone told me that it takes a few days and your device will become certified again. Mine was certified 3 days later and as someone else mentioned installing Netflix and other stuff was never an issue like it was on recent OnePlus phones like the 10 Pro.

I don't think it is not being play store certified that causes the apps to disappear it is the modded USNF by Display that fixed that.

My P6P only has basic integrity and an unlocked BL and it is still play store certified.
[Google Pixel 7 Pro] Namelesswonder:
Something a little odd I noticed in the bootloader after unlocking it and it hasn't gone through any updates yet, it appears there is no radio installed on the second slot on my phone? Shows unknown on the screen too.

$ fastboot getvar version-baseband
version-baseband: unknown
Finished. Total time: 0.001s

Extremely odd, I didn't reboot into the second slot, but when switching slots on the fly on the Pixel 6 it would report just fine. Bootloader version still reports on the second slot.

Didn't check much further, was kind of sketched out about this and immediately flashed the firmware images onto both slots. I didn't want to take any chances with a brick.

Also it's imperative that everyone be using platform-tools 33.0.3, as 33.0.2 does not flash the kernel.

Writing 'boot_b' (bootloader) unable to update boot image: use unmerged...

Flashes fine on 33.0.3.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm not positive what you mean by "Some of the links in the OP cannot be clicked". If you can give me a particular example, that might help me make the OP clearer. Anything that is actually a link is clickable. Text that is a link doesn't have an underline on them until you hover over them, and for me, at least, the underline is blue when it appears.

Some of the things I list with white underlines under them aren't links. I'd be happy to take suggestions for how to make it clearer. Please let me know your thoughts, and I'll be more than happy to change the style of the OP.

I always opt to flash the latest factory image zip instead of taking OTAs, it's so much faster.

That's the one I link to in Post #2. It was also necessary on the Pixel 6 Pro in recent months.

There's nothing you could do that would cause your bootloader to be re-locked other than manually send your phone the command:

fastboot flashing lock

Or maybe I misunderstand what you're saying. I always unlock the bootloader the very first thing, and then I use the factory image zip to update the phone to the latest build.

Yes, if you've toggled OEM unlocking and [USB debugging] on and make sure the latest adb and fastboot commands work fine with your phone / have the USB drivers installed.

Thank you. I'll make a note of this so that tomorrow I can put that somewhere in the OP. Much appreciated!
[Google Pixel 7 Pro] wire55:
Getting CTS profile match fail as well as meets_device_integrity fail on 7 pro. Followed guide to a T, tried clearing data/cache with wifi on/off, data on/off, followed by reboot and still get these fails. Anyone else had this issue and have a fix?

Edit: was a little behind on reading. See that it's normal as of right now for those to both fail. Forgot things are different coming from Pixel 6a. Sorry for the uneducated post.
[Google Pixel 7 Pro] Ghisy:
@roirraW "edor" ehT

Hey, you mentioned you're using PFNext, right? I installed it but the instructions on the GitHub aren't clear to me. If I try to open the GMS app, I only get notifications (including one that says there is 0 profile). What am I missing here?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm using PlayIntegrityNEXT - that's what you're talking about, right? GMS app? I haven't had to use PlayIntegrityNEXT's "Fp Downloader" app yet, and I'm certified, so I'm a little paranoid to even launch it.

I notice now when I look for the PINext module "Now this module is EOL, use playcurl instead 😎", and then the playcurl entry links to instructions, and those instructions say:

So, it looks like I should update my OPs. I had originally installed first the PINext module, and then the curl one after, which is working for me at the moment, but it appears we're supposed to just use the app that comes with the PlayCurl module when needed, along with @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix).
[Google Pixel 7 Pro] Ghisy:
That's the one I'm using: https://github.com/daboynb/PlayIntegrityNEXT

So yeah, same. I'm passing basic and device integrity but Wallet still says my phone doesn't meet security requirements. Odd.

I don't care that much about it but just curious if it can work!
[Google Pixel 7 Pro] roirraW "edor" ehT:
My Wallet's working. How long have you had PINext installed? Play Store directly says Certified, as well?
[Google Pixel 7 Pro] Ghisy:
I just installed it today, maybe I need to wait?

My Play Store says Certified, yup.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, possibly wait and/or yet another reboot. But ultimately, it can take some hours.
[Google Pixel 7 Pro] simplepinoi177:
yea... you can either wait 48 hours, or clear data on things, but it removes all the cards so you'd have to re-add & re-verify each card...
[Google Pixel 7 Pro] Lughnasadh:
For those affected by the January GPSU shenanigans (storage issue), here's a fix (without causing data loss) Google has posted:

Issues accessing storage after January Google Play System update - Google Pixel Community
[Google Pixel 7 Pro] roirraW "edor" ehT:
Everyone comment about that in a constructive way on the https://support.google.com/pixelpho...stem-update?hl=en&sjid=9118382133164728040-NC article before they lock it down.
[Google Pixel 7 Pro] Lughnasadh:
Interesting....and kind of funny...

(Noticed the free version hasn't been updated in a while though)

https://twitter.com/i/web/status/1753205544205090886
[Google Pixel 7 Pro] skyrood2:
so what should i install, usual or A1?
[Google Pixel 7 Pro] roirraW "edor" ehT:
It depends. Are you using a Verizon or Verizon-based carrier, or on a different one? "Global" is what we call the builds that aren't aimed toward a particular carrier, so "everything else".
[Google Pixel 7 Pro] skyrood2:
got it, thanks!
[Google Pixel 7 Pro] vurtomatic:
Thank you! My Wallet stopped working and I was gonna deal with it with the Feb update but this turned out to be pretty straight forward! Wallet works again after a reboot.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! You're welcome, thanks for reporting your experience.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Magisk Beta (

not

Stable) v27 released:

Release Magisk v27.0 · topjohnwu/Magisk

[Zygisk] Introduce new code injection mechanism [Zygisk] Support new signature introduced in U QPR2 [SEPolicy] Update libsepol to properly set some policy config bits [MagiskBoot] Support compressi...

github.com
[Google Pixel 7 Pro] B00mB00mBang:
I'm a little behind in terms of figuring out the technical differences between PlayIntegrityNext, PlayIntegrityFork and original @chiteroman Play Integrity Fix. Can someone share the link if it's been discussed somewhere? Pixel 7 Pro guide states to use the fork but the link points to @chiteroman