Related
[SOLVED, see below].
I've also attached the Su flashable zip to this post, as linked below
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I recently rooted my Desire using unrevoked 3.2.1 Basically, no problems so far.
However, when I have tried to run a few Apps that require ROOT access, the Superuser pop-up screen shows, EVERY TIME.
I have clicked Allow, and made sure to check "Remember", but it comes back every time for the same Apps.
I have double-checked that the Apps requesting Superuser permissions are indeed in the Superuser.apk list for Allow. They are, little green dot and all, but it doesn't seem to matter.
I tried a Batch routine in Titanium Backup, and I had to click that damn Allow button like 150 times!
Does anyone have any idea what's going here? Anyone experienced the same thing?
I wonder if it is related to what mortenmhp mentioned over in this post (post 3, "Cant remove Stock apps? Root Explorer and Unrevoked3"; sorry, I can't link yet)...
the fact that unrevoked3 still does not achieve S-OFF HBOOT and thus doesn't r/w to /system.
Btw. the thread mentioned:
http://forum.xda-developers.com/showthread.php?p=8324672#post8324672
Your problem should not have to do with this though.
The superuser app stores it's list on the data partition, and it should be able to grant su access to anything apart from rw to the protected partitions.
First off:
- Does it happen to all apps requesting su?
- Which version of superuser are you currently using?
- How did you get it? Like was it included in a rom or did you install it by flashing superuser only?
- If included in a rom, which?
And finally. You should start by trying to clear the data associated with the superuser app:
"settings -> applications -> application list* -> Superuser -> clear data button"
*I dont remember the exact name, and the charger for my desire is gone for now
If it does not work, you should also try to do a nandroid backup and a factory reset by wiping the data partition to see, if it doesn't fix it.
Thanks for your response, let me see if I can fill in some of the details:
Yes, it happens AFAIK for ALL Apps requesting Superuser access
Version: Superuser v2.3.6.1 - Added c...
Database version 5
(From the info at the bottom of the Superuser>Settings menu)
IIRC, I may have installed the App myself from the Market...? Is that even possible? Honestly, I may have jumped ahead of my knowledge in this one area. But I'm certain it wasn't from any flashing, unless unrevoked adds the App itself.
ROM, Froyo w/ HTC OTA Sept. update
I rooted with unrevoked3.2.1, but haven't flashed anything
(other than the Clockwork Mod as part of unrevoked, and, the ?re-flash? of Clockwork via ROM Manager)
The most noticeable example of this problem is Titanium Backup; I have to click Allow 14 times each time I open the App. And it is clearly listed in the Superuser List, with a green dot.
UPDATE: It is definitely possible to install this App directly from the Market, as I just re-did it. Then I Rebooted, but it all made no difference, still have 14 Allows in order to launch Titanium Backup
Results
Alright, I tried to "Clear Data", and then I did a reboot for good measure. It did NOT work.
The Superuser list was blank, but as soon as I started Titanium, I had to do the same 14 Allows. The Titanium>Log clearly shows each of them, but it's like the fact that the setting is "Remembered" doesn't have any effect.
I guess I can try the Nandroid back-up/wipe, but that just seems to be in the "format and reinstall Windows" family of solutions (no offense).
Other observation
Here's something else I noticed, may or may not be related.
I have Spare Parts installed, and I was testing the different settings.
First, Reboot/Recovery options ask for Superuser access, but then nothing happens, it just returns to the Spare Parts menu.
I'm interested in "upgrading" my boot animation (I have another thread about that), so I also tried the LeoFroyo Addon of Bootanimation>LeoFroYo BIOS
It Requested Superuser access, delayed while "Working...", and then asked to Reboot. When I clicked Yes, nothing. Just went back to the Spare Parts menu. When I rebooted manually, the stock HTC animation is still what I got.
Relaunching Spare Parts confirmed that the bootanimation setting was still on the upgrade, it apparently just didn't work.
The reason I mention these things is because I wonder if possibly I haven't achieved all the ROOT access that maybe I should have???
Any other thoughts? I'm not sure what else to try, but I can provide any other details that would be useful.
Maybe I'm just fighting a pointless losing battle on this, since I plan to flash to Cyanogen anyway. But it just find it irksome that I can't find a solution to a relatively straightforward issue.
It is because you cannot just install the superuser app from the market, because it needs root in the first place. This might just be your problem. I cant find the update.zip only including superuser right now, so if you want cm anyway, I would just go for it. Otherwise you will have to search for a zip file only including the superuser files or another rom with it included.
edit: and sorry for not replying but i have school as well
edit 2: This should be the zip file to flash to get superuser only hope you can get it to work.
Success
Yessir! That did it.
I think you're right. Don't know what I read to carelessly make me think I could just download Superuser from the Market. Actually, I'm not even too sure why its on there, since it CANNOT work if you install it that way.
I guess when I installed Superuser to grant ROOT permissions, I didn't have ROOT permissions. So, Superuser could grant other Apps ROOT (which did work), but it didn't have ROOT itself to store the Allow list. How ironic.
When I get to a computer, I'll add that linked zip as an attachment to this thread, along with some flashing Instructions in case anyone else is less familiar.
It must be pretty uncommon to do the work to get ROOT and then not flash a custom ROM with Superuser built in.
Thanks for your help. All glory to mortenmhp
okay, i was stupid. this fixed the problem for me too! thanks a lot.
Thank god for this thread
Had same problem
solved for me
And for now, i just want su, no custom rom, they seem to be sometimes unstable
Guide for dummies
just in case(copied),
Transfer this zip file file to your SD card. Remember where you saved it.
Reboot the phone into Recovery
(Boot the phone by holding down either the circle button or Volume Down button, then press the Power button. Select Recovery from the menu. (You can navigate the menus with the volume button, and make selections with the round button thingy).)
Select Install zip from SD card and navigate to where you copied the zip file and install. Watch out: Do NOT select the similar-looking apply sdcard:update.zip menu item. You have to confirm by selecting the correct ZIP file from a list.
reboot phone.
This woked for me too. Thanks a lot it was very annoying.
Oh and thanks for the dummies guide. I have not done anything but a nandbackup do it helped me feel a little more comfortable.
Great . It worked for me as well.
Thanks scott and all
1.Get utoo root.zip file
2.Go into settings>backup & reset>recovery mode.
3.Once in recovery mode find utoo root.zip file whether it is in the ext storage or internal storage. You can navigate using the volume up button and select using the power button
4. Select the utoo root.zip file.
5.Wait for utoo root file to complete installation
6.After installation reboot system.
7.After reboot open up supersu and update binary.
8.Update supersu using playstore.
9.Open supersu and if you have not bought supersu pro (you should btw), click enable pro features and because chainfire is awesome he basically gave everyone pro features and stuff.
10.Enjoy Root
I did this, it worked, mostly.
I did this method.
It worked, sort of...
I was able to get root on my tiny Kurio 4s.
There were some problems though.
Several apps stopped working properly.
The keyboard kept stopping and restarting.
The loader did as well, but did not restart.
I could not use the keyboard to input.
Lucky for me I still had the stock upgrade apk in my system.
I was able to restart in recovery mode and run the upgrade.
That reset everything to factory new.
Then I had to go through the whole catalog of updates...
That took forever.
So, what I want to know is...
Has anyone else done this?
And it's there a more up to date root method I can use on my K4s?
All the other posts on this device are old.
P.s. towelroot does not work on 4.2.2
P.p.s framaroot does not work either.
tried again...
Ok, I tried the utoo zip again.
This time (so far) I have not had any issues with misbehaving apps.
At first root checker kept saying that I did not have root.
But after I rebooted, I changed some SU settings and now root check reports that I have root!
ES3 File explorer has root access as does ES startup manager..
Hooray! Successful root on my Kurio 4s touch!
Thank you.
First of all, I have no idea where should this be posted as I am a total noobie to this forum and there is way too many categories.
I have a big problem. I installed Framaroot, used the first option (Boromir?) and have rooted my phone successfully. I tried to use *#*#supersu#*#* but nothing came up, the digits just disappeared, so I installed SuperSU from the market. I didn't do much on it, just changed the theme and hid it from my apps. I were rooted and happy for about a month, then however I got angered by SuperSU because I had to restart Hex Editor every time to get the root permissions (I were editing Terraria save files). The anger made me want to uninstall SuperSU, hoping it would just grant all the perms to the editor. First of all I disabled SuperSU, and when I realised it actually disabled the whole root, I enabled it again (unsure if it worked), I assumed everything is working, but I still wanted to get rid of the permission thing, so I pressed something like 'clean up to switch to a different superuser', and restarted my phone. I come back, and I have no root, so I went into Framaroot and used all the options, each returning that SuperSU and superuser binaries were installed. I restarted my phone, grabbed SuperSU from the Play store, just to find out that 'SuperSU binaries were not installed and SuperSU cannot install them, this is a problem!'. I then went on Framaroot, uninstalled root with all 3 options, restarted, then installed all, restarded, and the problem is still occuring. I am running Android Jelly Bean on Alcatel 4030X.
I have completely no PC access, so any USB roots or things like that are a no go. Please help!
Hi
since no-one has replied it may be because you have no paragraphs so it shows a disorganised mind....giggles
#########
Since you claim you used framaroot to install we now try to get root again
system settings security enable unknown sources
install framaroot ....if you lost it....to sdcard
install it
run it
choose first root exploit as you say that worked
if success you must reboot
###########
What you need to do if you have chainfire's superuser installed next time
go to app drawer
click on the red and yellow su icon
click on settings
change the default from .....ask each time to grant
reboot phone to test permission for apps is now auto granted. Especially test Hex Editor
###########
Altho you don't ask....there are 2 ways of updating chainfire's app
playstore ....click on update for app
open it
it will give you a dialog box to update
choose normal............it attempts to autoupdate
b) install a custom recovery and choose TWRP or CWM or CTR etc and try to update thru custom recovery
good luck
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.
So this phone is used by my close relative and I usually update their phone for them. It worked great, no complaints.
Just today I wanted to do something in Magisk, but I didn't have the bottom options like I didn't have root.
Interesting. I thought something broke it, so I decided to update to latest OS and then try again.
Since the phone was running a few months old update, I thought I'd update + root to make sure everything works.
I used flash-all.bat to update, it flashed fine, the phone loaded fine, it shows September security update.
so I went ahead and tried to root like I always did.
got the latest image, updated via flash-all.bat (without -w switch), then copied over the boot.IMG, patched it on phone, copied back to my PC from /sdcard/Downloads, then used "fastboot boot magisk...img" to boot the patched img.
now, this is how I rooted my 9R and this 3a XL a dozen times. but not now.
I open Magisk once it boots up and it just shows me the same Install option.
It same as nothing happened.
like root just doesn't exist. wtf?
did Google mess remotely with Pixels? or what's going on?
ps.: I even tried to "flash" the img into the active slot, both slots, nothing.
like the .img itself is not getting patched.
using Magisk stable, 23.0.
update 1: Interestingly enough, Root Checker says I have root. But Magisk only has Patch File option, no Direct Install. Tried Canary too, nothing. Reinstalled Magisk app, nothing. So weird... like Magisk lost root access? But why? How do I fix that? So weird...
You can open a terminal app and type 'su' to see if it prompts you for root access. If not you can try uninstalling magisk, then rename the magisk.apk to .zip and sideload from recovery.
SOLVED!
Sorry for not updating my thread, it was pretty late when I cracked this.
Here is how I fixed it. (I'll format it a bit later.)
I went Termux, root with su.
went into /data/adb/ and there is a magisk.db file.
I copied that to /sdcard/ and then to PC (you can do this on phone too using SQLite editor apps but whatever. On PC it's easier, more screen estate, etc.)
I used SQLite Browser (free) to open the file, then Browse Data and Policies
here I saw all the apps that had root granted...
So I added a new line.
I used adb shell on PC to find out the data I needed.
first, pm list packages | grep magisk to find magisk's name (it's "com.topjohnwu.magisk")
then, dumpsys package com.topjohnwu.magisk | grep userId to find out the user ID (uid) for it.
I added these into the database, it looked like this in the end:
uid package_name policy until logging notification
10386 com.topjohnwu.magisk 2 0 1 1
(^ your userId will NOT be the same!
and the first line is the column names)
saved the file, copied it back to my phone in Windows, then used Termux to copy the file from /sdcard/magisk.db to /data/adb/magisk.db
then I shut down the phone, used "fastboot boot magisk_.. patched.img" so I'd have a rooted boot image loaded up.
and boom, Magisk app works again.....
how to tell if Magisk app loses root?
well, for me the screen went dark briefly for like 2 times when I opened the app on clean boot.
and of course, Direct Install was missing.
to verify root in this case - you can only use apps that are present in the .db file.
ie.: apps that you granted beforehand.
so I'd really recommend opening Termux then doing a "su" at least after a root.
Why does it happen?!?!
I THINK this happens when you repackage Magisk. So I'd recommend changing it back before doing a system update. Because after the system update, you most often need to reinstall the .APK and then its under the original package + app name. Thus, it's not in the Policy file -> ie.: the Magisk app will not have root.