Develop Bugs

[Q] Super Repo is empty XBMC !

I have tried everything from factory reset to reinstalling xbmc for ouya 12.3.2 or spmc version but I can't get the super repo to work again. I should of never tried to install SPMC by uninstalling the ouya version which was working fine but I wanted to give it a try bcuz it was newer version. How do I delete the file addons15.db on fire tv to get the super repo to work, is that possible with no root? Help !

batcave said:
I have tried everything from factory reset to reinstalling xbmc for ouya 12.3.2 or spmc version but I can't get the super repo to work again. I should of never tried to install SPMC by uninstalling the ouya version which was working fine but I wanted to give it a try bcuz it was newer version. How do I delete the file addons15.db on fire tv to get the super repo to work, is that possible with no root? Help !
Click to expand...
Click to collapse
Have you tried to add source manually using superrepo zip?

adfurgerson said:
Have you tried to add source manually using superrepo zip?
Click to expand...
Click to collapse
sorry but how do you do that?
I have installed some channels like 1channel, icefilms from Fusion repo, but need others like mashup, simply movies...etc but can't get super repo to work.

batcave said:
sorry but how do you do that?
I have installed some channels like 1channel, icefilms from Fusion repo, but need others like mashup, simply movies...etc but can't get super repo to work.
Click to expand...
Click to collapse
Disclaimer.... I don't own FTV and only have a basic knowledge of xbmc.
1. You will need to download or copy the zip into FTV.
2. Go to settings-file system-add source( on phone this requires long click to bring up menu, with keyboard and mouse try hovering over it and pressing "c" on keyboard)-browse.
3. Select an option such as root files to beginb looking for zip, once you find and select it the add one should show.
Side note... Other sources install similarly except you enter an http address into box rather than selecting browse.

adfurgerson said:
Disclaimer.... I don't own FTV and only have a basic knowledge of xbmc.
1. You will need to download or copy the zip into FTV.
2. Go to settings-file system-add source( on phone this requires long click to bring up menu, with keyboard and mouse try hovering over it and pressing "c" on keyboard)-browse.
3. Select an option such as root files to beginb looking for zip, once you find and select it the add one should show.
Side note... Other sources install similarly except you enter an http address into box rather than selecting browse.
Click to expand...
Click to collapse
I don't think that's possible with Fire tv as its not rooted to install channels from zip files like that bcuz there is no way to use fire tv with usb drive with zip files loaded to manually install channels.

batcave said:
I don't think that's possible with Fire tv as its not rooted to install channels from zip files like that bcuz there is no way to use fire tv with usb drive with zip files loaded to manually install channels.
Click to expand...
Click to collapse
Can you download the zip from web through browser? How are you installing apk's?

adfurgerson said:
Can you download the zip from web through browser? How are you installing apk's?
Click to expand...
Click to collapse
I side load them using ADB, I don't think I can download anything using even a browser "unknown source install/download" not allowed as far as I know on Fire TV not until its rooted then we have full control. But I will give it try using fireox browser.

batcave said:
I side load them using ADB, I don't think I can download anything using even a browser "unknown source install/download" not allowed as far as I know on Fire TV not until its rooted then we have full control. But I will give it try using fireox browser.
Click to expand...
Click to collapse
Can files be pushed to it via adb? Anyways check for a message in a bit I will send PM.
Edit.... I gave you the wrong instructions for zip. Sorry was going from memory.
Correct way- system-add ons-install from zip file.

adfurgerson said:
Have you tried to add source manually using superrepo zip?
Click to expand...
Click to collapse
Just install it like you did Fusion. Go to Settings > File Manager > add source, and them enter http://srp.nu/ for the address of the SuperRepo and on the second menu "Name for this Media"whatever name you want to give to the source e.g. SuperRepo.
You can put this url in your browser to verify that the 3 repo folders are not empty.

Thanks u very much it works now !

Can't reinstall Kodi after uninstalling!

I tried to update from kodi 14.1 to 14.2, but I was getting an error that the signature didn't match. So I uninstalled the version of kodi that I had, but now when I try and install the newest one and even the old one, I get an error that just says "app not installed". I used es file manager to try and install. As well as adbfire. When I try and install with es file manager at thinks I still have it installed, and says the old version is version 0 (null).
Can any help with this? I'm stumped!
I'm using Fire tv Pre-Rooted 51.1.5.0, updated from pre-rooted 5.1.1.4.1 which I installed the last version of kodi on.

Thats strange. Was about to insta;; 51.1.5.0 myself.. now would wait for some more updates.
try clearing the cache or data from CWM.. might work ( i am absolutely not sure about this, works with other android device though)

I decided to do a factory reset and reinstall the rom, and just reinstalled everything back on. Seems ok now.

I had the same problem.
I ended up moving the org.xbmc.kodi directory, uninstalling completely, installing 14.2 and letting it boot up fully, then moving the org.xbmc.kodi directory back.

Play Store - full howto

Here is an instruction how to install Play Store (and Play Services) on Chinese version of Nokia N1
DISCLAIMER: you're doing it on your own risk, it can probably even eat your kitten
Credits should go to rumambo who has described everything in this thread.
Original credits from rumambo:
Thanks a lot sadfrog_lin for right link
Great Thanks social-design-concepts for Tools and working solution !!!
This was successfully done by me on A5CN507 build. IMO it should work the same good on other versions of Lollipop, but I cannot promise anything.
Prerequisites
I assume that you have Intel Drivers up and running http://opensource.dell.com/releases...ition/FlashTool/IntelAndroidDrvSetup1.5.0.exe
I assume that you have adb/fastboot up and running http://forum.xda-developers.com/showthread.php?t=2317790
I assume that you have usb debugging enabled
I assume that yu have a basic knowledge how to use these tools
Installing GApps
Download GApps from this thread. I have used Nano version for Android 5.x, direct link here.
Copy it to your sdcard (any method is fine, but adb will do: adb push <filename> /sdcard/).
Download and extract IntelAndroid-FBRL-05-16-2015.7z.
Connect N1 via USB and run launcher.bat
Type ACCEPT (all capital) and select T4 method.
N1 should reboot and do a lot of things, then you should end up in temporary CWM Recovery session.
Choose install zip (volume up/down + power to select) and find and select the previously uploaded file.
After it finish reboot the tablet
Final fixes
After reboot you should have initial selection of Google Apps (including Play Store) installed. However Play Music will crash on start and GMail won't work (Play Services crashes). The reason for that is that GApps package is probably not fully prepared for x86 - but now you can simply fix it.
Go to ApkMirror and install Google Play services with -470 suffix, it is Lollipop x86 version (on the time of writing this the newest version was here ). Now both Play Music and GMail should work correctly.
An another issue is that Play Store reporting some apps (like Chrome, Google Maps, Google Earth, Chromecast, etc) as incompatible with the device. It probably could be fixed by hacking build.prop, however I haven't had time for it yet. The easiest method is to download them from ApkMirror and side install. Drawback is that you won't get autoupdates for them.
Enjoy!

reserved
reserved for a future use

For information the next update fails with this log...
I:verify_file returned 0
Installing update...
Verifying current system...failed to stat "/system/app/QuickSearchBox/QuickSearchBox.apk": No such file or directory
file "/system/app/QuickSearchBox/QuickSearchBox.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
"/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
E:Error in /cache/A5CN51C_update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse

This really works! Thanks a lot.
After the installation, a few days later I found out that there was an update for N1. I could not make the update successfully. Probably the GAPP issue. So in the end, we still need the Taiwan ROM so far. So that the system update can also be made.

I installed GAPPS, but disabled root(in SuperSU's settings). I can run the OTA update (A5CN51C) successfully.
After the update, "google service is stopped" appears again. I think re-flush GAPPS and SuperSU is needed.

bricked
Hi Guys,
after the issue with the update I started replacing new files with the originals from the previous update. I've checked md5 of every file I used and compared it with update script from the new update - so I'm sure every file was correct. Actually everything was working fine with these original files.
However after the update I got a boot-loop. If I remember correctly it was something abt OpenGL in logcat. I was not able to run recovery by pressing volume up and power, but since adb was working I did it via adb. I came with an idea to clear user data. That was mistake!
Now I still have the boot-loop but developer mode was disabled by cleaning the data. My plan is to reflash with A5CN507 which contains a full system partition image. To do so I need to boot into recovery or download mode.
Do you guys have any ideas how to boot into recovery or download mode if volume up (and down) doesn't work?
Thanks in advance.

Can confirm the boot loop. I was able to get into the CMW session again and tried to restore the backup I made before installing the gapps but CMW got stuck while restoring the system partition.
The device is now stuck in the "Powerd by Android" screen, any help is warmly welcome

Can't root by the method after update to latest 5.1.1 firmware. Pls update the method

After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?

Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
Your tablet bootloader is locked by the update. I've not found any ways to unlock it and install google play.

same here 5.1.1 messed everything up
Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
same here - so I thought I redo the whole thing with Gapps for 5.1.1, but now Fastboot Tethered Recovery Launcher doesn't recongnize my N1 anymore. Can anybody help? Thanks in advance

Any chance that the following common command work ?
Code:
fastboot oem unlock

jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
It's used to make your device unlocked, but only limited to some devices.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225

jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you,
I tried that, it didn't work - it says "waiting for device", but it waits forever. As to the Fastboot Tethered recovery launcher, this time I used the one from Jul, 27, before I had an earlier version. Could it be that the older version would work, but not the latest one? It does recognize my device, but it says unauthorized, although it OEM-unlocked and USB debugging is authorized. Thanks for any help.

and that's the end of it, good night N1
Since my N1 is still bricked, hung halfway through bootloading, I talked to an Android-Repair-shop. They said it cannot be unbricked, I would need a new motherboard... but motherboards for the N1 are not available.
Does anyone hv better news?

Hi,
so I came back to the problem today - and I managed to unbrick my device. Somehow (vol-up + power) I managed to enter fastboot. Then I rebooted into recovery and sideloaded a full update.zip with 701.
Now I'm trying to change Chinese version to Taiwanese one.

my nokia n1 stuck
my Nokia n1 stuck at boot screen i lost my recovery too my tablet only open at fastboot mode.Pls HELP
i need boot.img and recovery.img for NOKIA N1(A5CNS1C)

Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19

sasha2910 said:
Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19
Click to expand...
Click to collapse
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...

LineArc said:
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...
Click to expand...
Click to collapse
Can't wait for that! :good::good::good::good::good::good:

Need Netflix apk

For some reason the Netflix apk on Amazon won't download to my firetv. Can someone post a link to v 1.1.4 build 145. Someone linked it in another post but it won't install. Thanks.

Hi,
Can you test this link https://1fichier.com/?aqtiil17vx ?

Belegkarnil said:
Hi,
Can you test this link https://1fichier.com/?aqtiil17vx ?
Click to expand...
Click to collapse
I tried it but has an installation error. It's the same file I found on another post. Could someone please post the file from their FTV. Really appreciate it.

This file comes from my Fire TV. Are you sure that you do not have any problem with your Fire TV ?
Can you sideload other apps?
Did you tried to uninstall the Netflix app?
How do you proceed (command line or with a software)?

Belegkarnil said:
This file comes from my Fire TV. Are you sure that you do not have any problem with your Fire TV ?
Can you sideload other apps?
Did you tried to uninstall the Netflix app?
How do you proceed (command line or with a software)?
Click to expand...
Click to collapse
Discovered it's not your file. I loaded on my android phone and it installed. It's an issue with my FTV. Thanks for your help.

Es File Explorer issue

I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?

The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.

deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.

Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk

i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox

I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.

@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??

Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.

Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?

d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.

Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps

phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?

phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.

Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"

Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.