It started with a glitch that every smartphone owner dreads: the infinite boot loop. My Google Pixel suddenly rebooted, flashed the Google logo, and then died. Over and over.
Initially, I suspected a software bug, but then the power behavior became erratic. I plugged it into my 100W Honeywell PD charger — a beast of a power brick that usually handles my laptop without breaking a sweat. Instead of charging, the battery percentage began to drop while connected. It hit 3%, then 2%, then the device went totally dark. The phone was caught in a “power-deficit loop”: it was too weak to stay on, but every time it tried to boot, it consumed more power than the charger could supply, causing a crash.
I spent the night diving into the mechanics of lithium-ion chemistry and terminal diagnostics to understand what was happening under the hood.
The “Induced Coma” strategy
To break the cycle, I had to stabilize the device. I forced the phone into Fastboot Mode (Power + Volume Down). This is the lowest possible power state for a Pixel; the OS isn’t running, and the processor is idling. This “induced coma” allowed the phone to finally accept a trickle charge from the power brick without immediately burning it off through the boot process.
Diving into the Terminal
Since I run Linux Mint, I connected the phone to my laptop to see the raw data. After a quick fix with permissions to ensure the laptop recognized the phone, I ran:
sudo fastboot getvar battery-voltageThe first reading was a wake-up call: 3751mV (3.75V). This was a revelation — the battery percentage icon on your screen is essentially a software “guess,” but voltage is the physical reality.
- 4400mV: A healthy, full Pixel battery.
- 3400mV: The “death zone” where hardware cuts power for safety.
- 3751mV: High enough to attempt a boot, but too weak to survive the “voltage sag” once the CPU ramps up.
Why phone batteries aren’t like car batteries
I initially thought about this like jump-starting a motorcycle. With a vehicle, you can often revive a deeply discharged battery because it just needs to turn a starter motor once. But smartphone batteries are different.
Unlike a simple lead-acid battery, a phone’s Li-ion cell is chemically volatile. If it stays below its “safe floor” for too long, it can develop copper dendrites — tiny metallic spikes that can pierce internal layers. This creates a massive fire hazard; if you force-charge a compromised cell, it can lead to thermal runaway. The internal Battery Management System (BMS) is designed to “lock” the battery to prevent your pocket from turning into a torch.
The thermal discovery
During the night, I noticed the voltage climbing faster when the phone was sitting near the exhaust fan of my laptop. Heat decreases the viscosity of the internal electrolyte, lowering internal resistance. This accidental discovery confirmed that the battery wasn’t just empty; it was chemically struggling to move ions. The warmth was acting as a catalyst, helping the battery “wake up” enough to accept the current.
However, this is a delicate balance. While gentle ambient warmth (like the laptop exhaust) helped, too high a temperature is equally destructive. Direct heating — like using a hairdryer or leaving it in the sun — can cause the battery to swell or vent. Lithium-ion batteries generally perform normally between 15°C and 35°C (59°F to 95°F). Going significantly above 45°C (113°F) during charging accelerates chemical degradation, meaning the very thing that “woke” the battery up could also kill it if not carefully controlled. Ambient exposure is a tool; direct heat is a danger.
The 83% clue and the final collapse
By morning, the terminal showed 3967mV and the screen claimed 79%. I let it charge further until it hit 83%. I unplugged the wall charger, held my breath, and hit “Start.”
The animation began, and then — instant blackness. Even at 83%, the battery couldn’t sustain a load without the charger as a crutch.
The final confirmation came 12 hours later. I checked the phone, which had been switched off the entire time. The battery had plummeted from 83% to nearly 40% while doing absolutely nothing. This massive “parasitic drain” was the smoking gun. The internal cells were so degraded they couldn’t even hold a static charge, leaking energy into the ether while sitting idle.
The journey moved from troubleshooting a “glitch” to witnessing a total chemical breakdown. I went from fighting with cables to understanding the exact physics of a hardware failure. When a battery hits high internal resistance, it’s like a rotted bridge: it looks stable until you try to drive over it, at which point it collapses instantly. The mystery was solved, but the battery was gone.
Leave a Reply