Warning: 4.4.2 update breaks SD card access! - Sprint Samsung Galaxy S 4 General

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

Related

new razri user few questions

hi
should be getting mine today
how is everybody coping with the low storage issue?
i have been reading up on directory bind and also rickywyatt method
i dont plan on unlocking the bootloader but i do plan on rooting
What low storage issue are you talking about?
While most of them are installed on the SD, I have a lot of installed applications (about a hundred) and I still have more than 3Gb available (internal storage).
An SDcard can be used for your pictures/videos/games, up 32Gb (at least).
If you want to root your phone and don't want to unlock your bootloader, then don't upgrade it.
However, depending on the installed firmware, it may be impossible to root without unlocking the bootloader.
Motorola has fixed the root exploit in the last update.
ciberbeb said:
What low storage issue are you talking about?
While most of them are installed on the SD, I have a lot of installed applications (about a hundred) and I still have more than 3Gb available (internal storage).
An SDcard can be used for your pictures/videos/games, up 32Gb (at least).
If you want to root your phone and don't want to unlock your bootloader, then don't upgrade it.
However, depending on the installed firmware, it may be impossible to root without unlocking the bootloader.
Motorola has fixed the root exploit in the last update.
Click to expand...
Click to collapse
oh, that was something i wanna ask, so if i download Need for Speed MW the 2 gb will install on the SD?
I can't see that it goes to the sd card everything I have downloaded has gone onto the internal memory
App2sd doesn't work so I think the only two methods we can use are directory bind or the internal swap memory trick
Sent from my XT890 using xda app-developers app
emu123 said:
I can't see that it goes to the sd card everything I have downloaded has gone onto the internal memory
App2sd doesn't work so I think the only two methods we can use are directory bind or the internal swap memory trick
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Did u tried using this app? i dont have a good connection so i cant try it by myself with games https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImNvbS5zbGYuTGlzdGdsQXBwIl0.
Deshabilitado said:
oh, that was something i wanna ask, so if i download Need for Speed MW the 2 gb will install on the SD?
Click to expand...
Click to collapse
It depends on the application. Some apps put thier "big" files on the sdcard, some won't.
As emu123 said, you can use an app like Apps2sd to move them from the internal to the external storage.
Even if I install a lot of games, I never ran out of storage. That was the case with my old HTC Desire HD.
Big games can use up to 400Mb, I still have more than 3Gb, which means I can install, at least, 7 big games (but some of them will put files on the SDcard if present). It won't ever happen.
EDIT: I think Apps2sd doesn't work with Android 4.x. Not sure, but I think that the system manages where to install apps when internal storage is full.
I already suggested the ability to move apps to the SD card on the motorola forums, Razr I discussions:
I even got an answer!
I'm a new user so I can't post links search it
Agustinb14 said:
I already suggested the ability to move apps to the SD card on the motorola forums, Razr I discussions:
I even got an answer!
I'm a new user so I can't post links search it
Click to expand...
Click to collapse
I'm not sure the "gosh that's a good idea, we'll pass it on" really counts as an answer - almost as if no-one had ever thought of it before!
Does anyone know how to disable vibro on screen unlocking?
Hi, I set up a thread (in my signature) specifically for for those of us new to Motorola - I just got my first Moto phone 2 days ago too. You may find the thread helpful - I will update it with any info. that people need.
How do you mean low storage? Internally? 8GB (practically 5GB) is low to you? Compared with what? Most phones in the upper tier of mid-range have 8GB and many top-range phones start with 8GB...it seems perfectly normal to me. Either way, do you have an SD card? I've a 32GB for my music and it's now full...some phones load the SDs so slowly...but NOT thins phone, all of my music is found in seconds. :fingers-crossed:

Moving CoPilot GPS maps to sdcard1

Update:
I made a tutorial how to get CoPilot save the maps on the external sd card.
For this method you don't need any root access so it should work for almost everyone.
Make sure you check check whether your sdcard path is /storage/sdcard0 or /mnt/sdcard
For me it worked fine without rooting the phone.
I have a samsung ace plus S7500
I made a copy of
/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/
to
/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/
then (with KIES), i changed the
user.cfg situated in /mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/
then i erased the
/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/EU/
The adapted user.cfg would be changed like this
[Directories]
"AddonDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/EU/addon/"
"AudioDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/audio/"
"GlobalAddonDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/addon"
"GPSDemoDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/gpstracks/demo"
"LRGlobalSaveDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/save"
"LRGPSSaveDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/gpstracks"
"LRInfoDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/info"
"LRSaveDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/EU/save/"
"RegionDir"="EU"
"RootDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/"
"SkinDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/skin/"
"SpeechDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/speech"
"ThemesDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/themes/"
"UIConfigDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/uiconfig/"
"UpdateDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/save/update"
[Directories]
"AddonDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/EU/addon/"
"AudioDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/audio/"
"GlobalAddonDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/addon"
"GPSDemoDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/gpstracks/demo"
"LRGlobalSaveDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/save"
"LRGPSSaveDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/gpstracks"
"LRInfoDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/info"
"LRSaveDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/EU/save/"
"RegionDir"="EU"
"RootDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/"
"SkinDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/skin/"
"SpeechDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/speech"
"ThemesDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/themes/"
"UIConfigDir"="/mnt/sdcard/com.alk.copilot.eumarket.premiumeupan/uiconfig/"
"UpdateDir"="/mnt/sdcard/external_sd/com.alk.copilot.eumarket.premiumeupan/save/update"
Then it finally works
dagoban said:
Hi guys,
so this topic came up quite a few times for other phones, however I cannot get it working on my Razr I.
And I am talking about the Live version (that is the newest version which comes with all countries in 1app), not the Premium or Lite one.
So I want to move the maps folder to the external sdcard....
Basically what I did is this:
http://forum.xda-developers.com/showpost.php?p=42581577&postcount=2
But of course instead of /storage/extSdCard/ I used /storage/sdcard1/com.alk.copilot.mapviewer/
But after starting CoPilot Live it still overwrites the user.cfg file back to its normal settings (sdcard0)
Does anyone have a solution for that?
I also found out that there is a file called DeviceInfo.xml in the save folder that also has the sdcard0 included...
Click to expand...
Click to collapse
delete
dagoban said:
Update:
I made a tutorial how to get CoPilot save the maps on the external sd card.
For this method you don't need any root access so it should work for almost everyone.
Make sure you check check whether your sdcard path is /storage/sdcard0 or /mnt/sdcard
Click to expand...
Click to collapse
Outstanding! worked perfectly, thank you!
installing maps to SD card
dagoban said:
Update:
I made a tutorial how to get CoPilot save the maps on the external sd card.
For this method you don't need any root access so it should work for almost everyone.
Make sure you check check whether your sdcard path is /storage/sdcard0 or /mnt/sdcard
Click to expand...
Click to collapse
Dear Michael, your tutorial is fantastic, it is logical, clear and easy to follow, unfortunately the text of my “user.cfg” file is different, the text contained often the word “emulated” but there is nowhere the word “mapviewer “ I wonder if you could give me a push in the right direction. The device I am running is Samsung Galaxy S5 (SM-G900i) and the CoPilot version is 9.5.0.440 Europa and USA
Regards Erik
Hi Erik,
just look for the RootDir and SpeechDir tag in the config and change that from your internal card to your external card.
If you still need help, start at step 1 again and then copy the config file to your PC and upload its content to pastebin.com so I can have a look at it.
erikdeoude said:
Dear Michael, your tutorial is fantastic, it is logical, clear and easy to follow, unfortunately the text of my “user.cfg” file is different, the text contained often the word “emulated” but there is nowhere the word “mapviewer “ I wonder if you could give me a push in the right direction. The device I am running is Samsung Galaxy S5 (SM-G900i) and the CoPilot version is 9.5.0.440 Europa and USA
Regards Erik
Click to expand...
Click to collapse
If you are on KitKat it could be a problem with writing your maps to external SDcard.
Moving CoPilot Map to SD card
dagoban said:
Hi Erik,
just look for the RootDir and SpeechDir tag in the config and change that from your internal card to your external card.
If you still need help, start at step 1 again and then copy the config file to your PC and upload its content to pastebin.com so I can have a look at it.
Click to expand...
Click to collapse
Thanks for your help,it is obviously not possible to move the copilot maps, so I will search for another brand of GPS
dagoban said:
Update:
I made a tutorial how to get CoPilot save the maps on the external sd card.
For this method you don't need any root access so it should work for almost everyone.
Make sure you check check whether your sdcard path is /storage/sdcard0 or /mnt/sdcard
Click to expand...
Click to collapse
Thanks for the guide!
Do I need to repeat step 14 (copy folder) when / if the app gets updated?
dagoban said:
Update:
I made a tutorial how to get CoPilot save the maps on the external sd card.
For this method you don't need any root access so it should work for almost everyone.
Make sure you check check whether your sdcard path is /storage/sdcard0 or /mnt/sdcard
Click to expand...
Click to collapse
Hi Dagoban,
I followed your tutorial and it worked great. At least up to yesterday, where I updated CoPilot to version 9.6.0.634. Now the phone directory no longer says /storage/sdcard0 but /storage/emulated/0/.
Changing the Root and Speech directory (in my case to extSdCard) doesn't allow downloading of Maps on my SD card anymore.
Any thoughts or tips?
Thanks
Rob
Update: I have a Galaxy S4 (GT-I9505), running on Android 4.4.2 (Kitkat)
transfering large maps to extsd card
rdijkstra said:
Hi Dagoban,
I followed your tutorial and it worked great. At least up to yesterday, where I updated CoPilot to version 9.6.0.634. Now the phone directory no longer says /storage/sdcard0 but /storage/emulated/0/.
Changing the Root and Speech directory (in my case to extSdCard) doesn't allow downloading of Maps on my SD card anymore.
Any thoughts or tips?
Thanks
Rob
Update: I have a Galaxy S4 (GT-I9505), running on Android 4.4.2 (Kitkat)
Click to expand...
Click to collapse
Hi Rob,
I had a similar problem with Galaxy S5 (SM-G900i), and rooting the phone did not help, after receiving just silly answers from ‘CoPilot Technical Support’ I purchased the application from ‘Sygic’ it cost a few Dollars more but for this you get annual several map updates and the service is excellent. The maps are slightly larger in size but the whole application can be transferred to external SD card (by cut and paste) for me it was an easy solution.
Cheers Erik
Seems to work, basically
dagoban said:
Update:
I made a tutorial how to get CoPilot save the maps on the external sd card.
For this method you don't need any root access so it should work for almost everyone.
Make sure you check check whether your sdcard path is /storage/sdcard0 or /mnt/sdcard
Click to expand...
Click to collapse
I tried this on my Atrix HD with Cyanogen 10.2, and it seems to work. The Atrix uses an "emulated" sdcard0, so it had some issues, but I edited the user file & continued the install. When I ran copilot initially, it seemed to have some problems. I kept getting "Do you really want to quit" messages when I would try and move through menu options. I turned on GPS (which I had not done prior) and after a minute or so, I was able to browse the map, so maybe that was the issue. Now, when I fire up Copilot, it seems to behave. I tried an "goto" address in another state, and the route was correct, so I'm saying thanks very much for the process you developed. I really wish that ALK would just add this to their software.
KitKat “EACCES permission denied”
rdijkstra said:
Hi Dagoban,
I followed your tutorial and it worked great. At least up to yesterday, where I updated CoPilot to version 9.6.0.634. Now the phone directory no longer says /storage/sdcard0 but /storage/emulated/0/.
Changing the Root and Speech directory (in my case to extSdCard) doesn't allow downloading of Maps on my SD card anymore.
Any thoughts or tips?
Thanks
Rob
Update: I have a Galaxy S4 (GT-I9505), running on Android 4.4.2 (Kitkat)
Click to expand...
Click to collapse
It seems that android 4.4.2 has limited access permission of the external SD card. Have a look at howto-avoid-the-eacces-permission-denied-on-sdcard-with-kitkat-4-4-2-version on stackoverflow (I can't post the link!).
I tried to change the folder permission via chmod but no lock. What is the workaround?
sesemin said:
It seems that android 4.4.2 has limited access permission of the external SD card. Have a look at howto-avoid-the-eacces-permission-denied-on-sdcard-with-kitkat-4-4-2-version on stackoverflow (I can't post the link!).
I tried to change the folder permission via chmod but no lock. What is the workaround?
Click to expand...
Click to collapse
Michael previously published an instruction on how to move the maps to SD card, but his instruction does not work with the recent KitKat version of Android. People look for methods to root the device to obtain access to SD-cards. Still it is perfectly possible even with unrooted devices. Edit folder path for Rootdir and Speechdir so that it would point to a folder "Android/data/" at your SD card. For example, for Samsung Galaxy 5, it would be "storage/extSdCard/Android/data/...". Save the file user.cfg. If you have a different brand, your external SD card might be called differently, this is why copilot guys do not want to mess with external cards (shame on them, btw).
It worked for me with Kitkat. Have found somewhere that every application under Kitkat gets its own folder in Android/data with full writing rights. But the folder should be named strictly after the application name. If you copy the folder to any other place and adjust user.cfg accordingly, it might not work, since the application tries to write something into folders, too.
delete
Works on Low Storage KitKat
Shato said:
Michael previously published an instruction on how to move the maps to SD card, but his instruction does not work with the recent KitKat version of Android. People look for methods to root the device to obtain access to SD-cards. Still it is perfectly possible even with unrooted devices. Edit folder path for Rootdir and Speechdir so that it would point to a folder "Android/data/" at your SD card. For example, for Samsung Galaxy 5, it would be "storage/extSdCard/Android/data/...". Save the file user.cfg. If you have a different brand, your external SD card might be called differently, this is why copilot guys do not want to mess with external cards (shame on them, btw).
It worked for me with Kitkat. Have found somewhere that every application under Kitkat gets its own folder in Android/data with full writing rights. But the folder should be named strictly after the application name. If you copy the folder to any other place and adjust user.cfg accordingly, it might not work, since the application tries to write something into folders, too.
Click to expand...
Click to collapse
That worked great, Shato. Thanks. It even worked on my phone which doesn't have enough free internal memory for the maps. I downloaded the maps on my tablet and copied the folder to the SD. Then I put the SD in the phone and applied the config change.
An update the developer should do - detect extsd during app install/update
Seems like a lot of trouble. With Sygic's app, all you have to do is move the folder, launch the app, and clean up whatever old filder remains on internal sd.
[*ttp://help.sygic.com/hc/en-us[/*
Haven't tried a Sygic app upgrade since I moved it, but added maps all go to extsd.. I have noticed one small issue. If I shut my device off, it rediscovers the extsd and remounts it, and it can take a whie to finish indexing it (2 minutes with my 32GB U-1 cl 10 card) and until it does, apps using fies from the extsd seem to hang. on launch I say seem to. If allowed to wait, they eventually open unless they err after loading some of their files, but aren't able to access all of them..
The work around is not to shut completely down, but sleep or suspend after putting the device in Airplane mode to minimise drain.
Yeah, I know this doesn.t solve the CoPilot\Kitkat issue, but I had to stop using CoPilot because I ran out of space on internal SD. I'm not going to deal with an app that requires massaging after every revision, and this one has enough bugs that it needs revisions, not just map updates. When I see an announcement that either Google lifts the extSD restrictions (in L I hope), or Copilot fixes its code, I'll use Sygics free version with all its limitations- disable its app from updating, and manually update the few state maps I use periodically.
I was learning to live with CoPilots quirks untilI I ran out of space. Syngic isn't as nice to use, and has its own quirks, but at least it doesn't have to fill my internal SD with maps of states to which I'll never go., and it's too pricy for me to buy the full version, so I lose turn by turn.
BTW, both apps suffer from many inaccuracies suburban and low pop density maps, but Syngic's are slightly better, in that adddresses are more often correctly located on the right side of roadways and nearer to the correct ends of irregularlyoshaped "blocks"..
I am running an LG Optimus L70 (D321) with kitKat 4.4.2
After just installing copilot, and stopping at the point it wants to install the maps, I see that copilot is scattered all over the place
It has files in /data/app-lib/
/data/data
/data/media/0/
/data/user/0/
/mnt/sdcard/
/mnt/shell/emulated/0/
/pkg/
/storage/emulated/0/
Several have the user.cfg file in them.
Which one do I edit? Which one do I move to my external SD card.
On my phone the external is /storage/external_SD/Android/
This was way easy in ICS
OK, got things moved around so my maps go to my EXTERNAL SD card.
On my LG Optimus L70 (D321 Cricket) running kitkat 4.4.2 the external sd card is located:
/storage/external_SD/Android/data/
you must point to the "ANDROID/DATA" or it will not work.
I did find one short issue, Copilot still looks at the INTERNAL SD CARD for the amount of available storage. It may balk if you try to download the entire USA, 1.77 GB or all of North America 1.87 GB. I had to DL it in sections and all worked fine.
deleted

[Q] SD Card not installed

Hi guys,
I recently bought a HTC One, I rooted it cause I wanted to change the htc icon to being operational so then flashed the kernel teaMSeven-sense-4.2.2-kernel-v2.1.4.zip. All appeared to be fine but now I am being told that I have no SD card installed so I can't access my photos, use my camera or access the Dropbox app properly. I presume there are some other issues but can't be sure yet. When I connect my computer to my laptop I can access the internal storage without a problem. When I go to recovery mode and go to Advanced - File Manager - sdcard I can see all the folders. Also when I go to mount and try it first gave an error that usb-otg couldn't mount and now it hangs at updating partition details.
Please help!
your sd card is there. there are some fixes in the development section. Take a look there
osmosizzz said:
your sd card is there. there are some fixes in the development section. Take a look there
Click to expand...
Click to collapse
Thanks osmosizz but is there any chance you can be more specific please? I have spent 2 hours seaching and it is like trying to find a needle in a haystack.......prob easy to find but sorry it ain't working out for me at the moment!
leesider said:
Thanks osmosizz but is there any chance you can be more specific please? I have spent 2 hours seaching and it is like trying to find a needle in a haystack.......prob easy to find but sorry it ain't working out for me at the moment!
Click to expand...
Click to collapse
try this http://www.youtube.com/watch?v=f1YiI-ZZGBs
USB OTG is not your internal storage.
I had the same issue and that video is far too complicated for what you actually need to do.
This is what I did when I upgraded from 4.1.2 to 4.2.2 on my HTC One.
Issue: You will have a new place for your data now. The default under 4.2.2 is now /data/media/0. Under 4.1.2 it was /data/media. Notice the extra /0 - that's for a multi-user environment.
Resolution: Needs root access, of course.
1. Install ES File Explorer
2. Enable ES File Explorer to have root under it's settings.
3. Navigate to /data/media
4. Ta-da! All your old files are there! NOW...
5. Select and move your files that you want to keep from /media/data to /media/data/0
This worked for me 100%. My free storage was only 2.58Gb with a fresh 4.2.2 install. Because I moved all my wanted files across and deleted all the other legacy items, it's now about 13Gb free.
Used the youtube vid so thanks for that osmosizz, worked well and thought me a bit in the process like getting your java paths right!!
Will try your method Joe if this happens again, cheers

I cannot write to microSD card (128Gb)!!

Any solution? Many thanks for your kind help!
First things first. Can you write to the SD card using the built-in File Commander app?
plvigo said:
Any solution? Many thanks for your kind help!
Click to expand...
Click to collapse
This really needs a fuller description of the problem: what exactly are you trying to do, what do you expect to happen, and what happens instead?
ghtop said:
This really needs a fuller description of the problem: what exactly are you trying to do, what do you expect to happen, and what happens instead?
Click to expand...
Click to collapse
Also is the sdcard genuine..?
Millions of fakes around..
Sent from my D5803 using XDA Free mobile app
I had same problem,first question should be where did you buy it and for how much? For example sellers from eBay are selling 128gb SD card for 15£ only but it's just rebranded 32 or 64gb cards!
Sent from my D6603 using XDA Free mobile app
Hi!
This is the Sd 128Gb I bought:
http://www.amazon.it/SanDisk-Androi...784&sr=8-1&keywords=micro+sd+128+gb+classe+10
I think that is a good one!
I saw that this kind of problem starts with Kit Kat, isn't correct?
It's very strange that I cannot copy from the device any file in the Sd card and viceversa!
Many thanks for your kind help!
It's probably not strange and yes, things changed with KitKat. But since you're still refusing to tell us what exactly you're trying to do and how, we cannot help you.
The device can read the SD card, but cannot write in it any kind of file; it's impossible to move or to copy, paste or delete any kind of file, using all file manager you can find in the google play, also trying with resco explorer for rooter user (my Z3 compact isn't rooted). I hope that this explanation can be clear enough!
It's very strange that you can use the Sd card like the older Jelly Beam system, that allow to move o copy any file from one directory to another or from the internal memory to the SD card!
Many thanks again for your kind cooperation!
Of course it's perfectly possible to copy to/from sd card on KitKat, otherwise what would be the point of even having them in KitKat devices.
But usage is more restricted than in earlier Android versions. Tell us *exactly* what you're trying to do, and we can point you in the right direction.
ghtop said:
Of course it's perfectly possible to copy to/from sd card on KitKat, otherwise what would be the point of even having them in KitKat devices.
But usage is more restricted than in earlier Android versions. Tell us *exactly* what you're trying to do, and we can point you in the right direction.
Click to expand...
Click to collapse
I think that my english is not good enough to explain what I would like to do!
I will try again: with my new Z3 compact and the SD Sandisk 128Gb I cannot copy or move a file from the internal storage of the device to the SD card and viceversa. Also, I can write the SD card, for example, to create or to rename or to delete a file or a directory in the SD card.
Is it clear?
I hope so and, once again, many thanks for your kind help!!
Have you tried the File Commander app provided by Sony? Otherwise apps can only write to their own folders.
ghtop said:
Have you tried the File Commander app provided by Sony? Otherwise apps can only write to their own folders.
Click to expand...
Click to collapse
Yes, I tried!
With the File Commander provided by Sony you can manage the SD, but you cannot use the directory which you created (that seems to be only for reading and not for writing) for example, for downloading files from app of the device (e.g. Ttorrent).
Any solution?
plvigo said:
Yes, I tried!
With the File Commander provided by Sony you can manage the SD, but you cannot use the directory which you created (that seems to be only for reading and not for writing) for example, for downloading files from app of the device (e.g. Ttorrent).
Any solution?
Click to expand...
Click to collapse
You *can* use it for writing ... with File Commander ... but as I stated, otherwise apps can only write to their own folders, e.g. SD card > Android > data > com.yourapp.something
Apps that support saving to SD card will typically have the option in their app settings, and they'll use their own app folder for that. Like Google Music or all of Sony's own apps.
You can also copy stuff to/from top level folders via USB or Wireless Media Transfer.
ghtop said:
You *can* use it for writing ... with File Commander ... but as I stated, otherwise apps can only write to their own folders, e.g. SD card > Android > data > com.yourapp.something
Apps that support saving to SD card will typically have the option in their app settings, and they'll use their own app folder for that. Like Google Music or all of Sony's own apps.
You can also copy stuff to/from top level folders via USB or Wireless Media Transfer.
Click to expand...
Click to collapse
Ok!! Many many thanks for your explanation!! Best regards!!
I can't delete photos from my SD since I started using QuickPic rather than the ultra buggy default 'Album' app thing.
Because the same policy applies to all user apps, they only have write access to their own folder for security reasons.

[Q] @#[email protected]#[email protected]#$ google

What possible reason (as in good reason), would google have for making it impossible for users to write to their own sd cards?
I just got this S5 (AT&T) and it updated when I turned it on before I realized that the SD card is mounted ro, AND that you can't root 4.4.4.
I've searched for workarounds and barring rolling back to 4.4.2 I haven't found any.
So, why did google do this?
And, is there really no way around it?
What good is an SD card that I can't even create, modify, or delete files from? Did they not realize that this is why we have external storage?
doesn't towelroot root 4.4.4? I'm a bit hungover this morning, but pretty sure you're rootable as long as you don't do an over the air (OTA) update to 5.0 from AT&T.
I'm on 5.0 rooted room and using at&t .
nicetucu said:
doesn't towelroot root 4.4.4? I'm a bit hungover this morning, but pretty sure you're rootable as long as you don't do an over the air (OTA) update to 5.0 from AT&T.
I'm on 5.0 rooted room and using at&t .
Click to expand...
Click to collapse
towelroot told me that it doesn't support this phone.
If 5.x is available for my phone, won't that cure the sdcard ro mess? I was reading on Android Police that 5 was supposed to fix things.
4.4.4 is rootable, 5.0 owa is not. Don't do anything before you read up on the process to root 4.4.4 first and then how to update to 5.0 while keeping root. As for the sdcard, it works fine, read and write, on all versions. You have a different issue.
From all I've read after searching, 4.4.4 is not rootable, and below 5.something the sd card is not writeable by any app that either google or the carrier did not install or include with the firmware. Are those points incorrect?
Thanks
Tref said:
From all I've read after searching, 4.4.4 is not rootable, and below 5.something the sd card is not writeable by any app that either google or the carrier did not install or include with the firmware. Are those points incorrect?
Thanks
Click to expand...
Click to collapse
Downgrade to nce. Read the entire OP
http://forum.xda-developers.com/showthread.php?t=3076803
Tref said:
From all I've read after searching, 4.4.4 is not rootable, and below 5.something the sd card is not writeable by any app that either google or the carrier did not install or include with the firmware. Are those points incorrect?
Thanks
Click to expand...
Click to collapse
Search Play Store for NextApp SDFix to make your SD card writable. Worked great for me.
From your pc, did your sd card are format in fat32? Did you see in esexplorer /storage/extSdCard?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
cmerlyn said:
Search Play Store for NextApp SDFix to make your SD card writable. Worked great for me.
Click to expand...
Click to collapse
Does it require root?
jo0147 said:
From your pc, did your sd card are format in fat32? Did you see in esexplorer /storage/extSdCard?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I've had this card in several phones, it's not new. This is a known issue with kitkat
All: I don't want to take a chance on a set of instructions that includes multiple mentions of others bricking their devices while trying to follow them. All I was hoping to do was first and foremost rant a bit about google, and second to learn whether or not google let common sense rule and restored full write access to "our" external cards in a later update. They shouldn't have messed with external r/w access in the first place. If they really want to make our phones more secure when installing apps they should do a better job of policing their appstore and the code they host on it, imo.
Tref said:
Does it require root?
Yes, root is required for the app.
Click to expand...
Click to collapse
Tref said:
Does it require root?
I've had this card in several phones, it's not new. This is a known issue with kitkat
All: I don't want to take a chance on a set of instructions that includes multiple mentions of others bricking their devices while trying to follow them. All I was hoping to do was first and foremost rant a bit about google, and second to learn whether or not google let common sense rule and restored full write access to "our" external cards in a later update. They shouldn't have messed with external r/w access in the first place. If they really want to make our phones more secure when installing apps they should do a better job of policing their appstore and the code they host on it, imo.
Click to expand...
Click to collapse
1) @muniz_ri's instructions will never result in a brick if followed correctly
2) there is no way to get sd card access on kitkat without root.
3) lollipop does support 3rd party apps writing to sd cards. However, the apps need to be updated to use the new API. (Most apps worth installing are updated by now)
Sent from my SAMSUNG-SM-G900A using Tapatalk
Tanks for the info about 5.0
I thing tail use the same policy about external storage. I not able to copie file from my linux to my usb, except for an other usb with tail partition.
Might it be that by disabling our ability to write to the external SD card, and limiting the abitlity of apps to do the same, that google is pushing people toward google drive? Could/would they be that avaricious?
It shouldn't come as a surprise as most all companies are driving toward paid storage.
But it is particularly galling when we are denied the use of storage that is vital to what we do on these things, and that we paid for ourselves.
Tref said:
Might it be that by disabling our ability to write to the external SD card, and limiting the abitlity of apps to do the same, that google is pushing people toward google drive? Could/would they be that avaricious?
It shouldn't come as a surprise as most all companies are driving toward paid storage.
But it is particularly galling when we are denied the use of storage that is vital to what we do on these things, and that we paid for ourselves.
Click to expand...
Click to collapse
Nope.. Android M is going have full sd card support including encryption.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Categories

Resources