I'm a bit of a noob here but I think I'm following the instructions correctly.
I've just rooted my device. I opened cmd to check for root acces and this is what it says:
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),
1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002( net_bt),3003(inet),3006(net_bw
_stats)
[email protected]:/ #
I'm presuming that means it's rooted. However when I launch ES Explorer or File Explorer and try to enable root access it says faild:
Root Explorer cannot be enabled
or
Sorry test failed
Any ideas what I'm doing wrong?
I dont know if its a problem with super user, because when it says there should be su request pop up in ES EXplorer it doesnt happen.
When i try to reinstall superuser.apk in cmd i get the following:
C:\Users\AJ\Desktop\Android>adb install Superuser.apk
3585 KB/s (1468798 bytes in 0.400s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\AJ\Desktop\Android>
ajnicho said:
I dont know if its a problem with super user, because when it says there should be su request pop up in ES EXplorer it doesnt happen.
When i try to reinstall superuser.apk in cmd i get the following:
C:\Users\AJ\Desktop\Android>adb install Superuser.apk
3585 KB/s (1468798 bytes in 0.400s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\AJ\Desktop\Android>
Click to expand...
Click to collapse
try es explorer and do it again at the first time it said sorry test failed but when I repeated it, it gave me access. if you have superuser you pretty much are rooted, and if not follow the qemu root process.
Related
I was on v8 non-rooted.
I followed the instructions here to the letter:
http://forum.xda-developers.com/showthread.php?t=1566729&page=4
didn't have any issues at all, no errors.
I'm confirmed on V8 and do have root but can't access CWM. Attempting to run the new AIO again gives the following:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: Read-only file system
7781 KB/s (5345280 bytes in 0.670s)
Unable to chmod /system/xbin/busybox: Read-only file system
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
Any ideas how to get to CWM?
Looks like you need to root again after your upgrade. Run MT's Root&RecoveryAIO.bat again and select the "Root ZV8" option.
[EDIT]
My bad. That's what you are trying to do! I've been up all night and am tired. Did you get any errors when you ran the "Prepare for Update" option before you upgraded? That option actually pushes the superuser files back to your phone and the "Root ZV8" option just goes back and set's the permissions. You can try manually running these commands with adb first.
Files\adb push Files\zergrush /data/local/tmp/zergrush
Files\adb shell "chmod 755 /data/local/tmp/zergrush"
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 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!
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: shell (non root) user - ro.secure=1
Results provided on your DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
clyde1914 said:
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 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!
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: shell (non root) user - ro.secure=1
Results provided on your DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
Click to expand...
Click to collapse
Try rebooting.
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link Here. If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
nobe1976 said:
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
Click to expand...
Click to collapse
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
clyde1914 said:
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
Click to expand...
Click to collapse
I would stick with the HOB just to keep the data. The only route I have found that will successfully re root it is done with Linux. It can be done running Linux on a thumb drive as long as there was space created for updates.
Sent from my XT875 using Xparent Red Tapatalk 2
If that doesn't work and you need restore it to JB, here are the relevant links:
FXZ files for Bionic:
http://forum.xda-developers.com/showthread.php?t=2240725
RSD Lite Example (not for bionic, but gets you some of the links you'll need):
http://forum.xda-developers.com/showthread.php?t=2231249
If you want to try it from linux, fastboot from linux:
http://forum.xda-developers.com/showthread.php?t=1263009&highlight=fxz
And if you need to root once you flash your JB stock image, you'll need something like this:
Easy root:
http://forum.xda-developers.com/showthread.php?t=2256439
So in the [Root 4.4.X] Pie for Motorola devices thread (thanks to jcase) on page 32 (thanks to dubyajaysmith):
http://forum.xda-developers.com/mot...ot-4-4-x-pie-motorola-devices-t2771623/page32
found this gem for Mac users. But I'm an old noob (ran CM on GalaxyS forever using Windows tools) to using adb on Mac. Tried to follow instructions but apparently not getting it right. I can get root (partial) but it doesn't survive "soft reboot" (which I'm not sure which of several methods is correct).
TiBuPro seems to work (sorta). Root Checker Basic says root access.
return from Terminal had a couple fails?:
xx-mbp:~ x$ chmod 700 mxr.sh && ./mxr.sh
5083 KB/s (1538138 bytes in 0.295s)
99 KB/s (192 bytes in 0.001s)
rm failed for /data/local/atvc/blop.asec, No such file or directory
rm failed for /data/local/atvc/blop, No such file or directory
pie by jcase
want to buy me pie? paypal-> [email protected]
Root not retained after “soft reboot” (holding power down for 5 sec - is this correct “soft reboot”?… or reboot from TiBuPro? (nope)… or?)
So did adb ./mxr.sh - returned:
4345 KB/s (1538138 bytes in 0.345s)
28 KB/s (192 bytes in 0.006s)
rm failed for /data/local/atvc/blop.asec, No such file or directory
rm failed for /data/local/atvc/blop, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
After TBP reboot still lost root, adb ./mxr.sh or chmod 700 mxr.sh && ./mxr.sh
again:
platform-tools d$ chmod 700 mxr.sh && ./mxr.sh
4337 KB/s (1538138 bytes in 0.346s)
33 KB/s (192 bytes in 0.005s)
rm failed for /data/local/atvc/blop.asec, No such file or directory
rm failed for /data/local/atvc/blop, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
so again, not doing something right…
Tried installing ChainFire SU & Xposed Framework, tripping at the Xposed Framework Installer's "Install/Update" Framework (using "classical"), does it's thing, cancel "reboot now" and use "soft reboot" (perhaps this isn't the correct "soft reboot"?) which after reboot leaves root disabled again.
So please forgive wall of text, suspect these fails:
rm failed for /data/local/atvc/blop.asec, No such file or directory
rm failed for /data/local/atvc/blop, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
are the "root" (lol, pun) of trouble...
Can anyone help the helpless here? TIA
Samsung S3 i9305 supersu binary problem
Quote:
Originally Posted by cbmk
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
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 **
—------------------------------------------------------
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 extracted SuperSU.zip and tried to copy the .su file to \bin but also didn't work.
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. Any help will be appreciated this is the first time I have rooted.
PS. If this post is in the wrong place please advise where itshould be.
Thanks
S
i just updated and rooted stock android 5.1.1 on my xperia Z1 and ro works for everything but ES file explorer. before the update it was working (on android 5.0.1) but no matter how many times i switch the option on it just does this
asks for root permission, i grant, it switches on for 3 seconds then slides back off saying sorry test failed this feature cant run on your device.
xdarkmario said:
i just updated and rooted stock android 5.1.1 on my xperia Z1 and ro works for everything but ES file explorer. before the update it was working (on android 5.0.1) but no matter how many times i switch the option on it just does this
asks for root permission, i grant, it switches on for 3 seconds then slides back off saying sorry test failed this feature cant run on your device.
Click to expand...
Click to collapse
Did you disable Sony RIC?
xasbo said:
Did you disable Sony RIC?
Click to expand...
Click to collapse
i have never heard of Sony RIC, whats that?
i downloaded some sony RIC killer v2 and used it, this is the output
Code:
=============================================
Getting device variables
=============================================
Device model is C6902
Firmware is 14.6.A.0.368
Checking if device is rooted...
Device rooted.
=============================================
Sending files
=============================================
1870 KB/s (657704 bytes in 0.343s)
52 KB/s (849 bytes in 0.015s)
Copying kernel module...
1077 KB/s (34473 bytes in 0.031s)
51 KB/s (823 bytes in 0.015s)
424 KB/s (13592 bytes in 0.031s)
Kernel version is 3.4.0-perf-g4fd66c3
Version does not match 3.4.0-perf-ge4322cd, needs patching...
dd: conv option disabled
Kernel module patched.
error: only position independent executables (PIE) are supported.
=============================================
Checking for Sony RIC
=============================================
Sony RIC Service found.
Installing RIC kill script installmount.sh...
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error)
mount: Operation not permitted
Stock mount does not exist. Creating dir and link
mkdir failed for /system/bin/stock, Read-only file system
Unable to open /system/bin/stock: No such file or directory
ln: /system/bin/stock/mount: No such file or directory
rm: /system/bin/mount: Read-only file system
cp: /system/bin/mount: Read-only file system
Unable to chmod /system/bin/mount: Read-only file system
Installing of mount.sh finished
Done. You can now unplug your device.
Enjoy SONY RIC KILLER
=============================================
What to do next?
- Modify platform.xml to access SD card without issues.
Press any key to continue . . .
do i need a custom kernel? i dont really feel the need to install a custom kernel if i dont have to.
EDIT SGP621-RICDefeat.zip seems to work, root is working as far as i can see for now
xdarkmario said:
i have never heard of Sony RIC, whats that?
Click to expand...
Click to collapse
The RIC is what prevents you from (normally) making /system read/writeable on the stock kernel. Normally, this is defeated by flashing root and a RIC killer at the same time (e.g., SuperSU + XZDR).
Looks like you've got it sorted.
i have a rooted xperia zr on 5.1.1 with superSU and dual recovery installed but can't get ES explorer to let me use root explorer after providing super user access to the app. can't get sony ric killer to work, either. i'm flat out of ideas.
I've had this issue when i flashed the latest 5.1.1 zip. The solution that worked for me was to flash the kernel with XZDR again. After that the root explorer option in ES file explorer sticks.
Bro, you have to disable Sony RIC