• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Solution for no Root and no Accessibility Service on Fire TV 4K Mantis on Version 6.2.8.1

Search This thread

Spamm00r

Senior Member
Nov 21, 2011
67
5
Hi,

I recently bought a new Fire TV 4K that came with Version 6.2.8.1 out of the Box. It also has a Serial Number containing VM in it. According to some posts here this means, that it has some efuses blown and the USB Download Mode disabled in its bootrom, which makes it impossible right now to root or downgrade it.

The reason I need to downgrade is that I need to automate some tasks on the Fire TV for example with tasker. For exmaple I need the Fire TV to switch the Input at Boot automatically. It does this only when I press the home button. Automating this with tasker however requires the Accessibility Service, which Amazon has removed in current Versions of the Firmware. So the only solution is to root it or go back to older Firmwares, and both ways seem to have been blocked by AMazon right now.

Is this the latest information or are there solutions for this device to still root it?

And are there alternative ways to automate for example Home button press without root and Acessibility Service?

And which Fire Tv Stick can still be rooted right now even with the latest Firmware installed?

Any help would be appreciated.
 

JohnC

Senior Member
May 5, 2007
606
130
Amazon Fire TV
Google Pixel 4a
According to this post, only versions with "VM190 or higher" have the fuse blown.


So maybe your unit has a s/n lower then VM190.
 

Spamm00r

Senior Member
Nov 21, 2011
67
5
Yeah my Serial contains *VM081* but I bought it far later than the post you mentioned. Also that post was made before Version 6.2.8.1 was released and efuses burned, which apparently does not allow downgrading anymore. And the guy who found the exploit has not posted anymore since 2019.

My understanding is that the USB Download mode being disabled and the efuses blown are two different things.

I have not yet read any comment on wether you can root a fresh out of the box device that has Version 6.2.8.1 on it.

And additionally newer devices seem to have no USB Download mode.

Is there a way to check whether my devices efuses are blown or not? And whether my device has USB Download mode before I open and short the device. RIght now I can still send back the device, but not once I have opened it. I don't wanna find out after opening the device that I can not root it.

So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.

ALso it would help to know wether the efuses burning only is limted to the 4K model. In that case I could get a Lite or Version 2 of the Fire TV. Unfortunately I have not found any FAQ regarding such questions.
 
Last edited:

Sus_i

Senior Member
Apr 9, 2013
1,265
516
My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
No, it's most likely the same thing...
Is there a way to check whether my devices efuses are blown or not?
Yes, you can short the stick, connect usb and watch in lsusb. It will show no sign of the stick if the efuse is gone.
You can also connect an USB TTL UART Adapter, while doing the shorting. Then the log shows you that the boot-process goes to halt.
So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.
The root/unlock method based on BR DL-Mode (via shorting), will not work on any 4k stick running 6.2.8.0 or later, regardless of the serial number.
The new Lite Stick, the new fTV Stick and the newest fTV 4K-Max Stick are also BR DL-Mode disabled.
 
  • Like
Reactions: AlexViean

Spamm00r

Senior Member
Nov 21, 2011
67
5
So its game over for the current Fire TV Stick Models in regards to rooting right?!

This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.

I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.

I have already a few ideas.
My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.

All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.

Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.

My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.

I hope that works out.

For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
 
  • Like
Reactions: JohnC

Shaikh Amaan FM

Senior Member
Oct 30, 2016
63
24
Mumbai
So its game over for the current Fire TV Stick Models in regards to rooting right?!

This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.

I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.

I have already a few ideas.
My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.

All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.

Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.

My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.

I hope that works out.

For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
 

Shaikh Amaan FM

Senior Member
Oct 30, 2016
63
24
Mumbai
But the Tasker adb function needs it or how else can I make that Tasker function work?
You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
 
  • Like
Reactions: JohnC

Spamm00r

Senior Member
Nov 21, 2011
67
5
You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
Yes I agree the adb is active one the Fire Tv Stick and you can connect to it via wifi on port 5555.

But tasker still does not work with the adb function.

How did you make it work?

According to this:


You need to run this comamnd everytime you reboot.
 

Shaikh Amaan FM

Senior Member
Oct 30, 2016
63
24
Mumbai
Yes I agree the adb is active one the Fire Tv Stick and you can connect to it via wifi on port 5555.

But tasker still does not work with the adb function.

How did you make it work?

According to this:


You need to run this comamnd everytime you reboot.
I am not using Tasker. But as you said above that you'll use raspberry to issue adb tcip command to the stick to turn on wireless debugging, that's not needed.

As far as I think, you'll have a profile of device boot event in Tasker and in it you'll have a ADB Wifi action which will have the button press command.

If that's the case then it should work without any issue.
In ADB WiFi action, set host to 127.0.0.1 ( Just saw that this is optional as well )
If it doesn't works let me know, I'll try installing tasker in my stick and test adb wifi in it.
 
Last edited:

Spamm00r

Senior Member
Nov 21, 2011
67
5
How do you change volume in your volume change app without root?
Maybe I can issue the command for changing hdmi input the same way.
I am not using Tasker. But as you said above that you'll use raspberry to issue adb tcip command to the stick to turn on wireless debugging, that's not needed.

As far as I think, you'll have a profile of device boot event in Tasker and in it you'll have a ADB Wifi action which will have the button press command.

If that's the case then it should work without any issue.
In ADB WiFi action, set host to 127.0.0.1 ( Just saw that this is optional as well )
If it doesn't works let me know, I'll try installing tasker in my stick and test adb wifi in it.
 

Spamm00r

Senior Member
Nov 21, 2011
67
5
What's the adb command to change hdmi input?
There is no adb command to do that diretcly, but the Fire TV switches to HDMI source, if you press home button. SO I wanna issue Home key input via adb to make it switch the HDMI source to the Fire TV Stick.

"key_home": "adb shell input keyevent 3",

As far as I know you need to have root to issue CEC COmmands diretcly. Otherwiese you ahve to make a system method do that for you.
 

g96818

Senior Member
Dec 27, 2014
309
56
You probably bought one with a serial number of
G4N0VM081..... which is the new blown fuse version. You need to scour ebay for serial number
G070VM190..... or lower, then follow the current rooting guide. Make sure it's BRAND NEW and never been opened or else you're SOL since used sticks have probably been updated. New rootable sticks exists. I found half dozen on ebay a few months ago.
 
Last edited:

Shaikh Amaan FM

Senior Member
Oct 30, 2016
63
24
Mumbai
There is no adb command to do that diretcly, but the Fire TV switches to HDMI source, if you press home button. SO I wanna issue Home key input via adb to make it switch the HDMI source to the Fire TV Stick.

"key_home": "adb shell input keyevent 3",

As far as I know you need to have root to issue CEC COmmands diretcly. Otherwiese you ahve to make a system method do that for you.
Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.
 

Spamm00r

Senior Member
Nov 21, 2011
67
5
That would be awesome.

Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.
 
  • Like
Reactions: JohnC

Shaikh Amaan FM

Senior Member
Oct 30, 2016
63
24
Mumbai
That would be awesome.

Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
 
  • Like
Reactions: JohnC and Sus_i

Spamm00r

Senior Member
Nov 21, 2011
67
5
I have to correct myself about adb wifi out of tasker not working.

ADB Wifi does work depending on the app that you are using. Local ADB shell does not work, while Remote ADB Wifi app does work.
The adb plugin for tasker does not work, but the adb wifi action from Tasker itself does work right away. In my earlier tests, other apps were just blocking adb wifi and I was confused and thought tasker's adb wifi is not working. But you have to properly close the abd wifi session with a "exit" command. Also the windows adb tool freezes and has to be killed in taskmanager. That is a source of error for testing adb on fire TV.

Also the adb wifi of tasker will not accept semicolon seperated commands. Shaikh Amaan FM's tool however does. In tasker You will have to create new task for every command and only issue one command. I don't know why, but thats the result of my troubleshooting.

Also you have to make sure that Tasker is properly bought, a trial version or a not genuine version won't work, as Tasker has signature checks implemented which silently brakes plugins without any obvious error messages.

Plugins however also do not work in Macrodroid.

So best thing is to use Remote ADB Shell app or Tasker's built in adb wifi task. Thatway you can mostly work around the fact that Fire TV is locked down, has no root and has accessibility services disabled.

So this is the solution to:

Solution for no Root and no Accessibility Service on Fire TV 4K Mantis on Version 6.2.8.1​


Thatway I'm able to make Fire TV switch input via tasker by issuing a home button press via adb.



That's the best thing you can do under these conditions that you can't have root on Fire TV right now.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    That would be awesome.

    Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
    1
    My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
    No, it's most likely the same thing...
    Is there a way to check whether my devices efuses are blown or not?
    Yes, you can short the stick, connect usb and watch in lsusb. It will show no sign of the stick if the efuse is gone.
    You can also connect an USB TTL UART Adapter, while doing the shorting. Then the log shows you that the boot-process goes to halt.
    So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.
    The root/unlock method based on BR DL-Mode (via shorting), will not work on any 4k stick running 6.2.8.0 or later, regardless of the serial number.
    The new Lite Stick, the new fTV Stick and the newest fTV 4K-Max Stick are also BR DL-Mode disabled.
    1
    So its game over for the current Fire TV Stick Models in regards to rooting right?!

    This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.

    I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.

    I have already a few ideas.
    My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.

    All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.

    Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.

    My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.

    I hope that works out.

    For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
    1
    But the Tasker adb function needs it or how else can I make that Tasker function work?
    You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
    1
    That would be awesome.

    Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
    Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.