So while trying to compile an Atrix rom from source after typing:
". build/envsetup.sh && brunch olympus"
I get an error:
. build/envsetup.sh && brunch olympus
including device/motorola/olympus/vendorsetup.sh
including device/moto/stingray/vendorsetup.sh
including device/moto/wingray/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
Device olympus not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_motorola_olympus
Duplicate device 'CyanogenMod/android_device_motorola_olympus' found in local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_olympus'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
I've tried "breakfast" to no avail. I've used multiple guides in trying to do this and always the same outcome... If it helps you can assume I've ran all the same steps (but for the Atrix of course) as in this guide: http://forum.xda-developers.com/showthread.php?t=1188298
Disclaimer: I don't know a ton about this stuff yet either. I have yet to execute a successful build for the Atrix.
Have you looked at http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Compile_CyanogenMod_(Linux) and http://forum.xda-developers.com/showthread.php?t=1442842 ? Are you trying to build CM7 or CM9? If it's CM9 then I don't think the Atrix specific bits are in the CM github. You'll have to overlay joker or turl's github on top of it.
Try this
Davidrd91 said:
So while trying to compile an Atrix rom from source after typing:
". build/envsetup.sh && brunch olympus"
I get an error:
. build/envsetup.sh && brunch olympus
including device/motorola/olympus/vendorsetup.sh
including device/moto/stingray/vendorsetup.sh
including device/moto/wingray/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
Device olympus not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_motorola_olympus
Duplicate device 'CyanogenMod/android_device_motorola_olympus' found in local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_olympus'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
I've tried "breakfast" to no avail. I've used multiple guides in trying to do this and always the same outcome... If it helps you can assume I've ran all the same steps (but for the Atrix of course) as in this guide: http://forum.xda-developers.com/showthread.php?t=1188298
Click to expand...
Click to collapse
From your device tree I'm assuming you're trying to build CM9.
Try using the ADT repo instead of the CyanogenMod one. The one you're using does not have a cm.mk file, which is what I think is giving you your error. Can't make something if the instructions aren't there.
Compare the contents of the CM one to the ADT one and you'll see there's a lot of stuff missing.
Also, you may want to try checking out the building CM9 from source link lautern posted above. You'll most likely get better feedback / more experienced eyes to help you out.
Thanks guys I'll look into both. And yes it is CM9 I'm trying to compile, I've been using Jokersax's repo and the CM ics branch to compile but i got a little confused between the device files and proprietary. I've started from scratch to make sure everything is fresh and hopefully this time all will go well.
I'll post again when this is all done syncing and I test what I've compiled =]
This time it wouldn't find the "modules". By this I'm assuming it meant the Wi-Fi modules so I tried to compile a kernel. Which failed as well. I don't have the cmd prompt logs to post but I just wanted to ask if you guys know of any guides specific for compiling Cm9 for an Atrix? I'm assuming that its a bit more difficult because the Atrix doesn't come with ics.
Or any guides on how to do so using Jokersax/turls repos?
Thanks in advance everyone
Sent from my MB860
Davidrd91 said:
This time it wouldn't find the "modules". By this I'm assuming it meant the Wi-Fi modules so I tried to compile a kernel. Which failed as well. I don't have the cmd prompt logs to post but I just wanted to ask if you guys know of any guides specific for compiling Cm9 for an Atrix? I'm assuming that its a bit more difficult because the Atrix doesn't come with ics.
Or any guides on how to do so using Jokersax/turls repos?
Thanks in advance everyone
Sent from my MB860
Click to expand...
Click to collapse
See previous suggestion:
lauterm said:
Disclaimer: I don't know a ton about this stuff yet either. I have yet to execute a successful build for the Atrix.
Have you looked at http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Compile_CyanogenMod_(Linux) and http://forum.xda-developers.com/showthread.php?t=1442842 ? Are you trying to build CM7 or CM9? If it's CM9 then I don't think the Atrix specific bits are in the CM github. You'll have to overlay joker or turl's github on top of it.
Click to expand...
Click to collapse
Building CM9
Building CM7 (linked in above quote)
Read both threads. The CM7 one will probably be of more help to you (it has more troubleshooting discussion). Each has links to other useful guides.
So I've read through both posts several times, and now that I have a new laptop its around the 6th time (not exaggerating) that I set up Ubuntu and the "build enviroment" from scratch.
This time though my problem seems to be with java >_<...
build/core/config.mk:269: *** Error: could not find jdk tools.jar, please install JDK6, which you can download from java.sun.com. Stop.
Device olympus not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_motorola_olympus
Duplicate device 'CyanogenMod/android_device_motorola_olympus' found in local_manifest.xml.
build/core/config.mk:269: *** Error: could not find jdk tools.jar, please install JDK6, which you can download from java.sun.com. Stop.
** Don't have a product spec for: 'generic_olympus'
** Do you have the right repo manifest?
I have the correct JDK installed (sun not openjdk) version 1.6.0_31, and looking through the folders I can find the tools.jar file in the directory, I've even tried to point it out by putting:
# Variable ANDROID_JAVA_HOME
ANDROID_JAVA_HOME=/usr/lib/jvm/jdk1.6.0_31/lib
export ANDROID_JAVA_HOME
into my .bashrc. Also tried changing the ANDROID_JAVA_HOME variable to the HOST_JAVA_TOOLS_JAR variable which seems to be what the build/core/config.mk file cant find.... Yet still no hope ... as of now Im not even worried about the "Device Olympus not found" error as I've had it before. Dont really know how I fixed it but atleast I know I can lol...
Any help would be greatly appreciated, thanks =]
Also I have made sure to update the java alternatives and java -version returns
java -version
java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
Which to my knowledge is correct?
Ok so I fixed the Java problem, and got another Java problem. I'll post all the fixes I find in case others need help with errors. If you know some C programming (which I dont but was
linked to in one of the threads you guys sent me to ) most errors will have
"build/core/config.mk:269"
The number at the end corresponds to the line 269 in the config.mk file found in build/core directory in your source folder. Going to that line I saw that it ran a script:
"find-jdk-tools-jar.sh"
After doing a search for it I saw that the script in turn looked for the tools.jar file using the variable ANDROID_JAVA_HOME.
"$ANDROID_JAVA_HOME/lib/tools.jar"
So I added this at the end of my ~/.bashrc
"# Variable ANDROID_JAVA_HOME
ANDROID_JAVA_HOME=/usr/lib/jvm/jdk1.6.0_31
export ANDROID_JAVA_HOME "
If you look at my last post you'll see I added "/lib" to the end of "ANDROID_JAVA_HOME=..." so the script was looking for:
"ANDROID_JAVA_HOME=/usr/lib/jvm/jdk1.6.0_31/lib/lib/tools.jar"
^ 2 /libs... that folder doesn't exist.
Now it tells me I'm using the incorrect version of Java. (it says I have 1.6.0_31 and the correct version is just 1.6 or something) I've fixed this before so I'll post again when I see exactly how I did it >_< lol.
Edit: Just ran "sudo apt-get install openjdk-6-jdk" then ran build>lunch>olympus and it's building as we speak.
A follow up on this - http://forum.xda-developers.com/showpost.php?p=28177937&postcount=1768 - in the CM9 FXP thread, have I promised to make a little guide.
Guide how I build CM9 for my Mango.
For the first time you try to build CM9.
Create ~/bin and download repo to that directory. Afterwards set executable bit to make it possible to ”execute”.
Code:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Now reboot the computer.
Create ~/android/system amd initialize the repository.
Code:
mkdir -p ~/android/system
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
Setup the environmental settings and initialize the Mango build.
Code:
. build/envsetup.sh
brunch mango
Setup the environmental settings and initialize the Mango build.
Code:
git clone git://github.com/TheMuppets/proprietary_vendor_semc.git -b ics ~/android/system/vendor/semc
cd ~/android/system/device/semc/mango/
./setup-makefiles.sh
Download the prebuilts
Code:
~/android/system/vendor/cm/get-prebuilts
Check for new changes
Code:
cd ~/android/system/
repo sync
Setup the environment again and build the ROM (takes long time)
Code:
. build/envsetup.sh
brunch mango
You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-9-DATE-UNOFFICIAL-mango.zip
The next times you try to build it, you only need to do the following.
Delete build.prop, if not will build.prop not get generated.
Code:
rm -f ~/android/system/out/target/product/mango/system/build.prop
Syncronise the git repositories.
Code:
cd ~/android/system/
repo sync
Setup the environmental settings.
Code:
. build/envsetup.sh
Configure/build.
Code:
brunch mango
You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-9-DATE-UNOFFICIAL-mango.zip
If you are trying to build it on a 32bit system, you should change line 374 in ~/android/system/device/semc/msm7x30-common/releasetools/common.py
from:
Code:
cmd = ["java", "-Xmx2048m", "-jar",
to:
Code:
cmd = ["java", "-Xmx1024m", "-jar",
If you get into any trouble, please let me know, I may have missed something.
EDIT (July 2. 2012): I have made a patch to msm7x30-common, so you do not need to edit the file (with this patch does it automatically check if you run on a 64bit or a 32bit system):
http://code.google.com/p/freexperia/issues/detail?id=527
EDIT (July 6. 2012): If there has been an update on git://github.com/koush/proprietary_vendor_semc.git (like there has been today), shall you do the following (pull the updates):
Code:
cd ~/android/system/vendor/semc
git pull
EDIT (July 8. 2012): Adding the following, just before "</manifest>" in ".repo/local_manifest.xml" and the proprietary files will also get updated, when you make a normal "repo sync". Got this idea after talking to Andreas (so thank you Andreas).
Code:
<project name="TheMuppets/proprietary_vendor_semc" path="vendor/semc" remote="github" revision="ics" />
EDIT (July 11. 2012): Changed the proprietary repository from git://github.com/koush/proprietary_vendor_semc.git to git://github.com/TheMuppets/proprietary_vendor_semc.git
allright, i have already synched the cm9 repo. about 5.8 gbs
can you tell me what folders does it include?
edit:took me a few days to download, just don't want to download again
gandhar said:
allright, i have already synched the cm9 repo. about 5.8 gbs
can you tell me what folders does it include?
Click to expand...
Click to collapse
Are you thinking of the "clean" repo?
My ~/android/system/ consists of the following (remember the hidden directories):
abi
android
bionic
bootable
build
dalvik
development
device
external
frameworks
hardware
kernel
libcore
ndk
out
packages
prebuilt
sdk
system
vendor
.repo
.repoconfig
Makefile
You should be able to move your current directory and "just" sync it, to get it up to date.
hnl_dk said:
Are you thinking of the "clean" repo?
My ~/android/system/ consists of the following (remember the hidden directories):
abi
android
bionic
bootable
build
dalvik
development
device
external
frameworks
hardware
kernel
libcore
ndk
out
packages
prebuilt
sdk
system
vendor
.repo
.repoconfig
Makefile
Click to expand...
Click to collapse
allright, out of these except for kernel, out and .repoconfig i have all the others synced.
will using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
work?
i am missing kernel, out and .repoconfig
gandhar said:
allright, out of these except for kernel, out and .repoconfig i have all the others synced.
will using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
work?
i am missing kernel, out and .repoconfig
Click to expand...
Click to collapse
They are possibly first created when running brunch the first time. So it should be fine.
successfully building, but getting loads of warnings..
is that normal for the first build?
will report if it boots after compile is over.
gandhar said:
successfully building, but getting loads of warnings..
is that normal for the first build?
will report if it boots after compile is over.
Click to expand...
Click to collapse
There are lots of warnings.
Personally I usually remove all that warnings (using the -Werror option, so warnings get treated as errors) in the projects I am working on. But I understand why it can be a big problem with CM9, that is based on many different projects.
Looking forward to hear if you get a successful built.
hnl_dk said:
There are lots of warnings.
Personally I usually remove all that warnings (using the -Werror option, so warnings get treated as errors) in the projects I am working on. But I understand why it can be a big problem with CM9, that is based on many different projects.
Looking forward to hear if you get a successful built.
Click to expand...
Click to collapse
building will take some time...
well, most warnings are 'some variable has been set but not used', is that much significant?
gandhar said:
building will take some time...
well, most warnings are 'some variable has been set but not used', is that much significant?
Click to expand...
Click to collapse
Yes, first build takes a lot of time... the next times it will be a lot faster.
No that is not very significant, but things like that should still get fixed, to to make it easier to find the significant things.
The less warnings the more easy it is to spot what is important. This also goes for things that should get changed when upgrading to a new major version of the toolchain.
succesfull build!
phone:coconut-wt19i
time: 56 mins for the complete build.
cpu: 2.9 ghz - 4 cores
os:ubuntu 12.04 64 bit
backed up the phone.
boots into recovery
errorless install.
gandhar said:
phone:coconut-wt19i
time: 56 mins for the complete build.
cpu: 2.9 ghz - 4 cores
os:ubuntu 12.04 64 bit
backed up the phone.
boots into recovery
errorless install.
Click to expand...
Click to collapse
Super, looking forward to hear if everything is going to run as as should
hnl_dk said:
Super, looking forward to hear if everything is going to run as as should
Click to expand...
Click to collapse
running fine.
but i see some dependencies missing from the libs needed from
http://wiki.cyanogenmod.com/wiki/Template:Build_from_source_(CM9)
downloading them, will build again later..
is that the reason for the warnings?
gandhar said:
running fine.
but i see some dependencies missing from the libs needed from
http://wiki.cyanogenmod.com/wiki/Template:Build_from_source_(CM9)
downloading them, will build again later..
is that the reason for the warnings?
Click to expand...
Click to collapse
looks like a nice guide that is working with most devices, will save that link
No, the warnings are simply that you rarely find "clean" code, where most warnings have been fixed.
You also need to think of all the code from external projects.
You also only get many of the warnings, if you do not compile the code for some specific platforms.
hnl_dk said:
looks like a nice guide that is working with most devices, will save that link
No, the warnings are simply that you rarely find "clean" code, where most warnings have been fixed.
You also need to think of all the code from external projects.
You also only get many of the warnings, if you do not compile the code for some specific platforms.
Click to expand...
Click to collapse
saw that guide after i started checking for dependencies.
1.hey i see two zips in the output,
one cm-9-20120702-UNOFFICIAL-coconut and other cm_coconut-ota-eng.gandhar
the second is bigger.
i used the first one. why is the second one built i wonder?
2.i think of compiling aosp from source too, but the out folder is 11.3 gbs, what about that?
i do not want to end up falling short on space.
3.this is a system related question, how much will it hinder performance if i move the source to a different internal hd from the main one and build from there?
gandhar said:
saw that guide after i started checking for dependencies.
1.hey i see two zips in the output,
one cm-9-20120702-UNOFFICIAL-coconut and other cm_coconut-ota-eng.gandhar
the second is bigger.
i used the first one. why is the second one built i wonder?
Click to expand...
Click to collapse
Try to read the name ;-)
OTA - Over The Air... I guess that it can mbe used tfor OTA updates, like the mobile companies makes.
gandhar said:
2.i think of compiling aosp from source too, but the out folder is 11.3 gbs, what about that?
i do not want to end up falling short on space.
Click to expand...
Click to collapse
You could do a "make clear", but if you have enough space, would I keep it, so you do not need to wait for the already up to date files.
gandhar said:
3.this is a system related question, how much will it hinder performance if i move the source to a different internal hd from the main one and build from there?
Click to expand...
Click to collapse
There will be no problem with performance, as long as you move it to a HDD that is not too slow.
EDIT (July 2. 2012): I have made a patch to msm7x30-common, so you do not need to edit the file (with this patch does it automatically check if you run on a 64bit or a 32bit system):
http://code.google.com/p/freexperia/issues/detail?id=527
i do a repo sync again, at end of it i get errors on changed files. i think its not replacing the old files.
it's red text
error: bootable/recovery/: CyanogenMod/android_bootable_recovery checkout f8fc12e741d566af215407f35cfc52e5c1cc0023
error: build/: CyanogenMod/android_build checkout df7d6893a59e62c15dd20e306d8280b16969097c
error: external/openssl/: CyanogenMod/android_external_openssl checkout d4004ae717232b83ea445f74c881d9ddc24f589d
error: frameworks/base/: CyanogenMod/android_frameworks_base checkout e0a8c35c1572f0f0dbbda4d871d0a919a79cbe3f
error: hardware/samsung/: CyanogenMod/android_hardware_samsung checkout 23280fc439163a1971956167217283c4ae70bce3
error: packages/apps/Camera/: CyanogenMod/android_packages_apps_Camera checkout 644384a979ec9bd6b237e9031d5afbf592d3056b
error: packages/apps/Settings/: CyanogenMod/android_packages_apps_Settings checkout a946d9a905d460fa9d6c153e031285b566f8d223
error: system/core/: CyanogenMod/android_system_core checkout 389a2fa1d7e4bb8b6be411f272de2e8c92817964
gandhar said:
i do a repo sync again, at end of it i get errors on changed files. i think its not replacing the old files.
it's red text
error: bootable/recovery/: CyanogenMod/android_bootable_recovery checkout f8fc12e741d566af215407f35cfc52e5c1cc0023
error: build/: CyanogenMod/android_build checkout df7d6893a59e62c15dd20e306d8280b16969097c
error: external/openssl/: CyanogenMod/android_external_openssl checkout d4004ae717232b83ea445f74c881d9ddc24f589d
error: frameworks/base/: CyanogenMod/android_frameworks_base checkout e0a8c35c1572f0f0dbbda4d871d0a919a79cbe3f
error: hardware/samsung/: CyanogenMod/android_hardware_samsung checkout 23280fc439163a1971956167217283c4ae70bce3
error: packages/apps/Camera/: CyanogenMod/android_packages_apps_Camera checkout 644384a979ec9bd6b237e9031d5afbf592d3056b
error: packages/apps/Settings/: CyanogenMod/android_packages_apps_Settings checkout a946d9a905d460fa9d6c153e031285b566f8d223
error: system/core/: CyanogenMod/android_system_core checkout 389a2fa1d7e4bb8b6be411f272de2e8c92817964
Click to expand...
Click to collapse
Have not tried that.
You can try to do a "repo forall -c git reset --hard" this "resets" all the repositories (removes all changes, also if something has been corrupted).
hnl_dk said:
Have not tried that.
You can try to do a "repo forall -c git reset --hard" this "resets" all the repositories.
Click to expand...
Click to collapse
will it redownload?
Hello there,
I am trying to build a custom ROM for Samsung P3113 based on AOKP source on the jb branch. I was able to make "unofficial" release using "brunch aokp_p3113". However, when I attempted to make a distribution release, the "make -j4 dist" failed. The following are the commands I used:
. build/envsetup.sh
lunch aokp_p3113-userdebug
make -j4 dist
I got the following error messages:
device/moto/stingray/recovery/recovery_ui.cpp:22:20: fatal error: device.h: No such file or directory compilation terminated.
make: *** [out/target/product/p3113/obj/STATIC_LIBRARIES/librecovery_ui_stingray_intermediates/recovery_ui.o] Error 1
Can someone help? By the way, I don't need to build OTA package.
Found root cause
Found the root cause -
All the three header files needed by recovery_ui.cpp are missing. To workaround, I excluded the stingray recovery from the make, and the problem solved.
Hopefully, someone in the AOKP team will add the missing files to repository.
Hey guys, I have device tree from dianlujitao, hardware from codeaurora, Vendor and kernel source from official huawei, and try to compile cm11 for my device(HUAWEI honor 4X), but when making hardware/qcom/audio-caf/hal/audio_extn/ssr.c, I got this error message: no such header file "surround_filters_interface.h".
I search all of sync of source, google, github. still cant find header file "surround_filters_interface.h".
if guys can help, i would be grateful.
Code:
target arm C: audio.primary.msm8916 <= hardware/qcom/audio-caf/hal/audio_extn/ssr.c
hardware/qcom/audio-caf/hal/audio_extn/ssr.c:34:40: fatal error: surround_filters_interface.h: No such file or directory
compilation terminated.
make: *** [/android/cm11/out/target/product/c8817d/obj/SHARED_LIBRARIES/audio.primary.msm8916_intermediates/audio_extn/ssr.o] Error 1
make: leaving directory “/android/cm11”
[email protected]:/android/cm11#
You probably have AUDIO_FEATURE_ENABLED_SSR defined in your device, but audio-caf doesn't contain it. Look for and try to remove this in your BoardConfig.mk file in device tree.
mrjabol61 said:
You probably have AUDIO_FEATURE_ENABLED_SSR defined in your device, but audio-caf doesn't contain it. Look for and try to remove this in your BoardConfig.mk file in device tree.
Click to expand...
Click to collapse
It works, thank you!
Maybe I shouldn't change audio-caf.
Sometimes it's necessary to change something in repos, if you can't get it working.
Hey guys, I want to port a TWRP for my device.
My device is Micromax Canvas Juice 3+ a.k.a. Micromax Q394. It has MT6582 chipset, i.e. it is a MTK device.
I have prepared my device tree and vendor tree.
I synced the source of minimal manifest TWRP using the following commands.
Code:
repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-8.1
repo sync -j4
It synced successfully. After that I put my device tree and vendor tree at the appropriate locations and entered the following commands which you can see below but I got some errors.
Code:
(venv) [[email protected] twrp]$ . build/envsetup.sh
including device/Micromax/Q394/vendorsetup.sh
including vendor/omni/vendorsetup.sh
including sdk/bash_completion/adb.bash
(venv) [[email protected] twrp]$ lunch Q394
device/Micromax/Q394/Q394.mk:113: *** multiple target patterns. Stop.
WARNING: Trying to fetch a device that's already there
Traceback (most recent call last):
File "vendor/omni/build/tools/roomservice.py", line 355, in <module>
fetch_device(device)
File "vendor/omni/build/tools/roomservice.py", line 323, in fetch_device
git_data = search_gerrit_for_device(device)
File "vendor/omni/build/tools/roomservice.py", line 81, in search_gerrit_for_device
device_data = check_repo_exists(git_data, device)
File "vendor/omni/build/tools/roomservice.py", line 58, in check_repo_exists
"exiting roomservice".format(device=device))
Exception: Q394 not found,exiting roomservice
device/Micromax/Q394/Q394.mk:113: *** multiple target patterns. Stop.
** Don't have a product spec for: 'Q394'
** Do you have the right repo manifest?
(venv) [[email protected] twrp]$
What am I doing wrong? Please help
Thread closed per OP request.