2017-06-20, 00:49
(2017-06-20, 00:26)mechaaztlan Wrote:(2017-06-19, 22:51)jocala Wrote:(2017-06-19, 21:50)mechaaztlan Wrote: I don't think there's anything different. I did a factory reset on it and it gives me the same issue. I may have tried to root it once? I'm pretty sure it couldn't be rooted because of it's firmware. Could there be some left over junk on there that would survive a factory reset?
That's possible. A factory reset doesn't nuke everything. You can try to using the adb shell button then at the $ prompt paste the command:Code:/data/local/tmp/adblink/which su
This will show you if there's an su binary on the stick.
The upcoming version has the ability to turn off root detection, hoping for a mid-July release.
I get back
/data/local/tmp/adblink/which su
/system/bin/su
Does that mean there's something there?
You may have used Kingroot? The which command tells us that a su binary (required by root) lives at /system/bin/ on your stick and a stock Fire TV stick does not have su installed. adblink's file manager is attempting to use this su, and it's [the su] not behaving as expected and the file manager chokes. I've seen this happen once, with a pre-rooted generic Amlogic S905. Installing supersu fixed things on that system, it may fix yours. It's worth a try.