Develop Bugs

[Q] Stock Kindle Fire Stuck in Boot Loop (No Space on Device

I have a Kindle Fire that is stock and was NEVER rooted. It was being used and the user said it told them that the space was getting full. He began to remove apps in order to free up space (he's a novice user) and as he was doing this it rebooted and is now stuck in a boot loop. It will flash the kindle fire logo for a few seconds, screen goes black, etc.
I was able to get it connected and accept adb commands. I first was able to reboot it (./adb reboot) and then see it listed as a device (./adb devices). However, it still wouldn't boot up all the way. I've rooted a number of devices before and work with computers for a living so I'm pretty familiar with what's going on, however I know that every device is different. I looked into the different things to do with a Kindle Fire and decided I should try to push the fbmode app to the kindle. When I tried that I got an error saying:
failed to copy 'fbmode' to '/data/local/temp': No space left on device​
Any idea what I should do? I don't really want to root the device if I can just get it to run first. What is the best way to free up some storage so that it might boot again?
UPDATE: I've sent the wipe_data and wipe_cache commands to the KF. The screen kinda turns yellow for a second and then reboots and goes back into a boot loop. I can't seem to find another way to clean up space. Help?

Same here
I'm having the same problem. Did you ever find a solutions?

dawn12123 said:
I'm having the same problem. Did you ever find a solutions?
Click to expand...
Click to collapse
No. I'm still searching or hoping someone else might have an answer.

carlowahlstedt said:
No. I'm still searching or hoping someone else might have an answer.
Click to expand...
Click to collapse
I started a new thread about it. Here is the link:http://forum.xda-developers.com/showthread.php?p=40509965#post40509965

arestspubs
Thanks! Looks like you might be getting somewhere. I'll be anxious to see what you figure out.

Connect it to computer and navigate to Android/data/com.amazon.venezia/cache and delete the entire folder.
This took about 3.51 GB of the Kindle's 4.99 GB of Space!When clearing up after receiving a low storage notification, i saw that the Android folder had over 3 GB so i decided to see if i could clean anything over there.Once I saw that this had 3.51 GB in a cache folder,I googled com.amazon.venezia to see if i could delete it and this post was the first link.:good:Thanks this really helped me a lot and i have no idea why amazon follows this method

Recover / Hard Reset

Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.

jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
End Result. If you brick you box Amazon has no troubleshooting steps outside of rebooting the box. Once you get past that step and your still having an issue Amazon will issue you a replacement FireTV.
You will need to call Amazon as the Live chat is useless: 866-216-1072 Press 0 and ask to be transferred to the Fire TV department.

jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
Oh, boy. That is unfortunate. What did you do that lead to bricking your box?

I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.

if you bought yours at a local best buy and are a select customer, you may have an extended return policy.

You must have edited something you shouldn't have with the sqlite editor. I edited mine to allow package installs and did a factory reset and its all good. Did you only disable the updates through pm disable com.amazon.dcp or did you also edit the /etc/hosts? Lets get this figured out so others don't end up the same way.

Stupid question, did you pick TWRP as a method of recovery during the rooting process? I did that on my note 10.1 and boy did it mess up that tablet when I tried to recover it. Luckily I had Odin at the time.
Sent from my SM-N900V using Tapatalk

arman68 said:
I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.
Click to expand...
Click to collapse
Do you recall which sqlite editor app you used that caused the problem?

Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.

roustabout said:
Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.
Click to expand...
Click to collapse
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.

kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
i have only sideloaded a few apps , no root or root attempt was made before issues.
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
ps : amazon phone help mentioned reset on remote was hold right arrow key ( ie right circle ) and home button for 10 secs , to reset just the remote ,. nothing helped mine , i say its dead. another is on the way ,. he also said the lack of pairing with remote should not have stopped the ftv boot , it should have gone past first amazon screen . other than restarting the ftv by disconnecting power he offered no other reset method .

bkdg100 said:
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
Click to expand...
Click to collapse
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,

userr12 said:
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,
Click to expand...
Click to collapse
thanks ,. i called amazon they confirmed normal boot even without pairing ,. also said how to reset "just the remote" ,. right tab and home for 10secs.

kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
I'm trying to find that review now. so far nothing

fireTVnews.com said:
Do you recall which sqlite editor app you used that caused the problem?
Click to expand...
Click to collapse
I have reviewed the logs of what I did, and it was my fault:
I used a non-root SQLite editor, which means I had to give -rw-rw-rw- access to the database folder and content, which I did.
With the SQLite editor, all I did was to explore the database structure.
Once done, I restored the original permissions, fist -rw------- (chmod 660) on the database folder and database file itself.
Finally I restored read-only -r-------- (chmod 600) to the extra files (settings-*), and that was my mistake: I did not notice my chmod line had 2 entries, with the first one being the database folder (wrong)
If only I would have root write access to the file system with adb, I could easily fix it, with a simple chmod 660 on the database folder.
In hindsight, I was very careless to do that directly on the FireTV; I should have taken a copy of settings.db, and explore it on the PC.

Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
Yeah I took a look again today. Their search doesn't really drill down very well.

Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
kairnage said:
Yeah I took a look again today. Their search doesn't really drill down very well.
Click to expand...
Click to collapse
Here are all the reviews with the word "USB" in them on one page:
http://firetvnews.com/review_usb.html
I skimmed through it but couldn't find the elusive review.

@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)

roustabout said:
@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)
Click to expand...
Click to collapse
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?

fireTVnews.com said:
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?
Click to expand...
Click to collapse
I didn't mean to say you can't hose your device by changing settings with an editor, just that I don't think any of them change permissions. so using them to look but not change is pretty safe, IMO, and I'd hate to see folks discouraged from doing so.
I'm surprised that there's not a better onboard recovery on this device, or at least not one anyone's figured out how to get moving. I'dthink it'd be cheaper for Amazon if the devices had a viable recovery, or if there was a solid reset to factory which actually did a full reinstall of the OS.
Interesting about the fastboot mode - when i connect the FTV to my laptop using an A to A cable I don't get a device recognized in fastboot, but it may be down to not having a driver for it.

Strange issue with USB port at boot

This problem appears to be unique. Its not my intention to double post but I only just narrowed it down after some very lengthy posts.
It appears like I'm bricked except not really.
I boot up the fire TV with a USB drive inserted and it goes to amazon white logo to a staticky snow screen to an amazon colored logo then it just hangs on amazon yellow and black logo. Never boots to home screen.
If I unplug the flash drive and restart it, the aftv boots normally and works fine EXCEPT if you go to "Display" then press screensaver it sort of freezes. There's nothing to select and only the home button takes you back. All other apps load and work fine.
At first I thought it was a corrupted USB but all USB drives cause it to hang on boot after the snow screen. You can plug In a keyboard and it will boot to recovery and the keyboard functions properly. My system is no longer setup to mount drives persistently so it just makes this more puzzling??? The USB port works for keyboards and a mouse but if it detects a hard drive, mounted or unmounted I can't boot.
And the fact that that I'm prohibited from accessing the screensaver settings, but everything else functions great, just adds a layer of confusion I can't figure out.
This occurs with 2 different firmware versions 51.1.4.1 with boot menu and now 51.1.4.0 with NO boot menu. I want to flash the latest and boot menu for an extra way to access recovery but now I'm sort of afraid to try flashing something. It works and I can get to cwm right now. But every time I plug it in I worry it won't boot.

Do you have xposed installed? Or another launcher?
http://www.reddit.com/r/fireTV/comments/2ux6vx/i_bricked_and_unbricked_my_firetv_using_an/
Did you recently update Kodi and then not check if it has root privileges? Not sure if this has anything to do with it, just something that may have played a role if you were using Kodi as a launcher or where the home button directs you.

KLit75 said:
This problem appears to be unique. Its not my intention to double post but I only just narrowed it down after some very lengthy posts.
It appears like I'm bricked except not really.
I boot up the fire TV with a USB drive inserted and it goes to amazon white logo to a staticky snow screen to an amazon colored logo then it just hangs on amazon yellow and black logo. Never boots to home screen.
If I unplug the flash drive and restart it, the aftv boots normally and works fine EXCEPT if you go to "Display" then press screensaver it sort of freezes. There's nothing to select and only the home button takes you back. All other apps load and work fine.
At first I thought it was a corrupted USB but all USB drives cause it to hang on boot after the snow screen. You can plug In a keyboard and it will boot to recovery and the keyboard functions properly. My system is no longer setup to mount drives persistently so it just makes this more puzzling??? The USB port works for keyboards and a mouse but if it detects a hard drive, mounted or unmounted I can't boot.
And the fact that that I'm prohibited from accessing the screensaver settings, but everything else functions great, just adds a layer of confusion I can't figure out.
This occurs with 2 different firmware versions 51.1.4.1 with boot menu and now 51.1.4.0 with NO boot menu. I want to flash the latest and boot menu for an extra way to access recovery but now I'm sort of afraid to try flashing something. It works and I can get to cwm right now. But every time I plug it in I worry it won't boot.
Click to expand...
Click to collapse
Did you attempt to move the system data to the USB? It sounds like with the USB plugged in, your FTV is trying to load the system from it. I would look into the guides for how to move the system data to USB. I believe they have how to revert it back.

smartymcfly said:
Do you have xposed installed? Or another launcher?
http://www.reddit.com/r/fireTV/comments/2ux6vx/i_bricked_and_unbricked_my_firetv_using_an/
Did you recently update Kodi and then not check if it has root privileges? Not sure if this has anything to do with it, just something that may have played a role if you were using Kodi as a launcher or where the home button directs you.
Click to expand...
Click to collapse
That is precisely what I had done before I started with the usb/boot issue. I was using rbox TV mods with elmerohueso fire TV launcher. Used it for 2 days and really like it. So after attempting to push advanced settings that also involve deleting textures13db in kodi (done it many times before) the aftv seemed a bit sluggish/unresponsive. (Man, I'm drawing blanks as to exactly what was going and my next step) But I wound up adb uninstalling the fire TV launcher and reinstalling it. It worked,as I recall, but something was off, probably related to the home screen. The next day after asking some questions and searching a bit, it seemed safe to uninstall rbox mods via adb (but if I recall correctly I DID NOT uninstall xposed installer. Then I did a wipe userdata/factory reset in cwm. I set it up and it worked great. At some point I plugged in my flash drive and though I didn't make the connection at the time, that's probably when issues arose again. That's when I rebooted and had the first instance of static and hanging logo. Thought I might be bricked but it made no sense.
Next move was to attempt to get to recovery but it was late so I did it the next day. I unplugged my hard drive, for no other reason than I needed a USB keyboard (still didn't suspect anything) Of course it booted normally.
So my next move was to flash a new ROM. I was planning on this anyway because its a process people are using to fix Netflix issues. Everything went smoothly. Everything ran smoothly once done and to sum it up I had the same boot problem after plugging in USB. No further intervention, I FINALLY realized it was the USB drive causing the issue. And that's where I'm at now.
Sorry for the long explanation. But you hit the nail on the head without me giving you that launcher info. If you don't have any ideas to fix it I'm hoping you don't think this is irreversibly damaged. How do you think I should proceed?
I read that link. His issue is sort of related with different symptoms and apparently he didn't want to do a factory reset. I essentially did this through cwm and after that installed a new ROM...actually I'm fearing the worst. That fixing it might involve unrooting it and doing an actual factory reset. To be honest, I'd rather have a rooted aftv with no USB than unrooted since the USB drive is essentially useless in both scenarios.

Got the day off today and it would be great if anyone can give me a safe action to try from here. I'm thinking the simplest first, push elmerohueso repo (NOT the launcher itself) and enable those sleep settings to see if it brings anything back. Maybe I'll be able to access the screensaver?
A little more daring...reinstall xposed and rbox mods. Maybe there's a missing link that got removed and the result is I can't access screensaver? If all goes well (still booting) uninstall the normal kodi 14.1 and reinstall elmerohueso 14.1 launcher. If by that time the launcher functions properly (aftv boots with usb inserted and display settings are accessible again) I'll have more options to safely revert back to a normal build of kodi or keep it as is...Flashing the same or a different rom doesn't correct the issue.
Question--you could use rbox tv mods and xposed with no launcher installed, right? If all you wanted to do was modifiy the normal homescreen, right? I only just started using xposed like 4 days ago and I think I have a good idea of what it does, I didn't read that people used it exclusively to tidy up the busy aftv homescreen, but I could see myself using it just for that reason.
EDIT--a search in file explorer revealed Xposed-Disabler-Recovery.zip in storage/emulated/0/android/data
I'm not sure how it pertains, if at all. Does anyone know what this does? Basically I was looking for any remnants from exposed that was left behind. That's all I found.

KLit75 said:
That is precisely what I had done before I started with the usb/boot issue. I was using rbox TV mods with elmerohueso fire TV launcher. Used it for 2 days and really like it. So after attempting to push advanced settings that also involve deleting textures13db in kodi (done it many times before) the aftv seemed a bit sluggish/unresponsive. (Man, I'm drawing blanks as to exactly what was going and my next step) But I wound up adb uninstalling the fire TV launcher and reinstalling it. It worked,as I recall, but something was off, probably related to the home screen. The next day after asking some questions and searching a bit, it seemed safe to uninstall rbox mods via adb (but if I recall correctly I DID NOT uninstall xposed installer. Then I did a wipe userdata/factory reset in cwm. I set it up and it worked great. At some point I plugged in my flash drive and though I didn't make the connection at the time, that's probably when issues arose again. That's when I rebooted and had the first instance of static and hanging logo. Thought I might be bricked but it made no sense.
Next move was to attempt to get to recovery but it was late so I did it the next day. I unplugged my hard drive, for no other reason than I needed a USB keyboard (still didn't suspect anything) Of course it booted normally.
So my next move was to flash a new ROM. I was planning on this anyway because its a process people are using to fix Netflix issues. Everything went smoothly. Everything ran smoothly once done and to sum it up I had the same boot problem after plugging in USB. No further intervention, I FINALLY realized it was the USB drive causing the issue. And that's where I'm at now.
Sorry for the long explanation. But you hit the nail on the head without me giving you that launcher info. If you don't have any ideas to fix it I'm hoping you don't think this is irreversibly damaged. How do you think I should proceed?
I read that link. His issue is sort of related with different symptoms and apparently he didn't want to do a factory reset. I essentially did this through cwm and after that installed a new ROM...actually I'm fearing the worst. That fixing it might involve unrooting it and doing an actual factory reset. To be honest, I'd rather have a rooted aftv with no USB than unrooted since the USB drive is essentially useless in both scenarios.
Click to expand...
Click to collapse
I am also having the static screen if I have USB plugged in when booting. When I unplugged USB and started firetv, instead of running Kodi as launcher/home button it was running firedtv launcher. I had read your post previously but did not reboot the first until I had problems watching amazon prime video, which was fine after a reboot.
Any chance we have the same USB hub? I have the "amazon basics powered USB 3.0 4 port hub" that sells for around $15-20.
The only thing I put on the USB drive was/is the icefilms metadata and zips containing movie/TV background/fanart.
I also recently installed elmerohuesos version of Kodi 14.1 and previously had his version of 14.0. I just seen that I didn't grant root rights when rebooted. You can check in appearance - skin - settings - general - android options - check su permissions
---------- Post added at 12:46 PM ---------- Previous post was at 12:29 PM ----------
KLit75 said:
Got the day off today and it would be great if anyone can give me a safe action to try from here. I'm thinking the simplest first, push elmerohueso repo (NOT the launcher itself) and enable those sleep settings to see if it brings anything back. Maybe I'll be able to access the screensaver?
A little more daring...reinstall xposed and rbox mods. Maybe there's a missing link that got removed and the result is I can't access screensaver? If all goes well (still booting) uninstall the normal kodi 14.1 and reinstall elmerohueso 14.1 launcher. If by that time the launcher functions properly (aftv boots with usb inserted and display settings are accessible again) I'll have more options to safely revert back to a normal build of kodi or keep it as is...Flashing the same or a different rom doesn't correct the issue.
Question--you could use rbox tv mods and xposed with no launcher installed, right? If all you wanted to do was modifiy the normal homescreen, right? I only just started using xposed like 4 days ago and I think I have a good idea of what it does, I didn't read that people used it exclusively to tidy up the busy aftv homescreen, but I could see myself using it just for that reason.
EDIT--a search in file explorer revealed Xposed-Disabler-Recovery.zip in storage/emulated/0/android/data
I'm not sure how it pertains, if at all. Does anyone know what this does? Basically I was looking for any remnants from exposed that was left behind. That's all I found.
Click to expand...
Click to collapse
I do not believe Xposed is causing the problem. That file you found is to disable xposed in the event that a bad module caused a problem IR if you just wanted to uninstall xposed from CWM/TWRP recovery. If select to install xposed via recovery manually then there is also an installer exposed.zip with the one you found.
---------- Post added at 12:54 PM ---------- Previous post was at 12:46 PM ----------
So you have tried disabling exposed and that didn't fix it? Also you tried official Kodi 14.1 but have not tried reverting to 14.0?
Uninstalled firedtv to get the static on reboot.
Items that I am going to mess with to see if it fixes the problem.
1. adbfire persistent USB mounting
2. I stalling elmerohueso's kodi_14.0 again to see if that is it.
Nothing has changed via exposed so that should not be what is causing the problem.
Changing the usb mount to non persistent did not change anything for me.
If this is happening to more than one person at the same time as it is and it did not happen before maybe there is an amazon app that updated, but then a lot more people would be having the same problem, or maybe they are having the same problem but have not had to reboot yet so they do not know the problem exists.

smartymcfly said:
I am also having the static screen if I have USB plugged in when booting. When I unplugged USB and started firetv, instead of running Kodi as launcher/home button it was running firedtv launcher. I had read your post previously but did not reboot the first until I had problems watching amazon prime video, which was fine after a reboot.
Any chance we have the same USB hub? I have the "amazon basics powered USB 3.0 4 port hub" that sells for around $15-20.
The only thing I put on the USB drive was/is the icefilms metadata and zips containing movie/TV background/fanart.
I also recently installed elmerohuesos version of Kodi 14.1 and previously had his version of 14.0. I just seen that I didn't grant root rights when rebooted. You can check in appearance - skin - settings - general - android options - check su permissions
---------- Post added at 12:46 PM ---------- Previous post was at 12:29 PM ----------
I do not believe Xposed is causing the problem. That file you found is to disable xposed in the event that a bad module caused a problem IR if you just wanted to uninstall xposed from CWM/TWRP recovery. If select to install xposed via recovery manually then there is also an installer exposed.zip with the one you found.
---------- Post added at 12:54 PM ---------- Previous post was at 12:46 PM ----------
So you have tried disabling exposed and that didn't fix it? Also you tried official Kodi 14.1 but have not tried reverting to 14.0?
Uninstalled firedtv to get the static on reboot.
Items that I am going to mess with to see if it fixes the problem.
1. adbfire persistent USB mounting
2. I stalling elmerohueso's kodi_14.0 again to see if that is it.
Nothing has changed via exposed so that should not be what is causing the problem.
Changing the usb mount to non persistent did not change anything for me.
If this is happening to more than one person at the same time as it is and it did not happen before maybe there is an amazon app that updated, but then a lot more people would be having the same problem, or maybe they are having the same problem but have not had to reboot yet so they do not know the problem exists.
Click to expand...
Click to collapse
very interested in your issues as they seem to mirror mine. Unfortunately I'm busy now and not home but hope to have later. Please let me know if you have more to add
No hub for me. At the time I was using this I just plugged right into usb port.

smartymcfly said:
I am also having the static screen if I have USB plugged in when booting. When I unplugged USB and started firetv, instead of running Kodi as launcher/home button it was running firedtv launcher. I had read your post previously but did not reboot the first until I had problems watching amazon prime video, which was fine after a reboot.
Any chance we have the same USB hub? I have the "amazon basics powered USB 3.0 4 port hub" that sells for around $15-20.
The only thing I put on the USB drive was/is the icefilms metadata and zips containing movie/TV background/fanart.
I also recently installed elmerohuesos version of Kodi 14.1 and previously had his version of 14.0. I just seen that I didn't grant root rights when rebooted. You can check in appearance - skin - settings - general - android options - check su permissions
---------- Post added at 12:46 PM ---------- Previous post was at 12:29 PM ----------
I do not believe Xposed is causing the problem. That file you found is to disable xposed in the event that a bad module caused a problem IR if you just wanted to uninstall xposed from CWM/TWRP recovery. If select to install xposed via recovery manually then there is also an installer exposed.zip with the one you found.
---------- Post added at 12:54 PM ---------- Previous post was at 12:46 PM ----------
So you have tried disabling exposed and that didn't fix it? Also you tried official Kodi 14.1 but have not tried reverting to 14.0?
Uninstalled firedtv to get the static on reboot.
Items that I am going to mess with to see if it fixes the problem.
1. adbfire persistent USB mounting
2. I stalling elmerohueso's kodi_14.0 again to see if that is it.
Nothing has changed via exposed so that should not be what is causing the problem.
Changing the usb mount to non persistent did not change anything for me.
If this is happening to more than one person at the same time as it is and it did not happen before maybe there is an amazon app that updated, but then a lot more people would be having the same problem, or maybe they are having the same problem but have not had to reboot yet so they do not know the problem exists.
Click to expand...
Click to collapse
I don't really know what the problem is. The road that got me here is pretty complicated but basically I had xposed with rbox mods and elmerohueso launcher 14. I uninstalled the launcher, uninstall rbox TV mods and factory reset. Then, experiencing the static boot, I flashed a new ROM going from 51.1.4.1 to 51.1.4.0
Only now in hindsight I realized it was the USB that triggered the bad boot. So I fear I made some mistakes. Im currently running Kofi 14.1 normal build with no launcher and no xposed installed. Are you able to access screensaver settings in the home screen?
Not having a precise idea of how I wound up here, I'm unsure what to do? When the launchers sleep options were enabled I did grant it su privs. I'm not Sure how it applies to reboot? It never asked that I recall? But you're the 2nd person to ask me that.
From here do you think its safe to reinstall xposed mods and elmerohueso launcher to see if it corrects the USB issue? Or do you think that might potentially make it so I can't boot at all?

KLit75 said:
I don't really know what the problem is. The road that got me here is pretty complicated but basically I had xposed with rbox mods and elmerohueso launcher 14. I uninstalled the launcher, uninstall rbox TV mods and factory reset. Then, experiencing the static boot, I flashed a new ROM going from 51.1.4.1 to 51.1.4.0
Only now in hindsight I realized it was the USB that triggered the bad boot. So I fear I made some mistakes. Im currently running Kofi 14.1 normal build with no launcher and no xposed installed. Are you able to access screensaver settings in the home screen?
Not having a precise idea of how I wound up here, I'm unsure what to do? When the launchers sleep options were enabled I did grant it su privs. I'm not Sure how it applies to reboot? It never asked that I recall? But you're the 2nd person to ask me that.
From here do you think its safe to reinstall xposed mods and elmerohueso launcher to see if it corrects the USB issue? Or do you think that might potentially make it so I can't boot at all?
Click to expand...
Click to collapse
It is safe to have xposed and rbox. There is something else going on... It won't solve the USB problem. The only thing there is to do is just make sure to have USB unplugged until after it starts for now. Maybe someone more knowledgeable will experience this and have a fix in the future.
I think I also I stalled system tools via adbfire recently as I had installed the tools separately before, not sure if that has anything to do with it. I think it might be a system app from amazon updating causing the issue.
I am not sure what you are talking about as far as the screensaver goes. If I am watching amazon prime then pause it the amazon screensaver of random photos starts up if that is what you are talking about.
When Kodi is on the window the screen just dims for the screensaver on my setup.
Maybe jocala changed up the automount script or something that could be causing it.
jocala said:
Just need to link you to this thread hoping you can help.
Click to expand...
Click to collapse

smartymcfly said:
It is safe to have xposed and rbox. There is something else going on... It won't solve the USB problem. The only thing there is to do is just make sure to have USB unplugged until after it starts for now. Maybe someone more knowledgeable will experience this and have a fix in the future.
I think I also I stalled system tools via adbfire recently as I had installed the tools separately before, not sure if that has anything to do with it. I think it might be a system app from amazon updating causing the issue.
I am not sure what you are talking about as far as the screensaver goes. If I am watching amazon prime then pause it the amazon screensaver of random photos starts up if that is what you are talking about.
When Kodi is on the window the screen just dims for the screensaver on my setup.
Maybe jocala changed up the automount script or something that could be causing it.
Click to expand...
Click to collapse
I had checked with jocola and basically there's nothing happening w the usb at boot for me. I just mount samba. I think system tools is just a more simplified renaming of busybox/samba script for users that might be confused.
No. That's not what I meant by display/screensaver issues. You know the aftv homescreen that section that says "display"? If you click it there's an option for "screen saver"? Well if I click that no further options appear. It just flashes then you get stuck. Only the home button takes you out.
My only half baked blind theory there is it's a remnant of the elmerohueso screen saver options and it's no longer installed to appear BUT the system isn't replacing it with the old options...
Anyway. Very few people seem to know what happened here. In your opinion, you think it's safe to reenable rbox/exposed and install the elmerohueso launcher? At the very least it might fix my screensaver problem. As of now my aftv doesn't sleep.
I'm just worried since we really can't pinpoint what caused this, I might end up in a worse situation. Right now, aside from not booting with usb and not sleeping, it runs almost perfectly. I used it for hours last nite without even a single hiccup.

Req: Hardware root / reflash service FTV Stick (USA)

Just wondering if some kind hacker would like to practice soldering and flashing on my Fire TV Stick. I was one of the folks who semi-bricked theirs with supersu me and Kingroot...
I have ADB but no root, boots to a black screen after animated rainbow logo. I can reboot to recovery, which seemingly does not make any changes to the device. Invoking a program like su or attempting a pm install freezes the adb shell. I haven't tried anything over USB yet. Invoking the settings menu, for instance, has no effect. I can get logs, ps, and navigate folders, but I don't think I'm going to be able to get it to a home screen.
But I wanted to put it out there - I'd throw some money your way for time, trouble, and shipping if you think you can re-flash it.
A dozen thanks in advance...

I have the same problem after I use supersu me with my box. stop at color amazon logo. Hope anybody can give me some idea to make it factory reset or pay for hardware write the emmc

Can my Fire TV Stick be saved?

I bought a Fire TV stick back in December 2014 and I remember rooting it (I don't remember what method I used), but then I lost interest thanks to the chromecast... Now 3 1/2 years later I find a use for the Fire TV Stick (media player on my boat) so I pulled it out of storage and booted it up. I wanted to install Kodi but every menu option I selected has an error contacting Amazon, so I decided I should just update it (probably a BAD idea!). The update (5.2.6.3) seems to have installed fine just fine, but now I still can't get anything on any menus and I can no longer enable ADB or unknown sources. When I boot it up I don't see anything about TWRP or CWM, so I don't think the bootloader is modified. At this point I don't know how I can get any apps on it (the apps menu doesn't even load) or get into any debug mode, does anyone have any ideas where I could start? I also tried a factory reset but it didn't change anything.

Buy a new firestick bro they dont cost anything these days.