yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] losticloud:
I started RMA I’ll try this again in a few weeks when I get new one.
[Google Pixel 7 Pro] badabing2003:
Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.

Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.
[Google Pixel 7 Pro] losticloud:
I did try but the phone wasn't detected. Files are attached.
[Google Pixel 7 Pro] badabing2003:
Thanks,

It's interesting that you started with slot a, ran into the problem writing product 11/11

I'm assuming that the phone could no longer boot to slot a,

Because the next thing I see is the phone in bootloader mode with slot b being active, not sure why it would be in bootloader mode as slot b should have been intact, nothing was written to slot b yet.

I wonder if out of factory phones have both slots the same image.

Then you trying flashing again, again the exact same step of flashing product 11/11 it failed.

However unlike the first time, the phone was placed in bootloader mode on slot b.

I wonder if you were manually putting the phone into bootloader mode or it was eventually ending up in that state?

You tried yet another time, again on slot b, and again it failed on the exact same step.

After that we have no data, I suppose at that point you couldn't even put the phone in bootloader mode.

When you get your new device, I would strongly suggest that you inspect the USB cable, and also make sure the USB port is connected to the PC without a hub or anything, and preferably USB 2.

I know at this day and age it sounds silly, but the signs are failure in communication, or hardware problem.

If you search Google for similar problems, you'd find lots of cases where most of those are related to either the drivers, the cable or the USB port, here's one as an example.

Let us know how your phone goes, and best wishes.
[Google Pixel 7 Pro] badabing2003:
New Release:

Oct 15, 2022 v4.3.0 release

New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.

Bug fix: Generating support.zip file was modifying the main db file unnecessarily.

Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.

Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.
[Google Pixel 7] badabing2003:
View attachment 5734059

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

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.

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.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 7] badabing2003:
Placeholder
[Google Pixel 7] dangercl0se:
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. Pixelflasher showed no error

And then my phone still prompts me to download updates,

phone android version = 13

build = TD1A.220804.009.A2

android security update = sept 5 2022

Did I flash the old factory image? or am I doing something wrong? or the pixel update prompt is an error?
[Google Pixel 7] Tiebe:
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.
[Google Pixel 7] badabing2003:
@dangercl0se , like what @Tiebe says.
[Google Pixel 7] dangercl0se:
thank you, i am noob.

all good, operator error!

thank you so much for making this, saved me so much time!!!
[Google Pixel 7] badabing2003:
New Release:

Oct 27, 2022 v4.3.1.0 release

Bug Fix: Magisk modules not listed on MacOS / Linux
[Google Pixel 7] schmeggy929:
Ok so im currently Bootloader unlocked, rooted and custom kernel on Slot B. I would like to update Slot A with verity and verification disabled using the same firmware currently in Slot B. Do I select processed firmware zip first or can I jump right to the patched magisk.img. I tried switching slots and flashing the firmware(no patched init_boot.img) with verity and verification disabled first. It goes through the steps and ends on the Fastbootd screen. When I reboot, it reboots 3 times and ends up on slot b. Not sure what Im doing wrong. I even tried checking "flash to inactive slot" and still boots to slot B.
[Google Pixel 7] badabing2003:
If you intend to flash the firmware on that slot, then yes, you have to select it.

This sounds like the flashing is not going past fastbootd stage.

I have read reports that it takes long in that stage (even doing things manually) with no feedback, so make sure you are waiting long enough.

You should also make sure your cable / USB drivers are good, and preferably use USB 2.0 port.

Few reboots and then back to B indicates that A is not bootable.
[Google Pixel 7] schmeggy929:
Looks like third time's a charm, I also swapped my usb type-c to type-c cable with a USB-A cable.
[Google Pixel 7] schmeggy929:
When the next update comes around, is it recommended to check the box for "Flash to both slots" along with checking disable Verity and verification?
[Google Pixel 7] badabing2003:
I don't disable verity and verification, Magisk patches properly.

However if you are using custom ROM, then you want to check with the ROM maker if either or both are necessary.

As for monthly update, I recommend you flash to inactive slot, not both slots, this way it is similar to OTA A/B, ie if anything goes wrong, your current setup in the current slot is not effected.
[Google Pixel 7] schmeggy929:
thank you, I will "Flash to inactive slot" route. And yes for now, the available Kernels require Verity and verification disabled. I only want to have both slots verity and verification disabled just in case something goes wrong and I have to boot the other slot. I do not want to have to full wipe because I booted a verity and verification enabled slot.
[Google Pixel 7] badabing2003:
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.
[Google Pixel 7] rspkt:
Typically I do everything manually but I decided to try this tool out on OSX and so far everything has worked flawlessly. Thank you for your work.
[Google Pixel 7] dpotter38:
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
[Google Pixel 7] dpotter38:
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.
[Google Pixel 7] badabing2003:
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.

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.

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

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.

< 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)

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.

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.
[Google Pixel 7] widelife25:
Hey there,

I am getting this error message when trying to re-root after installing the 14 beta 3.1 update.

ive tried platform tools 33, and 34, ive tried all different versions of magisk, ive tried the factory as well as the OTA, ive tried reflashing the OTA and using pixelflasher again but the error persists.

Getting SHA1 of C:\Users\****\AppData\Roaming\PixelFlasher\tmp\magisk_patched_26102_54aad592_952d2205.img ...

SHA1 of magisk_patched_26102_54aad592_952d2205.img file: 952d2205703d44ac4b289c26992d1c1442a5ab22

Getting SHA1 of source init_boot.img ...

Source init_boot.img's SHA1 is: 54aad592800008c904e58e830080af60882f2b35

Extracting SHA1 from magisk_patched_26102_54aad592_952d2205.img ...

SHA1 embedded in C:\Users\*****\AppData\Roaming\PixelFlasher\tmp\magisk_patched_26102_54aad592_952d2205.img is: 54aad5928~!~c904e58e83~!~!af60882f2b35!R

Comparing source init_boot.img SHA1 with SHA1 embedded in 54aad5928~!~c904e58e83~!~!af60882f2b35!R (they should match) ...

NOTICE: The two SHA1s did not match.

magisk_patched_26102_54aad592_952d2205.img extracted sha1: 54aad5928~!~c904e58e83~!~!af60882f2b35!R

init_boot.img sha1: 54aad592800008c904e58e830080af60882f2b35

This could be normal due to compression

Checking match confidence level.

The confidence level is: 27.500000000000004%

2023-06-15 22:53:13 ERROR: Something is wrong with the patched file SHA1, we got a low match confidence.

Aborting

2023-06-15 22:53:39 Creating support.zip file ...

Saved support file to: C:\Users\****\Desktop\support_2023-06-15_22-53-35.zip

Please help.
[Google Pixel 7] mruno:
The issue was the "Flash Pixel Phone" button stayed grayed out after selecting the patched boot.img.
[Google Pixel 7] badabing2003:
The patch is good, the differences are due to compression.

There is a shift due to the compression hence why the confidence level is low.

Next version of PF will do two things to address this.

1- Account for shift

2- Make the abort optional, this way a user can assess and decides to continue or not.

You can wait for the next version, or if you want the patch file, you should find it in C:\Users\REDACTED\AppData\Roaming\PixelFlasher\tmp\magisk_patched_26102_54aad592_f1f8bd72.img

Replace REDACTED with your username.
[Google Pixel 7] badabing2003:
Flash Pixel Phone enabling / disabling is a function of many parameters, depending on the choices you have made.

Selecting a valid boot image is just one of them.

I doubt that there is an issue in there, you're the first that brings it up, I strongly suspect one of the other requirements to enable the button was not satisfied.

Unless you provide an exact sequence of events to recreate the issue and show that there is an issue, there is not much I can do. (a video recording would be best)
[Google Pixel 7] widelife25:
Thank you for your quick and concise solution!
[Google Pixel 7] Aks:
I am also facing exactly same issue while trying to patch A14 Beta 3.1. Below is the summary and attached is the full message if it helps to debug further.

I guess I will wait for the next update.

Extracting SHA1 from magisk_patched_26100_54aad592_cd5f447b.img ...

SHA1 embedded in C:\Users\Akhil\AppData\Roaming\PixelFlasher\tmp\magisk_patched_26100_54aad592_cd5f447b.img is: 54aad5928~!~c904e58e83~!~!af60882f2b35!R

Comparing source init_boot.img SHA1 with SHA1 embedded in 54aad5928~!~c904e58e83~!~!af60882f2b35!R (they should match) ...

NOTICE: The two SHA1s did not match.

magisk_patched_26100_54aad592_cd5f447b.img extracted sha1: 54aad5928~!~c904e58e83~!~!af60882f2b35!R

init_boot.img sha1: 54aad592800008c904e58e830080af60882f2b35

This could be normal due to compression

Checking match confidence level.

The confidence level is: 27.500000000000004%

2023-06-16 23:38:51 ERROR: Something is wrong with the patched file SHA1, we got a low match confidence.

Aborting
[Google Pixel 7] Aks:
Mot sure why but text file is not visible to me. Here is the Google Drive link for the same file.

PixelFlasher 5.3.0.0 started on 202.txt

drive.google.com
[Google Pixel 7] badabing2003:
No worries, I don't need it, it is already fixed, I just have to prepare and push it.

In the future you can generate a support file, which is better as it redacts sensitive information, and it also provides me with more details to troubleshoot.
[Google Pixel 7] Aks:
Thank you for the quick response and the fix, I'll be on look out for the update :)
[Google Pixel 7] badabing2003:
@Aks and @widelife25

Release Release v5.3.1.1 · badabing2005/PixelFlasher

Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected. Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 buil...

github.com

I have to fix Windows 2019 (Win7) build, but all the others are there.
[Google Pixel 7] badabing2003:
New Release:

June 16, 2003 v5.3.1.2 release

Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.

Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.

Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.

Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.

Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
[Google Pixel 7] Aks:
It worked seamlessly. Thank you :)
[Google Pixel 7] :
Hi again. I'm trying to sideload the June OTA but the KEEP DATA option, and most others are greyed out. Curious where I'm screwing up?

I'm already rooted, just trying to update and keep my stuff. PF is connected, I got the right file, I patched it, and the only option I have is FULL OTA. Hmm.
[Google Pixel 7] badabing2003:
No worries, you didn't screw up, with Full OTA there is no Keep Data or not, it's a different type of flashing, that doesn't use fastboot (it uses sideload)

You can simply click on Flash Pixel Phone button, it will not wipe.
[Google Pixel 7] badabing2003:
New Release:

June 21, 2023 v5.3.2.0 release

Added support for Pixel tablet (tangorpro).

For future devices, fixed a bug to auto detect init_boot partition and flash init_boot instead of boot even if the device is newer than the PixelFlasher and is not in PixelFlasher's list.

Disable Patch buttons if device is not in adb mode.

Reboot to system after lock / unlock bootloader if No Reboot option is not selected.

Increase sleep after reboots to various modes to assure that slow devices have time to be detected.

Updated Readme and screenshots.

Minor improvements and bug fixes.
[Google Pixel 7] badabing2003:
New Release:

June 23, 2023 v5.3.3.0 release

#79 Bug-fix: Package Manager column stays unsorted when filtered.

Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.

Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3

Package manager bug fixes and improvements.
[Google Pixel 7] scorpio76r:
Hello, I am just preparing a new hp windows 11 pc for my 7pro when it arrives in a days. I can't seem to find 33.0.3 platform tools online. Can someone please link me the 33.0.3 platform tools?
[Google Pixel 7] t-ryder:
Here you go
[Google Pixel 7] scorpio76r:
Thank you so much. I don't even have my 7pro yet and, assistance is great in the Pixel XDA community. I'm truly glad to have dropped oneplus after many years and, come to Pixel. The fact that OPPO sucks and, they joined oneplus I predict many more people will come over to Pixel. I have many buddies here on xda and, look forward to making more many more. Lastly just, curious... is there currently a working twrp for this device?
[Google Pixel 7] badabing2003:
Nope
[Google Pixel 7] badabing2003:
New Release:

July 03, 2023 v5.4.0.0 release

Add Pixel Fold (Felix)

Add sorting capability to boot list.

Add warning about Magisk a8c4a33e:26103

Improved auto-resize of boot columns.

Improved internal DB management.

Handle beta or similar words in the firmware name to not trigger hardware mismatch warning.

Improved tracking the origin of a patched image.

Display Kernel version as part of device details

Refresh package manager list when packages are updated to reflect the changes.

Miscellaneous other improvements.

Update Readme.
[Google Pixel 7] tim1aust:
Each time I fire up PixelFlasher (AUR version), I get a page full of these messages:

(PixelFlasher:413528): GLib-GObject-WARNING **: 13:11:11.787: invalid cast from 'GtkMenuItem' to 'GtkImageMenuItem'

(PixelFlasher:413528): Gtk-CRITICAL **: 13:11:11.787: gtk_image_menu_item_set_image: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed

(PixelFlasher:413528): GLib-GObject-WARNING **: 13:11:11.787: invalid cast from 'GtkMenuItem' to 'GtkImageMenuItem'

(PixelFlasher:413528): Gtk-CRITICAL **: 13:11:11.787: gtk_image_menu_item_set_image: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed

It apparently has no effect on the functioning of the app, but is it something exxpected/known, or is it something with my Manjaro system?

TIA
[Google Pixel 7] badabing2003:
No it is not limited to your Manjaro,

I see these on Ubuntu as well, as you pointed out, they are benign, and I don't know how to suppress them.
[Google Pixel 7] badabing2003:
New Release:

July 13, 2023 v5.5.0.0 release

Added a patch method Other Magisk App to be able to select any Magisk apk and use it to create a patch without installing Magisk, handy when a patch needs to be created with an older version of Magisk (in case the current version has issues) and Magisk daemon gets in the way and replaces the older version with a stub.

UI improvements

Added Kill Application in Package Manager.

Added Clear Application Data in Package Manager.

Now that Full OTA flashing is the preferred method, added a direct link to the device's full OTA download page from Google.

While flashing, disable the Flash Pixel Phone button to avoid accidental clicking.

Improved root detection.

Bug fixes and other improvements.
[Google Pixel 7] badabing2003:
Bug Fix Release:

July 14, 2023 v5.5.1.0 release

Bug fix #85 Can't enable/disable Advanced option in v5.5.0

A little improvement #84 UI elements not optimized for monitors with low screen resolution
[Google Pixel 7] CodeOnDiscord:
I flashed the boot image of the latest OTA Pixel 7 pro image and then flashed it on my phone. That worked fine. After I booted though, a security update started installing (it was around 2.2GB).

After that updated, root was lost, so I applied the previous OTA patch thinking it would fix it, since it's a patched boot image. The problem is that it failed, and now my phone can't even enter the bootloader. Is there an easy way to fix this? Wanted to ask before doing anything drastic.

I can enter fastboot and recovery mode btw.
[Google Pixel 7] badabing2003:
You probably at first didn't flash the latest full OTA (switch to English on Google page, for some reason, only English shows the latest).

Just download that, process, patch , flash and yous should be fine.

With OTA you can't flash lower version.
[Google Pixel 7] badabing2003:
New Release:

July 16, 2023 v5.5.1.1 release

#84, further UI improvements for smaller screens.

Better dark mode handling for MacOS and Linux.

#86, improved handling of space characters in paths.