Cm12 Build Failed For Oneplus One
Solution 1:
I faced the same problem, Its due to cyanogenmod not keeping their dependencies updated.
Here is the solution:
1.) Go to your base directory where you have all the code (croot) and run the following commands: $ mkdir .repo/local_manifests $ nano .repo/local_manifests/local_manifests.xml (You can name it anything you like)
2.) Paste the following lines into local_manifests.xml:
<?xml version="1.0" encoding="UTF-8"?><manifest><projectname="CyanogenMod/android_device_oneplus_bacon"path="device/oneplus/bacon"remote="github"revision="cm-12.1" /><projectname="CyanogenMod/android_device_qcom_common"path="device/qcom/common"remote="github"revision="cm-12.1" /><projectname="CyanogenMod/android_device_oppo_msm8974-common"path="device/oppo/msm8974-common"remote="github"revision="cm-12.1" /><projectname="CyanogenMod/android_device_oppo_common"path="device/oppo/common"remote="github"revision="cm-12.1" /><projectname="CyanogenMod/android_kernel_oneplus_msm8974"path="kernel/oneplus/msm8974"remote="github"revision="cm-12.1" /><projectname="TheMuppets/proprietary_vendor_oppo"path="vendor/oppo"remote="github"revision="cm-12.1" /><projectname="TheMuppets/proprietary_vendor_oneplus"path="vendor/oneplus"remote="github"revision="cm-12.1" /></manifest>
3.) Follow rest of the guide. You can now also exclude "Extract proprietary blobs" section as all the files extracted from device (heMuppets/proprietary_vendor_oneplus) are already listed in local_manifests.xml
I hope this helps.
Solution 2:
I found that if I take device/qcom/comon/dbtool
and place it in (in my case) msm8916-common
this fixed the problem. I am not sure why, maybe it only associates qcom
common with the msm
devices, listed next to common idk but this works as a fix, hope it helps :)
Post a Comment for "Cm12 Build Failed For Oneplus One"