Power-key leakage
Disconnect the side-key flex and compare PWRKEY_N behavior before suspecting PMIC/SoC.
ANDROID DIAGNOSTICS / BOOT • RESTART • HANG
Boot / Restart
Boot / Restart
deep diagnostic engine
Separate early boot, storage/RAM, kernel/peripheral and power-trigger faults using current behavior, rail state, GR, reset/clock signals and USB/boot evidence.
BOOT STAGE FLOW
PWRVBAT / PON
APClock / Reset
RAMTraining
UFSBoot media
KERNELDrivers / HAL
Current and logo stage are evidence of progression, not proof of a specific BGA fault.
01 — FAILURE ENTRY POINT
Choose what the phone actually does
The uploaded source uses these symptom families to route the technician into different boot stages.
02 — DC CURRENT PROFILER
Read the shape, not only the number
The uploaded source provides several characteristic current behaviors. AIFlasher treats them as stage clues requiring confirmation.
SIMULATED CURRENT CURVEPattern
03 — HARDWARE BOOT EXECUTION TREE
Verify the stage before moving downstream
Searchable stage tables preserve the uploaded source structure: voltage, GR, signal behavior and failure interpretation.
3 stages
04 — BOOT RAIL / SIGNAL DATABASE
Voltage + GR + scope state in one table
Source values are kept as source references. Exact model and board revision data should override them whenever available.
0 points
| Test Point / Signal | Category | Voltage | GR | Scope / Logic | Stage | Evidence Note |
|---|
05 — LIVE LINE EVALUATOR
Compare one boot line
Use the uploaded source's line-evaluator idea, but report deviation and confirmation steps instead of declaring a component fault automatically.
Enter at least one measurement.
EVIDENCE ENGINE
Combine stage + current + USB state
Combine several observations to strengthen the stage conclusion.
06 — RAPID TRIAGE
Check physical causes before BGA work
The uploaded source includes common physical restart traps. AIFlasher keeps them as checks, not guaranteed causes.
Battery / BMS voltage collapse
Measure battery voltage under CPU load; a weak pack or high-resistance path can cause restart under current peaks.
Peripheral bus pull-down
Camera, audio, sensor or sub-board faults can pull a shared bus low and trigger later-stage restart behavior.
Thermal / NTC open path
Battery or sub-board thermal inputs can stop boot or charging logic depending on platform policy.
Storage power/link instability
Confirm VCC/VCCQ and activity under load before concluding UFS/eMMC failure.
Clock / reset instability
Use a suitable scope/probe and verified test point before escalating to CPU rework.