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.
YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. WE ARE NOT RESPONSIBLE FOR YOUR DEVICE. FLASH AT YOUR OWN RISK.
This will enable Native Tether for Build 183.46.15. Shout out goes to iKrYpToNite for his work with this.
Prerequisites:
Droid RAZR/RAZR MAXX HD Rooted or unlocked on 183.46.15
METHOD 1: TWRP INSTALL
1) Download the package below labeled "183.46.15_tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
METHOD 2: MANUAL INSTALL
1) Download the package below labeled "183.46.15_tether_manual".
2) Download root browser by Jrummy from the play store
3) Navigate to System/Priv-App and rename VZWEntitlementservice.apk to VzwEntitlementservice.apk.bak.
4) Navigate to System and rename the build.prop to build.prop.bak
5) Place the package on the root of your sd card and extract the build.prop file within the folder.
6) Navigate to system and Copy and paste the new file.
7) Set permissions for the file to
Owner: Read/Write
Group: Read
Others: Read
This should show (rw-r--r--)
8) Reboot. Verify tether works
9) Profit.
REVERTING
METHOD 1:
If installed in twrp, download the package below labeled 183.46.15_tether_revert. Flash in Twrp, reboot, verify subscription check re-enabled.
METHOD 2:
If manually installed, simply delete the build.prop you installed, remove the .bak extension from the original build.prop, verify permissions, reboot.
If you enjoyed this, consider donating! I do appreciate it.
Works Great on Razr M EXCEPT!
Works greeat on .15 and RazrM..however we will need the existing Razr M build prop done as the icons get HUGE
Rick
I tried the manual version, but no luck on my RAZR MAXX HD with a stock ROM.
After rebooting, I initiate the 'Mobile Hotspot' and the text goes grey for a bit and then goes back to normal without activating the hotspot.
UPDATE: I took the 'build.prop' from the '183.46.15_xt926_tether_twrpinstall.zip' and used that instead of the one in the '183.46.15_xt926_tether_manual.zip.zip' and it worked.
UPDATE2: I think (and I could be way off here) the one in the manual version doesn't work because it is missing the line:
net.tethering.noprovisioning=true
Does that sound about right?
2useless said:
I tried the manual version, but no luck on my RAZR MAXX HD with a stock ROM.
After rebooting, I initiate the 'Mobile Hotspot' and the text goes grey for a bit and then goes back to normal without activating the hotspot.
UPDATE: I took the 'build.prop' from the '183.46.15_xt926_tether_twrpinstall.zip' and used that instead of the one in the '183.46.15_xt926_tether_manual.zip.zip' and it worked.
UPDATE2: I think (and I could be way off here) the one in the manual version doesn't work because it is missing the line:
net.tethering.noprovisioning=true
Does that sound about right?
Click to expand...
Click to collapse
Yes you are correct. Don't know what happen there. Fixed the zip for the manual install and reuploaded. Thanks
blackice000 said:
Works greeat on .15 and RazrM..however we will need the existing Razr M build prop done as the icons get HUGE
Rick
Click to expand...
Click to collapse
The Razr M version is linked below
http://forum.xda-developers.com/showthread.php?t=2880591
Just wanted to say, this has been working like a champ until this afternoon. I ended up installing an Xposed module to get tether back, but the only change I had made was trying to install Nova (launcher) and, like an idiot, Firefox again. XPrivacy usually stops anything funky from happening, but I had quite a scare when I'd lost native tether for a bit.
Anyone else? —Anyone else even using Razr HD anymore? I got my latest new replacement from Asurion earlier this year, and it's been smooth sailing until today. I don't take OTAs (obviously: my build is ancient), but not sure why this exploit stopped working on my phone so suddenly.
Oh, still appreciate the exploit! Danke! :good:
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.
Hi Community, does anyone maybe know, where the script for "no startup data leak" is stored?
Ive checked the AFWall folders but can't find it.
I'm asking cause the option for it in AFWall is greyed out. I'm using Renovate with init.d support.
Thanks for any suggestions
Wrong thread - delete pls
Hello. I have an carrier unlocked S7 G930U (G930UUEU4BQE2) with Nougat 7.0. I tried to downgrade to 6.0, but I had a few issues. One being I could not get root to install properly and when I did it was lost after a few minutes or if I recall, after rebooting. Also no Wifi passwords would be saved and Wifi would keep shutting down. Is there a fix, or a specific version of 6.0 form a specific date or carrier I should use if I choose to try and downgrade again? Not sure if I did anything wrong or if it's just a bug. Any suggestions, help or advice much appreciated.
I assume you used Odin, did you flash all 4 firmware files (AP, BL, CP, CSC)?
Beanvee7 said:
I assume you used Odin, did you flash all 4 firmware files (AP, BL, CP, CSC)?
Click to expand...
Click to collapse
Indeed I did. I tried several actually. I read somewhere that flashing sometimes causes the radio to fail. If so, I tried flashing a radio from another provider, I forget which one, with no success. As for the root, I think I figured out what I did wrong there.
Just went through the same thing...here is the resolution....from this thread...
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
From the Recommended next step section.
Fix an issue with the Wi-Fi not saving passwords after reboots by editing the build.prop and setting 'ro.securestorage.support' to 'false'. I used JRummy's BuildProp editor:
https://play.google.com/store/apps/d...ld.prop.editor
redhawk0 said:
Just went through the same thing...here is the resolution....from this thread...
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
From the Recommended next step section.
Fix an issue with the Wi-Fi not saving passwords after reboots by editing the build.prop and setting 'ro.securestorage.support' to 'false'. I used JRummy's BuildProp editor:
https://play.google.com/store/apps/d...ld.prop.editor
Click to expand...
Click to collapse
You beat me to it! lol. I was looking for that link and had just found it. Works like a charm. WiFi saves !
Here's my settlement after 24 hours of rooting, debloating, tweaking and optimizing my G930U
- Flashed fresh, stock firmware: Marshmallow 6.0.1, first release, G930UUEU4API3
- Was FINALLY able to gain and hold root by following the steps located in the first section of this thread.
- After that I installed an UPDATED version of FlashFire via ADB.
- I opened FlashFire. Until you disable KNOX, SuperSU will be VERY slow to prompt you with the pop-up to grant root access to FlashFire (maybe a minute or so). Once access is granted, you can debloat and disable KNOX. This is the only root required app I installed at this point.
- In section two of the same thread, I downloaded and added the second .zip file, S7_or_S7Edge_Fixes_Debloater_V15.zip to internal storage (sdcard) and flashed it using FlashFire. I also downloaded this .zip, added it to internal storage and flashed it. I also went here and did the same with this .zip. (KNOX is disabled in the first flash so at this point SuperSU will function normally).
- IF YOU DO NOT DISABLE KNOX COMPLETELY YOU WILL LOSE ROOT!! Flash ALL 3 .zips to ensure KNOX is disabled!!
- I then disabled any other apps and or services I deemed fit and that suit my needs. If anyone wants me to I can compile a list of what I left installed.
- Installed Xposed following the 3rd step in the thread I linked twice already.
- Downloaded and installed HEBF - Battery Saver & Optimizer, selected a medium profile for Battery and medium for performance.
The difference is almost instant. On top of all the bloat, I can't believe how much battery this drains because of it. The build.prop edit is what got me to stick with 6.0 if it killed me or this phone while trying.
I don't like Xprivacy, so went the old route and got AppOps to work from the play store. That solves a lot of permission issues I had with various apps.
With the new found battery life I installed two bad ass wallpaper apps. (I have a thing for wall papers lol). By the time I'm really done, Samsung will barely exist on this phone.