I'have rooted a Primux zeta 2 with Android 4.4.2. I can see what stuff is stored in my (internal/emulated) sdcard (/storage/sdcard0) and external one (/storage/sdcard1) using ls command in Terminal Emulator. But if I do su, I can't see it:
[email protected]:/ $ ls /storage/sdcard0/
Alarms
Android
....
[email protected]:/ $
[email protected]:/ $ su -
[email protected]:/ # ls /storage/sdcard0/
(empty)
[email protected]:/ #
Related
Hi,
Holding in my hands this Chinese pretty well made and fast thing (maybe just border plastic looks little bit loose).
But in this post I will not tell about quality of this tablet, writing this just for other people who "googled" to solve problems :cyclops:
Device spec:
Freelander PD80 Shangpin
Exynos quadcore
Android 4.0.4
So nothing new here just flow what you need to perform.
Really this article not about rooting actually it's how to get root work here.
I'm using linux so everything below aligned to linux but with some modification you can perform everything under windows.
This flow can be applicable to any device with such problem.
And as usual - Whatever you do with your device, you do that at your own risk.
Description:
1. Executing "su" in connectbot or android terminal emulator return next:
Code:
$ su
su: uid xxxxx not allowed to su
2. By executing "su" from adb shell I'm getting the root rights:
Code:
linux$ ./adb shell
android$ su
android#
Conclusion:
So device is rooted problem just with "wrong" su binary (even busybox inside).
Let's solve it if it's really your problem.
Steps to solve:
1. Download "chainsdd superuser" (site http://androidsu.com/superuser/ direct link http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip)
2. extract archive and find inside Superuser.apk and su
3. Put Superuser.apk and su into folder with adb
4. Upload them to android device sdcard by executing from PC:
Code:
# ./adb push ./su_free /sdcard/su_free
Code:
# ./adb push ./Superuser.apk /sdcard/superuser.apk
5. Now we need to move them into system
Launch adb shell:
Code:
$ ./adb shell
$ su
#
6. Make sure that system partition writable (it was my case):
Code:
# mount|grep system
As result you will see:
Code:
/dev/block/mmcblk0p2 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
In our case we don't need that. But if you see "ro" instead of "rw", you need to simply remount it:
Code:
# mount -o remount,rw /system
7. Back up old su binary by executing
Code:
# cp /system/xbin/su /system/xbin/su_ori
8. Copy su binary from sdcard to system
Code:
# cp /sdcard/su /system/xbin/su
Fix permissions:
Code:
# chmod 6755 /system/xbin/su
Check permissions:
Code:
# ls -l /system/xbin/|grep su
You'll see something like this:
Code:
-rwsr-sr-x root root 380532 2013-11-17 01:02 su
-rwsr-sr-x root root 64412 2013-11-17 01:18 su_ori
and link it
Code:
# ln -s /system/xbin/su /system/bin/su
9. Copy superuser.apk to system applications:
Code:
# cp /sdcard/Superuser.apk /system/app/superuser.apk
Fix permissions:
Code:
# chmod 644 /system/app/superuser.apk
Check permissions:
Code:
# ls -l /system/app|grep superuser.apk
You'll see something like this:
Code:
-rw-r--r-- root root 1468798 2013-11-17 01:10 superuser.apk
10. Reboot. And try to execute su from connectbot or android terminal emulator.
You'll be asked about granting permission.
That's all now we can do everything.
Good luck.
$ cd /sdcard
$ ls
...
...
...
...
$ su
# cd /sdcard
# ls
#
Does anyone have an explanation for this error?
Running cyanogenmod 11 nightly on moto g
Got root, then su binary installed need some help backtracking a few things. If someone is up for it?
I guess the first thing first is. The first time I adb shell'd I got promted with root user: ( does this happen right off the bat for anyone else? I did a few things before this with modstrings and busybox. But, didn't try adb till after)
Code:
adb shell
[email protected]:/ #
Once I noticed I had root on shell I simply found the system mount at /dev/ubui0_0 and I mounted it rw.
Code:
[email protected]:/ # mount -o remount, /dev/ubi0_0
moved the su binary over to the sdcard. wrote it to system/xbin link named to /system/bin. gave permisions.
Code:
adb push su /sdcard/
[email protected]:/ # cat /sdcard/su > /system/xbin/su
[email protected]:/ # ln -s /system/xbin/su
[email protected]:/ # chmod 6755 /system/xbin/su
[email protected]:/ # su
[email protected]:/ # :D
Off I went. I need to update the binary, but as of right now Superuser shows root as 'allow', SuperSU deny (think it old binary).
If you guys are not getting root after adb shell on this device, I think I can backtrack the modstrings and other stuff I did.
I really don't know where this device sits on getting rooted. It seems like some windows programs did it before an update that happened at some point, but not anymore? I don't have access to windows so I don't keep up with those methods.
Thanks! Hope someone can help me out.
I used TWRP for installing the su command, and I installed SuperSU app from Google Play. It works.
The question - how su command works? It hasn't s-bit (it has -rwxr-xr-x, see below), so it can not change eUID by expected way. In what way it gets root's permissions?
Code:
[email protected]:/ $ id
uid=2000(shell) gid=2000(shell)
groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
[email protected]:/ # which su
/system/xbin/su
[email protected]:/ # ls -l /system/xbin/su
-rwxr-xr-x root root 75348 2016-10-29 22:31 su
[email protected]:/ #
Hi all,
im using a rooted samsung galaxy note 3 with lollipop
i have installed tasker to automate a few things ...
in addition i have installed the app "secure settings" to open the lookscreen
because of the message from secure settings in "System+ Module", that "Root access was not detected. The System+ module requires root access to function, i try the following:
Found on https://www.reddit.com/comments/3uf5bn ....
---------------------------------
adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit
reboot
---------------------------
im using Android Debug Bridge version 1.0.41
Version 28.0.3-5475833 <-- i think that's the latest version
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # touch /sbin/su /system/bin/su /system/xbin/su
touch: usage: touch [-alm] [-t YYYYMMDD[.hhmmss]] <file>
1|[email protected]:/ # exit
1|[email protected]:/ $ exit
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # touch /sbin/su /system/bin/su /system/xbin/su <-- don't work
touch: usage: touch [-alm] [-t YYYYMMDD[.hhmmss]] <file>
1|[email protected]:/ # exit
1|[email protected]:/ $ exit
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # touch /sbin/su <-- tried single step
255|[email protected]:/ # < -- is that the problem?
----------------------------
please help me ....
thanks Mikel