Database Develop

Permission Denied Error

As of this morning, my kindle fire HD 7" was reset back vanilla launcher and un-rooted.
I have re-rooted but keep getting the error "com.estrong..fs.FileSystemException: Permission Denied" whenever I attempt to move my launcher files to system/app
My file explorer has root privileges and I do have my device rooted but it just kind of stumped me.
Does anyone know of a way around this; Has this happened to anyone else within the last 24 hours?
P.S:
My System Version is 7.4.3
File Explorer: ES File Explorer (With all root options selected)

Anyone have any idea?
I still have no idea what's causing the issue.

evildread said:
Anyone have any idea?
I still have no idea what's causing the issue.
Click to expand...
Click to collapse
which method did you used to root kfhd !??
try to root your kf again if the problem is still unresolved !!

first root with restore and after that root with qemu. it's been my way of doing it trough all the amazon updates. it NEVER failed
if you have problems with superSU, just uninstall it and install superuser from market.

phonexpert_alex said:
first root with restore and after that root with qemu. it's been my way of doing it trough all the amazon updates. it NEVER failed
if you have problems with superSU, just uninstall it and install superuser from market.
Click to expand...
Click to collapse
I feel like such an idiot..
It turned out the system folders weren't mounted.. So I was getting denied root access..
I had gotten the new version of ES File Explorer (Which I'm not used too), which was giving me the problems.. So I Downloaded FX File Explorer and saw that it wasn't mounted and just NOW finally found how to mount with ES...
Sorry for the post, I feel so freaking stupid.. =/

[Q] Problems with CM 10.1 superuser

I have a plain vanilla CM10.1 on my HD+. The included CM File Manager runs fine with root privilege. I've also installed a newer version of Jackpal's Term (terminal emulator) which runs fine as well with root.
However, the current version of ES File Manager will not run with root privilege. When I try to activate this, I just get the message "Sorry, test failed." Interestingly, the app is visible in Settings>Superuser as "allowed", but it still fails to acquire root. (I already uninstalled and reinstalled ES File Manager a couple of times with no success.)
Additionally, another app I tried to install (SambaDroid) gets denied root by the CM Superuser app without me even being able to say yes or no.
So something is not working as it should be...?

Have you tried installing supersu from the market?
Sent from my PG86100 using xda app-developers app

jpisini said:
Have you tried installing supersu from the market?
Click to expand...
Click to collapse
No. I'm not sure whether installing multiple superuser apps is a good idea... I may end up with a system where the two apps slug it out and
I am left without root access. (OK, I do have backups so that wouldn't be a catastrophe.)
Having said that, I would have tried installing another SU if I could get rid of the CM SU in the first place, but these days this thing is baked into the Settings app and I've found no information as to whether (and if so, how) this can be disabled.
Hints anyone?

Seems I am the only one with that specific problem.
The solution (well, not really but probably better than mucking with the CM superuser app): I've removed ES File Manager and installed X-plore File Manager instead. The interface of the latter is not that great but it seems to do most (or all?) of what ES can do (plus it does open password-protected RAR files, a big plus for me). And of course it supports root...
Still I do not understand why ES would not work with the CM superuser but there you go.

ES File Explorer: no prompt, no notifications, no logs, runs as root

SuperSU 2.0.1 (the latest version installed from Google Play) silently grants SuperUser privileges to ES File Explorer.
What's even more worrying is that there's nothing in the logs! And no prompt at all. After rebooting the phone I see a prompt just once, but it never appears again no matter what I do (killing ES File Explorer or/and wiping its cache).
Can you please look into that?
I have a Nexus 5 phone with stock Android 4.4.4 (rooted via TowelRoot).
Edit: There are people who experience the same problem.

http://forum.xda-developers.com/showthread.php?p=55338769
Sent from my SGH-M919 using Tapatalk 2

Can't delete Velvet.apk (Google Now) from Stock ROM

Hello. At first, this problem doesn't exist on compiled AOSP ROM, it exists only on original ROM. I'm rooted and "busyboxed". I can't delete this app nor freeze, just nothing. I remember on N5 it was fine. Any idea?

reas0n said:
Hello. At first, this problem doesn't exist on compiled AOSP ROM, it exists only on original ROM. I'm rooted and "busyboxed". I can't delete this app nor freeze, just nothing. I remember on N5 it was fine. Any idea?
Click to expand...
Click to collapse
have you tried using a root file explorer, like root explorer, to go to its location and delete its apk(then reboot)?

simms22 said:
have you tried using a root file explorer, like root explorer, to go to its location and delete its apk(then reboot)?
Click to expand...
Click to collapse
I tried to delete in Root Explorer, in TWRP, or to turn it off in app settings (and it should work, wtf!). I always got a bootloop after reboot.

http://android.stackexchange.com/questions/131233/remove-google-app-velvet-from-android-marshmallow
Try the advice there. If you don't get a bootloop afterward, you'll know why.

Root /system in Marshmallow

Hi guys.
Currently have MM pre-rooted firmware installed, with TWRP and SuperSu 2.71.
Using ESFile Explorer Pro, I can gain root access to /, /system, but not /system/odex.app or /odex.priv-app or /odex.framework.
Anyone know why, or a work around for this?
Peace.

I would suggest either trying with another application (like Root Explorer) or SLiMM 1.9 (another MM based ROM, which works fantastically well, if you ask me).

Thanks, but no dice with Root Explorer or other apps.

chris5s said:
Thanks, but no dice with Root Explorer or other apps.
Click to expand...
Click to collapse
If you have recovery, Try re-flashing SuperSU.zip and see if the root explorer applications work

Also trried that, but no luck..
Strange I can get root access to /system but some folders within it are excluded.
Thanks.