PLEASE, DO NOT ANSWER TO THIS THREAD ASKING FOR ETAS, DISCUSSION AND IDEAS ALIKE ARE WELCOMEHey 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!!!
Related
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.
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
I'm trying to build cm12.1 custom rom for g531f but so far not good since i don't have much experience compiling...
Here are the files need for building custom roms like CM,AOSP etc. :
Device Tree(TWRP): github.com/TeamWin/android_device_samsung_grandprimevelte // Minimal device tree possibly only for recovery
Device Tree(MINE): drive.google.com/drive/folders/0B8TQ0igdaGTjUE53S1dDMDkwVTA?usp=sharing
Vendor Tree/Blobs(MINE): drive.google.com/drive/folders/0B8TQ0igdaGTjUE53S1dDMDkwVTA?usp=sharing
Kernel Source: opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G531F
Help for developers of g531f, most similar devices to g531f are X Cover 3(Same Specs) and Galaxy Tab 4 7.0(Most similar specs pxa1088 etc.)
I think the hardest part is now over,and that is to make all these files from scratch,now we need EXPERIENCED COMPILERS AND DEVELOPERS who know how to manipulate these files to work and to get successful build of CM or AOSP
PS. Keep in mind that i created these files in reference to our similar devices,so is most probable to need something removed or added and tweaked etc. this is just to jump start a development of roms for g531f
HIT THANKS IF YOU FOUND THIS POST HELPFUL OR USED MY SOURCE FILES
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
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Well, I have the same phone. Couldn't find ROMs for it.
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Click to expand...
Click to collapse
look in this forum here, there are a couple floating around for it, I've made one, that I was able to fully flash to mine and has touch (Android 10. there's another that is 11 on here too by another poster), but as there are multiple display options out there it seems for how they were made, that is the sticking point, as not all will behave properly when booted into a recovery like mode it seems. I have tried installing it over bootloader and it will have touch then, but when flashed to recovery the touch never activates properly. So it all likely comes to that, as we'll need combine them in, properly applying proper checks for each display type and having it use the proper driver files, since can't load them all at once or it breaks things.
Working shrp for Borneo
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
First place to start: twrpdtgen
Read the "readme"
Also check out:
[DEV]How to compile TWRP touch recovery
Device tree made from A10. Should still be relevant for A11.
Kernel for A10. Unfortunately I don't think Moto released the one for A11 yet. You can ask on their GitHub and devs might consider your request.
TWRP for A11. Touch is working.
Edit : here's a link for the device tree (in text) from A11
maybe this will work
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
maybe this will help probably https://github.com/MotorolaMobilityLLC/kernel-msm
UPDATE: I have a telegram account where we are discussing how to make a custom lineage OS. I'm at the gathering stage and in the process of porting a device tree. For starters I want to start with lineage OS 18 because its the same android version the stock OS is, to be on the safe side, and that I've never done ROMS before.
Moto G Power 2021
I now have a device tree with the help of AOSPdtgen from the stock ROM from mirrors.lolinet: https://github.com/thebestofall007/android_device_motorola_borneo
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
thebestofall007 said:
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
Click to expand...
Click to collapse
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
KILLFIREY1389 said:
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
Click to expand...
Click to collapse
The error turned out to be entries in the proprietary-files.text file that needed to be deleted.
@thebestofall007 If you'll suceed. please take in consideration to build \e\ (aka deGoogled Lineage) too.
Here's a couple of interesting links that may help:
https://doc.e.foundation/support-topics/build-e
https://community.e.foundation/t/howto-building-e-roms-a-beginners-guide/26371
Last but not least, we've also suggested them (check here) to setup a "build (V)Machine" by modding this colab notebook to made it device agnostic:
https://github.com/viam1-dev/colab_lineage_build
Hope can "inspire" you.
Thanks in advance.
Does anyone have a complete list of sources so far? I have some experience in the past building ROMs for Android 5 and I wouldn't mind trying. I have a lot of computer resources to dedicate to building as well.
Device tree: https://github.com/thebestofall007/android_device_motorola_borneo-old
Does anyone know if there is a kernel source? I looked on the Moto github and couldn't find one. Is everyone using prebuilt for the time being? Also, do we need a vendor tree?
Thanks