Some Questions about Compiling Cyanogenmod 13 - Android Q&A, Help & Troubleshooting

I am a newbie to android development and want to clear out my some confusion about compiling ROM as I am compiling ROM for first time. Your assistance will be appreciated.
Q1. Well. I run the repo sync command and at last, after 100% fetching project done , I got an error as " error: .repo/repo/: contains uncommitted changes"
What does it means? why it occurs and how to fix it ?
Q2. What is local_manifest ? I am compiling for a unsupported device (Micromax Q370), so do I have to create a local manifest by myself ? If yes, then how ?
Q3. What is device tree ? How to make it ?
Hire to extract device specific codes from my device using adb ?
Q4.
Q5.
Q6. How to choose a target ? What target means ? Is it my device (Micromax Bolt Q370) ? or something else ?
Can someone explain these guides reffered in android.com ? =
" Choose which target to build with lunch. The exact configuration can be passed as an argument. For example, the following command:
$ lunch aosp_arm-eng
refers to a complete build for the emulator, with all debugging enabled.
If run with no arguments lunch will prompt you to choose a target from the menu.
(When I type lunch, terminal prompt me to install" sudo apt install python-lunch") "
I am compiling CM13 for my device Micromax Q370, its not an emulator, so what I have to type instead of $ lunch aosp_arm-eng ? What are BUILDTYPES anyway ?
And what lunch does ?
Q7. What will happen if I type
$ make -j4
Will it start compiling the ROM ?
Well. These are my confusion. I know these are very nooby question but I am new to android development without any prior programming language knowledge and want to learn it. I hope someone will help me out. Thank you for reading my thread. Waiting for your help. Have a good day.
Q.4 and Q.5 are removed as I understood what those things are.

@sudharshankakoty I'm pretty much sure that you've MTK chipset based device. I tried to search online but the chip isn't mentioned anywhere. Download CPU Z nd post the screenshots here from all of the tabs. I'm afraid that if it's MTK based then you cannot do any further development except to port the roms. Only if there are roms for that chipset.

Has.007 said:
@sudharshankakoty I'm pretty much sure that you've MTK chipset based device. I tried to search online but the chip isn't mentioned anywhere. Download CPU Z nd post the screenshots here from all of the tabs. I'm afraid that if it's MTK based then you cannot do any further development except to port the roms. Only if there are roms for that chipset.
Click to expand...
Click to collapse
Nope, I am at Spreadtrum Chipset. My device details are here https://www.dropbox.com/s/pwpgo7muawmekwf/Device Details.zip?dl=0
Well, I got a lollipop rom of same chipset and android version, and I tried replacing the system/lib folder from base to port rom with setting the correct mount points of my device in updater-script .
But when I tried to flash, it says error executing updater binary in zip (TWRP)

Sudarshankakoty said:
Nope, I am at Spreadtrum Chipset. My device details are here https://www.dropbox.com/s/pwpgo7muawmekwf/Device Details.zip?dl=0
Well, I got a lollipop rom of same chipset and android version, and I tried replacing the system/lib folder from base to port rom with setting the correct mount points of my device in updater-script .
But when I tried to flash, it says error executing updater binary in zip (TWRP)
Click to expand...
Click to collapse
Okay so I checked the details. The problem is that you can't build the ROMs for this device. As far as I know Spreadtrum doesn't release the souce code. What status error did you get? 7? Give me the link of TWRP built for your device nd also the ROM you're trying to port.

Has.007 said:
Okay so I checked the details. The problem is that you can't build the ROMs for this device. As far as I know Spreadtrum doesn't release the souce code. What status error did you get? 7? Give me the link of TWRP built for your device nd also the ROM you're trying to port.
Click to expand...
Click to collapse
TWRP for my device : https://drive.google.com/file/d/0B377TLFOgWdsTExNTFIza1BCckE/view?usp=docslist_api
ROM trying to port : https://drive.google.com/file/d/0B6a7A5E8IzscdjNSRzRBSWZLZzg/view?usp=drivesdk

Sudarshankakoty said:
TWRP for my device : https://drive.google.com/file/d/0B377TLFOgWdsTExNTFIza1BCckE/view?usp=docslist_api
ROM trying to port : https://drive.google.com/file/d/0B6a7A5E8IzscdjNSRzRBSWZLZzg/view?usp=drivesdk
Click to expand...
Click to collapse
Error while flashing ROM : when I tried to flash, it says error executing updater binary in zip (TWRP)
Mount points of my device attached here.

@sudharshankakoty Sorry for replying, missed your notification. I want the source pages for this TWRP nd the ROM so I could see the details. Here is a guide to build device tree I haven't seen this video but it might help you:
https://www.youtube.com/watch?v=Uw_caMHZRC4
About the error, probably it is because of the mount points or the asserts.

Has.007 said:
@sudharshankakoty Sorry for replying, missed your notification. I want the source pages for this TWRP nd the ROM so I could see the details. Here is a guide to build device tree I haven't seen this video but it might help you:
About the error, probably it is because of the mount points or the asserts.
Click to expand...
Click to collapse
Well, somehow, I could managed to extract the device tree from boot.img file. But the problem is I am unable to make the recovery image, getting an make error... ********************************************************** Kernel source found, but no configuration was defined Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file *********************************

Sudarshankakoty said:
Well, somehow, I could managed to extract the device tree from boot.img file. But the problem is I am unable to make the recovery image, getting an make error... ********************************************************** Kernel source found, but no configuration was defined Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file *********************************
Click to expand...
Click to collapse
You can try to get help from @doesntexits He developed for Speadtrum device so he might be able to help you.

Has.007 said:
You can try to get help from @doesntexits He developed for Speadtrum device so he might be able to help you.
Click to expand...
Click to collapse
None of the CyanogenMod he developed is for sc7731 chipset

Sudarshankakoty said:
None of the CyanogenMod he developed is for sc7731 chipset
Click to expand...
Click to collapse
That's right but it is for sc device so it would be easy for him to at least have a kickstart. You even might be able to build tree by using his sources. Obviously it needs a lot of experience.

Has.007 said:
That's right but it is for sc device so it would be easy for him to at least have a kickstart. You even might be able to build tree by using his sources. Obviously it needs a lot of experience.
Click to expand...
Click to collapse
Ya. That's right, well I own my device tree, I need kernel sources actually. OK, let's contact him and will ask for some assistance. ☺

Has.007 said:
That's right but it is for sc device so it would be easy for him to at least have a kickstart. You even might be able to build tree by using his sources. Obviously it needs a lot of experience.
Click to expand...
Click to collapse
I am currently running a custom Android 5.1 ROM with almost stable state, by porting myself. It includes many features including CM Theme Chooser/Engine. Only bug is Auto-Rotation is not working. I am using stock boot.img so I need to port the kernel for this. Occasionally after porting the kernel, and flashing through TWRP, Touch was not working so I went to stock boot.img and running till now like this.
I want to learn rather than getting things done. ,:silly:
[Black is my happy colour]

Related

[Q] How to add new device tree,new kernel source code to CM source & compile?

Hello everybody.
I have a noob question about compile cyanogenmod for my new device.
Now, i have: CMW recovery, Kernel source code on local computer, full repo cm source + toolchains.
How to add my device tree, kernel source code to CM source and compile CM7 ROm?
Thanks you, cheer
Anyone here?
Did you figure it out yet? I asked the same question and am waiting for an answer, tho I'm on CM 10, HTC Vivid. If I figure it out I'll post back and try and help.
nguyenhonganh said:
Hello everybody.
I have a noob question about compile cyanogenmod for my new device.
Now, i have: CMW recovery, Kernel source code on local computer, full repo cm source + toolchains.
How to add my device tree, kernel source code to CM source and compile CM7 ROm?
Thanks you, cheer
Click to expand...
Click to collapse
I met the same problem, does anyone can help?
Do you have a device tree? Or do you have an unsupported device? If you have an existing device tree from some other ROM, etc, then you just need to edit your .repo/local_manifest/roomservice.xml to pull in the trees that you need.
If you need to create a device tree, then it gets not complicated, as each device is different. The basic process is to create the necessary directories (device/manufacturer/model, kernel/manufacturer/model (may need to be kernel/manufacturer/device_family/model, for reference to that, see CM's repo for the LG G3) and finally vendor/manufacturer/device.
After you have the directories setup, you will need to actually start building the tree. The easiest way is to copy another devices files into your devices tree, and then edit the files. The closer the device you copy in is, the less work you will need to do to the files. Refer to sites like gsmarena.com, PhoneArena.com, etc for phone specs.
That's about as far as I can take you without dealing with a specific device. If you need more info, post back here with your questions, and post your device specs, or at least the model number,and I'll see if I can help.
rassawyer said:
Do you have a device tree? Or do you have an unsupported device? If you have an existing device tree from some other ROM, etc, then you just need to edit your .repo/local_manifest/roomservice.xml to pull in the trees that you need.
If you need to create a device tree, then it gets not complicated, as each device is different. The basic process is to create the necessary directories (device/manufacturer/model, kernel/manufacturer/model (may need to be kernel/manufacturer/device_family/model, for reference to that, see CM's repo for the LG G3) and finally vendor/manufacturer/device.
After you have the directories setup, you will need to actually start building the tree. The easiest way is to copy another devices files into your devices tree, and then edit the files. The closer the device you copy in is, the less work you will need to do to the files. Refer to sites like gsmarena.com, PhoneArena.com, etc for phone specs.
That's about as far as I can take you without dealing with a specific device. If you need more info, post back here with your questions, and post your device specs, or at least the model number,and I'll see if I can help.
Click to expand...
Click to collapse
I have a mt6750 devices... And there is a device from my company manufacturer.. Its a mt6750 device, it have cm device tree.. Both device working on same rom.. I can port that device rom but it always give me bugs.. So my question is how to use it?

Galaxy Player 4.2 Developent - Need Help!

Hello fellow users of the SAMSUNG Galaxy Player 4.2!
I just recently received a Galaxy Player 4.2 for free from my brother SerkTheTurk since he got a Moto G, and I am planning to use it as an experimental device for development, since it's not my main device. I've gotten a device tree from SerkTheTurk and I've synced all the repos from CyanogenMod. I just need help on what to do next. I know that Serk made a complete build but it didn't boot. I just need help on what to change on the device tree and kernel files, if anybody can help I will appreciate it a lot. (I'm not super experienced on this topic but I can do work). Thanks! :fingers-crossed:
CenterTurkHD said:
Hello fellow users of the SAMSUNG Galaxy Player 4.2!
I just recently received a Galaxy Player 4.2 for free from my brother SerkTheTurk since he got a Moto G, and I am planning to use it as an experimental device for development, since it's not my main device. I've gotten a device tree from SerkTheTurk and I've synced all the repos from CyanogenMod. I just need help on what to do next. I know that Serk made a complete build but it didn't boot. I just need help on what to change on the device tree and kernel files, if anybody can help I will appreciate it a lot. (I'm not super experienced on this topic but I can do work). Thanks! :fingers-crossed:
Click to expand...
Click to collapse
Hey, you can build cm7 from my repositorys here is the readme how to
hoerwer there a still some bugs like no deep sleep
https://github.com/ChaOS-Development/android_device_samsung_hugo/blob/master/README.txt
CenterTurkHD said:
Hello fellow users of the SAMSUNG Galaxy Player 4.2!
I just recently received a Galaxy Player 4.2 for free from my brother SerkTheTurk since he got a Moto G, and I am planning to use it as an experimental device for development, since it's not my main device. I've gotten a device tree from SerkTheTurk and I've synced all the repos from CyanogenMod. I just need help on what to do next. I know that Serk made a complete build but it didn't boot. I just need help on what to change on the device tree and kernel files, if anybody can help I will appreciate it a lot. (I'm not super experienced on this topic but I can do work). Thanks! :fingers-crossed:
Click to expand...
Click to collapse
Great to some new devs.
I'm actually porting Android 4.4 "KitKat" to the Player 3.6 and with my help you could port KitKat also to the Player 4.2.
At first you need to get familiar with Androud building, so use Google and read something about it.
PM me for more help or information.
Greetings,
Androthan
Sent from my Nexus 7 using XDA Free mobile app
Need Help With building from source
Androthan said:
Great to some new devs.
I'm actually porting Android 4.4 "KitKat" to the Player 3.6 and with my help you could port KitKat also to the Player 4.2.
At first you need to get familiar with Androud building, so use Google and read something about it.
PM me for more help or information.
Greetings,
Androthan
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I'm a noob to developing roms but i decided to build a aokp kitkat rom for the galaxy player 4.2. I need someone to direct me to all the repo files for this device(device,kernal, and vendor repos). Someone please help me out because i would love to be running kitkat on my player 4.2. Thanks.
brewsterj98 said:
I'm a noob to developing roms but i decided to build a aokp kitkat rom for the galaxy player 4.2. I need someone to direct me to all the repo files for this device(device,kernal, and vendor repos). Someone please help me out because i would love to be running kitkat on my player 4.2. Thanks.
Click to expand...
Click to collapse
I think if there had been any full set of repo files that could build KitKat, other devs would've built it and you would've got KitKat earlier. Right now porting (instead of compiling) is the only hope I can see for GP4.2, but who knows
Sent from Google Nexus 4 @ CM11
AndyYan said:
I think if there had been any full set of repo files that could build KitKat, other devs would've built it and you would've got KitKat earlier. Right now porting (instead of compiling) is the only hope I can see for GP4.2, but who knows
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I found the repo files but i hit a wall while going to lunch, i get this.
Which would you like? [aosp_arm-eng] 17
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/aokp/products/bacon.mk]]: "device/oneplus/bacon/full_bacon.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_bacon'
** Do you have the right repo manifest?
im not sure which option to choose either but i get the same thing with every one. I pm'd some developers about it and hopefully they can tell me somthing.
brewsterj98 said:
I found the repo files but i hit a wall while going to lunch, i get this.
Which would you like? [aosp_arm-eng] 17
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/aokp/products/bacon.mk]]: "device/oneplus/bacon/full_bacon.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_bacon'
** Do you have the right repo manifest?
im not sure which option to choose either but i get the same thing with every one. I pm'd some developers about it and hopefully they can tell me somthing.
Click to expand...
Click to collapse
You are using the repo files for the Oneplus ONE...(codename bacon). The galaxy player 4.2's codename is "hugo". There are no 4.4 repo files for the 4.2
Sent from my XT760
so my only hope is to port?
or could i somehow build a repo file for it?
You are going to have to follow the official CM guide to port cm to a new device...to make a device, vendor and kernel tree...then you can use that to try and build AOKP...
EDIT: Here it is... http://wiki.cyanogenmod.org/w/Doc:_porting_intro If you dont find the method difficult, you can also ask Androthan for help as he has ported cm11 to the galaxy player 3.6, which is very similar to the 4.2.
Sent from my XT760
Another Guide
drakonizer said:
You are going to have to follow the official CM guide to port cm to a new device...to make a device, vendor and kernel tree...then you can use that to try and build AOKP...
EDIT: Here it is... http://wiki.cyanogenmod.org/w/Doc:_porting_intro If you dont find the method difficult, you can also ask Androthan for help as he has ported cm11 to the galaxy player 3.6, which is very similar to the 4.2.
Sent from my XT760
Click to expand...
Click to collapse
Can you point me to a guide that explains more and goes more in-depth about the process?
There are a limited number of guides for this process, this being the best imo. You should understand a few things if you're planning to undertake this project.
1. You cannot expect a guide for everything. Use google for any info that you need and ask devs. Search xda for threads that explain a similar problem.
2. If you don't have knowledge about the Android Build Process, some basic C knowledge, and have not even built a ROM that already has /device, /vendor etc. , I'd recommend not doing this, because even the best of devs reach problems while porting ROMs.
Sent from my XT760
drakonizer said:
There are a limited number of guides for this process, this being the best imo. You should understand a few things if you're planning to undertake this project.
1. You cannot expect a guide for everything. Use google for any info that you need and ask devs. Search xda for threads that explain a similar problem.
2. If you don't have knowledge about the Android Build Process, some basic C knowledge, and have not even built a ROM that already has /device, /vendor etc. , I'd recommend not doing this, because even the best of devs reach problems while porting ROMs.
Sent from my XT760
Click to expand...
Click to collapse
No, I have the knowledge(studied a bunch of stuff for hours and already have android build enviroment set up and i have a github account to access the files i need also, I have also ported using the android kitchen and a few other methods too never perfectly but i think porting it the official way would have a better result.) its just that i haven't tried porting through this method. I was following the guide all the way up until it said to get certain stuff from a file we pulled from my device using the terminal but i could never find the file. I know that repos and such go into a working folder or directory its just some stuff i just cant find.
Oh okay great then
Btw, porting with android kitchen and the whole copy paste the files from one ROM to the other to get port a custom ROM is TOTALLY different from what you're trying to do here.
I suggest you fork a repo from Androthan's CM11 for the 3.6 and start renaming it for us (our codename is "hugo", their's is "aalto" but the vendor is the same). If you can mention clearly what file you're not getting, and/or other problems you're facing, you can expect some help from the devs of the Galaxy Player (including all the players) community
Sent from my XT760
drakonizer said:
Oh okay great then
Btw, porting with android kitchen and the whole copy paste the files from one ROM to the other to get port a custom ROM is TOTALLY different from what you're trying to do here.
I suggest you fork a repo from Androthan's CM11 for the 3.6 and start renaming it for us (our codename is "hugo", their's is "aalto" but the vendor is the same). If you can mention clearly what file you're not getting, and/or other problems you're facing, you can expect some help from the devs of the Galaxy Player (including all the players) community
Sent from my XT760
Click to expand...
Click to collapse
ok i have forked the cm11 files for the 3.6 now how should i go about renaming it?(sorry for the noob question)
---------- Post added at 01:39 PM ---------- Previous post was at 01:32 PM ----------
brewsterj98 said:
ok i have forked the cm11 files for the 3.6 now how should i go about renaming it?(sorry for the noob question)
Click to expand...
Click to collapse
and this is where i got lost into the guide.
[So, if you have previously installed adb onto your computer, you can use the following command to pull this file to your computer:
adb pull /system/build.prop
Once you have the file...
Write down the value of the ro.product.manufacturer parameter. This will be your vendor name. The [vendor] is the name of the manufacturer/vendor of the device. CM has established naming conventions for most major vendors, such as samsung, htc, lge, etc. Note that in these directory names, the vendor is always lowercase and contains no spaces.
Write down the value of the ro.product.device parameter. This will be your device codename. The [codename] corresponds to the project code name of the device itself. This is almost never the sales name of the device. If you have built CM before (and again, you better have!), you should be familiar with the concept of a code name for each device. Like the vendor name, the codename is always lowercase and contains no spaces.]
Where does the pulled build.prop go? and are there any specific linux programs i would need to edit this file or any other files throughout the tortorial? I have gedit installed and its met my needs so far but do i need something more advanced to accomplish my goal?
got the repo renamed.
brewsterj98 said:
ok i have forked the cm11 files for the 3.6 now how should i go about renaming it?(sorry for the noob question)
---------- Post added at 01:39 PM ---------- Previous post was at 01:32 PM ----------
and this is where i got lost into the guide.
[So, if you have previously installed adb onto your computer, you can use the following command to pull this file to your computer:
adb pull /system/build.prop
Once you have the file...
Write down the value of the ro.product.manufacturer parameter. This will be your vendor name. The [vendor] is the name of the manufacturer/vendor of the device. CM has established naming conventions for most major vendors, such as samsung, htc, lge, etc. Note that in these directory names, the vendor is always lowercase and contains no spaces.
Write down the value of the ro.product.device parameter. This will be your device codename. The [codename] corresponds to the project code name of the device itself. This is almost never the sales name of the device. If you have built CM before (and again, you better have!), you should be familiar with the concept of a code name for each device. Like the vendor name, the codename is always lowercase and contains no spaces.]
Where does the pulled build.prop go? and are there any specific linux programs i would need to edit this file or any other files throughout the tortorial? I have gedit installed and its met my needs so far but do i need something more advanced to accomplish my goal?
Click to expand...
Click to collapse
The vendor for our device is "samsung" and the codename is "hugo"
Just fyi...when you are in the linux terminal...whichever directory you are in is where the pulled build.prop goes.
Sent from my XT760
I know I tried t post about me rereading the guide and understanding what it meant and that i have moved further into the guide but it never posted on here but i guess this whole thing was just a waste of time.
dude you should try porting from the galaxy sl i9003 because of the similar cpu stats
you would also need to create a boot image and an odin flashable recovery v 6+
Guys, I'll rewrite the stock kernel for you for booting KitKat, just give me 1-2 weeks
has this been done yet. Not to be a stickler, but this is the holdup for advancing this device. I can port the rom, just need an updated kernel with a recovery that supports. Thanks in advance.

[Q] Build a Custom ROM using only kernel source?

The HTC Desire 310 runs on a MediaTek SoC, and HTC only has the source code for the kernel. Is it possible to build a Custom ROM like CM for the device? And what are the drawbacks of doing this?
Lynuxen said:
The HTC Desire 310 runs on a MediaTek SoC, and HTC only has the source code for the kernel. Is it possible to build a Custom ROM like CM for the device? And what are the drawbacks of doing this?
Click to expand...
Click to collapse
Basically all a ROM development takes is a kernel source ,a device tree(how the source has to build your ROM {resolution,kernel source command lines....etc are set here}) , a vendor tree( usually proprietary shared libraries got from stock ROM ). Once you've got all these all you have to so is type make bacon. But since its mediatek its pretty hard to build anything since mediatek ril/libraries are not open source.
So doing this blindfolded won't work.
Lynuxen said:
So doing this blindfolded won't work.
Click to expand...
Click to collapse
Won't work, unless you set up a device tree for your SoC. MT6589 device tree may work for building only recovery but nothing further.
Yes, as @MasterAwesome said you need actually 3 components: Vendor tree, kernel source and device tree. Making vendor and device tree from scratch is hard.
GeekyDroid said:
Yes, as @MasterAwesome said you need actually 3 components: Vendor tree, kernel source and device tree. Making vendor and device tree from scratch is hard.
Click to expand...
Click to collapse
Hard, but not impossible? I really want to invest my time in something like this. Pretty long shot, will something like a method for reversed engineering the vendor and device tree work?
Lynuxen said:
Hard, but not impossible? I really want to invest my time in something like this. Pretty long shot, will something like a method for reversed engineering the vendor and device tree work?
Click to expand...
Click to collapse
Vendor tree is pretty easy to setup. You'd want to start with the CyanogenMod version which is similar your current android version. If your device has kitkat download cm11 sources. Read their docs about setting up a device tree(its not that hard). Vendor tree is basically just your stock ROM use it as a base to get your libs which are required for your ROM to start(logcats are helpful here). Since you have a similar SoC, you can use my device tree as a reference https://github.com/MasterAwesome/a210_device_tree/tree/master/micromax/a210. Initially just build a kernel and check if it works. And I have guides for kernel and ROM building,you could check it out.
MasterAwesome said:
Vendor tree is pretty easy to setup. You'd want to start with the CyanogenMod version which is similar your current android version. If your device has kitkat download cm11 sources. Read their docs about setting up a device tree(its not that hard). Vendor tree is basically just your stock ROM use it as a base to get your libs which are required for your ROM to start(logcats are helpful here). Since you have a similar SoC, you can use my device tree as a reference https://github.com/MasterAwesome/a210_device_tree/tree/master/micromax/a210. Initially just build a kernel and check if it works. And I have guides for kernel and ROM building,you could check it out.
Click to expand...
Click to collapse
Massive thanks MasterAwesome. :highfive:

Can someone explain how to create a device tree from the Samsung opensource zip?

I recently got my tab s7 sm-t870 for Christmas. I like it so far. I am trying to build TWRP and Lineage for it because only the 5g version is getting development. So i went and found out the source code for the wifi model is released by Samsung. I'm stuck on building a device tree from it though. I rooted the device so i can get the right blobs from it. If i were to succeed I will try to share it but I haven't used any file sharing sites so i don't know how that would work.
On second thought i should do twrp first before compiling Lineage but i still need a device tree
You might as well asked for the meaning of life...I doubt many will help with this. You maybe better off going to telegram and seeing if there is a dedicated forum, there maybe a dev there with more time or willingness
n0lan said:
I'm stuck on building a device tree from it though. I rooted the device so i can get the right blobs from it.
Click to expand...
Click to collapse
Have not done this before...
If I were to do this I would check out the github repositories of developers who are working on/publishing ROMs or recoveries for recent SAMSUNG devices.
Look what they use and from there find the equivalents for your tablet.
DHGE said:
Have not done this before...
If I were to do this I would check out the github repositories of developers who are working on/publishing ROMs or recoveries for recent SAMSUNG devices.
Look what they use and from there find the equivalents for your tablet.
Click to expand...
Click to collapse
hey i realized Ian has created a device tree for the s7 sm-t875 so i decided to clone it but when i lunch it complains that it doesn't exist in the config makefile. i'm getting so close but just need to figure out how to properly setup the files. I think the hard part is done finding something that would work. Do you have the knowledge of what I might be missing? This is the error
build/make/core/envsetup.mk:257: error: No config file found for TARGET_DEVICE gts7l.
Welp I just solved it it was just giving a different path in the BoardConfig.mk oops
You dont really lol.. samsung opensource is really just kernel source
elliwigy said:
You dont really lol.. samsung opensource is really just kernel source
Click to expand...
Click to collapse
wdym ??

Question Where to start building a working twrp and/or roms for moto g power 2021 (borneo)?

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

Categories

Resources