فاست بوت، تفليش التحديثات، مستخرج Payload، صور super والنسخ الاحتياطي — في برنامج واحد لويندوز.
- English · التحميل · أقسام البرنامج · طريقة الاستخدام · سجل التعديلات · ساهم معنا · موضوع XDA
+ English · التحميل · الأجهزة المدعومة · أقسام البرنامج · طريقة الاستخدام · سجل التعديلات · ساهم معنا · موضوع XDA
Fastboot, OTA flashing, payload dumper, super images, Samsung firmware and backups — in one Windows app.
- العربية · Download · Pages · What's new · Contributing
+ العربية · Download · Supported phones · Pages · What's new · Contributing
@@ -26,6 +26,16 @@ nothing to install.
> 🆕 **A new version.** Fastboot Studio is the new generation of Fastboot Enhance: a new
> interface from top to bottom, new pages, and more protection for the phone.
>
+> **New in 2.8:**
+> - A **?** in the corner of every page opens its help at the side: what the page is for, the steps,
+> what can go wrong for good, and the words it uses. In English and Arabic.
+> - A short **welcome tour** on first start (language, the pages, a quick check of the PC, safety rules),
+> and **What's new** on the first start after an update.
+> - **Samsung USB driver** in one click: downloaded from Samsung, kept only with Samsung's signature, installed.
+> - **Download mode reading** (Odin protocol): a Samsung phone's model, region and partition table (PIT), read over Samsung's own driver. It only reads.
+> - A **rooted boot image** is named before it is flashed, and a recovery suggests *Boot once* first.
+> - The Samsung page shows **Knox**, and the Magisk steps say when to use CSC and when HOME_CSC.
+>
> **New in 2.7:**
> - A **Samsung** page: open Samsung firmware (AP, BL, CP, CSC, or the zip it came in), check every
> file's MD5, take out boot, init_boot, vbmeta, recovery or super with LZ4 undone, and see whether
@@ -82,7 +92,8 @@ nothing to install.
The build is self-contained: .NET, `adb` and `fastboot` (platform-tools 37.0.1) are
included. You only need the phone's USB driver installed in Windows
-(e.g. the [Google USB Driver](https://developer.android.com/studio/run/win-usb)).
+(e.g. the [Google USB Driver](https://developer.android.com/studio/run/win-usb)); for a Samsung,
+the app can download and install Samsung's own driver for you.
An OTA or image can be opened straight away: `FastbootStudio.exe ota.zip`, or drop the
file onto the exe.
@@ -96,6 +107,41 @@ specifically requested by the user or the person installing or operating it.
---
+
+## Supported phones
+
+**The rule:** Fastboot Studio works with any Android phone that has **fastboot** (the bootloader
+or fastbootd) or **adb**. Writing partitions needs an **unlocked bootloader**. How a phone is
+unlocked is decided by its maker, so the app does not do it for you. On phones that use the
+standard command, you can run `fastboot flashing unlock` from the Terminal page; the app warns
+you first that it wipes the phone.
+
+| Phone | With the app | Unlocking the bootloader | Good to know |
+|---|---|---|---|
+| Google Pixel | ✅ Everything | Developer options → OEM unlocking, then `fastboot flashing unlock` | Carrier-locked models (Verizon, for one) cannot be unlocked |
+| OnePlus | ✅ Everything | The same as Pixel | Partitions fastbootd refuses (the modem) are written from the bootloader on their own |
+| Motorola | ✅ Everything | A code from Motorola's unlock site | |
+| Xiaomi, Redmi, POCO | ✅ Once unlocked | Mi Unlock, with a waiting period; the rules depend on the region | After that, fastboot flashing as usual |
+| Sony Xperia | ✅ Once unlocked | A code from Sony's site | Unlocking erases the DRM keys for good (camera quality, some features) |
+| Infinix, Tecno, itel and other MediaTek phones | ✅ On most models | Developer options → OEM unlocking, then `fastboot flashing unlock` (varies by model) | SP Flash Tool is only for reviving a phone in BROM mode |
+| Nothing, Fairphone, ASUS, and phones close to stock Android | ✅ Usually | The standard command | |
+| Oppo, Realme, vivo | ⚠️ Depends on the model | Many models cannot be unlocked at all | adb features work on all of them |
+| Samsung | ⚠️ No fastboot | OEM unlocking, then a long press on Volume up in Download mode | The **Samsung page** checks firmware, roots with Magisk and makes tars for Odin, and the app installs Samsung's driver. Flashing is in Odin for now; built-in flashing is coming |
+| Huawei, Honor | ❌ For flashing | Unlock codes stopped in 2018 | adb features (Phone page, copying files) still work |
+
+**Without unlocking**, these work on any phone, or on no phone at all:
+- **Payload Dumper**, **Image Tools**, **Build Super** and the Samsung firmware tools, which work on files on the PC;
+- the **Phone** page, and copying files on the **Backup** page, over adb;
+- reading a phone's state in fastboot on the **Device** page.
+
+Backing up partitions needs root, which in practice needs an unlocked bootloader.
+
+**Modes fastboot cannot reach:** Qualcomm EDL (9008, for QFIL), MediaTek BROM or preloader
+(for SP Flash Tool), Unisoc download (for ResearchDownload) and Samsung Download (for Odin).
+The **USB check** on the Device page recognises each of them and says which tool it needs.
+
+---
+
## The pages, one by one
@@ -271,7 +317,18 @@ HOME_CSC) for Odin. This page does everything around Odin, and nothing is writte
- **Extract** any image with LZ4 undone (boot, init_boot, vbmeta, recovery, super…). super opens
in Image Tools in one click.
- **Root with Magisk**: a small tar of init_boot (or boot) and vbmeta goes to the phone; after
- Magisk patches it, the patched tar is fetched and checked. Flash it with Odin in the AP slot.
+ Magisk patches it, the patched tar is fetched and checked. In Odin it goes in AP, with BL, CP and
+ CSC from the same firmware (never AP alone): **CSC** the first time, since the first Magisk install
+ needs a wipe, and **HOME_CSC** when updating a phone already rooted. It needs an unlocked bootloader
+ and trips Knox for good.
+- **Knox**: the phone's warranty bit, as it reports it (intact 0x0 or tripped 0x1).
+- **Samsung USB driver**: shows whether it is installed; *Install…* downloads it from Samsung, keeps
+ it only when Windows finds Samsung's signature on it, and runs its installer. It is the driver
+ Odin uses too.
+- **Download mode**: reads a phone in Download mode through the port Samsung's driver gives it,
+ as Odin does: its model, serial, region (CSC), the Odin protocol version and its partition table
+ (PIT), which can be saved as a `.pit`. It sends nothing that writes to the phone, and restarts it
+ afterwards (into Android, or into Download mode again).
- **Tar for Odin**: any images (TWRP's recovery.img, a patched boot…) packed as a `.tar.md5`.
**Why it helps:** the wrong firmware, a bootloader downgrade or a wiped phone are caught before
@@ -338,6 +395,8 @@ Type adb and fastboot commands and run them with the tools that come with the ap
(English, العربية with a full right-to-left layout, 中文, 日本語, 한국어).
- **Updates**: once a day (or with *Check now*) the app looks for a new release, shows what
changed, and downloads it only if you say so; the zip is kept only when its SHA-256 matches.
+- **Help, tour and What's new**: every page has a **?** in its corner with its help; About opens the
+ welcome tour again, and What's new for this version.
---
diff --git a/SamsungUI.cs b/SamsungUI.cs
index 77d67f8..4fed9fd 100644
--- a/SamsungUI.cs
+++ b/SamsungUI.cs
@@ -103,6 +103,27 @@ public static void init()
W.samsung_check_patched.Click += delegate { checkPatchedFile(); };
W.samsung_build_tar.Click += delegate { buildTar(); };
W.samsung_cancel.Click += delegate { cancel?.Cancel(); };
+ W.samsung_driver_install.Click += delegate { DriverUI.InstallSamsung(showDriver); };
+ W.samsung_odin.Click += delegate
+ {
+ OdinWindow.Show(W);
+ showDriver();
+ };
+ showDriver();
+ }
+
+ ///