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

[ROM][CM11][dev only] cm-11-UNOFFICIAL-d620 Alpha

Search This thread

Zaaap72

Senior Member
May 2, 2012
311
321
Amberg
CyanogenMod 11 for the LG G2 mini D620r

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

All Credits so far go to Quarx and his project CM11 for LG L90

What i have done so far:
Setup Ubuntu on my Laptop
Installed CM dev environment like described here!
Made a new device folder following THIS guide and build some recoveries.
Took the sources from CM11 for LG L90 and integrated them to my build environment.
CM11 for LG L90 builds fine but i can not test it.
Took the files i thought we need from L90 and put them to my d620 tree.
Trial and error till it compiled for d620.
For the kernel i use original LG sources extracted to kernel/lge/msm8226.
Switched to kernel source from Quarx and tweaked it for d620.

Find sources i use here.

Unfortunately the kernel i have build leads to boot loops. (Yes i have wiped everything)
If i only install the system with the original LG stock kernel i get an security error.
How can i find out why the kernel boot loops?
(had to use the dt.img from stock kernel because mine didn't work, phone gets stuck in fastboot)


Kernel now boots with recovery.
Touch only works if i copy the FW to system folder.
CM11 now works quit well.

Known issues:
- NFC not working at all
- Vibration not working at all
- Back/Main camara has overexposure on bright scenes
- LTE can only be activated by adding quick setting for LTE

Testers welcome.
Video review from simo14

Alpha: Download

attachment.php
attachment.php


Any help appreciated.
 

Attachments

  • 20140905_130344-800x600.jpg
    20140905_130344-800x600.jpg
    52.6 KB · Views: 69,409
  • 20140905_130413800x600.jpg
    20140905_130413800x600.jpg
    62.7 KB · Views: 3,157
  • Screenshot_2014-09-05-13-19-14-800x600.jpg
    Screenshot_2014-09-05-13-19-14-800x600.jpg
    49 KB · Views: 3,309
  • Screenshot_2014-09-05-13-31-42-800x600.jpg
    Screenshot_2014-09-05-13-31-42-800x600.jpg
    67 KB · Views: 69,463
Last edited:

partyzant_x

Senior Member
Sep 11, 2010
161
59
I think we need a "extract-files.sh" to extract device proprietary files with connected and enabled usb debbuging. I do some research but didnt luck. My English is weak and i don't know how to do this script. I know its necesary for boot and compile with success.
Maybe Quarx can help us.
Probably kernel boot loops because you compile with CM source and that its not compatible with stock rom.
Regards.
 
Last edited:
  • Like
Reactions: HoaPham98

partyzant_x

Senior Member
Sep 11, 2010
161
59
I'm extracted a system folder from TWRP backup and try to port by paste>copy method. I need a META-INF folder for our phone. I don't know how to make it.
Ok i found it.

I make four builds with AndroidKitchen but its always a update-binary script error.

Any help?
make -j4 otatools give me that error.

/media/radek/bee9f4ae-71a6-4ed8-9153-7dd674ea803d/CM11/out/target/product/generic/obj/APPS/SignatureTest_intermediates
"ebtables is disabled on this build"
find: `src': Nie ma takiego pliku ani katalogu
grep: /build/target/board/generic/recovery.fstab: Nie ma takiego pliku ani katalogu
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
make: Nie ma nic do zrobienia w `otatools'.

/build/target/board/generic/recovery.fstab exists in the directory.


When try to compile kernel:

*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2

That's mean the Quarx kernel should work for us?
 
Last edited:

Zaaap72

Senior Member
May 2, 2012
311
321
Amberg
When try to compile kernel:

*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2

That's mean the Quarx kernel should work for us?

w7ds is an LG L90 dual sim.
Go to your kernel folder /arch/arm/configs and look for a g2m... ...defconfig where the name fits your device.

Try to compile with the g2m defconfig should work.

You might be missing touch and other hardware if you didn't get all property blobs needed for our device.

This is the point where I got struck at the moment.
 
  • Like
Reactions: Fikret488

partyzant_x

Senior Member
Sep 11, 2010
161
59
/tmp/ccfkEagn.s: Assembler messages:
/tmp/ccfkEagn.s:166: Warning: swp{b} use is deprecated for this architecture
/tmp/ccfkEagn.s:192: Warning: swp{b} use is deprecated for this architecture
CC arch/arm/mach-msm/smd_private.o
CC arch/arm/mach-msm/smem.o
CC arch/arm/mach-msm/smd_init_dt.o
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2

I'm try to compile the LG source with:
Run following scripts to build kernel
a) cd kernel
c) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage

Zaaap can you share your device tree?


Ok. I fixed the errors. Now I have "zImage" how flash that?
 
Last edited:

invaderjohn

Senior Member
Jun 12, 2009
640
421
What did you do to fix the errors? And wich toolchain did you use?

The zimage comes with some .ko files? You have to make a .zip file of those and flash it through custom recovery or a flash app from market! Like rashr
 

partyzant_x

Senior Member
Sep 11, 2010
161
59
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
 

Zaaap72

Senior Member
May 2, 2012
311
321
Amberg
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.

Don't flash the zImage as it is only a part of the needed boot.img.
There is a command like 'make boot.img'. I'll have to look for it.

I'll explain more later when I get to my laptop.
 
Last edited:
  • Like
Reactions: Fikret488

invaderjohn

Senior Member
Jun 12, 2009
640
421

partyzant_x

Senior Member
Sep 11, 2010
161
59
Now I'm trying to create a device tree manually. A bit of getting lost in this. Zaaap can share with your device tree. Rather than create new ones we can work on one and make any fixes.
 

invaderjohn

Senior Member
Jun 12, 2009
640
421
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.

where did you find the readme.txt where it said wich toolchain you should use?
 

partyzant_x

Senior Member
Sep 11, 2010
161
59

Give me: Error executing updater binary in zip.

Downloaded kernel source from lg site. Unpack it and there is two files readme.txt and packed kernel source, unpacked it copy kernel folder to cm source then cd kernel and:
make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage

When I have error for example:
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2

Then open smd_init_dt.c find line with smd_private.sh. Its look include <smd_private.sh> and change it to include "smd_private.sh".
Sorry for my English.
 

Zaaap72

Senior Member
May 2, 2012
311
321
Amberg
Make boot.img

Here you can find the official doc about making boot.img: HERE

I took the device tree from Quarx found here made a copy in a new folder 'd620' but i think 'g2m' would have been correct for phone.

Find my device folder here.
Find my vendor folder here.
The kernel source is located under kernel/lge/msm8226

I normaly compile a recovery and see if the kernel works with it.
Thus i don't risk a semi brick because if the kernel is bad, then recovery may not start but system will start and i can flash an other recovery with a new kernel.
If recovery boots, i can use adb to get dmesg.log and see what works and what not.
On my last try, touch didn't initialize complete.
 
Last edited:

partyzant_x

Senior Member
Sep 11, 2010
161
59
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
 

Attachments

  • zImage.zip
    6.7 MB · Views: 18

Zaaap72

Senior Member
May 2, 2012
311
321
Amberg
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.

It boot, but takes long to do so and there is no touch.
This is the same problem i have.
We need to get the correct touch firmware + patch.

Find log attached.
 

Attachments

  • dmesg.txt
    128 KB · Views: 18
Last edited:

Zaaap72

Senior Member
May 2, 2012
311
321
Amberg
Kernel boots with touch

Got touch working.

The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.

Now i will investigate how to include the FW in compile process.
 

partyzant_x

Senior Member
Sep 11, 2010
161
59
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
 
M

moonbutt74

Guest
Got touch working.

The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.

Now i will investigate how to include the FW in compile process.

Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.

okay so root is good
look in /proc for
/proc/config.gz
it might be there it might not. i need the stock boot.img please. looking through source right now and unsure of which defconfig.
your modules also depend on libraries in system/vendor - you need that entire directory for your device tree. you may also need
manufacturer/device specific/proprietary libraries from system/lib
starting in /system/vendor type in terminal
strings [nameoflib].so | grep "\.so"
these will bring up a list of additional libraires needed. the ones you already have in vendor don't worry about. the ones you
will find in system/lib are the additional ones you need to get for your device tree. go to the thread i'm working in with restl3ss and read through the whole thing but please do not post any questions there. post here use the mention function @moonbutt74
or pm me or click reply button below any of my posts in this thread and i will know by email.

m

on defconfig readme suggests w7ds_open_cis_defconfig but will try g2m_global_com_defconfig
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    CyanogenMod 11 for the LG G2 mini D620r

    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    All Credits so far go to Quarx and his project CM11 for LG L90

    What i have done so far:
    Setup Ubuntu on my Laptop
    Installed CM dev environment like described here!
    Made a new device folder following THIS guide and build some recoveries.
    Took the sources from CM11 for LG L90 and integrated them to my build environment.
    CM11 for LG L90 builds fine but i can not test it.
    Took the files i thought we need from L90 and put them to my d620 tree.
    Trial and error till it compiled for d620.
    For the kernel i use original LG sources extracted to kernel/lge/msm8226.
    Switched to kernel source from Quarx and tweaked it for d620.

    Find sources i use here.

    Unfortunately the kernel i have build leads to boot loops. (Yes i have wiped everything)
    If i only install the system with the original LG stock kernel i get an security error.
    How can i find out why the kernel boot loops?
    (had to use the dt.img from stock kernel because mine didn't work, phone gets stuck in fastboot)


    Kernel now boots with recovery.
    Touch only works if i copy the FW to system folder.
    CM11 now works quit well.

    Known issues:
    - NFC not working at all
    - Vibration not working at all
    - Back/Main camara has overexposure on bright scenes
    - LTE can only be activated by adding quick setting for LTE

    Testers welcome.
    Video review from simo14

    Alpha: Download

    attachment.php
    attachment.php


    Any help appreciated.
    7
    Git up to date.

    Updated my repositories on Github.

    To Do:
    Add all needed proprietary blobs. (proprietary-blobs.txt -> vendor)
    Try the change moonbutt74 suggested to get external SD-Card working.

    Alpha: cm-11-20140906-UNOFFICIAL-d620.zip
    ! Full wipe is needed for first install !
    Main/back camera not working.
    NFC not working.
    External SD not working.
    7
    Some news. CAF kernel for our phone with g2m defconfig compile with success. Now CM is building i hope everything goes ok.
    6
    Hey guys, I am updating the kernel with latest quarx (l90) commits, It may improve the camera and fix NFC
    5
    Hi everyone, i working on vibrator actualy =)