"No SIM Card" Error after installing LineageOS

kidbao

Member
Feb 27, 2018
7
0
0
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
 
Last edited:

kidbao

Member
Feb 27, 2018
7
0
0
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
Hi thanks for responding! I have the E4 XT1765. It's Qualcomm. MetroPCS. I tried the PERRY_METROPCS_C and PERRY_METROPCS_C_7.1.1 from from here: firmware. center/firmware/Motorola/Moto%20E4/Stock/
 

beachfl

Senior Member
Nov 18, 2014
225
67
58
Miami
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.

It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
 

kidbao

Member
Feb 27, 2018
7
0
0
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.

It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Yeah same. I tried everything :\
 

kidbao

Member
Feb 27, 2018
7
0
0
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
I don't know. I was just pointing out that we had one, lol. Not sure it will help you.

I see you "solved" it, lol
 
Last edited:

beachfl

Senior Member
Nov 18, 2014
225
67
58
Miami
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem. :)
Not for me. As we've said, re-installing stock ROM doesn't seem to solve the problem for some people, but it's cool it did for you. Other forums are peppered with people experiencing the same SIM issue, some even apparently happening at random.
 

Scholeggo

Senior Member
Sep 27, 2017
277
27
28
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.

It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?

---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------

Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem. :)
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin... :confused:
 
Last edited:

beachfl

Senior Member
Nov 18, 2014
225
67
58
Miami
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.

But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin.. :confused:
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img

And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
 
Last edited:

Scholeggo

Senior Member
Sep 27, 2017
277
27
28
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.


You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img

And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
So, basically, to get back to original ROM, flash the following:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Compared to the original:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1

fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
 

beachfl

Senior Member
Nov 18, 2014
225
67
58
Miami
So, basically, to get back to original ROM, flash the following:

Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Yup, that list all looks exactly like what I did.
'sudo -s' .... no, you don't include that when running fastboot from Windows, it's a Linux thing. I'm not sure you have to, but I do always run adb/fastboot from a command prompt with admin priveleges when I'm using WIndows. which is kinda the same thing as 'sudo' on Linux.
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
So, basically, to get back to original ROM, flash the following:

Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Go to Android programs and scroll down to rsdlite 6.2.4

Edit: link corrected
 
Last edited:
  • Like
Reactions: beachfl and DB126

DB126

Senior Member
Oct 15, 2013
15,236
9,949
253