Database Info

[Q] Terminal Emulator - Permission denied

Hello!
I don't know how to pass this problem. I have downloaded superuser app but it was futile.
TE can install aps from .apk? And other files management?
Sent from my Nexus S using XDA App

Kalimdor said:
Hello!
I don't know how to pass this problem. I have downloaded superuser app but it was futile.
TE can install aps from .apk? And other files management?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did you root your phone? The superuser app relies on the su binary being installed, in other words, just downloading superuser from the market doesn't root you.
Then, in the terminal emulator app, many commands require you to type "su" to enable the terminal to have root access.

To root I have used this topic :
http://forum.xda-developers.com/showthread.php?t=927838
So I can manage my phone from google SDK adb command line but from Terminal emulator I can't.
Now superuser app is asking me to : 'A zip filr (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary' ...

Well...the superboot method shouldn't need you to install su, it's supposed to do it for you.
The message you're getting is telling you to boot into recovery and install that zip. I don't know if it will flash from the stock recovery, but it will certainly flash from clockwork recovery if you boot into clockwork.

Key I will try from clockw. Stock found problem with certificates.

How to fix this SuperSU problem?

“There is no SU binary installed, and SuperSU cannot install it.”
When open supersu, it show some error.
I use "[ROM][JB][4.1.1] Remics-JB - SIII Feel on Jelly Bean! [V2.0.0 is NOW ONLINE!!]"

did you root your phone first?

Download the SU binary from the rom thread, overwrite your current SU binary using root explorer or whatever. That's probably the easiest fix without getting into too much detail.

Issue with version of su files

Hello,
I update my asus last week but i forgot that i have install root in April to do some stuff during this time...
so i 'm not any more root i reinstall today motochopper to have last version of root install spent well.
but when i launch super user it told me that the binary su is not updated.
So i will move the su present in motochopper.zip to sbin/system,,, but i can't because
adb shell tell me permission denied and when i enter "su" i have always $ and not the # ...
So i'm a little lost how to delete the old file su in sbin and put the newest .. i test "mount -o rw,remount ...
but nothing works always issue with permission.
android v4.2.1
kernel : 3.1.10-g89b05a
build : JIP40D
Thanks a lot
Best Regards

reikanou said:
Hello,
I update my asus last week but i forgot that i have install root in April to do some stuff during this time...
so i 'm not any more root i reinstall today motochopper to have last version of root install spent well.
but when i launch super user it told me that the binary su is not updated.
So i will move the su present in motochopper.zip to sbin/system,,, but i can't because
adb shell tell me permission denied and when i enter "su" i have always $ and not the # ...
So i'm a little lost how to delete the old file su in sbin and put the newest .. i test "mount -o rw,remount ...
but nothing works always issue with permission.
android v4.2.1
kernel : 3.1.10-g89b05a
build : JIP40D
Thanks a lot
Best Regards
Click to expand...
Click to collapse
Hi, i am a new tf300t user. It seems that nobody can root latest stock 4.2 with motochopper and i read that all failed with rootkeeper as well. I bought my tf a week ago and it was with the latest update, so i coundt root it. I downloaded from asus website the previous stock firmware (V10.6.1.15.3 for WW SKU which is my tablet), extracted it to internal and i got a notification for downgrade. I did it and 10 min later i rooted with motochopper. Then i opened su and updated binaries. Installed voodoo ota rootkeeper, backed up root and temporarly unrooted. I then updated again via OTA notification (only 50mb) to latest fw and i ota rootkeeper managed to restore root successfully. So im on latest with root access.

H,
Thanks for you reply i will try this and if it doesn't work i forgot root it was just to recover a file and application to recover need to be root.
Thanks again.
Bregards

[Q] Loaded Clockworkmod Superuser Update - Lost Root - Note N7000

Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?

Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.

I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.

new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...

how to fix there are no su binary and superuser couldn't install them this is a probl

Hi today I tell you how to fix super su problem
To fix we need to install the latest version of busybox
Next we need to install vroot and root the device..
Notice: we have to open busybox befor root the device
And your device now rooted!