search

chenxiaolong / avbroot

Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot
GNU General Public License v3.0
525 stars 42 forks source link

Failed to boot into userspace fastboot #352

Closed luketeam5 closed 1 month ago

luketeam5 commented 1 month ago

Hello,

I may be a bit confused here, but I'm encountering an issue on my Pixel 8 Pro after following the fastboot flashall --skip-reboot steps outlined in the Initial setup. The phone installs everything up to vendor_kernel_boot_a, and then it prints Rebooting into fastboot before rebooting into fastbootd. After that, it hangs at < waiting for any device >, and nothing further seems to happen.

If I try to reboot back into Fastboot, I receive the message fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable. I've also tried experimenting with fastbootd, but that hasn’t resolved the issue.

I'm looking to get a GrapheneOS Rooted with Magisk working, so any assistance would be greatly appreciated! Thank you!

chenxiaolong commented 1 month ago

Any chance you're running Windows? My understanding is that on Windows, fastbootd mode might require different drivers than normal fastboot mode.

luketeam5 commented 1 month ago

Yup, running on Windows 11 as I didn't want to bother with using my desktop with Linux Mint on it

11 Sept 2024 01:06:26 Andrew Gunnerson @.***>:

Any chance you're running Windows? My understanding is that on Windows, fastbootd mode might require different drivers[https://developer.android.com/studio/run/win-usb] than normal fastboot mode.

— Reply to this email directly, view it on GitHub[https://github.com/chenxiaolong/avbroot/issues/352#issuecomment-2342312794], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AJRWX5NGJKFPCBBJNKFNF2DZV53O5AVCNFSM6AAAAABN7S7SAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBSGMYTENZZGQ]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/AJRWX5L3UNV5SEB6W7VHTL3ZV53O5A5CNFSM6AAAAABN7S7SAGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTULTTNVU.gif]

chenxiaolong commented 1 month ago

Ah, yeah, if that's the case, you'll probably have to install Google's drivers I linked to above. I don't think there's any way around it.

luketeam5 commented 1 month ago

Okay, thanks for the help. This solved the issue.