Pixel eSIM Failure / eUICC Chip Malfunction
Since the system update version 260305, there have been numerous reports of eSIM failures. The symptoms are that eSIMs cannot be added or removed, and checking *#*#4636#*#* shows the available eUICC bytes as -1. The models most affected are the Pixel 9 series, including: Pixel 9 Pixel 9a Pixel 9 Pro Pixel 9 Pro XL Pixel 9 Pro Fold This issue can occur across all regional variants, including US, JP, AU, and GB. The Root Cause (Trigger Condition) As a smartphone reseller, I have identified the exact operation most likely to trigger this permanent failure: Updating to version 260305 (or later), unlocking the Bootloader, and then re-locking it. This specific sequence carries an extremely high risk of bricking the eSIM functionality. This process is highly common because it mirrors the standard automated workflow when flashing firmware via flash.android.com. Consequently, users trying to return to stock or clean-flash their devices are triggering this glitch very easily. Important Recommendations: DO NOT update to the 260305 system version if you plan on flashing your device. If you are already on version 260305 or newer, DO NOT attempt to unlock the bootloader. If your bootloader is already unlocked, DO NOT try to lock it back under any circumstances. Current Google Status As of now, Google has not released any official explanation or acknowledgement. Their current after-sales policy seems to be offering repairs or replacements only for devices still under warranty. However, since the majority of cases involve the Pixel 9 series—which has been out for nearly two years now—many users are already out of warranty and left stranded.
Posted Jun 17, 2026, 1:12 PM UTC