Before you read this theard:
There isn't any rom which you can install.
This Development Thread is for users who have any idea, something to share.
Click to expand...
Click to collapse
As we know our L9 has locked bootloader. We can't flash boot.img and recovery.img, but we can load custom ramdisk and recovery through 2nd-init.
What is 2nd-init?: Read there: http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
My CWM Recovery for L9 is also loaded through 2nd-init, so we have ready 2nd-init scripts. Where recovery and custom ramdisk will be storied:
boot.tar (custom ramdisk): /system/bootstrap/boot.tar
recovery.tar (custom recovery): /system/bootstrap/recovery.tar
So, we have 2nd-init script, we can start porting rom to our device (I have P760 variant). We have to port rom from Prada 3.0 and Atrix 2 (very similar devices) or compile from sources. For now 1st option is better because we haven't got any sources expect 10a rom.
At the end I attach full 2nd-init script. You can test it on stock rom, it works. Only need to edit ramdisk and port some files to get working CM9/10. Link to ramdisk is in second post. In the most part it is playing with the files and ramdisk (like editing the lg prada, 4x was edited stock ramdisk), because we can not run custom kernels. There are many specific files, which ramdisk, kernel checks md5 checksum of this files (drm files).
IMPORTANT INFORMATIONS ARE ALSO IN POST BELLOW (2nd post, links to important files).
This is the end for now. Theard will be updated.
What can you do:
Post something useful for us
Have an idea, write there
Links to useful websites/theards
Share some info about porting roms to L9
Notes about the idea, porting roms, very important information
Please don't:
Ask for ETA's & Troll
Edit: Now. Cyanogenmod 9 is working. If you want to port roms use this rom as base. Ramdisk is storied in /system/bootstrap/boot.tar
For now I don't neeed tester, It don't work for now. I and persons who help me are working, but it isn't easy as porting with unlocked bootloader.
For devs. Some informations and links. I add some important links. Some of them are from Optimus 4X. I added it, because In 4X CM10 ramdisk is fixed drm conflict (everything I will write in this post).
LG Prada Cyanogemod 9 (uses 2nd-init, stock LG kernel, easiest way to port): http://goo.im/devs/milaq/p940/cm9/cm-9-20121126-NIGHTLY-p940.zip
LG Optimus 4X CM10 (there is fixed booting, drm conflict). Important files in this rom: /system/bin/netd /system/bootmenu/boot.tar (also I upload it without rom), /system/drm, system/drm2, /system/lgdrm.tar: http://d-h.st/ivJ
10b (branded 10a) P760 system and boot (ramdisk) dump: http://www.mediafire.com/?9b4oywl94j0bp
Optimus 4X Stock boot (ramdisk): http://www.mediafire.com/?k48h27ln4xnygrh
Optimus 4X CM10 ramdisk (you can compare with 4X Stock ramdisk, see what's changet, try to do this on L9, also included in 4X rom /system/bootmenu/boot.tar): http://www.mediafire.com/?fia0d72cs93cy71
Stock P760 ramdisk with ro.secure=0 edited to work with 2nd-init (bootable, working, to boot install cwm recovery and copy boot.tar to /system/bootstrap, it's base to port cm9/cm10). Only one bug is soft button light:http://www.mediafire.com/?ra5itp818uijpk3
CM 10 for Atrix 2 (similar device to L9): http://forum.xda-developers.com/showthread.php?t=1869692
Important theards/posts:
Similar devices to L9:
LG Prada 3.0 (The same platform, manufacturer, different screen resolution, similar ramdisk, also similar some files specific to platform, phone model)
Atrix 2 (the same resolution, platform, other manufacturer)
hi,i have a P760,if you need testers count with me.
have you recovery installed and i know how to flash kdz and everything else.(install zip and create backup).sorry for my google translate..
artas182x said:
I need testers witch other variant of L9 (P765, P768, P760 and others).
Click to expand...
Click to collapse
I have P765, fit for all your requirements, but don't have much free time. In any case, I will try to help if I can.
I can test the rom on a P760
Hallo guys, finally we have our sub forum, for me to begin will be also good to have one clean and deodexed stock rom with some advance, like script for kernel OK and........
Also agree to port cynogen 9 and other rom:thumbup:
Inviato dal mio LG-P760 con Tapatalk 2
count me in... P760... had a lot of android based devices. so i know to flash via recovery, also flashed P760 several times via kdz..
can test for the p769. I'm well versed in cwm flashing and have reflashed this phone using kdz several times.
P-765 user
Let me try it
i will test as well, got an lg l9 P760 thats the reason we are here. to support and try :highfive: hope it works and to go forward even more with CM 9,10, 10,1 ....
I can also help test with p760 , can do all that you ask and have alot experience in device modding/testing
Hi man! Im a developer for three lg phones and have p760! Do you know how compile cmX for phone that have locked bootloader?
Inviato dal mio LG-P760 con Tapatalk 2
P769 here.... happy flashing etc.
Sorry saw the post very late. I am here for...
P765 Indian (Asian) variant.
Excellent write up on 2nd-init at http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Thanks it explained many things and hijacking booting sequences.
I know its really early, but do you think its possible to have a touch led notification feature built into a rom? Thats the only thing missing from this phone I dont like. I miss having a blinking light telling me if I missed a call or message.
I know theres an app on the store but from my using it, its pretty buggy and doesnt always work. And it seems to eat up the battery too.
Would be difficult to compile the original KDZ 10E with root after install?
redspeed said:
I know its really early, but do you think its possible to have a touch led notification feature built into a rom? Thats the only thing missing from this phone I dont like. I miss having a blinking light telling me if I missed a call or message.
I know theres an app on the store but from my using it, its pretty buggy and doesnt always work. And it seems to eat up the battery too.
Click to expand...
Click to collapse
Not only that app but this feature itself is battery consuming. Tried this on O2x and removed after noticing battery drain.
nevp said:
Would be difficult to compile the original KDZ 10E with root after install?
Click to expand...
Click to collapse
ICS Source code for all L9 variants (except 765) are released. Should it be a problem for devs to compile rooted KDZ from source? Just curious to know this from devs.
One more thing, now as CWM by Artas185x is fully working, is it possible for sharing restorable zips with rooted roms? Again just curious to know.
well as of now i have set up a petition for lg to unlock the bootloader of all L9 Variants maybe if we get enough signatures they will do as they are doing with the 4X and the optimus G in my signature below hopefully they get a hint
cmahendra said:
Not only that app but this feature itself is battery consuming. Tried this on O2x and removed after noticing battery drain.
Click to expand...
Click to collapse
I guess its because the cpu gets woken up each time the leds go on? Is there a way to toggle a low brightness blinking or pulse when a notification is received that will shut off again once the screen is turned back on? I wouldnt think one or both of the leds blinking at low brightness by themselves would take up too much battery power?
I've just signed the petition and i'm ready to test with P760
Related
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
I am in no way a developer, I simply edit files and put them in the right place so it boots for us. I do this to help fellow d803 users.
If I helped with a file, always make a nandroid backup just in case things go haywire. Anything that happens to your phone is your responsibility.
Everything I submit gets tested rigorously on my own G2 before being posted to ensure its working, but we all get different results, so the experience might vary. Just a heads up.
Click to expand...
Click to collapse
Any suggestions or edits by mods to the post are welcome.
[email protected] said:
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
Any suggestions or edits by mods to the post are welcome.
Click to expand...
Click to collapse
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Well I meant it more in a way for those who don't understand much about editing the updater script and exchanging the boot.IMG. with what I'm offering all they have to do is ask the ROM and I'll post it online with said changes in case they don't know how to do it. Something like a small favor for everyone, but thanks for the reply!
Request
If you could please port this rom I would very much appreciate it
http://forum.xda-developers.com/showthread.php?t=2609355
---------- Post added at 08:48 AM ---------- Previous post was at 08:38 AM ----------
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Could you possibly make a quick tutorial on how to do this? or possibly direct me to where i could find one?
Hi, I was looking at your old thread about how you could port d802 roms to d803. I was wondering if you could port cyanogenmod 11 snapshot m12. http://download.cyanogenmod.org/?device=d802 i would really appreciate it. and it seems like u are good at what u do so you should maybe consider building for d803 for cyanogenmod. thousands of d803 users have been waiting for cyanogenmod support but to this day have recieved none. anyways if u could port it i would really appreciate it! thanks!
can you make lollippop rom pls
http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
CM12 !
PLZ !
Hey,
I was a semi-developer for a my previous phone, it was a mediatek.
As you all know porting and customizing ROMs for mediatek phones is really easy.
But now I also want to start building/porting for this phone.
Can someone give me links to guides,tips,.. for this phone.
What is the best phone to port ROMs from?
Thanks
Can no p760 developer give me tips? Or are you all thinkig "noob"?
You dont have to be PRO to port roms I started doing it one week ago and it goes really well. I will quote nasheich. He wrote very good tips:
nasheich said:
1. Find device with same CPU, LG L9 have dual core CPU, so find it, for example, Motorola Razr(I'm used on Mokee n Paranoid), Galaxy Tab 2(I'm used on Xperience, AOKP, Hellfire).
2. Forget about screen size(4", 5" or 7"), the important is screen DPI, it has to be used same DPI, LG L9 has HDPI, find it the HDPI device
3. Same OS version, KK with KK, JB with JB, special for JB, see the version of JB, example JB 4.2.2 with JB 4.2.2
4. Make sure you have installed software on Windows/Mac, for porting, you may need just 2 software,
- Note++(for editing build.prop & other files like .txt, .bin etc)
- Apktool (for decompile n recompile .apk n .jar files)
5. Open mind
Click to expand...
Click to collapse
I will add only two tips. Don't give up and try to read as many guides as you can
Xerdox said:
You dont have to be PRO to port roms I started doing it one week ago and it goes really well. I will quote nasheich. He wrote very good tips:
I will add only two tips. Don't give up and try to read as many guides as you can
Click to expand...
Click to collapse
Thanks for your response but could you give me a link to the guide you used? I tried some guides that I found but it didn't work. Im trying to port slimkat.
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=2245786
http://forum.xda-developers.com/showthread.php?t=2284985
I think that's all.
Xerdox said:
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=2245786
http://forum.xda-developers.com/showthread.php?t=2284985
I think that's all.
Click to expand...
Click to collapse
Thanks gonna try it soon
Remember that you will never find a guide which will work for all roms
can some of you fantastic developers create an Android M ROM for the LG Optimus G E970 at some point? does anyone have an ETA? I would love to learn to build it myself, but I have limited access to a computer (The library is practically my only source). I noticed that there is no developer preview for the Nexus 4, so would that slow down the building process? Thank you a lot!
Update : @ChiKaLiO is working on a few variants for the Optimus G and might start soon for geeb . Someone else has released Marshmallow for other variants...is anyone else working on it?
optimisandroid said:
can some of you fantastic developers create an android M ROM for the LG Optimus G E970 at some point? does anyone have an ETA? I would love to learn to build it myself, but I have limited access to a computer (The library is practically my only source). I noticed that there is no developer preview for the Nexus 4, so would that slow down the building process? Thank you a lot!
Click to expand...
Click to collapse
We'll have to compile from source for a bug-free version for the e970. However, there is a Google employee that's working on a version of M for the Nexus 4, so we may just be able to port that version on to our phone. ETAs are a big no-no. I'd get pissed if people kept asking when I'm going to release something when I'm working tirelessly to squash bugs and have a working build. It'll come. Patience is key.
Now that there is a Nexus 4 Marshmallow ROM out, is there someone experienced working on E970 Marshmallow (not asking for an ETA) or someone who could give me some tips on doing it myself as my first ROM?
yeah, an CM M Rom would be nice!
topdawg7793 said:
We'll have to compile from source for a bug-free version for the e970. However, there is a Google employee that's working on a version of M for the Nexus 4, so we may just be able to port that version on to our phone. ETAs are a big no-no. I'd get pissed if people kept asking when I'm going to release something when I'm working tirelessly to squash bugs and have a working build. It'll come. Patience is key.
Click to expand...
Click to collapse
Oh yeah. So great
Gửi từ LG-E970 của tôi bằng cách sử dụng Tapatalk 2
apparently there's already an M rom out for the nexus 4 (aosp) as well as the international optimus g (e975/f180 i believe). thing is i don't want to go back to a broken rom without a lot of features (biggest pain for me is changing mac addresses since my workplace uses mac filtering for allowing wifi devices). hopefully it'll come around before the year's out, preferably with some of M's bugs removed as well but ya never know.
There are a couple different ones built for the intl optimus g, e975.
If someone builds a 6.0 kernel for e970, most of those roms should actually work with little other modification.
kernel
i have one, but it is very unstable
kamera isn`t working properly, and video broken
Hope devs do make an M build
I skipped L, not interested in it, and Ive been quite happy on my 4.4.4 SlimRom and do hope Slim, Bliss or CM make builds for our phone with help of devs such as optimus, its an awesome phone and really dont feel the need to change it still, nothing new has really wowed me on new phones exept maybe some cameras but dont take much of video or pics so hope the comunity does deliver an M version for our phone.
Waiting patiently
I also am interestef in an M ROM. I installed M on my Galaxy S4 and love it. But i am selling it now (need the cash) and am keeping my e970.
Marshmallow for E970
I have been running the geeb version of Marshmallow (Nitrogen by Mr Mex) again now for a week or so (March 1 version). The biggest problem is the SIM card is intermittently not recognized when not on a call (shows EMERGENCY CALL ONLY instead of carrier) and Layers does not appear to be as stable for themeing as CM's theme engine though I have found a couple of Layers that spare my retinas.
You can download at http://xyyx.ga/nitrogen-os/geeb/ and install using TWRP v2.8 though Philz last CWM derivative may work as well. I still have one foot in the Resurrection Remix v5.6.4 (Lollipop) camp as it runs nicely on my E970 without the SIM recognition issue and with Privacy Guard and Interruptions has basically the same featureset as Marshmallow just a slightly different implementation. In addition CM themeing appears more polished than Layers for Marshmallow (not necessarily Lollipop) at this time as some Layers cause system problems.
If you want to see how well it works for you I would skip installing any Layers or Xposed until you've run it for a day or so to cut down variables.
See
http://forum.xda-developers.com/optimus-g-att/development/dev-roms-development-t3279183
http://forum.xda-developers.com/optimus-g-intl/development/rom-nitrogen-os-27-10-2015-t3234308
thanks for the info, hope the SIM card problem can be fixed.
does camera and sd card works?
GEEB builds
No problem with camera or SD. There was a major camera problem for a while but that has been fixed in recent builds.
OMGMatrix said:
There are a couple different ones built for the intl optimus g, e975.
If someone builds a 6.0 kernel for e970, most of those roms should actually work with little other modification.
Click to expand...
Click to collapse
The e975 is a geehrc device and the e970 is a geeb device. The ROM won't install. It fails with the error stating that it requires a geehrc device.
GEEB builds
Are you trying one of these?
http://xyyx-dev.ru/nitrogen-os/geeb/
http://xyyx-dev.ru/nitrogen-os/testing/geeb/
KnowNadda said:
Are you trying one of these?
http://xyyx-dev.ru/nitrogen-os/geeb/
http://xyyx-dev.ru/nitrogen-os/testing/geeb/
Click to expand...
Click to collapse
Not until I know the SIM is stable.
blitz9826 said:
apparently there's already an M rom out for the nexus 4 (aosp) as well as the international optimus g (e975/f180 i believe). thing is i don't want to go back to a broken rom without a lot of features (biggest pain for me is changing mac addresses since my workplace uses mac filtering for allowing wifi devices). hopefully it'll come around before the year's out, preferably with some of M's bugs removed as well but ya never know.
Click to expand...
Click to collapse
Mac addresses are Hardware IDs. They are not going to change with a new OS.
http://xyyx-dev.ru/nitrogen-os/geeb/
downloaded 2016-3-29 zip
tried to install it but installation of zip stops with error
this zip is not for geebus !!!
I have att lg optimus g E970
You do not mention what recovery you used or wipes performed, et cetera.
It installed for me using TWRP 3.0 (for geeb). I dirty flashed (cache wipes only) over my March 1st Nitrogen install.
KnowNadda said:
You do not mention what recovery you used or wipes performed, et cetera.
It installed for me using TWRP 3.0 (for geeb). I dirty flashed (cache wipes only) over my March 1st Nitrogen install.
Click to expand...
Click to collapse
Thanks updated my recovery to TWRP 3.0.
now Nitrogen OS sucessfully installed
EDIT: We got it! It boots. But some things like RIL and audio are not working, but we'll get this sorted out soon.
Official thread here: http://forum.xda-developers.com/opt...opment/rom-cyanogenmod-12-1-lg-l3-ii-t3297897Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. Nevermind, broken.
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 IINot needed.
Vendor files for CM12.1 for L3 IINot needed.
Lollipop kernel.Not needed.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
EDIT: I managed to build CM12.1 for LG L3 II, but I don't know if it's working or not - download here and tell me: https://www.androidfilehost.com/?fid=24345424848488130
Everyone, if you can help us create CM12.1, PM me your Telegram username (a great IM), I'll add you to a group chat. @aidasaidas75 @IGGYVIP and other devs are welcome.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
What do we probably need?
A device tree for CM12.1
Vendor files for CM12.1
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Caio99BR said:
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Click to expand...
Click to collapse
Yeah, it's that recovery I built Also, I can't test ROMs for L3 II anymore, I changed to Windows Phone But I think my cousin still has my old L3 II. I'll see. BTW I got a new PC, with a quad-core Intel Core i5-4460, and I set up a VM on it, so can build and build and build BTW You don't have to build, it's not building...
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Need more info and need a dev
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
And not say drivers, say vendor blobs or kernel drivers, this not is windows
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
dadziokPL said:
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
Click to expand...
Click to collapse
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Caio99BR said:
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
And not say drivers, say vendor blobs or kernel drivers, this not is windows
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Click to expand...
Click to collapse
Thanks for clearing up some stuff Caio!
Ok, so here are propertiary files for L5(for CM12.1): https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
And here are device blobs for L5(also for CM12.1): https://github.com/aidasaidas75/android_device_lge_e610
Let's see what we can do, we got @IGGYVIP, he knows a lot, and he pretty much started everything with modding L3 II, we can bring CM12.1 for our L3 II together!
I am the orders! e-e
Wow! Let's see what we can do, I can help them in some respects too, and I can test whatever they want. I'm not afraid to have a paperweight, and I know it will be worth it. If they need a Tester, I am the orders!
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
MinusThousand said:
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
Click to expand...
Click to collapse
Okay, but we need to get it to build first. It won't build, there are errors, we need a proper device tree and proprietary blobs for CM12.1.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 II
Vendor files for CM12.1 for L3 II
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
aidasaidas75 said:
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
Click to expand...
Click to collapse
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
IGGYVIP said:
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
Click to expand...
Click to collapse
I started building again so it might be lucky day for e430
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
IGGYVIP said:
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
Click to expand...
Click to collapse
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
aidasaidas75 said:
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
Click to expand...
Click to collapse
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
dadziokPL said:
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
Click to expand...
Click to collapse
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Caio99BR said:
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Click to expand...
Click to collapse
These are for Huawei Y300/G510. Are you sure these are gonna work?
Also, my carrier valued the phone at around 25 euro, If they figure out, I'll just have to pay it, but I can keep the phone forever, no big deal
I've been thinking about the myriad of "old" gadgets that are alive thanks to the variety of ROMs available these days.
But a fact that intrigues me is why this device has very few ROMs available ... it really is something that draws the attention precisely because it has a good potential to receive them.
I have been around the G2 Mini forums since, pretty much, when the device was released. If you have a look at the oldest posts, some of them are mine.
In that time, I have seen many devs, at first trying to unlock the bootloader of the device, with Zaaap finally succeeding, by figuring out how the Russians at 4pda hacked the bootloader of the L90, and then he, and others, made some ROMs.
Since then, the only ROM dev that seems to still be working on our device is @mobiusm . Other that him, I still work on my kernel, with the help of @likeadracula . (However, he is very busy and I don't have any features to add, so there is little work done lately)
I don't know why there aren't any other devs, although, I believe it's because of the initial price (250-300 €) so no dev got it, and, even when the price dropped, it was already "old".
So, yeah, that's what I think.
P.S.: This is not a development thread, but a discussion. It belongs in G2 Mini General.
EDIT: Thread moved by mod.
For me, one developer who works on ROMs and one on Kernels, seems like a lot for a nearly 4 year old, non flagship device.
Also, having the newest Recovery & newest ROM which are worked out properly + a neat kernel with all the features you desire should not be taken for granted.
I am very grateful for all the development that has been done and will be done and I wouldn't know why I should get a new phone, 'cause this one works just fine, at least for me.
My surprise in relation to this fact is related that this device does not differ in anything from the L90 in terms of hardware, and the boot unblocking is the same, same procedures, so it is common to see roms for L90 and not for the G2m. This is something I'm surprised about. Obviously I am happy that there is still developer for this device, particularly the rom of my preference that is the LOS, did not abandon it, so 2..3 or more roms for it does not make as much difference since I just like to use the LOS on my devices, for the stability, performance and commitment of the team to all supported devices, however, is my view, other people have divergent thoughts.
Oshmar said:
My surprise in relation to this fact is related that this device does not differ in anything from the L90 in terms of hardware, and the boot unblocking is the same, same procedures, so it is common to see roms for L90 and not for the L90. G2m, this is something I'm surprised about. Obviously I am happy that there is still developer for this device, particularly the rom of my preference that is the LOS, did not abandon it, so 2..3 or more roms for it does not make as much difference since I just like to use the LOS on my devices, for the stability, performance and commitment of the team to all supported devices, however, is my view, other people have divergent thoughts.
Click to expand...
Click to collapse
Actually, precisely because of the similar hardware, it's very easy for the L90 ROMs to be ported to the G2M.
One the devs that have made ROMs for the g2m recently told me that he is using the L90 for initial testing and then uses the blobs for the g2m to make it work. (I don't actually know, but I think that the only problem with the L90 blobs is the camera or the WiFi, if anything)
In fact, it's so easy that anyone, with the most basic knowledge of Linux, can get it to work. I think. I haven't actually tried.
So, find a ROM of the L90 that you like and give it a shot. Just follow an online tutorial and you should be able to port it.
If you need any help, just let me know. Or anyone on the forum (though, some, myself included, are busy)
I was thinking once before to try Slim Rom from l90, but I was afraid to ruin my phone
Boki11111 said:
I was thinking once before to try Slim Rom from l90, but I was afraid to ruin my phone
Click to expand...
Click to collapse
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Vagelis1608 said:
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Click to expand...
Click to collapse
If I try, I'll report
Complicated ... but as I said, it was only a sudden surprise because there were few roms, however, for my daily use, LOS I like, of course some options are always welcome, but if it is not possible, good size too.
Vagelis1608 said:
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Click to expand...
Click to collapse
not working,error in start installing zip,probably should first edit build.prop and kernel
Boki11111 said:
not working,error in start installing zip,probably should first edit build.prop and kernel
Click to expand...
Click to collapse
In the install script in the zip, there is a command "assert" that checks the device.
Remove that line and it will install.
I would like your opinion if it is worth changing my devices; Moto G Falcon and the LG D618, both in perfect condition, for a Moto G4 Play?
Oshmar said:
I would like your opinion if it is worth changing my devices; Moto G Falcon and the LG D618, both in perfect condition, for a Moto G4 Play?
Click to expand...
Click to collapse
Do you know in which parts the G Falcon and the G4 Play differ?
Is it possible for g2m to die if you try to install a rom of the L90?
Oshmar said:
Is it possible for g2m to die if you try to install a rom of the L90?
Click to expand...
Click to collapse
Nope. Only soft brick (a.k.a. bootloop)
Just restore the backup you (hopefully) made before flashing
Or, wipe /system /data and /cache and then flash a ROM for the g2m.
Still, no responsibility taken
They released an unofficial version of the android Oreo for the L90.