Develop Bugs

[Q] Kind Fire Bricked at Yellow Triangle....What Now???

So Ive read multiple threads from this forum and tried the suggested methods and nothing has worked at all. My Kindle Fire is stuck at the Yelllow triangle logo and I have no clue how to get it back working at this point. I originally rooted using BreakDroid using Clockwork recovery and was successful running the Energy ICS Rom.
I attempted to flash the Miui ICS Rom and thats where it went all bad and has been stuck at the Yellow Triangle ever since. I've tried to use the KFU 0.9.6 but my computer only recognizes the kindle as a "android phone" but doesn't see that's it plugged in. KFU states that it's waiting for device when trying to run any of the commands and I have reboot to get it to proceed but none of the commands work and only return me back to a frozen triangle screen everytime.
So I need some serious advise on how to start over and get my kindle fire back to stock and out of this dreadful yellow triangle screen thats haunting me! Please post any instructions based on your experiences or expertise.
Please Please Please Help!
Thanks in advance.....

Are you able to access recovery?

soupmagnet said:
Are you able to access recovery?
Click to expand...
Click to collapse
Nope not at all everytime I press the button and it turns orange nothing happens and it completely freezes and I have to reboot completely.

How comfortable are you with fastboot commands?

soupmagnet said:
How comfortable are you with fastboot commands?
Click to expand...
Click to collapse
Not the best but if you have some instructions I'm sure I can figure it out lol at this point I have no choice

You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.

soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I used the Kindle Fire Utility and did option #1 to boot normal mode but it didn't work but I'll these methods and post some feedback on it....thanks a lot

soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I understand all of that info but doesn't really lay out any steps to take to fix the issues I'm having. I'm not a newbie to rooting this is just the first time I've experienced this particular problem

Disregard

Thepooch said:
Disregard
Click to expand...
Click to collapse
Thanks for the positive advice

I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.

Thepooch said:
I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.
Click to expand...
Click to collapse
I actually got it fixed using breakdroid and thank god it worked but thanks for the advice I know exactly what not to do the next time

Had a similar problem brickoid sorted me
Sent from my i777 using xda
aokp on neak yo!

[Q] Kindle fire wont work I cant install twrp no OS just Stuck at Kindle Fire Logo

The only thing I can do is get the device status to go online. It's recognizable on my computer devices. But I can't open it. Only right click. Iv tried fast boot. Iv tried installing twrp manually. But I always get stuck at waiting for device. When the Kindle reboots reconnects and disconnects and then reconnects. But all I see is the kindle fire logo. It can sit there for hours like that. Iv tried Soupkit. But that didn't work because it said the device was offline even it actually wasn't. Iv tried everything unless someone has an idea. It has no OS to boot to. So thats the reason. It must be. I void the warranty obviously by rooting. But I'm not here for admitting I did a stupid move of actually rooting when you dont know what your doing. If someone can leave a suggestion. I'd appreciate the suggestion. thanks

nobleman221 said:
The only thing I can do is get the device status to go online. It's recognizable on my computer devices. But I can't open it. Only right click. Iv tried fast boot. Iv tried installing twrp manually. But I always get stuck at waiting for device. When the Kindle reboots reconnects and disconnects and then reconnects. But all I see is the kindle fire logo. It can sit there for hours like that. Iv tried Soupkit. But that didn't work because it said the device was offline even it actually wasn't. Iv tried everything unless someone has an idea. It has no OS to boot to. So thats the reason. It must be. I void the warranty obviously by rooting. But I'm not here for admitting I did a stupid move of actually rooting when you dont know what your doing. If someone can leave a suggestion. I'd appreciate the suggestion. thanks
Click to expand...
Click to collapse
Does your Kindle Fire logo stay brightly lit or at any point does it flash and/or go dim?

soupmagnet said:
Does your Kindle Fire logo stay brightly lit or at any point does it flash and/or go dim?
Click to expand...
Click to collapse
brightly lit

nobleman221 said:
brightly lit
Click to expand...
Click to collapse
Okay, are you using a Linux VM, LiveUSB or full normal Linux install on your PC?

soupmagnet said:
Okay, are you using a Linux VM, LiveUSB or full normal Linux install on your PC?
Click to expand...
Click to collapse
full normal linux, Ubuntu 12.10`

nobleman221 said:
full normal linux, Ubuntu 12.10`
Click to expand...
Click to collapse
Are you using a USB 3.0 port?

soupmagnet said:
Are you using a USB 3.0 port?
Click to expand...
Click to collapse
Noob question how do you tell

nobleman221 said:
Noob question how do you tell
Click to expand...
Click to collapse
How old is your computer?
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.

nobleman221 said:
Noob question how do you tell
Click to expand...
Click to collapse
If you have to ask then 99% likely you don't have one.
If you bought your computer in the last 6 months then maybe.

soupmagnet said:
How old is your computer?
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
Click to expand...
Click to collapse
Acer Aspire 5742. 3 years old.

nobleman221 said:
Acer Aspire 5742. 3 years old.
Click to expand...
Click to collapse
Nope. No way to possibly have a USB 3 port on that.

TheNetwork said:
Nope. No way to possibly have a USB 3 port on that.
Click to expand...
Click to collapse
So Is my kindle gone for good?

nobleman221 said:
So Is my kindle gone for good?
Click to expand...
Click to collapse
No. Did you follow the instructions I gave you previously?
soupmagnet said:
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
Click to expand...
Click to collapse

Ok, Im able to get the ADB device status to online in Soupkit. But where do I a start from exactly. do i got to bootmenu or what.

nobleman221 said:
Ok, Im able to get the ADB device status to online in Soupkit. But where do I a start from exactly. do i got to bootmenu or what.
Click to expand...
Click to collapse
Install menu > install TWRP...or COTR...your choice.
Sent from my Amazon Kindle Fire using Tapatalk 2

The kindle status is online. Should the kindle be off or not. Also when I run twrp install on the terminal. Its running nothing but words. How long does this take. Also do I need WiFi while doing this.
Sent from my EVO using xda app-developers app

nobleman221 said:
The kindle status is online. Should the kindle be off or not. Also when I run twrp install on the terminal. Its running nothing but words. How long does this take. Also do I need WiFi while doing this.
Click to expand...
Click to collapse
"It's running nothing but words." Hmm...interesting.
You have to understand that I cannot see your device and I definitely can't see these "words" you're talking about. I have no idea what you've done and you still haven't told me whether you understood the instructions I gave you to install FFF or whether or not you succeeded in doing so. So unless you are able to provide me some usable information, we're just going to go around in circles here.
Aside from that, ADB is not going to do you any good until you get TWRP installed. You won't get TWRP installed until you follow the instructions I gave you to get FireFireFire installed. In case you missed it...for the second time...I'll try to explain it a little better.
If you had read the SoupKit thread, you would find that the stock bootloader doesn't work like it should in regards to accepting fastboot commands. The command "fastboot devices" doesn't work, so the SoupKit, will always say "Device Offline". Other fastboot commands will work, but you have to enter the command, turn the device off (hold power button for 10 seconds), then turn it back on. I also explained in the SoupKit thread (and here...twice), that if you have the stock bootloader installed and you get "Device Offline", to choose an option anyway and follow the instructions it gives you (which will be to turn the device off, then back on, etc).
Now, considering you have not given me any information regarding the success or failure of those instructions, I'll have to assume you either didn't read or you didn't understand them. That being said, let's go back and try it again.

soupmagnet said:
"It's running nothing but words." Hmm...interesting.
You have to understand that I cannot see your device and I definitely can't see these "words" you're talking about. I have no idea what you've done and you still haven't told me whether you understood the instructions I gave you to install FFF or whether or not you succeeded in doing so. So unless you are able to provide me some usable information, we're just going to go around in circles here.
Aside from that, ADB is not going to do you any good until you get TWRP installed. You won't get TWRP installed until you follow the instructions I gave you to get FireFireFire installed. In case you missed it...for the second time...I'll try to explain it a little better.
If you had read the SoupKit thread, you would find that the stock bootloader doesn't work like it should in regards to accepting fastboot commands. The command "fastboot devices" doesn't work, so the SoupKit, will always say "Device Offline". Other fastboot commands will work, but you have to enter the command, turn the device off (hold power button for 10 seconds), then turn it back on. I also explained in the SoupKit thread (and here...twice), that if you have the stock bootloader installed and you get "Device Offline", to choose an option anyway and follow the instructions it gives you (which will be to turn the device off, then back on, etc).
Now, considering you have not given me any information regarding the success or failure of those instructions, I'll have to assume you either didn't read or you didn't understand them. That being said, let's go back and try it again.
Click to expand...
Click to collapse
i did read the instructions. But the terminal runs a bunch of commands rapidly so fast I cant read it. I have my WiFi turned on and when I enter the command to install TWRP the terminal window just runs and that's the end of it, it runs in an endless loop jumbled words. My Kindle fire connects making 3 connect/disconnect sounds when plugged in my computer. And Still is stuck at the boot logo with no signs of change.

nobleman221 said:
i did read the instructions. But the terminal runs a bunch of commands rapidly so fast I cant read it. I have my WiFi turned on and when I enter the command to install TWRP the terminal window just runs and that's the end of it, it runs in an endless loop jumbled words. My Kindle fire connects making 3 connect/disconnect sounds when plugged in my computer. And Still is stuck at the boot logo with no signs of change.
Click to expand...
Click to collapse
You can scroll up through the terminal to get the outputs of the previous commands. Regardless, if you ran the option to install FireFireFire, it would sit at "waiting for device" until you shut the device down and turn it back on.

soupmagnet said:
You can scroll up through the terminal to get the outputs of the previous commands. Regardless, if you ran the option to install FireFireFire, it would sit at "waiting for device" until you shut the device down and turn it back on.
Click to expand...
Click to collapse
"Your shell is either missing or corrupt shell making it impossible to change from the inside of the system your \nshell must be installed properly before you can proceed any further, the only way to do this is firefirefire." Is what was being spammed in the terminal. I couldent copy and paste the the thing because everytime I clicked inside the terminal the instructions dissappeared.

First bricked fire tv??

Not sure if its really bricked or not but Its all messed and wont fully boot so it doesnt have lan access anymore for ssh and adb over wifi. I have a male to male usb cable and my pc is recognizing when its plugged in but there are no device drivers installed and adb/fastboot wont recognize (no usb debugging enabled?) so it just hangs on <waiting on device> any idea how I can install devices drivers and move forward with restoring backup of the file I fuxored? Thx guys!

Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.

Havnt got that far yet myself but the way i tinker i will be there shortly .. but as a warning to others, if you are not 100% sure what you are doing, dont muck around especially if you remount /system as rw.
Playing around will be much safer once we get recovery..
Building a recovery shouldnt be too difficult.. its booting a custom recovery that will be the trick.. Jcase had allready said he has figured it out perhaps he will share now that root is out.

roustabout said:
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Click to expand...
Click to collapse
Ive got fastboot connected now so it appears it was some funky unknown issue. Fastboot isnt like adb tho and the only time ive ever used it was to re-write whole img files so is that my only option or is there some way I can push stuff through fastboot? The OTA firmware links posted a few weeks back are now dead too..

You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.

Luxferro said:
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Click to expand...
Click to collapse
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Im not have any luck with those links either ive even tried assigning a static public dns to make sure my opendns stuff was no longer blocking. Does anyone have an alternate link?

alwaysbless said:
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Click to expand...
Click to collapse
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.

I had a similar instance. Gained root messed around too much and got it to not boot. Amazon is sending a replacement... But if there is a way around that in the future I would love to just fix it my self.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Luxferro said:
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
Click to expand...
Click to collapse
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.

alwaysbless said:
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
Click to expand...
Click to collapse
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk

Luxferro said:
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got you now. So this is def the first bricked fire tv lol. Guess ill just sit it to the side and see if someone smarter than I can figure something like this out in the future.

Have you tried fastboot boot commands? Like fastboot boot blahblahblah.img? If it is softbricked i guess it can't hurt to try rite?

I don't know if this will work or not, but if you've already tried pulling the power, pulling USB and powering on the next thing 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.
What you're hoping is that the USB mass storage is mounted as a possible recovery source at power on and that the OTA is isntalled via the stock recovery. If it works, great, if it doesn't, too bad.

another brick on the wall ?
Dear OP ' i think you are not the only one .
im not sure if im bricked or plain noob
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su
pm disable com.amazon.dcp" . all was good and i had an issue with audio in xbmc and in my great wisdom i did a reset to factory settings.
since then i can not register to amazon i believe because it can not accsses amazon site for verification. so im stuck in there.
i tried to SSH and through command line no device was recognized .
any assistance to this stupidity will be much appericiated
thanks yigo

Yigo said:
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su pm disable com.amazon.dcp" .
Click to expand...
Click to collapse
Afraid I can't help you, but in light of preventing other people (and me) to have the same issues:
I assume the /etc/hosts file will survive factory-resets, it's a file that probably is not restored (so immediatly removed the host-lines from mine), but wonder if the pm disable dcp will also survice a reset ? I assume not (core funcationality for amazon, likely in factory-reset group), but you never know, esp. not in the v1 versions we are running.
Anybody knows if this is the case ? I like the pm disable solution, but if this means that borking up my installation will prevent me from ever restoring it (as unable to connect to amazon), I'll have to fall back to the router-blockage solution, and would suggest other ppl to do that as well

Deregistering AFTV may help with registration issue.
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
To de-register your Fire TV-
1 - log on to your amazon account
2 - Hold the mouse over where it says 'Your Account" but do not click. You will get a list of options.
3 - Click "Manage Your Content and Devices"
4 - Click the center tab "Your Devices"
5 - Click on your Fire TV.
6 - Click "Deregister" right below your Fire TV.
You will ge a message saying it there may be a delay for it to take effect.

[email protected] said:
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
Click to expand...
Click to collapse
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it

Still Learning - Passing it on.
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I read your other posting about update blocking.
Seems I did not have my amazon.dcp disabled.
I was not in SU mode when executing command and amazon.dcp was just killed not disabled.
Sorry for any confusion. Thanks

JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I hope one of the folks with a softbricked device gets a chance to see what happens with the over the air update file copied to a fat32 formatted USB stick and renamed update.zip.
With luck, at power on if there is media present, the stock recovery is looking to removable media to see if there's a file named update.zip it can process.
I don't want to softbrick mine to test, though.

So if I am understanding correctly, you should enable updates before you factory reset?

Fire TV1 bricked no lights

This FireTV has never been opened. I blocked updates per Aftvnews guide. ALso from AFTVnews serial conversion to software showed version 51.1.01 or 51.1.02. Unfortunately, I did not recall these version will not get past update screen if you are blocking updates. I had let sit at the update screen for over 30 minutes, then pulled plug. Now no lights, nothing. Tried ALT-PrtSCr-i and ALT-SysRq nothing. I bought USB A-A cable and windows shows QUB-xxxxx(or close to this from memory). Downloaded Ubuntu LiveCD and it shows 6 partitions from 17MB, 6.1GB, 2x 805MB, 2 x 8.4MB.
So not unlocked bootloader, no CWM, no TWRP nothing becasue this was A Virgin AFTV 1.
I have searched, requested help in other threads and no response and do not know what else can be done.
I do not know linux, but can follow steps and have updated 2 AFTV1 with rbox methods.
Is there anyway to save this Virgin AFTV1?

Im in the exact same boat.. But in deeper waters.. Fire Tv is only recognized as Qualcomm com port (Qualcomm HS QDLoader 9008) without showing the partitions, either in windows or linux... Never tried to install a recovery like Twrp, to unlock the bootloader, just had root since day one. But suddenly, when installing the last update something happened after the "Optimizing system storage and applications" menu. A bricked fire tv. Unfortunatelly i cant find a single trick to work... And yes.. I looked everywhere for a solution..

jj^2 said:
This FireTV has never been opened. I blocked updates per Aftvnews guide. ALso from AFTVnews serial conversion to software showed version 51.1.01 or 51.1.02. Unfortunately, I did not recall these version will not get past update screen if you are blocking updates. I had let sit at the update screen for over 30 minutes, then pulled plug. Now no lights, nothing. Tried ALT-PrtSCr-i and ALT-SysRq nothing. I bought USB A-A cable and windows shows QUB-xxxxx(or close to this from memory). Downloaded Ubuntu LiveCD and it shows 6 partitions from 17MB, 6.1GB, 2x 805MB, 2 x 8.4MB.
So not unlocked bootloader, no CWM, no TWRP nothing becasue this was A Virgin AFTV 1.
I have searched, requested help in other threads and no response and do not know what else can be done.
I do not know linux, but can follow steps and have updated 2 AFTV1 with rbox methods.
Is there anyway to save this Virgin AFTV1?
Click to expand...
Click to collapse
Was it a refurb? I had a refurb that had no power out of the box. Sent it back.

cancelyourcable said:
Was it a refurb? I had a refurb that had no power out of the box. Sent it back.
Click to expand...
Click to collapse
No, brand New.
Does the update work thru the usb?

walkabouts said:
Im in the exact same boat.. But in deeper waters.. Fire Tv is only recognized as Qualcomm com port (Qualcomm HS QDLoader 9008) without showing the partitions, either in windows or linux... Never tried to install a recovery like Twrp, to unlock the bootloader, just had root since day one. But suddenly, when installing the last update something happened after the "Optimizing system storage and applications" menu. A bricked fire tv. Unfortunatelly i cant find a single trick to work... And yes.. I looked everywhere for a solution..
Click to expand...
Click to collapse
Yes, I thought we would get some responses from somebody. Possibly even @rbox and @aftvnews.

I wish i was in your situation... You can always dd the partitions again, and eventually fix the brick... In my case (QDLoader 9008) there is nothing i can do. Eventually i could theoretically reprogram the emmc chip, but.. not going to happen. I presume you are in stuck in the Qualcomm HS QDLoader 9006, that should be fixable, since you can write to the partitions. There is a post from Rbox where he tells in detail what to do. Best of luck!

Since your FTV its still showing its partitions (unlike me!) you should be successful with these instructions. https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676

walkabouts said:
Since your FTV its still showing its partitions (unlike me!) you should be successful with these instructions. https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
Click to expand...
Click to collapse
Thanks for the idea, but i did not have any chance to unlock my bootloader. So, this will not help.

jj^2 said:
Thanks for the idea, but i did not have any chance to unlock my bootloader. So, this will not help.
Click to expand...
Click to collapse
You're absolutely right... Unfortunately.. Perhaps someone in a near future discover a way to bring it to life. But for now we're holding useless bricks..

walkabouts said:
You're absolutely right... Unfortunately.. Perhaps someone in a near future discover a way to bring it to life. But for now we're holding useless bricks..
Click to expand...
Click to collapse
Has anyone been able to download update files and put on usbdrive and have the AFTV read the usb?
Please Help

jj^2 said:
Has anyone been able to download update files and put on usbdrive and have the AFTV read the usb?
Please Help
Click to expand...
Click to collapse
From my experiences, won't work. The fire tv don't read the update.zip. Without access to a workable recovery, a unlocked bootloader, or functional ADB, there is no way to revive this thing. I would love to be wrong, though..

walkabouts said:
From my experiences, won't work. The fire tv don't read the update.zip. Without access to a workable recovery, a unlocked bootloader, or functional ADB, there is no way to revive this thing. I would love to be wrong, though..
Click to expand...
Click to collapse
Walkabout,
Thanks for the feedback. Really disappointed of the lack of responses from the XDA Community

jj^2 said:
Walkabout,
Thanks for the feedback. Really disappointed of the lack of responses from the XDA Community
Click to expand...
Click to collapse
To be honest, me too. But probably, since they all have hardware in working conditions, they aren't facing the same problems as us. Perhaps one of this days Rbox bricks his AFTV, and we get a way to solve our problem..

Any news on your brick? Just had an idea, although don't know if it works, and I don't have another working fire TV. But if a backup is made on QPST from a working fire TV, and then restore that same backup on the bricked unit (using again QPST) it might restore the unit. Mmmm.. Eventually! Damn, unfortunately I don't have a good unit to backup!

walkabouts said:
Any news on your brick? Just had an idea, although don't know if it works, and I don't have another working fire TV. But if a backup is made on QPST from a working fire TV, and then restore that same backup on the bricked unit (using again QPST) it might restore the unit. Mmmm.. Eventually! Damn, unfortunately I don't have a good unit to backup!
Click to expand...
Click to collapse
Still bricked, put in box hoping later someone could find a way. Ido have a workingAFTV1, but is rooted and updated to OS5. IF you have any idea how to do this I may entertain.
jj^2

Thanks for the reply! After thinking better about my approach, its pretty much pointless, since to make a backup via QPST we have to enter in EDL mode. And there is no way to make a healthy fire TV enter service mode, not even via fastboot. My bricked fire TV is just like yours, sitting in a drawer. But I haven't given up. At least my mind is busy!

Hey guys I've tried to install https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286,
I did the steps for the locked bootloader and I didn't notice that there were errors.
It is rooted and busybox is installed. But it's stuck at the amazon logo while booting.
Do you think it's possible to unbrick it when I buy an USB-A to USB-A cable?
Version is: 51.1.5.0 30720
Thanks for your help!
Update: Ok I was able to open the stock recovery mode and it was reseting but it still won't boot.
I've waited six hours still didn't boot.

Need help
I messed up with amazon fire tv first generatio, it's now not booting up, no light nothing... when i put male-male usb cable i see its storage but that's all. adb can't find device etc.. any help will be appreciated.

Did I finally bricked my 4k firetv?

I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?

tune345 said:
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
Click to expand...
Click to collapse
TWRP is still there when you restart/boot the stick? (you have to use OTG y cable + mouse in order to check that).
If TWRP is still there, then you can use it to restore a full stock rom or flash the system image.

tune345 said:
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
Click to expand...
Click to collapse
What custom rom (there isn't one available for the 4k)? From a linux install try a lsusb and see if anything is there (preloader or phone). When you were running commands, were you in the hacked fastboot? As @Pretoriano80 said, get in into twrp and flash, here is a link to the latest to flash to restore, but hopefully you made a backup for you started.
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777

Pretoriano80 said:
TWRP is still there when you restart/boot the stick? (you have to use OTG y cable + mouse in order to check that).
If TWRP is still there, then you can use it to restore a full stock rom or flash the system image.
Click to expand...
Click to collapse
TWRP was there but after performing /systemwipe i just see that black screen with firetv logo on the screen it skips the TWRP :/ nothing shows up when i type in adb devices (Minimal ADB and Fastboot) like before it would give a serial number and connected status. nothing in adblink either.
i did ordered that cable like 1 month ago it's not here yet. I might ordered another one today from amazon. I was wondering isn't there any software which can turn laptop keyboard to firestick keyboard from some commands? Adb link has remote which i can use ONCE it's inside the fireOS. A physical keyboard with OTG cable is must for this ? Any alternative ?
and i did search all the first 3 pages of the forum to find the stock rom for 4k firestick but couldn't may be because its was 3 am lol
Thanks for the reply!

Michajin said:
What custom rom (there isn't one available for the 4k)? From a linux install try a lsusb and see if anything is there (preloader or phone). When you were running commands, were you in the hacked fastboot? As @Pretoriano80 said, get in into twrp and flash, here is a link to the latest to flash to restore, but hopefully you made a backup for you started.
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
Click to expand...
Click to collapse
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?

tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Why you installed tank rom in mantis...
Redo kamakiri and flash prerooted.

tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Sounds like you unlocked. Did you make it to twrp?
Lsusb is a Linux command in terminal that will show what is connected. This will tell what mode it is in. I broke a chip off one of mine too (tweezers were a bad thought), but that was 7 months ago missing it and it still runs like the rest of mine sticks. The 4k is called mantis, tank is the fire stick2. Totally different.
---------- Post added at 02:30 PM ---------- Previous post was at 02:26 PM ----------
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Rortiz2 said:
Why you installed tank rom in mantis...
Redo kamakiri and flash prerooted.
Click to expand...
Click to collapse
You never know how deep the water is until you jump head first. I admire people who try!

Rortiz2 said:
Why you installed tank rom in mantis...
Click to expand...
Click to collapse
¯\_(ツ)_/¯
Rortiz2 said:
Redo kamakiri and flash prerooted.
Click to expand...
Click to collapse
I just literally just did that process again after like 7th try but it's still the same not showing up anywhere and black screen with firetv logo. Attaching the picture of the final process, does that mean it's good? it doesn't look like the first process ending.
Thanks !

tune345 said:
¯\_(ツ)_/¯
I just literally just did that process again after like 7th try but it's still the same not showing up anywhere and black screen with firetv logo. Attaching the picture of the final process, does that mean it's good? it doesn't look like the first process ending.
Thanks !
Click to expand...
Click to collapse
That shows you an obvious error in the fastboot step.
Try using a different cable and be sure to do the process from an 2.0 Port.
Since the bootROM part is already done, just type:
Code:
sudo ./boot-fastboot.sh
Connect the stick WITHOUT SHORT ANYTHING and the script will ask to the Preloader to boot to Hacked Fastboot Mode.
When you see "Hacked Fastboot Mode" in the screen of the device, try running fastboot-step.sh again.

Rortiz2 said:
That shows you an obvious error in the fastboot step.
Try using a different cable and be sure to do the process from an 2.0 Port.
Since the bootROM part is already done, just type:
Code:
sudo ./boot-fastboot.sh
Connect the stick WITHOUT SHORT ANYTHING and the script will ask to the Preloader to boot to Hacked Fastboot Mode.
When you see "Hacked Fastboot Mode" in the screen of the device, try running fastboot-step.sh again.
Click to expand...
Click to collapse
sorry where am i entering that code exactly ? because that window was still open with the final error in the instructed directory and i entered that it said command not found so i connected it back to my other laptop and ran Minimal ADB and Fastboot and ran that command there...nothing..
then i went back to linux laptop and close the terminal and re opened a new one and ran that command again said command not found.

tune345 said:
sorry where am i entering that code exactly ? because that window was still open with the final error in the instructed directory and i entered that it said command not found so i connected it back to my other laptop and ran Minimal ADB and Fastboot and ran that command there...nothing..
then i went back to linux laptop and close the terminal and re opened a new one and ran that command again said command not found.
Click to expand...
Click to collapse
You have unlocked and flashed recovery. Do you have a OTG (google if if you don't)? looks like you have TWRP now...

Michajin said:
You have unlocked and flashed recovery. Do you have a OTG (google if if you don't)? looks like you have TWRP now...
Click to expand...
Click to collapse
i have ordered last month, still not here yet. Might order another one from amazon today. isn't there any software which can convert laptop keyboard temporarily for firestick?
and this might be thinking too oddly but lets say i have a micro usb to usb adapter after i plug that in firestick can i take a usb to usb cable and plug it into usb hub? and then plug keyboard mouse usb drive in it ....all going to firestick via usb to usb cable finally converting the signal from usb to usb micro adapter. i believe i have a usb hub which can be powered...
X_X

tune345 said:
i have ordered last month, still not here yet. Might order another one from amazon today. isn't there any software which can convert laptop keyboard temporarily for firestick?
and this might be thinking too oddly but lets say i have a micro usb to usb adapter after i plug that in firestick can i take a usb to usb cable and plug it into usb hub? and then plug keyboard mouse usb drive in it ....all going to firestick via usb to usb cable finally converting the signal from usb to usb micro adapter. i believe i have a usb hub which can be powered... _X
Click to expand...
Click to collapse
No, it has to be a otg. On boot, it will detect it and automatically give you the option for recovery. If you can get into fastboot (you were there before when you ran fastboot.sh you might be able to boot into recovery with fastboot reboot recovery or something simalar. But being in recovery you wont be able to do much unless you have adb connections, or a mouse/keyboard with OTG. Amazon is basically shipping a week for everything right now. I think you really need a OTG to pull it out. ADB and fastboot commands can really screw things up from my novice experience. Get that OTG and try it. I will warn, get one that says it will work for the firestick4k, they dont all work....Make you you give a thanks to the people trying to help, no one is getting paid here...

Michajin said:
No, it has to be a otg. On boot, it will detect it and automatically give you the option for recovery. If you can get into fastboot (you were there before when you ran fastboot.sh you might be able to boot into recovery with fastboot reboot recovery or something simalar. But being in recovery you wont be able to do much unless you have adb connections, or a mouse/keyboard with OTG. Amazon is basically shipping a week for everything right now. I think you really need a OTG to pull it out. ADB and fastboot commands can really screw things up from my novice experience. Get that OTG and try it. I will warn, get one that says it will work for the firestick4k, they dont all work....Make you you give a thanks to the people trying to help, no one is getting paid here...
Click to expand...
Click to collapse
Thank you for that information. Appreciate it. Yea everything is late on amazon now even prime :/ but hopefully i find one which works on the first try otherwise it would be a super bumber...
..but then again how would i know if it's the otg NOT working OR the firestick software/hardware? i did broke one capacitor and was running commands on it like a mad man lol , i believe the CLK one on the picture. what it is for ? why was the firestick still working almost normally after i broke it ? attaching the picture
Thanks again !

tune345 said:
Thank you for that information. Appreciate it. Yea everything is late on amazon now even prime :/ but hopefully i find one which works on the first try otherwise it would be a super bumber...
..but then again how would i know if it's the otg NOT working OR the firestick software/hardware? i did broke one capacitor and was running commands on it like a mad man lol , i believe the CLK one on the picture. what it is for ? why was the firestick still working almost normally after i broke it ? attaching the picture
Thanks again !
Click to expand...
Click to collapse
There are some that say they work. The ones i have had issues with are the OTG hubs. Depending on which chip was damaged, but i broke one off of mine too about 7 months ago (tweezers are bad) but it has been working the same as the rest of mine. could be a heat thing?

Aaahhhhh hit that virus with a brick because i was able to finally fix my firestick last night, pheww!!
thank you everyone for helping
now i need to research the fastest way to clone my ENTIRE setup. I rooted it.

tune345 said:
Aaahhhhh hit that virus with a brick because i was able to finally fix my firestick last night, pheww!!
thank you everyone for helping
now i need to research the fastest way to clone my ENTIRE setup. I rooted it.
Click to expand...
Click to collapse
I have a similar problem with my firestick, How did you manage to fix yours?

Had to do the hardware mode multiple times until i landed at TWRP screen then used adb to flash the stock rom

tinybilbo said:
I have a similar problem with my firestick, How did you manage to fix yours?
Click to expand...
Click to collapse
Were you unlocked? Unless you were playing with recovery, If you have a OTG plugged in from a power off state you should get a recovery option.

Michajin said:
Were you unlocked? Unless you were playing with recovery, If you have a OTG plugged in from a power off state you should get a recovery option.
Click to expand...
Click to collapse
Hi Michajin (Thanks for the reply)
Yes I have an unlocked bootloader, TWRP, and was rooted.
I can get into TWRP via OTG, but it doesn't matter what I flash (Stock or Pre-Rooted), all I get is a black screen (I've left it overnight just to be sure).
I was thinking maybe I should try to flash directly from bootloader rather than TWRP, or making a backup from my other firestick and trying that (the data partition at least).
Either way I'll have to do a little more research first, so any thoughts would be greatly appreciated....