Rufid
Write and recover bootable USB media
新版本 0.2.1
Create Windows installer media as FAT32, NTFS MBR, or NTFS GPT.
Split install.wim over 4 GiB for FAT32 using source-built wimlib.
Add ISO9660/UDF extraction, path validation, progress, cancellation, and partial-failure cleanup.
Add source-built NTFS-3G and UEFI:NTFS layouts.
Harden USB BOT reset, halt clearing, CSW residue checks, and ambiguous-write handling.
Pin the 7-Zip-JBinding source build to the release Gradle toolchain.
Virtual QEMU/OVMF boot validation is complete. Physical USB and PC
Split install.wim over 4 GiB for FAT32 using source-built wimlib.
Add ISO9660/UDF extraction, path validation, progress, cancellation, and partial-failure cleanup.
Add source-built NTFS-3G and UEFI:NTFS layouts.
Harden USB BOT reset, halt clearing, CSW residue checks, and ambiguous-write handling.
Pin the 7-Zip-JBinding source build to the release Gradle toolchain.
Virtual QEMU/OVMF boot validation is complete. Physical USB and PC
Rufid turns an Android phone into a practical USB boot-media tool.
It writes local ISO/IMG files to attached USB mass-storage devices, streams direct image URLs, creates a small FreeDOS drive, verifies written media, inspects boot records, runs read benchmarks, backs up a USB device to an Android document, extracts ZIP files, and recovers used boot media back into a normal FAT32 or exFAT drive.
Windows installer ISOs can be written as a FAT32 UEFI layout, with install.wim split when it exceeds the FAT32 file-size limit, or as an NTFS data volume with an MBR or GPT UEFI:NTFS helper layout. These paths have been booted to the Windows Setup language screen in QEMU/OVMF. Physical USB controllers and PC firmware remain a separate compatibility test surface.
The main workflow is phone-first: select a USB device, inspect it, choose an ISO/IMG, URL, or FreeDOS source, review the plan, write, and verify. Direct URL mode includes quick access to official source pages for Windows, Ubuntu, Fedora, Debian, Linux Mint, Arch Linux, and openSUSE; it does not bundle those operating system images.
Destructive USB actions are guarded by an explicit plan screen and confirmation. Rufid shows the selected USB device, size, and available hardware identifiers before write or recovery operations. It is designed for external USB mass-storage devices, not internal Android storage.
Rufid has no ad SDK, analytics SDK, billing SDK, Firebase dependency, cloud account system, or remote crash-reporting SDK. Error reports stay local on the device.
The F-Droid build path packages the boot payload set from auditable inputs. FreeDOS is assembled from source-built FreeDOS kernel, FreeCOM, SYS, and boot sector artifacts. UEFI:NTFS, wimlib, NTFS-3G tools, and 7-Zip-JBinding are staged from pinned upstream source paths, and the 7-Zip-JBinding Android build excludes RAR/unRAR native sources. No payload is extracted from an opaque third-party APK.
USB recovery is a metadata quick-wipe plus FAT32 or exFAT format flow. It is useful for returning a boot USB to normal storage use, but it is not secure erase and not a full-disk wipe.
It writes local ISO/IMG files to attached USB mass-storage devices, streams direct image URLs, creates a small FreeDOS drive, verifies written media, inspects boot records, runs read benchmarks, backs up a USB device to an Android document, extracts ZIP files, and recovers used boot media back into a normal FAT32 or exFAT drive.
Windows installer ISOs can be written as a FAT32 UEFI layout, with install.wim split when it exceeds the FAT32 file-size limit, or as an NTFS data volume with an MBR or GPT UEFI:NTFS helper layout. These paths have been booted to the Windows Setup language screen in QEMU/OVMF. Physical USB controllers and PC firmware remain a separate compatibility test surface.
The main workflow is phone-first: select a USB device, inspect it, choose an ISO/IMG, URL, or FreeDOS source, review the plan, write, and verify. Direct URL mode includes quick access to official source pages for Windows, Ubuntu, Fedora, Debian, Linux Mint, Arch Linux, and openSUSE; it does not bundle those operating system images.
Destructive USB actions are guarded by an explicit plan screen and confirmation. Rufid shows the selected USB device, size, and available hardware identifiers before write or recovery operations. It is designed for external USB mass-storage devices, not internal Android storage.
Rufid has no ad SDK, analytics SDK, billing SDK, Firebase dependency, cloud account system, or remote crash-reporting SDK. Error reports stay local on the device.
The F-Droid build path packages the boot payload set from auditable inputs. FreeDOS is assembled from source-built FreeDOS kernel, FreeCOM, SYS, and boot sector artifacts. UEFI:NTFS, wimlib, NTFS-3G tools, and 7-Zip-JBinding are staged from pinned upstream source paths, and the 7-Zip-JBinding Android build excludes RAR/unRAR native sources. No payload is extracted from an opaque third-party APK.
USB recovery is a metadata quick-wipe plus FAT32 or exFAT format flow. It is useful for returning a boot USB to normal storage use, but it is not secure erase and not a full-disk wipe.
- 作者: Rufid contributors
- 授權條款: GNU General Public License v3.0 or later
- 問題追蹤系統
- 原始碼
- 更新紀錄
- 建置詮釋資料
- 可重現建置狀態
版本
雖然在下方可選擇下載 APK 檔案，但要留意這樣的安裝方式將不會收到更新通知，是一種較不安全的下載方法。建議您先安裝 F-Droid 用戶端使用。
下載 F-Droid-
arm64-v8aarmeabi-v7ax86x86_64此版本需要 Android 7.0 或更高的版本。
此套件包由 F-Droid 建置和簽署，並保證與此原始碼 Tarball 保持一致。
-
arm64-v8aarmeabi-v7ax86x86_64此版本需要 Android 7.0 或更高的版本。
此套件包由 F-Droid 建置和簽署，並保證與此原始碼 Tarball 保持一致。
新版本 0.1.2
USB write compatibility hotfix:
- Treat unsupported final SCSI SYNCHRONIZE CACHE responses as non-fatal after image data has been written
- Covers Illegal Request responses including invalid command, invalid command field, and invalid parameter-list reports
- Keeps actual USB data WRITE failures, capacity errors, medium errors, and hardware errors fatal
- Adds clearer local error reports that distinguish data WRITE failures from final cache-sync failures
- Treat unsupported final SCSI SYNCHRONIZE CACHE responses as non-fatal after image data has been written
- Covers Illegal Request responses including invalid command, invalid command field, and invalid parameter-list reports
- Keeps actual USB data WRITE failures, capacity errors, medium errors, and hardware errors fatal
- Adds clearer local error reports that distinguish data WRITE failures from final cache-sync failures