Project updates.

BootForge has moved a long way since 0.1.9, and this note catches the site up with it. The app on Google Play is now 0.1.24.

Boot-menu themes. The menu a PC shows when it boots your drive no longer has to be Ventoy’s plain one. There are seven themes, each a genuinely different layout rather than a recolour, and you can put your own photo behind the menu instead. A prepared drive still gets the plain menu unless you pick something, and BootForge’s own theme is free. The rest of the gallery and the custom background are part of Pro. How it works.

A file browser. You can now walk the folders on the drive and in your phone library, not just the list of bootable images. Text files open in a viewer that’s free everywhere, and it tells you when it’s showing only the beginning of a long file rather than truncating quietly. With Pro you can edit them and create new ones, which is what finally makes Ventoy’s own ventoy.json and ventoy_grub.cfg editable without a PC. The drive’s EFI partition can be browsed too, read-only for everyone. How it works.

Hindi. BootForge speaks five languages now: English, Español, Português (Brasil), Русский and हिन्दी, all fully translated.

The drive, easier to work with. Search, sort and a grid view on both the Drive tab and your library. BootForge also records a checksum for every file it writes to a drive and can read it back later to tell you whether the drive still holds what it wrote — a real check, not a claim about the past.

Copies that survive a wobble. If the connection drops for a moment mid-copy, the transfer now waits and picks up again instead of failing. When a file genuinely can’t be copied, its row says why and what to try.

Honest verification. The read-back check after writing a single image is a toggle, and the app is now precise about the result. If a drive will neither commit its cache nor let BootForge read the flash directly, it says the check may have read the drive’s buffer and tells you to boot-test before relying on it, rather than reporting a clean pass it can’t stand behind. A write that can’t place every byte fails instead of finishing quietly.

Fixes. A few drives used to close the app the instant they were connected; the cause sat in how Android hands a drive’s reply back to an app, and BootForge changed the way it reads from a drive to take itself out of that path. Those drives should now open. A hub with a built-in card reader also stops costing a second permission prompt on every connect — BootForge learns which slot is empty and tries your actual drive first.

Kits, the ready-made bundles of images for one job, also got a page of their own.

BootForge 0.1.9 is rolling out on Google Play, and it grows the app beyond multiboot. Three additions, all in the free tier:

Single-image writes. Pick one ISO and write it straight to a drive, byte for byte, with a read-back verification pass before the app calls it done. The classic direct-write job that used to need a second app.

Raw .img support. Raw disk images are accepted on the same write path. The app is upfront about the one thing it can’t promise: whether a raw image boots depends on the image and the device it targets, so the write is verified and the rest is stated plainly, not claimed.

Windows installer drives. A dedicated mode that turns Microsoft’s official Windows ISO into a standard UEFI installer stick, splitting the oversized install file automatically so the FAT32 layout Windows Setup expects just works. No conversion steps on your side.

The Home screen now opens with a build-mode chooser when you connect a blank drive, so all of this is one tap from the front door. The guides covering single-ISO writes and Windows installers have been updated to match.

BootForge is currently in the technical planning and validation phase. The first engineering milestone is a USB/OTG detection and permission flow spike on real Android hardware.

The website will track important product decisions, catalog updates, and release milestones as the Android app moves from validation into implementation.