• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Kernel][D850|1|2|5/F400/LS990/VS985]Unified Kernel Source repository/compilation

Search This thread

PRichardson

Senior Member
Apr 12, 2011
122
107
51
Louisville
PJRichardson.com
Now we just need a device config for D855 and let the CM game begin :D

BTW the bootloader may not be the biggest issue, the flashing of the rom may be able to be done using the tethered TWRP that was released.
<<-- can you (please) give me a link to the TWRP thread (HowTo for D850, via TWRP)? I've seen 3 thread talking about this, but want to be sure I'm using the correct (or main TWRP?) one for D850, before I flash the kernel I compliled from this github, in case I need to return to stock.

I'm of course presuming (or hoping) that Tectas has tested flashing this kernel already, as it's just the same stock kernel already on the D850?

(sort of taking a chance posting this, as I think I'm on the borderline of etiquette somehow)
 
Last edited:

paratox

Senior Member
Feb 18, 2010
1,112
376
we have to wait for the "bumping tool" or website to bump boot images from team codefire before custom kernels are bootable with new recovery.
if a kernel dev would ask politely in #lg-g3 freenode irc channel i`m shure one of the devs would / could bump a boot image for testing.
 

Tectas

Senior Member
Jul 26, 2011
3,344
2,941
<<-- can you (please) give me a link to the TWRP thread (HowTo for D850, via TWRP)? I've seen 3 thread talking about this, but want to be sure I'm using the correct (or main TWRP?) one for D850, before I flash the kernel I compliled from this github, in case I need to return to stock.

I'm of course presuming (or hoping) that Tectas has tested flashing this kernel already, as it's just the same stock kernel already on the D850?

(sort of taking a chance posting this, as I think I'm on the borderline of etiquette somehow)

It's not exactly stock, but the fixed stock source, D850 is tested indeed.


At a quick glance it seems like a permission glitch.

Now we all have twrp hope we can get some kernel in

As he said ;)

we have to wait for the "bumping tool" or website to bump boot images from team codefire before custom kernels are bootable with new recovery.
if a kernel dev would ask politely in #lg-g3 freenode irc channel i`m shure one of the devs would / could bump a boot image for testing.

I'll check by there, for my rin kernel, but I guess I'll better wait, to send images back and forth and because i support most devices won't be that good for me and also those who've achieved the bump tool, I'm pretty sure they've got better things to do, but maybe they'll provide the steps to bump stuff myself.

Has anyone tested this for any device other than T-moble?

Yes.
 
Last edited:

Jhinta

Senior Member
Dec 20, 2010
704
276
Preperation
................................
The resulting dtb zImage can be found at arch/arm/boot and is named zImage-dtb

Any suggestions for improvement? Feel free to comment :)

Does fastboot boot zImage-dtb works for you?
also
Code:
  LD [M]  arch/arm/mach-msm/dma_test.ko
/home/jhinta/Development/android-ndk-r10c/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-ld: -DMODULE: unknown option
/home/jhinta/Development/android-ndk-r10c/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-ld: use the --help option for usage information
make[1]: *** [arch/arm/mach-msm/dma_test.ko] Fout 1
 
Last edited:

mostafaz

Senior Member
Mar 16, 2013
1,216
2,076
iran
fastboot mode started

SOLVED
-------------------
hey
i just compiled kitkat kernel and repack zimage to boot.img
without bump i got certificate error on lg logo ( boot logo )
with bump i got fastboot mode started :eek:
boot.img copied from mine g3 kitkat cwm backup-and unpack n repack using @op suggested toolset/extracted from kdz
ps:im working on stock kernel from lg source
any solution ?
tnq in advance
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 42
    Just for developers!

    Hey guys and girls,

    I fixed and uploaded the stock kernel source for the G3 to my github which other developers can use as base for their kernels or just take it as it is to build their roms, currently the source for the D855, D851, D850, D852, VS985, F400 and LS990 are merged.
    As said, it's just the fixed stock source for now!
    There is for sure still the bootloader lock problem, but anyways, when this is fixed (which is hopefully soon) this may be helpful for some and it may can speed up things a bit.

    There may be some additional things coming, but for now, that's it.

    Have fun.

    Repository

    https://github.com/tectas/android_kernel_lge_msm8974ac

    Changelog

    14.08.2014
    • include/asm-generic: Change per_cpu_offset to take last element of array instead of returning 0 if out of bounds
    • firmware: Fix to compile prebuild firmware only once

    13.08.2014
    • kernel: quick fix
    • Fix -Warray-bounds warnings
    • Makefile: reenable -Wframe-larger-than
    • Makefile: ifeq y instead of ifdef at CONFIG_CC_OPTIMIZE_SPEED and CONFIG_CC_OPTIMZE_DEFAULT
    • init/Kconfig: Removed CC_OPTIMIZE_SIZE (default now) and added CC_OPTIMIZE_SPEED and CC_OPTIMIZE_DEFAULT
    • arch/sh/lib|arch/title:Changes for CC_OPTIMIZE_SPEED and CC_OPTIMIZE_DEFAULT

    12.08.2014
    • arch/arm/mach-msm|fs|ipc|kernel|mm: fix uninitialized warnings
    • arch/arm/configs: CONFIG_FRAME_WARN added, CONFIG_CC_OPTIMIZE_SPEED disabled
    • Makefile: Options for -O3, -O2 and -Os added
    • Makefile: Disabled warnigs for array-bounds and uninitialized
    • Makefile: linaro build optimizations
    • Makefile: started to add flags for -O3 linaro builds
    • net: bluetooth: linaro fix
    • drivers: cpufreq: Fixes for linaro at interactive governor

    11.08.2014
    • Fix Compiling Firmware
    • Cleanup of generated files
    • Reset of CONFIG_NF_CONNTRACK_SIP to default value
    • dtsi fix for VS985
    • Changes for D852
    • Changes for VS985
    • Changed CONFIG_NF_CONNTRACK_SIP to default value
    • Changes for F400

    ...

    Full list of commits can be found here

    Currently supported devices

    • D855
    • D851
    • D850
    • LS990
    • F400
    • VS985
    • D852

    Bugs

    • You tell me

    Toolchain

    Currently just the default android toolchain is officially supported, but it should work with others fine as well, if not, just tell me and i will fix it for the given toolchain.

    Credits

    9
    How to compile

    Preperation

    Check out aosp source and switch to it's directory (https://source.android.com/source/downloading.html)

    In the terminal:
    Code:
    mkdir -p kernel/lge/msm8974ac
    cd kernel/lge/msm8974ac
    git clone https://github.com/tectas/android_kernel_lge_msm8974ac.git -b kitkat .

    Compilation

    All Variants

    Code:
    export PATH=$PATH:tools/lz4demo

    D855

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-global_com-perf_defconfig zImage-dtb -j4


    D851

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-tmo_us-perf_defconfig zImage-dtb -j4

    D850

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-att-perf_defconfig zImage-dtb -j4

    LS990

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-spr_us-perf_defconfig zImage-dtb -j4

    F400

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-lgu-perf_defconfig zImage-dtb -j4

    VS985

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-vzw-perf_defconfig zImage-dtb -j4

    D852

    Code:
    make ARCH=arm CROSS_COMPILE=../../../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g3-bell-perf_defconfig zImage-dtb -j4

    Wait till it compiled

    The resulting dtb zImage can be found at arch/arm/boot and is named zImage-dtb

    Any suggestions for improvement? Feel free to comment :)
    7
    Glad to see you are here too, couldn't wait to see a SD kernel for G3. ??

    Sent from my LG-D855 using XDA Premium 4 mobile app

    Yep, kernel and ROM are coming soon ;) already in testing!
    5
    The flashing of the rom, yes, the boot.img is the problem i guess (and without proper kernel and ramdisk no aosp rom will work). It can be flashed as well, but if it doesn't match the stock one, the bootloader throws a security exception when you try to boot from it. At least that's what I faced, when i tried to flash TWRP directly to my device instead of just temporarly booting it, so, I guess it's the same with the kernel.

    This is true, I work with LG and they sent the company I work for a tool that loads code into the bootloader allowing unsigned code to run (we need it since we run vitual environments), I wonder if this tool is only for the LG device we test it on (can't tell you the model) or can be used on any device,
    it allows fastboot to write code to kernel + bootloader, something that always fails with the default tot without this app.


    I will test it on my g3, hope it doesn't brick it, if it doesn't on one hand this may be the key to unlock and develop ROMs, on the other hand since the software is company property that could get me fired, I won't be able to release it to everyone, maybe if I understand how it works, if it works at all on the g3, I can develop my own tool, but this is all wishful thinking.

    EDIT: the special file that is loaded into the app (you choose a file, I think it overides bootloader security chain certificate), just causes the app to crash on the G3, so no luck there unless I get this file from LG (we are not working on the G3 at this time in my company), so no hope with that, but there is a way obviously since this app without root is able to bypass bootloader (it shows a warning about security on the bootloader after)
    5
    Is interactive the default gov? That's super weird for on demand not to work as its generally the best for balance of performance and battery life. Interactive has horrible battery life and ime is laggy. I wouldnt be surprised tho, this kernel source is horrible.. :/

    Interactive is the default governor for many devices since jellybean. On demand has better battery life, but interactive is more responsive.
    For my opinion the source isn't as bad, Sammy did worse, at least at the s3.

    -----------

    Added a new branch to the repository, it's the same as the default branch, except that I added ioscheduler (default is set to vr) and voltage control, will maybe add some additional stuff within the next days and release it in another thread, just to your knowledge, to those interested.

    Sent from my LG-D855