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

[badabing2003]

Hey I unlocked my bootloader, downloaded magisk using this tool, and the latest rom. I patched the bootloader. I thought I followed instructions correctly, it did seem to flash the patched bootloader...

but now I'm stuck in fastboot and I've tried every single method I can find to recover the device...

Any help?

please provide support file so that I can take a look.

 

[Doug D]

please provide support file so that I can take a look.

Thanks but I ended up messing with it a bunch.

What eventually worked for me was flashing developer preview and then flashing 13 again. Not rooted yet, but I'll try again another time!

 

[dilligaf56]

Thanks for you support and kind words.
No donation required.
You can read about it in the main thread's OP

Read and noted. Thanks again, much appreciated!

 

[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.

 

[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

 

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

 

[DigiPooch]

Hey guys, I've tried finding somewhere throughout the thread where this was asked but I'm not seeing it and likely I'm just blind so apologies in advance... but i initially rooted with magisk using the 7 pro image on like the January update i believe. My question is should i use the current 7 pro factory cheetah image or the 6 pro raven image to update since I'm currently using 6 pro but technically on 7 pro patched image? I was going to use the 6 pro image to retain root and data, however I get the Sha mismatch when trying to patch the 6 pro image in pf, however when I try to patch the 7 pro image I do not receive the Sha mismatch and it will allow me to proceed but I'm too much of a chicken to pull the trigger on it yet without confirming which to use. Thank you for the insane amount of hard work with all this and any help pointing me in right direction.

 

[badabing2003]

Hey guys, I've tried finding somewhere throughout the thread where this was asked but I'm not seeing it and likely I'm just blind so apologies in advance... but i initially rooted with magisk using the 7 pro image on like the January update i believe. My question is should i use the current 7 pro factory cheetah image or the 6 pro raven image to update since I'm currently using 6 pro but technically on 7 pro patched image? I was going to use the 6 pro image to retain root and data, however I get the Sha mismatch when trying to patch the 6 pro image in pf, however when I try to patch the 7 pro image I do not receive the Sha mismatch and it will allow me to proceed but I'm too much of a chicken to pull the trigger on it yet without confirming which to use. Thank you for the insane amount of hard work with all this and any help pointing me in right direction.

• You're posting in pixel 6 pro forum so I assume your phone is pixel 6 pro. If it is not, stop right there.
• Never, ever flash factory image of another device unless you are prepared to turn your expensive device into a paperweight. So if your phone is 6 pro, you want 6 pro firmware to upgrade.
• You haven't stated if you are on official firmware or beta, upgrading within the same line is no problem, switching between the two might involve a wipe, depending what you have and what you're changing to.
• Everything that was said above has nothing to do with rooting, that's another thing.

Rooting typically involves patching boot.img file of the same firmware your device is running and flashing that, which means if you are upgrading to standard pixel 6 pro May release, you would patch the boot file of that may release.
However with Pixel 6 series with some firmware versions (specially the beta releases) patching the boot.img to get root was broken, and you needed to patch init_boot or boot extracted from pixel 7 series firmware, but just that, not the entire firmware.

Before you go any further, gather the details and post back so that proper instructions could be provided.
Support file from PF could provide us the details.

 

[DigiPooch]

Thanks for super quick reply. Should have specified currently on beta build T2B2.221216.006 with 6 pro device and I used the root workaround pulling the 7 pro boot.img flashed to my 6 pro. I didn't know if that was the possible reason for the mismatch error message in PF when trying the latest 6 pro image that matches my phone from the link within the app for the factory zip, but no error when doing same exact thing but with the 7 pro version if that makes sense. Sounds like I wouldn't need to use 7 pro image again for any reason here on out, so mainly just the matter of reason I'm seeing the mismatch or whether or not it's okay to run with a mismatch as it says may be caused by compression. Attached support file of attempt to patch 6 pro boot img. Thanks again

 

[badabing2003]

Thanks for super quick reply. Should have specified currently on beta build T2B2.221216.006 with 6 pro device and I used the root workaround pulling the 7 pro boot.img flashed to my 6 pro. I didn't know if that was the possible reason for the mismatch error message in PF when trying the latest 6 pro image that matches my phone from the link within the app for the factory zip, but no error when doing same exact thing but with the 7 pro version if that makes sense. Sounds like I wouldn't need to use 7 pro image again for any reason here on out, so mainly just the matter of reason I'm seeing the mismatch or whether or not it's okay to run with a mismatch as it says may be caused by compression. Attached support file of attempt to patch 6 pro boot img. Thanks again

Sorry,
Could you please upgrade PF to the latest 5.1.0.2, as the one you're using had a exception and I couldn't get device details.
Please scan with it while your device is connected.

 

[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.

 

[badabing2003]

Bug Fix Release:
June 01, 2023 v5.2.0.1 release

• Bug fix #78 Error when opening a shell console on Linux / Mac

 

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

 

[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.

 

[ykjae]

@badabing2003 I'm sure I'm missing something simple. I've been rooting my devices since forever. I've recently took the latest 6pro security update and can't get the boot image to boot. I'm using the 7pro boot image and pixel flasher. Any suggestions?

 

[badabing2003]

@badabing2003 I'm sure I'm missing something simple. I've been rooting my devices since forever. I've recently took the latest 6pro security update and can't get the boot image to boot. I'm using the 7pro boot image and pixel flasher. Any suggestions?

I suspect your Magisk version, which are you using, some versions have issues.
Support file would tell me the details if anything is going wrong.