Related
Ok, so I used to have cm11 installed, but it got sort of buggy in the long run.
I decided to try Foxhound rom, just for kicks... When it was finished installing, I got the default IMEI and the phone wouldnt connect to the network. I found a way to fix this (without backing up my efs folder), by installing an old rom. After that, I installed ef extreme rom (the one with the s5 ui).. It was supposed to be the most stable and smooth rom... But the camera and hotspot wouldnt work -_- ... I never understood why.
Anyhow, the problem is, now that Im trying to get off that crappy touchwiz rom, I NEVER get service anymore. My IMEI will always go blank.. Now the baseband goes "unkown" too (which hadnt happened before)... For ****s sake, I was trying to go back to my old cm11, and still, crazy IMEI... However, if i install the old rom all over again and the region modem: boom, mobile network works again... I dont understand why it fails to work after i have gotten it fixed over and over again...
I even made a backup of my efs folder when the mobile network is working (on the old rom.. Revolution HD)... When i restore it on newer roms, the IMEI and everything comes back.. however, it wont let me access the network (radio off?)
WTF can i do? Im desperate for help, please!!
@niko: standard is to get your actual firmware from sammobile.com & flash it with Odin … to get a stable base.
Your device serial number is probably corrupted. You can use service box to fully repair this issue. Or you can flash Ariza's patched modem. It will work but your efs folder will be permanently screwed and you will be forced to flash it every time you flash a new firmware.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
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.
i was running cyanide l for about a year when suddenly it started saying there was no sim card. i tried switching sims, same. sim works in other phones. i backed up, wiped and installed cyanide m. it recognized the sim and i had phone and 3g but no 4g and it would not allow me to access my sd card (others worked). so i backed up, wiped, and installed cm13. no sim, so i wipe and go back to cyanide m but still no sim. tried restoring backups going all the way back to last year to no avail. tried using different versions of twrp to flash all 3, same. tried flashing modem, same thing. imei and baseband show as unknown in about. would this be because efs corruption, or because its not recognizing the sim?
i cant find a efs backup. i may have one from CWMR, still searching hard drives.
does this sound like possible hardware issue? anybody have any suggestions for how to fix this?
im a little afraid of flashing a stock because i avoid knox like the plague.
replaced simcard slot with one from phone with cracked screen. same thing
used gsii_repair to mount efs and got signal (not sure why mounting it and rebooting did this). it would only get 3g, and in test menu 700mhz channel 13 used by Verizon lte was not shown in band list. figured it was a limitation of the rom (cyanide m) so backed up efs w/twrp, and odin back to vramc3 w/.pit. says no sim again. tried re flashing radio, restoring efs w/twrp. tried going back to my working backup of cyanide m, but still no sim and sgii_repair didnt fix this time. ive been messing with this for a week. any sugestions.
so it just started working again. not sure why, but i was running stock vramc3. backed up efs again, and manually copied efs folder. flashed de-knoxed/deodexed stock nd7. still working. made a backup. flashed cm13. still working. flashed open gapps. still working. installed Pandora and fell asleep listening to music. woke up to no service. reboot, no sim/baseband/imei again. compaired efs to backup, seems the same. overwrote efs with backup, no sim. there is no nv_data.bin in any of the efs saves/backups... checked 2 other i605 note 2's both on mj9, there efs has no nv_data.bin, but they work flawlessly. can anyone conferm if imei data is stored in some other way/place on 4.3+
maybe the nand if failing?
no sim when i went to sleep, working when i woke up... phone + 1x only. maybe the radio is bad... never had issues like this on any phone i worked on. think im going to buy a new phone as the gn2 community is dead and im getting nowhere without help. is there a test/diagnostic app.
through it in my pocket, it stops working... through it in the refrigerator, it starts working... i think its toast
A "script kiddie" here, tried to customize my phone for the first time, accidentally installed a wrong version ROM, the phone went into a bootloop and so i decided to completely wipe the internal storage (that was so very dumb...)
Now after a day of struggle i managed to install everything i wanted - TWRP and a custom MIUI, but ever since that memory wipe i lost my signal. After searching around some, it seems that my IMEIs got lost (disconnected, corrupted, i dont know how to call it) and the phone can not detect either of my SIM cards. WiFi works fine. I do not have "nvram" folder or file anywhere on my phone.
Nocturnal22 said:
A "script kiddie" here, tried to customize my phone for the first time, accidentally installed a wrong version ROM, the phone went into a bootloop and so i decided to completely wipe the internal storage (that was so very dumb...)
Now after a day of struggle i managed to install everything i wanted - TWRP and a custom MIUI, but ever since that memory wipe i lost my signal. After searching around some, it seems that my IMEIs got lost (disconnected, corrupted, i dont know how to call it) and the phone can not detect either of my SIM cards. WiFi works fine. I do not have "nvram" folder or file anywhere on my phone.
Click to expand...
Click to collapse
Look in Q&A section/IMEI NVRAM Restore Tools post. That is allmost the only way to restore lost IMEI.
Good luck.
stympy said:
Look in Q&A section/IMEI NVRAM Restore Tools post. That is allmost the only way to restore lost IMEI.
Good luck.
Click to expand...
Click to collapse
Im getting lost in that wall of text. Cant i just replace my damaged "nvram" with someone elses working one? Switching IMEI to mine afterwards of course.
Also it says i dont have a baseband, should i be fixing that first?
Nocturnal22 said:
Im getting lost in that wall of text. Cant i just replace my damaged "nvram" with someone elses working one? Switching IMEI to mine afterwards of course.
Also it says i dont have a baseband, should i be fixing that first?
Click to expand...
Click to collapse
At the end of that tutorial look for a small word tutorial zipped. Read that one first.
Turns out all i had to do was mess around with firmware re-flashing until i got a working baseband and then use Chamelephon to set up IMEIs.
Everything was that easy.
Nocturnal22 said:
Turns out all i had to do was mess around with firmware re-flashing until i got a working baseband and then use Chamelephon to set up IMEIs.
Everything was that easy.
Click to expand...
Click to collapse
Try this: reset the phone to factory defaults. Then try to see if IMEI'S are still there.
Tell me what firmware worked. It is a valuable information for others.
Thanks.
stympy said:
Try this: reset the phone to factory defaults. Then try to see if IMEI'S are still there.
Tell me what firmware worked. It is a valuable information for others.
Thanks.
Click to expand...
Click to collapse
I wiped all the factory settings and the ROMs i used to mess around were: P780_S124_ROW_140403, flashed through flashtool, supposed to be the "official" ROM (the one i got the stable baseband from) and MIUISU_4.4.2v_P780_7.2.24_ROW (the one im using currently). All the IMEIs got restored through Chamalephon as soon as i got a working baseband and i can send/accept calls and SMS with no problem. However there is a bug with constantly changing MAC now.
Nocturnal22 said:
I wiped all the factory settings and the ROMs i used to mess around were: P780_S124_ROW_140403, flashed through flashtool, supposed to be the "official" ROM (the one i got the stable baseband from) and MIUISU_4.4.2v_P780_7.2.24_ROW (the one im using currently). All the IMEIs got restored through Chamalephon as soon as i got a working baseband and i can send/accept calls and SMS with no problem. However there is a bug with constantly changing MAC now.
Click to expand...
Click to collapse
Hi. Did you installed MIUISU over s124 ?
If you did, you must update to s228 Kitkat.
S124 is jellybean. You will get errors, if you install kitkat over jellybean.
stympy said:
Hi. Did you installed MIUISU over s124 ?
If you did, you must update to s228 Kitkat.
S124 is jellybean. You will get errors, if you install kitkat over jellybean.
Click to expand...
Click to collapse
No, i installed s124 backed up the baseband and nvram files through MTK. Then i flashed the system, installed MIUI and recovered my baseband. The unstable MAC error started in s124 already.
Nocturnal22 said:
No, i installed s124 backed up the baseband and nvram files through MTK. Then i flashed the system, installed MIUI and recovered my baseband. The unstable MAC error started in s124 already.
Click to expand...
Click to collapse
Ok. I understand.