Related
I have been trying to for over a week in the captivate forum to get ANYONE to try and help me and so far no one will. So i'm really hoping someone will take the time, i will PAY YOU UP FRONT over paypal to help me. I am DEAD SERIOUS.
Have a captivate, but this problem is not exclusive to this phone. This error has happened on just about any/every android phone there is.
Phone was working fine, have been putting any and all custom roms on that i wanted, but went to install a new custom rom (cog4), and it fails every single time at system/xbin/su. Now ANY rom i install (custom), gives me that same error. NO CUSTOM ROM WILL INSTALL. THEY ALL FAIL. I have flashed back to stock a million times, wiped, re-partitioned the sd card, master cleared, and done all of those in every combination possible. The ONLY rom i can put on here is the one i had RIGHT before this problem started (cog3.04). Only roms that can be flashed via odin will go on my phone now. All zip files fail.
I am not a noob and know my way around a computer. I promise if someone tries to help me i will be very prompt in my responses and will try ANYTHING that you ask me to. I have been googling for over a week hours a day, i am never gonna resolve this issue unless someone with the know-how helps me Every time this topic is brought up on any forum on the internet, the problem never gets solved and it fades away....there is no answers out there. Someone who knows this stuff is my only hope
I will pay you to help me even if your troubleshooting does not work
Just out of curiosity, did you open Rom Manager once you installed it to grant it superuser rights? Also, make sure you Click the top link in Rom Manger and choose your phone. "Flash ClockworkMod Recovery"
Yes tim i have done that.
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
JoelParke said:
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
Click to expand...
Click to collapse
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
timbrendelaz said:
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
Click to expand...
Click to collapse
Yes i do 10char
xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
Not sure as this looks like a patch and specifically asks for no wipe. Also my knowledge is limited as to what harm you can do that will make the phone unusable -- BUT you are already into that realm . Perhaps someone with deeper specific experience can answer this????
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
K will report back.
Also it looks like the update.zip file is long gone....
JoelParke said:
Also it looks like the update.zip file is long gone....
Click to expand...
Click to collapse
??? 10 chars
xsteven77x said:
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
Click to expand...
Click to collapse
using adb remount will set the /system partition as read/write. This may help.
xsteven77x said:
??? 10 chars
Click to expand...
Click to collapse
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
JoelParke said:
using adb remount will set the /system partition as read/write. This may help.
Click to expand...
Click to collapse
I have been doing that within sgs tools, not the same thing?
timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
JoelParke said:
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
Click to expand...
Click to collapse
Oh ok sorry i didnt understand. Ty for trying regardless though.
xsteven77x said:
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
Click to expand...
Click to collapse
LOL, of course......
If it doesn't install, try installing Terminal Emulator from the Market
Ok so inside of the system folder they both have the permissions set to what you wrote.... .
There is only a bin in the folder right before the system folder...should there be an xbin there too?
I tried to install wifi calling via titanium backup and I keep getting Invalid sim. I'd appreciate if someone can help me get this feature working again. I've been searching for about an hour with no luck
payazo915 said:
I tried to install wifi calling via titanium backup and I keep getting Invalid sim. I'd appreciate if someone can help me get this feature working again. I've been searching for about an hour with no luck
Click to expand...
Click to collapse
My suggestion is do not us TB to restore your apps. Only data. It gets finicky when trying to install apps from different ROMs. Whenever possible do fresh installs of your apps. I attached the .apk for you to try.
Copy the WiFi-Calling.apk to your sd card. You can use 'Super Manager' from the app market. Open 'Super Manager' then go into file manager. Check your settings in Super Manager by going into setup/root and make sure 'enable ROOT function' is checked. Find your WiFi-Calling.apk on your SD Card and copy. Press 'Back up level folder' twice. Go into 'system/app' and make sure 'system is set to (r/w). Paste the WiFi-Calling.apk in the folder.
Ok..let me try that. Thanks for the info
Sent from my A100 using xda premium
No luck...wifi calling just keeps trying to enable.
Sent from my A100 using xda premium
payazo915 said:
No luck...wifi calling just keeps trying to enable.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
So you deleted the .apk you tried to back up through TB? I assume you have a SGS 4G along with your A100? And you followed the procedure that was laid out for you?
OH and... hit thanks and I'll keep trying to help you
Just kidding...
There is a chance there is another .apk that needs to go along with the .apk I attached above. I'll take a look or maybe somebody else will read and advise.
Or you may need to reflash... before doing so, unzip the ROM, add the .apk in the appropriate folder, then zip ROM back up, then reflash.
Raver took the libs out. So until the next update just flash back to something else if you really need wifi calling.
Nevermind.
lumin30 said:
Ok... Raver appears to not have taken out the libs. The problem you are having, from what I see, is Raver modified the build.prop.
It appears that the following needs to be added back:
1)Go to /system/build.prop and open using Super Manager or some similar file manager with ROOT permissions.
2) Go to the very BOTTOM of the prop, and add this:
## start GAN-Lite ##
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libsec-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
## end GAN-Lite ##
3) In Super Manager hit menu then Save
4) Reoot into recovery and wipe cache & Dalvik Cache just to be safe
5) Reboot and let phone sit 10 mins to rebuild cache
Maybe Raver or somebody else can confirm this fix.
Click to expand...
Click to collapse
Ok I'll try this once my phone has charged again and see what happens and thanks for the help..its much appreciated.
Sent from my SGH-T959V using xda premium
payazo915 said:
Ok I'll try this once my phone has charged again and see what happens and thanks for the help..its much appreciated.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Scratch that... I read the valhilla thread and Raver said "the sim card service for wi fi calling also was removed." So as far as I know if you flash the previous version... rc3.1 it has it in there. That is what I am on and I have it.
He also said in the thread he plans to add it back in the next update.
yeah sorry guys I should have made it clear where I got that from.
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Note : Another Playstore application avaliable to fix this issue : https://play.google.com/store/apps/details?id=nextapp.sdfix.
Edited on request of @webmastir
try it yesterday 4 times and every time I had a Bluetooth error.
The only way I was able to use Kitkat with my note was using a custom ROM. Do not understand, what are custom rom builders do other way, but it work for me...
And more. Even with custom rom, the external sd is showed the "different" way, when in 4.3 , For example, in Total commander, there is no SD2. and some other software, do not define microsd as SD card. Just another folder in fail system...
zpjotr said:
try it yesterday 4 times and every time I had a Bluetooth error.
The only way I was able to use Kitkat with my note was using a custom ROM. Do not understand, what are custom rom builders do other way, but it work for me...
And more. Even with custom rom, the external sd is showed the "different" way, when in 4.3 , For example, in Total commander, there is no SD2. and some other software, do not define microsd as SD card. Just another folder in fail system...
Click to expand...
Click to collapse
Well, the architecture is the same and permission manisfest is used with all roms, sammy developers forgot to add a group I guess or did it on purpose, who knows.. but this worked like a charm for me after I flashed kitkat and felt handicapped.
Maybe you have messed up with some permission or something if you're getting the bluetooth error.
Try to do a clean flash again and then edit the file. If clean flash is not possibe pm me ur email. I will send you my xml and try to replace it with yours to see if that fixes your problem.
Sent from my SM-N9005 using xda app-developers app
this method isnt working for me I already modified the file but still cant make the programs to access the sd card, worst than that my internal storage is "write protected"... Im starting to think to get rid of this phone it has been nothing but problems since the beggining: Region Lock, Knox crap and now the SD... whats next?
carlomagno78 said:
this method isnt working for me I already modified the file but still cant make the programs to access the sd card, worst than that my internal storage is "write protected"... Im starting to think to get rid of this phone it has been nothing but problems since the beggining: Region Lock, Knox crap and now the SD... whats next?
Click to expand...
Click to collapse
Can you add a screen of the platform.xml? Perhaps you may have wrongly entered the permission gid.. And you need to restart the phone after editing the file.
mateenf said:
Can you add a screen of the platform.xml? Perhaps you may have wrongly entered the permission gid.. And you need to restart the phone after editing the file.
Click to expand...
Click to collapse
Sure here it is.
I made it by flashing the zip file, am not able to copy or edit files in the internal memory because "write protection"
carlomagno78 said:
Sure here it is.
I made it by flashing the zip file, am not able to copy or edit files in the internal memory because "write protection"
Click to expand...
Click to collapse
I'd strongly recommend to do a full wipe and factory reset if you're having a custom recovery. Ive read fee forums outside XDA that many a times flashable zips have cause a problem to platform.xml.
If you dont have a custom recovery then you may need to flash the firmware again and then edit the file.
Sent from my SM-N9005 using xda app-developers app
mateenf said:
Well, the architecture is the same and permission manisfest is used with all roms, sammy developers forgot to add a group I guess or did it on purpose, who knows.. but this worked like a charm for me after I flashed kitkat and felt handicapped.
Maybe you have messed up with some permission or something if you're getting the bluetooth error.
Try to do a clean flash again and then edit the file. If clean flash is not possibe pm me ur email. I will send you my xml and try to replace it with yours to see if that fixes your problem.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
thank you for proposed help. But I'm to tired of setting up phone after all weekend "fun" with rom flashed (all together 5-6 times with full wipe)
I'm almost sure, I wasn't messing with anything else - I did it more then 4 times, and Bluetooth was working until I edit platform.xml
now, I start to think, it's possible the ownership and permissions were changed after editing (I was using total commander and did not check it after saving the file).
But, I'm not the only one - there someone having same issue:
http://forum.xda-developers.com/showpost.php?p=49530438&postcount=3
P.S. I wasn't modifying /mnt/media_rw
some application don't have permission to write extSdCard
I made this mod but some application don't have permission to write ExtSdCard.
these application in my case are: dolphin wont download files, tomtom navigator doesn't work but moving tomtom folder in internal sdcard it works.
Is there anybody that have same issue?
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
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.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Hey, I'm having the same issue, it's affecting my titanium backups. I tried the very same method above over the weekend based on instructions from another thread, but still no success.
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 06:40 PM ---------- Previous post was at 06:27 PM ----------
Hey, your permissions are correct, previously I granted sdcard_rw rights, but not media_rw as mentioned in your discussion. Since the changes to show
"
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
"
I'm able to write and titanium backup is running smoothly.
Thanks and Cheers!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thanks guy, work great for me on stock rom rooted NA6 kitkat
liva said:
Thanks guy, work great for me on stock rom rooted NA6 kitkat
Click to expand...
Click to collapse
Welcome Glad was able to help
Sent from my Nexus 5 using xda app-developers app
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
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.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Thanks for the best additional thing to bring stuck with KitKat.
sent from my iPhone 6s 64gb 5.7inch Super Oled screen and spen
Will there be a solution for non rooted stock rom?
liomajor said:
Will there be a solution for non rooted stock rom?
Click to expand...
Click to collapse
That will have to wait for Samsung to push the OTA update.
Sent from my Nexus 5 using xda app-developers app
Today's rollout for OMN, SIM, MTL and ATL have the same missing media_rw.
If you are not on root (!!!knox 0x1!!!), i suggest NOT to update to 4.4.2
or a lot programs you paid for might not work properly if they need
access to ExtSdCard.
Dunno if its a bug or changed permissions to use ExtSdCard.
Currently only programs with system access like stock Filemanager are working.
mateenf said:
That will have to wait for Samsung to push the OTA update.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I don't think there will be a fix. This is a kitkat feature where app that need access to external sd need to ask for permission. So it's up to each app developer to update their app with this permission.
Sent from my SM-N9005 using XDA Premium 4 mobile app
antt00 said:
I don't think there will be a fix. This is a kitkat feature where app that need access to external sd need to ask for permission. So it's up to each app developer to update their app with this permission.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1
Sent from my Nexus 5 using xda app-developers app
Can confirm that it is working on my SM-N900W8.
Thank you.
Editing permission.xml worked on exynos version.
Sent from my SM-N900 using Tapatalk
Hi,
I rooted my phone because I wanted to use an application called FolderMount, so I could store big chunks of data from apps onto my SD card.(it seems as though the SD card is useless on Android)I am using an HTC Desire 601, with Android version 4.2.2. Now my problem is that, I'm having an error with FolderMount because of something to do with external SD card r/w permissions.(no this is not specific to the app, it's a software wide problem, that's why I'm posting here.) So I found a "fix" that involved editing platform.xml and adding a line. However, everytime I try to edit it, either the phone just reboots, or no changes are made. Basically, the system folder is denying me r/w access. In root explorer there is a feature to mount it temporarily as r/w, but then if I reboot my changes are lost. This is a problem which I think is also not allowing me to install Busybox. Please help me with this. Thank you.
Jason1712 said:
Hi,
I rooted my phone because I wanted to use an application called FolderMount, so I could store big chunks of data from apps onto my SD card.(it seems as though the SD card is useless on Android)I am using an HTC Desire 601, with Android version 4.2.2. Now my problem is that, I'm having an error with FolderMount because of something to do with external SD card r/w permissions.(no this is not specific to the app, it's a software wide problem, that's why I'm posting here.) So I found a "fix" that involved editing platform.xml and adding a line. However, everytime I try to edit it, either the phone just reboots, or no changes are made. Basically, the system folder is denying me r/w access. In root explorer there is a feature to mount it temporarily as r/w, but then if I reboot my changes are lost. This is a problem which I think is also not allowing me to install Busybox. Please help me with this. Thank you.
Click to expand...
Click to collapse
Stock rom?
Which root app do you use?
LS.xD said:
Stock rom?
Which root app do you use?
Click to expand...
Click to collapse
I'm using the default version of Android that came with my phone, if that's what you mean. And umm what do you mean by which root app did I use?
Jason1712 said:
I'm using the default version of Android that came with my phone, if that's what you mean. And umm what do you mean by which root app did I use?
Click to expand...
Click to collapse
You said you "ROOTED" your phone. That means you have some kind of "SUPERUSER" app installed. I hope so at least
LS.xD said:
You said you "ROOTED" your phone. That means you have some kind of "SUPERUSER" app installed. I hope so at least
Click to expand...
Click to collapse
Oh okay I have the SuperSU app it's SuperSU v1.93 I don't know if it's the latest version. Sorry, I'm new to this rooting stuff. I only got this phone this Monday, and I only got to know about rooting the day after.
Jason1712 said:
Oh okay I have the SuperSU app it's SuperSU v1.93 I don't know if it's the latest version. Sorry, I'm new to this rooting stuff. I only got this phone this Monday, and I only got to know about rooting the day after.
Click to expand...
Click to collapse
Open SuperSU and check if access is granted for "FolderMount"
Do you use free FolderMount? Thats limited to 3links at all.
What type of sd card do you use?
LS.xD said:
Open SuperSU and check if access is granted for "FolderMount"
Do you use free FolderMount? Thats limited to 3links at all.
Click to expand...
Click to collapse
Yes, of course access is granted. I have only tried to create one link so far...so it can't be anything to do with the number of links permitted in FolderMount. I mean, I haven't been able to create a single working link. Precisely, the error I'm getting in FolderMount has something to do with sd card r/w permissions(I've linked a screenshot;maybe you've had this problem before and you solved it?)
The only possible fix I can find is the edit to platform.xml. I've contacted the developer; notice how it says "Attempt to patch my ROM"? Well the developer told me that when the patch is applied and when I reboot, the patch is erased because of the reboot(he said that seems to be the case) so I need to find a way to ensure that it isn't erased. I'm having the same problem here; when I make an edit, it's erased either immediately or after reboot. So that's why I need to find a way to fix this. Thanks, if you have a possible fix.
I've tried using DirectoryBind, but it doesn't work and I hear it's been broken since 4.2. I don't know how to revert back to a previous Android version for my device, so I'm stuck.
Jason1712 said:
Yes, of course access is granted. I have only tried to create one link so far...so it can't be anything to do with the number of links permitted in FolderMount. I mean, I haven't been able to create a single working link. Precisely, the error I'm getting in FolderMount has something to do with sd card r/w permissions(I've linked a screenshot;maybe you've had this problem before and you solved it?)
The only possible fix I can find is the edit to platform.xml. I've contacted the developer; notice how it says "Attempt to patch my ROM"? Well the developer told me that when the patch is applied and when I reboot, the patch is erased because of the reboot(he said that seems to be the case) so I need to find a way to ensure that it isn't erased. I'm having the same problem here; when I make an edit, it's erased either immediately or after reboot. So that's why I need to find a way to fix this. Thanks, if you have a possible fix.
I've tried using DirectoryBind, but it doesn't work and I hear it's been broken since 4.2. I don't know how to revert back to a previous Android version for my device, so I'm stuck.
Click to expand...
Click to collapse
Some files e.g. related to kernel will be generated on every boot. In that case you can't change em permanently. BUT you can try another solution so far Create a ext2/ext4 partition on your external sd and use Link2SD or APP2SD pro
In the superSU setting, try enabling option allow apps requesting root permission at start up(on boot).
Sent from my G610-U00 using xda app-developers app
LS.xD said:
Some files e.g. related to kernel will be generated on every boot. In that case you can't change em permanently. BUT you can try another solution so far Create a ext2/ext4 partition on your external sd and use Link2SD or APP2SD pro
Click to expand...
Click to collapse
Um..how do I do that?
Jason1712 said:
Um..how do I do that?
Click to expand...
Click to collapse
Do you have a custom recovery installed?
LS.xD said:
Do you have a custom recovery installed?
Click to expand...
Click to collapse
Yes.Philz-Touch Modified, Advanced CWM Recovery. At least, that's whats stated in the Desire 601 root guide.
Jason1712 said:
Yes.Philz-Touch Modified, Advanced CWM Recovery. At least, that's whats stated in the Desire 601 root guide.
Click to expand...
Click to collapse
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Your recovery / Rom (Kernel) has to support this feature. I can't find this information. So pls be patient. I'll pm you as soon as i found a safe solution.
LS.xD said:
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Click to expand...
Click to collapse
So I just have to do that? Just boot into recovery, then use the partition sd-card feature in my recovery, and then that's it? My sd card will be partitioned? Ok, then I download..Link2SD?
LS.xD said:
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Your recovery / Rom (Kernel) has to support this feature. I can't find this information. So pls be patient. I'll pm you as soon as i found a safe solution.
Click to expand...
Click to collapse
Oh sorry, I didn't see this post before I posted my reply. OK, thanks a lot.
Ive factory reset several times now, I've reflashed the android l preview image several times, and flashed two 5.0 roms over it even, and i even tried a multiboot with cm11. My device can't take pictures, video, basically anything to do with the camera doesnt work. Pictures seem to take, but don't save. Video or any panorama crashes the camera, and the error logs show something about permission denied to the files they are trying to create. How can i fix this?
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
rootSU said:
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
Click to expand...
Click to collapse
I tried that one, it did nothing and camera still acted up. I've tried every app on the store. Nothing seems to be allowed to write to DCIM, even though I can create files with a normal file manager just fine.
rootSU said:
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
Click to expand...
Click to collapse
I just tried creating a file inside the camera folder inside DCIM and permission was denied. How could I fix that?
dreamwave said:
I tried that one, it did nothing and camera still acted up. I've tried every app on the store. Nothing seems to be allowed to write to DCIM, even though I can create files with a normal file manager just fine.
Click to expand...
Click to collapse
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
rootSU said:
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
Click to expand...
Click to collapse
I can already download stuff. Is it a common problem with L for this to happen? I've looked it up and found little to nothing.
rootSU said:
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
Click to expand...
Click to collapse
I realize I just went full retard thanks to looking in the camera for permission. I had earlier set permissions with chmod from recovery for the DCIM directory to 777, but not the Camera directory within. Thanks for helping, though!
dreamwave said:
I realize I just went full retard thanks to looking in the camera for permission. I had earlier set permissions with chmod from recovery for the DCIM directory to 777, but not the Camera directory within. Thanks for helping, though!
Click to expand...
Click to collapse
One problem I have consistently had however is that my launcher and default camera app are never remembered. How can I fix this?
dreamwave said:
I can already download stuff. Is it a common problem with L for this to happen? I've looked it up and found little to nothing.
Click to expand...
Click to collapse
No it's uncommon. I've only sewn it for people using recovery or adb to push and pull sdcard folders.
Download and flash this zip via recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
and it seems that for any kind of panorama or photosphere it still crashes
they crash with an event trace of java.lang.NullPointerException: attempt to invoke virtual method 'void java.io.FileWriter.close()' on a null object reference
at
com.google.android.apps.lightcycle.panoramamodule.stopcapture(panoramamodule.java:802
etc
etc
etc
Its permissions, we know that. Please flash the fix I posted before anything else.
rootSU said:
Its permissions, we know that. Please flash the fix I posted before anything else.
Click to expand...
Click to collapse
Ok, so pushing it to the sd with adb won't break even more permissions?
dreamwave said:
Ok, so pushing it to the sd with adb won't break even more permissions?
Click to expand...
Click to collapse
Why would you need to do that? You can download it direct to your phone.
rootSU said:
Why would you need to do that? You can download it direct to your phone.
Click to expand...
Click to collapse
ok, I flashed it and my phone is rebooting
dreamwave said:
ok, I flashed it and my phone is rebooting
Click to expand...
Click to collapse
Cross your fingers.
rootSU said:
Why would you need to do that? You can download it direct to your phone.
Click to expand...
Click to collapse
thanks so much, that fixed it completely!
dreamwave said:
thanks so much, that fixed it completely!
Click to expand...
Click to collapse
No problem.
The adb (or TWRP MTP) only seems to break permissions if you're pushing folders. Pishing individual files should be fine.
rootSU said:
Cross your fingers.
Click to expand...
Click to collapse
is this problem new to android l or has it been around a while? I'll also admit I do a lot of adb push/pull/commands and such, and for a lot of the time need to because I only have a wired connection with my computer at school, is there a way to avoid this problem in the future?
dreamwave said:
is this problem new to android l or has it been around a while? I'll also admit I do a lot of adb push/pull/commands and such, and for a lot of the time need to because I only have a wired connection with my computer at school, is there a way to avoid this problem in the future?
Click to expand...
Click to collapse
Its not related to L at all. Files should be fine to push. Its just folders I think that cause the issue.