[Reference] Building Android / Kernels for the LG E980 (ATT)

Search This thread
By:
Advanced…
fronti90

fronti90

Senior Member
Mar 29, 2012
639
1,589
Noticed one more thing:
You are copying vold.fstab in device.mk (https://github.com/thecubed/android_device_lge_gkatt/blob/master/device.mk line 59) but there actually is no vold.fstab in your device tree
How are you setting mountpoints? Or is this not necessary anyway?


Timisone said:
if you need anyone to test let me know. Is it going to be 4.2.2?
Click to expand...
Click to collapse

yeah sure, newest slim version is on 4.2.2

Edit: same thing for gps.conf, which should be in configs/
Edit2: and for libpn544_fw.so, which should be in prebuilt/
 
Last edited:
  • Like
Reactions: Gotroot, Timisone and apascual89
Gotroot

Gotroot

Senior Member
Jun 27, 2008
684
289
www.sbhacker.net
I finally got a kernel built lol it was a pain in the butt... not just go to add few scripts to it see if i can get it to boot

---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
fronti90 said:
Hey,
first of all thanks, i am trying to get SlimBean working atm and you are doing a great job! I noticed that you still have the .gitignore file and created a second one called .gitignore_old. I guess you forgot to delete the original one there ;)
Click to expand...
Click to collapse

By the way I loved this rom on my Orig. Note thanks for your work
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
fronti90 said:
Noticed one more thing:
You are copying vold.fstab in device.mk (https://github.com/thecubed/android_device_lge_gkatt/blob/master/device.mk line 59) but there actually is no vold.fstab in your device tree
How are you setting mountpoints? Or is this not necessary anyway?




yeah sure, newest slim version is on 4.2.2

Edit: same thing for gps.conf, which should be in configs/
Edit2: and for libpn544_fw.so, which should be in prebuilt/
Click to expand...
Click to collapse

Right now, the tree is *just* for building CWM/TWRP, I haven't done anything to fix the Android-side dependency issues.
For the most part, you can clone the repos from github.com/teamlgog and use them as a base starting point for grabbing files.
 
fronti90

fronti90

Senior Member
Mar 29, 2012
639
1,589
thecubed said:
Right now, the tree is *just* for building CWM/TWRP, I haven't done anything to fix the Android-side dependency issues.
For the most part, you can clone the repos from github.com/teamlgog and use them as a base starting point for grabbing files.
Click to expand...
Click to collapse

ahh well that explains alot :D yeah i'll take a look at it then, feel free to check our github too if you are stuck at some point! https://github.com/SlimRoms/device_lge_gkatt
Right now there are a few commits still pending in our review system, i guess they are getting merged tomorrow
 
  • Like
Reactions: Gotroot and apascual89
K

kevinwzh

Member
Jul 13, 2012
14
2
Does this build include QuanCOMM baseband?

Hi,

Does this build include the baseband dump which support GSM/EDGE? As F240L exclaim that Quancomm 9615 support world module, but i can not use the GSM/EDGE from my 240L, could you suggest if i can use the EDGE after refresh the CM 10.1 build?

Thnks all.
 
F

fryguy128

Senior Member
May 10, 2012
129
25
Do you have the instructions for fastbooting or do we even need to go through fastbooting since we have freegee now?
 
S

suren21

Senior Member
Jul 17, 2007
94
2
hunting-arena.in
trying to build for e988

build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/gkatt/cm.mk]]: "device/lge/gee-common/gee-common.mk" does not exist. Stop.
Device gkatt not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Geting this error on trying to set build environment for recovery. Was able to build the kernel though
 
C

culot

Senior Member
Oct 11, 2014
435
177
Bay
How about building for non-CM stuff, using the LG.com sources: where in hokum is the device tree to build from LG's source?

EDIT: Nevermind, I didn't realize LG's sources were not complete. Bastards!
 
Last edited:
Snepsts

Snepsts

Senior Member
Apr 16, 2014
637
554
St. Louis, MO
cognitive said:
@thecubed, @culot,
Can I compile the kernel of lg gx f310 (code name omega, omegar) in CyanogenMod by the open lg source?
Click to expand...
Click to collapse

thecubed quit android. If you want to port to CM you'll need the LG source and need to get the LG specific changes from it (trace back CAF version & get the changes through kdiff3) then you'll need to get the latest CAF source (for us I think it's LA.AF-1.1) and use your kdiff3 to add the LG changes. And tadaaa, CAF/CM kernel!
 
  • Like
Reactions: cognitive
C

culot

Senior Member
Oct 11, 2014
435
177
Bay
cognitive said:
@thecubed, @culot,
Can I compile the kernel of lg gx f310 (code name omega, omegar) in CyanogenMod by the open lg source?
Click to expand...
Click to collapse

I would think a F240-based device tree and kernel for CM12 would work fine for that? Isn't the FX F310 basically the same? I've been digging into the Lollipop kernel code for both recently and I swear the only glaring differences seem to be that the F310 Lollipop kernel code is newer and fresher. Pretty sure?

Have you tried Flashing any F240k CM12 ROMs from a stock Kitkat setup? If might lead to having to flash back to stock, but it seems like it should work? Maybe check LGViet forums, they'd probably know best.
 
  • Like
Reactions: cognitive
C

cognitive

Member
Nov 24, 2014
33
2
culot said:
I would think a F240-based device tree and kernel for CM12 would work fine for that? Isn't the FX F310 basically the same? I've been digging into the Lollipop kernel code for both recently and I swear the only glaring differences seem to be that the F310 Lollipop kernel code is newer and fresher. Pretty sure?

Have you tried Flashing any F240k CM12 ROMs from a stock Kitkat setup? If might lead to having to flash back to stock, but it seems like it should work? Maybe check LGViet forums, they'd probably know best.
Click to expand...
Click to collapse
I'd tryed flash e980 or f240-based, but Gx f310 couldn't boot. LED blind and black screen.

The differentiation s between f310 and f240 are screen and knock on (touch). However, the e980-base CM source code have not drivers for f310's screen and touch. I've merd that drivers code from f310's kitkat, build successed. But not boot.

Sorry about my poor english.
 
You must log in or register to reply here.

Similar threads

bountyman334
[AUG 14][ROM][4.4.2]LG G3 Optimus G.PRO vXII
Replies
5K
Views
632K
heimdallZ
heimdallZ
A
G2 apps added E988 ROM (F240/E980) V7 Beta ..4.4.2
Replies
2K
Views
360K
D
dat.97.Vietnam
nerdyblonde
[ROM][OFFICIAL][5.1.1_r24] BlissPop by Team Bliss V4.0.3 - GProJ - E980 - 11/8/15
Replies
3K
Views
409K
N
NimaXDA
madmack
[GUIDE] [E980] Fix soft bricks. Flash back to stock using LGFLashTools
Replies
481
Views
303K
Y
YaBoiAnh
1Zero3forlife
[ROOT] for LG Optimus G Pro E98x + CWM + TWRP [s-off]
Replies
227
Views
242K
T
Tushcool

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 18
    thecubed
    thecubed
    Howdy Everyone!

    Here's my quick guide to compiling Android for the Optimus G Pro for ATT.

    Basic Reference

    For reference, this phone's codename is "geefhd" per the stock boot.img, however the kernel defconfig is "gkatt_bcm".
    Simplicity sake dictates that I would like to use the kernel defconfig's name as the device codename.

    From here on out, I'd like to refer to this phone in code as gkatt, yet we'll call the kernel source dir geefhd.
    ​

    Prerequisites

    Building Android for this phone requires quite a bit of familiarity with the Android build system. If you are unfamiliar with things like makefiles and bash, I do not recommend trying this, as you'll pull out more of your hair than you can afford to lose.

    That said, I'd recommend you have at least repo installed, or in your $PATH variable to make this guide a little easier to follow.

    You also need to have the build utilities installed. See the CyanogenMod wiki for the build dependencies and how to install them.
    ​

    Getting your tree set up

    Well, it ain't Christmas, but let's put up the tree anyway.

    For this guide, I'm going to assume you're like me, and you put all your Android projects in ~/android/.

    Let's begin.

    Code: 
    mkdir -p ~/android/cm-10.1/
cd ~/android/cm-10.1/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo sync

    Now after a few hours, you'll have a empty tree set up. Let's decorate!
    ​

    Getting the device repos set up

    Once you have the basic CM skeleton in place, we need to add our device support files.

    Code: 
    mkdir -p ~/android/cm-10.1/device/lge
cd ~/android/cm-10.1/device/lge
git clone -b cm-10.1 https://github.com/TeamLGOG/android_device_lge_gee-common.git gee-common
git clone https://github.com/thecubed/android_device_lge_gkatt.git gkatt

    Congrats. Now you have the Android side of things ready, however you're not fully ready to start building-- you need a kernel!
    ​

    Getting the kernel repos ready

    Next up: kernel.

    Code: 
    mkdir -p ~/android/cm-10.1/kernel/lge
cd ~/android/cm-10.1/kernel/lge
git clone https://github.com/thecubed/android_kernel_lge_geefhd.git geefhd

    You should now have a nice folder containing the kernel and everything you need to build it.
    ​

    Great! What do I do with this?

    You now have two options -- do you want to build Android AND a kernel, or just a kernel?

    Let's assume you want to build a kernel only first.

    Code: 
    cd ~/android/cm-10.1/kernel/lge/geefhd
. envsetup.sh

    Now you'll see some neat text from my setup script, it'll tell you what commands it just added to your shell and how to use them.
    To build a kernel do this:

    Code: 
    make mrproper
make gkatt_bcm-perf_defconfig
make zImage

    Then you can look in arch/arm/boot for a file called zImage, which is the kernel itself, ready to be used and abused.

    Once you're done and want to clean up, just run make clean or make mrproper to erase all tracks of ever building.

    Keep in mind, "mrproper" erases your ".config" file, so before you can build again, you have to issue "make gkatt_bcm-perf_defconfig".
    My envsetup script will warn you of that, just incase you forget ;)

    Now, let's assume you want to build an Android recovery image!

    Code: 
    cd ~/android/cm-10.1/
. build/envsetup.sh
lunch cm_gkatt-userdebug

    The environment is now ready for you to build...

    Code: 
    mka recoveryimage

    In about 10 mins you'll have a full recovery.img in $OUT.
    The neat thing about this is it builds the kernel inline with your build -- so you build a recovery AND a kernel at the same time.
    This will save you a LOT of time testing kernels, since you don't have to manually unpack and repack the boot image after modifying the kernel.

    To see your shiny new recovery.img file:
    Code: 
    cd $OUT

    KEEP IN MIND you CANNOT flash these images! Flashing them will result in a security error!
    You can only fastboot boot these images. I'll post fastboot instructions shortly.
    ​

    How do I get help??

    Well, first things first, ask on IRC.

    I'm nearly always around on Freenode. Join #lg-optimus-g and ask if I'm around.
    I go by the name IOMonster on IRC. When I'm at work, I'm IOMonster_work.

    Please don't just ask to ask a question, ask your full question.
    Don't PM me unless you ask first, it's weird to get 20 PM windows open on my IRC client and not have any idea who is who or what they want... basic courtesy please :)

    If by chance/miracle I'm not on IRC, post here. Again, I will not answer questions related to this via PM on XDA. I like answering things publicly so that others can read the answer. Google doesn't index PM's (yet, at least haha), so it doesn't do anyone any good to help you over PM unless it's something private.
    ​

    I <3 you so much, how do I show my love?

    You are so kind :D

    I most definitely do not expect donations of any kind, however they are appreciated a lot.
    I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever. :)

    XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
    ​

    Let me know if I missed anything!
    View
    3
    fronti90
    fronti90
    Noticed one more thing:
    You are copying vold.fstab in device.mk (https://github.com/thecubed/android_device_lge_gkatt/blob/master/device.mk line 59) but there actually is no vold.fstab in your device tree
    How are you setting mountpoints? Or is this not necessary anyway?


    Timisone said:
    if you need anyone to test let me know. Is it going to be 4.2.2?
    Click to expand...
    Click to collapse

    yeah sure, newest slim version is on 4.2.2

    Edit: same thing for gps.conf, which should be in configs/
    Edit2: and for libpn544_fw.so, which should be in prebuilt/
    View
    2
    thecubed
    thecubed
    apascual89 said:
    Awesome work! How can we get the vendor files to build cm-10.1? For now, could we use the same as the OG ?
    Click to expand...
    Click to collapse

    Check http://github.com/TeamLGOG :D

    The vendor files there should work fine for this device, minus the wlan props and any modem/DSP related firmware.

    This phone is *very* similar to the OG/N4, it's just got a larger screen and different wlan chip (Broadcom instead of Qualcomm)

    However, all that said, I've yet to build it for the phone-- I'm focused on getting it more unlocked right now.
    View
    2
    thecubed
    thecubed
    Hey all,

    I just pushed the proper file to make the kernel build-- sorry about that! Apparently LGE has a .gitignore file in firmware/ in the kernel that makes it ignore the .bin firmware files... ugh.

    I've removed that and pushed the update to my github. You should be able to build successfully now!
    Happy building!
    View
    2
    thecubed
    thecubed
    I'm not sure why you guys are getting those errors. I'm able to build the kernel just fine...

    Maybe my repo is missing something that I have locally? I'll try re-syncing everything to a new dir and testing again later.
    View

New posts