PixelFlasher Hanging right after vendor_boot_b image OKAY message

[totempole]

Hello,

Attached is the support.zip file as well.

Mac M1 Air Monterey 12.5.1 Phone: Pixel 6a (New out of the box with the bootloader unlocked) Image: Android 12 SD2A.220601.003.B1, Jul 2022

It doesn't seem to progress past the fastbootd screen after it reboots past "Writing 'vendor_boot_b' OKAY [ 0.086s]"

I've let it sit in past attempts for 15 minutes or longer and the phone just sits on the fastbootd screen. I've tried the following options:

Basic Mode: Flash to inactive with both keep data and WIPE data options Unchecked Flash to inactive slot with those same options Installed Magisk apk via tool and this is succesfull. I see the app in the app drawer and on subsequent adb scans the phone shows up as having Magisk installed.

Advanced Mode: Flash to both slots with both keep data and WIPE data

None of these yield a different outcome. Phone boots back into android 12. pixelflashersupport.zip

[badabing2005]

This typically suggests driver issue but you're on a Mac which does not require separate drivers. What happens when the phone reaches the fastbootd state and is just sitting there, if you open a terminal and type fastboot devices? I suspect when your device is in fastbootd mode, it is no longer detected. Typically using another cable or switching to a USB 2 port solves the issue considering that in your case it can't be a driver issue.

[totempole]

Thanks I suspected driver issue as well but as you mentioned, MacOS doesn't need it. I changed the cable too with no effect. I will try it again to the point that it gets to fastbootd and see if the device is seen by my laptop. Will report back.

Nov 30, 2022 8:02:12 PM badabing2005 @.***>:

This typically suggests driver issue but you're on a Mac which does not require separate drivers. What happens when the phone reaches the fastbootd state and is just sitting there, if you open a terminal and type fastboot devices? I suspect when your device is in fastbootd mode, it is no longer detected. Typically using another cable or switching to a USB 2 port solves the issue considering that in your case it can't be a driver issue.

— Reply to this email directly, view it on GitHub[https://github.com/badabing2005/PixelFlasher/issues/38#issuecomment-1333044929], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAMCXVAB6WE7AHJZZFSOVLWLABKHANCNFSM6AAAAAASQHB3IE]. You are receiving this because you authored the thread.[Tracking image][https://github.com/notifications/beacon/AAAMCXVUGIID3KYG77EJN7TWLABKHA5CNFSM6AAAAAASQHB3IGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSPOSTMC.gif]

[totempole]

Tried doing it again... Seems to reboot into fastbootd as soon as vendor_boot_b returns OKAY. I checked to see if the device was visible via a separate terminal and sure enough it's there and listed. Given this, I don't think it's a cable issue either (going on 3 different cables now incl. the one that came with the phone and I've used exactly once.. for this)

---

sh-3.2# fastboot devices 28231BEFR07704 fastboot

[totempole]

OK so tried something different... right after i get to fastbootd where it hangs, i rebooted the phone manually back into the bootloader and then killed the fastboot process... this seems to have allowed the script to progress.. Did this for both slots and i now have magisk root on my phone. Seems to be a wait in the script or a race condition.. not a programmer. Zip attached if it helps you.

[badabing2005]

Thanks for the update, Be careful, the only reason you managed to get it to work is because you were attempting to flash bluejay-sd2a.220601.003.b1-factory-79324336.zip and your device is already on SD2A.220601.003.B1.

Let me explain the process so that you know exactly what's going on and where it is failing. Take a look at this which is what PF generated and which is what is being run.

Everything is working until the highlighted line. That update image-... line does many things. If you look at the contents of that image file, you have these components. Some of these images need to be flashed in bootloader mode, and others need to be flashed in fastbootd mode and this is all managed by fastboot binary part of the Android platform tools. That is handled by the update parameter, and it does the necessary rebooting, and detecting of the modes.

What is happening in your case is that, part of the image update is working, the part that is done in bootloader mode, but the other parts that are done in fastbootd mode are not flashed because the process is waiting for the device to be detected in fastbootd state before proceeding. This could be a bug in fastboot binary, not sure, it really needs to detect and continue flashing the rest of the images.

By you rebooting your device and putting it bootloader mode, and killing the fastboot, practically you skipped flashing the rest of the images that are part of the update, and you let the rest of the script continue, which flashes the patched image. This only worked because your update is on the same version of firmware, Had you attempted to flash another firmware version (let's say the latest) then you would end up with partial update and most likely it won't be bootable to that slot.

What you could try is after rebooting your phone into bootloader mode you run the command fastboot reboot fastboot which will put the device in fastbootd mode, and hope that the other fastboot process that is waiting for it will detect it and continue the rest of the process.

If you kill the fastboot process, make sure to also kill the script process, and then manually rerun the highlighted line and the one after it (if you want it patched).

By the way, the first REDACTED is hiding your username, the second one is hiding your device id, this is done to protect your privacy, if you want to rerun that command, make sure you replace REDACTED with their appropriate values.

[totempole]

This makes a ton of sense. And yup, it was a calculated risk I took given the firmware was the same. Currently the image is flashed and we're good to go.. I will give it a shot again when upgrading to Android 13 (taking care to flash both slots of course). Thanks for your help thus far

[badabing2005]

Please update here when you do so that it can benefit others who face the same issue.