So I noticed my TB throws me an error when backing up to SD. I checked and you can't write to it. So I found a solution where you add <group gid=”media_rw” /> to “WRITE_EXTERNAL_STORAGE“ so from there **** started to hit the fan. After I rebooted all the apps started to crash. Now ES explorer can't even see the extCard where my backup is. I managed to copy the backup back to etc/permissions, then rebooted but nothing changed it is still crashing. So I tried NAND restore and tried copying it from there and putting it in my current version but that didn't work either. Then someone with a similar problem said reflash the ROM without wiping and now my phone is sitting in Download mode and I can't even get to recovery :/ HALP!
Related
I just had to delete all my app/system data backups on Titanium Backup Pro because I literally had no storage space left internally and could not find a way to move my backups to the external SD card. I have root and Titanium Backup Pro, but I can't choose my SD card as a destination to save TBP information to because it says "This folder is not writable". I tried FolderMount but haven't had any success with that either. Furthermore, I'm on T-Mobile and we haven't gotten the "App2SD" function yet, but even if that firmware comes I can't get it because my phone is rooted. OTA root keeper didn't allow me to temporarily unroot and install any Samsung updates either.
Anyone have any suggestions? I won't be getting a custom ROM either, since I don't want to lose any functionality with apps or anything.
Suchomimus said:
I just had to delete all my app/system data backups on Titanium Backup Pro because I literally had no storage space left internally and could not find a way to move my backups to the external SD card. I have root and Titanium Backup Pro, but I can't choose my SD card as a destination to save TBP information to because it says "This folder is not writable". I tried FolderMount but haven't had any success with that either. Furthermore, I'm on T-Mobile and we haven't gotten the "App2SD" function yet, but even if that firmware comes I can't get it because my phone is rooted. OTA root keeper didn't allow me to temporarily unroot and install any Samsung updates either.
Anyone have any suggestions? I won't be getting a custom ROM either, since I don't want to lose any functionality with apps or anything.
Click to expand...
Click to collapse
recently i have the same issue as well on my i9505 so i tried the solution at the following location and it works:
http://www.thriveforums.org/forum/t...rite-access-android-3-2-if-you-re-rooted.html
Titanium Backup with insuffiecient storage space - 1 problem, 3 solutions
To summarize, I have come across three solutions to this problem.
1.
Change the backup-location to /storage...
Open Titanium and go to Settings/Preferences/Backup folder location
Change to: /storage/emulated/legacy/TitaniumBackup
2.
If you had Titanium Backup installed on a previous ROM, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working. Reinstalling the app might lead to an insufficient storage space error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup.
Here’s how:
Using any file explorer like Root Explorer or ES File Explorer, go to /data/app , find and delete ”com.kermidas.TitaniumBackup-1.odex“. Now you can install Titanium Backup again!
If there is no such file in your folder, that´s OK. But please don´t delete any .apk file!
3.
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>
New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Done.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that accesses either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
This may also fix other apps that have issues writing to the card.
---------------------------------------------------------------------------------
If you find this post useful, pls feel free to click on "Thanks".
Have a nice day
I have a Sprint GN3. I've rooted with CF Auto Root, flashed TWRP, flashed Jellybomb, and then restored back to stock from a nandroid backup. I've come across a few different errors, and I'm not sure if they're related or not.
For one thing, when I try to download a file in Chrome, I get a "No SD Card" error, even though both the SD card and the internal storage have plenty of space.
And then for the Audible.com app, even after clearing all the data, and uninstalling and reinstalling, I get the following error:
Failed to save your library to your device. /storage/emulated/0/Audible/<snip>: open failed: ENOENT (no such file or directory)
And it's right, I don't have an Audible directory in there, or anywhere else that I can find.
So my question is: Is that likely the correct path for the Audible app to save my data, and if so, why could it not create the Audible directory there?
And could that have anything to do with Chrome not being able to see or write to storage?
Thanks.
Edit: So I tried to manually create the Audible directory in /storage/emulated/0/ with Astro, and it wouldn't let me do it. Then I tried with Total Commander, and it worked, but I also go the "Total Commander has been granted superuser permissions" popup.
Then when I run Audible, I now get a EACCESS (permission denied) error.
So did I somehow set my internal storage to read only other than for root?
Possible solution.
Hi, it has been over a year since you asked this question, but I figured I'd respond anyway. I was experiencing a similar problem (exact same error that you describe) with my galaxy s4 provided by FreedomPop - I think it stemmed from their special version of android that they pre-installed on the phone. Anyway, their support staff suggested installing and running a program called "folder mount (root)" - it ran and found 2 errors, I had to re-boot my phone, and it completely fixed my problem.. Hope this helps
Glad you posted. Not much info out there on this issue, and your fix worked. Thanks.
SGH-i337m
Rooted and still on stock MK6
SuperSU and TWRP
Everything seemed ok after root and was running fine, phone restored up from google without issue.
First noticed the issue a few days later when swiftkey keyboard suddenly was unable to load language packs. Of course suspected it was a swift key problem and troubleshot from there. No solution found so gave up and switched back to default keyboard.
Tried to run Titanium, received unable to access "/storage/emulated/legacy/TitaniumBackup" error.
Used X-plore (with SU privilege) to try to access and create dir or write to directory, no success. Able to create and write in /(root) without issue.
/sdcard 777 and all subs are 775
Seems that some apps can write into /sdcard and others fail.
Assume that the Swiftkey failure was due to unable to write to the default directory (/sdcard/Android/data/com.touchtype.swiftkey/files/).
Tried factory reset and restore to backup when keyboard worked and no change.
Unless there are any ideas my next option is to roll back to factory unroot and start over or look for good custom rom and hope it fixes the problem.
Hey guys, I recently found out that my external SD card was not writable so I looked up how to fix this.
I found instructions to go into my platform.xml file in my system/etc/permissions folder
and added this line where instructed:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
I was doing this using ES File explorer and when I tried to save it, it said "Save Failed!". I closed the app and reopened the platform.xml file and my previous edit seemed to be still there.
This is where the issue begins:
After rebooting my phone, a bunch of popups start coming up on startup with the following "Unfortunately, [app] has stopped."
I figure that this might be a permissions screw up on my part. I am now unable to access many apps and when I open ES File Explorer again, it gives me the error: "Cannot Start Streaming Server" and it shows an empty folder for almost every directory.
Any suggestions or help would be appreciated. I have tried flashing CWM onto my phone as well but when I try to go into recovery mode, I get stuck on the screen where is displays Samsung Galaxy S5. As I was getting desperate, I was trying to factory reset but it doesn't seem like this is an option anymore seeing as I can't get into recovery mode. I am currently downloading the stock firmware and planning to flash that using Odin but I am hoping it doesn't come to that as well.
Model: S-G900H
EDIT: Just tried flashing stock firmware using odin and it is still no good. Desperate for any suggestions.
EDIT2: Factory Reset and its working now
Same problem with SGS4
Hello,
I faced the same problem with my Samsung Galaxy S4. Factory reset solved the problem. However, it would be better if this could be avoided/solved without doing a reset.
any other solution?
have anyone found any other solution to this?
I don't wanna factory reset cuz all my apps, data, settings in internal sd and now i can't back it up cuz can't read it from my phone
I was trying to allow universal writing to external SD card. I tried doing as I have done before on other Android devices, modifying platform.xml. I added in <group gid=”media_rw” /> to WRITE_EXTERNAL_STORAGE. I also made sure the permissions were RW-R--R--. Of course I made a backup just in case. When I rebooted, internal & external sd card are not visible. In es file explorer I can only browser \device. Any app not installed on root drive will not work. (such as droid mote & wireless controller) controller works when plugged in.
I booted into twrp and replaced the original file but no dice. I even removed a file (can't remember which file, but it started with a letter P) that was said to be altered with changes to platform.xml which would be recreated. I also tried "fix permissions" in twrp.
Where I'm at now is i downloaded the OS 1.2 images from nvidia. I did an adb backup of I assume only what was it device root (familiar screen from helium!).
Is it possible to just flash the system image to fix this? Or do I need to factory reset & re root?
Hi
I understand what you tried to do, to just give a small tip the program FOLDERMOUNT (gplaystore) will fix the inability to write to sd for your, when you start it for the first time after rooting your shield.
This works on all my shield devices (Portable & Tablet), on the shield tv you will have to sideload it possibly
I guess the best thing to do is go back tot the original release 1.2 from nvidia and reroot, sideload foldermount and see if it works.
Many alternative images for the shield have great new features but unfortunately don't support the wireless controllor protocol used by nvidia yet , they haven't release the drivers either.
Hope this helps & enjoy your Shield Box!
greetings
Jostiband
JohnHenryIron said:
1) I was trying to allow universal writing to external SD card. I tried doing as I have done before on other Android devices, modifying platform.xml. I added into WRITE_EXTERNAL_STORAGE. I also made sure the permissions were RW-R--R--.
2) Of course I made a backup just in case. When I rebooted, internal & external sd card are not visible. In es file explorer I can only browser \device.
3) Any app not installed on root drive will not work. (such as droid mote & wireless controller) controller works when plugged in.
4) I booted into twrp and replaced the original file but no dice. I even removed a file (can't remember which file, but it started with a letter P) that was said to be altered with changes to platform.xml which would be recreated. I also tried "fix permissions" in twrp.
Where I'm at now is i downloaded the OS 1.2 images from nvidia. I did an adb backup of I assume only what was it device root (familiar screen from helium!).
Is it possible to just flash the system image to fix this? Or do I need to factory reset & re root?
Click to expand...
Click to collapse
Thanks. I'll give it a shot. I should have made a nandroid before editing the file. Unfortunately, I thought making a backup of the file itself would be enough. I had just finished setting up all my emulators, mapping controls to my ps3 controllers & changing settings. I should have done this first.
I went ahead and restored my ShieldTV by unzipping the OS package I downloaded from Nvidia into my adb folder and running the included batch file
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
(I first flashed system & boot but still was no good)
As soon as I got SuperSU up & running I sideloaded NextApp SDfix
http://forum.xda-developers.com/showthread.php?t=2684188
That seemed to have done the trick. SD is now unrestricted.
The only issue I have now is whenever I boot, leanback launcher crashes: "leanback launcher has stopped working". It done it a few other times, but it seems to be random. Was restoring the way I did the best way to completely wipe the system or could it be something left behind that could be causing issues?
[Update] I don't know what has corrected the force close issue, but I have not had any more crashes. Everything's working smooth.
i just rooted, download SDFIX: kitkat writable sd on my phone, backed up the apk, installed on the shield and used that.