I already have read multiple threads about this issue, however, this is sort of a more specific issue I ran into. The device I'm using is a MT6582 Karbonn Titanium S25 (sold under a different name in my country) with a pretty recent build of the software which is a completely stock Mediatek Android 4.4 build.
The issue here is simple enough - root can't access the external sdcard (sdcard0), but the user can oddly enough. This causes file operations to goof up and that's really annoying me. I can't copy any file from an external sdcard, but instead, I have to copy it to the internal one first and then wherever else on the phone.
I did do some crazy things which caused me to lose the original stock system image, but I still had the files of it so I had to create an updater script and a flashable ZIP of it, though, I don't believe that's what's causing the issue here, since I had an older build running which has the same issue when rooted. Unfortunately, this build they flashed on my phone (in the store lol, with SP flash tool of a newer build) seems private to them. I asked them specifically if it was available for download anywhere and they said no.
Using the utilities provided on the Play Store did not fix the issue for me.
On another note, BBS and V4A seem to have been affected by a similar issue as well. BBS can't read Kernel Wakelocks and V4A can't install its driver for some reason.
The issue here is simple enough - root can't access the external sdcard (sdcard0), but the user can oddly enough. This causes file operations to goof up and that's really annoying me. I can't copy any file from an external sdcard, but instead, I have to copy it to the internal one first and then wherever else on the phone.
I did do some crazy things which caused me to lose the original stock system image, but I still had the files of it so I had to create an updater script and a flashable ZIP of it, though, I don't believe that's what's causing the issue here, since I had an older build running which has the same issue when rooted. Unfortunately, this build they flashed on my phone (in the store lol, with SP flash tool of a newer build) seems private to them. I asked them specifically if it was available for download anywhere and they said no.
Using the utilities provided on the Play Store did not fix the issue for me.
On another note, BBS and V4A seem to have been affected by a similar issue as well. BBS can't read Kernel Wakelocks and V4A can't install its driver for some reason.
Just installed TWO Dell UP3214Q on a late 15" 2013 rMBP with discrete Nvidia GeForce 650m.
RépondreSupprimer