Hi all,
Am running a Galaxy S5 (klte) which I'd been using CM13 on without problem. I moved over to Lineage at the weekend - full factory reset, clear cache/Dalvik, use latest TWRP to install Lineage and re-install everything. So Saturday, Sunday, Monday everything fine. Then switch the phone off overnight (as I had done on the other nights) and switch back on this morning. The phone boots fine, no sign of any issues - but I don't get my usual "Enter your SIM PIN" screen, it boots straight to the desktop.
Can't access anything to do with phone functions and the signal icon sits as a triangle but hollow, a bit like when you get zero signal strength... it's not the SIM card with a line through it (no SIM card) icon, which is odd. Trying to access settings to select a network, or go for auto network detection draws a blank (can't access SIM card/network).
I've gone back into TWRP and cleared the cache and Dalvik again and the problem persists. I took the latest nightly (2017-02-13) and flashed that hoping it might fix it, but also no joy.
Any ideas without me having to factory reset the device and re-install everything again (pain!)
Thanks,
adamchap said:
Hi all,
Am running a Galaxy S5 (klte) which I'd been using CM13 on without problem. I moved over to Lineage at the weekend - full factory reset, clear cache/Dalvik, use latest TWRP to install Lineage and re-install everything. So Saturday, Sunday, Monday everything fine. Then switch the phone off overnight (as I had done on the other nights) and switch back on this morning. The phone boots fine, no sign of any issues - but I don't get my usual "Enter your SIM PIN" screen, it boots straight to the desktop.
Can't access anything to do with phone functions and the signal icon sits as a triangle but hollow, a bit like when you get zero signal strength... it's not the SIM card with a line through it (no SIM card) icon, which is odd. Trying to access settings to select a network, or go for auto network detection draws a blank (can't access SIM card/network).
I've gone back into TWRP and cleared the cache and Dalvik again and the problem persists. I took the latest nightly (2017-02-13) and flashed that hoping it might fix it, but also no joy.
Any ideas without me having to factory reset the device and re-install everything again (pain!)
Thanks,
Click to expand...
Click to collapse
I had this before as well. I was able to fix it using the correct modem and bootloader software. After this, it worked fine until I did a restore with TWRP. All restored but the modem was not working. I discovered a ADB command to easily fix it but I lost the bookmark for this page. ATM I am looking for this command. Something like "ADB SHELL /AUTO ....."
If you find it, please post it here. I do as well.
Regards, Gopher.
Solved not solved
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Thanks! It worked!
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
In my case I only had to turn off the whole System Profiles general button.
Same for me
I have done exactly as the first post and my sim is also not working now when it was fine. I have a Galaxy s3 i9305 lte. It's just says no sim. I have Lineage 14.1 and have updated to the latest nightly. Any ideas how to get my sim working again?
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
Same problem here and i don't use profiles Galaxy S4
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
On my S4 Mini LTE the profiles seem to sometimes stop the home button (long press) pulling up last apps used even though the button works fine as two quick presses gives me split screen. I think it's automotive profile that activates when it connects to my car Bluetooth that is the cause, but not sure as haven't had chance to pull a log.
Same here on Motorola Moto E XT1021, tried getting CyanogenMod 13, but all the mirrors are down and I don't feel like getting Android from not trusted source.
It's definitely a problem with the ROM because everything works fine on different ROMs, but on Lineage there is no SIM card detection at all and nothing seems to help.
I'm trying to get older Lineage ROM hoping it will work.
Consider removing and reassigning the PIN
Mikeyb2k said:
I have done exactly as the first post and my sim is also not working now when it was fine. I have a Galaxy s3 i9305 lte. It's just says no sim. I have Lineage 14.1 and have updated to the latest nightly. Any ideas how to get my sim working again?
Click to expand...
Click to collapse
What software was on the phone you first locked your SIM in?
Sometimes a SIM will respond to a config file that might be absent when you flash a new ROM.
If you can put your SIM in a different device that recognizes it, use that device to disable the PIN.
Then power down and eject it.
Then, re-insert it into the problem device to see if it works.
If it does, re-assign a PIN using that device.
Hey. Yeah that sounds like a good thing to try although I removed Lineage and have a stock KitKat rom now and works faultlessly. Still have root access and the s3 doesn't need a later version really. Tbh I would have been happy staying on kk if it wasn't for the tech industry moving forward with their software development! How dare they!
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
The trick with disabling the profiles works nicely on my Xperia T with the CM based Resurrection Remix ROM, android version 7.1.2.
XT has no main Profiles button, so i deleted all the profiles manually and restarted the phone. Now trying to find out which profile caused the problem.
.....
Made several new profiles, restarted the phone after each one, but the problem didn't turn back. I think it has issues only with the built-in profiles.
Thanks for the tip man!:good:
Single Sim Working Dual Sim Not
In my case when I remove both the sims and put in only one at a time regardless which slot or which sim it works but when I put two in together it doesn't, driving me to believe that the lineage is not supporting dual sim and is failing hence when both are inserted.
I am running Lineage OS 15 on my S7, and other than a few glitches, the SIM card issue is the only significant problem I have experienced. I have looked through the settings, and I found out that my baseband version is "Unknown." I tried flashing some files, in an attempt to fix it, but I still have no luck. I hope someone fixes this problem.
Hope this helps...
adamchap said:
Hi all,
Am running a Galaxy S5 (klte) which I'd been using CM13 on without problem. I moved over to Lineage at the weekend - full factory reset, clear cache/Dalvik, use latest TWRP to install Lineage and re-install everything. So Saturday, Sunday, Monday everything fine. Then switch the phone off overnight (as I had done on the other nights) and switch back on this morning. The phone boots fine, no sign of any issues - but I don't get my usual "Enter your SIM PIN" screen, it boots straight to the desktop.
Can't access anything to do with phone functions and the signal icon sits as a triangle but hollow, a bit like when you get zero signal strength... it's not the SIM card with a line through it (no SIM card) icon, which is odd. Trying to access settings to select a network, or go for auto network detection draws a blank (can't access SIM card/network).
I've gone back into TWRP and cleared the cache and Dalvik again and the problem persists. I took the latest nightly (2017-02-13) and flashed that hoping it might fix it, but also no joy.
Any ideas without me having to factory reset the device and re-install everything again (pain!)
Thanks,
Click to expand...
Click to collapse
On the latest Lineage build, I was having the issue with it not reading my SIM, so here's what I did:
-clean install of lineageOS (wipe, install rom, install gapps, and install Kernel)
It wouldn't read my SIM at this point, so I
-factory reset
-installed LG G3 Tekcafe VS985-49A_stock (I'm sure any rom would have worked though)
-installed Lineage over top of this rom and wallah! everything works great!
Download and flash this if you have sim card problem https://forum.xda-developers.com/ga...om-xperia-source-project-galaxy-core-t3616744
Please go to this thread : LINK
No access to sim card contacts
Hi all, first sorry for my english, is not my home lenguage, i have an samsung galaxy s5 SM-G900T with custom room lineage-14.1-20180309-nightly-klte-signed.zip, all fine at the moment, except that i can't wiew my contacts stored in sim card and i can't save new contacts in the sim either, any body have a solution for this issue?. Regards.
It's gapps...
Hola!
I am experiencing the same issue and I relate it to the gapps.
The sim works perfectly fine with normal lineage OS. With gapps the sim doesn't work. Reproduced 3 times.
Hello, I'm using a Grand Prime SM-G530H phone with LineageOS 16.0, and here it says, no SIM card but I have a card running normally, I uninstalled Lineage and installed the stock rom, and it normally worked the SIM card, but when I installed it back Lineage continued the same error, what can be ???
My Galaxy S5 somehow detects a Sim Card which is not even inserted. The signal strength showed at the screen is the same as the wifi strength, but never at zero. But if I try to call someone it says no sim card detected. Of course boy there isn't. The problem is that inserting the sim card changes nothing. Same Problem. I switched from lineage to the original firmware back... HELP
Hi everyone,
I am using a Oneplus 3 A3000 China variance. It was shipped with Hydrogen OS.
So i have unlock it and managed to flash it to Oxygen OS, as i need to use google services.
Everything was working perfectly fine until a couple of months later. I saw that Oreo is out and thus decided to upgrade it.
Using official method with stock recovery, i have managed to upgrade to the latest OxygenOS 5.0 using the below link
Oneplus 3 OOS5.0
I have followed the guide closely. Then after it reboot, my phone is no longer having service.
It will show my network SINGTEL (No service)
I have read close to 50 forums before i decided to post and seek help.
My phone info
OnePlus 3 A3000
Oxygen OS 5.0
Android 8.0 Oreo
Kernel version 3.18.66
Build number A3000_16_171116
Baseband MPSS.TH.2.0.c.1.9-00102-M8996FAAAANAZM-1.99649.1.118107.1
Stock recovery
Non root
Fingerprint, camera wifi all works
Both imei are still shown
Here is what i have already tried which all fails on me
1) Verified that Sim is not faulty. Have tested with 3 different working sim cards and it all shows no service on both Sim 1 and Sim, but works on my other phone
2) Tried using only one sim card at a time for sim1 and repeat with sim 2, same result as above
3) Remove sim card, power on phone and boot fully, power off phone and insert sim card and power it on again
4) Reset to default access point. Copied all settings from another phone using same telco access point setting and ensure its the default sim for data and services
5) Using *#*#46463*3* and set preferred network type
6) On the same menu, disable mobile radio power and reboot
7) Perform factory reset from phone phone system setting
8) Redownload OOS5.0 and reflash rom using stock recovery
9) Relock bootloader
Any help is greatly welcome. Phone no longer have warranty so i can't head back to the service centre.
Thanks for reading
donlimck said:
Hi everyone,
I am using a Oneplus 3 A3000 China variance. It was shipped with Hydrogen OS.
So i have unlock it and managed to flash it to Oxygen OS, as i need to use google services.
Everything was working perfectly fine until a couple of months later. I saw that Oreo is out and thus decided to upgrade it.
Using official method with stock recovery, i have managed to upgrade to the latest OxygenOS 5.0 using the below link
Oneplus 3 OOS5.0
I have followed the guide closely. Then after it reboot, my phone is no longer having service.
It will show my network SINGTEL (No service)
I have read close to 50 forums before i decided to post and seek help.
My phone info
OnePlus 3 A3000
Oxygen OS 5.0
Android 8.0 Oreo
Kernel version 3.18.66
Build number A3000_16_171116
Baseband MPSS.TH.2.0.c.1.9-00102-M8996FAAAANAZM-1.99649.1.118107.1
Stock recovery
Non root
Fingerprint, camera wifi all works
Both imei are still shown
Here is what i have already tried which all fails on me
1) Verified that Sim is not faulty. Have tested with 3 different working sim cards and it all shows no service on both Sim 1 and Sim, but works on my other phone
2) Tried using only one sim card at a time for sim1 and repeat with sim 2, same result as above
3) Remove sim card, power on phone and boot fully, power off phone and insert sim card and power it on again
4) Reset to default access point. Copied all settings from another phone using same telco access point setting and ensure its the default sim for data and services
5) Using *#*#46463*3* and set preferred network type
6) On the same menu, disable mobile radio power and reboot
7) Perform factory reset from phone phone system setting
8) Redownload OOS5.0 and reflash rom using stock recovery
9) Relock bootloader
Any help is greatly welcome. Phone no longer have warranty so i can't head back to the service centre.
Thanks for reading
Click to expand...
Click to collapse
Try the 5.0.1 update, maybe it works. https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-5-0-1-ota-update-oneplus-3-3t-t3727433
Good luck!
@donlimck
Try with previous ROM.
tnsmani said:
@donlimck
Try with previous ROM.
Click to expand...
Click to collapse
I'm a bit worried to go down from Oreo. Have read enough to find out that it may have bandbase issue which might result in a bricked phone
simanicu said:
Try the 5.0.1 update, maybe it works. https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-5-0-1-ota-update-oneplus-3-3t-t3727433
Good luck!
Click to expand...
Click to collapse
Just updated to 5.0.1 through OTA. Unfortunately, it still did not solve the issue
Take SIM out. Reboot phone. Once powered-up, put SIM back in. This worked for me, even though it's a pain.
ahall411 said:
Take SIM out. Reboot phone. Once powered-up, put SIM back in. This worked for me, even though it's a pain.
Click to expand...
Click to collapse
Thanks of the suggestion.
Have performed that too on my point 3
Tried something new today. Flashed back to Hydrogen OS hoping that it can detect my sim network
But sadly, it still does not detect.
Hey All,
So I've had issues with my phone where I rooted it and messed it up to the point where it no longer registered on any networks (tried several providers here in the UK). A few days back trying to get it up and running I managed to get it registered on the network (this after reloading various software versions, some failing some not). After powering it off and back on again with my primary sim, I was back to no network (I have two A70s). Swapped SIMS back (powered phone off) and again, no network.
This morning, I started again (Installing TWRP and was planning to root again):
- Flashed stock firmware using ODIN.
- Unlocked bootloader.
- Flashed vbmeta.tar (v3.3.1-5 from Grarak).
- Rebooted, wiped data/cache
- Rebooted, started going through the setup and noticed it was on the network! (have not flashed TWRP recovery).
I'm reluctant to power off again and wondered if there's anything I can do now whilst it's working and registered, making calls etc. The reason being, I've got 5 days before I can return the other A70, if not, I'll be stuck with 3 O2 contracts
Besides the usual backup (Google/Samsung/) - is there anything I should do via ADB? It's not rooted and TWRP is not installed, I've literally just flashed vbmeta.tar from Grarak's TWRP post....
did you try installing a custom rom. i am on havoc os n i own A70FN. i believe havoc works on A70F/FN/Q. the only issue it has is of fingerprint and volte but since i don't lock my phone that's not a problem for me.
other than that the rom is stable no reboots no crashes or anything. so maybe try a custom rom just make sure ur model is supported. n besides even if u r afraid of rebooting there's bound to be a day that the phone would need a reboot.
So i say go ahead root it, install a custom rom.
also i remember having this sim issue myself. my sim worked in all the sets at my home except the A70.
i had to get a new sim n it just started working.
Try some other sim in your A70.
Also rooting shouldn't cause such a problem. from my experience i believe its something else.
i have rooted several phones n never got a network issue. i even messed up the the rooting process on the A70 n either ended up with a bootloop or occasional system crash but no network issue