Right, I finally rooted my Desire today via revoked and would like to remove some of the preinstalled apps. I did try searching, but couldn't find a clear solution.
Basically I want to get rid of calculator, friendstream, peep, footprints and quickoffice. Can I just delete the .apk and .odex files or should I use adb? Also, are these apps integrated with eachother in a way that would cause problems with other apps? Any help would be appreciated
U can delete them, ive do this alway before i flash a rom ;-)
You have to do it via adb as if you try when the phone is on the apps will just reappear.
Cool, so just the files from /system/app then? I'm generally good with this kind of thing on PCs, but never tried it on Android before.
Edit: Thanks for the adb advice too
I used this thread for reference...
http://android.modaco.com/content/h...apps-from-the-htc-desire-with-adb-in-windows/
If i try to remove stocks apk and odex, syncronisation parameter crash because it can find stocks, any way to fix it ? Thank you
Sent from my HTC Desire using XDA App
First command line give me that:
Code:
Tof162$ ./adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Second one:
Code:
./adb shell rm /system/app/teeter.apk
rm failed for /system/app/teeter.apk, Directory not empty
After a second try:
./adb shell rm /system/app/teeter.apk
rm failed for /system/app/teeter.apk, Read-only file system
By the way, I don't understand why there is not an "app for that" that need root access.
Any problem or impossibility to program that?
You don't have write access to system partition in normal use even if it's rooted, you have to be in custom recovery. or delete it from the downloaded rom and flash it again
ephumuris said:
I used this thread for reference...
http://android.modaco.com/content/h...apps-from-the-htc-desire-with-adb-in-windows/
Click to expand...
Click to collapse
nice one for linking to my thread...XD
that works but the better way is to modify the rom pre-install, that way you dont end up with junk information in certain places
codeXcalibur said:
You don't have write access to system partition in normal use even if it's rooted, you have to be in custom recovery. or delete it from the downloaded rom and flash it again
Click to expand...
Click to collapse
When I am in Recovery, the device is not detected...
you need to be in custom recovery, not in "normal" htc recovery
And check your spelling when using ADB even the capital letters in files and paths are important.
And have a backup of the original .zip file if your removing the files directly from zip file. I had mine get corrupted and unable to flash forcing me to restore a Nandroid.
codeXcalibur said:
you need to be in custom recovery, not in "normal" htc recovery
Click to expand...
Click to collapse
I guess that the recovery of Unrevoked 3 is a custom recovery ;-)
I flashed a lot of ROMS on my Desire and succed to enter adb on any moment when the device is ON.
Unfortunately, in recovery, no phone detected.
I am now in recovery. Finally detected the device but got this message:
Tof162$ ./adb shell mount /system
mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy
Click to expand...
Click to collapse
It's a LOT easier to remove everything before you flash the ROM and then resign the ZIP using the package on here somewhere (that's what I do)
You should be OK removing FriendStream, I leave it in and just remove the widget so dunno if it'd FC the OS, but the other files can just be removed as I also remove them
EddyOS said:
It's a LOT easier to remove everything before you flash the ROM and then resign the ZIP using the package on here somewhere (that's what I do)
You should be OK removing FriendStream, I leave it in and just remove the widget so dunno if it'd FC the OS, but the other files can just be removed as I also remove them
Click to expand...
Click to collapse
could you pls point me the thread on how to sign zip files?
Sent from my HTC Desire using XDA App
profete162 said:
First command line give me that:
Code:
Tof162$ ./adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Second one:
Code:
./adb shell rm /system/app/teeter.apk
rm failed for /system/app/teeter.apk, Directory not empty
After a second try:
./adb shell rm /system/app/teeter.apk
rm failed for /system/app/teeter.apk, Read-only file system
Click to expand...
Click to collapse
Try in recovery
bradputt said:
could you pls point me the thread on how to sign zip files?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
there is no need to sign it
and it's even easier if your are using such script ..
Code:
@echo off
set zip="C:\Program Files\7-Zip\7z.exe"
set todelete=
set todelete=%todelete% /data/app/Facebook.apk /data/app/Twitter.apk'
set todelete=%todelete% /data/app/YouTube.apk'
set todelete=%todelete% /system/app/CarHomeGoogle.apk
set todelete=%todelete% /system/app/CarHomeGoogle.apk
set todelete=%todelete% /system/app/CarHomeLauncher.apk
set todelete=%todelete% /system/app/DeskClockGoogle.apk
set todelete=%todelete% /system/app/GoogleQuickSearchBox.apk
set todelete=%todelete% /system/app/Launcher2.apk
set todelete=%todelete% /system/app/Maps.apk
set todelete=%todelete% /system/app/VisualizationWallpapers.apk
REM set todelete=%todelete% /system/app/LiveWallpapersPicker.apk
set todelete=%todelete% /system/app/VoiceSearch.apk
set todelete=%todelete% /system/app/LiveWallpapers.apk
set todelete=%todelete% /system/app/MagicSmokeWallpapers.apk
set todelete=%todelete% /system/app/Calculator.apk
set todelete=%todelete% /system/app/ChrometoPhone.apk
set todelete=%todelete% /system/media/bootanimation.zip
set todelete=%todelete% /system/tts/lang_pico/de-DE_gl0_sg.bin
set todelete=%todelete% /system/tts/lang_pico/de-DE_ta.bin
set todelete=%todelete% /system/tts/lang_pico/en-US_lh0_sg.bin
set todelete=%todelete% /system/tts/lang_pico/en-US_ta.bin
set todelete=%todelete% /system/tts/lang_pico/es-ES_ta.bin
set todelete=%todelete% /system/tts/lang_pico/es-ES_zl0_sg.bin
set todelete=%todelete% /system/tts/lang_pico/it-IT_cm0_sg.bin
set todelete=%todelete% /system/tts/lang_pico/it-IT_ta.bin
REM DELETE
%zip% d update.zip %todelete% -r
REM ADD
%zip% a update.zip ./data
%zip% a update.zip ./system
Related
I just installed the Modaco ROM on my Desire (It is awesome BTW) but i don't like the WaveSecure program and i can't seem to be able to find it in /system/app to remove it!
Is there a way to delete this program off the phone!?
I would like to learn how to do this also
Don't think you can unless you use the online kitchen (I don't like it so removed it from mine)
I believe:
adb remount
adb shell rm /system/app/com.wsandroid.apk
Click to expand...
Click to collapse
Doesn't seem to work mate.
Code:
C:\DevTools\android-sdk-windows\tools>adb remount
remount succeeded
C:\DevTools\android-sdk-windows\tools>adb shell
# rm /system/app/com.wsandroid.apk
rm /system/app/com.wsandroid.apk
rm: can't remove '/system/app/com.wsandroid.apk': Directory not empty
#
plasmafire said:
Doesn't seem to work mate.
Code:
C:\DevTools\android-sdk-windows\tools>adb remount
remount succeeded
C:\DevTools\android-sdk-windows\tools>adb shell
# rm /system/app/com.wsandroid.apk
rm /system/app/com.wsandroid.apk
rm: can't remove '/system/app/com.wsandroid.apk': Directory not empty
#
Click to expand...
Click to collapse
Running as admin?
Same here. Running as admin - nevertheless "Directory not empty"
Edit: solved. Run SUBFS on phone and mounted /system RW. After that tried again in cmd - voila!
Insomnious said:
Same here. Running as admin - nevertheless "Directory not empty"
Edit: solved. Run SUBFS on phone and mounted /system RW. After that tried again in cmd - voila!
Click to expand...
Click to collapse
+1
For noobs like me: It's actually SUFBS, not SUBFS. Google for the apk, install the app, in the menu there's an option "mount /system RW". Activate and then run the adb commands above in a cmd window on your PC. Et voila!
(Just realised this is a Desire thread, this worked for me on my Nexus too)
how would one add an mp3 file to the read only directory
( system/media/audio/alarms )
the stock ones really don't wake me up
from what i do know the directory is a read only directory and really would like to
put this alarm.mp3 in the that read only folder...
appreciate your help and thanks in advance...
I highly suggest you buy the app "root explorer"
would astro do the same thing?...
Sent from my PC36100 using XDA App
are you fully rooted? if not, i know the answer.
I think I am...how would one confirm?... appreciate your help
Sent from my PC36100 using XDA App
if you have the android sdk set up use "adb remount". It should say something like partition remounted successfully. If you see that then all of your read only directories will be reset to read/write. Afterwards just reboot your phone and it will set everything back to normal.
thank you.....i tried that command and received this error:
remount failed: Operation not permitted
does this mean that I'm not fully rooted? what next?
appreciate your help xHausx ...
1candydick said:
thank you.....i tried that command and received this error:
remount failed: Operation not permitted
does this mean that I'm not fully rooted? what next?
appreciate your help xHausx ...
Click to expand...
Click to collapse
could be, do you have the superuser app in your app drawer? a few more things you can try is typing:
adb shell {enter}
mount system {enter}
at this point you will see either a $ or # sign, the # sign means you have root. If you see the $ type:
su {enter}
if that doesn't change it to a # then try typing
sh0 {enter}
su {enter}
if that still doesn't work then you need to use an exploit to get root. However, if it does work and you see # then type:
mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system {enter}
You can put these on your SD card too, you just have to put it in /media/audio/alarms (you can also use "notifications" or "ringtones" instead for those).
mv and chmod should work
Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
EDIT: Go to 3rd post.
kpaekn said:
Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
If you're wanting to root, go straight to the source; the guide in the Wiki here is based on the work the devs who actually found the means to root the device.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Is USB debugging turned on and is the SDcard not mounted?
Sent from my T-Mobile G2 using XDA App
Sounds like the SD card is mounted on your PC and not the phone ? It needs to be mounted on the phone or this won't work.
Sent from my HTC Desire Z
All that command does is copy that file from your computer to the sdcard. You could accomplish the same thing by dragging and dropping that file to the sdcard.
The 'push' command just means "copy from location A to location B"
Sent from my HTC Vision using XDA App
You could always just mount the SDcard... but anyway, to solve this type in "adb remount" and enter the command before pushing the file
Sent from my HTC Vision using XDA App
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
kpaekn said:
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
The adb remount error is expected (the command requires your ro.secure prop to be set to 0, which you can't do until you have rooted).
So you were able to copy files to the SD card? Just to verify again, you should try mounting the SD card to you computer (so it shows up as a device on your computer's file explorer), copy over a file, unmount the card from your computer (and remember to also hit the button on phone to do so), and then try the ADB push commands again.
Ok, with the phone on plug it into your computer and mount USB storage. Drag and drop 'su' and superuser.apk into the sdcard then unmount USB storage. Make sure USB debugging is on at this point (you'll see it in the notification task bar). Do these commands:
Code:
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/*
Then in the terminal app type:
Code:
/data/local/tmp/rage
You'll see some message pop up saying something about 'forked #### childs' and that's temp root. Then follow the instructions on running gfree to gain full root. Btw, you can just copy and paste all those commands if you think you'll make a mistake.
You may also be able to run the '/data/local/tmp/rage' command with the 'adb shell' command, never tried it myself though.
kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Oh come on !!!
the path separator in linux (and the phone is a linux computer) is / and not \ !!!
So the command is:
Code:
C:\AndroidSDK\tools>adb push su /sdcard/su
Just to tell you something about the unix shell:
The \ char is a so called escape character that you use to tell the shell that it should not ignore the next character even if it is a white space (i.e. space)
You would use it if you have to specify a path that contains spaces:
i.e.:
Code:
mkdir dir\ with\ 3\ spaces
will create a directory with the name "dir with 3 spaces". This would not work without the \ characters.
have fun - Guhl
Haha... it's funny how simple the answer was.
Thanks for your guys' help.
Hello folks,
I have a Wildfire, running CM7 #36, Jacob's 4.1 Kernel flashed.
Now I wanted to edit the /system/build.prop to get access to further apps (rom manager pro, e.g.).
After remounting system via
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
I wanted to copy/remove or whatever the /system/build.prop, but I only get
# rm /system/build.prop
rm: can't remove '/system/build.prop': Directory not empty
What does this mean? /system/build.prop is surely not a directory (ls -al).
Any help would be appreciated - can't post in the development-forums because of unsufficient number of posts - thanks,
Guntram
Don't remove it...
Pull build.prop using adb, edit and push it back to /system
Sent from my HTC Wildfire using XDA App
Hello Kevin1625,
unfortunately, this gives the same message (which I don't understand anyways?):
Code:
$ adb push build.prop /system
failed to copy 'build.prop' to '/system/build.prop': Directory not empty
Any ideas?
Are you doing this via terminal??
Adb is used on your computer.
Sent from my HTC Wildfire using XDA App
Mount system via recovery.
Open a cmd
cd into your tools folder
adb pull /system/build.prop
Edit it.
adb push build.prop /system/build.prop
adb reboot
I think youre trying to adb shell, there is no need.
Sent from my HTC Wildfire using XDA App
Thanks kevin2516 (what are these numbers for?)!
Seems, that build.prop is somehow blocked, when trying to access it on the running phone.
When I adb push on the mounted /system in recovery, everything seems to work fine.
Except, that I don't get the wanted result (Rom Manager Premium in the market) :-(.
Did you got it running, using SympMarket (which only once gave me >4000 video results - but I'm not able to reproduce ;( )?
If so, do you remember how?
Thanks a lot,
Guntram
thank you so much man! saved my phone after i accidently set PPI to 280 :L
and you should also adb shell chmod 644 /system/build.prop
Device says that system directory can not be accessed when pushing the file
I was in the middle of a nandroid backup, and accidentally entered "adb shell", then exited.
But now, even after power off and reboot, when I "adb shell" I get a prompt that looks like this:
Code:
/ #
instead of the usual
Code:
#
ls gives:
Code:
/ # ls
cache etc proc sd-ext tmp
data init res sdcard
default.prop init.rc root sys
dev mtdcache sbin system
"adb logcat" returns
Code:
/sbin/sh: exec: line 1: logcat: not found
"adb remount" gives
Code:
remount failed: Invalid argument
What is that slash?! It's scary! Is something wrong?
HELP!
When are you running adb shell? What ROM? Details!
The / # means 1) You're in the root folder ("/") and 2) You're the root user ("#").
drmacinyasha said:
When are you running adb shell? What ROM? Details!
The / # means 1) You're in the root folder ("/") and 2) You're the root user ("#").
Click to expand...
Click to collapse
There is no ROM -- I just wiped!
I've never seen the "/" before ... what would make it suddenly appear?
you mean in recovery? that means you're in recovery.
It's fine. Mine does that too when I'm in recovery. Flash something and move on.
drmacinyasha said:
When are you running adb shell? What ROM? Details!
The / # means 1) You're in the root folder ("/") and 2) You're the root user ("#").
Click to expand...
Click to collapse
This. Yes it is an indicator of your current location within the filesystem. Think of it as a reminder when you perform file operations (say you want to delete all the files in the /crap folder but you forget to to a 'cd crap' before the rm command... yes it would be bad)
I know that in most *nix systems, the "/" means root folder ... but I've been using adb for 2 years now and I've never seen my prompt change to anything other than "#".
Even if I cd to another directory, the prompt doesn't change ... it's still "/ #". And if "/" were the current dir, I would think it would be "# /" and then change when I changed dir...
Now the "/" is gone, but when I "ls", the listing is all in a single column, rather than tabbed across the screen.
I'm just baffled why my shell would change randomly like this when I haven't done anything besides wiping ...
d0g said:
I know that in most *nix systems, the "/" means root folder ... but I've been using adb for 2 years now and I've never seen my prompt change to anything other than "#".
Even if I cd to another directory, the prompt doesn't change ... it's still "/ #". And if "/" were the current dir, I would think it would be "# /" and then change when I changed dir...
Now the "/" is gone, but when I "ls", the listing is all in a single column, rather than tabbed across the screen.
I'm just baffled why my shell would change randomly like this when I haven't done anything besides wiping ...
Click to expand...
Click to collapse
yea it's recovery. it always does that when i'm in recovery.