yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hi, and welcome soon to the P8P!

I thought the OTA would, as everything would work 100% fine if you were taking an actual over the air update, but I will defer to @Lughnasadh, @badabing2003, or anyone else who knows 100%.

I will say that I never used the factory image (or an actual over the air update) on my Pixel 8 Pro at all, and every update for it has been manually flashed using the Full OTA Zip method (which switches slots just by flashing an OTA). Since I'm still waking up, though, I'll still defer. :)
[Google Pixel 8 Pro] badabing2003:
Not true, payload.bin has bootloader image data, I think you're confusing using fastboot and bootloader mode with what OTA has or hasn't.

OTA uses sideload command to flash the image (payload.bin is part of it), the image is identical to the factory image, except its is in different format, and flashed differently, so yes it includes a bootloader image (if need be).
[Google Pixel 8 Pro] ChillDuder:
Thanks.

I'm not at my pc now, but then yesterday i maybe missed out that image after i did payload-dumber on a ota payload.bin.

I just wanted to be sure that with first use a sideload ota completely takes care of second slots.

Thank you all.
[Google Pixel 8 Pro] Paz9:
Pif and playcurl started failing integrity

Anyone else? Updated and still failing
[Google Pixel 8 Pro] fijasko:
it's everyone and it doesn't look good

🔧 [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 8 Pro] badabing2003:
I don't know what you mean by takes care of second slots.

Are you expecting to have both slots flashed? (No, read OP, that's why it says flash twice)

Or are you asking if it flashes to the inactive slot? (Always does)
[Google Pixel 8 Pro] ChillDuder:
I'm sorry for making that such a confusing stupid topic.

(I'm flashing android devices for a few years now, but not pixels until now)

In the OP it is stated, that on a fresh device second slot is empty, and can, in worst case with a switch to that slot, lead to brick, if booted.

So i downloaded for just checking and learning both ota and images zips and did take a look. payload-dumper also used.

I factory image zip in the flash-all script there is that additional fastboot flash of bootloader and radio, after that fastboot update with the other images zip. all fine.

And what i wanted to ask first is: if using adb sideload (instead of switch to b manually and use factory images) THE FIRST time on a fresh device also flashing that bootloader and radio to second slot and be sure that they are filled/flashed. because i did not find that images in payload output (but because most likely the named differently).

Thank you. My p8p is already running&booting fine from B also ;-)
[Google Pixel 8 Pro] BillGoss:
The reason you don't find bootloader or radio in the payload file is because:

Bootloader is made up of the following partitions (and the *_b ones):

bl1_a

ldfw_a

dpm_a

gcf_a

pbl_a

bl2_a

dram_train_a

abl_a

bl31_a

tzsw_a

gsa_a

gsa_bl1_a

Radio is actually the modem_a/b partitions.

You can see this by looking at the output when flashing factory images.
[Google Pixel 8 Pro] Paz9:
All working after latest update
[Google Pixel 8 Pro] rester555:
Updated using PF and all is working. GPay, Wallet, RCS, and all other magisk modules I use. Only have MEETS BASIC INTEGRITY.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yesterday I updated PIF to 15.9.9 and playcurl to 10.4, and both at the time and just now I checked the status via the Play Store Developer options, and I get both MEETS_BASIC_INTEGRITY and MEETS_DEVICE_INTEGRITY.
[Google Pixel 8 Pro] rester555:
I am afraid to upgrade until mine no longer works.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm absolutely with you. I don't touch anything having to do with it unless I have a failure. I was only getting MEETS_BASIC_INTEGRITY before the upgrade. I was honestly surprised just upgrading both of those was all I needed. :)
[Google Pixel 8 Pro] ajaibhamid:
Rooted unlock
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hi and welcome to XDA, @ajaibhamid. I'm afraid that I don't understand what you're trying to say, or what your question is, if you have one. The OPs (Opening Posts - the first posts) of this thread explain everything about unlocking the bootloader of the Pixel 8 Pro, and about rooting it.

If you have any specific questions, by all means let us know, but please be detailed.

Cheers.
[Google Pixel 8 Pro] Lughnasadh:
What to expect with June's Feature Drop:

Android's latest feature drop makes your devices work better together

Google is rolling out 8 new exciting Android features to "elevate your everyday." Here's what they are.

www.androidfaithful.com
[Google Pixel 8 Pro] Ericarthurc:
@roirraW "edor" ehT

You could add Spectrum Mobile purchased phones to the T-Mobile/AT&T section for bootloader unlock.

Spectrum uses Verizon's towers but they purchase directly from Google. These are not Verizon variants.

The phone needs to be paid off and active for 60 days on Spectrum's service then you can request an unlock from support.

I bring it up because a lot of people have been asking about Spectrum lately and people seem to be confused. Spectrum mobile even has an official support page about unlocking and all the requirements.
[Google Pixel 8 Pro] roirraW "edor" ehT:
That's awesome, and good to know. I'll add that as soon as I can get to it.

Thank you!

Edit: Added a quote of your post to Post #2.
[Google Pixel 8 Pro] roirraW "edor" ehT:
June 2024 security bulletin is listed, but linked to the May 2024 one.

Here's the correct link:

Android Security Bulletin—June 2024 | Android Open Source Project

source.android.com

Edit: The main page:

Android Security Bulletins | Android Open Source Project

source.android.com

says June is still security patch level:

2024-05-01

2024-05-05

So obviously, they have some corrections to do on this page. :)
[Google Pixel 8 Pro] rester555:
Next Monday is new build day I assume.
[Google Pixel 8 Pro] Lughnasadh:
More likely later today or tomorrow, judging by past history at least. Last month they released the ASB on a Monday (which they usually do) and the builds were released the following day.
[Google Pixel 8 Pro] Lughnasadh:
Google can keep a phone if you send for repair with non-OEM parts (Update: Changing policy)

In its terms and conditions, Google said it could keep devices sent in for repair if they have a non-OEM part. This will be changed now.

www.androidauthority.com
[Google Pixel 8 Pro] rester555:
These companies are just getting worse and worse. You can't use software functions that are part of the OS with them being behind a paywall.

You can't modify hardware otherwise you forfeit what you bought.

This makes zero sense.

EDIT: With RCS messaging, why not give the consumer the option or a message claiming that you are susceptible to man in the middle attacks if you have an unlocked bootloader and rooted instead of just not allowing people to use the function with root.
[Google Pixel 8 Pro] Lughnasadh:
And in a turn around...

Google says it will not keep Pixel devices sent in for repair with 'unauthorized parts'

Google is updating its policy around Pixel repairs, no longer keeping devices that were sent in for repair with unauthorized aftermarket parts

9to5google.com
[Google Pixel 8 Pro] rester555:
Can they reverse their attack on people with root and third part development? I wish.
[Google Pixel 8 Pro] roirraW "edor" ehT:
QPR3 STABLE

June 11, 2024

:

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

developers.google.com

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

developers.google.com

Android Flash Tool

flash.android.com

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com

June 2024 Feature Drop
[Google Pixel 8 Pro] rester555:
I haven't had time. Has anyone updated and rooted with no issues other than the known issues like RCS and PIF
[Google Pixel 8 Pro] roirraW "edor" ehT:
I haven't updated my P8P yet - I'm about to.

No issues with my P7P, however:

Edit: See my P8P update (device is corrupt) a couple posts below.
[Google Pixel 8 Pro] Kingcool88:
Updated and rooted. Passes all but strong (as usual).
[Google Pixel 8 Pro] roirraW "edor" ehT:
Wah. I just got "Your device is corrupt" on my P8P after using the Full OTA Zip. I'll downgrade the boot.img, attempt to boot with it (which will fail), and then I'll reupgrade the boot.img. That usually takes care of that.

Edit: No luck yet. I'll try again. Whoops, had done init_boot.img to init_boot instead of boot.img to boot.img. It'll probably work with the right image. :D

Edit 2: Argh, still no luck. Hmmmmm....

Edit 3: I flashed the full May factory image (with the rooted init_boot.img), and all is well. Now to re-upgrade. 😬 I just triple-checked the Full OTA Zip's SHA-256 and it matches what it's supposed to be.

Edit 4: Re-upgrade is back to corrupt, although it took it rebooting on its own several times without getting to where I can unlock it, to get to that point. I'm giving up for today, after I re-flash the May factory image again.
[Google Pixel 8 Pro] rester555:
You used PF?
[Google Pixel 8 Pro] Kingcool88:
Yep!
[Google Pixel 8 Pro] Asma12:
With Magisk?
[Google Pixel 8 Pro] Asma12:
Pixel Flasher with latest Magisk canary was unsuccesfull for me.

I've tried APatch for my first time and it worked. All my magisk module works fine with it.
[Google Pixel 8 Pro] UberNorse:
This is with patching boot.img only and not init_boot, correct?
[Google Pixel 8 Pro] Kingcool88:
Yeah kitsune. I even reflashed again as I tested the Sultan kernel with the new firmware. After test I flashed whole stock firmware with kitsune again. No issues.
[Google Pixel 8 Pro] Albein:
I have pixel 6a and I have not received the update, but the strangest thing is I don't see it on Google servers either..... Has something happened with the update?
[Google Pixel 8 Pro] Asma12:
I've done everything with PixelFlasher, I think that it patches also init_boot automatically
[Google Pixel 8 Pro] Albein:
I found it! sorry :)
[Google Pixel 8 Pro] roirraW "edor" ehT:
That's okay! I was going to suggest that sometimes the various languages that are available for the webpage in the upper right corner don't always seem to be updated with all the latest firmware at the same time. Sometimes even English hasn't been first - but that if you switch to another language temporarily, you can occasionally find the latest release(s).

Is this what happened, or was it a different issue?
[Google Pixel 8 Pro] Albein:
The issue was.... me :).

I was looking in the OTA tab...... I didn't remember that since I am root, I need the factory image and patch it....
[Google Pixel 8 Pro] roirraW "edor" ehT:
I see. :) For what it's worth, I've been using the Full OTA Zip (twice, so it makes both slots bootable and fully workable) for the last year.

Glad you solved the issue, regardless!
[Google Pixel 8 Pro] Winryr:
For anyone having issues with Lsposed 1.9.3 after the June Security Update (unable to open Lsposed, manage modules, shell crashing), I updated to the lastest canary build and my issues were resolved. Hope this potentially helps save some of yall time troubleshooting similar issues.
[Google Pixel 8 Pro] Albein:
Excuse me .... Twice? you mean I have to flash the OTA twice in a row??
[Google Pixel 8 Pro] roirraW "edor" ehT:
Correct. Every time you flash the Full OTA Zip (just like taking an actual over the air update), it first changes slots.

So if you're currently running on Slot A, when you start sideloading the Full OTA Zip, it switches to slot B and flashes it there. It is optional if you want both slots' systems to be the same, but there's no reason not to (other than taking another few minutes), and some reasons to do so.

Having an old firmware in one slot doesn't help in any circumstance because there's only one set of System and user App Data (only one Data partition). When you upgrade your firmware in one slot, especially after you've booted into it and used it, the system and user app data becomes modified from what it used to be on the old firmware. If the new firmware slot stops being able to be bootable for whatever reason, and the phone automatically switches to the old firmware slot, the old firmware slot will still be using the new firmware's system and user app data.

There are bound to be changes to that app data between the old and new firmware, so things might not behave correctly on the old firmware.

So, if you flash the Full OTA Zip twice, you'll have the same upgraded firmware in both slots.

Another, more important reason to at least flash both slots at least once in the lifetime of your phone is that in the last few years, it was discovered that a Pixel had been shipped with no firmware at all in the second slot - not even a bootloader. In that circumstance, if you're using Slot A, and Slot B is completely empty, if Slot A stops working for whatever reason and the phone switches to Slot B, since there is no bootloader, your phone will be completely hard bricked with no chance of recovery except by RMAing it in to Google.

So if you've never taken an actual over the air update on your phone, and never flashed a Full OTA Zip at least once, and never manually switches slots before flashing the factory image, then there is a chance that you have nothing at all in the other slot of your phone.

We don't know if this definitely is always the case, but it's not worth taking the chance, since it doesn't hurt anything to flash both slots at least once after you get a new Pixel, and it's potentially helpful to have both slots have the same system firmware.

You could even have one slot rooted, and one slot not rooted, if you wanted, but the usefulness of that is debatable, since without root you can't use the root workarounds for Play Integrity, so it just depends on what you might want to do with a non-rooted copy of the firmware.

Hope this helps and that I haven't made it too confusing.

To be clear, you do not

have to

flash the Full OTA Zip twice. Some of us just recommend you do so, but again, at least flash it twice at least one time, if you understand my meaning.

I flash it twice every month.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Oh, to not make the above post even longer, another issue is that if you use the Factory Image instead of the Full OTA Zip, then it's been found that

only

the most recently flashed slot will work. i.e. if you flash the Factory Image to Slot A, then manually switch slots and flash the Factory Image to Slot B, only Slot B will work. If you manually (or automatically) switch slots back to A, it will boot to an extent, but it won't work.

Again, like all things Google, it's certainly possible that Google has or will change this randomly without notice sometime recently, but it's doubtful.

So that's why I both don't use the Factory Image anymore, unless I have to, and also why I flash the Full OTA Zip twice each month.
[Google Pixel 8 Pro] Ghisy:
After checking, it turns out I can't open the parasitic manager (I'm on LSposed 1.9.2 official). But it seems like everything related to LSposed works?

Should I update to this version? I guess 1.9.2 should be uninstalled first?

Edit: I'm on a P7P but I guess it doesn't matter.

Edit 2: dumb question, I only see an apk for this mod? Where's the Magisk flashable zip?
[Google Pixel 8 Pro] rester555:
Does this canary build have to be compiled?

EDIT: Nevermind figured it out.
[Google Pixel 8 Pro] Dataman100:
So were you finally able to get this to work? I'm confused. I'm reading in some posts that the standard OTA upgrade process in post #3 using Magisk we've been using doesn't work for this month. You now have to use something called Apatch instead of Magisk? Is that the case? I'd like to know the right process before I upgrade.

Thanks!
[Google Pixel 8 Pro] roirraW "edor" ehT:
My P8P is still corrupt, and I might have to factory reset at this point, but that's okay - I've got everything backed up all the time, it's just a pain to deal with when I have time.

I'm fairly sure some others in this thread have reported using Magisk just fine with the June firmware, but I don't recall if they were using the OTA or factory image, if they mentioned.

Do you have links to some sample posts about Magisk not working with the OTA for June?
[Google Pixel 8 Pro] Dataman100:
This was the post I saw that confused me.

Also the fact that it failed for you concerns me since you were the original creator of the process. 😬

I have my phone backed up as well but I really can't be down while I rebuild it. I'm hoping the process in post #3 still works. 🤞
[Google Pixel 8 Pro] rester555:
I flashed the June update with latest PF and latest platform tools. I have magisk 27002 build working fine with canary build LSposed 1.9.3. all seems to be working. Adaway works. I am not bothering with PIF.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I see. Don't take my single example of some kind of failure as meaning it will fail for everyone. I'm sure someone else would've reported even just in these last 24 hours the firmware has been available, if their phone became corrupt.

I understand what you mean, but just to be clear, I didn't create the process. :D

Yes, I'm lucky that I have a Pixel 7 Pro still, at least. In my case, I think I must just give in and factory reset.

Which brings me to...

@Lughnasadh, @badabing2003, once I reach this screen, there's pretty much no choice but Factory reset, correct? I had downgraded both boot and init_boot on both slots to March's, unpatched, and all was well, but after trying to flash the May Full OTA Zip (the most recent that I was successfully using), I got here. I'm able to get back into Fastboot using "ADB reboot bootloader" but all attempts at flashing any Full OTA Zip or factory image have failed.

I also flashed the June firmware without wiping, not relocking the bootloader, and not force flashing all partitions using https://flash.android.com/ , but I still wound up at this screen.

Just a last ditch confirmation before I wipe this phone and get everything back up on it / restored.

(I wasn't sure what the significance of the eight digits beyond the .005/ were, so I edited it out just to be safe)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! Using the Full OTA Zip or Factory Image?
[Google Pixel 8 Pro] rester555:
Full OTA zip
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you for confirming!

@Dataman100, for your reference, the below and above:

Of course, I was using Magisk Stable 27000, but I'm sure the version of Magisk didn't likely cause the corruption, either.
[Google Pixel 8 Pro] Dataman100:
I thought that as well. I figured there would be a lot more posts if it was something that was happening to everyone.

Ahh, I figured since you were the OP, it was you that had created the process. 🙂

I'm now seeing others being successful with PF and the OTA, but I usually don't use that to upgrade. I just follow the manual steps in post #3.

I guess I'll give it a try here in a little bit and 🤞.

Good luck getting your P8P back up and running.

Thanks!
[Google Pixel 8 Pro] Lughnasadh:
Oh, that screen is not the red eio corrupt message screen where flashing old boot.img then new boot.img most of the time works to get rid of the message. I don't believe flashing old and new boot.imgs would fix that message. I believe the only way to get out of that is to factory reset, assuming you already tried to flash a new image but it didn't work?, but wait for @badabing2003 to chime in. Sorry if I got the facts mixed up....haven't been following this discussion to throroughly.

Just wrote a somewhat related post here.
[Google Pixel 8 Pro] badabing2003:
How do you even get to that screen, Android recovery on Pixels is the upside down droid.

By any chance did you have vbmeta disabled and it got enabled?

I suppose not considering that you were able to flash with Android Flash Tools and still ended up here.

one other explanation possibly would be corrupt userdata.

when you're in bootloader, are you able to get into recovery? by

fastboot reboot recovery

if yes, do you get the above screen or upside down droid?

are you able to initiate a sideload process.

When you attempt a downgrade, it would require a wipe, unless you patch the boot's SPL before downgrading

See this menu option in PF
[Google Pixel 8 Pro] roirraW "edor" ehT:
I documented the steps in a way that's hopefully reasonably user-friendly for everyone, but I was definitely educated by other, more knowledgeable people, and they inspired me to switch from the Factory Image to Full OTA Zip method, and to document it in Post #3 for other users.

There are other users who have summarized it in their own ways elsewhere.

So, as far as writing it out specifically the way I did, yes, I create that, but if it weren't for others including @Lughnasadh, @badabing2003, and possibly others (apologies if I didn't credit you), I would still be ignorant of that method.

Also, it's more like gravity, although far less universal. The capability was put there by Google - it was there to be noticed and used, although certainly, Google doesn't plan for us to root. I also don't have anything to do with the apps and modules that have been developed, which let us do all the root things we can.

I hope you don't take offense at my picking at semantics. :D

Gotcha. Either way, with Post #3 or with PixelFlasher, it's the same difference in the end. PixelFlasher uses the same steps as Post #3, using ADB and FastBoot, et cetera - it makes things quicker/faster/easier. I did do the manual steps for at least several months, or maybe six at the most, before I started using PixelFlasher.

Thank you very much! I wish you the best of luck, too. Thank you, and you're welcome.

Thank you! Okay, I'll wait for @badabing2003 too. I'm in no rush, as it'll take far longer to sync everything back to my phone than to factory reset it.

I've been trying to research if the phone charges while on that corruption screen, or in FastBoot. I tried shutting the phone off with adb reboot -p, but I can't grab the USB cable out of port fast enough when doing so to keep it from turning back on due to the power cable.
[Google Pixel 8 Pro] bdr127:
FYI: If you're rooted (and therefore, bootloader is unlocked), you can use either OTA or factory image.

If you want to flash the factory image, then your bootloader *must* be unlocked.... but it is not a requirement that you use the factory image if your bootloader is unlocked. In fact, it is smarter and safer to flash the OTA, as @roirraW "edor" ehT said above.

In my (absent-minded, accidental) experience on a Pixel 6, and from what I've read from others here on XDA, if you try to flash a factory image to both slots, your phone won't even boot.
[Google Pixel 8 Pro] Lughnasadh:
Just to be clear, did you ever get the red eio corruption message (see pic below) or is the "Cannot load Android System" the message you have been getting the whole time? I had assumed it was the red eio corruption message you were talking about the whole time until I saw your pic with "Cannot load Android System".