while in terminal when i type su im getting error message:
tldTLD: permission denied
tldTLD: permission denied
ermission denied
NM~DqYL: permission denied
su: 5: Syntax error: "C" unexpected
$
now i went to my su permission and i saw a message of an update available and i did update the binaries rebooted but still the same problem. anyone help please. i mean i could always re-root right?
Sent from my HERO200 using XDA App
danielt021 said:
while in terminal when i type su im getting error message:
tldTLD: permission denied
tldTLD: permission denied
ermission denied
NM~DqYL: permission denied
su: 5: Syntax error: "C" unexpected
$
now i went to my su permission and i saw a message of an update available and i did update the binaries rebooted but still the same problem. anyone help please. i mean i could always re-root right?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
not sure I understand. If your in the terminal emulator and just type su what does it say?
danielt021 said:
ermission denied
Click to expand...
Click to collapse
Your terminal actually outputs a smiley with its tongue sticking out? J/k, sarcasm.
Have you tried deleting the terminal from the permissions list of your SU app? Then just re-add it next time you use it, since your SU app is a new version. Maybe it just needs to be re-added properly to the SU app.
Or if that doesn't work, try deleting the whole terminal app, then rebooting, then reinstalling it from the market.
Also try a dalvik wipe in recovery if none of the above work.
ASimmons said:
not sure I understand. If your in the terminal emulator and just type su what does it say?
Click to expand...
Click to collapse
and unless your like 6 years old its not I LOST its I LOSE.
And sounds like you dont have root since its saying permission denied. That is what it says when you type in SU right?
t12icky0 said:
and unless your like 6 years old its not I LOST its I LOSE.
And sounds like you dont have root since its saying permission denied. That is what it says when you type in SU right?
Click to expand...
Click to collapse
not sure why you quoted me but permission denied is what you get for about any command the terms doesn't understand, it looks like he type tldTLD: and got back perm denied. Not everyone here speaks "american" as there first language.
when i try to wipe dalvik it says that i need to do it thru adb, ....how? do i just enter adb wipe dalvik or something like that
Sent from my HERO200 using XDA App
danielt021 said:
when i try to wipe dalvik it says that i need to do it thru adb, ....how? do i just enter adb wipe dalvik or something like that
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
If you are running Recovery v1.5.2, then it actually does wipe dalvik even though it gives you that error. It's simply an output error that returns the wrong string of text after the operation is done...but it DOES actually wipe your dalvik even though it seems like it doesn't.
If you want, you can update your recovery to a newer one where that output error is fixed, but I still use v1.5.2 and have no problems whatsoever.
t12icky0 said:
and unless your like 6 years old its not I LOST its I LOSE.
Click to expand...
Click to collapse
And unless you are 6 years old, it's not YOUR, it is YOU'RE.
It sounds like you lost your ability to use proper english grammar. Jokes aside, just type in su in a shell, and if a "#" sign appears, you "got root"
stayclean said:
And unless you are 6 years old, it's not YOUR, it is YOU'RE.
Click to expand...
Click to collapse
lol... English Nazi fail.
Related
Hi, I am on Darchdroid 2.7 and while I was trying to push Camera.apk to my phone I kept getting the "read only file system" message. I did not know at the time that the first thing I should've done was "adb shell" followed by "su" to make sure adb got onto the superuser whitelist.
Well, i proceeded to read around the net (here)and I used this command I saw around to get root:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
Click to expand...
Click to collapse
And it worked, I was able to push the Camera.apk.
Now i have a problem though, when I use an app that requires root, it no longer brings up the superuser whitelist app even if I've chosen to forget them from the whitelist.
Titanium backup gives the following message:
Warning -
BusyBox works but the "su" command does not elevate to root: "whoami" reports "app_47" instead of root/uid 0. I think your "Superuser Whitelist" system app does not work. Please check with your ROM provider.
Click to expand...
Click to collapse
I searched around the net and I actually found a post regarding this from the dev behind Titanium Backup saying that if this message shows up, it means that the app is not properly communicating with the superuser whitelist....
Now, I believe that the commands I put in adb previously did away with the superuser whitelist and just gave root to whatever app asks for it, I don't know if I am correct.
Can anyone verify this? If so, is there a way to undo what I did? ..or will reflashing Darchdroid be my best option?
I really dont want to flash, I just got this rom settled in :\
Thanks in advance!
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
Do you have the "superuser" app on your phone?
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
TheRomero09 said:
Do you have the "superuser" app on your phone?
Click to expand...
Click to collapse
Yes, I have it on my phone
miztaken1312 said:
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
Click to expand...
Click to collapse
I have the app on my phone, but when I try this, I do not get a prompt for super user permissions, and the CL shell returns permission denied
EDIT: I was going to look at the superuser app to see what was in it to give you more info, but it the "app" that I assume is actually my computer had denied permissions. After changing it back to allow, the shell returns
Code:
su
#
I have cm6.1 on my phone i recently flashed the uncapped kernel and then i flashed the battery tweek then i went to the termial emulater to finish the battery tweeking and after i type in su it says permission denied so i contiued and type batt-cfg and it told me to press enter to try i root or 1 then enter to continue normally. i tryed just hiting enter and it said access denied so i try 1 then entered and it told me i wasn't rooted. so i launched astro and tryed to reroot my phone and it said failed. then i tryed unrooting my phone and it said failed that i am still all powerful ;; can anyone help?
Bondue said:
I have cm6.1 on my phone i recently flashed the uncapped kernel and then i flashed the battery tweek then i went to the termial emulater to finish the battery tweeking and after i type in su it says permission denied so i contiued and type batt-cfg and it told me to press enter to try i root or 1 then enter to continue normally. i tryed just hiting enter and it said access denied so i try 1 then entered and it told me i wasn't rooted. so i launched astro and tryed to reroot my phone and it said failed. then i tryed unrooting my phone and it said failed that i am still all powerful ;; can anyone help?
Click to expand...
Click to collapse
If your getting permission denied and your running cm6 thats very strange. Go into the app superuser and see what all is in there. You might have accidently denied permissions to it somewhere along the line.
Might have to reinstall SU, you can't be unrooted and still running CM..
SU had it allowed so i'll try to redo SU
okay redownloaded SU from market abd installed but no change it still says permission denied and it doesn't prompt to allow through SU.
Help
Sent from my HERO200 using XDA App
I think your phone is missing the SU framework. Do this: http://forum.xda-developers.com/showpost.php?p=9057544&postcount=1949.
That worked thank you very much
Sent from my HERO200 using XDA App
Rooted my hero 2.1 and when I try to $ su , I get "must be suid to work properly". I've not ran into this before, What needs to be done to fix this ? thanks.
dude what are you talking about when u root u have super user aka su
Bierce22 said:
dude what are you talking about when u root u have super user aka su
Click to expand...
Click to collapse
Yea, you'd think that would'nt you.. When I run Regs "root me" , It tells me I'm already rooted, but when I try the command, $ su , I get the above message..or permission denied..
Houndog101 said:
Yea, you'd think that would'nt you.. When I run Regs "root me" , It tells me I'm already rooted, but when I try the command, $ su , I get the above message..or permission denied..
Click to expand...
Click to collapse
Also, I see # from adb shell command, but the phone thinks its not rooted. What up with that. If I try to install busybox it says " No root access" , rom manager the same thing...all I want to do is install a recovery so I can get off the stock rom..
Have you tried something as simple as updating su in the play store and trying? If not, try flashing an HERCIMG recovery through hboot.
Sent from my PC36100 using xda premium
anthony_s said:
Have you tried something as simple as updating su in the play store and trying? If not, try flashing an HERCIMG recovery through hboot.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Yes and Yes, Niether worked,, thanks tho.
Have you tried updating the su binary from within the su app itself?
Sent from my PC36100 using xda premium
Yes, that worked, thanks.
Houndog101 said:
Rooted my hero 2.1 and when I try to $ su , I get "must be suid to work properly". I've not ran into this before, What needs to be done to fix this ? thanks.
Click to expand...
Click to collapse
Old old thread but if someone encounters this again, it is due to busybox SU not having the correct permissions and can be corrected easily.
I got the info from here: ttp://forum.nas-forum.org/index.php?page=Thread&threadID=526
Quoted from that page:
Code:
su: must be suid to work properly
I finally discovered that /bin/busybox which provides su (and in fact almost all commands) has not its set UID , i.e. the unix rights are
Code:
rwxr-xr-x instead of rwsr-xr-x
i could finally change the rights with
Code:
chmod 4755 /bin/busybox
and su works fine again
Click to expand...
Click to collapse
Just thought I would share since I saw this on my synology NAS and it pretty much directly applies to this issue from an age ago.
yes, you need to su in order to make it work as administrator.
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
The Magician Type 0 said:
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Has anyone try to format the entire phone, and then fast boot back?
Someone mentioned trying that, but I never heard the results.
Sent from my DROID4 using Tapatalk 2
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
It's almost like Motorola has us all figured out! This and the unrootable Atrix HD... I think we just have to get better. I'm sure there is a root check somewhere in nvram or something
Sent from my Nexus 7 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Whoa. I mean, it probably just writes a value somewhere we can't touch (yet?), but still.
repeated shell auto-granted permissions
fade_to_red said:
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
Click to expand...
Click to collapse
highlandsun said:
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Morlok8k said:
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
Click to expand...
Click to collapse
After doing this, here is what i did in a terminal emulator:
Code:
su
mount -o remount,rw /system
chmod 644 /system/bin/dumpstate
i had to do the "644" instead of "a-x" because i kept getting an error message "Bad mode 10|"
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file??
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file???
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
It's /system/bin/dumpstate not /sys/bin/dumpstate
removing execute permissions does not do anything.
Should I or shouldn't I?
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
supraket said:
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
Click to expand...
Click to collapse
I say.....
You should:
unlock tether, free apps, better phone, harder to replace if something goes wrong (worth it to me)
You shouldn't:
warranty risk, stock performance, easy replacement
je2854 said:
removing execute permissions does not do anything.
Click to expand...
Click to collapse
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
intellitek said:
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
Click to expand...
Click to collapse
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
je2854 said:
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
Click to expand...
Click to collapse
Okay, well, let's say, hypothetically-speaking, somebody was willing to experiment with this.
When exactly does this "rootchecker" run? I guess I'd need to rename/replace it before it runs, but after I've rooted. Or somehow before, although I believe that's currently not possible. I'll try and see if the bin is signed.. not sure how to check if it's actually verifying it on exec, though, without rooting.
EDIT: Nevermind, it looks like it's built into the boot and recovery .img files?