Release v1.4
This commit is contained in:
parent
41dfd5b788
commit
93dca4deb3
10 changed files with 181 additions and 36 deletions
56
README.md
Normal file → Executable file
56
README.md
Normal file → Executable file
|
|
@ -29,16 +29,28 @@ The main window exposes quick buttons for:
|
|||
|
||||
Unlock commands require confirmation because bootloader unlocking can erase user data.
|
||||
|
||||
## Project layout
|
||||
|
||||
- `src/` — application source (`core/` and `gui/`)
|
||||
- `modules/` — toolkit modules and their bundled tools
|
||||
- `scripts/` — launcher, Windows bootstrap, hidden launcher, and update helper
|
||||
- `tools/` — bundled command-line tools; development helpers are under `tools/dev/`
|
||||
- `config/` — Python dependency requirements
|
||||
- `assets/` — application artwork
|
||||
- `Project_Working_Folders/` — persistent per-module working directories
|
||||
|
||||
The root directory is intentionally kept for user-facing launchers, documentation, licensing, and project metadata.
|
||||
|
||||
## 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:
|
||||
The toolkit bundles the Android platform tools it needs in:
|
||||
|
||||
- Linux: `./setup-platform-tools-linux.sh`
|
||||
- Windows: `setup-platform-tools-windows.bat`
|
||||
- Linux: `platform-tools/linux/`
|
||||
- Windows: `platform-tools/windows/`
|
||||
|
||||
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`.
|
||||
The GUI automatically selects the correct `adb` and `fastboot` for the host platform and falls back to PATH when a bundled executable is unavailable. No separate platform-tools setup step is required.
|
||||
|
||||
Official release page: https://developer.android.com/tools/releases/platform-tools
|
||||
Official Android Platform-Tools information: https://developer.android.com/tools/releases/platform-tools
|
||||
|
||||
## GTK3 prerequisites
|
||||
|
||||
|
|
@ -55,42 +67,22 @@ Windows can use an existing Python distribution with GTK3/PyGObject. If `gi` is
|
|||
Linux:
|
||||
|
||||
```bash
|
||||
./run-linux.sh
|
||||
./START_LINUX-A-Team-Android_Image_Toolkit.sh
|
||||
```
|
||||
|
||||
Windows:
|
||||
|
||||
```bat
|
||||
launcher.bat
|
||||
START_WINDOWS-A-Team-Android_Image_Toolkit.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.
|
||||
The launcher and supporting bootstrap/update scripts live under `scripts/`; they are implementation details and normally do not need to be run directly. The application source lives under `src/` and is loaded from there by the launchers.
|
||||
|
||||
## 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.
|
||||
The architecture is module-first: each directory under `modules/` contains a manifest and `module.py`, so future A-Team packages can be added without changing the application shell.
|
||||
|
||||
## 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.
|
||||
Module 08 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.
|
||||
|
||||
## Integrated updater
|
||||
|
||||
|
|
@ -101,8 +93,8 @@ Expected update metadata fields:
|
|||
```json
|
||||
{
|
||||
"version": "2",
|
||||
"display": "1.2",
|
||||
"file": "A-Team-Android_Image_Toolkit-v1.2.7z",
|
||||
"display": "1.3.1",
|
||||
"file": "A-Team-Android_Image_Toolkit-v1.3.1.7z",
|
||||
"changelog": "Release notes here",
|
||||
"sha256": "optional sha256 hex digest"
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue