📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

Search This thread

nibera

Senior Member
Apr 19, 2008
237
29
I tried to load the firmware, but it says:

No previous flashable package is found for the firmware:
C: \ Users \ Nicola \ Desktop \ Service Root Pixel 6 Pro \ Service Pixel 6 pro \ raven-tpp2.220218.010 ANDROID 13 DEVELOPER PREVIEW 2 \ raven-tpp2.220218.010-factory-79bf5fe3.zip
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
I tried to load the firmware, but it says:

No previous flashable package is found for the firmware:
C: \ Users \ Nicola \ Desktop \ Service Root Pixel 6 Pro \ Service Pixel 6 pro \ raven-tpp2.220218.010 ANDROID 13 DEVELOPER PREVIEW 2 \ raven-tpp2.220218.010-factory-79bf5fe3.zip
That's ok, all it means is that you have not previously created a package.

if you create a package from it, switch to another firmware, and then come back to it, it will detect that you have a package and let you know.

That message is just info, not an error, and if it finds a previous package, it will tell you about the options you had selected, like custom rom, patch ...
 

nibera

Senior Member
Apr 19, 2008
237
29
That's ok, all it means is that you have not previously created a package.

if you create a package from it, switch to another firmware, and then come back to it, it will detect that you have a package and let you know.

That message is just info, not an error, and if it finds a previous package, it will tell you about the options you had selected, like custom rom, patch ...
Perfect, the .zip firmware after downloading do I have to unpack it and load the zip inside the pixel flasher or do I just have to load the zip without unpacking it?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
Perfect, the .zip firmware after downloading do I have to unpack it and load the zip inside the pixel flasher or do I just have to load the zip without unpacking it?
Nope, you don't even need to put it in the same folder, you can leave it anywhere in your system, just select it in the UI and it would take care of the rest, same goes for Android platform tools.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429

nibera

Senior Member
Apr 19, 2008
237
29

nibera

Senior Member
Apr 19, 2008
237
29
raven-sp2a.220405.004-factory-bce807a6.zip (ANDROID 12.1 PATCH APRILE)
raven-s3b1.220318.003-factory-b4b29ec4.zip ( ANDROID 12 BETA 2 QPR3)
raven-tpp2.220218.010-factory-79bf5fe3.zip ( ANDROID 13 DP2)

Can I install any of these firmware for the Pixel 6 Pro?

obviously I have to unlock the bootloader first, right?
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
raven-sp2a.220405.004-factory-bce807a6.zip (ANDROID 12.1 PATCH APRILE)
raven-s3b1.220318.003-factory-b4b29ec4.zip ( ANDROID 12 BETA 2 QPR3)
raven-tpp2.220218.010-factory-79bf5fe3.zip ( ANDROID 13 DP2)

Can I install any of these firmware for the Pixel 6 Pro?

obviously I have to unlock the bootloader first, right?
Short answer: Yes

Long Answer, PixelFlasher is a UI layer on top of underlying adb / fastboot commands, yes it does checks and validations, it automates steps (you don't have to place files in specific locations, nor do you have to remember commands and arguments to do something), it does the patching for you, but everything it does that interacts with the phone is through adb / fastboot commands, so in general if the manual steps to achieve something can be done through adb / fastboot, then it can also be done through PixelFlasher UI.

Just make sure you follow the Google recommendation when switching between beta, Android 13 and Android 12.
For example, if it requires a wipe, then make sure you select the wipe data option.
 

nibera

Senior Member
Apr 19, 2008
237
29
Short answer: Yes

Long Answer, PixelFlasher is a UI layer on top of underlying adb / fastboot commands, yes it does checks and validations, it automates steps (you don't have to place files in specific locations, nor do you have to remember commands and arguments to do something), it does the patching for you, but everything it does that interacts with the phone is through adb / fastboot commands, so in general if the manual steps to achieve something can be done through adb / fastboot, then it can also be done through PixelFlasher UI.

Just make sure you follow the Google recommendation when switching between beta, Android 13 and Android 12.
For example, if it requires a wipe, then make sure you select the wipe data option.
OK thanks for all the info given, I'll try to flash android 13 dp2. thank you
 

nibera

Senior Member
Apr 19, 2008
237
29
Hi, can I install the customize roms, type:
PEP-raven-20220412-0120 PIXEL EXPERIENCE PLUS.zip
or
raven-factory-22304000 CALYXOS.zip

1) unlock the bootloader via adb commands (fastboot flashing unlock)
2) back to android 12.1 with april patch (now I'm on android 13 dp2) via pixel flasher
3) I select the rom and platform tools
4) I prepare the package
5) Flash Pixel Phone

I am attaching photos if I have selected everything correctly.

right ?
 

Attachments

  • Immagine 2022-04-13 140737.png
    Immagine 2022-04-13 140737.png
    64.6 KB · Views: 34

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
Hi, can I install the customize roms, type:
PEP-raven-20220412-0120 PIXEL EXPERIENCE PLUS.zip
or
raven-factory-22304000 CALYXOS.zip

1) unlock the bootloader via adb commands (fastboot flashing unlock)
2) back to android 12.1 with april patch (now I'm on android 13 dp2) via pixel flasher
3) I select the rom and platform tools
4) I prepare the package
5) Flash Pixel Phone

I am attaching photos if I have selected everything correctly.

right ?
Unfortunately there is no one size fit all answer when it comes to custom ROMs, each ROM steps are specific to that ROM, some need custom recovery, and things done through custom recovery, some provide rooted boot, others don't, what partitions they write ...

That is exactly why advanced mode has that red warning, you'd have to follow the guides posted by the ROM maker and know what you're doing.

I'm almost certain that the options you have selected in your screenshot won't work, you have specified a custom ROM where you need to specify a factory image.
It is important that a true factory image is selected because PixelFlasher processes the contents of a Factory image, expects certain files in there, parses the scripts, extracts boot.img ...
I doubt that the custom ROM has the same fileset (ie full factory image along with flashing scripts), if it were, then probably the flashing guide of the ROM would have been just unpack and run the flash script.

I'll give you an example of statix_oriole-SNOWCONE-20220226-img.zip
This is an equivalent of image-oriole-sp2a.220405.004.zip (which is a file found inside the zip of the factory image), basically to flash this ROM, you follow the factory flashing steps (which would include flashing the bootloader and radio first) and then instead of flashing (update) image-oriole-sp2a.220405.004.zip you flash statix_oriole-SNOWCONE-20220226-img.zip.
The boot is not patched
But this is specific to this ROM, maybe others do the same thing, but you'd have to check their guides and understand the steps.

If you wanted to flash the statix ROM with PixelFlasher.
- You select Pixel firmware for your phone (example: oriole-sp2a.220405.004-factory-f560807e.zip for Pixel 6)
- You select the ROM next where its says Apply Custom ROM
- You choose if you want to patch or not
- Prepare package, then flash.

But please read the custom ROM guide, understand the steps.
 

nibera

Senior Member
Apr 19, 2008
237
29
Unfortunately there is no one size fit all answer when it comes to custom ROMs, each ROM steps are specific to that ROM, some need custom recovery, and things done through custom recovery, some provide rooted boot, others don't, what partitions they write ...

That is exactly why advanced mode has that red warning, you'd have to follow the guides posted by the ROM maker and know what you're doing.

I'm almost certain that the options you have selected in your screenshot won't work, you have specified a custom ROM where you need to specify a factory image.
It is important that a true factory image is selected because PixelFlasher processes the contents of a Factory image, expects certain files in there, parses the scripts, extracts boot.img ...
I doubt that the custom ROM has the same fileset (ie full factory image along with flashing scripts), if it were, then probably the flashing guide of the ROM would have been just unpack and run the flash script.

I'll give you an example of statix_oriole-SNOWCONE-20220226-img.zip
This is an equivalent of image-oriole-sp2a.220405.004.zip (which is a file found inside the zip of the factory image), basically to flash this ROM, you follow the factory flashing steps (which would include flashing the bootloader and radio first) and then instead of flashing (update) image-oriole-sp2a.220405.004.zip you flash statix_oriole-SNOWCONE-20220226-img.zip.
The boot is not patched
But this is specific to this ROM, maybe others do the same thing, but you'd have to check their guides and understand the steps.

If you wanted to flash the statix ROM with PixelFlasher.
- You select Pixel firmware for your phone (example: oriole-sp2a.220405.004-factory-f560807e.zip for Pixel 6)
- You select the ROM next where its says Apply Custom ROM
- You choose if you want to patch or not
- Prepare package, then flash.

But please read the custom ROM guide, understand the steps.
Hi, in fact I have seen that each rom has its installation flasher, for example to install this rom PEP-raven-20220412-0120 PIXEL EXPERIENCE PLUS.zip I ran the command (fastboot update -w name.zip) but first I brought through the google tools from android 13 dp2 to android 12.1 april patch, then o had to unlock the bootloader (fastboot flashing unlock) and install the rom as described above, everything is ok.

to return stock with google firmware can i use your tools?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
Hi, in fact I have seen that each rom has its installation flasher, for example to install this rom PEP-raven-20220412-0120 PIXEL EXPERIENCE PLUS.zip I ran the command (fastboot update -w name.zip) but first I brought through the google tools from android 13 dp2 to android 12.1 april patch, then o had to unlock the bootloader (fastboot flashing unlock) and install the rom as described above, everything is ok.

to return stock with google firmware can i use your tools?
Again you have to check the custom ROM guides to see what steps (if any) need to be taken before reverting back to stock.
For some custom ROMs you do need to perform special revert actions otherwise you risk bricking your phone if you go ahead and blindly flash stock firmware, of course this is specific to each ROM.

Once you do those steps, or if there are no revert steps, you probably can just use PixelFlasher to flash stock firmware.
 
  • Like
Reactions: catseyenu

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
@badabing2003 , I really like your work, well done, I couldn't find a donation link, can you please provide me with that. Thanks and keep up the good work.
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.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,849
2,429
New Release:
April 17, 2022 v2.3.0 release
  • Optional automatic check for updates feature.
  • Added help menu links to:
    - Report an issue
    - Feature Request
    - PixelFlasher Project Page
    - PixelFlasher Community (Forum)
    - Homeboy76's Guide
    - V0latyle's Guide
    - Open Configuration Folder
    - Check for New Version
  • Icons for menu items.
  • Link to download Pixel Firmware.
  • Link to download Android Platform Tools.
  • Unlock Bootloader.
  • Lock Bootloader.
  • SOS (experimental) - disable Magisk modules to get out of bootloop.
  • Additional flashing options:
    - product
    - system
    - system_ext
    - system_other
    - vbmeta_system
    - vbmeta_vendor
  • Added sideload flashing option.
  • Updated documentation.
  • Further improved console messages for troubleshooting.
  • Linux build using Github Actions.
  • Manual build for Kali Linux.
 

Top Liked Posts

  • 3
    Mod translation:
    I can't boot the phone

    Greetings. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:

    4. Use the English language.

    We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

    Thank you for your cooperation, and have a pleasant day.

    -Regards: Badger50
    3
    @Omarqaissy
    Please pay attention to the XDA forum rules.
    Specifically #4 regarding language.

    4. Use the English language.

    We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

    Obviously I can use a translator myself to understand what you are asking, however the onus is on you not me.

    To answer your questions.
    I can't get the phone to turn on developer mode and factory unlock. The problem when installing it requires a factory unlock

    Is there a way to contact you to find a solution to the problem?

    Sorry, that is beyond the scope of PixelFlasher, if you can't get your phone unlocked, you can't use PF for rooting.
    Contacting me directly won't help.
    3
    لا يمكنني تشغيل الهاتف لتشغيل وضع المطور وفتح قفل المصنع. تتطلب المشكلة عند تثبيته فتح قفل المصنع

    هل هناك طريقة للاتصال بك لإيجاد حل للمشكلة؟

    Mod translation:
    I can't boot the phone to turn on developer mode and factory unlock. The problem when installing it requires a factory unlock

    Is there a way to contact you to find
    I'm not sure what performance has to do with anything, I assume it is lost in translation.

    To learn how to do things, it's best you follow one of the guides, it teaches all the manual steps.
    There are few excellent guides that you can find in PF help menu under links.
    Definitely all those guides show you the manual steps you need to do on the phone to get it OEM unlocked and then the bootloader unlocked, bootloader unlocking can also be done in PF, but the manual ones on the phone like OEM unlocking, setting up developer mode and enabling adb, all those are per-requisities that need to be done manually and are covered it the guides.

    a solution to the problem?

    In the future when I ask for support.zip, please click on the big Support button and pass me the generated zip file.

    1- You are using the OTA file, you need to use the Factory image
    2- You need to have OEM unlocked and bootloader unlocked if you want to root
    3- if you just want to flash OTA and don't want to root, then select custom flash and choose your OTA file and select SIDELOAD from the dropdown choice.
    Hey Badabing2003, I don't think PF is going to help the person you're messaging with. They need to find "rooting 101" and learn everything from scratch. Probably isn't a good idea for them to learn how to root with an expensive device either, they should definitely start with an older phone if they have one. Everyone has to start somewhere but they're in the wrong thread and need to do a little more searching. Good job with the advice and patience though.
    2
    This is what appears when working through the official website
    In the future when I ask for support.zip, please click on the big Support button and pass me the generated zip file.

    1- You are using the OTA file, you need to use the Factory image
    2- You need to have OEM unlocked and bootloader unlocked if you want to root
    3- if you just want to flash OTA and don't want to root, then select custom flash and choose your OTA file and select SIDELOAD from the dropdown choice.
    1
    أنا مستخدم جديد ولا أعرف الأدوات. هل هناك طريقة لشرح طريقة عمل الأسلوب في الأداء
    Huh ?
  • 6
    I follow your instructions but no way to work .please see the support
    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 fastboot
    6
    I create a new folder into the Platform tools and I put only the adb and the fast boot .
    Since that is the first time and I'm already rooted from January without updating till now I will use for 1st time this tool . Do i have to care for something else ?
    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 OP
    6
    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.
    5
    @xzenx1234x Please stop posting about this here, I told you already that this is off topic, you started a thread about it, why are you still posting it here?
    4
    yes, and on github too. Wasn't sure if the table in the middle will apply just the boot or the whole image and found the "Flash Boot" button or root process undescribed. Also manual describes "Flash Pixel Phone" button as it flashing boot only in all the points, so i'm not sure if it does the OTA update.
    If you follow the number sequence in basic usage, that is the main usage, everything else is additional features / tools.
    You can learn about what they do by hovering to show tooltip.
    PF needs a wiki for all the added tools / features aside from the basic usage, and it's on my TODO list, but it's low on the list because it is expected that the advanced features are used by experienced users who intuitively know what they are about.

    Flash Boot just flashes the selected boot file in the middle screen, it does not flash full factory.
    For full factory flashing you want to use the big Flash button above the console.

    OTA flashing can be done by enabling the advanced settings and then using custom flash with SIDELOAD selected.
    But that is intentionally in advance settings because you're have to know what to do, the OTA image is not patched, and you have to flash a patched boot as a follow up step.
  • 118

    PF_promo-banner_v4.png

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

    Prerequisites​

    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

    1. 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 Image of link 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.
    2. 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.
        Image of shell root access
      • (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).
    3. Next select the factory image, the application will recognize the phone model from the image name.
      You can download factory images by clicking the Image of link next to it.
    4. Process the factory image. PixelFlasher will extract boot.img file from the factory image and populate it in the list below (5).
    5. Select boot.img from the list, the selected boot.img can be patched (6), or flashed (10).
    6. 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.
    7. If you want to flash (10) a patched boot.img select the newly added entry.
      The following details are listed.
      • Image of patched-boot 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.
    8. 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.
    9. 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).
    10. 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 Image of PixelFlasher GUI
    Image of PixelFlasher GUI

    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.

    1. Option to Change the Active Slot (the inactive slot is automatically selected).
      Option to reboot to Recovery.
    2. Options to Lock / Unlock bootloader, Option to disable Magisk modules when bootlooping.
    3. 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.
    4. Custom Flash. select this to switch from flashing a Factory Image to flashing a single file.
    5. 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.
    8
    PixelFlasher 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
    Forgive me if I've asked this before....does ADB shell need root access in order for Pixel Flasher to patch the boot image via Magisk?

    In other words, will the automatic patching work on unrooted devices?
    Here's a complete flow diagram of the patching process, hope it makes it clearer.

    1662558670612.png


    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.
    7
    New 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
    @badabing2003 , I really like your work, well done, I couldn't find a donation link, can you please provide me with that. Thanks and keep up the good work.
    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.