yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] 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 7] 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 7] elong7681:
I will uninstall the safetynet module and flash the kernel and report back. I'm not at my computer right now but when I get back to it I'll let you know what happens
[Google Pixel 7] elong7681:
So I uninstalled safetynetfix and I think it removed the enforcing flag but I was still unable to use the kernel

[ro.boot.product.hardware.sku]: [GVU6C]

[ro.boot.revision]: [MP1.0]

[ro.boot.secure_boot]: [PRODUCTION]

[ro.boot.slot_suffix]: [_b]

[ro.boot.theme]: [1]

[ro.boot.verifiedbooterror]: [ERROR_VERIFICATION]

[ro.boot.verifiedbootstate]: [orange]

[ro.boot.verifyerrorpart]: [vbmeta]

[ro.boot.warranty.sku]: [UGS]

[ro.bootloader]: [cloudripper-1.0-9074510]

[ro.bootmode]: [unknown]
[Google Pixel 7] badabing2003:
Have you checked the kernel forums / threads?

I don't know what Kernel it is, what it expects and what problems you're having, and even if I knew, I probably shouldn't give advice on it.
[Google Pixel 7] badabing2003:
New Release:

Dec 04, 2022 v4.5.0 release

New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.

New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.

Use latest Python updated packages.

Ubuntu 22.04 support.

Miscellaneous improvements.
[Google Pixel 7] badabing2003:
New Release:

Dec 05, 2022 v4.6.0 release

Added single click button to easily flash just the boot/init_boot (stock or patched) to the phone.

#39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.

#39 Do the Magisk backup only when rooted.

Decouple OTA sideload from needing factory image.

Other minor improvements.
[Google Pixel 7] efkosk:
Successfully installed December update. Excellent work! We thank you
[Google Pixel 7] jofa news:
Hello,

first of all thank you for the great tool.

My report about the first experiences:

After I received my new Pixel 7 last week, I immediately wanted to root it (like my old OnePlus 7).

The first attempts under Windows 11 and Linux failed and always bricked the Pixel.

This was not due to the PixelFlasher, but to the USB cable I used and its length.

After I tried it with the original cable everything worked :-)

One day later I had magisk so far that Google Wallet with PayPal worked without errors.

I just downloaded the December update and patched and flashed it.

Everything worked right away. YASNAC SaftyNet Check shows everything green :-)

Google Wallet also does not complain, so the next purchase at the checkout should all go well ...

Thanks again for PixelFlasher

Greetings Jerry
[Google Pixel 7] Bestiole222:
I can't launch 4.5.0 or 4.6.0 versions, I'm under windows 11, there's only the access fence "Pixel flasher is loading" and when it disappears nothing more (the app appears on windows task manager). 4.4.0 version is working fine.

Any idea?
[Google Pixel 7] badabing2003:
Please see this. 4.6.0.3 should work.
[Google Pixel 7] badabing2003:
New Release:

Dec 06, 2022 v4.6.1 release

#40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.

Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.

Credit to gecowa6967 at XDA.
[Google Pixel 7] Bestiole222:
That ok with 4.6.1, thanks a lot for your tool.
[Google Pixel 7] fullmetal509:
Once connected i try to to restar boot loader or do a Dry Run. It says phone doesnt seem to be connectedView attachment 5779835
[Google Pixel 7] asamofal:
badabing2003, Hi! Have some problems here...

Pixel 7, current firmware installed on the phone is 220804.031, I'm trying to patch a boot image but always failed. I tried on MacOS and Linux, the same error.

Spoiler content hidden.

Looks like the model is not recognised. Would appreciate any ideas.
[Google Pixel 7] scuzzo500:
@fullmetal509

Click on the box between adb connected devices and scan. I think that's what you need.
[Google Pixel 7] badabing2003:
Why is your device in recovery mode?
[Google Pixel 7] badabing2003:
As @scuzzo500 said, hit the scan button.

Read the main thread's OP or GitHub for usage.

If after scan and then selecting from the dropdown does not work, please provide support.zip
[Google Pixel 7] asamofal:
It was in "bootloader mode" but PixelFlasher requires "adb mode"... I thought recovery is what I need because in recovery mode my phone is available by "adb devices", I was wrong :)

Now I see, need just to enable USB debugging in developer options and keep the phone in "system running" state. Ok, now I patched desired init_boot with no problems. Thanks for the tool!
[Google Pixel 7] badabing2003:
When flashing the device can be in any mode, PF will detect the mode and reboot to bootloader (assuming that the device can get into bootloader mode)

However to create a patch, you need to be in adb mode.
[Google Pixel 7] scuzzo500:
I have a question and I hope someone can help me understand something confusing me. I've got my phone updated to the November patch. In the attached screen shot I have updated to the firmware circled in red. I know the December update is out and I'm set up and ready to apply it. However, I'm not sure if the firmware circled in blue is usable on my pixel 7 since labeling tda1 has changed to tq1a. I've got the global version so I figure I don't need to worry about the Verizon, telia, or o2 firmwares. Is this the right firmware for my pixel 7? If it is, why does Google change the labeling in, what to my experience is, such an odd way?View attachment 5780603
[Google Pixel 7] badabing2003:
This should tell you what they mean.

Yes TQ1A is good
[Google Pixel 7] scuzzo500:
@badabing2003

Thank you sweet baby Jesus. I've been looking using pixelflasher in every query and couldn't find anything about how Google numbered their releases. I never thought to just look at what Google uses as their naming convention.

All I want is to stay stock and rooted. I think this will do it for me. Thank you for the help.
[Google Pixel 7] miklat106:
Hi, I tried flashing the November image over the December one (downgrading) and it ended up giving me "cannot load android" message in recovery mode. I got out of it after flashing the December OTA again from the android flash tool but I'm wondering what I did wrong. Is it because I tried flashing and older update on top of a new one without wiping?

Don't know if it matters but I did with a patched boot as well (patched by PF).
[Google Pixel 7] badabing2003:
I don't know, I had a similar issue flashing Aug release on a September running Redfin.

You can read all about it here.

I don't know if it is possible, I would assume it is, but the only time I tried I was not successful.
[Google Pixel 7] krugm0f0:
This tool is a game changer! Wow! Thank you!
[Google Pixel 7] fivefour:
I've not used this tool but being available for Linux makes it interesting, I normally use CLI but wanted to subscribe to the topic and say thanks for making it available. Bookmarking if you will for future use.
[Google Pixel 7] bizkit_120:
Hello, thanks for sharing, moving from op 9 to Pixel 7.

QQ, do you see any major benefits on Dec update? ( Like clear call..I may gonna hold awhile no sure if any bugs) Good to hear your Google pay works, how about inTune company Portal ,can it bypass root check?
[Google Pixel 7] jofa news:
Hi @bizkit_120,

I haven't had any issues with the Nov update, I don't see any fixes in the Dec update that are relevant to me.

My phone calls were and are clear. I was hoping there were improvements with the fingerprint sensor, but that wasn't the case with the Dec. update.

I can't say anything about inTune Company Portal since I don't use it.

But with my rooted OP7 with EvolutionX, many apps detected the rooting but didn't cause any problems.

With Android 13 on the Pixel 7, I no longer have an app that detects rooting. Most important for me was Goolge Wallet (Pay).

Merry Christmas and best regards
[Google Pixel 7] bizkit_120:
Nice, this is my first pixel device, Finger sensor i won't say bad but definitely OP 9 is more faster and accurate, for me p7 got 2 out 10 fail to recognize, still acceptable range.

Yep.Google wallet important to me as well, still plenty of merchants not accepting it, big ones like Lowe's, walmart , kroger...

Thank you, same to you, Merry Xmas! Cheers,
[Google Pixel 7] Moppusan:
Just rooted my Pixel. That was so much easier than rooting my old OnePlus 5T. Finally have AdAway back!

Thank you to @badabing2003 and all the PixelFlasher devs.

Happy New Year everyone!​
[Google Pixel 7] mruno:
How to update and retain root after connecting phone and enabling usb debugging:

1 - click Pixel Phone Factory Image button and download from website

2 - browse to the location of the downloaded update

3 - process the update by pressing the rocket 🚀 button

4 - select the update

5 - click the Patch button

6 - select the patched image

7 - click Flash Pixel Phone

be patient and let the device update and reboot. it should take 2 - 5 mins.

View attachment 5802799
[Google Pixel 7] jofa news:
@mruno :

do I need to do the two steps before?

- Disabled all modules

- UInhide Magisk

or can I skip these steps with PixelFlasher?

Many greetings

Jerry
[Google Pixel 7] badabing2003:
You do not need to hide Magisk, as for disabling modules, it all depends on the modules, I don't disable any of mine, but then again the modules I use are basic and safe for updates.

Examples. Systemless hosts, busybox, safetynet fix, ....

You can enable/ disable modules from within PF.
[Google Pixel 7] jofa news:
Thank you, i will try ... yeah ... it works ...

thx, this is a wonderful tool :)
[Google Pixel 7] PurppleMonkey:
Can i use this to root for the first time ?
[Google Pixel 7] Aks:
Yes, you can. Just follow instructions
[Google Pixel 7] PurppleMonkey:
TY !

i used the "flash boot" button !

But, if i want to flash the firmware with the patched boot, the phone get stuck in fastboot mode for 15min... something get wrong ? (mac user)
[Google Pixel 7] badabing2003:
Check this and this
[Google Pixel 7] PurppleMonkey:
TY !

With the next update i'll try with a USB A to USB C - Connected to a Thunderbolt port !

Q° - During the flash, there is no problem to stop the process if it still blocks?
[Google Pixel 7] badabing2003:
Definitely there is, depending on when you stop the process.

If it is stuck at fastbootd, you can unplug and replug safely in hopes that it gets detected and continues.

You can only stop the process (abort) if what has been flashed to that point is compatible with what's left behind from the previous flash.
[Google Pixel 7] charlie..:
I'm new to the pixel family. Root worked very well (wihtour pixel flasher). Now I stumbled over a question which is rather related to the PF but maybe can be answered here anyway.

How does the beta opt-on or opt-out procedere work with focus on data loss.

Is it possible, coming from stock rom, to simply flash the current beta to opt-in and opt-out with the next stable release without full wipe. I read that in the end of the beta there will be the chance to come to the stable release without wiping data.

Shortend question: Can I switch between stable and beta release (each way) wihtout data loss?

PS. @badabing2003 congrats and thank you for such a master piece of software and your unstopable support.
[Google Pixel 7] mruno:
Check out the verbiage "Once you're enrolled" at the bottom of this page: https://www.google.com/android/beta#devices
[Google Pixel 7] Bestiole222:
Hi to everyone, I'd like to disable verity and verification on my phone to install custom kernel and I saw that there's an option in pixelflasher. Do I have to do this operation each time I install a ROM update or it's only one time? Because I read that these operation needs a wipe data.

Has someone install a custom rom patched with pixel flasher?

Thanks in advance for your answers ans thanks a lot for this great tool.
[Google Pixel 7] badabing2003:
I believe you have to select those options every time you flash, don't quote me on this as I don't use custom ROM, if I'm not mistaken the wipe is only when you switch from one state to the other, again this is pure speculation, I'll let someone who flashes custom ROM speak up.
[Google Pixel 7] bao_gg:
My Pixel 7 is on TQ1A.221205.011 build. I just unlocked the bootloader so all the user data are gone. Now I want to use PF to root the phone. So on PF I can browse to find the platform tools which version is 33.0.3 and factory image (panther-tq1a.221205.011-factory-ab58bb03.zip). I processed the zip file and saw there is a boot.img file showed up. I think for P7 we should use ini.boot.img. Is it OK to go ahead? And do I need to flash into inactive slot for safety reason?

Also I haven't installed Magisk yet. Is there a option that I can get Magisk Delta? My final purpose is to root the phone and then get 32-bit app supported.
[Google Pixel 7] badabing2003:
where do you see boot.img ?

In the list you see boot.img?

or just the label to the left.

Select the boot and the console should show you the path and filename. PF knows that it needs to use init_boot with P7

Yeah, flash to inactive.

There is an option to install Magisk Alpha and Magisk Delta are supported, and they can be installed all from PF.

Make sure you only install one, and when installing, make sure you first unhide magisk, if you have one hidden.

After installation if PF says Magisk not found, just update the package name in the PF configuration section (Magisk delta has different package name, soon to be released next PF should do this automatically)
[Google Pixel 7] bao_gg:
Thank you badabing2003 for help.

I mean the file is the zip file with SHA1 and Package Fingerprint.

The left there is "select a boot.img".
[Google Pixel 7] bao_gg:
Installed Delta first but PF did not detect it as you said the package name is different.

And then choose stable version everything works like a charm.

One more thing: Open magisk app I just see "App 25.2 installed". Above that there is a Magisk logo but shows Installed N/A.
[Google Pixel 7] badabing2003:
You didn't have to change it if you wanted the Delta, all you had to do is go to pF configuration and enter the Delta's package name io.github.huskydg.magisk

Did you create a patched boot using magisk and flashed that? or you just installed Magisk Manager?
[Google Pixel 7] bao_gg:
My bad. I installed the magisk and then forgot to flash the patched file.

After flashing pixel phone, at first it says system is corrupt and restart automatically and then got stuck on Goolge logo.
[Google Pixel 7] bao_gg:
Tried to recover the device by hold power key for 30s.

I think the problem is the magisk is not fully installed because the Magisk logo beside the "Reboot to bootloader" is greyed out.
[Google Pixel 7] badabing2003:
Please provide a support.zip file from PF help menu and I'll take a look.

The Main thread and the Github are linked in the OP, both of which has the usage details.
[Google Pixel 7] bao_gg:
Thanks.
[Google Pixel 7] badabing2003:
You had never updated your phone previously?

Just flash to both slots and you should be fine.

Why not go with January update? or better yet on Monday with the February drop?
[Google Pixel 7] bao_gg:
I planned using PF to update Jan patch. Now I would wait for Feb one.

According to the main thread, we need to grant root permission to shell in Magisk. But I can't find this option.

Thank you.
[Google Pixel 7] badabing2003:
New Release:

Feb 05, 2023 v4.7.0 release

Added Magisk Backup Manager:

List all Magisk backups currently on the device.

Highlight the one that is backup of the current installed version.

Delete backups.

Manually add backup from PC.

Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.

Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk

Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.

Magisk installer improvements:

When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.

Magisk installer window displays the package name.

You can now copy to clipboard, the download URL and package ID.

Magisk Manager columns are now wider for better readability.

Package Manager improvements:

Added Search / Filter option.

Show count of filtered packages.

Application Name (label column).

"Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.

Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).

Other under the hood improvements.

When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.

More verbose logging that helps with troubleshooting.

Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.

Moved existing links under Help Menu | Links, and added few more handy links.

Added timestamp to support.zip filename.

On request, spinning cursor with text "Please be patient ..." is now displayed in red.

Flashing to inactive slot is now in basic configuration instead of advanced configuration.

Preparation work for version 5.0 DB improvements.
[Google Pixel 7] bjevers:
@badabing2003 I'm having an issue and not sure what the problem is. I first flashed the latest update to my Pixel 7 Pro and it went fine. Next, I tried to update just a normal Pixel 7, but his time it fails with a message saying it can't find the Magisk patched boot image. Yes, I processed and patched the panther boot image. I have attached a support zip. I had the same issue last month and I think I fixed it by deleting the PixelFlasher folder under AppData\Roaming. I will do that now to verify and update this post.

EDIT: Nope, deleting the folder didn't work. Not sure what I did last time.

EDIT 2: Now I remember, I have 2 Pixel 7 devices (1 for each of my daughters). I plugged in the other one and everything went fine. And I used that patched image to flash the second Pixel 7. Just not sure why the one doesn't work for patching. They both have the same version of Magisk.
[Google Pixel 7] badabing2003:
You have Magisk hidden, hence no Magisk Manager, just a stub.

And you have not granted adb shell access, hence root is not allowed.

You can't create a patch.

Best to grant root access, but if for whatever reasons you don't want to, then unhide Magisk before patching so that full Magisk Manager is available to create a patch.

I'd add login in the next version to block you from attempting to patch when your phone is in this state.
[Google Pixel 7] bjevers:
Hmm, I have it hidden on all 3 phones and it worked fine on 2 of them.

Ok, I think I figured it out. I have the Magisk package name set to the phone that didn't work in the advanced settings and since it couldn't find that on 2 of the phones, it patched with the Magisk included with PF. Correct?
[Google Pixel 7] badabing2003:
No because you have not granted root access to adb shell.

See Basic Usage point 2.
[Google Pixel 7] praveenpc:
I have windows 7 with 32 bit. It shows error .." Check your computer's system information to see whether you need a x86 or x64 version....."
[Google Pixel 7] norbert.x:
How long does it take for your devices to boot into android after flashing? I tried to go from Nov update to Feb and it just stayed with the google logo forever (waited 20 mins). I then flashed the patched Nov factory image and everything was back and also booting more or less instantly.

I further tried going from Nov to Dec update, but the same thing happens. I'm alrady waiting for 15 mins and all I see is the Google-Logo. Kinda lost here.

To clarify:

In my first attempt, I had my magisk modules on.

But switched those of for the next tries (for both nov-feb and nov-dec) and rebooted the device to check wether they're disabled in Magisk Manager.

What could be the reason for the device not booting?
[Google Pixel 7] badabing2003:
Support.zip can give me an idea of what's going on.

Help menu.
[Google Pixel 7] norbert.x:
here you go
[Google Pixel 7] badabing2003:
You're using

Android SDK Version: 34.0.0-9570255

Which is known to have issues.

Switch back to 33 and you should be fine.
[Google Pixel 7] norbert.x:
Oh man I feel dumb now. The first time I update platform tools (you know, to not run into any incompatibilities) and I achieve the complete oposite.

Switching to 33 did the trick, update worked.

Thank you very much!
[Google Pixel 7] badabing2003:
Blame it on Google for breaking it, otherwise you did the right thing, the latest has always been the recommended one to use.
[Google Pixel 7] badabing2003:
New Release:

Feb 12, 2023 v4.8.0 release

#50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro

#48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.

Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues

Disable Magisk Backup Manager button if root access to adb shell is not granted.

Button to Open adb shell connected to the selected device.

Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
[Google Pixel 7] happynexuss:
I was able to use Pixel Flasher to update to the January release, but both February and March images are refusing to make a Patched boot image. Any help is greatly appreciated! I'm including a support.zip.