I’m posting here because I’ve hit a complete wall with Google Fi Senior Support (Case ID: 0-2863000042474) and need visibility on how a software-induced eSIM failure is being handled.
The Situation
I own a US Google Pixel 10 Pro purchased directly through Google Fi (about 15 months old, so just past the 1-year warranty). Right after the November 5 software update, the phone’s eSIM/eUICC completely stopped working, throwing Error T120.
Because the US Pixel 10 Pro is eSIM-only with no physical SIM tray, a dead eSIM turns a flagship phone into a Wi-Fi-only brick. I’ve had to move my line to a backup phone just to keep cellular service.
Why Support’s Handling Makes No Sense
I opened a ticket on November 15 and requested a replacement (RMA) on November 16, given that Google’s own update caused the failure. Instead of addressing a goodwill replacement or giving me a clear resolution path, "Senior Support" has kept me stuck in a repetitive, non-functional troubleshooting loop:
- Ignoring completed steps: I enabled Developer Options, turned on verbose vendor logging, captured full bug reports, and completed a full factory reset on November 19.
- Repeating broken instructions: Support keeps telling me to dial *#*#34284#*#* to pull diagnostic logs—the exact same step I already told them does not work. Even after a full factory reset, dialing the code just clears the dialer instantly with no prompt or notification.
- Ignoring video proof: On November 20, I recorded and attached a screen recording proving the diagnostic code fails immediately on the phone. Still no movement or escalation.
- Ignoring their own documentation: Google Fi’s own troubleshooting guidance for Error T120 on an eSIM-only Pixel 10 purchased from Google Fi points to a replacement device.
Even at 15 months old, a Google-pushed software update shouldn't permanently kill cellular service on an eSIM-only phone and leave the customer with an unusable device. I even offered to factory reset the phone again and ship it directly to Google's engineers so they can inspect what the November 5 update did to the eUICC chip.
At this point, it feels like support is running on autopilot scripts rather than actually reading the case. Has anyone else hit Error T120 after the November 5 update, and how did you get Google to approve a replacement or goodwill exception?
(Note: Keeping my IMEI and email private here, but happy to share them with u/googlefisupport, u/PixelCommunity, or via Reddit Request.)