Hi,
I have a Wiko Wax smartphone (Official page)
It's an NVIDIA® Tegra® 4i with Quad Core, 1.7 GHz soc.
I trying to build, in first time, a clean CM11.0 ROM without any bug. After what I'll try to make an CM12.1.
I have follow this GUIDE
I'm using mucski's device tree to build :
https://github.com/mucski/device_nvidia_s8515/ --> forked from Cpasjuste
https://github.com/mucski/kernel_nvidia_s8515 --> forked from Cpasjuste
https://github.com/mucski/proprietary_vendor_nvidia --> forked from TheMuppets
I succeful build a flashable zip but I want to fix some bugs:
1# can't move App to SD
2# the led color is orange (red/green) in charge
3# I've got "screen glitch" (?) sometimes
4# the bleutooth works in call but I can't stream music
5# I wan't add an OC kernel
My original thread is on wikoandco site. HERE but as you have understand it's in french because I'm !
Edit:
I'm found a CM12.1 working ROM for the Nvidia Sheildtablet with device tree which is nearly the same! Do you think I can use those sources for build a CM12.1 fo my the Wax ?
And what I need to edite for make it work ?
Hi, I'm not an expert so I can't help and unfortunately I don't know french, but I'm interested about your work because I'd like to have CM on my Wax!
Did you build the ROM without bug or you still have problems?
lemon_lama said:
Hi, I'm not an expert so I can't help and unfortunately I don't know french, but I'm interested about your work because I'd like to have CM on my Wax!
Did you build the ROM without bug or you still have problems?
Click to expand...
Click to collapse
Hi,
If build a working ROM but stile have all bugs mentioned in first post.
Pre-requires:
1# Install TWPR
(tuto in french)
Installation :
1# Backup your ROM (make sure your chose external sd folder)
2# Wipe Data / Factory reset / System / Internal storage
3# Install .zip
4# Reboot
You can find ZIP:
cm-11-20151022-UNOFFICIAL-s8515.zip
Google Apps:
3# Add .zip to list
Got to http://opengapps.org/
Chose ARM / 4.4 / variant you want
I use pico....
There's a folder duplication in gallery because Cpasjuste try to merge external and internal storage....
You can fix by editing /system/builp.prop
replace :
Code:
swapsd @ cpasjuste
config.swapsd=true
by:
Code:
swapsd @ cpasjuste
config.swapsd=false
CM13.0 branch
Hi, I'm trying to build a CM13.0 ROM for this device.
I use my specific manifest .repo/local_manifests/core.entin.xml
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<manifest>
<remove-project name="CyanogenMod/android_external_tinycompress"/>
<project path="external/tinycompress" name="BriceChk/tinycompress" remo$
<remove-project name="CyanogenMod/android_bootable_recovery"/>
<project path="bootable/recovery" name="omnirom/android_bootable_recove$
<!-- <project path="bootable/recovery" name="TeamWin/Team-Win-Recovery-Proje$
<project path="external/busybox" name="omnirom/android_external_busybox$
</manifest>
you can find my device tree :
https://github.com/coreentin/android_device_nvidia_s8515
I use following command to make the ROM :
Code:
source build/envsetup.sh
lunch cm_s8515-userdebug
make -j5 bacon
but the following error:
Code:
build/tools/generate-notice-files.py /home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/obj/NOTICE.txt /home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
Installing recovery patch to system partition
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 51, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/home/corentin/00_Android_build/WAX/CM13.0/build/tools/releasetools/common.py", line 1460, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File "/home/corentin/00_Android_build/WAX/CM13.0/build/tools/releasetools/common.py", line 1146, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/home/corentin/00_Android_build/WAX/CM13.0/build/tools/releasetools/common.py", line 100, in Run
return subprocess.Popen(args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [/home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/system/bin/install-recovery.sh] Erreur 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Is anyone can help me ?
Hi! I also have a Wiko Wax 4G (S8515) and I would love to get Android 6.0 working on this. I'm not a experienced person regarding creating roms, but I would like to help whatever I can on putting this to work.
Have you got any new news regading the rom?
Core.entin said:
Hi, I'm trying to build a CM13.0 ROM for this device.
I use my specific manifest .repo/local_manifests/core.entin.xml
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<manifest>
<remove-project name="CyanogenMod/android_external_tinycompress"/>
<project path="external/tinycompress" name="BriceChk/tinycompress" remo$
<remove-project name="CyanogenMod/android_bootable_recovery"/>
<project path="bootable/recovery" name="omnirom/android_bootable_recove$
<!-- <project path="bootable/recovery" name="TeamWin/Team-Win-Recovery-Proje$
<project path="external/busybox" name="omnirom/android_external_busybox$
</manifest>
you can find my device tree :
https://github.com/coreentin/android_device_nvidia_s8515
I use following command to make the ROM :
Code:
source build/envsetup.sh
lunch cm_s8515-userdebug
make -j5 bacon
but the following error:
Code:
build/tools/generate-notice-files.py /home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/obj/NOTICE.txt /home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
Installing recovery patch to system partition
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 51, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/home/corentin/00_Android_build/WAX/CM13.0/build/tools/releasetools/common.py", line 1460, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File "/home/corentin/00_Android_build/WAX/CM13.0/build/tools/releasetools/common.py", line 1146, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/home/corentin/00_Android_build/WAX/CM13.0/build/tools/releasetools/common.py", line 100, in Run
return subprocess.Popen(args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [/home/corentin/00_Android_build/WAX/CM13.0/out/target/product/s8515/system/bin/install-recovery.sh] Erreur 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Is anyone can help me ?
Click to expand...
Click to collapse
After upgrade my linux mitn to 18 (Sarah), and follow this GUIDE
I can't build a zip ROM anymore :
Code:
...
LD fs/built-in.o
Copy: /home/corentin/00_android_build/CM13.0/out/target/product/s8515/obj/STATIC_LIBRARIES/libext6_intermediates/libip6t_ipv6header.c
Copy: /home/corentin/00_android_build/CM13.0/out/target/product/s8515/obj/STATIC_LIBRARIES/libext6_intermediates/libip6t_NETMAP.c
Copy: /home/corentin/00_android_build/CM13.0/out/target/product/s8515/obj/STATIC_LIBRARIES/libext6_intermediates/libip6t_REDIRECT.c
Copy: /home/corentin/00_android_build/CM13.0/out/target/product/s8515/obj/STATIC_LIBRARIES/libext6_intermediates/libip6t_REJECT.c
Copy: /home/corentin/00_android_build/CM13.0/out/target/product/s8515/obj/STATIC_LIBRARIES/libext6_intermediates/libip6t_icmp6.c
Makefile:130*: la recette pour la cible «*sub-make*» a échouée
make[1]: *** [sub-make] Erreur 2
make[1]*: on quitte le répertoire «*/home/corentin/00_android_build/CM13.0/kernel/nvidia/s8515*»
build/core/tasks/kernel.mk:286*: la recette pour la cible «*TARGET_KERNEL_BINARIES*» a échouée
make: *** [TARGET_KERNEL_BINARIES] Erreur 2
make: *** Attente des tâches non terminées....
make*: on quitte le répertoire «*/home/corentin/00_android_build/CM13.0*»
Related
Hi all,
I'm trying to compile the kernel inline with my CM9 build. It builds fine without in-lining the kernel. I added the following to my device/samsung/p4wifi/cm.dependencies file:
Code:
[
{
"repository": "android_device_samsung_p4-common",
"target_path": "device/samsung/p4-common"
},
{
"repository": "android_kernel_samsung_p4",
"target_path": "kernel/samsung/p4wifi"
}
]
Then i added the following to my device/samsung/p4wifi/BoardConfig.mk
Code:
TARGET_KERNEL_CONFIG := samsung_p4wifi_defconfig
And when i try to build i get this error:
Code:
/root/android/system/kernel/samsung/p4wifi/kernel/sysctl.c:362: error: 'sysctl_sched_autogroup_handler' undeclared here (not in a function)
make[3]: *** [kernel/sysctl.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [kernel] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/root/android/system/kernel/samsung/p4wifi'
make: *** [TARGET_KERNEL_BINARIES] Error 2
Any ideas? Thanks.
I guess you're using CyanogenMod repo for the kernel, I suggest that you use pershoot's repo instead, it has the latest changes.
If you want, add this to your local_manifest.xml :
Code:
<project name="pershoot/android_device_samsung_p4-common" path="device/samsung/p4-common" />
<project name="pershoot/android_device_samsung_p4wifi" path="device/samsung/p4wifi" />
<project name="pershoot/android_vendor_samsung_p4wifi" path="vendor/samsung/p4wifi" />
<project name="pershoot/android_kernel_samsung_p4" path="kernel/samsung/p4wifi" />
And change your BoardConfig.mk (my guess is that this is why you're getting that error):
Code:
TARGET_KERNEL_CONFIG := pershoot_samsung_p4wifi-ics_defconfig
Thanks MapleSyrup, you were right, the TARGET_KERNEL_CONFIG was what was screwing it up. Now i'm going to switch over to pershoots repo.
I'm assuming i just have to delete my current
kernel/samsung/p4wifi
device/samsung/p4wifi
vender/samsung/p4wifi
device/samsung/p4-common
Directories before i add pershoots projects in?
Thanks again.
Not really, because git takes care of the update, but if you want, do it.
BTW, if you read the README in the kernel repo:
Note:
This kernel must be built with Codesourcery's 2010.09.
You can find this toolchain here:
http://droidbasement.com/androidTO/arm-2010.09.tar.gz
Click to expand...
Click to collapse
Change the variable ARM_EABI_TOOLCHAIN in your build/envsetup.sh to the directory (full path) of the decompressed toolchain (e.g. /path/to/arm-2010.09/bin). Comment the toolchaindir and the related if condition.
Also, you'll have to alter the variable ARM_CROSS_COMPILE in build/core/tasks/kernel.mk, changing the "arm-eabi-" part to "arm-none-eabi-".
To be sure, do a "make clean" (in your work directory. It will delete the out/ directory, in case you're using cache to speed up builds) before doing a new build (just this time).
Thanks, I did read the readme but had no clue about setting those variables. Everything is building perfectly now.
Thanks again for the help.
i want build P.A.C from souce
i have sync the repo but i cant build it using
build-pac.sh scripts for haida
any guide line / suggestion would be helpful.... :fingers-crossed:
I'm sure you will get better answer if you actually say which error you get.
Madfysh said:
I'm sure you will get better answer if you actually say which error you get.
Click to expand...
Click to collapse
[email protected]:~$ cd pac
[email protected]:~/pac$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/semc/haida/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pac/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/pac$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. mini_armv7a_neon-userdebug
5. mini_armv7a-userdebug
6. cm_haida-eng
7. full_panda-userdebug
8. pac_anzu-userdebug
9. pac_haida-userdebug
10. pac_mango-userdebug
11. pac_mint-userdebug
12. pac_smultron-userdebug
13. pac_urushi-userdebug
14. pac_zeus-userdebug
15. pac_zeusc-userdebug
16. pac_hercules-userdebug
17. pac_i9100-userdebug
18. pac_i9100g-userdebug
19. pac_quincyatt-userdebug
20. pac_skyrocket-userdebug
21. pac_i927-userdebug
22. pac_cooper-userdebug
23. pac_grouper-userdebug
24. pac_vigor-userdebug
25. pa_crespo-userdebug
26. pa_grouper-userdebug
27. pa_maguro-userdebug
28. pa_toro-userdebug
29. pa_toroplus-userdebug
Which would you like? [full-eng] 9
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/semc/haida/full_haida.mk]]: "device/semc/mogami-common/mogami.mk" does not exist. Stop.
Device haida not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 56, in <module>
result = json.loads(urllib2.urlopen(githubreq).read())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 400, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 418, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 1215, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open
raise URLError(err)
urllib2.URLError: <urlopen error [Errno 111] Connection refused>
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/semc/haida/full_haida.mk]]: "device/semc/mogami-common/mogami.mk" does not exist. Stop.
** Don't have a product spec for: 'pac_haida'
** Do you have the right repo manifest?
thats what i get.......
Any further progress on this?
arch_saiful said:
[email protected]:~$ cd pac
[email protected]:~/pac$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/semc/haida/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pac/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/pac$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. mini_armv7a_neon-userdebug
5. mini_armv7a-userdebug
6. cm_haida-eng
7. full_panda-userdebug
8. pac_anzu-userdebug
9. pac_haida-userdebug
10. pac_mango-userdebug
11. pac_mint-userdebug
12. pac_smultron-userdebug
13. pac_urushi-userdebug
14. pac_zeus-userdebug
15. pac_zeusc-userdebug
16. pac_hercules-userdebug
17. pac_i9100-userdebug
18. pac_i9100g-userdebug
19. pac_quincyatt-userdebug
20. pac_skyrocket-userdebug
21. pac_i927-userdebug
22. pac_cooper-userdebug
23. pac_grouper-userdebug
24. pac_vigor-userdebug
25. pa_crespo-userdebug
26. pa_grouper-userdebug
27. pa_maguro-userdebug
28. pa_toro-userdebug
29. pa_toroplus-userdebug
Which would you like? [full-eng] 9
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/semc/haida/full_haida.mk]]: "device/semc/mogami-common/mogami.mk" does not exist. Stop.
Device haida not found. Attempting to retrieve device repository from CyanogenMod Github
Traceback (most recent call last):
File "build/tools/roomservice.py", line 56, in <module>
result = json.loads(urllib2.urlopen(githubreq).read())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 400, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 418, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 1215, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open
raise URLError(err)
urllib2.URLError: <urlopen error [Errno 111] Connection refused>
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/semc/haida/full_haida.mk]]: "device/semc/mogami-common/mogami.mk" does not exist. Stop.
** Don't have a product spec for: 'pac_haida'
** Do you have the right repo manifest?
thats what i get.......
Click to expand...
Click to collapse
Currently, even I'm building from source (Carbon ROM) for Sony Xperia Pro and I got the same error. Could you help?
Hi,
I have been trying to build CM11 from source. I've basicly been following the build on the CM WIKI (http://wiki.cyanogenmod.org/w/Build_for_i9300)
I got as far as running "Brunch i9300" but it fails quickly with the follwoing error:
Code:
make: *** No rule to make target `vendor/samsung/smdk4412-common/proprietary/system/lib/libTVOut.so', needed by `/home/mark/cm11/out/target/product/i9300/obj/lib/libTVOut.so'. Stop.
I've googled a lot for a solution - but not made much progress!
1.. As far as I can work out libTVOut.so is a file proprietary file that I am supposed to extract from the my phone using the "extract-files.sh" script. I have run this an it does appear to complete sucessfully (i.e. it does pull a whole bunch of files) but libTVOut.so is notone of the files extracted.
2. It seems the alternative to running extract-files is to download the blobs from https://github.com/TheMuppets. However libTVOut.so is also not present there for the CM11 branch. (although does appear to be present for older branches (e.g. CM10.2).
Can anyone point in the right direction as I'm just about out of ideas?
Not to worry. I don't know the extract files method of getting the vendor blobs did not work, but I worked round the problem by delting the files in the vendor directory and adding a local manifest file.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-11.0" />
</manifest>
It's all working now!
mtdoughty said:
Not to worry. I don't know the extract files method of getting the vendor blobs did not work, but I worked round the problem by delting the files in the vendor directory and adding a local manifest file.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-11.0" />
</manifest>
It's all working now!
Click to expand...
Click to collapse
I have the same issue too, so hopefully this info will help me out to finally build CM 11 for the first time.
Could you be more specific on this fix? Is this a new xml file that I create? What's it called and where do I put it?
Thanks in advance
Hi,
Yes it is a new xml file you need to create with above contents. I don't think the file name matters (so long as it ends with ".xml". It needs to go into the local_manifests folder inside your .repo directory.
There is more of an explanation here:
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Good luck
hello
I have a problem with the creation of the manifest file for Sailfish os
in the documentation of sailfish os is that one should make it so :
You’ll have to create the local manifest yourself, which contains at least two repos: one for the kernel,
another for the device configuration. Find those CM device wiki, for Nexus 5 it would be http://wiki.
cyanogenmod.org/w/Hammerhead_Info inside the Source code table. Local manifest below will also
need pointing to correct branches - identify which one matches the default manifest branch.
Add the following content to $ANDROID_ROOT/.repo/local_manifests/$DEVICE.xml:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/hammerhead"
name="CyanogenMod/android_device_lge_hammerhead"
revision="stable/cm-11.0" />
<project path="kernel/lge/hammerhead"
name="CyanogenMod/android_kernel_lge_hammerhead"
revision="stable/cm-11.0" />
</manifest>
Time to sync the whole source code, this might take a while:
HABUILD_SDK $
hadk
repo sync --fetch-submodules
that is my manifest named kenzo_mm.xml :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/kenzo"
name="CyanogenMod/android_device_xiaomi_kenzo"
revision="cm-13.0" />
<project path="kernel/xiaomi/msm8956"
name="CyanogenMod/android_kernel_xiaomi_msm8956"
revision="cm-13.0" />
</manifest>
as described is the file in the folder
/home/xxxxxxxx/ANDROID_ROOT/.repo/local_manifests/kenzo_mm.xml
when i try repo init or sync I get error message :
[Error02] repo-about-git-head-error-manifest-missing-or-unreadable-please-run-init
thanx 4 Help
greetz
I helped myself , I thank you for helping all who helped me
noobstyle1337 said:
I helped myself , I thank you for helping all who helped me
Click to expand...
Click to collapse
Hey man, I have the same issue, what's the fix?
Benjimaestro said:
Hey man, I have the same issue, what's the fix?
Click to expand...
Click to collapse
I have the manifest file pushed into the .repo folder and could then sync
but now I have the next problem I if
wants breakfast kenzo do then I have another error with the manifest file
I have also downloaded to github all things kenzo per zip download and pulled in $ home / android folder and could then run extract-file.sh what not hasnt
I bite me through
somehow it seems to be so easy in the tutorial but the capabilities are not steps you have to tinker immediately until it works .
totally frustrating for me
all manifests are bull**** I start again
have again and start to point 5.4 everything works repo init has also but when I breakfast kenzo enter I get this error
including vendor/cm/vendorsetup.sh
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
Device kenzo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_xiaomi_kenzo
Default revision: stable/cm-13.0-ZNH0E
Checking branch info
Default revision stable/cm-13.0-ZNH0E not found in android_device_xiaomi_kenzo. Bailing.
Branches found:
cm-13.0
stable/cm-13.0-ZNH5Y
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
** Don't have a product spec for: 'cm_kenzo'
** Do you have the right repo manifest?
did you set the path to the ndk/sdk
export NDK=<path>/android-ndk
export ANDROID_NDK=<path>/android-ndk
export ANDROID_HOME=<path.d/android-sdk-linux
might not be 100% correct since it's been awhile since I compiled anything for android
noobstyle1337 said:
have again and start to point 5.4 everything works repo init has also but when I breakfast kenzo enter I get this error
including vendor/cm/vendorsetup.sh
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
Device kenzo not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_xiaomi_kenzo
Default revision: stable/cm-13.0-ZNH0E
Checking branch info
Default revision stable/cm-13.0-ZNH0E not found in android_device_xiaomi_kenzo. Bailing.
Branches found:
cm-13.0
stable/cm-13.0-ZNH5Y
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
** Don't have a product spec for: 'cm_kenzo'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Hi, i've got the same error trying to breakfast the device. Did you find a way to fix this error ? Thanks you a lot !
I have fixed the problem . it was the roomservice.xml . manifest file . which is really huge and there is much to write
I also have the mount points fixed but the problem is the build that he believed break CM13 is supported not right i think
unfortunately I have no internet in the Moment, I change to o2 I germany 'm working on it maybe I find the error during build if I may give you the tip a look here in redmi note 3 forum to the manifest file which is to build ads of nougat . which helped a lot you need you can take the frameworks , security almost everything . you have to test it unfortunately if I have internet again I can even upload my manifest file
noobstyle1337 said:
unfortunately I have no internet in the Moment, I change to o2 I germany 'm working on it maybe I find the error during build if I may give you the tip a look here in redmi note 3 forum to the manifest file which is to build ads of nougat . which helped a lot you need you can take the frameworks , security almost everything . you have to test it unfortunately if I have internet again I can even upload my manifest file
Click to expand...
Click to collapse
Thank you a lot. I will try giving a look to nougat manifest waiting for your manifest.
View attachment roomservice.xml.tar.gz
here is the manifest file
repo init -u git://github.com/mer-hybris/android.git -b hybris-13.0
but I do not know if you also hybris repos add intended or whether to remain in the default xml so but it will run first
otyg said:
did you set the path to the ndk/sdk
export NDK=<path>/android-ndk
export ANDROID_NDK=<path>/android-ndk
export ANDROID_HOME=<path.d/android-sdk-linux
might not be 100% correct since it's been awhile since I compiled anything for android
Click to expand...
Click to collapse
I had the paths not set thanks
noobstyle1337 said:
View attachment 3880405
here is the manifest file
repo init -u git://github.com/mer-hybris/android.git -b hybris-13.0
but I do not know if you also hybris repos add intended or whether to remain in the default xml so but it will run first
Click to expand...
Click to collapse
Hi ! Did you managed to run without errors the breakfast command with your manifest ? I tried it, but unfortunately I got always the same error.
Thank you in advance
it runs without error one should manifest the add before the repo sync
** Don't have a product spec for: 'cm_kenzo'
noobstyle1337 said:
have again and start to point 5.4 everything works repo init has also but when I breakfast kenzo enter I get this error
including vendor/cm/vendorsetup.sh
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
Device kenzo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_xiaomi_kenzo
Default revision: stable/cm-13.0-ZNH0E
Checking branch info
Default revision stable/cm-13.0-ZNH0E not found in android_device_xiaomi_kenzo. Bailing.
Branches found:
cm-13.0
stable/cm-13.0-ZNH5Y
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
** Don't have a product spec for: 'cm_kenzo'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
just saying...if thats the prob the solution is inside decive source,rename the "cm.mk" to "cm_kenzo.mk"...i had this prob lately and i solved it in that way :good:
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.