Nothing is more frustrating when provisioning a single-board computer than an intermittent reboot loop. You flash Raspbian (or a media center distribution like Raspbmc / LibreELEC) onto a known-good SD card, connect a USB Wi-Fi adapter and HDMI display, and boot into the desktop environment via startx. Everything runs smoothly for ten minutes—until heavy filesystem writes or GPU initialization cause the board to reset without warning, entering a continuous 60-second reboot cycle even after stripping away USB and Ethernet peripherals.

1. Why Generic Cell Phone Chargers Trigger 5V Rail Brownouts

The single most common culprit behind Raspberry Pi boot loops is powering the board from a standard mobile phone charger rather than a regulated 5.1V DC power supply. While a phone charger may be rated for 5V @ 1A or 2A, battery charging circuits tolerate significant voltage droop—often dropping to 4.5V under load or across high-resistance 28AWG micro-USB cables.

A Raspberry Pi requires a strict 4.75V to 5.25V operating window on its 5V rail. When you launch an OS installer (like Raspbmc) or start the X11 graphical server alongside a USB Wi-Fi dongle, transient current spikes cause the input voltage to sag below the PMIC reset threshold (~4.63V), triggering an immediate hardware brownout reset.

2. The PTC Polyfuse (F3) Recovery Trap

Why would a board that booted fine yesterday suddenly reboot within two minutes today, even with HDMI, USB, and Ethernet unplugged? On early Raspberry Pi boards (and modern boards equipped with input overcurrent protection), the micro-USB power input passes through a PTC resettable polyfuse (labeled F3 on the underside of the PCB).

• High Resistance After Tripping: If a transient current spike or static discharge trips or partially heats the polyfuse, its internal crystalline structure transitions into a high-resistance state.
• Multi-Hour Cooling Curve: Even after removing peripherals, a partially tripped polyfuse drops several hundred millivolts across its terminals as soon as the SoC draws boot current, causing the board to brown out 60–120 seconds into boot. Full resistance recovery can take 24 to 48 hours—or, if the fuse or LDO voltage regulator (`RG2`) is permanently degraded, require an RMA board replacement.

3. Hardware Multimeter Verification (TP1 & TP2) and Kernel Telemetry

Before RMAing a single-board computer, two diagnostic checks isolate whether the fault lies in the PSU/cable or the board's voltage regulators:

On Linux systems that stay up long enough to accept an SSH session, query the VideoCore firmware power-state register directly:

#!/usr/bin/env bash
# Inspect Raspberry Pi hardware under-voltage and thermal throttling flags
RAW_HEX=$(vcgencmd get_throttled | cut -d= -f2)
STATUS=$((RAW_HEX))

printf "Raw throttled register: %s\n" "$RAW_HEX"
if (( STATUS & 0x1 )); then
  echo "[CRITICAL] Under-voltage currently active (< 4.63V on 5V rail)"
fi
if (( STATUS & 0x10000 )); then
  echo "[WARN] Under-voltage has occurred since last boot"
fi

Key Hardware Reliability Takeaways

• Use Dedicated 5.1V Power Supplies with 18AWG Leads: Avoid thin phone-charging cables; the extra 0.1V headroom compensates for cable resistance during SD card and Wi-Fi burst loads.
• Isolate High-Draw USB Peripherals: Connect external USB Wi-Fi adapters and hard drives through a powered USB hub on early Pi revisions to avoid tripping the input polyfuse.
• Know When to RMA: If voltage across the input rail sags or the board reboots with zero peripherals attached on a verified 5.1V supply, a defective onboard regulator or polyfuse warrants immediate manufacturer replacement.