Is their a cyanogenmod version that works for non developers editions of the verizon note. I just got my note 3 and without cyanogenmod it would stink.. has the bootloader been unlocked ?
No, still can't flash custom kernels
mjh68 said:
No, still can't flash custom kernels
Click to expand...
Click to collapse
there are may subjects and threads on this matter. I realized that not everyone understands everything, but if you know enough to register on this site, you must know how to use the search function.
to sum up:
search before posting
for the time being s4 and above on verizon wont be able to run aosp roms*
*besides developers edition. (if you have to ask, you don't have one)
dogenut said:
Is their a cyanogenmod version that works for non developers editions of the verizon note. I just got my note 3 and without cyanogenmod it would stink.. has the bootloader been unlocked ?
Click to expand...
Click to collapse
i did the same thing back in January and i'm kicking myself in the ass for not doing a lot more research first. samsung software has got to be the worst, thats why this phone has 3 gb ram. use towel root and at least get root access to shut half the ****ty software off. the custom roms for this phone are just rework versions of bloatwiz.
That blows... has anyone been working on it ?
dogenut said:
That blows... has anyone been working on it ?
Click to expand...
Click to collapse
The likelihood that our bootloader will even be unlocked or that any real development will go into kexec allowing us to flash custom kernels is probably close to 0%, meaning there will not be a cyanogenmod for retail N3.
However, if you are looking for a closer to AOSP rom check out Eclipse Rom. The dev has put much coding into the rom to make it feel like AOSP, it's not without its faults but what rom is perfect?
Also the devs for Alliance Rom have said they will be releasing an AOSP version in the future and many people are looking forward to that.
With practically any rom you will find yourself uninstalling a lot of bloatware unless you are one of the few who bought a Samsung device to use the proprietary software.
Either way, have fun.
Related
Hi
I just wanted to know where the new galaxy s 2 will likely be able to accept custom roms if a developer develops one for it.
Is this going to be possible folks?
thanks
I'd have presumed so. The bootloader is unlocked so I guess it's just a case of the right developers getting their own hands on the phone so they can work through the kinks.
Bootloader is not locked and kernel is unsigned so we can flash custom roms....just check the sgs2 dev section...once the devs port roms to sgs2 we can easily flash without difficulty
ranjb said:
Hi
I just wanted to know where the new galaxy s 2 will likely be able to accept custom roms if a developer develops one for it.
Is this going to be possible folks?
thanks
Click to expand...
Click to collapse
There is no need to talk about rooting & custom roms this soon.
It has not even launched in most of the major markets.
Bootloader is unlocked same as with SGS,no problem in that regard but still enjoy the stock version till some custom roms come
android_master said:
There is no need to talk about rooting & custom roms this soon.
It has not even launched in most of the major markets.
Click to expand...
Click to collapse
I would say the UK is a pretty big market...
Bring on the custom ROMs!
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723
Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??
khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol
khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.
My S4 got fried. When I got it fixed, I found that it was upgraded to a newer build which has Knox. Therefore, I cannot use custom recovery or flash AOSP ROMs anymore. I cant stand Touchwiz.
I was thinking of selling my S4 and going for an S5 but it appears that no AOSP ROMs have not been released yet and development has ceased because of issues with GPS and Camera.The GPE version which can help with ROM development also has not been released yet and its release appears unlikely as time goes by. This phone was released back in April and I dont know if I can expect a stable AOSP ROM to be ever released - As the phone gets older, it gets more unlikely that someone will have the interest to fix these issues. Anyone share these concerns - any related thoughts - Is the S5 worth buying?
Development has not stalled, stop creating drama. This is a great phone all around so it was worth getting before root even occurred. Get the M8 if you can't be bothered...
phonedawg said:
My S4 got fried. When I got it fixed, I found that it was upgraded to a newer build which has Knox. Therefore, I cannot use custom recovery or flash AOSP ROMs anymore. I cant stand Touchwiz.
I was thinking of selling my S4 and going for an S5 but it appears that no AOSP ROMs have not been released yet and development has ceased because of issues with GPS and Camera.The GPE version which can help with ROM development also has not been released yet and its release appears unlikely as time goes by. This phone was released back in April and I dont know if I can expect a stable AOSP ROM to be ever released - As the phone gets older, it gets more unlikely that someone will have the interest to fix these issues. Anyone share these concerns - any related thoughts - Is the S5 worth buying?
Click to expand...
Click to collapse
GPS and Camera issues? No. And the development hasn't stalled, but is definitely more moderated than older phones. And you will not see ANY AOSP roms until the bootloader is unlocked(likely never). You have to use safestrap so you will only have Touchwiz roms.
phonedawg said:
My S4 got fried. When I got it fixed, I found that it was upgraded to a newer build which has Knox. Therefore, I cannot use custom recovery or flash AOSP ROMs anymore. I cant stand Touchwiz.
Click to expand...
Click to collapse
To add to what was said above, Knox is not the problem. The locked bootloader put in place on the Verizon and At&T variants is the problem. The T-Mobile and Sprint Galaxy S5s also have Knox, but their bootloaders are unlocked. So users of those models are free to flash whatever ROMs are available for their variants.
And the root exploit has been patched. So maybe not the best phone if you can't stand TW/absolutely can't stand not running a custom ROM unless you can get one that has not had the patch installed.
Sent from my Nexus 7 using XDA Free mobile app
FWIW I've been running custom ROM's since my old original Moto Droid and felt the same way. I finally took the plunge yesterday and paid full retail for the S5 (unlimited data plan)... I've got root and SuperSU with knox dis-abled, so I can freeze/delete anything I want and Foxfi lets me broadcast wifi tether. This phone is pretty well fantastic as it is. Even though some features are nice I ain't so sure I am even gonna mess with it. The phone is THAT good IMO....
phonedawg said:
My S4 got fried. When I got it fixed, I found that it was upgraded to a newer build which has Knox. Therefore, I cannot use custom recovery or flash AOSP ROMs anymore. I cant stand Touchwiz.
I was thinking of selling my S4 and going for an S5 but it appears that no AOSP ROMs have not been released yet and development has ceased because of issues with GPS and Camera.The GPE version which can help with ROM development also has not been released yet and its release appears unlikely as time goes by. This phone was released back in April and I dont know if I can expect a stable AOSP ROM to be ever released - As the phone gets older, it gets more unlikely that someone will have the interest to fix these issues. Anyone share these concerns - any related thoughts - Is the S5 worth buying?
Click to expand...
Click to collapse
As for AOSP ROMs. I have never had success with any AOSP ROM on my Moto Maxx HD, or my Sammy S4 Developer Edition and I tried every AOSP ROM available for them. In every case battery life was bad, or camera wasn't right or did not work, or GPS would not work or hold the sync, or they got real laggy after a few days or data would come and go. It didn't make a difference which ROM, there was always something that wasn't quite right. In the case of my S4, it always ran better on a TW based ROM.
I have an S5 Developer Edition now. Based on my previous experience with AOSP ROMs, I'm not holding my breath for a AOSP ROM that performs any better on my S5 than they did on my S4 because I don't think they'll ever get there.
There is root and SafeStrap for the S5 retail version now, as you already know. From most accounts the S5 performs very nicely with the TW based ROMs available...and so does my S5 Dev Edition. I'm not sure what it is about TW that you don't like but the S5 is a great phone whether you flash a custom ROM or not.
ezas said:
And the root exploit has been patched. So maybe not the best phone if you can't stand TW/absolutely can't stand not running a custom ROM unless you can get one that has not had the patch installed.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Verification on this statement? I gotta swap mine out for a warranty issue, hoping this isn't true. I haven't found anything else to confirm this....
Sent from my SM-G900V using XDA Free mobile app
prenedo said:
Verification on this statement? I gotta swap mine out for a warranty issue, hoping this isn't true. I haven't found anything else to confirm this....
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
The exploit has been patched, but the S5 has not received an update. So there is a chance the warranty replacement you receive may be ok, as long as the kernel is before June 3.
Sent from the Shark Tank using XDA Premium 4 mobile app
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
brolic925t said:
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Source ?
Sent from my LG-D852 using XDA Free mobile app
shahkam said:
Source ?
Sent from my LG-D852 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/
I'm OK now, I'm happy to have waited this long for an AOSP ROM.
I can wait longer if it becomes a L ROM for our G3!!
Great news !
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
It is usually very hard to get new android versions ported to a device where there is no official rom of the same version for it - you basically are going in blind trying to get all the hardware to work.
If we are lucky we might see one or two builds before LG release theirs (which is now less than 2 months away!) but I would expect them to be buggy with some hardware not working - so far we don't even have a fully working Kitkat AOSP build for our device.
manups4e said:
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
Click to expand...
Click to collapse
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Deeemm79 said:
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Click to expand...
Click to collapse
if someone would like to help here is last_kmsg at the very end you'll find the kernel panic about modem
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Oooh. I so happy. ????
jayzhoukj said:
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Click to expand...
Click to collapse
this is true although (and i may well be wrong) i would presume this would only apply if you take the update from OEM and not custom rom .... if we take a flashable custom rom i would assume that this lockdown is completely irrelevant and fairly risk free providing the devs can get all the hardware side of things up and running
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
jayzhoukj said:
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
that all depends what you want to be able to do on your device ..... without root you cannot use xposed (although until made to run on ART it wont work with lollipop onwards ) ... you need root to delete / modify any / all system apps and other tweaks under the hood ..... there are many things you could need root for
jayzhoukj said:
not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
LeoRex said:
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
Click to expand...
Click to collapse
infact since 1 month i'm trying to port lollypop and i'm blocked by kernel panic at boot due to modem resetting
My concern is for our d850 development .... It will pick up im guessing
2SHAYNEZ
OEM Unlock feature in Lollipop dev options
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
so excited in looking forward to your effort - friends....
hwong96 said:
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
Click to expand...
Click to collapse
OEM unlock meaning ?
Since we have a mostly stable root... why are there only 2 custom roms??
After being locked out of my s6, I was so excited this phone had root... just don't understand
Anthrax79 said:
Since we have a mostly stable root... why are there only 2 custom roms??
After being locked out of my s6, I was so excited this phone had root... just don't understand
Click to expand...
Click to collapse
Because there are not many options as we can only use stock 6.0.1 base with the locked bootloader that uses the engineering kernel. If we could use any kernel it would be a WAY different story.
Thanks for the insight. Did not realize the engineering kernel was so restricted. I came from an HTC one prior, and we had lots of roms based off the base kernel, but I am a jafu so my knowledge is limited.
More
Anthrax79 said:
Thanks for the insight. Did not realize the engineering kernel was so restricted. I came from an HTC one prior, and we had lots of roms based off the base kernel, but I am a jafu so my knowledge is limited.
Click to expand...
Click to collapse
Would give stang5litre a run man. Dude put a lot of work in it. Color just bout anything the way u want to. Smooth ass rom. Way smoother than stock rooted. Got a nice group of people come join
It could be worse....
Anthrax79 said:
Thanks for the insight. Did not realize the engineering kernel was so restricted. I came from an HTC one prior, and we had lots of roms based off the base kernel, but I am a jafu so my knowledge is limited.
Click to expand...
Click to collapse
You COULD be stuck with a MTK tablet; the only MTK devices getting any love are phablets and phones for the most part (and those are mostly in the MEAR: Middle East, Asia, and Russia). My Lenovo A7-30F (not the A3000 or A3300) has two recoveries (one each for KitKat and Lollipop) and no custom ROMs at all; my GNex (which is far older) has more ROMs just for KitKat (let alone Lollipop, Marshmallow, and Nougat).
The LG G3 was nice because there was an exploit (and it hasn't been patched to this day) that allows you to have what is called a "bumped" TWRP so you can flash all sorts of custom ROMs, including AOSP-based ROMs, as well as custom kernels. That was a nice feature of the LG G3 on VZW. Not sure why they never patched the exploit. I do miss those days, but I did stop rooting and such because I could still get really good battery life. Plus, Android Pay was a nice feature I liked using and now with the S7, I absolutely love Samsung Pay. Makes life so much easier when I check out not having to pull out my wallet, fumble and find the credit/debit card, swipe, etc. Just tap and pay! Nice!