Related
is it possible to give an app SU access without it asking for it? I love Linda's File Manager and want to be able to access my phone through it and modify accordingly.
Once u have Superuser.apk installed, (you can search for it on the forum) it will ask for su permissions the first time you run a program that needs it, and you can tell it to "Always Allow" so it doesn't keep asking. This is the best way to do it IMO. I have not used Linda File Manager so I'm not sure it has support for root use. If not then it might be possible to chmod the .apk from the terminal. Sorry, I'm a little Linux rusty...
Aloha-
LFM will let me read and copy the files and even has the ability to delete files, however due to the fact that it never asks the su.apk for permission, it never gets it and just tells em it can't do it.
Just use terminal to copy.remove files. Itls easier anyway.
I rooted following the 10 minute root video, however forgot to remove a lot of those junk system apps, like CityID. I cannot get back into SU while in recovery, no matter what I do. How do I get back into the shell in recovery so I can remove all the bloatware?
I can get the error message:
- exec '/system/bin/sh' failed: No such file or directory
however i cannot seem to get back into the shell where I can access SU and remove the bloatware, anyone have any ideas on what im missing?
areghas said:
I can get the error message:
- exec '/system/bin/sh' failed: No such file or directory
however i cannot seem to get back into the shell where I can access SU and remove the bloatware, anyone have any ideas on what im missing?
Click to expand...
Click to collapse
I'm in the exact same boat as you. I don't know where to go from here.
run update.zip and let it fail again then you caN adb shell su
hmm doesnt seem to work for me
in order to get the back to adb shell in recovery, you have to go through the whole root process again. Then once you have snuck in the payload-update.zip and it has successfully installed it, you are able to do adb shell.
i had to run do the hole process over again to get su so i could remove cityid after root.
i used the 1.bat file as in the utube video for noobs.
ejlax said:
in order to get the back to adb shell in recovery, you have to go through the whole root process again. Then once you have snuck in the payload-update.zip and it has successfully installed it, you are able to do adb shell.
Click to expand...
Click to collapse
not cool lol, took me 3 hours to get the things to work with my sd card haha not worth it.
that is the only way
They are correct, you must do it all again, but look for a PNY 4gig class 4 sd. I tried hundreds of times over a 3 day period to do it and it worked first time and every time with this card.
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
There is also another terminal app in the market for 1.99, listed as being for that purpose, so, has anyone tried it?
I don't have anything else I want to delete at the moment, since I got rid of cityid at the recovery adb prompt.
qwho said:
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
There is also another terminal app in the market for 1.99, listed as being for that purpose, so, has anyone tried it?
I don't have anything else I want to delete at the moment, since I got rid of cityid at the recovery adb prompt.
Click to expand...
Click to collapse
The nand is locked down when you are in the main OS, so no, it would not work. You would need to do the re-root to gain access to /system/ as recovery is the only place where we are able to access it right now.
qwho said:
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
Click to expand...
Click to collapse
E30kid said:
The nand is locked down when you are in the main OS, so no, it would not work. You would need to do the re-root to gain access to /system/ as recovery is the only place where we are able to access it right now.
Click to expand...
Click to collapse
I can get su access while in the OS. No problem on that. And I tried to delete teeter.apk, but got the "read only" message. So, I mounted it as read-write with
Code:
/system/bin/mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
that went fine too, but when I tried to delete teeter.apk, i got "rm failed, directory not empty"... but I'm not trying to delete a directory...
I guess the "nand is locked" and that's why, but... "the nand is locked" doesn't mean much to me, as I have no clue what that means
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.
I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
BR3W CITY said:
I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
Click to expand...
Click to collapse
To test that you are infact rooted, please do the following:
1. Open command prompt/shell
2. cd into your AndroidSDK directory
3. Issue the command:: adb shell (if you see the # mark, then you are rooted -- otherwise type, su.)
To answer your questions:
1. When your phone says its "read-only file system"; this means that you need to issue the adb remount command; this will remount the system as RW (read/write), at which point you can go on deleting any apps you no longer want.
2. If you still have S-ON, that means you did not run the Unrevoked FOREVER file. You've only ran the Unrevoked 3 file. Notice when going to the Unrevoked site, that there are two different downloads.
3. Clockworkmod/superuser will exist because you are rooted and the process was successful.
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
n/m, didn't read previous post properly
BR3W CITY said:
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
Click to expand...
Click to collapse
What kind of phone? Some phones won't reliably mount the system partition read-write while running in normal mode. You should be able to do it from the clockwork recovery system though.
htc desire on 2.1, from USCC. I have not yet tried to do it from clockwork yet. I will try that later
Thanks!
Thanks for the help, putting her into ClockwordMod and using it to Mount /system solved the problem. Stock crap is gone yay!
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
It is present on my phone.
Do you need me to upload it for you?
Yes please! That might fix my problem! For some reason I dont have it and I think that is why my phone is seen by my computer but is always offline. Hopefully this will work!
Sent from my MB860 using Tapatalk
Anyone that has the adbd service in /sbin/adbd, could you please upload it here for me. I would really appreciate it!
Sent from my MB860 using Tapatalk
here you go.
unzip and that's it. the file has no extension.
Let me know if this solved the ADB problem
Thanks a lot, I will let you know how it goes. Hopefully it works.
Sent from my MB860 using Tapatalk
clubtech said:
here you go.
unzip and that's it. the file has no extension.
Let me know if this solved the ADB problem
Click to expand...
Click to collapse
Holy crap, it worked!!! My device is not offline any more and adb is working!! For four days now I have been trying to figure this out. Thank you for the file!!
One weird thing though, after a reboot the file is gone and I have to copy it over to /sbin again to get it working. Now I need to figure out why it gets removed on a reboot. Anyone have any ideas?
airbillion said:
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
Click to expand...
Click to collapse
It gets removed because the ramdisk extracts it to that directory on boot
designgears said:
It gets removed because the ramdisk extracts it to that directory on boot
Click to expand...
Click to collapse
Is there a way to keep it in /sbin permanently? I think this is why early usb enumeration does not work for me.
Can I install your deodexed rom? I am nervous because I cant get the early usb enumeration working when the adbd file gets removed on reboot. Does the deodexed rom do anything requiring adb on the shutdown or reboot? Would I be ok without the adbd service until I reboot and replace the file?
airbillion said:
Is there a way to keep it in /sbin permanently? I think this is why early usb enumeration does not work for me.
Can I install your deodexed rom? I am nervous because I cant get the early usb enumeration working when the adbd file gets removed on reboot. Does the deodexed rom do anything requiring adb on the shutdown or reboot? Would I be ok without the adbd service until I reboot and replace the file?
Click to expand...
Click to collapse
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
clubtech said:
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
Click to expand...
Click to collapse
Yes a bunch: acpi_available, alsactl, apm_available, badblocks, blkid, blockdev.....vol_id. There are about 40 files, but the adbd seems to disappear after a reboot and my early usb enumeration does not work. I think it is because it adbd gets removed on a reboot. Is there a way to keep it in there after a reboot that you know of or to get usb early enumeration working?
not sure about a fix but as a work around, in theory you can try to create a script that runs on boot that always pushes the adbd file back into the /sbin folder. you can use a combination of programs like gscript to create the script and then a program like tasker to executive the script on boot or some other type of autostart program.
NguyenHuu said:
not sure about a fix but as a work around, in theory you can try to create a script that runs on boot that always pushes the adbd file back into the /sbin folder. you can use a combination of programs like gscript to create the script and then a program like tasker to executive the script on boot or some other type of autostart program.
Click to expand...
Click to collapse
Thanks, i will look into this.
What about adding it in then changing permissions on it to disable the system from deleting it?
Sent from my SAMSUNG-SGH-I897 using XDA App
Changing your adbd permissions back to stock may help, as the file in the .zip won't have the proper permissions. Do this:
Code:
chmod 0750 /sbin/adbd
The one in the zip will be 0777, which gives everyone read and write access, which isn't set normally.
Atrix ADB offline issue
clubtech said:
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
Click to expand...
Click to collapse
I have the same problem! Any solutions found?
How do it get this onto a phone that is not rooted, so that I can root it?
Thanks.
Atrix Rooted Deodexed ADB Offine Issue
When I received my Atrix I used the program superoneclick to root the atrix and then Fully Deodexed, i enabled the sideloading of apps with the same program.
I then went to my external sd card where I had saved the apk's for titanium backup and adfree and installed them without any issues.Over the next few days I used my phone without any problems at all.I had some apk's on my computer that i wanted to push to my atrix so i tried to connect via adb and my phone was seen as offline no matter what computer, usb port or cable I used.I then thought that a hard reset might solve the issue so I went to the recovery menu and performed a system restore.This did not fix the problem.For days I tried to figure out how to fix it, until I realized that the adbd service in /sbins was missing so i got a copy and placed it in /sbins and adb worked again. However, after a reboot the adbd file is removed from /sbin and to get adb working again I have to place my copy of the adbd service back into the folder.The problem now though is that early usb enumeration in the recovery does not enable adb, the phone just boots normally after about 5 seconds.Thank you for your help and interest in my problem.Mroadster
airbillion said:
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
Click to expand...
Click to collapse
I really wish I could tell you how I did it, but I was going through this very same issue with loss of ADB after doing the SuperOneClick with a subsequent reset. After resetting the device I was not able to obtain ADB.
I got to a point where I decided I was going to just get rid of root and try to remove Superuser however every time I ran the script to remove it, it was still there. The script was running but no connection to ADB resulted in no execution.
I reset the device a couple more times and uninstalled all Motorola drivers from my computer. When I went through the initial setup and driver install again, it installed all the drivers like normal including the ADB communication. I confirmed ADB via "adb devices" and I everything seemed good to go.
I then used DG's aRoot to root once again without any issues at all. Every time I attempt to use ADB, it now connects flawlessly.
I have this problem as well and it is driving me insane as I bit off more than I could chew just trying to root my phone... Hopefully we can figure something out in the future.