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
im looking to chmod a file i have on my sd card, but i cant really grasp what i need to do with it....
its stored in my /data/data/com.spb.shell3d/lib folder of my phone
so if anyone could tell me how to change it to a 755 would be AMAZING, and much rep sent your way
Thank you
/data is not on your sdcard
you can use adb from your computer or you can install terminal emulator from the market....
chmod 755 /path/to/file/filename.file
sorry i should have mentioned, i had it on my sd card, and then did a copy to the above mentioned file location....
and thats all i have to type in there is chmod 755 /data/data/com.spb.shell3d/lib ?
kneedraggin101 said:
sorry i should have mentioned, i had it on my sd card, and then did a copy to the above mentioned file location....
and thats all i have to type in there is chmod 755 /data/data/com.spb.shell3d/lib ?
Click to expand...
Click to collapse
yes. that should do it
So i've made a mistake. I forgot to download GAPPS but i've already done a factory reset and installed a new rom. I cant seem to mount the usb storage trough clockwork recovery. Is there a way to push the zip file to the device?? Or what should i do?
Thanx
xclusiv8 said:
So i've made a mistake. I forgot to download GAPPS but i've already done a factory reset and installed a new rom. I cant seem to mount the usb storage trough clockwork recovery. Is there a way to push the zip file to the device?? Or what should i do?
Thanx
Click to expand...
Click to collapse
If you only forgot gapps you can restart, the ROM and the phone will work fine you just won't have Google apps. Once it's on you can just copy the file like usual and return to recovery and flash it
Sent from my Galaxy Nexus using xda premium
Good question though. What IF he didnt flash the ROM, how do you get a file on the SDcard if you cant mount it in recovery?
adb push ./"filename.zip" /sdcard
Phone will boot just fine w/o GAPPS.
But you can just use adb push <FILE> <DIRECTORY>
for example:
Code:
adb push gapps.zip /sdcard/
Thanx for the help guys =)
This happens to me all the time. The Mounts section of CWM select "mount as USB" drive. Windows should see this drive and transfer away.
merge5 said:
This happens to me all the time. The Mounts section of CWM select "mount as USB" drive. Windows should see this drive and transfer away.
Click to expand...
Click to collapse
GN internal storage can't be mounted as USB - not even in recovery.
The only way I've found to push/pull files in CWM on the GN is over ADB. If the files in /sdcard/ don't appear, go into mounts and storage, and mount /data. Then try again.
/sdcard/ is nothing more than a symlink to /data/media.
I transfer files over ADB with
'adb push update.zip /data/media/'
no need to mount /data before.
just reboot open up your computer and youll see the gnex just transfer the gapps to your sd card and then reboot in recovery to flash
cmstlist said:
GN internal storage can't be mounted as USB - not even in recovery.
The only way I've found to push/pull files in CWM on the GN is over ADB. If the files in /sdcard/ don't appear, go into mounts and storage, and mount /data. Then try again.
Click to expand...
Click to collapse
Good point. I stand corrected. That was how I did it on my OG Droid. Sorry for the confusion.
bk201doesntexist said:
/sdcard/ is nothing more than a symlink to /data/media.
I transfer files over ADB with
'adb push update.zip /data/media/'
no need to mount /data before.
Click to expand...
Click to collapse
I'm not sure why but CWM on my phone used to auto mount /data and now it doesn't anymore. So to see anything from adb in recovery, I now have to go to mounts first.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
I'm not sure why but CWM on my phone used to auto mount /data and now it doesn't anymore. So to see anything from adb in recovery, I now have to go to mounts first.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
What cwm version are you on, for instance?
Latest CWM touch as of today, and also tried it with latest CWM non-touch.
Incidentally I just bumped into a caveat of transferring files to the GN in recovery mode. The permissions are set strangely when you push files over ADB in recovery, and as a result when booted into the OS I was unable to rename any of the pushed files/folders or put new files in. Since the DCIM directory was one that I'd pushed over, new photos weren't saving. And I did not have permission to change permissions.
This is pretty much a brute force method - so I rebooted into recovery again, mounted /data, did adb shell, cd sdcard, and then:
chmod -R 777 *
And upon booting back into the OS, everything works properly again.
I know that messing with permissions is usually a dangerous thing. My logic was that anything stored in /sdcard is supposed to be a file that any app would be allowed to access as long as it has SD permissions - it's been that way in every version of the OS through to 4.0.
But anyway, if there's something I should do to decrease the "unsafeness" of this situation, please advise me. I guess in theory this would give a malicious app permission to execute code from /sdcard, which would make me more vulnerable?
EDIT: Okay more to report. To see the permissions properly when booted into the OS, you have to go into /data/media rather than /sdcard (same directory but permissions appear differently).
When I went in there and typed ls -n, I found that all the files I had pushed in recovery have UID & GID of 0. All files I had created afterwards had UID & GID of 1023. That explains everything. The owner is root for files that came from ADB in recovery, and media_rw for files created in the OS.
I can use chown, but it looks like the version of chown that comes with busybox does not have -R recursion implemented. Hrm. Aha! In CWM, chown does support -R. And we're off to the races. So from recovery I did:
cd /data/media
chown -R media_rw.media_rw *
cmstlist said:
Latest CWM touch as of today, and also tried it with latest CWM non-touch.
Incidentally I just bumped into a caveat of transferring files to the GN in recovery mode. The permissions are set strangely when you push files over ADB in recovery, and as a result when booted into the OS I was unable to rename any of the pushed files/folders or put new files in. Since the DCIM directory was one that I'd pushed over, new photos weren't saving. And I did not have permission to change permissions.
This is pretty much a brute force method - so I rebooted into recovery again, mounted /data, did adb shell, cd sdcard, and then:
chmod -R 777 *
And upon booting back into the OS, everything works properly again.
I know that messing with permissions is usually a dangerous thing. My logic was that anything stored in /sdcard is supposed to be a file that any app would be allowed to access as long as it has SD permissions - it's been that way in every version of the OS through to 4.0.
But anyway, if there's something I should do to decrease the "unsafeness" of this situation, please advise me. I guess in theory this would give a malicious app permission to execute code from /sdcard, which would make me more vulnerable?
EDIT: Okay more to report. To see the permissions properly when booted into the OS, you have to go into /data/media rather than /sdcard (same directory but permissions appear differently).
When I went in there and typed ls -n, I found that all the files I had pushed in recovery have UID & GID of 0. All files I had created afterwards had UID & GID of 1023. That explains everything. The owner is root for files that came from ADB in recovery, and media_rw for files created in the OS.
I can use chown, but it looks like the version of chown that comes with busybox does not have -R recursion implemented. Hrm. Aha! In CWM, chown does support -R. And we're off to the races. So from recovery I did:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
that would explain it: i always use /data/media, didn't find any permission issues yet. thanks.
Its really bothering me. When flashing a Rom in the aroma I choose this red theme I never used. Well in the vrtheme folder on my SD card (internal storage) there is a bunch of. PNG files that show up in my gallery. If I try to delete from gallery they just come back. And if try to delete from file explorer with root permissions. It says file can not be deleted. This doesn't make sense or am I missing something?
Help would be appreciated.
Thank you
Give this a shot (assuming you are rooted)
find the folder they are in (for arguments' sake let's say they are in /storage/sdcard0/vrtheme/
download terminal emulator app
open it and type the following commands without quotes...
"su"
"rm /storage/sdcard0/vrtheme/*.png"
see if they are gone now.
Admiral Sir Manley Power said:
Give this a shot (assuming you are rooted)
find the folder they are in (for arguments' sake let's say they are in /storage/sdcard0/vrtheme/
download terminal emulator app
open it and type the following commands without quotes...
"su"
"rm /storage/sdcard0/vrtheme/*.png"
see if they are gone now.
Click to expand...
Click to collapse
Thank for trying to help. But if I go to directory all the way down to the PNG file I would have to repeat like 150 times
But anyways when I tried it. I was granted rights for su. Then received the # in terminal.
Then I did rm followed by file path.
It said permissions denied :/
Just wanted to report my findings. If you do a search for aroma file manager on xda. With that you can delete anyfile on SD card if given operation denied with any normal file explorer with root access.
FYI - sdcard0 is not really your SD Card at all. sdcard0 is the internal storage memory. extSdCard is your actual SD Card. And UsbDriveA, UsbDriveB, etc.. are your external drives like USB thumb drive, USB external drive, etc.
If you deleted file/s and then later came back that is because the file/s are being put back with the related app/s that the file/s are related too. Deal with the related app/s in order to stop the deleted file/s from reappearing.
If you can't delete the file/s at all then change the permissions of the file/s you want to delete and/or change the permissions with the folder that holds the file/s to be deleted. Then you can delete the file/s. You can change permissions with a file manager like Root Explorer, though you need to be rooted to change some permissions. Be careful. Deleting the wrong file/s can make your device bricked.
---------- Post added at 01:08 PM ---------- Previous post was at 12:34 PM ----------
trevor7428 said:
Thank for trying to help. But if I go to directory all the way down to the PNG file I would have to repeat like 150 times
But anyways when I tried it. I was granted rights for su. Then received the # in terminal.
Then I did rm followed by file path.
It said permissions denied :/
Click to expand...
Click to collapse
You wouldn't have to delete each .png file separately. Just type exactly what Admiral Sir Manley Power typed. The line command he wrote uses the wild card ( * ) so the command would delete all .png files within that folder at the same time.
Change the permissions of the folder that holds the files. Then try it. Make sure the app related to the files are not still caching the files. Caching the files would make the files to be currently in use. That would make the files not available to be deleted. You can also use another theme app, force kill the app related to the .png files, then delete the files. Then go back to that theme app.
JaguarXT said:
FYI - sdcard0 is not really your SD Card at all. sdcard0 is the internal storage memory. extSdCard is your actual SD Card. And UsbDriveA, UsbDriveB, etc.. are your external drives like USB thumb drive, USB external drive, etc.
If you deleted file/s and then later came back that is because the file/s are being put back with the related app/s that the file/s are related too. Deal with the related app/s in order to stop the deleted file/s from reappearing.
If you can't delete the file/s at all then change the permissions of the file/s you want to delete and/or change the permissions with the folder that holds the file/s to be deleted. Then you can delete the file/s. You can change permissions with a file manager like Root Explorer, though you need to be rooted to change some permissions. Be careful. Deleting the wrong file/s can make your device bricked.
Click to expand...
Click to collapse
I no SD card should be external. But on our note 2 the directory for internal is labeled SD card. Then vrtheme was in a folder named. " 0" I tried to change permissions and even the owner of file and folder, but it wouldn't let me with root permissions. That's why I was so stumped I had to post on xda.
And its not that the file would get deleted then put back it was I couldn't delete at all. There was no app to my knowledge for vrtheme.
trevor7428 said:
Thank for trying to help. But if I go to directory all the way down to the PNG file I would have to repeat like 150 times
But anyways when I tried it. I was granted rights for su. Then received the # in terminal.
Then I did rm followed by file path.
It said permissions denied :/
Click to expand...
Click to collapse
try this instead...
rm -f /storage/sdcard0/vrtheme/*.png"
if that doesn't work... try this....
chmod 777 /storage0/vrtheme
chmod 777 /storage0/vrtheme/*.png
rm -rf /storage/storage0/vrtheme
Admiral Sir Manley Power said:
try this instead...
rm -f /storage/sdcard0/vrtheme/*.png"
if that doesn't work... try this....
chmod 777 /storage0/vrtheme
chmod 777 /storage0/vrtheme/*.png
rm -rf /storage/storage0/vrtheme
Click to expand...
Click to collapse
I thanked everyone who replied, but I actually got it figured out. I flashed this zip file in recovery called aroma file manager. While let me delete whole folder from recovery. I appreciate all who helped.
Hi guys, today i am here to tell you a method only tested on a galaxy y, but i hope it will work for all. this is a method to change the download location for play store.
WARNING!!!
1. WARRANTY IS NOW VOID.
2. NOT MY PROBLEM IF SOME APP FAIL.
3. PLEASE, PLEASE, PLEASE DO A NANDROID BACKUP BEFORE THIS.
This is a simple code but it needs root for sure. now the necessities are as follows:
1. A complete nandroid backup
2. Root Permissions
3. Any terminal emulator. e.g https://play.google.com/store/apps/details?id=hecticman.jsterm
4. You need to know the default download location and the mount point of sd card( if that is where you want the new download location )
Now let's start.
Just know this that mnt/sdcard will have to be replaced by your sdcard mount point and data/app will have to be replaced by the default download location. i underlined them for easy understanding.
NOT MY PROBLEM IF THIS FAILS AND YOUR PLAY STORE CRASHES. JUST DO A NANDROID RESTORE.
THERE WILL ALREADY BE A $ AT START SO U DON'T HAVE TO PUT IT.
$ su
# mkdir /mnt/sdcard/playstore
# cp -r /data/app/* /mnt/sdcard/playstore
# rm -rf /data/app
# ln -s /mnt/sdcard/playstore /data/app
Click to expand...
Click to collapse
what the code does:
1. Grant super user permissions
2. Make a directory in sdcard named playstore.
3. Copy all items (recursively) from data/app to sdcard/playstore
4.Symlink the new location to fake the original.
Hitting Thanks can help.
and once again PLEASE BACKUP BEFORE THIS AND RESTORE IF NOT SUCCESSFUL.
This is based on the code used by link2sd.
Could you please double check your code fragments?
For me it looks, like you create a directory "playstore", but then copy to a directory "playstore-temp", which will most like not exist at that moment.
The ln you're using can't realy work as long as the /data/app directory is still in place... so you would first need to delete /rename it.
Just my 2¢
thanks dude
DThought said:
Could you please double check your code fragments?
For me it looks, like you create a directory "playstore", but then copy to a directory "playstore-temp", which will most like not exist at that moment.
The ln you're using can't realy work as long as the /data/app directory is still in place... so you would first need to delete /rename it.
Just my 2¢
Click to expand...
Click to collapse
looks like i was drunk making so much mistakes . corrected it.
It's not so simple if you use Link2SD. If you link some apps to sdext partition, some files in /data/app are symlinks which cannont be copied to /mnt/sdcard/playstore as it's FAT32. You have to try to symlink /app/data to folder on sdext partition. Create a folder /data/sdext2/playstore, copy /data/app/* there, delete /data/app and symlink /data/sdext2/playstore as /data/app. Sdext partition uses linux filesystem and all symlinks should work properly. I haven't tested it yet, but will do in a minute.
EDIT:
It doesn't work with Link2SD. Phone hangs on boot. It's probably cause Link2SD app must be directly in internal memory (so in real /data/app, not symlinked). I'll try to symlink /data/data or /data/dalvik-cache to save some internal memory but I doubt it'll work.