OK so as you have noticed kit kat does NOT allow third party apps to write to the SD card, this is stupid, but lucky for us we have a fix IF you are rooted
we have 2 solutions
1) using root explorer or something similar go to
Quote:
/system/etc/permissions/platform.xml
and enter the permission that i have circled in red below (see attached) then it will work. Enter it so it looks EXACTALLY like it does below
2) the other option that MAY work is to go to the play store and download SDFix, that does the same thing (however myself and a few others are reporting that it isnt working as it is written)
big thanks to Mr Sam Epic for showing the fix, which came from Unknown Force in a SGS4 forum
****edit 4/19
had a few reports of SDFix not working, it didnt for me, i thought it was just a random error, what i did to fix it was to go into platform.xml and manually edit the permission so it looks exactally like the image below, i put in the extra return after the permission, there is not a logical reason why this fixed it, but it did
original thread here:
http://forum.xda-developers.com/showthread.php?p=51861458
Seems like it worked, thanks.
I gave this a try in Root Explorer. I have gone over it many times and I did everything correctly but now Titanium won't launch, Weatherbug won't load, and GAPPS fails everytime. I am using Odin to go back to stock now-- will try the other method.
After write to extsd is enabled, I would strongly suggest the Xposed Framework module Downloads2SD. It allows you to change default directories to the extsd. It seems to work for Chrome downloads as well.
Here's a weird one... I edited the file exactly the way it should be, worked fine... played with a few things, edited build prop screwing around having fun. Boot looped because oops. No problem, Odin to stock. Fresh stock build.
Rooted, Edited the platform.xml again exactly the way required, reboot. Even system apps won't write to SD. Couldn't even install XDA app lol
Odin again, root, edit the xml exactly the depicted way again. Still nothing can write to SD. Wtf.
Anyone have a stock or working platform.xml I can peek at? Something is screwy here lol
I have all the source on my Linux box but I'm nowhere near it, unfortunately.
Nsane457 said:
After write to extsd is enabled, I would strongly suggest the Xposed Framework module Downloads2SD. It allows you to change default directories to the extsd. It seems to work for Chrome downloads as well.
Click to expand...
Click to collapse
I agree, I had issues with my S4 after moving to KK also with my new S5. And now with those of us on Verizon, we are lucky enough to have root Thanks to exposed you can start moving files around like before. Its just amazing how controlling companies feel they need to be.... Oh well, thanks for the Root Geohot, and Xposed rovo89 & Tungstwenty!
Excellent! This worked on my N900V with 4.4.2 and root! (fix #1)
I thought my old file browser just wasn't reading root correctly, but with this, it's back to normal/pre OTA function. Thanks again!
Could you please add to the instructions, for option 1 at least, to double-check the permissions on the file? (They should be 644 and root/root). Was helping my brother and just went through lots of problems (everything crashing) and turns out the editor changed the permissions (found the answer on another site where someone described the same symptoms). I'm also wondering whether the permissions also have something to do with why it seems to sometimes not work for people...
Just wanted to chime in and say that SDFix worked flawlessly the first time on my rooted SM-G900V.
All I did was root and then run this utility, installed nothing else at any point, not even SuperSU.
NextApp SDFix works great with my stock rooted SG5. Verified with ttorrent.
One thing I have to say about this is when I did it i had issues with the camera app saving to extsd. So I changed it back after a lot of work on it.
Confirmed working. Thanks for the mod advice. Just make sure to make the edits exactly as shown in the image.
I tried the SDfix apk and it worked only on the root of the SD card. Any file structure past the root did not have rw access.
Now that I can write to my sd, I am noticing very poor speeds. We are talking like less that 1MB/s. I tested it with both large iso files and a bunch of small 30-300 kb files. Both tests are very slow. Any ideas on where to look to fix that?
Sent from my SM-G900V using XDA Premium HD app
evilbeef54 said:
OK so as you have noticed kit kat does NOT allow third party apps to write to the SD card, this is stupid, but lucky for us we have a fix IF you are rooted
we have 2 solutions
1) using root explorer or something similar go to
Quote:
/system/etc/permissions/platform.xml
and enter the permission that i have circled in red below (see attached) then it will work. Enter it so it looks EXACTALLY like it does below
2) the other option that MAY work is to go to the play store and download SDFix, that does the same thing (however myself and a few others are reporting that it isnt working as it is written)
big thanks to Mr Sam Epic for showing the fix, which came from Unknown Force in a SGS4 forum
****edit 4/19
had a few reports of SDFix not working, it didnt for me, i thought it was just a random error, what i did to fix it was to go into platform.xml and manually edit the permission so it looks exactally like the image below, i put in the extra return after the permission, there is not a logical reason why this fixed it, but it did
original thread here:
http://forum.xda-developers.com/showthread.php?p=51861458
Click to expand...
Click to collapse
So I tried this and my ability to use the TextSecure app broke. I reverted back to the auto-created backup (thank you Root Explorer) of my platform.xml file, and it restored TextSecure functionality after a reboot. However, I have been unable to turn Bluetooth on since doing this. The only other change was updating to the latest release of Busybox this morning, which apparently was just released. Could this platform.xml file triggered some other actions upon rebooting that would cause Bluetooth problems?
evilbeef54 said:
OK so as you have noticed kit kat does NOT allow third party apps to write to the SD card, this is stupid, but lucky for us we have a fix IF you are rooted
we have 2 solutions
1) using root explorer or something similar go to
Quote:
/system/etc/permissions/platform.xml
and enter the permission that i have circled in red below (see attached) then it will work. Enter it so it looks EXACTALLY like it does below
2) the other option that MAY work is to go to the play store and download SDFix, that does the same thing (however myself and a few others are reporting that it isnt working as it is written)
big thanks to Mr Sam Epic for showing the fix, which came from Unknown Force in a SGS4 forum
****edit 4/19
had a few reports of SDFix not working, it didnt for me, i thought it was just a random error, what i did to fix it was to go into platform.xml and manually edit the permission so it looks exactally like the image below, i put in the extra return after the permission, there is not a logical reason why this fixed it, but it did
original thread here:
http://forum.xda-developers.com/showthread.php?p=51861458
Click to expand...
Click to collapse
You can also just use Folder Mount.apk and in the beginning while setting it up iT patches the external microsd and then anything and everything can read and write to the external micro sd. HIT THANKS IF YOU DIDNT ALREADY KNOW THIS..
Thank you very much, evilbeef54! Lol, funny username, by the way. The first solution (editing platform.xml) did the trick for my Xperia C4 (E5303) running Android Version 5.1, Build number 27.2.A.0.155. I edited the file using Root Browser then RB Text Editor, and after a reboot Titanium Backup finally allowed me to save my backups to my external SD Card.
xperia_c4_hater said:
Thank you very much, evilbeef54! Lol, funny username, by the way. The first solution (editing platform.xml) did the trick for my Xperia C4 (E5303) running Android Version 5.1, Build number 27.2.A.0.155. I edited the file using Root Browser then RB Text Editor, and after a reboot Titanium Backup finally allowed me to save my backups to my external SD Card.
Click to expand...
Click to collapse
way to necro a thread.
Seem like micky insecure kernel does make the root work great. But just wondering is there anyone also find the wifi wont auto connect anymore? I have to manually add them...
If you mean that the passwords are not saved the fix is in the kernel thread.
In build.prop change ro.securestorage from true to false.
Thank you ..it works. One more thing does anyone know how to disable that security notification after rooting other than disabling the whole smart manager? I try the notification setting unfortunately the smart manage do not have the block option.
Update: i think i found a soltion to this annoying security notification. Use titanium back up or root uninstaller to freeze security log agent.
Hey guys, I have this funny problem where when I install xposed, I lose tethering (both wi-fi and the rest) from the settings screen in Touchwiz. At one point, I knew the fix, which was to go and delete some system/xposed file somewhere and then reboot, but I can't remember what it was...does anyone know?
Thanks!
Hey so I think I figured it out...the file to delete (or rename) is feature.xml with all the csc values.
Hi everyone thanks for the reply in advance i searched the forum for someone with similar question and found none. Maybe its because no one is as dumb as I. Anyway from the title you might have understood my question.
I wanted to install App Ops in my Mi11x running MIUI 12.5 (Android 11) using shizuku. But shizuku says the permission on my adb is limited due to my manufacturer and thus cant enable application management to give permission to app ops. I gave shizuku permission to app ops through the system permission manager but that doesnt seem to work. Disabled miui optimization too and still doesnt work. The shizuku app sends me to this link : https://shizuku.rikka.app/guide/setup/
In the guide under miui in there it redirects me to 2 pages in chinese i tried translating with google translate but it just says what i did, that is in the github link. the other i didnt really understand much. Can anyone help me and just give me a guide or something on what i should do?
any help is appreciated. Thanks
Have a good day
Enable developer options, wireless debugging AND USB debugging, pair shizuku, start shizuku, go to App Ops app settings and allow usage of shizuku (from Apps> App Ops> permissions> additional permissions> allow shizuku access) and done. It's because MIUI breaks the dialogue for shizuku app permission
Hi!
Recently, I have been unable to open the Dreame Home App. My device has been rooted. When opening the application, an error message appears (presumably in Chinese) which says
"检测到该应用在root环境中运行".
All I can read is... "root"
With Magisk, I have ensured that the app no longer sees that the device is rooted. The app now opens initially without an error message. However, it closes automatically after a few seconds, without an error message.
Does anyone here have an idea what the cause might be and how I can get a handle on this problem?
[Mods: I have deleted my other post, please leave this here.]
The error message you mentioned, "检测到该应用在root环境中运行," translates to "Detected that the app is running in a root environment" in English. The Dreame Home App might be using advanced root detection methods that can bypass standard root-hiding techniques. It's possible that the app has implemented additional checks beyond just looking for the presence of root files or system modifications.
If possible, try disabling root access temporarily or unrooting your device entirely. This will help determine if the app's behavior is directly related to the root status. Also, you can try other root-hiding modules.
matthewJ32 said:
Also, you can try other root-hiding modules.
Click to expand...
Click to collapse
Thanks for your tips and ideas. Which other root hiding modules are you referring to?
niko26 said:
Thanks for your tips and ideas. Which other root hiding modules are you referring to?
Click to expand...
Click to collapse
I also used Magisk, but I know that there are modules like "Hide My Root" and "RootCloak". I can't guarantee success, but you can try.