Related
Ive done this before and for the life of me i cannot remember how to do this, and ive been searching xda and google for a half hour now, can anybody help me out. How do you remove stock apps via adb?
Thanks guys
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/app
# rm xxx.apk
Replace xxx with app names. Case sensitive.
Edit: ignore $ and # when typing the commands
well this is weird, i know i have root but when i try those commands thru cmd on pc, i get error sh-3.2 it won't let me su but when i do it in terminal on phone it works fine
androidtoy09 said:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/app
# rm xxx.apk
Replace xxx with app names. Case sensitive.
Edit: ignore $ and # when typing the commands
Click to expand...
Click to collapse
Do I need to remove the odex files as well?
Sent from DynamikD's R00t3d & OC G2
Advisable to, yes. Also, reboot and clear cache in recovery for best results.
What is the command to list "dir" to get the app names? I've done this on my mytouch3g as well but rusty
Edit: It's "ls" lol.
Ok, so I just attempted this and get this error:
rm failed for Twitter.apk, Read-Only file system
Click to expand...
Click to collapse
And I also would like to remove these:
amazonmp3.apk
Email.apk
com.google.android.apps.finance-1.apk
Web2GoShortcut.apk
Twitter.apk
Web2GoShortcut.odex
Email.odex
What is a .odex file?
Sent from my T-Mobile G2 using XDA App
Make sure is not a typo.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Anyone know the name of the photobucket APK?
So now that we have Perma-ROOT, is it safe to delete these bloatwares without worrying about future OTA's?
And what's a .odex file? How do we delete this? Can we just delete these apps thru Titanium Backup and then boot into Recovery to clear cache?
*EDIT* - n/m i see how to delete the .odex files now
What's the .apk name for Photobucket?
*EDIT* - Got it... it's PbAndroid.apk
Need help!
Well those are the commands to remove a app how do you push a apk file back onto the /system/app. I want to push a Bluetooth.apk file from the old ROM to the new OTA and see if that helps with the Bluetooth issue I'm having with the new OTA.
If your perma rooted why not just install titanium backup and uninstall the app. If your temp rooted then you can only disable the app cuz if you delete the apps it'll only reappear after a reboot.
Becuz titanium does not let u remove apps, if it was that easy I think everyone would do it
fryrice8850 said:
Becuz titanium does not let u remove apps, if it was that easy I think everyone would do it
Click to expand...
Click to collapse
It doesn't? Then what the heck does titainium do when I press uninstall? This is a serious question.. not sarcasm.
Sent from my T-Mobile G2 using XDA App
Nvm u need to select "problems" and it will download busybox on ur g2 and then u can uninstall stock apps...
fryrice8850 said:
Nvm u need to select "problems" and it will download busybox on ur g2 and then u can uninstall stock apps...
Click to expand...
Click to collapse
Then it really is that easy... and everyone should do it.
Sent from my T-Mobile G2 using XDA App
how would the remount command change for the MyTouch4G?
nemesys571 said:
how would the remount command change for the MyTouch4G?
Click to expand...
Click to collapse
Don't think it would.
BTW you can also try this remount command for either, I was advised that it's preferable to use and it's certainly easier:
mount -o remount, rw /system
If you were like me, you rushed right into installing CyanogenMod. Whoops, found out there is no swype installed. What to do?
Hopefully you made a nandroid backup like me. I didn't want to do a full nandroid restore just to extract the files. So I did this...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
UPDATED 11/22/2010 - Okay, some people have requested a "newbie friendly" solution. I have created an APK which will help automate this procedure, without the need for ADB. If you have already applied CyanogenMod, then use this APK to select an older Clockwork Backup that has your licensed Swype. It will then extract and install the files for you. I have only tested on the G2.
http://www.mediafire.com/?j7dnv321ej0mrch
I'll possibly do some updates to:
a) cache swype for future installs (to make restores super quick)
b) add other extractions of 'your' saved files (i.e. google apps)
c) add more options for handling cache/files/etc.
I hope this helps. Enjoy!
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
# --------------------------------------------------------------------------------------------
# How to recover your swype files from your nandroid backup
# Quick and dirty extract
# Prepare a staging area on your computer
mkdir nandtmp
cd nandtmp
# Copy your old nandroid (pre CM) backup to your staging area..........
# i.e. /androidbackups/clockworkmod/backup/2010-11-01.02.02.02
cp $WHEREVER_OLD_IMAGE_IS/system.img .
# extract files...
unyaffs system.img
adb remount
# Push the swype files back to your Android device
adb push ./system/lib/libSwypeCore.so /system/lib/
adb push ./system/app/Swype.apk /system/app/
# Some users have had issues with not seeing Swype in the options (possibly non read/write system?), so they just installed the APK. If you install it, make sure the lib file has been pushed first.
# i.e. adb install /sdcard/Swype.apk
# Update permissions for good measure (may not be needed)
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.so
# I rebooted, but have heard reports that it is not necessary
adb reboot
# Now in Menu>Settings:Language & keyboard unselect the Android keyboard and make sure Swype keyboard is checked.
A similar process can be done directly on your phone.
# --------------------------------------------------------------------------------------------
Hope that helps others restore Swype (or other files they desire) without having to do a full Nand restore.
-oldsk00lz
getting force close on swype as soon as I uncheck the android keyboard, not a huge deal but I do kinda miss swype
ranyvern said:
getting force close on swype as soon as I uncheck the android keyboard, not a huge deal but I do kinda miss swype
Click to expand...
Click to collapse
Did you push libSwypeCore.so to /system/lib yet?
For some reason it still doesn't show up in the keyboard list, any idea why?
Sent from my T-Mobile G2 using XDA App
Ok, what you're supposed to do is, you actually have to install the swype.apk. its not enough to copy it to the /system/app directory adb install Swype.apk or use root file explorer click on the apk file and choose install.
Sent from my T-Mobile G2 using XDA App
or you can open up cyanogenmod(unzip) and download a stock g2 rom and then just put the files in the proper places, then zip cm again and flash(i did this all from my phone ast night because i was too lazy to go to the computer)
have you tried to go to swype.com and signing up for there beta testing. Not sure if still open but does not hurt to try. I reinstall from the beta testing website and is working great on CM6.1 on my G2
k50aker said:
For some reason it still doesn't show up in the keyboard list, any idea why?
Click to expand...
Click to collapse
Be more specific. What have you done so far? Did you go into Settings > Keyboard and enable Swype yet?
I tried a few times before but could never get this dumb unyaffs to work for me.
i get
Microsoft Windows XP [Version 5.1.2600]
C:\g2orgsys>unyaffs systemg2.img
28852 [main] unyaffs 3212 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
30677 [main] unyaffs 3212 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
348883 [main] unyaffs 3212 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
375003 [main] unyaffs 3212 _cygtls::handle_exceptions: Error while dumping stat
e (probably corrupted stack)
Idk im pretty lazy sometimes, if you can provide some help on this, i would GREATLY appreciate it.
oh and I tried, quickly, to get the emulator working but failed! Im sure its probably something ez I missed. :/
Stryder5 said:
Be more specific. What have you done so far? Did you go into Settings > Keyboard and enable Swype yet?
Click to expand...
Click to collapse
Yea, it wasn't there, again, in my case pushing it in to the /app folder did NOT work, I had to intall the apk maually like any other app. Of course only after pushing the lib file.
adb push libSwypeCore.so /system/lib
adb install Swype.apk
Unyaffs is supposed to work on windows? I didn't know that. I use linux, you sould try it and get used to it, it would save you a lot of trouble.
Sent from my T-Mobile G2 using XDA App
k50aker said:
Yea, it wasn't there, again, in my case pushing it in to the /app folder did NOT work, I had to intall the apk maually like any other app. Of course only after pushing the lib file.
adb push libSwypeCore.so /system/lib
adb install Swype.apk
Unyaffs is supposed to work on windows? I didn't know that. I use linux, you sould try it and get used to it, it would save you a lot of trouble.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hmmm... I saw the swype in the settings after doing adb pushes and a reboot.
In reality, I had unchecked both Android keyboard, and Swype keyboard. Then went to a text field, and got a request for Android input. I then went back into settings and checked Swype, and then it just worked. I didn't need to install the APK. For those not seeing swype as an option, did you confirm that system was remounted and that files were copied? Did you reboot?
As for unyaffs, I was lazy. I just downloaded a binary for OSX from here: http://forum.xda-developers.com/showthread.php?p=7931772 . I haven't tried a Windows version of unyaffs.
-oldsk00lz
k50aker said:
Unyaffs is supposed to work on windows? I didn't know that. I use linux, you sould try it and get used to it, it would save you a lot of trouble.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
thats kinda sucks. lil more trouble then I was hoping for but I got a few LiveCDs somewhere.
How hard would it be to get this running through adb shell, on the phone? lol
wilnotdie said:
thats kinda sucks. lil more trouble then I was hoping for but I got a few LiveCDs somewhere.
How hard would it be to get this running through adb shell, on the phone? lol
Click to expand...
Click to collapse
wilnotdie - You should be able to do this directly on your phone, as well. Of course, you would need to mount your system read/write and cp files versus adb push.
i.e.
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp /sdcard/nandtmp/system/lib/libSwypeCore.so /system/lib/libSwypeCore.so
cp /sdcard/nandtmp/system/app/Swype.apk /system/app/Swype.apk
Hope that helps.
-oldsk00lz
oldsk00lz said:
wilnotdie - You should be able to do this directly on your phone, as well. Of course, you would need to mount your system read/write and cp files versus adb push.
i.e.
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp /sdcard/nandtmp/system/lib/libSwypeCore.so /system/lib/libSwypeCore.so
cp /sdcard/nandtmp/system/app/Swype.apk /system/app/Swype.apk
Hope that helps.
-oldsk00lz
Click to expand...
Click to collapse
Oh mybad, not that way. Was thinking of using the phone as my linux box instead of a pc. In theory it should work, just need to compile for use on the phone?
But Im guessing its not gonna be this ez lol
I didn't do any ADB pushes I just used root explorer to move the libswype file to lib directory then used the installer on the root explorer to install and it loaded right up for me. Only problem I'm getting is the double tap to edit isn't working now for some reason.
I pulled the files from the ota_root_noboot.zip from
http://forum.xda-developers.com/showthread.php?t=836042
Okay here is what I did and it worked. Using SU File manager (found in the market if you search "root explorer") and on the stock ROM, copy the lib and apk files from /system/app and /system/lib. I copied them to the root of my sd card. Wipe everything and install CM and the addon. Grab SU File manager again and find the lib file on your SD card. copy it. There are two little buttons on the top of SU File manager with an S and a D. I pressed both of them to mount system and data as read/write. Go to system/lib and paste the lib file. Verify that it is there and since there are so many files sort by size its like 998kb. Then just use SU File Manager or astro or whatever to find Swype.apk on your sd card. Install it from there. With Astro click it and "open app manger." Then go to keyboard settings and enable it as an input method. Go to swype settings and it should not FC if you did this stuff correctly. Set your settings and enjoy! Oh yea dont forget to uninstall and refund SU File manager
Hey Jkoenig00 did you have any issues with the double tap to edit?
Worked flawlessly and now I have swype running on CM. This should be stickied or something!
So for those of us who don't know what ADB is or how to use it...
are we screwed?
Is there a noob friendly method?
convolution said:
So for those of us who don't know what ADB is or how to use it...
are we screwed?
Is there a noob friendly method?
Click to expand...
Click to collapse
You can use root explorer. Download one of the stock roms. Access it through root explorer and copy the 2 files from the stock rom folders to its respective folder on your device. Then install the apk from within root explorer. Set everything up in your keyboard settings and your golden. Can be done in minutes.
Sent from my T-Mobile G2 using XDA App
Hello, I was recently able to upate my A100 to ICS. I followed the root instructions in the developer section and it worked great. Both Titanium Backup and Superuser say I'm rooted but I can't move/rename the wpa_supplicant file. I really need to be able to use ad hoc to tether to my phone. Did I do something wrong in rooting my tablet? Any help would be much appreciated.
Thanks.
You need to mount system as r/w. Which file manager are you using?
Sent from my LG-P999 using Tapatalk 2
How do I enable that? I'm using Root Browser, I never had to do that before in HC...it just worked lol. Thanks for the help.
DravenAcer said:
How do I enable that? I'm using Root Browser, I never had to do that before in HC...it just worked lol. Thanks for the help.
Click to expand...
Click to collapse
I personaly used Root Explorer, its free and it has a friendly little buttong that has R/o R/W which allows you to read only to read and write
I redid the root and reinstalled Superuser, Root Browser, Titanium and Terminal...they all I'm rooted but when I try to move or rename the wpa_supplicant file it says failed. When I try to mount on Terminal it says it can't because I don't have root. What's going on lol? Did I do something wrong or is my version of ICS incompatible with the rooting method? Please help...
DravenAcer said:
I redid the root and reinstalled Superuser, Root Browser, Titanium and Terminal...they all I'm rooted but when I try to move or rename the wpa_supplicant file it says failed. When I try to mount on Terminal it says it can't because I don't have root. What's going on lol? Did I do something wrong or is my version of ICS incompatible with the rooting method? Please help...
Click to expand...
Click to collapse
I noticed the same problem with Root Browser. It is probably not using the standard /system/bin/mount or /system/xbin/mount. Also it may be ZeroNulls mount script not taking in account for all possible mount scenarios. You could try my mount script in this thread forum.xda-developers.com/showthread.php?t=1512787 and replace your /system/bin/mount and /system/xbin/mount.
If you are sure it's rooted then remounting from a terminal will work. Are you typing su before trying to remount?
If you are and it still doesn't work try this instead
Code:
$ su
# mount -o remount,rw /dev/block/mmcblk0p3 /system/
BTW root explorer is not free
eww245 said:
I noticed the same problem with Root Browser. It is probably not using the standard /system/bin/mount or /system/xbin/mount. Also it may be ZeroNulls mount script not taking in account for all possible mount scenarios. You could try my mount script in this thread forum.xda-developers.com/showthread.php?t=1512787 and replace your /system/bin/mount and /system/xbin/mount.
If you are sure it's rooted then remounting from a terminal will work. Are you typing su before trying to remount?
If you are and it still doesn't work try this instead
Code:
$ su
# mount -o remount,rw /dev/block/mmcblk0p3 /system/
BTW root explorer is not free
Click to expand...
Click to collapse
Thanks for your help. I didn't know I had to type 'su' first lol. That worked...kinda. Because I have to retype that everytime I rename or move something. Is that some kind of bug in the script?
DravenAcer said:
Thanks for your help. I didn't know I had to type 'su' first lol. That worked...kinda. Because I have to retype that everytime I rename or move something. Is that some kind of bug in the script?
Click to expand...
Click to collapse
Yes that is a bug in the script. Using my mount script Root Browser is able to modify /system files.
Looks like the old wpa_supplicant file isn't working. I did a search but haven't found any yet that work. Has anyone been able to activate ad-hoc on their A100 with ICS?
eww245 said:
Yes that is a bug in the script. Using my mount script Root Browser is able to modify /system files.
Click to expand...
Click to collapse
Yes, that worked great! Thank you.
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.
Hello all,
I'm trying to delete a system file using the Android terminal (as my end goal is to put it in a run shell task in Tasker) and it either reboots my phone or just doesn't delete.
Long story short, I'm using the Weak Sauce root method, but I do not have S-Off as I like how easy it is to undo the Weak Sauce root alone. This means, of course, I don't have immediate RW access to system. So here's what I've done:
Code:
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p46 /system
# busybox rm -f /system/media/audio/ui/camera_click.ogg
# mount -o ro,remount -t yaffs2 /dev/block/mmcblk0p46 /system
When I do the first and last commands alone, the system mounts as RW and RO correctly, confirmed with # mount|grep system. But that middle command is the problem. Sometimes nothing will happen, other times my phone will reboot. I've also tried adding the following before the rm command with no success:
Code:
# chmod 777 /system/media/audio/ui/camera_click.ogg
I AM able to delete the file manually through ES File Explorer when mounted RW. But it comes back after I restart my phone, hence why I want this command to be used in Tasker.
What am I doing wrong?
PS: as for the "why" of deleting the shutter sound file, I take screenshots sometimes and the sound drives me nuts. I've tried removing the ogg file from the camera apk, but that didn't work after a reboot. I also tried replacing the ogg file with a silent one, but no success there either as the real one reloads itself when I restart.
Delete the file in recovery using TWRP
Sent from my HTC One_M8 using Tapatalk
SmiLey497 said:
Delete the file in recovery using TWRP
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'm trying to do it from the terminal so I can eventually put it into Tasker. I can delete it successfully with ES File Explorer, so no need for recovery. I just need some way to get it to work through the terminal.
If the file is coming back then you don't have proper write access to system and the file isn't actually being deleted which Is why it appears to come back.
Try using root explorer instead or do it through TWRP. Make system RW then just move or rename the file rather than delete it. If you have proper write access it will stick.
heather1209 said:
I'm trying to do it from the terminal so I can eventually put it into Tasker. I can delete it successfully with ES File Explorer, so no need for recovery. I just need some way to get it to work through the terminal.
Click to expand...
Click to collapse
It comes back when you reboot. Your system is not writable you need to S-OFF. get system RW kernel, or delete through recovery.
SmiLey497 said:
It comes back when you reboot. Your system is not writable you need to S-OFF. get system RW kernel, or delete through recovery.
Click to expand...
Click to collapse
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
heather1209 said:
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2701816
heather1209 said:
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
Click to expand...
Click to collapse
[KERNEL] [June 20] [Sense] [GPE] ElementalX 0.19 I think that'll work on stock Sense system.
heather1209 said:
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
Click to expand...
Click to collapse
He means flash a kernel that has write access to system enabled.
SmiLey497 said:
http://forum.xda-developers.com/showthread.php?t=2701816
Click to expand...
Click to collapse
Or yeah, the MOD can work too :good: