Related
This is DIY
If you are just looking for a well done and stable PA download, you are probably the wrong place. Then go and grab xzzz9097s build, it's good!
If you are impatient and know what to do, just leave and do the init/sync/build.
For anyone wanting to build her/his own PA without any "extras", go ahead and read on.
We already have a very easy full guide to compile CM10 for HOX. I was looking for the same for ParanoidAndroid, but did not find a 100% guide, meaning I had to do it myself.
To be fair, I only needed to do 1% as you will see after the usual disclaimer. I hope this little guide will be enough to make anyone complile their own PA for the HOX.
The usual disclaimer:
I am no developer!
I just happen to be able to read and understand instructions. I am persistent and know how to search for answers.
With luck and patience I ended up with a 184MB zip, that installs and runs just fine on my HOX.
I pass this guide as it is now, no guarantee no returns. I will probably not be able to help much here, time is very limited, so no commitments for support from me.
If it breaks you device, you broke it all by yourself
I am no developer!
gokussjx made the general guide, explaining how to port Paranoid Android 3.xx to different devices.
It works 99% for Endeavoru. The last 1% takes some effort to get right.
For me, not knowing what I am doing, it took a lot of trial and error, but eventually, - I made it and might as well pass it on here.
I'm in debt to all the people helping out in that thread. Huge thanks!
To get started, just follow a few simple steps:
You need a linux setup.
Install as your main system or run it in windows with VirtualBox.
Most guides are expecting Ubuntu. I use Mint Debian 64, which is just perfect for this job (and everything else ).
For VirtualBox you need at least a 50GB virtual-drive. Add 16GB if you will use ccache. I have build PA with a 52GB VBox in Win7.
It was just enough to compile, but had no room for ccache!
Compile time (VBox) on EliteBook 8540w (i7) was 120min. Not too bad, considering my old DeskTop need close to 4 hours on pure Linux.
Expect to download 8GB of source. Add 18GB for building to the "out" folder.
Enough statistics now, let's get started.
Follow gokussjx guide to setup linux for PA compiling.
Follow only these steps:
# Install OpenSSL, for Python
# Install Dependencies
# Configure USB
# JAVA JDK Installation
# Python Installation (just pick option 1)
# Android SDK
Click to expand...
Click to collapse
Exit gokussjx guide and continue here:
Download your favorite arm toolchain:
I found mine here.
Just extract the archive to any folder with user access, later you will point the build system to the /bin folder of the toolchain.
Install CCACHE:
Code:
$ sudo apt-get install ccache
Activate it in .bashrc:
Code:
# use ccache
export USE_CCACHE=1
You can change max-cache size, 16G should be enough for this build.
From terminal:
Code:
$ ccache -M 16G
Install Repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Download the build manifest:
Code:
$ mkdir -p padroid/system
$ cd padroid/system
$ repo init -u git://github.com/teemodk/manifest.git -b padroid
Get the source!
Code:
$ repo sync -j16
Find this section in "build/envsetup.sh" update with your favorite arm toolchain:
Code:
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=[B]~/toolchain/linaro4.8/bin[/B]
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
Go!
Code:
$ ./rom-build.sh endeavoru
Thats all. If it went well, get your new ROM in "out/target/product/endeavoru"
Don't forget the gApps.
Credits go to
PA:molesarecoming, D4rKn3sSyS for the awesome hybrid magic. All PA contributors. gokussjx for the mother of all PA guides. All the helpful people here, that use their time to help.
CM(aosp):thöemy,gorbi16,tbalden,(pabx) and all the unknown soldiers contributing to CM
Everyone I forgot.
Differencies from the official guide.
The official PA manifest is put together in a way, so you can easily build and maintain multiple devices with only one manifest.
It works by adding and removing device specific code with local manifests under the "vendor/pa" folder.
However, I am only compiling for OneX, so I found it easier to add/remove stuff directly in the main manifest.
The downside to this is, that you have to manually maintain the manifest everytime you want to sync with PA. Place for improvement
All changes in STEP 2 of the official guide, is already done if using my guide with padroid manifest.
In vendor/pa these steps are done:
Code:
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.adds"]/manifest/<device>.adds[][/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.removes"]/manifest/<device>.removes[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/prebuilt/pa_endeavoru.conf"]/prebuilt/pa_<device>.conf[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/pa_endeavoru.mk"]/products/pa_<device>.mk[/URL]
* Add device makefile entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/AndroidProducts.mk"]/products/AndroidProducts.mk[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/tree/padroid/vendorprops"]/vendorprops/<device>.proprietaries[/URL]
* Add device lunch menu entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/vendorsetup.sh"]/vendorsetup.sh[/URL]
Furthermore, I temporarily moved the CM adds/removes from "vendor/pa/manifests" to .repo/manifest.xml.
I am sure there are better ways to handle git/repo/manifest etc., but this works well for me for now. Open for suggestions though.
Problem Solving
If (when) you run into problems, go to the official guide and find the answer. Most, if not all, errors is already answered there. If not, ask.
But first make a serious effort to find the error yourself. Read some good advice about finding the error.
As a rule of thumb: The build system tells you where to find the error! Something is missing, something is duplicated or somthing is just wrong. It's all in the log, running up your screen when compiling.
Build 25.Oct.2013
http://d-h.st/XRt
Nice, I'm always eager to learn this stuff .
Thanks!
ROM uploaded to post 3.
teemo said:
ROM uploaded to post 3.
Click to expand...
Click to collapse
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Mat08.cc said:
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Click to expand...
Click to collapse
The ROM is as close to stock as it get for OneX. It is really a mix of CyanogenMod and ParanoidAndroid. I follow the official build guide from PA-team.
The kernel is from same source as CM.
You can see everything in the manifest.
@teemo
your build is running fast and stable, congratulations! maybe you can keep updating this .. I appreciate it and I'm sure many other people would be of the same opinion
Sry,wrong threat....
Gesendet von meinem EndeavorU mit Tapatalk
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Mat08.cc said:
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Click to expand...
Click to collapse
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
teemo said:
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
Click to expand...
Click to collapse
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Mat08.cc said:
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Click to expand...
Click to collapse
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
One-X-master said:
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
Click to expand...
Click to collapse
Yeah I thought so! But I would love to learn! I have always looked to devs as to extraordinary people, understanding what makes them such would be great
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
LuisDias said:
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
Click to expand...
Click to collapse
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
bosas200 said:
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
Click to expand...
Click to collapse
Thanks brotha
teemo said:
Build 25.Oct.2013
http://d-h.st/XRt
Click to expand...
Click to collapse
Any chance helping me build AOSB with newer cm 11 base?
As no instructions anywhere on building AOSB from source. Source is
https://github.com/AOSB?page=1
Many thanks
I understand there are some builds available on github ( https://github.com/omnirom/android_device_oppo_n1 ). Please could anyone guide on how to build it so we can test it on our devices. Thanks.
That would be a pretty in-depth guide.
Omnirom has their own wiki page that can teach you how to compile and port to your device.
http://docs.omnirom.org/Main_Page
:good:
Thank you Harfainx for sharing the guide, I'll try following it and post my finding(s) for everyone.
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
nospam said:
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
Click to expand...
Click to collapse
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Harfainx said:
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Entropy512 said:
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Click to expand...
Click to collapse
Glad to hear an official response. Thanks for the update. :highfive:
viperdream26 said:
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
Click to expand...
Click to collapse
Maintaining a thread is more work then you would ever think
At the moment I am more then full doing that at oppoforums
I'm going to take a crack at compiling the Cyanogen Source code to take a peek at the o-click issues.
I'm fairly knowledgeable in C, but haven't done any android/bluetooth coding before, so I think I have a snowball's chance in hell.
But it'll be an interesting exercise anyway.
So I'm following random links in:
http://wiki.cyanogenmod.org/w/Development
Mainly using this:
https://skydrive.live.com/view.aspx?cid=B3BFF0D42AE1E534&resid=B3BFF0D42AE1E534!107&app=OneNote
To set up virtualBox/Ubuntu/android SDK.
Although I am a bit confused about required JDK versions.
Is there a list of prefered JDK versions for different CM versions?
I also just noticed the page for the Find 5: aka
http://wiki.cyanogenmod.org/w/Build_for_find5
So I guess I'll use that as the instructions until the actual source code pull?
- Frank
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Entropy512 said:
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Click to expand...
Click to collapse
This is based on the Google BLE sample. It allows pairing with the o-click and will recognise single and double clicks on the remote
Sent from my N1 using Tapatalk
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
ChodTheWacko said:
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
Click to expand...
Click to collapse
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
add_lunch_combo cm_n1-user
add_lunch_combo cm_n1-userdebug
add_lunch_combo cm_n1-eng
Click to expand...
Click to collapse
Could you just be using the wrong vendorsetup script or should that one run first? Like I said, I'm still very new to this but wanted to at least point this out.
mybrotherischad said:
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
Click to expand...
Click to collapse
You're right, the n1 directory's vendor explicitly lists them.
I was looking at the wrong one I guess. Or it's not being used for some reason.
My Brunch n1 is also complaining with:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
which doesn't look right, but I'm taking stuff one step at a time.
- Frank
As the title says. This board is created for questions and answers pertaining to getting new ROM's and ports for our P9000.
THIS IS NOT A BUG REPORT DISCUSSION.
New Development only.
If you would like to see a new ROM for the P9000? Build it, and share it. Check out some of the guides, then ask some questions on building it.
I will be staying with Mediatek devices for the long term and encourage more people like me to start bringing some development love to them.
Thank you
Some useful guides.
https://www.youtube.com/watch?v=aF--LQDgg1M
http://source.android.com/source/initializing.html
Any guides to add? I'll be glad to add them.
Credits:
@Deepflex (Active) Vendor, Device, Kernel sources
@Jonny (Active) TWRP and multiple additions to Kernel source
@skeleton1911 (Active) Stock based ROM's
@leskal (ACTIVE) device and kernel commits
Please let me know of any credits I'm missing.
Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?
syncing AOKP MM. I enjoyed this rom in my samsung days.
something interesting to try for automating builds.
http://forum.xda-developers.com/chef-central/android/guide-tool-projekt-scribt-v1-33-t3503018
electrofryed said:
Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?
Click to expand...
Click to collapse
Check the .mk files in the root of your device tree, I'm guessing you need to rename a reference in one of them from something like 'cm.mk' to 'candy.mk'
So far I've modified /AndroidProducts.mk cm.mk vendorsetup.sh I think I'm missing a file to modify. Just not sure which one. Unfortunately, since I didn't make a copy of the original Candy directory, I'll need to resync to get rid of my Troubleshooting changes. Good lesson. After each sync, make sure you make a backup of the original in case you forget the modifications you've made. Lol
I think I figured it out. My product name didn't match the vendorsetup.sh
Update: Nope. That didn't work. I've attached a screenshot of the changes I've made in case anyone wants to chime in.
Thank you
What lunch command are you using?
Jonny said:
What lunch command are you using?
Click to expand...
Click to collapse
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.
electrofryed said:
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.
Click to expand...
Click to collapse
I recomend the brunch command as on official build guide of cm
Yeah. I tried brunch and "rainbowfarts" (recommended by AOKP. Lol. It stops when calling for maven 1.6 (I'm on 2.10). I think I need to find the file that will link my builds to my build environment path.
leskal said:
I recomend the brunch command as on official build guide of cm
Click to expand...
Click to collapse
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.
electrofryed said:
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.
Click to expand...
Click to collapse
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command
leskal said:
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command
Click to expand...
Click to collapse
Great guide!! I see a few big differences between this guide and some of the others. The biggest is the method of getting java 7 for 16.04. I've been using Oracle and open Java 8 the whole time.
Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh
Hello,
i started my first build-experience with downloading the cm13 sources and the p9000 sources form deepflex. Since yesterday i have an successful build cm_p9000-ota.zip package but after installation it ends in an bootloop!! I have no idea where to start searching for the mistake... I get no error massage while installing it.
Could someone give me a hint?
electrofryed said:
Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh
Click to expand...
Click to collapse
You need to fix includes when building out of mtk build chain, or use other sources that already have this done
OK, i get it running!
But, is their a reason why "/android_device_elephone_p9000/mediatek_driver_nl80211.h" is missing in the repo? Sorry, but i am totally new and trying to understand how these builds work and what exactly is needed to build a bugles ROM.
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
cm11noob10 said:
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
Click to expand...
Click to collapse
Any news on this awesome rom?
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
cm11noob10 said:
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
liam_davenport said:
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
Click to expand...
Click to collapse
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
cm11noob10 said:
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
Click to expand...
Click to collapse
What linux distro are you using?
liam_davenport said:
What linux distro are you using?
Click to expand...
Click to collapse
Ubuntu. I have problems running Arch in a VM without scaling issues.
cm11noob10 said:
Ubuntu. I have problems running Arch in a VM without scaling issues.
Click to expand...
Click to collapse
Try this: sudo apt-get install linux-headers-generic
liam_davenport said:
Try this: sudo apt-get install linux-headers-generic
Click to expand...
Click to collapse
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
If you get it working I could try my hand for the sailfish
YTSec said:
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
Click to expand...
Click to collapse
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
ChongoDroid said:
If you get it working I could try my hand for the sailfish
Click to expand...
Click to collapse
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
cm11noob10 said:
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
Click to expand...
Click to collapse
I'll give it a try tonight when I can, and see if I get anywhere. Would be nice to at least get the music detection working somehow.
U may need to use a newer kernel tree to compile I did but I also had to update toolchain its what I did
cm11noob10 said:
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
Click to expand...
Click to collapse
Have you been able to get it compile and boot?
Zehlek said:
Have you been able to get it compile and boot?
Click to expand...
Click to collapse
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
cm11noob10 said:
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
Click to expand...
Click to collapse
Maybe you and @joeeboogz can work together. It would be an awesome rom
U have to update toolchain to ur computer then compile and add zip to tree then add toolchain line to board config I think I forgot which file to edit
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
YTSec said:
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
Click to expand...
Click to collapse
do you have aoscp.mk in your device tree?
i came across this tread because i want to use a prebuilt kernel and im getting the error "ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/sixohtew/bliss/out/target/product/taimen/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it" and saw someone had a previous error.. im trying to build for taimen obv which is the pixel 2 xl and it has an aosp prebuilt kernel and my rom wont compile any other kernels so i was looking for some help
Hey y'all!
I've seen that there aren't any lineageos 15.1 roms for a5 2017 out there so I decided I will build my own.
I followed the guide on rr's github page and I when I typed "breakfast a5y17lte" I got a big error that it cannot find the makefile. Also in device/samsung/a5y17lte there wasn't "vendorsetup.sh".
Please help.
Hello,
First, you can't build booting oreo aosp rom from actual sources.
Second, if you can't deal with something like that - leave building your own rom, or if you want to fight with that error, just use google and little common sense, nothing hard.
Good luck!
I'm glad someone out there is building custom roms for a5 2017. I looked for some the other day and couldn't find many.
Sent from my Samsung SM-A520W using XDA Labs
sheepkill15 said:
Hey y'all!
I've seen that there aren't any lineageos 15.1 roms for a5 2017 out there so I decided I will build my own.
I followed the guide on rr's github page and I when I typed "breakfast a5y17lte" I got a big error that it cannot find the makefile. Also in device/samsung/a5y17lte there wasn't "vendorsetup.sh".
Please help.
Click to expand...
Click to collapse
I got the same issue. I imported vendorsetup.sh from a device repo for another device, and adapted it to my own.
Code:
add_lunch_combo rr_a5y17lte-userdebug
This makes it show up in lunch combo but i get the same error as you,
Code:
Which would you like? [aosp_arm-eng] 16
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/samsung/a5y17lte/rr.mk]]: "device/samsung/universal7880-common/common.mk" does not exist. Stop.
Device a5y17lte not found. Attempting to retrieve device repository from ResurrectionRemix-Devices Github (http://github.com/ResurrectionRemix-Devices).
Repository for a5y17lte not found in the ResurrectionRemix-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/roomservice.xml
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/samsung/a5y17lte/rr.mk]]: "device/samsung/universal7880-common/common.mk" does not exist. Stop.
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/samsung/a5y17lte/rr.mk]]: "device/samsung/universal7880-common/common.mk" does not exist. Stop.
** Don't have a product spec for: 'rr_a5y17lte'
** Do you have the right repo manifest?
I know this is very late too, but I'm just glad to see that I wasn't the only one having this issue.
YoMarshMellow said:
I got the same issue. I imported vendorsetup.sh from a device repo for another device, and adapted it to my own.
This makes it show up in lunch combo but i get the same error as you,
I know this is very late too, but I'm just glad to see that I wasn't the only one having this issue.
Click to expand...
Click to collapse
Actually, I managed to fix these and succesfully go along my merry way after a few days of google searches