The current reading is a clue. Keep the rest of the story.

A number without a connection is incomplete

A board draws current according to where power enters, what is connected and which stage of startup it reaches. Feeding a USB input is different from supplying a battery connector. A display, storage device or daughterboard can alter the pattern. Lead resistance and current limit can alter it again. The same front-panel value can therefore describe several different conditions.

Record the exact point of connection and polarity, set voltage, current limit, actual terminal voltage and supply mode. Note what was connected to the board. Add timing: immediate on connection, after a power-button press, briefly pulsing or steady after several seconds. A photograph of the setup often resolves ambiguity that a line of text leaves behind.

A case that connects the tools

iPad Rehab’s published iPhone 8 data-recovery case records roughly 0.36A at a 5V input during its investigation. The team uses a known-good test arrangement, replaces the Tigris device with hot air, prepares pads with an iron and ultimately boots the phone to recover data. The value belongs to that case and connection. It is not a universal “0.36A means Tigris” rule.

The useful structure is observation, hypothesis, intervention and retest. Power behaviour helps form a hypothesis; board inspection and other checks decide whether it is plausible. Thermal tools carry out the repair; the subsequent boot and data extraction establish the reported outcome. Copying only the number removes most of the reasoning.

Keep a small, consistent diary

Use one entry per intervention. Start with the reported fault and a reproducible baseline. Write what you observed before describing what you think it means. Then record the change, including replaced parts, thermal method and any disturbed neighbouring components. Finish with the same baseline test, followed by the relevant functional checks.

An unsuccessful intervention still belongs in the record. A replaced part that changes nothing is useful evidence, provided the replacement and joints were independently checked. Do not rewrite the earlier observation to make the final diagnosis appear obvious. A repair diary is most valuable when it preserves the decision that seemed reasonable at the time.

Avoid familiar shortcuts

No visible hotspot does not establish that a board has no short. A changed current can reflect a disconnected load rather than a repaired fault. A temporary boot after heating does not by itself establish lasting reliability. Distinguish each observation from the claim it can support, especially where customer data or repeated intermittent failures are involved.

iPad Rehab’s older articles contain useful practical history but should not become universal rules. The long-screw case acknowledges uncertainty, and broad phrases in old reflow narratives need device-specific interpretation. Use the cases to study the decision sequence, not to build an automatic diagnosis table from a few readings.

Publish the reusable part

A public case can omit personal data while retaining its test conditions and decision path. Crop or obscure identifiers, obtain appropriate permission and avoid publishing recoverable customer content. The useful asset is the repeatable technical record: another technician should understand what was tested, why a tool was used and what remained uncertain.