yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 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 6 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 6 Pro] badabing2003:
New Release:

May 04, 2022 v3.2.0 release

Help menu option to create support.zip file, which sanitizes (redacts user names and device IDs) of the log files.

This makes it super easy to provide support.zip file when something goes wrong and need to report it.

In boot management, delete firmware cache of the selected boot.img if it is the last boot.img used from that firmware.

Handle space characters in username.

Console is now responsive when processing firmware file.

More checks and validations.

Update readme with instructions on how to build PixelFlasher on MacOS.
[Google Pixel 6 Pro] nibera:
hello, can I use the tools to be able to switch from beta 1 android 13 to stable 12.1 android or to switch to beta 3 android QPR?
[Google Pixel 6 Pro] badabing2003:
See this and the follow up few posts.
[Google Pixel 6 Pro] wgrant:
Used this again to upgrade this month, worked perfectly. Thank you.
[Google Pixel 6 Pro] badabing2003:
New Release:

May 05, 2022 v3.3.0 release

MacOS build.

Handle Magisk module.prop with comments.

Exception handling on magisk module errors.

boot.img management improvements.

Removed old Powershell script.

More checks and validations.

support.zip now includes sanitized PixelFlasher.db
[Google Pixel 6 Pro] Thebear j koss:
I have a request if possible, how about an inverted theme for the tool? I am usually on my laptop at night and the light ui kills me lol
[Google Pixel 6 Pro] badabing2003:
The problem is with Windows controls

If you want to know more about it, you can read this.

See how it looks on MacOS and Kali-Linux (Default dark mode)

I'll see if I can do something forcefully, but I want to keep the code maintainable, maybe I'll find a way..
[Google Pixel 6 Pro] badabing2003:
@Thebear j koss I took a stab at it, this is totally garbage, some controls just can't change color.

I'd be embarrassed to put my name on it.
[Google Pixel 6 Pro] Thebear j koss:
No problem. I appreciate you trying. Windows has always had an issue with dark or inverted themes, their high contrast theme is atrocious. Function is more important than style in this case, plus I can always minimize and just go back to watching porn ..lol
[Google Pixel 6 Pro] wgrant:
This actually looks like a lot of the dark themed applications in Windows. I would use it personally but completely understand the desire for perfection in something you're creating.
[Google Pixel 6 Pro] pdaemon:
Hi,

I have flashed the factory image for Android 13 beta 2 (from Beta1) to my google pixel 6 pro with Pixel flasher and it all seems to work well, but then it keeps on rebooting to Fastboot mode. Any idea how to fix this?

I tried with magisk patched boot.img and also non and it doesn't boot.

Thanks Alot

Cheers pdaemon
[Google Pixel 6 Pro] badabing2003:
Can you provide a sanitized support.zip,

You can generate it from the help menu.

I'll take a look and see if I can spot anything.

When you say

> it all seems to work well, but then it keeps on rebooting to Fastboot mode.

So it boots into system, and and it appears to be working fine, and then all of a sudden it decides to go to fastboot?

Is that what is happening?

What Linux flavor are you using?
[Google Pixel 6 Pro] pdaemon:
Hi, thanks for getting back to me so quickly.

No the flashing process is working as expected, but then it just goes into Fastboot mode when it restarts.

It doesn't seem to back able to save the support file for some reason.

Cheers pdaemon
[Google Pixel 6 Pro] pdaemon:
I'm using Linux Mint 20.3 Cinnamon.
[Google Pixel 6 Pro] badabing2003:
Just to be clear, you generate the support.zip in PixelFlasher, are you not able to use PixelFlasher anymore?
[Google Pixel 6 Pro] pdaemon:
I restarted PixelFlasher and it was able to write the support.zip as expected.
[Google Pixel 6 Pro] pdaemon:
Hi,

I've updated my platform tools to v33.0.1 and flashed again keeping data with the factory boot.img and it's work this time!

Thank you very much for looking at this.

Can I just flash the magisk patched boot image now through Pixel flasher?

Cheers pdaemon
[Google Pixel 6 Pro] badabing2003:
Thanks,

Looking at the support.zip, some observations that could or could not be relevant.

I see that you're using SDK version 32.0.0-8006631, you should use the latest, specially since you're flashing a bleeding edge beta version, I'm not saying that this a problem or the problem, but it does not hurt.

You're also using Magisk 24309, which was released today, again, the latest is usually recommended, but this is hot of the presses, not sure if its has been battle tested.

I see one report that it failed with 24308, and suggestion was to use 24306

Pixel 6 Pro Android 13 Beta 2 breaks root - Issues Antenna

Device: Pixel 6 ProAndroid version: Android 13 Beta 2 (raven-tpbb.220414.015-factory-2cc44e38)Magisk version name: Canar...

issueantenna.com

I see that you disabled Magisk modules prior to flashing, you did good there.

Lastly, this might be the case for you.

PixelFlasher does this.

After flashing the image with skip-reboot, so that it flashes the patched image before rebooting it does this.

Reboots to bootloader

Sleeps 5 seconds

Flashes patched boot

reboots

Since it's in fastboot mode, it sounds like it did the 1 and 2, but didn't do 3 and 4

Maybe 5 seconds was not enough.

You can do one of two thing,

Just restart the phone , if that was the case, the phone should start normal but not be rooted.

Or if you rather be rooted right away, you can enable advanced mode,

select Custom Flash

Select boot and choose this file

```

/home/pdaemon/.local/share/PixelFlasher/boot_images/2a185a6ac900a60ee404f6bea387a37c/magisk_patched.img

```

and flash, since you're already in fastboot mode, it should flash the patched boot, then just do reboot system.
[Google Pixel 6 Pro] badabing2003:
Yes, see my previous message. The last step.

Happy to hear that all is well.
[Google Pixel 6 Pro] pdaemon:
Thanks for looking at this and the detailed explanation.

I have booted to Beta 3 but root isn't enabled.

I will downgrade to magsik 24306 as suggested and patch boot.

FYI, the software is great and way better than having to do it from the commandline.

Cheers pdaemon
[Google Pixel 6 Pro] badabing2003:
Thanks for your support, don't hesitate to come back if you run into issues.

For the next version,

- I'm adding a longer sleep (just to be safe), along with few echo messages to make it clear at what stage it reached.

- A button to fill with the currently selected boot file's path into the file picker.

It should make it easier to select boot.img from the list above without having to hunt for the file location.
[Google Pixel 6 Pro] rhetorician:
Guys, I'm not having success with the MAC release. I installed a Magisk module that killed my phone so I factory reset, updated Magisk, installed the tool and I can't get the tool find my or flash my phone. The program can't find platform tools which are located on my desktop. I must be missing something but I can't figure it out. I am trying to start all over again by wiping and installing the May update. I generated a support zip which I have attached here. I hope you can help. Thanks!
[Google Pixel 6 Pro] badabing2003:
Have you selected where your platform tools is located?

1- download the sdk if you haven't already (the blue button takes you to the download link)

2- unpack the zip somewhere

3- hit the browse button and select where you unpacked.

It should work.

Make sure you refresh the devices and select your device from the dropdown of the adb connected devices.

I also noticed that your firmware is: raven-sp2a.220505.002-factory-e1266508.zip.zip

notice the double .zip.zip

Although it shouldn't be a problem if it is a valid file, you should not rename it or add another .zip to it.

BB
[Google Pixel 6 Pro] rhetorician:
Thanks for the advice. I am still running into an issue, though, with platform tools. I have platform-tools on my desktop and when I go to select it through the button you noted it takes me to the downloads section for Pixel firmware. Perhaps I am overlooking something but I'm afraid I'm just not getting it for some reason :/

I sent you a PM with screenshots so you can better understand what I see.
[Google Pixel 6 Pro] badabing2003:
Check your PM, you're clicking on the second blue button not first.
[Google Pixel 6 Pro] badabing2003:
New Release:

May 21, 2022 v3.3.1 release

Change encoding from utf8 to ISO-8859-1

Button to paste the currently selected boot.img into custom flash file selection.

Several Mac version improvements, thanks to rhetorican for reporting and testing.

UI improvements

Fix: On low resolution screens, the application startup position is high enough to clip the top part.

Fix: On low resolution screens, the patch icon is too large and dis-proportional to the rest of the UI

Better dark mode handling on Mac / Linux

Increase the wait during flashing to account for slower devices.

Further improvements on support.zip redaction process.

Other minor fixes and additional validations.
[Google Pixel 6 Pro] badabing2003:
New Release:

May 25, 2022 v3.3.2 release

Handle system codepage.

Add configurable codepage setting in advanced settings to be able to override the value.

Selected boot color is now blue instead of red to avoid thinking that it has a problem.

After Flashing, clear connected device to avoid using device in case it is not yet ready.

Fix: Paste boot button should be hidden in basic mode.

Always print md5 of Magisk_patched (previously only verbose mode displayed it).

Wait 10 seconds instead of 5 seconds after reboot before issuing next command.
[Google Pixel 6 Pro] badabing2003:
Update:

June 06, 2022 v3.3.3 release

Bug Fix: When choosing custom ROM, the ROM file was not being copied to the package directory.

Update Documentation and screenshots.
[Google Pixel 6 Pro] Gytole:
Anyone fail at flashing to both slots? Pixel 6 Pro? Flashing one slot at a time is peach, but both causes errors
[Google Pixel 6 Pro] badabing2003:
There was another case of someone reporting that they got an error when flashing to both slots.

Although they didn't state if flashing each slot individually worked or not.

If you can create a support zip and provide that, I can take a look to see exactly at what point the flashing is failing, perhaps something can be spotted.
[Google Pixel 6 Pro] Thebear j koss:
So, newest version is just frozen with a loading circle and pixelflasher not responding in top left corner after hitting the button to process the firmware. Been like this for almost 40 minutes...
[Google Pixel 6 Pro] badabing2003:
That's probably unrelated to the newest version, does it work properly if you go back to the previous version? My suspicion would be no.

What happens if you kill it and restart it ? the same thing?

Does this happen while a phone is connected to the PC? or it doesn't matter if it is or not?

If you restart PixelFlasher, can you manage to create a support.zip file? if yes please create one and pass it along.

If none of that works,

Kill PixelFlasher processes

Kill adb processes

Try again?

Again if not

repeat the kills

Navigate to %APPDATA% directory, and zip up the PixelFlasher directory in there.

Provide me the zip file, and delete or rename PixelFlasher folder you just zipped.

PixelFlasher should start normally after that.

Let me know, thanks.
[Google Pixel 6 Pro] Thebear j koss:
So, I let it just go a little while longer and it processed the zip. Patched the boot img and flashed with no issues. For some reason it took forever to process the zip. All good though. Thanks.
[Google Pixel 6 Pro] badabing2003:
Oh good, happy to hear that it all worked, I'd be curious to know what might have happened.

if you could provide a support zip file, I'll take a peek to look for clues.

Thanks
[Google Pixel 6 Pro] Kris Chen:
I have used this tool to update pixel 6 pro ROM to Jun version and it works flawlessly and without any issue.
[Google Pixel 6 Pro] Lycidias:
Today I firstly used pixel flasher for installing the June update on my raven. I checked flashing to both slots and it finished just fine.

But after the initial reboot I only got stuck to the Google logo and then the logo faded away, just like the device stopped getting electricity/ power loss. Then boot looping and the same thing infinitely again. Very weird.

Ended up flashing the June patch with android flash tool and everything went well
[Google Pixel 6 Pro] badabing2003:
Thanks Lycidias for the info, would you be kind enough to provide a sanitized support zip file (You can generate one from the help menu, you don't have to run anything to generate one).

This can give some clues on what might have gone wrong.

Also was there any specific reason as to why you tried flashing to both slots?

Normally you don't have to.

Thanks
[Google Pixel 6 Pro] Lycidias:
Of course I can do it tomorrow, at work.

I wanted to flash to both slots because I install a custom ROM and be on the latest firmware at both slots. I simply don't know if I fastboot update a rom, the zip gets flashed to the current/updated slot or the older slot
[Google Pixel 6 Pro] badabing2003:
Thanks,

See this post,

It looks like flashing each slot separately works, but not at the same time,

The logs could help narrowing down the issue.

You can flash to both slots with Android flash tool?
[Google Pixel 6 Pro] Gytole:
Not at the same time. Idk how they do it, but I flash to one slot, then right when it tries to reboot I hold the volume down and make it boot right into bootloader again but then seitch the slot manually and re-run the flash tool. I flash to both slots because if you use magisk. If the phone randomly decides to switch slots, which it HAS on me before, when one side is rooted and the other is NOT, the out dated other side causes a bootloop for some reason. So I avoid it by running both slots. Overkill? Yes. But no bricks when I am out and a out. 🤣🤗

I will test the flash to both slots soon and pull a log and everything. For science!
[Google Pixel 6 Pro] niko26:
@badabing2003 - thanks for this great tool! It's very handy because Magisk and OTA has never worked for me :(

I have used your tool for the first time on a P6P, with the June update. Everythings seems to be running well.

A "wizard" to guide a noob through the steps would be nice to have for the future ;) We all know.. we're too lazy to read manuals :-D

Here is a feature suggestion.. during the process of flashing the firmware, the app seems to hang while it is actually unzipping the firmware.

It would be nice if there was a heads up that the UI will freeze or look non responsive (or even better ... if the UI was still responsive, multithreaded? ;) ).

Other than that .. very nice! Saves us a few (error prone) steps :) thank you very much again :)))

BTW - is there a donation button/link anywhere?
[Google Pixel 6 Pro] badabing2003:
Thanks Niko26 for you feedback and kind words.

Wizard guide is a great idea, but it can easily get complicated/messy specially considering each person's differing needs, I know perhaps one use case can be wizard-ized (if that is even a word) but choosing one hardly covers all needs, what I think would be better is someone who's good with videos, doing video tutorial(s), I prefer this option over a wizard mainly because it adds less code and less possibility for bug / regression. (I will not dismiss the idea though, if I can pull it off without making the code too complicated, I might do so).

Coming to the unzipping part, this is all part of the Google's flash process being done by fastboot, whether you do it with flash-all script yourself or you do it with PixelFlasher, it's the same process, PixelFlasher has nothing to do with that part. I'm puzzled as to why in your case it took that long to extract the product.img, I have never seen it that long.

See how long it took when I flashed the June release

Heads up warning is a good idea, specially if this is a common case, it is a balancing act of not annoying the user but still being informative, would such message in the console be satisfactory? A message that could scroll up (more on that below) or would you want a dialog with ok to dismiss? (the annoying part).

About the scroll up / multi-threading

The flashing part is multi-threaded, that is how you're able to see the messages scroll up while flashing without having to wait for the whole process to complete, although as you pointed out, the program blocked (intentionally, as I don't want to interfere while a flashing is ongoing).

I have already changed the buffering parameter (when the messages flush to console / file) few versions back and it is currently set to line buffering, which is the sweet spot, but as you can see, that output line does not output a newline after displaying

to disk ...

effectively that won't be displayed until it is completed (unfortunately not in my control).

As for donation link, I've said it before (it should be somewhere in these threads lol) this program will remain totally free, ad free, even donation free, it's my way to give a little back to the community that I benefited from for years.

You can contribute by helping the next newcomer to learn the ropes.

Thanks for your feedback.
[Google Pixel 6 Pro] niko26:
True, it can get complicated. My assumption is that the majority of users will use only a certain type of function from your tool. For them it might be beneficial. But yeah, it means more work for you ;)

Ok, I didn't know that it was all in one process which you trigger. I thought you'd expand the zip archive.

Why it takes so long? Hm.. I have SSDs built in - however they might be too slow. Some people still use regular harddrives - they'll wait even longer.

I don't have any issues with waiting, as long as I know something is happening in the background. In this case it seemed like the process completely hung.

I don't think one needs to have a dialog. Maybe an animation which shows "hey, I'm doing something, my UI is not frozen".

Disabling the buttons visually might do it. However, I am not an UX expert. But the UI complety freezing is not good IMHO.

Hats off! Thank you very much for your generous work again :)
[Google Pixel 6 Pro] Scalee:
Last time (may update) I used the A B method inside of Magisk, this failed horribly so this time I thought I'll use PixelFlasher, Unfortunately it did not go any better.

After flashing with patched image my phone started boot looping, so I tried again same result.

Then I tried flashing with the none patched boot.img this did work. And then flashed the patched version again finally got everything back up and running.

I tried using the create support zip in three different locations but that kept failing as well.
[Google Pixel 6 Pro] Lycidias:
Can't create support.zip
[Google Pixel 6 Pro] badabing2003:
@Scalee and @Lycidias

Are you running PixelFlasher as admin?

If you quit the app, and restart it, and then try to generate support.zip file (no need to do anything else in the app), does it work?
[Google Pixel 6 Pro] badabing2003:
I really would like to avoid yielding during the flash process, I'll see if I can manage something without adding risk.
[Google Pixel 6 Pro] Lycidias:
Yes I tried as an admin and different locations.

I am running windows 11
[Google Pixel 6 Pro] Scalee:
That did indeed work, strange since I tried saving to locations that don't require admin rights.
[Google Pixel 6 Pro] badabing2003:
PixelFlasher should not be run as admin,

Can you please share the support.zip it generated so that I see what might have gone wrong?
[Google Pixel 6 Pro] badabing2003:
Should not be run as admin, see my previous suggestion
[Google Pixel 6 Pro] Scalee:
Here you go, I hope it's helpful! Let me know if you need anything else.
[Google Pixel 6 Pro] badabing2003:
Yes it helps more than you can imagine.

Looking at the logs, you did everything right, and everything went smoothly, there is absolutely nothing wrong there.

The only thing I can think of is magisk module volte-properties somehow causing the bootloop.

Other than than It would be a puzzle.

I see that you are using a relase build 24.3 I personally tend to use the canary as it tends to include latest fixes.
[Google Pixel 6 Pro] niko26:
Totally get that and I agree. My suggestion is to disable all buttons during the flashing process and NOT making the UI "stall" (it should not give you the "process not responding" message when clicking on the UI while the flashing process (or any other) runs.

And.. it's just nit picking ;) You could quickly add a warning that during the process the UI becomes unresponsive and ask the user to bear with the flashing process. :)
[Google Pixel 6 Pro] banshee28:
After a few user errors, I successfully updated from May to June using the latest Magisk (25). All appears good.

Thanks.
[Google Pixel 6 Pro] badabing2003:
I have no control of how the application behaves when the process does not yield.

I'm changing the following popup

to

Hope that should help.
[Google Pixel 6 Pro] niko26:
"PLEASE BE PATIENT" ;) also... I don't understand why your main application stalls if you invoke the script to flash. Unless it's the main thread, your GUI should still behave properly and responsive, right?
[Google Pixel 6 Pro] badabing2003:
PLEASE BE PATIENT is applied, good idea.

For the gui to be responsive I have to

1- Yield in the thread of flashing to the UI

2- Make sure the user cannot click on anything on the UI and accidentally start other processes, and that could cause issues, although all is possible, it's quite a bit to make sure everything is done and done right.

Maybe one day when I have some free time, I'll work on that.