Related
I updated my Vzw GNex to the vzw 4.2.2 ota this afternoon. Everything works fine except when I try to download something from chrome I get a message saying "No SD card" when I click a download link. I can access the sd card just fine with rootexplorer and the stock browser downloads things just fine. I tried clearing cache and data for chrome and even uninstalled and reinstalled it. Anyone else having this issue? Is there a way to fix it?
MurdocZero said:
I updated my Vzw GNex to the vzw 4.2.2 ota this afternoon. Everything works fine except when I try to download something from chrome I get a message saying "No SD card" when I click a download link. I can access the sd card just fine with rootexplorer and the stock browser downloads things just fine. I tried clearing cache and data for chrome and even uninstalled and reinstalled it. Anyone else having this issue? Is there a way to fix it?
Click to expand...
Click to collapse
I am seeing the same issue on my GNex running AOKP mr-1 build 6. I have not found a fix yet.
Of note: I do NOT have this issue on my Xoom running 4.2.2 [baked_wingray_bb-8]
Try making a copy of your sdcard and factory resetting, then copy all the files over using MTP, not ADB.
I get that if i copy files over using ADB.
Mach3.2 said:
Try making a copy of your sdcard and factory resetting, then copy all the files over using MTP, not ADB.
I get that if i copy files over using ADB.
Click to expand...
Click to collapse
Mach - Thank you for your response. I have to ask though, is there any other way?
Per your recommendation I began to copy my sdcard but quickly realized that given the amount of data on my phone this would be painful using standard methods. Windows [7] was reporting no progress and seemed as if it was going to take forever to copy the contents and applications like RichCopy and TeraCopy do not see MTP devices
In the end, I simply used 'adb pull' to copy the contents. So, while it's good that I have a copy, I'm not sure how I plan to restore the copy after a factory reset without using 'adb push', which you said sometimes causes the issue. I always thought that using 'adb' was considered more reliable than the MTP interface.
Recommendations?
Thank you.
Hi, if you are running Xprivacy you should check if you have denied the 'Storage' permission for Google Chrome. That was the problem in my case.. :silly:
getting same problem on my moto g after rooting and flashing sm roms
Megabliss said:
Hi, if you are running Xprivacy you should check if you have denied the 'Storage' permission for Google Chrome. That was the problem in my case.. :silly:
Click to expand...
Click to collapse
hy its not the thread for moto g bt im getting same problem on my cell since i rooted it .. and by the way what u mean by xprivacy..??? xplain steps to allow it...
it seems like my system cant make changes to internal sd .. it cant take screenshots,gallerythumbnals all gone etc. -_-
I had similar troubles after changing roms on my N5, found this that fixed it just download terminal emulator and do the given commands, hope it helps people in the future: http://blog.wadegarrett.com/2014/08/10/easy-solution-for-sdcard-error-on-android-l
I have the same problem and the info in the link didn't work
CalebQ42 said:
I had similar troubles after changing roms on my N5, found this that fixed it just download terminal emulator and do the given commands, hope it helps people in the future
Click to expand...
Click to collapse
Thanks! It worked for my Xperia z ultra
lakhwani009 said:
hy its not the thread for moto g bt im getting same problem on my cell since i rooted it .. and by the way what u mean by xprivacy..??? xplain steps to allow it...
it seems like my system cant make changes to internal sd .. it cant take screenshots,gallerythumbnals all gone etc. -_-
Click to expand...
Click to collapse
Hi, sorry it took a long time to reply, I just saw it. Xprivacy is an Xposed mod to manage the permissions for each app. If you haven't installed it then it is not causing you any problems!
In regards to my aforementioned issue.
"Cannot download due to SD card missing" Error.
Simply open a terminal emulator and type in the following.
su
restorecon -FR /data/media/0
Reboot and it should work thereafter.
wrong thread, genius, sorry.
(that is the solution though )
CalebQ42 said:
I had similar troubles after changing roms on my N5, found this that fixed it just download terminal emulator and do the given commands, hope it helps people in the future: http://blog.wadegarrett.com/2014/08/10/easy-solution-for-sdcard-error-on-android-l
Click to expand...
Click to collapse
I had the problem with my Galaxy S3 running Lineage OS 14.1. This helped, Thanks!
I have just found another and simply solution in no rooted devices. Just open file manager and rename 'Download' folder to 'Download2' and then the system will automatically recreate 'Download' folder. Now, you are able to download.
mbahar92 said:
I have just found another and simply solution in no rooted devices. Just open file manager and rename 'Download' folder to 'Download2' and then the system will automatically recreate 'Download' folder. Now, you are able to download.
Click to expand...
Click to collapse
That worked for me. You saved my day!
Hi all, i have a nexus 7 2013 with 4.4.2 Android stock
I tried to install whatsapp on the tabled following many many guides on internet. At end of my experiments i understand that whatsapp crash if i install it on an user that it is not owner.
Someone else have a second user on the tablet and have a whatsapp working there?
I have installed whatsapp on my nexus 7 second gen. It works fine for mr.
Sent from my GT-I9500 using xda app-developers app
vijay6788 said:
I have installed whatsapp on my nexus 7 second gen. It works fine for mr.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
you have it on the second account? (not the owner). if yes what procedure you follow? can you link pls
atomico001 said:
you have it on the second account? (not the owner). if yes what procedure you follow? can you link pls
Click to expand...
Click to collapse
i have the same problem on my galaxy s4 i9505 running stock rom android 4.4.2
i had whatsapp installe on my device
then i enabled multi user support using xposed mod multi users ... which works fine.
when i switch to the second profile i can install whatsapp from playstore ( whcih installs very quick ... i don not think it is downdloading).
i can start whatsapp but after I enter the verification codefor my second number in whats App it just crashes ....
Anybody has a clue ? Would be great to see this working ...
my crash report says:
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
it seems too be a problem with the second user not beeing able to access /data/data
http://stackoverflow.com/questions/...rror-when-copying-a-sqlite-database-from-asse
only ... i do not know what to do with this information ...
anybody ?
hi mephisto.. i try for day and day to find a solution but seem that on internet noone user multi-user and whatsapp on android...
atomico001 said:
hi mephisto.. i try for day and day to find a solution but seem that on internet noone user multi-user and whatsapp on android...
Click to expand...
Click to collapse
Hi atomico001, I too have the same problem using multi-user and whatsapp on android. Can you share your solution?
psdp said:
Hi atomico001, I too have the same problem using multi-user and whatsapp on android. Can you share your solution?
Click to expand...
Click to collapse
i just wrote that i haven't a solution..
atomico001 said:
i just wrote that i haven't a solution..
Click to expand...
Click to collapse
I was trying to achieve the same for my tablet and I've found a solution. I've posted an article on my fresh new blog
camolin3.tumblr.com/post/91306835140/make-whatsapp-to-run-in-a-second-user-of-an-android
Basically you have to grant read, write and exec permission to all the users of the /data/data/com.whatsapp directory.
I hope it helps you.
camolin3 said:
I was trying to achieve the same for my tablet and I've found a solution. I've posted an article on my fresh new blog
camolin3.tumblr.com/post/91306835140/make-whatapp-to-run-in-a-second-user-of-an-android
Basically you have to grant read, write and exec permission to all the users of the /data/data/com.whatsapp directory.
I hope it helps you.
Click to expand...
Click to collapse
unlucky it is not rooted but ty for news
atomico001 said:
unlucky it is not rooted but ty for news
Click to expand...
Click to collapse
atomico001, have you tried towelroot? It is very easy to use: download an app, press a button, and after a restart you got rooted.
That's the way I rooted my nexus, and since we have the same tablet I guess it should work for you as well.
youtube.com/watch?v=P80NMQss2B0
camolin3 said:
atomico001, have you tried towelroot? It is very easy to use: download an app, press a button, and after a restart you got rooted.
That's the way I rooted my nexus, and since we have the same tablet I guess it should work for you as well.
youtube.com/watch?v=P80NMQss2B0
Click to expand...
Click to collapse
no wipe needed? i know that from 4.3 and more it is not more possible
atomico001 said:
no wipe needed? i know that from 4.3 and more it is not more possible
Click to expand...
Click to collapse
No wipe required. My Nexus 7 2013 has android 4.4.4. Try it (under your own risk).
Any update on this issue? I am trying to install it on a Second account, which is not the owner and it just crashes after verifying the code.
It works!
camolin3 said:
I was trying to achieve the same for my tablet and I've found a solution. I've posted an article on my fresh new blog
camolin3.tumblr.com/post/91306835140/make-whatapp-to-run-in-a-second-user-of-an-android
Basically you have to grant read, write and exec permission to all the users of the /data/data/com.whatsapp directory.
I hope it helps you.
Click to expand...
Click to collapse
Thank you camolin! This fixed it for me! Note that the permission change needs to be recursive (for all subfolders as well)
Update
etienne.vdlinde said:
Thank you camolin! This fixed it for me! Note that the permission change needs to be recursive (for all subfolders as well)
Click to expand...
Click to collapse
Here's an update - seems like the location /data/data/com.whatsapp will be shared amongst all users - causing your whatsapp db to corrupt each time you fire up another user's whatsapp. I found a way around this (probably not the cleanest) by keeping the contents of the com.whatsapp folder in a space where android can manage seperate user access (e.g. /sdcard/temp) and inserted a static link to it at the original place where whatsapp expects it. That is:
backup you whatsapp messages in app
exit and uninstall all instances of whatsapp
create a folder /sdcard/temp/com.whatsapp
copy the contents of /data/data/com.whatsapp to /sdcard/temp/com.whatsapp
remove /data/data/com.whatsapp
create a static link at /data/data to /sdcard/temp/com.whatsapp (requires terminal access):
ln -s /sdcard/temp/com.whatsapp /data/data/com.whatsapp
verify linked access to folder /data/data/com.whatsapp from all user accounts
reinstall whatsapp (might need to recover backed up messages)
I am now able to run a seperate whatsapp under each user account without affecting the other (thus far)
Update - this setup does not survive a restart (which then requires unlinking and reinstalling whatsapp)
Any update on this? Ive done the above. When i go to the second user, and use a file explorer to view the contents of /data/com.whatsapp .... It is the same data as the first user? I was hoping that changing to to the second user would leave this empty? Ie. It seems that the sdcard on the second user doesnt get used at all. Any ideas? (in Not using a nexus)
I have rooted and have disabled most of the recommendations listed here: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503
I now find myself unable to create a folder (using ES or ASTRO) in any directory?
Very confused
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)? I checked out that thread, downloaded the "SDFix: KitKat Writable MicroSD", rebooted and still does not work. I am attempting the wanam xposed fix but whenever I attempt to use the xposed installer, it can't extract (due too inability to write to disk). Is there a way to install xposed via odin?
Thank you for the response. I am new to rooting and Android in general, but I am trying!
lordnorth4 said:
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)?
Click to expand...
Click to collapse
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Freakstyler said:
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Click to expand...
Click to collapse
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
same issue
lordnorth4 said:
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
Click to expand...
Click to collapse
I have the same exact issue. I can add folders through the Samsung My Files; the ES File explorer gives me 'Sorry, operation failed' also. I have reformatted, and re-rooted, but same issue.
Im no expert mind you, but i had this exact same issue, pretty sure its a kernel issue, specifically i think selinux and its two modes passive and enforce.........first i tried an app on the store thats suppose to change this mode upon reboot, before i realised newly installed apps were now also having issue with internal storage........anyways, long story short, i checked out the lone kernel in the dev thread, paraphrasing, selinux disabled, or some such, and bingo bango, everythings back the way it was
If you have recovery, might be worth backing up and flashing kernel, see if that works, report if it does for the benifit of others that might find themselves with internal storage issues
Edit
T700/T705 version
http://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-skyhigh-tw-kernel-t2806563
"SELinux PERMISSIVE" - turns out kernel is permissive by default, not disabled
T800/T805 version
http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
Hopefully thats usefull
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
UpInTheAir said:
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
Click to expand...
Click to collapse
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
banderos101 said:
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
Click to expand...
Click to collapse
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
UpInTheAir said:
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
Click to expand...
Click to collapse
Thanks by the way, for your kernel, and its rescue of my device .........and not least of all, the work you've done with our devices:highfive:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
Worked fine until i started rooting and flashing the recovery, pretty sure during that process something triggered this issue
UpInTheAir said:
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
Click to expand...
Click to collapse
Yup, first post in the Samsung threads and I messed up. Now I have to find a proper thread to get an answer....
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
banderos101 said:
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
Click to expand...
Click to collapse
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
UpInTheAir said:
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
Click to expand...
Click to collapse
Okay, i could have sworn that i was experiencing the same issue on the external, aswell as the internal, infact im certain, i remember trying the external fixes first, assuming i had the kitkat external storage issue, untill i noticed it was also happening to the internal storage.......this was the first and only thread i found concerning internal issues, maybe i had both issues, but then again, the kitkat fixes didnt fix the external issues, your kernel seemed to fix both, at least in my specific situation
Edit
Okay, i see maybe you were answering my question from a more knowledgeble perpective, it just seemed that whatever affected the internal, was also affecting the external, otherwise, wouldnt the sdfix and/or root file managers like es file explorer with a kitkat/sd workaround, worked, both of which i tried.......seems like whatever was affecting my internal was also affecting external..........one way to find out is if folks who find themselves with the internal issues could confirm if they also have external issues, and whether the external fixes work or not
Edit
Ive just come to realise the fact that i was having internal storage permission issues might have caused the external storage fixes not to function properly, and that maybe i did indeed have two seperate issues, and that whatever was affecting my internal storage was a different issue to the kitkat/external sd card issue, so maybe you are right in saying that this only fixes the internal storage issue, which in turn allowed the external storage fixes to work.........hopefully time will tell, and hopefully, some of that makes sense
I've recently switched to an M8 from a Z2 and am no stranger to the roadblock that is the External SD access issue, but can't seem to find a solid fix for the HTC One.
Have spent the evening unlocking the bootloader an rooting only to have some strange issues. It seems that whenever an app attempts to write to the system the phone reboots. This means I can't install NextApp SD Fix or make changes to the platform.xml file since they send me into a reboot.
Additionally, removing system apps with Titanium backup doesn't stick as after a reboot they all reappear.
My question is, am I missing something that is causing these problems and is there a fix for the external SD problem?
Thanks
DeGozaru said:
My question is, am I missing something that is causing these problems and is there a fix for the external SD problem?
Click to expand...
Click to collapse
You need a kernel module:
http://forum.xda-developers.com/showthread.php?p=51543139
Or a custom kernel.
BenPope said:
You need a kernel module:
http://forum.xda-developers.com/showthread.php?p=51543139
Or a custom kernel.
Click to expand...
Click to collapse
Thanks BenPope. Gave it a try but can't get it to work. Have asked for help in the thread.
Additionally, I have solved my issue for external SD write access by following the steps here: http://forum.xda-developers.com/showpost.php?p=54696085&postcount=13
Thanks mods for moving thread. Please close.
Help me Plz..................:crying:
akashaakash said:
Help me Plz..................:crying:
Click to expand...
Click to collapse
If you want help, so Post more Details.
Model
Rom Version
And what you have done?
bierma32 said:
If you want help, so Post more Details.
Model
Rom Version
And what you have done?
Click to expand...
Click to collapse
Well Firstly,
Android Version 4.4.2..........in wich i was unable to Write nythng in th SD Card..........i cant even install an .apk file....actually i was trying to install
new updated Whatsapp........wich is nt for tablets......
Accrding to the Instruction Odin 3.07 Helpd me to gt root access......oh i forgt, th model is SM-T311 tab 3 8.0.......
aftrwrd by means of ES file Explorer......i tried to edit platform.xml file.....but i failed ...........system was not allowing me to do so.......
thn i gt an app named Nextapp SD fixer....installed.....nd again i was facing th same problm .......stuck.d in btwn.........SD card wasnt allowing me....to do so......used titaniumBackup..........for backup......thn i restartd my device.......suddenly aftr rebooting .....msg loop generated on my screen......tht com.android.systemui has stpd .......thn i decided to restore my device .....remote restore ........using android device manager.....thn also tht msg is still popping out ....com.android.systemui has stopped .......tried safe mode access also.....but tht same old story.....m nt gttng ROM version.....i cnt even open my setting panel..in my tablet.........
Check your SD card on another device. The card could have gone bad (can't write, occasional problems reading, can't format). I've had it happen to me twice.
If system files are on the SD card, read-only can cause problems. Last time I had that happen, I believe I ended up reflashing a clean stock ROM and starting over
Recommend saving app data (not the apps as one of them could be the problem) before nuking your flash though.
Greaper88 said:
Check your SD card on another device. The card could have gone bad (can't write, occasional problems reading, can't format). I've had it happen to me twice.
If system files are on the SD card, read-only can cause problems. Last time I had that happen, I believe I ended up reflashing a clean stock ROM and starting over
Recommend saving app data (not the apps as one of them could be the problem) before nuking your flash though.
Click to expand...
Click to collapse
The point is Katkat v4.4.x dont allow apps to write or install in sdcard, you just change The permissions to write.
In your case , install by a clean setup The Stockrom, root it, change The Permission to write on sdcard at Platform.xml with a root Explorer.