yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] wangdaning:
I was not thinking of this in particular when I did it, or I would have got some any relevant stuff. What I did out of box was to turn on unlocking and run the flash-all.bat. After skipping through setup, I rebooted to bootloader. It was slot a so I switched to b and ran flash-all again.

Also, just to clarify, the reason I flash to both slots has to do with custom roms. There are times when certain bugs might pop up if you have only flashed one slot to the correct version of android and it is really hard to know. Best is to have both run through a complete install.
[Google Pixel 8 Pro] badabing2003:
Thanks,

Your steps confirms that there was bootloader on B, which is very good to know.

Maybe like you suggested, bad batch of new phones.

No hard evidence to associate the bricking with missing bootloader.
[Google Pixel 8 Pro] simplepinoi177:
Yeah...I figured it was something like that....just wanted to point it out and/or clarify (in case I was missing something)...

Yeah, that's why I tried to preface the quotes by saying you were speaking on it early on after the Pixel 7 released. I quoted all of those more to display the whole --slot-all, how from the factory one slot is unpopulated/unloaded/unbootable, and how important it is to slot-all it to both at some point if you've only flash-all'd the Full Factory so you can have a workable slot to fall back on (without needing to further download images and flash to get the device up and running again); more than it was to speak on how Full OTA is a better choice than Full Factory....

But as always, it's appreciated you keeping things straight and also coming on here to explain & enlighten this all for me/us!
[Google Pixel 8 Pro] wangdaning:
I still think something was done wrong if someone has a perfect device from factory and simply switching the slot bricks it. It seems more of a mistake from google than an intended thing. I did the same thing on both my 7 pro and 8 pro, update with factory image, switch slot and update factory image. I never found the inactive to be unbootable. I have also never used ota, they are not available here and downloading an ota vs factory img seems strange.

I am not knocking anyone or their experience, but there is something weird in this whole situation.
[Google Pixel 8 Pro] HipKat:
When you flash the Factory Image, which is what I had always done on the P7P, do you flash both slots or just the inactive?
[Google Pixel 8 Pro] Homeboy76:
I missed this the first time I read it.
[Google Pixel 8 Pro] Cares:
Just starting today my Google Pay says my device is not secure to use it. But I pass safety checks. Any ideas? Or are there updates to the modules? I haven't updated to November patch yet.
[Google Pixel 8 Pro] simplepinoi177:
Yea...Google just changed something on their end (last 36 hours) and gotta use the newest(I imagine Displax will release something soon enough) root detecting circumvention -- Play Integrity Fix
[Google Pixel 8 Pro] Cares:
I see there was something updated 4 hours ago. Does this work now?

I'm passing device integrity when my previous setup didn't. I can't test payment at the moment though.
[Google Pixel 8 Pro] simplepinoi177:
Probably just gotta clear cache all the requisite, involved services; Play Protect Services, Google Framework, Play Services, Play Store, Wallet, GPay . If not enough, then clearing data as well -- but this will also clear the cards from Wallet that you'll have to re-enter....

I read this wrong....I read it as "I can't ... payment at the moment though..."🤦‍♂️
[Google Pixel 8 Pro] CarlosTime:
Guys, I'm trying to get the image or ota for UD1A.231105.004.... when I go to the site, I only have the files for the October update... you have the update up to date from November you?
[Google Pixel 8 Pro] simplepinoi177:
Make sure you are looking at the English/US site....there's a known issue when viewing the page in another language setting
[Google Pixel 8 Pro] djmcnz:
Sorry for the delayed reply, as others have stated in the meantime you don't need a working bootloader to bootstrap into fastboot mode, and from there you can recover.

People who are RMA'ing new devices fit into 3 categories IMO:

Hardware error

RMA is actually unnecessary but they don't know how to fix it

They've broken something and then royally screwed it up trying to fix it

People just need to forget about the second slot unless they're a real player and know what they're doing, and respectfully, if they're asking how A/B works, then they don't know what they're doing.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I disagree. A certain amount of being proactive is healthy; we all start with zero knowledge, and it has to come from somewhere.

Not that your post is targeting this, but I'm happy if our advocating for users to make sure their second slot has at least a bootloader on it, and preferably the same full OTA as the first slot so that it can actually fully boot if the worst happens, leads to education about being prepared.

After all, I've certainly had the worst happen on my phone while I was out, about, away from home and computers, and anything that can help prevent what is a mild inconvenience for some of us, from happening to those who it's a huge panic moment for, is worth it.

There are all sorts of different levels of knowing what we're doing. I'm not at the top, but I'm not at the bottom. I'm somewhere in the middle. I make no assumptions about anyone's knowledge.

My instructions should be able to be followed by anyone who is willing to read them, and take time to ask questions first, if they have any. And if they mess up, we'll help them with that, too, as much as we can.

The more help we provide before it's needed means less, more complicated help that would be required after the fact.

I can distinctly separate all the things I learned before I got my Pixel 6 Pro two years ago from after. I learned a lot, but the most talented users here on XDA have helped me really be more educated on so many detailed aspects of Google Pixels. That's what XDA is all about, in my opinion; learning and helping.

No rant intended, so I hope you don't take it that way. 😁
[Google Pixel 8 Pro] Kalaskas:
Since some days ago cant use tap to pay on Google wallet.

Working fine until then.

In yasnac integrity check is like always didnt changed , CTS pass, basicintegrity.

Using this mod:

SafetyNet Fix Mod 4.0 Mod 1.3

There is something i can do so i can use tap to pay on Wallet??
[Google Pixel 8 Pro] roirraW "edor" ehT:
Take my word for it that every other post yesterday and today is about this. Google PlayIntegrityFix and use the latest version (12.2 as of the last couple of hours). When you install it, it will automatically uninstall USNF v2.4.0 Mod 1.3.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Added to Post #2:

As of November 11, 2023, this is the only one that will work @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix)

Spoiler content hidden.
[Google Pixel 8 Pro] Sasaiber:
After installation, I still can’t add a card to Google Pay((And the check is stuck
[Google Pixel 8 Pro] roirraW "edor" ehT:
Try those ^ yet? Sometimes if you just wait a bit, too (after trying those things), it'll start working.
[Google Pixel 8 Pro] Sasaiber:
I tried it, it’s already working) Thank you, I added the card)) All that’s left is to try to pay
[Google Pixel 8 Pro] Ghisy:
Quick question: which model of the Pixel 8 Pro is sold by Google in the US? Is it the GC3VE or G1MNW?
[Google Pixel 8 Pro] roirraW "edor" ehT:
My Settings / About / Regulatory labels shows my 512 GB (was thinking of my P7P) 1TB Unlocked Pixel 8 Pro I got direct from the Google Store as model G1MNW
[Google Pixel 8 Pro] Ghisy:
Thanks! So I guess GC3VE is for Europe/rest of the world then.

I'm asking because it seems like there might be an interesting discount on the P8P in the US for Black Friday and I'll be there for a few days. I can swing by one of the Google Stores in NYC and check it out. I need to find out which 4G/5G bands my carrier is using in Europe.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome and good luck! I hope you can get a good deal and find out about the bands. I'm a little jealous you might go to a Google Store. :)
[Google Pixel 8 Pro] Ghisy:
Thanks bud! You're gonna be more jealous: I've already been to both in NYC (the one in Manhattan and the newest one in Brooklyn). They're nice but it's a lot of wasted space IMO.

Anyway, on the lookout for a bay blue 256GB P8P. I know I shouldn't... Let's see how much it will be (of if it is at all) discounted.
[Google Pixel 8 Pro] webleeper:
Does anyone on the latest Magisk stable and latest Android beta(QPR2 beta1) have Zygisk enabled and get stuck on "Pixel is starting" on a reboot after flashing Magisk Patched Init_boot?
[Google Pixel 8 Pro] badabing2003:
You have previously enabled modules? or is this your first patching hence no modules yet?
[Google Pixel 8 Pro] Lughnasadh:
No problems here. Seems Google changed some things so that Substratum themes and Iconify are no longer working on this build. So check your modules, as badabing suggested.
[Google Pixel 8 Pro] webleeper:
I had enabled modules, extracted the init_boot.img, patched it, upgraded to the latest beta, fully booted up the phone, rebooted to bootloader then flashed the patched image. Rebooted and got stuck at Pixel is starting.

Disabled zygisk with the following and was able to boot up normally

.\adb.exe shell su -c magisk --sqlite 'update settings set value=0 where [key]="zygisk"'
[Google Pixel 8 Pro] badabing2003:
So you're lucky, it had reached the point of loading adb and making root available,

just disable suspect modules, enable zygisk and reboot.
[Google Pixel 8 Pro] Paz9:
Can someone confirm whether Google assistant works ?

Mine says not compatible with the device rooted with pif

edit: is it because PIF spoofs the phone to report as Zenfone?
[Google Pixel 8 Pro] roirraW "edor" ehT:
It sure looks like the next Google Pixel phone will support Qi2 as certification arrives

Qi2 certification has arrived, and with it, the likely support of the magnetic charging standard on Google Pixel devices.

9to5google.com
[Google Pixel 8 Pro] Ultimoose:
Flashed the November update painlessly and without drama. Such a ridiculously amazing piece of software. :) (PixelFlasher)
[Google Pixel 8 Pro] ada12:
" For now even the AK3 Zip versions of custom kernels requires Verity and Verification to be disabled. "

This is false.

1- for kernel using 5 image ( boot , vendor_kernel_boot , dtbo , vendor_dlkm , New partition gki module : system_dlkm )

In alternative to disable verification :

*And command used by Google for flash custom kernel is : fastboot oem disable-verification

>resign via avbtool all IMG will Work without any wipe. Its need New avb Key...

Solution 2 : actually in my p8 I run a kernel monolithic mean its have no modules so only image.lz4 + dtb in the anykernel3 zip.

I no need " Verity and Verification to be disabled. "
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yep, I hadn't updated that part since sometime on my Pixel 7 Pro, and I just copied that from my thread there. I've now deleted that part from both threads, and the following will remain, since ultimately, it is the kernel developer's instructions that should be followed:

Some kernels still need them to be disabled, and some don't.

The alternatives to disabling them that you presented are really beyond the scope of this thread, since I don't intend on telling users to ignore developer's instructions and use advanced methods, plus any troubleshooting users may need when things don't work the way things were intended.

Don't get me wrong, having alternatives is why I'm on XDA (and Android) to begin with, and I think the more choices that are available to get around limitations, the better, and it's a beautiful thing when more possibilities are found.
[Google Pixel 8 Pro] Gilg@mesh:
yup, I'm still on stock kernel, hopefully kernels arrives soon without need to disable verity as I'm happy with my setup and don't want to start over again.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I've been keeping a close eye out for any that use the new method, that's for sure. Looking forward to it. :)
[Google Pixel 8 Pro] Paz9:
Can anyone confirm that 'hey google' is working with root and PIF?

Mine says not available on device....
[Google Pixel 8 Pro] Gilg@mesh:
working for me.
[Google Pixel 8 Pro] ada12:
Sultan kernel will be available for pixel 8/8 pro soon™ im testers its already no need to disable verity
[Google Pixel 8 Pro] Paz9:
Weird...

I may give it another try I've gone back to stock locked BL...
[Google Pixel 8 Pro] danw_oz:
@roirraW "edor" ehT FYI- there is a Play Integrity fix now that actually works 99% of the time now release version 12.3 (to update your title) :). I never got 12.2 to work after adding the cards.
[Google Pixel 8 Pro] Ghisy:
Latest PIF is actually v13.1 now: https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v13.1

On a completely different note, I wasn't able to find out if the physical Google Stores are also getting this $200 off BF discount for the P8P as well. I guess I'm just gonna have to go there and see for myself.
[Google Pixel 8 Pro] cmh714:
13.1 for me fails on the latest Beta.....13.0 works
[Google Pixel 8 Pro] Ghisy:
I'm still on v13.0 as well on my P7P. Seems to be working although I don't use Google Wallet on my phone. I just have it ready in case I forget my actual wallet.
[Google Pixel 8 Pro] gpvecchi:
13.1 works perfectly on latest QPR2 beta
[Google Pixel 8 Pro] cmh714:
Good to hear that....I will try again! TY!

****EDIT- Nope still failing Integrity Check here....interesting
[Google Pixel 8 Pro] HipKat:
Did you try clearing cache and data in Wallet, GPay, Play Services, Google Framework, make sure SELinux is Enforcing??

Also I have the Deny List enabled.

I'm sure you have but just checking to make sure
[Google Pixel 8 Pro] cmh714:
Failing when using the Integrity Checker app.
[Google Pixel 8 Pro] danw_oz:
Lol, actually you are right, I am running 13 now, which works for me more reliably than 12.2 or 12.3, did this through Magisk manager update process, showing a new update but based on others feedback won't upgrade to 13.1
[Google Pixel 8 Pro] HipKat:
Don't use the app. The point of the PIF is to not need the YASNAC and Integrity Checker apps any longer, according to the Dev.

Again, you may have done this, but just to make sure;

Instead, go to the Play Store/Settings/General/About and tap the Version 4 times til the Dev Options for the Play Store Opens, then back out.

Go to those new Dev Options and check integrity there.

However, I DID try the App on my end and it passed. (YASNAC Times out)
[Google Pixel 8 Pro] Pfeffernuss:
PIF 13.1 / Yasmac results in this here:
[Google Pixel 8 Pro] cmh714:
TY HipKat!! Much Appreciated!!!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! I'm replacing the integrity app-related parts of my OPs with this quote. Anytime I can get rid of one or two apps out of my hundreds is a good thing. :D
[Google Pixel 8 Pro] crisco654:
Just updated to Nov update(from Oct) using flash method, and PIF 13.2(just release a few hours ago), and everything works!
[Google Pixel 8 Pro] HipKat:
Anytime, if I helped, that’s all that matters
[Google Pixel 8 Pro] HipKat:
That’s good to know because in the PIF thread, a couple of guys said that it stopped working when they updated but I can’t tell what devices they have. Seeing that it still works on ours let’s me know I can go ahead and update it in magisk like it’s telling me to.
[Google Pixel 8 Pro] HipKat:
One thing I’m curious about is if it should be disabled on a monthly update, and then re-enabled going through the process again.

I don’t typically disable any of my modules whenever I do an update, and I’ve never had a problem but next month I think we should test it both ways and OTA in full image
[Google Pixel 8 Pro] roirraW "edor" ehT:
I don't think it should make any difference, but I suppose it's possible. This is my first month on PIF, so we'll see. :)

Despite my OP instructions, I don't either. Of course, I sometimes wait several days for reports of what works and what doesn't before I update, but I do use the OTA to both slots, although someone else might test and report the results first.
[Google Pixel 8 Pro] HipKat:
I am the same way. I usually wait until the next weekend after an update comes out by then usually enough people had posted about anything that might not be working
[Google Pixel 8 Pro] badabing2003:
I don't disable USFN and now PIF (or any of my minimal set of modules I use) mainly because for that brief period of time when I boot to system with it disabled, and I get flagged, I'd have to go through the pain of clearing data adding cards and worst having to redo my Samsung watch setup from scratch as it will no longer pair (the stupid thing is tied to GSM)

I know how to recover if I run into an issue, and I doubt that I'll run into issues.

Besides let's say that I disable them, but then I'd have to enable it right? I'd go into bootloop if there is anything bad with it, so I practically just delayed the inevitable.

It's mostly advised to people who don't understand why they go into bootloop and how to recover from it, disabling it at least gives them an idea that it was all good before they enabled modules.
[Google Pixel 8 Pro] l3l4ck0ut1:
I did the 13.1 it was ok at first for a few minutes. then it crashed System UI so bad it the screen went blank. it started with being unresponsive, but my buds were still connected. but tapping my buds to see if it would go to the next song did nothing. power button would bring up the power menu, but tapping restart or any option did nothing. fingerprint sensor stopped working. then buds disconnected, screen went completely blank, couldn't get it to shut down or anything. when I got it up and running, thought it was a fluke. but it did it again 10 minutes later. finally got it running again, so i removed the module in magisk, n now it's been fine for hours. n yes i have a P8P. now i don't wanna install 13.2 in case it's worse 🙄🙄
[Google Pixel 8 Pro] HipKat:
That's very odd.

I wonder if it's conflicting with another Module

I flashed 13.2 last night with no issues
[Google Pixel 8 Pro] roirraW "edor" ehT:
13.3 is the latest - came out yesterday, too. But I'm waiting for when there are no new versions for at least a week before updating from the 13.0 I'm on.
[Google Pixel 8 Pro] Ghisy:
Eeeesh.

https://9to5google.com/2023/11/20/pixel-8-pro-display-bumps/

I'm holding out buying one for now during Black Friday in the US. Because not sure the warranty would apply in Europe if this might happen to my unit.
[Google Pixel 8 Pro] HipKat:
As fast as they're coming out, I might go with a weekly update
[Google Pixel 8 Pro] Pfeffernuss:
13.4 running fine ;)
[Google Pixel 8 Pro] Paz9:
Anyone notice delays for google pay notifications after paying? My notification won't show for up to 2-5 minutes...I only noticed after installing PIF not sure if related

But the payment appears in the recent activity for gpay but notification takes ages
[Google Pixel 8 Pro] Voklav:
I thought I'd ask here instead of starting a new thread:

"Unlocking the bootloader will factory reset your device."

Is this true for every time you unlock the bootloader or only for the first time?

Is there a state of "relocked" bootloader in pixel ... or are there only two: "unlocked" and "locked"?

I ask because several apps started using program libraries that check all 3 states:

MEETS_STRONG_INTEGRITY, MEETS_DEVICE_INTEGRITY, and MEETS_BASIC_INTEGRITY.

So if I understand correctly, MEETS_STRONG_INTEGRITY will pass only if your bootloader is locked.

or perhaps the question is: Can we bypass this MEETS_STRONG_INTEGRITY check-in another way?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Every time you either unlock or lock the bootloader, your device will be factory reset. There's no way around that. However, typically you only unlock it once, and never lock it again.

Just locked and unlocked. Pixels aren't like some phones that permanently "blow" an efuse.

Personally, there hasn't been anything I couldn't do with only basic and device integrity passing, but it just depends on your apps. My banking apps all are fine with the mitigations I use to fool them into thinking I don't have root. One of them even says that I might be rooted, and I might not be able to do everything in the app, but it still lets me use the app fine anyway, and there's always the web browser if there is something I can't do, eventually.

No.
[Google Pixel 8 Pro] jcp2:
Question.... I got my new P8 Pro yesterday and unlocked the BL and updated the OS to Nov build and Rooted with Pixel Flasher. I saw somewhere that there is a risk of bricking the phone if both slots don't have a bootloader installed. My question is: do I only just need to flash the init_boot.img with Pixel Flasher to the inactive slot to avoid the possibility of hard bricking the phone, or is more required?
[Google Pixel 8 Pro] roirraW "edor" ehT:
More. Really, the minimum is the bootloader, but even then it's better just to have the same full firmware on the other slot. You can then flash the rooted init_boot.img to that second slot.
[Google Pixel 8 Pro] jcp2:
Thank you for the quick response. I'll flash the full firmware to the inactive slot as well.
[Google Pixel 8 Pro] badabing2003:
I wouldn't take the chance., if that slot is blank, all he gets is the init_boot, and if that slot has full firmware, then he most likely has an older OS release on it, and there are no guarantees that the newer init_boot would be compatible.
[Google Pixel 8 Pro] badabing2003:
You're still taking an unnecessary (although minor) chance than flashing full OTA.

Here's why:

During flashing, if anything goes wrong, and the inactive slot that you're flashing to becomes unbootable,, your previously main slot's system will be overwritten in the process of flashing firmware, hence that one becomes unbootable too (not necessarily a brick)

Why chance it.
[Google Pixel 8 Pro] roirraW "edor" ehT:
What I was meaning was flash the full firmware to the other slot, and then if they want, they can flash the init_boot.img.

Oh yeah, thank you. I forgot, flashing the firmware versus the OTA.
[Google Pixel 8 Pro] jcp2:
Got it. I'll just do the OTA file then. I didn't know you could flash An OTA file with PixelFlasher.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I forgot, what @badabing2003 is saying, and reminded me of is that the only way to flash both slots and have both of them usable is to flash the Full OTA Zip twice, each time it automatically changes slots.

You can see the directions for doing that in post #2.
[Google Pixel 8 Pro] wangdaning:
If you want to make sure bootloader is on both slots just use "fastboot flash --slot-all bootloader bootloader.img" bootloader.img being whatever the name of the image you have is.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yep, having bootloader on both slots at minimum will at least keep your phone from being bricked (if the phone tried switching to the empty slot), but if you're going to do that, might as well just flash the OTA to both slots instead, and have fully functional Android in both slots.
[Google Pixel 8 Pro] Lughnasadh:
You reported earlier that your new phone came with the bootloader on both slots, correct?
[Google Pixel 8 Pro] wangdaning:
For me it was like that, but I guess if it is not like that for everyone better safe than sorry.
[Google Pixel 8 Pro] whatsisnametake2:
when I got my p8p I unlocked the bootloader. nothing else, didn't root it yet. all banking apps have been fine, as I was expecting as hadn't rooted. all of a sudden wallet and mbna are throwing up security flags and throwing me out! I wasn't expecting this. I notice that also my play store is showing device not certified. what has happened here? are these apps now detecting unlocked bootloader alone? or is something else going on. I'm still on release firmware October. I can't imagine that would cause it?

I mentioned this in the other thread about whether it was worth rooting now. at the moment my only reason not to root has gone so I may as well root.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Don't know the cause, but it's a common experience.