yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] treefrog20012003:
No it was all on my end, working on too much at the same time. Anyway it was the build from this post and not the official build and I tried it without the gapps as well and it kept having the crash of the services. I'm going to give the official a shot and see what happens, thank goodness for backups to fall on! Thanks for the reply.
[Verizon LG G2] El Ha$on:
So I'm having an odd issue.

I've been on CM11 this entire. It's been working and completely solid so I've decided to stick to it. Today I got a replacement device. Touchscreen wasn't working. The replacement device arrived with 39A. So I rooted it using the one click method and then autorec from playstore to flash twrp. I then flashed the 26A bootstack and went about restoring my nandroid. Everything works as planned. But when I try to make a phone call I get "mobile network not available" and I can't send a text but LTE works fine.

So I downloaded a stock rooted 26a ROM. Flashed it. And tried to make a phone call and text and everything works perfectly fine. So then went about doing a clean flash of cm11 and the same issue occurred "mobile network not available.

Just doesn't make sense to me how I can have internet working just fine but yet calls and text won't go through.

Not sure what to do at this point and searching the Google leads me to flashing radios but with the bootstack I've essentially done that so I'm stuck. Anyone have any ideas?

Thanks in advance. Appreciate it!

UPDATE: (following morning)

So I fell asleep left the phone charging. When I wake up I attempt to make a call and text and its working but LTE cuts out while on call. When I hang up it doesn't come back only 1X.

So I reboot the phone and now the issue has returned " mobile network not available.

Someone please help, thanks in advance!

Sent from my LG-VS980
[Verizon LG G2] bigtourist:
try this:

settings -> mobile networks -> access point names

..then select any other APN than the one already selected, then immediately re-select the original. (ie. if you are on VZWINTERNET, switch to VZWIMS then back to VZWINTERNET)

this always fixes the problem when i cant get a data connection after a reboot.

good luck.
[Verizon LG G2] da_reeseboy:
Was the efs partition in the restore you did? Are you sure you were previously on 26, not 24 or 27?

... Just random thoughts...

You might just have to do a full restore to stock Kit Kat and get data working, then restore the nandroid.
[Verizon LG G2] El Ha$on:
So I've gotten back to it working. I had to tot back to 11A just to be able to upgrade.

Now the only issue that stands is the Google play store no connection error. I've used different gapps, edited the host file, factory reset, adjust date and time, used adaway to edit the host file and still get no connection, manually install an updated version of play services and play store, deleted data, deleted cache, removed account and readded, so I'm at a lost. Any other ideas out there?

Sent from my LG-VS980
[Verizon LG G2] El Ha$on:
Ok, so now I have even attempted to go to CM12, to see if the LP gapps would give me an error, but when i go to flash JPC cm12 3/21 build i get patching system image unconditionally and nothing happens.

My exact steps were:

flash 39A bootstack from resources thread

flash stock 39A firmware, to ensure all was working

go to flash cm12 and i get patching system image unconditionally

what can i do now?

getting this replacement device has been a complete nightmare.
[Verizon LG G2] Lawlrus:
Every ROM I flash patches the system unconditionally, you mean it freezes up after it states that or what?
[Verizon LG G2] da_reeseboy:
What do you want to be running when all is said and done? Or are you just trying out different things right now?
[Verizon LG G2] El Ha$on:
yes it freezes up or maybe I am acting to impatient but how long do it take for that to pass?
[Verizon LG G2] Lawlrus:
Whatever time it takes for a ROM to flash, its just a very generic flash animation.

I'd say let it sit for ten minutes, if it takes log than that it might be an issue. I'm assuming you tried redownloading?

I've only ever had twrp **** out on me once of twice, it doesn't happen often at all, but it can
[Verizon LG G2] El Ha$on:
I was just attempting to restore a nandroid from my original device to the replacement hoping that it would just go smoothly, but that has not been the case at all.

so right now I am just trying to get to a complete working build of either cm11 or cm12.

I've tot back several times already and no matter whether i clean flash or restore nandroid i cant get gapps to work correctly, currently have no access to the play store, stuck with no connection.

---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------

alright ill give it another shot to see if gapps will finally work, the only thing not working on JPC cm12 build is tap to pay....correct?
[Verizon LG G2] Lawlrus:
I think so? Its been so long since I've been on jpc's build I can't recall but I think it's borked.

Make sure you're rebooting out of recovery and back in after flashing the bootstack.
[Verizon LG G2] El Ha$on:
thanks!

how does it compare to the nightly builds of official cm12.1 that is now based off 39A?
[Verizon LG G2] Lawlrus:
Night lies are running on the full caf kernel, this kernel if I'm not mistaken is still caf patched.

Its also now fully based on 4.4 source like this ROMs kernel is. And is the same kernel most other ROMs are using.

Which is better? Both run well, best to try both incarnations
[Verizon LG G2] da_reeseboy:
If you're flashing cm12 (not cm12.1) be sure you're using a gapps for lp 5.0.x not one for lp 5.1.x.
[Verizon LG G2] El Ha$on:
All is well again. Thank you so much for all the help

Sent from my LG-VS980
[Verizon LG G2] joedajoester:
Anyone know a way to get the "gestures" menu like motorola devices have on cm12? It includes ambient display and wake to pulse notifications. Thanks
[Verizon LG G2] ddzado:
Anyone else lose LTE on the latest?
[Verizon LG G2] da_reeseboy:
I'm guessing you're referring to something other than the apn bug that it's had for a couple months? Playing with apns doesn't fix it right?

I'm not on it, but before I build a new rom based on the latest I wanted to ask. :)
[Verizon LG G2] ddzado:
I have had issues before. I went back to stock to fix them.
[Verizon LG G2] da_reeseboy:
Try going to settings > mobile network > access point names and then switch to another one, then switch back to the one it was on.
[Verizon LG G2] ddzado:
Unfortunately I've done a good share of troubleshooting before I announced it was gone. APN switching, reset to default, remove sim card, switch preferred network. I'll have to probably wait for the next build or go to stock again.
[Verizon LG G2] da_reeseboy:
Sorry to hear. Thanks for replying tho, you saved me several hours of building a rom that wouldn't work.
[Verizon LG G2] ddzado:
Well I wouldn't say don't build it. I'm the only one that is reporting an LTE problem of this magnitude. I'd love to be building the code on my own. I could probably find and fix this bug.
[Verizon LG G2] [] AL []:
Hi there JC!

First off: thank you very much for all the work and support you've done and provided here for the VS980 - much, much appreciated.

Well, I very sorry to wake up the dead by quoting such an old post (KitKat break anyone?), but I thought that since I'm here to thank you, I would use the occasion to ask (although I think I know the answer -especially after seeing that you've just got a Moto X...). Anyway...: have you finally ever got your VS980 CM11 work environment up and running again? I ask because I've just order my G2 a few hours ago (thanks to this thread and CM11 KK-based) and I want to run CM11 on it and I've noticed that your M12 build links are down (was there an issue with it?). Anyhow, the last nightly is newer anyway, so no biggie there really! But, I'm wondering if you've ever thought of following what CM did and release a final M13 (actually labeled differently, but you know what I'm referring to here I'm sure). That was almost 6 months after the M12. There weren't many commits in the mean time, but I do believe that some important security fixes (heartbleed) were implemented -that unless I'm mistaken and they were actually fixes that people unofficially brought over from CM12...

Anyway, I know - I know: I should really stop and start learning how to build from sources myself (it's about time!!). But I thought I'd ask because I'm a die hard fan of CM11 and it might be all my G2 will ever run on...

Thanks again for everything and long live CM11! :p
[Verizon LG G2] Zimeron:
Flash official CM12, it works fine.
[Verizon LG G2] [] AL []:
Thanks.

But for me, newer doesn't always equal better

I don't want to run CM12 or M (for now anyway) and I've chosen this phone because of the first half of this thread...

edit:

I would really like opinions from (maybe past) CM11 users here:

running an official C11-M9 (JB-based?) on a LS980 would be much less stable than [MENTION=2845033]jacpot[/MENTION]clavin"s last CM11 KK-based (~M12) nightly on a VS980?

I'be just received the Sprint and was expecting a Verizon...

The above dilemma represents 4 months of CM11 commits and from this thread's comments, a much more stable than JB-based...

So hard to quantify "much more stable", but is it really a deal breaker here? i.e: worth the hassle of returning this phone and re-ordering a VS980?

Thanks for any input in advance.
[Verizon LG G2] Zimeron:
Uh, you're asking for a new cm11 build? Why not just get the cm12 build which has all the fixes and more. A lot has changed since this thread started and official cm12 is just as good as JPCs, but it's updated with fixes, so most would argue better. This thread and it's roms are for the Verizon variant, they are separate for a reason from the sprint ones. I would suggest the official cm12 for the ls980, but since you don't care for those, I'd find another rom designed for your phone.
[Verizon LG G2] El Ha$on:
I'm going to +1 [MENTION=3140732]Zimeron[/MENTION] here. Official cm12.1 is solid. At first I was hesitant towards making the plunge because JC cm11 was so dependable. I ran that last M build he built for 10 months with no issues what so ever. When I got a replacement device I immediately wanted to just go that route but after reading thru the forums I found out that official cm bad updated their kernel base using the most recent so I figured it would be stable enough for daily driver status and I was correct on my assumption.

No random reboots, no bugs nothing that hinders me from using the device day to day, and I'm on a nightly (there hasn't been an snapshot build for us yet) so you would think there might be a potential issue but none.

I would recommend official cm, its been working great for me. Just be sure to flash Rashed bootstacks those are the recommended ones for these builds if you decide to take a plunge.

Sorry for completely sidetracking this thread any further questions should probably be taken to the Q&A thread of official cm12.1.
[Verizon LG G2] jsight:
On the other hand, I've been thinking about trying to find a good, stable older ROM. I've used multiple ROMs based on the latest and all constantly lose LTE for me. I can't blame someone for wanting an older one of they hit these issues and the older ROM didn't have them.
[Verizon LG G2] Zimeron:
If you truly do all that, you have a very unique and odd use case. With that being said, if you're capable of doing all that, then you're capable of building the rom yourself and should get used to doing that, since CM11 is now two versions behind, soon to be three.
[Verizon LG G2] xlxfoxxlx:
Can these commands be done in terminal from the phone
[Verizon LG G2] koftheworld:
worked perfectly. i'm currently restoring apps now. thank you so much! if i can make a suggestion, maybe extra bold the run as root step and explain where the files are pushed (or should be moved to). other than that, the guide was amazing.

THANK YOU THANK YOU THANK YOU.

now i'll let you know how it's runs... :eek:)
[Verizon LG G2] JackpotClavin:
Wow that was really fast! Thanks for installing :) hope you enjoy
[Verizon LG G2] koftheworld:
i know i will. even though stock kk was great, i really missed cm11. no matter what people say re: xposed, it just never makes the device feel the same.

thanks again man.
[Verizon LG G2] xlxfoxxlx:
To answer myself yes it can be done threw terminal just gotta dl some gapps and back up my stock and it's off to cm11
[Verizon LG G2] Enter The Nexus:
Is this a regular CM 11 build we could just flash over a ROM or do we have to be on 24A to do this?
[Verizon LG G2] heffzilla:
Does it matter where we push the files?

*EDIT: got it
[Verizon LG G2] datsyuk:
Out of curiosity does this build have broken 3g like official CM builds? CM 11 is pretty buggy and annoying no matter what build I run would love to run the official binaries and 4.4 kernel for once. Seems like some work although not too challenging but want to see if it'll be worth it haha. Also once all the steps are done can we flash any other ROMs (official CM, PA, etc) without issues?
[Verizon LG G2] jrgilbert79:
Very awesome Jackpot. I was hoping you would write a guide for the LG stock as well. I spent 4 years on aosp the OG droid then Galaxy Nexus so I dig the LG UI probably because I'm just sick of the vanilla look. No one seems to be able to build an LG kernel that boots with the 12b boot images. They are using the ls980 source should they be using the t mobile source?

Also does it have to be cm cause people are raving about c-rom kinda wanted to try it out especially if this squashes bugs due to the old radios.
[Verizon LG G2] xdabbeb:
If you follow the guide through step 8 you'll have 24a with a working recovery. I would think the boot.img in step 7 is pretty close to stock anyway, but if not I can give you (or whoever) the one I built.

Excellent write-up [MENTION=3727492]JackpotClavin[/MENTION]

EDIT: Oops...apparently flashing the recovery is step 8, but you get the idea. The boot/recovery flashing order doesn't matter.
[Verizon LG G2] xlxfoxxlx:
For those wanting to use terminal from the phone to do this easiest way is put the files of the root on the internal SD and type this into terminal,

cd ~/data/media/0

Then type "su" and give superuser permission and then follow the commands in the OP.

This version of cm seems to be running amazing.. Now just gotta wait for the other ROMs to get updated as I've never been a big CM fan
[Verizon LG G2] jrgilbert79:
[MENTION=2941286]xdabbeb[/MENTION] and JC one question for clarification. Will the kernel from the 24A OTA work with the old boot images. I was under the assumption that needed a modified kernel to use the loki'ed boot images.
[Verizon LG G2] xdabbeb:
Nope...it won't work with the older aboot (all KK G2 kernels are this way). The older 12b aboot (which is the last one exploitable by loki on VS980) is looking for a separate device tree and a few other things. This is what JC had found in the past. That said, all of the variants are basically sharing the same kernel base and even though the source DL may say that it's for LS980, D801, etc it contains everything necessary for most variants. I just built off LS980 b/c it was newer and I didn't already have it set up.
[Verizon LG G2] Nom Prophet:
Thanks a lot Clavin! Thumbs up.

This was a lot easier than it originally appeared to a beginner like me. Just some tips for others who are hesitant:

Make sure the 3 downloaded files are simply on the root of your sd card. There's an md5sum app I used to check to make sure the 3 were verified afterwards.

Now this is too easy:

After opening your command window in your adb folder

1) Type

adb devices

just to make sure your phone is recognized and active.

2) Type

adb shell

3)Type

su

Now you're ready to run commands "as root" like he specifies (I had no clue what this meant and had to search for it)

4)Type

dd if=aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot

Enter

5) Type

dd if=boot.emmc.win of=/dev/block/platform/msm_sdcc.1/by-name/boot

Enter

6) Type

dd if=recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Enter

Done.

I booted into TWRP using ROM Toolbox with no problem.

Gonna give this CM11 a shot because I desperately need tether.
[Verizon LG G2] krazie1:
If we didn't want to have a custom recovery with the 12b aboot can we just flash the 11a tot file and go back to complete stock?
[Verizon LG G2] shanetrain:
I keep getting a "cannot open for read: No such file or directory" in ADB.

Followed the steps to a tee.
[Verizon LG G2] heffzilla:
You have to cd to where you pushed the files first

I made the same mistake, it's late lol
[Verizon LG G2] shanetrain:
Thanks man, LOL!

I feel like a bonehead right now.

Worked perfect!

We have KK OTA with a working custom recovery!
[Verizon LG G2] beezysg3:
im in there like swimwear!!! thanks guys

so what roms etc can be flashed now?
[Verizon LG G2] koftheworld:
Anyone else having a Bluetooth issue? Mine seems to come on after a reboot but shuts off after a minute. After that if you try to turn it on again it just says "turning on" perpetually.
[Verizon LG G2] Coolsaber57:
I think that that just means it has the Kitkat drivers. The ROM itself is based on AOSP, and not the stock software.
[Verizon LG G2] simon_lefisch:
Installed the third April 5th build last night. All seems great so far. Haven't tried Bluetooth yet as I don't use BT really. Otherwise, great build. Was wondering if anyone has tried a different kernel yet? Are the current AOSP compatible with this build?
[Verizon LG G2] :
Can't seem to get MMS working here either. Everything else seems very stable.
[Verizon LG G2] Apex i ITR:
My biggest gripe with all the CM based roms is the reception. Seems like I go roaming or loose reception completely. I also drop calls alot without warning. Can anyone confirm that this is resolved with this update? If it isn't I'll just stay put until the official update.
[Verizon LG G2] tacosrdelicioso:
Well I don't have any issues
[Verizon LG G2] :
I have had no issues. My biggest issue with the regular CM11 was the proximity sensor, but this one based on 4.4 fixes that.
[Verizon LG G2] simon_lefisch:
Most to all AOSP ROMs have a weaker signal....at least that's been my experience for many years.
[Verizon LG G2] dr87:
Do you mind double checking if this is the right commit to revert? Reverting this brings back a .c file deleted by a later merge/commit, and since its not longer being built in the makefile I'm wondering if this is the commit you were intending to revert before I rebuild the rom and go further :good:
[Verizon LG G2] eleazar123:
I'm a complete noob with this kernel/CAF stuff, so i apologize in advance if this type of question has already been asked.

Can I just flash this new 2.0 kernel from savoca with a CAF rom (ie. CM) and avoid having to go through all of this to get an AOSP rom without SODs or random reboots? http://xdaforums.com/showthread.php?t=2572992
[Verizon LG G2] steveo17:
Doubt it. It's based on the old kernel still
[Verizon LG G2] JackpotClavin:
Yeah that's the right one. Maybe the base of the ROM you're using is different from CM? The history of that file in the CM branch is here:

https://github.com/CyanogenMod/andr...2/vidc/venc/src/video_encoder_device_v4l2.cpp

it's reverting the patch which is 2nd from the top, which is cf8408186605323a6797e5f431192ab434e79fff

It's the normal hardware/qcom/media, not media-caf
[Verizon LG G2] heffzilla:
AOSP ROMs display signal differently than stock. Stock ROMs pad the signal stats to make it look better. If you look at your signal dBm under settings, it's "usually" the same. There have been a few rare occasions where it was worse, but not many.
[Verizon LG G2] dr87:
Whoops you are right, I did something stupid and cloned the default branch forgetting it was 10.2, then tried to revert. :good:
[Verizon LG G2] simon_lefisch:
I have used the dBm setting and for me AOSP has always been a little weaker.
[Verizon LG G2] tacosrdelicioso:
Can anyone confirm my weird stupid Pandora streaming issue on headphones?
[Verizon LG G2] jschramm:
yes, I am also having headphone issues with Pandora.
[Verizon LG G2] RoboJoe:
Can someone tell me if both the front and rear cameras are super dark in Google hangouts during a video chat for anyone else?
[Verizon LG G2] C.Hatfield:
I have already done the 24A OTA yet I havent done this recovery hack bc I wanted to KNOW for certain that it can be done w/o any issues before I jumped into it - I havent done any tweaking on my stock 24A - BUT - I was about to mess around w/ Xposed .... does that eff with JC's hack ? Also, are there any OTHER things that may conflict w/ proper completion of hack ?
[Verizon LG G2] HueyT:
You have to push laf.bin file to prevent broken "download mode" (see step 6B in the first post of this thread). Otherwise, it's nice to have TWRP 2.7.0.0 to back stuff up and flash up coming roms or tweaks.
[Verizon LG G2] C.Hatfield:
Everything is totally cool if following directions from Step 6 in OP, correct ? I kept up reading this thread for several days but I stopped bc I thought I was just gonna wait .... I just couldn't help myself :cool:

..... any idea if Xposed mods (or ANY-THING else) will cause conflicts with this being done correctly ? I am no novice but I do not want any unneccesary issues bc I was careless or I simply wasn't thorough enough ....
[Verizon LG G2] tacosrdelicioso:
Um I don't think so. But honestly this discussion is getting very tired
[Verizon LG G2] cheami:
Nothing will affect the step by step. The directions are very self explanatory, very hard to messed up.
[Verizon LG G2] simon_lefisch:
I hadn't notice the rear camera, but def the front camera is darker. Happens on the stock OTA leak as well.
[Verizon LG G2] 55Pegasus:
I just installed Pandora on my phone and headphones work. I do have Viper installed.
[Verizon LG G2] jeston:
Just went through the whole process from originally running cm11 nightlies. Everything went super smooth and now I'm running this much more stable and better cm11 :D

Thanks JackpotClavin, xdabbeb, and everyone else who worked on making this possible!
[Verizon LG G2] RoboJoe:
I did some light Googling and it seems that it's a problem with the LG G2 running (official) KK with Hangouts only. I know I didn't have this problem when I was running KK before our leak, so it must be something introduced from by LG. Hopefully Google will tweak Hangouts, because Zeus only knows how long it would take coming from LG. (Then again, maybe the official KK from Verizon will have a fix. Hey, I'm an optimist.)

I actually use Hangouts Video chat a fair amount, so if it wasn't such a pain in the caboose to roll all the way back, I'd consider doing it. Ah well.
[Verizon LG G2] heymoe:
So, I seem to be running into the same issue where I've dd the 12B laf.bin file and when I try to get into Download Mode my G2 gets to the screen with that says Download mode with the blue dots but never gets to the next screen.

I backed up my Stock 24A laf partition using this command before I dd the 12B laf.bin file.

dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=24a_laf.bin

The resulting size of 24a_laf.bin was: 33,554,432 with an MD5 of: df4ea6516bd8a93c7b6a270adbfdec44

The thing I find odd is that the 12B laf.bin file we're trying to flash has the size of: 15,204,352 and MD5 of: 176266cf5b0f156980955e5603d3f232

The 12B laf.bin file is about half that of the 24A laf backup I made which means that it's not overwriting all of the actual laf partition on the phone.

Doesn't this mean that there is a lot of leftover data from the 24A stock laf sitting in the laf partition that was not overwritten by the 12B laf.bin file when running this command.

dd if=/sdard/laf.bin of=/dev/block/platform/msm_sdcc.1/by-name/laf

Could this be causing the problem with getting into Download Mode?

I did try and zero out the laf partition using this command:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf

and then dd the 12B laf.bin file and that didn't seem to help.
[Verizon LG G2] ppeklak:
does this work with ART?

edit: nm read the thread :D