After roughly two months of unusable phones, Pixel 4a owners say the boot loop bug is finally gone — killed off by a Google Play system update rather than a full Android update. Affected users report their handsets are booting normally again once July’s Play system release installs, ending a saga that left some people locked out of a working phone since early June.
What the Pixel 4a boot loop bug did
Affected phones simply never finished starting up. They would begin the boot sequence, fail, and restart — over and over, with no way in and nothing the owner could troubleshoot from the inside. Reports centred on the Pixel 4a, with scattered accounts of the same behaviour on the Pixel 4 and Pixel 4 XL, and user feedback consistently pointed at Wi-Fi and location settings as the trigger.
The important detail is where the fault came from. None of these phones has received an Android OS update in years — the Pixel 4a shipped in 2020 and is long past Google’s old three-year support window. Google Play services and the Play system updates that carry them, however, keep arriving regardless, pushed through the Play Store rather than as a carrier-gated OTA. So a component Google still updates managed to break phones Google no longer supports, on devices whose owners had no way to decline the change or roll it back.
Google confirmed a fix, then shipped it quietly
Google acknowledged the problem and, at the start of July, told Android Authority a repair was on the way. A Google spokesperson said “a fix will be going out with the July update,” pointing at the July Google Play system update rather than a special out-of-band patch like the one the Pixel 4a received in January 2025 for its battery problems.
What Google has not done is say so publicly anywhere a Pixel 4a owner would look. The release notes for the July 2026 Play releases — Google Play services v26.29, dated 27 July — list nothing about boot loops, restarts or the Pixel 4 family. The nearest entry is a generic line reading “Bug fixes for System Management & Diagnostics related services.” The evidence that the fix has actually landed comes from affected owners reporting success, not from Google’s own changelog.
If your Pixel 4a is still stuck
The obvious catch is that a phone caught in a boot loop cannot easily reach the Play Store to install the update that fixes it. The workaround being passed around is to turn Wi-Fi data off in the brief window before the phone resets, then try pulling the Play update down over mobile data instead. It is fiddly, and it should not be the resolution path for a bug Google caused — but it is the one that works.
Credit where it is due: Google did investigate and repair a fault on hardware that stopped being its responsibility years ago, which is more than several manufacturers would do. The uncomfortable half of the story is the rest of it. Play system updates reach almost every Android phone in the world, including hundreds of millions that will never see another OS release, and this episode shows what happens when one of them goes wrong on a device with no support channel behind it: two months of a dead phone, no advisory, no entry in the changelog, and a fix you learn about from other users.
Sources: Android Authority
