I am using the Darkforce ROM of WM 6.1, after I insert a SD in my Universal, I found that aa file generated automatically called "EncFiltLog.menc". It will continuous exist no matter I deleted it or not.
Anyone know what is "EncFiltLog.menc"??
By the way, I am using Transcend 16GB SDHC. Today, I found that my PPC can't detect it suddenly, I tried to insert it on my NB, but there are some files halt! When I double click it and wait for a moment, a messege box appear and say there are some problem about I/O device. No any device can detect my card now, anyone know what's the issue? I even can't format it now...
Please HELP!!
THANKS YOU VERY MUCH!
.menc files
.menc files are encrypted files.
When you set the option to encrypt files (Start\Settings\System\Encryption) then anything new that is saved to your SD card will be encrypted (and will have this extension - although this extension doesn't appear when viewing from the device that encrypted the files).
To read the file, you must view it via your device. (You can view/transfer it onto your PC via active sync from the device that encrypted it).
If you have reflashed your device without backing up your SD via active sync, then I don't think there is any way of recovering the file . (NB. I copy everything from my SD card to my computer before reflashing, and then copy it all back again ).
Hi my friend!
I had the same issue but with things 4.1 ROM. I don't know how, but i tried every day to format my sd card, and after 5 days it worked I have also this file in the root... It's the encryption file i think...
Mine was a 2GB panasonic SD not an SDHC... Keep trying!
Thanks for all reply!
But I found that I haven't tick the option of"Start\Setting\System\Encryption" , but the file still exist! I don't know why...
Any my SD issue....
I an using this ROM for few weeks already, but not newly flashed. My SD have no problem before. Haven't backup the datas is my mistake! I am so regreted. My SD is now can't detect from all device, and I can't format it also.
ALL DATAS ARE LOST!! Just wanna cry!
damaged sd-card!
Hi! Had the same problem with my new kaiser. Also thought about problem of ROM or the device itself. But it was just the SD-Card itself. Bougth a new one - no probs anymore...
any true solutions to this?
I have this same problem, so the only way to fix it is to get a new card?
Step By Step To Delete File EncFiltLog.menc (EFLG.m)
1) Insert your SD into Card Reader Cut EFLG.m
2) Paste insde your PC
3) Defrag your SD card
4) Select Option Tools>Folder Options>View Select Show hidden file
5) Now you can see new folder ie File 0000
6) Delete the folder
7) Now your SD card become as original
I read somewhere (http://forum.xda-developers.com/showpost.php?p=2718217&postcount=9) that the hidden file "EncFiltLog.menc" is stored on every SD-Card by WindowsMobile weather encryption is activated or not.
So it should be no problem to have it on the card - as long as everything works.
I received my Note Pro (WiFi) on Wednesday.
It really is superb and I am loving it, however I have a really irritating problem.
When connecting to my PC and attempting to transfer content to the Micro SDCard (SanDisk 64gb - mainly video files) the connection frequently drops causing the transfer to fail. Sometimes it is fine for a file or two, sometimes it fails on the first file. The PC then cannot see any content on the card untl I reboot the Note Pro.
Any ideas?
Please note:
1) I have tried two other cards, another 64gb SanDisk and a 32gb Samsung but this happens with all transfers (suggesting its not the card)
2) All cards work fine in my Note 3 and Note 10.1 2014
3) Transfers to the internal memory are fast (on USB 3.0) and work fine (suggesting it is the Note Pro)
4) Transfers from my PC to my Note 3 and Note 10.1 2014 work fine (suggesting it is not the PC)
5) The problem occurs with both USB 2.0 and USB 3.0 transfers, and with various cables to any PC port
6) My MX Player Pro app cannot delete files from the SDCard but can see them
7) Some apps (e.g. My Drives) cannot see the SD Card but the stock apps can all see the content and delete/modify files
8) I have tried reformatting the cards both in the Note Pro and the PC but that makes no difference
9) I have used Kies 3 to re-install the USB drivers but this didn't cure the problem
As my primary use for the tablet is watching pre-downloaded video on my commute to work this is very frustrating.
It might be that this is a firmware problem that gets sorted as the device becomes more available and I am working round it atm.
Any help would be appreciated.
ashtonsd said:
I received my Note Pro (WiFi) on Wednesday.
It really is superb and I am loving it, however I have a really irritating problem.
When connecting to my PC and attempting to transfer content to the Micro SDCard (SanDisk 64gb - mainly video files) the connection frequently drops causing the transfer to fail. Sometimes it is fine for a file or two, sometimes it fails on the first file. The PC then cannot see any content on the card untl I reboot the Note Pro.
Any ideas?
Please note:
1) I have tried two other cards, another 64gb SanDisk and a 32gb Samsung but this happens with all transfers (suggesting its not the card)
2) All cards work fine in my Note 3 and Note 10.1 2014
3) Transfers to the internal memory are fast (on USB 3.0) and work fine (suggesting it is the Note Pro)
4) Transfers from my PC to my Note 3 and Note 10.1 2014 work fine (suggesting it is not the PC)
5) The problem occurs with both USB 2.0 and USB 3.0 transfers, and with various cables to any PC port
6) My MX Player Pro app cannot delete files from the SDCard but can see them
7) Some apps (e.g. My Drives) cannot see the SD Card but the stock apps can all see the content and delete/modify files
8) I have tried reformatting the cards both in the Note Pro and the PC but that makes no difference
9) I have used Kies 3 to re-install the USB drivers but this didn't cure the problem
As my primary use for the tablet is watching pre-downloaded video on my commute to work this is very frustrating.
It might be that this is a firmware problem that gets sorted as the device becomes more available and I am working round it atm.
Any help would be appreciated.
Click to expand...
Click to collapse
Are you able to check out logcat to see if it is spitting out any errors?
Logcat
I have repeated the process a few times but cannot see anything obvious in logcat. There are certainly no errors in the log immediately after the event.
logcat.zip file attached.
I'm having a similar issue when transferring a 1.3g video file from my notepro storage to the micro sd card.... It starts to transfer the data and then fails.
It's like the sd card had been removed as when I look at the sd card using a file Explorer it is accessible but all info on the card isn't present. If I unmount the sd card I can't remount it, I have to manually remove the card and put it back in to see any info on the card!!!!
Definitely a faulty sd card reader or a bug in the firmware!!!
Sent from my SM-P900 using xda app-developers app
extrememonkey said:
I'm having a similar issue when transferring a 1.3g video file from my notepro storage to the micro sd card.... It starts to transfer the data and then fails.
It's like the sd card had been removed as when I look at the sd card using a file Explorer it is accessible but all info on the card isn't present. If I unmount the sd card I can't remount it, I have to manually remove the card and put it back in to see any info on the card!!!!
Definitely a faulty sd card reader or a bug in the firmware!!!
Sent from my SM-P900 using xda app-developers app
Click to expand...
Click to collapse
Well at least I know I am not going mad :laugh:716
Samsung will need to sort this out quickly with the impending release of the Note Pro in the US on 13th Feb.
I hope it can be fixed with a firmware update.
extrememonkey said:
I'm having a similar issue when transferring a 1.3g video file from my notepro storage to the micro sd card.... It starts to transfer the data and then fails.
It's like the sd card had been removed as when I look at the sd card using a file Explorer it is accessible but all info on the card isn't present. If I unmount the sd card I can't remount it, I have to manually remove the card and put it back in to see any info on the card!!!!
Definitely a faulty sd card reader or a bug in the firmware!!!
Sent from my SM-P900 using xda app-developers app
Click to expand...
Click to collapse
Yes I know - whats the point of having a micro sd card slot if you cant write to the card!!! I know I can do this on my S4 and Note 2 and I used to be able to do this on my old 10.1 - all are rooted but that shouldn't make a difference!!!!
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:01 PM ----------
Just got off the phone to samsung support..... its definitely a problem with how 4.4 is implemented on the NotePro, even though the Samsung Support Guy did everything he could to blame my SD Card.
Hopefully a firmware update will fix it a little down the line.... so for the time being my micro sd card adapter is going to get a lot of use!!!!
Sent from my GT-I9505 using xda app-developers app
Looking around the net and looking at Note 3 and Note 10.1 (2014) forums there have been lots of problems when people upgrade to 4.4 and aren't rooted.
It looks like the permissions are set to disable write access to the ext micro card, if your rooted it's is easy to change these, if your not it can't be changed.
Samsung will need to change these permissions if they see fit and release an update. I have sent an email to Samsung support advising them of the issue and also advising them how to fix it..... Just have to wait and see!!!
Sent from my SM-P900 using xda app-developers app
ashtonsd said:
I have repeated the process a few times but cannot see anything obvious in logcat. There are certainly no errors in the log immediately after the event.
logcat.zip file attached.
Click to expand...
Click to collapse
Maybe a problem with SELinux permissions on the card? I see a lot of errors with Knox/SELinux from that logcat.
MTP is the media transfer protocol.
W/ContextImpl( 7677): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1464 android.content.ContextWrapper.sendBroadcast:377 android.content.ContextWrapper.sendBroadcast:377 com.samsung.android.MtpApplication.MtpReceiver.finishSync:606 com.samsung.android.MtpApplication.MtpReceiver$2.handleMessage:485
W/ContextImpl( 7677): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1464 android.content.ContextWrapper.sendBroadcast:377 android.content.ContextWrapper.sendBroadcast:377 com.samsung.android.MtpApplication.MtpReceiver.finishSync:613 com.samsung.android.MtpApplication.MtpReceiver$2.handleMessage:485
Click to expand...
Click to collapse
I/SELinux (13275): Function: selinux_android_load_priority [0], There is no sepolicy file.
I/SELinux (13275):
I/SELinux (13275): Function: selinux_android_load_priority [1], There is no sepolicy version file.
I/SELinux (13275):
I/SELinux (13275): Function: selinux_android_load_priority , loading version is VE=SEPF_SM-P900_4.4.2_0004
I/SELinux (13275):
I/SELinux (13275):
I/SELinux (13275): selinux_android_seapp_context_reload: seapp_contexts file is loaded from /seapp_contexts
I/JAM ( 2248): isRunningJackd : stopped...
W/System.err(13275): java.lang.NoSuchFieldException: SYSTEM_UI_FLAG_REMOVE_NAVIGATION
E/JAM ( 5470): print sendControlCommand error: Invalid argument
W/System.err(13275): at java.lang.Class.getField(Class.java:724)
W/System.err(13275): at com.sec.android.gallery3d.util.GalleryFeature.checkSystemUiVisibility(GalleryFeature.java:1517)
W/System.err(13275): at com.sec.android.gallery3d.util.GalleryFeature.init(GalleryFeature.java:320)
W/System.err(13275): at com.sec.android.gallery3d.app.GalleryAppImpl.getDataManager(GalleryAppImpl.java:229)
W/System.err(13275): at com.sec.android.gallery3d.provider.GalleryProvider.onCreate(GalleryProvider.java:126)
W/System.err(13275): at android.content.ContentProvider.attachInfo(ContentProvider.java:1591)
W/System.err(13275): at android.content.ContentProvider.attachInfo(ContentProvider.java:1562)
W/System.err(13275): at android.app.ActivityThread.installProvider(ActivityThread.java:5029)
W/System.err(13275): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4624)
W/System.err(13275): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4538)
W/System.err(13275): at android.app.ActivityThread.access$1500(ActivityThread.java:164)
W/System.err(13275): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1318)
W/System.err(13275): at android.os.Handler.dispatchMessage(Handler.java:102)
W/System.err(13275): at android.os.Looper.loop(Looper.java:157)
W/System.err(13275): at android.app.ActivityThread.main(ActivityThread.java:5341)
W/System.err(13275): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(13275): at java.lang.reflect.Method.invoke(Method.java:515)
W/System.err(13275): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1259)
W/System.err(13275): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1075)
W/System.err(13275): at dalvik.system.NativeStart.main(Native Method)
E/EnterpriseContainerManager( 2707): ContainerPolicy Service is not yet ready!!!
Click to expand...
Click to collapse
As a temporary workaround you should be able to transfer files to the sdcard using an external reader. I should be getting mine soon so I can test this out.
Is this an issue with all note pro 12.2s? just returned one and ordered another for this issue... Was able to transfer to main memory over WiFi then copy to SD card but transferring to the SD card over WiFi was a 50/50 chance if even that...
I was expecting a lot more reports once the tablet launched in the US but haven't seen too many so far.
It's a real pain but I can live with it. I'm waiting it out for firmware fix for now, but if that doesn't come then it's going back. There is time yet and I love the screen size too much to let it go...
Let us know how you get on with the replacement.
ashtonsd said:
I was expecting a lot more reports once the tablet launched in the US but haven't seen too many so far.
It's a real pain but I can live with it. I'm waiting it out for firmware fix for now, but if that doesn't come then it's going back. There is time yet and I love the screen size too much to let it go...
Let us know how you get on with the replacement.
Click to expand...
Click to collapse
Same issue with replacement and replacement card... Can not transfer files using WiFi to SD card... Can transfer to device then copy to SD card, hook up usb cable and transfer to SD card or transfer through a card reader... hopefully Samsung will get on this quick like... lol ya that made me laugh too
Exactly the same problem here with mine (UK). Hopefully Samsung will hop on it asap. Glad I don't just have a duff Note. Thanks! :good:
Is this just a problem with the UK version? I think I read somewhere the US version was coming shipped with an update that the UK version would soon be getting?.. If it makes anyone feel better, my US model has no problems at all syncing to the external over wifi..
The only problem I did run into was the changes of writing to the external sd with 4.4 Normally I would just make a folder anywhere on the external and sync my comics to it in the past.. but now, I had to copy my reader app to the external and then make the folder within that one in order to copy my books to it..
It looks like this is a widespread issue caused by Android 4.4. Since Samsung is running KitKat on these out of the gate, it seems to be a pretty widespread issue. From https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn:
KitKat will make your SD Card completely useless: per the Android API specification, apps can no longer write files to your SD card. And Samsung is following it.
This only applies to dual-storage devices, i.e., devices with a user-writable internal flash storage AND a removable SD card.
From http://source.android.com/devices/tech/storage/index.html:
"The WRITE_EXTERNAL_STORAGE permission must only grant write access to the primary external storage on a device. Apps must not be allowed to write to secondary external storage devices, except in their package-specific directories as allowed by synthesized permissions."
If your device has user-accessible internal flash storage, your SD Card is a "secondary external storage device".
What this means is that with KitKat, applications will no longer be able create, modify, or remove files and folders on your external SD card. As a for-instance, you can no longer use a file manager to copy files from your computer to the SD card over a network. This ability, which has existed since the beginning of Android, has been taken away.
The only stated reason for this removal of functionality is that, "Restricting writes in this way ensures the system can clean up files when applications are uninstalled." I do not pretend to understand this logic. Apps are still allowed to write in arbitrary directories on the primary storage (with the appropriate permission), but are denied the same access to external storage.
Samsung has implemented this feature with their KitKat OTA updates. Note3 users are now complaining that FX File Explorer can no longer write to their external SD cards. There are solutions to this problem for users with root access. Users without root access appear to be screwed.
I'm not quite certain how Google intends for you to place files on your SD card. Perhaps you have to use proprietary Google apps that contain permissions unavailable to the rest of the developer world. Perhaps you're supposed to put everything on the cloud and pay carrier data fees to get it there. Perhaps you're supposed to use some kind of WIRE to attach your WIRELESS device to your computer and have the computer do that work for you.
In my opinion this is a horrible misstep by Google and the Android Open Source Project. Functionality has been removed without reason, to the severe detriment of users and developers alike.
I apologize for not bringing this to everyone's attention when KitKat 4.4 was released, but it was not mentioned in the Android 4.4 changes document: http://developer.android.com/about/versions/android-4.4.html. It's only mentioned in the article on source.android.com. I was only made aware of its existence from user reports as a result of Samsung implementing this change in its KitKat OTA updates.
Click to expand...
Click to collapse
Now, there is a fix for this, but you need a rooted device.
Can it be that this is the culprit:
KitKat will make your SD Card completely useless:
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
bitpushr said:
It looks like this is a widespread issue caused by Android 4.4. Since Samsung is running KitKat on these out of the gate, it seems to be a pretty widespread issue. From https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn:
Now, there is a fix for this, but you need a rooted device.
Click to expand...
Click to collapse
Tried this on my GalaxyNote Pro, and the fix for the N9005 as described is working . Titanium backups and Appmonster backups are now stored on the ExtSDcard.
bitpushr said:
It looks like this is a widespread issue caused by Android 4.4. Since Samsung is running KitKat on these out of the gate, it seems to be a pretty widespread issue. From https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn:
Now, there is a fix for this, but you need a rooted device.
Click to expand...
Click to collapse
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Working for me as well!
Android.Ninja said:
I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Is not working for me. Lost ability to see my sd card and all apps where failing. ALOT!! Not exactly sure what the issue was. I had to reflash using odin twice to fix the issue. Also before reflashing it seems I lost the ability to write to either sd card. Internal or external.
Got it to work o the second try. Make sure the format is exactly the same when you add the new line or things go crazy
Sent from my SM-P900 using XDA Premium HD app
I went to Wal-Mart and picked up a 64GB SD card. I just purchased the tablet yesterday and rooted it using towelroot but that's all I've done. I put the SD card in and it's recognized and showing the correct available space. I'm able to create a file using ESFile explorer but I can't do anything with it. I tried a couple torrent clients to download files to the SD card and it keeps saying unable to write to folder or that it's write protected. When in file explorer I can create a file and under properties it does show it's able to be written to. I also have downloaded and tried the kitkat SD card fix app. I've gotten pretty frustrated with it so just did a complete factory reset and going to start from scratch. I was able to move apps to SD card using an app but that's all I could do. I'd really like to put any/all downloaded apps and files on the SD card since I only have a 16GB version.
Any ideas what I can do?
ToiletDucky said:
I went to Wal-Mart and picked up a 64GB SD card. I just purchased the tablet yesterday and rooted it using towelroot but that's all I've done. I put the SD card in and it's recognized and showing the correct available space. I'm able to create a file using ESFile explorer but I can't do anything with it. I tried a couple torrent clients to download files to the SD card and it keeps saying unable to write to folder or that it's write protected. When in file explorer I can create a file and under properties it does show it's able to be written to. I also have downloaded and tried the kitkat SD card fix app. I've gotten pretty frustrated with it so just did a complete factory reset and going to start from scratch. I was able to move apps to SD card using an app but that's all I could do. I'd really like to put any/all downloaded apps and files on the SD card since I only have a 16GB version.
Any ideas what I can do?
Click to expand...
Click to collapse
Well just an update after doing a factory reset everything seems to work now, of course i get to download everything again. I think it might have had something to do with the OTA update. After doing the factory reset it kept the update. Now I can freely move to and from the SD card so all is good.
FYI, since you are rooted I would suggest installing the Xposed Framework and then install the "HandleExternalStorage" module, the KitKat update cripples external SD card access so file managers, emulators, and the like can no longer write to the SD card. Installing this module re-enables external SD card read/write access for all applications, it is not the device. There is also an app on the Play Store call 'SDFix: KitKat Writable MicroSD' which accomplishes the same thing, however the Xposed module is much safer as it can be enabled and disabled at will. Simply install the module, enable it, and that's it.
Did the platform.xml fix to enable external sd write, but then got "not enough space.
Hello all. I couldn't post this as a reply to anything (not enough posts) so I put a new thread here to share my experience for the possible benefit of others with the same problem.
I have a rooted T-Mobile Galaxy Note 10.1 2014 edition (SM-P607T) running stock kitkat 4.4.2 (uvuane2 fw). I did the platform.xml manual fix to enable external sd card writing, but in every file manager in which I tried to move a file (root explorer, ES, even TW My Files) only a few MB would move and then I would get an insufficient space error. I knew this couldn't be right as I was using a 32gig sandisk with almost nothing on it. I had previously used this card in my Note 2 SGH-T889 also running 4.4.2, which had created the "Android" and "lost.dir" folders on the card. I wondered if something in those folders was interfering with write, or perhaps a filesystem issue. So I formatted the external sd from settings and bingo, the write suddenly worked! Anyone have any thoughts as to how and why?
Cheers...Kittie
(Correction: In ES and My Files, I got insufficient space error, but in Root Explorer, I got the "restricted write access 4.4.2 nothing we can do etc." popup.)
In every 2 or 3 months the memory card automatically gets the unreadable file names in the root directory while other folders and files on root are working perfectly.
I searched and found out that the default apps in TouchWiz for photo gallery and files are causing such issues, therefore i installed third party apps for gallery and file navigations, but same problem occurs again.
i tried to delete through windows but its giving error while deleting.
Snapshots attached.
Memory Card info: Kingston 32gb micro sdhc4
Mobile : Samsung GT-19305 (non rooted)
Android Version : 4.3 Jelly Bean
Please forgive if this or similar to this question was previously answered.
I have had a similar issue whenever i remove my usb or sd card without ejecting it. Put your sd card in a card reader. Backuo your data then delete partition by using minitool partition wizard. Recreate partition. Check for disk errors then, in the properties of sd card. It will be good to go.
Hit THANKS if I helped you
------- Bilal -------
Thanks bilal for sharing your expertise with me. Yes, this is the only method left to make my sd card again usable. but transferring the data is headache. isn't there any other option left??
If you want to get it all fine and clean you need to either format it or recreate partition. Its up to you otherwise there are minimal chances of sending those chinese files away. Mine wasn't deleted so i recreated partition...!