Related
I am using DeFrost 9.0b with spare parts that lets you install apps on the sdcard. I am trying to backup all my apps that I downloaded and installed but I can't find them on the sdcard with root explorer.
Does anyone know where on the sdcard the apps are downloaded?
look in the android secure folder on the root of the SD card
Nekromantik said:
look in the android secure folder on the root of the SD card
Click to expand...
Click to collapse
I did and it is empty. ???
Sandule said:
I did and it is empty. ???
Click to expand...
Click to collapse
that is where they are meant to be.
So I dunno where else it could have placed them.
Nekromantik said:
that is where they are meant to be.
So I dunno where else it could have placed them.
Click to expand...
Click to collapse
Could it be a permission issue. I can't seem to change the permissions for the .android_secure folder. Is there a specific way that I need to change permissions in root explorer?
Did you direct the apps to the correct location with pm SetInstallLocation 2?
As suggested, the apps should be inside encrypted files within the /sdcard/.android_secure folder, whose contents are visible in recovery mode only.
So how can I get to the files then?
Should also work by using a Terminal Emulator.
Go to the Android Market, download an app called "ConnectBot".
Sign in to it, set is to local.
try the following (enter these commands):
su
ls -l /sdcard/.android_secure
I think you could also install Apps2SD using the Terminal Emulator with these commands:
su
pm setInstallLocation 2
Let me know if that helps at all.
Regards,
Mas.
I have already performed the setinstallLocation 2
When I do the ls command nothing comes up.
Not sure then mate
May be worth trying a full wipe again, re-flashing the rom and installing A2SD?
-------------------------------------
Sent via the XDA Tapatalk App
My cell phone OCD is being aggravated due to my broken market. I suspect there may be a fix out there, but the Cyanogen threads are all MASSIVE. I've done my best to sort through them and every 'fix' so far hasn't worked on newer builds.
Back on my Hero, whenever I had this problem I would just edit the build.prop and wipe cache. The way I understand it is that we can't fix it that way because up until very recently we haven't had an official Froyo build.
I downloaded the OTA zip hosted on HTC's website hoping I would be able to pull a build.prop from it, but it seemed to only contain a patch file for the build.prop.
If someone running the official OTA could upload a pull of their build.prop, I think we might have a fix... ...or am I totally off base?
I figure it might be a good idea to include apps I'm missing in market just to be clear. Paid version of Cachemate, Fandango, aSpiritbomb Live Wallpaper just to name a few.
I'm running the 8/03 build FYI
Nightly Market
http://forum.xda-developers.com/showthread.php?t=729367&highlight=nightly
Pretty sure it's in the first post.
EDIT: Actually, maybe not. I haven't run a nightly in a day or two, and I could be getting it confused with RC-1...
Bang3r said:
http://forum.xda-developers.com/showthread.php?t=729367&highlight=nightly
Pretty sure it's in the first post.
EDIT: Actually, maybe not. I haven't run a nightly in a day or two, and I could be getting it confused with RC-1...
Click to expand...
Click to collapse
I've tried that market fix at least 3 times on 8/02. I'll try it once on 8/03.
EDIT: Still no worky. Maybe I should just flash back to RC1.
I think I may have fixed it if anyone cares. Clear market data, cache. Push the attached file to /system/build.prop and reboot.
Paid cachemate is showing for me now.
Props to netarchy for upping the 2.2 build this fingerprint was pulled from.
illogic6 said:
I think I may have fixed it if anyone cares. Clear market data, cache. Push the attached file to /system/build.prop and reboot.
Paid cachemate is showing for me now.
Props to netarchy for upping the 2.2 build this fingerprint was pulled from.
Click to expand...
Click to collapse
this does work folks!!!!
thanks for working this up
illogic6 said:
I think I may have fixed it if anyone cares. Clear market data, cache. Push the attached file to /system/build.prop and reboot.
Paid cachemate is showing for me now.
Props to netarchy for upping the 2.2 build this fingerprint was pulled from.
Click to expand...
Click to collapse
can you explain how to "push" a file in a shell/command window/terminal emulator?
ryan2202 said:
can you explain how to "push" a file in a shell/command window/terminal emulator?
Click to expand...
Click to collapse
The easiest way is through adb on your computer.
Code:
adb remount
adb c:\%pathtofile%\build.txt /system/build.prop
adb reboot
You could also delete your original build.prop with a root file manager, rename the attached file build.prop and move it to /system/. I wouldn't bother with the terminal on the phone.
Thanks for this!!
terminal app works fine too.
Code:
SU
mount -o remount,rw /dev/block/mtdblock4 /system
rm /system/build.prop
cat /sdcard/build.txt > /system/build.prop
Sorry for the noob question, but what exactly are "protected apps" ?
I'm on the latest nightly and my market "seems" to be fine. I'm just wondering if i'm missing anything in the market.
LP_sk8er said:
Sorry for the noob question, but what exactly are "protected apps" ?
I'm on the latest nightly and my market "seems" to be fine. I'm just wondering if i'm missing anything in the market.
Click to expand...
Click to collapse
Three are listed in the first post.
Sent from my PC36100 using XDA App
LP_sk8er said:
Sorry for the noob question, but what exactly are "protected apps" ?
I'm on the latest nightly and my market "seems" to be fine. I'm just wondering if i'm missing anything in the market.
Click to expand...
Click to collapse
Documents to Go full version key diddnt show up before the fix.
Is calorie counter by fatsecret one of these? I went back to fresh from cm6 recently because I couldn't get that app to show up in the market.
Sent from my PC36100 using XDA App
sdc177 said:
Is calorie counter by fatsecret one of these? I went back to fresh from cm6 recently because I couldn't get that app to show up in the market.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yup, I believe so.
illogic6 said:
I think I may have fixed it if anyone cares. Clear market data, cache. Push the attached file to /system/build.prop and reboot.
Paid cachemate is showing for me now.
Props to netarchy for upping the 2.2 build this fingerprint was pulled from.
Click to expand...
Click to collapse
What is the actual command to push this file to build.prop?
Do I have to rename the fle build to build.prop?
Is there a directory the build file has to be in on my computer to push it to the phone?
violent23 said:
What is the actual command to push this file to build.prop?
Do I have to rename the fle build to build.prop?
Is there a directory the build file has to be in on my computer to push it to the phone?
Click to expand...
Click to collapse
Question 1:
Code:
adb remount
adb push c:\%pathtofile%\build.txt /system/build.prop
adb reboot
Just like above.
Question 2:
No. If you put in the commands like I've listed above, it will push to build.prop even though on your desktop it shows as a txt file.
Question 3:
No. The build.txt file can be in any directory. You will just need to specify the path.
I would recommend you push this build.txt if you are running 8/04 nightly. This is updated.
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
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.
I just switched from my M7 to the M8 yesterday. I was excited to have the external SD for saving pictures, moving apps, but mostly to host my backups. I have since unlocked my bootloader and rooted the device. Unfortunately I'm unable to write any back ups through TWRP to the card. I was wondering if anyone found any fixes? I've already tried SDFix but it seems not to work with our device. Any help would be appreciated!
Sidenote: I know this probably belongs under development but I'm unable to post yet as my post count is too low. Thanks again!
iNiREALiZED said:
I just switched from my M7 to the M8 yesterday. I was excited to have the external SD for saving pictures, moving apps, but mostly to host my backups. I have since unlocked my bootloader and rooted the device. Unfortunately I'm unable to write any back ups through TWRP to the card. I was wondering if anyone found any fixes? I've already tried SDFix but it seems not to work with our device. Any help would be appreciated!
Sidenote: I know this probably belongs under development but I'm unable to post yet as my post count is too low. Thanks again!
Click to expand...
Click to collapse
You will need to edit platform.xml file in/system/etc. Are you comfortable ?
I'm not sure. If there was a tutorial that was available I could possibly follow it. Otherwise is this something that could be included in future rom builds? I wouldn't mind waiting.
Sent from my HTC One_M8 using xda app-developers app
iNiREALiZED said:
I'm not sure. If there was a tutorial that was available I could possibly follow it. Otherwise is this something that could be included in future rom builds? I wouldn't mind waiting.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Look for nextapp's SDFix in the play store.. Root and system write protection off is required. It basically edits the file for you (also backs up the original)
silentvisitor said:
You will need to edit platform.xml file in/system/etc. Are you comfortable ?
Click to expand...
Click to collapse
Could you detail the edits for reference anyway please? I'll need to know shortly too.
graffixnyc said:
Look for nextapp's SDFix in the play store.. Root and system write protection off is required. It basically edits the file for you (also backs up the original)
Click to expand...
Click to collapse
The app worked for me!
graffixnyc said:
Look for nextapp's SDFix in the play store.. Root and system write protection off is required. It basically edits the file for you (also backs up the original)
Click to expand...
Click to collapse
Thanks for the help. I tried sdfix this morning. It kept failing and rebooting. I'm rooted but if you could explain how I turn write protection off that would be awesome!
iNiREALiZED said:
Thanks for the help. I tried sdfix this morning. It kept failing and rebooting. I'm rooted but if you could explain how I turn write protection off that would be awesome!
Click to expand...
Click to collapse
the quick way? go to the module thread in Original development and follow the instructions. You'll have to do it at every boot though unless you're on a rom that supports init.d support. If you're on stock I made a guide to disable it on boot automatically without init.d support
My guide: http://forum.xda-developers.com/showthread.php?t=2702575
graffixnyc said:
the quick way? go to the module thread in Original development and follow the instructions. You'll have to do it at every boot though unless you're on a rom that supports init.d support. If you're on stock I made a guide to disable it on boot automatically without init.d support
My guide: http://forum.xda-developers.com/showthread.php?t=2702575
Click to expand...
Click to collapse
Sorry if I'm missing something totally obvious. I went and read the thread. I download the file with extension .ko. Copied it to root of internal memory. Opened up terminal app and typed "sh" then used command "insmod /storage/sdcard0/wp_mod.ko"
Am I missing something?
iNiREALiZED said:
Sorry if I'm missing something totally obvious. I went and read the thread. I download the file with extension .ko. Copied it to root of internal memory. Opened up terminal app and typed "sh" then used command "insmod /storage/sdcard0/wp_mod.ko"
Am I missing something?
Click to expand...
Click to collapse
su
not sh..
type su
hit enter
then type
insmod /storage/sdcard0/wp_mod.ko it wont show you any output or anything.. if it brings your back to the terminal prompt it ran right
graffixnyc said:
su
not sh..
type su
hit enter
then type
insmod /storage/sdcard0/wp_mod.ko it wont show you any output or anything.. if it brings your back to the terminal prompt it ran right
Click to expand...
Click to collapse
I tried it again using "su". I'm pretty sure that is what I used the first time as well because when I entered the command the super user prompt came up to allow access for terminal. Same results. Didn't see any confirmation. Exited app and tried running SDFix and failed again. I then followed your link to your thread and followed step by step. Got all the way to the point where I was trying to save the text document at the end and got the prompt that I could not save the file.
I'm usually pretty good at following tutorials and I'm sure I'm not skipping steps but who knows. I think this one has me defeated lol.
If you put it on your SD card try just /sdcard/wp_mod.ko
Sent from my HTC One using Tapatalk
If you run the command.. And then run it again. It will tell you it already exists that's how I figured out it ran ok..
Sent from my HTC One using Tapatalk
backfromthestorm said:
Could you detail the edits for reference anyway please? I'll need to know shortly too.
Click to expand...
Click to collapse
Sure. Here it is:
You need to make following change to platform.xml in /system/etc.
Add <group gid="Media_rw"/> under WRITE_EXTERNAL_STORAGE and WRITE_MEDIA_STORAGE(or similar).
Save. Set Permission to rw-r-r or 644.
Reboot and Enjoy
Good luck :good:
silentvisitor said:
Sure. Here it is:
You need to make following change to platform.xml in /system/etc.
Add <group gid="Media_rw"/> under WRITE_EXTERNAL_STORAGE and WRITE_MEDIA_STORAGE(or similar).
Save. Set Permission to rw-r-r or 644.
Reboot and Enjoy
Good luck :good:
Click to expand...
Click to collapse
Well I ran through both tutorials (yours and the others) once again. Entered the command twice to confirm and got the message "failed file already exists". So I'm assuming that part went through fine but still unable to run SDFix successfully or edit the install_recovery.sh file. Wouldn't allow me to save through es text edit or the standard one.
So now I'm trying to manually change the platform.xml file. When I navigate to system/etc I don't see any file named "platform.xml". Also tried a search through es file explorer and couldn't find any file. Any thoughts?
iNiREALiZED said:
Well I ran through both tutorials (yours and the others) once again. Entered the command twice to confirm and got the message "failed file already exists". So I'm assuming that part went through fine but still unable to run SDFix successfully or edit the install_recovery.sh file. Wouldn't allow me to save through es text edit or the standard one.
So now I'm trying to manually change the platform.xml file. When I navigate to system/etc I don't see any file named "platform.xml". Also tried a search through es file explorer and couldn't find any file. Any thoughts?
Click to expand...
Click to collapse
My apologies.
Its /system/etc/Permission/platform.xml
iNiREALiZED said:
Well I ran through both tutorials (yours and the others) once again. Entered the command twice to confirm and got the message "failed file already exists". So I'm assuming that part went through fine but still unable to run SDFix successfully or edit the install_recovery.sh file. Wouldn't allow me to save through es text edit or the standard one.
So now I'm trying to manually change the platform.xml file. When I navigate to system/etc I don't see any file named "platform.xml". Also tried a search through es file explorer and couldn't find any file. Any thoughts?
Click to expand...
Click to collapse
Are you mounting it as r/w in the file explorer? It doesn't seem like you're doing that. I know the module works.. You can't just install the module and it's magically writable.. you still have to make it r/w in a file explorer before you make any changes. I don't use es. I use root explorer and there is a r/w button on top.
graffixnyc said:
Are you mounting it as r/w in the file explorer? It doesn't seem like you're doing that. I know the module works.. You can't just install the module and it's magically writable.. you still have to make it r/w in a file explorer before you make any changes. I don't use es. I use root explorer and there is a r/w button on top.
Click to expand...
Click to collapse
Wow. Excuse my ignorance. I wasn't doing that. I downloaded root explorer and used the button to mount as you mentioned and viola I was able to save the edits! I'm now able to create folders on the ext SD. Still get an error when trying to backup from twrp but I guess that's an issue for another day.
I really appreciate all the help!
iNiREALiZED said:
Wow. Excuse my ignorance. I wasn't doing that. I downloaded root explorer and used the button to mount as you mentioned and viola I was able to save the edits! I'm now able to create folders on the ext SD. Still get an error when trying to backup from twrp but I guess that's an issue for another day.
I really appreciate all the help!
Click to expand...
Click to collapse
As of now recovery doesn't support exfat formatted cards, If your sd card is formatted as exfat it will fail in recovery. You need to either format your external sd card to fat32 or just wait until the recovery is updated to support exfat. It will once they get kernel source code
graffixnyc said:
As of now recovery doesn't support exfat formatted cards, If your sd card is formatted as exfat it will fail in recovery. You need to either format your external sd card to fat32 or just wait until the recovery is updated to support exfat. It will once they get kernel source code
Click to expand...
Click to collapse
How far out do you think that is? I was figuring I could just get a cheaper card for my backups. Only thing is if I remember correctly Fat32 only supports up to 4GB files correct? I remember my backups being a tad over that so getting another card might not even make a difference.