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

[nikkiscores]

Why do you say it is not detecting?

It even flashed the phone.

that's bramble, the 4a5g that i did earlier. i was talking about the 7, which is panther. i thought i had cleared the PF console before testing pixel 7, but it seems i either didn't, or does support.zip always include info on previous flashes?

at any rate, i will check again when i get home.

@J.Michael - are you not able to see the screenshot, or do you not like what it's detecting? in case it's the former, the output of

/usr/bin/fastboot devices

was

28151FDH20021H  Integrated Webcam

which matches the id under adb.

 

[badabing2003]

that's bramble, the 4a5g that i did earlier. i was talking about the 7, which is panther. i thought i had cleared the PF console before testing pixel 7, but it seems i either didn't, or does support.zip always include info on previous flashes?

at any rate, i will check again when i get home.

@J.Michael - are you not able to see the screenshot, or do you not like what it's detecting? in case it's the former, the output of

/usr/bin/fastboot devices

was

28151FDH20021H  Integrated Webcam

which matches the id under adb.

Integrated Webcam?

 

[J.Michael]

that's bramble, the 4a5g that i did earlier. i was talking about the 7, which is panther. i thought i had cleared the PF console before testing pixel 7, but it seems i either didn't, or does support.zip always include info on previous flashes?

at any rate, i will check again when i get home.

@J.Michael - are you not able to see the screenshot, or do you not like what it's detecting? in case it's the former, the output of

/usr/bin/fastboot devices

was

28151FDH20021H  Integrated Webcam

which matches the id under adb.

I was able to read the screen-shot. I assumed Integrated Webcam was a webcam, and expected to see a line saying "Pixel". Having seen the transcript, I now see that was expecting too much.

So, to be clear, when you use fastboot, your phone is identified as "Integrated Webcam"?

If you connect both phones at once, are they both Integrated Webcam? Are these IDs something you can find on each phone?

 

[badabing2003]

PF will not identify a phone in bootloader mode if it is reported as Integrated Webcam, that's for sure.
The text after device id has to match one of these.
device - adb mode
fastboot - fastboot (bootloader) mode
recovery - recovery mode
sideload - sideload mode

 

[J.Michael]

PF will not identify a phone in bootloader mode if it is reported as Integrated Webcam, that's for sure.
The text after device id has to match one of these.
device - adb mode
fastboot - fastboot (bootloader) mode
recovery - recovery mode
sideload - sideload mode

Should he be manually putting the phone in fastboot (bootloader?) mode before running PixelFlasher?

 

[badabing2003]

Should he be manually putting the phone in fastboot (bootloader?) mode before running PixelFlasher?

That won't help if it is detected as integrated Webcam.
He should be using the latest Android platform tools from Google which he said works fine.

In fact when you launch PF and select old version, it warns you, you actually have to acknowledge "I know what I'm doing, continue using my old version" (something along those lines) otherwise it won't use that.

 

[Gruber008]

Thank you once again, Pixel Flasher made OTA updating so damn easy even for dummies like me

 

[Kerrylee1738$$$]

i had a question.... i keeping getting a error message saying the android platform isnt valid and i download straight from the link on the flasher and ones i download from browser. im confused on what the issue is. could someone plz tell me how to fix this issue...thank you in advance

 

[zgfg]

i had a question.... i keeping getting a error message saying the android platform isnt valid and i download straight from the link on the flasher and ones i download from browser. im confused on what the issue is. could someone plz tell me how to fix this issue...thank you in advance

How do you think anybody could help you if you don't provide details about your 'Android platform' - phone, ROM, etc?!

 

[Kerrylee1738$$$]

How do you think anybody could help you if you don't provide details about your 'Android platform' - phone, ROM, etc?!

Lol whatever kid anyhow figured it out. Needed a different flash tool to get it done

 

[krakout]

Lol whatever kid anyhow figured it out. Needed a different flash tool to get it done

Oooh boy.

 

[Larakali]

So here is something weird ive been experiencing. Ive attached a log for it too but let me explain.
I tried flashing the January Update as it came out, but had a Writing error as if my phone had been disconnected.
No Biggies i just reflashed on all. Now the funny thing is i can only use one slot at a time.
Meaning if you look in my Log i can use Slot B if i flash it but not Slot A. Reflashing into inactive slot, aka Slot A here, makes Slot A usable but Slot B cant be booted anymore. I see the Google Logo and then it Bugs out and reboots until it Boots into the working Slot.
Is this Intended?

EDIT: It doesnt seem to accept my Txt.
Im just gonna pastebin it then:
Log

 

[badabing2003]

So here is something weird ive been experiencing. Ive attached a log for it too but let me explain.
I tried flashing the January Update as it came out, but had a Writing error as if my phone had been disconnected.
No Biggies i just reflashed on all. Now the funny thing is i can only use one slot at a time.
Meaning if you look in my Log i can use Slot B if i flash it but not Slot A. Reflashing into inactive slot, aka Slot A here, makes Slot A usable but Slot B cant be booted anymore. I see the Google Logo and then it Bugs out and reboots until it Boots into the working Slot.
Is this Intended?

EDIT: It doesnt seem to accept my Txt.
Im just gonna pastebin it then:
Log

This is an expected behavior,
I have previously posted my findings and why this happens, I'll try to find my post which had all the details.
In short there is two reasons why it's not bootbale.

1- Full Factory image flashes system_other.img to the other slot's (inactive) system partition, which includes the optimized dex for the target phone, and on first successful boot, it copies those.
This in effect makes the alternate slot's system partition not usable.

2- You would think ok, let's just rewrite that system partition, or flash factory with system_other removed and problem solved, and that would be logical thought, and it actually works, I managed to test that on Pixel XL and booted one with rooted image and the other stock. However in newer Androids (Android 10 or newer with logical partitions), this does not work, because AVB fails when you switch slots.

 

[Larakali]

So its normal only one slot works.
Relieved.

To the second one. Both Slots work fine if flashed to. I tested it. It boots into B and A after a flash just fine.
So to be 100% sure, i am fine right?

 

[badabing2003]

So its normal only one slot works.
Relieved.

To the second one. Both Slots work fine if flashed to. I tested it. It boots into B and A after a flash just fine.
So to be 100% sure, i am fine right?

I'm not sure I understand you fully
If you flash to a, b would break and a would work
if you flash to b, a would break and b would work.

What are you observing?

 

[Larakali]

I'm not sure I understand you fully
If you flash to a, b would break and a would work
if you flash to b, a would break and b would work.

What are you observing?

Im observing the same

 

[badabing2003]

Im observing the same

Yep based on data and behavior interpretation, that is the expected outcome, until we find a way to cheat AVB and let it pass.

 

[tator-Salad1738]

i had a question about the issue im having with the flasher. i have a google pixel 6a IN2015 running android 13 and whenever i add the factory image to it then add custom rom to flash and so far every Rom error's saying its missing the boot file, but it flashes flawlessly using fastboot. anyone know why im not about to flash custom with the flasher

 

[dyval]

i had a question about the issue im having with the flasher. i have a google pixel 6a IN2015 running android 13 and whenever i add the factory image to it then add custom rom to flash and so far every Rom error's saying its missing the boot file, but it flashes flawlessly using fastboot. anyone know why im not about to flash custom with the flasher

Pixel 6a IN2015? Are you using a OnePlus device running a custom rom?

 

[badabing2003]

i had a question about the issue im having with the flasher. i have a google pixel 6a IN2015 running android 13 and whenever i add the factory image to it then add custom rom to flash and so far every Rom error's saying its missing the boot file, but it flashes flawlessly using fastboot. anyone know why im not about to flash custom with the flasher

Support.zip please