Not sure where to post this so if its not correct, please move it.
I have fire tv, rooted, current Rom as of 1 month ago. using gotham 14x. never had any problems, but today got message amazon fire tv is low on memory. (I have it using xposed to boot right to xbmc) so as soon a I cleared the message, it goes back to Launch Xbmc and I get the default blue splash screen, but there is no menu, and without any menu, I have no way to control anything, i can't get to any other menus. Kind of stuck, lol.
I got the low on memory message but before then everything was working fine earlier today, i went to watch a movie, got the normal, please wait popup in bottom right, it never went away, i powered down, powered back up, but now it loads xbmc without any menu.
I hope this makes sense, i tried looking for the same type of issue but i couldn't find it.
Related
I have a friend here at work that has a Kindle Fire and some how he lost his Action Drop Down Menu that allows him to get to settings and all that. He took it to Bestbuy where he bought it and they were not able to help him. So I suggested to him to root it and then put an Android OS on it. He was telling me with the root directions he found they require him having to access the settings area which he can not do with out the drop down action menu. I told him about XDA and how awesome this site was, so I decided to inquire on his behalf. Does anyone have any suggestions for him?
after plying with it myself i see there is more to this than just the action drop down missing. The whole top bar is not there. The time, wifi indicator, and notification bar is missing. There seems to be the background image of the shelf and all that is not there as well. it is as if there are files missing at first glance at this. Not sure how this can happen but... He says that his daughter uses it for facebook and other social apps, but there is something majorly missing on this one. Just to give an update...
If signed in a google account on kindle, go to google play store with PC/Mac and install a different launcher.
I it a Fire 1 or 2.
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
If signed in a google account on kindle, go to google play store with PC/Mac and install a different launcher.
I it a Fire 1 or 2.
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
it is currently in my possession for a few hours as I try and figure this out. He just told me that this is a Kindle Fire HD i thought it was just a Kindle Fire. Whenever you try and access anything you get a blank screen. it is on but nothing shows up. In order to get back to the home screen you have shut it down (soft reset) then then turn it back on. this is very weird. however i do have access to the file system when I plug it into my pc.
I try and go to anything the first thing that comes up is that there is no connection. I hit the button for wifi setting then it goes to a blank black screen. in order to get back to the home screen i have to soft reset it again.
I don't even think there is a way to factory reset with out being able to have that drop down menu to access the settings is there?
Should be a reboot to recovery option when it's booting up, in recovery you can factory reset
Sent from my Amazon Kindle Fire using Tapatalk
I am also having the exact same problem and can’t figure out how to access the settings without a drop down menu, HELP!
nothing exactly meaningful, just wanted to mention in case other people had similar experience.
well also it may have implications after the next OTA / post-root-if-that-happens
for reference: to be safe, for a while now I have had both of the known IPs blocked on my router.
- maybe a week ago, tried to scroll into Home->Recent and got a solid blue screen for 5-10 seconds. didn't touch the device, it auto-reboots, then everything ok. version number unchanged still etc_02.etc like we all have.
- few days after that, Prime TV was playing and kept playing fine, but usb went sideways. reconnecting usb, power looked ok but still nothing. tv app kept playing 100% fine just no HID. stupidly did not try the remote. recycled power, and got stuck at (white-logo)amazon screen. power-off, wait a while, tried a few more times and always stuck at (white-logo)amazon screen.
-- removed the 2 blocked URLs from my router and booted, everything back to normal. (version number still same etc_02.etc)
wasn't even going to bring all of this up, who knows I may have a flaky KFTV, but then
- today got the solid blue screen again trying to scroll Home->Recent*. as before, box eventually rebooted itself, without having to do anything, and everything normal again. (and this with both IPs still re-unblocked)
if nothing else reminded me to re-block both URLs lol. but it is a very small and random sample size so far.
semi-weird: the first blue screen, and the usb breakage, both very hot days here, it almost could have been temp-related (but box did not feel warmer than usual) - but then blue screen today is bad weather / cold here, so yeah probably not.
*since it happened same way both times, could easily just be some bug about Recent, or in the KFTV Launcher
tarvoke said:
nothing exactly meaningful, just wanted to mention in case other people had similar experience.
well also it may have implications after the next OTA / post-root-if-that-happens
for reference: to be safe, for a while now I have had both of the known IPs blocked on my router.
- maybe a week ago, tried to scroll into Home->Recent and got a solid blue screen for 5-10 seconds. didn't touch the device, it auto-reboots, then everything ok. version number unchanged still etc_02.etc like we all have.
- few days after that, Prime TV was playing and kept playing fine, but usb went sideways. reconnecting usb, power looked ok but still nothing. tv app kept playing 100% fine just no HID. stupidly did not try the remote. recycled power, and got stuck at (white-logo)amazon screen. power-off, wait a while, tried a few more times and always stuck at (white-logo)amazon screen.
-- removed the 2 blocked URLs from my router and booted, everything back to normal. (version number still same etc_02.etc)
wasn't even going to bring all of this up, who knows I may have a flaky KFTV, but then
- today got the solid blue screen again trying to scroll Home->Recent*. as before, box eventually rebooted itself, without having to do anything, and everything normal again. (and this with both IPs still re-unblocked)
if nothing else reminded me to re-block both URLs lol. but it is a very small and random sample size so far.
semi-weird: the first blue screen, and the usb breakage, both very hot days here, it almost could have been temp-related (but box did not feel warmer than usual) - but then blue screen today is bad weather / cold here, so yeah probably not.
*since it happened same way both times, could easily just be some bug about Recent, or in the KFTV Launcher
Click to expand...
Click to collapse
This started to happen to me about a week ago did you ever get it sorted out.
Hello,
Got an AFTV at staple the other day. I tried to follow the aftvnews guide "How to setup a new AFTV...".
Apparently my AFTV was pretty old since the initial unplug/plug trick did not work and the box was always stuk on waiting to download the update. I finally let the update run through and ended up with Firmware 51.1.0.2_user_510058520.
After that I tried to root the AFTV. For this I used adbFire. I was able to connect to the box (no internet connection at that time) and click on the Towelroot option. I did click on "Make it ra1n" and wait for a very long time. I never saw any message indicating that it succeded or failed. With the remote I ended up going back to the previous menu. I tried to install SuperSu but that did not work. Su was not installed. After rebooting the box, I get the back and white Amazon logo and then the screen goes black. The TV shows the selected input as if the AFTV is not sending any signal. I tried to plug the internet cable (with the 2 domains blocked) and the AFTV finally goes from the Orange blicking led to the Blue one but it's still stuck after the amazon back and white logo. I did try the ALT-I-PrntScr (which had worked previously when I was trying to prevent the update to install, I managed to get into recovery and do a factory reset ,so I know the keyboard itself is OK). But this time ALT-I-PrntScr only get the box to restart and brings me back to the Amazon black and white logo that disappear after a minute.
Nevertheless, I can still access the box from an adb shell, adbFire can connect to the AFTV. But since I no longer see any menu on the screen I can't attempt to reroot from adb fire.
A reboot recovery does not work as it's not authorized.
su command is not found , so it would confirm supersu did not install (properly). What's weird though is that if I do a ps, I see a process "u0_a1 6199 328 476352 18640 ffffffff 00000000 S eu.chainfire.supersu"
Any idea how I can unstuck the box ?
Thank you.
Some info for people in the same situation, the issue was that Towelroot needs internet access to complete.
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I have the same exact issue right now, probably that same update yours downloaded from 2 weeks ago:
https://forum.xda-developers.com/fire-tv/general/fire-tv-stuck-amazon-logo-adb-t3809305
This guy had the same problem too, and he has a big list of things to try, none of which worked for me:
https://forum.xda-developers.com/fire-tv/help/fire-tv-remains-stuck-amazon-firetv-t3561797
Mine's unrooted on the latest version, so I guess I can't root and reinstall rom. I'd hate to have to throw this away it's only 2 years old. I have a 5 year old Roku that still runs great.
"Perfect" timing I guess with Prime Day coming up?
Edit: couple more guys having the same issue recently, sounds like a mass bricking going on
https://forum.xda-developers.com/fire-tv/help/firetv-box-white-amazon-logo-blank-t3472867
https://forum.xda-developers.com/fire-tv/help/fire-tv-stucks-white-amazon-logo-t2889867
https://forum.xda-developers.com/showthread.php?t=2799779&page=7
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
johnusesandroid said:
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
Click to expand...
Click to collapse
I wish I had the same luck like you but i tried different tv's, all the ports availble and different HDMI cables but still no luck.
Anyone able to find a solution to fix it? or should I just throw it out?
DhiJay23 said:
Anyone able to find a solution to fix it? or should I just throw it out?
Click to expand...
Click to collapse
Sorry you weren't able to fix. Before you throw away, try contacting support. Not because they can fix it, they most probably can't. When I had problems with mine, I contacted them and they gave me a $15 credit off of a new one because I was out of warranty. This was a couple days before Prime Day so I was able to snag a new one for really cheap. Plus my old one started working again, so I now have 2 Fire TVs
Hey guys,
I was watching a video on the FTV and the video went off and the screen started to flicker. I unplugged it and restarted it and it goes to the Amazon logo screen then goes black and starts to blink again. I also tried a reset by the remote and nothing.
I changed out my cables to make sure that wasn't the problem,and it wasn't. The cables that are used for the FTV was used on another piece of equipment and it worked fine.
Suggestions? Any thing else to try?
It's less than a month old and it it's just fried,then I'll take it back and get another one. Thanks
are you rooted and using kodi as your launcher? i had this problem yesterday it was like kodi changed to a resolution that my tv didnt recognize if i held the home button it brought up sleep, screen mirror, and settings i chose settings wiped kodi data and all was good again.
My FireTV is stuck in boot. I get a black screen with white amazon logo (no orange colours). The white light slowly flashes on the front box, and eventually my TV eventually gets a no signal response.
The device registers the remote, (every click gives the white light comes on) but I am unable to go into recovery (Right button + Back Button). Opening up ADBLink, I am able to connect to the device by IP address, and I can reboot the device remotely and I can enter reboot recovery. When I enter reboot recovery, the FireTV reboots and in red writing I get
"Your Amazon Firetv will restart in a few minutes, and show resume normal operation, If it does not restart please unplug the power cable and plug it back in to force a restart. If you need assistance please contact support at Amazon" .
However nothing happens, and when I restart I get stuck at the white amazon logo.
I have tried 3 separate keyboards and tried ALT + Print screen, or ALT + i + Print Screen, or ALT+ Home, or ALT + i + home. None of them worked.
It has the stock OS installed (Dont know which version but assume the latest update), and the only action beyond normal operation has been the sideloading of a couple of common APKs. (No rooting, bootloader it locked). As it is out of warrrenty Amazon are little help (15% discount on next FireTV purchase).
Is there anything I can do, or is my box now a paper weight ?
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
rainman74 said:
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
Click to expand...
Click to collapse
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
abfmdf said:
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
Click to expand...
Click to collapse
Good luck to you! :fingers-crossed: