[Q] Cyanogenmod build (TARGET_DEVICE is empty) - Galaxy S III Q&A, Help & Troubleshooting

I'm try to build the cyanogenmod source. I find this and this tutorials.
but when i run "breakfast i9300" i get a error:
"build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop."
Seems like the TARGET_DEVICE is empty, but don't no how indicate that, i try to create a environment variable and everything but doesn't work.
Someone passing through this ?And/Or know how solve
Thanks for attention

What was the output of source build/envsetup.sh?
If in doubt, do everything again. Don't mix guides
Sent from my GT-I9300 using Tapatalk 2

espeansh been
rootSU said:
What was the output of source build/envsetup.sh?
If in doubt, do everything again. Don't mix guides
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I do everything again, and follow only the xda trhead, but the error keep
when i run
Code:
. build/envsetup.sh && breakfast i9300
I have the follow output:
Seems the envsetup execute with success but the brakfast don't
have some enviroment that i need to create ? or only add android bin from path ?
Code:
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
Looking for dependencies
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
Can't find toolchain for unknown architecture:
Can't find toolchain for unknown architecture:
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.

Related

Build CNA error

Hello guys! I have installed pre-resequites,repo init,repo sync..when i'm building i got this error:
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `test-runner/src': No such file or directory
find: `test-runner/src': No such file or directory
find: `src': No such file or directory
im runnin' ubuntu 11.10.Some help?
oblikas said:
Hello guys! I have installed pre-resequites,repo init,repo sync..when i'm building i got this error:
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `test-runner/src': No such file or directory
find: `test-runner/src': No such file or directory
find: `src': No such file or directory
im runnin' ubuntu 11.10.Some help?
Click to expand...
Click to collapse
Try updating the OS, 11.10 is no longer supported.
Update to 12.04?

[Q] CM10.1 Won't suddenly won't build (No rule to make target...)

This isn't the first time I've tried to build Cyanogenmod for my i9100 on Ubuntu 12.10; I've done it successfully a few times before. However recently, it has just refused to build.
Code:
lunch cm_i9100-userdebug && mka
gave a bunch of errors: http://pastebin.com/Mn3YLZDY.
Code:
brunch cm_i9100-userdebug
gives different errors: http://pastebin.com/xiv4ettD. Teamhacksung's build script also gives the exact same errors. I tried starting in a new directory from scratch, but I still get the same errors.
The parts that look suspicious to me are
Code:
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
(/home/ari/android/system/external/apache-harmony does exist) and
Code:
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
find: `src': No such file or directory
I think this could be related to a repo sync problem I had/have where it couldn't download anything properly with lots of
Code:
Connection reset by peer
errors, although I think it has now synced (df -h shows 15GB). I also ran
Code:
repo forall -c "git fsck && git gc"
which "repairs" each repository, and that didn't give any errors.
Can anyone help with getting this to build?
EDIT: I found a post on the Android Building mailing list that was similar, and the suggestion to run
Code:
export CDPATH=""
(previously, $CDPATH=".")
got CM to build much further than before. No idea how this works, but it does.
However there are now more errors later during the build, e.g.
Code:
make: *** No rule to make target `/media/build/android/out/system/target/product/i9100/obj/lib/libTVOut.so', needed by `/media/build/android/out/system/target/product/i9100/obj/EXECUTABLES/mediaserver_intermediates/LINKED/mediaserver'. Stop.
It seems to have built a .zip flashable file now:
Code:
Package complete: /media/build/android/out/system/target/product/i9100/cm-10.1-20130121-UNOFFICIAL-i9100.zip
md5: f9fe076a6f0dfe140329e94ce6aa1867
Creating kernel zip...
Bootimage found...
No instructions to create out/target/product/i9100/kernel-cm-10.1-20130121-i9100-signed.zip... skipping.
Elapsed: 47 min(s) 20 sec(s)
but it says it can't create a kernel zip?

Help MultiROM

This MultiROM trying to install but I get the following error:
Log
Installing '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Installing MultiROM for condor
Extracting binaries...
about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p36 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/busybox] with 3 args
minzip: Extracted 40 file(s)
minzip: Extracted 6 file(s)
about to run program [/tmp/extract_multirom.sh] with 1 args
mkdir: can't create directory '/data/media/0/multirom': Permission denied
chown: /data/media/0/multirom: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
mkdir: can't create directory '/data/media/0/multirom/roms': No such file or directory
chown: /data/media/0/multirom/roms: No such file or directory
chmod: /data/media/0/multirom/roms: No such file or directory
touch: /data/media/0/multirom/.nomedia: No such file or directory
chown: /data/media/0/multirom/.nomedia: No such file or directory
rm: can't remove '/data/media/0/multirom/boot.img-ubuntu*': No such file or directory
rm: can't remove '/data/media/0/multirom/infos/*': No such file or directory
rm: can't remove '/data/media/0/multirom/res/*': No such file or directory
cp: can't create '/data/media/0/multirom/adbd': No such file or directory
cp: can't create '/data/media/0/multirom/busybox': No such file or directory
cp: can't create '/data/media/0/multirom/exfat-fuse': No such file or directory
cp: can't create '/data/media/0/multirom/fw_mounter': No such file or directory
cp: can't create directory '/data/media/0/multirom/icons': No such file or directory
cp: can't create '/data/media/0/multirom/kexec': No such file or directory
cp: can't create '/data/media/0/multirom/lz4': No such file or directory
cp: can't create '/data/media/0/multirom/mrom.fstab': No such file or directory
cp: can't create '/data/media/0/multirom/multirom': No such file or directory
cp: can't create '/data/media/0/multirom/ntfs-3g': No such file or directory
cp: can't create directory '/data/media/0/multirom/res': No such file or directory
cp: can't create '/data/media/0/multirom/trampoline': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-sysimage-init': No such file or directory
chmod: /data/media/0/multirom/multirom: No such file or directory
chmod: /data/media/0/multirom/busybox: No such file or directory
chmod: /data/media/0/multirom/trampoline: No such file or directory
chmod: /data/media/0/multirom/kexec: No such file or directory
chmod: /data/media/0/multirom/ntfs-3g: No such file or directory
chmod: /data/media/0/multirom/exfat-fuse: No such file or directory
chmod: /data/media/0/multirom/lz4: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/local: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
chown: /data/media/0/multirom: No such file or directory
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/extract_multirom.sh") == 0
assert failed: run_program("/tmp/extract_multirom.sh") == 0
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'
Error flashing zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip
Now edit the build.prop but I get the same error also delete the first lines of updater.script and follows me out the same. I just worked with me but I want to install cm11 in stock
Sorry for my bad English
Which rom you are using as a primary rom
prajapati ravi said:
Which rom you are using as a primary rom
Click to expand...
Click to collapse
I'm using the stock
Then whats the problem add the cm11 and reboot
---------- Post added at 01:20 AM ---------- Previous post was at 01:16 AM ----------
magdeoz said:
I'm using the stock
Click to expand...
Click to collapse
If you use stock as primary rom then will not get any issue's if still get it then you doing something wrong with your hand

[Q] Proprietary files missing in CyanogenMod BLOB

I'm building CM12 for XL. While trying to extract proprietary BLOB, I could see that latest NIGHTLY builds (e.g. cm-12-20150308-NIGHTLY-taoshan.zip) have a different structure from earlier EXPERIMENTAL builds (e.g. cm-11-20150112-EXPERIMENTAL-taoshan.zip)
-----------------------------------
Structure of NIGHTLY build:
-----------------------------------
install
META-INF
system
file_contexts
system.new.dat
system.patch.dat
system.transfer.list
boot.img
--------------------------------------------
Structure of EXPERIMENTAL build:
---------------------------------------------
META-INF
system
file_contexts
boot.img
I failed to extract ANY proprietary file from NIGHTLY build, because 'system' directory contains a single file: system\build.prop. On the contrary, the size of system.new.dat is very large: 427MB. I could extract all but three files from EXPERIMENTAL build as 'system' directory contains a collection of other required files, as expected. Ultimately, following three files are missing from the BLOB:
Code:
cp: cannot stat '/home/androbuild/original/system/bin/led_deamon': No such file or directory
cp: cannot stat '/home/androbuild/original/system/bin/led_deamon': No such file or directory
cp: cannot stat '/home/androbuild/original/system/etc/firmware/libpn544_fw.so': No such file or directory
cp: cannot stat '/home/androbuild/original/system/etc/firmware/libpn544_fw.so': No such file or directory
cp: cannot stat '/home/androbuild/original/system/vendor/lib/libtime_genoff.so': No such file or directory
cp: cannot stat '/home/androbuild/original/system/vendor/lib/libtime_genoff.so': No such file or directory
Because of 'libtime_genoff.so' being missing, my build is failing after running for ~7 hours. Any idea how to obtain three files as mentioned above?

[ROOT] Doogee T3

Hi all,
Im trying to root my Doogee T3 but haven't been sucessfull so far. Seems like no one tried before or posted about it.
It has a
Mediatek MT6753,
so MTKdroidTools should work but it gives a few errors:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I tried to install twrp but it doesnt seem to work on this device. Happy if you prove me wrong.
I found a guide to root a Doogee F5, same chipset as the T3 so I gave it a shot.
(adb_log at the end, obviously a disaster)
Maybe there is a way to use the User2Root option of the MTK Engineer Mode? Like used in the F5 guide but I dont really understand what it actually does. I understand that its trying to change the linux-like persmissions and that it doesn't find anything, but thats it.
Lets skip this stuff:
-Yes, USB debugging and OEM unlocking are enabled
-Yes, I do have adb and fastboot
-Yes, I do have the drivers
-I already tried previous MTKdroidTools Versions
-KingRoot doesn't work
-RootGenius doesn't work
-Framaroot doesn't work
-I wasn't able to create a scatter file but found one for MT6753 online
adb log of Doogee F5 method:
Code:
DrĀcken Sie eine beliebige Taste . . .
mount: Read-only file system
/system/bin/sh: can't create /system/toolbox: Read-only file system
chmod: /system/toolbox: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
mkdir: '/system/bin/.ext': Read-only file system
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext: No such file or directory
chmod: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
mkdir: '/system/app/SuperSU': Read-only file system
rm: /system/bin/.ext/.su: No such file or directory
failed to copy 'su_bin/su' to '/system/bin/.ext/.su': Read-only file system
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/su: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/su': Read-only file system
chown: /system/xbin/su: No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/daemonsu: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/daemonsu': Read-only file system
chown: /system/xbin/daemonsu: No such file or directory
chown: /system/xbin/daemonsu: No such file or directory
chmod: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/sugote: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/sugote': Read-only file system
chown: /system/xbin/sugote: No such file or directory
chown: /system/xbin/sugote: No such file or directory
chmod: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
rm: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: can't create /system/xbin/sugote-mksh: Read-only file system
chown: /system/xbin/sugote-mksh: No such file or directory
chown: /system/xbin/sugote-mksh: No such file or directory
chmod: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/supolicy: No such file or directory
failed to copy 'su_bin/supolicy' to '/system/xbin/supolicy': Read-only file system
chown: /system/xbin/supolicy: No such file or directory
chown: /system/xbin/supolicy: No such file or directory
chmod: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/lib64/libsupol.so: No such file or directory
failed to copy 'su_bin/libsupol.so' to '/system/lib64/libsupol.so': Read-only file system
chown: /system/lib64/libsupol.so: No such file or directory
chown: /system/lib64/libsupol.so: No such file or directory
chmod: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
chown: /system/app/SuperSU: No such file or directory
chown: /system/app/SuperSU: No such file or directory
chmod: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/app/SuperSU/SuperSU.apk: No such file or directory
failed to copy 'su_bin/Superuser.apk' to '/system/app/SuperSU/SuperSU.apk': Read-only file system
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chmod: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/install-recovery.sh: No such file or directory
failed to copy 'su_bin/install-recovery.sh' to '/system/etc/install-recovery.sh': Read-only file system
chown: /system/etc/install-recovery.sh: No such file or directory
chown: /system/etc/install-recovery.sh: No such file or directory
chmod: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/etc/install-recovery.sh' to '/system/bin/install-recovery.sh': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/install-recovery.sh' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/install-recovery.sh' to u:object_r:system_file:s0: Read-only file system
rm: /system/bin/app_process: Read-only file system
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/xbin/daemonsu' to '/system/bin/app_process': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process' to u:object_r:system_file:s0: Read-only file system
mv: bad '/system/bin/app_process64': Read-only file system
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/xbin/daemonsu' to '/system/bin/app_process64': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process64' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process64' to u:object_r:system_file:s0: Read-only file system
rm: /system/bin/app_process_init: No such file or directory
/system/bin/sh: can't create /system/bin/app_process_init: Read-only file system
chown: /system/bin/app_process_init: No such file or directory
chown: /system/bin/app_process_init: No such file or directory
chmod: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/init.d/99SuperSUDaemon: No such file or directory
failed to copy 'su_bin/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Read-only file system
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chmod: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments

Categories

Resources