[G Pad 8.3 Q&A, Help & Troubleshooting] jk8260:
What I did that worked...

Hi Shaun,

OK, since I to have a TWRP backup and this file is a pretty simple xml text file I decided to first make a copy of the file just incase (I copied it to the download folder) and then edit it in place (I saw your issues and wanted to try the direct edit approach). To be clear I have experience in doing this for years in my day job but by no means think this is the safest way, but it is just what did work for me, and you asked me.

So here were my steps that worked for me (at work without tab with me so winging it from my memory).

(note I use both FX and ES File Explorers during this walk through, you probably only need the FX one)

- Copied the platform.xml file to my download folder to save as a backup.

- Then I installed the Fx FileExplorer listed above and then installed the Fx FileExplorer root access add on.

- When I opened the Fx FileExplorer and granted it root access it now had a new folder option something

like '#system ROOT' and I believe it a different color you will see it.

- When I tapped on the folder a scary pop up warned me of the dangers traveling through the file system with root permission.

(right away this made me feel better since I new I really had the right raw access now that I wanted)

- So I navigated to the 'system/etc/permissions' folder and tapped on (or somehow selected to open) the platform.xml file.

At this point a popup asked what I wanted to open it with and I selected 'FX File Editor' and up popped the raw file in the editor.

- I made the change (see above) and then saved the file. I did have to tap a few icons to find the save button but it was not hard to find.

- I do remember not being able to find how to close the editor so I just exited the app and killed it.

- I then went back in with ES file explorer to check if my edit was saved, and the datetime stamp was 1/12/2014 and my edit appeared in the file.

- Just to be sure I compared the file size to the original and it was only a few bytes larger (what I expected), I also compared the permissions listed under details to what the file had before I played with it (I took a digital pic of the file detail screen before editing).

- Then I took a deep breath and shut down and restarted the tab, and it started fine.

- First thing I did was open ES File Explorer and navigate to the SD card and tap the NEW Icon and selected folder and hit Save/OK whatever and bam it worked.

- Next I opened Titaniam BU and selected to backup to the SD and bam it worked, I know have perfect clean access to the SD.

Of course I would never recommend editing live files on any systems (but this seemed pretty straight forward), and after I read your earlier post I thought that maybe something was getting borked by copying in and out so I decided to go off road comando and this time it paid off.

Disclaimer

- backup with TWRP first

- backup the file itself again as well

- I do not recommend editing live files on any systems (but I have and do with xml, ini and text based files often)

- I do not recommend looking directly into the sun

- I do recommend making careful calculated tricky moves to better your life and device

Hope this helps.

---------- Post added at 09:51 AM ---------- Previous post was at 09:33 AM ----------

While I do not doubt that these sandisks have an issue, two of the three sds I have are Sony and are fine in my S4 or my wifes S3 but were locked down in the LG GPE V510. Oddly when running TWRP it could write to them fine just not when boot into KitKat. The platform.xml fix did work for me and all sds are working fine on it now.