Hi all,
not sure if this is the right section to post this...
I already have root access through adb shell and I've installed superuser. However, my apps don't seem to be able to gain root access. This is what they have available:
$ su
# ls -l /system/xbin/su
lrwxrwxrwx root root 2012-03-29 17:27 su -> /system/bin/su
# ls -l /system/bin/su
-rwsr-sr-x root shell 64196 2012-03-29 14:10 su
I also compiled busybox 1.19.4 and it's on the device in /system/bin and xbin. I can use it with the busybox prefix (didn't manage to install it, the --install option doesn't work here... applet not found).
What am I missing for my root apps to work? Is it because of the missing --install on busybox? If so, does anyone know where to find a version that works?
Thanks!
Hi All,
Need some help with getting init.d to work on my Atrix 2. Its currently running ME865 on my international A2(thanks to cogeary for making this possible)
I flashed the init.d support from noobs thread, but the folder init.d under /system/etc was not created. So i created the directory manually and placed few scripts in there.
Problem being its not getting called on boot...
I checked permissions, etc and it looked good to me. Please check the below log, shows most of the required details.
Code:
[email protected]:/$ uptime
uptime
up time: 00:02:56, idle time: 00:03:00, sleep time: 00:00:00
[email protected]:/$ cd /system/etc
cd /system/etc
[email protected]:/system/etc$ ls -l install*
ls -l install*
-r-xr--r-- root root 189 2012-08-08 22:32 install-recovery.orig
-r-xr--r-- root root 189 2008-08-01 17:30 install-recovery.sh
[email protected]:/system/etc$ cat install-recovery.sh
cat install-recovery.sh
#!/system/bin/sh
if [ -f /system/xbin/busybox ]; then
/system/bin/logwrapper $bb run-parts /system/etc/init.d
else
for i in $(ls /system/etc/init.d/*); do
sh $i
done
fi
[email protected]:/system/etc$ cd init.d
cd init.d
[email protected]edison:/system/etc/init.d$ ls -l
ls -l
-rwxrwxrwx root root 177 2012-08-08 16:10 99cwr
-rwxrwxrwx root root 806 2012-08-07 14:21 99SuperCharger
-rwxrwxrwx root root 82 2012-08-08 22:09 99sdboost
[email protected]:/$ cat /sys/block/mmc*0/bdi/read*
cat /sys/block/mmc*0/bdi/read*
[B]1024[/B]
[email protected]:/system/etc/init.d$ sh 99sdboost
sh 99sdboost
99sdboost: cannot create /sys/block/mmcblk0/bdi/read_ahead_kb: permission denied
[email protected]:/system/etc/init.d$ su
su
[email protected]:/system/etc/init.d# sh 99sdboost
sh 99sdboost
[email protected]:/system/etc/init.d# cat /sys/block/mmc*0/bdi/read*
cat /sys/block/mmc*0/bdi/read*
[B]2048[/B]
Any helps appreciated.
Hm... where did you find the flashable zip for init.d support?
Try changing the scripts' permissions a little bit... chmod 755 scriptname
girishvk said:
Hi All,
Need some help with getting init.d to work on my Atrix 2. Its currently running ME865 on my international A2(thanks to cogeary for making this possible)
I flashed the init.d support from noobs thread, but the folder init.d under /system/etc was not created. So i created the directory manually and placed few scripts in there.
Problem being its not getting called on boot...
I checked permissions, etc and it looked good to me. Please check the below log, shows most of the required details.
Code:
[email protected]:/$ uptime
uptime
up time: 00:02:56, idle time: 00:03:00, sleep time: 00:00:00
[email protected]:/$ cd /system/etc
cd /system/etc
[email protected]:/system/etc$ ls -l install*
ls -l install*
-r-xr--r-- root root 189 2012-08-08 22:32 install-recovery.orig
-r-xr--r-- root root 189 2008-08-01 17:30 install-recovery.sh
[email protected]:/system/etc$ cat install-recovery.sh
cat install-recovery.sh
#!/system/bin/sh
if [ -f /system/xbin/busybox ]; then
/system/bin/logwrapper $bb run-parts /system/etc/init.d
else
for i in $(ls /system/etc/init.d/*); do
sh $i
done
fi
[email protected]:/system/etc$ cd init.d
cd init.d
[email protected]:/system/etc/init.d$ ls -l
ls -l
-rwxrwxrwx root root 177 2012-08-08 16:10 99cwr
-rwxrwxrwx root root 806 2012-08-07 14:21 99SuperCharger
-rwxrwxrwx root root 82 2012-08-08 22:09 99sdboost
[email protected]:/$ cat /sys/block/mmc*0/bdi/read*
cat /sys/block/mmc*0/bdi/read*
[B]1024[/B]
[email protected]:/system/etc/init.d$ sh 99sdboost
sh 99sdboost
99sdboost: cannot create /sys/block/mmcblk0/bdi/read_ahead_kb: permission denied
[email protected]:/system/etc/init.d$ su
su
[email protected]:/system/etc/init.d# sh 99sdboost
sh 99sdboost
[email protected]:/system/etc/init.d# cat /sys/block/mmc*0/bdi/read*
cat /sys/block/mmc*0/bdi/read*
[B]2048[/B]
Any helps appreciated.
Click to expand...
Click to collapse
Are you trying for ics or gb? If its ics, that one wont work
Sent from my MB865 using xda premium
cogeary said:
Hm... where did you find the flashable zip for init.d support?
Try changing the scripts' permissions a little bit... chmod 755 scriptname
Click to expand...
Click to collapse
i got it from here:
http://code.google.com/p/opptimizer/downloads/detail?name=moto_init_d-signed.zip&can=2&q=
I think its from one of your posts. :good:
Will try permission changes and will update here.
rdavisct said:
Are you trying for ics or gb? If its ics, that one wont work
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Hi rdavisct, im running GB. i'll be sticking with the same for a while.
Check out the [GUIDE] in my signature...
Edit: One thing I see is that you're not entering the commands as "su" (superuser). Are you doing this through terminal emulator?
Sent from my SAMSUNG-SGH-I747 using xda premium
File permissions changes did not help.
@apex_strider: I think the flash zip file in your siggy link(overclocking guide) is the same one i've used.
I'll nandroid back to stock (ME865) and will start over again.
Desire S
Hboot 2.00.2002 o-on rl dev->unlocked
instaled = rooted stock RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068
when i replace boot.img ...from ---> .V7.1 STABLE FOR SENSE 4 | EXPERIMENTAL FOR SENSE 3.6/MIUIv4
I only got black screen and reboot to recovery (after some time)
flashing org boot.img from ruu zip ... restores phone operation again
Why is this kernel not working .. because of hboot???
(installed busybox 1.20.2 with busysbox installer from market)... ?
Thanks for HELP!
Hboot 2.00.2002 is ENG S-OFF
Yours probably is 2.02.0002. Be more careful about such things.
You have to modify one number in the zip before flash. Read the kernel thread again
Sent from my HTC Desire S
amidabuddha said:
Hboot 2.00.2002 is ENG S-OFF
Yours probably is 2.02.0002. Be more careful about such things.
You have to modify one number in the zip before flash. Read the kernel thread again
Sent from my HTC Desire S
Click to expand...
Click to collapse
ok! mine is is 2.02.0002. ----- > S-ON Rl (****unlocked****)
"
mount("ext4", "EMMC", "/dev/block/mmcblk0p29", "/system/lib"); --- The line is totaly missing from "updater-script" in Tweaked3_7.1-Sense3.6-bcm4329.zip
adding mount line with 28 or 29 does not solve the issue :/ .... but 29 should be the right one.. as i looked up mount command in terminal... and system/lib is --> dev/block/mmcblk0p29
Flashing ZIP with 4ext recovery (latest)...
Obviously you dont like to read instructions.
Sense3.6 is for custom ROMs not for Stock
Anyway there is a new installer - use it
Sent from my HTC Desire S
amidabuddha said:
Obviously you dont like to read instructions.
Sense3.6 is for custom ROMa not for Stock
Anyway there is a new installer use it
Sent from my HTC Desire S
Click to expand...
Click to collapse
ok. New installer works.
oTeMpLo said:
ok. New installer works.
Click to expand...
Click to collapse
stock ics rom.
8.0 installer fails to create init.d folder !!!! /system/etc/init.d .. after manualy creating it .. it copies scripts to init.d folder,,
after that ficing permissions with fix_perm.bat .. as some init.d scrips have wring pemissions..
but modules still don't get loaded.
lsmod --> only wifidriver listed.
no zram ---> ecet...
free returns ---> swap 0 0 0
manualy starting ./51-zram works!!!
just init.d scripts dont get processed.
oTeMpLo said:
stock ics rom.
8.0 installer fails to create init.d folder !!!! /system/etc/init.d .. after manualy creating it .. it copies scripts to init.d folder,,
after that ficing permissions with fix_perm.bat .. as some init.d scrips have wring pemissions..
but modules still don't get loaded.
lsmod --> only wifidriver listed.
no zram ---> ecet...
free returns ---> swap 0 0 0
manualy starting ./51-zram works!!!
just init.d scripts dont get processed.
Click to expand...
Click to collapse
Code:
adb shell chmod 750 /system/etc/init.d/{scriptname}
adb shell chown 0.2000 /system/etc/init.d/{scriptname}
reboot
amidabuddha said:
Code:
adb shell chmod 750 /system/etc/init.d/{scriptname}
adb shell chown 0.2000 /system/etc/init.d/{scriptname}
reboot
Click to expand...
Click to collapse
yes i run fix_perm.bat
[email protected]:/system/etc/init.d # ls -l
ls -l
-rwxr-x--- root shell 157 2012-10-02 21:31 50-s2wEB
-rwxr-x--- root shell 68 2012-10-02 21:31 52-cifs
-rwxr-x--- root shell 107 2012-10-02 21:31 54-ntfs
-rwxr-x--- root shell 80 2012-10-02 21:31 53-kineto_gan
-rwxr-x--- root shell 117 2012-10-02 21:31 51-zram
[email protected]:/system/etc/init.d #
[email protected]:/system/lib/modules # ls -l
ls -l
-rw-r--r-- root root 320724 2008-08-01 14:00 bcm4329.ko
-rw-r--r-- root root 3118416 2012-10-02 21:31 cifs.ko
-rw-r--r-- root root 2262132 2012-10-02 21:31 ntfs.ko
-rw-r--r-- root root 29536 2012-10-02 21:31 nls_utf8.ko
-rw-r--r-- root root 175844 2012-10-02 21:31 kineto_gan.ko
-rw-r--r-- root root 218212 2012-10-02 21:31 zram.ko
[email protected]:/system/lib/modules #
Any other idea?
installed busybox 1.20.2 in /system/xbin ... some comands are still inked to "toolbox" ?!?
Thanks for help!
Check if /system/xbin/run-parts is there
amidabuddha said:
Check if /system/xbin/run-parts is there
Click to expand...
Click to collapse
[email protected]:/system/xbin # ls -l run*
ls -l run*
lrwxrwxrwx root root 2012-10-02 21:08 run-parts -> /system/xbin/busybox
[email protected]:/system/xbin #
[email protected]:/system/xbin # ls -l busy*
ls -l busy*
-rwxr-xr-x root root 863436 2012-10-02 21:08 busybox
[email protected]:/system/xbin #
oTeMpLo said:
[email protected]:/system/xbin # ls -l run*
ls -l run*
lrwxrwxrwx root root 2012-10-02 21:08 run-parts -> /system/xbin/busybox
[email protected]:/system/xbin #
[email protected]:/system/xbin # ls -l busy*
ls -l busy*
-rwxr-xr-x root root 863436 2012-10-02 21:08 busybox
[email protected]:/system/xbin #
Click to expand...
Click to collapse
.. ok now it works.... reboot afer remove in new install of busybox.....
tanks for Patiens with me!!! ....
There was a thread on the SU model, I'm interested if anyone else has a One SC. There's a family of One S-lookalikes that HTC makes for the three major Chinese networks. It's a dual-SIM device supporting CDMA2000 and GSM mainly for the China market. Outside specs are similar to the One SU but the SoC is supposedly an ST-Ericsson U8500.
Anyway, I've been trying to root the thing using Root_with_Restore_by_Bin4ry (http://forum.xda-developers.com/showthread.php?t=1886460) but it always fails. I've modified the script and managed to remount /system as read-write and copy su to /system/xbin/su. ls shows that su is in the right folder with the right permissions. However, after rebooting, all changes are lost. Anyone else having success rooting this phone? Do I need to unlock the bootloader first?
# ls -l
-rwxr-xr-x root shell 9756 2013-01-02 13:35 battery_params
-rwxr-xr-x root shell 71700 2013-01-02 13:35 dexdump
-rwxr-xr-x root shell 35660 2013-01-02 13:35 kexec.dyn
-rwxr-xr-x root shell 22280 2013-01-02 13:35 pppoe
-rwxr-xr-x root shell 13920 2013-01-02 13:35 ste-cg29xx_ctrl
-rwsr-sr-x root root 380532 2013-03-17 17:14 su
-rwxr-xr-x root shell 34668 2013-01-02 13:36 wireless_modem
Click to expand...
Click to collapse
Hey all,
I wrote an exploit to use cow root to pull/push images. I've only tested it on the Galaxy S7 Active, but it should also work for other arm64 phones. Let me know how it works out for you all!
https://github.com/freddierice/farm-root
Also, don't run `make push` if you don't know what you're doing. Its dangerous.
If you don't have the ndk, feel free to download the prebuilt binaries here: http://static.freddierice.co/868ab104ae202545f2d8aa97442073f3/farm-root-bins.tgz
Going back to stock on my T-Mobile Galaxy S7 Edge. Then going to poke around. Thank you sir
Sent from my SM-G935U using Tapatalk
freddierice said:
Hey all,
I wrote an exploit to use cow root to pull/push images. I've only tested it on the Galaxy S7 Active, but it should also work for other arm64 phones. Let me know how it works out for you all!
https://github.com/freddierice/farm-root
Also, don't run `make push` if you don't know what you're doing. Its dangerous.
Click to expand...
Click to collapse
I don't have a arm64v8 device to test on.
I tested on my x86 and armeabi doesn't work on either, thanks for sharing should helps those that have arm64v8
vampirefo said:
I don't have a arm64v8 device to test on.
Click to expand...
Click to collapse
I just haven't tested other devices. Try replacing `arm64-v8a` in the Makefile with your architecture, and see if it works.
How exactly would one use this tool. I have it on my PC at ~/farm-root and it is also pushed to /data/local/tmp on my phone
Sent from my Z981 using XDA Premium
Masterchief87 said:
How exactly would one use this tool. I have it on my PC at ~/farm-root and it is also pushed to /data/local/tmp on my phone
Click to expand...
Click to collapse
1. connect your phone with usb debugging allowed
2. open a terminal window and run `make log`
3. open a second terminal window and run `make pull`
freddierice said:
I just haven't tested other devices. Try replacing `arm64-v8a` in the Makefile with your architecture, and see if it works.
Click to expand...
Click to collapse
Yes, I already tried that as well as changing location of recovery, but just doesn't work for me.
Masterchief87 said:
How exactly would one use this tool. I have it on my PC at ~/farm-root and it is also pushed to /data/local/tmp on my phone
Sent from my Z981 using XDA Premium
Click to expand...
Click to collapse
Sent from my R1HD(ZenUI) via Tapatalk
freddierice said:
1. connect your phone with usb debugging allowed
2. open a terminal window and run `make log`
3. open a second terminal window and run `make pull`
Click to expand...
Click to collapse
Running `make log` yields
adb logcat | grep -a farm-root
Running `make pull` in the 2nd terminal window yields
ndk-build NDK_PROJECT_PATH=. APP_BUILD_SCRIPT=./Android.mk
make: ndk-build: Command not found
make: *** [build] error 127
Any idea what I'm doing wrong?
Masterchief87 said:
Running `make log` yields
adb logcat | grep -a farm-root
Running `make pull` in the 2nd terminal window yields
ndk-build NDK_PROJECT_PATH=. APP_BUILD_SCRIPT=./Android.mk
make: ndk-build: Command not found
make: *** [build] error 127
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
This project makes the binaries when you run `make`. You don't have the ndk installed. Or at least don't have the binaries sourced in your PATH.
OK. What is the procedure for using the pre built binaries?
Sent from my Z981 using XDA Premium
Masterchief87 said:
OK. What is the procedure for using the pre built binaries?
Click to expand...
Click to collapse
Same procedure as before. Just untar the files in the project directory. I ran `make clean all` on my box, then threw them up on the web.
Guess I'm SOL on this one?
Code:
[email protected]:/data/local/tmp $ logcat |grep farm
10-30 17:29:05.794 10572 10572 I farm-root: [*] farm-root started
10-30 17:29:05.795 10572 10572 I farm-root: [*] building a bridge
10-30 17:29:05.797 10572 10572 I farm-root: ERROR: could not open /system/bin/dumpstate
10-30 17:29:05.797 10572 10572 I farm-root: ERROR: could not overwrite /system/bin/dumpstate
10-30 17:30:40.315 10672 10672 W farm : type=1400 audit(0.0:7): avc: denied { read } for name="dumpstate" dev="mmcblk0p14" ino=105 scontext=u:r:shell:s0 tcontext=u:object_r:dumpstate_exec:s0 tclass=file permissive=0
Guess I'm SOL on this one?
Click to expand...
Click to collapse
I guess so. I didn't realize that SELinux policies varied so drastically. I am surprised though that you do not have read privs to /system/bin/dumpstate. Could you post `adb shell ls -laZ /system/bin/`? I'm curious
Here yuh go.
Code:
[email protected]:/ $ ls -laZ /system/bin
lstat '/system/bin/ClockworkProxy' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 acpi -> toybox
lstat '/system/bin/adspd' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 am
lrwxr-xr-x root shell u:object_r:system_file:s0 app_process -> app_process32
-rwxr-xr-x root shell u:object_r:zygote_exec:s0 app_process32
-rwxr-xr-x root shell u:object_r:system_file:s0 applypatch
-rwxr-xr-x root shell u:object_r:system_file:s0 appops
-rwxr-xr-x root shell u:object_r:system_file:s0 appwidget
-rwxr-xr-x root shell u:object_r:system_file:s0 atrace
lrwxr-xr-x root shell u:object_r:system_file:s0 basename -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 bcc
lstat '/system/bin/blkid' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 blockdev -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 bmgr
lstat '/system/bin/bootanimation' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 bu
-rwxr-xr-x root shell u:object_r:system_file:s0 bugreport
lrwxr-xr-x root shell u:object_r:system_file:s0 bzcat -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 cal -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 cat -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 chcon -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 chgrp -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 chmod -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 chown -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 chroot -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 cksum -> toybox
lstat '/system/bin/clatd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 clear -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 cmp -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 comm -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 content
lrwxr-xr-x root shell u:object_r:system_file:s0 cp -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 cpio -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 cut -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 dalvikvm -> dalvikvm32
-rwxr-xr-x root shell u:object_r:system_file:s0 dalvikvm32
lrwxr-xr-x root shell u:object_r:system_file:s0 date -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 dd -> toolbox
lstat '/system/bin/debuggerd' failed: Permission denied
-rwxr-xr-x root shell u:object_r:dex2oat_exec:s0 dex2oat
lrwxr-xr-x root shell u:object_r:system_file:s0 df -> toolbox
lstat '/system/bin/dhcpcd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 dirname -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 dmesg -> toybox
lstat '/system/bin/dnsmasq' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 dos2unix -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 dpm
lrwxr-xr-x root shell u:object_r:system_file:s0 du -> toolbox
lstat '/system/bin/dumpstate' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 dumpsys
lstat '/system/bin/e2fsck' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 echo -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 egrep -> grep
lrwxr-xr-x root shell u:object_r:system_file:s0 env -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 expand -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 expr -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 fallocate -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 false -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 fgrep -> grep
lrwxr-xr-x root shell u:object_r:system_file:s0 find -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 free -> toybox
lstat '/system/bin/fsck_msdos' failed: Permission denied
lstat '/system/bin/gatekeeperd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 getenforce -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 getevent -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 getprop -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 grep
lrwxr-xr-x root shell u:object_r:system_file:s0 groups -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 gzip
-rwxr-xr-x root shell u:object_r:system_file:s0 hciattach
lrwxr-xr-x root shell u:object_r:system_file:s0 head -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 hid
lrwxr-xr-x root shell u:object_r:system_file:s0 hostname -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 hwclock -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 id -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 ifconfig -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 iftop -> toolbox
-rwxr-xr-x root shell u:object_r:system_file:s0 ime
lstat '/system/bin/init.mmi.boot.sh' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 inotifyd -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 input
lrwxr-xr-x root shell u:object_r:system_file:s0 insmod -> toybox
lstat '/system/bin/install-recovery.sh' failed: Permission denied
lstat '/system/bin/installd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 ioctl -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 ionice -> toolbox
-rwxr-xr-x root shell u:object_r:system_file:s0 ip
-rwxr-xr-x root shell u:object_r:system_file:s0 ip6tables
-rwxr-xr-x root shell u:object_r:system_file:s0 iptables
lstat '/system/bin/keystore' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 kill -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 ld.mc
-rwxr-xr-x root shell u:object_r:system_file:s0 linker
lstat '/system/bin/lmkd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 ln -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 load_policy -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 log -> toolbox
-rwxr-xr-x root shell u:object_r:logcat_exec:s0 logcat
lstat '/system/bin/logd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 logname -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 logwrapper
lrwxr-xr-x root shell u:object_r:system_file:s0 losetup -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 ls -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 lsmod -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 lsof -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 lsusb -> toybox
lstat '/system/bin/m4setup' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 make_ext4fs
lstat '/system/bin/mbm_spy' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 md5sum -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 media
lstat '/system/bin/mediaserver' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 mkdir -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 mknod -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 mkswap -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 mktemp -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 modinfo -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 monkey
lrwxr-xr-x root shell u:object_r:system_file:s0 more -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 mount -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 mountpoint -> toybox
lstat '/system/bin/mtpd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 mv -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 nandread -> toolbox
-rwxr-xr-x root shell u:object_r:system_file:s0 ndc
lstat '/system/bin/netd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 netstat -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 newfs_msdos -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 nice -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 nl -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 nohup -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 oatdump
lrwxr-xr-x root shell u:object_r:system_file:s0 od -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 paste -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 patch -> toybox
-rwxr-xr-x root shell u:object_r:dex2oat_exec:s0 patchoat
lrwxr-xr-x root shell u:object_r:system_file:s0 pgrep -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 pidof -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 ping
-rwxr-xr-x root shell u:object_r:system_file:s0 ping6
lrwxr-xr-x root shell u:object_r:system_file:s0 pkill -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 pm
lrwxr-xr-x root shell u:object_r:system_file:s0 pmap -> toybox
lstat '/system/bin/pppd' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 printenv -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 printf -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 prlimit -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 ps -> toolbox
lstat '/system/bin/pvrsrvctl_SGX530_125' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 pwd -> toybox
lstat '/system/bin/racoon' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 readlink -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 realpath -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 reboot
lrwxr-xr-x root shell u:object_r:system_file:s0 renice -> toolbox
-rwxr-xr-x root shell u:object_r:system_file:s0 resize2fs
lrwxr-xr-x root shell u:object_r:system_file:s0 restorecon -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 rm -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 rmdir -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 rmmod -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 route -> toybox
-rwxr-x--- root shell u:object_r:runas_exec:s0 run-as
lrwxr-xr-x root shell u:object_r:system_file:s0 runcon -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 schedtest
-rwxr-xr-x root shell u:object_r:system_file:s0 screencap
-rwxr-xr-x root shell u:object_r:system_file:s0 screenrecord
lstat '/system/bin/sdcard' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 secdiscard
lrwxr-xr-x root shell u:object_r:system_file:s0 sed -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 sendevent -> toolbox
-rwxr-xr-x root shell u:object_r:system_file:s0 sensorservice
lrwxr-xr-x root shell u:object_r:system_file:s0 seq -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 service
lstat '/system/bin/servicemanager' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 setenforce -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 setprop -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 setsid -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 settings
lstat '/system/bin/setup_fs' failed: Permission denied
lstat '/system/bin/sgdisk' failed: Permission denied
-rwxr-xr-x root shell u:object_r:shell_exec:s0 sh
lrwxr-xr-x root shell u:object_r:system_file:s0 sha1sum -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 sleep -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 sm
lrwxr-xr-x root shell u:object_r:system_file:s0 sort -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 split -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 start -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 stat -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 stop -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 strings -> toybox
lstat '/system/bin/surfaceflinger' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 svc
lrwxr-xr-x root shell u:object_r:system_file:s0 swapoff -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 swapon -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 sync -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 sysctl -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 tac -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 tail -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 tar -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 taskset -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 tc
lrwxr-xr-x root shell u:object_r:system_file:s0 tee -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 telecom
lrwxr-xr-x root shell u:object_r:system_file:s0 time -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 timeout -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 tinycap
-rwxr-xr-x root shell u:object_r:system_file:s0 tinymix
-rwxr-xr-x root shell u:object_r:system_file:s0 tinyplay
-rwxr-xr-x root shell u:object_r:toolbox_exec:s0 toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 top -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 touch -> toybox
lstat '/system/bin/touch_ramoops.sh' failed: Permission denied
-rwxr-xr-x root shell u:object_r:toolbox_exec:s0 toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 tr -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 true -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 truncate -> toybox
lstat '/system/bin/tzdatacheck' failed: Permission denied
-rwxr-xr-x root shell u:object_r:system_file:s0 uiautomator
lstat '/system/bin/uim-sysfs' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 umount -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 uname -> toybox
lstat '/system/bin/uncrypt' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 uniq -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 unix2dos -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 uptime -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 usleep -> toybox
lstat '/system/bin/vdc' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 vmstat -> toybox
lstat '/system/bin/vold' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 watchprops -> toolbox
lrwxr-xr-x root shell u:object_r:system_file:s0 wc -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 which -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 whoami -> toybox
-rwxr-xr-x root shell u:object_r:system_file:s0 wm
lstat '/system/bin/wpa_supplicant' failed: Permission denied
lrwxr-xr-x root shell u:object_r:system_file:s0 xargs -> toybox
lrwxr-xr-x root shell u:object_r:system_file:s0 yes -> toybox
[email protected]:/ $
It looks super strict. I forgot to mention I'm attempting this on a moto 360. It's stripped down android so there probably less mistakes in a policy making it more secure. It's a watch why would I need to read those files was probably their thought. Beggining to think root won't be possible without damaging its water resistance.
freddierice said:
Hey all,
I wrote an exploit to use cow root to pull/push images. I've only tested it on the Galaxy S7 Active, but it should also work for other arm64 phones. Let me know how it works out for you all!
https://github.com/freddierice/farm-root
Also, don't run `make push` if you don't know what you're doing. Its dangerous.
If you don't have the ndk, feel free to download the prebuilt binaries here: http://static.freddierice.co/868ab104ae202545f2d8aa97442073f3/farm-root-bins.tgz
Click to expand...
Click to collapse
Did this ultimately root this device?
Could you get this to flash the LAF partition for LG phones? I would love to work with you on flashing the LAF partition as my LG G5's is nuked and I can no longer work on finding a root exploit for it...
root
Please help me to root infocus epic 1..
freddierice said:
Hey all,
I wrote an exploit to use cow root to pull/push images. I've only tested it on the Galaxy S7 Active, but it should also work for other arm64 phones. Let me know how it works out for you all!
https://github.com/freddierice/farm-root
Also, don't run `make push` if you don't know what you're doing. Its dangerous.
If you don't have the ndk, feel free to download the prebuilt binaries here: http://static.freddierice.co/868ab104ae202545f2d8aa97442073f3/farm-root-bins.tgz
Click to expand...
Click to collapse
So does your tool will allow us to flash twrp on S7 active and hence get a stable root method instead of the engineered kernel method which is very buggy
Sent from my SAMSUNG-SM-G891A using XDA-Developers Legacy app
I was able to run the makefile but recovery_pull and boot_pull don't seem to get written. Make log returns an error about not being able to open /system/bin/dumpstate.
Am I missing something? I might be in the same boat as Geofferey but if there's something I'm glossing over I'd love to hear about it.
I'm a forker! Thanks for the awesome code, seriously man
***** Warning: This is an unfinished, powerful, tool for developers. When I have it working I will compile it with easy instructions *****
1. Updated Makefile to retrieve the device via adb. Android.mk <snippet> APP_ABI=$(ARCH) APP_PLATFORM=android-$(SDK_VERSION)
2. Updated dirtycow to use the new improved version. e.g. prefer ptrace as well as large file support
3. Added printf statements to farm.c to echo progress to the console.
and I dunno if I made other changes but github does, just check..
I'm not an Android developer I'm a C programmer with a new passion for Android. It is not implausible that your device will never boot again!!
Here's my repo. I'm open source in everything I do and I ask that if you use any work that I've contributed please be 100% open source as well!
https://github.com/droidvoider/N920A-farm-root
but if you can't be open source then just don't charge people for fixing their miserable devices!
Notice: Scope of this tool, i.e. CVE-2016-5195 for Google & SVE-2016-7504 for Samsung <== we are patched by SVE patch
****** Samsung owner's please note the patch date was November 2016 by Samsung, 14 patches were in that package ******
Even though Google patches were Nov 1st, 2016 = partial and Nov 5th, 2016 = full this may not be a rule for us! My AT&T Note 5 with Security Patch Level Date Nov 1, 2016 is patched. If you're with AT&T that might be it, see SETTINGS==>SYSTEM|ABOUT|"Security Patch Level.
(I am patched but I downgraded my kernel by using boot.img + recovery.img from October 2016 firmware!! It isn't checked you can downgrade those!)
The Samsung SVE-2016-7504 is stated to be included in November's patches so if you have a patch post Nov 1st from your carrier that's likely the end of the story. But if you are with other than AT&T, Verizon for example, I don't know how to look up the details of when you were patched. But Samsung had 14 patches in that set. AT&T N920AUCS4CPK1 has a note about 14 patches from Samsung, the exact number. So match that logic with your carrier, or whatever, to figure it out. If you're patched and you can't downgrade kernels there's no work around for that. I don't mind helping you but this is super risky stuff...
updated: farm-root to work on note 5 and added some more info on compiling this yourself
https://forum.xda-developers.com/an...nux-stages-t3573036/post71528270#post71528270
seems to work