yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] badabing2003:
Good to see you back @t-ryder

I'm heading out now, upon my return or tomorrow (in case I return late) I'll read this in detail, but in the meantime have you checked the built in option SIDELOAD

View attachment 5770343

This is done to flash OTA

PF will reboot to sideload issuing this command

adb reboot sideload
[Google Pixel 7] t-ryder:
Yes, nice to see you keeping it up. Got me a Pixel 7 after the OnePlus 9 was a letdown and the Realme GT2 pro did not make me happy totally.

So the OTA flashing for non bootloader unlocked devices is already there? I did not check PF for some time now. My bad if I did not get it.
[Google Pixel 7] badabing2003:
Congrats for your new phone.

Yes OTA flashing is there, and no worries of not seeing it, the UI (not my best skill) is not the best (and the chosen platform doesn't help), some of the features are obscured and can only be discovered by clicking around.
[Google Pixel 7] BetaPix:
Thank you OP for your hard work and for making our life on Pixel phones much easier :)

I rooted my Pixel 7 the day after I bought it, and I can't remember if I disabled dm-verity and avb during the unlocking process (I think I ticked those flags but I'm not 100% sure). How can I check my dm-verity and avb's actual status? If they are disabled, can I re-enable them at the next update through PixelFlasher without being forced to wipe data? Thank you in advance for your answer.
[Google Pixel 7] t-ryder:
So one has to enable advanced options, use custom flash setting to flash the full OTA file in SIDELOAD mode (dropdown menu) ... and there will be no data wipe (since I can't choose KEEP DATA)?
[Google Pixel 7] badabing2003:
Correct,

You probably want to set the flag `Flash to Inactive Slot` to mimic a true OTA behavior.
[Google Pixel 7] elong7681:
I have a problem with disabling verity and verification. I've tried four times and every time it still shows me that verity is enforcing and it says verification error when I use the dump device info
[Google Pixel 7] badabing2003:
Get support.zip and let me take a look to see if anything is going wrong.
[Google Pixel 7] elong7681:
Ok, how do I get that and I have already shut down my computer So I'm assuming that will affect me from getting it but I can retry it
[Google Pixel 7] badabing2003:
You launch PF and in help menu you choose Generate sanitized support.zip

No need to do anything else
[Google Pixel 7] elong7681:
If I wanted to edit the flash-all.bat file in the factory image so that I could do it manually then what would it look like ex: fastboot -w fastboot --disable-verity --disable-verification update image-panther-td1a.221105.001.zip
[Google Pixel 7] badabing2003:
That would do it, but will also wipe your data.

If you don't want to wipe data remove -w

I took a look at your logs, I don't see errors that would cause it not to work.

As you can see in the logs, this is what PF ran.

The commands match

chcp 437
@ECHO OFF
:: This is a generated file by PixelFlasher v4.4.0.0

PATH=%PATH%;"%SYSTEMROOT%\System32"
"C:\platform-tools\fastboot.exe" -s REDACTED --slot all --disable-verity --disable-verification flash bootloader bootloader-panther-cloudripper-1.0-9074510.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --slot all --disable-verity --disable-verification flash radio radio-panther-g5300g-220908-220908-b-9040061.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --disable-verity --disable-verification --skip-reboot -w update image-panther-td1a.221105.001.zip
echo Switching active slot to the other ...
"C:\platform-tools\fastboot.exe" -s REDACTED --set-active=other
echo rebooting to bootloader ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --disable-verity --disable-verification --skip-reboot -w update image-panther-td1a.221105.001.zip
echo rebooting to bootloader ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\platform-tools\fastboot.exe" -s REDACTED --slot all --disable-verity --disable-verification flash init_boot pf_boot.img
echo rebooting to system ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot

REDACTED is your device ID.

How are you check that verity is disabled?

What are you expecting and what are you getting instead?
[Google Pixel 7] elong7681:
When I use your PF to dump device info it says verity is enforcing and I want to install a custom kernel and we have to do a data wipe in order to disable verity and verification correct?
[Google Pixel 7] badabing2003:
I see that you are using Safetynet module, which inherently changes that flag and few others so that is passes Safteynet.
[Google Pixel 7] elong7681:
So if I remove the safetynet fix and reboot will it go back to verity not enforcing
[Google Pixel 7] badabing2003:
I don't know, possibly yes, as SafteyNet alters that.

These are questions best asked in the Kernel threads, I don't personally disable verity or verification as I don't use custom kernels, I wouldn't be the best source of the info.

As far as PF is concerned, it adds the proper flags to the fastboot command if those options are selected, and we can see that in your logs.

I'm still interested to hear back and learn.
[Google Pixel 7] badabing2003:
From the guide in OP and Github.

Basic Mode | Step 3 | Bullet point 1

View attachment 6035063
[Google Pixel 7] Yahoo1:
Sorry for my ignorance, @badabing2003. It works perfectly now.
[Google Pixel 7] badabing2003:
New Release:

Nov 22, 2023 v6.2.0.0 release

Added Magisk module update detection and updating.

Add button to install Play Integrity Fix module by @chiteroman

Added gui to pull / edit and push pif.prop file. (If there is interest I will add the ability to pull pif.prop values from system, using @osm0sis script)

Added Systemless Hosts module install button.

Maintain a list of unlocked bootloaders in memory to skip over extra unlock checks.

#121 Removed Delta Magisk from Magisk Install options (update json no longer published).

Removed the functionality that automatically finds and adds platform tools from the system, it is now required to select the desired platform tools.

Bug fixes and improvements.
[Google Pixel 7] badabing2003:
New Release:

Nov 26, 2023 v6.2.1.0 release

New feature: Added Bulk apk install capability. Point to a directory where the apk files are and all of those would be installed.

New feature: Extract current device's Pif print.

New feature: Push a file to /data/local/tmp

New feature: Push a file to /sdcard/Download

New feature: Kill Google GMS (for testing different pif.json files without needing a reboot)

Updated pip.prop editing to pif.json (with syntax coloring).

Option to create pif.json if one is missing.

Miscellaneous improvements.
[Google Pixel 7] Magnivore:
Good day Android-holics!

Over the last week my P7 A14(v10) has been sending me notifications about the need to update my phone. It will give me a silent notification in the quick panel that says it'll install the update when I restart. There's been fairly intrusive pop-ups that say I'm X days overdue for updating and to [press here] to install it. I have automatic updates turned off and the 'install update on restart' option off.

My question is, what the h*ck? Why in the world is my phone doing this despite being rooted and having auto updates off?
[Google Pixel 7] lordoftheflows:
Hi, I found some interesting behaviour which is related to the USB cable I'm using, maybe it is a bit flaky (USB3 port). Trying a different cable & port (USB2), everything works fine (no need to support me). I just thought I'd share this to maybe detect such a situation and make PF more reliable for everyone.

I noticed that with the working cable, the ADB connected devices will show "panther", and "TQ3A.... (the currently installed build), and shows active slot B. With the bad cable/port, it will only show the adb device ID 29...LL1, nothing else, and not indicate the slot (just "rooted").

Trying to patch the Nov. OTA for Pixel 7 on PF 6.2.1.0, I encounter these problems with the bad cable (support.zip attached):

Warning about boot model mismatch. It says WARNING: Your phone model is: <blank>, then ... selected device: 291...LL1 <same number as shown under ADB connected devies>.

Makes sense, as with the bad cable, this info is not shown.

If I continue nevertheless (OK), it errors out with return code 1, adb: error: failed to read copy response
[Google Pixel 7] badabing2003:
Thanks for the feedback

If the cable / port is bad, there's not much I can do about it, and I can't automatically detect the situation, because there are devices that don't match the phone model.
[Google Pixel 7] badabing2003:
New Release:

Nov 29, 2023 v6.3.0.0 release

New feature: Process build.prop, browse for the build.prop and it will extract PIF relevant fields, no fancy checking of dates or anything, if it is in there it will extract the values.

Added Magisk module uninstall / restore functionality.

Added PlayIntegrity API checking, can use one (or more) of the three apps from Playstore (user has to install the app)

Play Integrity API Checker (less reliable than the other two).

Simple Play Integrity Checker

TB Checker.

pif.json editing automatically kills the com.google.android.gms.unstable process, no need to reboot.

Magisk Management UI improvements

Bug fixes and improvements
[Google Pixel 7] SOCOM-HERO:
So I think I did a dumb thing. I tried processing a build prop file from one of my older devices to hopefully fix play integrity but when I made the edits to the file in Pixel Flasher I believe it wiped my build.prop file from my Pixel 7 as if I was making live edits to the build.prop file.

I can't restart the phone or power it off normally and am having other issues that indicate this is the case which is not good.

I do have the original Pixel 7 prop values for things like device/fingerprint/etc but not the full file - the phone won't let me open it now...

I grabbed the device info using Pixel Flasher and it still recognizes ADB and root commands, but I'm afraid if I do a hard reboot/power off it won't restart and I've effectively bricked the phone and would have to do a hard reset.

Am I screwed (as in hard reset is only option?) If that is the case I'll probably just run this guy locked and unrooted since the safetynet bugs are going to take a long time to battle and I can probably get near as many mods without root these days)

Some screenshots attached. If anyone knows the way out of this mess I've created please let me know.

Edit: I was able to download the build.prop file using mixplorer app and also grabbed the pif.json from there. Both look good, but I still can't restart the device, or edit USB options when connected to a PC. Pixel Flasher/ADB are working however...for now.
[Google Pixel 7] badabing2003:
Impossible, not only PF does not edit any build.prop, your device's build.prop is in a read only partition.

I have no idea what you have done or think you have done, but definitely this is not the case.

I don't even know why you need to have the original Pixel 7 prop values.
[Google Pixel 7] SOCOM-HERO:
False alarm, phone just needed a restart which I did out of Magisk app (for whatever reason the built in restart menu was not working). You were correct (obviously) but I was experiencing some weird stuff at the time of my post.

I'm just gotta steer clear of the Google Pay integrity issues and bring a physical card with me until that gets sorted. My banking apps don't detect this (yet). Hopefully the community can find a more permanent fix than spoofing.

Thank you as always!
[Google Pixel 7] badabing2003:
Latest Release Changelog:

Dec 02, 2023 v6.3.1.0 release

When processing build.prop extract values from ro.system.* and ro.product.product.* if ro.product.* values are not found, just like @osm0sis script does.

Bug Fix: On Linux, set permissions to readable before attempting pull.

Dec 02, 2023 v6.3.0.4 release

Support for @osm0sis Play Integrity Fork which uses a different path for the print file: /data/adb/modules/playintegrityfix/custom.pif.json

Dec 02, 2023 v6.3.0.3 release

Make Magisk dialog resizable

Add support for PlayIntegrityFix-resetprop

Dec 01, 2023 v6.3.0.2 release

Add debug message for module troubleshooting.

Handle unpdateJson entry for modules on Linux / Mac

Nov 30, 2023 v6.3.0.1 release

Update pif.json editing to use the one in /data/adb/pif.json, Playintegrityfix changed the location in version 14.0 beta

Bug Fix: #125, handle exception when a module's update link is broken.

Other silly oversight bug fixes.
[Google Pixel 7] Seriousfreedom:
Exactly how does that bulk apk install work exactly??

I had used pm in pixelflasher and downloaded apk's from phone to computer then flashed my phone and went to use the bulk install but the apk's don't show up when selecting the folder they were saved in
[Google Pixel 7] badabing2003:
You select the folder, not the apks, and every apk in that folder will be installed.
[Google Pixel 7] badabing2003:
New Release:

Dec 08, 2023 v6.3.2.0 release

Added Dump Screen XML (uiautomator).

With SPIC and Play Integrity Api Checker apps, when they hit quota limits, detect and report.

Added Playintegrity testing using Play Store (Developer options need to be enabled. First run takes longer as PixelFlasher tries to find the coordinates of the elements).

Added a setting to disable Firmware / OTA image hash validation, useful for firmware images that are for Pixel devices (example CalyxOS) but don't follow Google's naming convention.

Detect and report cases where a device rebooted into bootloader mode is not detected by the PC, provide suggestion on how to fix / continue.

Make the Magisk management window resizable and remember and load last size on startup.

Support for older Pif modules PROPS-v2.1 and PROPS-v2.0 as they store pif.json in a different location.

Improve pif.json extraction by detecting and using (if need be) ro.product.vendor.name ro.product.vendor.device ro.product.vendor.manufacturer ro.product.vendor.brand ro.product.vendor.model ro.vendor.build.fingerprint ro.vendor.build.security_patch

add pif print BUILD_ID extraction.

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

Dec 09, 2023 v6.3.3.0 release

When selecting build.prop to generate pif.json, you can now do multi-select, PixelFlasher will process them in a priority order based on the filename. build.prop being the highest priority.

Added Auto Copy to Clipboard which automatically copies the generated pif.json content to clipboard.

Added Auto Push pif.json which automatically pushes the file to the device and kills GMS process (after generated build.props processing).

Added Auto Check Play Integrity which automatically triggers the selected Play Integrity checker after editing or auto-pushing pif.json.
[Google Pixel 7] OfficeLinebacker:
Hi @badabing2003 .

I've been meaning to OTA update my rooted Pixel 7 for a while and after some research I used your tool.

I had two Magisk modules enabled, one for wireless tethering and one for passing safetynet. I disabled both of those (Step 10) from the Windows side, then flashed the latest OTA update. It went through the process and rebooted.

I seem to have lost root and those magisk modules.

I cant figure out what to do next. Should I reboot back to my previous slot? Re-root and install those Magisk modules from scratch? Some other option? Thanks!

Support.zip file attached here.
[Google Pixel 7] badabing2003:
I'll respond in the main thread as the issue is not device specific.
[Google Pixel 7] anas sami:
My banking apps are not working after updating to Android 14, dec ota update, Pixel 7. I have masked magisk (v26.4 stable). Hided root related apps with hidemyapps and blacklisted all the banking apps in magisk denylist. I'm using Play integrity fix 14.3. no shamiko. Please help.
[Google Pixel 7] badabing2003:
No need to cross post and this has nothing to do with PixelFlasher
[Google Pixel 7] ctradio:
Can pixel flasher mount the "user space" in a phone that won't boot? Can get to the login to input my code, but it reboots almost immediately after logging in. Need to delete just one file so I can free up storage space. Android 13 is too busy protecting me from myself to let me access the user data from my recovery (lineage OS / e/OS. I cannot list files under /sdcard no matter what I try to do. ADB shell appears to be running as root.
[Google Pixel 7] badabing2003:
Sorry, no such think in PF

you can try to issue the following command

adb wait-for-device shell ls -l /sdcard

or if you want to delete a file

adb wait-for-device shell rm -f <full_path_to_file>

You might want to reboot and then immediately issue the command.

No guarantees it will work, because the command will be executed as soon as adb state is detected

However user data might still not be mounted because you haven't unlocked the phone.
[Google Pixel 7] 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 7] 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 7] 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 7] ezflip:
Apologize up front for being a noob. I used Pixel Flasher to root my phone awhile back, then it took the A14 update. But when I try to use PF now, it will not let me patch the boot file like it did before. The patch button is grayed out. I tried multiple times with multiple downloaded factory images and OTAs from google. What am I doing wrong?
[Google Pixel 7] badabing2003:
A support file will help me figure it out.

Seeing that you used PF a while back, have you gone over the guide to make sure you're not missing one of the steps?

Perhaps selecting the stock boot ?
[Google Pixel 7] ezflip:
Is this the support file you need?

I ended up doing a factory reset because something I did put it into a bootloop. So I am starting over with a fresh install of A14 December update.
[Google Pixel 7] badabing2003:
Yes, that is a support file.

The reason you couldn't create a patch is because you were in bootloader mode, you can only create a patch when you're in adb mode and system if operational.
[Google Pixel 7] ezflip:
Progress...the patch button isnt gray now, but when I press it, it immediately gets aborted. New support file attached.
[Google Pixel 7] badabing2003:
Why is your phone in rescue mode or bootloader mode?

If you just wiped your phone, shouldn't it be running properly?

Like I said, you can't create a patch unless your phone is in adb mode and running properly,
[Google Pixel 7] ezflip:
Apparently I don't know the difference between fastboot, bootloader, and adb mode. It was in fastboot previously when you said it was in bootloader. PF can't see my phone if its on and running normally.

This was so easy last time. I booted to fastboot, patched the file and flashed it. I don't think I'm doing anything differently this time but I can't get it working at all. 🤷
[Google Pixel 7] badabing2003:
Yes you are, from v1 patching always required a functional phone.

It is impossible to create a patch in bootloader mode.

I suggest you go through the steps again, as it is clear that you need a refresher, in the steps there is a clear step to make sure that your device is detected in adb mode.
[Google Pixel 7] ezflip:
I figured it out. I'm definitely an idiot, but not for the reasons you said. I was doing everything correctly, I just forgot to turn usb debugging back on after the factory reset. All is well now. Sorry for wasting your time.
[Google Pixel 7] 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 7] 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 7] 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.