tech-division/develop./about
kakel/tech
get started↗
[01]phonetoolkit·desktop refurbisher kit

phonetoolkit.
the desktop kit licensed refurb shops
actually use.

Built originally for KAKEL Store's own returns floor and orphan queue, now licensed to other refurb operations. Carrier-orphan SIM unlock, iPhone DFU recovery, blacklist intelligence, and audit-grade evidence export. macOS shipped and signed; Windows and Linux builds in public beta.

see pricing↗read the docs
ships onmacOSwindows · βlinux · β
// where it runs · §01

three operating systems.
one workflow.

Same recipes, same SQLite schema, same evidence-bundle format on every platform. License once, install everywhere your techs sit.

macOS

stable
Apple Silicon · Intel

Signed with Apple Developer ID. Native arm64 build.

windows

public β
x86_64

PyInstaller build pipeline ready · Authenticode signing in setup. Full parity except cfgutil.

linux

public β
x86_64 · arm64 (deb · rpm)

AppImage + distro packages. libimobiledevice via system libs.

// what's in the kit · §02

eight recipes. one license key.

  • ▸ carrier xlsx import (AT&T format library)orphan queue distributed across techs
  • ▸ samsung SIM unlock chainNCK service-call · SNR sibling lookup · secret-code playbooks
  • ▸ mediatek BROM mode partition dumpfor chipsets where userdata wipe is the unlock
  • ▸ iPhone DFU / Recovery restoreidevicerestore + libimobiledevice
  • ▸ Activation Lock detectionHello-screen observation + cfgutil (Apple Configurator)
  • ▸ cross-reference against KAKEL blacklistplus Companion APK provenance records
  • ▸ evidence-bundle PDF generationfor Apple Support / carrier escalation
  • ▸ local SQLite + optional cloud syncsync available on Pro Plus tier
// supported · §03
samsung
Exynos · MediaTek · Qualcomm — NCK chain and service codes
Apple iPhone
DFU restore + Activation Lock observation (every chip A7 → A18 Pro)
MediaTek-based
BROM-mode userdata wipe for OnePlus, Realme, Xiaomi, Tecno
// honest about · §04
what phonetoolkit will not do.
  • ✗iCloud and Activation Lock bypass are not possible. We detect and document, full stop.
  • ✗Samsung Odin write on modern Exynos — we hit a vendor wall and have not solved it.
  • ✗Android 14+ FRP bypass requires owner credentials. We do not market workarounds.
// who it is for · §05

licensed dealers and authorized repair operations processing volume.

Typically 50+ devices per month, multiple techs, and a need for a defensible audit trail.

[01]
refurb operations

You buy returned and orphaned lots from carriers and need to clear them before resale.

[02]
repair chains

Multi-location shops that want one consistent toolset across technicians with a shared records database.

[03]
e-com returns processors

Reverse-logistics operations that verify, unlock, wipe, and document devices for re-listing.

pick a plan. get your license key.
start clearing tonight.

see pricing→create account