I am rooted with S-OFF on the phone. But, unlike the Vibrant, adb denies me su access when I enter "su" at the $ prompt. Anyone else see this?
Once you enter ADB through the SDK tools if I remember right, just start out with the 'su' command- I just caught it a couple days ago in one of the mt4g rom threads under the android development section- maybe a search for 'su' in those threads- I can't take the time to look right now- I'm @ work
Some roms connect by default as Su over adb... if you see a $ your regular user, # is root prompt...
If you have a $ and you get denied still, go to your Su app and confirm that adb has Su permission or at least isn't denied...
Sent from my Desire HD using XDA App
ESKIMOn00b said:
Some roms connect by default as Su over adb... if you see a $ your regular user, # is root prompt...
If you have a $ and you get denied still, go to your Su app and confirm that adb has Su permission or at least isn't denied...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks for the replies so far. ADB is not listed in the su app. How do I add that? Wouldn't it be the daemon that needs root access?
EDIT: Got it. Duh! It would help if I look at the phone while requesting root access. Thanks!
yes it should.... i was wanting you to check that it was not in there with specific permission to deny...
youll need to hit allow on the phone just like any SU call BTW...
Editing my post while you posted. Thanks!
Confused me too the first time.... I got it figured out pretty quick tho....
Give a look at wireless adb its super sweet! Market wireless adb...
Sent from my Desire HD using XDA App
Related
When i try to do a adb remount i get operation not permitted.
It looks like you dunt have superuser
Sent from my DROID2 using Tapatalk
See if your phone is asking to allow superuser permission. It does not stay on screen very long, so just glance at it and see if it pops up and then push the grant permission button.
i got it. i just had to put the bootstap on it.
driverx125 said:
i got it. i just had to put the bootstap on it.
Click to expand...
Click to collapse
Without bootstrap you do not have a constant root adb shell. In order to get root in adb shell, you would have to type su. Bootstrap patches adbd on the phone to allow for a constant root adb shell.
I've got a problem with my Wildfire.
I've rooted it with unrevolked 3, and in Android itself I've got root access for applications, but if I access the phone using ADB and type in su I only get permission denied.
Why does that happen?
Shouldn't a fully rooted phone provide access as su over ADB too?
And why can't I use Titanium to delete the HTC shipped apps, doesn't unrevolked unlock the NAND?
Thanks in advice
ChrBeck
What UID you have on adb shell ?
Use
Code:
adb shell
then
Code:
whoami
the wildfire atm only has full root via recovery, not full root access to the whole phone, soon it will get full root acess when alpharev releases their working patch for the wildfire.
Ok guys thanks for your answers.
I just found out the recovery thing yesterday evening too.
In ClockworkMod I mounted /system.
Then I was able to delete files.
After that I installed Wildpuzzle and now I have full root in the normal system too.
Anyways thanks for your help.
I rooted my wildfire with unrevoked and it worked good. In the shell: whoami
Root
Make sure the terminal is accepted by superuser
Sent from my Milestone using XDA App
And if you use adb from linux you need to setup android.rules add the vendorId, kill adb server, restart then type. /adb devices
Sent from my Milestone using XDA App
OK, I used adb under Linux and of course haven't added the Vendor ID.
So maybe that was my problem, but WildPuzzle is better anyways and doesn't cause these problems.
Has nothing to do with that. If Linux has no defined rules it will not be able to see your device.
http://menodev.com/mobile/debugging-your-android-device-on-linux/
Sent from my Milestone using XDA App
OK, then that wasn't my problem because I was able to see the device and access it, only su in adb wasn't working, but the simple things like cd and ls have been fine.
As far as i recall you need a rooted phone to su in the adb shell
Sent from my Milestone using XDA App
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
You may have to run visionary and reboot a few more times to make root privileges stick.
My MyGlacier 4G MINE!!!
Try this:
: adb shell (this should give $)
:$ su (next line type su, this should give you prompt on Super user to allow permission)
:# ( once you get this your good)
Sent from my HTC Glacier using Tapatalk
Try to install visionary and then re install open click temp root then permoot super user should ask to approve click yes. After that restart
Sent from my HTC Glacier using XDA App
Please post questions in Q&A forum. Thank you
ok everytime i try adb shell in terminal emulator it says the permission denied, im gonna try the first reply again and then see....any other ideas?
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
mrpanic7 said:
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
Click to expand...
Click to collapse
Ok, go into adb shell and type su + enter. Watch your phone when you do this. Superuser should ask if you want to allow "unknown" root privileges. "unknown" is adb. Click allow and your problems should go away.
My MyGlacier 4G MINE!!!
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Whats a test command I could try?
Sent via MyTouch 4G
mrpanic7 said:
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Click to expand...
Click to collapse
I ran into this same issue and it drove me crazy. I would not get prompted by the phone to allow su permissions when going through ADB- kept getting "permission denied"
I did finally get SU permissions through ADB, but I dont recall exactly what I did to get prompted to allow access.
I will try to retrace what I did... believe I had ADB shell running (without su permissions "$"), but I also had terminal emulator running on my phone. I entered the su command on my phone, then I did the same from ADB shell.
Finally the phone prompted me to allow access - accepted - and no problems from that point.
Basically, I just had to keep f'n with it.
Yeah thats my problem exactly. Yeah I appreciate any assistance you can provide. I mean my pc reads my device when I adb devices command, but it wont allow nothing past that. Please keep me informed on anything I can try, also im not thag most fluent with using sdk/adb stuff so any additional info with using that is much appreciated thanks again fellow enthusiasts!
Sent via MyTouch 4G
Have you tried to bacup su, then uninstall su. Reinstall su, Then try it again. MIGHT work
Sent from my HTC Glacier using XDA App
yeah i re-installed su and didnt help, @dbiggs-what can i do thru adb to initiate the su permissions to the device like you did?
I wish I could help more specifically, but I dont remember exactly what I did that allowed me access- just kept trying
Maybe try this...(dont be offended if any of these steps are ones that you already know or have tried, I am just trying to be as thorough as I can from memory)
Open up super user, then go back to the terminal emulator and enter the "su" command to gain superuser permissions.
Plug the phone into the computer, select charge only, enter ADB through tools (probably "C:\Android\tools" if your Android folder is in the root of your harddrive).
from the prompt C:\Android\Tools, enter:
adb shell
then you will get the "$" that you mentioned.
enter the "su" command, and hopefully you will get prompted to allow superuser permissions for ADB.
I am pretty sure these are the steps that I took, just had to keep trying.
Lemme know how it works out.
I see some people here asking about getting su privileges in adb, however I do have SU and I can run su in adb shell. My problem is that I am trying to push some files and use Android Commander. I can't run "adb remount" (remount failed: Operation not permitted), I can't copy files in Android Commander (it's says that I do not have ROOT)
How can I get Read-Write in ADB ??
Edit: Oh, now I got it, I don't have root in ADB, when i type "adb root" it says "adbd cannot run as root in production builds"
Did anyone figure this out? I'm being denied on TE and PC also.
I have managed to be able to get around this issue by going into recovery mode on my phone.
If the end result that you are looking for is to adb push files, then the easier way to do this is to flash clockwork recovery to your phone, then start your phone into recovery mode, mount system and you should be able to push files no problem.
Lemke know if this helps.
Sent from my HTC Glacier using XDA App
mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
I'm pretty sure your issue has nothing to do with SU access. Most likely, your phone is simply mounting as r/o (read only) when it boots up, so ADB is unable to change anything to the system folder. The easiest way to mount as r/w (Read/Write) is to go into Root Explorer and click the r/w button in the top right corner, and then go to ADB and see if it will allow you to do the same commands that it previously denied.
I have the same issue with my phone mounting as r/o by default, but I haven't been able to figure out how to automount as r/w on the MT4G. If anyone knows how, please share.
I had this same issue, on several android phones including MT4G. Here is how I fixed it.
1. Connect phone via usb (I was in "charge only" mode, not disk drive mode)
2. Open command prompt and navigate to the android tools folder
3. type "adb shell"
4. MAKE SURE YOUR PHONE SCREEN IS ON AND UNLOCKED
- The above step is very important otherwise you will not get the SU prompt
5. At the "$" prompt type "su"
6. Your phone should now display the SU screen asking you to allow the connection root access.
7. Once you allow it, you are golden.
I did this on a windows pc. Hope it helps.
ok so i have my phone rooted
I have ADB working right
I go to the terminal in the phone and type "su" and it takes me to the # just fine, also works in ADB (after adb shell).
When i type "free" to see the memory it says "permission denied" on the phone, and in ADB. In ADB, I have tried it from the # which gives me "not found", and then tried it at the $ and that says "permission denied".
I can reboot my phone from ADB, but not in terminal on the phone.
I'm not real sure why i get "permission denied" if my phone is rooted right
any ideas and help would be great thanks
Similar issue Kinda
when I type in 'free' after 'su', I get:
free: not found
It worked just fine for me.
Sent from my HTC Glacier using XDA App
dustrho said:
It worked just fine for me.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
when you rooted your phone .. did you use the visonary temp way .. or the new way thru ADB?
Also those who are or are not having the permission denied...was your root done pre or post update? Mine was post and do you have a recovery flashed?
Sent from my HTC Glacier using XDA App
Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>
zolah said:
Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>
Click to expand...
Click to collapse
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.
Daneshm90 said:
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.
Click to expand...
Click to collapse
I am rooted with superuser...
zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
The default superuser timeout is 10 secs, either increase it or keep looking at your screen.
PS : Have you tried a an app called Mount R/W? works great.
zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"
Daneshm90 said:
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"
Click to expand...
Click to collapse
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...
zolah said:
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...
Click to expand...
Click to collapse
Yes, but by default, if u dont run
adb root....ur not running the shell in root mode
Also on most roms if u run :
adb shel
u'll see $......
when u type su
u see #
So to enter # mode u need root but still need to execute either adb root or adb shell n then su.
Hope that clears it.
install android commander and forget about command line for simple listing and coping tasks
Sent from my GT-I9000 using Tapatalk
This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $
zolah said:
This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $
Click to expand...
Click to collapse
I dont see a # anywhere in there...
Are u accepting the dialog on ur phone when u type su ?
There shud b a popup on ur phone once u do that.
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.
the plot thickens...
Ill fill you guys in from the start in a short story..
Updated to darkyy v9.5 from v9.3
I thought the phone went a bit funny when it loaded the first boot as on the boot animation it vibrated like crazy and the animation started again as it was going to loop but then the phone loaded...
Been using the phone a few days and everything fine and wanted to pull an app from /data/app
All the above stuff happened and it wouldnt let me.
I thought something wasnt right so i took out the battery for a few minutes and put it back in and went into download mode and plugged my phone into computer to see of odin would still recognise it ok...
My windows vista computer started installing device drivers???? ive had this phone 7 months and plugged in about 100,000,000 times lol
Odin recognised my phone so i rebooted and tried again and now it works fine...
Something weird going on there which is concerning me with it installing new drivers...
This is what i get now and used to get before when i used adb...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
FasterFix.apk
Vending.apk
com.adobe.flashplayer-1.apk
com.android.wallpapersetandsave-1.apk
com.darkyrom.darkyconfig-1.apk
com.ebproductions.android.launcher-1.apk
com.google.maps.apk
com.google.youtube.apk
org.projectvoodoo.controlapp-1.apk
circular_battery_indicator.apk
com.androidapps.spareparts.apk
com.haxor-1.apk
com.sgsinfo.apk
com.sgstoolbox.apk
de.Fr4gg0r.SGS.Tools-1.apk
neldar.bln.control.free-1.apk
ymst.android.homeswitcherfroyo-1.apk
com.android.vending-1.apk
com.handcent.nextsms-1.apk
com.keramidas.TitaniumBackup-1.apk
com.pants.sc.lite-1.apk
com.navigon.navigator_select-1.apk
org.adwfreak.launcher-1.apk
com.speedsoftware.rootexplorer-1.apk
com.anddoes.fancywidget.pro-1.apk
adw.creativethemez.gingerbread-1.apk
com.quoord.tapatalkxda.activity-1.apk
c:\AndroidSDK\platform-tools>
Thank you for all the responses by the way...
Any one have any idea what could have happened?
woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
For what i was doing no because i wanted to just quickly pull an apk, decompile it and edit something and compile it and push it back...
Daneshm90 said:
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.
Click to expand...
Click to collapse
I know how to navigate with adb very well. I just couldnt figure out why i was being blocked from entering /data/app...
I even have a video tutorial in my sig that i made showing how to use adb and its commands...
Seems a quick battery pull did the trick although i still now dont know why new drivers where auto installed on reboot to my pc