A rough guide for help on removing apps manually (i had to do this as android would not allow me to uninstall an app and it was no longer listed as an installed app in Google Play )
I used the following commands (In Terminal Emulator) in this order to remove Wi-Fi Direct (in this case but same process should work for other apps) manually (remember this is only a backup of the app and not a complete removal in the phone system, bricks are not to be made but found, this merely removes the app from the android dashboard/desktop/app list)...
su
ls
cd system/app
ls
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
mv WifiWsdsrv.odex backupwifi/WifiWsdsrv.odex
mv WifiContactSync.odex backupwifi/WifiContactSync.odex
mv WifiContactSync.apk backupwifi/WifiContactSync.apk
mv WifiP2PWizardy.odex backupwifi/WifiP2PWizardy.odex
mv WifiP2PWizardy.apk backupwifi/WifiP2PWizardy.apk
And to actually remove the backupwifi folder (completely remove everything from system) issue the following command...
rm -r backupwifi
Related
I seem to be frequently flashing or messing up my G1 so I decided to write some shell scripts to help out but they seem to only half work if at all. Actually I'm not sure what they did because they displayed no output.
This script is supposed to backup the default init.rc and mountd.conf files then replace the existing ones with the modified ones.
Though it does not work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
busybox cp -a /system/etc/mountd.conf /sdcard/recovery/mountd.conf.bak
busybox cp -a /system/init.rc /sdcard/recovery/init.rc.bak
busybox cp -a /sdcard/recovery/mountd.conf /system/etc/mountd.conf
busybox cp -a /sdcard/recovery/init.rc /system/init.rc
then this is the next set to move the apks and the program caches which doesn't work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
busybox cp -a /data/app /system/sd
rm -r /data/app
ln -s /system/sd/app /data/app
busybox cp -a /data/app-private /system/sd/app-private
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -R /data/data/com.android.browser/cache/webviewCache
ln -s /sdcard/cache/webviewCache /data/data/com.android.browser/cache/webviewCache
rm -R /data/data/com.android.vending/cache
ln -s /sdcard/cache/marketCache /data/data/com.android.vending/cache
rm -R /data/data/com.google.android.street/cache
ln -s /sdcard/cache/streetCache /data/data/com.google.android.street/cache
reboot
Plus both run and output no errors either. Who knows what problems I'll run into because I have no idea what they actually did.
Anyone see anything wrong here?
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
I have a menu that does that and I have got some experience as why it works one day and not the other.
Rafase282 said:
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
Click to expand...
Click to collapse
I took the reboot out after the mountd.conf and init.rc did not appear to copy due to the lack of /dev/mmcblk0p2 hoping to see some sort of output why it did not run. Unfortunately it runs and backs up the files but does not replace them with the modded ones.
Rafase282 said:
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
Click to expand...
Click to collapse
Not copying the apps is a good idea, modified the script to not do so.
Rafase282 said:
I have a menu that does that and I have got some experience as why it works one day and not the other.
Click to expand...
Click to collapse
Does Android require that you do a chmod on all shell scripts first?
On Debian I usually just use sudo sh ./ and it runs the script w/o changing anything on the file permissions so I figured Android would be similar if I just ran them as root. Still I see a lot of people requiring a chmod 777 on any guide referring to running shell scripts.
I will try that and report back with my findings. Thanks for replying.
Does Android require that you do a chmod on all shell scripts first? I just have to type m oon anywhere in the androud shell and my scripts run, for that i put it on /system/bin and do a chmod 4755 to the file. it is still needed to type su before you run the script.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
cp /sdcard/media/Data/mountd.conf /system/etc/mountd.conf
cp /sdcard/media/Data/init.rc /system/init.rc
Thats my code for copying the modified files to the right place. So maybe you should try that.
Oh for androoid you dont unless you put it on /system/bin then you will have to use sude and sometiems it still wont run due to lack or permisions so is better to do a chmod 4755
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
joshtheitguy said:
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
Click to expand...
Click to collapse
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
LucidREM said:
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
Click to expand...
Click to collapse
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
joshtheitguy said:
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
Click to expand...
Click to collapse
yes .. but you can't create the sym links when they already exist .. running the update.zip only wipes the /system .. not /data .. if the links were there before the update.zip they will be there after
I did not write these scripts. I claim zero credit for them. I pulled them from somewhere (another ROM or a mod for another phone, I can't remember.) I am simply passing on the information.
Here is a way you can add two scripts to change your /system from read-only to read-write and visa-versa. I am not going to hold your hand through this one. If you don't understand it, then don't do it. This is only for those that want a command line script to set their system filesystem to RW and back to RO in a simple way. This is only for people that are comfortable with the command prompt and adb shell to begin with. I am not responsible if you brick your phone.
I'll say it again. I am not responsible if you brick your phone.
Save a text file called: ro that contains:
Code:
#!/system/bin/sh
fs=`mount | grep system | awk '{print $5}'`
mount -t $fs -o remount,ro /dev/block/stl9 /system
Save a text file called: rw that contains:
Code:
#!/system/bin/sh
fs=`mount | grep system | awk '{print $5}'`
mount -t $fs -o remount,rw /dev/block/stl9 /system
Then open a command prompt and change directory to where you have the ro and rw files located. Notice that the ro and rw files DO NOT have any file extension on them. These should NOT show up as text files with Notepad icons when using Windows Explorer. If they do, then you need to take the .txt off the end of the filename. If you can't see it, then you have to be sure to show the hidden extensions.
The following steps assumes that you either have adb.exe and related files in the same directory as your rw and ro scripts OR you have added adb.exe to the PATH environment variable on your computer system.
When you are ready do this:
Code:
adb push rw /data/local/tmp/rw
adb push ro /data/local/tmp/ro
adb shell chmod 0755 /data/local/tmp/rw
adb shell
/data/local/tmp/rw
cp /data/local/tmp/rw /system/xbin/rw
cp /data/local/tmp/ro /system/xbin/ro
chmod 0755 /system/xbin/ro
chmod 0755 /system/xbin/rw
/system/xbin/ro
reboot
Notice that the last command will reboot your phone. This is only necessary if you want these scripts to be usable immediately. When you have rebooted, you should be able to type the command: rw to set your /system to read-write and ro to set your /system to read-only
Personally, I skip that last "reboot" command and I just run /system/xbin/ro manually until the next time I reboot my phone anyway.
These two scripts should be compatible with what ever file system you have on /system since if you read the script it actually checks the file system type first and then uses that response in the next line.
Use at your own risk, though.
EDIT: On Gingerbread, I had to use /dev/block/stl10 instead of /dev/block/stl9 above.
Hi, I'm enter on my transformer by :
adb shell
and I want do that :
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /data/app
rm com.mhuang.overclock*
cd /data/data
rm com.mhuang.overclock*
cd /data/dalvik-cache
rm *mhuang.overclock*
exit
But when I execute su, it don't work :
/data/app # su
Segmentation fault
Can you help me ?
Thanks
Just reflash your rom without wiping data unless your trying to flash a rom that is overclocked by default
If it's in your data partition, then it's not a system file. Try this:
adb uninstall com.mhuang.overclocking (use the full package name)
EDIT: saw your other thread about borking your TF. follow badfrog's trick and flash a rom with a non-overclocking kernel, which will limit setcpu.
If adb uninstall don't work, which rom with overclock by default propose me ? Révolution HD ?
Sorry for my english, i'm french ?
Prime has a stock kernel as default
http://forum.xda-developers.com/showthread.php?t=1251044
I used the xUltimate-v2.3.3 to make deodex.
Then it comes to two folders "done_app" & "done_frame"
I copy the two folders into my sdcard, and I want to use adb shell to push & replace
files to system/app /frams
down are my situation.
===========================
C:\android-sdk-windows\tools>adb shell
[email protected]:/$ su
su
[email protected]:/# stop
.................................then it stop...I can't do anything
===========================
down are the sample code from internet
============================
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
=====================================
Can you help me ?
I did wrong on what step....
My OS system is windows7 x64 in command line.
dickluo said:
i used the xultimate-v2.3.3 to make deodex.
Then it comes to two folders "done_app" & "done_frame"
i copy the two folders into my sdcard, and i want to use adb shell to push & replace
files to system/app /frams
down are my situation.
===========================
c:\android-sdk-windows\tools>adb shell
[email protected]:/$ su
su
[email protected]:/# stop
.................................then it stop...i can't do anything
===========================
down are the sample code from internet
============================
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
=====================================
can you help me ?
I did wrong on what step....
My os system is windows7 x64 in command line.
Click to expand...
Click to collapse
記得右鍵點擊cmd圖標，選擇 以管理員身份運行。 看看你是不是忘記了這一步~
No use about that.
Maybe I'll try it on winxp system.
Sent from my ME865 using xda premium
Hey, I installed BT5 arm on the Motorola Xoom wifi and i would like to know how to completely remove it from my device. My device is rooted and i have tried to delete the whole BT5 file with astro file manager and absolute file manager but neither of them worked. I was wondering if anyone knows another way of doing it.
I tried deleting it with commands in terminal emulator but its a read only file. Wouldn't chmod help with that? If so how would i use it?
jimmothycharles said:
I tried deleting it with commands in terminal emulator but its a read only file. Wouldn't chmod help with that? If so how would i use it?
Click to expand...
Click to collapse
Go read the backtrack 5 thread. There is a link on how to remove it. That really should be the first thing you check before asking
ok thanks, ill do that the next time i have a problem
I couldn't find it. I think it might be a tiamat BT5 img and i have the remover tool but im not quite sure how to use it. I just flashed it like i would do with a rom but it says installation failed. what would i do to fix that?
jimmothycharles said:
I couldn't find it. I think it might be a tiamat BT5 img and i have the remover tool but im not quite sure how to use it. I just flashed it like i would do with a rom but it says installation failed. what would i do to fix that?
Click to expand...
Click to collapse
Common knowledge - system must be set to RW
Here is an alternate route- manually
How To:
ADB Shell Folder Removal - (we will use BT5 as an example)
++++++++++++++++++++++++++++
1. Connect Xoom to pc
2. Boot into recovery
3. Toggle to internal storage as /sdcard
4. mount /data
Enter adb shell via pc
(cd to file location) in this case BT5, is in the sdcard directory
Code:
Code:
cd /sdcard #
(once typed, you will be at.... /data/media prompt)
if after the above command and you are not at the /data/media prompt start over)
Code:
Code:
rm -r BT5
(BT5 is the stubborn Folder)
*Side note ... This works for any other stubborn folder that you want to delete as well...
USE AT YOU OWN RISK - MAKE SURE YOU DO A BACKUP FIRST
If this was helpful Hit The Thanks!
it didnt work it said that rm failed for BT5, permission denied
jimmothycharles said:
it didnt work it said that rm failed for BT5, permission denied
Click to expand...
Click to collapse
Come on now, lol Your device must be set to rw. Google can guide you.
Mjamocha said:
Come on now, lol Your device must be set to rw. Google can guide you.
Click to expand...
Click to collapse
ok well this is what i got when i tried to do that.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\Users\josh\Desktop\xoom files\BT5
C:\Users\josh\Desktop\xoom files\BT5>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # cd storage/sdcard0/0/0/0
cd storage/sdcard0/0/0/0
[email protected]:/storage/sdcard0/0/0/0 # ls
ls
Android
BT5
Box
DCIM
Download
Evernote
Pictures
SELog.txt
Video
airdroid
goodies
goomanager
tmp
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 # rm BT5
rm BT5
rm failed for BT5, Is a directory
255|[email protected]:/storage/sdcard0/0/0/0 # cd
cd
[email protected]:/data # exit
exit
C:\Users\josh\Desktop\xoom files\BT5>adb shell
[email protected]:/ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # cd storage/sdcard0/0/0/0
cd storage/sdcard0/0/0/0
[email protected]:/storage/sdcard0/0/0/0 # ls
ls
Android
BT5
Box
DCIM
Download
Evernote
Pictures
SELog.txt
Video
airdroid
goodies
goomanager
tmp
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 # rm -rBT5
rm -rBT5
rm failed for -rBT5, No such file or directory
255|[email protected]:/storage/sdcard0/0/0/0 # chmod 777 BT5
chmod 777 BT5
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 #
I looked up on google how to mount system rw and thats where [email protected]:/ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system came from. then i tried rm -r BT5 after that and it was still denied. so i tried to
do chmod 777 BT5 to give all permissions and then when i tried to remove it again it was still denied.
I looked up the permissions of the file and its set to rwxrwxr-x. so chmod apparently didn't work