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

Dec 21, 2023 v6.4.0.0 release

A new resizable Pif Manager dialog decoupled from Magisk dialog.

Pif Manager new features:

Two pane window, top pane always showing the active loaded pif.json (if one is present, it is automatically loaded), bottom pane showing the output of processing props or Play Integrity testing.

Easy to use paste button to paste the output of the processed props into active pif.

Real time json validation (input is handled as json5 to allow json5 formatting / commenting, however the saving to device is done in regular json to keep it backward compatible.

Pushing to device is disabled if the contents are not a valid json.

If you make changes to local active pif, an indicator will reflect that changes need to be pushed.

Reload pif.json which reloads from device and discards what is in active pif window.

Few other features and improvements in in the works.

#129 Resizable and scrollable settings dialog for smaller display resolution devices.

Improved Magisk manager.

Pif install modules allows you to select @osm0sis or @chiteroman module.

New forward looking feature to dump selected device's entire props as json.

Completely reworked device property handling, to make it future proof and extensible.

Improved device detection between reboots of various modes.

Dark splash screen, thanks to @T-Ryder for the artwork.

#131 Disable Magisk denylist for Magisk delta, which is not compatible with official Magisk.

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

Dec 23, 2023 v6.4.1.0 release

Added Get xiaomi.eu pif, use it only if you don't manage to find working print, strongly recommended not to rely on it.

Support for caching of xiaomi.eu pif to avoid unnecessary downloads and processing.

All done in Python, hence no dependency on apktool or Java.

Support for @osm0sis native props.

Minor UI improvements.
[Google Pixel 8 Pro] badabing2003:
Update Release:

Dec 23, 2023 v6.4.2.0

New feature: Label and save your working pifs into your favorites and load them quickly from a combo box.

Added Get TheFreeman193 Random Pif, credit to @TheFreeman193 for the print supplies and the original logic of randomization based on device architecture.

Other minor improvements.
[Google Pixel 8 Pro] badabing2003:
New Release:

Dec 26, 2023 v6.5.0.0

Retry downloading with disabled SSL certificate verification if SSL error is encountered during TheFreeman193 pifs download. Print an alert to warn the user.

Added testing with YASNAC

Display a warning toast during Play Integrity test, when the Active Pif window content is not in sync with the device's pif.json.

Added Paste Down button to transfer the contents of Active Pif to Output Console (useful for reprocessing a pif.json.

Added Reprocess button to reprocess and produce pif.json compatible with the installed module version. Useful when different versions of modules require / depend on different fields / props. (Note: this is compatible with @osm0sis modules, @chiteroman modules change often and it's hard to keep up, I've done my best to keep compatibility with some of those versions).

Fill in missing build fields from fingerprint or vice versa.

Added an option to add missing fields with values from running phone (not the donor print)

Added an option to point to a directory full of json files and import them to favorites.

Added an option to disable UIAutomator (useful for devices that have a buggy UIAutomator). coords.json file can be manually created to run the automated tests. See #137

Did some code refactoring.
[Google Pixel 8 Pro] WhiteDain1:
Fantastic this is just what I was looking for as I've just got my pixel 8 pro now (UK). So I will be trying this step by step
[Google Pixel 8 Pro] roirraW "edor" ehT:
@badabing2003, bringing this over from my thread (

this is solved

):

I used your Magisk apk, installed on my P8P, to inject Magisk into the 100% stock December uq1a.231205.015 init_boot.img. I then rebooted to bootloader and flashed this newly Magisk'd init_boot.img but I was still getting the SystemUI FCs.

I then did the patching using your Magisk through PixelFlasher with the same result - still getting SystemUI FCs constantly after unlocking.

I then use PixelFlasher to wipe the data for the Dark Tricks v3.0 app, and uninstall it, and rebooted, and all is now fine. Thanks again!
[Google Pixel 8 Pro] badabing2003:
Great, (y)
[Google Pixel 8 Pro] badabing2003:
Update Release:

Dec 29, 2023 v6.5.1.1

Support for PlayIntegrityFix 15.1 added keys.

Improved auto-fill (from device) missing fields.

Dec 29, 2023 v6.5.1.0

Added Bulk Reprocess json file(s) (detects module flavor / version and outputs compatible format, similar to previously included Reprocess Pif feature which only applied to the Active Pif).

Get donor device's Pif print, now outputs @osm0sis v5 fork format print (needless to say, donor device must be connected).

Adding to Pif favorites now auto-fills the label with device brand and device model.

Other minor improvements.
[Google Pixel 8 Pro] HipKat:
The link to 6.5.1.1. is broken

Should be https://github.com/badabing2005/PixelFlasher/releases/tag/v6.5.1.1
[Google Pixel 8 Pro] badabing2003:
Shoot, even link to 6.5.1.0 was wrong
[Google Pixel 8 Pro] HipKat:
It happens!
[Google Pixel 8 Pro] badabing2003:
New Release:

Dec 30, 2023 change log:

Pif Manager option to Force First API to 25 (some prints like Xiaomi.eu are missing the value and that would cause newer devices to fail Device Integrity).

Pif Manager options are now saved so that each time you open Pif Manager, the last settings are loaded.

Bug Fix: Enable checkboxes in Magisk Modules.

In Magisk Modules, add VersionCode column.

Better positioning of Pif Manager with respect to the parent window.
[Google Pixel 8 Pro] badabing2003:
Latest Release:

Dec 30, 2023 v6.5.3.0 change log:

Added Smart Paste Up to simplify getting operational for beginners.

It automatically sets the First API to 25 if it is not set, otherwise keeps the value.

It automatically reprocesses the output window content, to meet module / version requirements.

It automatically pastes the processed data into Active Pif window

If Auto Update pif.json is checked.

Updates the correct pif.json on the device.

Kills the unstable GMS.

Runs Play Integrity Check if Auto Check Play Integrity is selected.

Updated screenshot for the guide.

Pif guide in OP is updated as well.
[Google Pixel 8 Pro] Kingcool88:
Windows Defender now flag the app as a virus:'

Trojan:Win32/Sabsik.FL.A!ml threat description - Microsoft Security Intelligence
[Google Pixel 8 Pro] Homeboy76:
OP

Troubleshooting:

... • If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 8 Pro] HipKat:
It's been doing that, if not Defender then Edge's built-in security. I just click on Keep and let it d/l.

I PROMISE, @badabing2003 is not handing out anything with a virus in it.

You can always set up a VM to use it in if you're concerned
[Google Pixel 8 Pro] Kingcool88:
Windows Defender hasnt flagged it before for me, so it was just a heads up that there might be some people that might have issues finding the app after download if they are not aware of it, as WD flags it as serious so the app will be deleted directly.

And no I'm not concerned about it, I'm using it as before. Its was just the new behavior from WD I was reporting :)
[Google Pixel 8 Pro] Samuel Holland:
What a fine job on this tool, that has really came along. Thank you very much.
[Google Pixel 8 Pro] HipKat:
I just realized, I have every version in a folder going back to when I first got my P7P
[Google Pixel 8 Pro] supermansaga:
I used PF 6.5.3.1 to relock bootloader. Upon relocking, the device enters this "no valid operating system could be found. The device will not boot. Visit this link on another device: g.co/ABH. ID: e5362ddf. Code: 3." It asks me to "press power button to power off." But it doesn't work.

I then tried to hold down volume Down key + power key for 30 seconds, but nothing happens either. I am freaking out. Thanks.
[Google Pixel 8 Pro] badabing2003:
Sorry to be the bearer of bad news, you should be freaking out.

It's been said million times, you have to take strict measures prior to locking your bootloader.

What measures did you take?
[Google Pixel 8 Pro] supermansaga:
Nothing. I just went for the menu and click lock bootloader. The device then presents me with lock or do not lock. I chose lock. In the past I used Android Flash Tool to lock and was spoiled.
[Google Pixel 8 Pro] badabing2003:
It's not about what tool you use to lock the bootloader. It's about the state of your device prior to locking.
[Google Pixel 8 Pro] supermansaga:
I was in a rooted Jan 2024 factory image state. I didn't unroot first...So what can I do now?
[Google Pixel 8 Pro] badabing2003:
How was it rooted?

Factory or OTA?

What was on the other slot?
[Google Pixel 8 Pro] supermansaga:
Factory via PF 6.5.3.1. The other slot appears to be the 12052023 one, when I checked the box that says, "show all boot/init boot." But then I think i clicked on that line and pressed "delete," because it's pointing to a package path that no longer exists on my windows....Later on, PF does show both slots are unbootable.

I then tried to PF Unlock the bootloader again and Voila!!! I can put the factory image back in now. So stupid of me. Phone is back to normal with at least one working bootable slot. How should I responsibly relock it this time? I only meant to use network signal guru to provide 5G to my sim card in an unsupported country.
[Google Pixel 8 Pro] badabing2003:
If you plan to lock, then you'd have to be stock.

If that is your intention, then flash OTA (choose the stock init_boot) twice in a row to make both slots identical and bootable.

Factory does not do that.

Then and only then lock your bootloader.

Make sure you keep oem unlock enabled in developer options in case you need to unlock again.
[Google Pixel 8 Pro] supermansaga:
When you say "factory does not do that," are you saying the following is then not right in terms of making both slots identical? I thought I flashed the OTA twice, once by selecting the UQ1A and another by selecting OTA-UQ1A, however, upon completion, they still look exactly the same as before in the screenshot. I then went ahead to lock the bootloader using PF and it was a success, though for a moment, I was very scared because I saw the wiping warning on re-locking. Finally, it went back to fastboot mode and I pressed "START" to see the system rebooting again. What else can I perform to confirm which slot has which image?

View attachment 6051626
[Google Pixel 8 Pro] badabing2003:
Earlier on you said you flashed factory image.

But now you're saying you flashed OTA?

Your screenshot does not tell me much, neither

So not sure what you're expecting to see.

That part of the screenshot is just listing boot images extracted.
[Google Pixel 8 Pro] supermansaga:
the OTA flash is a subsequent action that I performed. Right now after re-locking with stock image with probably one slot featuring factory and another slot featuring OTA, my biggest dumb question is if PF could help provide insight on which slot has factory vs OTA. Trying to de-memorize/refer to those command lines.

I now do see PF shows "Current Active Slot " with a purple B. And if I click the "switch slot" button, it will go to "Current Active Slot [A]" with a purple A. And the "tick mark vs cross mark" next to "ADB connected devices" would indicate if it's [probably] rooted or not rooted. But it will be great to understand factory vs OTA on which slot. Or it doesn't matter? Thanks.
[Google Pixel 8 Pro] V0latyle:
If you flash the OTA twice, both slots will have whatever the OTA version is. The only difference between "factory" and "OTA" is how the update is installed. Factory image installs to the currently active slot (or both slots if commanded)

OTA on the other hand installs to the currently inactive slot, then marks that slot as active; when the device reboots, it starts fom the newly updated slot. So if you install the OTA again, it will now install to the slot you were originally on as that slot is now inactive.

How about we make this really simple.

Close Pixel Flasher and go to flash.android.com

Authorize ADB access, you may have to add the device, and you'll have to authorize on the phone too.

Select latest public build. Click pencil icon and select Wipe Device, Lock Bootloader, and under Advanced Options, Force Flash all Partitions

Click Install Build

This will return your phone to 100% bone stock on both slots with a locked bootloader.
[Google Pixel 8 Pro] HipKat:
TBH, I would flash the factory image, without patching with Magisk, of course, and another thing, I lock/unlock in Terminal with adb.

If you don't know:

adb reboot bootloader

fastboot devices

fastboot flashing lock

(or unlock to unlock Bootloader)

As awesome as PF is, I just feel this is better, IMO, for me
[Google Pixel 8 Pro] supermansaga:
I actually have been using Flash.Android.com until yesterday and today, when the website now says "Flash Failed. Failed to Fetch." This is why I highly appreciate PF's offline approach. Maybe the failure was caused by the VPN I have been using. They used to work in the past, but not this round.
[Google Pixel 8 Pro] badabing2003:
If you are able to boot to both slots, and both show not rooted, then you're 100% stock.

It does not make a difference whether it was flashed with factory or OTA.

If OTA was your last flashing, then the factory slot would not have been touched and effectively remain bootable.

If you do the inverse order, then only one slot would be bootable.

But I see that you did the correct order, so you should be fine.

Except that you won't have both slots bootable.

I beg to differ, this is not good advise, unless you meant it but not indicated, flashing factory only takes care of one slot unless you modify the command and flash to both slots, and that involves some knowledge to know exactly which partitions can be flashing simultaneously and which need to be done separately (depending on the Phone model)

Furthermore the same issue that I mentioned above for @V0latyle still applies to your method.

Why take a chance, flash stock OTA twice, and then lock.

The safest way, and whether you do it with PF or not, that is up to you.
[Google Pixel 8 Pro] V0latyle:
True, it's really hard to screw up an OTA update.
[Google Pixel 8 Pro] vegetaleb:
Hello

Pixelflasher kees telling me that I have an android platform tool while I updated the sdk platform tools to 34.0.5

What am I doing wrong?
[Google Pixel 8 Pro] badabing2003:
How am I supposed to know?

There is a reason why PixelFlasher has generate support file option.
[Google Pixel 8 Pro] vegetaleb:
I uninstalled Android studio now, rebooted, but pixelflasher is still saying I have an old platform tool

As Android studio is not there anymore, where is pixelflasher checking for the platform tool?
[Google Pixel 8 Pro] badabing2003:
Seriously, support file will help me help you.
[Google Pixel 8 Pro] vegetaleb:
My bad sorry

This is the file you need?
[Google Pixel 8 Pro] badabing2003:
In C:\Windows you have Android Platform Tools version 30.0.1-6435776

2024-01-06 17:43:32 Selected Platform Tools Path:
C:\Windows.

2024-01-06 17:43:32 ERROR: Detected old or problematic Android Platform Tools version 30.0.1-6435776
Bad Android platform tools is not accepted. For your protection, disabling device selection.
Please update Android SDK.

2024-01-06 17:43:38 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: 30.0.1-6435776
Adb SHA256: 5c5caf34ecf3e2ca1af55fe26d0ae7697eb2f30808250c11ed16e63dd86d1a5c
Fastboot SHA256: 51403c072cf3ea68e643c39f9ab542db2cba43e29f62894b0e5bbeae6cb5eb15
[Google Pixel 8 Pro] vegetaleb:
Thanks mate!

Replaced the files with the newest ones and it's working :)

Thanks mate
[Google Pixel 8 Pro] badabing2003:
You shouldn't be putting them in c:\windows

If your only use is with PixelFlasher, then place them wherever you please and point PixelFlasher to it, and it should pick it up, this way you can have multiple versions on disk, and be selective which to use (as long as in your path environment you don't have others)

On the other hand if you drop to command line a lot (like I do) and would like to have adb / fastboot accessible without having to specify the path, place them somewhere other than c:\Windows

and add the path to user environment PATH.

Ideally you should not place anything non Microsoft Windows files in c:\Windows.
[Google Pixel 8 Pro] vegetaleb:
@badabing2003

Finally unlocked my P8P and followed the tutorial in the main thread, I chose a factory image but when I flashed it the ''flash to inactive slot'' was not selected, does it mean only one slot was rooted?

If yes should I do it again but this time with the inactive slot chosen?
[Google Pixel 8 Pro] badabing2003:
Yes,

Flash OTA, this way both slots are bootable.

Since you already flashed factory, you only need to flash OTA once.
[Google Pixel 8 Pro] vegetaleb:
Thanks

So I picked the full ota file in pixelflasher, then Process, then flashed twice in a row

After that I installed Magisk app also with pixelflasher, but Magisk is saying it's not installed

Here's my log
[Google Pixel 8 Pro] badabing2003:
This is not a support file, and has no information helps me troubleshoot the issue.

Click on Support button and provide the zip it creates please.
[Google Pixel 8 Pro] vegetaleb:
Here you go
[Google Pixel 8 Pro] badabing2003:
You jumped over step 7 and step 8 from the guide.

As @roirraW "edor" ehT correctly guess, you flashed stock init_boot.img hence why you're not rooted.

Select the stock boot from the list

Hit the patch button, which should create a patch

Select it and Flash Boot (not Flash Pixel Phone)

This should make the current slot rooted.

The alternate slot remain stock.

Let me know if you want to make both slots rooted.
[Google Pixel 8 Pro] vegetaleb:
Thanks

Yes I guess both slots is better no? I will have to repeat what I did before + Flashing the missed patch?
[Google Pixel 8 Pro] badabing2003:
Not necessarily, depending on the person.

If you have an app that detects root and only works when note rooted. then you can switch slots and run the app.

Keep in mind that you can switch from rooted to stock on device or using PixelFlasher, however to switch from stock to rooted, you need a PC as it needs to be done in with fastboot, PixelFlasher can do that, but you can't do it from the phone.
[Google Pixel 8 Pro] vegetaleb:
There are no magisk module to hide root with banking apps?
[Google Pixel 8 Pro] badabing2003:
Depending on the app, there are different techniques and tools, but that's a totally different discussion and there are dedicated threads of that, it is out of scope for PixelFlasher.
[Google Pixel 8 Pro] badabing2003:
New Release:

Jan 07, 2024 v6.6.0.0 change log:

New Feature: Download any Google device firmware or full OTA directly in PixelFlasher.

Automatic detection and notification if an update is available for the selected device.

New feature: Cancel / reset OTA update pushed by Google (need to be used prior to a reboot). Binary graciously provided by @capntrips.

Removed outdated links from help menu.

kdrag0n's safetynet-fix

Displax's safetynet-fix

Added new links to the help menu

osm0sis's PlayIntegrityFork

chiteroman's PlayIntegrityFix

TheFreeman193's Play Integrity Fix Props Collection

Full OTA Images for Pixel Phones / Tablets

Factory Images for Pixel Phones / Tablets

Full OTA Images for Pixel Watches

Factory Images for Pixel Watches

Full OTA Images for Pixel Beta 14

Factory Images for Pixel Beta 14

Enable Magisk Kitsune patch creation using Magisk core component (previously disabled due to incompatibility and patches were only created using the manager).

Miscellaneous improvements, bug fixes and code refactoring
[Google Pixel 8 Pro] mko000:
@badabing2003 You're unbelievable...you've really made PixelFlasher into an "eierlegende Wollmilchsau". Which is German and translates to "egg-laying, milk-bearing woolly sow" 😂
[Google Pixel 8 Pro] HipKat:
Go back and just install Magisk with PF without flashing anything.

I've had that happen before

Edit: I should have read on

Correct.

My path and the default path is C:\Android\platform-tools\
[Google Pixel 8 Pro] HipKat:
You are a crazy person.

And a hero to this community.

+1 my dude!
[Google Pixel 8 Pro] badabing2003:
Bugfix Release:

Jan08, 2024 v6.6.0.1 change log:

Bug Fix: Toolbar menus were interfering with the download menus and triggering a download when toolbar was modified.
[Google Pixel 8 Pro] knopie:
The latest 2 versions keeps hanging during startup, is is active but I don't see anything.

I'am using a MacBook Air with osx 14.3 beta.

When I stop PIxelflasher I see this screen

Jos

View attachment 6053356
[Google Pixel 8 Pro] badabing2003:
Please create a support file with version 6.5.3.1 and provide that.

Thanks
[Google Pixel 8 Pro] knopie:
The support file.
[Google Pixel 8 Pro] badabing2003:
I don't have a MAC, I do my testing on MacOS docker image, and and it's passing for me.

View attachment 6053519

The logs don't show much, when it is crashing for you there are no logs :(

Any chance you can build it from source and see if it works for you?
[Google Pixel 8 Pro] Ultimoose:
This is an awesome addition sir.
[Google Pixel 8 Pro] knopie:
I installed Python , it is version 3.11.7 not 3.9.12. After following your instructions at Github I compiled with build.sh. The DMG file under dist is starting and I moved Pixelflasher to Applications. Pixelflasher is not starting.
[Google Pixel 8 Pro] badabing2003:
Thanks,

1- What do you get in the terminal when you run it like this

/Applications/PixelFlasher.app/Contents/MacOS/PixelFlasher --console

2- rename this file /Library/Application Support/PixelFlasher/PixelFlasher.json to PixelFlasher.json.bak, and do teh same with PixelFlasher4.db and see if it starts

Thanks
[Google Pixel 8 Pro] knopie:
1. version I compiled

View attachment 6053747

2. with the latest version you compiled

View attachment 6053750

Some issue with SSL I think

Thanks for your fast support.
[Google Pixel 8 Pro] knopie:
My own compile succeeded, adding the dependencies from requirements.txt with the latest version. There was an error with protobuf, I downgraded to 3.20.1. Pixelflasher starting, I don't see the window with the current version which I have to close. I seer the main screen. I connect my phone, after scan it sees the phone.
[Google Pixel 8 Pro] badabing2003:
1- Your own compile error above is missing darkdetect, I don't understand how is that possible unless you missed the venv activation and importing the modules.

requirements.txt has the darkdetect.

As for protobuf, it should have been >=3.19.3, <=3.20.1 if the import was done properly, I suspect there was an issue with the import, either you forgot or you got an error.

What do you get when you type pip freeze

If you say PixelFlasher is starting when modules are as the requirements.txt, then I'm confused why the compiled binary is having an issue.

You can see the logs here when it was built

View attachment 6053851

2- I'll have a version soon that ignores ssl errors.
[Google Pixel 8 Pro] knopie:
The message about darkdetect was before I did the import, after the import and compiling it is working .
[Google Pixel 8 Pro] badabing2003:
New Release:

Jan 10, 2024 v6.6.1.0 change log:

Changed PixelFlasher icons to dark icon (artwork provided by @T-Ryder).

Potential fix for #144, when getting firmware / ota download links, fallback to ignore ssl errors, if ssl errors are encountered.

Add ssl verify ignore fallback to any download (also display warning).

Add button in Pif Manager to convert key=value format (similar to env or older .prop format) to json format.

Device Info now gets props as root if the device is rooted.

Miscellaneous minor fixes and improvements.