I rooted successfully last night and got the app titanium and superuser and busybox. And I wana know what do I use to completely remove apps like moxier mail and some keyboards and quadropop. And what is superuser and busybox and titanium for? Sorry for noobness but ive nevrr rooted b4 so I wana learn.
the_ahmadzais said:
I rooted successfully last night and got the app titanium and superuser and busybox. And I wana know what do I use to completely remove apps like moxier mail and some keyboards and quadropop. And what is superuser and busybox and titanium for? Sorry for noobness but ive nevrr rooted b4 so I wana learn.
Click to expand...
Click to collapse
Remove app with adb.exe in a windows command prompt, or use Titanium Backup (backup software to be installed in your phone, makes backups to sdcard) to remove apps. (never tried it, as a unix/linux/OS X man i like the command prompt)
Superuser gives you the chance to allow/deny apps to have he superuser permissions.
Busybox gives the commands you need, like su, ls, mkdir, pwd, mv, cp, dmesg etc. that you need in the terminal window to do your magic. Unix commands that is. (more or less)
If you want to know what your phone is doing at start up, install Better Terminal and issue the command dmesg (means something like display message.log).
In Titanium Back Up, long press on the application you want to uninstall, it'll open a window or whatever you call it. Here's the "unistall" option
Related
When i download and install an App from the Android Market where the Apk installation file is temporary placed? Which path?
tnx in advance
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
sidvizioso said:
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
Click to expand...
Click to collapse
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
So which is the temp path of the downloaded apk from market?
i want to grab them...
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
of course you can.
you just have to copy them to your sdcard or pc an install them again, with «adb install something.apk» or «Astro File Manager» (or a similar file managerapp)
a hard reset will delete everything on «/data»
If you have root copy the contents of both folders to your SD card.
mkdir /sdcard/apps
cp /data/app/* /sdcard/apps
cp /data/app-private/* /sdcard/apps
Then after you wipe (I've never heard anyone call it a 'hard reset' before) you can use an app like Astore or ApkInstaller to reinstall them.
If you don't have root then not only will you not be able to read app-private, but your ROM wont have busybox so you wont be able to bash in those commands. In that case use an app like Astro or AppManager to copy non-private apks to the sdcard, but for private apps you'll have to redownload them (without being charged of course.)
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
Only if they're non-private (reside in /app, private being /app-private).
He's probably coming from WinMo. We called a factory reset/wipe a hard reset.
mopodo said:
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Click to expand...
Click to collapse
Slightly off topic lol But i see you said Private does that mean you could manually back up Private apps you buy off market by just copying them /w root access?
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
You could try an app manager and back 'em up from there.
Just try the following command.
busybox cp /data/app/* /sdcard/<your backup loc>
askwhy said:
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
Click to expand...
Click to collapse
Well in windows
'adb pull' is used if that helps
I can't seem to figure out how to remove stock apps using adb? Can anyone list the commands needed to do this?
adb remount
adb shell rm /system/app/YourApplicationHere.apk
cloudedice said:
adb remount
adb shell rm /system/app/YourApplicationHere.apk
Click to expand...
Click to collapse
Does this completely remove the app? I mean in particular the listing in the app drawer, as well as in the "Manage Apps" section (if applicable). Also where will app data be stored, if used?
Thanks
yes, completely.
use "adb shell ls -1 /system/app/" to find out the exact name of the app you want to delete, it's caps sensitive.
you can try these 2 programs to remove apps
you should try using android commander or droid explorer. search for them in the forums. they are free and help out a lot.
+ For Droid Explorer: http://de.codeplex.com/ I use this and it is pretty handy. Though you can just be lazy like I usually am and just uninstall apps via Titanium Backup. I haven't tried Android Commander (yet, but maybe I should...) but in interest of being fair, you can find it here: http://handheld.softpedia.com/get/Desktop-and-Shell/Windows/Android-Commander-93099.shtml and the official site is here, but didn't find it very well laid out (no offense PanPiotr...): http://androidcommander.com/
One other thing if you want to backup the app to your sd use cp /system/apps/appnname /sdcard/backup/appname
Sent from my Eris using XDA App
Sorry to ask such a noob question, but I just ran Unrevoked 3 and unrevoked forever. Everything seemed to work correctly, but when I try and run androind commander to delete files it says I need root permissions. I saw the superuser permissions icon in my app list, but when I click it nothing happens. Did I miss something?
ryanmc2033 said:
Sorry to ask such a noob question, but I just ran Unrevoked 3 and unrevoked forever. Everything seemed to work correctly, but when I try and run androind commander to delete files it says I need root permissions. I saw the superuser permissions icon in my app list, but when I click it nothing happens. Did I miss something?
Click to expand...
Click to collapse
do you use other apps (setcpu, etc) that require Superuser permissions? any issues with those? if you do have other apps that have SU permissions, then uninstall/reinstall Android Commander... it should then request permission again.
if neither situation applies... use the directions above to remove the Superuser.apk file from /system/app and then go to this thread and download the new Superuser app
http://forum.xda-developers.com/showthread.php?t=682828
Hi guys. I have already rooted my Wildfire with unrevoked3 and worked like a charm. Superuser is OK, I installed Titanium Backup and I installed busybox with it.
But I can't find how to run the busybox shell with root. Can anyone help me?
I downloaded android sdk for my Ubuntu 10.10 (I don't use windows) and I typed as root: ./adb shell and the terminal has not root priviledges.
Is there anyway to do this? Also how to run busybox? Via Terminal Emulator?
I think that the Titanium Backup didn't installed correctly.
My goal is to get a root terminal
Thanks in advance
Assuming that stuff works the same as on my linux computer, you would just su in the terminal emulator, then cd into the busybox directory, then make sure you have execute permissions for it, and then just ./busybox. That should start busybox in shell mode. That's how it should work.I think.
xc1024 said:
Assuming that stuff works the same as on my linux computer, you would just su in the terminal emulator, then cd into the busybox directory, then make sure you have execute permissions for it, and then just ./busybox. That should start busybox in shell mode. That's how it should work.I think.
Click to expand...
Click to collapse
The busybox is executed in my machine not in my phone right?
No, on your phone. Open up terminal on your phone (you can get one off the Market or alternatively connect you phone to the computer and start a ashell using adb), then cd to the directory you have busybox in, and then ececute ./busybox. Remember, you can't put it on the SD card because it doesn't allow execution.
sorry for this Android newbie question..
I installed Titanium Backup on my Desire....but when I ran it, an error message says " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again".
My Froyo is rooted....but whats this BusyBox and where can I get it and install it?
thanks..
I'm assuming you haven't rooted yet. Turn wifi on. Get an app called "universal androot". You need to get a version at least 1.6.2. It's not in the market so you may have to look around. Install and Open it up. Tick the box that says "soft root". Click the button labelled "root ". When the application force closes, wait 10 second and do nothing. then click on force close. Toggle wifi on. Go to titanium. Press allow when asked for root privileges. If it doesn't come up, look around titanium. It should allow you to instal busybox. Busybox is a set of *NIX utilities that are better than androids builtin. It allows the apps to use more advanced features. And It helps users if they are knowledgeable though to know how to use it.
nope..mine is rooted already via unrevoked3
dinoalbert said:
sorry for this Android newbie question..
I installed Titanium Backup on my Desire....but when I ran it, an error message says " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again".
Click to expand...
Click to collapse
Same problem here
rooted with revok3
installed rom manager and did a first backup
install titanium n tried to backup apps
It said " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again"
could some one link me to busybox app for wildfire n guide on how to backup wit titanium
pl reply
realxception said:
Same problem here
rooted with revok3
installed rom manager and did a first backup
install titanium n tried to backup apps
It said " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again"
could some one link me to busybox app for wildfire n guide on how to backup wit titanium
pl reply
Click to expand...
Click to collapse
Go to titanium backup, go to problems then it,will install busybox
thanks , its worked
I need to uninstall as many apks as I can from my phones memory and download them off of market and install on my sd card to free up memory. My phone memory is pretty full and seems to be causing it to lag.... What are the safe ones and unsafe ones to remove?
Tenacious--M said:
I need to uninstall as many apks as I can from my phones memory and download them off of market and install on my sd card to free up memory. My phone memory is pretty full and seems to be causing it to lag.... What are the safe ones and unsafe ones to remove?
Click to expand...
Click to collapse
If you can find the app in the market then its safe to remove. If its in the market that makes it optional. However removing google apps can have adverse affects on other google apps, but your phone will still continue to function just fine, and most if not all the google apps can be found in the market (with the exception of the market itself, dont remove that!). Apps such as the music app and clock apps can be replaced entirely by market apps. Preinstalled wallpapers can also be removed from the rom. Another thing i remove is any ringtones I dont think I"ll need. I dont know about liberated, but cm6 has WAY more ringtones than I need/want, so I just delete em. I also now remove the boot animation from the ROM before installing it to save a few MB. You just get a black screen where the bootanimation would normally show up until the phone boots.
Whats the easiest way to remove files? Ive tried to use Root Explorer and Titanium Backup but they show back up when I restart... Im hoping there is an easier way to remove than adb.....????
Tenacious--M said:
Whats the easiest way to remove files? Ive tried to use Root Explorer and Titanium Backup but they show back up when I restart... Im hoping there is an easier way to remove than adb.....????
Click to expand...
Click to collapse
adb is pretty easy actually. Search the forums for making a cmd shortcut for adb, or if someone remembers how they could post it (this will make life infinitely easier). Then you just boot into recovery and plug in the phone, type the following without the apostrophes:
'adb shell' hit enter.
'cd /system/app' enter.
'ls' enter. (this will pop up a list of the apps you have)
'rm name of app.apk' and its gone forever.
Just keep repeating that last step for every app you want removed.
Can i do this via Terminal Emulator?
yes but the command is different...id give it if i knew it...
CallMeAria said:
adb is pretty easy actually. Search the forums for making a cmd shortcut for adb, or if someone remembers how they could post it (this will make life infinitely easier). Then you just boot into recovery and plug in the phone, type the following without the apostrophes:
'adb shell' hit enter.
'cd /system/app' enter.
'ls' enter. (this will pop up a list of the apps you have)
'rm name of app.apk' and its gone forever.
Just keep repeating that last step for every app you want removed.
Click to expand...
Click to collapse
Im having a hell of a time removing apps from my Liberated Aria. I have installed ADB and the necessary software. I am able to get into CMD and get a listing of files (apk's), but they do not remove... what commands do I need to use?
Ive tried
rm /youtube.apk
rm /system/youtube.apk
rm /system/app/youtube.apk
They are still there... maybe Im not mounting the drive? Or its not in Read/Write mode?
Tenacious--M said:
Im having a hell of a time removing apps from my Liberated Aria. I have installed ADB and the necessary software. I am able to get into CMD and get a listing of files (apk's), but they do not remove... what commands do I need to use?
Ive tried
rm /youtube.apk
rm /system/youtube.apk
rm /system/app/youtube.apk
They are still there... maybe Im not mounting the drive? Or its not in Read/Write mode?
Click to expand...
Click to collapse
make sure your bored into clockwork recovery. Then go to partitions and mount system. then just follow those same directions I posted above. To remove the app you would type:
rm youtube.apk
Exactly like that, with a space after rm and no /.
hm...
Some times I use SystemApp Remover.
Its pretty easy to work.
Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.
cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer
cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again
I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.
cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.