Original Summary

On 10 Oct a data eSIM I'd just bought showed "No service" on my Galaxy S20 Ultra, and finding out why took about two hours in adb shell. The first fault was on the phone. Network selection was still stuck on manual from an older SIM, so the new one never tried a network it could actually use. That fix alone didn't bring service back. When I then picked each network by hand, all seven refused the SIM with error 38 in the radio log. That points at the provider or its roaming deal, but it's an inference: the phone shows you the refusal, not the reason. So that session is now a screen called SIM Doctor inside ADB Nexus, my app that runs ADB on the phone itself over Wireless debugging (Android 11+, no PC, no root). It's the same access I had from the laptop. It reads the SIM and network state and says what it found, and it asks before it changes anything, like switching selection back to automatic or trying every network one at a time and finishing on automatic. If they all refuse, it drafts a message for the provider from what it found. You can edit it, and it leaves the IMEI out. https://play.google.com/store/apps/details?id=com.metacyber.adbnexus (500+ downloads so far) It won't download, delete or switch eSIM profiles, and it never writes to the modem. Without the ADB pairing it only sees what Android shows any app, which is a lot less. The ServiceMode check is Samsung only. The sweep is slow as well, because the S20's modem took about 150 seconds to answer each manual pick, so it gives every network up to 3 minutes. The only real no-service case it has been through is that one S20, and that eSIM still had no service the same evening.   submitted by   /u/Hour-Measurement-835 [link]   [comments]

  • 情报分类：硬件与数码
  • 分类依据：内容涉及硬件、数码产品或通信卡
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/18 00:29:50