Diagnostic Engine

From Symptom to Repair Direction

A structured, repeatable process — convert uncertain repair situations into verified, actionable direction with evidence at every step. No guesses, no fake compatibility claims.

Step 01

Enter Device

Model, variant, storage type, firmware region — logged first as session context.

 Step 02

Add Evidence

Tool log, photo, current reading, error code, chip marking — collected before analysis.

 Step 03

Analyze Direction

Software mismatch, storage fault, boot bus issue, IC-level suspect — categorized with confidence.

 Step 04

Verify Proof

Check required proof — bench or field — before any final repair decision.

 Step 05

Save Case

Build reusable verified technician knowledge with full documentation and source.

 Side Module

Firmware Risk Check

OTA vs Factory vs Fastboot vs Odin vs Scatter vs EDL separation. AVB / anti-rollback aware.

Engine Core Policies

The diagnostic engine reads its rules from JSON policy files. No fake compatibility, no random direction.

Evidence Levels

  • schema: AIFlasher Evidence Levels
  • version: 1.0.0
  • principle: No final diagnosis without evidence. Confidence is capped by evidence quality.
  • levels:
  • rules:

Risk Policy

{
    "schema": "AIFlasher Risk Policy",
    "version": "1.0.0",
    "levels": {
        "low": {
            "meaning": "Safe checks, visual inspection, driver/cable checks, simple external measurements.",
            "ui_color": "green"
        },
        "medium": {
            "meaning": "Firmware or board measurement required. Wrong action can worsen fault.",
            "ui_color": "amber"
        },
        "high": {
            "meaning": "Wrong action can cause dead boot, data loss, storage damage, or board damage.",
            "ui_color": "red"
        },
        "critical": {
            "meaning": "Stop and verify before action. Safety, data, or security risk.",
            "ui_color": "dark_red"
        }
    },
    "automatic_risk_rules": [
        {
            "condition": "instant_high_current",
            "risk_level": "critical",
            "reason": "Possible short circuit or unsafe power condition."
        },
        {
            "condition": "battery_heating_or_swelling",
            "risk_level": "critical",
            "reason": "Battery safety risk."
        },
        {
            "condition": "preloader_operation",
            "risk_level": "high",
            "reason": "Wrong preloader may cause dead boot."
        },
        {
            "condition": "storage_replacement_or_reball",
            "risk_level": "high",
            "reason": "Storage work requires identity, voltage, bus-line, and tool evidence."
        },
        {
            "condition": "cpu_ram_rework_direction",
            "risk_level": "high",
            "reason": "CPU/RAM work must not be performed from current draw alone."
        },
        {
            "condition": "customer_data_operation",
            "risk_level": "critical",
            "reason": "Requires customer consent and backup attempt."
        },
        {
            "condition": "ntc_abnormal_charging",
            "risk_level": "medium",
            "reason": "Charging is temperature-protected; do not bypass NTC permanently."
        }
    ]
}
Do-Not-Do Rules
• AIFlasher Do Not Do Rules
• 1.0.0
•
•