TikTokDeviceGenerator：批量 device_register 设备生成 原文标题：code-root/TikTokDeviceGenerator

You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.
You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert

TikTok Device Generator

Repository: github.com/code-root/TikTokDeviceGenerator · Releases: all versions · Latest: v1.0.0

Desktop GUI (Tkinter) that generates device-registration payloads via Java / unidbg, POSTs them to TikTok’s device register endpoint, and saves results as JSON with batch mode, threading, and optional proxy support.

Documentation: English (this file) · Arabic — README.ar.md

Notice: Use this tool only in compliance with applicable laws and service terms. This document describes technical behavior only.

Search / topics: TikTok account creation (device binding), device_register, device_id / install_id (IID), signed registration payload (Java + native / unidbg), batch device registration, automation, optional proxy. Repository topics on GitHub include account-creation, device-registration, request-signing, tiktok-api, and related labels.

• Maintainer, company & contact

• Deposit QR codes (scan in Binance or any BSC wallet)

What it does

• Builds random inputs (e.g. openudid, timestamps, MAC-like pattern) and passes them to Java through Libs/unidbg.jar, loading natives from Libs/prebuilt/<platform>/.

• Parses the binary payload from unidbg stdout (hex=… block).

• Sends POST to https://log-va.tiktokv.com/service/2/device_register/ with fixed headers and content-type: application/octet-stream;tt-data=a.

• On successful JSON, stores device_id, install_id (and string variants when present) plus metadata.

• In batch mode, runs many devices in parallel with ThreadPoolExecutor; Stop cancels remaining work (in-flight tasks may still finish).

Requirements

Installation

[python](https://github.com/topics/python) -m venv .venv
# Windows:
.venv\Scripts\activate
# macOS / Linux:
source .venv/bin/activate
pip install -r requirements.txt

Install a JDK/JRE and verify java -version. If only 32-bit Java is installed on 64-bit Windows while the app uses win64 natives, unidbg will fail — see Java & native libraries.

Run

python [DeviceGenerator.py](https://github.com/code-root/TikTokDeviceGenerator/blob/main/DeviceGenerator.py)

There is no separate CLI; all options are in the GUI.

Versioned downloads, changelogs, and tagged snapshots: github.com/code-root/TikTokDeviceGenerator/releases

• A prebuilt .exe (when published) will appear under Assets on a release; you still need Libs/ and a suitable Java runtime unless the release notes say otherwise.

Project layout

TikTokDeviceGenerator-main/
├── DeviceGenerator.py # GUI + batch worker + HTTP
├── requirements.txt
├── [README.md](https://github.com/code-root/TikTokDeviceGenerator/blob/main/README.md) # This file (English)
├── README.ar.md # Arabic documentation
├── [assets](https://github.com/code-root/TikTokDeviceGenerator/tree/main/assets)/ # Support / deposit QR images
├── [scripts](https://github.com/code-root/TikTokDeviceGenerator/tree/main/scripts)/ # e.g. verify_environment.py (Java vs Apple Silicon)
├── Libs/
│ ├── unidbg.jar
│ └── prebuilt/ # win64, linux64, osx64, ...
├── Device/ # devices_001.json, ...
└── generated_devices/ # _batch_summary_*.json

• DEVICES_PER_JSON_FILE = 50 — records per file under Device/.

• DEVICE_REGISTER_URL — register endpoint URL.

User interface

Header — app title and short subtitle.

• Start — validates unidbg.jar, Libs/prebuilt/<platform>, counts, threads, and proxy URL (if any).

• Stop — signals cancel; pending futures are cancelled; progress reflects completed work.

• Open output folder — opens the folder path currently shown in Output folder (e.g. os.startfile on Windows).

• Number of devices — 1–9999.

• Threads — 1–64, capped by device count.

• Output folder — path shown in the field and used only for Open output folder.

Important: DeviceGenerator.py always writes device chunks to <project>/Device/ and batch summaries to <project>/generated_devices/, regardless of this field. Change it to open another folder for convenience (e.g. after you point it at generated_devices).

• Proxy URL (optional) — applied to all device_register requests in the batch.

Last device (preview) — read-only OpenUDID, Device ID, IID with Copy buttons; updates on each successful registration in the current batch.

Progress — indeterminate while preparing, then determinate by completed/total; status line combines count/percent and a short message.

Log — per device: URL, headers, hex preview of body, response or errors. request_log is stripped before writing each record to Device/devices_*.json to keep files smaller; the UI still shows full logs during the run.

Output files & JSON

• Files devices_001.json, …; part numbers continue from the highest existing devices_*.json.

• Each file: saved_at, part, devices_per_file, count, and devices: [{ "batch_index": n, "record": { ... } }, …].

• record includes fields like status, input, network, ids, register_response, etc., usually without request_log.

• Each batch run creates _batch_summary_YYYYMMDD_HHMMSS.json with requested_devices, threads, success, failed, completed_tasks, cancelled, paths, chunk size, and network (including proxy_url_masked when a proxy is used).

Default “Output folder” field

• Initialized to <project>/generated_devices via default_output_dir() so it matches where summaries are written; you may edit the field for which folder Open output folder opens.

Proxy

Supported schemes: http, https, socks5, socks5h.

http://127.0.0.1:8080
http://user:password@host:port
socks5h://127.0.0.1:1080

Install requests[socks] for SOCKS. Exported JSON uses proxy_url_masked under network when credentials are present.

Java & native libraries

Approximate invocation from Libs/:

java -Djna.library.path="<prebuilt>" -Djava.library.path="<prebuilt>" -jar unidbg.jar "<message>"

<prebuilt> is Libs/prebuilt/<getsystem()> (e.g. win64 on 64-bit Windows).

get_java_exe() tries JAVA_HOME, a common Windows path, then java on PATH. On 64-bit Windows it prefers a JVM that reports 64-Bit in java -version output.

Apple Silicon (M1/M2/M3): The JNA build inside unidbg.jar only ships a darwin x86_64 libjnidispatch. A default arm64 JDK cannot load it → UnsatisfiedLinkError on a temp jna*.tmp file. Use an Intel / x64 JDK (e.g. Eclipse Temurin macOS x64), set JAVA_HOME to it, and confirm java -XshowSettings:properties -version shows os.arch = x86_64. Quick check from the repo root: python scripts/verify_environment.py.

Troubleshooting

Credits

• Original work attributed to xSaleh — thank you.

• Branding / contact in the app footer is defined in DeviceGenerator.py (e.g. Storage TE).

Maintainer, company & contact

Developer

Mostafa Al-Bagouri

Company

Storage TE

WhatsApp

+20 100 199 5914

Support this project

If this tool is useful to you, optional support helps maintain and improve it. Pick whatever works best for you.

Network: Use BSC (BEP-20) only. This address is for USDT (BEP-20) and BTC on BSC (Binance-Peg / in-app “BTC” on BSC), matching the Binance deposit screens below. Do not send native Bitcoin (on-chain BTC), ERC-20, or NFTs to this address.

Deposit QR codes (scan in Binance or any BSC wallet)

Desktop Tkinter app: batch TikTok device_register via Python + Java (unidbg). Bilingual README (EN/AR).

account-creationautomationbatch-processingcross-platformdesktop-appdevice-fingerprintdevice-iddevice-registrationguiinstall-idjavapythonrequest-signingrequestsreverse-engineeringtiktoktiktok-accounttiktok-apitkinterunidbg

You can’t perform that action at this time.