Database Users

kernel ics

there is' someone who can compile a kernel for beta ics Andrew Garen?

There wont be any custom kernels for those roms till there's source code for ICS
Sent from my Google Nexus S 4G using xda premium

True. "Compiling" is referring to compiling source. As soon as we get source code....we're golden.

You could take the boot.img and unpack it to make minor tweaks but not nearly enough. The real quality tweaks reside in the zImage binary.
A boot.img consists of two major parts;
1. Ramdisk
2. zImage (binary)

Who's Andrew Garen?

Has been the ICS kernel already released? If yes, could please provide the link to the downloading page or git repository, I need to recompile a custom one.

adaimespechip said:
Who's Andrew Garen?
Click to expand...
Click to collapse
He's a dev. His roms work awesome. You should chcek it out. www.drewgaren.com

jlanza said:
Has been the ICS kernel already released? If yes, could please provide the link to the downloading page or git repository, I need to recompile a custom one.
Click to expand...
Click to collapse
It is not.

jlanza said:
Has been the ICS kernel already released? If yes, could please provide the link to the downloading page or git repository, I need to recompile a custom one.
Click to expand...
Click to collapse
I think that the matr1x kernel v11.5 should work on drew garens icy! do a backup and try!
Sent from my Nexus S using XDA App

[REQUEST] N8000 Kernel Source

I am about to build a kernel for N8000. But my problem is I can not download from samsung open source site (Very Slow Connection).
Can someone please mirror the update7(MD1) for me on a fast server like dev-host, android file host, mediafire or etc...?
Here's the Samsung open source site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8000
Thanks in advance.

You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.

kcrudup said:
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
Click to expand...
Click to collapse
Thanks.
I have two questions if you don't mind.
1. Merge-to-ss-jb is the latest source (MD1)? Is it a good to go for a kernel to be based upon?
2. Is it alright with you that I base my kernel on your own kernel?
I appreciate it if you can help me with some kernel stuff as I am new to this.
Sent from my HTC One X using Tapatalk 4 Beta

csec said:
"merge-to-ss-jb" is the latest source (MD1)?
Click to expand...
Click to collapse
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Is it alright with you that I base my kernel on your own kernel?
Click to expand...
Click to collapse
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.

kcrudup said:
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
Click to expand...
Click to collapse
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD

csec said:
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Heard that the published sources have different wi-fi drivers than preinstalled stock kernel.
This is the main reason of allshare cast not working with custom kernels (on the contrary, some s3 custom kernels DO SUPPORT allshare cast), even if status=official and flash counter=0.
Anyone can confirm?
Anyone has the proper ones or know which one (i.e. from a different samsung device) to use?

gitHub link dead

LG uploaded V500 kitkat kernel source today!

https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv500
Is where you can get it (start your downloading now...)
the strange thing is they appear to have two uploads for kitkat...
Sent from my LG-V500 using XDA Premium HD app

Yay! What does it mean for the simple user? Better roms?
Sent from my iPhone using Tapatalk

All I really want is gamma correction and maybe overclocking and U/V.

This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M

muiriddin said:
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
Click to expand...
Click to collapse
The first and most obvious is the gamma set at 2.05 roughly. If you set it to 2.2 - 2.3, that would already be a big plus.

The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk

id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Good to hear that someone else contacted them as well. I have been impressed with their open source group responding as quickly as they did. They definitely respond better than several other companies when facing these requests!

:good::good: I would pay anybody to incorporate or activate the OTG+Charging in this Kernel. :good::good: :fingers-crossed:

id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.

LBJM said:
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
Click to expand...
Click to collapse
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think

I compiled a kernel using the source provided by LG, but for some reason, it doesn't boot.
I keep getting this error:
Code:
Secure booting error
Cause: boot certification verify
I noticed that the resulting "boot.emmc.win" is a lot smaller than the original boot.emmc.win (~10 MB compared to 24MB)
Another interesting thing is that if I uncompress the original 24 MB boot.emmc.win using the command "unmkbootimg -i boot.emmc.win", I get two files: kernel (7.5 MB) and ramdisk.cpio.gz (2.6 MB). If I rebuild the boot.emmc.win using these exact two files, I get an 11MB boot.emmc.win, but this one DOES boot.
It probably has something to do with the locked bootloader and the loki exploit.
Can anyone help me get to the bottom of this? I really want to solve the gamma issue.

Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.

Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk

ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Canadoc said:
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Panel is very close to correct gamma when using default linear qlut, instead of MSM_MIPI_LGIT_VIDEO_WUXGA_PT_PANEL qlut.

I would definitely take a look at the 50018A kernel if someone can provide the source. I wasn't able to find it.

gin_silver said:
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
Click to expand...
Click to collapse
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.

LBJM said:
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
Click to expand...
Click to collapse
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996

gin_silver said:
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
Click to expand...
Click to collapse
Good to know.

20d source released
I do not know if anyone will find this of use, but they have now posted the 20d kernel source (and some other stuff).
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500

ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello ruxandy,
Can you explain in few words how did you manage to push the kernel to your v500?
Here is my story:
I downloaded the V500 Lollipop kernel because I wanted to compile .ko loadable modules and drivers to support RTL2832U DVB USB dongle. I successfully compiled those modules, rooted the tabled and tried to insmod them. But it failed because the modules did not find some kernel APIs.
Then I decided to build the kernel with built-in those drivers and I did it successfully, the problem now is what to do with zImage. I read there are two roads the one building own KDZ file seems very complicated and not sure if really possible. The other seems to be to extract the boot.emmc.win file using TWRP. So I downgraded the V500 bootloader from LT to KK and installed TWRT using this http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846 but after reboot got the secure boot error you did.
So again - how to use self built zImage and is this possible for KitKat only, since installing TWRP with Lollipop does not seem possible so far?

CyanogenMod for Pixel v1

FIRST TEST BUILD OUT
Since the MTK variants in the second gen Android One devices have steadfastly been ignored for development, I have taken it upon me to ensure that there is no dearth of top-of-the-line trees for any brave person wanting to build for this device. Here are my sources :
Device Tree : https://github.com/MSF-Jarvis/android_device_google_seedmtk
Common Tree (necessary) : https://github.com/MSF-Jarvis/android_device_google_sprout-common
Kernel Source (untested) : [url]https://github.com/MSF-Jarvis/android_kernel_mediatek_sprout[/URL]
Vendor Tree : https://github.com/MSF-Jarvis/proprietary_vendor_google_seedmtk-2ndgen
NOTE TO TESTERS : Please try getting logcats for me since it is IMPOSSIBLE to do anything without even knowing why something is broken

MSF Jarvis said:
Since the MTK variants in the second gen Android One devices have steadfastly been ignored for development, I have taken it upon me to ensure that there is no dearth of top-of-the-line trees for any brave person wanting to build for this device. Here are my sources :
Device Tree : https://github.com/MSF-Jarvis/android_device_mediatek_sprout
Common Tree (necessary) : https://github.com/MSF-Jarvis/android_device_google_sprout-common
Kernel Source (untested) : https://github.com/MSF-Jarvis/android_kernel_mediatek_sprout
Vendor Tree : https://github.com/MSF-Jarvis/proprietary_vendor_google_sprout-2ndgen
I am currently negotiating for a server with one of my dear friends, and will commence builds as soon as I can wrangle one out from him
Everyone is welcome to help me out with this project. I tried getting @DHARMESH17 onto it but apparently it seems he's not very interested or dedicated to the cause.
And oh, almost forgot, here's a local manifest to prevent manually cloning things : https://github.com/TeamRedux/local_manifests/tree/cm-13.0-sprout
Click to expand...
Click to collapse
Bro I am completely interested in it but because of some barriers I was unable to continue the project but now I am completely feee and start development on rom

DHARMESH17 said:
Bro I am completely interested in it but because of some barriers I was unable to continue the project but now I am completely feee and start development on rom
Click to expand...
Click to collapse
I would like some proof of your ability with ROM compiling before I let you in on my server.

Ashiron said:
Give me full details.
Start to end.
100% success result
??
Click to expand...
Click to collapse
Details as in??

The kernel source has been imported to my Github and I have also set-up Continuous Integration on it through Travis-CI, build progress can be tracked here.
I would like to thank @akhilnarang whose ThugLife scripts have been used to compile the kernel inside the CI. I couldn't include your name in the commits, but the original copyright notice has been retained in the spirit of open source.

I have been informed through Google Plus that @DHARMESH17 has been in the hospital for some time now, and @faddat is currently in China, so the project has been put on hold for now.

Work will begin tomorrow

You can get the stock source to boot on pixel?
A friend of mine has tried, it dosen't boot

akhilnarang said:
You can get the stock source to boot on pixel?
A friend of mine has tried, it dosen't boot
Click to expand...
Click to collapse
Kernel source? Of course not, I believe it's specific to the first gen sprout devices, as I found out earlier this day. I guess I'll have to end up messing with the device tree and see if I can sneak in a prebuilt kernel somewhere inside. One query though, since you've made an appearance, if I use a custombootimg.mk for userdebug builds, will it prepare the boot.img as per the recipe given there? Because as TWRP maintainer for the htc pico, I have to force it to use LZMA compression for the ramdisk to make it fit, and for that I set a ifeq into the boardconfig to use the customrecoveryimg.mk I put in the device tree, if build variant is eng. If it will work on boot.img and userdebug, then I may very well be able to fool CM's build system and use a prebuilt kernel.
If I'm not making myself clear, please do hop on to #team-redux on freenode and we'll discuss it at length and hopefully arrive at a solution

MSF Jarvis said:
Kernel source? Of course not, I believe it's specific to the first gen sprout devices, as I found out earlier this day. I guess I'll have to end up messing with the device tree and see if I can sneak in a prebuilt kernel somewhere inside. One query though, since you've made an appearance, if I use a custombootimg.mk for userdebug builds, will it prepare the boot.img as per the recipe given there? Because as TWRP maintainer for the htc pico, I have to force it to use LZMA compression for the ramdisk to make it fit, and for that I set a ifeq into the boardconfig to use the customrecoveryimg.mk I put in the device tree, if build variant is eng. If it will work on boot.img and userdebug, then I may very well be able to fool CM's build system and use a prebuilt kernel.
If I'm not making myself clear, please do hop on to #team-redux on freenode and we'll discuss it at length and hopefully arrive at a solution
Click to expand...
Click to collapse
No need of fooling any system, you can happily use a prebuilt kernel as it is to build CM

akhilnarang said:
No need of fooling any system, you can happily use a prebuilt kernel as it is to build CM
Click to expand...
Click to collapse
Go ahead and try

MSF Jarvis said:
Go ahead and try
Click to expand...
Click to collapse
I have, and I often use a prebuilt kernel, no issues. What do you get?
Sent from my Nexus 5X using XDA-Developers mobile app

akhilnarang said:
I have, and I often use a prebuilt kernel, no issues. What do you get?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
AOSP based ROMs are a different story, CyanogenMod raises this exception when you try using a prebuilt kernel :
```
Using a prebuilt kernel is deprecated and not allowed
Please add your kernel source to your BoardConfig.mk
```
Or something to that tune, been months since I ran a compile for any ROM(Server's late in coming, @faddat is a busy man )

I have got a server now, and will commence builds tomorrow. Stay tuned!

MSF Jarvis said:
AOSP based ROMs are a different story, CyanogenMod raises this exception when you try using a prebuilt kernel :
```
Using a prebuilt kernel is deprecated and not allowed
Please add your kernel source to your BoardConfig.mk
```
Or something to that tune, been months since I ran a compile for any ROM(Server's late in coming, @faddat is a busy man )
Click to expand...
Click to collapse
It still builds, as long as you've specified the PRODUCT_COPY_FILE properly
Anyway, why did you base your trees on the old cm-12.1 trees of Varun
If you're trying cm-13.0 then base on the latest cm-13.0 from CyanogenMod GitHub
Sent from my Nexus 5X using XDA-Developers mobile app

akhilnarang said:
It still builds, as long as you've specified the PRODUCT_COPY_FILE properly
Anyway, why did you base your trees on the old cm-12.1 trees of Varun
If you're trying cm-13.0 then base on the latest cm-13.0 from CyanogenMod GitHub
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I realised that earlier today, so I rebased my updates onto the snapshot trees and pushed it to my Github. The local manifest has been updated with the new branch as well.
About the prebuilt kernel, you use PRODUCT_COPY_FILES for copying the zImage ?? @thewisenerd once mentioned its a terribly ****ty idea, but you're more updated regarding building and ****, so I'll take your word. Just a quick query, what'll be the out location of the kernel? ($OUT/kernel ??)

MSF Jarvis said:
I realised that earlier today, so I rebased my updates onto the snapshot trees and pushed it to my Github. The local manifest has been updated with the new branch as well.
About the prebuilt kernel, you use PRODUCT_COPY_FILES for copying the zImage ?? @thewisenerd once mentioned its a terribly ****ty idea, but you're more updated regarding building and ****, so I'll take your word. Just a quick query, what'll be the out location of the kernel? ($OUT/kernel ??)
Click to expand...
Click to collapse
Yep
Code:
PRODUCT_COPY_FILES := $(LOCAL_PATH)/kernel:kernel
Sent from my Nexus 5X using XDA-Developers mobile app

@akhilnarang, you free some night? I'll be needing help as far as I can see.
Anyways, ever had a problem with cts/apps/ctsVerifier throwing exceptions? My build refuses to start! Not to mention that repo is also being very hard on me, not syncing projects, throwing exceptions while unpacking and ****. Gonna rebase to nightly level, currently on snapshot 1.

Official TWRP now available : http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364

MSF Jarvis said:
I would like some proof of your ability with ROM compiling before I let you in on my server.
Click to expand...
Click to collapse
Bro still want proof LoL ??

Building Cyanogenmod

Hi there,
Having seen that this device is gaining popularity in the Southeast Asian region, I have taken the time to start an unofficial development of CM for this device. Right now, having gotten the kernel to build but without the device I won't be able to extract the required blobs and such to start a device tree. So I'm asking here if you guys wanted to help and extract the blobs using the method here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Build a device tree based on @hondajohn88 repo and right now doing changes to it to support CM.
https://github.com/webhaikal/android_device_leeco_zl1
You can use this for Method 1 in the porting intro: https://www.androidfilehost.com/?fid=529152257862684212. You either need a Linux distro or Ubuntu Bash on Windows..
Here's the kernel I build: https://www.androidfilehost.com/?fid=529152257862684239
As I don't have the financials to actually buy the device, that's why I'm asking here...
Thank you..

I really don't know anything about building ROMs, but reading method 1 all you need is boot.img?

Hi, me, @hondajohn88 and someone else are working on a source build. Please dig in github for device tree and so on.
Let's keep in touch!
edit: checked updater script and it is referred to Xiaomi device (ferrari). Is that ok?

haikalizz said:
Hi there,
Having seen that this device is gaining popularity in the Southeast Asian region, I have taken the time to start an unofficial development of CM for this device. Right now, having gotten the kernel to build but without the device I won't be able to extract the required blobs and such to start a device tree. So I'm asking here if you guys wanted to help and extract the blobs using the method here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
You can use this for Method 1 in the porting intro: https://www.androidfilehost.com/?fid=529152257862684212. You either need a Linux distro or Ubuntu Bash on Windows..
Here's the kernel I build: https://www.androidfilehost.com/?fid=529152257862684239
As I don't have the financials to actually buy the device, that's why I'm asking here...
Thank you..
Click to expand...
Click to collapse
Check out my vendor repo on git hub. It has most of the blobs but I haven't added the rest. I might be able to do that later today.
https://github.com/hondajohn88

hondajohn88 said:
Check out my vendor repo on git hub. It has most of the blobs but I haven't added the rest. I might be able to do that later today.
https://github.com/hondajohn88
Click to expand...
Click to collapse
Question, your device tree is based on Kenzo? Or is the specsheet not updated?

haikalizz said:
Question, your device tree is based on Kenzo? Or is the specsheet not updated?
Click to expand...
Click to collapse
Sorry about that, yes, the spec sheet not updated.
Later this evening I'll try to get everything I have updated to git, but what's there now is a decent start (my first commit, so there are a few changes)

hondajohn88 said:
Sorry about that, yes, the spec sheet not updated.
Later this evening I'll try to get everything I have updated to git, but what's there now is a decent start (my first commit, so there are a few changes)
Click to expand...
Click to collapse
One thing when building the kernel, there are a few includes that needs to be fixed. The commit that fixes it can be found on marlin (Google Pixel) kernel on Cyanogenmod github...

http://opensource.le.com

haikalizz said:
One thing when building the kernel, there are a few includes that needs to be fixed. The commit that fixes it can be found on marlin (Google Pixel) kernel on Cyanogenmod github...
Click to expand...
Click to collapse
Ah, thanks...I've been having issues with that Damn thing. I'll look into it, thank you

Flounderist said:
Hi, me, @hondajohn88 and someone else are working on a source build. Please dig in github for device tree and so on.
Let's keep in touch!
edit: checked updater script and it is referred to Xiaomi device (ferrari). Is that ok?
Click to expand...
Click to collapse
Yikes, updater script in my repo? Sigh, so much to look into...
Time for beer.

I think using a device that has a SD821 would be a better starting point than kenzo.

Flounderist said:
Hi, me, @hondajohn88 and someone else are working on a source build. Please dig in github for device tree and so on.
Let's keep in touch!
edit: checked updater script and it is referred to Xiaomi device (ferrari). Is that ok?
Click to expand...
Click to collapse
Oops forgot about the updater script.. Whats the device codename? ZL1?

haikalizz said:
Whats the device codename? ZL1?
Click to expand...
Click to collapse
I'm not sure about the codename. I think it's "le_zl1" at least this is what "ro.build.product" contains. Here some relevant properties from my LEX720 (the chinese version which has dual-sim):
Code:
[ro.build.product]: [le_zl1]
[ro.config.product]: [le_zl1]
[ro.product.device]: [le_zl1]
[ro.product.model]: [LEX720]
[ro.product.name]: [ZL1_CN]
[ro.bootimage.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.description]: [le_zl1-user 6.0.1 WAXCNFN5801811012S eng.letv.20161101.120034 release-keys]
[ro.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.display.id]: [WAXCNFN5801811012S release-keys]

androcheck said:
I'm not sure about the codename. I think it's "le_zl1" at least this is what "ro.build.product" contains. Here some relevant properties from my LEX720 (the chinese version which has dual-sim):
Code:
[ro.build.product]: [le_zl1]
[ro.config.product]: [le_zl1]
[ro.product.device]: [le_zl1]
[ro.product.model]: [LEX720]
[ro.product.name]: [ZL1_CN]
[ro.bootimage.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.description]: [le_zl1-user 6.0.1 WAXCNFN5801811012S eng.letv.20161101.120034 release-keys]
[ro.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.display.id]: [WAXCNFN5801811012S release-keys]
Click to expand...
Click to collapse
Could you extract a boot.img too? Alot of info could be extracted from it too...

goroflack said:
I think using a device that has a SD821 would be a better starting point than kenzo.
Click to expand...
Click to collapse
I agree, and I have since changed to using some of oneplus3. I hadn't changed the device spec on my repo, but merged the change given to me by @haikalizz.
Mostly I was using the Kenzo files as a template, but changed it up a short while after.
Thanks

haikalizz said:
Could you extract a boot.img too?
Click to expand...
Click to collapse
Yes, of course. This is the original unmodified boot.img of the chinese LEX720 model running the latest EUI version for the chinese model (5.8.018S). Note that for the US version there is already a newer release (5.8.019S).
I uploaded it here to my server: WAXCNFN5801811012S_boot.img

the lastest cho x720 is eui 5.9 20s which available from
http://bbs.ydss.cn/thread-714235-1-1.html

moneyrain said:
the lastest cho x720 is eui 4.9 20s which available from
http://bbs.ydss.cn/thread-714235-1-1.html
Click to expand...
Click to collapse
This is a custom release. Is there also somewhere an unmodified official download to look into? The OTA server still responds with version 018S for my device:
Click here for OTA Check
You have to replace the XXXXXX.. with your actual IMEI (and maybe also model and product) to get a response from this server.

im downloading the package. I will flash this build for test ( x720 is my 2nd phone )

moneyrain said:
im downloading the package. I will flash this build for test ( x720 is my 2nd phone )
Click to expand...
Click to collapse
Please, can you upload this ROM with download link?
Sent from my LEX720 using Tapatalk