Did the update to my S5 from rooted NCG to rooted NI2, everything works great BUT having a major camera issue.
When I take a picture, and immediately review it from within the camera app, it does something to the picture. They show up as a grey screen. When I try to review them in the gallery, they show up as these grey broken thumbnails. I can't send them via MMS. It says "can't send file".
Now, if I take the picture, back out of the camera app, and ONLY review them in the galley app, they are fine. This only happens if i review them with in the camera app.
Now, here's the thing , this only happens when the pictures save to the SDcard. If it saves to the Phone's storage, there's no problems.
Didn't happen on NCG. Does this have something to do with the Secure Storage glitch related to Root and Xposed? I just deleted the secure storage module, and it's still happening. (Don't use S-Health so it didn't matter).
Is there anything I can do. We just had triplets, and we're taking A LOT of pictures, and just realized I've lost half of my pictures. This sucks.
Do I re-install the stock camera app? If I do, where do I find it?
Please help. Having root, isn't worth not being able to use my camera.
Can't format SD Card, SD Card is Write Only?
Since this issue is only happening when the photo's are saving to the SDCard, I attempted to FORMAT the card.
Using the phone to FORMAT, the phone UNmounts the card, says preparing, and REmounts the card exactly as is, without formatting it.
So I tried to reformat it on the computer, three different times, three different programs including the Windows 7 utility, ALL of them gave me the message that my SD Card is WRITE ONLY?
What the heck is that? Did the NI2 update do something to my SD card? Did it corrupt my SD Card?
Any one have any ideas? Guesses? Similar experiences?
ymDroid said:
Since this issue is only happening when the photo's are saving to the SDCard, I attempted to FORMAT the card.
Using the phone to FORMAT, the phone UNmounts the card, says preparing, and REmounts the card exactly as is, without formatting it.
So I tried to reformat it on the computer, three different times, three different programs including the Windows 7 utility, ALL of them gave me the message that my SD Card is WRITE ONLY?
What the heck is that? Did the NI2 update do something to my SD card? Did it corrupt my SD Card?
Any one have any ideas? Guesses? Similar experiences?
Click to expand...
Click to collapse
Never heard of that one...
Do you have exposed installed? Any other MODs? Install any apps that mess with permissions or SD Card?
If no to any of the above, backup all of your data (sd cards too): wipe the entire phone (including SD Card), ODIN back to an older rootable build, and start over.
Pretty sure it's the SD card.
Spoke to SanDisk, they said that something caused a fault in the card, and as a safety measure, the card will become write protected so your data can't be corrupted.
You can copy the data on the card, but you can't add or delete files. So the camera won't record new pictures to the card.
I tried to delete some sensitive files from the card through the File Explorer, and the phone reboots.
I've been using the phone's on board storage, and no issues thus far.
So everything is pointing to the card.
I have Xposed.
The only modules I have loaded is the Moto X tether, YouTube Ad Away, and the Secure Storage Fake that re-enable S Health.
Could one of these mods have created a fault in the card?
ymDroid said:
Pretty sure it's the SD card.
Spoke to SanDisk, they said that something caused a fault in the card, and as a safety measure, the card will become write protected so your data can't be corrupted.
You can copy the data on the card, but you can't add or delete files. So the camera won't record new pictures to the card.
I tried to delete some sensitive files from the card through the File Explorer, and the phone reboots.
I've been using the phone's on board storage, and no issues thus far.
So everything is pointing to the card.
I have Xposed.
The only modules I have loaded is the Moto X tether, YouTube Ad Away, and the Secure Storage Fake that re-enable S Health.
Could one of these mods have created a fault in the card?
Click to expand...
Click to collapse
Always possible when using MODs. Secure Storage Fake.. what all does that do? It's also possible the sdcard just failed. Things happen.
The S Health mod that changes your secure storage from True to False.
Fixes the S Health crash, and Private mode failure caused by running Xposed on the S5.
With NCG and NHA, I used to physical make the changes in the system/build.prop, and change ro.securestorage.support from True to False.
On NI2, and just used the Xposed module that does it for you.
That's the only thing I did different.
ymDroid said:
The S Health mod that changes your secure storage from True to False.
Fixes the S Health crash, and Private mode failure caused by running Xposed on the S5.
With NCG and NHA, I used to physical make the changes in the system/build.prop, and change ro.securestorage.support from True to False.
On NI2, and just used the Xposed module that does it for you.
That's the only thing I did different.
Click to expand...
Click to collapse
I believe most ROMs here already have build prop set to false (mine does). As for private mode, I don't use it so I couldn't make any mention on that note.
Have you tried another SD Card yet?
I'm stock, so I have to physically set it.
I have a new sd card on order, so we'll try again with a new one.
I really don't use S Health that much, and never use private mode, so I think I'm going to delete that mod and leave it at true.
Then again, it could just be a bad card. My S4, has had the same card (64 gb Ultra) for almost 2 years, a lot of the same settings, and never had a problem.
Related
I'm having an issue where I can't cut/copy/paste, create files(.nomedia), and delete files/folders on my external sd card using ES File Explorer. I can create folders though. Everything works on my internal storage. I tried using another app and still having problems. The preinstalled My Files app works on the external sd card.
Any one else having these issues? Any suggestions?
I had that issue with two new cards I put them in my phone and had to format them with the phone under settings for it to work
Sent from my SM-G900V using Tapatalk
syu78 said:
I'm having an issue where I can't cut/copy/paste, create files(.nomedia), and delete files/folders on my external sd card using ES File Explorer. I can create folders though. Everything works on my internal storage. I tried using another app and still having problems. The preinstalled My Files app works on the external sd card.
Any one else having these issues? Any suggestions?
Click to expand...
Click to collapse
KitKat changed the way Android deals with SD cards, particularly in regard to what applications can and can't do. Formatting the card in the phone might help for some things, but it won't solve everything since some changes are at the system level. Here are a couple of articles that explain the changes:
KitKat and SD cards — what's fixed, what's broken and what's misunderstood
External Blues: Google Has Brought Big Changes To SD Cards In KitKat, And Even Samsung Is Implementing Them
If you're going to root your phone, some progress has been made in being able to change the permissions needed to allow apps to access the SD card in the same way as has been the case on previous versions of Android. It's something to keep an eye on in regards to how it might or might now work with the S5: [APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD
Thanks for the info
bsweetness said:
KitKat changed the way Android deals with SD cards, particularly in regard to what applications can and can't do. Formatting the card in the phone might help for some things, but it won't solve everything since some changes are at the system level. Here are a couple of articles that explain the changes:
KitKat and SD cards — what's fixed, what's broken and what's misunderstood
External Blues: Google Has Brought Big Changes To SD Cards In KitKat, And Even Samsung Is Implementing Them
If you're going to root your phone, some progress has been made in being able to change the permissions needed to allow apps to access the SD card in the same way as has been the case on previous versions of Android. It's something to keep an eye on in regards to how it might or might now work with the S5: [APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD
Click to expand...
Click to collapse
Done reading and it helped.Thanks men
Yes. Might be it's working.. thanks @bsweetness
Dear all,
I have a N9005 (eu) with 4.4.2 stock. Never rooted.
Since a couple of weeks, I notice a strange behavior. Quite often I find broken thumbnails in the stock Gallery app, sometimes the actual photos I have take are not visible.
At the same time, it happens that I download and install an app and it won't run, giving me an error in com.appnamewhatever. After a restart, I still see the link to the app on the home, but as I click it says app not installed. After I reinstall I can often run it np.
It gives me the feeling that the internal SD Card is dying. Is that possible? Can I run some tools/fixes to prevent or check it? (with no root required)
Thanks.
Sent from my SM-N9005 using XDA Free mobile app
McBain_666 said:
Dear all,
I have a N9005 (eu) with 4.4.2 stock. Never rooted.
Since a couple of weeks, I notice a strange behavior. Quite often I find broken thumbnails in the stock Gallery app, sometimes the actual photos I have take are not visible.
At the same time, it happens that I download and install an app and it won't run, giving me an error in com.appnamewhatever. After a restart, I still see the link to the app on the home, but as I click it says app not installed. After I reinstall I can often run it np.
It gives me the feeling that the internal SD Card is dying. Is that possible? Can I run some tools/fixes to prevent or check it? (with no root required)
Thanks.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
1. Take a look if your photos and pics are in SDCard.
2. Take a look if you have the apps installed in your SDCard too (Aplication manager -> SD Card -> App marked to move to SDCard)
3. You will have to take off the SDCard and try making photos and installing new apps (change your SDCard for other new if this go ok)
Tell me what result do you have in your tests :highfive:
Man, you are right. I had not moved any app intentionally to the external SD Card so I did not think that would be the case. But that's what happened, the failing apps were on the external SD and so are the photos. It's a SanDisk Class 10 64 Gb.
So no way out other than substituting it?
Sent from my SM-N9005 using XDA Free mobile app
McBain_666 said:
Man, you are right. I had not moved any app intentionally to the external SD Card so I did not think that would be the case. But that's what happened, the failing apps were on the external SD and so are the photos. It's a SanDisk Class 10 64 Gb.
So no way out other than substituting it?
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
1. Take a look for what you can recover of your SDCard and copy it to your pc.
2. Format the card in the phone for last option.
3. Try again to put photos/apps there.
4. Good luck :highfive:
The corrupted photo's on the SDcard are a problem directly related to KitKat's increased security. It affects all KitKat devices. Any photo's on the SD randomly corrupt over time. The only solution is to put them on the internal memory.
The apps are a new one though. I've had apps suddenly become semi-uninstalled because I was dumb enough to mess with the Android_secure folder, but not with the errors after install.
Sent from my SM-N9005 using Tapatalk 2
ShadowLea said:
The corrupted photo's on the SDcard are a problem directly related to KitKat's increased security. It affects all KitKat devices. Any photo's on the SD randomly corrupt over time. The only solution is to put them on the internal memory.
The apps are a new one though. I've had apps suddenly become semi-uninstalled because I was dumb enough to mess with the Android_secure folder, but not with the errors after install.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Jeez that's crazy. I triedo to run a chkdsk on the card from windows (in a SD reader) and it got me a gazillion errors.
So now I proceeded to salvage what I can. I will try to format it (in the phone? in windows? still not sure about it) and see what happens.
Luckily I was able to salvage 99% of the photos.
I just remembered that I did something very unortodox, more or less at the same time problems started: I removed the SD Card with the phone still on. Yes, you can barely do it without removing the battery... I though "let's see if something bad happens". Maybe it started to corrupt the FAT or similar.
Anyway, please feel fee to point me to a thread or good article on this, I find information very scattered. Is there any advantage t oformat it in FAT32, NTFS or exFAT (assuming I can even choose)?
Thanks
McBain_666 said:
I just remembered that I did something very unortodox, more or less at the same time problems started: I removed the SD Card with the phone still on. Yes, you can barely do it without removing the battery... I though "let's see if something bad happens". Maybe it started to corrupt the FAT or similar.
Click to expand...
Click to collapse
I find it fairly easy to do. It's also perfectly fine, as long as you unmount it first in settings.
Is there any advantage t oformat it in FAT32, NTFS or exFAT (assuming I can even choose)?
Click to expand...
Click to collapse
Fat32 is the common format IT doesn't allow for filesizes over 3.9GB, so if you intend to use t for films, use exFAT.
NTFS can't be read without root. Don't use it.
exFAT is practically the same as FAT32, except that it allows for larger filesizes.
ShadowLea said:
I find it fairly easy to do. It's also perfectly fine, as long as you unmount it first in settings.
Click to expand...
Click to collapse
Thanks for the infos. At that time I obviously did it without unmounting it first (no fun in life without some screw-ups). Regarding the formatting, I seem to be unable to do it from the phone at the moment.
It unmounts it, says checking it. But doesn't format it. Trying from windows now...
Here are some updates.
Formatting in either windows (stock function) and phone was a no-go.
However, I dowloaded and installed SD Association Formatter:
https://www.sdcard.org/downloads/formatter_4/
and that did the trick. Now the SD Card is finally empy.
Also I strongly suggest using this tool instead of windows proprietary, because it's simply much much faster.
I will try and load it back with the stuff I had before, including pics, and see if I get the corrupted data again.
A difference is now that the chkdsk tool from windows says that no errors are found, unlike before. Let's see how it goes.
Final update to close thread:
The SD Card, a SanDisk UHS Class 10 SDXC, 64 Gb, had been declared dead.
It was possible to write data on in with seemingly no errors (from chkdsk) but all the data turned out to be simply corrupted.
Will send for replacement.
I have seen many comments on this card failing, so I would not recommend it. However, I think that this case it was not KitKat's fault.
Thanks for the inputs.
Do not blame the card yet
I am having the same issue with the same card, but it is limited to Note 3(N900).
Every now and then it becomes inaccesible, the photos appear broken, music player stops etc. It is not related to use of any particular app. When it happens, the card is still visible in Settings/Storage, just no app including mounting has access to it. What helps, is the old reboot fix
Happened on official KK, as well on LP. Device is stock unrooted N900.
The card is working without any problems in Note 1,even in Galaxy duos, and there are no issues writing/reading in windows nor linux. Something tells me that hardware is to blame.
Anyone else having SD card issues after the update?
Since the update my photos are saving to the phone's internal memory and if I change camera to save to the SD it stays until I take a photo, then it says there was a problem saving to the SD and writes to the phone again.
Using FX I can see the "Media Card" but when I click on it it says "Access Was Denied" however I can use System/ and see the SD Card folder and access it that way.
If I unmount and remount the SD card in Settings it works again for a short while both for accessing and saving photos to and then goes back to being seen but not able to be written to for photos along with looking at my gallery and seeing none of the photos saved to it.
I am going to back it up here to be safe but do I need to do a full format of it or has anyone had similar issues and fixed it?
Did you do the edit to platform.xml I got that when trying to back up TB Try flashing this then see if it helped, this is for a 910W8 but should work on any N4
Thanks mate.
I assume that is for rooted phones, yeah?
Mine is stock, not rooted.
I think it is just a bunk SD card, ah well time to warranty it with ADATA.
Udonitron said:
Thanks mate.
I assume that is for rooted phones, yeah?
Mine is stock, not rooted.
Click to expand...
Click to collapse
The zip I posted is flashable but it could be the card I had the same problem. I did a clean through diskpart on windows
Yeah it is really weird.
If I manually delete the info on the card it appears gone but when I go to format it, all that info comes back.
I did the regedit and diskpart trick and neither worked.
ADATA told me to download the SD Card Formatting exe and it tells me it is write protected when it clearly isn't.
Hence why it is not accessible on my phone and cannot be written to...no clue how to reverse it or why it happened in the 1st place.
I can't write to my card after jumping to 5.1.
Sent from my SM-N910T3 using Tapatalk
I have a very strange thing that has just started occurred with my wife's Note 4. It appears that all apps have lost write-access to the SD card.
I first noticed the problem with the camera app. The camera app was configured to write to external storage but when a picture is taken, it says "Unable to save file to SD card. Default storage has been changed to device memory."
The Gallery app is also not able to write to the SD card (cannot create a new album) or move files to an existing album on the card.
Solid Explorer cannot create a new folder on the card.
I've tried to clear app settings for the camera and Solid Explorer. But even after setting everything back up, I still get the same results.
I'm running stock v6.0.1 (EPJ2) rooted. Also, my (seemingly identical) Note 4 does not display any of this behavior. No changes other than normal application updates.
Any ideas what might be going on?
I've had this happen when an SD Card gets corrupted - you can still view and access the files that are already on the card, but you can no longer write to it.
Try the card in a PC and see if that can write to it - if not then your card is likely permanently damaged. I had 3 Sandisk 64Gb cards go like this in two different devices. Tried reformatting them every which way, but nothing would make them writeable again. Have used Samsung cards ever since and never had a failure yet.
Just restart your phone
Sent from this galaxy
SJMarty said:
I have a very strange thing that has just started occurred with my wife's Note 4. It appears that all apps have lost write-access to the SD card.
I first noticed the problem with the camera app. The camera app was configured to write to external storage but when a picture is taken, it says "Unable to save file to SD card. Default storage has been changed to device memory."
The Gallery app is also not able to write to the SD card (cannot create a new album) or move files to an existing album on the card.
Solid Explorer cannot create a new folder on the card.
I've tried to clear app settings for the camera and Solid Explorer. But even after setting everything back up, I still get the same results.
I'm running stock v6.0.1 (EPJ2) rooted. Also, my (seemingly identical) Note 4 does not display any of this behavior. No changes other than normal application updates.
Any ideas what might be going on?
Click to expand...
Click to collapse
There are 3 possible solutions:
Using MS Windows PC
Using Linux PC
Using TWRP Recovery with a proper BusyBox
Let me know which one do you choose & I will explain how.
Kinsman-UK said:
I've had this happen when an SD Card gets corrupted - you can still view and access the files that are already on the card, but you can no longer write to it.
Try the card in a PC and see if that can write to it - if not then your card is likely permanently damaged. I had 3 Sandisk 64Gb cards go like this in two different devices. Tried reformatting them every which way, but nothing would make them writeable again. Have used Samsung cards ever since and never had a failure yet.
Click to expand...
Click to collapse
You nailed it. My card was a 128 GB SanDisk Ultra. Pulled it from the phone and my laptop couldn't write to it either. Copied everything off and copied it back to a new card and there you go.
Grrrr...$^%**# SanDisk.
Out of curiosity, what Samsung line did you end up choosing? I think the EVO+ will be sufficient for me but wondering what you ended up using.
SJMarty said:
Out of curiosity, what Samsung line did you end up choosing? I think the EVO+ will be sufficient for me but wondering what you ended up using.
Click to expand...
Click to collapse
Glad you got it sorted! I've been using a Samsung PRO 64Gb - this is the 128Gb version on Amazon UK:
https://www.amazon.co.uk/dp/B01CRZCLAM
I think the newer version of it is this one:
https://www.amazon.co.uk/dp/B019QO1Q4O
But you're right - the EVO+ is probably sufficient. It wasn't available when I was purchasing:
https://www.amazon.co.uk/dp/B00WR0HIR4
tl;dr
The card is tested and good (results below), the card reader is good (tested by reinstalling 5.7.4).
So few other people are having this issue, what is going on with my phone?
--
I've read and read, but no matter what I try, I can't get my SD card to work.
Here's the details of how, and what, I installed on my Sprint S5.
I'm coming from Resurrection Remix 5.7.4 MM, (where the SD card worked fine, but did have a few issues with the camera (used open camera instead) and some post reboot oddness (shortcuts disappearing)).
I first formatted card using the windows software sdformatter to FAT32
copied files to SD card using a card reader plugged into PC.
Files copied
RR-N-v5.8.2-20170304-kltespr-Official.zip
open_gapps-arm-7.1-micro-20170327.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
TWRP 3.X
wiped dalvik/cache/system/data
then factory reset
added files to zip queue, Rom, then Gapps, then SU
Flashed
Phone boots fine, initial set up completes.
Tried a reinstall of apps using Ti Pro, but it failed, so started again and used google apps restore during boot. Issues with many apps. So started again, with a "fresh start" option during set up.
I took a few pictures.
I can view them immediately after taking, by pressing the previously taken image image inside the camera app.
Open default Gallery and get the error "No storage. No external storage available."
I installed a+ gallery and it is able to open the images just fine.
Default Files app can browse the SD card.
Aldiko will not download books, as it thinks there is no SD card installed
I've tried (and checking each time)
formatting in card as internal, then back to portable in phone.
Clearing the data/cache for the apps giving errors.
factory resetting
Wiping and formatting the card (on PC to FAT32), and starting again (several times).
Started from scratch again, with a brand new Sandisk card
Tried ZepherOS Zephyr-N Version (Viserion-6.1) Android 7.0
Wiping cache/dalvik only and rebooting
Same "No storage..." error, every time.
I tried ZephrOS. Right after install there is no file manager, but if I click the default app "downloads", I can navigate to the camera folder, then to the image. When I click on it, it opens the image, but still shows the same error "no storage..." even though I'm looking at the image behind the error window. :/
I'm running H2testw, but don't expect an issue, as the same error was on the previous card and the brand new card.
Can I go from 7.0/7.1 to a stock ROM without issues, if so which one?
Update:
SD card test result
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 7.15 MByte/s
Reading speed: 15.7 MByte/s
H2testw v1.4
UPDATE #2:
I started fresh with a new install of RR 5.7.4 and the card does still have issues with some apps, but is working fine with others. Open camera works fine, and the gallery access the correct card in this ROM. Aldiko still fails as it's trying to download to /sdcard
Most apps are looking for /sdcard but I have /sdcard1
If it helps, it appears sdcard is symlinking to /storage/self/primary
Anyone able to help?
permissions issue? have you gone into the apps mgmt and set the permissions manually?
youdoofus said:
permissions issue? have you gone into the apps mgmt and set the permissions manually?
Click to expand...
Click to collapse
Thanks for the reply. Yes, settings>apps>settings>App permissions>Storage is turned on.
Aldiko, for example, is looking for /sdcard but it doesn't exist. I'm thinking a symlink might fix the issue? But am not familiar enough with Android under the hood, to know what other issues that might cause.
syco123 said:
Thanks for the reply. Yes, settings>apps>settings>App permissions>Storage is turned on.
Aldiko, for example, is looking for /sdcard but it doesn't exist. I'm thinking a symlink might fix the issue? But am not familiar enough with Android under the hood, to know what other issues that might cause.
Click to expand...
Click to collapse
im not familiar enough with the under the hood stuff to know what else coul be the issue either, @AthieN, Mr. guru thoughts?
youdoofus said:
im not familiar enough with the under the hood stuff to know what else coul be the issue either, @AthieN, Mr. guru thoughts?
Click to expand...
Click to collapse
What file system is the card formatted in? Try ext4 or exFAT.
AthieN said:
What file system is the card formatted in? Try ext4 or exFAT.
Click to expand...
Click to collapse
FAT32 this was recommend in most places I read. I thinks it's a paths issue. I'm not sure the format would make a difference to that, right?
syco123 said:
FAT32 this was recommend in most places I read. I thinks it's a paths issue. I'm not sure the format would make a difference to that, right?
Click to expand...
Click to collapse
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
AthieN said:
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
Click to expand...
Click to collapse
thanks for chiming in sir! your help is always appreciated
AthieN said:
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
Click to expand...
Click to collapse
Thanks, I know the OP was long, but I hoped the details of what I'd already tried would be appreciated. I did several fresh installs trying to fix, and formatted every which way I could in phone and on a PC. Nothing has worked.
I've kind of given up on this and have decided to switch to Verizon. Sprint sucks so bad, after 10 years I've finally had enough, so I have to replace the phone anyway.
If you know of a decent phone to get, I'm looking for a recommendation in this thread, https://forum.xda-developers.com/android/help/switching-to-verizon-200-phone-t3588790
Thanks for your attention to my issue. Sorry it's left unresolved. I run my own business and just can't spend this much time fixing my phone.