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

Search This thread

elong7681

Senior Member
May 23, 2015
601
206
41
US
Google Pixel 5
Google Pixel 7
I don't know, possibly yes, as SafteyNet alters that.
These are questions best asked in the Kernel threads, I don't personally disable verity or verification as I don't use custom kernels, I wouldn't be the best source of the info.
As far as PF is concerned, it adds the proper flags to the fastboot command if those options are selected, and we can see that in your logs.
I'm still interested to hear back and learn.
I will uninstall the safetynet module and flash the kernel and report back. I'm not at my computer right now but when I get back to it I'll let you know what happens
 

elong7681

Senior Member
May 23, 2015
601
206
41
US
Google Pixel 5
Google Pixel 7
I don't know, possibly yes, as SafteyNet alters that.
These are questions best asked in the Kernel threads, I don't personally disable verity or verification as I don't use custom kernels, I wouldn't be the best source of the info.
As far as PF is concerned, it adds the proper flags to the fastboot command if those options are selected, and we can see that in your logs.
I'm still interested to hear back and learn.
So I uninstalled safetynetfix and I think it removed the enforcing flag but I was still unable to use the kernel

[ro.boot.product.hardware.sku]: [GVU6C]
[ro.boot.revision]: [MP1.0]
[ro.boot.secure_boot]: [PRODUCTION]
[ro.boot.slot_suffix]: [_b]
[ro.boot.theme]: [1]
[ro.boot.verifiedbooterror]: [ERROR_VERIFICATION]
[ro.boot.verifiedbootstate]: [orange]
[ro.boot.verifyerrorpart]: [vbmeta]
[ro.boot.warranty.sku]: [UGS]
[ro.bootloader]: [cloudripper-1.0-9074510]
[ro.bootmode]: [unknown]
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
So I uninstalled safetynetfix and I think it removed the enforcing flag but I was still unable to use the kernel

[ro.boot.product.hardware.sku]: [GVU6C]
[ro.boot.revision]: [MP1.0]
[ro.boot.secure_boot]: [PRODUCTION]
[ro.boot.slot_suffix]: [_b]
[ro.boot.theme]: [1]
[ro.boot.verifiedbooterror]: [ERROR_VERIFICATION]
[ro.boot.verifiedbootstate]: [orange]
[ro.boot.verifyerrorpart]: [vbmeta]
[ro.boot.warranty.sku]: [UGS]
[ro.bootloader]: [cloudripper-1.0-9074510]
[ro.bootmode]: [unknown]
Have you checked the kernel forums / threads?
I don't know what Kernel it is, what it expects and what problems you're having, and even if I knew, I probably shouldn't give advice on it.
 
  • Like
Reactions: elong7681

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
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.
 
  • Like
Reactions: manjaroid

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
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.
 

jofa news

Senior Member
Apr 3, 2016
80
32
Hannover
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
 
  • Like
Reactions: badabing2003

Bestiole222

Member
Aug 24, 2016
44
14
I can't launch 4.5.0 or 4.6.0 versions, I'm under windows 11, there's only the access fence "Pixel flasher is loading" and when it disappears nothing more (the app appears on windows task manager). 4.4.0 version is working fine.
Any idea?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
New Release:
Dec 06, 2022 v4.6.1 release
  • #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.
 

fullmetal509

Senior Member
Jul 12, 2010
531
100
Wenatchee
Google Pixel 7
Once connected i try to to restar boot loader or do a Dry Run. It says phone doesnt seem to be connected
Untitled.png
 

asamofal

New member
Dec 7, 2022
2
0
badabing2003, Hi! Have some problems here...
Pixel 7, current firmware installed on the phone is 220804.031, I'm trying to patch a boot image but always failed. I tried on MacOS and Linux, the same error.

2022-12-07 22:35:00 The following firmware is selected:

panther-td1a.220804.031-factory-2f036a47.zip



Please select a boot image!



2022-12-07 22:35:03 Scanning for Devices ...

1 Device(s) are found.



Selected Device on 2022-12-07 22:35:03:

Device ID: 28161FDH2000ZJ

Device Model:

Device Active Slot:

Device Mode: recovery

Device is Rooted: False

Device Build:

Device API Level:

Device Architecture:

Device Bootloader Version:

Magisk Manager Version:



Selected Boot:

File: init_boot.img

Path: /Users/anton/Library/Application Support/PixelFlasher/boot_images4/caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d/init_boot.img

SHA1: caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d

Patched: False

Date: 2022-12-07 21:35:30

Firmware Fingerprint: panther-td1a.220804.031

Firmware: /Users/anton/Downloads/panther-td1a.220804.031-factory-2f036a47.zip

Type: firmware





==============================================================================

2022-12-07 22:35:07 PixelFlasher 4.6.1.0 Patching boot.img

==============================================================================



*** Dialog ***

WARNING: Your phone model is:



The selected init_boot.img is from: panther-td1a.220804.031



Please make sure the init_boot.img file you are trying to patch,

is for the selected device: 28161FDH2000ZJ



Click OK to accept and continue.

or Hit CANCEL to abort.

______________



User pressed ok.

Deleting init_boot.img_caf4d53a.img from phone in /storage/emulated/0/Download ...



2022-12-07 22:35:09 ERROR: Encountered an error.

Return Code: 134.

Stdout: .

Stderr: adbd F 12-07 21:35:08 403 403 shell_service.cpp:380] Could not set SELinux context for subprocess

libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 403 (adbd), pid 403 (adbd)

.

Aborting ...

Looks like the model is not recognised. Would appreciate any ideas.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
badabing2003, Hi! Have some problems here...
Pixel 7, current firmware installed on the phone is 220804.031, I'm trying to patch a boot image but always failed. I tried on MacOS and Linux, the same error.

2022-12-07 22:35:00 The following firmware is selected:

panther-td1a.220804.031-factory-2f036a47.zip



Please select a boot image!



2022-12-07 22:35:03 Scanning for Devices ...

1 Device(s) are found.



Selected Device on 2022-12-07 22:35:03:

Device ID: 28161FDH2000ZJ

Device Model:

Device Active Slot:

Device Mode: recovery

Device is Rooted: False

Device Build:

Device API Level:

Device Architecture:

Device Bootloader Version:

Magisk Manager Version:



Selected Boot:

File: init_boot.img

Path: /Users/anton/Library/Application Support/PixelFlasher/boot_images4/caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d/init_boot.img

SHA1: caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d

Patched: False

Date: 2022-12-07 21:35:30

Firmware Fingerprint: panther-td1a.220804.031

Firmware: /Users/anton/Downloads/panther-td1a.220804.031-factory-2f036a47.zip

Type: firmware





==============================================================================

2022-12-07 22:35:07 PixelFlasher 4.6.1.0 Patching boot.img

==============================================================================



*** Dialog ***

WARNING: Your phone model is:



The selected init_boot.img is from: panther-td1a.220804.031



Please make sure the init_boot.img file you are trying to patch,

is for the selected device: 28161FDH2000ZJ



Click OK to accept and continue.

or Hit CANCEL to abort.

______________



User pressed ok.

Deleting init_boot.img_caf4d53a.img from phone in /storage/emulated/0/Download ...



2022-12-07 22:35:09 ERROR: Encountered an error.

Return Code: 134.

Stdout: .

Stderr: adbd F 12-07 21:35:08 403 403 shell_service.cpp:380] Could not set SELinux context for subprocess

libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 403 (adbd), pid 403 (adbd)

.

Aborting ...

Looks like the model is not recognised. Would appreciate any ideas.
Why is your device in recovery mode?
 

asamofal

New member
Dec 7, 2022
2
0
Why is your device in recovery mode?
It was in "bootloader mode" but PixelFlasher requires "adb mode"... I thought recovery is what I need because in recovery mode my phone is available by "adb devices", I was wrong :)
Now I see, need just to enable USB debugging in developer options and keep the phone in "system running" state. Ok, now I patched desired init_boot with no problems. Thanks for the tool!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
It was in "bootloader mode" but PixelFlasher requires "adb mode"... I thought recovery is what I need because in recovery mode my phone is available by "adb devices", I was wrong :)
Now I see, need just to enable USB debugging in developer options and keep the phone in "system running" state. Ok, now I patched desired init_boot with no problems. Thanks for the tool!
When flashing the device can be in any mode, PF will detect the mode and reboot to bootloader (assuming that the device can get into bootloader mode)
However to create a patch, you need to be in adb mode.
 
  • Like
Reactions: asamofal

scuzzo500

Senior Member
Jul 31, 2012
164
13
I have a question and I hope someone can help me understand something confusing me. I've got my phone updated to the November patch. In the attached screen shot I have updated to the firmware circled in red. I know the December update is out and I'm set up and ready to apply it. However, I'm not sure if the firmware circled in blue is usable on my pixel 7 since labeling tda1 has changed to tq1a. I've got the global version so I figure I don't need to worry about the Verizon, telia, or o2 firmwares. Is this the right firmware for my pixel 7? If it is, why does Google change the labeling in, what to my experience is, such an odd way?
Screenshot_20221208-152514.png
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,591
1,876
I have a question and I hope someone can help me understand something confusing me. I've got my phone updated to the November patch. In the attached screen shot I have updated to the firmware circled in red. I know the December update is out and I'm set up and ready to apply it. However, I'm not sure if the firmware circled in blue is usable on my pixel 7 since labeling tda1 has changed to tq1a. I've got the global version so I figure I don't need to worry about the Verizon, telia, or o2 firmwares. Is this the right firmware for my pixel 7? If it is, why does Google change the labeling in, what to my experience is, such an odd way?
This should tell you what they mean.
Yes TQ1A is good
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    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.
    Check out the verbiage "Once you're enrolled" at the bottom of this page: https://www.google.com/android/beta#devices
    2
    My Pixel 7 is on TQ1A.221205.011 build. I just unlocked the bootloader so all the user data are gone. Now I want to use PF to root the phone. So on PF I can browse to find the platform tools which version is 33.0.3 and factory image (panther-tq1a.221205.011-factory-ab58bb03.zip). I processed the zip file and saw there is a boot.img file showed up. I think for P7 we should use ini.boot.img. Is it OK to go ahead? And do I need to flash into inactive slot for safety reason?
    Also I haven't installed Magisk yet. Is there a option that I can get Magisk Delta? My final purpose is to root the phone and then get 32-bit app supported.
    where do you see boot.img ?
    In the list you see boot.img?
    or just the label to the left.
    Select the boot and the console should show you the path and filename. PF knows that it needs to use init_boot with P7

    Yeah, flash to inactive.
    There is an option to install Magisk Alpha and Magisk Delta are supported, and they can be installed all from PF.
    Make sure you only install one, and when installing, make sure you first unhide magisk, if you have one hidden.
    After installation if PF says Magisk not found, just update the package name in the PF configuration section (Magisk delta has different package name, soon to be released next PF should do this automatically)
    2
    You had never updated your phone previously?
    Just flash to both slots and you should be fine.
    Why not go with January update? or better yet on Monday with the February drop?
    1
    @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.
    1
    Can i use this to root for the first time ?
  • 14
    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 user interaction) 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.
      • 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.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • ID
      • Hardware model.
      • 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.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • 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 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.
    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.
    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.
    2
    You had never updated your phone previously?
    Just flash to both slots and you should be fine.
    Why not go with January update? or better yet on Monday with the February drop?
    2
    This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.

    If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.

    Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.

    Edit: Attached Support.zip

    Looking at your logs I have the following observation.

    You started with an old SDK, which is not a good idea, and PF warned you about it, and you chose to proceed regardless. Don't do this again, specially on the latest phones / firmware.
    Code:
    2022-11-17 20:08:35 ERROR: Detected older Android Platform Tools version 29.0.6-6198805
    2022-11-17 20:08:51 User accepted older version 29.0.6-6198805 of Android platform tools.
    SDK Version: 29.0.6-6198805

    At this point Magisk was not installed, and your phone was on slot b
    You first processed the 220804 firmware file, and when you tried to patch, PF told you that there was no Magisk on your device.

    You then manually (outside of PF) installed Magisk Manager 25.2:25200, or if it was hidden, you restored it. (just for my curiosity, which was it?)
    You created a patch from 220804 firmware's init_boot

    Then followed by creating a patch from 221105 factory image
    The above two patches was created by PF using binaries from Magisk Manager.

    Tried to flash the patched file and the phone got stuck at fastbootd.
    Most likely due to using an older Platform tools.
    Code:
    extracting super_empty.img (0 MB) to disk... took 0.002s
    Rebooting into fastboot                            OKAY [  0.000s]
    < waiting for REDACTED >

    You then upgraded the SDK to
    Code:
    Android SDK Version:    33.0.3-8952118

    But at this point your phone was already on slot a in bootloader mode, probably due to the previous botched flashing.

    You tried to flash slot a and ran into this issue.
    Code:
    < waiting for REDACTED >
    fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

    Still on slot a, next attempt was to flash both slots
    This worked without errors and the system booted to slot b

    You hid the Magisk Manager

    you then processed 221105 factory image, (FYI this is unnecessary, if you do it once, nothing changes if you repeat it)
    You patched this time PF using rooted Magisk
    Interestingly the generated patch had a different SHA1: f44feb1bc2b8643333af5e14f0a12755b537f076
    Whereas the previous patch SHA1 was 8753990ce4374d5a4509e0bae48f54e2553be216
    This is a curious case, the only differences are.
    875399 was patched using non-hidden Manager binaries
    f44feb was patched using rooted Magisk
    both same versions of Magisk.

    I'd be very interested if you could share these files for me to inspect.
    if you could zip the following (replace redacted with your username)
    Code:
    C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4

    You then proceeded to flash to both slots again
    Which went well.
    End of logs
    At this point your system is probably on slot a and working well.

    FYI, I was able to get this fixed by flashing the Oct init_boot, then manually patching the November init_boot and flashing it.

    I must have missed it the first time, but when trying to patch the November init_boot there was an error in the PixelFlasher console, "Foreign Key constraint failed", but it still showed the patched boot file as available in the list. Just wanted to put this out here in case anyone else runs up against a similar issue.
    No you didn't, or at least I didn't see that you did, If you don't mind I'd be interested in getting another support.zip from you which would include this along with the Foreign key error you encountered.
    That error is benign, as PF knows how to handle it, but it is included so that I can troubleshoot and find the root cause (it happens very rarely and I'm trying to see what conditions are causing that)

    Thanks and sorry for the delayed response, it takes time to process these logs.
    2
    Hi, thank you for doing this. My rooted pixel 7 pro is prompting me to install a security update. I tried to update via pixel flasher.

    Flashed with the latest platform tools from offical android site and downloaded the latest factory image.

    And then my phone still prompts me to download updates, phone android version = 13 and build = TD1A.220804.009.A2

    Am I flashing the old factory image? or am I doing something wrong? or the pixel update prompt is an error?
    You need to download the factory image at the bottom. It's sorted from oldest to newest. So currently TD1A.220804.031 is the latest.