Themes / Apps / Mods ðŸ“³ðŸ”¥PixelFlasher for Google Pixel 7 Support Thread.

Search This thread

scuzzo500

Senior Member
Jul 31, 2012
164
13
This should tell you what they mean.
Yes TQ1A is good
@badabing2003
Thank you sweet baby Jesus. I've been looking using pixelflasher in every query and couldn't find anything about how Google numbered their releases. I never thought to just look at what Google uses as their naming convention.
All I want is to stay stock and rooted. I think this will do it for me. Thank you for the help.
 
  • Like
Reactions: badabing2003

miklat106

Member
Sep 24, 2018
15
2
Hi, I tried flashing the November image over the December one (downgrading) and it ended up giving me "cannot load android" message in recovery mode. I got out of it after flashing the December OTA again from the android flash tool but I'm wondering what I did wrong. Is it because I tried flashing and older update on top of a new one without wiping?

Don't know if it matters but I did with a patched boot as well (patched by PF).
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,443
Hi, I tried flashing the November image over the December one (downgrading) and it ended up giving me "cannot load android" message in recovery mode. I got out of it after flashing the December OTA again from the android flash tool but I'm wondering what I did wrong. Is it because I tried flashing and older update on top of a new one without wiping?

Don't know if it matters but I did with a patched boot as well (patched by PF).
I don't know, I had a similar issue flashing Aug release on a September running Redfin.
You can read all about it here.
I don't know if it is possible, I would assume it is, but the only time I tried I was not successful.
 

fivefour

Senior Member
Jun 7, 2010
770
1,341
Emerald Coast
bit.ly
I've not used this tool but being available for Linux makes it interesting, I normally use CLI but wanted to subscribe to the topic and say thanks for making it available. Bookmarking if you will for future use.
 
  • Like
Reactions: badabing2003

bizkit_120

Senior Member
Feb 4, 2014
102
15
Hello,

first of all thank you for the great tool.

My report about the first experiences:

After I received my new Pixel 7 last week, I immediately wanted to root it (like my old OnePlus 7).
The first attempts under Windows 11 and Linux failed and always bricked the Pixel.
This was not due to the PixelFlasher, but to the USB cable I used and its length.
After I tried it with the original cable everything worked :)

One day later I had magisk so far that Google Wallet with PayPal worked without errors.

I just downloaded the December update and patched and flashed it.
Everything worked right away. YASNAC SaftyNet Check shows everything green :)

Google Wallet also does not complain, so the next purchase at the checkout should all go well ...

Thanks again for PixelFlasher

Greetings Jerry
Hello, thanks for sharing, moving from op 9 to Pixel 7.

QQ, do you see any major benefits on Dec update? ( Like clear call..I may gonna hold awhile no sure if any bugs) Good to hear your Google pay works, how about inTune company Portal ,can it bypass root check?
 

jofa news

Senior Member
Apr 3, 2016
82
34
Hannover
Hello, thanks for sharing, moving from op 9 to Pixel 7.

QQ, do you see any major benefits on Dec update? ( Like clear call..I may gonna hold awhile no sure if any bugs) Good to hear your Google pay works, how about inTune company Portal ,can it bypass root check?
Hi @bizkit_120,

I haven't had any issues with the Nov update, I don't see any fixes in the Dec update that are relevant to me.
My phone calls were and are clear. I was hoping there were improvements with the fingerprint sensor, but that wasn't the case with the Dec. update.
I can't say anything about inTune Company Portal since I don't use it.
But with my rooted OP7 with EvolutionX, many apps detected the rooting but didn't cause any problems.
With Android 13 on the Pixel 7, I no longer have an app that detects rooting. Most important for me was Goolge Wallet (Pay).

Merry Christmas and best regards
 

bizkit_120

Senior Member
Feb 4, 2014
102
15
Hi @bizkit_120,

I haven't had any issues with the Nov update, I don't see any fixes in the Dec update that are relevant to me.
My phone calls were and are clear. I was hoping there were improvements with the fingerprint sensor, but that wasn't the case with the Dec. update.
I can't say anything about inTune Company Portal since I don't use it.
But with my rooted OP7 with EvolutionX, many apps detected the rooting but didn't cause any problems.
With Android 13 on the Pixel 7, I no longer have an app that detects rooting. Most important for me was Goolge Wallet (Pay).

Merry Christmas and best regards
Nice, this is my first pixel device, Finger sensor i won't say bad but definitely OP 9 is more faster and accurate, for me p7 got 2 out 10 fail to recognize, still acceptable range.

Yep.Google wallet important to me as well, still plenty of merchants not accepting it, big ones like Lowe's, walmart , kroger...

Thank you, same to you, Merry Xmas! Cheers,
 
  • Like
Reactions: jofa news

mruno

Senior Member
Aug 27, 2010
204
54
Google Pixel 6
How to update and retain root after connecting phone and enabling usb debugging:
1 - click Pixel Phone Factory Image button and download from website
2 - browse to the location of the downloaded update
3 - process the update by pressing the rocket 🚀 button
4 - select the update
5 - click the Patch button
6 - select the patched image
7 - click Flash Pixel Phone
be patient and let the device update and reboot. it should take 2 - 5 mins.
1672954460950.png
 

jofa news

Senior Member
Apr 3, 2016
82
34
Hannover
How to update and retain root after connecting phone and enabling usb debugging:
1 - click Pixel Phone Factory Image button and download from website
2 - browse to the location of the downloaded update
3 - process the update by pressing the rocket 🚀 button
4 - select the update
5 - click the Patch button
6 - select the patched image
7 - click Flash Pixel Phone
be patient and let the device update and reboot. it should take 2 - 5 mins.
View attachment 5802799
@mruno :

do I need to do the two steps before?

- Disabled all modules
- UInhide Magisk

or can I skip these steps with PixelFlasher?

Many greetings
Jerry
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,443
@mruno :

do I need to do the two steps before?

- Disabled all modules
- UInhide Magisk

or can I skip these steps with PixelFlasher?

Many greetings
Jerry
You do not need to hide Magisk, as for disabling modules, it all depends on the modules, I don't disable any of mine, but then again the modules I use are basic and safe for updates.
Examples. Systemless hosts, busybox, safetynet fix, ....
You can enable/ disable modules from within PF.
 
  • Like
Reactions: jofa news

jofa news

Senior Member
Apr 3, 2016
82
34
Hannover
You do not need to hide Magisk, as for disabling modules, it all depends on the modules, I don't disable any of mine, but then again the modules I use are basic and safe for updates.
Examples. Systemless hosts, busybox, safetynet fix, ....
You can enable/ disable modules from within PF.
Thank you, i will try ... yeah ... it works ...

thx, this is a wonderful tool :)
 
Last edited:

PurppleMonkey

Senior Member
Jun 21, 2013
117
28
TY !

i used the "flash boot" button !


But, if i want to flash the firmware with the patched boot, the phone get stuck in fastboot mode for 15min... something get wrong ? (mac user)
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,443
TY !

With the next update i'll try with a USB A to USB C - Connected to a Thunderbolt port !



Q° - During the flash, there is no problem to stop the process if it still blocks?
Definitely there is, depending on when you stop the process.
If it is stuck at fastbootd, you can unplug and replug safely in hopes that it gets detected and continues.
You can only stop the process (abort) if what has been flashed to that point is compatible with what's left behind from the previous flash.
 

charlie..

Senior Member
Jan 22, 2016
53
14
Samsung Galaxy S III Mini
i9100
I'm new to the pixel family. Root worked very well (wihtour pixel flasher). Now I stumbled over a question which is rather related to the PF but maybe can be answered here anyway.
How does the beta opt-on or opt-out procedere work with focus on data loss.
Is it possible, coming from stock rom, to simply flash the current beta to opt-in and opt-out with the next stable release without full wipe. I read that in the end of the beta there will be the chance to come to the stable release without wiping data.

Shortend question: Can I switch between stable and beta release (each way) wihtout data loss?

PS. @badabing2003 congrats and thank you for such a master piece of software and your unstopable support.
 

Top Liked Posts

  • 1
    What are the issues with these versions of platform tools. It won't let me flash with the error messages & I can't find previous builds of platform tools online
    With the latest releases you could brick your device because those are buggy. I uploaded v33.0.3 for you.
    LINK (Mega.nz)
    1
    I have stock march update(pixel 7), i want to diable variety and verification to install custom kernel, just enabling these options in expert mode and done? or how? thank you.
    Keep in mind first time you do this it will wipe your phone,
    Just ticking the checkboxes is not enough, you do it during flashing.
    Also each time you update you have to make sure they remain ticked, otherwise it wipes.

    The good thing, PF remembers your choices.
    1
    You mean while flashing factory images ROM then enabling varity and verififcation?
    Yes they need to be enabled while flashing, the checkboxes are just options you select, they only apply when you flash with those choices.
  • 7
    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.
    4
    ahhhh thank you! It sounds like it's Magisk. I'm hesitant to try flashing stock image because I'm afraid it might turn into a nightmare trying to get everything working again. Do you think I'll have to wait long for a Canary update to resolve the issue?
    If you don't feel comfortable, wait, the reason you have to flash stock first because Magisk does not allow you to downgrade.
    I have not tested it tried it, but I've read in the Magisk general thread that it you flash debug, then you can downgrade.
    I'm supposed to use platform tools 33.0.3? I thought 34.0.1 is OK again and only 34.0.0 is bad?
    Unfortunately you have to use 33.0.3, both 34.0.0 and 34.0.1 cannot get into userspace fastbootd mode, which is necessary to flash factory image.
    Using 33.0.3 is much easier than downgrading Magisk, because all you have to do is point to the 33.0.3 folder in PF, and PF will take care of the rest.
    4
    Thanks so much for this tool, I finally could update my rooted Pixel 7 easily.
    3
    A top notch tool, it's too easy! Usually I like to do all this manually but got fed up copying, pasting, zips within zips etc etc :giggle:
    1
    I was able to use Pixel Flasher to update to the January release, but both February and March images are refusing to make a Patched boot image. Any help is greatly appreciated! I'm including a support.zip.
    • Use PF 4.8.0 only I see you are switching between 4.8.0 and 4.6.1
    • Use Android Platform Tools 33.0.3 (good you are already on that, don't try the 34.0.x)
    • Use Magisk Canary 25206 or Stable 25200, 25207-25210 have issues, also see this
    You should be good to go.
  • 17
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 7
    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 devices, generic issues that are device agnostic should be discussed in the main thread.
    8
    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.
    7
    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
    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.
    4
    New Release:
    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.