Related
Hi guys,
I managed to accidentally grab the ATT version of LiquidSmooth and flash it. Since then, I've had strange issues with service. Here's what I've tried:
Flashing (Verizon) versions of CM, LiquidSmooth, and Hyperdrive
Flashing the original and ME7 modems with Heimdall and Odin
Wiping data, system, caches, and fixing permissions before/after every flash
Randomly toggling Mobile Network settings (but I have no idea what I'm doing there)
[*[Searching everywhere I could think of on the forums
I had 0 service on either AOSP ROM I tried. Right now, I'm running Hyperdrive and getting weird results.
Sometimes it asks be to switch to "Global Mode" and shows that I'm roaming.
If I try to call, it says it can't find a mobile network and fails.
After leaving it sitting for a while (right after a clean flash), all the texts I missed came through.
If I try to text somebody, I'm warned that the mobile network is unavailable, but the text still goes through!
4G is working on Hyperdrive. Wifi still works on everything.
com.android.phone crashes when I try change the Network mode away from Global
I'd love to hear any suggestions you guys might have for me. Not sure what I have left to try.... is there a master reset for all of this?
Thanks!
EDIT
Some more details:
About Phone > Status in CM after fresh flash:
Network: Verizon
Signal Strength: 2147483647 (2^31 - 1) dBm, 255 (2 ^ 8 - 1) asu .......WHAT
Mobile network type: CDMA - 1xRTT:7
Service state: In service
Roaming: roaming
Mobile network: Disconnected
My phone number: something completely wrong
MEID, IMEI, ICCID are all there, but don't know how to tell if they're also whacked out
The APNs list is blank and my signal jumps between zero bars and a few bars + roaming. Call and text not working.
I've also attached my PIT file (grabbed with Heimdall). Have no idea how to read it.
Do you have a nandroid backup that includes your EFS partition? If so, I would try restoring it and seeing what happens. Sounds like something got out of whack in there and is giving your phone a hard time doing it's #1 job.
This is what ultimately switched me to the S4, my GNex randomly decided one day that it wasn't going to be a phone anymore, and I didn't have an EFS backup to restore in order to try and fix it.
Two things -
1. Always, always, always, make sure the ROM you are flashing is the correct ROM.
2. Always keep an ODIN file on handy of the full system image, here is the full MDK software, this WILL wipe all of your data - http://www.sxtpdevelopers.com/showthread.php?t=237
Sent from my Nexus 7 using xda premium
woierfere must
grussinko said:
Do you have a nandroid backup that includes your EFS partition? If so, I would try restoring it and seeing what happens. Sounds like something got out of whack in there and is giving your phone a hard time doing it's #1 job.
This is what ultimately switched me to the S4, my GNex randomly decided one day that it wasn't going to be a phone anymore, and I didn't have an EFS backup to restore in order to try and fix it.
Click to expand...
Click to collapse
I don't have a backup. That will definitely be the first thing I do when I get this working again.
gaontr the
Rebel908 said:
Two things -
1. Always, always, always, make sure the ROM you are flashing is the correct ROM.
2. Always keep an ODIN file on handy of the full system image, here is the full MDK software, this WILL wipe all of your data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
1. I know. LiquidSmooth could have done a better job of linking to the right place on their post, but it was still really dumb on my part.
2. Thanks for this! It looks like I'll be able to try this out tonight (slow connection). The SD card data is safe right? Also, I'm just downloading the tar - not sure what the exe is for.
I haven't used Odin for this since it was on version 1.8 or something (now it's over 3)... it looks like I still just choose the tar from the PDA block and hit go... no specific other settings needed for this phone / flash, right?
No luck :/ . I unzipped the stock restore, flashed in Odin (PDA), and booted fine. I have 4G and texts working, but no calling (mobile network not available) and calling my phone goes straight to voicemail. Also, it's very adamant about keeping me in Global mode over LTE/CDMA. This is the same state I was in earlier while running Hyperdrive, except now I don't have root.
I feel like I've tried everything there is to try. Does anyone have any further suggestions?
Are there any areas of software that don't get reset when flashing the stock images in Odin, and that could have been corrupted from the bad flash?
Thanks.
It's probably also worth mentioning that I'm warned about there being no mobile network when I send texts. I can cancel the dialog and they still go through. People can text me without issues.
espacex said:
No luck :/ . I unzipped the stock restore, flashed in Odin (PDA), and booted fine. I have 4G and texts working, but no calling (mobile network not available) and calling my phone goes straight to voicemail. Also, it's very adamant about keeping me in Global mode over LTE/CDMA. This is the same state I was in earlier while running Hyperdrive, except now I don't have root.
I feel like I've tried everything there is to try. Does anyone have any further suggestions?
Are there any areas of software that don't get reset when flashing the stock images in Odin, and that could have been corrupted from the bad flash?
Thanks.
Click to expand...
Click to collapse
I had the same happen to me when I was working on getting radio on MIUI ROM, after tinkering with the Sprint version, only 4G would work, and occasionally roaming would work. Every time I tried to make a call, it told me there was no mobile network available, and it constantly tried to switch into Global Mode instead of CDMA/LTE.
Sadly, the only thing that worked for me was getting my phone replaced with a brand new one. If you find anything that works please be sure that you post it, because someone else may end up doing the same thing.
Jonestown said:
I had the same happen to me when I was working on getting radio on MIUI ROM, after tinkering with the Sprint version, only 4G would work, and occasionally roaming would work. Every time I tried to make a call, it told me there was no mobile network available, and it constantly tried to switch into Global Mode instead of CDMA/LTE.
Sadly, the only thing that worked for me was getting my phone replaced with a brand new one. If you find anything that works please be sure that you post it, because someone else may end up doing the same thing.
Click to expand...
Click to collapse
Did you get it replaced via warranty? If so, did you need to do anything besides flashing a stock image in Odin beforehand?
Maybe try flashing the stock rooted ME7 that includes the new radios? Couldn't hurt at this point.
Edit: whoops, saw you already tried that
Sent from my SCH-I545 using xda app-developers app
Does anybody know whether ODIN / recovery deletes the partitions before writing new ones? If a file existed in the ATT rom, but not in the Verizon one, would it still be on my phone if I flashed the Verizon rom over the ATT one? Obviously this assumes a data / cache wipe in between. I'm really talking more about the other partitions.
Also, does anyone have any experience trying to get a replacement via warrantee after flashing? I've read all about the binary counter on our model, but didn't see any success / failure stories yet from people returning phones after flashing stock + unrooting.
Last question for now: is there any reason to believe that taking the recent update would help my situation? Maybe that could reset whatever is causing my calling issue.... just a random guess. I know that I'd lose any chance of getting root back (at least for a while).
Thanks again for the help guys!
Ok, i'm fairly new to this stuff but have successfully rooted and modified several of my devices over the years. I've been attempting to upgrade my vs985 to as close to stock 5.1.1 as i can and after much reading decided on jasmine. I was rooted on kk 4.4.2 12b and I had no problems. the main reason i wanted to upgrade was for compatibility with my android play car stereo. I didn't have twrp so first i downloaded flashify and quickboot then flashed twrp from flashify. All good so far. Next I downloaded jasmine 9.0 and 9.1 or at least i thought lol. As it so happened i mistakenly ended up with one of the files being just the kernel for 5.1.1 35b. Must of been a long day cause I mistakenly failed to backup my current system and proceeded wipe data, cache, dalvik, and flashed the kernel file. As you might imagine it didn't turn out very good. I was stuck in boot loop. Fortunately I could still get into download mode so I was able to use the lg flash tool and I brought it all the way back to 10b stock firmware. Then i grabbed stump and rooted and flashed twrp again. at some point i noticed my cell signal was all over the place, up, down , no signal and it roamed almost constantly if there was any signal. I've had this phone and service for well over a year and never had anything like this at all. I knew it was something I did. I checked the back cover to be sure it was on properly and had good connection with the antenna and all checked out. I decided to go ahead and do the upgrade to jasmine 9.1 hoping this would correct the issue. Well no dice. I did create a backup this time and proceeded to wipe everything and flash 9.0 reboot then wipe nothing and flash 9.1, i guess as you call it "dirty" then reboot again. Here is a link to where i got the zips and instructions
http://forum.xda-developers.com/showpost.php?p=63305722&postcount=4842
in the instructions it says "RESET factory from within ROM (in Settings) - REQUIRED" . this step seemed strange as why would i do a factory reset on my device and erase everything i just did? would it not return it to original? I wasn't even sure if that was what he meant so i skipped that. After all was finished my signal was still all over the place could hardly make a call. it was bad. So once again I used lg flash tool and returned it to stock 4.4.2 10b, this time I wiped the data, cache, delvik and system. To my complete surprise the signal had not improved, in fact it could have actually been worse. As I said waaaaaay at the top of this post before i started all this i was running 4.4.2 12b, not sure how i ended up with 12b as i don't remember any upgrades after i downgraded to 10b and rooted. I froze the ota's with titanium backup but maybe 12b was pushed before i was able to freeze them. Anyway I couldn't figure out how to get 12b back now so I just flashed the 4.4.2 12b modem instead, This time I wiped cache and delvik before and after the flash then rebooted. This fixed my signal, everything seems normal now. no roaming and good signal. my software build however still shows 10b, but I guess thats correct since I only flashed the modem.
I really want 5.1.1 on my G3 but I need my signal too lol. can any one help me figure out how to get this done, can I flash the 12b modem on 5.1.1 this is where i got the file
http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641 it is way down the bottom of the page. Sorry for the extremely long post i just wanted to make sure i didn't leave any details out.
Any help would be greatly appreciated,
thanks in advance
@Allen227
i dont know if jasmine flashes the L modem when you flash it, but if it doesnt, that would be why you are having issues after flashing the rom.
other than that, i dont know what would cause modem issues.
bweN diorD;4132606 [user=7106818 said:
@Allen227[/user]
i dont know if jasmine flashes the L modem when you flash it, but if it doesnt, that would be why you are having issues after flashing the rom.
other than that, i dont know what would cause modem issues.
Click to expand...
Click to collapse
@Allen227
TL;DR but yes, JasmineROM flashes the appropriate modem. v9.0 only flashes the 24B modem because it doesn't contain a fuller set of the necessary partitions to allow the 35B modem to work by simply replacing the 24B modem with the 35B one.
You can flash the 35B bootstack after flashing JasmineROM 9.0 and the 9.1 update, or SkyDragon 6.x, but you must not be on the 35B bootstack before flashing either UNLESS you also flash the 35B bootstack again after flashing the ROM.
For reasons why: http://forum.xda-developers.com/showthread.php?p=64064555
Edit: I meant to add, the 35B boostack contains the 35B modem and everything needed for it to work with JasmineROM 9.0/9.1.
Hi, anybody from bosses ,plz help, sorry for noob querry... using g3 stock rom 4.4.2 and want to upgrade to lollipop and find jasmine ROM most votes. rooted my device with king root and installed twrp 2.8.7.0 recovry. downloaded jasmin ROM9.0, back up my current rom.
can u please guide me steps,
have i too flash kernal before jasmine ROM? or my existing stock kernal will work fine with jasmine 9.1
placed downloaded ROM in my download folder in phone memory [not in sd Card] , when i would boot in recovry in wipe cache delvik etc will it erase this rom and phone data too???
what if something gone rom? in my g3 there is no option of adb , adb does not work on my g3 dont know why.....
if something gone wrong , can i recover phone?
please see attached pics for some clarification...
sorry for,long post, actualy want to be safe ,,, as i am new for these things ..
tAheEr73 said:
Hi, anybody from bosses ,plz help, sorry for noob querry... using g3 stock rom 4.4.2 and want to upgrade to lollipop and find jasmine ROM most votes. rooted my device with king root and installed twrp 2.8.7.0 recovry. downloaded jasmin ROM9.0, back up my current rom.
can u please guide me steps,
have i too flash kernal before jasmine ROM? or my existing stock kernal will work fine with jasmine 9.1
placed downloaded ROM in my download folder in phone memory [not in sd Card] , when i would boot in recovry in wipe cache delvik etc will it erase this rom and phone data too???
what if something gone rom? in my g3 there is no option of adb , adb does not work on my g3 dont know why.....
if something gone wrong , can i recover phone?
please see attached pics for some clarification...
sorry for,long post, actualy want to be safe ,,, as i am new for these things ..
Click to expand...
Click to collapse
In the future, please do not post the same thing in two different threads. This is against XDA's forum rules. Also, no reason to hijack an only partially related thread. I answered you in the JasmineROM thread.
Sorry for rule breaking, actually i did not aware of that. will avoid surely next time and thanks for reply. hats off to you.
Thanks for your help guys. Last night I figured out my phone was allowing me to send and receive text messages and make outgoing calls but was completely unable to receive any calls. Signal still terribly inconsistent, it would be on 4g one minute then you could watch as it dropped then no service. There'd be no service for 3 or 4 minutes then it would repeat that cycle again. If I switch from global to cdma/let in settings it would immediately regain full signal. Then the cycle of it dropping out would start again. I got to looking through about phone in settings and realized my imei number was missing, all zeros. I'm assuming that probably is the root of my problems. Not sure what to do, I doubt Verizon can help. Phones not insured or under warranty anymore. I haven't researched this New development on te forums yet it got to late last night. If anyone knows of this problem I could use your help. Thanks
Allen227 said:
Thanks for your help guys. Last night I figured out my phone was allowing me to send and receive text messages and make outgoing calls but was completely unable to receive any calls. Signal still terribly inconsistent, it would be on 4g one minute then you could watch as it dropped then no service. There'd be no service for 3 or 4 minutes then it would repeat that cycle again. If I switch from global to cdma/let in settings it would immediately regain full signal. Then the cycle of it dropping out would start again. I got to looking through about phone in settings and realized my imei number was missing, all zeros. I'm assuming that probably is the root of my problems. Not sure what to do, I doubt Verizon can help. Phones not insured or under warranty anymore. I haven't researched this New development on te forums yet it got to late last night. If anyone knows of this problem I could use your help. Thanks
Click to expand...
Click to collapse
If you go into the main Verizon G3 section or possibly the non-Verizon G3 section and use the search field to search for "IMEI" you'll probably find a helpful thread. I think it involves the QPST program on a Windows PC. You'll need the IMEI that it's supposed to have, so hopefully have that on the box or Verizon's website lists it.
Sometimes that's seemed to happen for some people when flashing TOTs, KDZs or ROMs. I've been lucky, it hasn't happened to me through all my flashing over the past year. Once you get it fixed, rooted and put TWRP on, you can back up the IMEI partition in TWRP. It's called something else in TWRP like EI or something - I forget.
Good luck!
roirraW "edor" ehT said:
If you go into the main Verizon G3 section or possibly the non-Verizon G3 section and use the search field to search for "IMEI" you'll probably find a helpful thread. I think it involves the QPST program on a Windows PC. You'll need the IMEI that it's supposed to have, so hopefully have that on the box or Verizon's website lists it.
Sometimes that's seemed to happen for some people when flashing TOTs, KDZs or ROMs. I've been lucky, it hasn't happened to me through all my flashing over the past year. Once you get it fixed, rooted and put TWRP on, you can back up the IMEI partition in TWRP. It's called something else in TWRP like EI or something - I forget.
Good luck!
Click to expand...
Click to collapse
Thanks again I will check that out now
Allen227 said:
Thanks again I will check that out now
Click to expand...
Click to collapse
I have spent sooooo many hours on this. The qpst apk wont see my phone I have done everything the tutorials suggest. the instructions are only applicable if there are no issues, in other words, in a perfect world. I'm sure its something stupid and very simple but I don't even have a place to start. First, its hard to believe this works on all OS's, but it doesn't state anywhere what it is and isn't compatible with. that info would be helpful. i have spent 4 hours a day for over a week trying to get this fixed and I'm no closer than i was when I started. Very frustrating. I'm still open to suggestions or any help that can be offered.
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.
For the last two weeks, I've miraculously had 4G LTE working on my vs985 despite using the 35b bootstack and 47a stock firmware (rooted and debloated)
I know it was just on band 4, and the 35b radio disables LTE on non Verizon networks. But somehow, amazingly, it was working anyway even across reboots, cache wipes, flashing zips for xposed, and even TWRP backups/restorations.
But when I removed my SIM card, put it in my old phone, and then put it back in my vs985, I lost 4G LTE!
Here are all the details I can remember, although I don't know what might be relevant or accurate:
Originally, I flashed to 10B stock using the TOT. From there I rooted and installed TWRP and flashed various roms to see what works best. I ended up on CM13, but at that point, my SIM card wasn't being detected at all, and I actually took it to AT&T to check my SIM and it was fine. They told me the phone must have re-locked itself. So I went home and wiped everything but microSD. I flashed the 35b bootstack, vs98547a rooted stock. I set up the phone with my google account and put in AT&Ts NXTGENPHONE APN settings. THEN I flashed a debloat zip (even though it gives you more space if you do it before starting the phone.) When I left the house and my phone disconnected from the Wifi, I had a 4G LTE signal! I had no idea how I got so lucky! When I got home, I made a full backup with TWRP, and kept only the zips I had just used for this setup.
So I got comfortable with the phone for two weeks, and now I'm crushed to have lost LTE! I can still use mobile data if I change my APN settings to "phone" instead of NXTGENPHONE, but it's obviously slower.
I wish I knew exactly why I manged that minor miracle for two weeks. I tried everything again, even flashing TOT, but without luck and I have no idea what perfect storm of events may have affected that magical time.
The zips I saved were: 35b bootstack, rooted vs98547a, and a custom debloat zip. I also saved the 10b radio zip, but I just can't remember if I used it that last time. I can't imagine I did, because obviously it wouldn't work with 47a. But then why did I keep it?
My guess is that somehow I got around the disabling of LTE, perhaps by having something specific flashed to a partition that only TOT can reach? Or maybe an LTEconfig got deleted or modified? Did I somehow hybridize the radios? I heard that maybe autoprime is working on a unified radio that might solve this problem?
Do you guys have any ideas? How did I ever make it work?
I've been having this issue ever since coming back from Europe a couple months ago where sending or receiving any MMS is not possible I always get a "You may be able to send after inserting your SIM". On top of that occasionally my SMS will act the same way, it will require hitting "retry" several times before it goes through. It only occurs on custom ROMs, such as Resurrection Remix and CM13, but when I switch to a Stock rom it works perfectly. It wasn't like this before Europe so I'm not sure what happened. Someone informed me that I would need to flash a Stock rom, used Bare_ceeV2, then backup the EFS folder (Which I did in TWRP), wipe and flash a new rom then restore the backed up EFS. This method failed and I'm still getting the same message. Any idea how I can restore the MMS sending capability, I'd really like to stay on custom rom.