yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] badabing2003:
To eliminate any possible confusion.

A normal Pixel would have both Verity and Verification Enabled.

People who want to apply custom ROM or Kernel would most often need them disabled.

Each time you toggle verification from enabled to disabled, you would need to wipe your phone.

You don't want them disabled unless you want to apply custom ROM / Kernel, and the custom ROM / Kernel requires it to be disabled (not all do), and you're ready for a wipe.

The flag in PF

Disable Verification is by default false, which means you don't want to disable, (I know double negative), I just want you to be clear on what the flag is telling you.

This would be for most users who don't want custom ROM / Kernel.

To be clear on the terminology, it is both slots, not partitions, the phone as many partitions, not just two.

What you read is correct, a brand new phone has only one slot flashed.

And you're correct, if you have done any OTA, either manually sideloading or through the phone's system updater, then the other slot would no longer be blank.

Based on your screenshot, your phone will be updated to November release and be rooted.
[Google Pixel 8 Pro] bigAL99:
many thanks for clearing all that up for me. I apprecaite your time.

updated without a hitch.

thanks again
[Google Pixel 8 Pro] Zilla0617:
After my mishap of using Pixelflasher for the Nov patch (bootlooped), could someone detail the proper method in updating OTA while maintaining disabled verity and verification as well as root. In the main OP of Pixelflasher instructions, there was no mention on how to maintain disabled verity & verification when updating OTA.

Also when it comes to flashing both slots, I read that you supposed to flash back-to-back. I did just that for the Oct patch when I first received the P8P. However, when i encountered issues flashing Nov patch I tried switching to the other slot and realized that there was no OS installed.

I'm learning how to use Pixelflasher, i've been doing everything manually for years. Thanks
[Google Pixel 8 Pro] mko000:
Are there any known problems with the current platform tools 34.0.5 or are they good to go?
[Google Pixel 8 Pro] badabing2003:
I'm not sure what your mishap is about, but if you want to disable verity / verification, you would need to enable advanced settings, and then you would see the options.

You select those options and PF will apply when flashing and will also remember.

In the next version PF will also check if what you're flashing (verity , verification wise) if it mismatches with your current and warn you about it as an extra check.

None so far
[Google Pixel 8 Pro] Zilla0617:
I recall seeing a warning about mismatching verity and verification, but my active slot already have verity and verification disabled so I was not sure why I seeing that...Unless it was referring to the inactive slot.

As far as my mishap, im referring to this (posted in a different thread):

So Im stuck with bootloop on P8P. I flashed Nov ota using pixel flasher back to-back assuming that both slots were flashed. I then flashed magisk patched init_boot using pixel flasher and rebooted. When I rebooted making sure i attained root I flashed a custom kernel, when it rebooted I entered into a bootloop. I tried restoring stock kernel, restoring boot image, sideloading the ota again. All failed. Not sure what i can do to restore without losing data. My phone is bootloader unlocked. Thanks

P.S. i tried switching to "a" slot since my active is "b" but there was no os installed ( android on its back). Out of ideas...

I ended up having to use android flash tool and it factory wiped my device
[Google Pixel 8 Pro] badabing2003:
Let me break down your steps

Can you elaborate on this, exactly what you did?

Did you select the stock boot or the patched boot.

Back to back means what?

You flashed, you got no errors, it booted to system and it was updated but not rooted?

You flashed again, and it switched slots and booted fine?

Did you do Flash boot?

and just applied the patch?

And you got root and all was working at this point.

Doesn't this tell you that the issue is with custom kernel or the way you applied it or the tool you used to apply it?

Why would label it as PF mishap?

You see why providing support file is useful, because it can trace your steps and see where if anything went wrong.
[Google Pixel 8 Pro] badabing2003:
It just that wording like when it's obviously an outcome of flashing custom kernel makes other people question the program.

I get "I hear PF is causing bootloops" comments.

I'm not suggesting that PF is flawless, but I put a lot of effort to make sure it is as good as it can be.

I don't know if people even bother reading the console display or even checking the screen / status, when you select your device it tells you a lot of things about your device, it tells you about your current slot (which by the way it is also on the UI next to your selected device), it tells what firmware you're running, if it is rooted or not , and on and on.
[Google Pixel 8 Pro] Morgrain:
I used Pixelflasher for the first time to update to November update, did all the steps as described in the original post, and it worked without issues.

I was a bit surprised that I didn't have to flash/that the program didn't flash the patched magisk file after applying the OTA update, but I did every step incl the patched magisk file, selected it before activating the flashing, and it seems that root has correctly been installed.

Thanks for this great program. Makes my life much easier. I don't mind using ADB, but over the years I did sometimes had typos in my commands, which actually lead to bootloops, so this should probably help me avoid that.
[Google Pixel 8 Pro] badabing2003:
Thanks for the comments.

Depending on which boot you select from the list, that would be applied with the OTA, the fact that you had selected the patched boot is the reason why you're rooted.

Thanks

PF is primarily is aimed for people like you, who know or learn the manual way, understand what is going on, and use the program to avoid typo mistakes or manual lookup for commands, and speed up the process.
[Google Pixel 8 Pro] Zilla0617:
To be fair I never claimed that PF was the reason of my bootloop. I took the time to detail the process I went through and even asked questions which you yet to acknowledge. But instead of attempting to provide insight to questions posed, you want to harp on semantics.

The UI console does not tell me "How to do something" especially when frozen.

No response on the situation of disabling ver & verf. when flashing monthly ota patches...got it

No comment on potentially why PF freezes during the flashing process...understood.

Let's focus on PF causes bootloop.
[Google Pixel 8 Pro] badabing2003:
View attachment 6030571

View attachment 6030572

View attachment 6030575

View attachment 6030573

View attachment 6030577

But what use is any of this if you don't bother reading.

And by the way, you seek assistance but fail to fulfill the most important requirement, which is providing a support file.
[Google Pixel 8 Pro] Zilla0617:
Whatever makes you feel better...keep pretending you answering questions. Im good... LMAO
[Google Pixel 8 Pro] Homeboy76:
Did you read the OP?

@badabing2003 is one of the most helpful XDA Member I know. If you want assistance resolving your problem: attach the Support file.
[Google Pixel 8 Pro] HipKat:
Do you have any idea of how many people use this without issue and have never had an issue because they simply read the OP's? Your issue is 100% user error, not the fault of the PF.

Suck it up, learn from it and go on.
[Google Pixel 8 Pro] Zilla0617:
Why is the peanut gallery adding their 2 cents? I said Im good...
[Google Pixel 8 Pro] xdrc45:
Been using PFT for over a year and for every monthly update also without any issues ever, not once.....and I'm good too! 🤣 Absolutely the best Pixel tool/program available for our devices period! Thanks @badabing2003 for all your hard work and all your continued support!
[Google Pixel 8 Pro] bsg411:
Is there any way to confirm both slots have been flashed?
[Google Pixel 8 Pro] mac796:
I finally decided to try this tool. Been using it to update the last couple months and keep root. I got to say this is one of the most well thought out , well laid out tools made for us to use to date. I thank you for your time in making this, and sharing it with us. 👍👍. I love the option to disable modules. Is there a way to unhide Magisk. In case you couldn't boot back to system to do it yourself?
[Google Pixel 8 Pro] badabing2003:
Thank you for your kind words.

Unhide Magisk is not going to help you with booting back, besides I don't know a direct way.

What you really need is being able to be rooted without running modules, and for that, check the details in Magisk installer | Special Magisk.
[Google Pixel 8 Pro] chill145:
Users like the one you're responding to is why the ignore feature is so helpful. Like you stated, @badabing2003 is so helpful and this tool is invaluable. When I had my P6P, I avoided monthly updates because it was such a process. Once I got my P7P and discovered this tool, I update the day OTA is released because this tool makes it so easy and it takes minutes. My only complaint is @badabing2003 won't accept donations.
[Google Pixel 8 Pro] badabing2003:
Check the firmware version on one slot, switch slot and check if it also matches the one you just flashed.
[Google Pixel 8 Pro] bsg411:
Can this be done After I have flashed? Can you use Pixel flasher to just check firmware and switch slots without flashing?
[Google Pixel 8 Pro] badabing2003:
Of course

Start PF

Scan for devices, and select your device

See what it reports about your device in the console

Switch slots

Scan for devices, and select your device

See what it reports about your device in the console
[Google Pixel 8 Pro] bsg411:
I'll check out it....Thank you very much !
[Google Pixel 8 Pro] DRatJr:
Anyone have a short, confuse way to upgrade via PixelFlasher?

I am used to only using boot.img and not sure what's changed with the 8 Pro to be able to update to OTAs with the tool.

Thanks.
[Google Pixel 8 Pro] simplepinoi177:
One of the wonderful insightful things @badabing2003 has done with this tool is set up checks and automation so easy and seamless that using the tool and following the steps in the OP is "short" in and of itself. For example, even if you were used to boot.img and went about it that way, PF would choose the correct image (not boot.img but init_boot.img) by detecting your device/phone and you wouldn't need to do much (in comparison with manually flashing/sideloading yourself)....

Just read & observe the steps in the OP, and you can progress/continue with confidence -- @badabing2003 wouldn't allow PF to steer you wrong!
[Google Pixel 8 Pro] DRatJr:
I just did an ota upgrade while retaining root and you're right. The progress went by very easily and required very little input from me.

I rebooted however and I'm assuming it booted to the second slot to where it said no command given with an Android icon. Do I need to flash the other slot? Or what would I need to do so that this doesn't happen again?
[Google Pixel 8 Pro] badabing2003:
Let me get this right, you were upgraded and rooted, and it was working fine and then you just rebooted and ended up in that state?

It does not make sense, it should not happen, something must have happened in between that and the reboot.

Do you recall what you did?

Please provide a support file and I'll take a look.
[Google Pixel 8 Pro] DRatJr:
This is genuine right? Sorry might be me just seems like sarcasm lol. Either way tho I'd live to provide the file. Let me see if I can find sorry l support file.
[Google Pixel 8 Pro] DRatJr:
Not let me see if I can find it, let me get it when I get back to computer sorry.

I'm guessing because maybe only one slot is active or flashed?
[Google Pixel 8 Pro] badabing2003:
Yes it is genuine.

Whichever way you fancy.

View attachment 6031518

View attachment 6031519

View attachment 6031520
[Google Pixel 8 Pro] DRatJr:
I figured you've always been super helpful in the past. As soon as I get to work I'll upload it here. If you've got fifteen minutes I should have them uploaded by then. Thanks man.
[Google Pixel 8 Pro] DRatJr:
Here is the support file.
[Google Pixel 8 Pro] badabing2003:
What is the current state of your phone?

You said you were updated and rooted fine and then rebooted and was in recovery.

The last thing I see in the logs is you flashing the OTA.

After that there is nothing.

So nothing was done in PF, I don't even see the reboot back to system.
[Google Pixel 8 Pro] DRatJr:
I had to reboot again and it booted fine. Haven't rebooted since but didn't want to have the same issue if so.
[Google Pixel 8 Pro] badabing2003:
Are you rooted?
[Google Pixel 8 Pro] DRatJr:
Yes I'm rooted with Magisk 26401.
[Google Pixel 8 Pro] badabing2003:
Ok All good then,

You must be on slot A now, if you are not, let me know.

If you are, I suggest you flash OTA one more time, you don't have to do the complete process, just select device, boot and hit Flash Pixel Phone

This way you'd have both slots current and both bootable.
[Google Pixel 8 Pro] DRatJr:
I am on slot A.

So reboot to bootloader, plug phone in, hit boot, and then hit flash pixel phone? And then I'm good to go?
[Google Pixel 8 Pro] badabing2003:
You don't even need to reboot to bootloader, PF will do the right thing for you.

In this case it actually reboots to sideload mode since you are using full OTA image (good choice)
[Google Pixel 8 Pro] DRatJr:
Just to confirm, plug in phone in normal mode, select device, select patched init boot, hit Live Boot, then hit flash pixel phone?
[Google Pixel 8 Pro] badabing2003:
no don't hit Live boot,

Just hit the Flash Pixel Phone
[Google Pixel 8 Pro] DRatJr:
Sorry for being dumb lol. That worked tho. Thank you!
[Google Pixel 8 Pro] badabing2003:
Happy to hear that it worked, you're welcome.
[Google Pixel 8 Pro] badabing2003:
New Release:

Nov 12, 2023 v6.0.0.0 release

More verbose logging and additional debug messages for troubleshooting.

Renamed the Verbose label to Debug.

Improve UI responsiveness when running background tasks.

Automatically detect vbmeta state for both slots, and warn if the selection would have wipe implications (this is for verity / verification disabling).

Removed Check Verity button, (verity / verification), replaced with vbmeta state reporting for both slots as part of device details.

Show Bootloader version as part of device details.

Show slot related details such as slot-retry-count, slot-unbootable, slot-successful as part of device details.

Added Reboot to Sideload option.

Graphical display of device's slot and root status.

In most cases long background processes are automatically killed with proper timeouts (when possible) and reported to unfreeze PixelFlasher.

Reworked device detection / update / refresh, reboots, PixelFlasher now automatically detects device state changes and waits exactly the time until the device state changes to the expected state. Less dependency on arbitrary timeouts.

Improved support logs sanitization.

Detect free space on the computer and block flashing if less than 5G of storage is available.

Refactor flashing function.

More response console widget log messages.

Detect currently installed OS version and block flashing older OTA (Android by default allows flashing but fails to boot).

Detect, warn and block flashing if bootloader is locked for flashes that require bootloader to be unlocked.

Added wipe option for custom flashing to easily wipe the phone when flashing vbmeta to disable verity / verification.

Report if the device is unlockable.

Bug fixes, lots of changes under the hood and miscellaneous improvements.

Added option to delete specified libraries from the PixelFlasher bundle, to let the system library be loaded instead. Needed for newer OSes that require updated libraries. See Symbol Lookup Error #109, and After a large system update (manjaro), do not work now. #111

Additional support for Scrcpy of non-Windows platforms.

Updated XDA links
[Google Pixel 8 Pro] HipKat:
Damn, that's a big changelog.
[Google Pixel 8 Pro] thefinger:
What happened to the dmg package for version 6.0.0.0
[Google Pixel 8 Pro] badabing2003:
Sorry, I don't know, but all attempts at building a dmg failed.

They get built by Github actions on Github, it usually takes 5-6 minutes, and now it takes very long time and it's eventually fails.

Perhaps something is broken on Github, or the resources that it accesses.

I can't try too many times otherwise my runtime quota will be hit and I won't be able to build anything.

You can see all the failed attempts here, here, here, and here.

If you want, you can fork the repo on Github, and try running the MacOS actions.

View attachment 6032388
[Google Pixel 8 Pro] thefinger:
Can you target a different python version? The error is that:

npm ERR! ModuleNotFoundError: No module named 'distutils'

This is because the module distutils was removed from python 3.12.0

That module is still on 3.11.0
[Google Pixel 8 Pro] badabing2003:
New Release:

Nov 13, 2023 v6.0.1.0 release

Added settings option to enable / disable free storage space check.

Improve storage check to follow symlinks and return the partition free space where the data resides instead of where the symbolic links resides.

Added command line support for specifying PixelFlasher config json file, use -c or --config flag followed by full file path of configuration json file.

Added command line --console (only useful on Linux / Mac) to display all PixelFlasher output to console, useful when troubleshooting.

Further improved handling of large file extraction on low memory computers.
[Google Pixel 8 Pro] badabing2003:
Thanks

See the releases section, there is a Mac version in 6.0.1.0 now

It took 50 minutes to build, ouch.
[Google Pixel 8 Pro] thefinger:
50 minutes ?! Ouch!

You sir are a true scholar!

Thank you for the extra love!
[Google Pixel 8 Pro] Voxilli:
I am back on Android after a brief foray in iOS (boo!). I used PixelFlasher to root. I currently have Magisk 26300 installed. I downloaded [14.0.0 (UD1A.231105.004, Nov 2023)]. What are my exact steps to update the OTA while keeping root? PixelFlasher has my platform-tools folder selected along with my phone. Do I Browse for the OTA file and Process it? Or what are my steps here?

Second question. Last time I was on a Pixel and wanted to update Magisk, I could just install to inactive slot. Would I still do that after updating the OTA?

Thanks in advance.
[Google Pixel 8 Pro] badabing2003:
Welcome to the good side :)

Just follow the OP from the main thread of Github, both linked in this threads OP and also in my signatrure, I think it should be clear, and if you still have questions come back and ask.

Nope, no need for any of that, you do it once with PF, it becomes clear how easy it is.
[Google Pixel 8 Pro] badabing2003:
Update Release:

Nov 14, 2023 v6.0.1.1 release

Bug fix: Make sure Low memory settings are loaded at startup.

After flashing factory or OTA, on last reboot to system, increase the wait from 60 to 90 seconds to make sure the device loads all the way to system and does not timeout PF. Although the error message is benign, it creates unnecessary anxiety seeing an error message in the console and thinking that something is wrong.

Bug fix: Available storage was not computed correctly on Linux platform.

Fix and speed up MacOS platform build.
[Google Pixel 8 Pro] Ultimoose:
Thank you sir.
[Google Pixel 8 Pro] dDoctar:
I am getting some error trying to flash the patched image. After the initial process, it presents me with this. I can confirm my device bootloader is unlocked. This has only started happening on attempt to flash the new QPR b2

Device Model:

Device Active Slot:

Device Mode: f.b

Has init_boot partition: False

Device Bootloader Version:

Device Unlocked:

Device Unlockable: Yes

slot-retry-count:a:

slot-unbootable:a:

slot-successful:a:

slot-retry-count:b:

slot-unbootable:b:

slot-successful:b:

2023-11-16 10:22:51 WARNING: Bootloader is locked, skipping flashing ...

2023-11-16 10:22:51 Getting device: xxxxxxx state ...

Rebooting device: xxxxxx to system ...

ADB waiting device: xxxxxx for device ...

2023-11-16 10:23:34 Getting device: xxxxxxx state ...

Device is now in adb mode.

Flashing elapsed time: 286 seconds
[Google Pixel 8 Pro] badabing2003:
Please provide support file so that I can take a look.

It's not supposed to return empty string.
[Google Pixel 8 Pro] dDoctar:
Already attached to original post
[Google Pixel 8 Pro] badabing2003:
Sorry about that, didn't realize you had attached the support file.

Can you reboot the device into bootloader mode, and then hit the Device Info button

View attachment 6033450

And create another support file please.

I wonder if the fastboot response changed with QPR b2,

I see you're using Android platform tools 34.0.5-10900879

I'd be curious if you change the platform tools back to 33.0.3

and get the Device info again while in bootloader mode

I'd compare the two to see if anything changed.

Basically PF is trying to see if your bootloader is unlocked and is getting a empty response instead of a yes and is blocking flashing.

Thanks

Update:

I'm still interested with the above so that I adjust if anything has changed, you can get rooted again by simply selecting the patch in the boot list and hitting the Flash Boot button to the right.
[Google Pixel 8 Pro] dDoctar:
I have attached both with 33. and 34.
[Google Pixel 8 Pro] badabing2003:
Thanks

I see that both versions reported correctly.

I also see that flashing the patch failed for whatever reasons.

Flashing patched init_boot ...

2023-11-16 11:10:26 ERROR: Encountered an error while flashing the patch.
Aborting ...

2023-11-16 11:10:26 INFO: Flashing was aborted.
This could be user initiated or a problem encountered during flashing.

I'll add more debug statements to print out why it failed, is it possible that it was unplugged during that flashing?

Are you able to select the patch boot, hit Flash Boot and get it rooted?
[Google Pixel 8 Pro] badabing2003:
Update Release:

Nov 15, 2023 v6.0.1.3 release

Cleanup temporary created files when using low memory option.

Don't wait for device to be available in adb when wipe option is selected. (The user would need to setup the phone for the first time, enable developer options and enable debug, which could take a while)

Add more debug messages for troubleshooting.

#117 psutil is not reporting free storage correctly on Linux platform, use shutil module instead.

Print available memory when processing Image.
[Google Pixel 8 Pro] eairknight:
View attachment 6033595

error during flashing... attaching log file, would really appreciate a bit of help :)
[Google Pixel 8 Pro] badabing2003:
USB drivers, I saw that you initially had really old Android platform tools, so most likely USB drivers are not current.

Download the latest (link in the help menu) install them

do fastboot --version you should get 34.0.5, do adb --version you should get 34.0.5

next do adb reboot bootloader

then do fastboot devices

You should see your device I listed in there, if you do, you're set.

At this point your OS is updated, the only thing that is not applied is the patch.

Once you fix the USB drivers, all you have to do is select the patched boot from the list, and hit the Flash Boot button to the right of it, this will just apply the patch and you should get rooted.
[Google Pixel 8 Pro] eairknight:
View attachment 6033753

updated them, hit "Flash Boot", didn't work :(
[Google Pixel 8 Pro] badabing2003:
Your bootloader is locked.

View attachment 6033766
[Google Pixel 8 Pro] eairknight:
jesus. thank you. that was extra retarded of me.
[Google Pixel 8 Pro] Voxilli:
It went perfectly fine. No issues at all! Thanks again for the hard work.