• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help with SuperSU please

Long story short, I was trying to update SU, but Google Play store said there was a problem with package file is invalid, so I went into the SU, clicked the spanner on the top right and manually updated SU. In doing so I partially lost my root access..

Here's the log from Root Checker Pro

Root Access is not properly configured or was not granted.

Super User Application Status:
Superuser application - version 3.0.2 - is installed!

SuperSU application - is NOT installed.

System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!

Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!

Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.

Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:
SU binary not found or not operating properly

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0

Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4

I've tried a couple of things, including unrooting and rerooting (using SRS Tool), downgrading SuperUser to v3.0.2 (great fun using adb.exe) and generally shouting at the phone (which helped a little)

Thanks in advance guys, sorry if I've posted this in the wrong section?
 
su (not SU - case counts in Android) is a binary, there's no user interface to click anything on - which is why there's a SuperSU app.

It says, "SuperSU application - is NOT installed."

Go to Play and install SuperSU.

Yes, agree after I reset the phone back to factory settings previously I didn't reinstall SuperSU.. I will do it now but I'm pretty sure that it won't make much of a difference as it wasn't on the phone which originally came rooted.


Welcome to Android Forums.

What device are you using and who is your carrier (e.g., Verizon).

... Thom

Hi Thom and thanks for your kind welcome. I'm in Ireland and using '3' - again the phone arrived SIM free so I didn't have to do anything to it, just popped my old SIM card into it and away I went.


Have you tried flashing an update zip?

No I have no, because my phone is a S3 Clone (details below) I haven't dared do anything like that.

Model : K47/C9_89
Build number : v89_jhgg_notv_20130502
Build date UTC : 20130502-084032
Android v : 4.2.1
Baseband v: MOLY.WR8.W1248.MD.WG.MP.V6.P4, 2013/04/12 17:49
Kernel v : 3.4.5 (root@android)
(gcc version 4.6.x-google 20120106 (prerelease) (GCC) )
#1 SMP Fri May 3 15:59:20 CST 2013
Uboot build v : -----
LCD Driver IC : 1-RX_47HX_500A

Here's the new Root Checker Pro log

Root Access is not properly configured or was not granted.

Super User Application Status:
SuperSU application - version 1.91 - is installed!

System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!

Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!

Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.

Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:
SU binary not found or not operating properly

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0

Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
 
Upvote 0
Yes, agree after I reset the phone back to factory settings previously I didn't reinstall SuperSU.. I will do it now but I'm pretty sure that it won't make much of a difference as it wasn't on the phone which originally came rooted.

If the phone came rooted, it's very likely that the su binary is in the system folder and would be restored on reset. SuperSU, the app, is user installed and would be removed when you performed a reset. I'll bet you'll find that once you install the SuperSU app, you've got root access again.
 
Upvote 0
If the phone came rooted, it's very likely that the su binary is in the system folder and would be restored on reset. SuperSU, the app, is user installed and would be removed when you performed a reset. I'll bet you'll find that once you install the SuperSU app, you've got root access again.

I've tried the system reset this morning (settings, backup & restore, factory data reset) unfortunately it didn't downgrade the update which I applied in SU.

That update occurred in a mini terminal window on my phone. I installed SuperSU and then posted my latest Root Checker Pro log (above) unfortunately it didn't make any difference :-(

Since then I've un-rooted, re-rooted, factory reset, manually downgraded SU all to no avail. I'm obviously missing something, I'm fairly technically savvy but I haven't a clue what to do next.. it's very frustrating!


This thread was moved to the forum where phones are discussed that don't have a dedicated forum.

... Thom

Thanks Thom (I think? lol, fingers crossed somebody will be able to help me!!)



EDIT : After running SuperSU it says that SU binaries need updating, when clicking OK it say it can do it using Normal mode or TWRP/CWM..

Normal mode complains that other SU programs are installed and when I choose to remove them I get Installation Failed!

I've just installed GooManager_2.1.3.apk to try the TWRP method.. It doesn't reboot itself so by pressing home and power I can get into Recovery mode but unfortunately it doesn't look like I have half of the options that I expected to see?

Obviously I don't want to brick the phone and I'm scared to choose Clear eMMC :-(

The instructions I was following can be viewed here.

Here is a small screenshot of my recovery mode options..

98Bie2tl.jpg


I've also tried CWM, but have an unsupported device so am unable to create a backup and continue with the operation :-(

Here's a small screenshot of trying to update SU binaries using SU itself

JCxZucPl.jpg


Now I will be manually able to update this (when I have a little more time tomorrow) as it was me who manually downgraded from v3.0.7 thinking where I went wrong was updating this in the first place.
 
  • Like
Reactions: lunatic59
Upvote 0
You edited your last post after I originally posted. Those pics you added help to tell the story. You are not using Super SU (by Chainfire). You are instead using Superuser (by ChainsDD). It has an outdated root binary. So delete the Superuser app and then use the SuperSU app which at startup will typically automatically update the binary if needed. I believe you already have both apps on your phone which is why it complained about competing root apps.

If by some chance the binary does NOT autoupdate, go into SuperSU's settings and choose the option under Cleanup titled "reinstall". That will do some smoke and mirrors in the background and when reinstalled, it should allow the app to see your phone, the su binary and it's location as a new project so to speak. Then the auto update of the binary should occur.
 
Upvote 0
I've tried SuperSU, it also is unable to update the binaries. Tried the cleanup reinstall too both with no luck.

Tonight I will uninstall Superuser, SuperSu, unroot my phone and await further instructions! Thanks


EDIT : Now that I have a little more time,

A factory reset will not take you back to previous versions. Once you've upgraded Android it will stay at the current version unless you flash the entire firmware package. Are you at least able to set SuperSU from the play store?

Initially this surprised me, however I guess that just highlight my inexperience with Android. As you have realised SuperSU is or at least was then installed.


Do you also have the Busybox app installed on your phone? If not, you may want to try installing that, then install SuperSU and attempt to mange root with it.

I have the installer on the phone, however Busybox itself will not load up and install due to not having correct root access.


Thread moved to Android Applications, as it concerns an application issue.

Thanks, hopefully I will get more hits/replies! :)


You edited your last post after I originally posted. Those pics you added help to tell the story. You are not using Super SU (by Chainfire). You are instead using Superuser (by ChainsDD). It has an outdated root binary. So delete the Superuser app and then use the SuperSU app which at startup will typically automatically update the binary if needed. I believe you already have both apps on your phone which is why it complained about competing root apps.

If by some chance the binary does NOT autoupdate, go into SuperSU's settings and choose the option under Cleanup titled "reinstall". That will do some smoke and mirrors in the background and when reinstalled, it should allow the app to see your phone, the su binary and it's location as a new project so to speak. Then the auto update of the binary should occur.

Yes agree, although at some stages I've actually had both on my phone. I did try to reply to this sooner using browser on my phone whilst at college however I somehow lost my reply and didn't have the time to type it all out again, so now here goes! - I seem to have a mismatch between which ever superuser application I choose to use and the su binary itself. The phone originally arrived with superuser 3.0.1 (i think) and after I updated it is when these problems started occuring. After seeing Root Checker Pro's (RCP) log file I decided to install SuperSU so at that point I had both on the phone. Neither would update the problematic binary so I started to do that manually myself. I down graded it successfully so as long as I get the right binary I would assume I can fix the problem using adb.exe, even SuperSU's reinstall cleanup didn't help matters when I tried using that.

As previously mentioned I have now installed both Superuser, SuperSU, manually removed the SU binary and un-rooted the phone. Awaiting instruction!

Current RCP log..

Root Access is not properly configured or was not granted.

Super User Application Status:
Superuser application - is NOT installed.
SuperSU application - is NOT installed.

System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.

Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.

Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.

Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:
SU binary not found or not operating properly

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0

Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4

This could also be part of the problem??

BusyBox has been installed correctly!

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

BusyBox binary location:
/system/xbin/busybox

BusyBox binary file information:
-rwxr-xr-x root root 822080 2014-01-13 17:17 busybox

Installed BusyBox Version:
1.21.1-Stericson

BusyBox supports the following applets:
[, [[, ash, awk, base64, basename, blkid, bunzip2, bzcat, bzip2, cal, cat, chat, chattr, chgrp, chmod, chown, chroot, chrt, cksum, clear, comm, cp, crond, crontab, cut, date, dd, depmod, devmem, df, diff, dirname, dmesg, dnsd, dnsdomainname, dos2unix, du, echo, egrep, env, ether-wake, expand, expr, fakeidentd, fbset, fdflush, fdformat, fdisk, fgrep, find, fold, free, freeramdisk, fsck, fsync, ftpd, ftpget, ftpput, fuser, getopt, grep, groups, gunzip, gzip, hd, head, hexdump, hostid, hostname, httpd, hwclock, id, ifconfig, ifenslave, inetd, inotifyd, insmod, install, ionice, iostat, ip, ipaddr, ipcalc, iplink, iproute, iprule, iptunnel, kill, killall, killall5, less, ln, logname, losetup, ls, lsattr, lsmod, lsof, lsusb, lzop, lzopcat, md5sum, microcom, mkdir, mkdosfs, mke2fs, mkfifo, mkfs.ext2, mkfs.vfat, mknod, mkswap, modinfo, modprobe, more, mount, mountpoint, mt, mv, nameif, nanddump, nandwrite, nc, netstat, nice, nmeter, nohup, nslookup, ntpd, od, patch, pgrep, pidof, ping, ping6, pkill, pmap, powertop, printenv, printf, ps, pscan, pwd, rdate, rdev, readahead, readlink, realpath, renice, reset, rev, rfkill, rm, rmdir, rmmod, route, run-parts, script, scriptreplay, sed, seq, setkeycodes, setlogcons, setsid, sha1sum, sha256sum, sha3sum, sha512sum, showkey, sleep, smemcap, sort, split, start-stop-daemon, stat, strings, stty, sum, swapoff, swapon, sync, sysctl, tac, tail, tar, tee, telnet, telnetd, test, tftp, tftpd, time, timeout, top, touch, tr, traceroute, traceroute6, tty, ttysize, tunctl, umount, uname, uncompress, unexpand, uniq, unix2dos, unlzop, unzip, uptime, usleep, uudecode, uuencode, vconfig, vi, watch, wc, wget, which, who, whoami, whois, xargs, zcat
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4

As far as I knew Busybox had been uninstalled, as it doen't show up in any of my App lists (downloaded, running or all) I assume I should also remove the binary from /system/xbin/busybox and have now done so...

Busybox file was not found in the system declared path. A popular method of installing Busybox is to use this BusyBox app by Stericson in Google Play
 
Upvote 0
How did you resolve your problem of....

  • SuperSU
  • Binary failed to download / update

I found a rather tasty batch file which put everything correctly as it should of been, the instructions are as per:

1.Make sure USB debugging is enabled. Go to settings > developer options > enable USB debugging
2.Install the PDAnet Drivers in the installation they ask for a brand select other.
After installing the drivers unplug your phone
3.Extract the Motochopper MTK6589 Auto Root folder from the .rar download
4.Connect your phone to PC
5.Run run.bat from the Motochopper MTK6589 Auto Root folder
6.Press any key and wait while it roots your phone
7.After finished, now reboot
8.You''re phone is rooted please check root with root checker. This worked for me and if you brick your phone just reinstall the isa a19q rom
rom is available here: check .txt file on the bottom for the rom


Files :

Code:
http://www.mediafire.com/download/yhtdxgf22p6zohc/PDAnet_MTK6589_MTK6577_4016.rar

Code:
http://www.mediafire.com/download/0dcs9e2251ztimo/Motochopper_Auto_Root_(1).rar

Sorry for late reply, im not as quick checking my emails these days!
 
Upvote 0
Yes, agree after I reset the phone back to factory settings previously I didn't reinstall SuperSU.. I will do it now but I'm pretty sure that it won't make much of a difference as it wasn't on the phone which originally came rooted.




Hi Thom and thanks for your kind welcome. I'm in Ireland and using '3' - again the phone arrived SIM free so I didn't have to do anything to it, just popped my old SIM card into it and away I went.




No I have no, because my phone is a S3 Clone (details below) I haven't dared do anything like that.

Model : K47/C9_89
Build number : v89_jhgg_notv_20130502
Build date UTC : 20130502-084032
Android v : 4.2.1
Baseband v: MOLY.WR8.W1248.MD.WG.MP.V6.P4, 2013/04/12 17:49
Kernel v : 3.4.5 (root@android)
(gcc version 4.6.x-google 20120106 (prerelease) (GCC) )
#1 SMP Fri May 3 15:59:20 CST 2013
Uboot build v : -----
LCD Driver IC : 1-RX_47HX_500A

Here's the new Root Checker Pro log

Hi. Can You please make FW backup? I lost my FW and now the screen is dark. please help. I have the same phone as your!
Q9300 Smartphone MTK6589 Quad Core 1.2GHz Android 4.2 4.7 Inch - White
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones