I have kodi 14.1 set to boot up first instead of the aftv home screen menu. Its a rooted aftv and I use xposed launcher to have kodi boot up first. The problem is that the aftv runs fine until kodi tries to launch but all o get is a black/gray screen. Im trying to get back into the aftv home menu but can't find a way to do so. Any suggestions or solutions?
Try turning off the launcher in xposed. They try launching Kodi from the applications settings. If this does not work, uninstall/reinstall Kodi and try it with a clean install. Back up your settings first but do not restore them until you confirm it works with a clean install. Then you can try to restore your settings.
If it doesn't work again, delete any advanced or user settings. Something is not configured correctly. Viewing the xmbc.log in the temp directory will get you to the source of the issue quickly too.
Sometimes the gray screen is on as long as 20 seconds for me. So be sure you are waiting long enough.
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.
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
Hello
i have a firestick running the latest software & kodi 16.1, everything works fine except kodi, when i install it initially it works fine then it will freeze or ill come back the next day and when i try open the app again kodi boots with the logo and then the screen goes black, force closing kodi from applications menu &/or clearing kodi cache changes nothing, i can see plugin updates flash up aswell as hear the navigations of the menu within kodi but its just black, i reinstalled kodi multiple times trying different custom builds each time & factory reset the stick aswell, with kodi reinstalled fresh it works for about an hour before this cycle begins again, only kodi is affected. Can anyone help as i cant send it back cuz i damaged the remote (altho it works fine)
Thanks.
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: