CIFS issue - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

Hi,
I am using CIFS manager and ES File Explorer. The first time I mount a share, it will open in ES as an empty folder. I'd have to unmount and remount, open it again. Good chance it will show the content but not always.
When it does show content, if I try to install an APK in the remote folder, it will generate error "there was a problem parsing the package". However, I can copy the file to a local folder and then install successfully.
And I can't seem to write to any mounted folder, regardless the permission I used.
Any way to fix this?
I am not sure if these are related to
Fix for empty app-mounted directories (CifsManager, etc.) in Android 4.2. Does anyone know if it's in this build?
Thanks

You can open CIFS shares directly from ES File Explorer.

Greek2me said:
You can open CIFS shares directly from ES File Explorer.
Click to expand...
Click to collapse
Yes. However, it will copy it to local if you try to read the file.
For something that's properly mounted, it should not happen that way -- it should be transparent to the program.

Related

[Q] How do I install a bootanimation?

Ahoy! Simply put, I'd like to install a new boot animation on my rooted HTC Desire HD running Android Revolution HD 3.0.
I've searched how to do this but I don't exactly understand.
I understand that I can 'push' the new bootanimation.zip to data/local via ADB, but some guides/installation tutorials have simply said 'copy bootanimation.zip to data/local.'
I'd much prefer to be able to simply copy the .zip to data/local and not have to deal with ADB as I have not yet used it, but how do I do this? Am I misunderstanding?
I thought 'copy to data/local' would be as simple as using for example, Astro File Manager and copying the new bootanimation.zip from my SDcard to data/local, however there is no 'local' folder inside of the 'data' folder and the option to create a new folder is greyed-out.
Long story short:
What's the simplest method of installing a bootanimation?
Can I simply 'copy bootanimation.zip to data/local?' If so, how?
If I have to use ADB to install the bootanimation, what is the exact process of doing this?
I'm sure this has been asked before, but my searches confused me more than cleared anything up. Thank you for any help in advance!
You need a program like root explorer(es file explorer with root access should work too) for the copy/paste method because the bootanimation.zip isn't stored at your sd card but at the phones internal memory.
At the root of your phone you should see folders like sdcard, dev, root and many more. One of them is called data. In this folder there is one called local. There should be a file called bootanimation.zip. just replace this file with your bootanimation.zip.
Normally it can't damage your phone when your bootanimation has a wrong format or whatever. If the new file is broken, you'll get a black screen instead of an animation but the phone will boot anyway
Sent from my Desire HD using Tapatalk
I see the folder you're talking about in both Astro and ES File Viewer, but this 'data' folder is empty by default. There's no bootanimation.zip and there's no 'local' folder.
I'm confused.
take a look at /system/media
Denavar said:
I see the folder you're talking about in both Astro and ES File Viewer, but this 'data' folder is empty by default. There's no bootanimation.zip and there's no 'local' folder.
I'm confused.
Click to expand...
Click to collapse
Use ES File Explorer, and make sure that you enable root mode in settings. Use hiapk mode. Also remount /system and /data, that option is also in the settings.
jkoljo said:
Use ES File Explorer, and make sure that you enable root mode in settings. Use hiapk mode. Also remount /system and /data, that option is also in the settings.
Click to expand...
Click to collapse
Thank you. This worked perfectly. I wasn't aware I needed to do this. Thanks again.
Edit: I've encountered another problem. Whenever I now attempt to access my SD card via ES File Explorer, I get the error "SD Card Unmounted or not present." How do I rectify this? It works fine in Astro.
Edit 2: I attempted to unmount /system and /data simply by unticking the option in ES (i'm really only just starting to delve into this sort of thing now and don't know what I'm doing.) and it says 'failed to mount'. How do I fix this also? ;P
Edit 3: Re-installing ES File Explorer fixed the above two issues, but I assume it will do the exact same thing again. For the time being and a short fix, is re-installing the app each time OK? I don't exactly know what 'failed to mount' or 'SD Card unmounted or not present' errors mean. I get the idea, but I'm not sure if they're really doing any damage.
I found my original boot animation in '/system/customize/resource/' and replaced with a custom one. Worked!

[Q] Help! I'm having trouble mounting my /system directory as r/w but my s-off

I've used unrevoked forever to get my s-off, but eveytime I try to delete/rename/copy a file to the /system directory I get an error. Anyway to fix this? I'm new XD
use the app root explorer , it allows you to enable write ability.
Root Explorer isnt free, and I can't buy it cuz...im 15
But I did try an app called "mount /system (rw/ro)". It tells me that the /system directory has been set to r/w, but when I use astro to browse to the folder, everything is still marked -ro
true true see ur PM. Does that app of your provide a file directory search or manager?
Astro doesn't have root capabilities. Use ES File Explorer (you have to enable root access in settings) or use Super Manager.
plainjane said:
Astro doesn't have root capabilities. Use ES File Explorer (you have to enable root access in settings) or use Super Manager.
Click to expand...
Click to collapse
I second ES File Explorer. I use it for all my system reading/writing needs in root.
quantumma said:
I've used unrevoked forever to get my s-off, but eveytime I try to delete/rename/copy a file to the /system directory I get an error. Anyway to fix this? I'm new XD
Click to expand...
Click to collapse
try running "Fix Permissions" in ClockworkMod then reboot
thats what did it for me when i had this issue
yup, use ES file explorer (I prefer root explorer, but as you noted, it's not free). You could also start learning to use adb to push/pull to system if you want. It comes in handy, knowing how to use adb. Definitely good to learn at some point.

[Q] Why can't I copy to 'notifications' folder?

I am running Paranoid Android 4.5 beta. I am trying to copy a sound file to /system/media/audio/notifications but it fails. I have root and I made sure it is mounted as R/W in root explorer but I can't do it. I can copy a file to my 'ringtones' folder. Any thoughts?
I just think its the way KK handles things...try different apps
I tried es file explorer and the terminal emulator and the error is it's a read only file system even though Root explorer says it is read write. Does anyone know how to change it?
bird333 said:
I tried es file explorer and the terminal emulator and the error is it's a read only file system even though Root explorer says it is read write. Does anyone know how to change it?
Click to expand...
Click to collapse
I fixed this problem on my note 10.1 gnabo rom with an xposed module. Now I can use my sd how I want not how google thinks I should
Any other thoughts?
Try this: https://play.google.com/store/apps/details?id=com.mrbimc.selinux

Can't move some files, can't create some folders

I don't know how else to describe this issue I'm having:
Essentially sometimes I cannot create new folders, either in an explorer app (ES File Manager, Explorer (free, not Root Explorer), or other file manager) or when connected to my computers via USB. Sometimes I can do both. Similarly, sometimes I cannot move files from one directory to another, both using file manager or when connected to computer over USB. It seems random, I think?
An example of this is I downloaded a PDF file from SharePoint using Chrome. The file is downloaded to the /Downloads directory by default. I wanted to move this to a different directory (/Documents), but the cut+paste operation failed. ES File Manager says the operation can't be completed, Explorer just sits there and doesn't say anything. When trying to do the same thing over USB connection, Windows just sits there saying the device is busy, and it'll sit there indefinitely. But an OGG file I downloaded from Dropbox was free to be moved to and from several directories when I was testing file operations.
Basically it's like my device doesn't want to play nice with files and folders. I tried doing a factory reset, but that didn't seem to help. Do you think completely reformatting the phone (as in fastboot format userdata, and a fresh ROM + kernel install) would help? It seems drastic, but at the same time being unable to move files and folders is very strange and likely hard to pinpoint the culprit.
I'm rooted (using traditional SuperSU root) running Pure Nexus 12/01/2015 ROM and ElementalX 0.07 kernel (Enforcing disabled). I doubt any of those 3 factors are the cause of it, but every detail might help, right?
Update: It looks like a permissions issue. Please see post below.
OK an update to this, I discovered that some folders that I thought I had deleted using ES File Manager are still showing up in USB storage when I'm hooked up to a computer. That is to say that what I see using a file manager versus what I see while connected to a computer are different.
Further to this, I am now getting "Permission denied" by the file managers when I try to copy and paste anything from anywhere to any other place. I have booted into TWRP to run Fix Permissions already. It looks like everything now has rwxrwx---, which means to me 770? It should be 775, no?
Any ideas what might be causing this permissions issue?
daver68 said:
OK an update to this, I discovered that some folders that I thought I had deleted using ES File Manager are still showing up in USB storage when I'm hooked up to a computer. That is to say that what I see using a file manager versus what I see while connected to a computer are different.
Click to expand...
Click to collapse
For this, I read somewhere that the latest ES File app has a recycling bin for when you delete apps. So, that needs to be emptied too.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
For this, I read somewhere that the latest ES File app has a recycling bin for when you delete apps. So, that needs to be emptied too.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did indeed clean out the Recycle Bin (and subsequently disabled it), but the problem persists. But thanks for pointing that out!
OK, an interesting discovery:
If I am on my device and using ES File Explorer and if I am in the path /storage/emulated/0/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /sdcard/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /data/media/0/* then I am able to do anything I damn well please.
Now this makes a bit of sense to me, given the permissions for each directory. For example, when viewing the permissions of a file or folder when in /sdcard or /storage/emulated/0, I can only see the permissions as "Readable: Yes, Writeable: Yes", but I cannot change said permissions. However, when I view the permissions for something when under /data/media/0 then not only can I see the explicit permissions "rw-rw-r--" I can also change it if I wanted to.
I suspect this might be more than just the ROM. Perhaps I did not flash the system.img correctly when I first went through the process? Is this possible?

Question Android 13 Foldersync Unable to access Android/data folder

hello, since Android 13, Foldersync has no longer access to the Android/Data folder. Can someone help me or give a workaround?
Hi. If no one else has any other ideas, you can try the developer of the app. If this is the app here FolderSync, it shows the developer information as:
Developer contact​Website
http://www.tacit.dk
Email
[email protected]
Click to expand...
Click to collapse
BiBaBuTzE said:
hello, since Android 13, Foldersync has no longer access to the Android/Data folder. Can someone help me or give a workaround?
Click to expand...
Click to collapse
Some info...
Why an Android file manager can't open folders under /Android
File managers aren't supposed to be able to access folders under /Android, but a loophole let them. Android 13 closes that loophole.
blog.esper.io
https://twitter.com/i/web/status/1560716910001520641
Lughnasadh said:
Some info...
Why an Android file manager can't open folders under /Android
File managers aren't supposed to be able to access folders under /Android, but a loophole let them. Android 13 closes that loophole.
blog.esper.io
https://twitter.com/i/web/status/1560716910001520641
Click to expand...
Click to collapse
Hi, please can you explain step by step what i must do to get access to the Folder. Foldersync needs Access to this Folder. Thx a lot and have a nice day
I haven't tried it, but this is supposed to take care of the problem, if rooted...
GitHub - Magisk-Modules-Alt-Repo/NoStorageRestrict: Remove the restriction when selecting folders through SAF
Remove the restriction when selecting folders through SAF - GitHub - Magisk-Modules-Alt-Repo/NoStorageRestrict: Remove the restriction when selecting folders through SAF
github.com
In android 13, data and obb folders are blocked. Tried many file managers with root to copy game data in obb folder but failed. Even the Xposed module "no storage restrict" did not worked. Finally copied data through browsing "/data/media/0/Android/obb". You may try this with root.
I am using Evolution X 7.1 on Redmi Note 11.
There are some file managers that are catching up with this. MiXplorer and FV File Manager have updated to allow access to /Android/data & /obb directories in Android 12+.
Now I have access to Android/Data & Android/Obb but I can't paste any file to these folders. I use ES File Explorer. I don't want to use other file manager like MiXplorer and make the trick of splitting screen with drag & drop so that to write files to the above paths. How to make it in the ES File Explorer or if it exists some magisk or xposed module in which to disable this restriction and to be like in Android 12 in which we didn't have any problem in accessing or writing any file to above paths ?
Johnn78 said:
I use ES File Explorer.
Click to expand...
Click to collapse
This is your problem right here. ES File Explorer stopped working properly upon release of Android 11 or 12. I discontinued my modded versions of the app at that time and switched to something that DOES work.
Get another file manager.
This File Manager tends to work in A13, I moved from ES a long time ago when they removed some features, https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore .
Strephon Alkhalikoi said:
This is your problem right here. ES File Explorer stopped working properly upon release of Android 11 or 12. I discontinued my modded versions of the app at that time and switched to something that DOES work.
Get another file manager.
Click to expand...
Click to collapse
When I went to Android 13 then I had ES File Explorer which didn't have access to Android/Data. Then I found ES File Explorer v4.4.0.2.1 which has the ability to have access to Android/Data but it hasn't the ability to write (via copy - paste) to Android/Data. This problem doesn't exist only to ES File Explorer but in all File Managers which I have used like File Manager+, File, MiXplorer, Xplore etc... The MiXplorer which can write to Android/Data not be done via copy - paste but via some trick by splitting screen and drug-drop the file which is some intermediate solution. If it is found some solution which can work the copy - paste to Android/Data then this will work to all File Managers which means that the problem isn't that the ES File Explorer is deprecated. May exist some magisk module or lsposed module which deactivate the SAF (Storage Access Framework) permission in which wasn't enabled in Android 12.
Johnn78 said:
This problem doesn't exist only to ES File Explorer but in all File Managers which I have used like File Manager+, File, MiXplorer, Xplore etc...
Click to expand...
Click to collapse
ES File Explorer, as I said in my previous post, no longer works with current versions of Android. This is because there is no one working on its code. No one to fix bugs when they appear. No one to ensure root functions continue to work. No one to enable proper access to Android/data.
There are file managers out there that are not ES File Explorer, and while you have tried some, you've not tried them all. I tried Root Explorer just now and had no problems copying files to /Android/data in internal storage; no tricks or workarounds needed. So I stand by my statement. Especially as the file manager I now use doesn't have this issue.

Categories

Resources