Cannot Get Root Access After New ROM Installed - AT&T HTC One (M7)

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

Related

[Q] error with [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0

i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
ramongarza said:
i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
Click to expand...
Click to collapse
could you list what rom you were on and what steps you took to flash cm7.1 please?
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
ramongarza said:
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
Click to expand...
Click to collapse
what recovery did you use to flash cm7?
Clockworkmod then later I tried rom manager. Does that answer your question?
Sent from my SCH-I500 using XDA App
follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1212239
i loaded the Rom thank you so much man!
Got CWM installed, and CM7 installed and running. superuser is there, but doesn't show any apps yet.
I installed titanium Backup and ran it, but get this error:
Sorry, I could not acquire root privileges. This application will *not* work! etc etc..
It mentioned verifying that busybox was installed, so I went to the market and downloaded the one by jrummy16, tried to run it, but it errors out - no root access.
Then I tried the one by stephen - same issue.
superuser v3.0.5 (39) is installed. It auto-updated to that immediately after the first full boot on CM7 with the market installed.
EDIT -
I uninstalled the superuser update, but still have the same issue. Downloaded rootchecker from the market, here is the output:
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as root
Standard su binary location: ls -l /system/bin/su:
ls: /system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location:
ls: /sbin/su: Permission denied
Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SCH-I500 device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae

[Q] Rooted Vibrant issues

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.

[Q] Unlocked bootloader, s-on, not rooted HELP!!!!

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!!!!!

[Q] Kyocera Rise Root Issue

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

[Q] How to manually reroot after problem with SuperSU?

I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?

Categories

Resources