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

Root [fixed] Kyocera Rise Root Issue

xaltjc

Lurker
(I also posted this question on xda.)

I was wondering if someone could help. I have followed all the instructions of this post http://forum.xda-developers.com/show....php?t=1886460 It says it is successful, but still do not have root access. Could someone tell me if they see something wrong?

Here is the log from Root Checker.

Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.98 - is 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: -rwsr-sr-x root root 91988 2012-11-20 09:39 su
Analysis: Setuid attribute present and root user ownership 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:
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: shell (non root) user - ro.secure=1
Results provided on your C5155 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
 
"Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist."

Pretty sure it is saying su is not there.
Have you checked with a file explorer?
 
There's still an issue. Removing supersu, root works, but there is no control. Installing superuser, and it won't update binaries, and it doesn't prompt when a program requests root permissions but root is still there. Something is still up, its not good not knowing what is getting root access.

Any fixes? I've tried the older version on the root program, still something is up.
 
There's still an issue. Removing supersu, root works, but there is no control. Installing superuser, and it won't update binaries, and it doesn't prompt when a program requests root permissions but root is still there. Something is still up, its not good not knowing what is getting root access.

Any fixes? I've tried the older version on the root program, still something is up.

I've been a little stumped by this myself. I'm fairly new to this device but have a lot of experience with my other device (Motorola Photon 4G).

Like u mentioned above, I've noticed the same issue. If u really wanna know what's accessing root, u can keep SuperSU installed, just make sure its set to GRANT root privileges instead of PROMPT. This is the only way I've been able to keep track of what apps are accessing root.

I've seen it mentioned several times to uninstall SuperSU and install Superuser, but like u mentioned, that really does nothing as it won't successfully update the "su" binary. To get around this, I tried swapping out the apk and binary in the "stuffs" folder within the root script mentioned to use with Superuser and it installed it and the correct binary, but root still doesn't work regardless and I ended up having to replaced SuperSU and its binary in order to have root back.

So in conclusion, something isn't right. Granted, we definitely have root but we're not able to use the Superuser apps to their fullest by any means.
 
I've been a little stumped by this myself. I'm fairly new to this device but have a lot of experience with my other device (Motorola Photon 4G).

Like u mentioned above, I've noticed the same issue. If u really wanna know what's accessing root, u can keep SuperSU installed, just make sure its set to GRANT root privileges instead of PROMPT. This is the only way I've been able to keep track of what apps are accessing root.

I've seen it mentioned several times to uninstall SuperSU and install Superuser, but like u mentioned, that really does nothing as it won't successfully update the "su" binary. To get around this, I tried swapping out the apk and binary in the "stuffs" folder within the root script mentioned to use with Superuser and it installed it and the correct binary, but root still doesn't work regardless and I ended up having to replaced SuperSU and its binary in order to have root back.

So in conclusion, something isn't right. Granted, we definitely have root but we're not able to use the Superuser apps to their fullest by any means.
Yeah, I was able to manually get the latest binaries in too, but like you said it breaks root. It looks like this program works from the pics. [GUIDE] Root your Kyocera Rise! - Android Forums at AndroidCentral.com
I haven't tried it yet, if it doesn't, I'll slap supersu back on and change out the settings like you said.
 
Yeah, I was able to manually get the latest binaries in too, but like you said it breaks root. It looks like this program works from the pics. [GUIDE] Root your Kyocera Rise! - Android Forums at AndroidCentral.com
I haven't tried it yet, if it doesn't, I'll slap supersu back on and change out the settings like you said.

Lol I see we're on the same page with this. I say that becuz I just read in another post that basically to solve the issue, an older version of the su binary and apk is needed. Pretty much the same as what u just showed me by providing that link.

I'm gonna test both here momentarily to see what the results are.

What's really strange about this tho, is when I first rooted this device a couple months ago, I swear I didn't have this issue with SuperSU. I could've sworn it prompted me to grant permission but I had since updated SuperSU and changed the setting to grant permission. About a week ago I noticed I wasn't getting a toast notification anymore from ES File Explorer and Titanium Backup and have been messing with it on device with no luck.

I've been determined to figure this out one way or another! I'll report back here in a few. Gonna try re-rooting to see if anything changes
 
**Update**

I tested the version from the link u provided and it worked! Here is the proof!
yva3udeb.jpg


So that was the issue then, it was becuz the newer apk's and binary's don't play nice with our device at this time!

*Edit*
Logging also works now as expected :)

ytume9uj.jpg
 
Cool man thanks for the update. I'll run it tomorrow.

UPDATE: Worked for me too. This script should be in the "All things Root" guide.
 
Back
Top Bottom