I was wondering if someone could help. I have followed all the instructions of this post http://forum.xda-developers.com/showthread.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
Fixed
Removed Super SU all is now ok.
I have been trying to root my Kyocera Rise I just got a week ago, and I am having this problem as well. However it seems that removing SuperSU isn't doing the trick. What was your method of going about this? I'm so lost without root access . I followed the tutorial to a T, multiple times, as other users have suggested, and I get nothing! Thanks for your time!
I had the same problem I went into stuff folder of binry and replaced supersu with su, re-ran it and root took 1st time
Sent from my Amazon Kindle Fire using Tapatalk 2
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Could not get v17 to work. I saw in the thread v3 was supposed to so I tried it and after a few attempts I got it.
Sent from my LG-VM670 using Tapatalk 2
any luck on 4.0.4?
the latest krise firmware version is 4.0.4.
In the thread the guy who reported rooting success didn't say his version num, so it could be outdated information.
I am on 4.0.4, was not aware of any other version for this phone
Sent from my Amazon Kindle Fire using Tapatalk 2
jimchee said:
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Click to expand...
Click to collapse
Could you please be more specific with your procedure?
sonic_knx said:
Could you please be more specific with your procedure?
Click to expand...
Click to collapse
Since you have a rooted copy now, could i borrow a backup or a copy of the system folder because I installed hp beats audio installer (do not do) and my audio drivers are messed up. It is really taking a long time to get a copy so I was hoping that you guys would have a good copy. I also have another guy with the same issue so please help us.
the actual problem and a slight fix...
The actual problem/glitch with supersu is when it tries to promt access for su it freezes the app. When I tried unistalling supersu and installing superuser. It did not work for me even with the proper uninstall procedure (going into super su settings and click uninstall and prepare for new su app. Then go to the play store search supersu, google still thinks installed so click uninstall from there then immediatly search and install superuser.) I even tried going into the root setup folder I downloaded and switched the su apk files to start the root fresh... and still nothing. I figured out its the problem with the app trying to promt you for su access (ether app) bcs when I went into the settings I changed it to automaticaly grant su (TO EVERY APP READ BOTTOM DISCLAIMER) instead of promting you to ask for su.
DISCLAIMER: I AM NOT RESPONSIBLE FOR A ROUGE APP TAKING ADVANTAGE OF YOUR PHONE WITH YOUR SU SET TO GRANT ACCESS TO ALL APPS INSTEAD OF PROMTING YOU FOR YOUR ACTION ON ACCESS.
root VM rise
I used this method to root my Rise it says hydro but works on rise too.
http://www.cricketusers.com/content/646-root-cricket-wireless-kyocera-hydro-tutorial.html
Related
Check this thread for updated and improved information, many thanks to j4mm3r
http://forum.xda-developers.com/showthread.php?t=953110
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2
Extract the above files using your favourite program
Using adb, install all three files to /data/local:
adb push su /data/local
adb push Superuser.apk /data/local
adb push busybox /data/local
Use adb remount to open the /system directory
adb remount
Use adb shell to move files
adb shell
cd /data/local
cat Superuser.apk > /system/app/Superuser.apk
cat su > /system/bin/su
cat busybox /system/xbin/busybox
Symlink su and set permissions:
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
Typing su should now work
su
su: access granted, courtesy of www.magicdroidapps.com
Install busybox
exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,
su
busybox --install -s /system/xbin
That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.
Good Luck
really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
anbradle said:
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
Click to expand...
Click to collapse
Check your steps, especially permissions and the symlink. Works consistently on reboot for me.
Homer_S_xda said:
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
Click to expand...
Click to collapse
I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin
chhaggerty said:
It wouldn't work for me without installing in /system/bin and using a symlink to /system/xbin
Click to expand...
Click to collapse
It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...
[email protected]:/system/bin # echo $PATH
echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
[email protected]:/system/bin # ls -l su
ls -l su
su: No such file or directory
[email protected]:/system/bin # ls -l /system/xbin/su*
ls -l /system/xbin/su*
-rwSr-sr-t root root 76232 2011-02-04 09:08 su
-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic
-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new
-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org
chhaggerty said:
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2.
Good Luck[/B]
Click to expand...
Click to collapse
i might take credit for gaining root, but the rest is all you
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
nswenson said:
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
Click to expand...
Click to collapse
Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
You were right I tried again and now I am rooted after reboot. Thanks
jleecong said:
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
Click to expand...
Click to collapse
Okay...
I am running HC (v2) off a 8gb sd card.
So do I just do these steps to gain root or do I need to partition the sd card first?
Thanks
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
agreed, i was just going for root myslef
j4mm3r said:
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
In
http://howto.ccroms.net/android_project/build/mod/root
I would have though that the purpose of the changes, specifically;
LOCAL_FORCE_STATIC_EXECUTABLE := true
LOCAL_STATIC_LIBRARIES := libc
Were what should resolve the _mktemp not found?
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Mikey1022 said:
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Click to expand...
Click to collapse
yes, at the stands, its just root access. granted i had my own reasons for this
I'm unmounted and rooted, but every now and then an app requiring root will tell me I don't and usually say the Superuser.apk is missing. CWM runs fine, Absolute system tools pops up saying I don't, but then another popup from Superuser says Root access granted to absolute system tools and it allows me to use all the options within. So I downloaded and ran root check, here are the results. Any ideas why I'm getting the error?
Advanced Root Check
Congratulations you have root access!
Standard su binary location:
/system/xbin/su: No such file or location
Alternate su binary location:
/sbin/su: No such file or location
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Reventrant said:
I'm unmounted and rooted, but every now and then an app requiring root will tell me I don't and usually say the Superuser.apk is missing. CWM runs fine, Absolute system tools pops up saying I don't, but then another popup from Superuser says Root access granted to absolute system tools and it allows me to use all the options within. So I downloaded and ran root check, here are the results. Any ideas why I'm getting the error?
Advanced Root Check
Congratulations you have root access!
Standard su binary location:
/system/xbin/su: No such file or location
Alternate su binary location:
/sbin/su: No such file or location
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Click to expand...
Click to collapse
Try uninstalling & re-installing Superuser. Also make sure to check the "Remember" option the first time you use an app.
I uninstalled and reinstalled the Superuser app.
/system/app/Superuser.apk does not exist is the error I get, but it goes away quickly and I can use all the tools.
SD Maid works
ROM manager works
SetCPU works
Root Check says I am
*shrug*
I used Oneclickroot and it says my device is rooted, but none of the apps like Titanium backup, say I have root. I also followed another way or rootiong my phone where you use the volume down button to select "reinstall packages" it says it was rooted successfully, yet none of the root-required apps are detecting root. I also have the superuser app installed now.
I dont want to flash a ROM or anything, i just want to delete the bloatware and make my battery last longer
Are you on android 2.2 or 2.1?
Sent from my SGH-T959 using xda premium
im on 2.2 with froyo.
I actually followed the directions that were posted on XDA about how to root, so im not sure why it didnt work. This is another that I followed when the XDA one didnt work... http://www.techwhizz.com/root-samsung-vibrant-android-22-froyo-2/
I also keep getting this when OnClickRoot asks to test when rooting is finished...
Running a SU test...
Test failed!
FAILED
any suggestions?
I have used the ODIN route with Eugene's Unofficial TMO 2.2 Froyo ODIN. You can find it here with the directions:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
If you are successful, you will be rooted and stock. Some of the bloat will already be removed. Good Luck.
The goal is not to wipe anything from my phone. This is why I have never bothered to root my phone. I knew something would go wrong, and it would be so easy like everyone says it is. I just want my battery to last longer. Im already using Juice Defender, but I still only get about 8 hours on my phone. I hardly use it and find it almost dead by 8pm
I have busybox and battery calibrator, but say im not rooted. Superuser shows no apps
To be clear, you were using nothing but stock 2.2 Froyo. You then used the OneClickRoot method for rooting, follow all instructions exactly as they're listed. After you rebooted, you attempted to download and use an app that requires root and it didn't work. Is that correct?
I've noticed that occasionally Titanium Backup won't properly recognize root until you've wiped the data for it through the Applications Manager.
kaintfm said:
To be clear, you were using nothing but stock 2.2 Froyo. You then used the OneClickRoot method for rooting, follow all instructions exactly as they're listed. After you rebooted, you attempted to download and use an app that requires root and it didn't work. Is that correct?
I've noticed that occasionally Titanium Backup won't properly recognize root until you've wiped the data for it through the Applications Manager.
Click to expand...
Click to collapse
thats correct. The only thing that does recognize root is now battery calibrator. Superuser still shows no apps
so far the only app that recognizes root is battery calibrator. Busybox, TB, and autokiller memory optimizer dont recognize root. super user shows no apps. Im wondering if my phone is even rooted, since after using battery calibrator, my phone has dropped 15% in the last 20 minutes. Nothing is even running on my phone. its just sitting there.
I did use Root Checker, heres the results...
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SGH-T959 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae
but I guess BusyBox was installed correctly...
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
BusyBox binary location: /system/xbin/busybox
BusyBox binary file information: -rwxrwxrwx root root 282624 2011-10-27 22:46 busybox
Installed BusyBox Version:
BusyBox is not sharing its version information
BusyBox supports the following applets:
BusyBox is not sharing its supported applets
Results provided on your SGH-T959 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae
Im sure that im putting the update.zip on the internal sdcard and that it isnt called update.zip.zip. Ive been at this for 3 days now...
Anything? Ive posted the results from Root Check... really didnt think rooting would be this much of an ordeal
How about if you unroot and start over.
Get a terminal (any terminal) from the market or if you have adb set up and run these commands.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Then start over with the update.zip from the stickie that I show you yesterday.
I don't usually solicit thanks but this is going on two days now. How about a little something for the effort, eh? hahaha
I did try ot unroot last night with one click root and it says Im not rooted when I try that. I did use the update.zip from the sticky you gave me.
When i used the terminal I got:
rm failed for -r/system/bin/su, no such file/directory
reboot: operation not permitted
At this point, i would say Odin back to stock or try to re-root with the first method you tried. I agree though, it should not be this hard to do it. If you do end up going back to stock, just use the update.zip method to root it. It works so much easier.
Like I said yesterday, it took less than 3 mins to do it. It actually took me longer to download it than to do it and I never once hooked up to a PC. Did it all through phone with browser, xda app and root explorer.
itsLYNDZ said:
When I used the terminal I got:
rm failed for -r/system/bin/su, no such file/directory
reboot: operation not permitted
Click to expand...
Click to collapse
Did you type su and then enter first? Did ask for superuser permission? From what you posted last night and now this, I am almost positive that you are not rooted and Odin-ing back tostock is the way to go and start over.
I just deleted the update.zip file. im gonna start over, again. Should it remain zipped? Or do I need to extract it? Ive also read somewhere the update.zip needs to go in the j:/ or the root of the internal sdcard? I dont see that anywhere on the internal sdcard or anywhere in my files. Ill try the terminal again.
Hi guys, need some help here.
I followed all the steps to unlock the bootloader and root the rezound last night but the root didnt work. The bootloadrer is unlocked, i have been able to confirm that at the very least by going back into the fastboot screen.
I was using the guide at the unlocker as it really went over step by step in great detail.
No idea what i did and am really hoping someone can provide me some guidance here.
See below for the errors i am getting from root checker app.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-09-18 06:41 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2012-09-18 06:41 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 /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: shell (non root) user - ro.secure=1
Results provided on your ADR6425LVW device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market -
Thanks so much, i have always done a ton of reading on this site and love it...figured it was about time to reach out for some help.
Thanks again and please let me know if i can provide any other info that would help you all figure out where i went wrong.
Amon Ra 3.15?
swilbert80 said:
Amon Ra 3.15?
Click to expand...
Click to collapse
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
jesternsb said:
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
Click to expand...
Click to collapse
When you pull battery and then power + volume down start into hboot (make sure no PH98IMG.zip on root of ext sd card), you should be able to get into recovery. You will see very quickly if Amon Ra is there. It is a dark screen with blue text. If you don't have it, you can get it at:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
I assume you are using adb fast boot for this. If I am telling you stuff you already know, let me know.
jesternsb said:
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
Click to expand...
Click to collapse
If you are not sure on Amon Ra, I think you missed a step. The unlocker only puts the SuperSU program on your phone. You then need to go into recovery (Amon Ra) and flash the file. When I did this to my friends phone a few days ago, the file was on the internal SD card.
If you are still having issues, please refer to this thread - http://forum.xda-developers.com/showthread.php?t=1872651
Download the latest version of SuperSU zip file and install it with Amon RA recovery.
http://download.chainfire.eu/204/SuperSU/
swilbert80 said:
When you pull battery and then power + volume down start into hboot (make sure no PH98IMG.zip on root of ext sd card), you should be able to get into recovery. You will see very quickly if Amon Ra is there. It is a dark screen with blue text. If you don't have it, you can get it at:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
I assume you are using adb fast boot for this. If I am telling you stuff you already know, let me know.
Click to expand...
Click to collapse
Thanks for the info.....I went back into the hboot menu and did see a zip file titled PH98IMG.zip when it flashed the check on that hboot screen....i also was able to go into recovery and see a black backround with options to install the su.......and yes i am using adb for this.
Hey thanks for the reply here HowardZ......i am assuming i place that file in the same location as i do the recovery image? Trying to figure this out tonight....never a dull moment. lol
Thanks again
Correction.....no ph98im.zip was located....was just searching for it.
UPDATE i tried to go back through ADB and re work the steps and now the superuser is not on the phone anymore....argh.
UPDATE...i dl'ed the superuser through google play.....but still no root access.
I think if i can get some guidance on flashing Amon Ra and getting the supersu on the phone i might be ok, not 100% on that though.
Updated root checker report below.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2012-09-18 19:22 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 /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-09-18 19:22 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
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: shell (non root) user - ro.secure=1
Results provided on your ADR6425LVW device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market
Flash amon ra in boot loader and then download the super user.zip, the link is a few posts above mine
Sent from my cm_tenderloin
You can try updating the binary for SU from:
http://androidsu.com/superuser/
First, reinstall SU in recovery, and then flash the new binary followed by reboot. Should fix so SU remains (in app drawer) and root success.
MD5 checksum provided below DL link to check.
chaos254 said:
Flash amon ra in boot loader and then download the super user.zip, the link is a few posts above mine
Sent from my cm_tenderloin
Click to expand...
Click to collapse
Hey Chaos thanks for the reply here.....and please excuse my Noob-ness, god i hate the sound of that. I just want to make sure i fully understand and follow your instructions here.
Once i flash the amon ra recovery in the bootloader where do i save the super user zip file to and how do i flash that? That is where i seem to be getting hung up on.....not exactly sure where to save that file to and where to access/flash it from.......
I just want to make sure i follow you so that i dont scew it up.
thanks again
jesternsb said:
Hey Chaos thanks for the reply here.....and please excuse my Noob-ness, god i hate the sound of that. I just want to make sure i fully understand and follow your instructions here.
Once i flash the amon ra recovery in the bootloader where do i save the super user zip file to and how do i flash that? That is where i seem to be getting hung up on.....not exactly sure where to save that file to and where to access/flash it from.......
I just want to make sure i follow you so that i dont scew it up.
thanks again
Click to expand...
Click to collapse
Superuser.zip should be on your SD card. Once in amon ra>flash zip menu>sdcard>superuser.zip
Sent from my ADR6425LVW using Tapatalk 2
Awesome....victory is mine....thanks again......XDA is the shiznit!!!!!
Hey Guys -
After being an iPhone fanboy for years, I recently went to Android to try something new. For two months, I've been running Revolution HD (4.3) on my HTC One - but - yesterday decided to give Venom ViperOne a try. I downloaded the latest version, booted to recovery (TWRP) wipred cache, and applied new ROM.
Everything seemed to work great, but after getting many things set up, I found out that I didn't have full root access. When laucnhing SuperSU, it said something like the binaries were not installed, but I finally got that to go away. Re-installing the binary via Recovery didn't fix everything, though.
I installed Root Checker Pro and here is what it said about my phone:
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.69 - 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: -rwxr-xr-x root root 104556 2013-11-17 20:25 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
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 /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
I have tried many suggestions and now have 3 different zip files for SuperSU that I've tried. I'm still researching, but any suggestions would be fantastic... Thanks!
Click build number at setting 7 times until it appear developer option, change root access to app and adb, see if that can solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
Thanks for your reply. Fortunately, I finally fixed it by doing the following:
1. Uninstalled SuperSU via Play Store
2. Downloaded the 1.69 SuperSU update file and installed it through Recovery.
3. Re-installed SuperSU via Play Store
Once I did this, it verified working 100% again in apps as well as passed verification.
Thanks again for your help!
No sweat, Glad you've solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
THANKS!
bzowk said:
Thanks for your reply. Fortunately, I finally fixed it by doing the following:
1. Uninstalled SuperSU via Play Store
2. Downloaded the "" and installed it through Recovery.
3. Re-installed SuperSU via Play Store
Once I did this, it verified working 100% again in apps as well as passed verification.
Thanks again for your help!
Click to expand...
Click to collapse
Thanks man I was stuck with no root access for the longest. This worked!
Su not found
Thanks again for your help![/QUOTE]
Error in tmp/sideload/package.zip (Status 255)
McNaireP said:
Thanks again for your help!
Error in tmp/sideload/package.zip (Status 255)
Click to expand...
Click to collapse
why are you sideloading superSU ?
just copy it to your phone storage and flash it with TWRP /CWM
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
clsA said:
why are you sideloading superSU ?
just copy it to your phone storage and flash it with TWRP /CWM
"1.93"
Click to expand...
Click to collapse
Using CWM to do just that, flash 1.93 update to fix the fact that 'su' disappeared after KDZ update to ICS, trying go back to GB KDZ Stock has me stuck at LG logo. tried re-flashing a number of times...just going around in circles...
pls delete - wrong thread SRY!
azliazmi said:
Click build number at setting 7 times until it appear developer option, change root access to app and adb, see if that can solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
Click to expand...
Click to collapse
You saved my skin. Thanks so much!
Sudo password