Hi ! And thanks for your answers 
It’s effectively Bouygues carrier, but it seems not to be an issue to use its sim.
Here come some Claude conversation i had, with some adb outputs :
This message confirms and further refines the diagnosis — here’s where things really stand:
What can now be ruled out
Thanks to these latest commands, we can rule out several hypotheses:
Not an APN issue (that only comes into play after network registration)
Not a missing RIL/telephony service: qcrilNrd, imsdaemon, com.android.phone, org.codeaurora.ims, netmgrd are all running normally
Not a base Android/framework layer issue (all the phone, telephony.registry, telephony_ims services are registered)
What remains as the core anomaly
There’s a direct contradiction between two sources:
*#*#4636#*#* says: Mobile radio power = ON
The actual ServiceState says: mVoiceRegState=3(POWER_OFF) then OUT_OF_SERVICE, with cellIdentity=null, channel=-1, technology=Unknown
In other words: the Android framework believes it turned the radio on, the Qualcomm processes are running, but the modem never returns any cell info at all — not on 4G, 3G, or 2G, across 13 hours of logs.
This now points to two main hypotheses, not just one
Corrupted or incompatible modem (baseband) firmware — the Android-side processes are running, but the actual low-level dialogue with the Qualcomm chip isn’t happening correctly.
An actual hardware issue (antenna, RF front-end, or the modem chip itself) — increasingly plausible given that all the software looks healthy.
Next step I’m proposing
Before the QCRIL|qcril|RIL|RADIO|modem|SIM|UIM filter already planned (useful, but we already partly have it from earlier logs), I’d add this to settle it:
powershell
.\adb.exe shell getprop | Select-String "baseband|gsm.version|ril.impl"
→ to see the exact modem firmware version installed.
powershell
.\adb.exe logcat -b radio -d -v time | Select-String "RADIO_STATE_CHANGED|REQUEST_RADIO_POWER|RIL_UNSOL_RIL_CONNECTED"
→ to see whether the modem itself internally confirms a radio state change after Android’s request, or whether the request goes nowhere on the hardware side.
A decisive test to run in parallel: since the Bouygues SIM works in your Honor, can you test another SIM card (even an old inactive plan) in the OnePlus? If no SIM ever picks up a network on this OnePlus, even one you know works elsewhere, that points strongly toward hardware rather than software.
Do you want me to run these commands, or would you rather test with another SIM first?
PS C:\Users\USER\Desktop\platform-tools> PP^C
PS C:\Users\USER\Desktop\platform-tools> .\adb.exe shell getprop | Select-String "baseband|gsm.version|ril.impl"
[gsm.version.baseband]: [Q_V1_P14,Q_V1_P14]
[gsm.version.ril-impl]: [Qualcomm RIL 1.0]
[ro.baseband]: [msm]
[ro.boot.baseband]: [msm]
PS C:\Users\USER\Desktop\platform-tools> .\adb.exe logcat -b radio -d -v time | Select-String "RADIO_STATE_CHANGED|REQUEST_RADIO_POWER|RIL_UNSOL_RIL_CONNECTED"
PS C:\Users\USER\Desktop\platform-tools>
my other SIM doesn’t work in the OnePlus either, but the Bouygues SIM works in the Honor
There you go — that’s the decisive test I was waiting for, and the result is very clear.
Key result: NO SIM card works on the OnePlus at all, while the Bouygues card works perfectly in the Honor
This completely changes the nature of the diagnosis. We can now rule out almost anything software/config-related:
It’s not an APN issue
It’s not a Bouygues card / network compatibility issue
It’s not (solely) a carrier-specific iodéOS firmware issue
It’s not the SIM itself (it works elsewhere)
What remains plausible, in order of likelihood:
Hardware failure of the modem/RF (now the most likely) — disconnected/damaged cellular antenna, faulty modem chip, disconnected RF connector (common after a drop, a teardown, or even a light shock)
Corrupted modem (baseband) firmware at the modemst1/modemst2 partition level (radio calibrations) — possible after a botched prior flash, but less likely since the Q_V1_P14 firmware is present and consistent
Deeper vendor/firmware corruption tied to iodéOS — but increasingly unlikely, since no SIM at all works, which goes beyond the scope of “just an Android software issue”
On your 2nd, empty command output: the fact that RADIO_STATE_CHANGED and REQUEST_RADIO_POWER return no lines isn’t necessarily abnormal — those log strings correspond to the older HIDL RIL, whereas your system uses the AIDL RIL (Qualcomm RIL 1.0 with OplusRadioAidlImpl). So this isn’t an additional signal, just a filter that didn’t match anything in this log format.
What I recommend now
Before any flashing or manipulation:
Check physically/visually whether the OnePlus has recently been disassembled, dropped, or exposed to water — even lightly, this can disconnect the internal cellular antenna (RF ribbon cable).
Check whether Wi-Fi Calling / VoLTE over Wi-Fi would work with a forced config — not to fix the issue, but to see whether the entire RF stack is dead or just classic cellular.
If you have access to a computer with QPST/QFIL (Qualcomm tools) or a OnePlus/Oplus technical center, an EFS/NV modem test would confirm hardware vs. software definitively — it’s the only way to be 100% sure.
Given that no SIM works at all on this phone while another card works elsewhere, I genuinely think we’re now closer to a hardware issue (antenna/RF/modem) than an iodéOS issue. Does the phone have a history of being dropped, repaired, or having its motherboard/ribbon cable replaced recently?
[Thought for 8s]
Good question, but I don’t think that’s it, and here’s why, with the full reasoning:
The LE2125 model is normally France-compatible
The LE2125 is the Europe/Global variant of the OnePlus 9 Pro (as distinct from the LE2121 China, LE2123 India, LE2127 North America/T-Mobile variants). This EU variant supports all the bands used by French carriers: 800/900/1800/2100/2600 MHz on 4G, and n1/n3/n7/n28/n78 on 5G — so Bouygues, Orange, SFR, and Free should all work natively.
Why the symptoms don’t match a band incompatibility
If this were a radio band issue (wrong variant, or a foreign-carrier lock like T-Mobile US), you’d expect to see:
The modem detecting cells but failing to register on them (wrong tech, unsupported band)
Or a manual scan that finds operators but can’t connect to them
Potentially partial functionality (2G/3G working, 4G not, for example)
What you actually have is:
GET_CELL_INFO_LIST returns an empty list continuously, for 13 hours
mVoiceRegState=POWER_OFF then OUT_OF_SERVICE — not “cell found but rejected”
No SIM at all, French or otherwise, picks up anything
A band incompatibility almost never produces total, permanent radio silence like this. It looks much more like the modem literally isn’t “seeing” anything at the RF level, regardless of carrier or country.
The only scenario where the model would matter
If this phone is actually a mislabeled LE2127 (T-Mobile US variant), or a unit locked to a foreign carrier, that could restrict certain bands — but even then, you’d expect to see at least some cell detection on common bands (low 4G bands like B3/B7 are nearly universal). The total silence you’re observing goes beyond a simple band mismatch.
My conclusion stays the same: the symptoms (zero cell detection, across all SIMs, for hours, with the radio reported “ON” at the framework level but no response from the modem) point more toward a hardware RF issue or broken modem firmware, rather than a regional model incompatibility.
Can you check the exact model listed under Settings → About Phone → Model, to confirm it’s really an LE2125 and not an imported variant?
Model LE2125 Hardware version EU
That confirms it: LE2125, EU hardware — this is exactly the correct European variant, fully supports French carrier bands. So we can now definitively rule out any model/region mismatch as the cause.
Where this leaves us
With the model confirmed correct, the remaining explanation is narrowed down to:
-
Hardware failure (most likely) — modem chip, RF front-end, or a disconnected/damaged antenna ribbon cable
-
Corrupted modem firmware/calibration data (in modemst1/modemst2) — less likely but not impossible, especially if there was ever a botched flash, downgrade, or an interrupted OTA update in this phone’s history
Given that:
-
The model/hardware is correct for France 
-
No SIM at all works, not just Bouygues (rules out carrier-specific issues)
-
All Android-side software/services are healthy
-
The radio reports “ON” but the modem returns zero cell data, for 13+ hours straight
…the most honest read of the evidence is that this is very likely a modem/RF hardware problem, not something fixable by reflashing iodéOS or tweaking settings.
What I’d suggest as next concrete steps
-
History check: has this phone ever been dropped, opened, repaired, or had a battery/screen replacement? Even a slightly disconnected antenna cable after a repair is a very common cause of exactly this symptom.
-
Physical inspection if you’re comfortable opening it (or know someone who is) — checking that the RF antenna cables near the SIM tray/mid-frame are properly seated is sometimes enough to fix this.
-
If you want one more diagnostic before assuming hardware failure: try EFS backup + modem firmware reflash via QFIL (Qualcomm’s official flashing tool) using an EDL/9008 mode connection. This is the only way to definitively rule out corrupted calibration data before concluding it’s a hardware fault.
-
If none of that works, this points to sending it to a repair shop for board-level modem/antenna diagnostics, or checking if it’s still under OnePlus warranty.
Do you know if this phone has any repair or drop history, or did the problem appear out of nowhere on a phone that’s never been opened?
————————
End of Claude extract
What do you think guys ? Is he hallucinating ?
Thanks for your answers
) that the LE2125 is intended for the North American market. [EDIT: Method of identifying region by 7th and 8th digit of IMEI not applicable to some phone brands.] Some mobile carriers are picky about regional variants. Although the LE2125’s