📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
- Thread starter badabing2003
- Start date
Ive lost any traces of the flash.. (no log or something).
I dont know what command :/ But I can see in fastboot mode that i am on "cloudripper-1.0-9288096" and "g5300g-220923-221028-b-9229469"
So maybe at fastboot update image-panther-tq1a.230205.002.zip
Maybe I can try to execute this last command?
I dont know what command :/ But I can see in fastboot mode that i am on "cloudripper-1.0-9288096" and "g5300g-220923-221028-b-9229469"
So maybe at fastboot update image-panther-tq1a.230205.002.zip
Maybe I can try to execute this last command?
Last edited:
just launch PixelFlasher and generate support.zip file from help menu, the logs are probably there.
YEAH! Its works!
Go into fastbootd : https://www.verizon.com/support/knowledge-base-208003/
And then execute flash-all.sh:
Boot OK now. Then patched init_boot.img, after copying it, with magisk then:
Thanks for your replies!
Go into fastbootd : https://www.verizon.com/support/knowledge-base-208003/
And then execute flash-all.sh:
Code:
$ ~/platform-tools $ ./fastboot devices
ID fastbootd
$ ./flash-all.sh # without -w flag
Sending 'bootloader' (12332 KB) OKAY [ 0.379s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.056s
< waiting for any device >
Sending 'radio_b' (111200 KB) OKAY [ 3.272s]
Writing 'radio_b' (bootloader) Flashing pack version g5300g-220923-221028-M-9229469
(bootloader) Flashing partition modem_b
OKAY [ 0.190s]
Finished. Total time: 3.466s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.050s
< waiting for any device >
[...]
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_b' OKAY [ 0.013s]
Sending 'vendor_dlkm_b' (41116 KB) OKAY [ 1.176s]
Writing 'vendor_dlkm_b' OKAY [ 0.109s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 0.001s]
Finished. Total time: 220.789sBoot OK now. Then patched init_boot.img, after copying it, with magisk then:
Code:
./fastboot flash init_boot magisk_patched_47e58602.imgThanks for your replies!
No need to double post, I check the main thread and the support threads.
This does not give me enough information to understand your issue.
I don't know where you're getting this message at what point doing what?
No screenshots, no logs, no details.
I don't have 32bit windows 7 device to test and reproduce this myself, so I have to go with what you provide.
Thanks
Had to postpone working on it. Broke my laptop last night smh
Sorry about that.
I downloaded the file with .exe extension. When I double click on that , l get a prompt to run the program . Then I get the following error.
Ok I see, it does not even launch.
I'll see if I can create a workflow on Github to build 32 bit windows version (it could take some time as I'm currently quite busy). In the meantime you can try the Build it yourself steps.
Just flashed Android 14 Developer Preview with no problems.
It doesn't appear that Zygisk works on Android 14, but other than that...
It doesn't appear that Zygisk works on Android 14, but other than that...
on a mac, got everything going and it's stuck on restarting bootloader, even though it already restarted .... was trying to update from November build , with root, all magisk modules disables.
Last edited:
support.zip please, from help menu, it is sanitized and all sensitive info is removed.
You can generate now even though it happened before.
The update and flash tool itself is really cool. Thanks Dev keep up the good work 
Sorry i can't get that anymore, i have closed the laptop, anyway my pixel won't even turn on anymore.
Help
You would need your laptop to fix your phone.Sorry i can't get that anymore, i have closed the laptop, anyway my pixel won't even turn on anymore.
Help
So turn it on.
When you turn it on, remove Android Platform Tools 34.0 (it has known issues) and install 33.0.3
Then connect your phone to the laptop and scan for devices (update PF with platform tools path to 33.0.3)
Then generate support.zip so that we could help you
okay ill do that but i can't even get my 7 pro to turn on, or get into recovery, just a off screen, i know it's charged but not responding to any button press.
Where do i download the proper platform tools you listed?
Last edited:
Sometimes the screen looks off but it could be in recovery or some other state.
That is why scan is useful.
Hopefully it is only that.
if it turns into a brick, hopefully you can claim free replacement / repair from Google.
It's due to this
Google Issue Tracker
Thanks , ill try again , where do i get those proper platform toolsSometimes the screen looks off but it could be in recovery or some other state.
That is why scan is useful.
Hopefully it is only that.
if it turns into a brick, hopefully you can claim free replacement / repair from Google.
It's due to this
Google Issue Tracker
issuetracker.google.com
PS I'm pressing power and then vol up for 10-15 seconds, windows makes the chime of USB connectivity but when i scan for the device nothing shows up.
I'm in panama right now and can't get google warranty options or replacement options so i'm a bit SOL.
If the platform tools was the issue i wish i would've read more before starting
Slim2none4u
Senior Member
- Oct 28, 2011
- 882
- 546
- 49
Thanks, that's one problem solved, now to get my phone into fastboot or recovery.
Vol down + power. I can hear the windows chime notifying me of device disconnected and then a few seconds later the opposite chime of a device connected but adb devices shows nothing.
Similar threads
Top Liked Posts
-
5
Downloaded 25206, uninstalled 25210, so of course lost root. Installed 25206, rebooted with previously patched (25206) February boot.img, did direct install, enabled modules, regen'd the Deny list, all good. PF now worked fine, patched and flashed rooted March image. All good!!
Delta may indeed work well, and deserves a look....but since 25206 is still working OK, will stick with it for now.
Thanks, much appreciated, guys.1 -
6
That's not how you do it, don't just get the adb and fastboot files, unpack the Android Platform Tools 33.0.3 (not 34.0.1) and when you point PF where it is, point where adb and fastboot are , the other files in there are not decoration, they need to be there.
Then follow the basic usage guide in the main thread OP6
When you unzip the Android Platform Tools
Make sure you select the folder that has the adb and fastboot in it, not the parent folder that says Platform Tools.
Code:ERROR: The selected path \\Ds\ds\Downloads\platform-tools_r33.0.3-windows does not have adb and or fastboot6New 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.
5
Downloaded 25206, uninstalled 25210, so of course lost root. Installed 25206, rebooted with previously patched (25206) February boot.img, did direct install, enabled modules, regen'd the Deny list, all good. PF now worked fine, patched and flashed rooted March image. All good!!
Delta may indeed work well, and deserves a look....but since 25206 is still working OK, will stick with it for now.
Thanks, much appreciated, guys.4Just want to add my thanks for making this excellent tool available. I've used it several times now with no issues. It really takes the stress and drama out of keeping my devices up-to-date while keeping root.
Thank You -
118
DESCRIPTION
As the name suggests this is an application to flash (update) Pixelâ„¢ phones (possibly all Googleâ„¢ made phones/tablets, YMMV.)
PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence many of its features can be used on non Pixel devices as well. (YMMV).
The executable is self contained and does not require Pythonâ„¢ to be installed on the system.
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.
- 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).
Prerequisites
- Android SDK Platform-Tools.
- Android Pixel phone factory image.
- Bootloader unlocked phone (see excellent guide links in credits section below).
Installation
PixelFlasher doesn't have to be installed, just double-click it and it'll start.
Check the releases section for downloads.
Supported platforms
- Windows
- MacOSX
- Linux (see this if you're having issues with a Linux build.)
Usage
Basic Mode
- First thing to do is select Androidâ„¢ Platform Tools, if Androidâ„¢ Platform Tools is already in your PATH environment, the application will detect it and pre-populate it.
Otherwise you'd have to select where it is installed.
You can download the lastest Androidâ„¢ Platform Tools by clicking the
next to it.
If you have multiple versions, you can select another version, although it is best to always use the most recent version (The selected version will be identified and displayed.)
If you already have your phone connected to the PC, the application will detect all connected devices
(in adb, fastboot, sideload, recovery modes) and populate the combo box (2).
Otherwise connect your phone to your PC, and hit the Scan button and then select your device. - Select your device from the list in the combo box. The following information about the connected device is displayed.
- (1st field) Rooted devices will be identified with a checkmark ✓. Note: If you want PixelFlasher to detect root, or automatically use Magisk to patch boot.img, you need to grant root permissions to shell in Magisk.
- (1st field) Non-Rooted devices will be identified with a ✗.
- (1st field) Devices in fastboot mode will be identified with a ? (in fastboot mode, root status cannot be determined).
- (2nd field) (adb), (f.b), (sid) or (rec) to indicate connection mode adb / fastboot / sideload / recovery.
- (3rd field) Device ID.
- (4th field) Device hardware.
- (5th field) Current running firmware (in fastboot mode current firmware cannot be determined).
- (1st field) Rooted devices will be identified with a checkmark ✓. Note: If you want PixelFlasher to detect root, or automatically use Magisk to patch boot.img, you need to grant root permissions to shell in Magisk.
- Next select the factory image, the application will recognize the phone model from the image name.
You can download factory images by clicking the
next to it. - Process the factory image. PixelFlasher will extract boot.img file from the factory image and populate it in the list below (5).
- Select boot.img from the list, the selected boot.img can be patched (6), or flashed (10).
- Optional: Select this option if you want to patch the boot.img with Magisk. If Magisk is not already be installed on your phone, PixelFlasher will install it for you.
Your phone does not need to be rooted to create a patched boot.img file.
This would be the typical choice for monthly updates.
This option will allow updating the phone without losing root (not even temporarily).
Note: See note above for granting root permissions to shell.
Whether the phone is already rooted or not, the whole process is without any manual step. - If you want to flash (10) a patched boot.img select the newly added entry.
The following details are listed.-
Indicates that the selection is patched. - SHA1 is (shortened for display only) sha1 of boot.img
- Source SHA1 (shortened for display only) SHA1 of source boot.img extracted from the image (This should be the same as SHA1 of an unpatched boot.img)
- Package Fingerprint is just the filename portion of the image (without the extension).
- Patched with Magisk indicates the version of Magisk used to patch the image (if applicable).
- Patched on Device indicates the device model that performed the patching. You should always use patched images that match the model of the device that it will be flashed on.
- Date is the either the date the boot.img was extracted, or the date it was patched.
- Package Path indicates the file from which boot.img was extracted.
-
- Select the Flash Mode
- Keep Data: In this mode -w flag is removed from the flash scripts so that data is not wiped. This is commonly known as dirty flashing.
- WIPE all data: As the text suggests, this will wipe your data, use it with caution!
If this mode is selected PixelFlasher will ask for confirmation during the flashing phase. - Dry Run: In this mode, the phone will reboot to bootloader, and then mimic the flash actions (i.e. reboot into bootloader) without actually flashing anything (it prints to the console the steps it would have performed if dry run was not chosen). This is handy for testing to check if the PixelFlasher properly is able to control fastboot commands.
- Optional: Open Magisk Modules Manager and disable (uncheck) modules known to cause issues during upgrades (the below list has never caused issues for me, so I keep them enabled YMMV).
- Flash Pixel Phone This is the final step, to actually flash the phone in the selected Flash Mode.
Note: Unlike the previous versions of the PixelFlasher, all the options are dynamic, i.e. depending on what you select before clicking the Flash button, there is no more concept of prepared package. PixelFlasher will first present you the selected options and ask for your confirmation if you want to proceed with flashing.
Expert Mode
To enable the export mode use the File Menu | Advanced Configuration and select Enable Advanced Options
In this mode the following additional options are exposed (green bounding boxes), below notes are more for enumeration than a guide, as they should be trivial and obvious to an expert.
- Option to Change the Active Slot (the inactive slot is automatically selected).
Option to reboot to Recovery. - Options to Lock / Unlock bootloader, Option to disable Magisk modules when bootlooping.
- Apply Custom ROM. This replaces the factory ROM image with the selected file.
PixelFlasher extracts boot.img from the ROM image and displays below for selection or patching. Please make sure to read the documentation of the chosen ROM, as each custom ROM instructions could be different.
To be clear, this is what PixelFlasher does internally when this mode is selected, please understand it, and don't use it if the selected ROM guide does not fit the bill. You've been warned!- Keeps stock bootloader and radio images.
- Replaces the stock ROM image with the selected custom ROM image.
- Flashes in the chosen Flash Mode just like a stock image, i.e. bootloader, custom ROM and radio images in the original order that they were in the stock firmware.
- Patching boot.img can be performed if the option is selected. You can select any of the listed boot.img.
- Flash Mode is similar to basic flash mode described above in step 7.
- Custom Flash. select this to switch from flashing a Factory Image to flashing a single file.
- Browse to select a a valid image file (.img or .zip). Or select a boot.img from the list above and click on the paste button to paste the selected boot.img into the file selection. Choose the dropdown to select image type.
- boot (can be flashed to Live or boot) - Expected file type .img
- bootloader - Expected file type .img
- dtbo - Expected file type .img
- product - Expected file type .img
- radio - Expected file type .img
- recovery - Expected file type .img
- super_empty - Expected file type .img
- system - Expected file type .img
- system_ext - Expected file type .img
- system_other - Expected file type .img
- vbmeta - Expected file type .img
- vbmeta_system - Expected file type .img
- vbmeta_vendor - Expected file type .img
- vendor - Expected file type .img
- vendor_boot - Expected file type .img
- vendor_dlkm (the device will be put into fastbootd mode during this operation) - Expected file type .img
- image - Expected file type .zip
- SIDELOAD - Expected file type .zip
Select the appropriate flash options. Note: For Tensor devices (Pixel 6, Pixel 6a, Pixel 6 Pro, Pixel 7, Pixel 7 Pro) When Flash to both slots option is selected, Pixelflasher flashes each slot individually to overcome a Google bug that fails with the option --slot=all
Credits
- First and foremost Magisk by John Wu which made rooting Pixelâ„¢ phones possible, without it none of this would have mattered.
- Big thanks to [ryder203], [t-ryder] for his valuable ideas, feedback and testing. Your contributions are very much appreciated.
- [Homeboy76] and [v0latyle] at xda for their excellent guides [here and here] on Pixelâ„¢ series phones. This program could not have been possible without their easy to follow guides.
I strongly encourage all beginners to follow those guides rather than use this program, it is important to understand the basic steps involved before diving into one click tools or advanced tasks. - Marcel Stör's nodemcu-pyflasher source code which jump started my introduction to wxPython and eventually this program.
- JackMcKew for pyinstaller Github Actions.
- Endless counts of xda members and their posts that tirelessly answer questions and share tools. Too many to enumerate.
Disclaimer
Code:******************************************************************************* PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE USING THIS PROGRAM AND/OR ATTEMPTING ANY MODIFICATIONS ON YOUR DEVICE. THIS PROGRAM ASSUMES THAT YOU ALREADY KNOW HOW TO AND HAVE ALREADY UNLOCKED YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, AND KNOW HOW TO USE ANDROID SDK PLATFORM-TOOLS, ETC. THIS TOOL IS SIMPLY MY QUICK WAY OF UPDATING THE FIRMWARE WHILE ROOTED WITH MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE. MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY IF YOU LOSE YOUR DATA OR BRICK YOUR DEVICE. THE TOOL I SHARE HAVE WORKED FOR ME, BUT THAT DOESN'T MEAN THAT YOU MAY NOT RUN INTO PROBLEMS. **BACKUP YOUR DATA.** *******************************************************************************
No Donation
I've been asked quite few times about donation, (here, here ... just to list a few).
I'll put it here so that my stance is clear.
This program will remain totally free, ad free, even donation free, it's my way to give a little back to the community that has given me years of support and joy.
You can contribute by helping the next newcomer to learn the ropes and navigate through the maze of information.8PixelFlasher 4.0.0 pre-release:
Sep 25, 2022 v4.0.0 pre-release
- New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
See Patching flow chart for details. - New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
- New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
- New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
- New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature). - New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
- New spinner to indicate PixelFlasher activity.
- Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
- PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images. - PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
This is just an extra validation. - Code cleanup / refactoring, adding more validations and exception handling.
- Print debug details when encountering non compliant Magisk modules.
- Firmware link now takes you to the device's download page instead of just the general download page.
- To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
- Allow sideload even if bootloader is locked.
7
Here's a complete flow diagram of the patching process, hope it makes it clearer.
Drive UI and generate patched boot.img box is a new feature that will be available in 3.8.0 (hopefully to be released today), it uses UIAutomator to drive the UI and not require user interaction, the user can still decide to do it manually.
Without su permissions on adb shell, PixelFlasher will report that the device is not rooted and will follow the flow of un-rooted.7New release:
July 18, 2022 v3.4.0 release
- Improvements to the boot extraction / categorization.
- Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.
- Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
7
Thanks for your consideration, appreciated.
Like I mentioned to other such queries, no donation is necessary, this is a payback to the community that has given me years of support and joy.
If you want to do something good, help others who're just starting or struggling navigating through the maze of information.
