Alright, so checking up the system folder with root explorer I noticed that there are several applications related to the stock music player.
I can't just simply remove these "apks", right? Pretty certain there'd be leftovers of this app somewhere.
So, I realize, there's no "uninstall" script for the music app, but I was wondering, what is the most correct way to delete music application?
Simple doing this won't cut it, right?
Code:
su
cd system/app
mount -o rw,remount /system
rm -r MusicCommonUtility
rm -rMusicLiveShare2.apk
rm -rMusicPlayerWT.apk
mount -o remount,ro /system
For that kind of things I use Titanium backup app. With that app you can backup ANY app before uninstalling it or just simply uninstalling it. After that reboot the phone and that app is gone.
Related
I rooted my hero last night and tried out a few different ROMs but eventually decided to revert to stock and make some manual changes. I used nandroid to restore to just after the root (1.56.651.2). I was able to remove some apps using adb, but the adb remount command fails (permission denied), and I'm unable to push a new bootscreen on to the phone. I also tried a Root File Manager and pre-kitchen as alternatives for the bootscreen, and neither one works. The Root Manager won't paste the files from SD into /system/media/ and pre-kitchen just reboots the phone.
Any suggestions?
Any chance this has something to do with downloading only up to SDK Platform 1.5? I'm at a total loss. I RUU'd my phone, did a clean root at startup using adb shell, and I still have the same problem. The adb remount command won't work, and I can't push anything into the system directory. For what it's worth, when I still had Root Manager installed I was able to toggle RO R/W in any directory with no problem, and I could move files around within the ROM... but I couldn't move anything into it from the SD. I'm new at this, so I have no idea what the problem might be. Anyone else had this problem or have any suggestions?
If anyone else runs into this problem, this solution worked for me:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
Restore modified permissions when done.
Though I'm still not sure why this is necessary in place of adb remount.
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dametzg said:
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Thanks... didn't realize stock wouldn't accept adb remount. If I use the above line from within shell, that doesn't help me push anything on to the phone though... so I needed to enable global permission and then do the push. Oddly enough I tried the same approach last night using Root Manager, and the transfer from SD still failed, even after I applied 777 to the dir I was trying to modify. The current solution may be kind of tedious, but at least it works.
you really shouldn't do 777 on your filesystem, ANY app can then write to your system, overwrite things, or install malicious code. Just remount manually and you should be able to push anything you want, just remember that w/ the stock rom you also don't get a full busybox either.
I'm not positive, but I would think after you remount, you should be able to "adb push" to /system. I suppose it might be specific to that shell, but I would think not.
You just may have to do it once each time you boot your phone.
Edit - err nevermind... you're having permission errors.... um... change adbd on the phone to run as root? not sure how off the top of my head...
Thanks for all the help from the forum on rooting.
Titanium backup is working great on the DI.
Got Root, Manually installed Superuser, Manually install busybox. Used Titanium to install a new Busybox to the app, everything backs up great.
It's missing from the market for some reason
xvenom89 said:
It's missing from the market for some reason
Click to expand...
Click to collapse
I pulled it from the market just a few hours ago.
xvenom89 said:
It's missing from the market for some reason
Click to expand...
Click to collapse
Did you make your root persistent? You're not going to be able to see root apps if you're not rooted, I don't think.
heavensblade23 said:
Did you make your root persistent? You're not going to be able to see root apps if you're not rooted, I don't think.
Click to expand...
Click to collapse
I could see Titanium on the market before I rooted. I would check the spelling or better yet, use appbrain.com to locate it.
how did you get superuser.apk to install?
See this post for installing superuser.apk
But how did you get busybox installed so Titanium would work?
When you go into Titanium, go to the Menu -> Problems. It will prompt you to download a version of busybox that works with it.
Skapunker said:
See this post for installing superuser.apk
But how did you get busybox installed so Titanium would work?
Click to expand...
Click to collapse
After Superuser.apk and su are setup
while still in recovery root (this does not seem to work if rebooted and using persistance root and remounting /system rw),
cd /system/xbin
/system/bin/cat /sdcard/busybox > busybox
chmod 777 busybox
./busybox --install -s /system/xbin
Reboot, Run Titanium, use Problems? button to download and install a new busybox into the Titanium app
For me, Titanium would not run to a point to use the Problems button until I put a version of busybox on the phone first.
da_knowledge said:
When you go into Titanium, go to the Menu -> Problems. It will prompt you to download a version of busybox that works with it.
Click to expand...
Click to collapse
That was easy, can't believe I didn't bother to try that, thanks
Thanks for the replies
Got it working!! Great, thanks!!
I just got my Incredible rooted and installed Titanium Backup when I run it it says "BusyzBox works but the "su" command does not elevate to root:"whoami" reports "whoami:unknown uid 10108" instead of root?uid 0. I think your "Superuser Whitelist" system app does not work. Please check with your ROM provider." how do I fix this? or is it even a problem? Thanks.
same problem here
I am sure it is just a linux issue, but I am getting it too, but i am not a guru and do not know how to handle it ;-)
Can anyone explain titanium backup a little more??? Do I need to backup every app individually or just let the schedule take care of it? Which schedule option should I pick (in terms of all the options of what function you want titanium back to perform)?
I figured it out.
Just wondering, updating the version of busybox will do nothing to the root access, correct? It'll just allow titanium to work properly and root will remain?
My problem was from a not working superuser.apk. rerooted using the files from the 10min root video and now all is well. To answer the above question in regards to updating busybox, I assume you are refering to letting Titanium Backup update busybox. If so it is ok to update busybox.
Yep, that's what I was wondering. Thanks
Sent from my ADR6300 using Tapatalk
Looking at what this backs up, I am a bit curious if it can actually restore some of it. Many sections it appears to be backing up are not writable even with root access at the moment on the Dinc.
I'm guessing it will require NAND access for this to truely be useful unless I am missing something...
krelvinaz said:
Looking at what this backs up, I am a bit curious if it can actually restore some of it. Many sections it appears to be backing up are not writable even with root access at the moment on the Dinc.
I'm guessing it will require NAND access for this to truely be useful unless I am missing something...
Click to expand...
Click to collapse
That was the main purpose of me getting titanium, i'm not expecting to have the need to restore anything until i flash a custom rom. Having the backup now is awesome because i know i won't lose anything once they figure out how to unlock NAND and flash a recovery and roms
when i'm in recovery mode trying to gain persistant root i get an error.
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
when in Titanium and I hit the "problems ?" button it downloads busybox, but says it failed because it doesn't have root.
any help?
i am rooted, downloaded a file manager..which file did they store the factory apps in
system/app is where the apps are delete the odex file too if you decide to delete any apps. make sure you dont delete anything that the phone needs to run. if you dont know what to delete then dont delete anything!!! if you decide to delete anything from system/app you also need to delete another folder that has to do with the app in data/data. for example say you wanna delete bluetooth go to system/app and delete bluetooth.apk and the bluetooth.odex files then go to data/data and delete com.android.bluetooth folder. thats an example dont do that as you will no longer have bluetooth lol but same thing for whatever app you delete except the folder in data/data will be different
Whats wrong with factory apps?
lou0611 said:
Whats wrong with factory apps?
Click to expand...
Click to collapse
That's like when you get a new HP Laptop and they throw all this bloat-ware that you don't need.
Why use the ''TeleNav GPS'' when the Google Navigation is free?
And are you really going to use that Slacker or GoGo app? Not likely.
Root, install Titanium backup, installed busybuzz or whatever (Hit the Problems? button in TB), BACKUP all your apps, then delete whatever you dont want
i got rid of Telenavi, GoGo, MobiTV and i think one other.....i never would use them so there was no reason to keep them.
You can also do this via adb shell like this:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
After you've mounted the correct partition you can pull up a complete list of apps with this command:
ls /system/app
Then, remove apps with this command. The apps name are case sensitive to make sure you type the app name as its displayed:
rm VoiceSearch.apk
Dont even need to mount.
Use VoiceSearch.* instead of apk to get rid of the .odex file also.
bubonik said:
Dont even need to mount.
Use VoiceSearch.* instead of apk to get rid of the .odex file also.
Click to expand...
Click to collapse
Good suggestion. Never thought of that, kill two birds with one stone.
bubonik said:
Dont even need to mount.
Use VoiceSearch.* instead of apk to get rid of the .odex file also.
Click to expand...
Click to collapse
What do you mean by this?
phragg said:
What do you mean by this?
Click to expand...
Click to collapse
if you use "rm VoiceSearch.*" * is seen as a wild card so it deletes every file named VoiceSearch with any extension so it will delete VoiceSearch.apk and VoiceSearch.odex
This might have something to do with why I can't mount my drives on any computer:
When I tried to mount via adb, this was my output:
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
Any suggestions?
cashless said:
This might have something to do with why I can't mount my drives on any computer:
When I tried to mount via adb, this was my output:
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
Any suggestions?
Click to expand...
Click to collapse
Are you rooted? You need to be rooted in order to get access to those file systems. If you are rooted, then type 'su' (don't include the quotes), then you'll get a #. Now start entering the commands.
Also make sure that when you enter the commands (via adb) your screen is not locked, so that you can allow the SU app to grant superuser status.
Hi, I installed ClockworkMod recovery installing Droid 2 Bootstrapper to make changes that I did. From now on every startup I get ClockworkMod recovery, can I remove it or make it appear only on request?
thanks
If you unnistall the droid2bootstrapper app you'll always get to recoveryon boot. Just reinstall the app.
Or, if you wanna delete it, do it in the Terminal Emulator/ADB Shell:
su
busybox mount -o remount,rw /system
rm /system/bin/hijacker
rm /system/bin/logwrapper
mv /system/bin/logwrapper.bin /system/bin/logwrapper
Sent from my Milestone 2 XDA App
Thanks! I did it with Root Explorer and it worked!
Moved to general as not android development.
I have the Verizon VS995 LG20 and rooted via DirtySanta a couple weeks ago. I recently have lost root privilege with Titanium Backup. Root on other apps is fine. The issue may be related to changes I made a week ago in trying to get root access for Secure Settings plugin for Tasker. Secure Settings doesn't work with systemless root. I have tried uninstalling and reinstalling both the su app and Titanium Backup, but I keep getting the same error:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I would appreciate any suggestions in how I can fix this. I would like to make a backup before trying some new roms.
I just ran into this same exact problem. I removed the su files I created in order to get Secure Settings working and Titanium Backup now works. But why did Titanium Backup start having a problem with this all of a sudden and what is the true solution?
Here's what I did to fix Secure Settings from adb shell:
su
mount -o rw,remount /system
touch /system/bin/su /system/xbin/su
mount -o ro,remount /system
So I fixed the problem by just removing the su files. However I want both Secure Settings and Titanium Backup working!!!
TheShanMan said:
I just ran into this same exact problem. I removed the su files I created in order to get Secure Settings working and Titanium Backup now works. But why did Titanium Backup start having a problem with this all of a sudden and what is the true solution?
Here's what I did to fix Secure Settings from adb shell:
su
mount -o rw,remount /system
touch /system/bin/su /system/xbin/su
mount -o ro,remount /system
So I fixed the problem by just removing the su files. However I want both Secure Settings and Titanium Backup working!!!
Click to expand...
Click to collapse
I had a similar issue - TB stopped obtaining root after a kernel change - don't know why. I solved it by changing the su 'dummy' file in /system/bin/su (TB was trying to use this) to a symbolic link pointing at the real su:
Code:
[email protected]:/su # rm /system/bin/su
[email protected]:/su # ln -s /su/bin/su /system/bin/su
Rebooted and TB and SecureSettings can now use root.
Not having this problem but TB does force close alot on me. It started when rom toolbox pro deactivated app manager. Maybe TB has something to do with the dev?