Solution Lineage OS No Sim

[sebastian79hl]

it seems these steps no longer working for latest build lineage-14.1-20171107-nightly-hlte-signed.zip,no sim detected,or it is just happen to me? anyone else having a problem?

Have you made any Process with this Prob?
I really should have checked the comments before flashing but who is expecting a Problem is even getting worse then before when an official app is offering an update ? doesn't the dev of this build has any channel to contact him or her? Thanks.

 

[sebastian79hl]

Solved

So for everybody that ran into this issue....

There is a solution hidden in the depths of the net.

Simply grab the following file:

https://1drv.ms/u/s!AmCNiDoyEHththrWbctwIzHYWAv-

Shut down your Phone and keep it shut down for a minute.

Open Download Mode (power + volume down + home)

Start Odin and load the File under the AP Tab

Start Flash

After reboot your Sim should be detected

Greetz Seb

 

[Lysathor]

No SIM detected - Solution works for me.

There is a solution hidden in the depths of the net.
Simply grab the following file:
https://1drv.ms/u/s!AmCNiDoyEHththrWbctwIzHYWAv-
Shut down your Phone and keep it shut down for a minute.
Open Download Mode (power + volume down + home)
Start Odin and load the File under the AP Tab
Start Flash
After reboot your Sim should be detected
Greetz Seb

This works for me. SIM and GPS work. THANKS!
It seems that the file contains
BL N9005XXSGBQD5 and CP N9005XXUGBPB1 with date 2017-07-01
@sebastian79hl: Where have you found that firmware? I tried new modems from sammobile.com but that did not work for me.

 

[sebastian79hl]

This works for me. SIM and GPS work. THANKS!
It seems that the file contains
BL N9005XXSGBQD5 and CP N9005XXUGBPB1 with date 2017-07-01

@sebastian79hl: Where have you found that firmware? I tried new modems from sammobile.com but that did not work for me.

After I ran into this problem yesterday I searched for about 2 hours. This firmware was in a thread in the lineages bug forum... Somebody posted this solution there and provided the file. Unfortunately this "bug board" isn't easily found or maybe because the Problem is to new... Anyway if you want I can search it in the History and post the Link. Great it helps cause there are people (like me) that still use there Note 3 daily and after the official app pushed the update I just did it and ended up with a none working phone... There were people complaining 3 days ago and it would have been easy to post a link to the solution... But obviously no one cares so I did... No offense or Disrespect to the Dev (I really appreciate your work!) of this build but like I wrote, posting a link to the solution is a 2 sec thing....
Thx anyway. Hope it helps out a lot of people.


Gesendet von meinem SM-N9005 mit Tapatalk

 

[No_Fear01]

@sebastian79hl

Did not work for me, SIM is still not recognized

 

[sebastian79hl]

@sebastian79hl

Did not work for me, SIM is still not recognized

Sorry to hear [emoji852]️ I search the post tomorrow morning as it is 1.30 here right now. That's the "official" solution. Sometimes this happens if Phone wasn't turned off long enough. Or maybe change usb cable and port. It can happen that Odin says it flashed the file but in fact it didn't. I have a look tomorrow morning and let you know.

Gesendet von meinem SM-N9005 mit Tapatalk

 

[GF_2015]

did not work for me either. Seems that after update to RR-N-v5.8.5-20171111-hlte-official from vidwhal one error apply in the update process. Unable to repack boot image! with Magisk v14 Installer.

 

[sebastian79hl]

Hey up Guys...

So here is the Link I grapped the File from. Seems to be strange.... On the lineage Downloader App there are Guys where it worked and also didn't work[emoji53] anyway the link posted is the official "bug Forum" from lineage and that's where I got that file from.... Hope at least that helps you out somehow as I don't have a clue why it's not working in your case...

https://jira.lineageos.org/plugins/servlet/mobile#issue/REGRESSION-773/comment/16222

Gesendet von meinem SM-N9005 mit Tapatalk

 

[GF_2015]

I checked the file and confirm that it is working with the old RR-Version, will do again the update to the newest Version as mentioned above.
What it keeps me helping was to wait without battery for 5 Minutes and used the ODIN 3.12 Version to flash.
Thx all.
Noch einen schönen Tag ins kalte Deutschland!

 

[sebastian79hl]

I checked the file and confirm that it is working with the old RR-Version, will do again the update to the newest Version as mentioned above.
What it keeps me helping was to wait without battery for 5 Minutes and used the ODIN 3.12 Version to flash.
Thx all.
Noch einen schönen Tag ins kalte Deutschland!

Exactly the setup I used. Odin 3.12. And I took the battery out as well for a few minutes [emoji106] so this seems to be Importend.

Kalt aber die Sonne scheint[emoji6] Gruß zurück

Gesendet von meinem SM-N9005 mit Tapatalk

 

[atagunov]

libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk

THANKS

20171113 still has the issue
the fix still works provided you rename libsec-ril.so to libsec-ril.gsm.so

ALL, WHAT IS THE LAST KNOWN GOOD NIGHTLY? - need that to file a regression Jira

Details:
- hlte SM-N9005 UK baseband N9005XXUGBOD3
- downloaded libsec-ril.so from google drive
- started ClockworkMod Recovery
- clicked 'mount /system'
- plugged in USB cable from a Linux laptop
- in 'adb shell' executed 'mv /system/vendor/lib/libsec-ril.gsm.so /system/vendor/lib/libsec-ril.gsm.so.disabled
- back in Linux terminal executed 'adb push path-to-downloaded/libsec-ril.so /system/vendor/lib/libsec-ril.gsm.so
- reboot

P.S. command reproduced from memory sorry if there is any inaccuracy

 

[Ante666]

Sorry to hear [emoji852]️ I search the post tomorrow morning as it is 1.30 here right now. That's the "official" solution. Sometimes this happens if Phone wasn't turned off long enough. Or maybe change usb cable and port. It can happen that Odin says it flashed the file but in fact it didn't. I have a look tomorrow morning and let you know.

Gesendet von meinem SM-N9005 mit Tapatalk

It helped me and managed:

1. In ODIN, uncheck autoreboot.
2. Flash in AP "N9005XXSGBQD5_N9005XXUGBPB1_Baseband_Firmware.tar.md5"
3. Remove the battery.
4. Insert the battery and download mode.
5. Repeat flash "N9005XXSGBQD5_N9005XXUGBPB1_Baseband_Firmware.tar.md5".
6. Remove the battery.
7. Insert battery and normal boot ROM.

Result = SIM detected.

 

[atagunov]

Regression Jira filed

jira.lineageos.org/browse/REGRESSION-1410
Interested parties welcome to vote or add last known good date, thx

 

[shallmann]

It's basic, libsec-ril.so is for sim card.
If your sim card is working before download Lineage OS you simply no need to download baseband/upgrade modem.

1.Need Root device
Example Magisk, SuperSU

2.Need Root File Manager
Example Root Explorer

3.Replace this file
Root/System/Lib/libsec-ril.so

0.How to get working sim card libsec-ril.so ?
-Find Lineage OS previous version that can make your sim card exist in your phone.
-Flash rom to that old version.
-Go to Root/System/Lib/ and backup libsec-ril.so
-Flash rom to new version and go to step 3 to replace file
-Turn Airplane mode on off, if not working reboot.

Or you can use this link to download libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk

Im sure file in that link is working for all note3 hlte if not please go to step 0

If you find anyone got problem like this, please help them, spread the solution.

Congrats Lineage OS team, for messed up basic thing in phone.

I don't have Root/System/Lib/libsec-ril.so. I have libsecril-client-sap.so and libsecril-client.so in that folder.
Running lineage-14.1-20171107-nightly-hltetmo-signed.zip, the last daily with no sim card issues. Stopped reading the sim with lineage-14.1-20171122-nightly-hltetmo-signed.zip.

---------- Post added at 05:51 PM ---------- Previous post was at 05:12 PM ----------

This is what worked for me. (I hadn't had any problems with sim card until the 11/22 daily). So I backed up just the modem from the 11/07 daily in twrp. Flashed 11/22 daily, SuperSU. Restored modem only, rebooted. Working great!

 

[sebastian79hl]

So there is a new Version and we still run in the "No Sim" issue? Why's that? I really like to know why this can't be fixed once and for all? So everytime we update we'll end up with an "non functional" phone?

 

[rayman95]

So there is a new Version and we still run in the "No Sim" issue? Why's that? I really like to know why this can't be fixed once and for all? So everytime we update we'll end up with an "non functional" phone?

if you have good version of BL+CP, there is no issues...

 

[poviking]

Flash this: https://www.androidfilehost.com/?fid=673368273298969340
AP choice via odin.
Enter Download mode via Vol-, Power and home buttons after removing the battery and inserting it again.
had the same problem today and just fixed it.
hope that works for you
using my N9005

Tried the first option with no luck, but yours my friend worked like a charm.

lineage-14.1-20171122-nightly-hlte-signed

 

[riqmarmes]

THANKS

20171113 still has the issue
the fix still works provided you rename libsec-ril.so to libsec-ril.gsm.so

ALL, WHAT IS THE LAST KNOWN GOOD NIGHTLY? - need that to file a regression Jira

Details:
- hlte SM-N9005 UK baseband N9005XXUGBOD3
- downloaded libsec-ril.so from google drive
- started ClockworkMod Recovery
- clicked 'mount /system'
- plugged in USB cable from a Linux laptop
- in 'adb shell' executed 'mv /system/vendor/lib/libsec-ril.gsm.so /system/vendor/lib/libsec-ril.gsm.so.disabled
- back in Linux terminal executed 'adb push path-to-downloaded/libsec-ril.so /system/vendor/lib/libsec-ril.gsm.so
- reboot

P.S. command reproduced from memory sorry if there is any inaccuracy

Any idea how to fix the new versions? this one stopped working
EDIT: Never mind, my libsec-ril.gsm.so got corrupt, just had to get a fresh copy, and all worked well

 

[crireal]

Flash last Nordic Baseband and Bootloader or:
- make a nandroid backup
- flash last stock firmware
- re-install custom firmware following its guide
Avoid custom kernels in this steps

 

[T3CHN0M4NC3R]

Thanks to all of you who mentioned the battery removal. I wonder though, what's with Samsung and battery removals? Does that triggers something we don't know?