Question PixelFlasher for Google Pixel 6 Pro Support Thread.

Search This thread

banshee28

Senior Member
Aug 31, 2010
236
40
Wait...are you still on A13 Beta? Still, there's no reason to go back to A12.
Yes, on 13 Beta on b slot. I think my a slot maybe corrupt somehow. I also did not wipe data when going from 12 to 13 and had lots of issues even getting this 13 beta to work. Crazy I know. Now I am ready to wipe everything and start over. Thanks!
 

badabing2003

Recognized Contributor
Sep 17, 2012
997
889
@banshee28
Looking at your logs, I see a problem with fastboot drivers.
Make sure your fastboot drivers are in good order.
As soon as your phone is booted to fastboot, it is no longer detected.
 

Griffinx

Member
Dec 29, 2010
38
9
Has anyone successfully upgraded from A12 to A13 using PixelFlasher with Flash to both slots option ON
 

Scalee

Senior Member
Aug 21, 2009
195
250
I took these steps to upgrade to 13:

1. Extracted bootloader-raven-slider-1.2-8739948.img from the factory image and placed it next to ADB/fastboot
2. Unhide magisk
3. Use pixelflasher to process the image and patch the boot img
4. Pressed reboot to bootloader
5. ran fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img to prevent the brick issue
6. Pressed 'flash pixel phone' in PixelFlasher

Everything seems fine, data and root are preserved
 
  • Like
Reactions: jspikeball123

banshee28

Senior Member
Aug 31, 2010
236
40
@banshee28
Looking at your logs, I see a problem with fastboot drivers.
Make sure your fastboot drivers are in good order.
As soon as your phone is booted to fastboot, it is no longer detected.
So this is a "new" laptop with W11 on it, clean Pixel Flasher install then installed Android Platform Tools from the link on the top left. They appear to be accessible from that folder fine. Weird.
 

Lughnasadh

Senior Member
Mar 23, 2015
3,892
4,155
Google Nexus 5
Huawei Nexus 6P
So this is a "new" laptop with W11 on it, clean Pixel Flasher install then installed Android Platform Tools from the link on the top left. They appear to be accessible from that folder fine. Weird.
Might also want to make sure you have these drivers installed, if you haven't already. Additionally, seems as if most people have better luck flashing things when they use a A to C cable on a USB 2.0 port.
 
Last edited:

banshee28

Senior Member
Aug 31, 2010
236
40
Might also want to make sure you have these drivers installed, if you haven't already. Additionally, seems as if most people have better luck flashing things when they use a A to C cable on a USB 2.0 port.
Yea, using the A to C cable too. Downloaded the google USB drivers but when I installed them it said I already had the best drivers for my device is already installed. It shows up fine in the Flasher and shows adb is working. Just weird it goes offline in fastboot. Will try another cable and USB port now.
 

banshee28

Senior Member
Aug 31, 2010
236
40
Yea, using the A to C cable too. Downloaded the google USB drivers but when I installed them it said I already had the best drivers for my device is already installed. It shows up fine in the Flasher and shows adb is working. Just weird it goes offline in fastboot. Will try another cable and USB port now.
So used a diff high speed USB data cable, diff port, same failure at fastboot. It initially sees it as adb and reboots when initiating the flash, but gets stuck at fastboot saying unable to detect device, no device selcted. Maybe I can try another laptop or my PC next. .
 

banshee28

Senior Member
Aug 31, 2010
236
40
So I thought I had it working! I used my Linux PC and it appears the fastboot drivers worked right away! It processed all the commands quickly but when the phone rebooted it was the same, LOL.

It looks like it could not flash the b slot for some reason.
 

Attachments

  • support.zip
    4.9 KB · Views: 8

badabing2003

Recognized Contributor
Sep 17, 2012
997
889
So I thought I had it working! I used my Linux PC and it appears the fastboot drivers worked right away! It processed all the commands quickly but when the phone rebooted it was the same, LOL.

It looks like it could not flash the b slot for some reason.
Just to be clear, same all being bootloop?
The logs show that everything went ok.
 

banshee28

Senior Member
Aug 31, 2010
236
40
Just to be clear, same all being bootloop?
The logs show that everything went ok.
Sorry, same meaning my Android image (phone) was not flashed/changed at all, at least not from any data wipe!

extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 261095424 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (831 MB)...
Invalid sparse file format at header magic
archive does not contain 'system.sig'
extracting system_other.img (23 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (490 MB)...
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.

.....

writing 'system_b' 1/4...
(bootloader) image size (872411136) biffer than partition size (868085760
FAILED (remote: failed to flash partition (system_b))
finished. total time: 2.778s
rebooting to bootloader ...
rebooting into bootloader...
 

badabing2003

Recognized Contributor
Sep 17, 2012
997
889
I took these steps to upgrade to 13:

1. Extracted bootloader-raven-slider-1.2-8739948.img from the factory image and placed it next to ADB/fastboot
2. Unhide magisk
3. Use pixelflasher to process the image and patch the boot img
4. Pressed reboot to bootloader
5. ran fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img to prevent the brick issue
6. Pressed 'flash pixel phone' in PixelFlasher

Everything seems fine, data and root are preserved
There is a way you can do all this in PixelFlasher without having to resorting to manual file extraction / copy / fastboot command.

I'll put it here for the benefit of others, and I'll add an option to PixelFlasher to flash bootloader only into both slots (the checkbox of Flash on both slots currently flashes everything on both slots)

Steps

  1. Select Platform Tools
  2. Select Device
  3. Select Factory Image
  4. Process Factory Image
  5. Select boot.img from the list
  6. Patch the boot.img from the list
  7. Turn on Advanced options in PixelFlasher (File | Advanced Configuration)
  8. Choose Custom Flash for Flash Mode
  9. Select bootloader for the Flash
  10. Click on Browse and navigate to %APPDATA%\PixelFlasher\factory_images\raven-tp1a.220624.021\bootloader-oriole-slider-1.2-8739948.img (replace raven with your device name if not on raven, and possibly the version could be different)
  11. Select "Flash on both slots" and optionally choose "verbose"
  12. Hit Flash Pixel Phone, the phone will reboot to fastboot and flash the bootloader to both slots and remain in fastboot
  13. Undo step 11, (uncheck Flash on both slots)
  14. Next Select Flash Mode "Keep Data"
  15. Hit Flash Pixel Phone.

    Just to note that steps 7 - 13 are the additional steps for flashing Bootloader on both slots, the rest are the normal steps you would typically do when updating the monthly drop.
    If you already have done the update without steps 7 - 13, and are on Pixel 6* it is advised that you just do those steps.
    See this thread.
 

uoid

Senior Member
Jun 19, 2013
135
32
Manama
Google Pixel 6 Pro
I updated to Android 13 everything was smooth until i decided to flash inactive slot via Magisk and my phone has no display only boots into fastboot.
I tried flashing factory image but it Stop here, tried it multiple times.
Tried doing it to both Slots.



Bootloader Version...: slider-1.2-8739948
Baseband Version.....: g5123b-102852-220720-B-8851166
Serial Number........: 0ab54fde3750
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.378s]
extracting boot.img (64 MB) to disk... took 0.159s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.511s]
Writing 'boot_b' OKAY [ 0.282s]
extracting dtbo.img (16 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.375s]
Writing 'dtbo_b' OKAY [ 0.063s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.015s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.016s]
Writing 'pvmfw_b' OKAY [ 0.016s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.000s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_b' OKAY [ 0.000s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.000s]
extracting vendor_boot.img (64 MB) to disk... took 0.188s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.457s]
Writing 'vendor_boot_b' OKAY [ 0.219s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: usage: no command
Press any key to exit...

1660932454545.png
 

badabing2003

Recognized Contributor
Sep 17, 2012
997
889
writing 'system_b' 1/4...
(bootloader) image size (872411136) biffer than partition size (868085760
FAILED (remote: failed to flash partition (system_b))
finished. total time: 2.778s
rebooting to bootloader ...
rebooting into bootloader...
I see that you are using the wipe option.

Assuming that the PixelFlasher state has not changed since.
Can you try the following and see if it works?
Navigate to the following directory
%AppData%\Roaming\PixelFlasher\factory_images\raven-tp1a.220624.021
and edit the file flash-phone.bat (you might not see the .bat part if you have hidden the extensions, which is the Windows default)

There should be a line in there with update image-raven-tp1a.220624.021.zip
Just before the update add --force (keeping space between the two)

Then you can run that batch file.
Just open a command prompt in that directory and run
flash-phone.bat

This should theoretically force partition resize.
It would wipe your phone, but you are already selecting that, so not an issue for you.

Let us know how it goes.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    New Release:
    Sep 04, 2022 v3.7.0 release
    • New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
    • New Feature: Install compatible apk file onto the device from PixelFlasher menu.
    • Check Android Platform Tools version and warn if it is old.
    • Block flashing when stock flash_all.bat file is tampered with.
    • Don't bother with flashing if bootloader is locked.
    • More validations and exceptions handling.
    • Improved logging.
    7
    Every few years or so, here on xda, an app (or script) comes along that really changes the game.
    This happens when an app is released with the certain "xda" development mindset: clear vision and a need for the apps' functionality, consistent development (with fast improvements), community feedback that's always respected by the dev and suggestions sometimes added to the app, and a finished product that is used by both newbies and veterans.

    Seriously, this reminds me of the Nexus-7'13/Nexus-5 days where there were so many dedicated devs that created some awesome apps (kernel managers, partition scripts and other apps). It's awesome to see @badabing2003 doing cool things and just know that a ton of people really enjoy your work.
    5
    Waste of time. Not going to provide anything. Nobody else has had any issues outside of a hiccup that was easily remedied. Some people just shouldn't root and flash. And I'm not being mean, but if something goes wrong, you shouldn't just go blaming everything and everybody else.
    I hear you, I can imagine the user's frustrations after finding themselves with a phone that is not working properly and not knowing how to get out of it.
    But the user's post doesn't help the situation, we're here to help out, and without any details, it's impossible to guess what had happened and what corrective actions to take.

    Help us help you is what I would say.

    I always would like to see the logs, just in case I can add another check / validation / warning to prevent a user from shooting themselves on the foot or fix a bug, we know things could go wrong, and not every scenario leads to the same outcome, anticipating the numerous scenarios we face or might face helps us add measures to prevent mishaps.
    5
    I got it back to stock right away. If you want to pm me directions on how to pull the logs I offered them in my original post. And I didn't bash you or your application, just made the point that it did not work out well for me, I may use a different method this evening.
    Sorry if I missed any of your posts.
    I only see two posts from you
    First post here, and your follow up post here. None of which is offering any logs, because you wrongly assumed that all of that is lost in a bricked phone.

    Did I by any chance allude you into thinking that I was seeing your posts as bashing me? Where? what gave you that idea?.

    As for asking for directions on how to pull the logs, it's all here in my reply to your post.
    Makes me wonder ...
    4
    Well lesson learned for me. I followed the directions to the letter after weeks of studying these forums and all day studying the directions, and bricked my new 6 pro I just dropped a grand on. Just have a battery symbol and no reaction to anything now.
    Which directions did you follow?
    What did you observe at what stage?
    Did you do anything outside any instructions you followed in an attempt to remedy the situation? If yes what did you do and what did you observe?

    Just saying that you have a brick is not going to help you receive any help, as in anything related to hacking / rooting the devil is in the details, every detail matters.
  • 37
    PF_promo-banner.png
    This is the support thread of PixelFlasher for Google Pixel 6 Pro
    PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.


    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 user interaction) 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.
      • Unique ID.
      • 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.
        Option to Live boot from a choice of boot.img.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • id
      • hardware
      • current installed firmware.
      • if it is rooted with Magisk.
      • Magisk version
      • List installed Magisk modules.
      • connection mode.
    • Magisk installation UI. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade. Display:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK 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.
    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.
    • 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.
    • SOS Disable Magisk modules to get out of bootloop (experimental).

    For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

    Troubleshooting:

    Note: This thread is meant for issues and problems faced in Google Pixel 6 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
    13
    New Release:
    Sep 04, 2022 v3.7.0 release
    • New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
    • New Feature: Install compatible apk file onto the device from PixelFlasher menu.
    • Check Android Platform Tools version and warn if it is old.
    • Block flashing when stock flash_all.bat file is tampered with.
    • Don't bother with flashing if bootloader is locked.
    • More validations and exceptions handling.
    • Improved logging.
    10
    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.
    9
    New Release:
    Aug 24, 2022 v3.6.0 release
    • When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
    • Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
    • Improved tooltips.
    9
    New Release: (See full details here on xda or here at github)
    April 03, 2022 v2.0.0.0-pre release.
    • Major refactoring
    • Added Advanced (Expert) mode UI.
    • Basic mode keeps UI simple and hides expert features.
    • Support for setting active slot.
    • Reboot options (recovery, system, bootloader)
    • Moved custom ROM options to expert mode.
    • Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
    • Moved flashing to both slots, disabling verity / verification to expert mode.
    • Many other improvements, validations and checks.
    • Updated documentation.