hoi board
i have made a clean install of the latest CM13 nightly to my serranoltexx
all went fine exept CM13 claims my sd card is corrupted:
Corrupted SD Card
SD Card is corrupt. Touch to fix it.
- i can use the sd card in TWRP
- i can use the sd card in CM11
- i can use the sd card in CM12.1
- i can use the sd card in my PC
no errors there.
it is a 32GB microSDHC CLASS10 card formatted with exFAT
so my question is: how can i tell the CM13 that the card is okay and
let the rom use it as usual?
some more info to help getting qualified answers:
- formatting the card IS NOT AN OPTION!
- I DO NOT WANT TO ADOPT THE CARD!!!
more more information:
- is it correct that MM/CM13 only supports fat32 or vfat on external storage?
EDiT: sd card is working as usual for me since 2016-01-02 nightly!
Not necessarily. What filesystem do you have on it? It could be that I need to add selinux policies for nonstandard filesystems. MM is a ***** now regarding security, so some tweaking might be required.
more additional infos
arco68 said:
Not necessarily. What filesystem do you have on it? It could be that I need to add selinux policies for nonstandard filesystems.
Click to expand...
Click to collapse
it is exFAT
i added the info also in the first post.
arco68 said:
MM is a ***** now regarding security, so some tweaking might be required.
Click to expand...
Click to collapse
sounds somehow familiar.
Should be fixed in next nightly.
roger that!
i will report back.
thx 4 the efforts :good:
Same issue with my jflexx samsung galaxy s4 international.
I had to roll back to cm12.1 as a result.
well...
i am quite curious.
browsed the git some seconds ago and i have the feeling
there is a discussion if VOLD or FUSE handles the exfat volumes
on external sd cards and should it be on vendor (CM13) or
device (android_device_samsung_msm8930-common) level.
also i think that it is not so easy to get something like that
realized at vendor (CM13) level, what seems to be preferred...:fingers-crossed:
i stay curious though :silly:
post scriptum: 129 views to this topic is a huge number, i searched like crazy before i opened this!
a new hope!
Code:
Change 126277 - Merged
cm: sepolicy: fix denials for external storage
Change-Id: I784a859671c69370cab0118a88a5fb0190352af9
CyanogenMod/android_vendor_cm
http://review.cyanogenmod.org/#/c/126277/
:victory:
@arco
is this somewhat of a frozen hell?
Sometimes complaining do help. [emoji14]
roger that!
well done dev!:good:
issue solved ...
i flashed the 2016-01-02 nightly an sd card is working as usual. :silly:
I've never been able to get my 64GB SDXC card to merge. When I do try, it hangs and get some sort of error then I have to use a program on PC to be able to identify my card and reformat it. Tried every system format you can think of...... I'm going mad with this lol
I have the same false notification but on AOSP 6.0, Can anyone tell me what I must change.
Samsung N5110
Hi, I am having the same issue reported above with the latest nightly of cyanogenMod 13. Are you able to explain how to solve the issue.
Thanks
I've had this issue tons on CM13 but never found a solution. Often a reboot fixes it. The mSD always works fine in a PC or from TWRP but CM just says it's corrupted.
Tried reformatting before, usually fixes the issue temporarily. Seems to trigger again eventually, possibly with a new build - so it could be TWRP or update related. Usually happens on boot, sometimes spontaneously. Might see if I can get a catlog but given how random it is, might be tough.
Pretty certain this is an issue with CM. Not had this on stock, had it with two different devices both on CM. Pretty sure its happened with multiple mSDs. Could be exFAT related?
What about supporting f2fs too? I get tons of messages in CM13 regarding a corrupted sdcard, but the card is regularly mounted by a userinit.sh script and is working ok. I also notice a drop in performance, with some short freezes, just before the system display one message for each f2fs partition on external sdcard.
droident said:
I've had this issue tons on CM13 but never found a solution. Often a reboot fixes it. The mSD always works fine in a PC or from TWRP but CM just says it's corrupted.
Tried reformatting before, usually fixes the issue temporarily. Seems to trigger again eventually, possibly with a new build - so it could be TWRP or update related. Usually happens on boot, sometimes spontaneously. Might see if I can get a catlog but given how random it is, might be tough.
Pretty certain this is an issue with CM. Not had this on stock, had it with two different devices both on CM. Pretty sure its happened with multiple mSDs. Could be exFAT related?
Click to expand...
Click to collapse
Thanks for your information. I like others have this issue on with 128 GB exFAT formatted card (using SDFormatter tool). Everything works fine (TRWP, and Windows 7 PC) without issue over multiple boots to and from my phone except that CM is reporting (incorrectly) that my SDXC card is corrupted. Formatting inside of CM13 does NOT solve the problem and actually never completes - CM hangs at 20% completed for my card and never moves forward - so it's hung - except that it doesn't do a Force Close. Every single reboot that I've tried with CM 13 or CM 13 based ROMs (like RR) respond with the same incorrect error message. No problems with CM12 based ROMs. Have also tried the XDA FixExtSD thread and that doesn't help at all either - after correctly saving (on my PC) and using TWRP to install the ZIP file (which TWRP sees fine) - still reboot system in CM with same error - it doesn't go away for me. To me this is a bug in CM13. I'm giving up on CM13 based ROMs (for now) and going back to CM12 where I can using my SD card as an external storage medium.
well...
almost a year later i can resume: it does not get better at all!
i am on 4.4.4 [2016-02] and have to admit, that neither CM12.x nor CM13
can offer the same reliability as CM11.
sadly.
jrchester said:
Thanks for your information. I like others have this issue on with 128 GB exFAT formatted card (using SDFormatter tool). Everything works fine (TRWP, and Windows 7 PC) without issue over multiple boots to and from my phone except that CM is reporting (incorrectly) that my SDXC card is corrupted. Formatting inside of CM13 does NOT solve the problem and actually never completes - CM hangs at 20% completed for my card and never moves forward - so it's hung - except that it doesn't do a Force Close. Every single reboot that I've tried with CM 13 or CM 13 based ROMs (like RR) respond with the same incorrect error message. No problems with CM12 based ROMs. Have also tried the XDA FixExtSD thread and that doesn't help at all either - after correctly saving (on my PC) and using TWRP to install the ZIP file (which TWRP sees fine) - still reboot system in CM with same error - it doesn't go away for me. To me this is a bug in CM13. I'm giving up on CM13 based ROMs (for now) and going back to CM12 where I can using my SD card as an external storage medium.
Click to expand...
Click to collapse
I formatted the card to EXT4 and it's improved things massively. No more hanging/crawling transfers and no more surprise unmounts - just really quick bug-free transfers between the internal and external. Been using for a couple of weeks now.
This has led me to one conclusion: exFAT support in CM is horrible. It should either be fixed or dropped entirely.
PS. Mine is also 128GB. I was toying with sending the card back until I switched over to EXT4.
droident said:
I formatted the card to EXT4 and it's improved things massively. No more hanging/crawling transfers and no more surprise unmounts - just really quick bug-free transfers between the internal and external. Been using for a couple of weeks now.
This has led me to one conclusion: exFAT support in CM is horrible. It should either be fixed or dropped entirely.
PS. Mine is also 128GB. I was toying with sending the card back until I switched over to EXT4.
Click to expand...
Click to collapse
Excellent tip. I will try EXT4 then. Possible issue with Win7 exchange, but I'll try Paragon's ExtFS for that. I have MiniTool Partition Wizard for the EXT4 partitioning. For data on my 128GB SDXC card, I have large collection of music flac and wav files and some other misc jpg photos, and of course I want to store ROMs and TWRP backups etc on the same card. I will report my findings later in a couple of days. I'm hoping that it works for me too, because I really would like CM13 or ROM based on CM13 (like latest RR). I'm trying it on my NOS (New Old Stock) LG G3 - which is new for me. Thanks again -
Related
okay, i've tried and looked for a similar issue but so far i can't find anything related.
I have a sandisk microsd ultrahc card 16gb.
the card itself works extremely well, both in my device when using the stock / custom samsung based roms,
Didn't really notice this untill i tried out android 4.3, at wich i thought first could be a bug in the rom, the settings kept fc'ing the moment i opened up the storage part, and a com.android.media kept fc'ing the moment i attached the usb cable.
as i thought 4.3 was the culprit i flashed 4.2.2 wich also had similar issues up until the moment i removed the card from my device and restarted, everything worked smoothly afterwards.
I've tried using exfat / fat32 both with cluster of 4096 and 8192 and neither of those helped in any way. Turns out that both TWRP and CWM (yes i tried it in both) also can't seem to mount the sd-card.
Is there any workaround for this issue? or do i have to get myself another sd-card?
I think it's the ROMs man messing things up...i tried android 4.3 yesterday and my whole android directory changed like I had to go into a folder called 0/0/0/my android files. to reach my files etc couldn't mount from sdcard couldn't copy things across from pc...I just flashed back my original stock firmware and everything is good..... android 4.3 is pretty messed up..give it time to mature still very buggy
Sent from my GT-N7105 using Tapatalk 2
The messed up folder i should get used to thoug its because of the multiple user profiles things are getting a bit messy.
Its something they added in 4.2.2 i believe
Best way to do it is to flash the rom and afterwards copy back everything to the sdcard.
Didn't have any issues with another sd card i still had laying around but that thing even thoug class 4 doesn't get more than 1mbps transfer speed.
Sent from my GT-N7105 using xda premium
if the sdcard works on your pc with directly like by using an mmc adapter or sdcard to USB converter then your card is ok if it just didn't work on the phone it has to be a software issue our maybe the hardware mmc port is faulty??!
Sent from my GT-N7105 using Tapatalk 4
thats just it, the sd card works like a charm untill i upgrade to 4.2.2 or 4.3. however both recoveries can't mount the sd-card either.
its not one of those black ones that goes to class 10, but an ultra hdsc class 1 so might be something related to not being able to work properly with anything higher than class 10
nope....the class issue has nothing to do with software.....that's purely the job off the chip electronics/hardware.... I would say a combination of your recoveries and ROMs like I had the same issue once the custom recoveries maybe can't point to the location/ section of the memory card...try changing to different version of the recovery...maybe that could help but be sure the recovery is supported on your device...these are risky issues...so only do it at your own risk
Sent from my GT-N7105 using Tapatalk 4
i've tried several versions of CWM both touch and normal, also philz (yesterday but touch didn't work as it should so won't stick with that one) and TWRP but none of them could mount/find the external_sd, the only think properly working with that sd card is the stock samsung and custom roms based on stock.
(not particulary fond of TWRP, i like the layout and how it works, i just don't like the backups of that recovery, can't copy them to my computer, the extensions keep giving me an error and they are located on the phone's storage)
the sd card couldn't be found in my sensation xe neither i remembered just now after i stopped using the 4.0 stock rom and switched to custom roms, at the time i didn't really see a connection and thought my sd card just didn't want to work properly in my sensation anymore, But having the same issues, and using another sd-card in the phone worked again. Used the ultra sd card in my tabled and because i didn't use that one anymore and someone in my family needed a 16gb one for tomtom europe i gave my good one away )
gonna get myself a new sd-card this afternoon as the 8gb i had laying around isn't getting higher transfer speeds then 1mbps at most even if its a class 4. a shop nearby has a class 10, 16gb for 13 euro's so reckon thats not a bad deal, might even go for the class 10 32gb for 26 euro's if they have it in stock.
I have a 64gig card and had similar problems. With phils recovery it only works when formatted fat32. Think that exfat is not supported. With stock kernel it mounts exfat with any other kernel i tried it would only mount fat32. I think samsung kernel has support for exfat and others dont. So it might not be adroid related but kernel related.
Grumps said:
I have a 64gig card and had similar problems. With phils recovery it only works when formatted fat32. Think that exfat is not supported. With stock kernel it mounts exfat with any other kernel i tried it would only mount fat32. I think samsung kernel has support for exfat and others dont. So it might not be adroid related but kernel related.
Click to expand...
Click to collapse
weird thing is though, even when formatted to fat32 and not exfat, android 4.2 and 4.3 will not recognise my card, also the recoveries i only get an error when i want to mount my sd-card
my tablet which is running an aosp version of android 4.0 or 4.1 (can't quite remember) could handle the sd-card just fine, while both my phones have issues with it.
solved it by buying myself a new sd card, ^^ now i can at least safely backup to my external card instead of the internal memory.
Hello everyone,
I am experiencing an odd issue with my G PAD 8.3. It seems to randomly "appear" that the microSD is unmounted (when i check my filemanager, i am unable to enter /storage/external_SD... However, when I go to settings -> storage, the SD card is not exactly unmounted as I still have the Unmount SD card option still available. When I check the usage though its showing as 0GB. So what I do is, I unmount the SD from the settings menu, then remount it from the same menu thereafter. It will fix the issue, but after some time, it will again show as mounted but 0GB used.
My current setup is:
ROM: Slimkat 4.4.4 latest weekly build
Sdcard: 32 GB Sandisk
What I suspect is either of the following:
1. A bug with the ROM (since there isnt a stable release of Slimkat on the g pad)
2. An issue with the microSD. It might fail soon
3. An issue with one of the apps. Might be worth noting that I have foldermount installed on my tablet. since it is an application that mounts and unmounts directories from the microSD, perhaps this may cause the problem, though i havent seen anyone who have experienced a similar issue.
Any ideas what could cause this?
jarod004 said:
Hello everyone,
I am experiencing an odd issue with my G PAD 8.3. It seems to randomly "appear" that the microSD is unmounted (when i check my filemanager, i am unable to enter /storage/external_SD... However, when I go to settings -> storage, the SD card is not exactly unmounted as I still have the Unmount SD card option still available. When I check the usage though its showing as 0GB. So what I do is, I unmount the SD from the settings menu, then remount it from the same menu thereafter. It will fix the issue, but after some time, it will again show as mounted but 0GB used.
My current setup is:
ROM: Slimkat 4.4.4 latest weekly build
Sdcard: 32 GB Sandisk
What I suspect is either of the following:
1. A bug with the ROM (since there isnt a stable release of Slimkat on the g pad)
2. An issue with the microSD. It might fail soon
3. An issue with one of the apps. Might be worth noting that I have foldermount installed on my tablet. since it is an application that mounts and unmounts directories from the microSD, perhaps this may cause the problem, though i havent seen anyone who have experienced a similar issue.
Any ideas what could cause this?
Click to expand...
Click to collapse
Lookup sandisk sdcard problems on google.
Sandisk was having issues with some of their cards. Pop in a different one to make sure its not the tablet.
sleekmason said:
Lookup sandisk sdcard problems on google.
Sandisk was having issues with some of their cards. Pop in a different one to make sure its not the tablet.
Click to expand...
Click to collapse
Thanks mate, ill pop one right in when I find one lying around. I might also try to slow format to FAT32 and then format the card using the tablet and see if it helps.... Just wondering if anyone else is having a similar issue. Been googling around, and the closest things I can see are people that are having issues when their microSD randomly gets unmounted... in my case its not really unmounted, just showing capacity is 0 and after a umount/remount cycle, it works again then shows 0gb again after some time...
Thanks for your response.
jarod004 said:
Thanks mate, ill pop one right in when I find one lying around. I might also try to slow format to FAT32 and then format the card using the tablet and see if it helps.... Just wondering if anyone else is having a similar issue. Been googling around, and the closest things I can see are people that are having issues when their microSD randomly gets unmounted... in my case its not really unmounted, just showing capacity is 0 and after a umount/remount cycle, it works again then shows 0gb again after some time...
Thanks for your response.
Click to expand...
Click to collapse
Same issue here.
Slimkat v4.4.4 latest weekly build
SanDisk 32GB ultra class10
Not using that folder app and SD worked normally before slimkat so I assume it's rom bug, and it's sad and I'm thinking about going back to stock. And one more thing - installed SD monitor and SD unmounts on screen off and then remounts when you turn screen back on. As no problems were detected on stock kitkat I think it's another bug of slimkat. Where can I report it?
I do not trust SanDisk anymore. Most of my earlier trouble was caused by a bad card that failed way to early from them.
I trust sandisk more than anything, but this case was just coincidence. My problem was resolved, when I downgraded back to 4.2.2 stock and then I could do what I wanted, currently I have slimkat again and almost 24hours no unmounts
I just flashed the latest CM nightly for MM and when I put my SD card in the phone it says its corrupt. I do the reset with the phone to wipe it and after its done I only have 15MB instead of 64GB. Is there a manual fix for this or is it something I just have to wait for CM to do? I have the G3 D852 with latest TWRP.
OptimusOBrien said:
I just flashed the latest CM nightly for MM and when I put my SD card in the phone it says its corrupt. I do the reset with the phone to wipe it and after its done I only have 15MB instead of 64GB. Is there a manual fix for this or is it something I just have to wait for CM to do? I have the G3 D852 with latest TWRP.
Click to expand...
Click to collapse
It looks like you're going to have to wait for a long while to see exFAT get fixed, and yes, I am in the same boat as you are so I literally feel your pain, but that said, when the OS asks me to format the Samsung 64GB EVO microSD card, it gets formatted to FAT32, which is absolutely useless for large files that are more than 4GB, and I have a LOT of FAT32-UNFRIENDLY files that I need on my microSD card, so Android Marshmallow is officially off the cards for me until that problem is fixed.
I have the same problem.
When I format to swapable sd card, I end up in 16MB.
When I format it to internal storage, the formatting stucks at 20% and after a few minutes I get a toast message with "java.util.concurrent.timeoutexception blah blah" and I have to reformat the card on my computer.
Looks like moving on from 5.1 to 6 was one of my biggest mistakes since I have a smartphone.
//Edit
I see there is already a thread about this. Cheers!
http://forum.xda-developers.com/lg-g3/help/android-m-sd-card-formation-stuck-20-t3259186
Exact same boat as everyone here. 64gb card shows as 15mb. If I format it as internal storage, I get the timeout exception. Didn't even realize I was upgrading to cm13 when I hit the update through OTA. It's came in the same list as cm12.1 nightlies. Of course since I didn't realize I booted it up without flashing gapps for 6.0 and was stuck the entire day trying to wipe clean, flash and restore backups from titanium. Android wear doesn't function properly, BT pairings get deleted on every reboot, SD card is screwed, the list goes on. Such a silly way to include it through OTA update without any warning.
Good news folks!
For those users who have flashed finnq's CM13 nightlies (20151219 onwards), you can now use exFAT-formatted microSD cards - all you need to do is flash the Nebula Kernel:
http://forum.xda-developers.com/lg-g3/development/kernel-nebulakernel-rev6-5-build20150715-t3161768
All this because I wanted to free up space to install Grim Fandango...
I backed up my Samsung 64 gb card on my laptop and then reformatted my card as internal so I could use AppMgr III to move apps over. Now, I'm stuck with my SD card saying "checking...", and it doesn't recognize the card on my laptop.
Any ideas?
Fixes coming....
There are proposed changes currently sitting in code review at CyanogenMod. The changes have not yet been approved or merged. Here is a ROM image for LG G3 d850 that includes the proposed changes to fix the exFAT problem as well as the GPS problem. They work for me. YMMV. Use at your own risk!
cm-13.0-20160101-UNOFFICIAL-d850.zip
Ive just installed the new CM 13. Everything is working fine more or less but I still got one major problem. When I format my sd card to use it as an internal storage, it gets stucked at 20 percent. After sometime it gives me a timeout error, so i cant use that Android M feature and my SD card. Does anybody know a solution?
Thanks a lot
BR
I think your not alone , it's a bug from the cm13 build for now do not sd card on cm 13
Envoyé de mon LG-D852 avec XDA Forums Pro.
You are not alone.
Thanks a lot for the repsonse Ive just realized that my sim card is not detected? Any ideas? Ive reinserted the sim card and wiped cache
Not alone. Me too! If I format as external storage shows 15MB on a 64GB card. Format as internal and gives timeout error. Stuck with a dud for now. Didn't realize when I hit update through OTA updates that it was CM13. Unfortunately, stuck with it for now.
amitabh15 said:
(...)
If I format as external storage shows 15MB on a 64GB card. Format as internal and gives timeout error.
(...)
Click to expand...
Click to collapse
I have exactly that problem, too!
So we have to wait a few days until it's fixed. Welcome to cm-nightly
same problem here,
also noticed that whatsapp won`t download or upload media.
So I was looking at the build for 11/28 for vs985 and found that... Fix mounting of non-FAT formatted SD cards (2/2) (android_packages_providers_MediaProvider) Fix mounting of non-FAT formatted SD cards (1/2) (android_frameworks_base) so the SD card mounting should be fixed if I am not mistaken because it clearly says Fix for the NON-FAT formatted SD cards.....I haven't tried the format because I have way too much music on my 64 gb card. Anyways whoever has the vs985 and is continuing to flash the nightlies keep us all up to date on the SD card fixes. I am going to revert back to 5.1.1 for my music on my sd card. Probably the only downside to the CM13 builds.
Edit:
Caught Bug/s: When taking pictures the image doesn't show. CM13 11/30 build.
The nightly I used already included these:
Fix mounting of non-FAT formatted SD cards (1/2) (android_frameworks_base)
Fix mounting of non-FAT formatted SD cards (2/2) (android_packages_providers_MediaProvider)
And it didn't work for me.
Haven't tested it with the current nightly, yet. Anyone else maybe?
Still doesn't work in latest nightly
Did you try to update today's version ?
I have updated it, of course. There is still too much to fix, so I try to take every update. [even when it doesn't makes sense ]
But I haven't tried to format the sd card since cm-13.0-20151129-NIGHTLY-d855.zip
Were there any changes? Haven't seen any related to it in the changelogs...
Doesn't Work here eather...
Im on the latest nightly and I have my full sd card after formatting
You mean "cm-13.0-20151207-NIGHTLY-d855.zip", right?
In that there was a change: vold: Fix native exfat driver support (android_system_vold)
Maybe that's what we were looking for.
http://www.cmxlog.com/13/d855/
Did anyone have any luck with the 07 build?
I'm on business trip right now and will be back home this evening (gmt+1).
Then I will try on the 07-build and report back.
Nope.
Stuck at 20%, timeout after a while.
07. Dec Build.
confirm half-working sd card on 11. dec build.
formatting and using as external drive works pretty fine. Formatting working, mounting, too.
I'm using a 64gb card and I have all available (not 15mb anymore etc).
Only probelm I found out was after formatting as internal drive.
The card got formatted, but when I was asked to move files, I got a force close of the settings. So it was not possible to let android move over files automatically.
Same here with 15dec build
After i flash cr droid rom my phone doesnt read my sd card, it appear to be formated first, but getting message sd card not suported , any solution??
I'm not much of an AOSP ROM user on this device. But as far as I know, this is a common issue (or at least, it was) on AOSP ROMs.
This happened a lot on my old Samsung Tab Pro 8.4 on a few different AOSP ROMs. What sometimes worked for me, put the SD card in a USB card reader, connected to Windows PC. A dialogue box appeared asking to fix errors on the SD/drive. I picked the default selection, which was to fix error by some quick/fast method (forget the exact wording) which only took a few minutes, and retained the data on the card And then the SD would work again.
Although this didn't work every time, but did the majority of times I got this error. In the remaining cases, you may need to reformat the SD.
Known issue on current Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=70512755&postcount=434
i can confirm what ckpv5 said in the linked post above
i had a similar issue
64GB card not working as it should,i can read the files without issues but when i write anything to it ( by any method to transfer data ) the data got corrupted
32GB card working fine with out issues at all
Sent from my HTC M8 using XDA Labs
ckpv5 said:
Known issue on current Nougat ROMs
Click to expand...
Click to collapse
Good to know. I guess I should have figured there were some hardware hiccups on the Nougat builds.