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

Search This thread

djcsurf

Senior Member
Jan 9, 2011
2,004
436
Kent
Can PF be used to flash December update over newer January update due to new bugs? Sorry if already asked I did try searching.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,870
2,454
Can PF be used to flash December update over newer January update due to new bugs? Sorry if already asked I did try searching.
You definitely can use to flash, I don't know if downgrading works though, one time I tried it didn't (even though I was expecting it to work)
You can try, make sure you select keep data the worst that will happen is that it won't work and you flash back the January update.
 
  • Like
Reactions: djcsurf

djcsurf

Senior Member
Jan 9, 2011
2,004
436
Kent
You definitely can use to flash, I don't know if downgrading works though, one time I tried it didn't (even though I was expecting it to work)
You can try, make sure you select keep data the worst that will happen is that it won't work and you flash back the January update.
Ok, thanks for letting me know. I've used it last couple of months to update, just wasn't sure about downgrade. Will try later when home and let you know how it goes.
 
  • Like
Reactions: badabing2003

djcsurf

Senior Member
Jan 9, 2011
2,004
436
Kent
@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
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,870
2,454
@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
Nah, that is something different, please provide support.zip so that I can take a look at that.
Most likely the patching worked, that is a message produced when PF tries to add the patched file to it's db.
Do you see the patched file in the list?
 

djcsurf

Senior Member
Jan 9, 2011
2,004
436
Kent
Nah, that is something different, please provide support.zip so that I can take a look at that.
Most likely the patching worked, that is a message produced when PF tries to add the patched file to it's db.
Do you see the patched file in the list?
It doesn't add the patched file, it just show the please wait thing on the left. Will grab the laptop and get log
 

simplepinoi177

Forum Moderator
Staff member
@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!

 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,870
2,454
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 -- 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!
I can give @djcsurf a workaround to make the patching work in PF, but I'm waiting for the logs so that I see why the error is produced. By giving a workaround, we'll lose the ability to troubleshoot further.

You're suggestion of doing manually is a very good advice.
 

krakout

Senior Member
Hello!

My 7P started downloading an update:

This update will install a beta version of Android 13 Quarterly Platform Release (QPR) (T2B2.22121 6.006) on your device. This pre-release version may contain errors and defects that can affect normal functioning of your device. Downloading updates over cellular data or metered Wi-Fi networks may lead to additional charges. To learn more about the Android Beta Program or opt out, visit g.co/ androidbeta.
Update size: 2.34 G

I'm on T2B1.221118.006 right now.


Will I lose root if I allow it? How should I proceed? Thanks!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,870
2,454
Hello!

My 7P started downloading an update:

This update will install a beta version of Android 13 Quarterly Platform Release (QPR) (T2B2.22121 6.006) on your device. This pre-release version may contain errors and defects that can affect normal functioning of your device. Downloading updates over cellular data or metered Wi-Fi networks may lead to additional charges. To learn more about the Android Beta Program or opt out, visit g.co/ androidbeta.
Update size: 2.34 G

I'm on T2B1.221118.006 right now.


Will I lose root if I allow it? How should I proceed? Thanks!
It will fail to install it you are rooted.
If you want to update and keep root, just download the firmware and repeat the process with the new firmware.
 
@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
Just use the Android flash tool and force flash all partitions. There is no reason you can't go back to december. There was no anti-rollback feature in this version.
You could even use Pixel Flasher.
 

djcsurf

Senior Member
Jan 9, 2011
2,004
436
Kent
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!

Thank you for the info, I will look into it when have some free time
I can give @djcsurf a workaround to make the patching work in PF, but I'm waiting for the logs so that I see why the error is produced. By giving a workaround, we'll lose the ability to troubleshoot further.

You're suggestion of doing manually is a very good advice.
I gave PF another try and it appeared to flash all ok but ended up in a boot loop with no option for anything but factory reset as data corrupt. Could be user error on my part, hence why I've not been about last couple days. I will grab the laptop later to see if any useful info might be stored as pass it over.
 
  • Like
Reactions: badabing2003

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    New Release:
    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.
    7
    For anyone else looking for the latest adb that actually works, here are the official links to adb/fastboot 33.0.3:

    https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - Windows
    https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip - Mac
    https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip - Linux

    Google doesn't keep the links to previous versions of adb on the platform-tools page.
    6
    Thanks @simplepinoi177 for finding relevant posts.
    What I want to add is that, although the initial thought process was to use the alternate slot as a fallback.
    Unfortunately that only works with older devices, and does not work for newer ones.

    Even for older devices one needs to remove system_other.img from the update image to get it to work.
    I have posted about the details, unfortunately I'm not very good at finding my own posts.
    The gist of the matter is that, factory images contain system_other which is flashed to the alternate slot's system partition, they contain the optimized dex files which are copied to the active slot after booting to system to save time.
    This effectively deems the alternate partition's system unusable.
    Removing system_other before flashing theoretically would get around that issue, at a small performance hit at first while the dex files are optimized on first use, and that works on older devices.
    I managed to setup Pixel XL with both slots bootable, and alternate between them at will, even one was rooted and the other stock.
    Sadly this no longer works on newer devices due to AVB.

    Having said all that, I still flash to alternate slot every month, knowing well that it I wouldn't be able to system boot to the alternate slot, I do this mainly because I want to keep all the partitions at most one release behind.

    Flashing to both slots makes sure that the bootloader is current on both slots, which avoids issues like what happened in August.
    I don't flash to both slots mainly because if there is a regression in the bootloader (I doubt it) or a disruption during flashing, I will have both bootloaders corrupt, effectively hard brick the device.
    I rather flash the alternate and in case something goes wrong, at least I can get into boatloader mode and fix things.

    There are a lot of posts about all this if you search the forums.
    6
    New Release:
    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.
    6
    Trying to dirty flash any factory image dated later than TD1A.220804.031 results in a bootloop

    I know it's neither a magisk nor modules issue as a non-patched boot.img results in the same issues and the only way to have the phone working again is fastboot flashing TD1A.220804.031 or TD1A.220804.009

    any ideas as to why this may be happening?

    edit: it essentially gets to the material you themed G logo then restarts
    @badabing2003 is going to ask you to pull a log and post it here. May as well get a head start and do that so he can see where the issue is
  • 49
    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.
    28
    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:
    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.
    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.
    13
    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.