Hi,
Just a little help for me please, I try to launch some adb command with SU
In my little head, I have think translate your code with the SU call before
Code:
adb shell uname -r
become
Code:
adb shell su uname -r
With the first command, all is good I have my answer, with the su first I have
Code:
Permission Denied
I have a DESIRE (bravo) rooted and S-OFF, what did I do wrong ?
The Linux su expects a user name as parameter, not a command. As far as I can see, the Android su simply ignores this parameter. If you want su to execute a command, use the -c option, like in
Code:
su -c uname -r
This causes su to execute "uname -r" as root, after that it returns immediately, so you're back at the user level you've been before. This might not be what you expect, but that's how it works.
Your permission error: Try a single su command, without any arguments or options. If it also returns a permission error, you're not rooted. It should ask you at the mobile's display for permission if you're rooted and you are doing that for the first time.
Thx U dude, U R the one
I'm trying to setup orbot (rooted) but didn't work...
It give me an error: Couldn't start tor process, retrying...
In aLogcat show:
D( 226) setHidden false (KeyguardViewMediator) D( 6828) 10064 org.torproject.android executing 0 /system/bin/sh using shell /system/bin/sh : sh (su) D( 6831) 10064 org.torproject.android executing 0 /system/bin/sh using shell /system/bin/sh : sh (su) D( 6834) 10064 org.torproject.android executing 0 /system/bin/sh using shell /system/bin/sh : sh (su) F( 6838) stack corruption detected: aborted (/data/data/org.torproject.android/app_bin/tor)
and nothing else... that stack corruption detected error show every time that try to run tor.
Ive tried olders version and still... and i saw a guy posting the same error on a moto xoom.
nevermind...
that was a problem with busybox (i had it installed) but somehow wasnt working correctly.
so... busybox update and permission fix will solve it.
Hi!
I just upgraded to 4.4.3 and lost root access. The /system/xbin/su binary is still present, but does nothing:
Code:
[email protected]:/ $ which su
/system/xbin/su
[email protected]:/ $ ls -l /system/xbin/su
-rwsr-sr-x root shell 104576 2013-12-13 19:17 su
[email protected]:/ $ su
1|[email protected]:/ $ whoami
whoami: unknown uid 2000
I booted into fast boot mode. The information there says (if it is of any help):
Code:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - XXX
SIGNING - not defined yet
LOCK STATE - UNLOCKED
And I can't seem to boot into recovery mode - it just shows "android" lying on his back with his tummy open with a red triangle (with exclamation mark) .
I guess the 4.3 update changed some stuff. I'm on a Mac. What can I do to regain root access?
Regards,
Miha.
Further to that, I stupidly also accepted the update - CWM seems to have been wiped, and when I try to flash it, I get the following error. The weird (and gratifying) thing is that other than that, the tablet seems to operating fine - for which I'm grateful - is there anything I can try to sort it out?
I was completely stock (but rooted with CWM 6.0.4.3).
Code:
goatees-MacBook-Air:platform-tools goatee$ fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_read failed with status e00002ed
ERROR: usb_read failed with status e000404f
sending 'recovery' (7318 KB)...
ERROR: usb_read failed with status e000404f
FAILED (status read failed (No such file or directory))
finished. total time: 3.057s
mihaval said:
Hi!
I just upgraded to 4.4.3 and lost root access. The /system/xbin/su binary is still present, but does nothing:
Code:
[email protected]:/ $ which su
/system/xbin/su
[email protected]:/ $ ls -l /system/xbin/su
-rwsr-sr-x root shell 104576 2013-12-13 19:17 su
[email protected]:/ $ su
1|[email protected]:/ $ whoami
whoami: unknown uid 2000
I guess the 4.3 update changed some stuff. I'm on a Mac. What can I do to regain root access?
Regards,
Miha.
Click to expand...
Click to collapse
Ok, so I've resolved my problem. I don't know if it's coincidence, but this time when I tried to reflash cwm
Instead of doing
Code:
fastboot flash recovery recovery-blah-grouper.img
I did this - and it worked
Code:
./fastboot flash recovery recovery-blah-grouper.img
This time, it flashed successfully, which let me reinstall root (by flashing the Super SU .zip)
I'm in OS X, (used *nix for the past 18 years or so), and it was successfully starting the fastboot binary before - so perhaps it's just a coincidence. The only other thing I did different was that my USB keyboard wasn't plugged in.
---------- Post added at 09:14 PM ---------- Previous post was at 09:06 PM ----------
And in fact, if that doesn't work for you - towelroot should do the job. See http://forum.xda-developers.com/showthread.php?t=2783157 or http://www.towelroot.com
goatee said:
Ok, so I've resolved my problem. I don't know if it's coincidence, but this time when I tried to reflash cwm
Click to expand...
Click to collapse
I confirm that it works for me too. CWM asked me whether to fix su: "Possible root access lost. Fix su?" and I chose yes (the first time and now, when I reflashed recovery too). And that actually breaks it. On second run, I chose no, and su is working again.
I saw reports about 4.4.4 update coming - we'll what that brings us...
Miha
Ah. . . I wonder why the SWM root fix didn't work correctly. Anyhow, glad you're also back to normal .
mihaval said:
I confirm that it works for me too. CWM asked me whether to fix su: "Possible root access lost. Fix su?" and I chose yes (the first time and now, when I reflashed recovery too). And that actually breaks it. On second run, I chose no, and su is working again.
I saw reports about 4.4.4 update coming - we'll what that brings us...
Miha
Click to expand...
Click to collapse
Hi all,
I tried to identify partitions on the device (userdata, vendor, system, etc.)
Device: Oneplus2 (unrooted).
After
Code:
adb shell
ls -l /dev/block/by-name
It returns
Code:
/dev/block/by-name: Permission denied
I also tried
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The same result followed.
So
1. How to solve this "permission denied" problem?
2. Would it nevertheless be possible identify partitions on an unrooted device?
Thanks in advance.
Cheers,
Wen
I followed this tutorial: https://forum.xda-developers.com/t/root-tutorial-for-alps-8227l-demo-looking-for-feedback.4197561/
And when issuing commands via adb on windows, I get:
8227L_demo:/ $ su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
/system/bin/sh: su: not found
I then tried to run adb root and I got:
c:\adb>adb root
adbd cannot run as root in production builds
the su file is already located in the adb directory so I'm not sure how to fix this error.