Hello,
I'm trying to build the lineageOS cm-14.1 version for Cancro
the build process stops here:
Code:
make: *** No rule to make target 'vendor/xiaomi/cancro/proprietary/bin/wcnss_service', needed by '/android/lineage/out/target/product/cancro/system/bin/wcnss_service'. Stop.
I followed the steps from the LineageOS guide ( https://wiki.lineageos.org/devices/cancro/build#prepare-the-device-specific-code ) in order to get the proprietary blobs and as I can see the next ones are not extracted (because doesn't exists):
Code:
/cranco/android/lineage/device/xiaomi/cancro$ ./extract-files.sh
Cleaning output directory (./../../../vendor/xiaomi/cancro/proprietary)..
Extracting 494 files in ./proprietary-files.txt from adb:
/system/bin/adsprpcd: 1 file pulled. 0.3 MB/s (13944 bytes in 0.043s)
adb: error: remote object '/system/bin/btnvtool' does not exist
adb: error: remote object '/system/bin/btnvtool' does not exist
adb: error: remote object '/system/bin/charger_monitor' does not exist
adb: error: remote object '/system/bin/charger_monitor' does not exist
adb: error: remote object '/system/bin/hvdcp' does not exist
adb: error: remote object '/system/bin/hvdcp' does not exist
adb: error: remote object '/system/bin/loc_launcher' does not exist
adb: error: remote object '/system/bin/loc_launcher' does not exist
adb: error: remote object '/system/bin/wcnss_filter' does not exist
adb: error: remote object '/system/bin/wcnss_filter' does not exist
adb: error: remote object '/system/bin/wcnss_service' does not exist
adb: error: remote object '/system/bin/wcnss_service' does not exist
adb: error: remote object '/system/lib/libdrmdecrypt.so' does not exist
adb: error: remote object '/system/lib/libdrmdecrypt.so' does not exist
adb: error: remote object '/system/vendor/lib/hw/activity_recognition.msm8974.so' does not exist
adb: error: remote object '/system/vendor/lib/hw/activity_recognition.msm8974.so' does not exist
adb: error: remote object '/system/vendor/lib/libQSEEComAPI.so' does not exist
adb: error: remote object '/system/vendor/lib/libQSEEComAPI.so' does not exist
adb: error: remote object '/system/vendor/lib/libbccQTI.so' does not exist
adb: error: remote object '/system/vendor/lib/libbccQTI.so' does not exist
Code:
android/lineage/vendor/xiaomi/cancro/proprietary/bin$ ls
adsprpcd fm_qsoc_patches irsc_util lowi-server mm-qcamera-daemon mpdecision netmgrd qmuxd qosmgr qseecomd quipc_igsn quipc_main radish rfs_access rmt_storage sensors.qcom time_daemon xtwifi-client xtwifi-inet-agent
how can I get these files in order to finish my build?
My xiaomi is running LineageOS 14.1 20170626-nightly
as I can see on the guide, I did it correctly:
Extract proprietary blobs
Note: This step requires to have a device already running the latest LineageOS, based on the branch you wish to build for. If you don’t have access to such device, refer to Extracting proprietary blobs from installable zip.
Now ensure your Mi 3 / Mi 4 is connected to your computer via the USB cable, with ADB and root enabled, and that you are in the ~/android/lineage/device/xiaomi/cancro folder. Then run the extract-files.sh script:
./extract-files.sh
The blobs should be pulled into the ~/android/lineage/vendor/xiaomi folder. If you see “command not found” errors, adb may need to be placed in ~/bin.
Click to expand...
Click to collapse
EDIT: I just found the next ones: https://github.com/TheMuppets/proprietary_vendor_xiaomi/tree/cm-14.1/cancro/proprietary
Can I use them in order to finish my build?
EDIT: With the last proprietary blobs I still missing one:
Code:
make: *** No rule to make target 'vendor/xiaomi/cancro/proprietary/bin/loc_launcher', needed by 'android/lineage/out/target/product/cancro/system/bin/loc_launcher'. Stop.
any ideas ?
thanks, Ivan
Related
Evening All,
I am attempting to compile a kernel for my droid incredible and am running into a problem. I successfully compiled one a few weeks ago, but am trying to refresh so i can learn more. I am using instructions found at:
http://wiki.cyanogenmod.com/index.php?title=Building_from_source,
only changing commands when necessary. I have pulled a working .config from Skyraider 2.2, created the backup and was able to edit it to my liking. For this I decided to leave everything as stock, as my intention was to just compile the stock kernel to help myself learn. When I enter
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER
,
I receive the following error:
Code:
[email protected]:~/androkern/incredible$ make ARCH=arm CROSS_COMPILE=$CCOMPILER
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
Generating include/asm-arm/mach-types.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mno-thumb-interwork"
kernel/bounds.c:1: error: unknown ABI (aapcs-linux) for -mabi= switch
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Being new to compiling would anyone be able to help me understand what this error means. I have not found anything so far that could help me. I was not expecting any issues since I was essential just compiling the Stock Kernel for my own use.
Would someone be able to help me learn what is causing this? Thank you.
tcberg2010 said:
Evening All,
I am attempting to compile a kernel for my droid incredible and am running into a problem. I successfully compiled one a few weeks ago, but am trying to refresh so i can learn more. I am using instructions found at:
http://wiki.cyanogenmod.com/index.php?title=Building_from_source,
only changing commands when necessary. I have pulled a working .config from Skyraider 2.2, created the backup and was able to edit it to my liking. For this I decided to leave everything as stock, as my intention was to just compile the stock kernel to help myself learn. When I enter
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER
,
I receive the following error:
Code:
[email protected]:~/androkern/incredible$ make ARCH=arm CROSS_COMPILE=$CCOMPILER
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
Generating include/asm-arm/mach-types.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mno-thumb-interwork"
kernel/bounds.c:1: error: unknown ABI (aapcs-linux) for -mabi= switch
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Being new to compiling would anyone be able to help me understand what this error means. I have not found anything so far that could help me. I was not expecting any issues since I was essential just compiling the Stock Kernel for my own use.
Would someone be able to help me learn what is causing this? Thank you.
Click to expand...
Click to collapse
you need to do:
export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
(assuming you pulled everything down in ~/mydroid , otherwise change it to where it is)
then you should be able to compile it
That command did work for me. I was able to compile it. What I would still like to know is what exactly I did when i ran that command? I don't really enjoy mashing in commands when i don't know what they mean.
Basically you created an environmental variable called CCOMPILER that is equal to the location of the cross compiler binaries.
This command would do the same thing:
make ARCH=arm CROSS_COMPILE=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
You are just pointing the make file to the location of the cross compiler so that it doesn't use the host compiler by default
mattwood2000 said:
Basically you created an environmental variable called CCOMPILER that is equal to the location of the cross compiler binaries.
This command would do the same thing:
make ARCH=arm CROSS_COMPILE=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
You are just pointing the make file to the location of the cross compiler so that it doesn't use the host compiler by default
Click to expand...
Click to collapse
+1 Whenever you "export" you're setting an environment variable to something. Then you can verify it by typing: "echo $CCOMPILER" (without quotes) and it should spit that path back at you.
fwiw, you can add that line to your .bashrc and it will always be set for you
Thank you guys, to be honest that answer is a little over my head, but its a nice basis to help me learn more. Really appreciate the quick responses.
Sent from my ADR6300 using XDA App
i really wanna use that govanor barry allan so i wanna recompile cm kernel with barry allan integrated but im always getting that error
gcc: error: unrecognized argument in option '-mabi=apcs-gnu'
gcc: note: valid arguments to '-mabi=' are: ms sysv
gcc: error: unrecognized command line option '-mlittle-endian'
gcc: error: unrecognized command line option '-mapcs'
gcc: error: unrecognized command line option '-mno-sched-prolog'
Hello,
I downgraded my lolipop to kitkat then rooted and I want to instal dualrecovery. I don't know exactly what to do with it. I want to install xposed + lolipop thats why I'm needing recovery. BTW. Sorry for my english
Please look at the log:
=============================================
Getting device and ROM info
=============================================
Device model is D5503
Firmware is 14.4.A.0.108
Android version is 4.4.4
=============================================
Step2 : Sending the recovery files.
=============================================
adb: error: cannot stat '..\tmp\dr.prop': No such file or directory
adb: error: cannot stat '..\system\bin\chargemon': No such file or directory
adb: error: cannot stat '..\system\bin\mr': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\dualrecovery.sh': No such file or directory
adb: error: cannot stat '..\tmp\NDRUtils.apk': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\rickiller.sh': No such file or directory
adb: error: cannot stat '..\tmp\byeselinux.ko': No such file or directory
adb: error: cannot stat 'byeselinux\byeselinux.sh': No such file or directory
adb: error: cannot stat '..\tmp\wp_mod.ko': No such file or directory
adb: error: cannot stat 'byeselinux\sysrw.sh': No such file or directory
adb: error: cannot stat '..\tmp\modulecrcpatch': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\busybox': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma': No such file or directory
adb: error: cannot stat '..\tmp\installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Unable to open /data/local/tmp/recovery/busybox: No such file or directory
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
sh: /data/local/tmp/recovery/busybox: not found
Press any key to continue . . .
sh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
PMMD123 said:
Hello,
I downgraded my lolipop to kitkat then rooted and I want to instal dualrecovery. I don't know exactly what to do with it. I want to install xposed + lolipop thats why I'm needing recovery. BTW. Sorry for my english
Please look at the log:
=============================================
Getting device and ROM info
=============================================
Device model is D5503
Firmware is 14.4.A.0.108
Android version is 4.4.4
=============================================
Step2 : Sending the recovery files.
=============================================
adb: error: cannot stat '..\tmp\dr.prop': No such file or directory
adb: error: cannot stat '..\system\bin\chargemon': No such file or directory
adb: error: cannot stat '..\system\bin\mr': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\dualrecovery.sh': No such file or directory
adb: error: cannot stat '..\tmp\NDRUtils.apk': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\rickiller.sh': No such file or directory
adb: error: cannot stat '..\tmp\byeselinux.ko': No such file or directory
adb: error: cannot stat 'byeselinux\byeselinux.sh': No such file or directory
adb: error: cannot stat '..\tmp\wp_mod.ko': No such file or directory
adb: error: cannot stat 'byeselinux\sysrw.sh': No such file or directory
adb: error: cannot stat '..\tmp\modulecrcpatch': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\busybox': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma': No such file or directory
adb: error: cannot stat '..\tmp\installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Unable to open /data/local/tmp/recovery/busybox: No such file or directory
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
sh: /data/local/tmp/recovery/busybox: not found
Press any key to continue . . .
sh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
Click to expand...
Click to collapse
I've never seen that error message,but my first guess would probably be wrong menu choice. When you first open the dual recovery bat file, you get a prompt to enter #1, 2, 3, or 4. Double check and make sure you pick right. Also make sure you downloaded the right file.
Im sure that I have right file and I press 1. Personally I think thats a problem connected with windows 10 :/
PMMD123 said:
Im sure that I have right file and I press 1. Personally I think thats a problem connected with windows 10 :/
Click to expand...
Click to collapse
Maybe first root your device with kingoroot then choose number 2
I'll try but error for example error: "adb: error: cannot stat '..\tmp\dr.prop': No such file or directory" means that installer can't find the right path to file right?
EDIT:
As I expected... After reflashing, rooting with Kingo ROOT + SuperUser
=============================================
Getting device and ROM info
=============================================
Device model is D5503
Firmware is 14.4.A.0.108
Android version is 4.4.4
=============================================
Step2 : Sending the recovery files.
=============================================
adb: error: cannot stat '..\tmp\dr.prop': No such file or directory
adb: error: cannot stat '..\system\bin\chargemon': No such file or directory
adb: error: cannot stat '..\system\bin\mr': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\dualrecovery.sh': No such file or directory
adb: error: cannot stat '..\tmp\NDRUtils.apk': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\rickiller.sh': No such file or directory
adb: error: cannot stat '..\tmp\byeselinux.ko': No such file or directory
adb: error: cannot stat 'byeselinux\byeselinux.sh': No such file or directory
adb: error: cannot stat '..\tmp\wp_mod.ko': No such file or directory
adb: error: cannot stat 'byeselinux\sysrw.sh': No such file or directory
adb: error: cannot stat '..\tmp\modulecrcpatch': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\busybox': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma': No such file or directory
adb: error: cannot stat '..\tmp\installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Unable to open /data/local/tmp/recovery/busybox: No such file or directory
tmp-mksh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
PMMD123 said:
I'll try but error for example error: "adb: error: cannot stat '..\tmp\dr.prop': No such file or directory" means that installer can't find the right path to file right?
EDIT:
As I expected... After reflashing, rooting with Kingo ROOT + SuperUser
=============================================
Getting device and ROM info
=============================================
Device model is D5503
Firmware is 14.4.A.0.108
Android version is 4.4.4
=============================================
Step2 : Sending the recovery files.
=============================================
adb: error: cannot stat '..\tmp\dr.prop': No such file or directory
adb: error: cannot stat '..\system\bin\chargemon': No such file or directory
adb: error: cannot stat '..\system\bin\mr': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\dualrecovery.sh': No such file or directory
adb: error: cannot stat '..\tmp\NDRUtils.apk': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\rickiller.sh': No such file or directory
adb: error: cannot stat '..\tmp\byeselinux.ko': No such file or directory
adb: error: cannot stat 'byeselinux\byeselinux.sh': No such file or directory
adb: error: cannot stat '..\tmp\wp_mod.ko': No such file or directory
adb: error: cannot stat 'byeselinux\sysrw.sh': No such file or directory
adb: error: cannot stat '..\tmp\modulecrcpatch': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\busybox': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma': No such file or directory
adb: error: cannot stat '..\tmp\installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Unable to open /data/local/tmp/recovery/busybox: No such file or directory
tmp-mksh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
Click to expand...
Click to collapse
You might be right about the Windows 10 thing... Did you do this --
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
Thats a good idea coz I couldn't do that yesterday because of being a new member now I've permission thank you! I hope it will help
Problem solved
C:\adb>adb connect 192.168.100.13
connected to 192.168.100.13:5555
C:\adb>adb install AlarmClock_v2.9.2.apk
error: more than one device and emulator
- waiting for device -
error: protocol fault (status read)
error: protocol fault (status read)
- waiting for device -
^C
----------------
C:\adb>adb connect 192.168.100.13
connected to 192.168.100.13:5555
C:\adb>adb shell
error: more than one device and emulator
-----------------------------solved
C:\adb>adb devices
List of devices attached
1a13899 device
192.168.100.13:5555 device
C:\adb>adb -s 1a13899 shell
[email protected]:/ $ exit
C:\adb>adb -s 1a13899 install AlarmClock_v2.9.2.apk
adb -s 1a13899 push LetItGo.mp3 /sdcard/
Hello everyone,
I tried to root my Mi Mix 2 with XiaoMiTool V2 but I have got a problem during the step of pushing file magisk_20.4.zip.
In the log, I can see :
[10:07:04][PSTA ][70c729f4] Start process (781): "C:\Xiaomi\XiaomiTool2\res\tools\adb.exe" "-s" "ebf1f094" "push" "C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip" "/sdcard/magisk_20.4.zip"
[10:07:05][PROC ][55e63029] Process (781) output: adb: error: failed to copy 'C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip' to '/sdcard/magisk_20.4.zip': remote couldn't create file: No such file or directory
[10:07:05][PROC ][55e63029] Process (781) output: C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip: 1 file pushed, 0 skipped. 48.9 MB/s (5942417 bytes in 0.116s)
[10:07:05][INFO ][70c729f4] Process (781) ended with exit code: 1, output len: 268
[10:07:05][ERROR ][70c729f4] Task error: exception: Failed to push file to the device: adb: error: failed to copy 'C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip' to '/sdcard/magisk_20.4.zip': remote couldn't create file: No such file or directory : AdbPushTask -> status: RUNNING
Can you help me ??
Thanks by advance !
Do you know an other way to root it easily ?
Thanks by advance.