PixelFlasher crashed while updating OTA update

[louisamand]

MacBook Pro 14" M3 Max with MacOS Sonoma 14.4.1
Pixel 6 with EvolutionX 8.3 oriole-ota-uq1a.240205.004-03050058 installed
PixelFlasher v6.9.3.1
SDK version 35.0.1-11580240

While updating my phone to Stock oriole-ota-ap1a.240405.002-bee2137c, I have been stuck on

for more than an hour now.
My mac tells me PixelFlasher stopped responding.
My phone shows:

Now send the package you want to apply to the device with "adb sideload <filename>"...
Support API: 3
Finding update package...
Installing update...
Step 1/2

and that's it.

What can/should I do in order not to brick my phone?

[badabing2005]

• Kill PixeFlasher
• Start PixelFlasher
• Scan for devices
• Generate support file
• Submit the support file, and I'll take a look.

It's odd that PixelFlasher did not send the OTA, or perhaps the device is not detected in sideload mode.
While your device is still saying what you posted, if you scan for devices does PixelFlasher see your device?

What version of platfoorm tools are you running?
All of these would be answered by a support file.

[louisamand]

Funny enough, as soon as I click on my device, PixelFlasher seems to not respond anymore:

It seems to be in sideload mode both from the dropdown menu and adb:

Android Platform Tools version 35.0.1-11580240

[louisamand]

At least holding volume up + power did restart it 😉

[louisamand]

So, since it seems to be not too risky (I hope), I tried again and exactly the same happened.
However, doing a dry run on the Factory image seems to run fine. But I'm a bit scared of going further than the dry run haha

Support for factory dry run: support_2024-05-06_15-43-43.zip, don't know if it can help.

[badabing2005]

That's really weird.
It looks like when this command is executed (which is what sideloads the OTA), it just hangs.

"/Users/REDACTED/Downloads/platform-tools/adb" sideload "/Users/REDACTED/Downloads/oriole-ota-ap1a.240405.002-bee2137c.zip"

Where REDACTED is your username on your MacOS

When it gets into that state, can you try issueing that command from terminal and see if you get anything?

Make sure you replace REDACTED with your username.

[louisamand]

So, in case it happens to someone:

• I continued trying to flash the OTA and at some point it finally seemed to work until 47%.
• At that point recovery asked me if I wanted to restart while hanging the 47%. I said "no" and the installation crashed and my phone started "bootlooping".
• Then I had to hold volume down + power to start fastboot, go to recovery and then go to sideload (update with adb).
• I tried installing again and again and again and nothing changed. I tried saying yes to the recovery question and going back to main menu, same result. I also tried doing it directly on the terminal. I tried a Factory reset which actually sent me an error I could not comprehend. Anyway, it never went further than 47% and the Pixel would go back to bootloop.
• At some point I tried changing the image from B to A and it then booted with fresh stock android.

Now it works fine and I have no clue why (it never went higher than 47%).

I included the support zip in case there is anything to learn 🤔 (15h40 session was the first appearance of the 47%)

[badabing2005]

I admire your persistance.

Soemthing is definitely off communication wise between your Mac and your device.
It is not normal that when the device is in sideload mode, and you issue the command to send the OTA, it becomes unresponsive.
And you also experienced this doing it manually from the terminal.

In the logs, I noticed that in one of your attempts it actually started accepting the file and then it justgot stuck

serving: '/Users/REDACTED/Downloads/oriole-ota-ap1a.240405.002-bee2137c.zip'  (~0%)

As for 47%, that usually happens for vaious reasons, mostly related to a previous OTA update that didn't complete and needs to be cleared, PixelFlasher can do that, but it needs root access to do that, or if you had flashed custom ROM that had changed the partitions (which is not the case for you)
47% actually represents 50%, there is a bug in the way Google's sideload reports the progress.

At this point I would recommend trying different cable / different port, perhaps even trying Android platform tools version 33.0.3

[badabing2005]

This issue was automatically closed by Github bot, due to inactivity.