What they did
The poster bought a used Korean Galaxy S25 Ultra on a trip and knew Korean firmware does not work with Jio's 5G in India. They turned on developer mode, plugged the phone into a Mac with ADB installed and let the Claude Code CLI drive it. Its first suggestions were generic: flash Indian firmware, which could trip Knox, or try dialer codes found online. The poster pushed it to inspect the device itself. It then read the telephony service's transaction codes out of framework.jar and used an adb service call to turn standalone 5G back on. When the phone still saw Jio cells but would not register, the poster asked for the actual rejection, so it pulled modem logs through the SysDump dialer menu and found a modem config file that allowed standalone 5G only on SK Telecom and test networks. It switched the USB port into Qualcomm diagnostic mode from adb and wrote a Python script over libusb to append Jio's network codes to that file.
How it went
After a reboot the phone showed Jio True5G on standalone n78. The poster says this needed no root and no reflash, and Knox stayed intact. The script backed up the original file, wrote only if the bytes matched what it expected, read the result back and was set to roll back on any mismatch. Two of Claude Code's early guesses, a dialer-code trick and an IMEI filter on Jio's towers, were wrong; the logs settled it.
Worth knowing
The useful turn came when the poster refused advice copied from the web and asked the agent to prove each theory from the device's own logs. Writing to the modem's config over diagnostic mode can brick a phone if it goes wrong, which is why the backup and readback check matter. The thread had no comments confirming or disputing it, and the codes are specific to Samsung's Korean firmware.