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

Search This thread

thekdub

Senior Member
Jul 9, 2011
116
88
I was using Pixel Flasher to flash the August update and it failed in the middle of the flashing process (maybe when I picked up the phone and it possibly jostled the usb cord). I tried to flash again but it gave me a warning message:

Unless you know what you are doing, if you continue flashing
you risk bricking your device, proceed only if you are absolutely
certian that this is what you want, you have been warned.

Unsure how to proceed.
 

Attachments

  • support.zip
    23.8 KB · Views: 17

thekdub

Senior Member
Jul 9, 2011
116
88
I also tried to restart the patching process, but no longer have a connection with adb.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
@thekdub

Looking at your logs.
You started with July A12,
You were on slot a
You tried to flash Aug A13
With patched boot.img
You managed to flash the bootloader to slot a ...
The process failed when flashing product to slot a, possibly as you pointed out due jostled usb cable .

When it was flashing product, the device was in fastbootd mode

The device is now detected to be in bootloader mode or fastbootd mode.
The fact that it is reported as:

Device Model:
Device is Rooted: None
Device Build:
Device Active Slot:
Device Bootloader Version:
Device Mode: f.b

Suggests that It's in limbo and not reporting device details.
We want the device either in adb mode or fastboot mode reporting info.

Have your tried rebooting your phone? long pressing the power ?
Does it always go back to this mode?

You can try power cycling if you can, and hit the refresh button in PixelFlasher, and then hit the Info button
If you get info, you're good, either in adb or fastboot is fine,
Then you want to repeat the flashing, but make sure you select flash to both slots.

report back,
We can try few other things, but let's see if you can put the device in proper adb or fb mode
 

dinuka_haxxor

Member
Oct 16, 2014
14
1
Hi I was trying to update my bootloader by using Google method but ..
PS F:\torrentz\platform-tools_r33.0.3-windows\platform-tools> fastboot --slot=other flash bootloader D:\oriole-tp1a.220624.021-factory-4bd6cec7\oriole-tp1a.220624.021\bootloader.img
Warning: bootloader does not support slots, and slot b was requested.
Sending 'bootloader' (11554 KB) OKAY [ 0.419s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

It gives me this error. And previously I wanted to sideload an ota but it was stuck in verification stage and I aborted doing that however I flashes the factory image thru PixelFlasher and it worked perfectly... So maybe there is a issues with my fastboot drivers ? Or platform tools ?
And so is it safe to try updating my bootloader thru PixelFlasher tool ? (I have already flashed the factory image of android 13 thru the PixelFlasher btw)
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
Hi I was trying to update my bootloader by using Google method but ..
PS F:\torrentz\platform-tools_r33.0.3-windows\platform-tools> fastboot --slot=other flash bootloader D:\oriole-tp1a.220624.021-factory-4bd6cec7\oriole-tp1a.220624.021\bootloader.img
Warning: bootloader does not support slots, and slot b was requested.
Sending 'bootloader' (11554 KB) OKAY [ 0.419s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

It gives me this error. And previously I wanted to sideload an ota but it was stuck in verification stage and I aborted doing that however I flashes the factory image thru PixelFlasher and it worked perfectly... So maybe there is a issues with my fastboot drivers ? Or platform tools ?
And so is it safe to try updating my bootloader thru PixelFlasher tool ? (I have already flashed the factory image of android 13 thru the PixelFlasher btw)
I don't know if you renamed the bootloader file, but the correct filename is: bootloader-oriole-slider-1.2-8739948.img (renaming is not a problem, just making sure you renamed this file and not another file)

In any case if Pixelflasher is flashing factory fine, then I would say there is no issue with your phone or your drivers.
You can flash the bootloader through PixelFlasher, or you can flash OTA, but my preferred method is to flash Factory image to both slots.
 

kiwi32

Senior Member
Apr 25, 2010
66
7
Just wanted to say, I just bricked my Pixel 6. What a mess.
Was trying to upgrade to Android 13 with PixelFlasher. I had read the warning regarding the dual slot issue.
PixelFlasher hung while waiting for a fastboot reboot of the device that never came. My phone tried to boot a few times, but failed on the google logo.
I guess it then tried to revert to the other slot that was still on Android 12, since it then became completely bricked.
Complete black screen even while charging.
RMA in progress...
Attached is the log, if it can help anyone.

Please select a boot.img!
Android SDK Version: 33.0.3-8952118
Device: REDACTED oriole SQ3A.220705.004
Factory Image: C:\Users\REDACTED\Downloads\oriole-tp1a.220624.021-factory-4bd6cec7.zip

Boot image: ccce82c5 / ccce82c5
From: C:\Users\REDACTED\Downloads\oriole-tp1a.220624.021-factory-4bd6cec7.zip

Flash Mode: keepData



Note: Pressing OK button will invoke a script that will utilize
fastboot commands, this could possibly take a long time and PixelFlasher
will appear frozen. PLEASE BE PATIENT.
In case it takes excessively long, it could possibly be due to improper or
bad fasboot drivers.
In such cases, killing the fastboot process will resume to normalcy.

Do you want to continue to flash with the above options?
Press OK to continue or CANCEL to abort.

The script content that will be executed:
--------------------------------------------
chcp 437
@Echo off
:: This is a generated file by PixelFlasher v3.6.0.0

PATH=%PATH%;"%SYSTEMROOT%\System32"
"C:\platform-tools\fastboot.exe" -s REDACTED flash bootloader bootloader-oriole-slider-1.2-8739948.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED flash radio radio-oriole-g5123b-102852-220720-b-8851166.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --skip-reboot update image-oriole-tp1a.220624.021.zip
echo rebooting to bootloader ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\platform-tools\fastboot.exe" -s REDACTED flash boot pf_boot.img
echo rebooting to system ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot

--------------------------------------------

2022-08-29 10:57:09 User Pressed Ok.

==============================================================================
2022-08-29 10:57:09 PixelFlasher 3.6.0.0 Flashing Phone
==============================================================================
Rebooting device REDACTED to bootloader ...
Waiting 10 seconds ...

Selected Device on 2022-08-29 10:57:27:
Device ID: REDACTED
Device Model: oriole
Device is Rooted: None
Device Build:
Device Active Slot: a
Device Bootloader Version: slider-1.2-8739948
Device Mode: f.b
Device Unlocked: True

2022-08-29 10:57:27 Flashing device REDACTED ...
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\oriole-tp1a.220624.021>chcp 437
Active code page: 437
Sending 'bootloader_a' (11554 KB) OKAY [ 0.284s]
Writing 'bootloader_a' (bootloader) Flashing pack version slider-1.2-8739948
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 2.741s]
Finished. Total time: 3.040s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for REDACTED >
Sending 'radio_a' (82772 KB) OKAY [ 2.032s]
Writing 'radio_a' (bootloader) Flashing pack version g5123b-102852-220720-M-8851166
(bootloader) Flashing partition modem_a
OKAY [ 0.103s]
Finished. Total time: 2.149s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for REDACTED >
--------------------------------------------
Bootloader Version...: slider-1.2-8739948
Baseband Version.....: g5123b-102852-220720-B-8851166
Serial Number........: REDACTED
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.064s]
extracting boot.img (64 MB) to disk... took 0.283s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.484s]
Writing 'boot_a' OKAY [ 0.445s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.093s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.359s]
Writing 'dtbo_a' OKAY [ 0.016s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.000s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.036s]
Writing 'pvmfw_a' OKAY [ 0.000s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.429s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.604s]
Writing 'vendor_boot_a' OKAY [ 0.389s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for REDACTED >
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
Just wanted to say, I just bricked my Pixel 6. What a mess.
Was trying to upgrade to Android 13 with PixelFlasher. I had read the warning regarding the dual slot issue.
PixelFlasher hung while waiting for a fastboot reboot of the device that never came. My phone tried to boot a few times, but failed on the google logo.
I guess it then tried to revert to the other slot that was still on Android 12, since it then became completely bricked.
Complete black screen even while charging.
RMA in progress...
Attached is the log, if it can help anyone.

Please select a boot.img!
Android SDK Version: 33.0.3-8952118
Device: REDACTED oriole SQ3A.220705.004
Factory Image: C:\Users\REDACTED\Downloads\oriole-tp1a.220624.021-factory-4bd6cec7.zip

Boot image: ccce82c5 / ccce82c5
From: C:\Users\REDACTED\Downloads\oriole-tp1a.220624.021-factory-4bd6cec7.zip

Flash Mode: keepData



Note: Pressing OK button will invoke a script that will utilize
fastboot commands, this could possibly take a long time and PixelFlasher
will appear frozen. PLEASE BE PATIENT.
In case it takes excessively long, it could possibly be due to improper or
bad fasboot drivers.
In such cases, killing the fastboot process will resume to normalcy.

Do you want to continue to flash with the above options?
Press OK to continue or CANCEL to abort.

The script content that will be executed:
--------------------------------------------
chcp 437
@Echo off
:: This is a generated file by PixelFlasher v3.6.0.0

PATH=%PATH%;"%SYSTEMROOT%\System32"
"C:\platform-tools\fastboot.exe" -s REDACTED flash bootloader bootloader-oriole-slider-1.2-8739948.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED flash radio radio-oriole-g5123b-102852-220720-b-8851166.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --skip-reboot update image-oriole-tp1a.220624.021.zip
echo rebooting to bootloader ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\platform-tools\fastboot.exe" -s REDACTED flash boot pf_boot.img
echo rebooting to system ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot

--------------------------------------------

2022-08-29 10:57:09 User Pressed Ok.

==============================================================================
2022-08-29 10:57:09 PixelFlasher 3.6.0.0 Flashing Phone
==============================================================================
Rebooting device REDACTED to bootloader ...
Waiting 10 seconds ...

Selected Device on 2022-08-29 10:57:27:
Device ID: REDACTED
Device Model: oriole
Device is Rooted: None
Device Build:
Device Active Slot: a
Device Bootloader Version: slider-1.2-8739948
Device Mode: f.b
Device Unlocked: True

2022-08-29 10:57:27 Flashing device REDACTED ...
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\oriole-tp1a.220624.021>chcp 437
Active code page: 437
Sending 'bootloader_a' (11554 KB) OKAY [ 0.284s]
Writing 'bootloader_a' (bootloader) Flashing pack version slider-1.2-8739948
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 2.741s]
Finished. Total time: 3.040s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for REDACTED >
Sending 'radio_a' (82772 KB) OKAY [ 2.032s]
Writing 'radio_a' (bootloader) Flashing pack version g5123b-102852-220720-M-8851166
(bootloader) Flashing partition modem_a
OKAY [ 0.103s]
Finished. Total time: 2.149s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for REDACTED >
--------------------------------------------
Bootloader Version...: slider-1.2-8739948
Baseband Version.....: g5123b-102852-220720-B-8851166
Serial Number........: REDACTED
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.064s]
extracting boot.img (64 MB) to disk... took 0.283s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.484s]
Writing 'boot_a' OKAY [ 0.445s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.093s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.359s]
Writing 'dtbo_a' OKAY [ 0.016s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.000s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.036s]
Writing 'pvmfw_a' OKAY [ 0.000s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.429s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.604s]
Writing 'vendor_boot_a' OKAY [ 0.389s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for REDACTED >
Sorry about your troubles.
Looking at the above log
Code:
Device Bootloader Version:       slider-1.2-8739948
Your phone is already on A13 bootloader,
This is only possible if you had already flashed to A13.

Please upload the full support.zip so that I can analyze what might have gone wrong and if it is salvageable.
Thanks
 

kiwi32

Senior Member
Apr 25, 2010
66
7
Just pmed you the support.zip. Dont waste too much time, it's already on the way back to Google ;)
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
Just pmed you the support.zip. Dont waste too much time, it's already on the way back to Google ;)
Thanks for the support.zip.

I'd like to get to the bottom of it, in case there is a bug in PixelFlasher or in case I can make improvements for it to abort early on before flashing in cases where it detects weird stuff.

I can already see some improvements that could help.

1- What is your adb/fastboot version? PixelFlasher could not determine the version.
Code:
Found Android Platform Tools in C:\Users\REDACTED\adb

2022-08-26 15:14:04 ERROR: Unable to determine Android Platform Tools version.

The version check was for display only, so that we know the version that is being used, however I can add a check in case it is not known or it is an old version, not to allow the device Listing (the Refresh button), hence you won't be able to proceed further than that.

2- Next Issue is, what is your Magisk Version, and is there anything unique different about your Magisk?
PixelFlasher was able to determine that you had Magisk installed and are rooted, however it couldn't get Magisk Version, nor it could list the modules.

There's another improvement I can add to at least warn the user and ask for confirmation, this situation should not happen, if rooted, Magisk should respond to magisk -c

3- On Aug 26th you tried to flash the A13, at the time the active slot was slot a
During the flashing, PixelFlasher reported the following Error.
Code:
C:\Users\REDACTED\adb\fastboot.exe: unknown option -- skip-reboot

This is a puzzle, there is a space between -- and skip which should not be there.
But PixelFlasher code does not put a space there.
you can see it from this log entry which is the code it tried to execute
Code:
"C:\Users\REDACTED\adb\fastboot.exe" -s REDACTED  --skip-reboot update image-oriole-tp1a.220624.021.zip
Perhaps this is another case of adb/fastboot version being too old or something weird about it. (you should always use the latest version)

4- Patching stage, issuing simple adb command of checking if the file exists on the phone caused error, my guess it is related to adb version

I know you can't check the magisk version considering that the phone is being RMA-ed
Can you please check Android sdk version?
Code:
adb --version
It should be in C:\Users\<YOURNAME>\adb\

In the meantime I'll work on adding extra checks in the program to block user from continuing when adb version is old or unknown.
 

kiwi32

Senior Member
Apr 25, 2010
66
7
Hi,
1- I manually changed my adb path to c:\platform-tools in the GUI. My version is platform-tools_r33.0.3-windows.zip.
2- This could be an issue. My phone had a plain Magisk and was rooted, but automatically applied an OTA and restarted overnight. It was not Android 13 from what I can see, but I lost root and Magisk reported N/A after the OTA. So, the fact PixelFlasher reported my phone had root was wrong.
3-That's weird. Fastboot comes in ADB package right ? I was using the latest version from what I gather.
4- My path ADB is old ( Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android). Thus why I manually changed the adb folder in the GUI. Perhaps I forgot to change it initially and that's what triggered the issue ?
Thanks for all the help. This shows your implication to this community. Let me know how I can help.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
Hi,
1- I manually changed my adb path to c:\platform-tools in the GUI. My version is platform-tools_r33.0.3-windows.zip.
2- This could be an issue. My phone had a plain Magisk and was rooted, but automatically applied an OTA and restarted overnight. It was not Android 13 from what I can see, but I lost root and Magisk reported N/A after the OTA. So, the fact PixelFlasher reported my phone had root was wrong.
3-That's weird. Fastboot comes in ADB package right ? I was using the latest version from what I gather.
4- My path ADB is old ( Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android). Thus why I manually changed the adb folder in the GUI. Perhaps I forgot to change it initially and that's what triggered the issue ?
Thanks for all the help. This shows your implication to this community. Let me know how I can help.
Thanks for the follow up and your feedback.
I think that explains it, the root of the problem being old adb, Looking at the logs, only the adb folder was used during your patching and flashing.

Next version will prevent the use of older adb.
Thanks
 

kiwi32

Senior Member
Apr 25, 2010
66
7
Hey, just an update. I got my replacement phone. Updated the OTA to Android 13, then tried flashing with PixelFlasher. Well, it did exactly the same behavior, waiting for fastboot forever, but this time I figured it out. The drivers of the phone would not be correct by default, the device would display with the red ! in device manager. I had to manually select adb driver for the pixel with every reboot of the phone by PixelFlasher. Could be a useful popup to display if the reboot timeout in the tool fails.
Thanks,
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
Hey, just an update. I got my replacement phone. Updated the OTA to Android 13, then tried flashing with PixelFlasher. Well, it did exactly the same behavior, waiting for fastboot forever, but this time I figured it out. The drivers of the phone would not be correct by default, the device would display with the red ! in device manager. I had to manually select adb driver for the pixel with every reboot of the phone by PixelFlasher. Could be a useful popup to display if the reboot timeout in the tool fails.
Thanks,
Can you kindly provide a support.zip so that I clearly understand the issue?
Thanks

You should also resolve your drivers issue.
 

tom1807

Senior Member
Hey, just an update. I got my replacement phone. Updated the OTA to Android 13, then tried flashing with PixelFlasher. Well, it did exactly the same behavior, waiting for fastboot forever, but this time I figured it out. The drivers of the phone would not be correct by default, the device would display with the red ! in device manager. I had to manually select adb driver for the pixel with every reboot of the phone by PixelFlasher. Could be a useful popup to display if the reboot timeout in the tool fails.
Thanks,
Which drivers did you install? You should only use these. They are for ADB and fastboot boot. Red triangle could be an indication that the drivers are not WHQL signed.

Cheers
Tom
 
Last edited:

kiwi32

Senior Member
Apr 25, 2010
66
7
Not sure which drivers were used by default, but once manually selecting the correct adb drivers it worked.
I will resend the support.zip
Thanks,
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
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.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,445
1,680
Umm, is this part referring to Magisk? Because it sounds like you can't flash at all when the bootloader is locked, which is hard to believe.

Cheers
Tom
With the exception of sideloading OTA, you can't flash anything if the bootloader is locked.
Previously PixelFlasher did not block flash attempts of such if the bootloader was locked.
Although it was harmless, as it wouldn't change a thing, it was unnecessary.
That is what changed now.
 

Top Liked Posts

  • 1
    Thanks @V0latyle
    I did some reading.
    The successful bit needs to be set to true, otherwise boot process will not boot to it.
    You can see the flow and the required bits in Google's official document here

    @Jaitsu
    Put your device in bootloader mode and hit the Get Info button in PF
    Check the following values and see what you get.
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:yes
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:2
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:yes
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no

    Thankfully @capntrips has a tool specifically for this DevinfoPatcher

    Interestingly though, perhaps @capntrips can explain what might be going on here.
    I put this to test:
    I first launched the DevinfoPatcher and got a screen that reflected the following state (next code block).
    Sorry I did not think of taking a screenshot at that point (but there was no Patch button, suggesting that everything was good)
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:yes
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:2
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:yes
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no

    Rebooted to bootloader and dumped the properties
    Which had the above.
    Then I issued fastboot --set-active=b
    Immediately after I read the slot info and I got this
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:no
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:3
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:no
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no

    I was surprised because all I did was switch the slot and it marked (bootloader) slot-successful:b:no and (bootloader) slot-fastboot-ok:b:no

    I had not even rebooted at this point yet

    Next I rebooted back to bootloader
    fastboot.exe reboot bootloader
    This time it read
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:yes
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:3
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:no
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no

    Then I tried to reboot to system slot b
    Counter decremented but did not boot to system
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:yes
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:2
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:no
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no
    Tried it one more time, and the counter decremented again.
    I finally switched back to slot a and booted to system
    At this point, DeviceinfoPatcher showed this.
    1670439733370.png

    I hit the patch button and got this
    1670439791125.png


    Reboot to bootloader
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:yes
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:1
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:yes
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no

    fastboot --set-active=b
    And it's back to
    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:no
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:3
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:no
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:no

    Tried reboot multiple times till the counter reached 0 and marked the slot unbootable

    Code:
    (bootloader) slot-count:2
    (bootloader) slot-fastboot-ok:a:yes
    (bootloader) slot-fastboot-ok:b:yes
    (bootloader) slot-retry-count:a:2
    (bootloader) slot-retry-count:b:0
    (bootloader) slot-successful:a:yes
    (bootloader) slot-successful:b:no
    (bootloader) slot-suffixes:_a,_b
    (bootloader) slot-unbootable:a:no
    (bootloader) slot-unbootable:b:yes

    One more reboot, and it booted to system by switching to slot a as expected.
  • 1
    Maybe I still have a chance because even though adb devices does not return any devices, I can fastboot reboot the device from terminal. So I can probably flash some image, but I don't want to try anything randomly right now so waiting to see if anybody has ideas. Now I wish I could cross-post this with the pixel 7 thread.
    Good news. I used Android Flash Tool to flash TD1A.221105.001 (9104446). Lost all my configurations, but phone is working again. Though I still get the "your device is corrupt" message, but now it works when you press continue and I can boot into the phone. So now I repeated all the manual command executions. And now it worked fine, and I have root.

    God I wish I wasn't so stupid yesterday and flashed the boot.img. Is there a way to get rid of the "your device is corrupt" message?!#@!
    1
    @awesomeo3000
    Something is not right on your Mac.
    Looking at the terminal output you sent, I see lots of wrong things there.
    But don't fret, this can be solved / fixed, you don't want to go through this every month.
    Reach out to me privately pass me your username and device id, so that I give you precise commands to execute.
    Probably best when we're both are online at the same time.
    Tell me about your availability / timezone.
    Once I do, I would need execution of one command and one command only (no multiple tries of different variations), based on the output of that, I will give you the next command.
    Troubleshooting 101 :)

    I have to ask you, you said you had to wipe your device or at least it ended up wiped.
    Is wiping still an available option to you? or you rather not?
    There are different ways to approach this, and if wiping is an option, we'll take the easy route of clean start.
    1
    Hi all!

    I would like to root my Pixel 6 but I've been out from the modding scene since 2017 and everything is different now! My Pixel 6 is bootloader-locked, stock Android 13 manual installed when it came out via adb (didn't want to wait for the ota).

    I'm having difficult times understanding if I can root directly with this tool and also the slots thing, does it apply to my case too?

    Thanks in advance!
    I encourage everyone to read up on the guides, learn the what it takes to mod manually before jumping into using automated tools that do it for you.
    Granted the learning curve at first could be steep, but the benefits are enormous, if anything goes wrong or not according to the plans, you would know how to recover.

    If you still want to use PF without investing in learning the manual way,
    The Basic Usage steps on the Main page page or the Github page is what you need to follow.
    However considering that you're bootloader is locked, you need to unlock it first, PF has a button to do it, but it is not part of the automated process, as one would probably do this once.
    Furthermore to be able to unlock the bootloader, you need to enable developer mode, turn on OEM unlock and ADB Debugging ...
    Details of all of these are mentioned in the Guide threads, there are few great such guides links in the Help menu of PF, and you probably could find other good guides as well.

    Speaking of slots, it applies to your device, Pixel 6 has two slots, but you don't have to worry about it, the only recommendation I would make is flash to inactive slot, this way if anything goes wrong, you can still go back to the previous slot, and if everything goes well, the inactive becomes the current active and you're good,
    You repeat that on next month's release, this way you always have something to fallback to.

    Good luck and don't shy away to ask questions if anything is unclear.
    1
    I think I will follow the part about unlocking bootloader and then use your tool to root. Is this fine?
    Yes this is fine

    I still don't understand the part about slots, when should I enable "flash to inactive slot"? When I flash the boot.img or the patched_boot.img?
    Typically with PF, you don't flash the boot.img, you flash the patched_boot.img, PF automates the process for you so that with one flash you're updated and patched.

    The basic flow is as follows
    - you download a firmware, and select it in PF, no need to unpack the zip or extract files from it, just point to it, PF does the rest.
    - you process the firmware (just press the button) which extracts and shows the the boot.img
    - you select the boot and press the patch button
    - you select your flash options (this is when you choose flash to inactive slot, and keep data)
    - you flash
    1
    Did everything and all went like a charm! So easy and straightforward!

    I still have a question about monthly updates: Which updates I'm allowed to do directly on phone and which need to be done via PF to preserve root?

    Thanks again for your help!
    I wouldn't do anything on the phone,
    Much easier / quicker / reliable to do on PF,
    Repeat the process as you did now.
  • 17
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 6
    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.
      • 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.
    • 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 model.
      • 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.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • 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 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.
    • 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).

    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:
    • See this post.
    • Generate Sanitized support.zip file (File Menu) and submit that with your report.
    Note: This thread is meant for issues and problems faced in Google Pixel 6 devices, generic issues that are device agnostic should be discussed in the main thread.
    5
    Thank you for the consideration.
    No donation, this is simply giving back to the community that has given me a lot over the years.
    5
    Update:
    Version 2.0.1 which includes a hotfix for issue reported here.
    5
    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.
    5
    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.