📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

[purgy]

Thanks for confirming,
I'll add it to the automated builds.

I'm not sure I understand the question regarding info.

From the release notes of 5.1.0.0

When a Pixel device is selected, PixelFlasher now displays additional information about the device's support. Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.

I'm on pixel 7a

 

[badabing2003]

From the release notes of 5.1.0.0

When a Pixel device is selected, PixelFlasher now displays additional information about the device's support. Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.

I'm on pixel 7a

Yeah, that's how long Google will support your device
It's probably May 2026 (Android update) and May 2027 (security update)
These are just public information that PF is telling you about.

 

[badabing2003]

New Release:
June 06, 2003 v5.3.0.0 release

• Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.
• PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's ), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.
  When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.
  If there was a way to pre-load odin with the extracted files, flashing could also be automated.
  I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.

 

[Cornloaf]

Pixel Flasher v5.3.0.0 was quarantined by Windows Defender. I never had an issue with any of the previous versions over the last 6 months or so.

Trojan:Win32/Wacatac.B!ml

There were two PIDs that it started that caused the quarantine. Anyone else seeing this behavior?

 

[badabing2003]

Pixel Flasher v5.3.0.0 was quarantined by Windows Defender. I never had an issue with any of the previous versions over the last 6 months or so.

Trojan:Win32/Wacatac.B!ml

There were two PIDs that it started that caused the quarantine. Anyone else seeing this behavior?

Are you getting this when you start the application or when you download.
By the way I use Windows defender as well and am not getting prompted.

Regardless, I can't do much about false positives.
Here's what changed in 5.3.0.0

You can read more about false positives.

Here's what VirusTotal thinks of 5.3.0.0

 

[Cornloaf]

Are you getting this when you start the application or when you download.
By the way I use Windows defender as well and am not getting prompted.

Regardless, I can't do much about false positives.
Here's what changed in 5.3.0.0

You can read more about false positives.

Here's what VirusTotal thinks of 5.3.0.0

I was fairly confident that your software is safe so I just posted here to see if you had any other inquiries about false positives. The alert came up after running the software once and closing out when I saw that the June 2023 update hadn't released yet. I was going to check for updates today and saw that the file was missing from my desktop and Defender logged that error. I downloaded the previous version and scanned it and it was clean. I downloaded 5.3.0.0 again and scanned it, no alerts. I ran the app, clicked a few things like the button to launch the Pixel download page and the system tools link... scanned the executable again and no alerts. Did a full computer scan and nothing.
Looks like it was a glitch on Defenders part this time!

 

[sawdoctor]

Are you getting this when you start the application or when you download.
By the way I use Windows defender as well and am not getting prompted.

Regardless, I can't do much about false positives.
Here's what changed in 5.3.0.0

You can read more about false positives.

Here's what VirusTotal thinks of 5.3.0.0

I know the current ubuntu version works on arch based distros but one of the manjaro tean members has started maintaing it in the aur

AUR (en) - pixelflasher-bin

aur.archlinux.org

Just a heads up

 

[badabing2003]

I know the current ubuntu version works on arch based distros but one of the manjaro tean members has started maintaing it in the aur

AUR (en) - pixelflasher-bin

aur.archlinux.org

Just a heads up

Thanks for the info,
I'm not familiar with the format, but based on what I'm seeing in here.

pkgbase = pixelflasher-bin
    pkgdesc = Pixel phone flashing GUI utility with features.
    pkgver = 5.3.0.0
    pkgrel = 1
    url = https://github.com/badabing2005/PixelFlasher
    arch = x86_64
    license = GPL3
    depends = glibc
    depends = zlib
    optdepends = android-tools
    provides = pixelflasher
    conflicts = pixelflasher
    options = !strip
    source = PixelFlasher-5.3.0.0::https://github.com/badabing2005/PixelFlasher/releases/download/v5.3.0.0/PixelFlasher_Ubuntu_22_04
    source = PixelFlasher.desktop
    source = PixelFlasher.png
    sha256sums = 3651036a6f629646dcd6b05940fb67847d19cd525374929aa6b03cc197a67b07
    sha256sums = 3f503e3e3b819562669e1d0a8a25043c478c8c1709b376642fd678caf3d8ee34
    sha256sums = 7ac7e66ab29fd58c300196cc5f639baec6d8070b12613dcf09877a2fc5522c0d

pkgname = pixelflasher-bin

I'm assuming that this is defining / publishing it in arch linux pkg format, where the source binary is the Ubuntu build, and it is declaring what are the dependencies, which I suppose if they are not present, they would be installed by the package.

If that is what is happening, than it's great, people can just install it using the native package manager?
It would be great if this is repeated on other Linux distributions.

What would be the way to install this on Manjaro?

sudo pacman -Syu PixelFlasher

 

[sawdoctor]

Thanks for the info,
I'm not familiar with the format, but based on what I'm seeing in here.

pkgbase = pixelflasher-bin
    pkgdesc = Pixel phone flashing GUI utility with features.
    pkgver = 5.3.0.0
    pkgrel = 1
    url = https://github.com/badabing2005/PixelFlasher
    arch = x86_64
    license = GPL3
    depends = glibc
    depends = zlib
    optdepends = android-tools
    provides = pixelflasher
    conflicts = pixelflasher
    options = !strip
    source = PixelFlasher-5.3.0.0::https://github.com/badabing2005/PixelFlasher/releases/download/v5.3.0.0/PixelFlasher_Ubuntu_22_04
    source = PixelFlasher.desktop
    source = PixelFlasher.png
    sha256sums = 3651036a6f629646dcd6b05940fb67847d19cd525374929aa6b03cc197a67b07
    sha256sums = 3f503e3e3b819562669e1d0a8a25043c478c8c1709b376642fd678caf3d8ee34
    sha256sums = 7ac7e66ab29fd58c300196cc5f639baec6d8070b12613dcf09877a2fc5522c0d

pkgname = pixelflasher-bin

I'm assuming that this is defining / publishing it in arch linux pkg format, where the source binary is the Ubuntu build, and it is declaring what are the dependencies, which I suppose if they are not present, they would be installed by the package.

If that is what is happening, than it's great, people can just install it using the native package manager?
It would be great if this is repeated on other Linux distributions.

What would be the way to install this on Manjaro?

sudo pacman -Syu PixelFlasher

It's an aur package so you'd use an aur helper to install it like yay or pamac or pikaur rather than pacman.

On manjaro if you enable the aur then pixelflasher is available in the native package manager (pamac) and appears in the gui (Software manager or whatever you want to call it) and then it's just a one click install

So for me I open the native package manager gui search for pixelflasher then press build and that's it job done, hope that makes sense

 

[Ultraman666]

I am on Windows 10 and trying to run PixelFlasher and its stuck at the loading screen and never starts the app, it use to work just fine, i am on the newest version, i have even tried to go to an older version and it wont load either. I also tried to run PixelFlasher as administrator and it still wont go past the loading screen. I have looked online but cant find anything that can help to get it working. Any ideas? Thanks for the help all

 

[badabing2003]

I am on Windows 10 and trying to run PixelFlasher and its stuck at the loading screen and never starts the app, it use to work just fine, i am on the newest version, i have even tried to go to an older version and it wont load either. I have looked online but cant find anything that can help to get it working. Any ideas? Thanks for the help all

Navigate to %APPDATA%\PixelFlasher
Look into the logs directory for the last file, and see if there are any errors, even if there aren't any, it would help to know what was the last event it recorded.
Then rename the PixelFlasher folder there, to something like PixelFlasher.old and start PixelFlasher again.
If it works, zip up the old folder and send it to me privately.

 

[Ultraman666]

Navigate to %APPDATA%\PixelFlasher
Look into the logs directory for the last file, and see if there are any errors, even if there aren't any, it would help to know what was the last event it recorded.
Then rename the PixelFlasher folder there, to something like PixelFlasher.old and start PixelFlasher again.
If it works, zip up the old folder and send it to me privately.

you got it i will give that a go thanks for the help

 

[Ultraman666]

you got it i will give that a go thanks for the help

ill be dang it worked naming it pixelflasher old, i will sent you the zip file in DM thanks man much appreciate the help

 

[badabing2003]

ill be dang it worked naming it pixelflasher old, i will sent you the zip file in DM thanks man much appreciate the help

Thanks, the zip will help me figure out why / where it ran into an issue.

 

[V0latyle]

@badabing2003 apoligize if this has been asked before...have you looked into what would be required for the digital signature necessary to get rid of the "Unverified Publisher" warning?

 

[badabing2003]

@badabing2003 apoligize if this has been asked before...have you looked into what would be required for the digital signature necessary to get rid of the "Unverified Publisher" warning?

You're talking about this?

I would need an official certificate to sign PixelFlasher, I looked into the free offering from https://about.signpath.io/code-signing/windows-platform for open source projects, and was denied because PixelFlasher was deemed to be hacking / cracking / jailbreaking type of software.

 

[V0latyle]

You're talking about this?
View attachment 5932049

Yep

I would need an official certificate to sign PixelFlasher, I looked into the free offering from https://about.signpath.io/code-signing/windows-platform for open source projects, and was denied because PixelFlasher was deemed to be hacking / cracking / jailbreaking type of software.

Lol wut. By who? I guess ADB Platform Tools is the same thing then, even though it's officially maintained by Google themselves

 

[badabing2003]

Yep

Lol wut. By who? I guess ADB Platform Tools is the same thing then, even though it's officially maintained by Google themselves

I know, I tried to explain, but then gave up, no point in arguing.

By the way, if you build it locally yourself, then you don't get those because it is self signed but trusted by your PC (only).
So if it bothers people or scares them off, they can always build it locally.
Same story with false positive malware alerts, people have a choice to inspect the open source code and build it themselves.

 

[V0latyle]

I know, I tried to explain, but then gave up, no point in arguing.

By the way, if you build it locally yourself, then you don't get those because it is self signed but trusted by your PC (only).
So if it bothers people or scares them off, they can always build it locally.
Same story with false positive malware alerts, people have a choice to inspect the open source code and build it themselves.

It's just annoying every time I update. I'm too lazy to build it myself lol

 

[badabing2003]

It's just annoying every time I update. I'm too lazy to build it myself lol

Actually if you want, you self sign it yourself so that you don't get bothered each time you use it.

- You would use openssl or makecert to generate a self signed certificate
- Install it in your system
- sign the executable (something like)

signtool sign /f <path_to_certificate_file> /p <certificate_password> /t <timestamp_server> <path_to_executable>

- You can verify the signature

signtool verify /pa /v <path_to_executable>