Installation and usage
These steps are deliberately conservative. Confirm every device path and checksum before writing media or installing software.
Bootable PC ISO
The ISO boots Intel/AMD x86_64 desktops and laptops in QEMU and is intended for physical PCs. It does not target Apple Silicon Macs. The image runs read-only inventory and health collection, then serves a local report at http://127.0.0.1:8080/report.html.
1. Verify the ISO
After downloading, compare it with the published SHA-256:
# Linux
sha256sum diagd-live-amd64.iso
# macOS
shasum -a 256 diagd-live-amd64.iso
# Windows PowerShell
Get-FileHash .\diagd-live-amd64.iso -Algorithm SHA256
Expected hash: cfcf836562a96e41affba49616b6bef1bee484370821d4f74c4e2fa97462bc23.
2. Flash the ISO
Use balenaEtcher or Rufus if you prefer a GUI. On Linux/macOS, first identify the USB device carefully:
# Linux
lsblk
# macOS
diskutil list
# Linux example only: replace /dev/sdX after double-checking
sudo dd if=diagd-live-amd64.iso of=/dev/sdX bs=4M status=progress conv=fsync
sync
Warning: choosing the wrong device can destroy data. The ISO itself does not write to the target PC's disks, but flashing media is an operator action.
3. Boot and read the report
- Insert the USB into the target Intel/AMD PC.
- Open the boot menu, commonly F12, F9, Esc, or F2.
- Select the USB device. If firmware blocks the unsigned image, Secure Boot may need to be disabled temporarily.
- Wait for the
diagdread-only run to complete. - Open
http://127.0.0.1:8080/report.htmlin a browser in the live session, or inspect the generated files under/var/lib/diagd.
The ISO was verified by booting in QEMU. Physical hardware coverage, firmware quirks, and Secure Boot behavior still need technician testing.
Android debug APK
This is an unsigned debug build, not a Play Store release. Use a test or customer-authorized device and review the requested permissions before installing.
Direct install
- Download
ai-repair-android-debug.apkand verify its SHA-256:ae88b3ab4ff744e6b6b70c5760ce4ed4ae58965ac120597b4a66a8d6bbb134ea. - On Android, enable Install unknown apps for the browser or file manager that opened the APK.
- Open the APK and approve installation when Android asks.
ADB install
adb devices
adb install ai-repair-android-debug.apk
Enable Developer options and USB debugging only on a device you are authorized to inspect. The app's collection logic is read-only; it does not root the device, erase storage, or write firmware.
Companion source tools
The ZIP files are Python source distributions and include their README. Extract them, create an appropriate Python 3.10+ environment, install the repository dependencies, and run the documented CLI or replay tests.
- PC agent: the
diagdpackage reads Linux-visible signals. Optional tools can be absent; the agent reports unsupported fields rather than guessing. - ADB: run from a technician host with Android platform-tools and a paired device. Without a device, use the recorded transport tests.
- iOS: run from a host with libimobiledevice/go-ios-style tools and a paired device. Locked iOS legitimately exposes fewer fields.
- macOS: run on an Apple-Silicon Mac with its host tools. The source bundle cannot collect Mac host data from Linux.
# Example source verification
unzip -l companion-source.zip
sha256sum companion-source.zip
Safety boundary
These tools collect evidence and offer suggestions. They do not automatically perform firmware writes, disk erasure, power injection, battery stress, reflow/reball work, or board programming. Board/chip-level conclusions require physical measurements by a skilled technician. Simulator and recorded-fixture outputs must never be presented as real instrument or board results.