SIM2 disabled in LOS 16, stuck like that in 17.1

[skythe83]

Hi All,

TLDR:
- LineageOS 16, Dual-SIM
- Deactivated second sim in the settings
- Updated to LOS 17.1
- SIM is still deactivated, no button to enable
- Looking for ways to remove SIM card settings

before upgrading from LineageOS 16 to 17.1, I had my second sim card disabled via the general slider (it's my business sim, and I was on vacation). This slider feature now seems to be gone in LOS 17 but the sim is still in a disabled state, meaning LOS is not even asking me for a pin on boot, instead I receive a message saying "Adroid System" / "There's an internal problem with your device. Contact your manufacturer for details". I can still see the sim in the settings (which actually freeze if I try to change carrier settings), and the sim is visible in the top bar with zero reception and the "x". I can still use the sim card in other phones, but the OP3T seems to have memorized the sim card settings somewhere, regardless of which sim slot I use. My solution would have been to delete the per-sim settings, that LOS seems to be storing somewhere, but I have no idea where they could be located.
Any pointers or other ideas would be much appreciated. Thanks!

 

[aurelieng]

Same issue here:

System:

- Hardware: OnePlus 3T
- Firmware: 9.0.3
- Recovery: TWRP 3.3.1-1
- Software: LineageOS April 25, 2020

Symptom:

Dual SIM issue: SIM1 (in slot1) works as expected. SIM2 (in slot2) never connects to its network. I use SIM1 mainly for calls, SIM2 mainly for data.

Tried:

- to update firmware to 9.0.6, no change
- to swap SIM1 and SIM2, SIM1 still works in slot2, SIM2 does not work even in slot1, no change
- to remove SIM1 and keep only SIM2 (slot1 or slot2), no change.
- to use different bands GSM/WCDMA only for SIM1 (was GSM/WCDMA/LTE) and LTE only for SIM2 (was GSM/WCDMA/LTE), no change

Hints:

- when I installed LOS17.1, SIM2 was probably locked (I only unlock it when I used mobile data)
- at boot, only PIN1 is asked, not PIN2
- in SIM2's menu, choosing "Advanced > Access point names" crashes `Settings`.
- when SIM1 is not inserted, only SIM2, the `Mobile data` icon in `Quick tiles` does nothing

I looked in this XDA thread dedicated to LineageOS 17.0/17.1 on OnePlus 3/3T, and found several messages complaining about SIM cards not being detected. The problem seems different and the solution suggested is outdated, since the line is now already in `init.qcom.rc`.

The most similar issue is this thread, I cross posted in reddit. I searched gerrit for `dual sim` in the lineage-17.0 and lineage-17.1 branches as well `sim` in the oneplus_oneplus3 tag, without success.

Any idea?

 

[aurelieng]

Summary: `/data/system/radio` seems to be broken. Should be replaced with the same directory from a clean install. This breaks PIN auth, which means that
`/data/system/locksettings.db` has to be removed as well, and the PIN reconfigured.

Steps:

0. reboot in TWRP
1. backup broken `data` partition
2. wipe data partition
3. adb sideload `lineage-17.1-20200423-nightly-oneplus3-signed.zip` and `open_gapps-arm64-10.0-nano-20200516.zip`
4. reboot in system
5. make sure that both SIM cards are unlocked and working
6. reboot in TWRP
7. backup working `data` partition (or copy `/data/system/radio` somewhere)
8. restore broken `data` partition
9. move `/data/system/radio` to `/data/system/radio_broken`
10. put instead `/data/system/radio` extracted at step 7, either by gunzip/untar backup, or from the "somewhere" you selected
11. delete `/data/system/locksettings.db`
12. reboot into system
13. unlock both SIM cards
14. set a PIN

Done

 

[Notor1ouS-]

why are the devs unable to solve that with an update or flashable zip?

 

[nvertigo67]

why are the devs unable to solve that with an update or flashable zip?

Clean flashing on major version bumps will always avoid this issue in the very first place. In my opinion there are much more important topics for a dev to focus on then getting dirty upgrading major versions fool-proof as long as clean flashing works flawlessly and fool-proof.

 

[Notor1ouS-]

i disagree on that. a competent dev should be able to do that.
but that's going nowhere anyway, so I'm out.

 

[nvertigo67]

i disagree on that. a competent dev should be able to do that.
but that's going nowhere anyway, so I'm out.

If you have the competences and the knowledge to fix issues from dirty upgrading, go ahead, dirty upgrade and fix the issues.
If you don't have the competences and the knowledge to fix issues from dirty upgrading, go ahead and clean flash as recommended on major version bumbs.
If you don't have the competences and the knowledge to fix issues from dirty upgrading and you are resistent to recommendations, blaming the devs as incompetent will polish your ego but don't fix the issue.

For a community driven open source project, you can easily push a fix instead of blaming the devs as incompetent!

Be a user - not a customer.