Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

Search This thread

AllusionPDX

Senior Member
Jan 10, 2012
138
27
Google Pixel 7 Pro
So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
 

JakeDHS07

Senior Member
So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
Those options are already part of the application if you are using Expert mode 👍
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,617
1,949
So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
Like @JakeDHS07 said, these options are already in PixelFlasher.

Don't take this the wrong way, but if you just came back over from iPhone and admittedly are a bit out of date, you shouldn't be asking for features without understanding what exactly you're asking for.
For example you say,

if you read the post on the krisakura kernel ...

And you expect me to hunt for Krisakura Kernel post and learn the process? For something you're not willing to understand? You haven't even linked the post.
I'm sorry but this only tells me that you don't want to put any effort in helping yourself, you just expect it to be delivered on a platter.

I suggest the following.
If you want to flash a Krisakura Kernel, go over that post, understand the steps / the process, apply it to your phone, if you have any problems regarding that, ask them in that forum.
Repeat this few times, then identify the pain points, the parts where you think if it were automated would save you time and be less error prone.
Come back and explain your workflow, and describe how adding such and such feature into PF would ease that pain point and I would seriously consider it if it is feasible.

This is from the OP in the main thread.

1668803698944.png


Tools like PF could be used by the following types of users.
  • People who know the process, know exactly what goes into modding the phone manually, and want to save time and effort repeating the same tedious process each and every time they want to flash / mod.
    And if anything goes wrong, they know how to recover, or ask pertinent contextual questions.
    This is the main audience of PF, people in this group not only are capable of understanding the steps, but are also in position to help others.
  • People new to the game, that find the initial learning curve steep to overcome, but are willing to learn, comparing the console output to the manual steps outlined in the guides and trying to make sense of the workflow / steps and learning along the way. People in this group would eventually become proficient and graduate to the first group.
  • People who don't care about learning, they are merely lazy leeches that just want things to be done for them. PF is not intended for this type of users, if I wanted to attract this group I would have charged for the program.
  • People who are incapable of learning / following guides, although I don't believe that this group exists at XDA, but if there are rare few of them, then I respectfully suggest that modding is not for them.
 
Thanks for chiming in.
This is more targeted to @AllusionPDX and others who request such auxiliary features.

A stated previously, I don't have the necessary understanding of the process / tools involved in achieving ... whatever (I say whatever because honestly I don't even know what we're doing, there is a mention of Powerhint which apparently is a Magisk module, so why PF's Magisk Module manager is not used to enable / disable it? and if it is used, what exactly it is missing?)

Yeah I can research, dig and learn, which would require my time and effort, which is not in abundance.
That is why I asked for manual steps.

I see mention of "just restore from backup instead of having to re-configure each time"
What am I backing up? what are the backups? in what format? where are they persisted? Are they already previously made or PF has to create them? at what point in the process the backup is made / restored?
You can see where this is going.

"Kernel Flashing Apps like EXKM," which suggests that there are other tools, why this tool and not others? Questions about limitations / and usefulness to others.

Automating / programming something requires detailed understanding of the precise process of all possible paths.
I'm not against adding features that could help XDA members, if this is something doable and within the reasonable scope of PF's usage, however simply asking for such features without providing the required details is not going to motivate me in looking into it.

Lastly, I don't intend to flash Kernels and experiment on my main driver, so even if I'm inclined to add such feature, I wouldn't be able to test it and would require the commitment of the requester not only to provide the details I ask, but also to do the testing, which of course comes with risks.
Just my opinion, those aren't necessary. Magisk has to be set up before it can flash any mods. And Kernels are just as easy to flash with a Flash Manager, like EX, et al.

Last night, I soft-bricked my phone flashing a Substratum Theme (Still not sure what happened) and had to do a Factory Reset, friggin lying in bed at 3AM, but once I did, came to my Computer, rebooted to Windows, started the Flash Tool and in 3 minutes, I was up and running.

Sadly, I hadn't done a Swift Backup or a Storage Backup in a week so I'm gonna lose some stuff and restoring thousands of pics is taking for-EVER, but the tool works perfectly as it is!
 
  • Sad
Reactions: badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,617
1,949
Just my opinion, those aren't necessary. Magisk has to be set up before it can flash any mods. And Kernels are just as easy to flash with a Flash Manager, like EX, et al.

Last night, I soft-bricked my phone flashing a Substratum Theme (Still not sure what happened) and had to do a Factory Reset, friggin lying in bed at 3AM, but once I did, came to my Computer, rebooted to Windows, started the Flash Tool and in 3 minutes, I was up and running.

Sadly, I hadn't done a Swift Backup or a Storage Backup in a week so I'm gonna lose some stuff and restoring thousands of pics is taking for-EVER, but the tool works perfectly as it is!
Sorry to hear about your troubles, and happy to learn that the tool is doing its job well.
Thanks
 
  • Like
Reactions: HipKat
Sorry to hear about your troubles, and happy to learn that the tool is doing its job well.
Thanks
One thing I just thought of. I HOPE I didn't just waste a few hours restoring things because I had Don't Wipe selected with disable Verity and Verification, coming from a Factory Rest. Gonna check that real quick....

EDIT: Nope, starting over......
Lessons learned
 
Last edited:
  • Sad
Reactions: badabing2003

chaos193

Member
Jul 5, 2011
16
9
Haven't rooted my phone since 2014, a Oneplus One. Coming back to this I was very reluctant to root my phone given all the steps needed. Tried using PixelFlasher. On first try, unlocked the booloader, patched the init.boot using Magisk, gain root all while disabling verity and verification. Not once a bootloop happened. Dev you have no idea how much I appreciate this tool. Thanks a lot.
 
Haven't rooted my phone since 2014, a Oneplus One. Coming back to this I was very reluctant to root my phone given all the steps needed. Tried using PixelFlasher. On first try, unlocked the booloader, patched the init.boot using Magisk, gain root all while disabling verity and verification. Not once a bootloop happened. Dev you have no idea how much I appreciate this tool. Thanks a lot.
I was in the same boat and came away with the same sense of gratitude!
 

Light_Wing

Senior Member
Has anyone been using PF to successfully flash custom roms? I've heard there's some available "out in the wild" :cool:
yes, if GrapheneOS is considered custom rom :)

the GraphineOS docs say to lock the bootloader after following their steps see here and i tried it (before trying to add magisk to it...) and it changes the message about unlocked bootloader to something about booting a different os (then the original).
now after installing it with magisk, i was about to lock it again, but got the big caps lock WARNING to NEVER EVER lock it without returning to or firmware... or it will BRICK.

now im hesitant to do it, but already did it once before i rooted (with the custom rom = GrapheneOS)

anyone know if this will for sure brick, or the warning is just in case?
and if its for sure, then why did it not break when it was without magisk?
 

EtherealRemnant

Senior Member
yes, if GrapheneOS is considered custom rom :)

the GraphineOS docs say to lock the bootloader after following their steps see here and i tried it (before trying to add magisk to it...) and it changes the message about unlocked bootloader to something about booting a different os (then the original).
now after installing it with magisk, i was about to lock it again, but got the big caps lock WARNING to NEVER EVER lock it without returning to or firmware... or it will BRICK.

now im hesitant to do it, but already did it once before i rooted (with the custom rom = GrapheneOS)

anyone know if this will for sure brick, or the warning is just in case?
and if its for sure, then why did it not break when it was without magisk?
You cannot re-lock the bootloader with Magisk as it will instantly fail AVB verification.
 

Light_Wing

Senior Member
You cannot re-lock the bootloader with Magisk as it will instantly fail AVB verification.
so it just wont let me lock it?
if so ill try...

i also found a post about building your own GrapheneOS with Magisk, and re signing, then locking bootloader. and it tells you to just to make sure not to disable OEM unlocking later in dev settings, in case something happens due to root, as long as its open you can recover from it, and if not then thats when you get a hard brick (this is what i understood, maybe im wrong)

here is the link to that post
 

EtherealRemnant

Senior Member
so it just wont let me lock it?
if so ill try...

i also found a post about building your own GrapheneOS with Magisk, and re signing, then locking bootloader. and it tells you to just to make sure not to disable OEM unlocking later in dev settings, in case something happens due to root, as long as its open you can recover from it, and if not then thats when you get a hard brick (this is what i understood, maybe im wrong)

here is the link to that post
This is a really dangerous thing to attempt to do with a device that doesn't have a low level recovery tool like OnePlus does with the MSM Tool. When you re-lock the bootloader, it automatically untoggles that switch as it factory resets the phone, so if something goes wrong, there's no way to recover as usually these bricks won't let you get into recovery, just fastboot, and you require an unlocked bootloader to flash with fastboot.
 

EtherealRemnant

Senior Member
Agreed. It's a solid rule to never relock your Bootloader until you're ready to trade your device in. Especially if it's just to remove a stupid warning on a reboot
Even then, it's best to use the Android Flash Tool to do this, to make sure you actually are back to full stock so you don't brick anyway.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,617
1,949
New Release:
Dec 04, 2022 v4.5.0 release
  • New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
  • New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
  • Use latest Python updated packages.
  • Ubuntu 22.04 support.
  • Miscellaneous improvements.
 

Top Liked Posts

  • 6
    Why the heck did I wait so long to use this? This is the easiest way to update by far. Thanks much.
    2
    Ok, so I updated using PF, rebooted and made sure everthing worked great. So I figured i try to get inactive up to same version. Same procedure as before. selected patched init_boot.img and checked flash to inactive slot. Flash went well no errors. Rebooted phone and after colorful google boot text phone goes black and nothing. Manually reboot and same thing. rebooted again and switched slots, phone boots to colorful Google text and goes black. Then decided to reflash with non-root firmware. Im back on Slot A and everything is working. Flashed patch init-boot.img and back to root.
    So any idea why after successfully flashing latest firmware and then flashed same firmware to inactive slot and doesn't boot?
    You started with the device on slot a and January build
    You updated to February build, to active slot with the following options (why are you disabling verity / verification, even though that is not an issue)
    Code:
    Custom Flash Options:   True
    Disable Verity:         True
    Disable Verification:   True
    Flash Both Slots:       False
    Force:                  False
    Verbose Fastboot:       False
    Temporary Root:         False
    Flash To Inactive Slot: False

    Everything went well and you booted to slot a February build
    Code:
    Selected Device on 2023-02-06 20:12:25:
        Device ID:                       REDACTED
        Device Model:                    cheetah
        Device Active Slot:              a
        Device Mode:                     adb
        Device is Rooted:                True
        Device Build:                    TQ1A.230205.001.D2
        Device API Level:                33
        Device Architecture:             arm64-v8a
        Device Bootloader Version:       cloudripper-1.0-9288096
        Magisk Manager Version:         
            Checked for Package:         com.topjohnwu.magisk
        Magisk Version:                  25.2:25200
        Magisk Config SHA1:             
        Magisk Modules:
            AOSP Mods (Full version)            enabled   2.4.1
            Powerhint_Cheetah                   enabled   v4
            Themer                              enabled   1.2.3B2
            ViPER4Android Reverse Engineered    enabled   v0.1.0
            JamesDSP Manager                    enabled   v4.6 (8-4-2022)
            Audio Modification Library          enabled   v4.2
            Font Manager                        enabled   v5.6.45
            Systemless Hosts                    enabled   1.0
            Universal SafetyNet Fix             enabled   v2.4.0
            Zygisk - LSPosed                    enabled   v1.8.6 (6712)

    Then you decided to flash again this time to inactive slot (ie b) with the following options
    Code:
    Custom Flash Options:   True
    Disable Verity:         True
    Disable Verification:   True
    Flash Both Slots:       False
    Force:                  False
    Verbose Fastboot:       False
    Temporary Root:         False
    Flash To Inactive Slot: True

    Again everything went well and the system booted properly to slot b
    Code:
    Selected Device on 2023-02-06 20:17:04:
        Device ID:                       REDACTED
        Device Model:                    cheetah
        Device Active Slot:              b
        Device Mode:                     adb
        Device is Rooted:                True
        Device Build:                    TQ1A.230205.001.D2
        Device API Level:                33
        Device Architecture:             arm64-v8a
        Device Bootloader Version:       cloudripper-1.0-9288096
        Magisk Manager Version:         
            Checked for Package:         com.topjohnwu.magisk
        Magisk Version:                  25.2:25200
        Magisk Config SHA1:             
        Magisk Modules:
            AOSP Mods (Full version)            enabled   2.4.1
            Powerhint_Cheetah                   enabled   v4
            Themer                              enabled   1.2.3B2
            ViPER4Android Reverse Engineered    enabled   v0.1.0
            JamesDSP Manager                    enabled   v4.6 (8-4-2022)
            Audio Modification Library          enabled   v4.2
            Font Manager                        enabled   v5.6.45
            Systemless Hosts                    enabled   1.0
            Universal SafetyNet Fix             enabled   v2.4.0
            Zygisk - LSPosed                    enabled   v1.8.6 (6712)

    Not sure why, but you tried to change the active slot to a again
    Code:
    Rebooting device REDACTED to bootloader ...
    Waiting 5 seconds ...
    Setting active slot to slot [a] for device 29141FDH3001H9 ...
    
    Selected Device on 2023-02-06 20:17:34:
        Device ID:                       REDACTED
        Device Model:                    cheetah
        Device Active Slot:              a
        Device Mode:                     f.b
        Device Unlocked:                 True

    Once b becomes active and bootable, a becomes unbootable, this is expected, only one slot is bootable, (see earlier posts if you're interested to know why this happens)
    Then while in bootloader mode, you switched to b, and flashed to inactive slot (that would be a)
    That worked, and you now you are on a.


    I would really like to be able to get the latest PF to work with Linux Miint, but cant get the pre-req Python setup. Any easy way to get this working? I guess the latest Mint still does not/wont have the req'd Python?
    Have you tried to use the published Kali build, and or Ubuntu 22.04 built?
    What happens? what errors do you get?
    What version of Mint do you have?
    Have you tried to build from source?


    Can i go back to January Patch from February?
    You can try, the worst that will happen is that it won't work and you will go back to February.
    I don't have much experience with reverting, I only attempted once to revert to an older firmware and it didn't work for me, but that doesn't mean that it won't work for you either.
    Others might chime in with their experiences.
    Curious why you want to go back
    1
    I only used PF once to root the phone when I first got it almost 4 months ago, and been updating/rooting using the Android Flash Tool and commands.

    I'm now wanting to update and retain root using PF, is the process different? Currently reading through the main thread and Github, and wondering if there's a beginner-friendly summary on how to do that.

    Edit: All good. Updated using PF, easy process. Thanks Dev.
    1
    Can i go back to January Patch from February?
    I've never had a problem going back to any firmware. Other than the time thaey added the anti-rollback to the pixel 6 on that one update one month which i cant remember which one it was. Other than that one time, I've always been able to roll back on all my Pixel phones.
  • 26
    New Release:
    Feb 05, 2023 v4.7.0 release
    • Added Magisk Backup Manager:
      • List all Magisk backups currently on the device.
      • Highlight the one that is backup of the current installed version.
      • Delete backups.
      • Manually add backup from PC.
      • Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
    • Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
    • Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
    • Magisk installer improvements:
      • When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
      • Magisk installer window displays the package name.
      • You can now copy to clipboard, the download URL and package ID.
    • Magisk Manager columns are now wider for better readability.
    • Package Manager improvements:
      • Added Search / Filter option.
      • Show count of filtered packages.
      • Application Name (label column).
      • "Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
      • Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
      • Other under the hood improvements.
    • When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
    • More verbose logging that helps with troubleshooting.
    • Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
    • Moved existing links under Help Menu | Links, and added few more handy links.
    • Added timestamp to support.zip filename.
    • On request, spinning cursor with text "Please be patient ..." is now displayed in red.
    • Flashing to inactive slot is now in basic configuration instead of advanced configuration.
    • Preparation work for version 5.0 DB improvements.
    6
    Why the heck did I wait so long to use this? This is the easiest way to update by far. Thanks much.
    4
    Another update, another P7P flash using this tool with less than a handful of mouse clicks and zero issues.

    Even if you have been using ADB for years like me, why choose to make things more difficult?
    4
    Hi all,

    I'm trying to figure out how to use pixel flasher.

    My P7pro is rooted with verity and verification disabled. But, PF does not recognize my device to be rooted. So, my question is how do I get PF to recognize root and to update + retain root and verity & verification left disabled?
    Did you allow root access for "[SharedUID] Shell" (com.android.shell) in Magisk? That's used by PF to detect root.
    If you use Magisk Hide you can also set the new package name (not app name) in the PF settings.
    3
    @badabing2003
    Just FYI I tried to flash back to December from Jan update but PF fails at trying to patch the boot img
    sqlite3.IntegrityError: FOREIGN KEY constraint failed

    I guess I'll just stick with Jan update and the bug rather than wipe. Worth a try tho
    You might try manually flashing the Full Factory image i.e. enacting flash-all.bat -- if you are unfamiliar, it's a really good thing to learn & know and it basically is what badabing2003's PF does, just using a GUI and automating the process; so if you love this program, this will give you a better idea on its inner workings and how it achieves things -- if it might be something in PF and not in the actual flashing/applying process.

    If you are unfamiliar with doing this, the best resource (IMHO) is roirraW "edor" ehT's guide in the section of "How to update each month"...It would be great if you could try it -- if anything, just for the knowledge & experience -- and hopefully it might be successful outside of PF's processing/GUI.
    If you have any questions or hesitations, of course feel free to ask in the thread...

    Good luck to you and hope it works out!

  • 43
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 7 Pro
    PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.

    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 / 7 Pro).
      • 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).

    For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

    Troubleshooting:
    • See this post.
    • Generate Sanitized support.zip file (File Menu) and submit that with your report.
    Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
    26
    New Release:
    Feb 05, 2023 v4.7.0 release
    • Added Magisk Backup Manager:
      • List all Magisk backups currently on the device.
      • Highlight the one that is backup of the current installed version.
      • Delete backups.
      • Manually add backup from PC.
      • Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
    • Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
    • Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
    • Magisk installer improvements:
      • When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
      • Magisk installer window displays the package name.
      • You can now copy to clipboard, the download URL and package ID.
    • Magisk Manager columns are now wider for better readability.
    • Package Manager improvements:
      • Added Search / Filter option.
      • Show count of filtered packages.
      • Application Name (label column).
      • "Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
      • Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
      • Other under the hood improvements.
    • When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
    • More verbose logging that helps with troubleshooting.
    • Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
    • Moved existing links under Help Menu | Links, and added few more handy links.
    • Added timestamp to support.zip filename.
    • On request, spinning cursor with text "Please be patient ..." is now displayed in red.
    • Flashing to inactive slot is now in basic configuration instead of advanced configuration.
    • Preparation work for version 5.0 DB improvements.
    14
    New Release:
    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.
    12
    Pre-Release:
    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.
    12
    New Release:
    Dec 04, 2022 v4.5.0 release
    • New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
    • New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
    • Use latest Python updated packages.
    • Ubuntu 22.04 support.
    • Miscellaneous improvements.