I have had nothing but pain and suffering since deciding to install CM 10.2 last night. I installed the latest stable version of CM 10.2.2 as well as the google apps pack and after several wipes (system, cache, data), it finally worked. The issue that I am not having is that it wont connect to the Verizon network.
I think the issue may be that in Mobile Network Settings>CDMA Subscription it is set to NV, and won't let me switch to RUIM/SIM. Another clue is that in the About Phone section, Baseband version is UNKNOWN. Any ideas?
EDIT: Ok, I updated to the latest CM version via the CM update process on the phone. looks like i am now on CM11 and i have network connectivity, though it is 1 bar of 3G. And now the google play store keeps throwing errors so i have to uninstall it.
I thought CM was a polished ROM that I could just install and go. I am now considering going with something else since I still cant get it working right.
killerroomba said:
I have had nothing but pain and suffering since deciding to install CM 10.2 last night. I installed the latest stable version of CM 10.2.2 as well as the google apps pack and after several wipes (system, cache, data), it finally worked. The issue that I am not having is that it wont connect to the Verizon network.
I think the issue may be that in Mobile Network Settings>CDMA Subscription it is set to NV, and won't let me switch to RUIM/SIM. Another clue is that in the About Phone section, Baseband version is UNKNOWN. Any ideas?
EDIT: Ok, I updated to the latest CM version via the CM update process on the phone. looks like i am now on CM11 and i have network connectivity, though it is 1 bar of 3G. And now the google play store keeps throwing errors so i have to uninstall it.
I thought CM was a polished ROM that I could just install and go. I am now considering going with something else since I still cant get it working right.
Click to expand...
Click to collapse
You definitely want to be using CM 11! 10.2 is ancient at this point.
As for your problems. First, Sense based ROMs apparently show more bars for the same signal strength. To know if it is actually worse, you need to compare the numeric (db) signal strength. Second, did you also flash a kk gapps package?
I would recommend downloading the latest gapps-kk-* from http://goo.im/gapps and then in recovery do:
* factory reset
* format /system
* install cm 11 version of your choice (latest nightly or M8)
* install gapps
And see if that makes your life a little better.
Thanks for taking the time to respond. The reason i went with 10.2 is it was the latest "stable" version on CM's website. I wasn't sure what "snapshot" meant so i didnt do any of those. Then i eventually did download and flash the kk gapps but was still having issues.
I am following your steps above to start fresh again, though I was still having issue with the radio before though, so we will see if this helps.
killerroomba said:
Thanks for taking the time to respond. The reason i went with 10.2 is it was the latest "stable" version on CM's website. I wasn't sure what "snapshot" meant so i didnt do any of those. Then i eventually did download and flash the kk gapps but was still having issues.
I am following your steps above to start fresh again, though I was still having issue with the radio before though, so we will see if this helps.
Click to expand...
Click to collapse
Well, everything seemed to install ok and phone booted fine but I have no mobile network. I do have data if i monkey around with the Preferred Network Type setting, but regardless, when i try to make a phone call, it says there is no mobile network. does anyone have the recommended settings for verizon?
Related
Hello,
I'm new here and i have a problem with my wifi.
I'm running Cyanogenmod 7.1 and i never had problems with original rom.
The problem is that it makes a connection and keeps it when idling, but then when
i need to use it the connection falls away and doesn't reconnect automatically.
When i go to the wifi settings it does automatically tries to reconnect.
I found a fix here: http://forum.xda-developers.com/showthread.php?t=1177650
and i think that one should work. I tried to install the zip but it uses an older script version. I also tried to put the files on the cyanogenmod rom and flash it all again but i also get an error.
Is there any option to get it to the newer script version so I don't get errors anymore?
Erwin
CM7.1 is old now. flash a newer version (the nightlies)
here:
Captivate: http://download.cyanogenmod.com/?type=nightly&device=captivatemtd
Fascinate: http://download.cyanogenmod.com/?type=nightly&device=fascinatemtd
Vibrant: http://download.cyanogenmod.com/?type=nightly&device=vibrantmtd
i9000: http://download.cyanogenmod.com/?type=nightly&device=galaxysmtd
download the newest file
I always thought that the nightly builds are like the experimental builds with possibly some glitches or something.
When i flash the newest version, do i lose all the settings and stuff or will it just update some files?
Erwin
000Erwin000 said:
I always thought that the nightly builds are like the experimental builds with possibly some glitches or something.
When i flash the newest version, do i lose all the settings and stuff or will it just update some files?
Erwin
Click to expand...
Click to collapse
They are experimental...that's what makes them better. You get all the new features in it. Nd no they shouldnt wipe any of your data. Always make a backup though !!
They usually don't have any glitches...usually just new feature.
You should start looking at I cs roms though...they now pretty much all work flawlessly.
Everyone,
I have been running the latest CM10 nightlies for a couple days and love it on my EVO. However, I am having consistent issues with the navigation. I am S-OFF running the latest firmware. I have been flashing the latest CM10 nightly, although I have also tried deck's latest version as well. When flashing, I wipe everything in sight, trying both the superwipe zip and manual wiping, but everytime I install CM10 the Google navigation crashes on me and has weird screen artifacts. I have also tried using the GPS Status app to clear my GPS data to no avail. Does anyone have any other tricks to get nav to work on CM10?
Thanks!
Brian
Well, all I can say is to make sure you have a half decent kernel, and make sure you're using the right gapps. No reason it should crash on you.
actually im in the same boat. had to use waze (not bad at all), just wish it works.
Misterblc said:
Everyone,
I have been running the latest CM10 nightlies for a couple days and love it on my EVO. However, I am having consistent issues with the navigation. I am S-OFF running the latest firmware. I have been flashing the latest CM10 nightly, although I have also tried deck's latest version as well. When flashing, I wipe everything in sight, trying both the superwipe zip and manual wiping, but everytime I install CM10 the Google navigation crashes on me and has weird screen artifacts. I have also tried using the GPS Status app to clear my GPS data to no avail. Does anyone have any other tricks to get nav to work on CM10?
Thanks!
Brian
Click to expand...
Click to collapse
I have the same issue. Eventually I was going to get around to trying a different kernel.
I am running the Kernel from the CM10 build:
3.0.53-dc2c1ebb
[email protected] #1
Mon Dec 3 21:32:25 PST 2012
As for the GAPPS I just installed the latest I could find with the ROM and then downloaded the latest Maps from the market.
Any recommendations on a good kernel to try?
This is a widespread issue for unrooted, stock users. It is documented in several forums, so it does not only affect you or other rooted users.
I am running CM10 12/05 build from IRC and used my Navigation with G maps for 2 straight hours today with no problems.
I am on the kernel it comes with. Before flashing CM10 I update prl, profile and make sure I have a GPS lock on a Sense rom. Then go into TWRP and wipe cache, dalvick, factory reset, and system a couple times each, flash CM10, I'm using the Captain's Gapps from IRC and it works fine for me.
I've never wiped the GPS data stuff or anything like that either.
YMMV though I guess
Naters
Naters,
I haven't tried using the IRC build...do you have a link / instructions on how to get that (and the GAPPS). I will try loading up MeanROM, getting a sense lock, and then switching to that build.
Thanks!
Brian
NaterTots said:
I am running CM10 12/05 build from IRC and used my Navigation with G maps for 2 straight hours today with no problems.
I am on the kernel it comes with. Before flashing CM10 I update prl, profile and make sure I have a GPS lock on a Sense rom. Then go into TWRP and wipe cache, dalvick, factory reset, and system a couple times each, flash CM10, I'm using the Captain's Gapps from IRC and it works fine for me.
I've never wiped the GPS data stuff or anything like that either.
YMMV though I guess
Naters
Click to expand...
Click to collapse
This is the link to get into the IRC channels.
Once you are in the DL link for the rom and Gapps will be at the top of the page.
http://forum.xda-developers.com/showthread.php?t=1643396
Let me know how it works for you.
Naters
Tried it, some problem unfortunately...I guess this is a YMMV type thing.
BTW, is that IRC channel a good place to get support for CM10? I was hoping to talk with the developers and try to help out with kernel logs or whatever may be useful.
Brian
NaterTots said:
This is the link to get into the IRC channels.
Once you are in the DL link for the rom and Gapps will be at the top of the page.
http://forum.xda-developers.com/showthread.php?t=1643396
Let me know how it works for you.
Naters
Click to expand...
Click to collapse
Sorry it didn't work.
No clue why it works for some and not others.
Sent from my PC36100 using xda app-developers app
Working now
I was having a lot of problems with the navigation until looked in the location access menu and selected the GPS source as "Use Internal GPS." It has been running smooth since then. :fingers-crossed: Hopes this helps.
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
Hey guys, I tried to flash the HTC One Stock rom ported to my DNA, which “bricked” my phone. I was stuck on the white HTC boot screen when I tried to boot, and was only able to go into the bootloader (CWM recovery would not boot). I have S-OFF, HBOOT, unlocked bootloader, root access. I then tried flashing the team win recovery, which worked, but also would not boot. After continuing to get frustrated, trying to run RUU (failing because my battery was below 30%), I did some more research and tried “fastboot clear cache”, then tried booting into recovery – tada! So now I was in recovery, cleared all my cache/data, flashed the CM 10.2.1 zip and the latest PA Gapps I had stored on the phone. Everything went clean and Cyanogenmod booted up.
Now, however, the Play Store will not open (connection error, “retry”) and Hangouts will not connect. Any ideas? I’ve tried clearing Google Play Services data, Hangouts data, Play Store data, rebooting, toggling airplane mode, removing and re-adding my google account. Also, I’m getting sync errors for my google account. Any help here would be appreciated.
Most of the other Google apps I’ve tried work fine and have all my data, including Maps, Gmail, Keep, Search/Now, Play Music, etc.
It may also be important to note that the phone is currently not attached to a number (I re-activated my old iPhone 4s so I can at least have a phone for the time being). I do have wifi access.
Thanks.
Try This
Everytime that happened to me it always ended up being because it was either an outdated version of GAPPS or it wasn't a minimal gapps install. What i recommend is to look up version of android you're running, google "*your android version 4.x.x* minimal gapps.zip" I always go minimal because having all of the extra play apps and google services isn't necessary and can cause issues with certain roms, plus dat battery drain is rough compared to a minimal gapps install. After this has happened and it still hasn't worked, let me know :good:
WestTexasCoder said:
Everytime that happened to me it always ended up being because it was either an outdated version of GAPPS or it wasn't a minimal gapps install. What i recommend is to look up version of android you're running, google "*your android version 4.x.x* minimal gapps.zip" I always go minimal because having all of the extra play apps and google services isn't necessary and can cause issues with certain roms, plus dat battery drain is rough compared to a minimal gapps install. After this has happened and it still hasn't worked, let me know :good:
Click to expand...
Click to collapse
I tried two different "minimalistic" gapps - one was 15mb and the other ~60mb. For the 15mb one, my keyboard didnt work and I had the same google connection issues with the other one.
The latest pa gapps on 10.2.1? Do you mean the latest 4.3 gapps or did you accidentally use the kitkat ones? If you used the kitkat ones it would definitely cause problems like that. My suggestion: just flash the latest cm11 and pa gapps. I think you'll be much happier with it anyway.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
The latest pa gapps on 10.2.1? Do you mean the latest 4.3 gapps or did you accidentally use the kitkat ones? If you used the kitkat ones it would definitely cause problems like that. My suggestion: just flash the latest cm11 and pa gapps. I think you'll be much happier with it anyway.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Hey, been a little to busy to troubleshoot this. My problems began when I flashed a snapshot build of CM11 for the DNA. There is no "Stable" release on their downloads page yet: http://download.cyanogenmod.org/?device=dlx&type=.
I did find this guy though: http://forum.xda-developers.com/showthread.php?t=2714425
Should I try flashing this? Also, I was reading that you need new radio firmware for Kit-Kat. Is this true? I tried to flash the latest radio through fastboot but it gave me an error that had something to do with an unknown device ID.
Let me know your input, thanks.
Update:
I Flashed C-Rom 6.5 (Android 4.4) and the 4.4 PA Gapps and still had the same exact issues as before:
Play Store Connection issue
Hangouts connection issue
Other google connection issues
No 800 MHz cell band connection (device said Voice was Out of Service when I put my phone number back on). 700 MHz LTE, however did work.
Can't get adb to see my device, but fastboot can.
Corrupted model id and serial number.
So with all these issues above, the corrupted model id and serial number are what I've been mainly trying to tackle. I've read about fastboot flashing the ENG HBOOT and changing the model id that way, but I cannot flash zips in fastboot because of the corrupted model id (give the model id check error and fails). I'd be completely satisfied at this point with running RUU and getting onto the stock 4.4 update that came out. However, when I run the RUU.exe, it says it can't see my device and when I try to flash the RUU hboot, radio, and recovery zips, obviously the model id check will fail. I've since factory reset and flashed CM10.2.1 back onto the phone because C-Rom 6.5 was very laggy. The phone is pretty much just a wifi device now and I have to download apps via apk's in the browswer and manually update everything.
Anyone have any ideas on getting the model id and serial number back to normal? Really starting to get tired of my cracked iPhone.
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.