Learning to root my old Galaxy S4 - General Questions and Answers
I have an old Samsung Galaxy S4. It's been off the network for a while and its system clock has drifted. However, adb works and I can use the old phone as a sandbox environment to learn about low level Android fundamentals. I would like to learn how to root the phone, ideally without using any apps - I prefer to learn how to compile my own local privilege escalation exploit and run it on my old phone.
adb shell getprop ro.build.version.release
5.0.1
adb shell getprop ro.build.version.sdk
21
dumpstate:
Build: LRX22C.I337UCSGOK3
Build fingerprint: 'samsung/jflteuc/jflteatt:5.0.1/LRX22C/I337UCSGOK3:user/release-keys'
Bootloader: I337UCSGOK3
Radio: mdm
Network: (unknown)
Kernel: Linux version 3.4.0-6185444 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Nov 30 21:31:59 KST 2016
Command line: console=null androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3F ehci-hcd.park=3 [email protected] [email protected] sec_debug.reset_reason=0x1a2b3c00 androidboot.warranty_bit=0 lcd_attached=1 lcd_id=0x418047 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enable_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0 cordon=a569d279d878ac52077d6cfb9721d339 connie=SGH-I337_ATT_USA_76d68869445a30d9d8d06ffe689dd803 lpj=67678 loglevel=4 samsung.hardware=SGH-I337 androidboot.emmc_checksum=3 androidboot.warranty_bit=0 androidboot.bootloader=I337UCSGOK3 androidboot.nvdata_backup=0 androidboot.boot_recovery=0 androidboot.check_recovery_condition=0x0 level=0x574f4c44 vmalloc=450m sec_pvs=0 batt_id_value=0 diag=0 androidboot.csb_val=1 androidboot.emmc=true androidboot.serialno=95e836b4 androidboot.baseband=mdm
cat /proc/cpuinfo:
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 13.53
processor : 1
BogoMIPS : 13.53
processor : 2
BogoMIPS : 13.53
processor : 3
BogoMIPS : 13.53
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x06f
CPU revision : 0
Hardware : SAMSUNG JF
Revision : 000a
Serial : 000095e8000036b4
Android is a ported Linux, hence rooting Android means adding su ( read: switchuser ) functionality welllknown from Linux to device's Android. That's all.
Can get achieved with ADB having a suitable su at hands.
https://forum.xda-developers.com/attachments/su-binaries-zip.5566949/
Do you have source code for that su? I believe it would still require an exploit to escalate privileges, since normally su needs to run with root permissions, and I don't have a way of elevating to root without it.
What you believe ist totally wrong: su doesn't need root permissions to run a shell command, su is what in general is called root.
Code:
su -c "<SHELL-COMMAND-HERE>"
Become familiar with Linux shell commands.
I can already run shell commands using adb shell. However, I cannot run privileged commands because the adb shell process does not run with root privileges. Can you please elaborate further?
OMG.
Code:
adb shell
simply opens a remote Android terminal what doesn't require any elevated privileges per se.
To run shell commands what require elevated privileges ( e.g. mount ) is achieved as follows
Code:
adb shell "<PATH-OF-SU-BINARY-HERE> -c '<SHELL-COMMAND-HERE>'"
Example:
Code:
adb shell "/data/local/tmp/su -c 'mount -o rw,remount /data'"
The adb shell allows running unprivileged commands but there are numerous things which cannot be done without the root privilege, such as remounting filesystems, changing permissions, accessing directories which require elevated privileges, etc. This is what I am asking about. Am I misunderstanding you - are you trying to say that adb shell can be used by an unprivileged user to run privileged commands?
See my revised post above yours.
@jf80dEf
The Samsung Galaxy S4 variant you have is from AT&T (model number SGH-I337) and it's running the final software release (OK3).
For this model, you need to downgrade to a lower firmware (NB1) and achieve root access by exploiting the vulnerability formally known as CVE-2014-3153. More details can be found here.
Thank you @SkandaH for answering my question! I believe the method you suggest involves using Odin to wipe the phone to make it vulnerable to the towelroot exploit. Reading between the lines, am I interpreting correctly that there is no known (at least to you) exploit that runs on the OK3 software?
jf80dEf said:
... am I interpreting correctly that there is no known (at least to you) exploit that runs on the OK3 software?
Click to expand...
Click to collapse
Yes, that's correct.
just for fun, I tried that method on rooted device, it doesn't work for Android 5+
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Android>adb devices
List of devices attached
ca1296db7d29 device
C:\Android>adb push su /data/local/tmp
su: 1 file pushed. 0.7 MB/s (75344 bytes in 0.105s)
C:\Android>adb shell
cereus:/ $ cd /data/local/tmp
cereus:/data/local/tmp $ chmod 6775 ./su
cereus:/data/local/tmp $ ls -la
total 84
drwxrwx--x 2 shell shell 4096 2022-12-27 15:22 .
drwxr-x--x 4 root root 4096 2022-07-24 14:19 ..
-rwsrwsr-x 1 shell shell 75344 2022-12-27 15:22 su
cereus:/data/local/tmp $ ./su
"./su": error: Android 5.0 and later only support position-independent executables (-fPIE).
1|cereus:/data/local/tmp $ rm ./su
cereus:/data/local/tmp $ exit
C:\Android>
copied another su binary from stock rooted android tv box (no superuser app required, permissions granted automatically.
Code:
C:\Android>adb push su /data/local/tmp
adb: error: failed to get feature set: more than one device/emulator
C:\Android>adb -s ca1296db7d29 push su /data/local/tmp
su: 1 file pushed. 1.4 MB/s (100068 bytes in 0.070s)
C:\Android>adb shell
error: more than one device/emulator
C:\Android>adb -s ca1296db7d29 shell
cereus:/ $ cd /data/local/tmp
cereus:/data/local/tmp $ chmod 6775 ./su
cereus:/data/local/tmp $ ls -la
total 108
drwxrwx--x 2 shell shell 4096 2022-12-27 15:39 .
drwxr-x--x 4 root root 4096 2022-07-24 14:19 ..
-rwsrwsr-x 1 shell shell 100068 2022-12-27 15:38 su
cereus:/data/local/tmp $ ./su
255|cereus:/data/local/tmp $ ./su --help
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
cereus:/data/local/tmp $ ./su --version
16 com.thirdparty.superuser
cereus:/data/local/tmp $
still it doesn't work from /data/local/tmp as the uid is 2000 (shell) so tried from /data/local where uid is 0 (root)
but I had to use Magisk /sbin/su for this already
Code:
cereus:/data/local/tmp $ ls -la /data/local
ls: /data/local: Permission denied
1|cereus:/data/local/tmp $ ls -la /data/local/tmp
total 108
drwxrwx--x 2 shell shell 4096 2022-12-27 15:39 .
drwxr-x--x 4 root root 4096 2022-07-24 14:19 ..
-rwsrwsr-x 1 shell shell 100068 2022-12-27 15:38 su
cereus:/data/local/tmp $ cp ./su ..
cp: ../su: Permission denied
1|cereus:/data/local/tmp $ which su
/sbin/su
cereus:/data/local/tmp $ /sbin/su -c 'cp ./su ..'
cereus:/data/local/tmp $ cd ..
cereus:/data/local $ ls -la
ls: .: Permission denied
1|cereus:/data/local $ /sbin/su -c 'chmod 6775 ./su'
cereus:/data/local $ /sbin/su -c 'ls -la'
total 120
drwxr-x--x 4 root root 4096 2022-12-27 15:45 .
drwxrwx--x 48 system system 4096 2022-07-24 20:32 ..
-rwsrwsr-x 1 root root 100068 2022-12-27 15:45 su
drwxrwx--x 2 shell shell 4096 2022-12-27 15:39 tmp
drwxrwxrwx 2 shell shell 4096 2022-07-24 14:19 traces
cereus:/data/local $ ./su
255|cereus:/data/local $
despites the SUID bit is set correctly still it doesn't work. so I removed the nosuid mount flag for /data partition and double checked selinux isn't the problem
Code:
255|cereus:/data/local $ grep ' /data ' /proc/mounts
/dev/block/dm-1 /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=10010,resgid=1065,errors=panic,data=ordered 0 0
cereus:/data/local $ /sbin/su -c 'busybox mount -o remount,rw,suid /data'
cereus:/data/local $ grep ' /data ' /proc/mounts
/dev/block/dm-1 /data ext4 rw,seclabel,nodev,noatime,noauto_da_alloc,resuid=10010,resgid=1065,errors=panic,data=ordered 0 0
cereus:/data/local $ ./su
255|cereus:/data/local $ getenforce
Permissive
cereus:/data/local $
still no way to get the root shell with that su binary, maybe prevented to run from /data at all. decided to try from other partition but there was no way. although permissions 2000 (shell) should at least see the file, but that wasn't the case. Magisk mount namespaces are set to global, no idea why the file is invisible in /cache
Code:
cereus:/data/local $ grep ' /cache ' /proc/mounts
/dev/block/platform/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
cereus:/data/local $ /sbin/su -c 'busybox mount -o remount,rw,suid /cache'
cereus:/data/local $ grep ' /cache ' /proc/mounts
/dev/block/platform/bootdevice/by-name/cache /cache ext4 rw,seclabel,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
cereus:/data/local $ /sbin/su -c 'cp ./su /cache'
cereus:/data/local $ cd /cache
/system/bin/sh: cd: /cache: Permission denied
2|cereus:/data/local $ /sbin/su -c 'cd /cache'
cereus:/data/local $ /sbin/su -c 'mkdir /cache/tmp'
cereus:/data/local $ /sbin/su -c 'chown 0.2000 /cache/tmp'
cereus:/data/local $ cd /cache/tmp
/system/bin/sh: cd: /cache/tmp: Permission denied
2|cereus:/data/local $ /sbin/su -c 'chown 2000.2000 /cache/tmp'
cereus:/data/local $ cd /cache/tmp
/system/bin/sh: cd: /cache/tmp: Permission denied
2|cereus:/data/local $ /sbin/su -c 'ls -la /cache/tmp'
total 16
drwxr-xr-x 2 shell shell 4096 2022-12-27 15:54 .
drwxrwx--- 8 system cache 4096 2022-12-27 15:54 ..
cereus:/data/local $ /sbin/su
cereus:/data/local # cd /cache/tmp
cereus:/cache/tmp # cp /cache/su .
cereus:/cache/tmp # chmod 6775 ./su
cereus:/cache/tmp # exit
cereus:/data/local $ /cache/tmp/su
/system/bin/sh: /cache/tmp/su: not found
127|cereus:/data/local $ /sbin/su
cereus:/data/local # cd /cache/tmp
cereus:/cache/tmp # ls -la
total 120
drwxr-xr-x 2 shell shell 4096 2022-12-27 15:58 .
drwxrwx--- 8 system cache 4096 2022-12-27 15:54 ..
-rwsrwsr-x 1 root root 100068 2022-12-27 15:58 su
cereus:/cache/tmp # ./su
255|cereus:/cache/tmp # chown -R 0.2000 .
cereus:/cache/tmp # ls -la
total 120
drwxr-xr-x 2 root shell 4096 2022-12-27 15:58 .
drwxrwx--- 8 system cache 4096 2022-12-27 15:54 ..
-rwxrwxr-x 1 root shell 100068 2022-12-27 15:58 su
cereus:/cache/tmp # ./su
255|cereus:/cache/tmp # exit
255|cereus:/data/local $ /cache/tmp/su
/system/bin/sh: /cache/tmp/su: not found
127|cereus:/data/local $ /sbin/su -c 'chmod 6775 /cache/tmp/su'
cereus:/data/local $ /cache/tmp/su
/system/bin/sh: /cache/tmp/su: not found
127|cereus:/data/local $
finally, even tried from within Magisk root shell. still the binary throws error 255. as you can see the su binary owns the sticky bit and uid 0 (root)
Code:
127|cereus:/data/local $ /sbin/su
cereus:/data/local # /cache/tmp/su --version
16 com.thirdparty.superuser
cereus:/data/local # /cache/tmp/su
255|cereus:/data/local # exit
255|cereus:/data/local $ /cache/tmp/su
/system/bin/sh: /cache/tmp/su: not found
127|cereus:/data/local $ /sbin/su -c 'ls -la /cache/tmp'
total 120
drwxr-xr-x 2 root shell 4096 2022-12-27 15:58 .
drwxrwx--- 8 system cache 4096 2022-12-27 15:54 ..
-rwsrwsr-x 1 root shell 100068 2022-12-27 15:58 su
cereus:/data/local $
to confirm the binary is working at least, I wanted to install in /system. Because of systemless-root and avb/dm-verity i can't place file /system partition directly, so I used Magisk bind mount overlay
Code:
cereus:/data/local $ /sbin/su
cereus:/data/local # cd /data/adb/modules
cereus:/data/adb/modules # mkdir su_test
cereus:/data/adb/modules # cd su_test/
cereus:/data/adb/modules/su_test # mkdir -p system/xbin
cereus:/data/adb/modules/su_test # cp /cache/tmp/su system/xbin
cereus:/data/adb/modules/su_test # chown -R 0.2000 system
cereus:/data/adb/modules/su_test # chmod 6775 system/xbin/su
cereus:/data/adb/modules/su_test # ls -la system/xbin
total 108
drwxr-xr-x 2 root shell 4096 2022-12-27 16:10 .
drwxr-xr-x 3 root shell 4096 2022-12-27 16:10 ..
-rwsrwsr-x 1 root shell 100068 2022-12-27 16:10 su
cereus:/data/adb/modules/su_test # echo 'id=su_test' > module.prop
cereus:/data/adb/modules/su_test # echo 'name=su_test' >> module.prop
cereus:/data/adb/modules/su_test # echo 'version=0.0.1' >> module.prop
cereus:/data/adb/modules/su_test # echo 'versionCode=001' >> module.prop
cereus:/data/adb/modules/su_test # echo 'author=aIecxs @ XDA' >> module.prop
cereus:/data/adb/modules/su_test # echo 'description=proof that su binary is "suitable" >> module.prop
cereus:/data/adb/modules/su_test # cat module.prop
id=su_test
name=su_test
version=0.0.1
versionCode=001
author=aIecxs @ XDA
description=proof that su binary is "suitable"
cereus:/data/adb/modules/su_test # ./system/xbin/su --version
16 com.thirdparty.superuser
cereus:/data/adb/modules/su_test # exit
cereus:/data/local $ exit
C:\Android>
after installing the magisk module, rebooted the phone and confirmed su binary works when running from system.
Code:
C:\Android>adb -s ca1296db7d29 shell
cereus:/ $ which su
/sbin/su
cereus:/ $ ls -l /system/xbin/su
-rwsrwsr-x 1 root shell 100068 2022-12-27 16:10 /system/xbin/su
cereus:/ $ /system/xbin/su --version
16 com.thirdparty.superuser
cereus:/ $ /system/xbin/su
cereus:/ #
(note the /sbin/su binary is Magisk while the /system/xbin/su binary is the file copied from android tv box)
as on stock android device user/release-keys build adb root cannot work, there is no way to use the chown command. because it is impossible to place the file into /system or any proper location with directory owner 0 (root) from adb, it's not possible to get root shell from adb.
conclusion: an additional exploit (like mtk-su) is required to achieve this.
edit: fun fact. Magisk complains the foreign su binary that is provided by Magisk module xD
Related
Samsung Behold 2 Rooting
Here is the commands I used: cd\ cd androidsdk\tools adb push try3.dat /data/local adb shell chmod 0755 /data/local/try3 adb shell /data/local/try3 /system/bin/sh mount -o rw,remount /dev/st9 /system chmod 04755 /system/bin/sh cat /sdcard/su.dat > /system/bin/su1 cat /sdcard/su.dat > /system/bin/su chmod 04755 /system/bin/su su cat /system/bin/playlogo > /system/bin/playlogo_real /system/bin/chmod 0755 /system/bin/playlogo_real echo “#!/system/bin/sh /data/local/try3.dat /system/bin/sh mount -o rw,remount /dev/st9 /system chmod 04755 /system/bin/sh cat /system/bin/su1 > /system/bin/su chmod 04755 /system/bin/su /system/bin/playlogo_real” > /system/bin/playlogo exit exit exit adb install Superuser.apk adb shell reboot It said Superuser.apk installed successful. When I tried to reboot it said permission denied. Here is the CMD pasted. Please help me I have no idea what I am doing wrong. C:\AndroidSDK>cd\ C:\>reboot 'reboot' is not recognized as an internal or external command, operable program or batch file. C:\>cd\ C:\>cd androidsdk\ C:\AndroidSDK>adb shell error: device not found C:\AndroidSDK>adb shell error: device not found C:\AndroidSDK>adb shell $ su su su: permission denied $ exit exit C:\AndroidSDK>adb devices List of devices attached SGH-T939 device C:\AndroidSDK>adb shell $ su.dat su.dat su.dat: permission denied $ exit exit C:\AndroidSDK>adb shell $ su su su: permission denied $ su.dat su.dat su.dat: permission denied $ exit exit
Rooting the HTC DESIRE Z, VISION, G2 with Super Tool under Linux
I'm posting this in order to show how to use Super Tool under Linux (for Windows & Mac users, changes should be minimal) and also to show some weird results when rooting HTC Desire Z (aka Vision or G2) phones, which may lead to enhancements in the tool. Also, the Super Tool thread is already over 90 pages long, and has to do with several phones; I thought that a separate thread about these HTC phones would be useful; I hope this won't be against the forum rules, but please accept my apologies in advance if I'm wrong about this! A summary: To sum everything up in advance, results are sort of weird... you can get root using the ZergRush exploit, then install "su", "SuperUser", and "BusyBox", but after a while they just disappear. This makes me suspect that there is some kind of "behind the lines" software running, which sets things back to normal, but I don't know the solution yet. Some experiments I set up an Android development environment. I'm working in its platform-tools directory, where the "adb" command resides. I extracted the Super Tool files in the root of the Android directory, two levels up, so they are found at the ../../htcsupertoolv2 directory. I set my phone for USB Debugging, and then, working from the Linux shell: Code: $ ./adb kill-server $ ./adb start-server * daemon not running. starting it now on port 5037 * * daemon started successfully * $ ./adb devices List of devices attached HT0B9RT01278 device OK, my device is attached and ready. Let's see if we already had root: Code: $ ./adb shell $ su su: permission denied $ exit The device is in its basic state, and we haven't got root. Let's install the ZergRush code. Code: $ ./adb shell "rm /data/local/tmp/*" $ ./adb push ../../htcsupertoolv2/root/zergRush /data/local/tmp/. 451 KB/s (23056 bytes in 0.049s) $ ./adb shell "chmod 777 /data/local/tmp/zergRush" $ ./adb shell "./data/local/tmp/zergRush" [**] Zerg rush - Android 2.2/2.3 local root [**] (C) 2011 Revolutionary. All rights reserved. [**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew. [+] Found a GingerBread ! 0x00015118 [*] Scooting ... [*] Sending 149 zerglings ... [+] Zerglings found a way to enter ! 0x10 [+] Overseer found a path ! 0x000151e0 [*] Sending 149 zerglings ... [+] Zerglings caused crash (good news): 0x401219d4 0x0054 [*] Researching Metabolic Boost ... [+] Speedlings on the go ! 0xafd194d3 0xafd395bf [*] Popping 24 more zerglings [*] Sending 173 zerglings ... [+] Rush did it ! It's a GG, man ! [+] Killing ADB and restarting as root... enjoy! $ ./adb shell # exit Nice, it managed to get root, at least for the time being! Now, let's set the system R/W. Code: ./adb remount remount succeeded ./adb shell # mount rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 [COLOR="Red"]/dev/block/mmcblk0p25 /system ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0[/COLOR] /dev/block/mmcblk0p26 /data ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0 /dev/block/mmcblk0p27 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=ordered 0 0 /dev/block/mmcblk0p28 /devlog ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=ordered 0 0 [I][...many lines snipped out...][/I] # exit So, /system is now r/w. Let's push "su". Code: ./adb push ../../htcsupertoolv2/root/su /system/bin/su 411 KB/s (22228 bytes in 0.052s) ./adb shell "chown root.shell /system/bin/su" ./adb shell "chmod 06755 /system/bin/su" ./adb shell "rm /system/xbin/su" rm failed for /system/xbin/su, No such file or directory ./adb shell "ln -s /system/bin/su /system/xbin/su" ./adb push ../../htcsupertoolv2/root/Superuser.apk /system/app/. 2861 KB/s (785801 bytes in 0.268s) $ ./adb push ../../htcsupertoolv2/root/su /system/bin/su 516 KB/s (22228 bytes in 0.041s) $ ./adb shell # cd /system/bin # ls -l s* -rwxr-xr-x root shell 5392 2011-08-02 01:09 schedtest [I][...many lines snipped out...][/I] lrwxrwxrwx root shell 2010-10-26 09:02 stop -> toolbox [COLOR="Red"]-rw-rw-rw- root root 22228 2011-11-10 12:53 su[/COLOR] -rwxr-xr-x root shell 5456 2011-08-02 01:09 surfaceflinger -rwxr-xr-x root shell 192 2010-09-23 06:51 svc lrwxrwxrwx root shell 2010-10-26 09:02 sync -> toolbox -rwxr-xr-x root shell 5480 2011-08-02 01:09 system_server # chmod 755 su # chown root.shell su # ls -l su -rwxr-xr-x root shell 22228 2011-11-10 12:53 su As we see, "su" is installed, with the same owner/group/permissions as the other commands. Let's add a symlink in /system/xbin to "su". Code: # cd /system/xbin/ # ls -l * -rwxr-xr-x root shell 5536 2011-08-02 01:11 crasher -rwxr-xr-x root shell 60276 2008-08-01 09:00 dexdump -rwxr-xr-x root shell 22256 2011-08-02 01:11 wireless_modem # ln -s /system/bin/su /system/xbin/su # cd /system/xbin/ # ls -l * -rwxr-xr-x root shell 5536 2011-08-02 01:11 crasher -rwxr-xr-x root shell 60276 2008-08-01 09:00 dexdump [COLOR="Red"]lrwxrwxrwx root root 2011-12-30 16:48 su -> /system/bin/su[/COLOR] -rwxr-xr-x root shell 22256 2011-08-02 01:11 wireless_modem # exit There's the symlink, all right. Now, let's push "Superuser.apk". Code: $ ./adb push ../../htcsupertoolv2/root/Superuser.apk /system/app/. 2689 KB/s (785801 bytes in 0.285s) $ ./adb shell # cd /system/app # ls -l S* -rw-r--r-- root root 7221765 2011-08-02 01:08 Settings.apk [I][...many lines snipped out...][/I] -rw-r--r-- root root 296419 2011-08-02 01:09 Street.apk -rw-rw-rw- root root 785801 2011-11-10 12:54 Superuser.apk -rw-r--r-- root root 551020 2008-08-01 09:00 SystemUI.apk -rw-r--r-- root root 255720 2008-08-01 09:00 SystemUI.odex # chmod 644 Superuser.apk # ls -l Super* [COLOR="Red"]-rw-r--r-- root root 785801 2011-11-10 12:54 Superuser.apk [/COLOR]# exit So, there is Superuser.apk, with appropriate user/group/permissions. It's time for a reboot! Code: $ ./adb remount remount succeeded $ ./adb reboot A short while afterwards... Code: $ ./adb shell $ su [B][COLOR="Red"]su: permission denied[/COLOR][/B] $ cd /system/bin/ $ ls -l s* -rwxr-xr-x root shell 5392 2011-08-02 01:09 schedtest [I][...many lines snipped out...][/I] lrwxrwxrwx root shell 2010-10-26 09:02 stop -> toolbox -rwxr-xr-x root shell 5456 2011-08-02 01:09 surfaceflinger -rwxr-xr-x root shell 192 2010-09-23 06:51 svc lrwxrwxrwx root shell 2010-10-26 09:02 sync -> toolbox -rwxr-xr-x root shell 5480 2011-08-02 01:09 system_server $ cd /system/xbin/ $ ls -l * -rwxr-xr-x root shell 5536 2011-08-02 01:11 crasher -rwxr-xr-x root shell 60276 2008-08-01 09:00 dexdump -rwxr-xr-x root shell 22256 2011-08-02 01:11 wireless_modem So, "su" is gone?! The exploit managed a temp root, but after the reboot, something set things back to standard, removing "su" and "Superuser.apk". Doing this with scripts I set up a pair of scripts to automate the previous work (and included BusyBox installation, by the way) but the results are the same. The first script, htc1.sh, is: Code: #!/bin/sh ./adb shell "rm /data/local/tmp/*" ./adb push ../../htcsupertoolv2/root/zergRush /data/local/tmp/. ./adb shell "chmod 777 /data/local/tmp/zergRush" ./adb shell "./data/local/tmp/zergRush" The second script, htc2.sh, to be run afterwards, when (temp) root has been achieved, is: Code: #!/bin/sh ./adb remount ./adb push ../../htcsupertoolv2/root/busybox /data/local/tmp/. ./adb shell "chmod 755 /data/local/tmp/busybox" ./adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox" ./adb shell "cd /system/xbin; chown root.shell busybox; chmod 04755 busybox" ./adb shell "/system/xbin/busybox --install -s /system/xbin" ./adb shell "rm -r /data/local/tmp/busybox" ./adb push ../../htcsupertoolv2/root/su /system/bin/su ./adb shell "cd /system/bin; chown root.shell su; chmod 06755 su" ./adb shell "rm /system/xbin/su; ln -s /system/bin/su /system/xbin/su" ./adb push ../../htcsupertoolv2/root/Superuser.apk /system/app/. ./adb shell "cd /system/app; chmod 644 Superuser.apk" If you run ./htc1.sh and then ./htc2.sh results will be the same; the added commands will be gone, and you won't be able to "su" no more. The attached scripts should help Linux users to root other phones (which are known to work) but the Desire Z question still remains; there seems to be something missing, at least for the time being.
G2 Temp Root Hi, I got a tmo g2 2.3.4 i used the superhtctoolv2 on win7, and htcdrivers linked in the original thread. i performed the option 1 and 2, and was able to gain temp root, but just like every1 else it goes away with a reboot, or even after prolong period of inactivity, it works as long as i keep messing with Titanium backup or other root apps. Any way to combine this temp root with older options to gain a perm root?
Cool man! Thanks!
HTC security measure? Looking around, I found this page about a security method by HTC... to quote: The HTC software implementation on the G2 stores some components in read-only memory as a security measure to prevent key operating system software from becoming corrupted and rendering the device inoperable. There is a small subset of highly technical users who may want to modify and re-engineer their devices at the code level, known as rooting, but a side effect of HTCs security measure is that these modifications are temporary and cannot be saved to permanent memory. As a result the original code is restored. Click to expand... Click to collapse This sure looks like the problem we are having with the HTC DESIRE Z/G2/VISION...
Cannot get S-OFF I tried adapting the third script (get S-OFF) for Linux but it didn't work out. I first tried everything by hand. I ran ht1.sh first (to get root) and then went on to: Code: $ ./adb push ../../htcsupertoolv2/root/gfree /data/local 2127 KB/s (134401 bytes in 0.061s) followed by Code: $ ./adb shell # chmod 777 /data/local/gfree # ./data/local/gfree -f --secu_flag off set --cid set. CID will be changed to: 11111111 --sim_unlock. SIMLOCK will be removed Section header entry size: 40 Number of section headers: 44 Total section header table size: 1760 Section header file offset: 0x000138b4 (80052) Section index for section name string table: 41 String table offset: 0x000136fb (79611) Searching for .modinfo section... - Section[16]: .modinfo -- offset: 0x00000a14 (2580) -- size: 0x000000cc (204) Kernel release: 2.6.35.10-g7b95729 New .modinfo section size: 204 Attempting to power cycle eMMC... [B][COLOR="Red"]Failed. Module failed to load: No such file or directory[/COLOR][/B] So I'm guessing the DESIRE Z/G2/VISION cannot be perm rooted with Super Tool, at least "as is" --- I'll possibly be trying backdating the firmware next.
fkereki said: I tried adapting the third script (get S-OFF) for Linux but it didn't work out. I first tried everything by hand. I ran ht1.sh first (to get root) and then went on to: Code: $ ./adb push ../../htcsupertoolv2/root/gfree /data/local 2127 KB/s (134401 bytes in 0.061s) followed by Code: $ ./adb shell # chmod 777 /data/local/gfree # ./data/local/gfree -f --secu_flag off set --cid set. CID will be changed to: 11111111 --sim_unlock. SIMLOCK will be removed Section header entry size: 40 Number of section headers: 44 Total section header table size: 1760 Section header file offset: 0x000138b4 (80052) Section index for section name string table: 41 String table offset: 0x000136fb (79611) Searching for .modinfo section... - Section[16]: .modinfo -- offset: 0x00000a14 (2580) -- size: 0x000000cc (204) Kernel release: 2.6.35.10-g7b95729 New .modinfo section size: 204 Attempting to power cycle eMMC... [B][COLOR="Red"]Failed. Module failed to load: No such file or directory[/COLOR][/B] So I'm guessing the DESIRE Z/G2/VISION cannot be perm rooted with Super Tool, at least "as is" --- I'll possibly be trying backdating the firmware next. Click to expand... Click to collapse well that sucks!
[Q] Nabi XD root
So I have been working on rooting for the Nabi XD. Specifically to grab a dd of mmcblk0p1 and p2 so I can extract kernel and ramdisk to build a TWRP. The 2 options I have tried are 1) Bin4ry root many Android, 2) Build TWRP based off the different Nabi2 kernel to gain access to /system Bin4ry exploit fails with mount: Permission denied, when attempting to remount rw with busybox. The device is 4.1.1 so they must have patched it or cherry picked a patch. The build was this year. The TWRP will boot but with a blank screen. Comparing the config.gz for kernel builds explains the blank screen. ADB is however is up and running, but the internal storage is not seen as a block device. cat proc/partitions is blank. The third thing of interest is that there is a bin in xbin called su2. su2 -v yields an output of 3.3. Code: [email protected]:/system/xbin $ su2 -v su2 -v 3.3 [email protected]:/system/xbin $ su2 -help su2 -help Usage: su [options] [--] [-] [LOGIN] [--] [args...] Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login pretend the shell to be a login shell -m, -p, --preserve-environment do not change environment variables -s, --shell SHELL use SHELL instead of the default /system/bin/sh -v, --version display version number and exit -V display version code and exit, this is used almost exclusively by Superuser.apk [email protected]:/system/xbin $ ls -l su2 -rwxr-xr-x root shell 91728 2013-02-02 07:03 su2 How can I put this to use? Just running su2 over adb results in nothing, and through Term.apk as permission denied. I obviously need the associated Superuser.apk to grant access, but it seems hardcoded to look for su. I looked through the source to see if I could recompile to look for su2, but I don't know if it's as simple as that. Any thoughts?
Strange they left the su binary there. But first : show me a "ls -l su2", we need to see if it has correct permissions or if it is just there and cannot do anything Second: just try "su2 -c /system/bin/sh", if you are lucky it starts a rootshell. Regards
I thought it was weird too that is was left behind, and hopefully an easy way to even gain temp root. If I can just dd the boot partition it's smooth sailing. [email protected]:/system/xbin $ ls -l su2 -rwxr-xr-x root shell 91728 2013-02-02 07:03 su2 No setuid bit set? Should be -rwsr-sr-x? I tried the second thing via adb. It just echos the command and prompt stays $. Using something like Term.apk yields permission denied. Tried different quotes for passing -c. Any symlinking tricks? [email protected]:/system/xbin $ su2 -c /system/bin/sh su2 -c /system/bin/sh 1|[email protected]:/system/xbin $ su2 -c '/system/bin/sh' su2 -c '/system/bin/sh' 1|[email protected]:/system/xbin $ su2 -c "/system/bin/sh" su2 -c "/system/bin/sh" 1|[email protected]:/system/xbin $
[Q] Zygote Restrict slave mountspace
Has anybody tried to implement this in KitKat ? When I mount my server by sshfs on my Nexus 5 I can see this mount only in su, every other App/User is not seeing the mountpoint. As explained here http://forum.xda-developers.com/showthread.php?t=2106480 this is a "Security-Feature" for MultiUser-Support. So I've applied the Dalvik-Patch in android-4.4_r1 and compiled a new libdvm.so for my Nexus 5 und modified my boot.img (init.rc). But this does not solve the Problem as expected. Anybody has patched this in KitKat or has in depth knowlege of Zygote and Dalvik and could explain?
I've digged a litte deeper and found those threads: http://forum.xda-developers.com/showthread.php?t=1781411 http://forum.xda-developers.com/showthread.php?t=2062768 http://forum.xda-developers.com/showthread.php?t=2107224 All of those basicly say that it is possible to mount using adb and all apps will be able to access them, because adb is not running as a child-process of dalvik. This is why mounts are not visible to other apps when an app run by dalvik mounts them. What I don't really get is why mounts by sshfs are not visible to other processes even when I use adb to run sshfs: [email protected]:~$ adb shell [email protected]:/ $ su [email protected]:/ # sshfs [email protected]: /sdcard/mountpoint [email protected]:/ # mount ... sshfs#[email protected]: /storage/emulated/legacy/mountpoint fuse rw,nosuid,nodev,relatime,user_id=0,group_id=0 0 0 ... [email protected]:/ # exit [email protected]:/ $ mount ... <sshfs mount not listed> .... So why is the mount only visible when I'am root (in su)?
I'am still working on it and tried the following without using sshfs, but even bind-mounts are not accessible by other users. Does anyone know why and how to workaround it? [email protected]:~$ android/android-sdk-linux/platform-tools/adb shell [email protected]:/ $ su [email protected]:/ # mount -o rw,remount / [email protected]:/ # mkdir /mnt/test [email protected]:/ # chown media_rw:media_rw /mnt/test/ [email protected]:/ # chmod 777 /mnt/test/ [email protected]:/ # busybox mount --bind /mnt/sdcard/ /mnt/test [email protected]:/ # ls /mnt/test/ -la drwxrwx--- root sdcard_r 2013-11-06 14:10 .MySecurityData -rw-rw---- root sdcard_r 33 2013-11-20 18:17 .bugsense drwxrwx--- root sdcard_r 2013-11-21 14:00 .estrongs drwxrwx--- root sdcard_r 1970-01-02 01:01 Alarms drwxrwx--x root sdcard_r 2013-11-06 01:12 Android drwxrwx--- root sdcard_r 2013-11-12 18:10 DCIM drwxrwx--- root sdcard_r 2013-11-18 23:38 Download ... [email protected]:/ # exit [email protected]:/ $ ls /mnt/test -la [email protected]:/ $
[Q] Error while remount a partition read only
I have a rooted HTC and need to create a custom file in /system/xbin. I execute a mount command (for read-write permission on /system), create the file, remount /system in readonly and after that my file magically disappear. Here are the commands I wrote in a su shell via adb. Code: [email protected]:/system/xbin # mount | grep system /dev/block/mmcblk0p35 /system ext4 ro,seclabel,relatime,data=ordered 0 0 [email protected]:/system/xbin # mount -o rw,remount /dev/block/mmcblk0p35 /system [email protected]:/system/xbin # cd /system/xbin [email protected]:/system/xbin # echo test > myfile [email protected]:/system/xbin # ls daemonsu dexdump dexus myfile <- 'myfile' is created nc su [email protected]:/system/xbin # cat myfile test [email protected]:/system/xbin # mount -o ro,remount /dev/block/mmcblk0p35 /system [email protected]:/system/xbin # ls daemonsu dexdump dexus nc su PUFF after remounted /system in readonly my file is disappeared. Any idea about this? NOTE: If I try to re-execute the commands, my HTC restarts itself ... EDIT 2: As you could see in the 'ls' command output, in /system/xbin exist 'su' installed with a root tool. How could this root tool install 'su' permanently?