I'm using r0mans latest froyo ROM and he has the wifi tether app on /system. It FC's everytime I try to use it and it won't let uninstall it either. I tried in ADB to do "adb uninstall android.tether" and then it says waiting for device and never does anything. Any ideas here? Thanks.
EDIT: I figured it out...had to go into clockwork and then mount /system and then do adb shell and I was able to rm a .apk
Related
OK, so i installed the swype from stock espresso 2.1 ROM but it doesnt let me swype. tells me that its configured for a different device which is a fail honestly but how do i go along to delete it? Terminal or ADB commands would be nice because. Thanks fellas. i tried
rm -r /system/app/swype.apk
rm -r /system/app/com.swype.inputmethod
any other suggestions?
Did you try reflashing cm6? Idk if it will work, but worth a try.
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Did you try reflashing cm6? Idk if it will work, but worth a try.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
That seems like the only thing I can think of too. I'm having a similar problem where I tried to flash Swype, but it just keeps force closing, and now I actually HAVE the beta but I can't uninstall my old swype D: . I tried going thru with ADB and Root Explorer... It seems I deleted anything involved with Swype, BUT it's still in there somehow.
Shaquiel Harris said:
OK, so i installed the swype from stock espresso 2.1 ROM but it doesnt let me swype. tells me that its configured for a different device which is a fail honestly but how do i go along to delete it? Terminal or ADB commands would be nice because. Thanks fellas. i tried
rm -r /system/app/swype.apk
rm -r /system/app/com.swype.inputmethod
any other suggestions?
Click to expand...
Click to collapse
You have to do it via adb in while your phone is in recovery because our phones are s-on.
reboot into clockwork recovery, go into the partitions menu, mount /system, then in command prompt type
Code:
adb shell
rm /system/app/apkname.apk
If you're not sure what the exact name is do this:
Code:
adb shell
cd /system/app
ls
then it'll give you a list of all files in /system/app, type rm apkname.apk to remove it. Then reboot
MusicMan374 said:
You have to do it via adb in while your phone is in recovery because our phones are s-on.
reboot into clockwork recovery, go into the partitions menu, mount /system, then in command prompt type
Code:
adb shell
rm /system/app/apkname.apk
If you're not sure what the exact name is do this:
Code:
adb shell
cd /system/app
ls
then it'll give you a list of all files in /system/app, type rm apkname.apk to remove it. Then reboot
Click to expand...
Click to collapse
Ive tried that before (suggested by others) wouldnt work for me. I would always get a read only error. The cd /system/app ls command would run fine though :/
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Ive tried that before (suggested by others) wouldnt work for me. I would always get a read only error. The cd /system/app ls command would run fine though :/
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Were you in recovery? Another thing to try while in recovery and in adb shell, type this:
Code:
mount -o rw,remount /system
You might also try adb remount, not in shell, then go back into shell.
I'm on a HTC Desire, rooted with unrevoked and I have flashed the Oxygen ROM. I want to install custom framework, but every time I try to open Metamorph, I get the ''some files could not be extracted and set up. please make sure you have enough space in /system''. I have tried
''adb remount
adb shell
ln -s /system/xbin/busybox /system/xbin/cp'', but still without luck. Could someone please tell me what to do? I'm not very skilled at this, so please explain carefully. Thanks!
Isnt it because of the fact you need BusyBox from the market in order to get Metamorph to work, but BusyBox is not working for Desire yet.
it says so in the description of BusyBox in the market.
If you want busybox download titanium backup and open it, you will see how obtain busybox working on desire It worked for me
qweasdfzxc said:
If you want busybox download titanium backup and open it, you will see how obtain busybox working on desire It worked for me
Click to expand...
Click to collapse
Thanks, but am I supposed to do something after I've installed busybox with titanium? Or just open MM? cus that didn't work. And also, why can't I delete the 'busybox' file from /xbin? Sorry for being such a noob, but you're my hero if you can help me with this!
I have no idea how metamorp works or what you are trying to do, but if you want to write to the system partition while booted you need to be S-off.
If you want to delete busybox and you're not S-off, you need to do it with adb while in recovery.
TheGhost1233 said:
I have no idea how metamorp works or what you are trying to do, but if you want to write to the system partition while booted you need to be S-off.
If you want to delete busybox and you're not S-off, you need to do it with adb while in recovery.
Click to expand...
Click to collapse
alright, thanks. which adb command? tried adb uninstall, but that didn't work, unless i did something wrong
adb shell
rm /system/xbin/"whatever you are trying to remove from there"
To see what is in there:
ls /system/xbin
But i don't think uninstalling busybox will fix your problem since you got a error regarding /system and you won't be able to write to there unless you're S-off.
TheGhost1233 said:
adb shell
rm /system/xbin/"whatever you are trying to remove from there"
To see what is in there:
ls /system/xbin
But i don't think uninstalling busybox will fix your problem since you got a error regarding /system and you won't be able to write to there unless you're S-off.
Click to expand...
Click to collapse
Ok, thanks a lot anyway!
PLEASE CLOSE. ISSUE RESOLVED.
Hi everyone.
Basically I downloaded Wavesecure but it doesnt work so I need to take it off. Uninstalling the regular way doesnt work and I found a way to uninstall it by ADB commands but I have no idea how to get going.
The ADB command I need is
adb remount
adb shell rm /data/app/com.wsandroid-1.apk
I have no idea what it does either. Does it let the app become "uninstallable" through the normal settings?
So how do I give the command to the phone?
Thanks very much guys.
EDIT: nevermind, did it by removing the APK lol from root explorer.
I've got a few problems getting DSP Manager to work on Oxygen.
I try and install the DSPManager.apk file and just get a tick with "Application not installed" next to it.
That's a little confusing since the tick suggests it installed - the "Application not installed" and lack of app says otherwise.
I'm running Oxygen 2.2 but I also got this error on 2.1.6.
Any ideas?
Thanks.
push it via adb (I'm gonna assume you have android-sdk)
put the .apk in your c:\ and reboot into recovery
Code:
cd c:\android-sdk/platform-tools
adb shell
mount /system
exit
adb push c:\DSPManager.apk /system/app/DSPManager.apk
bortak said:
push it via adb (I'm gonna assume you have android-sdk)
put the .apk in your c:\ and reboot into recovery
Code:
cd c:\android-sdk/platform-tools
adb shell
mount /system
exit
adb push c:\DSPManager.apk /system/app/DSPManager.apk
Click to expand...
Click to collapse
That works.
Thanks a bunch mate.
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
SLOmtb said:
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
This is typically nothing to worry about. You will receive an error if the "check_rooted" folder didn't exist to begin with. Normal
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
Click to expand...
Click to collapse
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
Click to expand...
Click to collapse
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Wow! I'll give it a try tonight. Thanks!
soupmagnet said:
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Click to expand...
Click to collapse
Well, darn. I tried "adb root" and it says: "adbd cannot run as root in production builds." So I guess it isn't really rooted, after all.
Maybe the MoDaCo rom is the way to go, after all. Thanks, anyway!
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
sabithpkcmnr said:
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
Click to expand...
Click to collapse
The which system version?
Sent from my XT894 using Tapatalk
sd_shadow said:
The which system version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
sabithpkcmnr said:
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
Click to expand...
Click to collapse
That's Android version, not system version
Sent from my XT907 using Tapatalk