yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] badabing2003:
Update Release:

June 24, 2024 v6.9.8.0 change log:

Improve Check keybox.xml to report if the certificate is software signed, also report about all included certificates.

Added settings option Keep temporary support files in case one needs to inspect the support files.

Add Github action to build on MacOS 12, MacOS 11 runner has been deprecated.

Update Pixel beta links from A14 to A15.

Minor bug fixes and improvements.
[Google Pixel 8 Pro] HipKat:
Nice.

Say, what is the Telus version for the June update?
[Google Pixel 8 Pro] badabing2003:
Not sure I understand the question.
[Google Pixel 8 Pro] Lughnasadh:
Telus is a Canadian carrier. If you don't use them, use the global version.
[Google Pixel 8 Pro] HipKat:
Thanks, I couldn't remember ever seeing that one before
[Google Pixel 8 Pro] mko000:
@badabing2003 May I humbly request your advice?

I am still on the May firmware and Android seems to have automatically done an OTA update and is now prompting me to restart via notification (Android 14 - Restart your device to complete the update).

I remembered that PF had a functionality to cancel an OTA update, but that doesn't work for me:

2024-06-27 23:07:38 User Pressed Cancel OTA Update
Pushing local file: ...\AppData\Local\Temp\_MEI142042\bin\update_engine_client to the device: /data/local/tmp/update_engine_client ...
Return Code: 0
Setting permissions 755 on /data/local/tmp/update_engine_client on the device ...
Return Code: 0
Cancelling ongoing OTA update (if one is in progress, ignore errors) ...
[ERROR:update_engine_client_android.cc(316)] Status(-8, EX_SERVICE_SPECIFIC): '1: No ongoing update to cancel.'
Resetting an already applied update (if one exists) ...

What should I do? Should I just manually flash the full June OTA right now? Will that fix any problems? I'm scared that verity/verification become enabled.

I attached my support file.

Thank you very much in advance!

EDIT: Never mind, my impatient self tried to switch slot, which then ended up in the problematic slot. I then rebooted to fastboot, switched slot again and then flashed the full OTA. All is fine now!
[Google Pixel 8 Pro] mko000:
Thank you very much for your extensive reply! That's what I was hoping, but nothing happened after that.
[Google Pixel 8 Pro] badabing2003:
What do you mean by nothing happened?
[Google Pixel 8 Pro] mko000:
After the last message "Resetting an already applied update (if one exists) ..." nothing happened anymore. Nothing was logged and the OTA reboot notification remained.
[Google Pixel 8 Pro] badabing2003:
Nothing is usually logged after that resetting message.

As for notification, did you dismiss it and it came back?

Have you done what I have suggested?
[Google Pixel 8 Pro] mko000:
I did not dismiss it, but since nothing else was logged I thought it didn't work anyway.

How would that reset work anyhow? Hasn't the data already been written to the inactive slot at that time?

Your other suggestions regarding flashing the full OTA worked perfectly, thank you very much!
[Google Pixel 8 Pro] fma388:
Hi guys,

I know that a few months ago there was a problem with the latest versions of adb (after v33), is the problem still there or can I use a version newer than 33 with PixelFlasher?
[Google Pixel 8 Pro] Lughnasadh:
I've been using the latest, 35.0.1, with no problems. Haven't seen any issues reported pertaining to that version.
[Google Pixel 8 Pro] badabing2003:
Yep, use 35.0.1
[Google Pixel 8 Pro] badabing2003:
New Release:

July 4, 2024 v7.0.0.0 change log:

When sideloading OTA, automatically cancel a previous OTA (in progress or completed but not rebooted), which assures a better success rate. (Only applies to rooted devices that are in adb mode).

Added My Tools Menu, you can now add custom tools to PixelFlasher to easily launch your favorite tools / apps (example odin3).

Added Process Image in PIF Manager, PixelFlasher can now process a device image and extract PIF print from it with a single click. (Currently supported image types are, Pixel firmware, Pixel OTA, images with payload.bin, Samsung firmware).

When reading device details, report the sys.oem_unlock_supported prop value.

Miscellaneous minor improvements.
[Google Pixel 8 Pro] rester555:
Does PF flash Full OTAs on a locked and stock device?
[Google Pixel 8 Pro] badabing2003:
Yes it can, but will not apply a patched boot (just stock) if the bootloader is not unlocked, becuase that operation requires unlocked bootloader.

So just load OTA in PF, process, select the stock boot and Flash phone.
[Google Pixel 8 Pro] kingpeppermint:
Yes but if you're locked and stock you might as well just use the build in updater. Pixelflasher and similar tools help if you're unlocked and rooted to pre-root the update so you don't have to re-root every time.

But yes it can certainly do that.
[Google Pixel 8 Pro] rester555:
Thanks. I just enjoy using PF.
[Google Pixel 8 Pro] bsg411:
Here's a support.zip. I tried flashing OTA and patching with Apatch again with the July OTA....still not rooting properly. Not sure what I'm doing wrong.
[Google Pixel 8 Pro] badabing2003:
Did you launch Apatch app and entered the same key you used during patching?
[Google Pixel 8 Pro] bsg411:
Yes I did ...then it runs a script and then I reboot the phone.
[Google Pixel 8 Pro] HipKat:
Can I ask why Apatch instead of Magisk or KernelSU (Which I admittedly know nothing about)?
[Google Pixel 8 Pro] bsg411:
Once i lost my RCS messages using magisk, a few ppl said they had success retaining RCS capability as well as google wallet by using Apatch so I gave it a try but it doesnt seem to be patching correctly for me. I think it may have something to do with not uninstalling magisk fully or properly....who knows !!
[Google Pixel 8 Pro] r0ni3:
Good morning,

first of all congratulations on the wonderful tools!!!

This is my first time approaching a pixel (ex oneplus :P).

I managed to root it, but I'm finding 2 problems.

The first one I am not getting Magisk recognition from the app, in fact next to the connected device, I get the X (Probably not root, magisk tools not found).

Forward after patching the firmware I am trying to update, but I get this error:

INFO: Flashing was aborted.

This could be user initiated or a problem encountered during flashing.

I assure you, I tried searching and reading, but I couldn't find a solution (I'm still not too familiar with pixels).

Thank you if you would take a few minutes!

I am attaching the sanitized.

thankyou!
[Google Pixel 8 Pro] HipKat:
I'm sure @badabing2003 will have you sorted in no time.

Meanwhile, here's the quick step-by-step.

The pics in the main thread are dated and the program will look a little different.

What I do is run adb devices in a CMD Prompt, first, then open PixelFlasher.

Scan Device

Browse to the Update file - I do the OTA twice to install to both slots.

If this is your first root, choose Magisk at the top menu bar to install the app

Select Process.

Select Patch

Choose Root method - I only use Magisk Stable

Select save data - unless you want to wipe.

I selected Wipe Verity and Verification when I first rooted and keep them checked - that WILL wipe your data the first time as it was needed to flash custom Kernels but most of those it's not needed anymore, I just keep them checked.

Flash Device and let it go.

OTA updates take longer to flash so be patient until you're fully rebooted
[Google Pixel 8 Pro] r0ni3:
I think I did as you say, but I find the problems there!

I think the problem is with the other slot. i attach a picture of how it is configured and the problem.

keep data (as well as wipe data) does not let me select them, in this case the data will be kept right?

I wanted to try to do slot change, but I'm afraid of doing damage
[Google Pixel 8 Pro] HipKat:
One thing, switch to Advanced mode up where it says File Device Dev Tools, etc

But otherwise, it appears to look like you have selected the right options.

And yes the Data will be kept according to your settings
[Google Pixel 8 Pro] badabing2003:
Welcome

No you didn't

This is your clue that you didn't

I don't think you read enough.

Considering that this is your first time with PIxels, more reasons for you to read carefully, specially the OP and make sure you follow it in details.

Tell me, do you meet the pre-requisites?

Nope, your bootloader is locked.

View attachment 6120751
[Google Pixel 8 Pro] Slim2none4u:
OTA's don't wipe data thats why the option is not available.
[Google Pixel 8 Pro] r0ni3:
thank you very much.

Yes of course, I had already activated the expert mode, I was just trying again.

Another strange thing is that it doesn't detect root for me (even though it's up and running..).

You mention Magisk Tools not detected, what are you referring to though?
[Google Pixel 8 Pro] r0ni3:
hello!

is that the strange one, I assure you that the tel is rooted and bootloader unlocked.
[Google Pixel 8 Pro] badabing2003:
View attachment 6120760
[Google Pixel 8 Pro] r0ni3:
you are right. now recognize it correctly! forgive me!

now i will try to do the OTA update!
[Google Pixel 8 Pro] r0ni3:
ℹ️ 2024-07-06 15:20:34 INFO: Flashing was aborted.

This could be user initiated or a problem encountered during flashing.

nothing...I can't...
[Google Pixel 8 Pro] badabing2003:
Your device is currently on A15 Beta

Device Build: AP31.240517.031

And you're trying to flash A14 over it.

husky-ota-ap2a.240705.005

And even though PF has done the OTA cleanup on your device,

Cancelling a previous OTA update for good measure ...

It's still not accepting it.

It looks like you would need a wipe to be able to do that.
[Google Pixel 8 Pro] r0ni3:
After the tests I did today I am strangely finding the space occupied at 100%.

I have no photos or application or anything else that can justify the occupied space.

Before I do a wipe, do you recommend I do some more tests?
[Google Pixel 8 Pro] badabing2003:
considering thatr you said you were rooted.

You could do the follow

adb shell
su
cd /data
du -sk * | sort -nr

This should tell you where your space is consumed.
[Google Pixel 8 Pro] r0ni3:
I don't know if I can do any other tests before l

Restore totally..

Thank you for your time!
[Google Pixel 8 Pro] badabing2003:
As you can see, /data/local is taking all of your space.

You can cd to /data/local and then run the du command again,

It should tell you what's in there that is talking the space.
[Google Pixel 8 Pro] r0ni3:
You solved another problem for me. Can I buy you a beer? :)
[Google Pixel 8 Pro] badabing2003:
So what was taking the space?
[Google Pixel 8 Pro] r0ni3:
It was an incomplete copy of the userdata.img file.

Yesterday I was doing a dump of all the partitions, but I had interrupted ( I was accidentally dumping that file as well).

And it remained incomplete there.
[Google Pixel 8 Pro] srilk:
Hello, confused novice here.

I want to root my phone so i can use call recording and some automations from macrodroid, I understood that pixelflasher will do this easily but i see in the 'Prerequisites' that I need an "bootloader unlocked phone" hence i am confused, what exactly is it that i need? (most importantly i need to be able to hide root so my banking apps continue to work).

I use linux and don't hae easy access to win/mac OS so prefer tools that I can use on linux.

Any help/guidance is really appreciated.

Thanks
[Google Pixel 8 Pro] HipKat:
Start here to get your bootloader unlocked.

Keep in mind this will wipe your device, so back up anything you need

July 1, 2024 AP2A.240705.005 Global | .A1 Telus - Unlock bootloader / Root Pixel 8 Pro [Husky] Stable firmware / SafetyNet

Pixel 8 Pro [Husky] July 1, 2024: https://developers.google.com/android/images#husky https://developers.google.com/android/ota#husky https://flash.android.com/ https://support.google.com/pixelphone/community?hl=en...

xdaforums.com

For Linux, depending on what Distro you run, search Android Studio for ____ Linux
[Google Pixel 8 Pro] srilk:
i was so excited that pixelflasher doesn't need to wipe data.. i need to wipe it after all? after that pixelflasher and reinstall all my apps? i did not see in the guide how to hide root/Magisk
[Google Pixel 8 Pro] badabing2003:
Because that is not PF's job, that's a totally different topic and OT for this thread.

There is a lot you're asking for, and it looks like you're totally foreign to the basic concepts of what it takes to rooting, what are the parts, what part is needed for what ...

I strongly suggest you start reading the guide links referenced in OP and linked in the application's help menu.

You really ought to learn to walk before you try to run.
[Google Pixel 8 Pro] srilk:
last time i rooted was my samsung s2(or 3) many years ago, before i purchased my p8p i saw this and hought amazing, thanks for the clarifications, will have to make some time to read it up properly.
[Google Pixel 8 Pro] badabing2003:
Latest Release:

July 11, 2024 v7.1.0.0 change log:

Add license headers to source files.

Improved logging.

By request, PIF Manager now supports processing img files to extract PIF prints. (This is in addition to supporting zip files of factory / OTA images).

Check keybox.xml tool now provides more extensive report about the keybox.
[Google Pixel 8 Pro] badabing2003:
Update Release:

July 14, 2024 v7.1.1.1 change log:

Bugfix: #222 Customize My Tools menu is duplicatede when no tools are added.

July 14, 2024 v7.1.1.0 change log:

Windows versions of PixelFlasher are now signed (self-signed).

Hopefully this would cut down on false positive virus / trojan alerts, but it should also get rid of Unrecognized app warnings.

PixelFlasher.crt is the certificate, and ca_badabing2005.crt is the root CA.

Bugfix: #221 handle a corner case exception.
[Google Pixel 8 Pro] badabing2003:
Latest Release:

July 27, 2024 v7.2.0.0 change log:

In Magisk Manager, added the option to install Tricky Store module. (You now have 3 PIF related modules to choose from, Playintegrity Fix, Playintegrity fork, Tricky Store).

Updates to PIF Manager:

Option to convert from Json to prop (Env) format and vice versa (Tricky Store uses prop format) .

Compatible with Tricky Store (latest CI), you can now edit / update / test using Trick Store module.

Note: Tricky Store module does not yet support automatic updates, hence PixelFlasher is currently setup to point to the latest release in Github, this still uses Json file to spoof prints, use the latest CI.

If you have multiple PIF modules, for example if you use Trick Store and PiFork together, you can select which module's print you want to edit / update by selecting from the combo box. (Only enabled PIF modules are listed).

When loading prints from favorites, or console output, or using Smart Paste, PixelFlasher automatically converts the print to the format (json / prop) that the module requires.

Added option to push keybox.xml file to Tricky Store's predefine path.

Added a button to generate FrameworkPatcher compatible code for use in Android.java, just select the print, generate code and paste it in the proper section of Android.java to use your custom print with FrameworkPatcher.

Note: the generated code by default is commented out, as you can select multiple prints, just uncomment the ones you want to apply.

Added option to backup / restore /data/adb directory, please be aware that this only backs up / restores /data/adb/*, any modules that installs files outside this path will not be backed up, as it's impossible to know what all modules do.

New features in My Tools Manger:

Different methods to launch application.

Option to enable / disable launching detached process.

Option to insert separator.

Note: Start with the defaults and experiment if default behavior is unacceptable.

Miscellaneous fixes and improvements.
[Google Pixel 8 Pro] badabing2003:
Update Release:

July 28, 2024 v7.2.0.1 change log:

Set a default PIF format to json to allow displaying the print when Processing Image in PIF Manager.

When PIF Manager is used with an unrooted device or one without granting su permissions to shell, display a message to inform the user about the reduced PIF Manager functionality.
[Google Pixel 8 Pro] badabing2003:
New Release:

Oct 18, 2023 v5.8.2.0 release

Added `Wipe` option (only available in custom flashing), this will wipe userdata after flashing, required for first time vbmeta verification disabling.

Added validation checks to make sure A and B slot vbmeta verity / verification states match.

Added a warning when toggling `Disable Verification` to inform about the the potential wipe implications.

Display both slots verity / verification states when displaying device details.

Extract vbmeta.img if found to easily select it for patching.

Improved paste button which now dynamically selects what to paste based on the custom flash option selection.
[Google Pixel 8 Pro] HipKat:
Just under 12 minutes to open the box, OEM unlock, Bootloader Unlock, Flash A14 w/ Magisk and rooted with PF.

It couldn't be any easier
[Google Pixel 8 Pro] badabing2003:
Thanks,

The spoiler says Pixel 7 Pro, but you're posting in Pixel 8 Pro thread.

I'm assuming the spoiler is outdated.

Curious to know what if you flashed full OTA or factory?

And if full OTA did you run it twice?

If factory, did you flash to both slots?

Trying to gauge the time it took end to end.
[Google Pixel 8 Pro] HipKat:
I haven't updated my signature yet and I only flashed to the inactive slot. I dunno why I'm nervous about flashing to both slots.

I flashed the Factory from the Developers page, so just once and the flash time showed 273 seconds
[Google Pixel 8 Pro] badabing2003:
Don't flash to both slots factory, flash OTA, safer than factory inactive.

And if you flash OTA twice in a row, you end up with two slots bootable, you can even choose one to be rooted and the other not rooted.

I know it's hard to break old habits, but OTA is much safer.
[Google Pixel 8 Pro] HipKat:
Yeah, old habit. Next month, I'll start doing that
[Google Pixel 8 Pro] b1nly:
If I flash the latest factory or OTA linked, I still get a notification to update on the device (which the phone can't unstall). Am I crazy to expect a tool like this could update me to latest or at least point the user in how they could?
[Google Pixel 8 Pro] badabing2003:
Am I too crazy to expect that users of tools like this when seeking for help, would provide proper details, perhaps read the OP, perhaps supply a support file?
[Google Pixel 8 Pro] b1nly:
1. This could be device related if it is expected but not occuring.

2. I am not seeking help.

3. Again, unsure if this is expected - it it is not expected, and should update to latest (e.g. the OTA image is latest(, then I would supply a support file if I was seeking help.

I probably worded this incorrectly:

* AM I SUPPOSED TO STILL HAVE AN UPDATE SHOWING WHEN FLASHING LATEST OTA ON THE PIXEL 8 PRO

* IF YES, it would be a good idea to add something about users installing the update without the tool. This has been common in the past with other methods.

* IF NO, I am notifying you that I had the issue, and would've followed up with whatever you needed.

I'll get out of this thread. Cheers.
[Google Pixel 8 Pro] HipKat:
I just did mine today and am not having that issue. Silly question but you're SURE you got 14.0.0 (UD1A.230803.041, Oct 2023)?
[Google Pixel 8 Pro] simplepinoi177:
He seems to be very well spoken native English speaker, but just in case he is not (which makes him all the more impressive if true), there have been site issues where the latest update image does not show up unless you view the US site....

so one could easily believe they are on the latest if they aren't looking particularly....
[Google Pixel 8 Pro] HipKat:
FWIW, just for the heck of it, I checked Play Update and there was one available
[Google Pixel 8 Pro] Gilbot:
I just got my Pixel 8 Pro and I want to install an AOSP GSI on it. I find the stock Pixel image slow. I am comparing this to running an AOSP GSI on a Galaxy Note 20 Ultra which is blazing fast and I'm wondering if it's just from the stock rom being bloaty and unoptimized.

I have had an issue in the past with a Pixel 6 Pro like a previous poster had where the Pixel would not boot, showed a black screen and would show up in Windows as "Pixel Rom Recovery". I am trying to avoid ****ing something up and having that happen cause only an RMA will fix that.

It's been a while since I used a Pixel Device, so excuse my inexperience. On my Note 20 Ultra I have to flash a vbmeta and disable verity.

Can I flash an AOSP GSI from Pixel Flasher? I've already bootloader unlocked the device and flashed magisk to it with pixel flasher.

Is the process to load and flash the GSI image under Flash Mode>Custom Flash>system>"gsi".img ?

If that is the right option, do I need to check off Disable Verification and/or Disable Verify? (I'm assuming yes..)

If that is all correct, does Pixel Flasher erase system before flashing as well, and is it recommended to flash to both slots?

Appreciate the help.
[Google Pixel 8 Pro] HipKat:
I wouldn't flash anything unless it's specifically made for the Pixel 8 Pro
[Google Pixel 8 Pro] Lughnasadh:
One thing that has changed is that it uses fastbootd again (at least it did when I used it on my Pixel 7 Pro via flash-all). Could be a reason why the wipe function now works. Wondering if this update will fix the problems MacOS users were facing on 33.0.3.
[Google Pixel 8 Pro] badabing2003:
Yes this one also has used fastbootd

extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for
[Google Pixel 8 Pro] badabing2003:
@Gilbot

Sorry I don't have any experience with GSI images, so can't really advise you one way or another.
[Google Pixel 8 Pro] 93ae8074:
No issues here on a M1 Pro running latest platform-tools. Just flashed a Pixel 8 Pro and two Pixel 7 Pro without any issues at all.
[Google Pixel 8 Pro] simplepinoi177:
I don't know if we're talking about "Google Play System Update" as "Play Update" or the Monthly/A14 Firmware Image Update, but if we are talking about the "Play System Update", a curious weird peculiar thing happened to me...

I finally felt safe/secure enough to finally update to A14 -- so I started with my wife's P7P last night. After everything, I found that "Play System Update" needed 2 updates; one was KBs big and one was like 2MB or something...we were both coming from August monthly update. So I knew what to expect when updating my own P7P to A14 tonight.

After I did my update, I found that there was no update for me -- which normally isn't much of anything as I know Google likes to do much of their updates as staged rollouts; but I knew for sure there were 2 updates available as my wife's did them -- so I didn't think anything to it. I've been having issues so I decided to flash the Full Factory image after updating -- in the hopes of giving all the chances of correcting any of the bugs/glitches -- and after I did that, I went to see if it would work again and lo and behold it did!

I wonder why Google didn't like Full OTA's sideloading but was good with Full Factory flashing....

As I said....weird/peculiar.....
[Google Pixel 8 Pro] HipKat:
Google Play System Update. I should have specified better
[Google Pixel 8 Pro] b0uNz:
The fastest and easiest way to update every month and keep root. Many thanks for this
[Google Pixel 8 Pro] bigAL99:
HI,

first time owning a pixel so all new but been flashing for a while. I'm just gwtting a bit turned around with a couple of things.

I have unlocked and rooted my phone using pixel flasher after I had done the initial ota update with no issue.

But then I have seen information regarding disable verity and disable verification. Am i correct in understanding that i can leave then disabled if doing ota updates and its not an issue?

Also i am unsure do I need to flash to both Partitions? I think I am reading that a new phone would only have 1 partition flashed and the other is blank? does the fact that I did an OTA update through the system mean that it would have flashed to the other partition so I dont need to now?

bellow is the output on Pixel flasher before i press ok does that read correct?

View attachment 6029987