Re-root Custom ROM? - Moto Z Questions & Answers

Hello everyone, I had stock Nougat 7 and managed to unlock my bootloader, flash TWRP and rooted Moto Z (EU1650-03). I then proceeded to flash a custom ROM (AICP N-12.1-GRIFFIN - Nougat 7.1.2) that came with a custom lineage kernel (3.18.31) & the Magisk Manager app. After having root access I wanted to remove root using SuperSU's option in the app due to certain apps not working upon detecting root access (which I did). But now I want to re-root my Moto Z with the custom ROM already installed, but when I try to re-flash SuperSU it fails. So my question is this, is there a way to re-root a custom ROM? I also made an idiotic mistake of not backing up my stock ROM/Recovery too. Logs when attempting to flash the SuperSU Zip are below.
Code:
- Detecting system compatibility
sukernel v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/sda17] ...
magic: [ANDROID!]
kernel: [10234663] (10235904) @ 0x80008000
ramdisk: [2545972] (2547712) @ 0x81000000
second: [0] (0) @ 0x80f00000
tags: @ 0x80000100
page size: 4096
unused: [0x007e9000] [0x0e041115]
dtb(?): [8294400] (8294400)
name: []
command line: [androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] cnsscore.pcie_link_down_panic=1 buildvariant=userdebug]
extra command line: []
id: [0xa4ce43a8667d37aae9db2ac40404e5118dfc24ef000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
sukernel v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk.packed] ...
Decompressing [2545972] --> [5334776]
Saving to [/sutmp/ramdisk] ...
sukernel v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk] ...
----- patch check -----
Loading from cpio:[init.rc] ...
Finding [daemonsu]
-!Found
Finding [SuperSU:PATCH]
-!Found
Result: not patched
sukernel v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk] ...
Saving to [/sutmp/fstab] ...
- System-less mode, boot image support required
- Creating image
/data/su.img: 11/6144 files (0.0% non-contiguous), 1422/24576 blocks
- Mounting image
mkdir: can't create directory '/su': File exists
- Creating paths
mkdir: can't create directory '/su/bin': Read-only file system
chown: /su/bin: No such file or directory
chown: /su/bin: No such file or directory
chmod: /su/bin: No such file or directory
mkdir: can't create directory '/su/xbin': Read-only file system
chown: /su/xbin: No such file or directory
chown: /su/xbin: No such file or directory
chmod: /su/xbin: No such file or directory
mkdir: can't create directory '/su/lib': Read-only file system
chown: /su/lib: No such file or directory
chown: /su/lib: No such file or directory
chmod: /su/lib: No such file or directory
mkdir: can't create directory '/su/etc': Read-only file system
chown: /su/etc: No such file or directory
chown: /su/etc: No such file or directory
chmod: /su/etc: No such file or directory
mkdir: can't create directory '/su/su.d': Read-only file system
chown: /su/su.d: No such file or directory
chown: /su/su.d: No such file or directory
chmod: /su/su.d: No such file or directory
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
/tmp/updater: line 1564: can't create /su/bin/su: nonexistent directory
chown: /su/bin/su: No such file or directory
chown: /su/bin/su: No such file or directory
chmod: /su/bin/su: No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
/tmp/updater: line 1564: can't create /su/bin/daemonsu: nonexistent directory
chown: /su/bin/daemonsu: No such file or directory
chown: /su/bin/daemonsu: No such file or directory
chmod: /su/bin/daemonsu: No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
/tmp/updater: line 1564: can't create /su/bin/supolicy_wrapped: nonexistent directory
chown: /su/bin/supolicy_wrapped: No such file or directory
chown: /su/bin/supolicy_wrapped: No such file or directory
chmod: /su/bin/supolicy_wrapped: No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
/tmp/updater: line 1564: can't create /su/lib/libsupol.so: nonexistent directory
chown: /su/lib/libsupol.so: No such file or directory
chown: /su/lib/libsupol.so: No such file or directory
chmod: /su/lib/libsupol.so: No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
/tmp/updater: line 1564: can't create /su/bin/sukernel: nonexistent directory
chown: /su/bin/sukernel: No such file or directory
chown: /su/bin/sukernel: No such file or directory
chmod: /su/bin/sukernel: No such file or directory
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda17
/tmp/updater: line 1564: /su/bin/sukernel: not found
- Extracting ramdisk
/tmp/updater: eval: line 1: /su/bin/sukernel: not found
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 9 second(s).
Updating partition details...
I:Data backup size is 3611MB, free: 45361MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
Truncating string cache entries.
I:Set page: 'filemanageroptions'
I:Set page: 'filemanagerlist'
I:Set overlay: 'slideout'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 25
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 25
I:Set overlay: ''
I:Set overlay: ''
I:Set overlay: 'slideout'
I:Set overlay: ''
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

Go to the magix main Post and Downloading The uninstall zip. After u can install supersu. All in recovery Mode
Gesendet von meinem XT1650-03 mit Tapatalk

Related

sed Permission denied and No such file or directory errors while building CWMR

I've been looking around and i can't fix this. My cm10 source is all updated and before I did this i entered
Code:
sudo apt-get update
so everything is up to date
i've been following this guide: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device but im stuck on step 3 when I enter
Code:
build/tools/device/mkvendor.sh samsung_aegis2vzw /your/path/to/the/boot.img (yes i changed this to my boot.img path)
i get this as the outcome:
Code:
build/tools/device/mkvendor.sh: line 83: /sedcommand: Permission denied
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
Any help is much appreciated.
bump
Bump
Bump
Okay I now believe this is occurring because I don't have the file sedcommand. Is this file in the root of everyone's cm10 source?
bump

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

[NEED HELP] - Android Kitchen ROM

Hello, xda!
I need a help!
I want to port stock rom via Android kitchen, so I dumped system.img and boot.img from my phone and then I have tried to cook it in the kitchen.
But when I flash it, it says "Updater process ended with signal: 11"
Is there error in my rom or in the updater-script?
How to fix that?
Could be anyone here so kind to tell me, please?
recovery log while flashing:
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/VF-895N_signed_040116_202039.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.
Updater process ended with signal: 11
I:Legacy property environment disabled.
Error installing zip file '/external_sd/VF-895N_signed_040116_202039.zip'
Updating partition details...
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Data backup size is 0MB, free: 3498MB.
I:sending message to remove 65537
I:Message sent, remove storage ID: 65537
mtppipe remove storage 65537
...done
I:Set page: 'flash_done'
I:operation_end - status=1
P.S. there is no stock rom (zip) for my phone yet, that's the reason I need to make it.
All we have is Sugar program that downloads the stock rom but when it downloads the rom, there are just .mbn files.
Is there any method to make the flashable stock rom from these .mbn files ?
Thank you so much for advices.
Same prop

Can flashfire work on VRSGPL1?

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.

[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