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,
Just wanted to start by saying, big thanks to DooMLoRD and the rest of the xda-developers forum for providing me the tools to get root access to a friends phone, who has recently accidentally deleted all their photos and videos. If we are successful, I'll definitely be suggesting that they make a donation to Doom for his epic contributions
I'm trying to help them recover the lost media. I know that typically performing data recovery on a phone requires root access, so I have gone ahead and done this. On with...
My question:
I've got an Xperia S running Jellybean (4.1.2) which is rooted. However attempting to use my data recovery tools on the phone, the device is not shown as a storage device. As you may well be aware, the S does not come with external storage. The S also has the 'mass storage mode' removed. Nice one Sony, give professionals another reason to avoid your products in the future...
I don't want to Flash the phone since any added files will start destroying the potentially recoverable data (plus I'd simply rather not format the phone if possible).
Is it possible to mount the internal storage of the Sony Xperia S as a drive so that I can run my PC based data recovery tools on it?
I imagine App Store apps are too lightweight to handle a file-based undeletion. If I could just see the device in my recovery apps I'm sure I'd be in business! I've attempted Recuva and R-Studio.
Doing some more research (like a good little n00b) I imagine I'm going to need SD Mounter.
I'm a little thrown off because 'SD' usually describes SD cards (of which the Xperia S has none). Also, the screenshots (for SD mounter) seem to indicate it's for ICS so I'm not sure if there's going to be a compatibility issue there.
Am I barking up the wrong tree by making this assumption? Should JellyBean have access to the mass storage and the option is simply not showing for some reason? Anyway, I'll continue working under my assumptions until someone suggests otherwise...
To get SD Mounter running, I'm going to need BusyBox. The problem is, I'm trying to read the BusyBox installation FAQ, and I'm finding it very vague. Like...
and save it under the name "busybox"
Click to expand...
Click to collapse
but it does not specify WHERE. Make a folder called 'busybox' on the root folder of the phone? Somewhere on my PC (the page suggests its for the PC rather than the phone)? Also I'm seeing Linux-looking command lines, but I'm on a PC... can I run this via the command prompt in Windows? I downloaded the 'binaries' like it said, but there aren't any executables in here...
Can anyone shed some light?
There's an app called BusyBox Installer, that installs it correctly on my Xperia S. That SD Mounter app works perfectly on 4.1.2, though. I use time to time. It just messes up a bit with Media Scanner, requiring me to do a reboot on the phone to make it work again.
I wish you lot of luck trying to recover your files. I once tried something like that, but came unsuccessful. There were some media I wish I had saved, but it wasn't THAT important, so I just gave up.
Suggest to your friend, though, to get an account on Mega, Box.net or Dropbox. All of them has auto backup of camera media to the server. All of them has options to backup only on WiFi, and even when charging only. The first two has 50 Gb of free storage for life (Box, you just need to sign with your Xperia device), and the later only 2 Gb, but you can get more and more with promotions.
Alternatively, he can enable the Google+ Auto Backup. There is 15 Gb (shared with Gmail and Google Drive) for pictures on original resolution or unlimited on 2048px, compressed. On Google+, though, you have the Auto Awesome, which make some awesome images.
Hope it helped. If I can help any further, just tag me
Sent from my LT26i using Tapatalk
Hey Felimenta97, thanks for your swift response!
Felimenta97 said:
There's an app called BusyBox Installer...
Click to expand...
Click to collapse
I see 'BusyBox Installer' in the Play Store, is that the one? Seems strange that the Play Store would add an app that requires rooting. Just wanna make sure I shouldn't be looking for it somewhere else (plus I'm away from that phone at the moment)
Felimenta97 said:
It just messes up a bit with Media Scanner, requiring me to do a reboot on the phone to make it work again.
Click to expand...
Click to collapse
That's okay. I've warned them this process might even brick their entire phone. They are prepared (I hope) for complete loss/compromised apps
Felimenta97 said:
...I wish you lot of luck trying to recover your files. I once tried something like that, but came unsuccessful...
Click to expand...
Click to collapse
*touches wood*. Gah I'm suddenly 10 times less confident this file recovery is gonna work. Wish me luck! They'll be crushed if I can't get their media back...
Felimenta97 said:
...get an account on Mega, Box.net or Dropbox...
Click to expand...
Click to collapse
Oh trust me, I've already given them the lecture
Thanks for your help!
TheWaste said:
Hey Felimenta97, thanks for your swift response!
I see 'BusyBox Installer' in the Play Store, is that the one? Seems strange that the Play Store would add an app that requires rooting. Just wanna make sure I shouldn't be looking for it somewhere else (plus I'm away from that phone at the moment)
That's okay. I've warned them this process might even brick their entire phone. They are prepared (I hope) for complete loss/compromised apps
*touches wood*. Gah I'm suddenly 10 times less confident this file recovery is gonna work. Wish me luck! They'll be crushed if I can't get their media back...
Oh trust me, I've already given them the lecture
Thanks for your help!
Click to expand...
Click to collapse
As I'm a lazy person, who can't find a way to break quotes into multiple parts (serious, how do you Do that, without having to write the quote code every time? It is not much, but I'm really lazy, so yeah.
Yep, that's the app. There's no reason for Google to block root apps. It's a function of the OS itself, just hidden from users. It's one of the easiest things to do on a Nexus device, after all. It's hidden because, if used without caution, can soft brick your device. But, don't worry, that shouldn't do any harm. At it least it hasn't with my device until now haha
As I said, I had already lost lots of stuff, and I didn't bothered much to go any further to recover it. It was a simply Install Recuva, run on the SD card and see if I could restore anything. Nothing? OK, no worries. As you already mentioned in your first post, avoid at all costs writing new files to the SD Card partition.
About the lecture, yeah, I imagined you had already told them, but it doesn't hurt to tell anyway.
About the SD Card on the Xperia S, another technical info you might or might not know, and also doesn't hurt to tell. Until Android 2.3, devices with a big internal storage required a partition for cache, one for data (apps and their own data), one for system, and one SD Card. The last one in Fat32 (plus others, but those are just too small and insignificant, for most, anyway) Think of a normal hard drive with plenty of partitions. Since Xperia S was developed (and launched) with 2.3 (one of Sony's biggest mistakes with this phone), it had to follow those "guidelines".
With Android 4.0 and beyond, the above mentioned data and SD Card turned into one partition, in Ext4 format. That data partition stores both apps and their data, and also other types of media, like media, documents, and etc. That storage goes into a mounted folder.
Anyway, again, wish you good luck. If they aren't very close friends/relatives, you should charge some money for all the hassle if you recover haha
Sent from my SGP311 using Tapatalk
Felimenta97 said:
how do you Do that, without having to write the quote code every time?
Click to expand...
Click to collapse
Haha, actually I still kinda do. #hen I hit 'reply' I empty the quote block, copy the empty quote block a few times, then copy-paste the parts of the text I'm replying to as I go
Felimenta97 said:
avoid at all costs writing new files to the SD Card partition.
Click to expand...
Click to collapse
Yeah absolutely.
Felimenta97 said:
Until Android 2.3, devices with a big internal storage required a partition for cache, one for data (apps and their own data), one for system, and one SD Card
Click to expand...
Click to collapse
Jeaz. Thank god I don't have to eff around with that!
Felimenta97 said:
With Android 4.0 and beyond, the above mentioned data and SD Card turned into one partition, in Ext4 format. That data partition stores both apps and their data, and also other types of media, like media, documents, and etc. That storage goes into a mounted folder.
Click to expand...
Click to collapse
I don't need to re-format the internal storage of the phone to attempt recovery do I?
Thanks again Felimenta!
TheWaste said:
Haha, actually I still kinda do. #hen I hit 'reply' I empty the quote block, copy the empty quote block a few times, then copy-paste the parts of the text I'm replying to as I go
Yeah absolutely.
Jeaz. Thank god I don't have to eff around with that!
I don't need to re-format the internal storage of the phone to attempt recovery do I?
Thanks again Felimenta!
Click to expand...
Click to collapse
Not in Xperia S case. As I said, it is on Fat32, so it is easily mount-able on Windows.
On any phone with Android 4.0 or more, you'd need a Linux to do the recovery. You can't format it, or else you will turn the device into a really expensive paperweight.
Sent from my SGP311 using Tapatalk
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
Just purchased my galaxy tab s. When I found out how it behaves with external memory rooted it at once, did the thing for read/write permissions, disabled this weird safety feature and... It does not alow editing files to any program which causes a big problem when I try to use "iGO" navigator for example which keeps its files on SD, or use some office program to edit any content on SD... It does alow creating and deleting files though.
Any ideas? Many thanks in advance!
I guess it's a kitkat problem. I heard in lollipop google returned to full read write access to SD cards.
Or try using a custom kernel
DUHAsianSKILLZ said:
Or tey using a custom kernel
Click to expand...
Click to collapse
what do you mean?
hmaxos said:
I guess it's a kitkat problem. I heard in lollipop google returned to full read write access to SD cards.
Click to expand...
Click to collapse
Maybe there is some fix possible about it?
gyrtaz said:
what do you mean?
Click to expand...
Click to collapse
Sorry i meant try a custom kernel. Skyhigh kernel fixes sd problems. I am running it now and it does work. Perhaps you can try that?
DUHAsianSKILLZ said:
Sorry i meant try a custom kernel. Skyhigh kernel fixes sd problems. I am running it now and it does work. Perhaps you can try that?
Click to expand...
Click to collapse
I only found topics about sd r/w problems where they say that I need to root and run some code (or edit some file manually) to fix permissions. Well I did it... But I couldn't find anyone talking about editing... I can get around that by saving an edited file in diferent name, deleting the original and renaming it back to original... But programs I try to use does not do tricks like that :silly:
Was your problem similar? Any links regarding the fix of this?
gyrtaz said:
I only found topics about sd r/w problems where they say that I need to root and run some code (or edit some file manually) to fix permissions. Well I did it... But I couldn't find anyone talking about editing... I can get around that by saving an edited file in diferent name, deleting the original and renaming it back to original... But programs I try to use does not do tricks like that :silly:
Was your problem similar? Any links regarding the fix of this?
Click to expand...
Click to collapse
Well I have always ran skyhigh kernel for my sd card. Even if rooted with the sd fix my sd card still worked fine(on stock rom). Perhaps it could be the file manager your using? Well i also seen the r/w fix by editing a file but that was months ago and I forget how to do it. Sometimes sd fix app would say its fixed, but it wasnt. So using another app from the playstore could fix it? Hope this helps
DUHAsianSKILLZ said:
Well I have always ran skyhigh kernel for my sd card. Even if rooted with the sd fix my sd card still worked fine(on stock rom). Perhaps it could be the file manager your using? Well i also seen the r/w fix by editing a file but that was months ago and I forget how to do it. Sometimes sd fix app would say its fixed, but it wasnt. So using another app from the playstore could fix it? Hope this helps
Click to expand...
Click to collapse
The file seems to be edited properly but none of programs are able to edit files. Biggest problem at the moment that iGO won't save its configuration and shut down when a route is entered. I assume it is because of unability to edit files in sd also
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
I had to use it for some apps, so I say YES. Lollipop has the same regulations for the external SD like KitKat, so the apps have the same problems.
misteurz said:
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
Click to expand...
Click to collapse
I use it as well and it works - I can now save TB backup directly on my external SD :good:
clandes said:
I use it as well and it works - I can now save TB backup directly on my external SD :good:
Click to expand...
Click to collapse
+1
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
I downloaded SDFix from Google Play (pretty sure it's the same one I used when KitKat first came out) and it reported that the app wasn't necessary.
EU H815 rooted with the recently released Low Effort Exploit (and not by unlocking the bootloader via LG's Dev site).
TiBu was one of the first apps I installed after rooting earlier this week, and it never had a problem backing up to my ext. SD card.
Midnight_Rider said:
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
Click to expand...
Click to collapse
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Charsher47 said:
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Click to expand...
Click to collapse
Don't get the option to 'protect' backups though if you go this route. Only if you use the default setting with edited platform.xml file.
TecknoFreak said:
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Click to expand...
Click to collapse
Same here, and this worked perfectly fine on my H815 (SEA version). Now I can actually let GoneMadMusicPlayer edit tags in my music collection.
Thanks :good: