Before I upgraded from a 4.1 to a 4.2 based rom, I copied all my files from my sd card and then flashed the Rom. Then I formatted my phone's storage so I wouldn't have that weird 2 sd card file system going and so that I could see all my old files which I pasted back onto my phone. When I boot into cwm, and want to install a .zip, I see a couple folders such as the cwm folder and venom folder and legacy folder, and I find that my sd cards files are not under root and I have to go to /0. If I go into a file explorer such as we file explorer, I can't see any files under the the place where those several folders are. Any ideas?
Sent from my HTC One using xda premium
Noticing same thing...
I've just been searching these threads for the exact same issue. Wondering if it would be possible to take a nandroid, erase system and everything and either restore or reload my room from scratch to fix this? My phone says it's running low on memory while it still shows almost 10gb free when attached to my computer. I assume this is the problem...
BJodrey said:
I've just been searching these threads for the exact same issue. Wondering if it would be possible to take a nandroid, erase system and everything and either restore or reload my room from scratch to fix this? My phone says it's running low on memory while it still shows almost 10gb free when attached to my computer. I assume this is the problem...
Click to expand...
Click to collapse
Yeah, ive tried to format my phones internal storage but the problem is still there. Though it does free up a lot of space when I do it. I think it says it is low memory because there are duplicate files of everything on your sd card
So, I just installed the 4.4.2 OTA and I immediately noticed one big problem: I wasn't able to modify content on my SD card. I wasn't able to delete folders, or create folders, or create files. Reading content was no problem, and the camera app was able to save pictures to the card, but going through a file manager wouldn't work.
I started to do some research and I found this post from the developer of my chosen file manager, FX:
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Then, while getting ready to post this, I found another related thread:
http://forum.xda-developers.com/showthread.php?t=2641936
I thought this was a big enough deal to warrant a new thread here. Bottom line is you may want to hold off on this update, or at least go in with your eyes open because for a lot of people, like me, this is a BIG problem. It's damned near a dealbreaker for using my S4 as a matter of fact. Note that it does seem you're able to use the My Files app, but that's almost useless to me: FX has SMB support and I'm constantly pulling files off my server. I even have FolderSync set up to run every night, but I don't expect that'll work either (I'm about to try now).
Whether Samsung spits out a fix quickly, or whether I can root and fix this, it's a pretty significant problem. Be aware folks!
Then I will update after a stable de-knoxed ROM is available.
Sent from my SPH-L720 using Tapatalk
Thanks.for this. I think I will still update as I plan on staying unrooted and will use "my files".
Sent from my SPH-L720 using Tapatalk
anees02 said:
Then I will update after a stable de-knoxed ROM is available.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm all for avoiding Knox, but in this case it appears to not be Knox-related after all... looks like it was a permission change that Google mandated for devices with external storage and Samsung followed the specification to the letter. I think Tod Liebeck explained it better than I can though. I can only hope Samsung gets it together and quickly releases a patch... I've read in another thread that they may have done this before and quickly put out a fix... if so, shame on them for making the same mistake twice, but so long as a fix is forthcoming, so be it. I'm not so sure there will be one though, that's my concern.
It's early to call that is the bug since nobody mentioned this issue.
And all are busy how to update.
I will wait 48 hours until all things be more clear.
Could you try another SD card and tell us if the issue is happening to the new sd card?
Sent from my SPH-L720 using Tapatalk
anees02 said:
It's early to call that is the bug since nobody mentioned this issue.
And all are busy how to update.
I will wait 48 hours until all things be more clear.
Could you try another SD card and tell us if the issue is happening to the new sd card?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thing is, it was something that was apparently talked about before the update on other devices with 4.4.2. It's not a bug per se, Samsung did what Google told them to do, and Google told them to do it, I'd bet, to push people towards cloud storage since they don't want external storage used anymore anyway. None of that matters though because the fact is it's hurting some users (though I'd agree that not all will be impacted- it all depends on how you use your device).
A different card wouldn't matter, it's not related to that at all. It's a permission change that Google mandated with 4.4 (or 4.3, I've seen some conflicting info) that only impacts devices with external storage, and Samsung chose to follow Google's specification exactly in this case, to the detriment of (some) users.
FYI, *IF* you're rooted, here's a solution that fixes this. Worked for me and easy to do:
http://forum.xda-developers.com/showthread.php?t=2524277
Just remember to keep a copy so you can quickly undo it to take an OTA since I assume it'll stop an OTA.
Soooo lemme get this straight... Lets say I update to KitKat (NAE)and root it, and I have apps on my computer (like Flappy Bird APK for instance), I now cannot copy the Flappy Bird APK onto my SD Card then place it (using a root explorer) in system/app and use it?! If so this is a huge deal-breaker... Or am I misunderstanding this and there's more to it?
thankfully you can still create on the SD card from a computer when plugged. but i can confirm you cannot create anything on the SD card from ES file explorer, you can still create on the internal storage just fine tho
Joe0113 said:
Soooo lemme get this straight... Lets say I update to KitKat (NAE)and root it, and I have apps on my computer (like Flappy Bird APK for instance), I now cannot copy the Flappy Bird APK onto my SD Card then place it (using a root explorer) in system/app and use it?! If so this is a huge deal-breaker... Or am I misunderstanding this and there's more to it?
Click to expand...
Click to collapse
You can still copy from your computer if you use a USB cable... if you instead have a shared drive on your PC and connect to it via SMB from a file explorer, you won't be able to copy a file to the SD card.
In addition, using a third-party file explorer you won't be able to create, rename, delete or edit files or directories on the SD card, nor will you be able to copy files from internal storage to your SD card. This is strictly a limitation placed on non-system apps (meaning any you yourself install).
If you're rooted though, a quick edit to a single system file will deal with this, but nobody should *have* to do that.
fzammetti said:
You can still copy from your computer if you use a USB cable... if you instead have a shared drive on your PC and connect to it via SMB from a file explorer, you won't be able to copy a file to the SD card.
In addition, using a third-party file explorer you won't be able to create, rename, delete or edit files or directories on the SD card, nor will you be able to copy files from internal storage to your SD card. This is strictly a limitation placed on non-system apps (meaning any you yourself install).
If you're rooted though, a quick edit to a single system file will deal with this, but nobody should *have* to do that.
Click to expand...
Click to collapse
That's ridiculous... what the hell Android/Samsung?!
Wow! Not trying to rub it in or anything but thank goodness I switched to the Nexus 5. What a nightmare. I hope Samsung fixes it soon for you guys
Sent from my Nexus 5 using Tapatalk
Thanks for this, lets go here for any further discussion...http://forum.xda-developers.com/showthread.php?t=2646762
Ok so after reading about the limitation on kit kat regarding sd card, i got really confused being a newbie in technical aspects so i was hoping people here can shed a light on my questions:
1. Is the touchscreen issue fixed on kitkat?
2. If i update right now to kitkat, will all my pictures and mp3 saved in sd card be still readable and playable? Or will they be gone? Some people reported breaking sd card after updating.
3. Can i still download music and use file comando(never ised that app before) to move files to sd card?
4. If i use stock camera, images are still saved in sd right?
5. If i have an app moved to sd, and updated the app after updting to kitkat, will i still lose my saved files?
6. Does this limitation mean that we can no longer download files bigger than the internal memory of the phone? Isnt that going to make our xperia z1 useless if you have big apps and only have like 2g internal memory left??
7. I read something about apps can still write on your sd if they make a private folder but i dont understand it. So does this mean we can still download files directly to sd if the app supported kitkat?
Those are some of the questions i have for now. Please please someone answer me cause im really confused.. Thank you.
Search the forum...all questions will be answered if you put a little effort to it
Sent from my C6903 using XDA Premium 4 mobile app
1. It was fixed already in .136 4.3, if you still have problems go via Warranty.
2. Yes, with some specific applications.
3. No, you have to get root.
4. I think so.
5. How did you moved the apps to SD? it was never possible from 4.2.2.
6. Ask Google.
7. You are will not be allowed to write to SD until you get Root and modified system to do it. Search on Z1 section, is there.
Best answer for all your question is: Do not Update to KK.
On the SD card of my 5803 I have a folder called recovery and in it is a file named update_package that is 635mb. I have dual recovery installed. I have been using twrp for several months successfully. Does anyone know what this file is? Can I remove it? It's dated June 3 which I think is the day that I installed the recovery. Is it left over from the original installation and not needed any more? Would love to know if anyone knows or if anyone is using dual recovery and doesn't have this file on the internal card so I can figure it out. Thanks
Sent from my Nexus 6
Removed it, all is fine. Thanks for nothing guys.
?
Sent from my Nexus 6
I cannot seem to find a consistent experience with users whether it's here (XDA) or other forums and whether or not exFat support exists with Marshmallow. Has anyone else come across similar issues?
I have 128gb sdcard formated in exfat and stock MM_tmobile SM-N910T...I can read the sdcard with no problem but I cannot write without using a program like office suite. You can still backup your rom on external sdcard using twrp.
Strange. I can definitely see it in TWRP but beside that, it says it's corrupted. Guess I'm off to experiment some more.
Edit: Card works on my GF's phone. It has the same exact modifications. Something must be wrong with the flashing of MM. Thanks for the indirect help gmenik6. I didn't even occur to me to try her phone until you said that, even though hindsight it was very obvious.
I got a 200gb SanDisk I use formatted to exfat no problems here reading it or writing to phone and it mounts fine when I use it on the pc.
Which card are you using and are you on a vanilla tw mm or a custom rom like cm13/aosp?
Sent from my SM-N910T using Tapatalk
d12unk13astard said:
I got a 200gb SanDisk I use formatted to exfat no problems here reading it or writing to phone and it mounts fine when I use it on the pc.
Which card are you using and are you on a vanilla tw mm or a custom rom like cm13/aosp?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Jus re-flashed through Odin to clear out everything and to reset all paritions just to be safe. Booted up and SD is read. Flash TWRP and SU and still reads fine. I then let all my apps install, install BusyBox, Xposed Framework, XTouchWiz and Titanium Backup, I even restored a few apps through Titanium (from my SD Card). Phone sits over night and now this morning I cannot access my SD Card.
XTouchWiz doesn't seem to be working anymore and the damn TMobile App keeps trying to get root access. I can't freeze it either because TB unexpectedly quit's which I'm guessing is because it's a systemless root.
Thoughts while I troubleshoot/experiment?
Sounds like a faulty SD card, if you did all that and it's still not reading your card correctly.
Sent from my SM-N910T using Tapatalk
d12unk13astard said:
Sounds like a faulty SD card, if you did all that and it's still not reading your card correctly.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I'll have to respectfully disagree on the basis that a separate FAT32 card does not read and my current exFat card is read in both my tablet and another Note 4 phone. Now could it be a faulty reader in the phone? That's what I plan to find out by flashing MM through Odin again and keeping it stock for a few days.