Initial commit

README.md

@@ -1,2 +1,109 @@
-# A-Team-Android_Image_Toolkit
+# A-Team Android Image Toolkit
 
+Cross-platform GTK3 Android image and device toolkit for Windows and Linux.
+
+## Modules
+
+1. **A-Team Sparse Chunk Converter** — sparse chunk -> raw `super.img`.
+2. **A-Team Super Image Extractor** — `lpunpack` based dynamic partition extraction.
+3. **A-Team EROFS / EXT4 Image Rebuilder** — supplied unpack/repack scripts (Linux-oriented).
+4. **A-Team Super Image Creator** — dynamic `super.img` creator.
+5. **A-Team Vendor Boot Extract / Rebuild** — vendor_boot ramdisk extraction/rebuild.
+6. **A-Team Vbmeta Security Disabler** — supplied vbmeta flashing workflow.
+7. **A-Team Android Image Kitchen** — supplied Windows/Linux image kitchen.
+8. **A-Team Terminal** — command console with copyable output.
+
+## Device controls
+
+The main window exposes quick buttons for:
+
+- `adb devices`
+- `adb reboot`
+- `adb reboot recovery`
+- `adb reboot bootloader`
+- `fastboot devices`
+- `fastboot reboot`
+- `fastboot reboot recovery`
+- `fastboot oem unlock`
+- `fastboot flashing unlock`
+
+Unlock commands require confirmation because bootloader unlocking can erase user data.
+
+## Platform Tools
+
+The toolkit is wired for Google's official Android SDK Platform-Tools (`adb` and `fastboot`). The current development environment could not retrieve the binary archives directly, so the release contains bootstrap scripts rather than redistributing Google binaries:
+
+- Linux: `./setup-platform-tools-linux.sh`
+- Windows: `setup-platform-tools-windows.bat`
+
+The scripts download the official packages from Google's current Platform-Tools endpoint and place only `adb` and `fastboot` into `platform-tools/linux` or `platform-tools/windows`.
+
+Official release page: https://developer.android.com/tools/releases/platform-tools
+
+## GTK3 prerequisites
+
+Linux typically needs GTK3 + PyGObject, for example on Debian/Ubuntu:
+
+```bash
+sudo apt install python3-gi gir1.2-gtk-3.0
+```
+
+Windows requires a Python distribution with GTK3/PyGObject available. The launcher reports startup errors instead of silently opening a blank window.
+
+## Launch
+
+Linux:
+
+```bash
+./run-linux.sh
+```
+
+Windows:
+
+```bat
+launcher.bat
+```
+
+The architecture is module-first: each directory under `modules/` contains a manifest and `module.py`, so future A-Team packages can be dropped in without changing the application shell.
+
+## Device controls
+The main window provides ADB and Fastboot controls, including ADB sideload and Fastboot getvar all. ADB Logcat writes timestamped text files into the root `Logcat/` directory and can be stopped from the same control.
+
+Place the supplied platform binaries at `platform-tools/windows/adb.exe`, `platform-tools/windows/fastboot.exe`, `platform-tools/linux/adb`, and `platform-tools/linux/fastboot`. The application also falls back to PATH when a bundled executable is absent.
+
+Module 8 is the A-Team Magisk Boot Patcher. The terminal is Module 9.
+
+## Bundled platform tools
+
+Android SDK Platform-Tools are bundled in `platform-tools/windows` and `platform-tools/linux` from the supplied archives. The GUI automatically selects the correct `adb` and `fastboot` for the host platform; no separate Platform Tools setup button is required.
+
+The Device Tools panel is collapsible and contains ADB/Fastboot actions, ADB sideload ZIP selection, and Logcat capture to the root `Logcat/` folder.
+
+## Magisk Boot Patcher
+
+Module 08 now presents the supplied A-Team Magisk 0.07 patcher through the same file/browse/options/log workflow used by the Super Image Creator. The supplied patcher binaries are Linux ELF and are therefore enabled on Linux; the original source is retained unchanged inside the module.
+
+## v0.5.4 UI
+
+- Device Tools now uses the A-Team/Android cyber-tech banner as the dropdown background.
+- Device command hit targets are overlaid on the artwork, so the visible controls remain real GTK actions.
+- Device Tools themes: A-Team Green (Default), A-Team Blue, A-Team Purple, A-Team Orange, A-Team Cyan, A-Team Red, and A-Team Pink.
+- Header and module sidebar styling updated to match the A-Team visual concept.
+- Fixed ADB/Fastboot command execution so the executable name is not passed twice.
+- ADB sideload and Logcat controls are kept inside the banner layout and remain clickable.
+
+## Integrated updater
+
+The Device Tools header includes **Check for Updates**. The updater reads `Updates/version.json` from the A-Team Git repository, compares the published `display` version with the installed toolkit version, and can download/install the referenced `.7z` package. An optional `sha256` field can be supplied in the JSON for archive verification before installation.
+
+Expected update metadata fields:
+
+```json
+{
+  "version": "2",
+  "display": "1.2",
+  "file": "A-Team-Android_Image_Toolkit-v1.2.7z",
+  "changelog": "Release notes here",
+  "sha256": "optional sha256 hex digest"
+}
+```

Updates/version.json

@@ -0,0 +1,6 @@
+{
+    "version": "2",
+    "display": "1.1",
+    "file": "A-Team-Android_Image_Toolkit-v1.2.7z",
+    "changelog": "Fixed Linux folder launching so the desktop file manager opens as the invoking desktop user instead of inheriting the toolkit's root privileges. Module 3 (EROFS / EXT4 Rebuilder) no longer opens its module working-folder root; it opens the concrete extracted image folder when available.- Applied the non-root folder opener to the other module folder-opening actions as well."
+}