\I have the issue where the phone:
Reports an "Invalid SIM Card", "Please Insert SIM" etc. regardless of what carrier or generation of SIM card is inserted. This flip-flops somewhat consistently, ,
Gives an "Error While Searching for Networks" / "Unable to connect to Network now, please try again Later" when trying to manually register using Settings/Mobile Networks/Select Network
LG P999DW
Baseband: Mar 11 2012 |M6600 9720a || Carrier: T-Mobile
ROM: Stock V21y Rooted (Also experienced on Weapon G2X, CM10 Hackfest, AOKP m6 & m5b40, v21e)Screenshots of various settings INC
There are about 5 threads with similar reported problems scattered across Q&A here, 2-3 on RootzWiki, and various others at T-Mo's Official and LG's Support forums, so this seems to not be an isolated issue.
Is there a known solution to this issue?
Can users experiencing this issue, or similar issue, perform any steps to isolate the problem further in order to better troubleshoot it?
I apologize if it's been covered elsewhere or even in this thread (I just read it in it's entirety, though).
I am wondering if re-flashing the baseband is a possible solution to issues I've been having with Network Registration and SIM Card errors.
All threads previously came to end in despair, lack of a resolution, or varied musings on the possibility the Original SIM must be inserted prior to baseband flashing. or a baseband flash using an unsupported SIM causes corruption. Others have made mention that Wifi Calling & Certain SIMs don't jive, and claim a mismatched configuration of these 2 elements prior to a BB Upgrade can cause SIM issues. I find this a dubious, but possible given that this phone's HW/SW Config can seem like a goddamn Rubik's Cube at times.
Can anyone confirm or deny such a speculative claim, or perhaps give more information about the relationship between BB, RIL, SIM module, and Modem Settings? Anything special about the properties of any or all that could apply to issues of this sort?
I will try to consolidate the threads I've mentioned and put together a holistic index of all SIM-Related G2X problems, including better detail of my issue in particular. I'll do my best to rule out obvious cases in which the SIM Card slot hardware itself is obviously just effed in an effort to make this discussion more productive. If anyone has some input on how best to make this go smooth, send me a PM and I'll do what I can to facilitate.
I really believe there is a userbase that needs this help, but has mostly gone unanswered and ended up junking or RMA'ng the unit. As official support slowly recedes for the device, this solution becomes unrealistic and the benefits of producing user-enabled solutions will increase over time.
I have a similar issue with my LG G2X. Did you find a solution?
Related
Hi everybody! I searched for more than one week about this, but I couldn't find a real solution....
I tried installing CyanogenMod on my friend's Optimus Hub, and I dramatically faced what someone called the "Funny SIM" problem: in simple words, it is impossible to save APNs, and so data connection is not available.
This, as my research suggested, is a compatibility problem between Hub's CyanogenMod and some SIM cards, the 128k ones. In fact, using a 64k sim made APN and data connection instantly work.
The problem is that my friend's telephone company told him that he can't keep his number downgrading to a 64k SIM, so he would have to change his number in order to have 3g/H working, and that would be a big issue to him.
My searches led me to this thread http://forum.xda-dev....php?t=1444328.
This is about Optimus One, and the problem seems to be the same, but the flashable zips in the thread seem to SOLVE their problem.
I downloaded and opened the "Funny-SIM-Fix-OldBB" .zip and had a look at the changes it made:
It replaced some libs and made modifications to build.prop.
I am not very expert in this, but tried replacing CM libs with the stock ones, using the names contained in the .zip I previously downloaded to locate them and then rebooted but nothing changed. APN were the same.
So, Is there someone who tried something else, or is willing to try now?
Thank you for your attention!
Jar3112 said:
Hi everybody! I searched for more than one week about this, but I couldn't find a real solution....
I tried installing CyanogenMod on my friend's Optimus Hub, and I dramatically faced what someone called the "Funny SIM" problem: in simple words, it is impossible to save APNs, and so data connection is not available.
This, as my research suggested, is a compatibility problem between Hub's CyanogenMod and some SIM cards, the 128k ones. In fact, using a 64k sim made APN and data connection instantly work.
The problem is that my friend's telephone company told him that he can't keep his number downgrading to a 64k SIM, so he would have to change his number in order to have 3g/H working, and that would be a big issue to him.
My searches led me to this thread http://forum.xda-dev....php?t=1444328.
This is about Optimus One, and the problem seems to be the same, but the flashable zips in the thread seem to SOLVE their problem.
I downloaded and opened the "Funny-SIM-Fix-OldBB" .zip and had a look at the changes it made:
It replaced some libs and made modifications to build.prop.
I am not very expert in this, but tried replacing CM libs with the stock ones, using the names contained in the .zip I previously downloaded to locate them and then rebooted but nothing changed. APN were the same.
So, Is there someone who tried something else, or is willing to try now?
Thank you for your attention!
Click to expand...
Click to collapse
Hello
For my LG Optimus Hub e510 I tried the cm 7-9-10 mods.
All with the same effect
in case "APN could NOT be written/saved to the phone" as described by many users.
OK - this prob is described as the "funny sim problem" shown in several forums.
Users worldwide with 128bit sim cards told about this damned effect.
2 "Funny Sim" fixes existing( as much I know).
An old version and a beta. Only result(for my LG E510) after flashing in recovery mod.
Freezing in the boot procedure.
State of facts is actually,there is no idea to change it proper.
That means, with an 128bit sim in your android all these MODS are "no goes" in case of mobile internet via provider.
As it looks? Is it so?
XXX andreas
aw man so no solution for our hub? its been ages since it existed or are the cm devs not working on it any more? if yes does anyone know another good rom for the hub?
Does anyone know if the "no sim" issue was fixed in JB? My daughter is still having trouble with this up at school. Someone on the VZ board posted this:
Well I didn't believe it at first but I think they have finally resolved this issue!
First of all I'll give you some background. This is pertaining to the Samsung Galaxy S3 issue known as the "No Sim Error" where intermittently your phone will fail to send text messages or make and receive phone calls. When this failure happens, the phone displays "No Sim" at the top and you lose connectivity with the network briefly. The problem is location based. ie only certain areas are affected. This issue only pertains to the Samsung GS3 and only these specific symptoms. If your phone or symptoms are different then this is not your issue. I had actually planned to post a detailed synopsis of all the information I've compiled but that would appear to be unnecessary now that a solution has actually been found.
The following is a paraphrased quote from a level 1 Verizon tech who by his own admission did not himself understand what he was reading to me.
"There are 2 crossbands (data formats if you will) called TCA and 1XRTT. These crossbands are used in communication with the towers and the manufacturer's default distance threshold for these settings was incorrectly set on the GS3. They reduced the distance threshold to half a mile and this should fix your issue".
This fix was not a software patch but according to the tech was a config change they made on my account that overrode the Samsung factory default setting. I don't pretend to know exactly what that means but I can tell you that today is the first day since I've owned this phone that I cannot get it to fail. I do not know if you will have to call in to get them apply this configuration change or if they will push it out to all GS3 owners. I hope this is the beginning of the end of these problems with the Galaxy S3.
Click to expand...
Click to collapse
Anyone know if there's a config menu we can get to that will display this setting?
Thanks!
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So you already tried everything that's available on the web to fix your Chinese phone GPS after a stock/custom ROM Flashing, and problably your device is a MT6572, MT6577, MT6582, MT6589(T), MT6592, MT6753 or any other media tek.
You already tried:
1 - The classic method, that shouldn't even be mentioned in a case like this, and felt like an idiot:
* DOWNLOAD EPO AND ENABLE AGPS.
2 - The Plan B Method: Used Faster GPS app to create or manually changed your GPS.config file.
3 - The plan C Method: Deleted mtkgps file and restarted.
4 - The plan D Method: Searched for a NVRAM file on the Web and tried to restore it using MTK Tools.
5 - The plan E Method: You downloaded/replaced the file libmnlp_mt6572 in your system/xbin folder.
6 - The plan F Method: You Downloaded/replaced the files mtk_agpsd from bin folder, agps_profiles_conf.xml from etc folder, android.hardware.location.gps.xml from etc/permissions folder, gps.default.so from lib/hw folder and mtk_stp_gps.ko from lib/modules folder.
7 - The plan G Method: Perhaps you tried some African ritual...
8 - You climbed Mount Fuji to get some signal, and had to keep your screen ON in the GPS APP during 2 hours.
9 - You tried some Native Indian ritual...
10 - You hacked you GPS Antenna, building a custom one as it is shown YouTube tutorials, and it works... for the guys who made the videos.
Your GPS was working before flashing, even if weak, so you know your hardware is not broken or something.
11 - You tried to transform into Mumm Ra the ever living!
12 - Like me, it's been over 1 week since you decided to fix this issue, and you're about to pull all your hair. In my case I'm spending hours on this, I'm really trying to get a solution.
AND NOTHING WORKED AFTER DELETING, REPLACING, DOWNLOADING.
You even learnt and tried using EXPELLIARMUS!!!
Still didn't work...
And your GPS still can't get a lock, even with all the network aid, all the tutorials you found in the web. If you religious, you even asked Jesus to help you (At least that was my case). But your phone is still the same.
Now you feel like an idiot that is never, ever again going to buy another Chinese phone anymore in your life, but you don't want to discard your phone, what you're going to do?
Well I -- STILL -- haven't found a solution, but I found a clue that may lead to a solution. Since I'm not a smart ass programmer that knows basically everything about Androids, I humbly come here now to open this discussion and see if we can finally find a solution for this problem that I believe it already annoyed at least 1 hundred people around the globe.
My clue is:
1 - I saw some people saying that when they restored their NVRAM backup after flashing the stock ROM, they got their GPS working again. So it is related to NVRAM, but with what in NVRAM?
2 - Today I was testing some hacks, when I disabled my SIM card, I the GPS TEST app could not find any satellites anymore, and I was using wifi, so it makes no sense at all, I mean, could the GPS be using the 3G/GMS/WCDMA band?
I believe the GPS device is operating in a different frequency, probably the same as the SIM CARD, and that's why people can't get a lock.
That's related to NVRAM. Perhaps with the 900/2100 and 850/2100 operator frequencies.
Let's discuss and see if we can find a definitive solution for this case, please.
Found this in another forum:
we were discussing this point also in the thread regarding unlocking the 3G bands.
it seems that neither the NVRAM nor the ROM alone has much effect regarding to the GPS, but it seems that if either one does not match the other you can also have trouble with your GPS.
how it's connected i do not know - actually as you said it should not be connected at all.
but it's pretty much clear now that the 850/2100 and 900/2100 phone have at minimum different radio hardware.
We were not able to determine how the bands were locked/opened through the firmware (since it would make sense that in theory both are available but can be turned on or off by the manufacturer, because its more expensive for MTK to produce actually different radio hardware) so that suggest that there is a hw difference. that could be connected to the GPS also.
in other threads people had reported that by upgrading the firmware they nuked their NVRAM (lost IMEIs, changing MAC address etc.) and most of them had problems with the GPS afterwards.
better safe than sorry. if you really want to try this out, please make sure to have a working backup of your NVRAM beforehand.
Click to expand...
Click to collapse
So a site about developers doesn't have a developer that could ever solve that issue?
I want to start by saying thank you to everyone on this forum. I have learned so much from reading the guides and resources (particularly those by @Gawd, @spanna, @Heisenberg, @EddyOS, and @Timmmmaaahh. I know some may have moved on but you legacy remains.).
This issue seems to have come up before on the forum, but I have not found one that matches my own situation with a solution, unless I am missing something. I am also lucky in that I have access to another near identical OPO without the issue for comparison. I am visiting my family and we all have OPO.
I have noticed that my phone will have decent to good signal (1-4 bars of Tomobile LTE) be able to use cellular data and send SMS, but not make and receive phone calls in certain areas. I would have been content saying this was a reception/carrier issue. However, I am visiting family for Memorial day and have been able to troubleshoot this with their phones. I bought my parents OPOs when it came out and my brother has a Find7, so we all have essentially the same hardware. For my troubleshooting I used primarily my mother's OPO (not updated since CM11S) and occasionally my brother's Find7. Both my mother and I have the 64 GB edition of OPO purchased around Oct-Nov 2014. Both are cobranded with Cyanogen, though mine was purchased a month or two prior to hers. When comparing the OPOs I notice her phone is able to send and receive calls in places where mine is not able. We have similar reception. I have cellular data and can still SMS. The issue is just with calls. I have tried the following (i have bolded things which I noted were different):
Basic stuff:
1) Making and receiving calls with both phones side by side. Her phone can send and receive calls in all areas (even with just one bar), while mine can only make and receive calls in some areas. My brothers Find7 has identical performance as my mothers phone.
2)Toggling airplane mode. -- Same result.
3)Toggling LTEonly, 3g only, and 2g only. -- Same result.
4)Verifying APN -- Identical for all three phones
5)Swapping SIM Cards -- both phones perform the same irrespective of which sim card is in it.
6)Verfied IMEI -- present in all phones.
7)Verifying signal strength (dBm/asu) in phone settings (*#*#INFO#*#*) -- near identical between phones. Our dBm numbers were the same but my asu number was sometimes triple her phone's asu. Her's was identical to the Find7.
More advanced stuff:
8) Removing the back cover and making sure the terminal are making contact to the backplate antennae.
9) Changing roms and firmware. No success.
- I had recently upgraded from the final release COS 13 to the latest Oreo RR with a clean wipe using TWRP. I was running RR when I first started this.
- First I tried flashing my recovery file with TWRP. It says it ran successfully, but didn't make any changes to the system.
- Since my mothers phone has no issues I tried to replicate her setup. I fastboot flashed the cm-11.0-XNPH05Q-bacon-signed-fastboot.zip provided by spannaa.
- I found some similar posts to my problem which linked to gawds firmware. I verified that both my mother's working OPO and mine had the same OS (XNPH05Q) and baseband (c7-00020) I also tried flashing different firmwares with no benefit.
- I tried fastboot flashing back to COS 11 XNPH33R (what my OPO came out out of the box with).
- I then used EddyOS guide to return device to stock COS 13.1.2. with no change.
- Thinking another new ROM may include a better firmware. I most recently did a clean install of AOSPExtedned and currently have baseband c6-0241.
Going forward:
- I was thinking of flashing gawds firmwares with AOSPExtedned. Is this safe?
- Looking to disable/unlink my google voice account from my cell number. My mom does not have this set-up. I noticed a delay in making calls, and that my google voice account has a log of all my missed calls (those that never make it to my cell). Maybe it interfering with my calls going in and out.
- Any suggestions on diagnostics I can run while I have access to my Mom's functioning OPO.
Much thanks for everyone's help.
Hey guys, I've been nearly driving myself insane trying to find a fix for what seems to be a pretty serious, near-system breaking bug in the most recent Android 11 system update for the Blu View 3 (B140DL)
I had working antenna signal and strength working perfectly fine, after marrying my new SIM card's iccid to my carriers account. After marrying, I was told to reset my network settings, apply system updates (if any) and reboot the device. There was an update, so I proceeded with it, and when my phone was done rebooting, there was an empty antenna signal triangle with an x in it. I've heard about and seen ota updates have bugs in the firmware that cause issues but it's always been with top tier flagship type devices and there's a fix rolled out almost instantly. This being a budget unlocked device, I have had no luck with any kind of information about possible fixes or any being released; hell, I can't seem to find if anybody else has experienced this problem with the specific update on this build or not anywhere on the internet, and this update is from January of this year. I am going to post the build and specific software update that caused the radio firmware to not work, so hopefully that helps. I'm hoping that maybe there's a fix for this that doesn't involve reflashing the official firmware (can't seem to find the stock firmware for this device at all) and I'm humbly asking for any help or advice that anyone is willing to share with me. I'm having to resort to using text now & voice over WiFi with no access to my carriers services. Thank you in advance!
P.S. I also put a screenshot with the current kernel and baseband as well, because I'm not sure if either of those got updated during the last system update.
There is now firmware available. I'd try flashing stock
Dial *#*#info#*#* which will open up a menu to change radio from 3g to LTE only, and others, try them.
Also is your apn set?