porting g-stylo 6.0 to the leon - LG Leon Questions & Answers

I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0

natediggler said:
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
Click to expand...
Click to collapse
Hey are you still working on this rom? i would like to know because i can try to help in any way if needed

Related

Could this be uses to root the samsung moment and other devices

maybe someone more linux savvy can check into this.
a search on our kernel version 2.6.27 thats on the moment brings up a website with a program for a local root vulnerability.
http://www.milw0rm.com/exploits/9545
not sure if it can be compiled for android... Just trying to help
I compiled it, and i am trying to get it to work but its running me into a brick wall. Its weird cause it works on my computer(full linux)... so Ill keep trying
Intresting indeed. I wish i could figure it out, but i dont know anything about linux.
there is some additional info over at ppc geeks here
http://forum.ppcgeeks.com/showthread.php?t=96237
Have you rewritten the x86 assembly instructions for ARM assembly? Also, I tried one of the milw0rm exploits on my Moment...seems they patched the kernel before the release.
I managed to discover a root exploit but its not the same as we are used to thanks to Samsungs stupid RFS aka FAT16 rom file system.
I'm nor knowledgable to make a rom, but hopefully this can be used to redo the rom in yffs2 so that it will work with existing apps, because even if we COULD keep root, stuff doesnt work, like nandroid, or Root Explorer.
http://www.samsungmomentforum.com/how-to/root-access-(finally-achieved!)/
I know many devs frequent xda and with zefie's root expliot maybe someone with the knowledge can create a rom for it in yffs2 using the source code samsung released.
Link: http://phandroid.com/2009/11/24/sprints-moment-open-source-released-by-samsung/

[Q] what is Kernel

Gents,
I need your help about "kernel", as I know when installing Android I need the folder named Android and the data.img.
But the kernel what is that?
Thanks for reading and more for helping.
The kernel is the core of the Android OS. Windows too runs on a kernel. Every build already includes one, and usually the most up-to-date or stable version, so you shouldn't have to worry about it, unless you want to update your kernel some time in the future.
I've been running Android for several months now and I've not updated the kernel once.
Still there is somthing to say
First I want to thank you for giving me some of your time.
The answer is clear, but why there is update always (now is 8.6)?
and what the kernel is including, is it the same of Android folder?
I hope I will find some more time.
Check out here for a bunch of explanations of terms that are commonly used around here
http://forum.xda-developers.com/showthread.php?t=852660&highlight=glossary
The reason that the kernels are updated alot is that the people who build the kernels find flaws in them through testing them, and through the feedback they recieve here on XDA.
Then they work to try and find ways to fix those flaws. Sometimes in fixing one flaw, a new one emerges. Generally it is a good idea to use the latest version of whatever kernel came with the build.

[Q] Is it possible to "upgrade" kernel version?

I still use my Nexus 4 happily and recently started modding the kernel a bit.
This led me to the question in the first hand, because it is possible to upgrade minor versions (3.4.0 -> 3.4.105)
The thing is, N4 uses google_msm 3.4 sources
shamu is pretty new, uses google_msm too but 3.10
I've tried by bluntly downloading shamu's kernel source, placing mako_defconfig in arch/arm/configs and updating the defconfig with make menuconfig.
As expected didn't work out, but i'm just a little modder cherry-picking stuff i'd like to have, so in reality i have no clue how to archieve that, or if it is even possible with some modifications.
I've also tried with the standard 3.18 Linux kernel too before, but got the same expected result.
Did someone actually tried this and got a bit further, is this something simply not posiible or too much work to get it going?

[Q] AOSP/CM on G935F

Hi, I'm kind new in creating stuff for my phones but I want to give a try and bring CM/AOSP (I know that they are totally different things) to our phones.
I've done a research and all that I found was that it wasn't possible because we haven't the kernel source. But now that it is available in the Samsumg Open Source page could we make that possible?
Thanks a lot!!
If u really did the research, u should know someone had made this before but unable to call success....
http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
pigmich said:
If u really did the research, u should know someone had made this before but unable to call success....
http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
Click to expand...
Click to collapse
Yes, i did read that, but everything i found was this:
In the case of the S7/S7E because the SOC is either closed source (Exynos) or has a locked bootloader (Qualcomm). The former makes it very difficult to produce a Rom that approaches anything near being stable, the latter makes it literally impossible until the bootloader is unlocked, which is unlikely to happen.
Click to expand...
Click to collapse
But I can't understand why if we already got the kernel source. Can't we just modify the kernel to make a kind of "mask" that allows the ROM to use the hardware correctly?
Maybe I'm asking something really stupid, and if thats the case I'm sorry, but I really want to know why we fail in this and see if I can find a workaround
Start here: http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
Get the source, make a local_manifest.xml file, get the rest of the source, edit the source code and build a rom .
But before You try, I can already tell You that it will be extremely hard to do. I've got CM to compile (yeah, compiling is actually a HUGE step) on other devices and then eventually to boot. But it took couple of days of code fixing (which I at this point somehow understand but it's still quite a magic for me).
Couple of days ago I tried building CM 13 and 14 for S7 Edge and after a whole day of fixing code and stuff I gave up. The worst issues are "shared library, excludes, includes" thingys.

Port of lineageOS

Hello Guys,
Today I woke up with a new idea; I want to port LineageOS to the LG V20 version H990DS. I was tinkering with this idea for about one year, but never actually wanted to make the step. Until today. I used LineageOS and CyanogenMod since 2012.
The reason why I want to create the first port is because I have the time at the moment, so why not help the community? I do have four years of programming skills C/C++. Run Linux as daily driver etc... Do know how to use git, linux, autotools etc... The tricky part however is: I never compiled a Lineage OS rom from source and I don't think the compiling would be a problem, but the LG V20 H990DS isn't officially supported. My question is: Where do I start to program? How can I compile and build a working Lineage OS for the LG H990DS. Are there any good website I can read from?
I saw this:
https://www.youtube.com/watch?v=MGI3NSJFtKA&feature=youtu.be
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
https://www.reddit.com/r/LineageOS/comments/6iie9l/how_to_compile_lineage_os_141_for_unsupported/
https://www.reddit.com/r/LineageOS/comments/684qkp/help_noob_compile_lineageos/
So to make it easy: I want to program a working LineageOS for the LG H990DS, but don't have any understanding about where to start. I do have four years of programming skills, not so much, but know C and C++ well.
Thanks in advance,
Maurice
English isn't my native language, sorry for grammars.
someone help this man up.
Did you check the existing LineageOS thread?
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/post74550386#post74550386
If you want to help, I'd suggest asking him if there's anything you can do.
Thank you for your response. I do watch that thread, because I want lineageOS for the h990ds device. The problem however is that I don't want to jump right into the code. I want to know what I am doing with each line of code. At the moment I think I have to change some things in the kernel so that it can boot, but I don't know if that's true. And there is so many documentation about how to compile lineageOS, which I don't want to do. I want to program and compile lineageOS. Every tutorial skips the program parts and just compiles lineageOS.
So maybe a good programmer can give my some advice? Where to start and where can I find some documentation?
Best regards,
Maurice
Welcome!
First off, I recommend using Ubuntu 16.04 (I personally use 16.10 however). Be sure to follow the guide you linked from chef central carefully.
For the dual SIM variant, I don't believe any current source exists. Although with the similar hardware and if you have decent skills, you could get it going.
Take a look at the existing v20 trees:
V20-common: https://github.com/LineageOS/android_device_lge_v20-common
Msm8996-common: https://github.com/LineageOS/android_device_lge_msm8996-common
H918 (as a reference): https://github.com/LineageOS/android_device_lge_h918
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8996
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Those are the basics to check out. Now I did see someone converted the H918 tree to H990. Here's a link to that for reference: https://github.com/android-device-lge-h990/android_device_lge_h990
You will definitely need to make a custom defconfig in kernel sources. The device tree changes should be rather easy. You'll need to pull vendor files from stock and import the drivers and dts files from stock kernel source. If/when you get a working kernel and device trees there's a 99% chance you will need to Port other drivers and vendor files as stock files don't play nice in aosp. If I were you, I'd start looking through commit history on GitHub to see how the other devices we're brought up. That is how I learned everything.
Also, git will be your best friend when bringing up large projects, like kernel. Learn git, get comfortable with it. Cherry-picking and merging is what keeps us going.
Best of luck!
I suppose you could say there are dueling work-in-progress H990 trees since the other one is: https://github.com/x86cpu/android_device_lge_h990
The one you pointed to is mine. I was hoping for some collaboration with @x86cpu on there (in theory @x86cpu also has permissions to modify that repository, assuming I've set things up correctly). While the initial steps have been done, it is not finished! Some issues are left for getting LineageOS operational on H990 devices.
Of crucial note the modem fix in its current form is unacceptable to LineageOS (despite working). I've got two variants of one solution almost ready, but they're yet ready.
Thank you for your answer and I will look into it. I sure hope that I can help you some day, but first I want to understand the repository. After that I will help you both to code.
Really thank you and I will do my best to catch up with you.
As for the Ubuntu version. I personally use arch Linux (with plasma), because I like it more than Ubuntu. I don't think that's a problem and else I will compile the Ubuntu programs to arch. And I know my way around got. Use it for about 4 years now and now what merging/branching rebasing etc means and know how to use it.
@emdroidle I could help

Categories

Resources