yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] badabing2003:
View attachment 5567239

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

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.

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.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 6 Pro] badabing2003:
Placeholder
[Google Pixel 6 Pro] Alekos:
this is an interesting project.

can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
[Google Pixel 6 Pro] badabing2003:
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.

Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.

https://xdaforums.com/t/pixelflashe...g-updating-pixel-phones.4415453/post-86622153
[Google Pixel 6 Pro] badabing2003:
Done, check the new release.
[Google Pixel 6 Pro] badabing2003:
New Release:

March 24, 2022 v1.2.0.1-alpha release.

Added Advanced Configuration menu which unlocks advanced features such as:

- Flashing to both slots

- Disabling Verity

- Disabling Verification

- (More features to come)

The UI will now display the chosen Android Platform Tool's version.

Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).

Stability fixes.
[Google Pixel 6 Pro] badabing2003:
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.
[Google Pixel 6 Pro] badabing2003:
Update:

Version 2.0.1 which includes a hotfix for issue reported here.
[Google Pixel 6 Pro] minhgi:
Flawless one click update. Thanks. This going to be my default update tool.
[Google Pixel 6 Pro] rmiles7721:
Just used it to flash April update on my 6 Pro. Worked like a charm. Thanks.
[Google Pixel 6 Pro] wgrant:
Also used this to get to April from February and it was one of the simplest things I've ever had to do. Excellent work on this.
[Google Pixel 6 Pro] Zach Alt:
It keeps saying magisk is not on my phone, but it is, and it's not hidden.

According to the logs it thinks my phone is not rooted, but it is.

Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
[Google Pixel 6 Pro] badabing2003:
Thanks for bringing this up, I'll add it to the guide,

Shell would need root permission for it to be able to do detect and use magisk.

View attachment 5581317
[Google Pixel 6 Pro] Zach Alt:
Awesome, I'll enable it for next month's update. Again, thanks for this software, it's awesome.

I toggled root access for shell and now my phone shows as rooted in Pixel Flasher.
[Google Pixel 6 Pro] badabing2003:
New Release:

April 06, 2022 v2.1.0 release

Setup dedicated profile directory.

Put logs in the profile directory and maintain log history.

Plumbing for Linux support (just the flashing part is left to do).

Plumbing for new workflow.

Bugfix to handle name conflict in ROM filename.

Various minor improvements.

Update documentation.
[Google Pixel 6 Pro] wgrant:
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.

Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.

If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
[Google Pixel 6 Pro] badabing2003:
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.

Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.

It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.

I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
[Google Pixel 6 Pro] wgrant:
That's a good idea as well, better to not force a closure of the process and instead inform then give the user the information necessary to close it themselves. It was definitely the fastboot process that was holding the files. Once I killed that it was fine for me to proceed. Providing a pop up with the PID or even just the process name (unless the PID is always the same) and instructions in that pop up would certainly help someone get out of a jam without needing to reboot the computer.

I've done some stuff like this project with batch but this blows that completely out of the water. Excellent work, you should be proud of what you've given to the community.
[Google Pixel 6 Pro] Radon7:
can I also root my Pixel with that?
[Google Pixel 6 Pro] badabing2003:
I would listed to @Lughnasadh advice.

If you generate support.zip, I'd be happy to take a look in case I spot anything.
[Google Pixel 6 Pro] banshee28:
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!
[Google Pixel 6 Pro] banshee28:
Will try to pull one, thanks!
[Google Pixel 6 Pro] badabing2003:
@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.
[Google Pixel 6 Pro] Griffinx:
Has anyone successfully upgraded from A12 to A13 using PixelFlasher with Flash to both slots option ON
[Google Pixel 6 Pro] Scalee:
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
[Google Pixel 6 Pro] banshee28:
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.
[Google Pixel 6 Pro] Lughnasadh:
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.
[Google Pixel 6 Pro] banshee28:
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.
[Google Pixel 6 Pro] banshee28:
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. .
[Google Pixel 6 Pro] banshee28:
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.
[Google Pixel 6 Pro] badabing2003:
Just to be clear, same all being bootloop?

The logs show that everything went ok.
[Google Pixel 6 Pro] banshee28:
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...
[Google Pixel 6 Pro] badabing2003:
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

Select Platform Tools

Select Device

Select Factory Image

Process Factory Image

Select boot.img from the list

Patch the boot.img from the list

Turn on Advanced options in PixelFlasher (File | Advanced Configuration)

Choose Custom Flash for Flash Mode

Select bootloader for the Flash

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)

Select "Flash on both slots" and optionally choose "verbose"

Hit Flash Pixel Phone, the phone will reboot to fastboot and flash the bootloader to both slots and remain in fastboot

Undo step 11, (uncheck Flash on both slots)

Next Select Flash Mode "Keep Data"

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.
[Google Pixel 6 Pro] uoid:
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...
[Google Pixel 6 Pro] badabing2003:
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.
[Google Pixel 6 Pro] badabing2003:
It sounds like you hit this issue

this thread.

Try to follow this and see if it fixes your issue
[Google Pixel 6 Pro] uoid:
Thanks and do you think this issue is covered under warranty?
[Google Pixel 6 Pro] badabing2003:
Whatever I say it would be pure speculation.
[Google Pixel 6 Pro] uoid:
Tried the methods you suggested, Still same problem, the phone is stuck at the same issue.
[Google Pixel 6 Pro] badabing2003:
Thanks for the update.

Have you tried Android Flash Tool?
[Google Pixel 6 Pro] banshee28:
So I am running Flasher on Linux, not sure the path is the same? On Windows the fastboot drivers did not work for some reason. I will try to locate these on Linux.
[Google Pixel 6 Pro] Namelesswonder:
Directory will be under ~/.local/share/PixelFlasher/
[Google Pixel 6 Pro] banshee28:
Got it, thanks! Now for Linux it would be "flash-phone.sh" with same flag as above?
[Google Pixel 6 Pro] Namelesswonder:
Yes flash-phone.sh should be inside the directory named after the factory image.

I would like to note that if the script has --slot all on the update command then it isn't going to flash properly, as documented on my post here.

https://xdaforums.com/t/psa-do-not-...tral-repository.4352027/page-69#post-87309913

So if it's there then remove that, you could then use PixelFlasher to then follow up with the Android 13 system image being installed to both slots or follow the steps in my post.

If this still fails then I would like to know what version your fastboot is on. fastboot --version

Some distributions come with an android-tools package, however Google only drops the source to platform-tools maybe every 6 months to a year, so these distribution packages could be very out of date and stopping the flash from working. You'll have to go and grab the binaries from Google if this is the case, it was for me a couple months when I didn't realize that Fedora has tools from 2020.
[Google Pixel 6 Pro] banshee28:
fastboot version 1:8.1.0+r23-5ubuntu2

Installed as /usr/lib/android-sdk/platform-tools/fastboot

Luckily --slot-all was not there so good there. However I need to first reboot into bootloader so doing this now.
[Google Pixel 6 Pro] Namelesswonder:
Stop what you are doing and cease using that. Uninstall the android-tools package or whatever it may be named on Ubuntu. Go and download the platform-tools binary from Google.

@badabing2003

It may be in your favor to check the fastboot version on start and throw up an error if it is older than the current release.
[Google Pixel 6 Pro] banshee28:
WOW! I managed to use the latest drivers and my phone FLASHED! Its sitting at the Welcome to your Pixel screen now! Thanks so much @Namelesswonder and @badabing2003.

I will post back soon once I get it setup again, but it looks like it should be working now!!!

fastboot version 33.0.2-8557947
[Google Pixel 6 Pro] badabing2003:
Happy to hear that, I'll add an option to PixelFlasher for --force.

To fix your windows fastboot drivers issue.

Set the following two system environments

DEVMGR_SHOW_NONPRESENT_DEVICES=1
DEVMGR_SHOW_ALL=1

Launch Device Manager

If you can find the fastboot driver, click on it and hit delete to uninstall.

I would go a step further and uninstall anything that has an exclamation mark.

Then delete anything that is light gray (which means not loaded) (delete, but not uninstall the light gray ones)

You'd end up with clean drivers.

Now connect your phone and do

adb reboot bootloader

Once it reboots, you should see the fastboot drivers loading in Device Manager, make sure it does not come with an exclamation make.

You can check if it is working by issuing the command

fastboot devices[/device]
It should show your phone device ID, and.

Hope it helps.
[Google Pixel 6 Pro] badabing2003:
New Release:

Aug 19, 2022 v3.5.0 release

Add support for fastboot --force flag (to help fix partition issues, caution it will wipe data) see this.

Split image flashing to all slots into two separate single slot flashing to bypass a Google bug on Pixel 6* devices, see this by @Namelesswonder.
[Google Pixel 6 Pro] heij20032003:
I have flashed to A13 yesterday successfully using the basic way....but it seems that it is not secure without flashing into both slots....

so what do I need to do now?

should I download the new pixelflasher and then repeat all steps 1-15?
[Google Pixel 6 Pro] badabing2003:
The above steps 1-15 is if you want to flash the bootloader to both slots but nothing else, which is the minimum you should do to protect yourself from accidentally bricking.

With version 3.4.0 you couldn't flash everything to both slots by simply choosing the `flash to both slots` option because of a Google bug in Pixel 6, 6a and 6 Pro. (see PixelFlasher 3.5.0 release notes)

If you download the version 3.5.0 and flash to both slots you should be fine, it works around the Google bug and flashes everything in both slots, which is actually a better option than the minimal one.
[Google Pixel 6 Pro] uoid:
Tried the 3.5 Version still getting stuck at

rebooting to fastboot after Super-empty flash
[Google Pixel 6 Pro] badabing2003:
Please share support.zip and I'll check.
[Google Pixel 6 Pro] uoid:
I hope this is what you've asked for.
[Google Pixel 6 Pro] badabing2003:
What phone do you have? is it a Pixel?

You're applying Raven image but your phone is not Raven?

Another issue is that you're using OLD SDK, you're using 31.0.3-7562133 on windows you should always be using the latest.
[Google Pixel 6 Pro] uoid:
My phone is Raven pixel 6 pro
[Google Pixel 6 Pro] badabing2003:
Why does it say:

Device Model: slider
[Google Pixel 6 Pro] uoid:
I have tried button combinations to boot it up into fastboot, but there is no display.
[Google Pixel 6 Pro] badabing2003:
I'm not following you.

Why does your phone hardware is reported as slider?

What is the current state of the phone?

What was the last image you successfully applied on the phone? anything custom?

Your phone is able to get into fastboot, that is how PixelFlasher is able to get hardware info and attempt flashing.
[Google Pixel 6 Pro] uoid:
I flashed Android 13 without Flash on both Partitions, BL is unlocked. so I was patching Magsik and accidently selected "Flash Inactive slot" on Andorid13

The phone never booted and after that No dislpay.

if i leave it plugged into the computer it shows up as a fastboot device with a name slider.
[Google Pixel 6 Pro] badabing2003:
ok try the following

1- Make sure you are using the latest Android SDK, you're using an old one

2- Select Factory image, process it

3- For options choose wipe data and force, don't choose both slots just yet

if that does not work, repeat the above with flash to both slots chosen.

Also turn on the console verbose option, the one on the left side of the console.

Post the support.zip afterwards.
[Google Pixel 6 Pro] uoid:
Tried it and showed the same result

support is attached.
[Google Pixel 6 Pro] badabing2003:
I see it is failing to boot to fastbootd.

While in fastboot, try this from command line and see if it works.

fastboot reboot fastboot

if it does not, try switching the slot first and trying again

fastboot --set-active=other
fastboot reboot fastboot
[code]
[Google Pixel 6 Pro] uoid:
Nope! didnt work, the phone didnt boot into fastboot however if I use fastboot reboot bootloader . it always works
[Google Pixel 6 Pro] badabing2003:
Have you tried flashing OTA as Google recommends in here?

Another thing you can try is flash bootloader to both slots.

# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot

# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot

You can find out your active slot with (I think it is b)

fastboot getvar current-slot

By the way you can flash OTA in PixelFlasher,

Choose custom flash, select SIDELOAD, browse for the OTA image and hit flash.
[Google Pixel 6 Pro] uoid:
It didnt work, gave me the same no respone from the phone