I don't know if it has anything to do with it, but after I installed the new google voice search, my search key didn't work any more. When I touch the search key now, it doesn't do anything. Any idea?
Thanx in advance.
Sent from my PC36100 using XDA App
Same boat.
Cm6.
Any ideas people?
Add me to this list same here
The voice search isn't to blame it's the new Google search widget that you need to blame.
Sent from my PC36100 using Tapatalk
you got to hold it, hold it for like 3-4 seconds, it will work, at least on fresh does!!
What ive been looking for..
Sounds like a great fix to that annoying thing. I hate that it comes on all the time. Think ill install it just for the break rofl....................
jonathaflores said:
you got to hold it, hold it for like 3-4 seconds, it will work, at least on fresh does!!
Click to expand...
Click to collapse
That asks for the long press one
I'm talking about the single press search
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
drmacinyasha said:
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
Click to expand...
Click to collapse
I am fully rooted anyway to do this via titanium backul? Is the main goal here to uninstall the old apps?
Jsimon9633 said:
I am fully rooted anyway to do this via titanium backul? Is the main goal here to uninstall the old apps?
Click to expand...
Click to collapse
No way that I found. His way is flawless and just requires typing what you see.
the adb commands worked awesome...I still have a slight lag with the "hard" key search button...still requires a long press.
Thanks!!
Quick note: If you do all of that, and when short-pressing the Search key, you don't get the Google Search (and assuming you've installed Google Search from the Market), use these commands:
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell cp /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
adb reboot
This thread oughtta be stickied. I've already quoted my post in here three times.
drmacinyasha said:
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
Click to expand...
Click to collapse
I've already uinstalled/rebooted/installed both the voice search and the google search. Do i still proceed with the above steps? And if so, can I type these commands as I see them into the Terminal Emulator on the phone itself?
The commands are meant to be done via ADB (a command prompt/shell on your computer).
If you already have everything working (including the search key) then there's no need for you to do this.
drmacinyasha said:
Quick note: If you do all of that, and when short-pressing the Search key, you don't get the Google Search (and assuming you've installed Google Search from the Market), use these commands:
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell cp /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
adb reboot
This thread oughtta be stickied. I've already quoted my post in here three times.
Click to expand...
Click to collapse
You are a lifesaver. Was freaking out when my search button broke. This fixed it. Thank you!
Sent from my PC36100 using XDA App
drmacinyasha said:
The commands are meant to be done via ADB (a command prompt/shell on your computer).
If you already have everything working (including the search key) then there's no need for you to do this.
Click to expand...
Click to collapse
I've just uinstalled/rebooted/installed both the voice search and google search. Voice search works fine, but as I said previously, the google search button is broken.
I want to use your instructions but I've never used adb on my computer before. Can you help me out? I've always avoided using it, but maybe it's time I learn.
tranquilchaos said:
I've just uinstalled/rebooted/installed both the voice search and google search. Voice search works fine, but as I said previously, the google search button is broken.
I want to use your instructions but I've never used adb on my computer before. Can you help me out? I've always avoided using it, but maybe it's time I learn.
Click to expand...
Click to collapse
there's a thread in development on how to use adb.
seriously, once you get the least bit familiar with it, you won't want to use anything else...
i do everything from adb. it's just easier. trust me. i've tried all the other methods, and they're a pain in comparison
timothydonohue said:
there's a thread in development on how to use adb.
seriously, once you get the least bit familiar with it, you won't want to use anything else...
i do everything from adb. it's just easier. trust me. i've tried all the other methods, and they're a pain in comparison
Click to expand...
Click to collapse
Wowsers, so I found the following post: http://forum.xda-developers.com/showthread.php?t=502010 (adb for dummies) but I'm lost.
It seems to be designed for Windows users....So far I have:
downloaded the newest SDK package, Eclipse and installed the ADT Plugin. Now what? I'm so confused...any help would be great!
tranquilchaos said:
Wowsers, so I found the following post: http://forum.xda-developers.com/showthread.php?t=502010 (adb for dummies) but I'm lost.
It seems to be designed for Windows users....So far I have:
downloaded the newest SDK package, Eclipse and installed the ADT Plugin. Now what? I'm so confused...any help would be great!
Click to expand...
Click to collapse
You don't need Eclipse or anything like that.
Just go to Start>Run, type in "cmd" (no quotes) and then type the command:
cd *location of where you saved the Android SDK*
cd tools
So if you copied the Android SDK to "C:\Program Files (x86)\Android SDK", you would type:
cd "C:\Program files (x86)\Android SDK\"
cd tools
Now just type in the commands, starting with "adb " such as "adb reboot" or "adb shell" and so on.
EDIT: Since there was an update for the Nexus One version of CM6, there's now a new GApps ZIP which contains the new search, Voice Search, etc. Just copy it to your SD card, reboot into recovery, and flash it:
http://mirror.kanged.net/gapps/gapps-hdpi-20100814-signed.zip
Related
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
After reading a little more i can see that this will never work for me and my ROM (I'm a donut)
So yea... anyone know if anything like this is possible in a donut build?
not like the animations from eclair . as far as i have been able to find this is only a eclair thing.
ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
adb push boot1.gif /system/media/bootscreen/
adb push boot2.gif /system/media/bootscreen/
adb push boot_animation.xml /system/media/bootscreen/
adb push boot_bg.gif /system/media/bootscreen/
adb push boot_bg.mp3 /system/media/bootscreen/
unzip the file
xile6 said:
adb push boot1.gif /system/media/bootscreen/
adb push boot2.gif /system/media/bootscreen/
adb push boot_animation.xml /system/media/bootscreen/
adb push boot_bg.gif /system/media/bootscreen/
adb push boot_bg.mp3 /system/media/bootscreen/
unzip the file
Click to expand...
Click to collapse
First of all, if you even read his request, he wants to know how to do it via terminal since he doesn't want to install adb drivers on his computer and I'm pretty sure .gif boots won't work on a cupcake/donut/eclair/ ROM unless they are a HTC SENSE ROM. Please read before posting some BS.
Dude you should just flash via Recovery.
ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
try
cat /sdcard/bootanimation.zip > /system/media/
Macrophage001 said:
try
cat /sdcard/bootanimation.zip > /system/media/
Click to expand...
Click to collapse
Not gonna work, 1) What the hack are you trying to do with that command and 2) He's on Donut, he needs eclair
Damn My eyes are terrible.
note to self:
READ BEFORE WRITE!!!!
on google donut builds, you're stuck with the android-logo-mask and android-logo-shine boot animations. on hero builds, you can use the animated gifs. on eclair builds, you can do the bootanimation zips. if you want to know how to do a standard google build boot animation without using adb, check the link in my signature. i made a full written + video tutorial on how to do it.
the other easy way to do it, is of course, metamorph. making the .thm files takes about 30 seconds and you can flash it without having to use adb, terminal OR recovery.
So how did Cyanogen make a custom boot animation for CyanogenMod?
exactly in the fashion shown in my video tutorial. its not hard.
CM=google build.
your signature
kusotare said:
exactly in the fashion shown in my video tutorial. its not hard.
CM=google build.
Click to expand...
Click to collapse
Dude I love your sig...its tight how you got everything you are running in the form of a link, so people who want the same can easily learn how to do it without asking questions(which they still will do anyway) by simply clicking your links.
thats what I call community contribution.
heh, thanks, i havent updated the links in a LONG damn time though, as you can see. I'm obviously not running CM 4.2.3.1 anymore.
Kudos for the Vibrant!
Gotta love that 4.0 amoled screen dislplay.
and I love how Klyentel has his "G1-BRICKED!"
in his signature, too funny.
ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
yeah it is possible i do it all the time download terminal emulator form the market and enter the following commands
su
# cp /sdcard/bootanimation.zip /data/local/
# reboot
it works for me all the time
I followed this thread:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac-3.html
I went through all the steps and I'm exhausted since I spent like 2 hours doing this rooting process.
Now someone PLEASE tell me before I gouge my eyes out and skull **** myself if I achieved root.
Am I supposed to see a new icon indicating that I rooted? I don't see anything that says Super Agent but I followed those instructions to a T.
Right now I'm restoring my apps back on and I'm going to be very pissed if I'm thinking what I'm thinking. By the way I searched Google and someone on a forum said that if you cab download wireless tether from market then you're rooted. I was able to download it but does that really mean I am or did that just apply to that particular android phone?
open up a terminal or command line window.
run your adb program, with the following command line
mac
./adb shell
windows
adb shell
(or however you invoked it during the rooting process)
if your prompt looks like
Code:
#
you win.
else, you lose.
edit:
you'll only see superuser permissions if you install the app, not sure where to get it from as when i flash new roms they're preinstalled.
i suggest going on to flash a recovery image, so you can flash other ROMS with ease.
Thankfully I saw the # sign so that means I'm good. How do I go about starting to remove the apps I don't need anymore?
I have to research recovery roms because I don't have the patience to do it today.
just go flash a new ROM that has all the junk removed and save yourself the trouble.
i here there are programs that will do this for you as well, btu i dont know em off hand
gqstatus0685 said:
Thankfully I saw the # sign so that means I'm good. How do I go about starting to remove the apps I don't need anymore?
I have to research recovery roms because I don't have the patience to do it today.
Click to expand...
Click to collapse
1. Reboot in to recovery, so that /system will be writeable.
2. Launch an adb shell and navigate to /system/app:
Code:
./adb shell
# cd /system/app
3. Delete the programs you don't want by using the rm (remove) command:
Code:
# rm Flickr.apk
4. Reboot the device.
If you want to err on the side of caution, you can move the programs to your SD card, or your computer, so that you can restore them if needed:
Move to SD card:
Code:
./adb shell
# mkdir /sdcard/apkbackup
# mv /system/app/Flickr.apk /sdcard/apkbackup
Restore from SD card:
Code:
./adb shell
# mv /sdcrd/apkbackup/Flickr.apk /System/app
Backup to your computer:
Code:
./adb pull /system/app/Flickr.apk ~/Desktop/Flickr.apk
./adb shell
# rm /system/app/Flickr.apk
Restore from your computer:
Code:
./adb push ~/Desktop/Flickr.apk /system/app/Flickr.apk
Have fun!
cent
Alright all,
I know there's another thread about "easier" method, but this is easiest for me. 3-Clicks after installation.
I was really tired of typing the same crap over and over after rebooting just to get my temproot back to do more testing/playing.
So I redeveloped this to be quicker/easier upon reboot. Mainly I altered the Term app to be have a scripted start-up on the 1st 3 launches.
I also updated the su/Superuser combo with ChainDD's latest stuff.
Here's how it works, after it's installed.
3ClickTempRooter said:
1) You run the terminal app once, wait a few seconds and it disappears.
2) You run the terminal again, wait for it to FC.
3) You run the terminal a final time and receive root.
Click to expand...
Click to collapse
Now on each reboot, it will be simply 3-clicks (running terminal app 3 times).
Finally ... any executable script placed in /data/local/tmp will be in the path of the new terminal mod. This makes running other scripts very easy.
Installation
Download the attached QuickTempRooter.zip and place it in a directory and unpack it.
Turn on USB debugging and install through adb ...
Here's the adb installation snippet ...
Code:
adb kill-server
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push rage /data/local/tmp/rage
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/busybox
adb shell chmod 0755 /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/root
adb shell 'pm uninstall com.android.term'
adb install Term.apk
Has made my life wayyy easier when playing with this phone while we wait for the real-deal!!!
Hope you enjoy!
NOTES
If you get a permission denied on the ''adb shell 'pm uninstall com.android.term' '' ... this is normal if you don't have a terminal already installed or have an alternate terminal app (using a namespace other than com.android.term.
If you have another Terminal App installed, you may want to uninstall it first, to avoid confusion.
Also, you may need to reboot after the initial installation for it to work properly!
ummmmm.....Enomther??
Did you get a G2 already?
Great to see you helping out with this
Great to see you here man! Trying this now can't wait to get themes rolling once we get permanent root!
Sent from my T-Mobile G2 using XDA App
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
burton14e7 said:
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
Click to expand...
Click to collapse
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Thank you sir. Appreciate the goodness.
damn i wish i could hit the thanks button
Thanks man good to have you on the G2 too
Sent from my T-Mobile G2
enomther said:
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Click to expand...
Click to collapse
good to see you on this side.... i have terminal app installed rebooted but still get this denied when running adb shell 'pm uninstall com.android.term
Edit: fixed it uninstalled the Android Terminal E,ulator and just ran the setup now have root thanks
Thank You..
Enom.. (sigh)
Welcome Home..
thank u so much now i can wireless tether. easiest root ever
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
ddgarcia05 said:
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
Click to expand...
Click to collapse
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
HamNCheese said:
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
Click to expand...
Click to collapse
So they go into the tools folder? Damn. I think I've in over my head here.
Like this?
If you have better terminal, you can also add the rage and root to specific keys.
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
kevdawg said:
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
Click to expand...
Click to collapse
Unplug then plug ur phone back in then try again also make sure u are in usb debug mode
Good work, Temp root in like 5 seconds
Quick question, ok I was able to get root for a few mins, then it went away I guess I have to have the terminal always open or ignore so my taskiller doesnt terminated it?
Don't use task killers. (IMHO)
But I tend to have to reboot every once in a while to keep root in tacked within terminal but all my apps seem to stay with su permissions until reboot (or sometimes 12 hours)
I'm trying the rage root method after reading up on all the stuff. I managed to get adb installed and connected, but i can't use adb actions.
I type in c\androidsdk\tools\adb shell
$ su
$ SUermission denied
even without su, if i try to type "adb push su /sdcard/su" it says adb permission denied.
I have kept my phone screen on as per another thread, but i do not get a prompt that asks for adb permissions. Am i missing an app or something? I do have debugging and screen awke both on.
I have placed the g2 root folder in the androidsdk\tools\ folder, both just the files and the entire folder just to be sure.
Obviously I'm new to adb, so If i'm doing something completely wrong just let me know.
as long as you're not rooted (temp or perma) you can't use "su" in adb-commands... If you tell a little more about what you're trying to push, then I can help some more
Im just trying to root the phone with rage since visionary seems unreliable.
Im trying to adb push the su/ sdcard/su as per the first line of instruction in the rage temp root guide
hehe... I used the visionary root, and it have worked good for me btw, I think you should've posted in the rage-thread instead of opening a new topic, but now it's already opened so here it goes
firstly... are you sure you're in the right folder, and have the folder "su" in there?
If so, don't go into "adb shell"... use the lines exactly as stated in the OP. adb inside an adb shell won't give the results you want... Post back if it doesn't work
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Ok, my adb stuff is in c:\tools .. so when I first open command prompt, I have to type this:
cd c:\tools
That puts me into the correct folder. If yours is in C, then you'd probably have to do this:
cd c:\androidsdk\tools
Then type:
adb devices
It should at least give you SOME sort of output, either with your device number (if it's connected, and adb is working properly), or just say devices, with no numbers (incorrectly)
dwang93 said:
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Click to expand...
Click to collapse
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
FYI you will not see the $ symbol. that just indicated the next line you have to enter in commnad prompt. Each time you see $ just mean you type that line then press enter. Wait to see a result of transfer from prompt then enter next line and so on.
rsxtypes72 said:
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
This!! I'll be kind though.
Make your life easy. Unzip the contents of g2TempRoot, to your tools folder, in sdk. So, unzip the g2temproot to your desktop. Go into that folder. Copy all, and move them to c:\androidsdk\tools. Now, once that's done, go into command prompt. cd c:\androidsdk\tools. Then, do as follows, as per that link
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
(Sorry I couldn't be of more help, as I used VisionaryR12 and it worked fine for me.)
One more word of advise...
I would recommend you try temp root first.
Become used to using adb then try to get full root.
When you use temp root everything you do is temporary only.
Rebooting will reset everything back to stock so its good practice.
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
any tips on going onto the perm root?
Click to expand...
Click to collapse
Read .. research .. double check .. triple check .. and right before you do it .. check again. As you're doing it, go over every letter, space, and character to make sure it's as it should be.
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Daughain said:
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Click to expand...
Click to collapse
Upload a screen shot of your command window
with the error
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
Click to expand...
Click to collapse
dude..I think I am doing something like you...could you please post what you did....I think is an issue of directories..but I'm not that familiar with adb and i have not been able to figure this out.....
Thanks!!!
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.