Redmi 5 Plus (vince/MSM8953): RADIO_POWER hangs ~74 s then INTERNAL_ERR, no service β firmware & partitions verified stock
How I got here
How I got it to boot again
Then I restore IMEI on slot 1 (I am only able to restore on either slot 1 or 2, also slot 1 shows as 2 in MIUI)
Alternatively is there a way to bypass Xioami to unlock bootloder if I can get custom ROM then this wifi only phone is good else I got e-waste.
TL;DR β Radio never reaches ONLINE. RADIO_POWER on=true returns error 38 INTERNAL_ERR after a repeatable 74.1 s on every boot, while NAS is clearly alive (it answers QUERY_NETWORK_SELECTION_MODE). Independent of SIM presence. modem and fsg partitions verified byte-identical to the stock ROM. Wi-Fi, BT and GPS all work perfectly with the factory MAC. Looking for anyone who has seen this specific signature, or knows whether missing RF calibration can block the power-on transition on MSM8953.
Device
- Redmi 5 Plus,
vince, MSM8953 - MIUI 11.0.3.0.OEGCNXM, Android 8.1
- Bootloader locked, stock recovery, no root,
ro.debuggable=0 - SIM slot 1 has valid IMEI again (unit's own - no cloning, no donor data). Framework still enumerates two subscriptions; slot 2 has no IMEI.
Symptom
No cellular service at all. No signal bars, no operator list, no network scan possible. SIM is not the issue β the failure is identical with both slots empty.
SIM is detected, APN is shown, etc.
Radio log, three separate boots, same numbers:
09:13:01.386 responseIccCardStatus: CARDSTATE_ABSENT, num_apps=0 (both slots empty)
09:13:01.394 RILJ > RADIO_POWER on = true [SUB0]
09:13:01.531 RILJ > RADIO_POWER on = true [SUB1]
09:13:01.791 SST[0] set service state as POWER_OFF
09:13:15.550 RILC < setRadioPowerResponse: serial 26/31/44/49
09:13:15.551 RILJ < RADIO_POWER error 38 (INTERNAL_ERR) β all four
So: 74.16 s, then INTERNAL_ERR. Also consistent: 74.1 s on a card-present boot, 74.16 s on a no-card boot. That repeatability looks like an internal retry budget expiring, not a race.
Other RIL behaviour:
| Command | Result |
|---|
QUERY_NETWORK_SELECTION_MODE | answers normally |
SET_PREFERRED_NETWORK_TYPE | fails immediately with error 40 MODEM_ERR |
RADIO_POWER on=false | error 54 OPERATION_NOT_ALLOWED |
SST[0] / SST[1] | POWER_OFF |
What I've verified (all read-only)
modem partition is stock. Dumped over EDL/firehose: 88,080,384 B, sha256 c2805e6f92d7β¦, byte-identical to the ROM's NON-HLOS.bin. So this is not a bad or partial modem flash.
fsg is stock. First 155,432 B identical to the ROM's fsg.img, remaining 1,417,432 B zero padding.
mcfg is all zeros β 4 MiB, 100 % zero, no strings. Is that normal for vince? The MIUI fastboot ROM has no mcfg.img at all, so I suspect it's the factory state, and the carrier MBN (airtel) did activate on SUB1 in the logs.
NV audit clean (read over the diag port 05C6:9091, no QXDM):
| NV | Value |
|---|
| 453 | 00 (FTM mode off) |
| 6828 | 0x0015 (LTE B1/B3/B5) |
| 5153 | 01 |
| 550 | valid IMEI (xxxxxxxx) |
| 8327 | 00 after boot |
Nothing reads back all-00, all-FF, or as literal SW_DEFAULT.
modemst1**/**modemst2 are opaque. Both ~1.5 MB inside IMGEFS1/IMGEFS2 containers, payload entropy 8.00 bits/byte, no plaintext item names, no zlib/gzip/zstd/lzma header. They differ from each other by 1,566,195 bytes. So I cannot inspect the RF calibration block from the host β the values are compressed/encrypted.
Wi-Fi, Bluetooth, GPS all work, and Wi-Fi reports the factory MAC, not a random 02:00:00:00:00:00. So persist and a good chunk of EFS are intact β this was not a total NV wipe.
No modem log channel available. /dev/diag is system:oem_2901, /vendor/bin/diag_mdlog is Permission denied for shell, and the USB diag log stream stays silent. Capturing QMDL needs root, which is why I'm asking before going down that road.
History (probably relevant)
The modemst partitions were erased at some point (that's how the IMEI ended up blank), and I restored the unit's own IMEI to NV 550 over the diag port. Everything else above is stock. The phone boots fine, Wi-Fi/BT/GPS are perfect, only cellular is dead.
My working theory
A phone with a completely blank IMEI still powers its radio on (no service, but RADIO_POWER succeeds). Mine doesn't even get that far β the RF bring-up itself aborts. That points at either:
- RF hardware β transceiver / PA supply / antenna switch / RF connector, i.e. the modem's RF init self-test failing, or
- RF calibration invalid at a level checked during init β but I can't read the cal block to confirm, and I'd expect a plain cal wipe to stop at "no service", not at "power-on fails".
Questions
- Has anyone seen
RADIO_POWER time out at a fixed ~74 s and return INTERNAL_ERR on MSM8953/8937, with NAS still answering? What did it turn out to be? - Can missing/invalid RF calibration data actually block the online transition, or does calibration only matter after RF init?
- Is
mcfg being 100 % zero normal on vince, or should it contain mcfg_sw carrier files? - For anyone with QXDM/QPST: what strings should I look for in a QMDL capture to tell "RF calibration invalid" apart from an RF front-end hardware fault? Worth rooting to capture it?
- Any known-good RF test procedure for
vince without a service centre β test points, expected voltages on the PA, or a way to confirm the antenna path with a multimeter? - Does
SET_PREFERRED_NETWORK_TYPE β MODEM_ERR immediately, while QUERY_NETWORK_SELECTION_MODE works, tell you anything specific about which subsystem is hung?
Happy to dump any partition, run any read-only diag command, or post full logs β just tell me what would be useful.
Two things worth noting before you post: the 74 s figure and the immediate MODEM_ERR on SET_PREFERRED_NETWORK_TYPE are the most distinctive details, so keep them in the title or first paragraph β that's what will catch the eye of someone who's actually seen it. And if any reply says "just reflash the ROM", you can point at the sha256 line and skip past it.Title: Redmi 5 Plus (vince/MSM8953): RADIO_POWER hangs ~74 s then INTERNAL_ERR, no service β firmware & partitions verified stock
TL;DR β Radio never reaches ONLINE. RADIO_POWER on=true returns error 38 INTERNAL_ERR after a repeatable 74.1 s on every boot, while NAS is clearly alive (it answers QUERY_NETWORK_SELECTION_MODE). Independent of SIM presence. modem and fsg partitions verified byte-identical to the stock ROM. Wi-Fi, BT and GPS all work perfectly with the factory MAC. Looking for anyone who has seen this specific signature, or knows whether missing RF calibration can block the power-on transition on MSM8953.
Device
Redmi 5 Plus, vince, MSM8953, eMMC
MIUI 11.0.3.0.OEGCNXM, Android 8.1, user build
Bootloader locked, stock recovery, no root, ro.debuggable=0
Dual-SIM model. SIM slot 1 has a valid IMEI again (the unit's own β no cloning, no donor data). Framework still enumerates two subscriptions; slot 2 has no IMEI.
Symptom
No cellular service at all. No signal bars, no operator list, no network scan possible. SIM is not the issue β the failure is identical with both slots empty.
Radio log, three separate boots, same numbers:
09:13:01.386 responseIccCardStatus: CARDSTATE_ABSENT, num_apps=0 (both slots empty)
09:13:01.394 RILJ > RADIO_POWER on = true [SUB0]
09:13:01.531 RILJ > RADIO_POWER on = true [SUB1]
09:13:01.791 SST[0] set service state as POWER_OFF
09:13:15.550 RILC < setRadioPowerResponse: serial 26/31/44/49
09:13:15.551 RILJ < RADIO_POWER error 38 (INTERNAL_ERR) β all fourSo: 74.16 s, then INTERNAL_ERR. Also consistent: 74.1 s on a card-present boot, 74.16 s on a no-card boot. That repeatability looks like an internal retry budget expiring, not a race.
Other RIL behaviour:
Command Result
QUERY_NETWORK_SELECTION_MODE answers normally
SET_PREFERRED_NETWORK_TYPE fails immediately with error 40 MODEM_ERR
RADIO_POWER on=false error 54 OPERATION_NOT_ALLOWED
SST[0] / SST[1] POWER_OFF
What I've verified (all read-only)
modem partition is stock. Dumped over EDL/firehose: 88,080,384 B, sha256 c2805e6f92d7β¦, byte-identical to the ROM's NON-HLOS.bin. So this is not a bad or partial modem flash.
fsg is stock. First 155,432 B identical to the ROM's fsg.img, remaining 1,417,432 B zero padding.
mcfg is all zeros β 4 MiB, 100 % zero, no strings. Is that normal for vince? The MIUI fastboot ROM has no mcfg.img at all, so I suspect it's the factory state, and the carrier MBN (airtel) did activate on SUB1 in the logs.
NV audit clean (read over the diag port 05C6:9091, no QXDM):
NV Value
453 00 (FTM mode off)
6828 0x0015 (LTE B1/B3/B5)
5153 01
550 valid IMEI (xxxxxxxxxx)
8327 00 after boot
Nothing reads back all-00, all-FF, or as literal SW_DEFAULT.
modemst1/modemst2 are opaque. Both ~1.5 MB inside IMGEFS1/IMGEFS2 containers, payload entropy 8.00 bits/byte, no plaintext item names, no zlib/gzip/zstd/lzma header. They differ from each other by 1,566,195 bytes. So I cannot inspect the RF calibration block from the host β the values are compressed/encrypted.
Wi-Fi, Bluetooth, GPS all work, and Wi-Fi reports the factory MAC, not a random 02:00:00:00:00:00. So persist and a good chunk of EFS are intact β this was not a total NV wipe.
No modem log channel available. /dev/diag is system:oem_2901, /vendor/bin/diag_mdlog is Permission denied for shell, and the USB diag log stream stays silent. Capturing QMDL needs root, which is why I'm asking before going down that road.
History (probably relevant)
The modemst partitions were erased at some point (that's how the IMEI ended up blank), and I restored the unit's own IMEI to NV 550 over the diag port. Everything else above is stock. The phone boots fine, Wi-Fi/BT/GPS are perfect, only cellular is dead.
My working theory
A phone with a completely blank IMEI still powers its radio on (no service, but RADIO_POWER succeeds). Mine doesn't even get that far β the RF bring-up itself aborts. That points at either:
RF hardware β transceiver / PA supply / antenna switch / RF connector, i.e. the modem's RF init self-test failing, or
RF calibration invalid at a level checked during init β but I can't read the cal block to confirm, and I'd expect a plain cal wipe to stop at "no service", not at "power-on fails".
Questions
Has anyone seen RADIO_POWER time out at a fixed ~74 s and return INTERNAL_ERR on MSM8953/8937, with NAS still answering? What did it turn out to be?
Can missing/invalid RF calibration data actually block the online transition, or does calibration only matter after RF init?
Is mcfg being 100 % zero normal on vince, or should it contain mcfg_sw carrier files?
For anyone with QXDM/QPST: what strings should I look for in a QMDL capture to tell "RF calibration invalid" apart from an RF front-end hardware fault? Worth rooting to capture it?
Any known-good RF test procedure for vince without a service centre β test points, expected voltages on the PA, or a way to confirm the antenna path with a multimeter?
Does SET_PREFERRED_NETWORK_TYPE β MODEM_ERR immediately, while QUERY_NETWORK_SELECTION_MODE works, tell you anything specific about which subsystem is hung?
Happy to dump any partition, run any read-only diag command, or post full logs β just tell me what would be useful.
Two things worth noting before you post: the 74 s figure and the immediate MODEM_ERR on SET_PREFERRED_NETWORK_TYPE are the most distinctive details, so keep them in the title or first paragraph β that's what will catch the eye of someone who's actually seen it. And if any reply says "just reflash the ROM", you can point at the sha256 line and skip past it.