5.0.5 breaks a lot??? - Fire TV Q&A, Help & Troubleshooting

Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed

JedSpink said:
Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
Click to expand...
Click to collapse
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....

bula1ca said:
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
Click to expand...
Click to collapse
Thanks for confirming 1), I tried AutomateIt too and it seems to have the same problem, so I suppose it's some sort of OS-level blocking of the kind of hooks that Llama and others used in the past? Guess they could argue it was a security improvement as allowing one app to start another could be abused...
Re: Wukong and side-loading being blocked.... I played a bit more and similar results to you.... I don't think the OS is deliberately blocking / preventing but there may be a bug or issue. For example if I do a reboot of the box then, say, Wukong, will work fine but then tried:
adb kill-server
adb start-server
adb connect xx.xx..x.xx
and then quick test with: adb shell
and get the error: device not ready.
Do a reboot, don't connect Wukong and try the above commands and adb shell works (quick test) and then any commands like adb push / install work too. But then Wukong seems blocked, e.g. may connect as mouse pointer but using the click function does nothing, or may not connect at all.
I'll try your fix of the ADB debug off/on instead of reboot; and see how that goes.
Fun times!

Wukong seems working fine for me but the remote mouse for fire t.v. unable to click

did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.

El_Nino9 said:
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
Click to expand...
Click to collapse
Lama is broken in OS5. Are you sure about it?

bula1ca said:
Lama is broken in OS5. Are you sure about it?
Click to expand...
Click to collapse
i never said llama works under OS5.
all i said it's not needed anymore due to kodi being available to launch from the apps menu on the left hand side.

Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
My remote mouse for fire tv works fine on OS5 prerooted rom

Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
Hi that's what I get sometimes, shows mouse pointer but click does not work. I find a reboot of the fire box fixes... what i've noticed it that once you have got say Wukong working then adb will not do adb - install or push: gets the device not ready error. Again a reboot will fix but then, say, Wukong won't work properly.
So it seems like something is blocking the other process - hence why I was wondering if a bug.
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed

JedSpink said:
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
Click to expand...
Click to collapse
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.

El_Nino9 said:
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
Click to expand...
Click to collapse
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.

JedSpink said:
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
Click to expand...
Click to collapse
i rooted my device and would use titanium back up. however kodi within itself has various tools.
they have an addon called back up and they also have other features.
however, on the stick, you can use storage easily unless you know how to adb well.
for simple use i would recommend titanium back up and then back up to a cloud service such as gdrive.
each user has different preferences.
if you aren't rooted just use the addon back up too or there is a 3rd party app that also does similar stuff which i've never used so can't help.
if you do decide to root, do not use supersume app after kingroot. stick to king root su until a rooted system image is released for the device. i used kingroot 4.1 from xda thread and despite it saying failed i had root.
if you're not comfortable don't do it

You can use Tasker instead of llama

Related

Rooted amazon fire tv booting to black screen.

Hello, today one of my rooted fire tv's became stuck on black screen and basically none of the important stuff can be accessed. This has happened to me a few times in the past and I am usually able to get the settings menu launched by playing around with the remote and the voice functions or if all else fails usually disconnecting my network will prompt the network connections menu which then will jog the main settings again and from there I can force quit and get it back up and running. But today I have gone through pretty much every method I know of and still no luck just a black screen. I run xposed on my fire tv so it is set to use spmc as the homescreen launcher. Any other methods out there that I have not tried? I wanted to avoid having to do a factory restore and reinstall everything if I can.
Nobody? LOl
danknasty said:
Hello, today one of my rooted fire tv's became stuck on black screen and basically none of the important stuff can be accessed. This has happened to me a few times in the past and I am usually able to get the settings menu launched by playing around with the remote and the voice functions or if all else fails usually disconnecting my network will prompt the network connections menu which then will jog the main settings again and from there I can force quit and get it back up and running. But today I have gone through pretty much every method I know of and still no luck just a black screen. I run xposed on my fire tv so it is set to use spmc as the homescreen launcher. Any other methods out there that I have not tried? I wanted to avoid having to do a factory restore and reinstall everything if I can.
Click to expand...
Click to collapse
If you just need to get into the settings menu, then connect to the Fire TV via ADB and run the following command to load up the settings menu:
Code:
adb shell am start -n com.amazon.tv.launcher/.ui.SettingsActivity
AFTVnews.com said:
If you just need to get into the settings menu, then connect to the Fire TV via ADB and run the following command to load up the settings menu:
Code:
adb shell am start -n com.amazon.tv.launcher/.ui.SettingsActivity
Click to expand...
Click to collapse
Is there anyway to access settings without abd. I know I can change resolution and restart from the remote is that all?
danknasty said:
Is there anyway to access settings without abd. I know I can change resolution and restart from the remote is that all?
Click to expand...
Click to collapse
The only other way is to hold the home button until the popup menu appears with the settings option. You have to be on one of the newer software version for that to work since it was recently added.

none sideload apps are working after latest update

Usually I let my fire tv update it self,cause I don't really care bout something going to be broken since I have no root in there..but not anymore since the last update (5.0.5)kick in,and that messed up one of my helpful app i used..Name is mouse toggle i used for the remote..uninstall tried to put it back but can't get none of the sideload apps to work with my fire tv..anyone out there kwn which one that's working or in PC..any links please? your help would be appreciate.I'm a none root user possibly will use for that purpose as well
Ths
im using this on 5.0.5 on my rooted AFTV2, my boys non rooted stick the one with the voice controller, & my AFTV stick without the voice controller & non rooted. Works on all of them, since you have installed OS5 things have changed in the settings of Firestarter which need to be changed, ADB only works with one device at a time so you have to look in your firestarter settings? try a fresh reboot? or reintall the app again?
Ok..deanr1977 I got it all figured..i now that i root, I'm waiting for a working costume recovery so I can install a nice launcher get ridded of somes bloats..thanks for your replied though
So do you own where to get the latest ADB software so I can try to block the update?
donjan3 said:
So do you own where to get the latest ADB software so I can try to block the update?
Click to expand...
Click to collapse
ADB -
http://www.aftvnews.com/how-to-setup-adb-and-fastboot-on-a-mac-or-windows-computer/
How to connect ADB to a Stick -
http://www.aftvnews.com/how-to-connect-to-a-fire-tv-or-fire-tv-stick-via-adb/
How to block updates -
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Commands -
adb shell
su
pm disable com.amazon.device.software.ota
exit
exit
PLEASE NOTE
On the su part be sure to select “Grant” if your Fire TV prompts you for superuser access!!!!
If this helps press that thanks button
Sent from my SM-G900F using Tapatalk

Fire TV 1 - Rooted on 51.1.5.3 Home Screen Issues

Hi all,
I have recently upgraded my FireTV 1 to the latest Prerooted stock image as per this forum page: https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
Software Version: 51.1.5.3_user_515040320
I upgraded from FireOS 3 so did the TWRP recovery first.
I also installed the su /sdcard fix as outlined in the forum page as well.
Everything installed correctly, and the FireTV boots correctly to the main screen. I am experiencing problems however:
The Home, Your Videos, Movies and TV Shows screens never load, just stay black with the three small dots bottom right of screen animating.
The Apps and Settings screens work as expected.
Connection to the Internet works, Netflix and YouTube apps work as expected, as does Kodi and others.
Individual application updates work, and are automatically triggered as expected.
I have no DNS/IP filtering setup in my router or hosts file on the FireTV
I have blocked updates from running with the following command: pm disable com.amazon.device.software.ota
Any advice on getting the rest of the interface working would be greatly appreciated.
fionn.colvin said:
Hi all,
I have recently upgraded my FireTV 1 to the latest Prerooted stock image as per this forum page: https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
Software Version: 51.1.5.3_user_515040320
I upgraded from FireOS 3 so did the TWRP recovery first.
I also installed the su /sdcard fix as outlined in the forum page as well.
Everything installed correctly, and the FireTV boots correctly to the main screen. I am experiencing problems however:
The Home, Your Videos, Movies and TV Shows screens never load, just stay black with the three small dots bottom right of screen animating.
The Apps and Settings screens work as expected.
Connection to the Internet works, Netflix and YouTube apps work as expected, as does Kodi and others.
Individual application updates work, and are automatically triggered as expected.
I have no DNS/IP filtering setup in my router or hosts file on the FireTV
I have blocked updates from running with the following command: pm disable com.amazon.device.software.ota
Any advice on getting the rest of the interface working would be greatly appreciated.
Click to expand...
Click to collapse
Since you are not blocking updates thru OpenDNS or thru your Router then my only advice is to do a cache wipe thru TWRP. Also make sure you don't have any VPN apps running. And also go into Settings/My Account & choose Sync Amazon Content & reboot.
Connect a keyboard to your FTV.
Then choose Launch Recovery.
Then go into WIPE & Choose Advanced Wipe.
From Advanced Wipe choose both "Dalvik / Art Cache" & "Cache" (This is not a Factory Reset).
Then Swipe to Wipe & restart your FTV.
It will take no more then 10 minutes to reload & everything should be unchanged (Apps, Settings, etc).
Then redo the ADB Method 1 FireOS 5 update blocking command. Just to make sure it is still blocking updates.
Use the "Troubleshooting" part of this guide for visuals:
http://www.aftvnews.com/how-to-installupdate-a-package-using-twrp-on-the-amazon-fire-tv/
If this doesn't work. Then maybe you will need to do a Factory Reset & reflash the whole PreRooted ROM.
Thanks for the advice.
Followed the steps suggested with the same results.
Would rather not factory refresh, however will do that if there re no other suggestions to try.
PS. I've also got a Fire Stick not rooted with latest firmware that works as expected, so shows there are no network reasons for it to not work on the FireTV
fionn.colvin said:
Thanks for the advice.
Followed the steps suggested with the same results.
Would rather not factory refresh, however will do that if there re no other suggestions to try.
PS. I've also got a Fire Stick not rooted with latest firmware that works as expected, so shows there are no network reasons for it to not work on the FireTV
Click to expand...
Click to collapse
You can try both forgetting the Wifi info & logging out & in of your Amazon Account.
Also restart your modem & router. And make sure you turned off both Featured Content.
Any chance you tried to debloat your device?
Guess you can try reflasing the PreRooted ROM without doing a Factory Reset. Only the same Dalvik & Cache. You would keep the same Apps installed. But you probably still need to reinstall the XPosed Framework. And update SuperSU. From what I remember.
After trying a number of different things I ended up performing a factory refresh following the guide from aftvnews
After doing that, blocking updates, re-installing the su sdcard patch, and then all my apps and settings everything is working as expected.
Thanks for all the suggestions. Happy to have everything back to normal again.
fionn.colvin said:
After trying a number of different things I ended up performing a factory refresh following the guide from aftvnews
After doing that, blocking updates, re-installing the su sdcard patch, and then all my apps and settings everything is working as expected.
Thanks for all the suggestions. Happy to have everything back to normal again.
Click to expand...
Click to collapse
Glad to hear everything has been resolved. :good:

Can't install Kodi on Fire TV1 anymore. Help!

Hello, I am about ready to give up on my Fire TV 1. Currently, I am on Software 51.1.6.3_user_516012020, and I apparently have root, bootloader, etc. However, due to low memory space, I ended up deleting (through ADB) the Amazon Home screen. Now nothing works. I did a factory reset (probably a bad idea), and still can't get anything to work. I have tried installing Kodi 17.4 with the Downloader app, and get a "parse error." Installation fails when I tried to install through ADBFire. Finally, install fails on App2Fire as well, with the message: "Upload successful, ERROR listing packages: Broken pipe."
I'm at a loss here. Any help would be greatly appreciated. I would even ship the device to you, if you could fix it! Should I just upgrade to a Fire TV 2 at this point?
Don't know if this will make any difference, but try sideloading the firestarter / appstarter app ( name was changed over time). In the app settings is the option to directly install the latest version of kodi. I've had a few issues in the past where I couldn't get it to install using adbfire, but it worked when using the appstarter / firestarter gui interface. I believe firestarter or appstarter still boots directly into its gui interface if you've got root. If you can sideload the appstarter or firestarter apk, reboot the fire tv and see if it boots into the app's gui interface. Go to settings and you'll see a kodi option allowing you to download kodi 17.4. No guarantees, but worth a shot.
Come to think of it, you've probably bricked it. See if there's anything that's useful in this article
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/

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

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.
According to this post, only versions with "VM190 or higher" have the fuse blown.
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
So maybe your unit has a s/n lower then VM190.
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.
Spamm00r said:
My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
Click to expand...
Click to collapse
No, it's most likely the same thing...
Spamm00r said:
Is there a way to check whether my devices efuses are blown or not?
Click to expand...
Click to collapse
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.
Spamm00r said:
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.
Click to expand...
Click to collapse
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.
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.
Spamm00r said:
So its game over for the current Fire TV Stick Models in regards to rooting right?!
Click to expand...
Click to collapse
That is valid for the current methods. There is still further development, but development needs time...
So it's best if you take a look into the xda forums from time to time
Spamm00r said:
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.
Click to expand...
Click to collapse
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
Shaikh Amaan FM said:
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
Click to expand...
Click to collapse
But the Tasker adb function needs it or how else can I make that Tasker function work?
Spamm00r said:
But the Tasker adb function needs it or how else can I make that Tasker function work?
Click to expand...
Click to collapse
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.
Shaikh Amaan FM said:
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.
Click to expand...
Click to collapse
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:
https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html
You need to run this comamnd everytime you reboot.
Spamm00r said:
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:
https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html
You need to run this comamnd everytime you reboot.
Click to expand...
Click to collapse
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.
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.
Shaikh Amaan FM said:
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.
Click to expand...
Click to collapse
Spamm00r said:
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.
Click to expand...
Click to collapse
What's the adb command to change hdmi input?
Shaikh Amaan FM said:
What's the adb command to change hdmi input?
Click to expand...
Click to collapse
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.
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.
Spamm00r said:
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.
Click to expand...
Click to collapse
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.
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.
Shaikh Amaan FM said:
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.
Click to expand...
Click to collapse
Spamm00r said:
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.
Click to expand...
Click to collapse
[APP][NO ROOT] ADB on Boot | Run adb commands at boot automatically
How to use? 1. Enable ADB Debugging from Fire TV settings 2. In this app, add the adb commands that you want to execute on every boot 3. Set whether you want to display a Toast message on completion of command execution 4. Test the script if...
forum.xda-developers.com
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.

Categories

Resources