I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.
Hey, I really need help to realize some things about compiling rom from source.
I already read many posts about "how to", but none talks about it ... I already have the environment ready, I have done all the sync, however I want to compile android L. As we all know many kernels and device tree are still kk. I wonder how do I make the transition between kk for lollipop.
I have two manifests already sync : android-5.0.0_r2 from AOSP and android-5.0 from OMNI. Also have the device tree and kernel for my phone at kk.
Anyone knows how to do this "merging" ?
PLEASE, DO NOT ANSWER TO THIS THREAD ASKING FOR ETAS, DISCUSSION AND IDEAS ALIKE ARE WELCOME​Hey guys, I think we should start thinking about the G531F model, which does not have anything except TWRP. I am thinking about building CM12.1 for this phone, there are some limitations tho, we don't have enough sources.
What we do currently have:
-a device tree for building TWRP for Android 5.1 (probably incomplete and not suitable for building CM) https://github.com/dadziokPL/android_device_samsung_grandprimevelte
-kernel source from Samsung for Android 5.1 (I could not build it, faced several errors) https://github.com/dadziokPL/android_kernel_samsung_grandprimevelte
-some vendor stuff from Samsung and Marvell(the CPU manufacturer) http://opensource.samsung.com/
What do we need:
-a proper, fixed device tree
-fixed kernel source
-proper vendor files and proprietary blobs
I also got an unpacked stock ROM for this phone.
I am not very advanced in this stuff, I basically only know how to build ROMs, that's it. I need experienced developers to help me with this device. I have a plenty of time, a fast connection, a beefy PC and a secondary phone in case the Grand Prime gets bricked, so I can build and test.
dadziokPL said:
PLEASE, DO NOT ANSWER TO THIS THREAD ASKING FOR ETAS, DISCUSSION AND IDEAS ALIKE ARE WELCOME
Hey guys, I think we should start thinking about the G531F model, which does not have anything except TWRP. I am thinking about building CM12.1 for this phone, there are some limitations tho, we don't have enough sources.
What we do currently have:
-a device tree for building TWRP for Android 5.1 (probably incomplete and not suitable for building CM) https://github.com/TeamWin/android_device_samsung_grandprimevelte
-kernel source from Samsung for Android 5.1 (I could not build it, faced several errors) http://opensource.samsung.com/
-some vendor stuff from Samsung and Marvell(the CPU manufacturer) http://opensource.samsung.com/
What do we need:
-a proper, fixed device tree
-fixed kernel source
-proper vendor files and proprietary blobs
I also got an unpacked stock ROM for this phone.
I am not very advanced in this stuff, I basically only know how to build ROMs, that's it. I need experienced developers to help me with this device. I have a plenty of time, a fast connection, a beefy PC and a secondary phone in case the Grand Prime gets bricked, so I can build and test.
Click to expand...
Click to collapse
Any help from me build the rom we can test no worry of bricking your phone
chaudharyjatin115 said:
Any help from me build the rom we can test no worry of bricking your phone
Click to expand...
Click to collapse
Nah, I can do it by myself, I need someone to prepare all the code needed to build and fix any bugs, at this moment there's no chance for a successful build
Excuse me for this little off-topic, but it has TWRP with at least 1 bug reported by me at GitHub. Since this model has no maintainer, it would be nice to have this bug fixed. I know this has nothing to do with your post, but if you're a programmer, maybe you can do something... Thanks in advance.
Boblo said:
Excuse me for this little off-topic, but it has TWRP with at least 1 bug reported by me at GitHub. Since this model has no maintainer, it would be nice to have this bug fixed. I know this has nothing to do with your post, but if you're a programmer, maybe you can do something... Thanks in advance.
Click to expand...
Click to collapse
Sorry, I have no idea how to fix it. But I agree, this model deserves more maintainers, overall it needs more XDA love
dadziokPL said:
PLEASE, DO NOT ANSWER TO THIS THREAD ASKING FOR ETAS, DISCUSSION AND IDEAS ALIKE ARE WELCOME
Hey guys, I think we should start thinking about the G531F model, which does not have anything except TWRP. I am thinking about building CM12.1 for this phone, there are some limitations tho, we don't have enough sources.
What we do currently have:
-a device tree for building TWRP for Android 5.1 (probably incomplete and not suitable for building CM) https://github.com/TeamWin/android_device_samsung_grandprimevelte
-kernel source from Samsung for Android 5.1 (I could not build it, faced several errors) http://opensource.samsung.com/
-some vendor stuff from Samsung and Marvell(the CPU manufacturer) http://opensource.samsung.com/
What do we need:
-a proper, fixed device tree
-fixed kernel source
-proper vendor files and proprietary blobs
I also got an unpacked stock ROM for this phone.
I am not very advanced in this stuff, I basically only know how to build ROMs, that's it. I need experienced developers to help me with this device. I have a plenty of time, a fast connection, a beefy PC and a secondary phone in case the Grand Prime gets bricked, so I can build and test.
Click to expand...
Click to collapse
Hope this wil help to create device tree http://xda-university.com/as-a-developer/getting-started-building-android-from-source
---------- Post added at 11:41 AM ---------- Previous post was at 11:39 AM ----------
dadziokPL said:
PLEASE, DO NOT ANSWER TO THIS THREAD ASKING FOR ETAS, DISCUSSION AND IDEAS ALIKE ARE WELCOME
Hey guys, I think we should start thinking about the G531F model, which does not have anything except TWRP. I am thinking about building CM12.1 for this phone, there are some limitations tho, we don't have enough sources.
What we do currently have:
-a device tree for building TWRP for Android 5.1 (probably incomplete and not suitable for building CM) https://github.com/TeamWin/android_device_samsung_grandprimevelte
-kernel source from Samsung for Android 5.1 (I could not build it, faced several errors) http://opensource.samsung.com/
-some vendor stuff from Samsung and Marvell(the CPU manufacturer) http://opensource.samsung.com/
What do we need:
-a proper, fixed device tree
-fixed kernel source
-proper vendor files and proprietary blobs
I also got an unpacked stock ROM for this phone.
I am not very advanced in this stuff, I basically only know how to build ROMs, that's it. I need experienced developers to help me with this device. I have a plenty of time, a fast connection, a beefy PC and a secondary phone in case the Grand Prime gets bricked, so I can build and test.
Click to expand...
Click to collapse
Hope this can help you to create device tree http://xda-university.com/as-a-developer/getting-started-building-android-from-source
dadziokPL said:
PLEASE, DO NOT ANSWER TO THIS THREAD ASKING FOR ETAS, DISCUSSION AND IDEAS ALIKE ARE WELCOME
Hey guys, I think we should start thinking about the G531F model, which does not have anything except TWRP. I am thinking about building CM12.1 for this phone, there are some limitations tho, we don't have enough sources.
What we do currently have:
-a device tree for building TWRP for Android 5.1 (probably incomplete and not suitable for building CM) https://github.com/TeamWin/android_device_samsung_grandprimevelte
-kernel source from Samsung for Android 5.1 (I could not build it, faced several errors) http://opensource.samsung.com/
-some vendor stuff from Samsung and Marvell(the CPU manufacturer) http://opensource.samsung.com/
What do we need:
-a proper, fixed device tree
-fixed kernel source
-proper vendor files and proprietary blobs
I also got an unpacked stock ROM for this phone.
I am not very advanced in this stuff, I basically only know how to build ROMs, that's it. I need experienced developers to help me with this device. I have a plenty of time, a fast connection, a beefy PC and a secondary phone in case the Grand Prime gets bricked, so I can build and test.
Click to expand...
Click to collapse
Here is how to extract device tree files from stock roms
Which errors did you faced while compling kernel with source code
Only saw this today... Do you still need help building a kernel for G531F?
No instal root my divce
Plz help me sm-g531f is me root nhi ho rha hai. Sab root me ne chak keay hai pc par b or pc k begar b pr koi b root nhi rha mere moble me .
Koi friends betay ga kia maslaha hai.
Try this http://forum.xda-developers.com/showthread.php?t=3459748
Sent from my SM-G531F using Tapatalk
What about g530t ..That model needs some developing
Iamsanaullah said:
Plz help me sm-g531f is me root nhi ho rha hai. Sab root me ne chak keay hai pc par b or pc k begar b pr koi b root nhi rha mere moble me .
Koi friends betay ga kia maslaha hai.
Click to expand...
Click to collapse
Simple flash prerooted firmware with odin
Sent from my AO5510 using Tapatalk
I made a different thread in this forum, but it could be appropriate here. It's about making a ROM for one g530 variant work with another variant.
I am considering purchasing a Galaxy Grand Prime and the most likely model that I would purchase would be the SM-G530p or SM-G530t. While doing my research on this platform before purchasing I cannot help but notice that the majority of development and ROM releases overwhelmingly support the SM-G530h or SM-G531h.
What exactly is required to get an "H" ROM working on a "T" or "P" model? I am not exactly a noob when it comes to building android ROMs (I am a dev on androidforums.com and very active on freaktab) so your reply doesn't have to be too dumbed down. I am just unfamiliar with this platform. I have a sprint galaxy s4 (SPH-L720), however it seems like the ROM support is better for the various S4 than the various Grand Primes and this hasn't been an issue so far with my s4.
Would it not be possible to take any Grand Prime ROM (ex: an S7 ROM based on 5.1.1 ported for G530H), replace the kernel and supporting files with the 5.1.1 kernel including root for the G530P, flash it to the device, and have a functional ROM?
In general when flashing a custom ROM we won't be flashing the modem or radio partitions, correct? So as long as the android userland version matches the android version that the kernel is built for, and that kernel supports the installed baseband/radio/modem then won't this result in a functioning ROM?
Please let me know if I am incorrect, and if so where is the flaw in my logic!
Cheers and Thanks!!!
We need build instructions in order for people to more easily make custom roms. Currently most roms here only provide a repo or two, hardly describing the build process if anything. Not sure if those repos contain all the sources/blobs you need either.
It's not that hard to build and you can always go on th cheap and hire a cloud vps for a few hours, so don't bother with local building unless you have the powerful hardware.
Anyhow, so far what I know is that some people just replace the kernel and firmware, it seems this is called repacking.
Others are building Lineage from source as per their instructions, which are not descriptive when you're porting to a new device.
We need concrete and concise information about how it's done.
Lineage wiki is pretty accurate and if someone ask here I can try to solve his doubt.
I am not the best developer but I know the basics xD
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
randxor said:
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
Click to expand...
Click to collapse
Thats thanks to codeworkx code. Basically you compile a rom for zl1 and works for zl0.
My workflow is
repo init/sync the rom
Fix libhidl and libbfquio if needed (Dont know why they fix an error creating a bigger one tho)
Take the device tree, vendor and kernel
Adapt the device tree for the rom (Like in cosmic where config is in root not in config folder, boardconfig...)
And just brunch or make or lunch depends on rom xD
Edit: Forgot u need like 200 frameworks/av commits to make zoom work https://github.com/mosimchah/frameworks_av/commits/o8.1 all the january 15th and this one http://gerrit.aicp-rom.com/#/c/54436/
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
randxor said:
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
Click to expand...
Click to collapse
Yout init the rom source you want to compile
You dont need to adapt anything codeworkx already did it for us we just compile zl1 roms with his device tree (Los one) or any of the forked ones (Like Aicp which I recommend).
Libhidl and libbfquio depends on the rom you are building. Libhidl is solved by reverting this changes https://github.com/PixelExperience/system_libhidl/commit/607e961b85eea8969503d8ff8437c014f04f0ca2 and libbfquio by taking this http://gerrit.aicp-rom.com/#/c/56488/
You dont adapt device tree to device you adapt it to the rom you are compiling see how other devs do it in their github (Every rom is different for example in cosmic you rename lineage/aicp.mk to cos.mk and change where to import things)
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
Start by picking up a rom you want to compile that has 8.1 source working and better if a msm8996 device is there (zuk z2, oneplus 3...)
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
randxor said:
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
Click to expand...
Click to collapse
Np
Not sure dont know much about android kernels