Develop Bugs

[Q] Odd Root Access Results

I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?

dferrey said:
I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
Click to expand...
Click to collapse
I have seen this happen before that you can retain some permissions with certain apps but not really remain rooted its a 50/50 shot its odd but not totally uncommon results. Generally it has something to do with apps that had su permissions prior to the update adding new su permissions don't usually occur after

I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.

Sometimes it won't push the files if they already exsist

I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.

dferrey said:
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
Click to expand...
Click to collapse
No its always worked like a charm for me maybe go to the market and install su from there to see if that doesn't change its strange though that prime is still detecting it. This method only works on rooted stock from what I have seen. Each time delete backup when you restore root. You can also give a shot at fixing permissions. I believe that ota rootkeeper ask for permissions to maybe at some point it was denied and it stuck.uninstall ota and reinstall hope you get er fixed

dferrey said:
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Click to expand...
Click to collapse
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
Note: I have never been a superuser on this kindle before, this is my first attempt at rooting - but the 2nd try at rooting is throwing the above error. I can see the file renamed as check_rooted.bak in the dir but cant rename with ES_FileExplorer utility as I dont have write permissions
TIA

harbinger13 said:
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
TIA
Click to expand...
Click to collapse
Download root checker from the market its free if you like make sure you gift the developer a buck
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
When I used kfu the last time it took 2 times to stick don't try much until you know its rooted and you have twrp installed and fff boot loader and have made a backup you can restore if something goes gunny.
---------- Post added at 03:02 AM ---------- Previous post was at 02:51 AM ----------
If you have done everything right it should reboot a couple of times the last thing you will see is twrp screen with a big reboot button click reboot and your done you will then see the fff splash screen of the boot loader it should eventually boot into the os
---------- Post added at 03:10 AM ---------- Previous post was at 03:02 AM ----------
The same rules apply for 6.3.1 watch nat3mil do it http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US

[Q] TWRP backup hangs...what to do?

Using KFU v0.9.8 this evening, I was able to install TWRP v2.4.4.0 and FFF on my 1st gen KF, as well as to root it and install the GO launcher. I'm now interested in installing JB 10.1.
Before I do, however, I want to backup the device Using TWRP's backup feature, I am able to get to the point where it has backed up all 6 partitions. However, it appears to hang at "Updating partition details..." with the words "Generating MD5" at the top of the backup window. FWIW, I have tried it without MD5 and the same problem still happens but then it says "Backing up Android Secure" at the top.
Any ideas what may be causing this and a possible workaround? I'm hesitant to believe this backup will allow me to recover the KF later if needed.
Any advice is appreciated.
Many thanks,
Mumford67

Run smirkit and flash COT Recovery instead of twrp and your issues will magically disappear.
Sent from my Nexus 7 using Tapatalk 2

asf58967 said:
Run smirkit and flash COT Recovery instead of twrp and your issues will magically disappear.
Click to expand...
Click to collapse
That worked perfectly! As it is, came to realization that KFU had never installed Superuser privileges anyway. Had to readjust the batch file to allow enough time for the Kindle to reboot so that it could install Superuser.
Now I'm running with CM's latest Jelly Bean build and all is wonderful!
Thanks for the help!
Mumford67

Same boat but your solution is beyond my experience
Original KF, 6.3.2, KFU 98+, TWRP v2.4.4
I'm in the same boat, stuck at stuck at "updating partition details" TWRP v2.4.4 after seemingly successful backup.
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
I really need some help, thanks
---------- Post added at 09:34 PM ---------- Previous post was at 08:55 PM ----------
mebobbob said:
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
Click to expand...
Click to collapse
I grabbed my kahonas and just forced a reboot. No idea if the backup is any good, not gonna risk finding out. I sideloaded superuser.apk from KFU folder and that went fine, got my root access.
My objective was simply to get root and backup apps+data for my kids' games before loading jellybean. So far so good...

mebobbob said:
Original KF, 6.3.2, KFU 98+, TWRP v2.4.4
I'm in the same boat, stuck at stuck at "updating partition details" TWRP v2.4.4 after seemingly successful backup.
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
I really need some help, thanks
---------- Post added at 09:34 PM ---------- Previous post was at 08:55 PM ----------
I grabbed my kahonas and just forced a reboot. No idea if the backup is any good, not gonna risk finding out. I sideloaded superuser.apk from KFU folder and that went fine, got my root access.
My objective was simply to get root and backup apps+data for my kids' games before loading jellybean. So far so good...
Click to expand...
Click to collapse
Post back if you need help with anything.
Sent from my Samsung Galaxy SV using Tapatalk 3

I'm going to update KFU with more time to upload superuser and I will add an option for COTR. Hopefully I will see less problems like this.
Sent from my One V using xda app-developers app

thanks for continuous development, winging it for now
awidawad said:
I'm going to update KFU with more time to upload superuser and I will add an option for COTR. Hopefully I will see less problems like this.
Click to expand...
Click to collapse
being a half-assed informed newb I used KFU to install COTR by renaming the COTR img to twrp.img in the KFU recovery folder [made a twrp.ori]. COTR installed and did the trick so now I have a couple of different configurations/ROMs backed up to toy around with.
I'm sure if I took more time to learn how it all works there'd be a more straight forward way, but... haha

I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")

scalywhisper said:
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
Click to expand...
Click to collapse
To force reboot hold down the power button until it shuts off then power it back on. Also, if SU wasn't installed then boot to TWRP, the under the reboot menu select system and if SU isn't detected it will install it for you. Good luck!
Sent from my One V using xda app-developers app

here's everything i did, going fine now
scalywhisper said:
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
Click to expand...
Click to collapse
Generally, I had issues using the KFU 98+ but nothing insurmountable and definitely got everything done that i couldn't get done before!
Follow the KFU/TWRP instructions carefully, as i assume you've done.
Once you run KFU to install SU, your Fire is "ready" to be rooted even if it didn't install the SU app/apk. If you don't have root after running KFU, you can still sideload superuser.apk. With your Fire connected to your PC and ready for file transfers, copy superuser.apk found in KFU\files\ to your Fire. On your Fire, disconnect USB, browse to where you saved superuser.apk and install it. Run the app to establish SU access. Your rooted. Use a rootchecker app to confirm if you need to.
When I got stuck in TWRP, I forced shutdown by holding the power button until it turned off. When i powered back up, it booted fine all the way to Fire home screen. I had a backup of unknown quality because i was unsure if it finished.
To get a good backup, I used COTR [Cannibal Open Touch Recovery], found here
There's nothing wrong with TWRP, it's what I've used before but v2.4.4 simply wasn't reliable for me. The half-assed-but-worked-anyway method for me was installing COTR by using KFU. On your PC, in the KFU folder \recovery\, change the twrp.img to twrp.ori. Copy the COTR image into the same \recovery\ folder [CannibalOpenTouch-v2.1_otter.img downloaded from above link]. Change the COTR filename to twrp.img.
Now, with your Fire connected to PC, Run KFU and install TWRP - it will actually install COTR.
Now reboot your Fire to recovery, same method as you did for TWRP. Use COTR to run Nandroid [standard android backup tool]. works perfect.
This sounds really complicated but it really isn't too rough. Be patient, lots of reboots.
The backups are found in a \cotrecovery\ folder on your Fire. I copied them to my PC for safe keeping. I was able to go back and forth between original setup and new reset configuration fairly easily until I had everything the way I wanted.
To prevent Amazon from updating your fire and taking root away, see this article.
I did all this just because I screwed up my parental access PW on my Fire! only way around that is to reset to factory defaults. I wanted to backup app data [games and a few critical apps] to reload after reset. My kids would have been heartbroken to loose all their progress on a few games and I felt like an idiot for screwing up the password. all said it was worth it to restore root [lost it way back after an update]. I used Mybackup Pro to save apps+data online, GREAT app [requires root to save app data]. Its a regular app you run from Fire home and you can very selectively pick what apps and data you want to backup. Not the same as recovery mode backup, such as TWRP, COTR, or clockwork.
Good luck and I hope this roundabout method helps you if you're still stuck. While i was at it, i tried a few ROMs with ICS and Jellybean but didn't really like them on my Fire and really wasn't up to figuring out how navigate the systems. That's usually something i enjoy but simply not up for it. I'll just get a new tablet to toy with true Android versions! My rooted Samsung SII with stock ICS is fairly easy to configure and navigate.

I'm in the same boat, tried to backup on my ext sd and now its stuck at generating md5. How do I stop or cancel this safely?

jreink01 said:
I'm in the same boat, tried to backup on my ext sd and now its stuck at generating md5. How do I stop or cancel this safely?
Click to expand...
Click to collapse
May need to force, power off
Sent from my XT907 using Tapatalk

sd_shadow said:
May need to force, power off
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Tried that, the only thing that worked was a battery pull. I thought I would ruin my ext sd but it looks like everything is ok. I just backed up successfully to internal. How come it hangs up on the generating md5 on the external sd but not on internal?

jreink01 said:
Tried that, the only thing that worked was a battery pull. I thought I would ruin my ext sd but it looks like everything is ok. I just backed up successfully to internal. How come it hangs up on the generating md5 on the external sd but not on internal?
Click to expand...
Click to collapse
Kindle Fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk

sd_shadow said:
Kindle Fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
OK, thanks for trying to help.
---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?

jreink01 said:
OK, thanks for trying to help.
---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?
Click to expand...
Click to collapse
This is a thread for the Kindle Fire 1, you should be asking in a thread for your device, because the answer maybe be different

sd_shadow said:
This is a thread for the Kindle Fire 1, you should be asking in a thread for your device, because the answer maybe be different
Click to expand...
Click to collapse
Sorry, I typed in search g3 twrp freezing and this is what popped up.

I firstly tried to backup with TWRP on sd storage without luck, after 1,30h I give up and canceled that darn thing (the error says: "create tarfork process ended with error:255") and tried to backup on internal storage where it seems it work like a charm. Backup completed in 767sec.

Root

This isn't hard. Towel root, use ES file Explorer to uninstall system app Device Services Platform from rooted device to disable OTA updates. Do everything else from other posts to install Gapps. Enjoy a truly nice phone.

Not sure if I am doing something wrong but I downloaded the towelroot v3 apk from geohots site and when I press the make it rain button it says "This phone isn't currently supported".
I also tried tapping the towelroot v3 button and trying the below with no luck:
1337 0 1 0 4 0
1337 0 1 7380 4 0
1337 0 1 0 4 1

I am experiencing the same. When you click "make it rain" in Towel Root you get a phone is unsupported. Looks like no way as of yet to root Amazon Fire Phone.

Guys,could you try Bin4ry's rooting method? I has worked on all tate and jem models. Also,can someone make a list of the files in /dev/block?

SafinWasi said:
Guys,could you try Bin4ry's rooting method? I has worked on all tate and jem models. Also,can someone make a list of the files in /dev/block?
Click to expand...
Click to collapse
@SafinWasi - I tried the Bin4ry root method but I don't see an option in the Fire OS to enable USB debugging, so adb does not read the device. I will try to get a list of the files in /dev/block/ to you if I'm able to read the file system through one of the explorers. Sounds like towelroot is working for some, and not for others?
EDIT: Here is the list of files in /dev/block/
/platform/msm_sdcc.1
/voId/ (EMPTY FOLDER)
/loop0
/loop1
/loop2
/loop3
/loop4
/loop5
/loop6
/loop7
/mmcblk0
/mmcblk0boot0
/mmcblk0boot1
/mmcblk0p1
/mmcblk0p10
/mmcblk0p11
/mmcblk0p12
/mmcblk0p13
/mmcblk0p14
/mmcblk0p15
/mmcblk0p16
/mmcblk0p17
/mmcblk0p18
/mmcblk0p19
/mmcblk0p2
/mmcblk0p3
/mmcblk0p4
/mmcblk0p5
/mmcblk0p6
/mmcblk0p7
/mmcblk0p8
/mmcblk0p9
/mmcblk0rpmb
/ram0
/ram1
/ram10
/ram11
/ram12
/ram13
/ram14
/ram15
/ram2
/ram3
/ram4
/ram5
/ram6
/ram7
/ram8
/ram9
/zram0
Please let me know if there's anything else I can do to help.

I am M3 said:
@SafinWasi - I tried the Bin4ry root method but I don't see an option in the Fire OS to enable USB debugging, so adb does not read the device. I will try to get a list of the files in /dev/block/ to you if I'm able to read the file system through one of the explorers. Sounds like towelroot is working for some, and not for others?
EDIT: Here is the list of files in /dev/block/
/platform/msm_sdcc.1
/voId/ (EMPTY FOLDER)
/loop0
/loop1
/loop2
/loop3
/loop4
/loop5
/loop6
/loop7
/mmcblk0
/mmcblk0boot0
/mmcblk0boot1
/mmcblk0p1
/mmcblk0p10
/mmcblk0p11
/mmcblk0p12
/mmcblk0p13
/mmcblk0p14
/mmcblk0p15
/mmcblk0p16
/mmcblk0p17
/mmcblk0p18
/mmcblk0p19
/mmcblk0p2
/mmcblk0p3
/mmcblk0p4
/mmcblk0p5
/mmcblk0p6
/mmcblk0p7
/mmcblk0p8
/mmcblk0p9
/mmcblk0rpmb
/ram0
/ram1
/ram10
/ram11
/ram12
/ram13
/ram14
/ram15
/ram2
/ram3
/ram4
/ram5
/ram6
/ram7
/ram8
/ram9
/zram0
Please let me know if there's anything else I can do to help.
Click to expand...
Click to collapse
Oh yeah,it's got a boot0block file(mmcblk0boot0). Can you check which file is ridiculously large? Also,what's in the platform file?
Sent from my device running CyanogenMod 11

SafinWasi said:
Oh yeah,it's got a boot0block file(mmcblk0boot0). Can you check which file is ridiculously large? Also,what's in the platform file?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
@SafinWasi - The files in the dev/block/ all show as empty 0.00b. And I apologize, looks like msm_sdcc.1 is actually a folder which contains the following:
By-name (folder)
aboot
boot
cache
dbi
DDR
fsc
fsg
misc
modem
modemst1
modemst2
persist
recovery
rpm
sbl1
ssd
system
tz
userdata
By-num (folder)
p1 thru p19
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
Again, all files show as 0.00b for me, but I'm using ES File Explorer. Also the files are showing with -rw permissions.

I am M3 said:
@SafinWasi - The files in the dev/block/ all show as empty 0.00b. And I apologize, looks like msm_sdcc.1 is actually a folder which contains the following:
By-name (folder)
aboot
boot
cache
dbi
DDR
fsc
fsg
misc
modem
modemst1
modemst2
persist
recovery
rpm
sbl1
ssd
system
tz
userdata
By-num (folder)
p1 thru p19
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
Again, all files show as 0.00b for me, but I'm using ES File Explorer. Also the files are showing with -rw permissions.
Click to expand...
Click to collapse
Can you pull the boot file and send it to me? Looks like we just found the kernel. Also,the system file should be large
Sent from my device running CyanogenMod 11

towelroot
SafinWasi said:
Oh yeah,it's got a boot0block file(mmcblk0boot0). Can you check which file is ridiculously large? Also,what's in the platform file?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
All versions of towelroot are not created the same it seems. I had rooted my Kindle Fire HDX 8.9 and done everything it seems that everyone here had posted. Installed Super SU, KindleFree Pro, etc. Well, the pesky Kindle Fire updated nonetheless and I had to search for and find a version of towelroot that would work to re root the device again. At the same time, it was a different version of towelroot that rooted my 2 day old phone weeks ago and before I knew it, I was getting nags that when I was connected to wifi again, the phone was going to update OS! I did I boatload of searching on the internet and discovered that the Fire TV uses system app Device Services Platform (DSP) to do OTA updates. I just took a gamble and used ES File Explorer to uninstall that system app. ES File Explorer gave me an error saying uninstall failed (on phone and Kindle HDX 8.9). but on reboot nag was gone and I continue to have access to Gapps, playstore, Chrome, everything. I did use xposed installer to load Gapps. Amazon Instant video still works, it's all the phone it should be and is fast as heck and pretty, lol.
I have no idea why there are so many sources for towelroot and why seemingly same versions really are NOT. I just know that Google is your friend and shotgun approach works and there is a version that will your phone. I am not a geek and did this

Dilbert1959 said:
All versions of towelroot are not created the same it seems. I had rooted my Kindle Fire HDX 8.9 and done everything it seems that everyone here had posted. Installed Super SU, KindleFree Pro, etc. Well, the pesky Kindle Fire updated nonetheless and I had to search for and find a version of towelroot that would work to re root the device again. At the same time, it was a different version of towelroot that rooted my 2 day old phone weeks ago and before I knew it, I was getting nags that when I was connected to wifi again, the phone was going to update OS! I did I boatload of searching on the internet and discovered that the Fire TV uses system app Device Services Platform (DSP) to do OTA updates. I just took a gamble and used ES File Explorer to uninstall that system app. ES File Explorer gave me an error saying uninstall failed (on phone and Kindle HDX 8.9). but on reboot nag was gone and I continue to have access to Gapps, playstore, Chrome, everything. I did use xposed installer to load Gapps. Amazon Instant video still works, it's all the phone it should be and is fast as heck and pretty, lol.
I have no idea why there are so many sources for towelroot and why seemingly same versions really are NOT. I just know that Google is your friend and shotgun approach works and there is a version that will your phone. I am not a geek and did this
Click to expand...
Click to collapse
I agree mate. Towelroot versions are different.

Dilbert1959 said:
All versions of towelroot are not created the same it seems. I had rooted my Kindle Fire HDX 8.9 and done everything it seems that everyone here had posted. Installed Super SU, KindleFree Pro, etc. Well, the pesky Kindle Fire updated nonetheless and I had to search for and find a version of towelroot that would work to re root the device again. At the same time, it was a different version of towelroot that rooted my 2 day old phone weeks ago and before I knew it, I was getting nags that when I was connected to wifi again, the phone was going to update OS! I did I boatload of searching on the internet and discovered that the Fire TV uses system app Device Services Platform (DSP) to do OTA updates. I just took a gamble and used ES File Explorer to uninstall that system app. ES File Explorer gave me an error saying uninstall failed (on phone and Kindle HDX 8.9). but on reboot nag was gone and I continue to have access to Gapps, playstore, Chrome, everything. I did use xposed installer to load Gapps. Amazon Instant video still works, it's all the phone it should be and is fast as heck and pretty, lol.
I have no idea why there are so many sources for towelroot and why seemingly same versions really are NOT. I just know that Google is your friend and shotgun approach works and there is a version that will your phone. I am not a geek and did this
Click to expand...
Click to collapse
Hi @Dilbert1959 - could you please post in this thread, or PM me, the towelroot apk which worked for you?

I am M3 said:
Hi @Dilbert1959 - could you please post in this thread, or PM me, the towelroot apk which worked for you?
Click to expand...
Click to collapse
Same here, interested in the working towelroot apk. Having the same issue with what I can get from the towelroot site.

Grizzlax said:
Same here, interested in the working towelroot apk. Having the same issue with what I can get from the towelroot site.
Click to expand...
Click to collapse
I got a response from Dilbert1959 which linked to a file on Google Drive, but would not let me download as it violated ToS. Haven't gotten a response from him since. Every towelroot apk I've tried has not worked for me, and I've tried around 10 different sources. I've also tried multiple variations of the modstrings in the v3 towelroot with no success, however I believe there is a modstring that will work for this phone - we just haven't found it yet.

So nothing new yet on this front?
I've tried several versions of Towelroot with no success.
I'm really digging the phone, with a few exceptions. I'd love to be able to get Google Services on it.
Hopefully something solid works out soon.

rkalajian said:
So nothing new yet on this front?
I've tried several versions of Towelroot with no success.
I'm really digging the phone, with a few exceptions. I'd love to be able to get Google Services on it.
Hopefully something solid works out soon.
Click to expand...
Click to collapse
If your phone is already updated to 3.5.1, there is currently no root method. You can follow this guide to install the Google apps on your phone. They work (with some annoying force close messages)
http://www.gizmag.com/how-to-install-google-apps-kindle-fire-hd-hdx/30736/
Click to expand...
Click to collapse

I am M3 said:
If your phone is already updated to 3.5.1, there is currently no root method.
Click to expand...
Click to collapse
Damn. I'm already on 3.5.1. Has anyone been able to successfully roll back somehow?

rkalajian said:
Damn. I'm already on 3.5.1. Has anyone been able to successfully roll back somehow?
Click to expand...
Click to collapse
Amazon still has the download link up for the 3.5 OS. The stock recovery has an option for "update via ADB" which will prompt you to sideload an update file. I'm thinking this will allow us to revert to version 3.5 unless Amazon has somehow blocked it. This hasn't been tested yet (and since this is my only phone to use right now, I'm not willing to risk turning it into a paperweight)
I suggest installing a different launcher (CLauncher works good) and installing the GApps if you want a more "regular" Android experience.

I am M3 said:
If your phone is already updated to 3.5.1, there is currently no root method. You can follow this guide to install the Google apps on your phone. They work (with some annoying force close messages)
Click to expand...
Click to collapse
I tried this method of non-root access to install Google Play support. It didn't work for my purposes. I could pull up GMail (after setting up a one-time App password since I use 2-step verification), but there were lots of error messages all the time about Google services stopping. What I really wanted it for was to be able to link my Clash of Clans game into my Google+ account for backups. But, that App won't even pull up with the bastardized Play support they had developed for the Fire HDX.
Anyone else have any luck with Towelroot after the 3.5.1 update? I'd really like to get working Google Services support - it is by far the most disappointing feature of the phone. I actually love the Fire Phone other than that.
Thanks in advance,
MR

Guys,if you have trouble in recovery with Update Via ADB,try using a linux distro. @Dilbert1959 @I am M3 please try this.

I was able to get into recovery and sideload the 3.5 bin and downgrade. It worked sort of. In that it killed the phone services and created a lot of errors but it was on 3.5 and I was able to use towelroot to root it. Unfortunately the fact that it killed the phone made it a non-starter and I had to go back. And it wasn't as simple as just updating again I had to do a full factory restore.

Shield Android TV rooted

I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.

Great job. Will try later.

It offers fastboot OEM unlock?!? Sweet

I'm starting dev work on this as well. Can you try the flipped screen flag and see if it that fixes the display? That's required to make the tablet work correctly. I preordered the pro edition, so I can't test anything for almost another two weeks. Hopefully someone will be able to get the normal usb ports working, since it'll be much easier to use those for a mouse/keyboard.

Sweet can't wait to try this out

Thanks for posting this. I've got my NVIDIA Shield Android TV coming on Wednesday, so I'll give this a try. I had a USB OTG cable, but lost it several months ago so I ordered another one of those as well. Just to clarify... the 2 USB 3.0 ports will work after rooting when you boot back to stock, right?
Also, this works on the latest 1.1 OTA update too, correct?
Sorry to ask this as it is super n00bish, but could someone explain to me step-by-step directions for rooting this or perhaps link to a guide that uses this same procedure? I know the main steps are listed in the OP, but I'm not really sure how to use adb to push supersu.zip, reboot into bootloader, fastboot, etc.
Lastly, what will be the process of upgrading via OTA updates in the future after I root it? Will I need to unroot one way or another (instructions or a link to a guide would be great), or will OTA updates work just fine?
Once again, sorry for all the n00b questions. I just want to make sure I don't do something stupid to mess the device up...

FreeEmulator said:
Thanks for posting this. I've got my NVIDIA Shield Android TV coming on Wednesday, so I'll give this a try. I had a USB OTG cable, but lost it several months ago so I ordered another one of those as well. Just to clarify... the 2 USB 3.0 ports will work after rooting when you boot back to stock, right? Also, this works on the latest 1.1 OTA update too, correct?
Also, sorry to ask this as it is super n00bish, but could someone explain to me step-by-step directions for rooting this or perhaps link to a guide that uses this same procedure? I know the main steps are listed in the OP, but I'm not really sure how to use adb to push supersu.zip, reboot into bootloader, fastboot, etc.
Click to expand...
Click to collapse
Yup, everything works normally after rooting. These issues only exist in TWRP because I did an extremely quick and dirty build (extracted a Shield Tablet TWRP and replaced the kernel). I'll work on fixing them soon, unless someone beats me to it. Thanks for the tip on the screen flipping, Steel01.
I've updated the OP with some more detailed instructions.
ETA: I can't see OTAs being a problem. In theory, they could check if an su binary is installed and deny the update until you remove it, but if they're allowing oem unlock, I can't see why they'd do that. And you could just remove it anyway. You will have to re-root after each OTA update.

teletype said:
Yup, everything works normally after rooting. These issues only exist in TWRP because I did an extremely quick and dirty build (extracted a Shield Tablet TWRP and replaced the kernel). I'll work on fixing them soon, unless someone beats me to it. Thanks for the tip on the screen flipping, Steel01.
I've updated the OP with some more detailed instructions.
ETA: I can't see OTAs being a problem. In theory, they could check if an su binary is installed and deny the update until you remove it, but if they're allowing oem unlock, I can't see why they'd do that. And you could just remove it anyway. You will have to re-root after each OTA update.
Click to expand...
Click to collapse
Awesome, thank you so much for the info and instructions. :good: I should be good to go now once everything arrives on Wednesday.

Twrp for forge?
Is there any skilled folks out the with a forge tv? I'm in need of some kind of recovery for this. I'm a bit of a noob so compiling it on my own is kinda greek to me

Quick warning for Pro owners: OEM Unlock takes about 92 minutes. Just be warned and ready for it...

Yeah so go to links with viruses in them and then waste time removing them. You know there are website without a million links to viruses all over them that can be used. It's always nice not to have to play guess which download link isn't a virus. -_-

i read somewhere that full hd/4k playback in netflix and other vod services needs a locked bootloader. is that right?

A.N.Droid said:
i read somewhere that full hd/4k playback in netflix and other vod services needs a locked bootloader. is that right?
Click to expand...
Click to collapse
Hypothetically if you can oem unlock bootloader can you just oem lock bootloader to fix the issue?

teletype said:
ETA: I can't see OTAs being a problem. In theory, they could check if an su binary is installed and deny the update until you remove it, but if they're allowing oem unlock, I can't see why they'd do that. And you could just remove it anyway. You will have to re-root after each OTA update.
Click to expand...
Click to collapse
Actually rooting will likely break OTA updates. Since lollipop, Google has moved to block level OTA updates. That means it doesn't just patch individual files, it patches at the block level. So if there is a change to /system the OTA won't update.
The same seems to apply to the Shield TV. Here's the updater-script from the current OTA:
Code:
(!less_than_int(1432624016, getprop("ro.build.date.utc"))) || abort("Can't install this package (Tue May 26 00:06:56 PDT 2015) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "foster" || abort("This package is for \"foster\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/sdhci-tegra.3/by-name/APP", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/sdhci-tegra.3/by-name/LNX");
show_progress(0.200000, 10);
nv_copy_blob_file("blob", "/staging");
nv_copy_blob_file("bmp.blob", "/bmps");
But borked OTA shouldn't be much of an issue, since Nvidia is releasing the fastboot factory images: https://developer.nvidia.com/shield-open-source The text is there now for them, but they aren't up yet. So you can always revert to stock, then OTA update.

Wait... What? You got one of of the tablet twrps to boot on the console? I'm shocked that worked. Didn't think it what that easy to get 32-bit mode. Anyways, that's why it's upside down, because that flag is set for the tablet. As soon as a console section opens up here and on androidfilehost, I'll post my builds. I have cm, twrp, and multirom compiling, but I can't test them until next week, when Amazon ships the pro, so they might not even boot.
@agrabren: Oh my goodness, the wipe takes that long? What's it doing? US Government certified nuking? And people complain about multi minute cache wipes on the tablet now. What am I going to be hearing in a couple weeks for this?
Actually, since you're around again... Do you still have the CM files you made for the portable? I'm still interested in what you did to make the cwm recovery work as well as it did.

One more quick question for now... once rooted, does anyone know how I would go about locking the GPU clock speed / frequency at its highest setting (which if I've read correctly is 1 GHz)? I'd like to be able to flip the lock on only while testing out some pretty hardware intensive emulator games (the Dolphin GameCube/Wii emulator, which I was told by a developer of the emulator to try to lock the maximum GPU clock speed to ensure best performance). Thanks again for all the help, you guys are great.

Tested out the pro console on my side (Got it early due to reasons).
It refuses to mount any partitions, so it is impossible to root.

sonicadvance1 said:
Tested out the pro console on my side (Got it early due to reasons).
It refuses to mount any partitions, so it is impossible to root.
Click to expand...
Click to collapse
It's probably because the partition layout/names are different for the internal 500GB drive. If you poke around you can probably find the info, or just dump your boot.img, decompile it and look for the fstab file. It will look similar to the below (that is for the ADT-1).
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/system /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/crypto
/dev/block/platform/sdhci-tegra.3/by-name/misc /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/boot /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/DTB /dtb emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/staging /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/sysdata /sysdata emmc defaults defaults

Someone skilled do this also for Forge anyways hopefully XDA adds Android TV forums.
Keep up the good work even though I don't own the Shield.

patt2k said:
Someone skilled do this also for Forge anyways hopefully XDA adds Android TV forums.
Keep up the good work even though I don't own the Shield.
Click to expand...
Click to collapse
The forge has a locked bootloader. Sure, you can root it (supposedly), then replace the recovery, but you'll never be able to use fastboot until it's unlocked.
BTW, the Nvidia Shield TV factory images are up now :victory:

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.