Related
Hi, i have about 1 month trying to get work a LS990 that i bought in ebay to sim unlocked and use it outside the US, i have followed every possible guide in this forum and still cannot make it work.
I am using the file replacement method with the modified files, and it works, the sim card is recognized and if i go to the network info appears the carrier network info. I get full signal but when i try to make a call, it ends immediately and appears the message "call ended".
I have tried over and over again, setting the RAT mode to automatic and Network mode to automatic, tried with ZVA,ZV8 and ZV4, same result, tried with different sim cards of different carriers also.
The bands are compatible with the carriers where i live, since i have acknowledgement of other people with this model working ok, what i am missing here?
Thanks in advance.
Just flash one of the GSM roms like Killaprime's. I recommend V4.7 as V5 and V6 have major problems/Ui glitches. And 4.7 is the closest to stock LG software
Those file replace methods never work
Edit: http://forum.xda-developers.com/devdb/project/?id=10304#downloads
Porcupineomg said:
Just flash one of the GSM roms like Killaprime's. I recommend V4.7 as V5 and V6 have major problems/Ui glitches. And 4.7 is the closest to stock LG software
Those file replace methods never work
Edit: http://forum.xda-developers.com/devdb/project/?id=10304#downloads
Click to expand...
Click to collapse
Just flash it and pop in the sim card? I already tried the version 6.0 and it didn't work. Any other steps required to get it work?
andr_oid said:
Just flash it and pop in the sim card? I already tried the version 6.0 and it didn't work. Any other steps required to get it work?
Click to expand...
Click to collapse
Try V4.7, and yes just clean flash it and you're good to go
Porcupineomg said:
Try V4.7, and yes just clean flash it and you're good to go
Click to expand...
Click to collapse
Ok, i just flash the rom, same result, i got signal but cannot make or receive calls, when a try make a call after 1 or 2 seconds it ends automatically, one thing i notice is that now when i try to change the network mode to any of the GSM bands, it changes successfully, with other stock or customized roms it always fail.
Let me know if i am wrong, i notice that the IMEI number seems to not be a "normal" IMEI. Can that be what the problem is?
I just fix it, indeed the problem was that rare IMEI, luckily i had a full backup before the very first rom flash including the EFS folder, everything is working ok now.
I have a VS985, I have tried the latest CM13 nightly, the latest CM12.1 Snapshot, Fulmics 5.0, latest Resurrection Remix, and AICP MM, I have tried the 24B, 23C, 23B and 34B modems, none of them seem to work, I can call and text on any of these configurations, and i have tried setting my apn on all of these roms, but they either delete the apn automatically, despite me saving it, or it gives no option of adding an apn, im on the normal Verizon network, how on earth do I fix this?! Do I need to flash back to stock using a TOT or KDZ?
Yes, you've flashed so much that who knows what's going on behind the scenes. Flash the 10B TOT, re-root with the Stump app, then use TWRP Manager from the Play Store to install TWRP, then flash the bootstack and ROM you want. Preferably not CM-based nor international stock ROM based. They seem to require more fiddling with to get everything working reliably, especially Mobile Data. I recommend @xdabbeb 's VS985 v2.0 ROM based on 35B (5.1.1) or his stock 47A firmware, which is Marshmallow - the latter along with any further debloating via my debloat post in my signature below.
Of course, right after you flash 10B, before you root and install TWRP, you should verify that Mobile Data is working for you. If it's not, you might need to exchange your SIM card with Verizon for a new one - some others have had to do that because their old SIM card didn't allow Mobile Data to work any more, if I'm remembering correctly.
Ok, will try tomorrow, and i dont really want root anymore, this device is going to a family member thats not really into that stuff, so could i just flash the stock 35B and be done, unless data still doesnt work, in which case, ill go to verizon.
Also, earlier, i was running CM13, and tried to flash the 35B modem again (might want to stop trying) and my twrp crashed to the twrp splash, and i reflashed the 35B, wiped cache, rebooted to system, and it put it into an infinite LG splash logo loop, had to reboot to stock recovery and wipe cache to get to twrp, reflashed my rom, wiped cache and dalvik, and it boot fine after that.
TOTs flash more partitions than KDZs. Sometimes flashing a TOT is necessary to fix strange issues that even flashing KDZs won't. So I suggest down the 10B TOT and then flash the 47A KDZ and be done with it. It's still double check mobile data on 10B.
So theres no 35B TOT? Currently when i try to flash KDZ files, it fails, it detects the device fine, but wont install the software.
When install TWRP and flashed CM12.1 for the first time, my device was on 5.0.1, and data worked fine on CM12.1, but now it doesnt.
Nick80835 said:
So theres no 35B TOT? Currently when i try to flash KDZ files, it fails, it detects the device fine, but wont install the software.
When install TWRP and flashed CM12.1 for the first time, my device was on 5.0.1, and data worked fine on CM12.1, but now it doesnt.
Click to expand...
Click to collapse
No, the only TOT available for our device is 10B. You can always take the OTAs up to 47A from there if you want (assuming you're using an activated Verizon SIM), although it's harder to root after 10B, and harder to put TWRP on after 12B, if that's what you ultimately want.
Are you using the original USB cable with a USB 2.0 port preferably directly connected to the PC - not through a USB hub?
Im using an Insignia cable, connected directly to my pc, nothing in between, I dont think i have the original cable anymore.
Nick80835 said:
Im using an Insignia cable, connected directly to my pc, nothing in between, I dont think i have the original cable anymore.
Click to expand...
Click to collapse
Not saying it is definitely, but not using the original cable could be the problem.
Downloaded the TOT, will try later, ill report back.
When it was installing the TOT, my kitten decided to jiggle the cable (found my original cable!) and caused the phone toose connection, I could still get into dl mode, but that scared the crap out of me, it was sending system when it disconnected.
I installed the TOT, data works, updating, currently at 23C, thanks for the tips.
Successfully went from 10B to 47A without an issue, factory reset on 47A, everything working very good, data has no problems, thanks, MM is very good on this device, but AOSP seems to kill it for me, even LGs skin runs better!
Nick80835 said:
When it was installing the TOT, my kitten decided to jiggle the cable (found my original cable!) and caused the phone toose connection, I could still get into dl mode, but that scared the crap out of me, it was sending system when it disconnected.
Click to expand...
Click to collapse
Nick80835 said:
I installed the TOT, data works, updating, currently at 23C, thanks for the tips.
Click to expand...
Click to collapse
Nick80835 said:
Successfully went from 10B to 47A without an issue, factory reset on 47A, everything working very good, data has no problems, thanks, MM is very good on this device, but AOSP seems to kill it for me, even LGs skin runs better!
Click to expand...
Click to collapse
Glad it worked, thanks for the update! Cats, so cute but so rotten sometimes. We have one too. ?
They love cables! Especially when they are important.
I have a cyanogenmod 12.1 release on my VS985 LG G3 and it's starting to have some issues with the SIM card potentially. When I first installed cyanogenmod, I had issues seeing the Verizon network, so I flashed the appropriate modem files (can't remember them off the top of my head). It worked for a while, but then at some point a few months back, the phone had issues seeing the LTE network. I found somewhere that if you put it into airplane mode, then restart the phone, then take airplane mode off, you'll see the network, and it worked.
Lately though, the phone is occasionally giving me random problems saying that it can't even see the SIM card. Can SIM cards fail? Are the modem files buggy and just need to be reflashed?
I can't seem to figure this out, and I can't even find all the modem files for the cyanogenmod 12.1 I used...it's starting to become a nightmare! Help!
Yes, SIM cards can fail.
No, the modem files aren't buggy and shouldn't normally require re-flashing. That said, it doesn't hurt anything at all to flash a modem any amount of times. I would suggest you flash the entire Bootstack instead of just the modem. The Bootstack includes the modem. For CM 12.1, the 24B Bootstack from @xdabbeb 's VS985 v2.0 ROM thread is what you need. For reference, the 12B Bootstack is for KitKat, 24B is for Lollipop 5.0.x and 35B is for Lollipop 5.1.x and Marshmallow 6.0. I doubt if reflashing the modem/bootstack will achieve any result you're looking for. If your phone still lists a baseband in the Settings/About menu, then the modem's working.
The modem partition itself is only one file, modem.img.
Last but not least, it's very common for anyone who uses non-stock LG VS985 ROMs that they eventually have problems, usually with Mobile Data but maybe trouble recognizing the SIM card too. Unless you flash back to stock (I suggest the 10B TOT, which will wipe all data including internal storage) and it's possible that you'll find there's nothing wrong with your SIM card at all - if you remain on stock.
I've considered going back to the stock, I felt that the Cyanogenmod for the VS985 was actually a downgrade. The camera for the LG G3 was pretty badass and I never ever had issues with data. CM does allow some cool stuff, so maybe just a rooted version of the stock ROM is what I should go back to...hmmmmmm....
Did you mean this thread for the bootstacks/modems? http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
thegreataus said:
I've considered going back to the stock, I felt that the Cyanogenmod for the VS985 was actually a downgrade. The camera for the LG G3 was pretty badass and I never ever had issues with data. CM does allow some cool stuff, so maybe just a rooted version of the stock ROM is what I should go back to...hmmmmmm....
Click to expand...
Click to collapse
For what it's worth, the paid version of G3TweaksBox for Marshmallow Xposed module helps alleviate some of the pain of not running CM ROMs. Good luck!
roirraW "edor" ehT said:
For what it's worth, the paid version of G3TweaksBox for Marshmallow Xposed module helps alleviate some of the pain of not running CM ROMs. Good luck!
Click to expand...
Click to collapse
Where do I find this G3tweaksbox? Never heard of it
thegreataus said:
Where do I find this G3tweaksbox? Never heard of it
Click to expand...
Click to collapse
Just Goggle for:
Code:
G3TweakBox Marshmallow
and you should find the XDA thread.
I'm on same Problem with my VS985 running on STOCK 6.0 (KDZ). sometimes network bars shows up but it can not make or receive calls/msgs & also no data connectivity from past 2 moths my LG G3 is a 5" Android Tablet nothing much.
DO reply for any solution/suggestion
morfiq said:
I'm on same Problem with my VS985 running on STOCK 6.0 (KDZ). sometimes network bars shows up but it can not make or receive calls/msgs & also no data connectivity from past 2 moths my LG G3 is a 5" Android Tablet nothing much.
DO reply for any solution/suggestion
Click to expand...
Click to collapse
Exchange your SIM card at a Verizon store. Also, has the phone ever been previously rooted? If so, see the last paragraph of the second post in this thread.
roirraW "edor" ehT said:
Exchange your SIM card at a Verizon store. Also, has the phone ever been previously rooted? If so, see the last paragraph of the second post in this thread.
Click to expand...
Click to collapse
Exchanging is what a have already done, no luck but I will try 10B TOT, I'm wondering how to Flash this(TOT) file. I tried with TWRP and some unusual error message came up
morfiq said:
Exchanging is what a have already done, no luck but I will try 10B TOT, I'm wondering how to Flash this(TOT) file. I tried with TWRP and some unusual error message came up
Click to expand...
Click to collapse
If you Googled "How to flash TOT" you'd get the general idea. You can't flash TOTs or KDZs from the phone, you need to use a Windows PC.
http://forum.xda-developers.com/showpost.php?p=69287997&postcount=6
My wife's SIM slot suddenly stopped working a month ago. LG wanted $75 to fix it, so we didn't have it fixed and we'll be in the market for new phones soon - she's just using her old flip phone for now. Apparently it's a common issue with the VS985.
Not sure why mods locked my other post, but I DO NOT have an international version of LG G3, I have a Verizon version, VS985.
And this issue is not about Fulmic's ROM, but is about Xdabebb's 47a Marshmallow ROM which is a stock rom.
So I am going to repost, in hope of getting the help I was looking for originally.
I'm pretty tired of my LG G3 which I've owned now for a few months. It is the VS985 version. Purchased brand new.
I started off on the stock Kitkat it came with. Connectivity with Verizon 4g was fine, but the phone overheated regularly.
Then I updated to Fulmics 5.2, which worked okay, but only gave me slow 3g data.
Next I reverted all the way back to stock 10b, and then tried Xdabebb's Stock 47a. The rom works fine, but 4g connectivity is ****! I get constant blinking triangles (roaming) even though roaming is turned off. Worse yet, I don't get phone calls or texts half the time, and it constantly loses data connection. I got a new sim card, which works fine in my Nexus 6, but fails to be consistent in my LG G3.
Here's my questions:
1. Is there a fix with XDAbebb's 47a? Should I reflash the 35b bootstack?
2. If XDAbebb's 47a is the problem, is there a ROM that people have had good Verizon experience on?
3. Or should I just sell my LG G3 and move onto another phone or go back to my nexus 6 (which I like but it's so huge!)
I don't want to waste a lot of more time on this.
Mods, please don't lock this, as it is a different set of questions/issues from my other Fulmic's thread.
android94301 said:
Next I reverted all the way back to stock 10b, and then tried Xdabebb's Stock 47a. The rom works fine, but 4g connectivity is ****! I get constant blinking triangles (roaming) even though roaming is turned off. Worse yet, I don't get phone calls or texts half the time, and it constantly loses data connection. I got a new sim card, which works fine in my Nexus 6, but fails to be consistent in my LG G3.
Here's my questions:
1. Is there a fix with XDAbebb's 47a? Should I reflash the 35b bootstack?
2. If XDAbebb's 47a is the problem, is there a ROM that people have had good Verizon experience on?
3. Or should I just sell my LG G3 and move onto another phone or go back to my nexus 6 (which I like but it's so huge!)
I don't want to waste a lot of more time on this.
Mods, please don't lock this, as it is a different set of questions/issues from my other Fulmic's thread.
Click to expand...
Click to collapse
1. There's nothing that needs fixing in @xdabbeb 's stock 47A firmware, at least for the majority of people. It's as completely stock 47A as can be possible while being rooted and still being able to get into TWRP - there's no other differences from stock unrooted 47A. The 35B Bootstack is part of what's necessary in order to have a working modem while still being able to get into TWRP.
I doubt if reflashing the bootstack will make a difference but it doesn't hurt anything either. Does your Settings/About menu list a baseband and an IMEI for your device? If it does, it's doubtful that reflashing the bootstack will help, and that would only help if it said you have no baseband, or the wrong one. Just reflash it though if you have any doubts, like I said, it doesn't hurt anything to flash it.
2. @xdabbeb 's VS985 v2.0 ROM (based on 35B) is overall my very favorite ROM although I've been using his 47A and the 46A before it ever since he released them, along with heavy debloating. His VS985 v2.0 ROM is more heavily modified from stock 35B which is why he differentiates between his VS985 v2.0 ROM and his stock 47A firmware and although 47A in general is really smooth, you can tell the pride he took doing the work he did on the 2.0 ROM.
3. Only you can decide this. Have you tried flashing the 10B TOT (which will wipe your data and internal storage too)? As @xdabbeb taught me and I've personally witnessed when I checked into it, TOTs flash more partitions than KDZs do. Flashing the 10B TOT can fix things that flashing any KDZ or ROM won't. I had a weird problem several months ago that no matter what ROM or KDZ (including 10B) I flashed, the problem persisted. It wasn't until I flashed the 10B TOT that the problem went and stayed away.
It's very common that people that flash several ROMs, especially when some of them are CM/AOSP based and/or international stock ROM ports that they have trouble with mobile data afterward until they flash back to stock. I realize (I think you said) that you flashed the KDZ but try the TOT and go from there. Once you flash it, verify if everything is working 100% okay before rooting, putting TWRP on and flashing anything else. Then once you do that, go straight to flashing whichever stock-based ROM you decide on including the appropriate bootstack.
4. Please mail me your Nexus 6 so I have a new toy to play with.
Thanks, and see my replies below.
roirraW "edor" ehT said:
1. There's nothing that needs fixing in @xdabbeb 's stock 47A firmware, at least for the majority of people. It's as completely stock 47A as can be possible while being rooted and still being able to get into TWRP - there's no other differences from stock unrooted 47A. The 35B Bootstack is part of what's necessary in order to have a working modem while still being able to get into TWRP.
I doubt if reflashing the bootstack will make a difference but it doesn't hurt anything either. Does your Settings/About menu list a baseband and an IMEI for your device? If it does, it's doubtful that reflashing the bootstack will help, and that would only help if it said you have no baseband, or the wrong one. Just reflash it though if you have any doubts, like I said, it doesn't hurt anything to flash it.
[My setting DO not list an IMEI. Is there a problem I need to fix?]
2. @xdabbeb 's VS985 v2.0 ROM (based on 35B) is overall my very favorite ROM although I've been using his 47A and the 46A before it ever since he released them, along with heavy debloating. His VS985 v2.0 ROM is more heavily modified from stock 35B which is why he differentiates between his VS985 v2.0 ROM and his stock 47A firmware and although 47A in general is really smooth, you can tell the pride he took doing the work he did on the 2.0 ROM.
[Thanks maybe I'll try this 2.0 version.]
3. Only you can decide this. Have you tried flashing the 10B TOT (which will wipe your data and internal storage too)? As @xdabbeb taught me and I've personally witnessed when I checked into it, TOTs flash more partitions than KDZs do. Flashing the 10B TOT can fix things that flashing any KDZ or ROM won't. I had a weird problem several months ago that no matter what ROM or KDZ (including 10B) I flashed, the problem persisted. It wasn't until I flashed the 10B TOT that the problem went and stayed away.
[Yes, I flashed the Tot file to 10b, before I went to 47A.]
It's very common that people that flash several ROMs, especially when some of them are CM/AOSP based and/or international stock ROM ports that they have trouble with mobile data afterward until they flash back to stock. I realize (I think you said) that you flashed the KDZ but try the TOT and go from there. Once you flash it, verify if everything is working 100% okay before rooting, putting TWRP on and flashing anything else. Then once you do that, go straight to flashing whichever stock-based ROM you decide on including the appropriate bootstack.
[OK, will try the stock Tot 10b again and make sure it's all okay before rooting or upgrading. How do I fix the IMEI though? ]
4. Please mail me your Nexus 6 so I have a new toy to play with.
Click to expand...
Click to collapse
[What's your address? JK, I actually love my Nexus 6 but sometimes want a smaller phone to carry.]
android94301 said:
Thanks, and see my replies below.
Click to expand...
Click to collapse
You're welcome!
[My setting DO not list an IMEI. Is there a problem I need to fix?]
Click to expand...
Click to collapse
I'm attaching screenshots for where you should find the IMEI on 47A (Settings/About/Status) Just to be clear, you're saying you found the spot the IMEI should be in but it's not listed there? And you do have a baseband listed (Settings/About/Software info)? If so, then not having an IMEI is definitely the problem.
[Yes, I flashed the Tot file to 10b, before I went to 47A.]
Click to expand...
Click to collapse
It probably won't make any difference then if you went straight from the 10B TOT, Stump root, TWRP to 35B Bootstack and 47A firmware. Sounds like the no IMEI thing is the problem.
[OK, will try the stock Tot 10b again and make sure it's all okay before rooting or upgrading. How do I fix the IMEI though? ]
Click to expand...
Click to collapse
You can't make phone calls either, right? I'm no expert on fixing no IMEI - I've never had to do that personally. When in TWRP, I use it to backup the EFS which I believe includes the IMEI, so that if it should get lost (which happens sometimes when flashing KDZs and TOTs), I can just restore it via TWRP.
If you don't have a TWRP backup of your EFS, then assuming you have the box the phone came in, or some record of what the IMEI was, I believe you have to use some Windows software - maybe QPST - to manually type the IMEI back in the right place. I know there's threads in the General and Q&A section, and probably those sections in the non-Verizon G3 forums too. I'd have to search for the threads myself though.
[What's your address? JK, I actually love my Nexus 6 but sometimes want a smaller phone to carry.]
Click to expand...
Click to collapse
Every once in a while I'm tempted to go Nexus, but I guess none have attracted me enough yet, either feature/storage/camera/review/size and/or price-wise. I don't think I'd like anything bigger than the G3.
You are a genius! Saved my LG G3 from Craigslist
roirraW "edor" ehT said:
You're welcome!
I'm attaching screenshots for where you should find the IMEI on 47A (Settings/About/Status) Just to be clear, you're saying you found the spot the IMEI should be in but it's not listed there? And you do have a baseband listed (Settings/About/Software info)? If so, then not having an IMEI is definitely the problem.
It probably won't make any difference then if you went straight from the 10B TOT, Stump root, TWRP to 35B Bootstack and 47A firmware. Sounds like the no IMEI thing is the problem.
You can't make phone calls either, right? I'm no expert on fixing no IMEI - I've never had to do that personally. When in TWRP, I use it to backup the EFS which I believe includes the IMEI, so that if it should get lost (which happens sometimes when flashing KDZs and TOTs), I can just restore it via TWRP.
If you don't have a TWRP backup of your EFS, then assuming you have the box the phone came in, or some record of what the IMEI was, I believe you have to use some Windows software - maybe QPST - to manually type the IMEI back in the right place. I know there's threads in the General and Q&A section, and probably those sections in the non-Verizon G3 forums too. I'd have to search for the threads myself though.
Every once in a while I'm tempted to go Nexus, but I guess none have attracted me enough yet, either feature/storage/camera/review/size and/or price-wise. I don't think I'd like anything bigger than the G3.
Click to expand...
Click to collapse
Thanks for your help. As you can see from the pics I've attached, baseband is fine, and there is no IMEI. Must have gotten nuked somehow when I went from Fulmics to 10b to 47A. I have an EFS backup in TWRP, so will try to restore the EFS partition.
I just did, and my IMEI is back, although phone number is blank, IMS registered status is Not Registered, ICCID says unknown. Let's try putting the sim card back in and see what happens.
IMEI is there, as is ICCID. IMS is still not registered. Phone number now shows up. As does PRL. Just tried phone calls and they now work, let's try a text. Works!!!!
Now lets try a data test. Speedtest now is off the charts! 74mbps down, and 13mbps up! Can't beat that.
roirraW "edor" ehT you are a genius, seems like that solved it. Now I guess I should make another nandroid backup while I've got everything working.
One last question, is the improvement of XDAbebb's VS985 v2.0 debloated enough to make it worth going from 47a to that one? Thanks again.
And no stupid blinking triangle of roaming! Tried Google Play store and now things install rapidly.
android94301 said:
Thanks for your help. As you can see from the pics I've attached, baseband is fine, and there is no IMEI. Must have gotten nuked somehow when I went from Fulmics to 10b to 47A. I have an EFS backup in TWRP, so will try to restore the EFS partition.
I just did, and my IMEI is back, although phone number is blank, IMS registered status is Not Registered, ICCID says unknown. Let's try putting the sim card back in and see what happens.
IMEI is there, as is ICCID. IMS is still not registered. Phone number now shows up. As does PRL. Just tried phone calls and they now work, let's try a text. Works!!!!
Now lets try a data test. Speedtest now is off the charts! 74mbps down, and 13mbps up! Can't beat that.
roirraW "edor" ehT you are a genius, seems like that solved it. Now I guess I should make another nandroid backup while I've got everything working.
One last question, is the improvement of XDAbebb's VS985 v2.0 debloated enough to make it worth going from 47a to that one? Thanks again.
And no stupid blinking triangle of roaming! Tried Google Play store and now things install rapidly.
Click to expand...
Click to collapse
Both roms are excellent xdabebbs 2.0 is pretty slimmed down and runs really smooth. And his 47A is as close to stock marshmallow as you can get but still being rooted. I'm always flashing back and forth between the two, sometimes a few times per week lol I would recommend either one since they are both awesome. If you run 47A you can use some debloating zips that the warrior has made, and remove a lot of bloat or only take out what you want. I hope this helps in anyway and glad you got your g3 working now.
Sent from my g3 using XDA Labs
android94301 said:
Thanks for your help. As you can see from the pics I've attached, baseband is fine, and there is no IMEI. Must have gotten nuked somehow when I went from Fulmics to 10b to 47A. I have an EFS backup in TWRP, so will try to restore the EFS partition.
I just did, and my IMEI is back, although phone number is blank, IMS registered status is Not Registered, ICCID says unknown. Let's try putting the sim card back in and see what happens.
IMEI is there, as is ICCID. IMS is still not registered. Phone number now shows up. As does PRL. Just tried phone calls and they now work, let's try a text. Works!!!!
Now lets try a data test. Speedtest now is off the charts! 74mbps down, and 13mbps up! Can't beat that.
[URL=" "edor" ehT[/I][/COLOR][/URL] you are a genius, seems like that solved it. Now I guess I should make another nandroid backup while I've got everything working.
One last question, is the improvement of XDAbebb's VS985 v2.0 debloated enough to make it worth going from 47a to that one? Thanks again.
And no stupid blinking triangle of roaming! Tried Google Play store and now things install rapidly.
Click to expand...
Click to collapse
Awesome! You're welcome. I'm glad it was that relatively simple and that you had an EFS Backup! I (think I) keep a cloud backup of just an EFS TWRP backup of all of my wife's and my devices just in case. Much simpler than fooling around in proprietary software.
I've just luckily seen enough people have the no IMEI problem enough times on this device - glad it hasn't happened to me yet.
Hi,
I have the Verizon LG G3 on Android 6.0 and it frequently loses connection with the SIM card, saying "SIM Card not readable" or "No SIM found" in the notifications. A reboot can temporarily fix the problem, but the phone always encounters the problem while booted. I don't know if this is a hardware or software problem or what can be done to permanently fix it.
Thanks for any help or input!
Hi!
You've probably already thought of this, but have you tried taking the SIM card completely out and then re-inserting it, making sure it's in all the way?
Are you rooted or non-rooted? If rooted, try restoring to 100% stock unrooted. If you plan on rooting after confirming if that fixes it, stick with the 10B TOT and then confirm if the problem still occurs. You might want to try the 10B TOT anyway because flashing TOTs can fix weird problems that flashing KDZs or ROMs can't. TOTs flash more partitions than KDZs.
Lastly that I can think of, a few others on this phone have had the same trouble and found that when they took the phone/SIM card to Verizon and they replaced the SIM card with another one for them, the problem was fixed. So the trouble might be a flaky SIM card.
Good luck! Let us know how things work out.
I too have the same issue. Got a replacement sim card sent to me last week. That didn't fix the problem. LG sent me a replacement phone Monday June 27th 2016. Worked flawlessly those 2 days I had it. Now this morning in wake up to. "Sim card not found" a simple shutdown and remove the sim card and reinsert it worked. But this is exactly how this problem started before. Could get by with doing that for about a week. Then my old phone wouldn't even recognize there was a sim card installed. Help if anyone has any answers. Verizon can't seem to figure anything out.
I have the same problem as well. Exact same. Haven't got around to buying a new sim card and I am glad.
JTlane16 said:
I have the same problem as well. Exact same. Haven't got around to buying a new sim card and I am glad.
Click to expand...
Click to collapse
From what I've read of others' experiences, Verizon users were able to exchange their faulty one for a good one at a store. Of course if you're not using a Verizon SIIM or you're out of the country...
I'm having the same issue. I have tried different modems/bootstacks and that hasn't worked. I guess I'm going to try the TOT and report back if that fixes it.
Also,I haven't tried a different sim. It actually hasn't recognised the sim in a long long time. I've used an LG V10 as my DD since January so haven't needed my G3 to work but I really want to get this thing working again.
imucarmen said:
I'm having the same issue. I have tried different modems/bootstacks and that hasn't worked. I guess I'm going to try the TOT and report back if that fixes it.
Also,I haven't tried a different sim. It actually hasn't recognised the sim in a long long time. I've used an LG V10 as my DD since January so haven't needed my G3 to work but I really want to get this thing working again.
Click to expand...
Click to collapse
Good luck! Keep us updated. If the TOT doesn't work are you going to try exchanging your SIM? If you're using the same SIM in a different device and it's fine, then in your case it might not make a difference unfortunately.
roirraW "edor" ehT said:
Good luck! Keep us updated. If the TOT doesn't work are you going to try exchanging your SIM? If you're using the same SIM in a different device and it's fine, then in your case it might not make a difference unfortunately.
Click to expand...
Click to collapse
Actually i just got it working again. I'm on the latest release of Bliss and started on the 35b modem. I flashed back to the 24b and the sim still wouldn't work. So then I flashed back to the 35b, wiped dalvik and cache, and now it's working. Not sure if it's going to stay working but I made some calls and everything seems in order so far.
My G3 started doing the same thing about a month ago. Tried flashing about 3 new roms to no avail, and the final ROM hard bricked my phone. Had to JTAG to get back to soft brick then TOT recovery to get back to system. IMEI is null (all zeros) and I still receive SIM error. It all started a few weeks after flashing a custom marshmallow rom (don't know if it was related directly). I had to get a replacement in the meantime but I would really like to get my G3 back in working condition. Any suggestions?
mc1175 said:
My G3 started doing the same thing about a month ago. Tried flashing about 3 new roms to no avail, and the final ROM hard bricked my phone. Had to JTAG to get back to soft brick then TOT recovery to get back to system. IMEI is null (all zeros) and I still receive SIM error. It all started a few weeks after flashing a custom marshmallow rom (don't know if it was related directly). I had to get a replacement in the meantime but I would really like to get my G3 back in working condition. Any suggestions?
Click to expand...
Click to collapse
If you don't have a TWRP backup of your EFS (which includes the IMEI) then you'll have to search XDA and/or the G3 sections for the directions, which involves proprietary software used on Windows, and you'll have to know what your IMEI was (on the original box, might be on some paper record, your carrier might know the old info).
roirraW "edor" ehT said:
If you don't have a TWRP backup of your EFS (which includes the IMEI) then you'll have to search XDA and/or the G3 sections for the directions, which involves proprietary software used on Windows, and you'll have to know what your IMEI was (on the original box, might be on some paper record, your carrier might know the old info).
Click to expand...
Click to collapse
I do have a few TWRP backups, do full backups include EFS? I still have the IMEI (on sticker in phone) so I can do some searching for a tool to reset it. What I've seen seems fairly in-depth (hex editor) but if it'll work I'll have a go at it.
mc1175 said:
I do have a few TWRP backups, do full backups include EFS? I still have the IMEI (on sticker in phone) so I can do some searching for a tool to reset it. What I've seen seems fairly in-depth (hex editor) but if it'll work I'll have a go at it.
Click to expand...
Click to collapse
That's why TWRP is the easiest way to restore.
I don't know what you consider "Full". When you do backups and restores it lists all the partitions and defaults to whatever you backed up last, but you can select and deselect partitions as you wish.
I keep a backup of only the EFS for all three of our devices on Google Drive for just in case.
Just try a restore and see if it lists EFS as one of the partitions you can restore. If not, don't bother. If it does, deselect all other partitions and only select EFS to restore that.
roirraW "edor" ehT said:
That's why TWRP is the easiest way to restore.
I don't know what you consider "Full". When you do backups and restores it lists all the partitions and defaults to whatever you backed up last, but you can select and deselect partitions as you wish.
I keep a backup of only the EFS for all three of our devices on Google Drive for just in case.
Just try a restore and see if it lists EFS as one of the partitions you can restore. If not, don't bother. If it does, deselect all other partitions and only select EFS to restore that.
Click to expand...
Click to collapse
Really beating myself up, I could have sworn that when I took backups I selected every single box. I had 3 TWRP backups and none had EFS partitions included. I guess I'll have to find another way.
mc1175 said:
Really beating myself up, I could have sworn that when I took backups I selected every single box. I had 3 TWRP backups and none had EFS partitions included. I guess I'll have to find another way.
Click to expand...
Click to collapse
Oh, sorry to hear that! For what it's worth, you could take a look at the new thread posted in the General section with "DIAG" in the thread title. I've never had to restore my IMEI by any method, but the OP says that his findings might help with restoring the IMEI, although I know he mentions QPST which I believe is what others used to manually put their IMEI back in too, so I have no idea if there's a difference or improvement to it with what he reveals. I know there are other threads in either the Verizon G3 General and/or Q&A sections or the non-Verizon sections having to do with restoring IMEI using the Windows software. Good luck in your quest.
roirraW "edor" ehT said:
Oh, sorry to hear that! For what it's worth, you could take a look at the new thread posted in the General section with "DIAG" in the thread title. I've never had to restore my IMEI by any method, but the OP says that his findings might help with restoring the IMEI, although I know he mentions QPST which I believe is what others used to manually put their IMEI back in too, so I have no idea if there's a difference or improvement to it with what he reveals. I know there are other threads in either the Verizon G3 General and/or Q&A sections or the non-Verizon sections having to do with restoring IMEI using the Windows software. Good luck in your quest.
Click to expand...
Click to collapse
That article worked like a charm! IMEI restored just like it said. Oddly enough the SIM card still seems to eject randomly (no sim error), but the phone can now make calls and when the error does occur a reboot usually fixes it. At this point it's seeming like a hardware problem, but the only method I have of testing that is sending it back to LG which is an idea I'm not particularly fond of. I've done a bit of looking around and it seems I'm not nearly the only one with this issue on the G3:
https://www.reddit.com/r/LGG3/comments/4edhs1/sim_not_readable_and_no_sim_found_vs985/
https://community.verizonwireless.com/thread/832587
Both of those were just for the VS985, let alone dozens of others for the T-mo and ATT variants. Not sure whether to be relieved or disappointed but I suppose I'm at the next step. Any other info would be helpful.
mc1175 said:
That article worked like a charm! IMEI restored just like it said. Oddly enough the SIM card still seems to eject randomly (no sim error), but the phone can now make calls and when the error does occur a reboot usually fixes it. Any other info would be helpful.
Click to expand...
Click to collapse
A lot of people with this trouble solved it by exchanging their SIM card at a Verizon store. As far as I know it was free to do so. However, there have been others for whom this didn't solve anything.
It's funny, this thread was started by someone else and others besides you had commented with the same issue but only one of the four others has followed up after suggestions are made.
Make that EFS backup and store it securely!
well if someone solved the SIM problem i would love to hear it,i have been thru 4 SIM cards,2 brand new vs985 and all of them have the exact same problem,i was soo worried i screwed up my phone(was rooted) that i unrooted,stated all over again with 10b,in between rerooting i lost the SIM signal,long story short,im on my 4th phone and have the sdame problem again,,yes i am stock 48a,and verizon claims only the lg4 has been troubled with the SIM card....still got 1 more year of the vs985 so kinda searching for a solution.as i said i was worried it was my flashing too much or anything to do with that but since this phone is 4 days old,with a new SIM i am at a total loss...thanks...
same probblem here...started few days ago on my G3....wtf
bad news from lovely verizon, told me the update added security which conflicts with the SIM, so today i got my 5th phone in 10 days, honestly sick of the guess game from verizon, 5 SIM cards, 5th phone, dont even know who to trust, i spent 3 days wiping my phone from jasmine thinking i messed up, down graded to 10b,then took ota updates all the way to 48a,so verizon wouldnt bag me, and then they give me 4 more phones with the exact problem, now todays phone lasted 4 hrs and i list SIM again...
fropalace said:
Hi,
I have the Verizon LG G3 on Android 6.0 and it frequently loses connection with the SIM card, saying "SIM Card not readable" or "No SIM found" in the notifications. A reboot can temporarily fix the problem, but the phone always encounters the problem while booted. I don't know if this is a hardware or software problem or what can be done to permanently fix it.
Thanks for any help or input!
Click to expand...
Click to collapse
I had same issue, but i could fix it by doing this