Hey all,
Does anyone think when lollipop is released for our devices that maybe a talented dev would build a stock lollipop rom with bloatware removed and maybe some custom tweaks like built in wifi tether?
Sent from my LG-LS995 using Tapatalk
Nybs31 said:
Hey all,
Does anyone think when lollipop is released for our devices that maybe a talented dev would build a stock lollipop rom with bloatware removed and maybe some custom tweaks like built in wifi tether?
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
We first need to get our device tree situated and bring it up for Lollipop and idk if our recoveries will work on Lollipop but don't worry soon we will have custom roms
we can only hope
No custom development or our device?
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app
Murshad007 said:
No custom development or our device?
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app
Click to expand...
Click to collapse
Actually i have begun work and i am making progress but i need to remove that loki tools bs from our sources. I wish i had more help from other devs as i have compiled AOSPA 4.6 successfully but it wont flash . tried several things like removing getprop crap from updater script and removing recovery folder which its kind of useless since it compiled for use for loki i just need to figure out which files i need to remove or modify.
sickkside13 said:
Actually i have begun work and i am making progress but i need to remove that loki tools bs from our sources. I wish i had more help from other devs as i have compiled AOSPA 4.6 successfully but it wont flash . tried several things like removing getprop crap from updater script and removing recovery folder which its kind of useless since it compiled for use for loki i just need to figure out which files i need to remove or modify.
Click to expand...
Click to collapse
Glad your making progress but will this be a universal rom or for a particular model of the flex and cant you post a dev post to see if other devs can poke around ans see if they can point you in the right direction
I have the update on my phone but i havent updated since i like root, if i can, do yiu want the update files? (Sprint)
Related
Just wondering wich was the benefit on get SS on the phone if no one will be developing roms, or maybe im wrong and some ppl is developing already some CM, AOPK, Slim etc etc
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
Just wondering wich was the benefit on get SS on the phone if no one will be developing roms, or maybe im wrong and some ppl is developing already some CM, AOPK, Slim etc etc
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
We need SS to have the ability to flash Roms. It doesn't do any good to have developed any Roms of there is no way for locked users to load them. Having SS is the first step in the right direction.
Sent from non rooted motoX :'(
SS allows me to run a rooted copy of the latest AT&T update (.54), and I can still flash back to the original firmware (.51) if I wanted to start over.
Has anyone seen any mention of modem/TZ/RPM packages so those of us still on AOSP, can flash those and new ROMs and kernels built with new sources when available? Rather than having to go back to stock, update to KK, then pushing the JB aboot to get custom recovery back.
JRJ442 said:
Has anyone seen any mention of modem/TZ/RPM packages so those of us still on AOSP, can flash those and new ROMs and kernels built with new sources when available? Rather than having to go back to stock, update to KK, then pushing the JB aboot to get custom recovery back.
Click to expand...
Click to collapse
Not yet. We will have to see how out plays out the next week of so.
Sent from my VS980 4G using XDA Premium 4 mobile app
JRJ442 said:
Has anyone seen any mention of modem/TZ/RPM packages so those of us still on AOSP, can flash those and new ROMs and kernels built with new sources when available? Rather than having to go back to stock, update to KK, then pushing the JB aboot to get custom recovery back.
Click to expand...
Click to collapse
Depends on whether or not people can figure out a way to put a recovery on 4.4. As it stands right now, there is an issue with Loki and 4.4.
If no one can, then they are going to have to make the new 4.4 builds compatible with the 12b aboot just like roms needed patched for 12b when it first came out.
Sent from my LG-VS980
Post #2 to reach 10 min required posts to participate in Dev Section--yes I have a LG G2 running 24A :good:
since we have a working kitkat safestrap now will the pacman rom thread in development be reopened again? and has anyone tried it since we can flash it now with safestrap???? id like to see the pacman rom grow on this device as I've used it on my s3 and optimus g pro (g pro never had a unlocked bootloader and still may not as I havent checked, we used freegee to bypass) and would like the thread to reopen now that we can flash on 4.4
If it were only that simple, aosp roms require the flashing of different kernels. which we can't do because of a locked bootloader
ah I see. just thought id ask. seeing the g pro had a bypass using freegee kernels were flashable too and pretty much everything else. I talked to the person for freegee and he was interested in helping but he needs files from our at&t n3 that I dont have time to pull right now.
What files need to be pulled? I'm sure if you list them, I or someone else can and will grab them.
Sent from my SM-N9005 using XDA Premium 4 mobile app
it was a while ago, but I can speak to him tomorrow after work and re get the files he needs and post them here. wish I had the time tonight but I will tomorrow. he did great work on the g pro and hope he can on this one too.
looks like his app used the loki patch
https://github.com/djrbliss/loki
BLOWNCO said:
looks like his app used the loki patch
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
yeah it did
Loki has been patched on our devices.
I'm supposed to pick up an LG G2 today.
I'm coming from a Galaxy S3.
Anyways, is there a way to unlock the bootloader?
I'm a sucker for AOSP ROMs.
Sent from my D2LTE (D2VZW) using XDA app-developers app
RBarnett09 said:
I'm supposed to pick up an LG G2 today.
I'm coming from a Galaxy S3.
Anyways, is there a way to unlock the bootloader?
Sent from my D2LTE (D2VZW) using XDA app-developers app
Click to expand...
Click to collapse
Nope. But the great devs here have found a way around that.
njstein said:
Nope. But the great devs here have found a way around that.
Click to expand...
Click to collapse
So how can I go about rooting and installing an AOSP ROM?
Sent from my D2LTE (D2VZW) using XDA app-developers app
RBarnett09 said:
So how can I go about rooting and installing an AOSP ROM?
Sent from my D2LTE (D2VZW) using XDA app-developers app
Click to expand...
Click to collapse
User ioroot25 or toweroot to root it, Autorec to install a recovery, have fun.
Seeking clarity on LG G2 "customizability"
njstein said:
Nope. But the great devs here have found a way around that.
Click to expand...
Click to collapse
OK - I'm actually in the exact same situation as RBarnett09 - my Samsung GS3 just died - and I'm researching my replacement options. If I get a new LG G2 and it's already got vzw's "latest & greatest" firmware, I can still get root and/or unlock it to the point that I can I run CM11?
With the vzw GS3, the last couple of vzw OTAs locked things down too tight for AOSP (I avoided that crap but my hardware finally died).
Anyway, I just viewed a thread in the LG G2 dev section about setting up to run an LG 4.4.2 kernel binary on an unofficial CM11 build, but it doesn't say explicitly whether or not you're SOL if your phone is "current" from VZW's point of view. I gather that the factory KitKat release from LG is close enough to AOSP that the kernel will support custom (AOSP-based) ROMs (is that it?).
Are we better off finding a used LG G2, and if so, what version and date of firmware sucks the least? Thanks.
bmeek said:
OK - I'm actually in the exact same situation as RBarnett09 - my Samsung GS3 just died - and I'm researching my replacement options. If I get a new LG G2 and it's already got vzw's "latest & greatest" firmware, I can still get root and/or unlock it to the point that I can I run CM11?
With the vzw GS3, the last couple of vzw OTAs locked things down too tight for AOSP (I avoided that crap but my hardware finally died).
Anyway, I just viewed a thread in the LG G2 dev section about setting up to run an LG 4.4.2 kernel binary on an unofficial CM11 build, but it doesn't say explicitly whether or not you're SOL if your phone is "current" from VZW's point of view. I gather that the factory KitKat release from LG is close enough to AOSP that the kernel will support custom (AOSP-based) ROMs (is that it?).
Are we better off finding a used LG G2, and if so, what version and date of firmware sucks the least? Thanks.
Click to expand...
Click to collapse
Latest firmware is 24A - KitKat, it can be rooted and recovery installed using the method posted. Most of the AOSP roms work with that firmware and contain working kernels. A couple still only work with the JB firmware.
bmeek said:
OK - I'm actually in the exact same situation as RBarnett09 - my Samsung GS3 just died - and I'm researching my replacement options. If I get a new LG G2 and it's already got vzw's "latest & greatest" firmware, I can still get root and/or unlock it to the point that I can I run CM11?
With the vzw GS3, the last couple of vzw OTAs locked things down too tight for AOSP (I avoided that crap but my hardware finally died).
Anyway, I just viewed a thread in the LG G2 dev section about setting up to run an LG 4.4.2 kernel binary on an unofficial CM11 build, but it doesn't say explicitly whether or not you're SOL if your phone is "current" from VZW's point of view. I gather that the factory KitKat release from LG is close enough to AOSP that the kernel will support custom (AOSP-based) ROMs (is that it?).
Are we better off finding a used LG G2, and if so, what version and date of firmware sucks the least? Thanks.
Click to expand...
Click to collapse
Yep. I'm actually coming from an S3 myself. I understand exactly what you were saying.
Sent from my VS980 4G
Just confirming that I used towelroot to successfully gain root and also successfully flashed TWRP custom recovery via autorec.
Pretty sweet gaining a full permanent root without even hooking my device up to a computer. Not to mention that no data was deleted.
Thanks guys.
Sent from my VS980 4G
Use autorec
Sent from my LG-D802 using XDA Free mobile app
Will our get Android lollipop through Cyanogenmod?
I doubt it as we can't even get the official KK bootloader which may or may not be required for Lollipop.
I tried Android L on my Nexus 4 and didn't really like the new interface.
audit13 said:
I doubt it as we can't even get the official KK bootloader which may or may not be required for Lollipop.
I tried Android L on my Nexus 4 and didn't really like the new interface.
Click to expand...
Click to collapse
Im actually quite content with my custom rom kitkat with the Gem Flat skin on top of it. (really quite stable just ui crash twice per week).
But then the unthinkable thing happens with one of the oldest moto droid devices went from ICS to Kitkat without any official updates due to alot of developers.
Anything is possible
InDianMi3 said:
Will our get Android lollipop through Cyanogenmod?
Click to expand...
Click to collapse
audit13 said:
I doubt it as we can't even get the official KK bootloader which may or may not be required for Lollipop.
I tried Android L on my Nexus 4 and didn't really like the new interface.
Click to expand...
Click to collapse
I guess its standard to question if we will see something BEFORE THE ACTUAL PUBLIC RELEASE HAPPENS AND BEFORE CYANOGENMOD, WHICH IS NOT MOTOROLA, GETS THEIR HANDS ON IT TO SEE WHAT THEY CAN DO ABOUT PUSHING IT OUT TO OUR DEVICES.
Btw, as far as that bootloader point goes, ask yourself this, do the older devices that got left behind on GB or ICS need updated bootloaders to run KK? B/c i can guarantee i can grab my Atrix 4G or my Droid X and see KK running on both of them with GB bootloaders.
Sent from my ATRIX HD using XDA Free mobile app
Is this a signal?
I Think, yes.
Because, this night, someone did an Android L ROM For the HTC Evo 3D [POST]
I Remember, this phone has come to the world running GB, well, ROM Is still buggy, but see, that device more older than Atrix HD, I Don't know if that device has an ''updated'' bootloader [like bootloader for ICS or JB], But i think this would be a great news for this device.
I Already tried Lollipop on a Nexus 4 [Is the official update], an i really liked it. i think is better than KK, [ppl comming here and spammin' ''KK Is better'' in 3.... 2.... 1.....]
If HTC EVO 3D Has Lollipop, Our Atrix HD's can have Lollipop too :victory: , the only thing we need is hope, and a brave developer.
and please sorry about my bad english~ :silly:
Maybe.
Soon
TecknoFreak said:
Soon
Click to expand...
Click to collapse
Did you check pm about my observations/possible lead on the kernel?
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
Did you check pm about my observations/possible lead on the kernel?
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
our devices upgrade has to do with more than kernels I need to backport some ion commits to the new qcom branches lot of guess work to what is needed and what isn't. Basically have to make a custom qcom folder for jbbl. As for the kernel there are lots of ways to get this right but it will need lots of time and testing.