yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] badabing2003:
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.
[Google Pixel 7] happynexuss:
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?
[Google Pixel 7] t-ryder:
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?
[Google Pixel 7] badabing2003:
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.

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.
[Google Pixel 7] ozyk100:
I was just wondering if someone has the same problem as me?

I downloaded march update and everything is like usual, extraction, patching and flashing but the flashing part lasts only 1 second, it says success, but my software remains on february update.

Tried several times, disabled Magisk modules but software doesn't change.

Would the fix from above, with flashing stock boot first, then rooting with different Magisk version apply to me to?

Pixel 7

Magisk 25.200 stable

PF 4.8.0

Platform tools 33.0.3
[Google Pixel 7] badabing2003:
Are you clicking on Flash Boot button instead of Flash Pixel Phone button?

support.zip would help (from help menu)
[Google Pixel 7] ozyk100:
I'm a f*****g retard, thank you pointing out MY mistake and for the quick response.
[Google Pixel 7] badabing2003:
No worries, we all have those moments, besides it's easy to get confused with both buttons having the word Flash in them. I just don't know how I can make it less confusing even though the tool tip clearly says it.
[Google Pixel 7] ozyk100:
Absolutely not the fault of your software since the button is huge when compared to the other buttons.

I had a brain fart and just wasn't even registering 'flash pixel phone' button.

Maybe I would have a better excuse if it was my first time using PF but I use it every month so no excuse for me!

Thanks again.
[Google Pixel 7] manjaroid:
I ran into a couple March update problems that were no fault of PixelFlasher.

First, with Platform Tools 34.0.1 I'd lose the connection in fastboot mode. 33.0.3 to the rescue. Either 34.0.0 wasn't fixed by 34.0.1 or there's a new bug.

Second, I was running Magisk Canary 25209 and patched init_boot.img couldn't be flashed. Patching worked but the file wasn't showing in PF. That's when I recalled something I scanned in a Magisk thread about a flashing issue with boot images patched by 25209.

I uninstalled Magisk and while at it updated manually. This time rooted with Magisk Canary 25206.
[Google Pixel 7] badabing2003:
Yes this combination works
[Google Pixel 7] manjaroid:
Ahhh-Ha! I missed that this morning.
[Google Pixel 7] badabing2003:
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.
[Google Pixel 7] Tirofog:
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:
[Google Pixel 7] Plasros:
Thanks so much for this tool, I finally could update my rooted Pixel 7 easily.
[Google Pixel 7] LineArc:
Can this tool be used to change IMEI?
[Google Pixel 7] LineArc:
Could this tool be used in anyway to change IMEI NUMBER?
[Google Pixel 7] badabing2003:
No
[Google Pixel 7] Jwtiyar:
hey iam on february update (panther), magisk installed and rooted, what i have to do to install march update? without losing data.
[Google Pixel 7] badabing2003:
Look at the main thread's OP or the Github, and follow basic usage.

Make sure you pay attention to any warnings you get, specially regarding Magisk / Android platform Tools versions.
[Google Pixel 7] bigw34:
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
[Google Pixel 7] t-ryder:
With the latest releases you could brick your device because those are buggy. I uploaded v33.0.3 for you.

LINK (Mega.nz)
[Google Pixel 7] Jwtiyar:
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.
[Google Pixel 7] badabing2003:
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.
[Google Pixel 7] Jwtiyar:
You mean while flashing factory images ROM then enabling varity and verififcation?
[Google Pixel 7] badabing2003:
Yes they need to be enabled while flashing, the checkboxes are just options you select, they only apply when you flash with those choices.
[Google Pixel 7] Jwtiyar:
thank you, i thought may be possible to just disable variety and verification without flashing ROM itself again, it Just wipes current ROM and disables these settings .
[Google Pixel 7] Magnivore:
Good evening super users,

I just got finished going through the guide [basic mode] for this, everything went great, though after the phone booted back up and PF detected the device it's not saying it's rooted. I redid it making sure that the patched boot image was selected just to be sure, though it still shows at not rooted. What did I do wrong, or what am I missing?
[Google Pixel 7] badabing2003:
If you actually have root, (can check with root App) the it is most likely due to not granting root access to adb shell

Point #2 in Basic Usage

If you actually have no root, it's possibly due to Magisk version used, though can't tell for sure without seeing the support.zip
[Google Pixel 7] Magnivore:
Root Checker Basic suggests I don't have root so I'm glad I have a second opinion on that. I installed Magisk fresh via PF so unless the stable version from that didn't work then I'm unsure.

re: adb shell, how do I activate that? I'm sure I'm overlooking something obvious but I can't seem to find it.
[Google Pixel 7] badabing2003:
You can only do that once you are rooted., see the link I provided.

Provide support.zip and I'll check it out.
[Google Pixel 7] Magnivore:
Here you are, thank you for the help.
[Google Pixel 7] badabing2003:
The problem is the Magisk version.

PF is warning you about it.

WARNING! Problematic Magisk Manager Version: 981ccabb:25210 is installed. Advised not to use this version.

You then installed Magisk Stable 25200 which is good.

But would need to flash the patched you created with it.

One that starts with f7771421

Just select it and click on Flash Boot button (not Flash Pixel Phone button)
[Google Pixel 7] Magnivore:
That seems to have done it, at least according to the root checker. Thank you for the help!

For my own knowledge's sake, what did I do wrong exactly and what caused the issue? I followed the primary guide to the T.
[Google Pixel 7] badabing2003:
You used a Magisk version that is known to have problems patching a stock boot.

PF warned you but you used it anyways ;)

Then when you finally switched to stable Magisk that works, you forgot to flash it so that you get root.
[Google Pixel 7] Magnivore:
😰 You know me so well. I definitely did those things. For the Magisk thing, I took that as the usual software complaints of it saying it's out of date but would work anyway.
[Google Pixel 7] badabing2003:
Lol,

I don't know you. The logs tell me what went on.
[Google Pixel 7] badabing2003:
New Release:

Apr 10, 2023 v4.8.2 release

Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.

Display USNF related flag values when selecting a device.

Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.

Link to download Google USB Driver is added in the help menu.

Added more visual troubleshooting event flows.

Install APK now defaults to Non Market.

Added Install APK cancel option.

You can now select an app in package manager and right click to launch it on the phone.

Minor bug fixes and other improvements.
[Google Pixel 7] Element1860:
I am on February image and there are "only" OTA updates for March and April. I don't find the necessary info on how to update a simple OTA. What am I missing? Pixel flasher denies this zip file. A simple reference would be highly appreciated. Thanks

Edit: I am using Magisk 25.2 and android platform tools 33.0.3 which should be fine imo.

Edit2: Am I able to skip March update and flash April directly?
[Google Pixel 7] badabing2003:
Firmware download page is linked in the help menu as well as the main screen next to selecting the firmware, and it is also in the usage guide. With all that I'm surprised you still couldn't find it.

In any case, yes you can flash the April firmware directly.
[Google Pixel 7] Element1860:
I am sorry. I think there is something off with the translation. I switched to English (i am german) and then the April update showed while i hasn't been shown before. So changing the site to English did the trick.
[Google Pixel 7] badabing2003:
New Release:

Apr 27, 2023 v4.9.0 release

Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).

Support for recognizing Lineage firmware and extracting / patching boot.

Display 32 bit capabilities of the device.

Utilize New Magisk 26.x flags as needed (patch support for more devices).

Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.

Partition Manager can now list the partitions even if the devices is not rooted.

Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).

Added Open Folder button to open a file browser to the directory of the selected boot image.

Added Reboot to Download button (Odin mode).

Added Reboot to Safe Mode button.

Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.

Various additional validation checks.

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

Apr 30, 2023 v4.10.0 release

Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.

Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)

Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.

Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.

Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
[Google Pixel 7] badabing2003:
New Release:

May 19, 2023 v5.0.0.1 release

#75 Bug fix, when device is in bootloader, type error.

#74 Added Support for Pixel 7a (lynx)

Configuration option to define the file manager to use on Linux (default: Nautilus)

Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).

Support for additional types of Factory / ROM files.

Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)

New advanced option, ability to choose the patching method (with recommendations).

Added Recovery Image patching option.

Advanced option to enable the use of busybox shell (default off).

Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.

Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.

Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)

Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.

#66, when checking the patched files internal SHA1, provide a confidence rating.

Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.

Added fastbootd testing to Dry Run.

Added Github actions to build all the targets on Github.

Code refactoring, bug fixes and improvements
[Google Pixel 7] DallasCZ:
Hello, i have the latest software update on my P7 and i downloaded pixelflasher and adb platform tools. I also enabled usb debuging. The problem is, when i run the pixelflasher on my win 11 the adb connected devbices line is grayed out.

When i use command line and type adb devices i can see the device.

Please help. Thank you
[Google Pixel 7] badabing2003:
Can you provide support file please.

Big support button or from help menu.
[Google Pixel 7] DallasCZ:
here you go.
[Google Pixel 7] badabing2003:
2023-05-21 19:21:09 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

Download 33.0.3 and use that

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 Pixel 7] DallasCZ:
now it works..thank you very much.
[Google Pixel 7] badabing2003:
New Release:

May 25, 2023 v5.1.0.0 release

Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3

Temp workaround to avoid selecting root method patching when Magisk Delta is detected.

Nicer looking / clearer manual patching dialog.

When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.

Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.

Boot image list box now displays the applied PixelFlasher patch method.

Auto-resize boot image list box columns for better readability.

Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.

#77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).

Bug fixes and improvements.

Update:

Patch Release:

v5.1.0.1 release

Exception handling when device is not in the listed Pixel devices.

v5.1.0.2 release

Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
[Google Pixel 7] SirRhor:
Trying to process firmware for Panther, I get this:

2023-05-26 15:13:35 PixelFlasher 5.1.0.2 Processing firmware file ...

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

Traceback (most recent call last):

File "Main.py", line 1255, in _on_process_firmware

File "modules.py", line 500, in process_file

File "runtime.py", line 1095, in check_archive_contains_file

File "runtime.py", line 1117, in check_zip_contains_file

File "zipfile.py", line 913, in read

MemoryError

Using version 5.1.0.2
[Google Pixel 7] badabing2003:
Can you please provide support file?

It works for me (ie processing the panther firmware)
[Google Pixel 7] SirRhor:
I thought of something. I am trying to flash older firmwares for a Pixel 7 and 7 Pro LOCKED to Verizon, therefore no luck unlocking the bootloader, so PixelFlasher would no work in this case, right?
[Google Pixel 7] badabing2003:
When flashing OTA images through sideload, the bootloader does not need to be unlocked,

However I don't know if OTA allows downgrade.
[Google Pixel 7] SirRhor:
Yes, unfortunately I can downgrade from OTA either.

I however downgraded PixelFlasher to 4.10.0.0 and the firmware processing went fine. On 5.0.0.1 and later, the processing shows the error.
[Google Pixel 7] :
Detected Unsupported firmware, with payload.bin, perhaps in a future version it could be supported
[Google Pixel 7] badabing2003:
panther-ota-tq2a.230505.002-c3d87694.zip

You're loading OTA image not a factory image.

Click on that left green link icon next to the factory image selection to open up a download page of factory image for your device.

Next version of PF will support OTA patching.
[Google Pixel 7] :
2023-05-31 18:57:29 User Pressed Ok.

Rebooting device REDACTED to bootloader ...

Waiting 10 seconds ...

2023-05-31 18:57:46 No Device is selected!

2023-05-31 18:57:46 ERROR: Unable to detect the device.

You can try scanning for devices and selecting your device (it should be in bootloader mode).

and then press the same Flash button again.

2023-05-31 18:58:57 Scanning for Devices ...

No Devices found.

PixelFlasher_2023-05-31_18h41m43s.log - BayFiles

bayfiles.com
[Google Pixel 7] badabing2003:
Is your bootloader unlocked?
[Google Pixel 7] :
Should be. Dev settings -> OEM unlock. Yet I didn't reboot the phone, just poked the slider. Hmm. I'm stuck on the bootloader screen says FASTBOOT MODE, STATUS LOCKED. Guess I can boot past this and try the process again. Unless you have a better idea.
[Google Pixel 7] badabing2003:
OEM unlock and bootloader unlock are two different things, your bootloader needs to be unlocked.

You can press on that unlock button, but be WARNED, it will wipe your phone.

You can go to the help menu | links and check any of the the guides to learn more about bootloader unlocking.
[Google Pixel 7] V0latyle:
This.

OEM Unlocking does not unlock the bootloader; it functions as a safety that allows the bootloader to be unlocked.
[Google Pixel 7] :
I hear you all. However, I cannot "fastboot flashing unlock" when the phone is booted as it just says "waiting for any device", and when I'm in Fastboot Mode I can't run ADB. So.. I donno.. help
[Google Pixel 7] badabing2003:
Switch Android platform tools to version 33.0.3

Then reboot to bootloader

and issue fastboot devices

if you see your device ID listed, then you can try the unlock.

If you don't, update your drivers (there is a download link in the help menu)
[Google Pixel 7] :
It was a driver issue. I got the official USB Google driver and all is good. Flashing now and sh!tting bricks. Thanks for your helps, hope this is the last you hear from me.
[Google Pixel 7] badabing2003:
New Release:

June 01, 2023 v5.2.0.0 release

Update build workflows

Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.

Added rules engine code to better / easier management of the UI widgets enabling / disabling.

Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.

Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
[Google Pixel 7] :
Oh awesome.. perfect timing! heh
[Google Pixel 7] badabing2003:
Bug Fix Release:

June 01, 2023 v5.2.0.1 release

Bug fix #78 Error when opening a shell console on Linux / Mac
[Google Pixel 7] badabing2003:
Update:

June 03, 2003 v5.2.0.2 release

#76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
[Google Pixel 7] badabing2003:
New Release:

June 06, 2003 v5.3.0.0 release

Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.

PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's 😀), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.

When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.

If there was a way to pre-load odin with the extracted files, flashing could also be automated.

I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
[Google Pixel 7] mruno:
EDIT: I was able to get the "Flash Pixel Phone" button to work after reselecting & processing the firmware.

I am unable to update to the June update. I believe it may be due to this error:

Getting package com.topjohnwu.magisk path on the device ...
2023-06-14 05:53:31 ERROR: Could not get package com.topjohnwu.magisk path.
Return Code: 1.
Stdout: .
Stderr: .

Thanks for the assistance.
[Google Pixel 7] badabing2003:
That is only an indication that you have hidden Magisk or using a version of non-original Magisk the package name of which is not com.topjohnwu.magisk

That is not the issue.

Please do not filter out files from support.zip, what you sent me does not have anything regarding the problem you are reporting, which honestly is quite vague.
[Touch Pro, Fuze Themes and Apps] zahbaker:
Hi,For some odd reason my quick GPS does not work anymore. My TomTom is non functional as well. I have checked my data connection and it is active. Can somebody help please.

Thanks in advance.
[Touch Pro, Fuze Themes and Apps] professorman:
Mine has stopped working as well. It says its expired, and when I click to download, it says "Connection Failed. Please try again later". My connection is good, and I cant figure out what is wrong. My GPS will not pick up any signal, and nothing that uses GPS works now.
[Touch Pro, Fuze Themes and Apps] zahbaker:
Can somebody please assist?

Thnaks
[Touch Pro, Fuze Themes and Apps] zahbaker:
Hi, can somebody please advise on how to get GPS working again.

Thanks
[Touch Pro, Fuze Themes and Apps] zahbaker:
I have tried everything and yet I cannot get this damm gps to work, It seems like the gps unit is not active. Can somebody please assist me in getting the gps to start working again.

Thanks
[Touch Pro, Fuze Themes and Apps] borisku:
There are so many threats not only here in this location that handle about this theme, that i can only say:

USE THE SEARCH FUNCTION!

Greetz Boris
[Touch Pro, Fuze Themes and Apps] realist:
Quick GPS not updating/downloading

I'm having the same problem, last time I downloaded the Quick GPS update was 1/20/09, now it will not update, and I cannot get a GPS fix in google Maps, however using the program GPS Test, it does register the GPS Satelites. Please help. (Yes, I have looked in probably 20 other threads, for my phone Raphael/Fuze and others, and was not able to find a solution)
[Touch Pro, Fuze Themes and Apps] hivesnl:
Indeed there are alot of threads, without any solutions.

Although i have applied all solutions because i had this problem twice.

(Without anything that i had applied before it occured.)