Installer stuck on FastbootD

Hello,

I’m installing iode on a Pixel 8 Pro using their latest installer but am having issues. The installer is stuck at the “FASTBOOTD” screen and reports that it is “< waiting for any device >”

I’ve attached a photo of the screen the Pixel 8 Pro is stuck on, as well as the readout from the installer

Setting current slot to ‘a’ OKAY [ 0.134s]
Finished. Total time: 0.134s
Warning: skip copying bootloader_a image avb footer (bootloader_a partition size: 0, bootloader_a image size: 19179128).
Sending ‘bootloader_a’ (18729 KB) OKAY [ 0.412s]
Writing ‘bootloader_a’ (bootloader) Flashing pack version ripcurrent-16.4-14097582
(bootloader) flashing platform zuma
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition gsa_bl1_a
(bootloader) Validating partition ldfw_a
(bootloader) Validating partition gcf_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition gsa_bl1_a
(bootloader) Flashing partition ldfw_a
(bootloader) Flashing partition gcf_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.130s]
Finished. Total time: 0.547s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
< waiting for any device >
Warning: skip copying radio_a image avb footer (radio_a partition size: 0, radio_a image size: 112926860).
Sending ‘radio_a’ (110280 KB) OKAY [ 2.430s]
Writing ‘radio_a’ (bootloader) Flashing pack version g5300i-250909-251024-M-14326967
(bootloader) Flashing partition modem_a
OKAY [ 0.381s]
Finished. Total time: 2.820s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
< waiting for any device >
Erasing ‘avb_custom_key’ (bootloader) avb custom key: erase done
OKAY [ 0.026s]
Finished. Total time: 0.027s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending ‘avb_custom_key’ (1 KB) OKAY [ 0.001s]
Writing ‘avb_custom_key’ (bootloader) avb custom key: flash done
OKAY [ 0.037s]
Finished. Total time: 0.042s
Warning: metadata type is raw, but ext4 was requested for formatting.
mke2fs 1.47.2 (1-Jan-2025)
Creating filesystem with 16384 4k blocks and 16384 inodes

Allocating group tables: 0/1 done
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done

Warning: skip copying metadata image avb footer due to sparse image.
Sending ‘metadata’ (204 KB) OKAY [ 0.005s]
Writing ‘metadata’ OKAY [ 0.010s]
Finished. Total time: 0.249s
Erasing ‘metadata’ OKAY [ 0.011s]
Finished. Total time: 0.012s
Warning: userdata type is raw, but f2fs was requested for formatting.

F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)

Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 229970088 (112290 MB)
Info: block size = 4096
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
“”
[f2fs_init_sit_area: 743] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 777] Filling nat area at offset 0x00e00000
[f2fs_add_default_dentry_root:1393] Writing default dentry root, at offset 0x1d800
[f2fs_write_root_inode:1439] Writing root inode (hot node), offset 0x1d200
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d801 (1/2)
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d802 (2/2)
[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d201
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d803 (1/2)
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d804 (2/2)
[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d202
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d805 (1/2)
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d806 (2/2)
[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d203
[f2fs_update_nat_default:1620] Writing nat root, at offset 0x00000e00
Info: Overprovision ratio = 0.430%
Info: Overprovision segments = 245 (GC reserved = 239)
[f2fs_write_check_point_pack: 969] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack:1056] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1070] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1082] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1096] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1104] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1146] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1165] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1198] Writing super block, at offset 0x00000000
Info: format successful
Warning: skip copying userdata image avb footer due to sparse image.
Sending ‘userdata’ (89 KB) OKAY [ 0.003s]
Writing ‘userdata’ OKAY [ 0.527s]
Finished. Total time: 0.834s
Sending ‘frp’ (512 KB) OKAY [ 0.012s]
Writing ‘frp’ OKAY [ 0.010s]
Finished. Total time: 0.025s

Bootloader Version…: ripcurrent-16.4-14097582
Baseband Version…: g5300i-250909-251024-B-14326967
Serial Number…: 41160DLJG000LP

extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.000s]
Setting current slot to ‘a’ OKAY [ 0.091s]
extracting fastboot-info.txt (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to disk… took 0.000s
Writable partitions are not supported
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting boot.img (64 MB) to disk… took 0.160s
archive does not contain ‘boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘boot_a’ (65536 KB) OKAY [ 1.425s]
Writing ‘boot_a’ OKAY [ 0.243s]
extracting super_empty.img (0 MB) to RAM…
extracting init_boot.img (8 MB) to disk… took 0.022s
archive does not contain ‘init_boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘init_boot_a’ (8192 KB) OKAY [ 0.178s]
Writing ‘init_boot_a’ OKAY [ 0.038s]
extracting super_empty.img (0 MB) to RAM…
extracting dtbo.img (16 MB) to disk… took 0.029s
archive does not contain ‘dtbo.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘dtbo_a’ (16384 KB) OKAY [ 0.355s]
Writing ‘dtbo_a’ OKAY [ 0.067s]
extracting super_empty.img (0 MB) to RAM…
extracting vendor_kernel_boot.img (64 MB) to disk… took 0.132s
archive does not contain ‘vendor_kernel_boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vendor_kernel_boot_a’ (65536 KB) OKAY [ 1.423s]
Writing ‘vendor_kernel_boot_a’ OKAY [ 0.244s]
extracting super_empty.img (0 MB) to RAM…
extracting pvmfw.img (1 MB) to disk… took 0.004s
archive does not contain ‘pvmfw.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘pvmfw_a’ (1024 KB) OKAY [ 0.023s]
Writing ‘pvmfw_a’ OKAY [ 0.012s]
extracting super_empty.img (0 MB) to RAM…
extracting vendor_boot.img (64 MB) to disk… took 0.187s
archive does not contain ‘vendor_boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vendor_boot_a’ (65536 KB) OKAY [ 1.416s]
Writing ‘vendor_boot_a’ OKAY [ 0.227s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_a’ (8 KB) OKAY [ 0.001s]
Writing ‘vbmeta_a’ OKAY [ 0.007s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta_system.img (0 MB) to disk… took 0.001s
archive does not contain ‘vbmeta_system.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_system_a’ (8 KB) OKAY [ 0.001s]
Writing ‘vbmeta_system_a’ OKAY [ 0.007s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta_vendor.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta_vendor.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_vendor_a’ (4 KB) OKAY [ 0.001s]
Writing ‘vbmeta_vendor_a’ OKAY [ 0.007s]
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >

Any thoughts?

Thank you in advance for any help!

Can You check your Google/ADB Drivers? See:

3 Likes

This problem seems most common if you don’t have the latest Android USB drivers. Here is a direct link them: https://dl.google.com/android/repository/latest_usb_driver_windows.zip

Let us know if that helps.

2 Likes

That solved it. What’s odd, is when I checked for drivers earlier in the process it said I had the most recent ones. Should have made sure rather than trusting Windows on that one lol

Thanks!

1 Like

Thank you for coming back and confirming it worked! I don’t actually use Windows, so this will give a bit more confidence when I am giving the same advice to others in the future :slight_smile: