Plug in an iPhone — the app pulls the logs and tells you which part is to blame.
English · Українська · Русский
| 🔌 Pulls the logs for you | Connect the cable, tap “Trust” on the phone — the app collects every fault log and shows the model, iOS, IMEI, battery wear and cycle count. |
| 🩺 Tells you what's broken | Not “thermalmonitord panic” but “Charging flex — the phone can't see the bottom microphone and the barometer”. With how the phone behaves, why, and what to do. |
| 📊 Confidence and a chart | “17 of 18 panics point to this part”, plus panics per day — you can see when the trouble started. |
| 🔧 Before and after repair | “Mark repair” — from then on only new faults count: “No panics since the repair ✓”. |
| 🗂 Phone history | Every connected phone with visits, repairs and notes. When a customer comes back, you see what happened last time. |
| 📄 PDF for the customer | A report with the conclusion, the state of each part and your workshop name. |
| 🔎 Error search | A code (4013), a sensor (mic1), a bus (i2c3), a word or a line from a panic — across the database and all logs. Paste panic text from the phone and get the analysis right away. |
| 🌍 Three languages, auto-update | Русский, English, Українська. Like 3uTools: at startup a “New version available” window with the changes, “Update now” downloads with a progress bar and restarts. Your data is never touched. |
| 📱 By model | Pick a model (or it's taken from the connected phone) — connector, Face ID / Touch ID, eSIM, which parts are serialized, where the sensors are, I2C buses and errors typical for that model. |
| 🤝 Grow the database | “Suggest for the database” on any log: the app removes the serial number, IMEI, UDID and paths, shows exactly what will be sent and opens a GitHub issue. |
 Result — problems found, most important first, with explanation and steps |
 Panics per day and what else was found in the logs |
 Parts — the state of each part and its faults in the logs |
 Logs for this part — every panic explained |
 After the repair — only new faults count |
 History — phones, visits, repairs, notes |
 Search across the error database and all logs |
 PDF report for the customer |
Screenshots use demo data.
- Download
iOSPanicReader.exe. - Install Apple Devices from the Microsoft Store (or iTunes) — it provides the iPhone driver.
- If Windows shows “Windows protected your PC” — “More info” → “Run anyway” (the app isn't signed).
- Download
iOSPanicReader-macOS.zip, unzip it, moveiOSPanicReader.appto Applications. - First launch: right-click → Open → Open (the app isn't signed by Apple).
- If macOS says the app is “damaged”:
xattr -dr com.apple.quarantine /Applications/iOSPanicReader.app
No driver is needed on a Mac — it's built in. On Intel Macs run it from source (start.command).
- Launch the app and connect the iPhone with a cable.
- Unlock the phone and tap “Trust”.
- A few seconds later you get the result: what's wrong and what to do.
You can also open logs without a phone: “Open log file…” (panic-full-*.ips files from the phone:
Settings → Privacy & Security → Analytics & Improvements → Analytics Data).
Everything stays on your computer in Documents/iOSPanicReader: logs, phone history, notes, the
workshop name. The app sends nothing anywhere — it only goes online to check GitHub for updates.
Updates never touch your data, and a copy of the history is kept in backups/.
Almost a hundred entries: kernel panics (thermalmonitord, SEP, AOP, NAND, SMC, I2C…), sensors from “Missing sensor(s)” (mic1, prs0, TG0B…), I2C buses per model, iTunes/Finder error codes (9, 4013, 53…), app crash codes (0x8badf00d…) and symptoms (“restarts every 3 minutes”). Every entry lists its sources and reliability: Apple documentation, repeatedly confirmed, or “reported by repair shops”.
The hints are a guide for diagnostics, not a final diagnosis: sensor and bus locations depend on the model.
iActivator — one-click iPhone activation and setup: activation, language, region, Wi-Fi, skipping the setup screens, diagnostics and a PDF report. Windows and macOS, free.
Running from source, building, tests, the database and translations — see docs/DEVELOPMENT.md (in Russian).