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

Search This thread
By:
Advanced…
B

bigdumb111

New member
Jun 4, 2023
3
1
Hey, im on a bootloader unlocked pixel 7 (panther) and tried using this after running into issues with manual methods.

The patching went fine with no errors, but when it booted up, it said "Cannot load android system [etc etc]"

Which is the same issue i had previously. Tried flashing the stock boot.img to the same issue, tried wiping to the same issue.
How fix?
 
B

bigdumb111

New member
Jun 4, 2023
3
1
bigdumb111 said:
Hey, im on a bootloader unlocked pixel 7 (panther) and tried using this after running into issues with manual methods.

The patching went fine with no errors, but when it booted up, it said "Cannot load android system [etc etc]"

Which is the same issue i had previously. Tried flashing the stock boot.img to the same issue, tried wiping to the same issue.
How fix?
Click to expand...
Click to collapse
huh. well that was weird. I installed the latest factory image and flashed it with the mode set to wipe, but I managed to boot. On top of that I booted back to my home screen as if it had never been wiped.
 
shoey63

shoey63

Recognized Contributor
Jun 5, 2012
4,244
4,361
Somewhere in Oz...
Sony Xperia XZ2 Premium
ASUS ROG Phone 3
badabing2003 said:
Yes, this build is confirmed to address that infamous libwx_baseu_net-3.2.so issue.
Let me know if you encounter any issues, hopefully we put it to bed once and for all.

You don't need to have Python at all, unless you're trying to build it yourself.
Executable bundles what it needs.
Click to expand...
Click to collapse
No issues now, fires up straight away.
No problems flashing either. I flashed the May OTA zip (twice) and my p6 is now rooted with the same firmware on both slots, and both slots are bootable.
Great work.
 
  • Like
Reactions: badabing2003
Slim2none4u

Slim2none4u

Senior Member
Oct 28, 2011
958
622
50
Livermore Falls
www.youtube.com
Verizon Droid Incredible 2
Sprint HTC EVO 4G LTE
  • Like
Reactions: J.Michael
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,001
4,636
bigdumb111 said:
Sorry if it wasn't clear by my update but I got my phone booted and magisk working. Here's the log file as requested: https://pastebin.com/bHWen09D
Click to expand...
Click to collapse
By the way, in the future, if you click on the big support button or from the help menu, PixelFlasher generates a support.zip file that is sanitized (sensitive information like device id, username ... are redacted) furthermore It include visual event trace that makes it much easier for me to troubleshoot and understand what might have happened instead of scrutinizing the logs.
Much easier and better for you, and for me as well,

If this was my phone, I wouldn't trust the current state,
I don't like the fact that on slot a you routinely got this warning.

Code: 
Warning: skip copying bootloader_a image avb footer (bootloader_a partition size: 0, bootloader_a image size: 12628232).
Warning: skip copying radio_a image avb footer (radio_a partition size: 0, radio_a image size: 113868940).

Considering that your last flash was with wipe, and you didn't even get a wipe it does not smell good.
As @Slim2none4u pointed out, stay away from Platform tools 34.x and use 33.0.3

If wipe is still an option do the following.
  1. Enable advanced configuration
  2. make sure to use Platform Tools 33.0.3
  3. select factory, and the stock boot
  4. select Wipe all data
  5. select Flash to Both Slots
  6. select Force
  7. Flash Pixel Phone
  8. Provide support, so that I can check if everything was flashed properly., no warnings, no errors.
If all good, setup phone, install Magisk
select patch (if Magisk version is the same, you don't have to create patch again, you already have)
Flash Boot
 
  • Like
Reactions: J.Michael and Slim2none4u
P

purgy

Senior Member
Aug 29, 2013
183
62
Sydney
Google Pixel 7a
I can't get v5.2.0.2 to run on windows 7.
At first it complained about api-ms-win-core-pathl1-1-0.dll being missing, i found a copy of that, plonked in in sysWOW64 and win32 which fixed that...

Now on launch, it presents a "Fatal error detected" error, with the text
No error messages generated.
FormatMessageW: the paramater is incorrect.
Click to expand...
Click to collapse

OKing that away, leads to another Fatal error message, this time the text is
Error loading Python DLL
'd:\users\me\AppData\Local\Temp\_MEI103482\python310.dll'
LoadLibrary: PyInstaller: FormatMessageW failed
Click to expand...
Click to collapse

python310.dll is indeed present in that directory, and i'm not sure what steps to take from here. There don't seem to be any issues like this reported on the github, and a few searches of this thread haven't turned up anything either.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,001
4,636
purgy said:
I can't get v5.2.0.2 to run on windows 7.
At first it complained about api-ms-win-core-pathl1-1-0.dll being missing, i found a copy of that, plonked in in sysWOW64 and win32 which fixed that...

Now on launch, it presents a "Fatal error detected" error, with the text


OKing that away, leads to another Fatal error message, this time the text is


python310.dll is indeed present in that directory, and i'm not sure what steps to take from here. There don't seem to be any issues like this reported on the github, and a few searches of this thread haven't turned up anything either.
Click to expand...
Click to collapse
Check the Github link, try to build it yourself and see if it works.
Sounds like library dependencies.

Were you able to run older versions? and only 5.2.0.2 can't run?
 
Last edited:
  • Like
Reactions: Slim2none4u, purgy and J.Michael
J

J.Michael

Recognized Contributor
Jan 20, 2018
2,050
2,425
Samsung Galaxy Tab A series
purgy said:
That's the only version I've tried, I'll try some earlier releases, thanks.
Click to expand...
Click to collapse
It makes sense that when you OK the "error in FormatMessageW", you then get an "error returned by FormatMessageW".

Maybe a mismatch between whether your computer is 32-bit or 64-bit Windows, and which size Python you installed. (The first Google result was someone on stackoverflow who I think got the error when he built an executable on his Windows 10 machine and then tried to run it in a Windows 8 virtual machine. I think he found that if he built the executable in the virtual machine, that executable worked on both machines.)
 
  • Like
Reactions: badabing2003 and purgy
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,001
4,636
purgy said:
im getting the same messages whichever version I try, i've got all the way back to 5.0.0.1

building from source is probably a bit beyond me tbh

edit- 5.2.0.2 built on my pc with python 3.8.10 (last working for win7) is working it seems, thanks!
Click to expand...
Click to collapse
Great that you got it working.
So Python 3.10 is not compatible with Windows 7?
I'll see if I can add an automated GitHub build that builds with Python 3.8.10, if that works you won't have to build manually on every release.
 
  • Like
Reactions: Thebear j koss, J.Michael and purgy
P

purgy

Senior Member
Aug 29, 2013
183
62
Sydney
Google Pixel 7a
badabing2003 said:
Great that you got it working.
So Python 3.10 is not compatible with Windows 7?
I'll see if I can add an automated GitHub build that builds with Python 3.8.10, if that works you won't have to build manually on every release.
Click to expand...
Click to collapse
Hey, that would be greatly appreciated if it's not too much effort.

Otherwise, now I've worked out wtf I'm doing, building from your git is pretty straightforward with the directions you gave. Thanks for laying it all out so clearly.
 
  • Like
Reactions: Thebear j koss, J.Michael and badabing2003
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,001
4,636
purgy said:
Hey, that would be greatly appreciated if it's not too much effort.

Otherwise, now I've worked out wtf I'm doing, building from your git is pretty straightforward with the directions you gave. Thanks for laying it all out so clearly.
Click to expand...
Click to collapse
Give this build a shot,
If it works, then I'll add it to main build.

PS: The link might require you to be signed in to Github (not sure).
 
  • Like
Reactions: purgy
You must log in or register to reply here.

Similar threads

T
[ROM] [BETA] [ANDROID 7] PrimeOS: Android for Laptops/PCs - V0.6.1
Replies
5K
Views
2M
ExTw0
ExTw0
superdragonpt
[RECOVERYs] [ROMs] [UNLOCK BL] ASUS Memo Pad HD 7 (me173x) [MT8125] [MULTILANG]
Replies
2K
Views
994K
onstantint
onstantint
lokeshsaini94
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
Replies
1K
Views
1M
alisadty
alisadty
D
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Replies
2K
Views
841K
jeff_0618
jeff_0618
S
Intel Android Devices Root / Temp Recovery Session
Replies
1K
Views
949K
K
Koleczek

Top Liked Posts

24 Hours 30 Days All time
  • 6
    badabing2003
    badabing2003
    nikola1970 said:
    Hello all,

    Currently my 7 Pro is rooted with Magisk Stable 25.2, but my bank app detect root and I cant use it.
    I want to install Magisk Alpha https://github.com/Displax/safetynet-fix/issues/32 with this tutorial, but I am a little bit confused what to do, can someone explain me what to do with old magisk?
    I installed Alpha as apk btw.

    Thanks in advance guys
    Click to expand...
    Click to collapse
    Not sure why you would need TWRP and flash alpha in TWRP, that instruction could be for a different phone.
    You should be able to flash alpha in fastboot.
    But in any case, if you want to follow that guide, than PF is no use for you, yes you can flash TWRP using PF, but you also could using fastboot, and then you still need to use TWRP to flash Magisk, and not use PF.

    When you're considering to replace some Magisk with some other Magisk (either an older on or a different flavor)
    Two things need to be updated.
    The manager application, which is easy
    And the boot partition (along with the data in /data/adb/magisk)
    You could delete everything in /data/adb/magisk while rooted with the current Magisk, and then uninstall Magsik app and flash stock boot. That will take you to a stock state, and then easily install the other Magisk and follow the rooting steps with it.
    You might ask, why would I need to do all that, can't I just replace Magisk Manager and install in place?
    Depending on the version of Magisk you're running, as soon as you uninstall the Manager, as stub might be installed again by the root portion, so installing a different flavor my end up being blocked / replaced.

    For that PF has a special feature.
    Go to settings and Enable Advanced Options and Offer Patch Methods.
    1695246518810.png


    Next make sure you download to your PC the Magisk version that you want to install.
    Next select the stock boot in PF and hit the Patch button.
    You will be offered patch options like the following.
    1695246565846.png


    Select the downloaded Magisk.
    What this will do is it will create a patch using the selected Magisk rather than the installed Magisk, without having to worry about it being installed or not.
    Uninstall Magisk Manager from the phone.
    Select the created Patch in PF and hit "Flash Boot" not Flash Pixel Phone.

    When the phone reboots you would be rooted with the new Magisk,
    Install it's Manager and you're done.
    View
    4
    N
    nikola1970
    badabing2003 said:
    Not sure why you would need TWRP and flash alpha in TWRP, that instruction could be for a different phone.
    You should be able to flash alpha in fastboot.
    But in any case, if you want to follow that guide, than PF is no use for you, yes you can flash TWRP using PF, but you also could using fastboot, and then you still need to use TWRP to flash Magisk, and not use PF.

    When you're considering to replace some Magisk with some other Magisk (either an older on or a different flavor)
    Two things need to be updated.
    The manager application, which is easy
    And the boot partition (along with the data in /data/adb/magisk)
    You could delete everything in /data/adb/magisk while rooted with the current Magisk, and then uninstall Magsik app and flash stock boot. That will take you to a stock state, and then easily install the other Magisk and follow the rooting steps with it.
    You might ask, why would I need to do all that, can't I just replace Magisk Manager and install in place?
    Depending on the version of Magisk you're running, as soon as you uninstall the Manager, as stub might be installed again by the root portion, so installing a different flavor my end up being blocked / replaced.

    For that PF has a special feature.
    Go to settings and Enable Advanced Options and Offer Patch Methods.
    View attachment 6007183

    Next make sure you download to your PC the Magisk version that you want to install.
    Next select the stock boot in PF and hit the Patch button.
    You will be offered patch options like the following.
    View attachment 6007185

    Select the downloaded Magisk.
    What this will do is it will create a patch using the selected Magisk rather than the installed Magisk, without having to worry about it being installed or not.
    Uninstall Magisk Manager from the phone.
    Select the created Patch in PF and hit "Flash Boot" not Flash Pixel Phone.

    When the phone reboots you would be rooted with the new Magisk,
    Install it's Manager and you're done.
    Click to expand...
    Click to collapse

    Wow thank you so much for detailed reply, this will be helpful for me in the future.
    Yesterday i just uninstalled Magisk directly from the app, after that installed Alpha, then patched init_boot with app, and flashed directly from cmd.
    View
    3
    badabing2003
    badabing2003
    Thebear j koss said:
    So @badabing2003 I got a new laptop a few weeks back after having so many issues with my old 1. I tried to update to the September patch with PF and it kept failing, device would lose connection after rebooting to bootloader/fastboot. I tried different cables, different ports, tried side loading ota, flashing in command prompt... So long story short, I'm a total idiot and just needed to update my driver. After a loooong night of tearing my hair out trying to figure out what is wrong, PF sped thru the update in less than 5 minutes after I realized what a dummy I am. Hopefully I'll be issue free for a few years. With the new laptop with 12gb of RAM I should be alright. 👍
    Click to expand...
    Click to collapse
    Sorry to learn that it took hair pulling for a simple thing, and happy to see that you figured it out.
    We all get episodes like that, you're not alone, there are days my brain cannot add one plus one.
    No pain no gain :)
    View
    2
    Thebear j koss
    Thebear j koss
    So @badabing2003 I got a new laptop a few weeks back after having so many issues with my old 1. I tried to update to the September patch with PF and it kept failing, device would lose connection after rebooting to bootloader/fastboot. I tried different cables, different ports, tried side loading ota, flashing in command prompt... So long story short, I'm a total idiot and just needed to update my driver. After a loooong night of tearing my hair out trying to figure out what is wrong, PF sped thru the update in less than 5 minutes after I realized what a dummy I am. Hopefully I'll be issue free for a few years. With the new laptop with 12gb of RAM I should be alright. 👍
    View
  • 6
    badabing2003
    badabing2003
    nikola1970 said:
    Hello all,

    Currently my 7 Pro is rooted with Magisk Stable 25.2, but my bank app detect root and I cant use it.
    I want to install Magisk Alpha https://github.com/Displax/safetynet-fix/issues/32 with this tutorial, but I am a little bit confused what to do, can someone explain me what to do with old magisk?
    I installed Alpha as apk btw.

    Thanks in advance guys
    Click to expand...
    Click to collapse
    Not sure why you would need TWRP and flash alpha in TWRP, that instruction could be for a different phone.
    You should be able to flash alpha in fastboot.
    But in any case, if you want to follow that guide, than PF is no use for you, yes you can flash TWRP using PF, but you also could using fastboot, and then you still need to use TWRP to flash Magisk, and not use PF.

    When you're considering to replace some Magisk with some other Magisk (either an older on or a different flavor)
    Two things need to be updated.
    The manager application, which is easy
    And the boot partition (along with the data in /data/adb/magisk)
    You could delete everything in /data/adb/magisk while rooted with the current Magisk, and then uninstall Magsik app and flash stock boot. That will take you to a stock state, and then easily install the other Magisk and follow the rooting steps with it.
    You might ask, why would I need to do all that, can't I just replace Magisk Manager and install in place?
    Depending on the version of Magisk you're running, as soon as you uninstall the Manager, as stub might be installed again by the root portion, so installing a different flavor my end up being blocked / replaced.

    For that PF has a special feature.
    Go to settings and Enable Advanced Options and Offer Patch Methods.
    1695246518810.png


    Next make sure you download to your PC the Magisk version that you want to install.
    Next select the stock boot in PF and hit the Patch button.
    You will be offered patch options like the following.
    1695246565846.png


    Select the downloaded Magisk.
    What this will do is it will create a patch using the selected Magisk rather than the installed Magisk, without having to worry about it being installed or not.
    Uninstall Magisk Manager from the phone.
    Select the created Patch in PF and hit "Flash Boot" not Flash Pixel Phone.

    When the phone reboots you would be rooted with the new Magisk,
    Install it's Manager and you're done.
    View
    5
    I
    iwearthebelt
    Just for the record, I have been using 33.0.3 for a long time and decided to take a chance on 34.0.4 just to be sure it's working properly. I've read in a few places that those who updated a while ago and experienced the issues decided to try it again and are having no problems anymore. That's just what I have read so I'm now trying it myself. So far it's been fine. If I have any problems I'll be sure post and share my experience
    View
    5
    badabing2003
    badabing2003
    New Release:
    Sep 19, 2023 v5.8.0.0 release
    • Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.
    • Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.
    • For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.
    • Added a button to reboot to userspace fastboot (fastbootd).
    • Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)
    • When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.
    • On Linux, display a message when terminal app is not set and open shell feature is used.
    • For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.
    • Miscellaneous fixes and improvements.
    View
    4
    N
    nikola1970
    badabing2003 said:
    Not sure why you would need TWRP and flash alpha in TWRP, that instruction could be for a different phone.
    You should be able to flash alpha in fastboot.
    But in any case, if you want to follow that guide, than PF is no use for you, yes you can flash TWRP using PF, but you also could using fastboot, and then you still need to use TWRP to flash Magisk, and not use PF.

    When you're considering to replace some Magisk with some other Magisk (either an older on or a different flavor)
    Two things need to be updated.
    The manager application, which is easy
    And the boot partition (along with the data in /data/adb/magisk)
    You could delete everything in /data/adb/magisk while rooted with the current Magisk, and then uninstall Magsik app and flash stock boot. That will take you to a stock state, and then easily install the other Magisk and follow the rooting steps with it.
    You might ask, why would I need to do all that, can't I just replace Magisk Manager and install in place?
    Depending on the version of Magisk you're running, as soon as you uninstall the Manager, as stub might be installed again by the root portion, so installing a different flavor my end up being blocked / replaced.

    For that PF has a special feature.
    Go to settings and Enable Advanced Options and Offer Patch Methods.
    View attachment 6007183

    Next make sure you download to your PC the Magisk version that you want to install.
    Next select the stock boot in PF and hit the Patch button.
    You will be offered patch options like the following.
    View attachment 6007185

    Select the downloaded Magisk.
    What this will do is it will create a patch using the selected Magisk rather than the installed Magisk, without having to worry about it being installed or not.
    Uninstall Magisk Manager from the phone.
    Select the created Patch in PF and hit "Flash Boot" not Flash Pixel Phone.

    When the phone reboots you would be rooted with the new Magisk,
    Install it's Manager and you're done.
    Click to expand...
    Click to collapse

    Wow thank you so much for detailed reply, this will be helpful for me in the future.
    Yesterday i just uninstalled Magisk directly from the app, after that installed Alpha, then patched init_boot with app, and flashed directly from cmd.
    View
    4
    badabing2003
    badabing2003
    Jwtiyar said:
    i made an auto backup, now how i can restore modules? or its backing up only the magisk app?
    i was on a13 now on beta 5.3.
    Click to expand...
    Click to collapse
    This is backing up the stock boot image, if Magisk for whatever reasons hadn't.
    It is used by Magisk to restore stock boot image when you choose to uninstall.
    There are times when one is missing a backup, and this allows you to create one or upload one from your PC.
    It has nothing to do with Modules.
    beeshyams said:
    I must be blind.. Can you please point out from where you took the auto Backup?
    Click to expand...
    Click to collapse
    Magisk Backup button
    1694447253261.png
    View
  • 150
    badabing2003
    badabing2003

    PF_promo-banner_v4.png

    DESCRIPTION​

    As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.)
    PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence many of its features can be used on non Pixel devices as well. (YMMV).
    The executable is self contained and does not require Python™ to be installed on the system.

    Basic mode: Should suit most users. Some of the features in basic mode are:
    • Simple UI interface, click and go. No more command line, no more placing all files in one directory.
    • boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without manual steps) and perform upgrades without losing root.
      No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
      No more setting airplane mode and clearing storage to retain Safetynet passing.
    • Display details of boot.img (or init_boot.img for Pixel 7 or newer devices).
      • SHA1 checksum.
      • Origin (file it was extracted from).
      • Whether it is patched or not, and if it is patched.
        • What version of Magisk was used to patch it.
        • On what device it was patched.
        • Date of patching.
        • The SHA1 of the source boot.img file.
      • Option to Live boot from a choice of boot.img or patched image.
      • Flash just the boot / init_boot image.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Option to flash to inactive slot.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Device architecture.
      • Current installed firmware (build).
      • If it is rooted with Magisk.
      • Magisk version (Magisk Tools).
      • Magisk Manager version (the app).
      • List installed Magisk modules.
      • Connection mode (Adb | Fastboot | Sideload | Recovery).
      • Bootloader version.
      • Active slot.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable (official)
      • beta (official)
      • canary (official)
      • debug (official)
      • alpha
      • delta
      • special build that disables modules, used to recover from bootloops due to bad module(s) when safe mode does not work.
    • Magisk Backup Manager, screenshot.
      • 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.
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK (an app) file from the computer onto the device.
    • Advanced features are hidden to keep the interface simple and easy to follow.
    • A lot of checks and validations for smooth operation.
    • Automatic check for program updates.
    • Package (Application) Manager, screenshot:
      • Disable (Freeze)
      • Enable
      • Uninstall
      • Install APK
      • Download APK
      • Multi-Select
      • Show Package Details.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • The ability to flash custom ROM (with or without patching boot.img)
    • Option to flash to both slots.
    • Option to flash to inactive slot.
    • Options to disable verity and or verification.
    • Ability to change the active slot.
    • Ability to live boot to custom boot.img (temporary root).
    • Ability to boot to recovery.
    • Ability to flash custom image: boot, recovery, radio, kernel, ...
    • Ability to sideload an image.
    • Lock / Unlock bootloader.
    • Option to gain temporary root (good for testing or checking things out).
    • SOS Disable Magisk modules to get out of bootloop (experimental).

    Prerequisites​

    Installation​

    PixelFlasher doesn't have to be installed, just double-click it and it'll start.
    Check the releases section for downloads.

    Supported platforms​

    • Windows
    • MacOSX
    • Linux

    ​

    Usage​

    Basic Mode

    1. First thing to do is select Android™ Platform Tools, if Android™ Platform Tools is already in your PATH environment, the application will detect it and pre-populate it.
      Otherwise you'd have to select where it is installed.
      You can download the lastest Android™ Platform Tools by clicking the Image of link next to it.
      If you have multiple versions, you can select another version, although it is best to always use the most recent version (The selected version will be identified and displayed.)
    2. Hit the Scan button to detect connected devices, the application will detect all connected devices
      (in adb, fastboot, sideload, recovery modes) and populate the combo box (2).
    3. Select your device from the list in the combo box. The following information about the connected device is displayed.
      • (1st field) Rooted devices will be identified with a checkmark ✓. Note: If you want PixelFlasher to detect root, or automatically use Magisk to patch boot.img, you need to grant root permissions to shell in Magisk.
        Image of shell root access
      • (1st field) Non-Rooted devices will be identified with a ✗.
      • (1st field) Devices in fastboot mode will be identified with a ? (in fastboot mode, root status cannot be determined).
      • (2nd field) (adb), (f.b), (sid) or (rec) to indicate connection mode adb / fastboot / sideload / recovery.
      • (3rd field) Device ID.
      • (4th field) Device hardware.
      • (5th field) Current running firmware (in fastboot mode current firmware cannot be determined).
    4. Next select the factory or full OTA zip file (don't unzip), the application will recognize the phone model from the image name and validate the SHA-256 checksum.
      You can download factory images by clicking the Image of link next to it. You can download full OTA images from here.
      Note: Because both firmware package and full OTA are complete images, you can upgrade to any newer version without worrying about jumping versions (downgrades might work, but are not recommended).
    5. Process the factory image. PixelFlasher will extract boot.img (or init_boot.img for Pixel 7 or newer devices) file from the factory image and populate it in the list below (5).
    6. Select boot.img (or init_boot.img for Pixel 7 or newer devices) from the list, the selected file can be patched (6), or flashed (10).
    7. Optional: Select this option if you want to patch the boot.img (or init_boot.img for Pixel 7 or newer devices) with Magisk. If Magisk is not already installed on your phone, PixelFlasher will install it for you. Your phone does not need to be rooted to create a patched file. This would be the typical choice for monthly updates.
      This option will allow updating the phone without losing root (not even temporarily).
      Note: See note above for granting root permissions to shell.
      Whether the phone is rooted or not, the whole process is without any manual step.
    8. If you want to flash (10) a patched boot.img (or init_boot.img for Pixel 7 or newer devices) select the newly added entry.
      The following details are listed.
      • Image of patched-boot Indicates that the selection is patched.
      • SHA1 is (shortened for display only) sha1 of boot.img (or init_boot.img for Pixel 7 or newer devices)
      • Source SHA1 (shortened for display only) SHA1 of source boot.img extracted from the image (This should be the same as SHA1 of an unpatched boot.img)
      • Package Fingerprint is just the filename portion of the image (without the extension).
      • Patched with Magisk indicates the version of Magisk used to patch the image (if applicable).
      • Patched Method indicates what method PixelFlasher used to create a patch (possible options: root, app, uiautomator, manual)
      • Patched on Device indicates the device model that performed the patching. You should always use patched images that match the model of the device that it will be flashed on.
      • Date is the either the date the boot.img was extracted, or the date it was patched.
      • Package Path indicates the file from which boot.img (or init_boot.img for Pixel 7 or newer devices) was extracted.
    9. Select the Flash Mode
      • If factory firmware is selected in step 4:
        • Keep Data: In this mode -w flag is removed from the flash scripts so that data is not wiped. This is commonly known as dirty flashing.
        • WIPE all data: As the text suggests, this will wipe your data, use it with caution!
          If this mode is selected PixelFlasher will ask for confirmation during the flashing phase.
        • Dry Run: In this mode, the phone will reboot to bootloader, and then mimic the flash actions (i.e. reboot into bootloader) without actually flashing anything (it prints to the console the steps it would have performed if dry run was not chosen). This is handy for testing to check if the PixelFlasher properly is able to control fastboot commands.
      • If full OTA image is selected in step 4:
        • Full OTA: Will flash full OTA image in sideload mode. Features of this mode:
          • This will always flash to inactive slot similar to how OTA updates happen on the phone.
          • If something goes wrong during flashing, the active flash is uneffected and the phone boots back to active functional slot.
          • If you flash to both slots (ie flash twice in a row) then both slots would be bootable.
          • Your phone's bootloader does not have to be unlocked to be able to flash full OTA image (stock boot only).
    10. Optional: Open Magisk Modules Manager and disable (uncheck) modules known to cause issues during upgrades (the below list has never caused issues for me, so I keep them enabled YMMV).
    11. Flash Pixel Phone This is the final step, to actually flash the phone in the selected Flash Mode.
      Note: Unlike the previous versions of the PixelFlasher, all the options are dynamic, i.e. depending on what you select before clicking the Flash button, there is no more concept of prepared package. PixelFlasher will first present you the selected options and ask for your confirmation if you want to proceed with flashing.

    Expert Mode
    To enable the export mode use the File Menu | Advanced Configuration and select Enable Advanced Options Image of PixelFlasher GUI
    Image of PixelFlasher GUI

    In this mode the following additional options are exposed (green bounding boxes), below notes are more for enumeration than a guide, as they should be trivial and obvious to an expert.

    1. Option to Change the Active Slot (the inactive slot is automatically selected).
      Option to reboot to Recovery.
    2. Options to Lock / Unlock bootloader, Option to disable Magisk modules when bootlooping.
    3. Apply Custom ROM. This replaces the factory ROM image with the selected file.
      PixelFlasher extracts boot.img from the ROM image and displays below for selection or patching. Please make sure to read the documentation of the chosen ROM, as each custom ROM instructions could be different.
      To be clear, this is what PixelFlasher does internally when this mode is selected, please understand it, and don't use it if the selected ROM guide does not fit the bill. You've been warned!
      • Keeps stock bootloader and radio images.
      • Replaces the stock ROM image with the selected custom ROM image.
      • Flashes in the chosen Flash Mode just like a stock image, i.e. bootloader, custom ROM and radio images in the original order that they were in the stock firmware.
      • Patching boot.img can be performed if the option is selected. You can select any of the listed boot.img.
      • Flash Mode is similar to basic flash mode described above in step 7.
    4. Custom Flash. select this to switch from flashing a Factory Image to flashing a single file.
    5. Browse to select a a valid image file (.img or .zip). Or select a boot.img from the list above and click on the paste button to paste the selected boot.img into the file selection. Choose the dropdown to select image type.
      • boot (can be flashed to Live or boot) - Expected file type .img
      • bootloader - Expected file type .img
      • dtbo - Expected file type .img
      • product - Expected file type .img
      • radio - Expected file type .img
      • recovery - Expected file type .img
      • super_empty - Expected file type .img
      • system - Expected file type .img
      • system_ext - Expected file type .img
      • system_other - Expected file type .img
      • vbmeta - Expected file type .img
      • vbmeta_system - Expected file type .img
      • vbmeta_vendor - Expected file type .img
      • vendor - Expected file type .img
      • vendor_boot - Expected file type .img
      • vendor_dlkm (the device will be put into fastbootd mode during this operation) - Expected file type .img
      • image - Expected file type .zip
      • SIDELOAD - Expected file type .zip
        Select the appropriate flash options. Note: For Tensor devices (Pixel 6 or newer devices) When Flash to both slots option is selected, Pixelflasher flashes each slot individually to overcome a Google bug that fails with the option --slot=all

    Credits​

    • First and foremost Magisk by John Wu which made rooting Pixel™ phones possible, without it none of this would have mattered.
    • Big thanks to [ryder203], [t-ryder] for his valuable ideas, feedback and testing. Your contributions are very much appreciated.
    • [Homeboy76] and [v0latyle] at xda for their excellent guides [here and here] on Pixel™ series phones. This program could not have been possible without their easy to follow guides.
      I strongly encourage all beginners to follow those guides rather than use this program, it is important to understand the basic steps involved before diving into one click tools or advanced tasks.
    • Marcel Stör's nodemcu-pyflasher source code which jump started my introduction to wxPython and eventually this program.
    • JackMcKew for pyinstaller Github Actions.
    • Endless counts of xda members and their posts that tirelessly answer questions and share tools. Too many to enumerate.

    Disclaimer​

    Code: 
    *******************************************************************************
PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE USING THIS PROGRAM
AND/OR ATTEMPTING ANY MODIFICATIONS ON YOUR DEVICE.
THIS PROGRAM ASSUMES THAT YOU ALREADY KNOW HOW TO AND HAVE ALREADY UNLOCKED
YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, AND KNOW HOW TO USE ANDROID SDK
PLATFORM-TOOLS, ETC.
THIS TOOL IS SIMPLY MY QUICK WAY OF UPDATING THE FIRMWARE WHILE ROOTED WITH
MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE.
MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY
IF YOU LOSE YOUR DATA OR BRICK YOUR DEVICE. THE TOOL I SHARE HAVE WORKED FOR ME,
BUT THAT DOESN'T MEAN THAT YOU MAY NOT RUN INTO PROBLEMS. **BACKUP YOUR DATA.**
*******************************************************************************

    No Donation
    I've been asked quite few times about donation, (here, here ... just to list a few).
    I'll put it here so that my stance is clear.
    This program will remain totally free, ad free, even donation free, it's my way to give a little back to the community that has given me years of support and joy.

    You can contribute by helping the next newcomer to learn the ropes and navigate through the maze of information.
    View
    14
    badabing2003
    badabing2003
    New Release:
    July 03, 2023 v5.4.0.0 release
    • Add Pixel Fold (Felix)
    • Add sorting capability to boot list.
    • Add warning about Magisk a8c4a33e:26103
    • Improved auto-resize of boot columns.
    • Improved internal DB management.
    • Handle beta or similar words in the firmware name to not trigger hardware mismatch warning.
    • Improved tracking the origin of a patched image.
    • Display Kernel version as part of device details
    • Refresh package manager list when packages are updated to reflect the changes.
    • Miscellaneous other improvements.
    • Update Readme.
    View
    11
    badabing2003
    badabing2003
    Latest Release:
    Sep 19, 2023 v5.8.0.0 release
    • Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.
    • Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.
    • For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.
    • Added a button to reboot to userspace fastboot (fastbootd).
    • Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)
    • When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.
    • On Linux, display a message when terminal app is not set and open shell feature is used.
    • For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.
    • Miscellaneous fixes and improvements.

    Aug 15, 2023 v5.7.2.0 release

    • Regression Bug fix: Refresh UI to display / hide flash options after changing advanced settings.
    • Use Python 3.11 instead of 3.10
    Aug 13, 2023 v5.7.1.0 release
    • Print available memory when starting PixelFlasher.
    • Option to sacrifice speed in favor of using less memory (used when processing large firmware files, turn it on only if you run into out of memory errors).
    Aug 09, 2023 v5.7.0.0 release
    • Rework the settings window: code refactoring and bug fixes.
    • Bug Fix: In some cases log files were not saved.
    • Bug Fix: Custom font size changes were not always applied.
    • When getting device details, get battery details.
    • Don't set ASH_STANDALONE=1 when using busybox, it encounters selinux related issue.
    • Extra check to make sure the created patch is not zero bytes long.
    Aug 07, 2023 v5.6.0.0 release
    • Added configurable toolbar.
    • Added device controls buttons to the menu.
    • Added feature to Magisk Manager, ability to install modules from the PC.
    • After flashing OTA, detect if the slot switched as expected, if it didn't, skip patched boot flashing (if selected).
    • Added feature to Package Manager to be able to manage (add, remove, list) Magisk denylist.
    • Added export csv formatted package list feature.
    • When sanitizing DB, wipe write-ahead logs (WAL) for better privacy.
    • Under the hood optimizations.
    • Verity / Verification status check.
    • Counter in package manager.
    • Added a quick link to Android security and update bulletins.
    July 16, 2023 v5.5.1.1 release
    • #84, further UI improvements for smaller screens.
    • Better dark mode handling for MacOS and Linux.
    • #86, improved handling of space characters in paths.
    July 14, 2023 v5.5.1.0 release
    • Bug fix #85 Can't enable/disable Advanced option in v5.5.0
    • A little improvement #84 UI elements not optimized for monitors with low screen resolution
    July 13, 2023 v5.5.0.0 release
    • Added a patch method Other Magisk App to be able to select any Magisk apk and use it to create a patch without installing Magisk, handy when a patch needs to be created with an older version of Magisk (in case the current version has issues) and Magisk daemon gets in the way and replaces the older version with a stub.
    • UI improvements
    • Added Kill Application in Package Manager.
    • Added Clear Application Data in Package Manager.
    • Now that Full OTA flashing is the preferred method, added a direct link to the device's full OTA download page from Google.
    • While flashing, disable the Flash Pixel Phone button to avoid accidental clicking.
    • Improved root detection.
    • Bug fixes and other improvements.
    July 03, 2023 v5.4.0.0 release
    • Add Pixel Fold (Felix)
    • Add sorting capability to boot list.
    • Add warning about Magisk a8c4a33e:26103
    • Improved auto-resize of boot columns.
    • Improved internal DB management.
    • Handle beta or similar words in the firmware name to not trigger hardware mismatch warning.
    • Improved tracking the origin of a patched image.
    • Display Kernel version as part of device details
    • Refresh package manager list when packages are updated to reflect the changes.
    • Miscellaneous other improvements.
    • Update Readme.
    June 23, 2023 v5.3.3.0 release
    • #79 Bug-fix: Package Manager column stays unsorted when filtered.
    • Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.
    • Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3
    • Package manager bug fixes and improvements.
    June 21, 2023 v5.3.2.0 release
    • Added support for Pixel tablet (tangorpro).
      For future devices, fixed a bug to auto detect init_boot partition and flash init_boot instead of boot even if the device is newer than the PixelFlasher and is not in PixelFlasher's list.
    • Disable Patch buttons if device is not in adb mode.
    • Reboot to system after lock / unlock bootloader if No Reboot option is not selected.
    • Increase sleep after reboots to various modes to assure that slow devices have time to be detected.
    • Updated Readme and screenshots.
    • Minor improvements and bug fixes.
    June 16, 2023 v5.3.1.2 release
    • Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.
    • Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.
    • Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.
    • Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.
    • Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
    June 06, 2023 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.
    June 03, 2023 v5.2.0.2 release
    • #76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
    June 01, 2023 v5.2.0.1 release
    • Bug fix #78 Error when opening a shell console on Linux / Mac
    June 01, 2023 v5.2.0.0 release
    • Update build workflows
    • Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
    • Added rules engine code to better / easier management of the UI widgets enabling / disabling.
    • Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
    • Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
    May 25, 2023 v5.1.0.2 release
    • Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
    v5.1.0.1 release notes:
    • Exception handling when device is not in the listed Pixel devices.
    v5.1.0.0 release notes:
    • Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3
    • Temp workaround to avoid selecting root method patching when Magisk Delta is detected.
    • Nicer looking / clearer manual patching dialog.
    • 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.
    • Boot image list box now displays the applied PixelFlasher patch method.
    • Auto-resize boot image list box columns for better readability.
    • Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.
    • #77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).
    • Bug fixes and improvements.
    May 21, 2023 v5.0.1.0 release
    • Added workflow for building on MacOS 13.
    • ComboBox behavior on Mac is different than Windows, make adjustments.
    • Ability to set PixelFlasher working directory (no UI).
    • Speed up startup.
    • Popup device selection after Wifi adb connect.
    • Clear Device list after adb kill-server.
    May 19, 2023 v5.0.0.1 release
    • #75 Bug fix, when device is in bootloader, type error.https://github.com/badabing2005/PixelFlasher/issues/74
    • #74 Added Support for Pixel 7a (lynx)
    • Configuration option to define the file manager to use on Linux (default: Nautilus)
    • Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
    • Support for additional types of Factory / ROM files.
    • Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
    • New advanced option, ability to choose the patching method (with recommendations).
    • Added Recovery Image patching option.
    • Advanced option to enable the use of busybox shell (default off).
    • Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
    • Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
    • Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
    • Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
    • #66, when checking the patched files internal SHA1, provide a confidence rating.
    • Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
    • Added fastbootd testing to Dry Run.
    • Added Github actions to build all the targets on Github.
    • Code refactoring, bug fixes and improvements
    Apr 30, 2023 v4.10.0 release
    • Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.
    • Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)
    • Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.
    • Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.
    • Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
    Apr 27, 2023 v4.9.0 release
    • Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).
    • Support for recognizing Lineage firmware and extracting / patching boot.
    • Display 32 bit capabilities of the device.
    • Utilize New Magisk 26.x flags as needed (patch support for more devices).
    • Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.
    • Partition Manager can now list the partitions even if the devices is not rooted.
    • Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).
    • Added Open Folder button to open a file browser to the directory of the selected boot image.
    • Added Reboot to Download button (Odin mode).
    • Added Reboot to Safe Mode button.
    • Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.
    • Various additional validation checks.
    • Bug fixes and other improvements.
    Apr 10, 2023 v4.8.2 release
    • Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
    • Display USNF related flag values when selecting a device.
    • Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
    • Link to download Google USB Driver is added in the help menu.
    • Added more visual troubleshooting event flows.
    • Install APK now defaults to Non Market.
    • Added Install APK cancel option.
    • You can now select an app in package manager and right click to launch it on the phone.
    • Minor bug fixes and other improvements.
    Mar 14, 2023 v4.8.1 release
    • #47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
    • Added more visual troubleshooting event flows.
    • Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
    • Improved support.zip redactions.
    • Added Support.Zip generator button on the Main screen.
    • APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
    • Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
    • Bug fixes and other improvements.
    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.
    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.
    • #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.
    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.
    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.
    Nov 09, 2022 v4.4.0 release
    • New feature: Font and Font size should be configurable by the user #33
    • New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
      Handy to access a device remotely.
      Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
      I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
    • Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
    • Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
    • Minor UI Improvements
    • If Magisk does not create a backup attempt to trigger Magisk to create one.
    • Update readme to include Pixel 7 / 7P specific info.
    Oct 27, 2022 v4.3.1.0 release
    • Bug Fix: Magisk modules not listed on MacOS / Linux
    Oct 16, 2022 v4.3.0.1 release
    • Bug fix: #30 Error during firmware processing file extraction phase.
    • PixelFlasher-Linux is now labeled PixelFlasher-Ubuntu (It is built on Ubuntu which is not compatible with all Linux flavors. Even though PixelFlasher-Kali is more compatible, it is still not a one size fits all solution.)
    Oct 15, 2022 v4.3.0 release
    • New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.
    • Bug fix: Generating support.zip file was modifying the main db file unnecessarily.
    • Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.
    • Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.
    Oct 13, 2022 v4.2.0 pre-release
    • Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
    • Added Pixel 7 / 7p partitions flashing options to custom flash.
    • Improved patching process using boot_patch, add more patch file validations.
    • Check for Magisk backup and trigger Magisk to backup if missing.
    • Add more logging messages for troubleshooting.
    • Code optimization / improvements.
    • Bug Fix #28 Error when opening download link without a device selected.
    • Added set_version script to easily set the product version.
    • Print path of the selected boot to console, for easy copy / paste.
    Oct 05, 2022 v4.1.4 release
    • Rooted Magisk patching will now automatically back up stock-boot.img (more to come).
    • Bug Fix #27, handle version exception.
    Oct 05, 2022 v4.1.3 release
    • Bug Fix: Extract Magisk Manager version properly.
    Oct 04, 2022 v4.1.2 release
    • include busybox binaries for different Android architectures (arm64-v8a, armeabi-v7a, x86_64, x86)
    • don't use hidden Magisk for patching, as it is a stub only.
    Oct 03, 2022 v4.1.1. release
    • Bug Fix: Bundle busybox with PixelFlasher to be used for unzipping Magisk.
    • Bug Fix #25, use the Magisk Manager version number instead of Rooted Magisk version number.
    • Cosmetic changes and a bit more logging.
    Oct 03, 2022 v4.1.0 pre-release
    • Patching is now fully automatic with or without root.
      PixelFlasher uses installed Magisk Manager binaries to create a patch (root binaries are only used if Magisk Manager is not available / accessible)
      UIAutomator no longer necessary, neither asking the user to manually patch and click ok when done.
    • Added an option to set a hidden Magisk package name so that PixelFlasher can find the Magisk and use it, the user still has a choice to use root binaries.
    • Speed improvements for device property reading.
    • Speed improvements for Magisk modules reading.

      NOTICE:
      I'm marking this release as pre-release because I just found out that unzip is not normally available on the phone, which this new patching mechanism uses.
      On my test phones they were available.
      Unless you have unzip on your phone, you should avoid using this version.
      Sorry about this oversight.
    Sep 25, 2022 v4.0.0 pre-release
    • New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
      See Patching flow chart for details.
    • New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
    • New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
    • New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
    • New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
      Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).
    • New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
    • New spinner to indicate PixelFlasher activity.
    • Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
    • PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
      This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.
    • PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
      This is just an extra validation.
    • Code cleanup / refactoring, adding more validations and exception handling.
    • Print debug details when encountering non compliant Magisk modules.
    • Firmware link now takes you to the device's download page instead of just the general download page.
    • To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
    • Allow sideload even if bootloader is locked.
    Sep 04, 2022 v3.7.0 release
    • New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
    • New Feature: Install compatible apk file onto the device from PixelFlasher menu.
    • Check Android Platform Tools version and warn if it is old.
    • Block flashing when stock flash_all.bat file is tampered with.
    • Don't bother with flashing if bootloader is locked.
    • More validations and exceptions handling.
    • Improved logging.
    Aug 24, 2022 v3.6.0 release
    • When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
    • Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
    • Improved tooltips.
    Aug 21, 2022 v3.5.1 release
    • Fix: Incorrect warning is displayed when Flash on both slots is selected.
    • The contents of the generated flash-phone.bat file will now be displayed on console even if verbose option is not selected, this helps the user know exactly what commands would be executed before clicking the OK button.
    Aug 19, 2022 v3.5.0 release
    • Add support for fastboot --force flag (to help fix partition issues, caution it will wipe data) see this.
    • Split image flashing to all slots into two separate single slot flashing to bypass a Google bug on Pixel 6* devices, see this by @Namelesswonder
    July 18, 2022 v3.4.0 release
    • Improvements to the boot extraction / categorization.
    • Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.
    • Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
    June 26, 2022 v3.3.5 release
    • Fix Lock / Unlock bootloader buttons being reversed.
    June 12, 2022 v3.3.4 release
    • Bug fix on MacOS / Linux
    • Improved notice message about Fastboot process.
    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.
    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.
    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.
    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
    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.
    May 02, 2022 v3.1.1 release
    • Handle UTF-8 Encoding.
    May 02, 2022 v3.1.0 release
    • Fixed a missing step in the final flashing of boot.img
    • Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
    • Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
    • Made the boot.img management delete function more extensive.
    • I flashed my phone with the May drop using this version.
    April 30, 2022 v3.0.0 release
    • New workflow, no more package preparation, select options and flash all dynamic.
    • boot.img caching and management UI with details about the state of boot.img files.
    • Faster as there is no more need to zip a package.
    • Other optimizations and improvements.
    • Update documentation.
    April 20, 2022 v2.4.1 release
    • Bug Fixes: Error message during flashing, introduced by code reshuffle.
    • It turns out that some Magisk Modules don't set the id, which was expected to be present, which caused Magisk module management screen not to display.
    April 19, 2022 v2.4.0 release
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade.
    • Autoscroll the console.
    • Code cleanup.
    April 17, 2022 v2.3.0 release
    • Optional automatic check for updates feature.
    • Added help menu links to:
      - Report an issue
      - Feature Request
      - PixelFlasher Project Page
      - PixelFlasher Community (Forum)
      - Homeboy76's Guide
      - V0latyle's Guide
      - Open Configuration Folder
      - Check for New Version
    • Icons for menu items.
    • Link to download Pixel Firmware.
    • Link to download Android Platform Tools.
    • Unlock Bootloader.
    • Lock Bootloader.
    • SOS (experimental) - disable Magisk modules to get out of bootloop.
    • Additional flashing options:
      - product
      - system
      - system_ext
      - system_other
      - vbmeta_system
      - vbmeta_vendor
    • Added sideload flashing option.
    • Updated documentation.
    • Further improved console messages for troubleshooting.
    • Linux build using Github Actions.
    • Manual build for Kali Linux.
    April 11, 2022 v2.2.2 release
    • Linux support.
    • Remember last window position.
    • List Magisk modules, when Magisk is detected.
    • Added fastboot verbose option.
    • Added more checks and validations.
    • Added more details when errors are encountered.
    • Cleaner message box (better formatting).
    • Notice to the user in case fastboot drivers are not setup properly.
    • More plumbing work for the new upcoming workflow.
    • Add notes on how to build the Linux version.
    April 06, 2022 v2.1.0 release
    • Setup dedicated profile directory.
    • Put logs in the profile directory and maintain log history.
    • Plumbing for Linux support (just the flashing part is left to do).
    • Plumbing for new workflow.
    • Bugfix to handle name conflict in ROM filename.
    • Various minor improvements.
    • Update documentation.
    April 03, 2022 v2.0.1.0-pre release.
    • Major refactoring
    • Added Advanced (Expert) mode UI.
    • Basic mode keeps UI simple and hides expert features.
    • Support for setting active slot.
    • Reboot options (recovery, system, bootloader)
    • Moved custom ROM options to expert mode.
    • Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
    • Moved flashing to both slots, disabling verity / verification to expert mode.
    • Many other improvements, validations and checks.
    • Updated documentation.
    March 24, 2022 v1.2.0.1-alpha release.
    • Added Advanced Configuration menu which unlocks advanced features such as:
      - Flashing to both slots
      - Disabling Verity
      - Disabling Verification
      - (More features to come)
    • The UI will now display the chosen Android Platform Tool's version.
    • Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
    • Stability fixes.
    March 22, 2022 v1.1.5-alpha release.
    • Some users were having issues with 7zip, add 7z.dll to the bundle.
    • Add fallback mechanism to use python libraries for unzipping when 7zip fails (it would be slower)
    March 22, 2022 v1.1.4-alpha release.
    • Bug Fix: Handle space characters in paths.
    March 17, 2022 v1.1.3-alpha release.
    • Visual indicator if the phone is root and Magisk Tools is found.
    • Bug Fix: KeyError 'flash_vbmeta'
    March 17, 2022 v1.1.0-alpha release.
    Changelog
    • 10x speed improvement for full package creation, down from 180 seconds to 18 seconds.
    • Bug Fix: When using patch option with custom ROM, the boot.img of the custom ROM is now correctly patched.
    • Add support for flashing vbmeta (experimental) with or without disabling verity and or verification. (This is currently only supported through preferences file)
    View
    10
    badabing2003
    badabing2003
    Device specific support threads:

    Troubleshooting:
    • See this post.
    • Generate Sanitized support.zip file (File Menu) and submit that with your report.
    View
    9
    badabing2003
    badabing2003
    New Release:
    Aug 07, 2023 v5.6.0.0 release
    • Added configurable toolbar.
    • Added device controls buttons to the menu.
    • Added feature to Magisk Manager, ability to install modules from the PC.
    • After flashing OTA, detect if the slot switched as expected, if it didn't, skip patched boot flashing (if selected).
    • Added feature to Package Manager to be able to manage (add, remove, list) Magisk denylist.
    • Added export csv formatted package list feature.
    • When sanitizing DB, wipe write-ahead logs (WAL) for better privacy.
    • Under the hood optimizations.
    • Verity / Verification status check.
    • Counter in package manager.
    • Added a quick link to Android security and update bulletins.
    View

New posts