yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] leveleyed:
I saw this when using payload-dumper-go.exe to extract the init-boot.img:

Found partitions:
abl (1.8 MB), bl1 (16 kB), bl2 (537 kB), bl31 (106 kB), boot (67 MB), dtbo (17 MB), gcf (8.2 kB), gsa (348 kB), gsa_bl1 (33 kB), init_boot (8.4 MB), ldfw (2.4 MB), modem (105 MB), pbl (49 kB), product (3.2 GB), pvmfw (1.0 MB), system (822 MB), system_dlkm (11 MB), system_ext (288 MB), tzsw (7.9 MB), vbmeta (12 kB), vbmeta_system (8.2 kB), vbmeta_vendor (4.1 kB), vendor (810 MB), vendor_boot (67 MB), vendor_dlkm (27 MB), vendor_kernel_boot (67 MB)
Number of workers: 4

Not sure if it would be in vbmeta (12 kB), vbmeta_system (8.2 kB), vbmeta_vendor or some other partition, or how to extract it using payload-dumper-go.exe.

EDIT: Never mind. I decided to wing it, and tried payload-dumper-go.exe -p vbmeta -o . payload.bin and it worked. Got the vbmeta.img file now!
[Google Pixel 8 Pro] DespairFactor:
that is an OTA, not factory image. That way works, but I was talking about a completely different file.
[Google Pixel 8 Pro] leveleyed:
Not sure if I might have missed it somehow, but despite searching through this quite a bit, I couldn't seem to find any step describing where/how/when to download & install Magisk on the phone. 🤔🤷‍♂️ I managed to figure it out from the Magisk Github link, and installed from the apk downloaded to my PC then copied to the phone after unlocking the bootloader. But there wasn't really any step in the instructions explaining this part.
[Google Pixel 8 Pro] leveleyed:
Sorry, probably should've specified which root method I am using. Thanks, though!
[Google Pixel 8 Pro] leveleyed:
11. fastboot flash init_boot Magisk'd_init_boot.img

12. Temporarily boot into the newly updated/rooted slot, to test to make sure it boots and all seems normal:

fastboot reboot

Now what do I do? Followed all instructions to the letter. Not sure why this is happening. 😭

Was there something else I should've done between extracting the vbmeta.img and flashing it with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ? Did I do it wrong when I extracted it from the OTA payload.bin with the command payload-dumper-go.exe -p vbmeta -o . payload.bin ?? WHERE DID IT ALL GO HORRIBLY WRONG?!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Post #2:

The

Full OTA Zip method

in Post #2 also mentions Magisk a ton.

Please don't use profanity on XDA. Don't sweat - we'll solve it. No, you're supposed to factory reset after disabling Verity and Verification. As I explained before, going from enabled to disabled, you have to factory reset after. This is normal and expected.
[Google Pixel 8 Pro] leveleyed:
I didn't use profanity! I alluded to a swear, but censored the ending of it. For all anyone knows, I could've meant "FFFFFFFFUUUUUUUUUUUUUUUUUUUUDGE!" ;)

Again, sorry, autistic spectrum outbursts, social awkwardness, idiocy, 13-yr-old sense of humor.

And I know the Magisk app is mentioned a ton - it's just not specifically stated in the instructions when to download it from github and install it on the phone before there are instructions on launching/applying it to the init_boot.img file, hence needing to 'figure it out' from what is written. Seriously, this is my second time rooting a P8P, and both times, when I got to the step to apply the Magisk patch to the boot file, I was like, "wait... how do I get the Magisk app on the phone for this part?" (because even though I had done it once a few months ago, I forgot how to get it and install it).

Anyway, just saying, as detailed as the instructions are for every other step, I just figured it was worth mentioning that it could be a bit clearer if there were steps for downloading and installing Magisk.
[Google Pixel 8 Pro] roirraW "edor" ehT:
If you have to censor it, then it's profanity.

In order to use Magisk on the phone to root the init_boot.img, you'd have to download it and install it at anytime before that step. You are correct that I don't spell that out, but I didn't think it was necessary to.

However, I should add a modified version of this part, which is in the Factory Image method, to the OTA one since it has the links:

The Full OTA Zip method instructions came later, so I didn't think about that aspect until now. Thank you.

I don't have time to do so at the moment, so it'll go in my "later" queue.
[Google Pixel 8 Pro] leveleyed:
Almost forgot... 🤦‍♂️ yep, I totally assumed it would factory reset like unlocking the bootloader, so wasn't expecting this 'OH NO! ERROR! 😱'-looking screen about the android system not being able to load. But okay, as long as I didn't miss a step of patching the vbmeta.img file with magisk or something, I'll do the factory reset and hope it all works out okay. 🙏 Thank you!!! ☺️

Also, I think telling someone with ASD/autism to not sweat stuff may be equivalent to telling someone with chronic depression they should just cheer up & be happy. Believe me, if I could shut if off and not react the way I naturally do to unexpected stuff like this, I would be more than happy to do so. It's a daily struggle. 😖
[Google Pixel 8 Pro] leveleyed:
Ok cool. THAT is the part I think I missed both times - the links not being in the OTA method.

And thank you for putting together such a helpful and detailed guide for this!!! 🙌

Also, I think censored profanity being considered profanity would lead into a philosophical debate. Rather than getting into that, I'll just avoid it by saying that I'll try to remember to avoid even censored profanity from now on. (y)
[Google Pixel 8 Pro] roirraW "edor" ehT:
It is certainly understandable that it might be something you're not expecting.

You're welcome!

I don't think you had told me before I had said that, otherwise I might've said something different.

This doesn't guarantee that I'll remember, however, so there is always the chance I might say something like that again, but I'll try not to. In the end, I was trying to convey that there's no big issue.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome!

Thank you!
[Google Pixel 8 Pro] leveleyed:
Okay weird. When I'm in the process of setting up the phone, I get to the point where it is asking about importing stuff from my backups. And it lists the backup frim my old Pixel 5, but instead of the backup from the wonky P8P, it lists Asus ZenFone 3 Zoom (ZE553KL) as my other backup. 😳

I was hoping I could restore stuff like photos, SMS, and contacts (everything except the apps since I think, if anything, that would most likely be the source of the problems I've been experiencing) from the bad P8P. But now I'm not sure if I should even use this incorrectly-labeled P8P backup at all out of concern that contacts, photos, or other data might be corrupted or restored incorrectly. 😟
[Google Pixel 8 Pro] Chickenkillla81:
We're you using an integrity fix module with magisk on the bad p8p? I noticed my p5 is called eureka, I think it is. Tripped me out first time I saw it. Could be that
[Google Pixel 8 Pro] leveleyed:
Yes, using play integrity fix. Okay. That's probably it then. Will try the restore of all but apps.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Personally, all apps that it backups and restores are ones from the Play Store, so there *shouldn't* be any issues restoring those and their data, but of course you can pick and select more suspect ones to not restore.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Pixel Phones Getting a Satellite SOS Feature

Spotted inside the latest build of the Adaptive Connectivity Services app, a new feature called Satellite SOS is being prepared by Google for Pixel devices. Unknown exactly which Pixel phones will receive support, we do at least have a basic understanding of how this feature... #Google #Pixel8

www.droid-life.com
[Google Pixel 8 Pro] Oganyr:
Anyone way for the P8P to pass the safety net STRONG? I think Uber Driver App need it or it'll not let you log in
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hi @Oganyr, welcome to XDA. You already created a thread about this subject just today:

UBER drivers app working with Root ?

Hi do anyone had success with the Uber Driver App on a rooted Rom ? Tried a few on my P8P with all the modules possible but none prevent UBER from detecting root... Even GrapheneOS with no Root dont work with the Uber Driver app

xdaforums.com

Please review XDA's Rule 5 regarding duplicate posts and how often you can bump an existing question of yours. If you had posted here first, it would be fine, but since you made your own thread, please keep it there instead.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android Security Bulletin—March 2024 | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
March 4, 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

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Two Google Pixel Help Community annoucements:

Google Pixel Update - Mar 2024 - Google Pixel Community

March 2024 Feature Drop - Google Pixel Community
[Google Pixel 8 Pro] Morgrain:
Here is the blog post with more in-depth info

Pixel feature drop: New productivity tools and advanced health features

The March Feature Drop brings productivity and health features to the Pixel portfolio, including new features for first-gen Pixel Watch.

blog.google

--

Those feature drops are getting less exiting with each passing month. If we look at those "features"

10 bit photo/video uploading for Instagram -> quite a stretch to call that a new feature, that's merely a basic necessity that should have been available at launch. It would have been a feature if Google managed some sort of basic API thing where ANY app on the phone would be able to process the 10bit data. Or at least all of the big social media apps (Whatsapp, Telegram, Instagram, Patreon, Discord etc) But Google calls it a "feature" if merely one app out of thousands can manage? Google... if we get 1 app support each 3 months, we'll just need a couple of millenia to make it a basic Android feature. Easy, right?

Google really needs to get serious. When Google embarked on the 10bit Ultra HDR journey, they should have changed the requirements for developers to include 10bit support in their apps. Just like Apple forces developers to support new features to make it easier for their customers to enjoy new features, Google needs to be stricter with the requirements. It's a complete joke if they create a new "basic" feature for the operating system, but half a year after release, only one app supports it natively.

Improvements to Call Screening -> only available in the US / other English speaking territories. It's also just a "hello" that you can press. I'd barely call that a new "feature".

Circle to search -> was already available for the P8 Pro for some time now

App screen sharing -> ok-ish I guess, the only real "feature" worth noting

Fast Pairing -> already available, they just "moved" a copy of the info to the upper menu - that's not a new feature, that's just a re-structuring of the UI

Docs markup -> I'm a bit at a loss for words here. Google often attempts to artificially enlarge these feature drops with barely noteworthy additions, but markup? The ability to... write with your hand in a Google document? What? That's... new? Are you telling me that before, a touchscreen capable Android device was not able to let you write with your finger in a docs document? Oh Google, this is not a feature to brag about... that's like the most basic of all features in a document app on a smartphone.

It's also odd that the Pixel Watch 2 is getting no love / new feature. Workout detection only works occasionally, and battery life needs some software improvements.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you! Adding to the OP(s).
[Google Pixel 8 Pro] DanielF50:
Updated to March build, everything went smoothly & all my Magisk modules still work (YMMV).

For what it's worth:

Bluetooth connectivity is fixed - I can finally listen to music on my Pixel Buds while my Galaxy Watch 5 is connected to my phone, without the Buds constantly dropping connection [1]. I can't believe it has taken Google since initial A14 release to fix this.

Camera zoom bug introduced in Dec update is still yet to be addressed (can't zoom when opening camera if "manual lens selection" is toggled) [1][2][3].

WhatsApp notification bug where persistent notifcations for unopened chats are dismissed once opening one chat, is still present [1].
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! Are you using Platform-Tools v35.0.0, by any chance?
[Google Pixel 8 Pro] DanielF50:
Yeah, I had to update to v35.0.0 as whatever Platform-Tools version I was on before said the update was finished, rebooted my phone, but the phone just wouldn't boot - as soon as I updated and ran flash-all.bat again, it booted right up.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Good to know. Will add to OP and other threads.

Edit: Apparently 33.0.3 still worked on the Pixel 7 Pro, so who knows...
[Google Pixel 8 Pro] roirraW "edor" ehT:
I got the following with Pixel Xpert v3.3.2 (336) Stable on my P7P, so you might want to wait for an update to Pixel Xpert:
[Google Pixel 8 Pro] stardomains:
I'm on AP11.231215.009 and opted out of beta. I don't want to wipe device. OTA not showing March update where to my understanding I would be able to go to stable without wiping. Can I just use full OTA method via platforn tools to go to today's stable release image without a wipe instead? https://developers.google.com/android/ota
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yes. You might still get a prompt after, offering and OTA back to beta - just don't take it. Eventually it'll recognize that you're opted out of the beta and stop offering another OTA.
[Google Pixel 8 Pro] stardomains:
Success. Worked great. Thanks!
[Google Pixel 8 Pro] DanielF50:
Fyi, I have encountered one slightly major issue with the March update. If you're rooted and using "Hide My Applist" for your banking apps I would suggest not updating.

Any apps that you apply a custom template to will not launch and will hang on their respective splash screen - they also seem to slowly take up a high amount of storage space while doing so??

Quote below is a direct link to the HMA thread (only 2 of us have narrowed it down to this so far).
[Google Pixel 8 Pro] jjlane86:
Firstly, thanks for everyone's assistance on these forums, I have been rooting since the OG pixel using these forums.

However, I am still a mostly casual user and root roughly every 1-2 years, so when i re-root or upgrade phones, it's kind of like relearning all over.

I have successfully unlocked bootloader, re-enabled developer options and USB debugging along with USB Data Xfer enabled, and have the magisk 27.0 and init_boot.img downloaded on the phone's internal memory.

My question is...in previous years I always extracted the factory images into the platform tools folder, did the flash--all and then patched boot.img. So based on THIS guide, we are only patching the init_boot and to both slots(Whatever that means?)...Am I still supposed to extract the factory image that has radio and bootloader and the flash all batch files into the platform tools folder?

This phone is brand new, unlocked from google and reading all the warnings about using the Full OTA method vs factory image because of the 2 "slots" has me a little confused and worried...
[Google Pixel 8 Pro] roirraW "edor" ehT:
Whether using the factory image or the OTA, my SoP has been to do just that - extract to the same Platform-Tools folder. So your answer is yes. :)

IMHO, I prefer the Full OTA Zip method now. If you use that method, I just suggest following the instructions for it exactly, during which you end up flashing the OTA twice. Each time, it changes slots before flashing automatically, so by flashing it twice, both slots are fully bootable and working.

Using the Factory Image, only the most recent slot you flashed with the Factory Image is actually useable, so if something bad enough happened with your current bootable slot, the alternate slot wouldn't do you as much good as it could, plus the fact that at least some brand new - never taken an OTA Pixels don't contain even a bootloader on the other slot, you should go ahead and flash whichever method you choose twice, even though flashing the factory image twice will still effectively only leave the most recently flashed slot as useable - but it'll at least have a bootloader on it.

Without a bootloader on the other slot, under certain conditions if your current booting slot becomes unbootable, then the only solution is to RMA to Google. So either follow the directions exactly to flash either method twice. I just recommend the OTA method over the factory image these days.

I hope that helps.
[Google Pixel 8 Pro] jjlane86:
So, I got impatient, and went ahead and flashed the init_boot and everything worked out fine, but if understand what you are saying now, is I have a currently bootable rooted distribution on only one slot currently? I flashed the patched init boot and then just set up my phone. How should I now go about setting up the other bootable slot?
[Google Pixel 8 Pro] roirraW "edor" ehT:
That is correct if you used the factory image, if you hadn't already taken any OTAs before that.

You'd have to use the Full OTA Zip method, which describes flashing the OTA twice. You can flash the rooted init_boot.img to both slots or leave one slot unrooted if you want, it's your choice.

Your existing factory image-flashed slot won't work as is once you flash the OTA (which will automatically flash to the other slot first), therefore you should flash the OTA again afterwards, then both slots will be fully useable.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I have no idea, since you were able to flash back fine. I'd suggest trying the Full OTA Zip method instead.

Edit: Probably won't lead to anything, but have you tried checking and comparing the hash of the zip?
[Google Pixel 8 Pro] Minux31:
After flashing back to february version, I updated with OTA directly on the phone and reroot my phone successfully after, thx for the suggestion.

And yes, I verified sha256sum of zip I downloaded, and it was good. No idea what appended (tried twice, same error each time)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Indeed, strange. Thanks for reporting back, and glad you had success with the OTA.
[Google Pixel 8 Pro] x111:
how to disable haptic fingerprint after march update ?

is there any solution ?

I disabled any haptic vibration settings, still vibrate.

and to downgrade we have to wipe !!

thanks for your replies.
[Google Pixel 8 Pro] Aks:
So, I managed to get the same issue you reported after latest update. It happened to me on the QPR build too, and guess what? Lsposed was the troublemaker. I tried everything, different builds, but Lsposed just wouldn't open, it kept getting stuck. Weirdly, PixelXpert worked even though HMA wouldn't budge, and all my banking apps were frozen solid.

Anyway, I switched to the stable build and everything magically started working again. This makes me wonder if maybe some stuff from the QPR3 build snuck into the stable version, causing problems with Lsposed and then messing with HMA as well. (Just a hunch, though!).

Now, as soon as I removed one app from HMA list, it worked well (It didn't need HMA but I still kept it hidden, just in case).

Edit: I missed one thing. After flashing update, somehow my device restarted 3 times and then it booted and works fine now (Not really sure what caused this).
[Google Pixel 8 Pro] DanielF50:
Weird, I wasn't having any issues with any other xposed modules other than HMA.

I think I've fixed the issue now though... maybe?

I had pumPCin's LSPosed fork (v1.9.3-7229) installed due to the offical repo being switched to read-only - as a test, I uninstalled this fork & reinstalled v1.9.2 from the official LSPosed repo & now I am able to use my banking apps again.
[Google Pixel 8 Pro] onesolo:
I have a similar problem!! Also a long time nexus/pixel user. Rooting my devices for a long time, so I constantly every month sideload the full OTA file. I discovered today, actually trying this on my previous Pixel 6 device, that if I try to boot on the other slot, it wont boot at all!! On my P8p it says that my device is corrupt and I have to go back to bootloader and switch to the other slot. (short story, as I said before the same happens on my P6 but it won't says that my device is corrupt, only goes directly to bootloader).

On my P8p I tried to switch slot and go to recovery and sideload again the OTA but happens the same.

Is this normal or is it really possible to have both slots fully bootable??

When I got my P8p a month ago, I just sideloaded the full OTA of the QPR beta that was around that time and rooted the device. Now I jumped to the stable by sideload the OTA. If by sideloading the OTA is possible to have both slots fully bootable, why is it that in this moment I can't do this??

In my P6, as it's clean and I can experiment with no problems, I even flashed the factory image on both slots but I still can only boot only on one slot...

Can someone please help me on this??
[Google Pixel 8 Pro] rester555:
Why did they set to read only? Any info on that?
[Google Pixel 8 Pro] DanielF50:
Nothing malicious - just people insulting / abusing the developers over end users using LSPosed to cheat in games as far as I can remember...

They halted development indefinitely in protest, so pumPCin forked the project and picked up development.
[Google Pixel 8 Pro] rester555:
Wow, that sucks.
[Google Pixel 8 Pro] roirraW "edor" ehT:
First, are you saying that you have the QPR Beta OTA on one slot, and the Stable on the other? If so, that is why at least one slot won't work right since the same app data is used by both slots. Both slots should have the same firmware on them in order for them both to be able to be used.
[Google Pixel 8 Pro] Aks:
Oh nice, I am also using v1.9.3-7229 fork. Let me switch to v1.92 and will confirm if it resolves my issue. Thank you @DanielF50
[Google Pixel 8 Pro] DanielF50:
Someone in the HMA thread said they're already running the official fork (Pixel 6) and it doesn't work, so it might just be the process of re-flashing LSPosed that fixes it? I'm unsure.
[Google Pixel 8 Pro] onesolo:
No, I'm not saying that I have on one slot the QPR and on the other the last stable. It was just to say that after I got the P8p in January, I flashed the full OTA of the QPR but nos I flashed the full OTA of the march stable.

Right now I have the stable on one slot and I can't boot on the other slot!!! Can anyone explain to me why this happens?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I hadn't updated yet, so I'm installing the OTA to both slots now, and I'll get back to you on what happens when I change slots after to see if it does the same thing or if something else is going on.
[Google Pixel 8 Pro] JazonX:
What's the current fastest / convenient method to go through / test through PIF files to find a working one?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I've flashed the March OTA to both slots on my P8P, initially booting into each individually after each slot was flashed - as is my SOP, then after booting into the second flashed slot, I changed slots and successfully booted into the other slot with no issues.

I'd suggest re-flashing the OTA (it'll change slots automatically) and Magisk'd init_boot.img if you're rooting. I don't know what the cause of the issue could be.