Database Info

[Q] Galaxy Nexus radio/modem failure, baseband version : unknown

Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu

sanu.mathews said:
Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu
Click to expand...
Click to collapse
I had a similar experience with my previous Nexus S device. The phone would start up perfectly fine but it wouldn't catch reception. I think I flashed the wrong radio.img file (there are a lot of Nexus S variants).
I would try the following steps:
- Flash CWM recovery
- Flash a custom ROM (you can use "Mounts and Storage" in CWM recovery to gain temporary access to your internal storage - you will need to do this to copy your ROM file there)
- If you like it, just stick to the custom ROM.
If you insist on going back to the stock ROM, there are threads here that guide you to go back to stock completely. Even if you go back to a previous ICS ROM (specific to your phone), you should start receiving OTA updates normally.
Best of luck!

Thanks for the reply.
I'm almost sure the radio image is fine. I downloaded the images from
Google Nexus developers site for "takju" for Galaxy Nexus "maguro" matching with my phone.
I flashed matching ROM and radio images from Google site. Tried both ICS 4.0.4 & JB 4.1.2
I'll try custom ROMs if nothing works out. I'm going to try this first time, so need to chk the threads first. This is my first Andriod phone and already ran into trouble after just 2 days of use, that too without any manual flashing. Only OTA happened before the issue.
Could the h/w have gone bad ?
In fastboot mode, the radio version is displayed correctly, but not after phone is up and running.
If the h/w has become faulty, I still expect the "Baseband version" in "About Phone" to be correct.
Is this assumption correct ? If it is s/w issue, I'm relived and I can try some custom image. So I'm hoping its only a s/w glitch.
Thanks a lot

you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition

Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
clait said:
you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition
Click to expand...
Click to collapse

sanu.mathews said:
Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
Click to expand...
Click to collapse
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?

*#06# shows "OK"
clait said:
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?
Click to expand...
Click to collapse

sanu.mathews said:
*#06# shows "OK"
Click to expand...
Click to collapse
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2

Thanks a lot.
This eliminates so much un-wanted time waste/means no need to try various steps.
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
I'm under the impression that IEMI number etc should be in OTP and that can't get corrupted but efs may have some meta data regarding the same
clait said:
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse

sanu.mathews said:
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
Click to expand...
Click to collapse
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!

If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
clait said:
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!
Click to expand...
Click to collapse

sanu.mathews said:
If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
Click to expand...
Click to collapse
Mate - I too am from India, and I too got the exact same problem, and I too tried all you did - all this about a month back. I have reconciled myself to the fact that its a hardware issue. Since samsung centers in India won't do any repairs, I'm afraid we're both stuck with really expensive music players.
My sympathies.

Fixed by sending in for warranty
Just an update...I was having all of these symptoms...unknown IMEI, Baseband, etc...basically gave me an expensive media player for a few months while waiting for a fix on XDA. After no update I decided to call up Samsung and after talking to 3 different technicians, I was able to send it in. Just a note for anyone about to do the same, they will try very hard to blame it on the carrier/SIM card, so save yourself some trouble and just say you already went to the physical store of your carrier (calling isn't enough)and they couldn't get it working. Once you get past that, they will email you a printable 2-day UPS shipping label so you can ship it to them for free. It took 2 weeks from the time I called to having a working phone back in my hands.
This was their fix:
Problem found:
NO PCS SERVICE
Solution:
REPLACED PBA
After a quick search I found that the PBA is the motherboard, so it's definitely a hardware issue. Hope you guys are still under warranty because I've heard this is ~$200 to fix otherwise.
Good luck.

[Q] Can't turn on Radio. No network.

Hi People.
I have a Nexus 5 that a friend gave a while ago. The phone came directly from google in Mountain View meaning this is/was a prototype phone. (It has a SKU number and a 'NOT FOR SALE' legend in the back)
The really interesting thing about this phone is that in model number it was saying "Nexus 4" even if in fact it is a nexus 5.
The phone was working perfect except for the google play that was crashing every time when I tried to open it. I factory reset the phone several times with no success. The android version it was 4.2.2 (If I remember right)
I decide to flash the phone with a newer version. I flashed everything (system, recovery and radio) with hammerhead 4.4.3.
After this update, I'm not able to connect to the network. If I try to make a call, it display: "to place a call, first turn off airplane mode".
When I go to phone info and try to "Turn on radio" it doesn't do anything.
I reflash all available modem versions with no success.
Any ideas???
Thanks.

Have you checked whether the apn settings are entered properly??
If you've flashed all the factory images then head over to the stock recovery and perform a factory reset.
If both the above things don't work, the EFS partition might have gone bad. If that's the case, then the phone is screwed.
You will need to take it to a lg centre so that they can rewrite the partition.
- Sent from an IceCold Hammerhead!

vin4yak said:
Have you checked whether the apn settings are entered properly??
If both the above things don't work, the EFS partition might have gone bad. If that's the case, then the phone is screwed.
You will need to take it to a lg centre so that they can rewrite the partition.
Click to expand...
Click to collapse
Easiest way to tell if your EFS is gone is look in Settings - About Phone - Status and look for an IMEI number. If its gone you need professional help to fix it as quoted above. Unless you made a back-up....

flyboy_9 said:
Easiest way to tell if your EFS is gone is look in Settings - About Phone - Status and look for an IMEI number. If its gone you need professional help to fix it as quoted above. Unless you made a back-up....
Click to expand...
Click to collapse
Sometimes a non-formatted or messed up cache partition can also show "0" IMEI in about-settings which can be solved by a factory reset. I hope that's the case with the OP. Otherwise he's in big trouble.

vin4yak said:
Sometimes a non-formatted or messed up cache partition can also show "0" IMEI in about-settings which can be solved by a factory reset. I hope that's the case with the OP. Otherwise he's in big trouble.
Click to expand...
Click to collapse
When I flash a hamerhead radio I have an imei number. If I flash a occam one I don't.
When I just got this phone it has occam. Phone model was nexus 4 (even when in fact is a nexus 5)
Now I can't flash it back to occam. Even if I disable confirmation before flashing.
Is there any way to query the modem on this device? I'm afraid because this is a prototype the modem version is different from the one it come with the rom releases.

[Q] Oneplus one not working

I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"

AxelWexel said:
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
Click to expand...
Click to collapse
Can't find your video, can you paste the link as text?

gsmyth said:
Can't find your video, can you paste the link as text?
Click to expand...
Click to collapse
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it

AxelWexel said:
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
Click to expand...
Click to collapse
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500

gsmyth said:
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
Click to expand...
Click to collapse
Thx for the Links and i tried to watch on my phone and there is no imei number. I also did a full wipe after i found the issues. I also tried it via the Toolbox to flash the stock rom back but it hadnt change anything. But I will look the links you postet and reply if anything has changed. But now thx again:good:
P.S: I renamed the Video to "Oneplus One not working (23.06.2015)" to find it more easily
Edit 1: The Second Link with fixing corrupt partitions via adb wont work for me because i dont have root but my bootloader is unlocked. so i cant find the root acsess for adb in the developer options
Edit 2: I installed color os like the link said, done everything it said, but still no wifi, bluetooth and no sim card detection:crying:. Luckily the random reboot stopped Could you again help me further more because it seemed to help
Edit 3: I went back to cm11s, because in color os when i turned the phone off it turned on again, the connectivity was not there. After the install it became worse with the random reboots. I think i must send it to repair and pay 300€:crying::crying::crying::crying:

[SOLVED] EFS damaged, imei null and have no backup

Hello guys,
So i have experienced alot of efs problems in the past and i managed to fix them all but now i can't really do anything about it, i tried flashing the combination firmware i flashed the correct file (i flashed U3) but i keep getting an bootloader exception error, so i went back to stock and tried again, got bootloader exception error again, now i am back at stock and i have no idea what to do i asked a repair center and he said 60€ i am not paying 60€ for a stupid code that turned in to 000000000000000 my baseband is NOT unknown and my signal bar keeps changing beween no signal and the normal signal bar it i have never experienced a changing signal bar like that before i hope someone can help me with this because i can't make any phone calls since 2 weeks or more
Thank alot guys, and sorry for my bad english, english is not my main language

go and pay 60€, u can't back the original IMEI only with soft, u need a box to repair

Had similar issue on S8. Downloaded latest firmware. Extracted the zipfile. And flashed the corresponding CP and BL file.
(Modem and bootloader)

Spacewide said:
Had similar issue on S8. Downloaded latest firmware. Extracted the zipfile. And flashed the corresponding CL and BL file.
Click to expand...
Click to collapse
Did that work?

Picklewickle said:
Did that work?
Click to expand...
Click to collapse
Yes it did! Happened to me and it's worth the try because you can't do anything wrong with this method.
Downloading the firmware can take some time, but I found a fast mirror after googling around.
Best of luck and please post an update
Sent from my SM-G950F using Tapatalk

Spacewide said:
Yes it did! Happened to me and it's worth the try because you can't do anything wrong with this method.
Downloading the firmware can take some time, but I found a fast mirror after googling around.
Best of luck and please post an update
Click to expand...
Click to collapse
Ok thanks for the help i will try it tommorow and then i will update you

Spacewide said:
Yes it did! Happened to me and it's worth the try because you can't do anything wrong with this method.
Downloading the firmware can take some time, but I found a fast mirror after googling around.
Best of luck and please post an update
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
This actually worked! Thank you so much!

Spacewide said:
Had similar issue on S8. Downloaded latest firmware. Extracted the zipfile. And flashed the corresponding CP and BL file.
(Modem and bootloader)
Click to expand...
Click to collapse
Thanks for the tip, but unfortunately, it didn't work i flashed the latest cp and bl file and it didn't bring back my imei
any other solutions?

I already tried flashing the combination rom with odin v3.11.1 and i selected auto reboot, re-partition, nand erease all, f.reset time, efs clear and bootloader update also no luck, i clicked on ime and entered *#06# to see or i got my imei back and nope i also wiped my full efs before flashing the rom, this problem sounds more serious then i've ever thought it would be
it would be great to have some idea's to fix this...
last time when i had this problem on my phone i wiped my full efs and installed sac23's s9 port rom suprisingly it did help me bring back my imei now i did that again and no luck, the problem also is that i used twrp to delete my efs now twrp doesnt recognize my efs so it shows that my /efs is empty and root explorer says that it has files in it i need to wipe efs with twrp like i did before because if i delete it while i have my phone on it gets rebuilded again? files keep coming back but my imei, signal are not coming back its weird, i tried samsung kies and smart switch but it says SM-G935F not supported
the combination rom also keeps getting cp crash error, it so after a short moment in the combination rom it reboots in cp crash mode or something like that with green and red text

UPDATE: IMEI is NOT 0 anymore, but its not correct, the imeisv numer is now at the end of the imei number which means its now a 16 number imei, it also says simcard not provisionized please help me guys

UPDATE: [SOLVED] I can use my phone 100% again,
I fixed it I accidentally switched my simcard to a simcard that was suspended,
Now for the people also have problems,
1. Go to twrp
2. Make sure Efs has been checked at mount
3. Go to file manager
4. Go to /efs and delete everything in it (DO NOT DELETE /EFS IT SELF OR ELSE PHONE WONT BOOT!! ONLY DELETE WHATS IN IT)
5. now flash a new rom directly without restarting your phone after deleting whats in your efs or else your efs will rebuild, now it should work, if your imei is changed and it says sim not provisoned then just change your simcard because that error message means you have been suspended or your sim is inactive

Picklewickle said:
UPDATE: [SOLVED] I can use my phone 100% again,
I fixed it I accidentally switched my simcard to a simcard that was suspended,
Now for the people also have problems,
1. Go to twrp
2. Make sure Efs has been checked at mount
3. Go to file manager
4. Go to /efs and delete everything in it (DO NOT DELETE /EFS IT SELF OR ELSE PHONE WONT BOOT!! ONLY DELETE WHATS IN IT)
5. now flash a new rom directly without restarting your phone after deleting whats in your efs or else your efs will rebuild, now it should work, if your imei is changed and it says sim not provisoned then just change your simcard because that error message means you have been suspended or your sim is inactive
Click to expand...
Click to collapse
What rom can you flash within TWRP? I have latest stock installed (G930W8VLU5CRI2)

peterman6 said:
What rom can you flash within TWRP? I have latest stock installed (G930W8VLU5CRI2)
Click to expand...
Click to collapse
Twrp can flash all roms aslong its a rom for your phone it can be flashed

Picklewickle said:
Twrp can flash all roms aslong its a rom for your phone it can be flashed
Click to expand...
Click to collapse
Also do full wipe when installing a custom rom

Picklewickle said:
Also do full wipe when installing a custom rom
Click to expand...
Click to collapse
So basically I can flash any Oreo custom rom and the EFS would repair ?
I have the Z3X box and I tried to repair the IMEI by entering my IMEI but unfortunately I made a 1 digit mistake.
The IMEI was written ok but did not Patch the certificate, at the time was on Binary 2, the phone got automatically update with latest stock (Binary 5), now can't repair IMEI nor patch the certificate (it would require downgrade to 7.0 which is not possible with Binary 3+).
Any idea ?

peterman6 said:
So basically I can flash any Oreo custom rom and the EFS would repair ?
I have the Z3X box and I tried to repair the IMEI by entering my IMEI but unfortunately I made a 1 digit mistake.
The IMEI was written ok but did not Patch the certificate, at the time was on Binary 2, the phone got automatically update with latest stock (Binary 5), now can't repair IMEI nor patch the certificate (it would require downgrade to 7.0 which is not possible with Binary 3+).
Any idea ?
Click to expand...
Click to collapse
I think there is more chance to make it work if there are cscs built in (do not install superman rom!! It has incorrect cscs) and please dial *#1234# and tell me what it says at cp also try z3x again

Picklewickle said:
I think there is more chance to make it work if there are cscs built in (do not install superman rom!! It has incorrect cscs) and please dial *#1234# and tell me what it says at cp also try z3x again
Click to expand...
Click to collapse
I erased the efs directory content, installed RR-O-6.1.0-2018-0908 rom and pico gapps, booted the phone but the there are no bars (emergency calls only).
Dialed *#1234#, does nothing, tried with Z3X but no modem detected, checked the status IMEI is all 0000...
Baseband is G930W8VLU5CRI2
???

peterman6 said:
I erased the efs directory content, installed RR-O-6.1.0-2018-0908 rom and pico gapps, booted the phone but the there are no bars (emergency calls only).
Dialed *#1234#, does nothing, tried with Z3X but no modem detected, checked the status IMEI is all 0000...
Baseband is G930W8VLU5CRI2
???
Click to expand...
Click to collapse
Weird, for me this did work make sure you didnt reboot the phone after deleting efs content also make sure the rom does modify efs like some roms install cscs

Picklewickle said:
Weird, for me this did work make sure you didnt reboot the phone after deleting efs content also make sure the rom does modify efs like some roms install cscs
Click to expand...
Click to collapse
Nope, after erasing the efs content, I flashed custom rom and gapps, then rebooted but got stuck, so I went back in TWRP, erased cache/dalvik, check efs directory and all the files where rebuilt.
can you tell me whitch custom rom you used, will try to do the same.thx

peterman6 said:
Nope, after erasing the efs content, I flashed custom rom and gapps, then rebooted but got stuck, so I went back in TWRP, erased cache/dalvik, check efs directory and all the files where rebuilt.
can you tell me whitch custom rom you used, will try to do the same.thx
Click to expand...
Click to collapse
I used kingrom s7e

is there meant to be sim detection on lineage os 16?

I currently own a GT-N8000 running the lineage 16 os, but theres no sim detection going on, & I'm having issues with efs partition staying mounted.

Tweaker Z said:
I currently own a GT-N8000 running the lineage 16 os, but theres no sim detection going on, & I'm having issues with efs partition staying mounted.
Click to expand...
Click to collapse
Hi,
you are the first person who mentioned this problem.
In usual cases, this is working fine.
How was it before you've installed LOS16?
Is there general a mounting problem with EFS?
Is your baseband working or unknown?

It works sir, even sim detection started working, but no signal at all, i assumed so because i saw some threads about using sim, and bugs with phone calls.

html6405 said:
Hi,
you are the first person who mentioned this problem.
In usual cases, this is working fine.
How was it before you've installed LOS16?
Is there general a mounting problem with EFS?
Is your baseband working or unknown?
Click to expand...
Click to collapse
Yes sir, there's a mounting issue with the efs partition

Tweaker Z said:
Yes sir, there's a mounting issue with the efs partition
Click to expand...
Click to collapse
Does it work with stock rom?
The most important thing, dont wipe or format efs!
This will destroy your imei data.

html6405 said:
Does it work with stock rom?
The most important thing, dont wipe or format efs!
This will destroy your imei data.
Click to expand...
Click to collapse
Never wiped the efs, i got the note as a christmas gift from an aunt, it wouldnt boot up, checked stock recovery, it said "failed to mount efs (invalid argument)" i didnt know any thing about that, so i thought flashing stock rom would fix it, it didn't. One way or another i finally got it to boot, but it displayed a transparent window with yellow letters on the home screen. If i left the home screen, the window disappeared. So i decided to switch to custom rom, but anytime i enter twrp, i still get the efs not mounted error, i usually mount it manually to stop the error from showing, i still have imei so i'm not sure the efs is corrupt.

Tweaker Z said:
Never wiped the efs, i got the note as a christmas gift from an aunt, it wouldnt boot up, checked stock recovery, it said "failed to mount efs (invalid argument)" i didnt know any thing about that, so i thought flashing stock rom would fix it, it didn't. One way or another i finally got it to boot, but it displayed a transparent window with yellow letters on the home screen. If i left the home screen, the window disappeared. So i decided to switch to custom rom, but anytime i enter twrp, i still get the efs not mounted error, i usually mount it manually to stop the error from showing, i still have imei so i'm not sure the efs is corrupt.
Click to expand...
Click to collapse
Ok this doesnt sound so bad, if the shown imei is yours (and not a 0049****** IMEI),
you just have to disable factory mode and your sim card detection should be back.

But TWRP should be able to mount it!
I'm pretty sure, that I could fix your problem (build some things years ago to fix a corrupt efs dumps, withoult loosing the imei and certificate).