Mobile data completely broken after most recent update

[kyeb]

My Zenfone 10 has been totally unable to connect to any internet over mobile network since the most recent update (35.0604.0404.109).  I'm using T-Mobile in the US.

This sucks, I really liked this phone, and only bought it a year ago. But it's totally unusable without mobile data.

The symptoms are super weird - the status bar shows signal, but there is no connection. It initially shows "4G" or "5G" with the connection not working, then after a minute, the status bar changes to showing an "E." SMS, calls, and WiFi all work fine - it's only internet over the mobile networks. I contacted support, and all they did was walk me through the steps in https://www.asus.com/us/support/faq/1011478/, which I already had tried (except for factory reset).

Is there a fix being worked on for this, or is it time to just give up on Asus and go over to iPhone? This is an insane bug to release.

[JerryAMuller]

After the latest update (35.0604.0404.109), many Zenfone 10 users on T-Mobile, like you, are experiencing mobile data issues despite having signal. Since calls, SMS, and Wi-Fi still work, it’s likely a firmware issue. Try checking APN settings, switching network modes, or testing another SIM. If that doesn't help and ASUS hasn’t offered a fix soon, considering another brand may be understandable.

[kyeb]

Yeah, I almost certainly won't buy another Asus phone after this, it's already caused far too much pain.  Any tips on APN settings? Not sure where to start there.

[Riquende]

Hi Kyeb, this might not be related to the update. I bought my Zenfone last July and after about a month I had the exact same symptoms you're describing, on EE's network in the UK. It did have a connection, showed E, and I'd get notifications I think. Occasionally even load a basic website after waiting a few minutes, but for anything like Google Maps, or Audible etc, forget about it.

In the end I had to RMA the phone and Asus repaired it, and it's been fine since. 

[kyeb]

Interesting @Riquende , sounds similar! Did you try factory resetting? I haven't done that yet, since it's a ton of work, but would rather try that before RMA-ing it.