# Installer stuck on FastbootD

**URL:** <https://community.iode.tech/t/installer-stuck-on-fastbootd/7936>\
**Category:** Installation Help\
**Tags:** Pixel8\
**Created:** [24 March 2026 23:39 UTC](https://community.iode.tech/t/installer-stuck-on-fastbootd/7936 "2026-03-24T23:39:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jayroll](https://community.iode.tech/letter_avatar_proxy/v4/letter/j/b3f665/32.png) [@jayroll](https://community.iode.tech/u/jayroll)\
**Post date:** [24 March 2026 23:39 UTC](https://community.iode.tech/t/installer-stuck-on-fastbootd/7936/1 "2026-03-24T23:39:56Z")

</div>

Hello,

I’m installing iode on a Pixel 8 Pro using their [latest installer](https://gitlab.iode.tech/ota/ota/-/blob/master/installer/iodeOS-installer-v0.3.0-windows.zip?ref_type=heads) 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

 ![fastbootd](https://community.iode.tech/uploads/default/original/2X/6/6af8a36a0c5b2cd135484ef8b9d621a3c2a90723.jpeg)

> 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!

---

<div class="post-metadata">

**Author:** ![volker01](https://community.iode.tech/letter_avatar_proxy/v4/letter/v/a698b9/32.png) [@volker01](https://community.iode.tech/u/volker01)\
**Post date:** [25 March 2026 13:36 UTC](https://community.iode.tech/t/installer-stuck-on-fastbootd/7936/2 "2026-03-25T13:36:29Z")

</div>

Can You check your Google/ADB Drivers? See:

> [@Pixel 7a black screen of death](https://community.iode.tech/t/pixel-7a-black-screen-of-death/7015/19):
>
> the other interesting stuff is when a press power + vol down, the device manager window refresh the list in the USB controller category. Same when I unplug/plug the device. It seems to answer a little, but I cannot communicate with it from my win11 computer. Another computer raise a plug infos, the device is reconized as “Pixel ROM recovery”. Any idea ?

---

<div class="post-metadata">

**Author:** ![rik](https://community.iode.tech/user_avatar/community.iode.tech/rik/32/1437_2.png) [@rik](https://community.iode.tech/u/rik)\
**Post date:** [25 March 2026 14:48 UTC](https://community.iode.tech/t/installer-stuck-on-fastbootd/7936/3 "2026-03-25T14:48:10Z")

</div>

> [@jayroll](#):
>
> \< waiting for any device \>

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](https://dl.google.com/android/repository/latest_usb_driver_windows.zip)

Let us know if that helps.

---

<div class="post-metadata">

**Author:** ![jayroll](https://community.iode.tech/letter_avatar_proxy/v4/letter/j/b3f665/32.png) [@jayroll](https://community.iode.tech/u/jayroll)\
**Post date:** [26 March 2026 18:06 UTC](https://community.iode.tech/t/installer-stuck-on-fastbootd/7936/4 "2026-03-26T18:06:15Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![rik](https://community.iode.tech/user_avatar/community.iode.tech/rik/32/1437_2.png) [@rik](https://community.iode.tech/u/rik)\
**Post date:** [27 March 2026 15:18 UTC](https://community.iode.tech/t/installer-stuck-on-fastbootd/7936/5 "2026-03-27T15:18:27Z")

</div>

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 🙂
