So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.
Also in the How To:
StirCwazy said:
So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=709220 - It's a few posts down, but will update first post later today.
Related
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 all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...
Shadowmite said:
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...
Click to expand...
Click to collapse
So all is good?
Yes....all is good. Reported.
I'm not issuing warnings yet for questions posted in development which may fall under that scope. I have requested a Q&A sub-forum be created for DI. We'll see how that pans out. Until then, please post questions in the thread where you believe your issue is coming from. Otherwise, please post questions in the DI/General sub-forum until a Q&A forum is created. Thanks!
ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
i have that problem right now. i have the original root(via loop.bat) in place, nothing else. i get the symbol "~#" too when i try to enter the adb shell while in recovery. adb devices show that my phone is attached and i am able to execute most commands. but there are some commands like "cd" that only work in the shell.
so we are going to need to resolve this eventually.
yes, you do not need su in recovery but you will need adb shell.
if there's anyone out there who can help us with this "~#" when typing adb shell in recovery, it would be greatly appreciated.
If you see that then that means you are using adb shell. No need for Su, but if you're removing apps etc mount the /system in the partitions menu of clockworkmod. Then cd /system/app to edit your apps.
Sent from my ADR6300 using XDA App
Hi I have been trying all evening to remove com.wsandroid.apk from my phone, using terminal but I simply cannot. I've tried many different commands and I'm just being told either permission denied, directory not found/not empty. I have a Wildfire which is obviously rooted. Please help me out, tearing my hair out here.
So you're using modaco custom rom?
Download the latest version of HTC Sync and install. This will also install the adb drivers. (I presume you use windows, if not, I apologise)
Download the Android SDK
Put the phone in fastboot mode (Power+Volume down) and plug it into your computer.
When the drivers are installed, use the command prompt to navigate to the tools folder within the android sdk folder.
Type the following commands, pressing enter at the end of each line:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
cd app
rm -r com.wsandroid.apk
That should do it
I'm using the stock ROM but it is rooted with Unrevoked. I'll try these instructions anyway.
- Connect your phone to the PC
- Clear WaveScure's cache on the phone
- Open a command prompt
- go to run go to C:\androidSDK\tools and then run these 2 commands
1. adb remount
2. adb shell rm /system/app/*wsandroid*
Click to expand...
Click to collapse
I'm trying these settings, but when I get to adb remount, I get this error: remount failed: Operation not permitted
EDIT: I put the phone into recovery mode and mounted it and it said remount succeeded, I then followed step 2. both *wsandroid* and com.wsandroid.apk and it says that they cannot be found.
EDIT: Nevermind, deleted it
There's currently no write access to system partition using Unrevoked on Wildfire. So you can't remove it. You flashed it with update.zip? I'm not an expert (yet) but I assume the only way (or easiest way) to remove it is to flash your stock ROM again.
--- I posted to general by accident, meant to do Q&A, but don't have permission to delete as a new user. --
--- Please see the question in Q&A ---
Greetings,
I'm new here, and can't get over to the developers forums to ask. I have two GT-I9500s for development purposes, one if full of junk, and the other is still stock, except for recovery. They both have CWM Recovery v6.0.3.2, the latest available pre-compiled I've found. The stock phone has only been booted once. That system is not rooted (and this is my whole point, I want as close to stock as possible)
I am attempting to extract the system image from Stock I9500. I have booted into CWM Recovery mode, then "adb shell" into the device. All commands I issue to the shell return "Permission Denied"
Code:
:$ adb shell
~ $ ls
/sbin/sh: ls: Permission denied
~ $ dd of=/storage/extSdCard/SYSTEM.img if=/dev/block/mmcblk0p20 bs=4069
/sbin/sh: dd: Permission denied
~ $ su
/sbin/sh: su: Permission denied
~ $ sudo su
/sbin/sh: sudo: Permission denied
I have tried to use Advanced->Fix Permissions to no avail.
CWM is pure and latest from www dot clockworkmod dot com slash rommanager (new users apparently cannot post links). CWM is able successfully operate "Backup to External" from the stock device.
The end goal is to clone the clean, stock device onto the other one. CWM claims success on "Restore from External" to the other device, but it sits on the "Samsung" loading screen forever.
A solution to either or both of these problems would be appreciated.
-MM
same issue
I have the same issue. I first also didn't adb shell available. But I fixed it in recovery mode by doing mount /system. However, now like you I have no permissions at all. I'm considering doing a factory reset, but that's gonna be my final resort. I first go looking for other ways to come around it.
ansjovis86 said:
I have the same issue. I first also didn't adb shell available. But I fixed it in recovery mode by doing mount /system. However, now like you I have no permissions at all. I'm considering doing a factory reset, but that's gonna be my final resort. I first go looking for other ways to come around it.
Click to expand...
Click to collapse
You need to allow your pc first to use adb. Boot into android, use adb and press allow. After that you can use adb in recovery. If it still fails, then try a different recovery. Philz or TWRP.
Greetings,
I'm new here, and can't get over to the developers forums to ask. I have two GT-I9500s for development purposes, one if full of junk, and the other is still stock, except for recovery. They both have CWM Recovery v6.0.3.2, the latest available pre-compiled I've found. The stock phone has only been booted once. That system is not rooted (and this is my whole point, I want as close to stock as possible)
I am attempting to extract the system image from Stock I9500. I have booted into CWM Recovery mode, then "adb shell" into the device. All commands I issue to the shell return "Permission Denied"
Code:
:$ adb shell
~ $ ls
/sbin/sh: ls: Permission denied
~ $ dd of=/storage/extSdCard/SYSTEM.img if=/dev/block/mmcblk0p20 bs=4069
/sbin/sh: dd: Permission denied
~ $ su
/sbin/sh: su: Permission denied
~ $ sudo su
/sbin/sh: sudo: Permission denied
I have tried to use Advanced->Fix Permissions to no avail.
CWM is pure and latest from www dot clockworkmod dot com slash rommanager (new users apparently cannot post links). CWM is able successfully operate "Backup to External" from the stock device.
The end goal is to clone the clean, stock device onto the other one. CWM claims success on "Restore from External" to the other device, but it sits on the "Samsung" loading screen forever.
A solution to either or both of these problems would be appreciated.
This was accidentally posted to General a few minutes ago, but as a new user, I don't have the ability to delete it.
-MM
You need to boot the device and then connect it to adb. Then you get a popup on your phone to allow your pc. After that you can use adb from cwm.
Lennyz1988 said:
You need to boot the device and then connect it to adb. Then you get a popup on your phone to allow your pc. After that you can use adb from cwm.
Click to expand...
Click to collapse
I booted into android, connected it to Ubuntu, enabled ADB, authorized the device, chose to remember the device, then "adb shell" into the phone. I can LS and CD around.
I rebooted into CWM Recovery, did "adb shell" and still cannot execute LS. CD works but that is bash internal not a program. Other programs are still "Permission Denied"
I am not that an expert of adb, but couldn't that be caused by the fact that you are not rooted?
Lennyz1988 said:
I am not that an expert of adb, but couldn't that be caused by the fact that you are not rooted?
Click to expand...
Click to collapse
You're conflating the environments. CWMis inherently rooted; when in recovery, Android is never booted. I have execute permission in Android, not in CWM.
nvm
As resolution to my problem, I never did fix Clockwork Mod. Instead, I flashed TWRP for the I9500 and it allows me to execute
Code:
adb shell su -c ...