Can't access interior storage - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Not sure why but after have a great day of running some new rom and everything going great I reboot and can't access any storage. Everything is still there but it states access denied to interior storage. Any idea why?

What file manager are you using to access the files? If you are trying to browse system files, you need root to view most of them- if you are using ES file explorer make sure root mode is enabled.

Related

[Q] Viewing nook system files on my computer?

I am a bit stuck... I rooted my Nook Touch using the TouchNooter method. It worked well and I can install apps from the market easily.
But I think I missed a step. I want to be able to access nook system files on my computer and can't seem to figure out how. When connected via USB, I can see the normal Nook folders for adding books and such but none of the system files.
I want to be able to add/remove apk's using my computer. Is this even possible?
The easiest way to do this is copy apk files to your SD card and then use ES File or Root explorer to fin and install them.
Sent from my NookColor using xda premium
Even Astro get to install apk, and it's free on market.
While the OP can get Astro she will not be able to see the system files with that. ES File allows access to root files and is free as well.
I have not wifi and any file mangers
I rooted my nook touch.
I have not wifi (unavailable to me)and any file mangers (root explorer &...) how can i install file manager in my nook ?
I want to be able to install apk's using my computer. Is this even possible?
you can install using adb throught wifi. google adb.
I've successfully rooted my touch, and am trying to install Messagease & Instafetch.
Using ES File Explorer, I can't gain access to /system/apps, which is where i'm told they need to go- ES File won't go navigate above the SD card, although I've enabled root access & /system mounting.
i've tried copying the apks to an sd card, but install fails due to non-market issues, although i've enabled installing from non-market sources as well (as far as i can tell, anyway- maybe i have to do that in another place too?).
any ideas what I've done wrong? let me know if i need to post any other info. I'm using LinuxMint.
thanks!
-steve
ypres333 said:
i've enabled installing from non-market sources as well
Click to expand...
Click to collapse
If you enable it using Nook Color Tools, you should untick and tick again the checkbox to make it work
Also, it may be possible to access the system partition booting with noogie.img ...
merci mille fois!
sorry for the question, but is rooting a 2nd time with noogie.img a bad idea, or will it just overwrite the image i created with touchnooter?
thanks in advance,
-steve
i may have figured something out: i remade a new image with noogie.img, the rebooted the nook with the sd card in. once the "rooted forever" appeared, I plugged in the USB and 7 partitions showed up on my computer screen. i was able to access the files there and put the messagease.apk and instapaper apps in there that way.
thanks again!

[Q] Cm7.1 root access?

I recently installed Cm7.1 on my Nook Color, does this give me root access? The reason i ask this is because i was attempting to access my build.prop to try to get some games to work but i can not seem to be able to access it via Astro File Manager. Also on a side note, every time i install an app and do not have my sd card in my Nook i am prompted to do so instead of using my internal memory?
Lsjreadingpa said:
I recently installed Cm7.1 on my Nook Color, does this give me root access? The reason i ask this is because i was attempting to access my build.prop to try to get some games to work but i can not seem to be able to access it via Astro File Manager. Also on a side note, every time i install an app and do not have my sd card in my Nook i am prompted to do so instead of using my internal memory?
Click to expand...
Click to collapse
CM7 is a rooted ROM. The file access model is setup to make sure you know what you're doing to prevent you from modifying or deleting a file that is essential to the system even though the ROM itself is rooted. I don't use Astro so I don't know how to get root access for that app. File managers like File Expert (free) or Root Explorer (cheap) will allow you to access the root and system files, but you may have to enable the capability in a setup option. In addition, you will have to set the directory to read/write from read-only to actually modify a file.
Thanks for the info, thought i did something wrong when i was installing cm7
shumash said:
CM7 is a rooted ROM. The file access model is setup to make sure you know what you're doing to prevent you from modifying or deleting a file that is essential to the system even though the ROM itself is rooted. I don't use Astro so I don't know how to get root access for that app. File managers like File Expert (free) or Root Explorer (cheap) will allow you to access the root and system files, but you may have to enable the capability in a setup option. In addition, you will have to set the directory to read/write from read-only to actually modify a file.
Click to expand...
Click to collapse
How do i do set a directory to read/write? Also, i have tried several file explorers and none work, i just cant get root access. I am trying to edit my build.prop to try to play some gameloft games.
Lsjreadingpa said:
How do i do set a directory to read/write? Also, i have tried several file explorers and none work, i just cant get root access. I am trying to edit my build.prop to try to play some gameloft games.
Click to expand...
Click to collapse
If you use ES File Explorer (recommended) then it has a setting to make the system directory read / write. You can then just long touch the file, open it using the built in text editor and save it.
Yup i did that, checked both boxes under root settings but i am unable to navigate out of the sd card
es file explorer
To get out of SD card, go into settings and change home to / instead of /mnt/sdcard next time you open it will start in base directory

Writing to external SD guide

Not sure if this has been covered already on the 7.7 forum, but it's a very useful guide.
This makes Titanium backup and other apps able to write to the external SD card.
Quoted from Thaloneus post on the 7+ forum.
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Sent from my GT-P6800 using xda premium
Copy or use mine at your own risk
Has anyone else tried this? Don't wanna make a mistake.
Semper Fi!!!
Sent from GT-P6800
Worke flawlessly! Thank you!!!
Semper Fi!!!
Sent from GT-P6800
how did you use it ?
just copy/paste ?
Used root explorer in rw mode, copy & paste to
/etc/permissions/platform.xml
If you're using vauxhallastra's, don't forget to unzip it first.
Semper Fi!!!
Sent from GT-P6800
thx
did copy/paste , but.. i'm still not able to move apps to the external sd card
must forget something
followed the steps, tab is root
must be one of those days :-(
I used root explorer in RW mode. Did you do this as well as unzip the file.
Sent from my Transformer Prime TF201 using xda premium
great!!works flawlessly
Sent from my GT-P6800 using xda premium
OK, so I have done this and all seems to be working. However, someone above mentions moving apps to the card, can someone explain how that should be done?
palexr said:
OK, so I have done this and all seems to be working. However, someone above mentions moving apps to the card, can someone explain how that should be done?
Click to expand...
Click to collapse
This can be done for instance with Titanium Backup. Tested and works.
what app2sd apps that you used? i tried few..but seems not to work either
Sent from my GT-P6800 using xda premium
answer is in mine opinion: not
Some people said that it is possible to move apps to sd card with Titanium Backup.
But when you looked afterwards at the size of your SD card nothing changed.
root enabled file manager?
Hi. I know this may sound stupid but what constitutes a 'root enabled file' manager? I've used the file manager that the 7.7 comes with, Astro, and ES explorer and I can't seem to find /sysem/etc/permissions.
What am I doing wrong?
mrexperience said:
Hi. I know this may sound stupid but what constitutes a 'root enabled file' manager? I've used the file manager that the 7.7 comes with, Astro, and ES explorer and I can't seem to find /sysem/etc/permissions.
What am I doing wrong?
Click to expand...
Click to collapse
The default file manager won't let you browse root, and I've never used Astro, but ES definitely does. You have to check "Root Explorer" (and if you want to make any changes, "Mount File System" as writable) in the options. I also recommend checking "Up to Root" option so you can just use the Up button or Back softkey to go from /sdcard to / (root directory), but in any case the favorites button will give you quick access to the root directory from anywhere.
mrexperience said:
Hi. I know this may sound stupid but what constitutes a 'root enabled file' manager? I've used the file manager that the 7.7 comes with, Astro, and ES explorer and I can't seem to find /sysem/etc/permissions.
What am I doing wrong?
Click to expand...
Click to collapse
root enabled file managers will allow you to browse and edit the system config files which we are doing here. the fact that you cant find /system/etc/permission might be because they are file managers. perhaps the paid version of those apps will allow you root access.
Next question:
Once I copy and paste this bit of code into platform. Xls, how do I ensure that its'saved. I see no option for that and pressing the 'back' button doesn't do the trick.
I also tried to use the link given. This was extracted using my astro file manager. What do I do with this document then? Should i copy and paste it in /systems/etc/permissions/ ?
Sent from my GT-P6800 using Tapatalk
Figured it out. Thanks much.
In using ES explorer, you have to go to PREFERENCES first. Therein tick r/w and root. This will enable you to write on the system files.
I found that the Root explorer app didn't help me cause I couldn't save my copied and pasted amendment. Whereas it was easy to do with ES explorer. Hope this last bit helps anyone who needed spoon feeding like me.
Sent from my GT-P6800 using Tapatalk
is there any way to divert the folder \sdcard\Android\data to \sdcard\extStorages\sdcard\Android\data ... this will save me atleast 9GB in my internal memory and will put my sdcard in full use
vauxhallastra said:
Not sure if this has been covered already on the 7.7 forum, but it's a very useful guide.
This makes Titanium backup and other apps able to write to the external SD card.
Quoted from Thaloneus post on the 7+ forum.
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
can we use this method I mean the zip file with tab 10.1

Need help with understanding mount-points, folder structure and file system rights...

Hi everyone,
I need your help. I sometimes face strange issues with my Nexus 4 (Stock Room, Rooted, Matrix Kernel v5). Yesterday I wanted to copy a apk-file for installation on my phone from my home-server. I use ES File Explorer for that. I failed to copy the apk-file to /sdcard/folder-name (operation failed). then i navigated to /data/media/0/folder-name and tried it from there, also it didn't work.
i then copied the file to /sdcard/download and was able to copy it to that and to install it.
i don't really understand why it behaves that way, i was always able to go to /sdcard/folder-name and do what i want. i also noticed another strange thing. i connected my phone via USB (MTP-mode) to the PC and uploaded a few GB of MP3s to it (Folder: Music).
when browsing this folder with ES File Explorer, I cannot delete anything from that folder /sdcard/Music. THOUGH it reports "deletion successful" the files or folders do not get deleted but just remain on the internal SD-card. i could only delete the music successfully via "/data/media/0/Music".
who can explain briefly WTF is going on? i obviously do not really understand the concept and logic behind this. is there a maximum file/path length that must not be exceeded?
thanks in advance and best regards,
hallu
need to bump this, sorry...
does anyone have any idea as to why this phone is behaving the way it is?
I use root explorer and have ZERO issues. That includes pulling apk's.
Try a different file explorer to see if that makes a difference so at least you can determine if the issue is just app specific and not something else.
Check to see of ES isn't mounting certain folders with RW permissions.
Also the actual internal storage is /data/media/0/ so /sdcard/ is just a symlink to that folder. ES seems to be having problems with the symlinks.

Can't see all the files/folders in windows explorer

have a recently rooted nexus 4.2.2 and did a nandroid backup using clockwork recovery. clockwork stored it into a directory which i can't access by just plugging my phone to the usb cable of my pc. i do see folders, but not that particular folder. i have usb debugging option turned on also. i just wanted to transfer the backup files to my pc for storage. is there a way to do this? thank you.
konoplya said:
have a recently rooted nexus 4.2.2 and did a nandroid backup using clockwork recovery. clockwork stored it into a directory which i can't access by just plugging my phone to the usb cable of my pc. i do see folders, but not that particular folder. i have usb debugging option turned on also. i just wanted to transfer the backup files to my pc for storage. is there a way to do this? thank you.
Click to expand...
Click to collapse
You can't see it because windows can't access those folders. You can either move the backups using a file explorer to a folder windows can access, pull the files using ABD or if you have the paid version of ROM Manager you can download the files to your pc using a browser.
I figured it was something of that nature. However I have downloaded different file explorers including the es file explorer and I still can't see the folders on my phone even, not just pc. But when I boot into clockwork recovery and browse through there I can see those folders. I'm at a loss.
konoplya said:
I figured it was something of that nature. However I have downloaded different file explorers including the es file explorer and I still can't see the folders on my phone even, not just pc. But when I boot into clockwork recovery and browse through there I can see those folders. I'm at a loss.
Click to expand...
Click to collapse
With ES File Explorer I had to turn on the root explorer option in the settings, the world and phone icon at the top left..
kzoodroid said:
With ES File Explorer I had to turn on the root explorer option in the settings, the world and phone icon at the top left..
Click to expand...
Click to collapse
yes, i did that as well, but it still doesn't let me see the directories that i see in clockwork. the directories i'm talking about are in /sdcard.. they are
- 0/
- clockworkmod/
- legacy/
- obb/
the only ones i can see are 0/ and legacy/. if i go to 0/ i can see what i normally see in the pc windows explorer. there is also a folder called clockworkmod/ but it only contains the folder called download/ and a couple of files under 100kb.
also, when i'm viewing the folders in ES file manager the sdcard folder has a little shortcut arrow on it instead of a solid folder like most of the other ones.
I can't speak for the intricacies of Clockworkmod as I have never used it, but after doing either a TWRP backup or a Titanium backup on 4.2.2, I have always been able to copy and/or view these backup files using any of the following methods, as well as verifying that they are equivalent (Same exact number of files, same exact file sizes):
1) Copying the files from the Nexus 4 to Windows 7 64 bit Professional using Microsoft Windows Explorer.
2) Copying the files from the Nexus 4 to Windows 7 64 bit Professional by performing an "adb pull".
3) Viewing the files with the Android ES Explorer app (With the "Root Explorer" option turned on and changing the top directory to root or "/").
4) Viewing the files in TWRP.
I also use the full path to the files (when possible). As I recall, there were instances where not all the files were visible if I didn't use the full path. Replacing /0 with /legacy on Android 4.2:
TWRP BACKUP
/data/media/0/TWRP/BACKUPS/<PHONE SERIAL# HERE>/<FILE BACKUP SUBDIRECTORY HERE>/
TITIANIUM BACKUP
/data/media/0/TitaniumBackup/
In fact I just performed all four of these methods a couple of minutes ago because I was originally having problems with Android 4.3 (Not all files being transferred over due to the known permission changes with 4.3), and I wanted to double check that everything is still working properly now. What solved all my issues with 4.3 was to update all my programs to “4.3 friendly” versions (You could see if this resolves your 4.2.2 issues as well):
1) Installed the latest version of TWRP.
2) Unrooted using the latest version of Superuser.
3) Installed the latest Android SDK and then ran the SDK Manager to insure everything was up to date.
a) Deleted my Windows driver and installed the latest Google USB driver from the SDK.
b) Used the new updated platform tools to perform fastboot, adb, etc.
pjc123 said:
I can't speak for the intricacies of Clockworkmod as I have never used it, but after doing either a TWRP backup or a Titanium backup on 4.2.2, I have always been able to copy and/or view these backup files using any of the following methods, as well as verifying that they are equivalent (Same exact number of files, same exact file sizes):
1) Copying the files from the Nexus 4 to Windows 7 64 bit Professional using Microsoft Windows Explorer.
2) Copying the files from the Nexus 4 to Windows 7 64 bit Professional by performing an "adb pull".
3) Viewing the files with the Android ES Explorer app (With the "Root Explorer" option turned on and changing the top directory to root or "/").
4) Viewing the files in TWRP.
I also use the full path to the files (when possible). As I recall, there were instances where not all the files were visible if I didn't use the full path. Replacing /0 with /legacy on Android 4.2:
TWRP BACKUP
/data/media/0/TWRP/BACKUPS/<PHONE SERIAL# HERE>/<FILE BACKUP SUBDIRECTORY HERE>/
TITIANIUM BACKUP
/data/media/0/TitaniumBackup/
In fact I just performed all four of these methods a couple of minutes ago because I was originally having problems with Android 4.3 (Not all files being transferred over due to the known permission changes with 4.3), and I wanted to double check that everything is still working properly now. What solved all my issues with 4.3 was to update all my programs to “4.3 friendly” versions (You could see if this resolves your 4.2.2 issues as well):
1) Installed the latest version of TWRP.
2) Unrooted using the latest version of Superuser.
3) Installed the latest Android SDK and then ran the SDK Manager to insure everything was up to date.
a) Deleted my Windows driver and installed the latest Google USB driver from the SDK.
b) Used the new updated platform tools to perform fastboot, adb, etc.
Click to expand...
Click to collapse
the thing is i can't see the directories that the files are in. either in file explorer or in windows. i need to get more familiar with adb and maybe do it through that, but its strange because i should be able to see them in the explorer. so essentially i have a nandroid backup on my phone that i can't really access to move it or delete it. i can only access it through clockwork recovery. also, all the stuff i used is the latest versions i.e. sdk, drivers, etc.
Then I am at a loss if you tried all the things mentioned. If it is a permission issue, then adb should bypass that problem. The adb executable is located in the platform-tools subdirectory of the SDK. You run the "adb pull" command from a "Command Prompt" window while located in that directory. The nandroid copy will take quite a while, so wait until it is finished (For example, my latest one was 330 MB in size).
While the phone is in recovery, here are some examples of grabbing the TWRP and TITANIUM backup files and putting them into the directories TWRP_BACKUP and TITANIUM_BACKUP respectively (That I previously created) on the windows "C" drive. As before, you would probably be replacing /legacy for /0:
adb pull /data/media/0/TWRP/BACKUPS/<PUT SERIAL # OF PHONE HERE>/<PUT DATE OF BACKUP HERE>/ C:\TWRP_BACKUP\
adb pull /data/media/0/TitaniumBackup/ C:\TITANIUM_BACKUP\
konoplya said:
yes, i did that as well, but it still doesn't let me see the directories that i see in clockwork. the directories i'm talking about are in /sdcard.. they are
- 0/
- clockworkmod/
- legacy/
- obb/
the only ones i can see are 0/ and legacy/. if i go to 0/ i can see what i normally see in the pc windows explorer. there is also a folder called clockworkmod/ but it only contains the folder called download/ and a couple of files under 100kb.
also, when i'm viewing the folders in ES file manager the sdcard folder has a little shortcut arrow on it instead of a solid folder like most of the other ones.
Click to expand...
Click to collapse
Clockworkmod puts the backups in a secure system folder with the path mnt/shell/emulated/clockworkmod/backup. In ES File Explorer hit the "/" at the top which will open up "device" and now you will see all of your system folders. Root Explorer is a simpler app to use as it only has two directory options, root and storage. I bought both apps a long time ago as I liked that ES File Explorer lets you connect to a lan to upload/download files through wifi.
pjc123 said:
Then I am at a loss if you tried all the things mentioned. If it is a permission issue, then adb should bypass that problem. The adb executable is located in the platform-tools subdirectory of the SDK. You run the "adb pull" command from a "Command Prompt" window while located in that directory. The nandroid copy will take quite a while, so wait until it is finished (For example, my latest one was 330 MB in size).
While the phone is in recovery, here are some examples of grabbing the TWRP and TITANIUM backup files and putting them into the directories TWRP_BACKUP and TITANIUM_BACKUP respectively (That I previously created) on the windows "C" drive. As before, you would probably be replacing /legacy for /0:
adb pull /data/media/0/TWRP/BACKUPS/<PUT SERIAL # OF PHONE HERE>/<PUT DATE OF BACKUP HERE>/ C:\TWRP_BACKUP\
adb pull /data/media/0/TitaniumBackup/ C:\TITANIUM_BACKUP\
Click to expand...
Click to collapse
i'll play around with that when i get home. thank you.
kzoodroid said:
Clockworkmod puts the backups in a secure system folder with the path mnt/shell/emulated/clockworkmod/backup. In ES File Explorer hit the "/" at the top which will open up "device" and now you will see all of your system folders. Root Explorer is a simpler app to use as it only has two directory options, root and storage. I bought both apps a long time ago as I liked that ES File Explorer lets you connect to a lan to upload/download files through wifi.
Click to expand...
Click to collapse
i have root explorer that i purchased a couple years ago as well. doesn't show me the path you mention. neither does the ES File Explorer. this is why it puzzles me since my phone is rooted. when i look in ES File Explorer and choose "/" as my starting point, i do see all the folders, however, the clockworkmod folder doesn't contain the "backup" folder. it has only "download" folder and a couple of files ".recovery_version" and ".settings".. nothing else.
konoplya;45563381i have root explorer that i purchased a couple years ago as well. doesn't show me the path you mention. neither does the ES File Explorer. this is why it puzzles me since my phone is rooted. when i look in ES File Explorer and choose "/" as my starting point said:
You can't see /mnt in the root directory? Are you sure your phone is still rooted? Open up your superuser app and see if both ES File Explorer and Root Explorer are listed. On my phone in the mnt/shell/emulated folder I have 4 files, 0, clockworkmod, legacy, and obb.
Click to expand...
Click to collapse
kzoodroid said:
You can't see /mnt in the root directory? Are you sure your phone is still rooted? Open up your superuser app and see if both ES File Explorer and Root Explorer are listed. On my phone in the mnt/shell/emulated folder I have 4 files, 0, clockworkmod, legacy, and obb.
Click to expand...
Click to collapse
I posted picks of the folders in ES File Explorer. In the clockworkmod folder I have 2 subfolders, download and backup.
kzoodroid said:
I posted picks of the folders in ES File Explorer. In the clockworkmod folder I have 2 subfolders, download and backup.
Click to expand...
Click to collapse
I looked in su and I have three apps listed there: root explorer, titanium backup, and es file explorer. I don't see those folders that you have in your screenshots. What app do you use for that? I'll take a screenshot of what I have.
Edit: I reinstalled the file explorer and rebooted the phone and I can see the mnt directory now. Don't know why it wasn't showing up. Thank you for the help.
Sent from my Nexus 4 using xda app-developers app
konoplya said:
I looked in su and I have three apps listed there: root explorer, titanium backup, and es file explorer. I don't see those folders that you have in your screenshots. What app do you use for that? I'll take a screenshot of what I have.
Edit: I reinstalled the file explorer and rebooted the phone and I can see the mnt directory now. Don't know why it wasn't showing up. Thank you for the help.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad you got it worked out. To take screen shots press and hold the power button and volume down at the same time. My photos automatically upload to dropbox and I just attached them from there to my post.
kzoodroid said:
Glad you got it worked out. To take screen shots press and hold the power button and volume down at the same time. My photos automatically upload to dropbox and I just attached them from there to my post.
Click to expand...
Click to collapse
thats badass. thanks!
Happened to me aswell
all you need to do is go into your file browser on your phone and then move the file somewhere else while still connected to the pc.. should be good then

Categories

Resources