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
Related
Alright. I'm attempting to get backtrack running. Obviously. Here's my terminal thus far.
[email protected]:/ $ su
[email protected]:/ # cd sdcard/BT5 # sh bootbt
[email protected]:/sdcard/BT5 # sh bootbt
Loop device exists
open backing file failed: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt[23]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
bootbt[24]: can't create /data/local/mnt/etc/hosts: No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/sdcard/BT5 #
As you can see. I have superuser rights and the file exists in that area. So I'm not sure why it won't work.
I'm running CyanogenMod 10.1.2 and I have busy box smart installed using the Terminal Emulator. Downloaded backtrack 5 arm version from the website itself and extracted it to sdcard/BT5
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ryno9100 said:
Alright. I'm attempting to get backtrack running. Obviously. Here's my terminal thus far.
[email protected]:/ $ su
[email protected]:/ # cd sdcard/BT5 # sh bootbt
[email protected]:/sdcard/BT5 # sh bootbt
Loop device exists
open backing file failed: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt[23]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
bootbt[24]: can't create /data/local/mnt/etc/hosts: No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/sdcard/BT5 #
As you can see. I have superuser rights and the file exists in that area. So I'm not sure why it won't work.
I'm running CyanogenMod 10.1.2 and I have busy box smart installed using the Terminal Emulator. Downloaded backtrack 5 arm version from the website itself and extracted it to sdcard/BT5
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Did you make it? How?
mdorey said:
Did you make it? How?
Click to expand...
Click to collapse
I did makeit. I deleted my backtrack files and redownloaded them. It either didn't fullydownload, or a file got corrupted in the process,but once I redownloaded it, it worked fine!
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?
Hi
I have problem with using AdAway on my Z3TC.
I have successfully rooted my device. Now I'm on stock KK with root and locked back BL.
I installed AdAway but it doesn't want to work. There is problem with hosts file.
I found that I have to change permissions for /system to -rw-rw-rw and for file host too. But the problem is I can't. When I'm trying to change permissions I got info: Changing permissions was not successful. And it doesn't matter what Explorer I use.
Any ideas? Of course there is root permission for explorer... May the locked Bootloader be the problem (I doubt...)
To write in system you have to install from the recovery ricdefeat
https://github.com/dosomder/SonyRICDefeat/blob/master/RICDefeat.zip
I didn't installed TWRP after relocking BL.
I tried now and there is another problem (looks similar)
Code:
##########################################################
#
# Installing XZDR version 2.8.3 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': Read-only file system
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: No such file or directory
chmod: /system/.XZDualRecovery/busybox: No such file or directory
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
ADB asked for root permission during installation, I agreed.
And after all recovery is not installed...
I see where the problem is. You can not write in system because you need ricdefeat, but to install XZDualRecovery and flash from there ricdefeat need to write in "system"
I'm afraid you have to start over. Is necessary Flash Ricdefeat from the TWRP recovery before it is erased.
Read here (where it says "To install rooted Stock"):
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534 (relatively speaking there nicely explains the steps to take and what order , replace firmware sgp621 -> sgp611)
or my tutorial in Spanish I did not know if you know the language:
http://www.htcmania.com/showthread.php?t=966040 (Part B)
---
I will try to explain what I would do, I'm using google translator if not understood:
1- unlock bootloader
2- install advanced stock kernel
3- Now there are two options:
** 3A) Create pre-rooted firmware. Copy firmware pre-rooted and ricdefeat.zip on the tablet. Login to TWRP and flash firmware then ricdefeat, and restart at the end.
** 3B) Copy to tablet the ricdefeat file. Go to TWRP recovery, flash ricdefeat and restart. With flashtool , install on the tablet only the kernel, using the original firmware.
4- Start android and restore TA
5- Install XYDualRecovery to have a custom recovery
Please confirm that Flashfire work on the latest firmware for Verizon Galaxy S4 SCH-I545...
I don't want to risk it.
I guess I bricked it now that I tried...
FlashFire works fine as long as you're rooted.
Don't know how you'd brick it.
Well Flashfire requires SuperSU for the most part.
If I can remember, I tried "replace Kinguser with SuperSU" when i was on OF1, and it failed. It rebooted and SuperSU failed to install. I guess I can't take any more risks...
Here's what it says:
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure - not installed for 0
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /system/app/Kinguser.apk: No such file or directoryFailure - not installed for 0
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_USER_RESTRICTED]
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
I guess it's the bootloader.
Kotetsukun said:
Well Flashfire requires SuperSU for the most part.
If I can remember, I tried "replace Kinguser with SuperSU" when i was on OF1, and it failed. It rebooted and SuperSU failed to install. I guess I can't take any more risks...
Here's what it says:
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure - not installed for 0
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /system/app/Kinguser.apk: No such file or directoryFailure - not installed for 0
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_USER_RESTRICTED]
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
I guess it's the bootloader.
Click to expand...
Click to collapse
It isn't the bootloader, it means your root access didn't implement correctly... something is wrong with your kinguser.
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:
Drcken 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