Develop Bugs

Kindle Fire utility not working

My kf was previously rooted at 6.2.1. I haven't played with it much considering it kind of did what I wanted, although it lost root a while back. I am now trying to reroot after getting the latest 6.3 upgrade. I downloaded the 0.95 KFU but it won't run. It starts, but the window disappears after about 5 seconds. I tried 0.91 and it went through the whole cycle but of course didn't work. I have downloaded everything I know to do and .95 won't run. I even dis the whole SDK thing all over again. Any help is appreciated.

saltyjd said:
My kf was previously rooted at 6.2.1. I haven't played with it much considering it kind of did what I wanted, although it lost root a while back. I am now trying to reroot after getting the latest 6.3 upgrade. I downloaded the 0.95 KFU but it won't run. It starts, but the window disappears after about 5 seconds. I tried 0.91 and it went through the whole cycle but of course didn't work. I have downloaded everything I know to do and .95 won't run. I even dis the whole SDK thing all over again. Any help is appreciated.
Click to expand...
Click to collapse
Are you running the latest version of Java and do you have the newest SDK? Also try Kindle Fire Utility v.0.9.4

My suggestion, from seeing countless members running into problems with the KFU, is root your device manually. It's a little more work but there's less chance of failure IMO.
Sent from my Amazon Kindle Fire using xda premium

thanks
I got it working. For whatever reason, I ended up replacing the older KFU version which was located it the root of the main drive with the new version. The new version was in the desktop. I have no idea why it wouldn't have worked, but as soon as I moved it, it ran, and there was no issue with getting rooted. Thanks for the help.

[Q] Sorry to ask, but I need help please.

I messed up. I was trying to root my Kindle Fire to get Google apps on my kindle. I am a Paramedic and use some apps that aren't available on the kindle store. I have since bought a Samsung tab 3 for myself and I"m giving the Kindle Fire to a friend who needs one.
I used TWRP v2.1.1 and everything seemed to be going ok, that and the normal kindle loaded just fine. I didn't have a change to play with it much, I'm a noob (obviously)
Before giving it to my friend I was going to restore it to factory settings. I did so in the normal kindle load. It turned off and now I can get it to load into TWRP only. The gray screen comes up, Instal, Backup, ext. It won't, however, load into the kindle fire interface anymore. It just goes to the white and orange KF screen and gets stuck, no animation. If I run the Kindle Fire Utility on my PC I can change it to 4000 and 4002. Thats about it... None of the other things seem to work. I can click on them, and they seem to load but nothing happens. I tried to use the "Obtain stock update" and nothing happened. All I want to do is get the original KF interface back for my friend I'm going to be giving this to. Is there a simple program a noob like me can use? I have read and read here on the forums for a few days and I'm more confused now than ever. Partially because I keep getting called for 911's in the middle of reading, lol. I'm sorry to bother you all, but if you can help me I'd appreciate it. I"ve already promised this thing to her and will just have to buy another one if I cant fix it.

Gave up.
meadowsja said:
I messed up. I was trying to root my Kindle Fire to get Google apps on my kindle. I am a Paramedic and use some apps that aren't available on the kindle store. I have since bought a Samsung tab 3 for myself and I"m giving the Kindle Fire to a friend who needs one.
I used TWRP v2.1.1 and everything seemed to be going ok, that and the normal kindle loaded just fine. I didn't have a change to play with it much, I'm a noob (obviously)
Before giving it to my friend I was going to restore it to factory settings. I did so in the normal kindle load. It turned off and now I can get it to load into TWRP only. The gray screen comes up, Instal, Backup, ext. It won't, however, load into the kindle fire interface anymore. It just goes to the white and orange KF screen and gets stuck, no animation. If I run the Kindle Fire Utility on my PC I can change it to 4000 and 4002. Thats about it... None of the other things seem to work. I can click on them, and they seem to load but nothing happens. I tried to use the "Obtain stock update" and nothing happened. All I want to do is get the original KF interface back for my friend I'm going to be giving this to. Is there a simple program a noob like me can use? I have read and read here on the forums for a few days and I'm more confused now than ever. Partially because I keep getting called for 911's in the middle of reading, lol. I'm sorry to bother you all, but if you can help me I'd appreciate it. I"ve already promised this thing to her and will just have to buy another one if I cant fix it.
Click to expand...
Click to collapse
I gave up going back to stock, apparently I'm not intelligent enough to ask proper questions and give proper info or nobody knew how to help. However, I was able to flash over a ROM from here, pretty easy, just not what I wanted to do. http://forum.xda-developers.com/showthread.php?t=1451747
Anyway, ty for the site and resources. Delete if you wish, I just thought I'd update in-case someone was watching with the same problem.

help needed please !!

Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?

Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it

Broncos15 said:
Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it
Click to expand...
Click to collapse
No if that was the case then why will the file bo .bin.html ?

Mr.Dumb said:
No if that was the case then why will the file bo .bin.html ?
Click to expand...
Click to collapse
It shouldn't have .html on the end. Check the md5 sum for the file and make sure that it is the same as it should be, you should ALWAYS do this when messing with the bootloader

Maybe you flashed wrong images.
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...

maxaurelius said:
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...
Click to expand...
Click to collapse
I actually plan on doing this for a similar reason. My sons kindle battery life is appalling as it drains faster than before and charges slower, plus kindle updates are lacking badly and some things don't work anymore.
I hope you can fix it somehow.
Happy new year.

Mr.Dumb said:
Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?
Click to expand...
Click to collapse
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike

11fan said:
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike
Click to expand...
Click to collapse
Thanks a lot friends, i surely have a jem and i tried to read ad do things intended to do for jem only (seems strange to me that link i posted is for otter though i cross checked many times not to flash other device images but may be messed up in enthusiasm)
Never mind i eventually had to end up selling this on craiglist as a friend mentioned and got a working one from ebay ( to my shock it's reported as lost and stolen) looks i have great bad luck...
Now the kindle is just nothing unless i have cm in it but i will need all you guys help so that i dont end up like before
So please help me out with links so that i do all things correctly ...please i don't have any money now to loose or fix this ...
Thanks in advance
Edit : i tried to root kindle but was not able to, its on the highest or most up to date version of fire os as per amazon
I tried to root with restore by binary, cant see superuser in app drawer, able to see it in system/apps via root explorer
Tried to install firefire.apk it shows no root & root explorer doesn't rename system apps to .bak.... So i believe i cant root..
Please @11fan help me out now i need only cm on kindle thats fine for me.......
I'd be gratful to you for the help

Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk

11fan said:
Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy

Mr.Dumb said:
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy
Click to expand...
Click to collapse
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike

11fan said:
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike
Click to expand...
Click to collapse
Yes please help me with TWRP / CWM. Please & I want to install CM on it now

Did you get it rooted?
Mike

11fan said:
Did you get it rooted?
Mike
Click to expand...
Click to collapse
Yes
Hello @11fan
Edit : got it rooted, TWRP installed, made a nandroid backuo & tried to flash CM (chkd MD5 as well) but CM boot screen stayed for so so long...so I rebooted the device to TWRP and did a full wipe as well as format data...now have no os installed, cant mount as usb storage to copy nandroid...kooks like i've messed again....
Praying to God that I have some way again to restore...
Edit 2 : sorted via adb sideload

Glad you got it....i was going to tell you that the LONG cm screen on first boot is normal! I just loaded cm12 on mine last night and first boot took about 8 minutes, maybe longer as I forgot to time it!
Mike

Help with confusing AFTV issues

Last night I wiped data/factory reset in cwm after experiencing some issues. When the main menu returned I noticed it loaded very slow and I thought there might be other problems, but then it started to behave normally and continued to as I disabled updates, installed kodi, llama, busybox, and es explorer. All was working fine. I setup kodi very basic (just scanned in Genesis and my local library) Couple of hours later, I exited Kodi to install netflix. Mind you, this was late so I don't remember exactly what I was doing but definitely nothing nefarious.
Basically the main menu had some lag. Kodi had trouble relaunching so I thought a reboot might be helpful. I rebooted--it went from boot menu to amazon (white) to amazon (colored) and all appeared fine till the screen turned to snow. This lasted like 10 seconds then it went back to the amazon fire tv (white and yellow logo) and it hung there at least ten minutes before I pulled the plug. Tried it again and replugged it in and it did the same sequence, hanging on amazon yellow and white.
I was pretty sure I was bricked because I couldn't connect over adb, but not too freaked out because rbox boot menu was still showing up. So today the plan was to use the boot menu to get to recovery and push and older firmware, WHICH I HAVE QUESTIONS ABOUT...
BUT when I plugged the aftv back in this morning it went through a normal boot sequence and right to the main menu like normal. It's very strange I have no idea what's happening to be honest but I'd like to revert my firmware back to an earlier version. After reading some posts it seems if you skip firmwares and install a later version you might have issues so I'm hoping that's what I did here and some of the bugs might be fixed by installing older firmware.
This aftv is running the latest 51.1.4.1 It has an unlocked bootloader and as I said rbox boot menu. Is there anything I need to do to revert from here? (lock bootloader?) Or can I just push the zip according to the guide and install it?
That's my main concern since I've never gone backward with the updates. Also***Obviously***if you have any theories as to what the heck was happening with my aftv last night--please share! I know there's not much info provided but this post is already a little long. But of course if you're interested in trying to diagnose I'd be happy to provide whatever details you need. Thanks.

Simliar Situation
KLit75 said:
Last night I wiped data/factory reset in cwm after experiencing some issues. When the main menu returned I noticed it loaded very slow and I thought there might be other problems, but then it started to behave normally and continued to as I disabled updates, installed kodi, llama, busybox, and es explorer. All was working fine. I setup kodi very basic (just scanned in Genesis and my local library) Couple of hours later, I exited Kodi to install netflix. Mind you, this was late so I don't remember exactly what I was doing but definitely nothing nefarious.
Basically the main menu had some lag. Kodi had trouble relaunching so I thought a reboot might be helpful. I rebooted--it went from boot menu to amazon (white) to amazon (colored) and all appeared fine till the screen turned to snow. This lasted like 10 seconds then it went back to the amazon fire tv (white and yellow logo) and it hung there at least ten minutes before I pulled the plug. Tried it again and replugged it in and it did the same sequence, hanging on amazon yellow and white.
I was pretty sure I was bricked because I couldn't connect over adb, but not too freaked out because rbox boot menu was still showing up. So today the plan was to use the boot menu to get to recovery and push and older firmware, WHICH I HAVE QUESTIONS ABOUT...
BUT when I plugged the aftv back in this morning it went through a normal boot sequence and right to the main menu like normal. It's very strange I have no idea what's happening to be honest but I'd like to revert my firmware back to an earlier version. After reading some posts it seems if you skip firmwares and install a later version you might have issues so I'm hoping that's what I did here and some of the bugs might be fixed by installing older firmware.
This aftv is running the latest 51.1.4.1 It has an unlocked bootloader and as I said rbox boot menu. Is there anything I need to do to revert from here? (lock bootloader?) Or can I just push the zip according to the guide and install it?
That's my main concern since I've never gone backward with the updates. Also***Obviously***if you have any theories as to what the heck was happening with my aftv last night--please share! I know there's not much info provided but this post is already a little long. But of course if you're interested in trying to diagnose I'd be happy to provide whatever details you need. Thanks.
Click to expand...
Click to collapse
I am experiencing the same issue. I tried re-installing the ROM.zip file I had left on it and it installs but it still will not start up. I just keep getting stuck on the white and yellow logo. Is there anyway to install a boot.img and unzip it in recovery that you are aware of? I was running SPMC w/ boot.
I kind of feel I should of let it alone like you did, and it might have fixed itself.

Well...it didn't fix itself
Kul-Aid23 said:
I am experiencing the same issue. I tried re-installing the ROM.zip file I had left on it and it installs but it still will not start up. I just keep getting stuck on the white and yellow logo. Is there anyway to install a boot.img and unzip it in recovery that you are aware of? I was running SPMC w/ boot.
I kind of feel I should of let it alone like you did, and it might have fixed itself.
Click to expand...
Click to collapse
Yes. It was running fine. Last nite I pushed 51.1.4.0 and it installed fine. In fact this aftv ran bug free all nite. This morning I noticed it wasn't in sleep mode (typical) I just hit the home button and usually it sleeps shortly after. Not this time.
So I turned on my TV and the home screen was there but navigating Very slow so I rebooted. It hung longer than usual on amazon white then the snow screen reappeared then it went to normal colored amazon then it hung on amazon white and yellow! I left it alone 20 minutes but it remained. BTW_rbox boot menu is gone. I hope I get it back. Gonna try a keyboard to get recovery.
Edit__keyboard got me to home screen not recovery?! Weird...If anyone has a clue please chime in. My next move (logically...I guess) is to push 51.1.4.1 because that was my initial fix for Netflix but this issue started before I changed anything. 2 different firmwares--same issue. So I don't think that's it. But it possible I should've maybe cleared dalvik before flashing. However I did do a factory reset in cwm just 24 hours prior to flashing 51.1.4.0 I'm over my head as far as troubleshooting goes. I can say it ran excellent last night with 51.1.4.0 and then it wouldn't boot. Now its running excellent again. If I had to guess the bug is triggered by idle time however, the first time this occurred I was using xbmc and having issues and I rebooted to snow so its not just that.
This seems to be an uncommon issue but I've followed those guides to a tee. After wiping and flashing I have 3 apps--es file, llama and kodi. Same apps, same firmware as my other aftv that doesn't give me problems. Only difference is history. The new aftv had a much more involved process to root, downgrade and get to 51.1.4.0

Yours messed up again?
KLit75 said:
Yes. It was running fine. Last note I pushed 51.1.4.0 and it installed fine. In fact this aftv ran bug free all nite. This morning I noticed it wasn't in sleep mode (typical) I just hit the home button and usually it sleeps shortly after. Not this time.
So I turned on my TV and the home screen was there but navigating Very slow so I rebooted. It hung longer than usual on amazon white then the snow screen reappeared then it went to normal colored amazon then it hung on amazon white and yellow! I left it alone 20 minutes but it remained. BTW_rbox boot menu is gone. I hope I get it back. Gonna try a keyboard to get recovery.
Click to expand...
Click to collapse
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.

Kul-Aid23 said:
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.
Click to expand...
Click to collapse
I didn't block them on the router. I only did that when I was rooting my new aftv about a month ago. But I'm obsessive about making sure they're disabled on the box. If they snuck something in ota you'd think both my boxes would be messed up--not the case.
Btw--if this was deliberate its messed up and I won't be buying anything from them ever again.
But now you got me paranoid. I'll block on the router again. Kind of a hassle because my router doesn't support it with stock. I need to ping the site with my Mac and do it manually but I will. I only bought a second one because android TV is a possibility. My other amazon product is running cm 11 over clocked and its laughable how well it runs by comparisdon--good hardware/bad os. But I didn't come here to rant. Any suggestions?
Edit--sorry I sort of blew you off there. Try a keyboard. Wait for amazon then hold Ctrl alt. Print screen. I did a combo of holding a pressing the keys and it booted. But it looks like this will continue. Hopefully we find a fix.

More info
I jumped the gun a bit when I said it was working. Yes I can navigate the main menu and the few apps I have open and work fine. But this is interesting...it doesn't appear to sleep after 30 minutes or so, like usual, so I went into "Display" on the menu. Sometimes when I do this it will just open a blank window and crash menu (unresponsive, cant move) Sometimes it will let me open the window but when I press "screensaver" it crashes again. This location seems to be prohibited for some reason. BUT...it reboots normally.
Question--I had unlocked the bootloader prior to flashing 51.1.4.0 last night. As I type I don't think that has anything to do with it. And thinking about it it displayed the same behavior when I was running 51.1.4.1 the night before with bootloader unlocked so I don't think that has any relevance. You know what I've got other options for the bedroom tv. For now I'm going to keep it unplugged, block updates on the router and hope people have theories.
Although at this point blocking updates on the router seems a little like locking the door to the Hen house after the Wolf has already entered...it'll still make me feel better if for no other reason than I own another aftv (using it now and it works fine.)

Kul-Aid23 said:
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.
Click to expand...
Click to collapse
You're issue may be different than mine. You're not getting the snow screen then it hangs.
Did you try to flash the later firmware without the latest version of CWM? Or try the latest with Rbox boot menu?

KLit75 said:
You're issue may be different than mine. You're not getting the snow screen then it hangs.
Did you try to flash the later firmware without the latest version of CWM? Or try the latest with Rbox boot menu?
Click to expand...
Click to collapse
I'm not sure I know what you mean, like which files to install on it or if I can. I can't ADB into it, I can only run zip files through CWM. I tried loading the last ROM I installed on it and nothing changes. I had put up a forum for it:
http://forum.xda-developers.com/fire-tv/help/aftv-bricked-reward-t3022426
I am debating trying different ROMs as well. I just don't want to lose CWM or else I'm bricked for sure.
And we might be having different issues. Bc mine loads boot loader where I can pick the boot kernel or CWM. But when it goes to boot kernel it just sits on that White and yellow Amazon screen. I don't encounter any static.

Which domains are you blocking?
Kul-Aid23 said:
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.
Click to expand...
Click to collapse
Kul-Aid23 said:
I'm not sure I know what you mean, like which files to install on it or if I can. I can't ADB into it, I can only run zip files through CWM. I tried loading the last ROM I installed on it and nothing changes. I had put up a forum for it:
http://forum.xda-developers.com/fire-tv/help/aftv-bricked-reward-t3022426
I am debating trying different ROMs as well. I just don't want to lose CWM or else I'm bricked for sure.
And we might be having different issues. Bc mine loads boot loader where I can pick the boot kernel or CWM. But when it goes to boot kernel it just sits on that White and yellow Amazon screen. I don't encounter any static.
Click to expand...
Click to collapse
I just meant, some people have attempted to install roms that require boot menu and the result is a brick but that's not you I guess since you get the boot menu. Mine skips boot menu now and goes right to homescreen which i guess means boot menu is no longer present after flashing 51.1.4.0
still boots fine after at least a half dozen reboots. But i do have a question for you...which domains are you blocking? Because I used the 3 from aftvnews. First for the aftv with issues which is unplugged so I didn't notice. The other one is on and playing prime. I blocked one (not sure which) then blocked another and Ive got a toddler screaming at me...Elmo dissapeared. My son was watching prime and it turned off. This is why I didn't keep updates blocked on the router for fear it would deny access to everything. But I couldn't even get an internet connection! At least one of the domains keeps amazon content but one...or 2 cut the aftv from the network! I have a wired connection and I couldn't get it back. Granted my son was screaming so I didn't have time to thoroughly troubleshoot but it appears blocking all those domains just isnt an option even if you did go without prime. So are you able to block all 3 domains from the guide and still connect? I tried rebooting and configuring the network.
BTW--brilliant idea offering a cash reward for the fix! I never would've thought of that.
Here's one thing I just thought of regarding my issues and it may be nothing but...it seems EVERYTIME my AFTV has booted to snow and then hung, I had a flash drive plugged directly into usb with the drive mounted persistent. Now I haven't tested this thoroughly, but when it boots so far it has NO flash drive and HAS HAD a usb keyboard plugged in. CTRL, PRINT Alt doesn't get me to recovery but it just boots to homescreen normally. MAYBE pressing those buttons did nothing. MAYBE the keyboard did NOTHING. But in fact, for my troubles it has something to do with the flash drive??? Or usb port???
Obviously I'm not a programmer or software/hardware expert but there are people here that could confirm it's a possibility or that's stupid. I'm just trying to narrow it down by providing info and that hadn't occurred to me until 10 minutes ago. Unfortnately my time is running out for now. I'll check back later and hope one or both of us has a solution or something to help get us there.
Keep me posted. Sorry I'm not sure why yours won't boot. It seems your doing everything right and even took it a step further to keep updates away.
EDIT--Possible I screwed up blocking updates on router. Like I said it's very tedious and I was distracted. I MAY have selected to block all internet access to that aftv. Makes sense since no one else had an issue there. But to confirm--does blocking these domains cause any issues accessing prime? Sorry about the long post.

BINGO!
So if you read the last post you'll see I suspected my AFTV booting into snow then hanging had something to do with the usb flash drive. Correct!
I unplugged the keyboard, plugged in the flash drive, and powered it on. It went from amazon white to SNOW to hanging amazon yellow and black. Unplugged the aftv, unplug the flash drive, powered on...it booted right to the homescreen. Corrupted flash drive? Issue with samba on startup? I don't know but would love to hear ideas...
EVERYONE has had corrupted hdd, sdcards and flash drives but for me it's never affected booting. This is still weird.
Also, though the fire menu navigation is fast and fluid, all apps work properly....there's STILL the issue with the Display section of the menu. It lets me click it. It lets me click screensaver BUT when it do it still crashes (sort of). Though I can't press back to escape or directional arrows, hitting the home button brings me back and it all works again. So maybe flashing the newest firmware from here will fix it but given the issues others are having I don't want to be too hasty. I'm looking for answers. It's running fine and the boot issue seems directly tied to the flash drive but that doesn't explain the issue with the Display/screensaver options...
I feel like I should intervene but without the boot menu currently installed I think I should sit tight and search/wait for some more ideas.

KLit75 said:
I just meant, some people have attempted to install roms that require boot menu and the result is a brick but that's not you I guess since you get the boot menu. Mine skips boot menu now and goes right to homescreen which i guess means boot menu is no longer present after flashing 51.1.4.0
still boots fine after at least a half dozen reboots. But i do have a question for you...which domains are you blocking? Because I used the 3 from aftvnews. First for the aftv with issues which is unplugged so I didn't notice. The other one is on and playing prime. I blocked one (not sure which) then blocked another and Ive got a toddler screaming at me...Elmo dissapeared. My son was watching prime and it turned off. This is why I didn't keep updates blocked on the router for fear it would deny access to everything. But I couldn't even get an internet connection! At least one of the domains keeps amazon content but one...or 2 cut the aftv from the network! I have a wired connection and I couldn't get it back. Granted my son was screaming so I didn't have time to thoroughly troubleshoot but it appears blocking all those domains just isnt an option even if you did go without prime. So are you able to block all 3 domains from the guide and still connect? I tried rebooting and configuring the network.
BTW--brilliant idea offering a cash reward for the fix! I never would've thought of that.
Here's one thing I just thought of regarding my issues and it may be nothing but...it seems EVERYTIME my AFTV has booted to snow and then hung, I had a flash drive plugged directly into usb with the drive mounted persistent. Now I haven't tested this thoroughly, but when it boots so far it has NO flash drive and HAS HAD a usb keyboard plugged in. CTRL, PRINT Alt doesn't get me to recovery but it just boots to homescreen normally. MAYBE pressing those buttons did nothing. MAYBE the keyboard did NOTHING. But in fact, for my troubles it has something to do with the flash drive??? Or usb port???
Obviously I'm not a programmer or software/hardware expert but there are people here that could confirm it's a possibility or that's stupid. I'm just trying to narrow it down by providing info and that hadn't occurred to me until 10 minutes ago. Unfortnately my time is running out for now. I'll check back later and hope one or both of us has a solution or something to help get us there.
Keep me posted. Sorry I'm not sure why yours won't boot. It seems your doing everything right and even took it a step further to keep updates away.
EDIT--Possible I screwed up blocking updates on router. Like I said it's very tedious and I was distracted. I MAY have selected to block all internet access to that aftv. Makes sense since no one else had an issue there. But to confirm--does blocking these domains cause any issues accessing prime? Sorry about the long post.
Click to expand...
Click to collapse
I had these 3 blocked via my router
amzdigitaldownloads.edgesuite.net (amzdigitaldownloads.edgesuite.ne though bc router limits # of charcters)
softwareupdates.amazon.com
updates.amazon.com
But i noticed the last comment on this link: http://www.aftvnews.com/how-to-block-software-updates-on-the-fire-tv-stick/
Maybe my AFTV lost internal OTA blocking at some point then got updated, but since I was using a different boot image, it can't boot now. Does that sound possible?
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Kul-Aid23 said:
I had these 3 blocked via my router
amzdigitaldownloads.edgesuite.net (amzdigitaldownloads.edgesuite.ne though bc router limits # of charcters)
softwareupdates.amazon.com
updates.amazon.com
But i noticed the last comment on this link: http://www.aftvnews.com/how-to-block-software-updates-on-the-fire-tv-stick/
Maybe my AFTV lost internal OTA blocking at some point then got updated, but since I was using a different boot image, it can't boot now. Does that sound possible?
Click to expand...
Click to collapse
Actually check out the bottom of this one where everyone is commenting on http://www.aftvnews.com/how-to-block-amazon-fire-tv-update-to-ensure-rooting/
I think I may have been updated then bricked.

Kul-Aid23 said:
I had these 3 blocked via my router
amzdigitaldownloads.edgesuite.net (amzdigitaldownloads.edgesuite.ne though bc router limits # of charcters)
softwareupdates.amazon.com
updates.amazon.com
But i noticed the last comment on this link: http://www.aftvnews.com/how-to-block-software-updates-on-the-fire-tv-stick/
Maybe my AFTV lost internal OTA blocking at some point then got updated, but since I was using a different boot image, it can't boot now. Does that sound possible?
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Actually check out the bottom of this one where everyone is commenting on http://www.aftvnews.com/how-to-block-amazon-fire-tv-update-to-ensure-rooting/
I think I may have been updated then bricked.
Click to expand...
Click to collapse
That's not what happened to you. I know right about now you're probably frustrated but the first article you linked was for fire tv stick (not fire tv). The fire tv stick doesn't have root, therefore they need to block on router because there is no way to disable updates otherwise. We can pm disable.
The 2nd article --check out the date--it's from may. We didn't get root till like mid june. So at that point people were trying to stay on low firmware in hopes when root came they'd be able to root!
It's unlikely you got an update if you blocked them on the box and you're sure you did. Especially with custom recovery, which you have. Even if you forgot to block them it's not likely they would install. Amazon would try, your box would likely boot itself to recovery like mine did when I forgot to block them after wiping data in CWM.
This doesn't help with your issue I know but I think you can look elsewhere as to the-- why it happened? There is maybe the slimmest chance an update could sneak through BUT if it happened to you I think lots of other people would be complaining of bricked devices. Hang in there. Hopefully we find a fix soon.

Might be able to help
I'm a long time lurker on these forums for all of my devices, but I just had this happen the other night. I had downgraded firmware, installed cwm, boot menu, and fully unlocked bootloader. When I went to upgrade to the latest custom rom (51.1.5.0?), I wiped data in cwm and ended up stuck on the Fire Tv splashscreen WITH NO BOOT MENU!! Therefore I could not boot to recovery or access via ADB. I was able to recover it by splicing some usb cables together that I had laying around to make a USB A to A cable, Installing the usb drivers for the kindle fire on my PC, and connecting it before powering on. Used cmd window and fastboot erased the boot partition and fastboot flashed @rbox bootmenu.img to the partition. Disconnected the USB cable and rebooted to find the boot menu back and able to access recovery!! Hopefully this can help you, or someone else that finds themselves in a similar predicament.
Edit: Once in CWM install zip via sideload then connect to ADB from PC to push the ROM

Firestick 2nd gen 5.2.7.4?

My firestick downloaded 5.2.7.4 and its broke my accessibility and adb commands. I looked on amazon to see latest versions for their devices and none of em are listed to have 5.2.7.4. Not sure if anyone else is having this problem or if they are rolling out another update and I just got unlucky and got some of the first roll outs of it. I also had ran some debloat commands and not sure if the stick just ran some updates after that. But it was after that it broke. But I have since factory reset and its still broke adb and accessibility. Just wanted to make people aware and see if anyone else has found a fix for this version or any info on a fix.

I having this problem too, cant set custom launcher.. anyone help us??

The 5-6 domains did not block this update either! This update made it through!
I also am wondering about this. Not even the app I used to prevent standby works anymore!

I have been looking all over for any info on the .4 update and no one seems to care as if this update doesn't exist. I have found no info on any existence of .4 except for a select few people sharing the same problem. this update has broke my adb as well as accessibility. Virus scanner wont work custom launcher will work if manually loaded. any app that requires any adb or accessibility are completely broke. sm commands come back as doesnt exists as will as i believe pm commands. only a select few non important commands will work. trying to give details in case it helps at all. but for now just letting developers do their thing and not trying to bother them to much. would love to help more but my 2nd gen tank cant be rooted. so i cant pull a backup or anything from it. not to mention if it was able to be rooted id be golden. Hopefully if someone figures out this whole .4 thing they will be kind enough to post something about it.

https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Adb works without any Problems.

dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.

Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.

noremy said:
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
Click to expand...
Click to collapse
Try toggling unkown sources and debugging in settings? Maybe they got turned off?
Oh and just straight usb, 1 cable? Mine wont do tether adb with an otg cable.

Done all that. Unfortunately Im stuck. I dont what else to do with this thing. ADB will still connect but all the important commands come back as missing or invalid. such as sm commands and pm commands.

With 5.2.7.4 , you need root for this commands!!!

Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.

TimmyP said:
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Click to expand...
Click to collapse
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.

Sus_i said:
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Click to expand...
Click to collapse
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.

TimmyP said:
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
Click to expand...
Click to collapse
:good:
You can fix this issue if you connect the FireISO system to the internet and run this, in order to update fb:
Code:
pacman -Sy
pacman -Sy fastboot

Ahh where were you a couple days ago!

noremy said:
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
Click to expand...
Click to collapse
So just to clarify, 5.2.7.4 OTA has taken custom launcher apart by blocking pm grant permissions in accessibility.
TechdoctorUK mentioned this too a couple of weeks back. It seems the devs at amazon have been all over him lately and have been quoting tutorials etc from his site.
I've been using the ftvlaunchx app wrote to system settings on a post Dec 2019 unrootable 2nd gen and thought I'd blocked 5.2.7.4 update but I came back in today and was fkin horrified it had updated to 5.2.7.4 (I nearly sh't myself) its still optimizing apps just now but I'm hoping, just hoping that due to the pm grant permission already being installed it maybe slip through the net. Wishful thinking I know.
Hurry up and arrive 4k firestick I NEED ROOT

Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.

noremy said:
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
Click to expand...
Click to collapse
Hi noremy, i just made a new thread there on 5.2.7.4, the cure is ftvlaunchx wrote to system settings, install atv launcher pro and set that as default launcher in the ftvlaunchx app, should work with any android tv launcher too.
Big thanks to the developers @github
Edit #### i rebooted and now the home button is not working at all
Only sending me back to amazon screen.
Regards
Sent from my SM-T580 using Tapatalk

Hi! Mine is a 2nd gen Firestick. After the 5.2.7.4 update, none of my apps are opening. It says "Amazon App Store is out of date. Please visit the Amazon website to install the latest version". When I click on the link, it says Appstore is installed & I am good to go. No matter what I do, same thing happens for each and every app. So I can't use any of the apps on my Firestick. Any suggestions on what this is? Thanks!

The only option I can think off would be to factory reset it. I know its a pain to put everything back on but not sure what else to try.