PixelFlasher hangs if previously connected device is not connected

[V0latyle]

Used Pixel Flasher to patch tangorpro boot image with Apatch. After flashing, tablet was disconnected and PixelFlasher was left open.

Connected Pixel 5 to try to live boot a patched boot image; forgot to rescan and select new device, so tangopro was still selected.

PixelFlasher then hung when "Flash Device" was started.

[badabing2005]

support file will be helpful

[V0latyle]

support file will be helpful

Sorry, unable to duplicate, and I'm not sure how useful a support file would be as I had to kill the program.

[badabing2005]

One good thing about the way PF calls the adb / fastboot commands is that it uses -s flag to target the device by id, the fact that you unplugged the tablet and plugged the Pixel 5, but issued the flash command, it still tried to operate on the tablet (the known device to PF), which didn't exist which is a good thing.

I'm surprised that you didn't get warned about mismatched flash with device, unless you also kept the boot selection wrongly the tablet's in which case it would match the device selection and proceed without warning.

The issue you experienced is that PF calls adb/fastboot commands with --wait-for-device, so that it gives it enough time to complete the reboot or whatever operation it is performing, but it also tries to end / kill the process after a timeout. This timeout operation although it most often works, there are cases where it doesn't. The support file would have told me the case, as in, was the tablet's last known state to PF was connected/disconnected? in which mode was it in? For example, if it was in adb mode then PF will issue the reboot command, however if it was already in bootloader mode, it will not reboot and jump straight to flashing. Obviously the commands are different, and the timeouts depending on the operation / use are different.

[V0latyle]

Exactly what I did:

Used PixelFlasher to update tablet to September Flashed aPatch boot image Disconnected tablet (yesterday) Today, connected Pixel 5 (did not scan for or select device) Selected Pixel 5 firmware Selected custom flash mode and experimental boot image Clicked Flash Device, confirmed selection Pixel Flasher then froze, had to close program from taskbar

Is a support file still useful after the program crashes/is killed? I thought it only captures the active session's log so if it's killed, how would you get any relevant info?

[badabing2005]

Yes it is still usefull, It would have everything until the kill which should be good enough.

[V0latyle]

So you're saying that if the program hangs and I have to kill it, it'll still remember everything that happened before I killed it? I thought each time the process was closed, the slate gets wiped so to speak

[badabing2005]

nah, nothing is wiped, in fact the console log is flushed to logfile each time the console is updated. So the actions done before crash or kill, if they logged anything to console, they will also be available in the logfile (support file) Of course if the crash happens to be due to writing file (which is not the case) then obviously it won't be there.

[V0latyle]

Understood. Here you go support_2024-09-10_09-38-30.zip

[badabing2005]

Thanks, Check your PM

[badabing2005]

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