Kodi and Confluence++ Skin Missing Power Options - Fire TV General

Hi all. I've installed kodi and with the confluence ++ skin. There are a few observations and questions I would be grateful if someone could help point me to the right direction.
1. I cannot get the power suspend option on kodi like how it exists in spmc. Is there a settin somewhere to enable it.? I cannot seem to find it. maybe some config file?
2. When adding 7 tiles to the bottom, the first tile gets slightly cut.
3. With rbox's boot menu. Is there a way to disable the boot menu display on every boot? or at least decrease the time of 5 seconds?
Really appreciate your help.

I tried to add the power options from elmero's repo but that requires the su and when I try to run the su script, it fails. however I do have root. am confused to make kodi my main OS yet . any guidance?

have you went into the SU app under the FTV menu ( the OEM rom, not XBMC ) and launch SU. Update binaries and apply etc. Try that.

mroneeyedboh said:
have you went into the SU app under the FTV menu ( the OEM rom, not XBMC ) and launch SU. Update binaries and apply etc. Try that.
Click to expand...
Click to collapse
what is the su app you are referring to in the ftv menu? I have supersu and I have an option to force stop only
also when I try spmc, I get the power options
confused.

Open superuser from the FTV app list and let it update.

Montisaquadeis said:
Open superuser from the FTV app list and let it update.
Click to expand...
Click to collapse
I have the supersu application. That does not have an open option. I also downloaded the superuser from the playstore and I still get eh checksu.py script failure. on spmc I too get the script failure but I have the power options working just fine.

Sorry man, there should be an option to update binaries like in any SU app.. Which version are you using

When I installed rbox's CMW recovery and custom ROMs I lost the ability to open su. I believe this is a known issue.

jmerrilljr2 said:
When I installed rbox's CMW recovery and custom ROMs I lost the ability to open su. I believe this is a known issue.
Click to expand...
Click to collapse
For now I'm still sticking to spmc. I don't think helix has the support ready yet. SPMC 13.3.2 (not the latest one) works the best with .ts files as well.

Related

[CM11S]Enabled functional built in Superuser

With some help on the cyanogenmod forums, I worked out a way to enable the integrated superuser manager to actually function!
REVISED EDITION:
WARNING! DO NOT ATTEMPT UNLESS YOU KNOW WHAT YOU ARE DOING.
This is an experimental step to bring a feature from regular Cyanogenmod to 11S. You have been warned.
This requires adb and fastboot to be installed.
Please read all the instructions before attempting
1)-- Optional-Flash a custom recovery of your choice. There are threads out there that explain this.
2)Next flash the debuggable kernel, found at the bottom of this post. You can easily flash it via fastboot.
fastboot flash boot ./path/to/boot-debuggable.img
2)Download su.zip I created.
3)Boot into custom recovery(a requirement). This can be done without actually flashing it. Look up how, plenty of threads already.
4)Flash su.zip
8) Reboot.
9)If you didn't before doing this, go to Settings => About Phone and enable developer mode. Under Settings => Developer Options select Root Access and change it to Apps and ADB. Now install any root application or root checker and test it out.
Debuggable Kernel is downloadable here at the bottom:
https://cyngn.com/products/oneplusone/
su.zip
http://www.androidfilehost.com/?fid=23578570567721138
https://mega.co.nz/#!sp8nmL5J!Pj2Z4UI-7vG2YsMwEpIbDLTWOwiyWwu398oLE9edFdk
RESERVED
RESERVED
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
joaocadide said:
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
Click to expand...
Click to collapse
What current superuser manager are you using? SuperSU?
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
How can I get rid of the menu when I use SuperSU instead?
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
That only makes the menu visible. The menu will not actually function as a Superuser manager. For that, you would need the debuggable kernel and the proper compatible su binary which is why I wrote my instructions.
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
jbass350z said:
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
Click to expand...
Click to collapse
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
vladashram said:
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
Click to expand...
Click to collapse
I had this same exact issue with secure settings, and elected to follow the instructions on this page to activate the cyanogenmod root settings - it worked just fine. Interestingly, even after losing the "built in root" after updating to XPNH300, secure settings still seems happy.
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
chenkeikari said:
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
vladashram said:
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Click to expand...
Click to collapse
As of right now, the stock debuggable kernel for 30O is live and available.
Thanks for your work.
But could you please update to the latest version of the SuperSU binaries or could you tell me, what you modified comparing it to the normal SuperSU.zip?
Would you please share how and why would this be different than a straight forward install of SuperSU?
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Not working for me
Titokhan said:
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Click to expand...
Click to collapse
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
remortr said:
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
Click to expand...
Click to collapse
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Pls help me step by step procedure..
sendhiloo7 said:
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Every thing done but fast boot wont work in my case pls help me sir .pls see my attachment...

[How-To-Guides] V4A, Play Store/Xposed And More!

Hey all,
I'm a regular on these forums (throughout the day every day) and like to develop my own ROMs for other devices and help out in every way I can!
I noticed a lot of threads spread out across the AFTV forum for Xposed, Gapps etc. I however feel they should all be in one place!
I will provide details/instructions for things that worked for me.
I will not have guides someone else made without their permission as well as I will provide credits where due!
* I will not cover rooting or installing a pre rooted ROM.
* I will assume if you are here you are on @rbox latest rom/recovery. You have root with SuperSU and a working Busybox.
* Thread will be cleaned and links added soon!
*I will upload files I know work 100% to either my AFH or my Drive folder.
* Eventually (when I get my keyboard/mouse) I will be creating ROMs with all of this baked in.
Xposed+Play Store
I didnt get around to pictures and a more advanced tutorial YET but willpost screens later:
1) Be on rbox latest pre rooted rom and recovery.
2) Download the following: Xposed framework, Xposed installer apk, hdx module apk, open gapps nano flashable zip, lean back playstore 5.10 & Market helper apk (market helper might not be necessary but I used it.)
https://drive.google.com/folder/d/0By9dxKZHr9vaUVhMRnc0RGxTNnc/edit
3) Have a custom launcher already such as leanback launcher or firestarter etc. as well as a root browser like es file explorer and/or root browser.
4) If mouse doesnt work then use a mouse apk such as Wukong on play store.
5) Move all downloaded files to storage of choice (internal sd card, microSD or usb storage)
6) Boot into TWRP and navigate to the Xposed framework and flash it then reboot system.
7) Once booted install the Xposed installer apk and reboot.
8) Install HDX module apk.
9) Go into Xposed installer it should say everythings installed. Go to modules and use a mouse to check the box for HDX and reboot.
10) Boot back into TWRP and navigate to and flash the open gapps zip and reboot to system.
11) Go into system/priv-app/Phonesky/ and delete the phonesky apk and reboot.
12) Using a root browser, navigate to the leanback play store we downloaded and rename to Phonesky.apk
13) Copy the apk and put it in /system/priv-app/Phonesky/Phonesky.apk
14) Set permissions on Phonesky.apk to rw-r-r and reboot
15) When booted back up, using a 3rd party launcher, open Play Store.
16) You might need to use a mouse again to be able to sign into google account.
17) optional step, install market helper apk and set to Google/Android TV.
Play Store should work and download apks successfully.
Note: As usual usb debugging should be on throughout the whole process and when opening stuff make sure to grant su permissions if it pops up throughout the process.
V4A with Neon
1) Download latest V4A apk and push to device.
2) Install apk and open it.
3) When it prompts, install driver (if it gives an option install highest quality.)
4) Download and extract zips at this drive folder (also download the v4a apk while youreat it) :
https://drive.google.com/folder/d/0By9dxKZHr9vaOHJOMkc3TUFsSXM/edit
5) Take all the files and place in respective folders. For example, 50viper.sh goes into /system/etc/init.d/50viper.sh
6) Each file we push needs to have permissions set to rw-r-r.
7) Reboot device.
8) Push universal init.d from the play store to your device and install it.
9) Open it and grant su. You should see the 50viper.sh file. Turn the init.d switch to on in the app and then press the start button towards top right.
10) you should see it say it was started. Now open the V4A app and select the menu button (you can use menu button on fire tv remote) and go to driver status.
It should say everything thing is enabled and supported! Keep in mind it will not show processing unless you are playing audio.
Miscellaneous APK's (Leanback Youtube, ADB Wifi, Kodi 15.2 etc. Is a work in progress...)
https://drive.google.com/folder/d/0By9dxKZHr9vaSUVUWExJYVNWSW8/edit
CREDITS
@zeroepoch for root - http://forum.xda-developers.com/showthread.php?p=63750572
@rbox - for Recovery/Pre Rooted ROMs and his constant support!
@jocala for adbFire - http://forum.xda-developers.com/showthread.php?p=53485230
@Chainfire - for SuperSU
@V4A Team
More to come! PM me if I forgot credits as I'm almost certain I have...
I willalso start working on a debloat list as well tomorrow.. I will list theAPK and what it is the best I can... If you have something toadd to the list or want guides for specific items you can request in here as well!
Screenshots...
Thanks Elliwigy! I am going to try again with playstore when I get home. I couldn't get the playstore to show in Firestarter. I ended up installing the apk as a normal app which gave the error code upon installing anything from the store. I will also try v4a and leanback you tube. I'll let you know how it goes!
worked perfectly for me.
Great work...
elliwigy said:
I willalso start working on a debloat list as well tomorrow.. I will list theAPK and what it is the best I can... If you have something toadd to the list or want guides for specific items you can request in here as well!
Click to expand...
Click to collapse
Great guides.....thanks much. quick question, does your Leanback Launcher show the settings?
thanks
Playstore automatically updates to different version. Won't install anything. Help!
dk1keith said:
Great guides.....thanks much. quick question, does your Leanback Launcher show the settings?
thanks
Click to expand...
Click to collapse
yup sure does
Largewoodenspoon said:
Playstore automatically updates to different version. Won't install anything. Help!
Click to expand...
Click to collapse
Unfortunately I havent figured out how to stop updates on the Play Store yet. If someone does let me know!
Largewoodenspoon said:
Thanks Elliwigy! I am going to try again with playstore when I get home. I couldn't get the playstore to show in Firestarter. I ended up installing the apk as a normal app which gave the error code upon installing anything from the store. I will also try v4a and leanback you tube. I'll let you know how it goes!
Click to expand...
Click to collapse
I tend to be very detailed in my instructions lol. others are reporting success with this guide so hopefully you will as well!
elliwigy said:
Unfortunately I havent figured out how to stop updates on the Play Store yet. If someone does let me know!
Click to expand...
Click to collapse
Just go to the google play store in fire tv apps
Then click uninstall (It won't uninstall)
Then click the play store app it will open the old version
go2xraj said:
Just go to the google play store in fire tv apps
Then click uninstall (It won't uninstall)
Then click the play store app it will open the old version
Click to expand...
Click to collapse
No option to uninstall?
Freeze it in titanium backup?
Largewoodenspoon said:
No option to uninstall?
Freeze it in titanium backup?
Click to expand...
Click to collapse
can you able to go fire tv home page?
go2xraj said:
can you able to go fire tv home page?
Click to expand...
Click to collapse
Yes indeed.
Go to apps section there and check for google play store which is installed
Sent from my iPhone using Tapatalk
go2xraj said:
Go to apps section there and check for google play store which is installed
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I cant do anything other than open it though? Long press doesn't do anything?
elliwigy said:
yup sure does
Click to expand...
Click to collapse
Cool....I have Leanback Launcher installed but the settings aren't visible and recommendations don't work. Mind telling me which apk and method you used to install it. I'm on rbox prerooted 5.0.5
thanks again for your work.
Largewoodenspoon said:
I cant do anything other than open it though? Long press doesn't do anything?
Click to expand...
Click to collapse
Sent from my iPhone using Tapatalk
My apps section looks totally different. Just little icons on a big page. How do I upload a picture for you?
Like this

[TOOLS Fire HD 6&7 ] Rooting, Gapps, Launchers, Block OTA & Ads + More

Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip​
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.​WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.
Nice Work!
@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.
DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!
notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?
DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!
Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.
I'm getting ready to update. Please let me know if you found any problems.
Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs
Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)
I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.

Really Useful Xposed Modules, mod and apps to get the most out of rooted fire TVs

Hey all,
I'm trying to figure out which xposed modules, mods and apps are the most useful ones for the rooted fire TVs and compile a list.
What I can recommend so far:
"Xposed Additions Pro"
to customize the keys of the remote control (longpress, double press, triple press shortcuts)
Adaway
No more annoying ads in youtube, twitch and other apps
Mozilla Firefox + Adblock Plus + Adobe Flash Player
Web-Browsing on Fire TV (only good with Mouse + Keyboard)
MarketHelper
spoof what device the firetv is to actually download apps through play store (usually says that apps are not compatible on 90% of the apps, to me)
AudioGlow
Nice AudioVisualizer of whatever audio is playing in the background (tuneinradio, mp3-player, kodi.. etc) - unfortunately a bit laggy or rather not on point with the audio.
Holo Themer (Xposed Module)
Open apps that do not seem to open on the FireTV (like SuperSu) - set the theme to "Material Dark" and they will open.
WARNING: Can cause bootloops. Use Version 3.0 as well.
harlekinade said:
I hold a grudge against the Fire TV community for basically making posts like this one a one in a million find on this subforum - and the whole "I think, I've read, It worked for me, who can help me" culture that comes with it.
Click to expand...
Click to collapse
I feel ya.... =)
---
Havent tried it myself yet but since Xposed App Settings keeps closing when you actually try to edit app settings (like to change DPI) I did some research and apparently you can get the dpi changing behaviour with tasker. Have it run a shell command "am set-density xxx" when an app starts and closes iirc. I would like to change the dpi setting of firefox for example... used to do it on my phone with xposed app settings but that damn thing wont work on fire tv.
Some other "activities" like this also keep closing - maybe we can together find out whats the cause and fix it. For example there is "supersu" which cant be opened - at least in the latest versions.. ive read that 1.x does work. And titanium Backup wont do batch commands and/or let you edit its settings.. really lame =/
FireTVs android is gimped down somewhat unfortunately..
ADD: also no recent apps overview available =( .. tried to set it up with xposed additions but wouldnt do anything .. but switching between the 2 recent apps does actually work. Put that on long-press menu button + long press play starts youtube.
---
Also (this needs more testing) there is a system app called com.amazon.videoads.xxx or something. Disabling that seems to disable the annoying prime ads which is played before stuff when you watch amazon prime. (WTF you put ads up anyway for prime for those that already have prime?! i dont get that..so annoying - yea i hate ads because i'm immune to them anyway)
argh idk how about you but trying out xposed modules to see if they work on the fire tv is really annoying - my damn thing keeps goin into bootloops quite often. Most of the times clearing dalvik cache helps but sometimes ill have to disable xposed, boot, uninstall xposed installer, install xposed in recovery, reboot, install xposed installer, disable all xposed modules.. reboot one more time and then reenable the xposed modules. Need to figure out a better way for this.
ADD: I installed supersu as user app (first removed the supersu system app off course) but it still cant be opened. So its not a "system app" problem. Older versions do seem to open, but they want you to "update" the supersu binary, which I didnt want to try yet hehe.
ADD2: Any idea how to disable the notification of supersu and make the delay longer? When i try to edit the supersu.cfg (in /data/data/) it just overwrites itself after saving.. ?!
ADD3: Figured out how to "edit" the supersu.cfg ... copy it to /data/local/tmp and edit it there, then go to recovery and overwrite the original with the modified version with the file manager (those supersu notifications lag out often so I prefer to have em disabled..)
harlekinade said:
@supersuCan the update prompt be ignored?
Click to expand...
Click to collapse
nope unfortunately not.. and the settings did overwrite itself again also.. so editing supersu.cfg doesnt help=/
harlekinade said:
Paragon NTFS (free)
Click to expand...
Click to collapse
have you also tried stickmount from chainfire? Wondering which one is better.
Another recommendation (regarding the DPI):
Tasker (+App Factory)
I created two apps with the tasker app factory for my fire TV to change the DPI when they are opened.
The shell command to use is actually "wm density xxx" where xxx is the dpi u want.
What I did is create one with 240 dpi and one with 320 dpi (default) and set them to long press back/forward buttons. This way I can change between 240 and 320 dpi with those buttons.
What you can also do is to set up tasker contexts for certain apps to change the DPI on launch. For Firefox for example 240 dpi is muuuch better and FireStarter also is cooler with 240 dpi (maybe even less.. it will downsize the fonts which you cant do with the FireStarter settings).
With a more complex script you could probably just increase/decrease dpi in steps. (if you run "wm density" without a dpi, it will return the physical dpi and if its changed the overwritten dpi.. when you parse that number one could just add/substract to make an universal dpi increaser/decreaser)
---
Gonna play around with supersu versions now and then tell you which is the latest that runs.
ADD: Seems like 2.02 or 2.12 (beta) is the latetest supersu that opens - but unfortunately the su binary is not compatible it seems. When I got myself the accoring zip and flashed it through twrp the app would open but say that there is no su binary ... *grmpf*
figured out a way to start supersu and also xposed app settings! but apparently nobody is interested.. ill tell ya by pm if you want i guess..
but goddammit this damn fire tv bootloops again just after applying some app setzings... dalvik cache gets fked up so easy..
stickmount is also able to mount exfat - but automounting is a bit messed up it seems.
Xposed Additions also breaks the voice search it seems. (or some other module)
But maybe this can be fine tuned somehow..
A bit disappointed that nobody except us 2 actually joins in - but this is how xda is nowadays i guess..
Anyway: To actually open supersu and xposed app settings you will have to install "Holo Themer" Xposed module and activate "material design" for the app that you want to use.
It seems that the apps / activities that dont work are using some ui elements that are not available on the fire tv - but with holo themer it works.
Be aware though: My fire tv didnt boot through anymore after restart - which seems to be related to holo themer .. which i dont really understand yet.
i wish i could just use dalvik .. i bet these bootloops / hangs are all caused by that fkin art runtime. On my phone I still use jellybean on purpose lol.. much more modding freedom compared to this newer android versions.. garh
Getting some really strange behaviors:
Activate some xposed modules, reboot, everything works. Then without actually changing any settings in the modules or smth I reboot one more time, and fire tv stuck at boot logo.
WTF is that?! Not really deterministic to me.. =/..... it should either work or not work.
Sometimes clearing the "dalvik" cache helps to get it to boot again.. but then after another reboot its back to beeing stuck at boot logo. I wish I would understand wtf is causing this. The modules which do seem to cause those loops actually do work also.. at least until you reboot lol.. (like that holo themer example from above..)
I read now that the holo themer has problems with lollipop. Its weird it actually works - you activate the module, reboot and it works.. then you reboot again and you are stuck in bootloop.
Im currently trying to figure out how to prevent the bootloops and still use it. I guess you just temporarily activate it to edit settings of an app like supersu. then uninstall it afterwards. If you need it again you just install it again. If youre stuck in bootloop the easiest way to get into the system again is to delete the modules.list file in the /data/data/xxx/conf folder of the xposed installer. Then it will boot without any modules active one time. Sometimes a clear of dalvik cache is also necessary to fix bootloops caused by xposed modules.
Regarding the Holo Themer Bootloop:
In order to temporarily use holo themer to change settings of apps that crash/close otherwise here is what I figured out:
1. Install Holo Themer and turn it on in xposed installer (but DONT launch it yet!)
2. Reboot device so that the xposed module is active and then launch holo themer.
3. Edit the Theme of the apps that normally dont work to "Material Dark"
4. Open those apps and do your stuff.
5. Deinstall Holo Themer.
6. Reboot.
Unfortunately you cannot make apps like supersu permanently run correctly but at least you can edit the settings that way.
now things get really weird. Using holo themer version 3.0 I manage to boot up the fire tv with it still active .. although not every time. Like I had to restart it (unplug + replug) it 3 times and then it finally boot through. No clearing dalvik - nothing inbetween. Dont get it.. but at least its kinda workin now...
------
ADD: Well it seems to be that only cold-booting works with holo themer installed. When I make a restart through settings the device bootloops, when I take out the wall plug and make a cold boot it does boot up..
Does the Adobe Flash Player comes with the sideloaded Firefox app?
Greetings by Idijt
Thanks for listing Xposed Additions. Allowed me to remap my home key after the latest update!
aleins4u said:
Thanks for listing Xposed Additions. Allowed me to remap my home key after the latest update!
Click to expand...
Click to collapse
What FW where u on ? Where u able to remap it to AppStarter ? More info please.
Y314K said:
What FW where u on ? Where u able to remap it to AppStarter ? More info please.
Click to expand...
Click to collapse
5.2.4.1. You can remap to any application with the pro version, I remapped to FiredTV. Testing today revealed that the voice search button no longer works when using Xposed Additions though.
You can also remap the home button with GravityBox (LP), but it only allows you to remap double-tap and long press of the home button. But I did remap that to FiredTV successfully as well.
---------- Post added at 02:48 AM ---------- Previous post was at 02:43 AM ----------
zroice said:
Hey all,
I'm trying to figure out which xposed modules, mods and apps are the most useful ones for the rooted fire TVs and compile a list.
What I can recommend so far:
"Xposed Additions Pro"
to customize the keys of the remote control (longpress, double press, triple press shortcuts)
Adaway
No more annoying ads in youtube, twitch and other apps
Mozilla Firefox + Adblock Plus + Adobe Flash Player
Web-Browsing on Fire TV (only good with Mouse + Keyboard)
MarketHelper
spoof what device the firetv is to actually download apps through play store (usually says that apps are not compatible on 90% of the apps, to me)
AudioGlow
Nice AudioVisualizer of whatever audio is playing in the background (tuneinradio, mp3-player, kodi.. etc) - unfortunately a bit laggy or rather not on point with the audio.
Holo Themer (Xposed Module)
Open apps that do not seem to open on the FireTV (like SuperSu) - set the theme to "Material Dark" and they will open.
WARNING: Can cause bootloops. Use Version 3.0 as well.
Click to expand...
Click to collapse
Are you still able to use the voice search button in tandem with Xposed Additions?
> 5.2.4.1. You can remap to any application with the pro version, I remapped to FiredTV. Testing today revealed that the voice search button no longer works when using Xposed Additions though.
I tried to re-map the home button to start FireStarter application by installing Xposed Additions pro via Google play store on my rooted Fire TV (first gen) with pre-rooted 5.2.4.1 ROM but no luck. Am I missing something?
aleins4u said:
5.2.4.1. You can remap to any application with the pro version, I remapped to FiredTV. Testing today revealed that the voice search button no longer works when using Xposed Additions though.
You can also remap the home button with GravityBox (LP), but it only allows you to remap double-tap and long press of the home button. But I did remap that to FiredTV successfully as well.
---------- Post added at 02:48 AM ---------- Previous post was at 02:43 AM ----------
Are you still able to use the voice search button in tandem with Xposed Additions?
Click to expand...
Click to collapse
rosinatte said:
> 5.2.4.1. You can remap to any application with the pro version, I remapped to FiredTV. Testing today revealed that the voice search button no longer works when using Xposed Additions though.
I tried to re-map the home button to start FireStarter application by installing Xposed Additions pro via Google play store on my rooted Fire TV (first gen) with pre-rooted 5.2.4.1 ROM but no luck. Am I missing something?
Click to expand...
Click to collapse
Guys try out the XPosed Edge Pro. It seems to be the most complete XPosed module that is compatible with FTV devices. It should even be compatible with FireOS 3.
It brought back all the options FireStarter used to have. Using it with AppStarter. Plan to play with it more in the future too.

Things to do with a rooted fire tv!!

Are you someone who just got their Fire TV rooted and don't know exactly what you can do with it being rooted? Or maybe you haven't rooted yet because you are unsure of what you can do with it rooted? Well hopefully i can shed some light on this with a little guide on things to do, along with some tips and tricks.
First let me get started by saying never forget to make a backup of your Fire TV via TWRP before making changes or tweaks. This is not to freak you out or disparage its just good practice ii have learned in rooting devices. I will cover TWRP later.
One of the best things to come along in the rooting world of android is Xposed installer. In short Xposed is a framework apk that allows users to modify/ customize their devices. This is not done by Xposed Installer per say but the modules that you download with in Xposed installer. So i will show how to install it, how to use and modules that will be beneficial use for Fire TV fyi mouse is need to navigate Xposed.
Xposed installation​
1. We need to download the following BusyBox a program that most rooted apps are dependent on here Xposed Installer v3.1.5 here along with Xposed Framework x89 sdk22 arm64 here
2. Install BusyBox however you install side loaded apks. Open BusyBox and click the install button on bottom right. On SU prompt screen grant root access. As you should for root apps you install.
3. Install Xposed Installer, there is no need to open after install because without Xposed Framework installed it doesnt work.
4 Place the Xposed v89 zip onto Fire TV internal or external storage is your choice just remember where so you can point TWRP to it.
5 Reboot into TWRP recovery, choose install, point TWRP to the Xposed zip and on right side of options choose install zip. Let TWRP run its script when it says complete simply reboot and voila Xposed is installed. NOTE it is NORMAL for the first boot to take 10 min after Xposed is installed.
Xposed Tutorial and Modules​
Open Xposed installer on be careful screen prompt click box to don't show again and ok. The 3 line icon on top left is menu button. Module option is where you can see and activate modules you install. Download option is where we search for and install modules. After you download a module Fire TV will prompt you to install. Note modules wont work until activated and a reboot.
Modules i find beneficial and know are SAFE are the following​Boot Manager- this allows for you to choose what apps start on boot.
RootCloak- this is designed to hide root app detection. Im assuming it still will hide root but could be wrong worth shot right
Xposed Edge- this is the FUN one that allows a fair share customs tweaks. My fav is remapping of remote buttons ie home button goes to alternative launcher, double tap home opens netflix. Which is great for 3rd party remotes that have a lot of buttons. NOTE There is a pro version as well Note- whenever you make changes in edge you may have to reboot for changes to effect.
DISCLAIMER be careful some modules may cause problems like bootloop and worse so research before you install modules to see if they are compatible​
Other Apps​
These are apps recommended or useful for rooted devices and for Fire TV use​ADBLink-allows you connect PC t to Fire TV via adb can install apks, push/pull files, run adb shell.
Easy Fire Tools- Android app that connects to Fire TV via adb can install apps from your android device onto Fire TV, transfer files and other features.
Root Explorer- these apps allow you to manage files but also a way to install side loaded apps, find one that is root friendly so you can access system folders if ever needed.
AdBlocker- we all know why we want one for all my rooted phones always been partial to adaway.
Alternative Home Launcher- who does like Fire TV launcher, really Karen of course you would!
TV App Repo and APK Editor- For those who do use alternative launcher i mention these because TV App Repo allows you to make bookmarks into apks. APK Editor to change the icon and name of TVApp Repo apks because the names and icons are generic.
TWRP​
Finally the benefits and how to use TWRP. This allows users to make a backup images of device and ability to restore it when **** goes wrong. You can also do a factory reset.
Backup- after you choose backup from main screen choose select storage and choose storage then click swipe to backup. These can take a while to do seemed like 20 mins or so. Whatever storage you chose will be the default storage until you change it. Note- I have a backup image and its size is 4.5gb so id recommend you need some sort of external storage for these. If there is not enough space backup can not be performed.
Restore- performed same way as backup.
Factory Reset- Just wanted to mention don't forget if you do this and have a backup image on Fire TV internal storage you will lose it.
Hope this helps out​
@g422
Thanks for the write up!!!
To be honest, the benefits of rooting appear to be somewhat underwhelming, at least, for the Fire TV. Not a single killer feature/application ...
I do know that it is more convenient to have root than not, but appears to be in pretty subtle ways.
My main use is between SmartYouTubeTV, and Netflix. If I fumble through the Amazon launcher, I am there, and life is good!
Am I missing something?
bibikalka said:
Am I missing something?
Click to expand...
Click to collapse
Yes, you didn't read the OP He gives many examples of use for root, if those aren't valuable to you, then root isn't for you.
ldeveraux said:
Yes, you didn't read the OP He gives many examples of use for root, if those aren't valuable to you, then root isn't for you.
Click to expand...
Click to collapse
Hmm, just for the record, pretty much every tablet or phone (except a couple of real cheap deals) I have in my household are rooted! So I do see good value in root on those devices.
It's just that I struggle with root utility on Fire TV devices. As in - "why bother?"
I see that the OP likes Xposed Edge for button remapping, so if that's your cup of tea, that's a killer feature to get root for. I myself religiously correct Chrome look on tablets using Xposed/App Settings (link), which very few others seem to care about. But I want to see more of these killer features for Fire TV! Suggestions?
Btw, I am not being adversarial or critical, just very curious. Which itch are people scratching with root on Fire TV???
bibikalka said:
Hmm, just for the record, pretty much every tablet or phone (except a couple of real cheap deals) I have in my household are rooted! So I do see good value in root on those devices.
It's just that I struggle with root utility on Fire TV devices. As in - "why bother?"
I see that the OP likes Xposed Edge for button remapping, so if that's your cup of tea, that's a killer feature to get root for. I myself religiously correct Chrome look on tablets using Xposed/App Settings (link), which very few others seem to care about. But I want to see more of these killer features for Fire TV! Suggestions?
Btw, I am not being adversarial or critical, just very curious. Which itch are people scratching with root on Fire TV???
Click to expand...
Click to collapse
I sort of see your point, but I think the root version of Mouse Toggle works, while the non-root doesn't. At least that's been my experience. Also, can you block updates without root?
I took no offense to your comments bibikalka. I am inclined to agree that there is a limit of what to do with rooted fire tv especially compared to a phone or tablet. I started this thread to give back to xda who has kept my multiple devices over years rooted. Thread was also done in hopes of getting ideas to do and/or sharing of apps that can be helpful especially now that rooting is allowed for the general masses just not those who were able to jump on board early.
ldeveraux said:
I sort of see your point, but I think the root version of Mouse Toggle works, while the non-root doesn't. At least that's been my experience. Also, can you block updates without root?
Click to expand...
Click to collapse
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
#1 reason I root a fire TV box is so I can use large NTFS drives on the USB port.
Can someone point to me how to fix sd card write permissions. I tried xiinternalsd for xposed but when i open it goes to amazon home screen
g422 said:
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
Click to expand...
Click to collapse
Right, so blocking updates only when rooted.
ldeveraux said:
Right, so blocking updates only when rooted.
Click to expand...
Click to collapse
yeah i just re read what ya posted i see what ya meant
Imho top reasons for it are Xposed Edge Pro, ad blocking via AdAway (if you use the browser) and finally, the updates issue. While unlikely, it's not impossible for Amazon to get crackin and stop the use of certain third-party apps (NIMH is a giveaway)
Edit: forgot one important one, "debloating" the OS, whether by blocking the startup or disabling packages you don't want/need to give more cpu and memory to apps you do
Without root access, it's Amazon's device; with root access, it's now your device.
g422 said:
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
Click to expand...
Click to collapse
ldeveraux said:
Right, so blocking updates only when rooted.
Click to expand...
Click to collapse
g422 said:
yeah i just re read what ya posted i see what ya meant
Click to expand...
Click to collapse
For a while, updates could be blocked without root, but Amazon fixed that hole:
https://forum.xda-developers.com/fire-tv/general/disable-ota-fire-stick-t3667978
But! You want to block updates so you don't lose root, so it's a bit circular. If you don't have root, you don't care, and just update as per Amazon otas. Btw, I do have updates blocked on my fire sticks
Anyway, please keep the conversation going! We should develop a good set of must have features which are only available via root.
The main reason I root now is to debloat. Go as barebones as possible in order to improve performance. I kill all possible services that are absolutely unnecessary. I've removed Amazons GUI and use Appstarter. I just like a clean fast experience.
Thanks for this but u all do know u can connect to a PC wirelessly via adb without root. It's the only way I have ever added apps to my stick. Find your sticks individual ip. Open terminal on a pc, adb connect ipaddress. Then adb devices, a prompt will pop like on your phone asking to allow device or not. Click always or yes whatever. Then u do adb install draganddropwhateverapphere. Loads up in seconds depending on apk size. U can even use your phone if u have the adb platform tools magisk module installed on your phone. I install apps to my stick from my OnePlus 6t
fullofhell said:
Thanks for this but u all do know u can connect to a PC wirelessly via adb without root. It's the only way I have ever added apps to my stick. Find your sticks individual ip. Open terminal on a pc, adb connect ipaddress. Then adb devices, a prompt will pop like on your phone asking to allow device or not. Click always or yes whatever. Then u do adb install draganddropwhateverapphere. Loads up in seconds depending on apk size. U can even use your phone if u have the adb platform tools magisk module installed on your phone. I install apps to my stick from my OnePlus 6t
Click to expand...
Click to collapse
Ummm, or you know just use the Apps2Fire app lol. No magisk module or root needed. You're welcome.
JUSTINMARMER said:
Ummm, or you know just use the Apps2Fire app lol. No magisk module or root needed. You're welcome.
Click to expand...
Click to collapse
I am saying I never need root or anything to use adb and install apps wirelessly. I have done this for the past year with NO ROOT. Don't need it for sideloading apps. Adb connect ipaddress, then adb install dragdropapp from PC into terminal. No root or magisk needed. I always have a rooted phone and that's where the magisk module comes in. On a PC u can load them to a stick out of the box.
fullofhell said:
I am saying I never need root or anything to use adb and install apps wirelessly. I have done this for the past year with NO ROOT. Don't need it for sideloading apps. Adb connect ipaddress, then adb install dragdropapp from PC into terminal. No root or magisk needed. I always have a rooted phone and that's where the magisk module comes in. On a PC u can load them to a stick out of the box.
Click to expand...
Click to collapse
Yep, that's exactly what you said before. Not sure why you are repeating it.
JUSTINMARMER said:
Yep, that's exactly what you said before. Not sure why you are repeating it.
Click to expand...
Click to collapse
Cuz u aren't understanding. If u read your comments, then mine, you would see it seems u think I'm saying one would have to have root to use adb install. U do not.
fullofhell said:
Cuz u aren't understanding. If u read your comments, then mine, you would see it seems u think I'm saying one would have to have root to use adb install. U do not.
Click to expand...
Click to collapse
That is 100% incorrect. I see now you have a reading comprehension disability. I can't imagine how hard that must be for you and I empathize.
Obviously root is needed for magisk modules. I suggested an app to help all those without root.
Bless your heart.

Categories

Resources