Native Shell
Native Shell: AI-generated UI, native in your app, on every platform. Apps on iOS, Android, macOS, Windows and Linux, GPUI apps and web pages load signed, sandboxed TSX modules at run time and draw th
Pull Sony Xperia stock firmware (Xperia Companion or Sony ESS API) and root the Xperia 1 IV with KernelSU Next. Windows toolkit + reverse-engineering notes.
Developer toolsGitHub @nsozturkOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
Free Windows toolkit to pull Sony Xperia stock firmware from Xperia Companion or Sony's ESS distribution API, extract boot.img from .sin, and root the Xperia 1 IV with KernelSU Next — plus adb data-migration tools.
Taken from the repository README
Loading the full README.
Read the full README ↗xperia-firmware-toolkit is a free, open-source Windows toolkit for pulling Sony Xperia stock firmware — straight from Xperia Companion or from Sony's own ESS distribution API — and rooting the Xperia 1 IV (XQ-CT72 / PDX223) with KernelSU Next. It documents how Xperia Companion works internally, where it drops firmware, and how to fetch the exact same files directly, then takes you through unlock → patch → root and (bonus) adb-based data migration between phones.
⚠️ For your own devices and security research. Unlocking a Sony bootloader wipes the device and revokes DRM keys. No Sony firmware is redistributed here — only the method and tooling. Every device token/ID/serial in the examples is redacted.
.sin bundle as it downloads..sin format.boot.img, patch with KernelSU Next,
fastboot flash boot, then Zygisk + PlayIntegrityFix + TrickyStore.| Path | What |
|---|---|
docs/xperia-companion-reverse-engineering.md | How Companion works + the MITM/JRE-truststore method |
docs/xperia-companion-firmware-capture.md | Where firmware lands on Windows + capture |
docs/sony-ess-api-direct-download.md | The ESS API chain (Companion-less download) |
docs/rooting-guide.md | Full bootloader-unlock → KernelSU Next → Zygisk/PIF/TrickyStore walkthrough |
firmware-capture/watch_firmware_win.ps1 | Watches Companion and copies firmware parts as they land |
mitm/log_urls.py, mitm/capture.ps1 | mitmproxy addon + transparent capture launcher |
data-transfer/*.ps1 | adb migration tools (contacts, SMS, media, APKs) |
tools/ | Bundled third-party root/ad-block/SSL-unpinning tools (see tools/CREDITS.md) |
examples/*.xml | Redacted ESS API responses |
# Capture firmware while Xperia Companion "Software repair" downloads it
powershell -ExecutionPolicy Bypass -File firmware-capture\watch_firmware_win.ps1
# Extract contacts from a source phone over adb
powershell -ExecutionPolicy Bypass -File data-transfer\contacts_to_vcf.ps1
Set $Serial and paths at the top of each script first. You need Android
platform-tools (adb/fastboot) on PATH.
No. This project shows two routes that don't use XperiFirm: capturing the files Xperia Companion downloads, and calling Sony's ESS distribution API directly.
Under %LOCALAPPDATA%\Sony\Xperia Companion\<InstallTime>\localstorage\<REGION>\
as FILE_<contentId> (a ZIP of all partition .sin files). Details in the docs.
Yes — Sony bootloader unlock (which wipes the device and revokes DRM keys) is required before flashing a patched boot image.
.sin file?Strip the SIN header up to the ANDROID! magic (offset 3584 on the analysed
build); the remainder is a valid boot image. See the RE notes.
No. Companion uses standard TLS with its own JRE truststore; a trusted MITM CA
imported into jre\lib\security\cacerts is enough — and even that is optional
because the firmware tokens are already in services.json.
.sin/FTF firmware over the flashmode protocol.
Complementary: use it to flash what you capture here.MIT — see LICENSE. Not affiliated with Sony. "Sony" and "Xperia" are trademarks of their respective owners; firmware is their property.