yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] djmcnz:
Just use PixelFlash to flash the full factory image (not OTA), no root, no Magisk, plain Jane (or Jack if that's your fancy), to the inactive slot, manually change to that slot then boot.

There's no fundamental reason that wouldn't boot unless your partitions are screwed (and in this case, the flash is unlikely to be successful anyway), and no need to wipe.

If it doesn't boot cleanly then...

adb logcat > bootloop.txt

And see what's causing the problem. If it's a problem with something in /data or Magisk you can probably remediate that manually using ADB once you've identified the culprit.

Edit: at the moment with Verity requirements I consider custom kernels more hassle and risk than they're worth. IMHO of course.
[Google Pixel 8 Pro] chill145:
Agree 100% with your edit. PixelFlasher makes it so easy to update each month that I don't want to be bothered with the extra headaches of verity.

I also want to be clear that I'm not putting down the work of those developers as I'd use their kernels in a heartbeat if Google made things easier.
[Google Pixel 8 Pro] HipKat:
That is correct. Unhide the App, update the app where it says in Magisk, then update Magisk within the app and reboot. Then rehide Magisk.
[Google Pixel 8 Pro] ysco:
Question guys.

I'm still on stable and the security update is available. Normally on my other phones I run the system update and no reboot then in magisk the option install to in-active slot (after ota) always works but I thought I read somewhere that this does not work on p8p. Please confirm and what easy steps are then necessary to flash and keep root.

Thx in advance. ysco..
[Google Pixel 8 Pro] roirraW "edor" ehT:
I've never used the method, but I've read many comments over the last couple of years and Pixels about others. As far as I know, it may have worked sometimes in recent times, but in my opinion, you can't rely on it, so personally, I wouldn't bother trying since it might be more of a headache to fix.

Recommendation: Use the Full OTA Zip method in Post #2.
[Google Pixel 8 Pro] HipKat:
Did you mean Full Factory or OTA?
[Google Pixel 8 Pro] ysco:
Thx mate for the reply, will try your suggestion I think. But still I'm curious if the magisk methode works.

Regards ysco..
[Google Pixel 8 Pro] roirraW "edor" ehT:
Full OTA Zip method. I've sworn to myself to stop referring to the Factory zip as Full Factory, because "Full" is only used by Google in that context in relation to the Full OTA. Factory image is solely that or Factory zip or Factory image zip.

I stopped sometime in the last couple of years, after doing so regularly in my P6P thread at least for a while, but I recognized there was the possibility for confusion between "Full Factory" and "Full OTA", and since me using "Full" before "Factory" was both redundant and when a user looks on Google's site, there's nothing listing "full factory", so I stopped. I may let it slip occasionally, but I think I catch myself most of the time.

I don't know if there is a non-Full OTA, but there used to be, so it's fine that Google has kept the old naming of the Full OTA, and it's good to continue specifying that it's not a simple differencing OTA. Instead, the files that are in it are complete and intact, exactly how they will be after they're flashed to the device.
[Google Pixel 8 Pro] Lughnasadh:
For what it's worth, I've seen at least 25 people report success with the "Install to Inactive Slot" method in the last 3 months with the Pixel 7 series. However, almost as many have reported failures, so at least for the Pixel 7 series it works, but it's hit or miss.

Haven't really seen many reports with Pixel 8 series users, but my guess is it would be similar to the above.
[Google Pixel 8 Pro] ysco:
Hmm, I think I will try it tomorrow because I want to know if it works as this was always the easiest way to update. Will post the results if it worked or not 😉.

Regards ysco..
[Google Pixel 8 Pro] Lughnasadh:
Just make sure that if you have a custom kernel that you revert it back to stock beforehand as that has been known in the past to cause failures for many.

Look forward to your report 👍
[Google Pixel 8 Pro] roirraW "edor" ehT:
Platform-Tools v34.0.5 release notes:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 8 Pro] Alkaizer Lord:
If I purchase the carrier unlocked device directly from Google, can I still unlock the bootloader if I activate it on the Verizon network?
[Google Pixel 8 Pro] cmh714:
Yes! As long as its unlocked from Google it should be fine on any carriers network.

I am a VZW customer and ONLY buy unlocked phones from Google.
[Google Pixel 8 Pro] Alkaizer Lord:
Awesome, thank you for letting me know!
[Google Pixel 8 Pro] ysco:
Damn when I try to download and install the security update then it fails probably cause it mismatch with the patched bootimage. I had this also with the nothing 2 phone. Needs to uninstall magisk first and then the system update probably works again. Damn don't know why they changed this, before it was a lot easier to remain rooted
[Google Pixel 8 Pro] Lughnasadh:
Did you restore images in Magisk first before taking the OTA update?
[Google Pixel 8 Pro] ysco:
I checked indeed this setting cause I did the same with nothing 2 phone update but now it says that the stock image is not available. Don't know why it's missing, maybe I deleted it by accident a while back?
[Google Pixel 8 Pro] Lughnasadh:
Maybe. They are stored in /data/magisk_backup_xxxxxxxxxx.
[Google Pixel 8 Pro] ysco:
Hmm just looked for that folder but it don't exist. I only have a magisk folder in root/data/data but it doesn't have a backup folder or boot.img
[Google Pixel 8 Pro] Lughnasadh:
Hmm, I guess you don't have any backups. The last 3 times I have updated firmware and flashed the patched init_boot.img via fastboot afterwards it created a backup in /data/magisk_backup_xxxxxxx
[Google Pixel 8 Pro] ysco:
Damn nope then I have no backups.

Well if I installed the Update after I completely uninstall magisk first and then re-root I will first look if the backup file exist in the data folder so that I can try the next time to update the old way and see if it works then 😉
[Google Pixel 8 Pro] Lughnasadh:
Looking forward to your results. Thanks for trying to test it out. See you in a month 😀😅
[Google Pixel 8 Pro] ysco:
For sure 😉👍

Regards ysco..
[Google Pixel 8 Pro] wangdaning:
I have the magisk backup folder, but why is the backup labelled boot.img not init_boot.img.
[Google Pixel 8 Pro] Lughnasadh:
I believe this is why. Quote from one of the Magisk devs:

"init_boot will still use the name boot (in find_boot function)"
[Google Pixel 8 Pro] reaper000:
For your flashing convenience, here's the Magisk 26.4-rooted version of the init_boot.img from the Nov 2023 update.

(If you don't know exactly what to do with this file to obtain root, then you should probably read up on rooting to the point of your own certainty before using this file)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Edit: Apologies, I was thinking this was the Pixel Watch 2 thread. :D

Disregard.
[Google Pixel 8 Pro] Lughnasadh:
I don't think we can know for sure until the kernel devs get a hold of it.
[Google Pixel 8 Pro] ZG_DEV:
The phone didn't even last for a complete week since it has been published, you are so quick on this ! 🫡
[Google Pixel 8 Pro] Lughnasadh:
Here's what Freak had to say about the flags in his Pixel 6 Pro thread...

"Thanks to @Sultanxda this kernel is now build in a monolithic fashion. That means all drivers are compiled into the zImage. This means no more modules and vendor_dlkm does not need to be modified any longer, which in return means users won´t have to disable the avb flags for veritiy/verification any longer to be able to boot the kernel.

However there´s something I want to keep everyone in mind. If you currently run with the flags disabled you might want to keep them disabled just like you did over the last months while updating. There´s the slight chance that kernel changes introduced by google in the future, changes to partition layout or undiscovered bugs will screw the monolithic build up. I tested it as best as I could and didn´t find any issues, but that´s just an advice I want to put out." (emphasis added)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! Hopefully I find time to incorporate the latest information and caveats into my OPs soonish ("if you already have them disabled, you might want to keep disabling them; if you don't have them disabled, you don't have to, but be aware changes in the future might require them to be disabled again in order to use custom kernels...")
[Google Pixel 8 Pro] roirraW "edor" ehT:
You will soon find all your Google Pixel updates in one place

Android 14 will soon display all your pending OS and app updates in one place

www.androidpolice.com

Google rolls out the Pixel 8 Magnifier app to older models

The app is a valuable accessibility function, designed to make small, dimly lit or distant text easier to read.

www.androidcentral.com

Magnifier - Apps on Google Play

Zoom in, brighten, and adjust contrast to aid your vision.

play.google.com
[Google Pixel 8 Pro] BranBro365:
I'm hoping ATT stores get some with higher storage. i had to settle for a 256GB model because that's the highest storage option they offered on launch day. When i receive it on Thursday I'm calling all my local ATT stores to see if they have any 512GB models so I can switch it out.
[Google Pixel 8 Pro] almahix:
I pre-ordered one on the 4th. It is due the 12th or 13th. Seems like an eternity! I had to report my pixel6 pro trade in as "cracked" so I'm taking a huge loss. The phone is perfectly fine except for a cracked camera lens. Hopefully they'll send via a responsible carrier. Last time I pre-ordered it was sent via OnTrack and it was misdelivered and it took days to find it.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Pixel 8 Gets Major Security Upgrade To Compete With iPhone 15

Google’s has finally bought back a fan favourite security feature: 3D Face Unlock.

www.forbes.com
[Google Pixel 8 Pro] simplepinoi177:
As long as they could/can achieve this without that god-awful notch (that, at one point, seems to just get bigger and bigger), this is great news!

I still feel/hate that there are still residual fallout from the "notch" and/or moving the front facing cut out to the middle of the screen -- I enjoyed the design of the Pixel 2 well enough -- that I purposefully go out of my way to find root methods to place my clock on the right side of my phone still; Maybe it's my Windows hammered-in mindset, but signal, sound (DND), battery life, & clock should all be at least together (if not all on the right, then all on the left then), versus a data reference you look at your phone very frequently everyday being separately on the other end of the top/notification! They only changed this because the clock pushed things too far into the notch. Yet it still remains even though the front facing camera cutout is so majorly more minimal than a notch, as it still resides in the middle.

But, I wonder, I don't believe the "chip" & A.I. can get the accuracy needed for 3D face unlock (as opposed to 2D on the Pixel 7's) if the front facing camera is off center like on the Pixel 2's....
[Google Pixel 8 Pro] roirraW "edor" ehT:
I don't remember how long I've preferred it, but I like my clock to be on the left. It irked me that as the time changed when the clock was on the right (especially if I had clock seconds enabled, which I preferred), that the icons to the left of the clock would constantly shift left and right, as the HH:MM:SS would change how much space it was taking up.

If/when I didn't have seconds enabled, and before that was a common (at least with root) option, I was certainly used to the clock being on the right.
[Google Pixel 8 Pro] rester555:
I am glad after 4 years from the Pixel 4XL, which had full face unlock, that they realize the importance of face unlock. It's SO MUCH FASTER than the garbage optical fingerprint reader. The FPR (optical or different) should be second fiddle moving forward as an added layer like 2FA in my opinion or something similar.

Also, like I said in other threads, Google is going to get a huge awakening when people stop buying on day one and actually buy the phones later in the year for this trade-in debacle. I for one will be watching the devaluation closely when making future decisions.
[Google Pixel 8 Pro] Lughnasadh:
https://twitter.com/i/web/status/1711429514130079970
[Google Pixel 8 Pro] Lughnasadh:
Not sure if this has been mentioned yet...

https://twitter.com/i/web/status/1711416356963287436
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hopefully this translates to real world improvement (although I didn't have any issue with the P7P, but I use a screen protector and OtterBox Defender), and isn't just paid for advertising.

Benefits of Gorilla Glass Victus 2 upgrade shown in Google Pixel 8 Pro drop and scratch tests

A switch to Corning Gorilla Glass Victus 2 is just one of the ways that Google is attempting to distinguish the Pixel 8 Pro from last year's Pixel 7 Pro. Initial drop and scratch tests suggest that the upgrade to the stronger glass type has paid off, just days before Google begins shipping Pixel...

www.notebookcheck.net
[Google Pixel 8 Pro] Utini:
Since the P8P factory images are up, is there any way to already verify that rooting (by patching boot via magisk) works?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I don't think so, since we can't attempt to boot the phone with the patched image.
[Google Pixel 8 Pro] Utini:
Hmm crap. I am too scared to unlock/flash before someone verifies the methode :D

Also not possible to try in a Android emulator?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I thought of that, but unfortunately I've only fiddled with the emulator a tiny bit, so I can't honestly say, but in the end, the only real meaningful proof is trying it on an actual device, but that's just my personal criteria.

It shouldn't be hard at all to recover if it doesn't boot, so I'd have no problem trying it if I had my hands on the new phone now.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks for the heads-up.

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

Be aware that there are both September and October images available, so either update your phone immediately, or use the correct old image, since using the wrong init_boot.img might not even boot, although it should be easily recoverable if you do that by accident (or on purpose :D ).

I would recommend the update to October and then root it method.
[Google Pixel 8 Pro] Utini:
Time to unleash our beast aKa @Freak07 on those images! :P
[Google Pixel 8 Pro] dr_rick13:
Team, quick question that's unrelated to the last update.

When you guys open Photos and click on a photo taken on the P8P - do you see the screen flash before the photo opens? It's like a millisecond... Very strange.

Thanks
[Google Pixel 8 Pro] Zilla0617:
Thanks for the suggestion, but it was too late as I was knee deep into restoring my phone. Will keep this in mind if the issue ever arises again.
[Google Pixel 8 Pro] foobar66:
Yes, on some photos.
[Google Pixel 8 Pro] MariusKv:
No ota for me yet, pixel 8 pro
[Google Pixel 8 Pro] simplepinoi177:
Sorry for such a long delay in responding to this (was just going through my alerts to see if there was any unread threads I've forgotten to check on and this was one), but I learned from badabing2003 that the "non-full OTA" (the OTAs that is used when using the OS System Update) is what he identifies as incremental OTA (I think he stated that's what's done in the OS System Update is when updates and patches and fixes are stacked one on top of the previous on and on; whereas Full OTA & Full Factory swipes it out and re-establishes it all form the ground up -- the difference between Full OTA and Full Factory then is one makes the other slot unbootable [Full Factory] while the other simply switches slots and updates); what you download from the developer site is Full OTA, and for what it's worth I name all my folders and identifiers as Full Factory -- I kinda like leaving it including "Full" because it gives the indication that it is a complete factory image which the contents is all/full of all images to all partitions to the device.
[Google Pixel 8 Pro] HipKat:
TBH, I always flashed the OTA. It was only with the recommendation of @badabing2003 when I got the P8P to flash the Factory Image. Now I just need to get brave enough to flash both slots..
[Google Pixel 8 Pro] HipKat:
Typically, I unlock the bootloader before putting the SIM Card in.
[Google Pixel 8 Pro] Annie the Eagle:
Updated to Magisk 26.4 on Oct 2023, then used PixelFlasher to flash the Nov 2023 Full OTA ZIP (making sure to preserve verity being disabled).

Then reflashed DespairKernel v1.03 and Powerhint Module.

All worked perfectly. I think PixelFlasher only does one slot. But I don't know of any real reason to do both at the same time, unless someone has any thoughts?

Current Setup, in case it helps:

Image: Nov 2023 (flashed via Full OTA ZIP)

Kernel: DespairKernel v1.03

Tools: Platform Tools v33.0.3

Magisk: 26.4 Stable

Modules:

PlayIntegrityFix v9.9

PowerHint Shusky Module v1.0

Systemless Hosts v1.0
[Google Pixel 8 Pro] HipKat:
It does byt you can choose to flash to both slots in the options
[Google Pixel 8 Pro] HipKat:
lol...

All I know is this is the page I get the update for the P8P from now :)

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

developers.google.com
[Google Pixel 8 Pro] Annie the Eagle:
Think that's disabled when you select an OTA ZIP, although in my case it is shown as ticked

Not sure if it forces it to "On", or just disables the checkbox and shows what you had last selected.
[Google Pixel 8 Pro] HipKat:
Possibly, my choice there is always Keep Data, which may re-enable flashing to both slots. I'm on Linux now (I use Windows for PF and a few other programs) but you can check or I will when I boot back to Windows again
[Google Pixel 8 Pro] Annie the Eagle:
Yeah if I select an OTA ZIP, it has options like that. I assume if I selected "Custom Flash", then the options like flashing both slots might be available again.
[Google Pixel 8 Pro] Jose.pH:
I still haven't received the update and I can't find the NOV ota on the site.... :(

edit lol I change language in ENGLISH and Find ota nov...

Immagini OTA complete per dispositivi Nexus e Pixel | Google Play services | Google for Developers

developers.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yep, incremental OTA. I seem to recall Google's site used to list them as well in their own section, just as Full OTA is separate from the Factory Images.

Just checking, so let me know if you already know... Flashing the factory image to both slots is only good for getting the bootloader onto both slots, although flashing the OTA will also do the same thing. I've been flashing the OTA twice (to get both slots fully bootable into Android, and flashing the rooted init_boot.img to both slots as well for the past ~4-6 months, exactly like I describe in Post #2 for the Full OTA ZIp method.

Edit: You can ignore the rest of my post below, since @badabing2003 clarified in the next post, and I wasn't 100% sure if you actually meant at the very same time, or just one right after the other, so my mistake.

There are a at least two reasons, as @Lughnasadh and @badabing2003 have educated me:

When a Google Pixel is brand new, out of the box, the slot that it isn't set to boot to does not even contain a bootloader. If something happens that makes the slot it's on unbootable, it will try to switch to the other slot, which will fail, and I think from memory, users experienced a bad enough brick that only RMAing to Google would fix.

The other reason to flash both slots is to make both slots bootable with the most up to date firmware, although only flashing the OTA (twice) really achieves that, as flashing the factory image instead always makes only the most recently flashed slot bootable and the other one will not be bootable.
[Google Pixel 8 Pro] badabing2003:
@Annie the Eagle is correct

Depending on your selection the options differ.

Full OTA flashing is one slot at a time.

You want to flash both slots, you hit the flash button again after you make sure what you flashed is good and working.

This is from the OP
[Google Pixel 8 Pro] HipKat:
I never had. I always just downloaded the OTA and made sure that I was disabling verification and verity and clicked on keep data, other than the few times I wanted to do a full wipe, and after unhinding magisk, I would flash with PF, and go on.

And I would always just flashed to the inactive slot, I guess, not really knowing any better. Which is actually what I did this month, except with the full factory image
[Google Pixel 8 Pro] badabing2003:
Is it a typo or are you mixing it up.?

with OTA, there is no wipe option or selection of inactive slot.

It is inherently Keep Data and Inactive slot but it's not something you can select.
[Google Pixel 8 Pro] LLStarks:
When you lose track of your slot or what you flashed, it's time to start over. Sometimes a full wipe cures everything.
[Google Pixel 8 Pro] Gilg@mesh:
device integrity suddenly fails, though payment etc still works, v2.4.0 Mod

1.3
[Google Pixel 8 Pro] Lughnasadh:
Known issue. Google shenanigans overnight/early morning.
[Google Pixel 8 Pro] Gilg@mesh:
FU Google lol, I guess only wait for fix then? :)
[Google Pixel 8 Pro] Lughnasadh:
Yep
[Google Pixel 8 Pro] roirraW "edor" ehT:
I just noticed this today, too.
[Google Pixel 8 Pro] LLStarks:
Why is Displax still used when Play Integrity Fix is actively developed?

1.3 could stop working at any time.
[Google Pixel 8 Pro] roirraW "edor" ehT:
The Download link in the XDA OP leads here, where there are no releases:

Releases · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

Edit: Sounds like whatever Google did affected that mod, too, and I'm guessing he took the mod down until he can fix it, so @Displax's mod isn't alone, and it was working fine up until now.

Edit 2: download is back and it's supposed to be fixed.
[Google Pixel 8 Pro] Morgrain:
Platform Tools version 34.0.5 is out. Can it safely be used to upgrade to November update?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yes. I used it, and multiple others have, too.
[Google Pixel 8 Pro] Pixel86:
Yes.
[Google Pixel 8 Pro] chill145:
I can probably guess the answer, but I assume you'd want to first flash the ota without root, letting it boot up, and then flashing the OTA again with the patched boot image and root. I've never flashed both slots but will do so moving forward.
[Google Pixel 8 Pro] Spookymyo:
Well the phone is back from RMA return and you were right. They didn't charge anything. I don't even think they looked at the phone. The details on the RMA said power failure. But it is a verified new phone and not a refurb. And I got to keep the watch.

Now to try to root again but using the OTA method.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Excellent! The best of luck, and if you have any questions, we'll be here.
[Google Pixel 8 Pro] badabing2003:
It has its pros and cons.

The advantage is that you're guaranteed that there is no patch involved and hence no Magisk modules getting in the way, and if it doesn't work, you have less elements that could be a factor for the issue.

On the other hand you might have to clean up data / cache of few apps to pass SafetyNet and the like, and you might have to re-add CC cards to wallet.

And it use to be worse because clearing GSM data meant you needed to setup your watchos (at least Samsung) all over again from scratch.

I personally do it in one shot, I only use a handful of modules and none of those cause issues, so I don't even disable the modules.

But each use case is different.