Related
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me. (I just installed stock Ubuntu to a flash drive with the fk file on root, I'm fairly certain that's all that needed to be done?)
Anyways, my Kindle is unresponsove, and the usbboot trick has yet to work for me. I really want to save this guy. I've heard the KF cannot be completely bricked through software/flashing. I hope it's true! Any help would be greatly appreciated. Thank you.
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
chris_m128 said:
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
Click to expand...
Click to collapse
Thanks fro replying. I'm pretty sure a factory cable only puts it into fastboot if you have a working bootloader. I don't, so I don't think it would work.
I remember an instance where a friend of mine had a broken bootloader, and we used a factory cable to restore it, this was on the kindle fire. we had to first reflash the bootloader. I hope this is possible here.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
but you'll have to ask someone with more experience than me sorry.
jophish said:
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me.
Click to expand...
Click to collapse
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
Click to expand...
Click to collapse
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
jophish said:
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
Click to expand...
Click to collapse
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
jophish said:
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
Click to expand...
Click to collapse
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
plinders said:
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
Click to expand...
Click to collapse
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Same Here..
I was thinking that all kindle fire are the same... installed fire fire fire using KFU and device got bricked....!
Hope someone here could help us get our devices up and running again...
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
jophish said:
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
Click to expand...
Click to collapse
I am sure they can figure it out. Can you boot into TWRP?
If so, you can still recover...
Dame problem
plinders said:
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
Click to expand...
Click to collapse
Same problem dude, did you fix it?
i.robert said:
Same problem dude, did you fix it?
Click to expand...
Click to collapse
Not yet I'm afraid. Everything I tried so far hasn't worked.
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
No, Absolutely nothing. I really would like to get this working.
jophish said:
No, Absolutely nothing. I really would like to get this working.
Click to expand...
Click to collapse
same here we need a new firekit for the kf2
Help..
any updates on the fix? I hope someone out there could help us revive our bricked kindle fire 2... :angel:
kindle fire 2
flashed wrong bootloader (fff)
no power
no lights
no adb
shorting trick is not working for me :crying:
This is somewhat unique, I haven't found an exact duplicate of this problem yet, but basically I have 2 original KF's. I rooted them months ago, and installed android 4.2 on them. I got a couple new tablets and decided to bring these back to factory defaults, so I went through the process. One worked great and is currently able to do everything as per usual. The second is in a perpetual boot loop. I can't get FFF or TWRP to install because it won't stay booted long enough. It will boot usually with the Kindle Fire gold and white text, and then go to the unlock screen. Once I swipe to unlock, I get a handful of errors about processes not working properly. I can navigate around for right about 20 seconds before it immediately reboots. There is no shutdown process, just a black screen and then the KF logo again. I have a full charge and I am at a loss, any suggestions?
I would reflash the rom.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
I would reflash the rom.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would love to, but I can't get it to connect to the PC long enough to do anything, how can I do that?
jonduben said:
I would love to, but I can't get it to connect to the PC long enough to do anything, how can I do that?
Click to expand...
Click to collapse
This is my problem exactly as well! I got rid of the error messages by clearing the data of contacts, contacts storage and calendar applications.
You can do this from settings -> applications -> all applications
Any help for the continuous lock screen -> home screen -> boot logo -> lock screen -loop would be appreciated!
I ran TWRP and had a custom rom on it before, but then reverted back to stock rom and am now running 6.3.2 from Amazon itself without any custom bootloaders.
So I got mine working, and now I feel really super embarassed.
Not sure which trick finally did it, but here's what I did:
I can't paste links yet as I am a newb user on the forum, but google for "kindle fire usb debugging" and open the result saying "Setting Up Your Kindle Fire Tablet for Testing". Note that there are two steps in that guide, first install the Amazon provided USB-driver and then prepare your Kindle.
Then the embarassing part: change the USB-port. I tried with three different cables and four different ports. Apparently the ports on the front of my desktop pc aren't good for this. After switching ports to behind my pc, Kindle Fire Utility all of a sudden was able to push in TRWP and FireFireFire bootloader!
4th: Wipe EVERYTHING using TRWP. Everything might not be necessary, but I figured why not. Even the SDcard had to go.
5th: Push in an older TRWP with instructions from here: teamw.in/project/twrp2/79
The instructions are a bit messy, after "idme bootmode 4002" you should exit the adb shell and run the fastboot command.
Having the older TRWP seems to be the only way to install Amazon's stock rom, newer ones give me errors. The version I used was 2.2.2.1.
I also installed the 6.3.1 version of the stock rom just to be sure, and let Kindle do the update afterwards on its own.
Everything seems to be working now, hope you'll get yours working too!
kesman said:
So I got mine working, and now I feel really super embarassed.
Not sure which trick finally did it, but here's what I did:
I can't paste links yet as I am a newb user on the forum, but google for "kindle fire usb debugging" and open the result saying "Setting Up Your Kindle Fire Tablet for Testing". Note that there are two steps in that guide, first install the Amazon provided USB-driver and then prepare your Kindle.
Then the embarassing part: change the USB-port. I tried with three different cables and four different ports. Apparently the ports on the front of my desktop pc aren't good for this. After switching ports to behind my pc, Kindle Fire Utility all of a sudden was able to push in TRWP and FireFireFire bootloader!
4th: Wipe EVERYTHING using TRWP. Everything might not be necessary, but I figured why not. Even the SDcard had to go.
5th: Push in an older TRWP with instructions from here: teamw.in/project/twrp2/79
The instructions are a bit messy, after "idme bootmode 4002" you should exit the adb shell and run the fastboot command.
Having the older TRWP seems to be the only way to install Amazon's stock rom, newer ones give me errors. The version I used was 2.2.2.1.
I also installed the 6.3.1 version of the stock rom just to be sure, and let Kindle do the update afterwards on its own.
Everything seems to be working now, hope you'll get yours working too!
Click to expand...
Click to collapse
you can also install the flashable zip version of 2.2.2.1 in current TWRP.
jonduben said:
This is somewhat unique, I haven't found an exact duplicate of this problem yet, but basically I have 2 original KF's. I rooted them months ago, and installed android 4.2 on them. I got a couple new tablets and decided to bring these back to factory defaults, so I went through the process. One worked great and is currently able to do everything as per usual. The second is in a perpetual boot loop. I can't get FFF or TWRP to install because it won't stay booted long enough. It will boot usually with the Kindle Fire gold and white text, and then go to the unlock screen. Once I swipe to unlock, I get a handful of errors about processes not working properly. I can navigate around for right about 20 seconds before it immediately reboots. There is no shutdown process, just a black screen and then the KF logo again. I have a full charge and I am at a loss, any suggestions?
Click to expand...
Click to collapse
I'm having the exact same issue. Were you able to fix yours?
fooz said:
I'm having the exact same issue. Were you able to fix yours?
Click to expand...
Click to collapse
kindle had a custom rom, and then you installed stock update.zip and now it's bootlooping?
sd_shadow said:
kindle had a custom rom, and then you installed stock update.zip and now it's bootlooping?
Click to expand...
Click to collapse
Correct. I wiped everything first, then renamed to update.zip and flashed stock.
Which update did you use? Bin name?
sd_shadow said:
Which update did you use? Bin name?
Click to expand...
Click to collapse
This one. https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.3_D01E_4112920.bin
update-kindle-6.3.3_D01E_4112920.bin
fooz said:
This one. https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.3_D01E_4112920.bin
Click to expand...
Click to collapse
file should be 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
update-kindle-6.3.3_D01E_4112920.bin[/QUOTE]Probably need a fastboot cable to fix, Amazon has locked that version down pretty good.
see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
if the md5 checksum matched
could try the [UTILITY] Kindle Fire Unbrick Utility V1.1
but think it is unlikely that will work, with 6.3.3
.
sd_shadow said:
file should be 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
update-kindle-6.3.3_D01E_4112920.bin
Click to expand...
Click to collapse
Probably need a fastboot cable to fix, Amazon has locked that version down pretty good.
see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
if the md5 checksum matched
could try the [UTILITY] Kindle Fire Unbrick Utility V1.1
but think it is unlikely t will work, with 6.3.3
.[/QUOTE]
Thanks for your help. Will try this and report back.
Started from 6.3.3 on my 1st gen Kindle Fire. I was able to follow instructions to root, convert to OtterX and installed an AICP ROM. I decided I didn't quite like that and wanted to try some other roms. I can't quite remember my train of thought, but for some reason or other I decided to go back to the stock ROM and go from there. I was able to reset to stock partitions and install TWRP 2.2.2.1 and then began flashing the stock rom per shadow's tutorials. However, at about 80% progress on flashing the stock ROM, TWRP froze up. I left it there for a day to see, and after almost 18 hours there had been no change so I did a hard reboot (power button for like 15 seconds) and it shut down. Upon restarting, it tried to boot the stock rom but nothing happens at all.
I've been trying to use Kindle Fire Utility, and Kindle Fire Unbrick Utility, but neither are able to locate the device. I can hear my computer detecting it though, when I plug in and reboot I get the notification sounds that a device is being plugged/unplugged. [edit] It is listed in Device Manager, as Android Phone > Android ADB Interface. But still, no utility like adb, KFU or anything else is able to see the device.
Any thoughts on what I could do to get back to any usable state here? Thanks in advance.
Tomyris said:
Started from 6.3.3 on my 1st gen Kindle Fire. I was able to follow instructions to root, convert to OtterX and installed an AICP ROM. I decided I didn't quite like that and wanted to try some other roms. I can't quite remember my train of thought, but for some reason or other I decided to go back to the stock ROM and go from there. I was able to reset to stock partitions and install TWRP 2.2.2.1 and then began flashing the stock rom per shadow's tutorials. However, at about 80% progress on flashing the stock ROM, TWRP froze up. I left it there for a day to see, and after almost 18 hours there had been no change so I did a hard reboot (power button for like 15 seconds) and it shut down. Upon restarting, it tried to boot the stock rom but nothing happens at all.
I've been trying to use Kindle Fire Utility, and Kindle Fire Unbrick Utility, but neither are able to locate the device. I can hear my computer detecting it though, when I plug in and reboot I get the notification sounds that a device is being plugged/unplugged. [edit] It is listed in Device Manager, as Android Phone > Android ADB Interface. But still, no utility like adb, KFU or anything else is able to see the device.
Any thoughts on what I could do to get back to any usable state here? Thanks in advance.
Click to expand...
Click to collapse
The unbrick utility doesn't work with 6.3.3.
You can't boot to stock if install fails.
Which bootloader? Can you boot to twrp?
Sent from my XT907 using Tapatalk
sd_shadow said:
The unbrick utility doesn't work with 6.3.3.
You can't boot to stock if install fails.
Which bootloader? Can you boot to twrp?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Did not realize that about Unbrick, that explains some things.
I've since gotten over this hump and am now working on different issues. I could not get to a bootloader or recovery at all, until I got a fastboot cable. That changed the device listing on my PC to "Android Composite ADB Interface", and then it was recognized by adb and fastboot, which allowed me reflash a bootloader and TWRP, and get it back to booting into the loader instead of the failed stock ROM installation.
Need some help please
Hi, I have a kindle fire 1st gen. The problem is like this, I can`t get into recovery, I can`t get into OS wich is custom, it is stuck at booting. In device manager I can`t see the tablet/kindle/Amazon Kindle/Android phone. When I restart the tablet right before "booting"for a few second appears in Device Manager as Android Phone. The kindle is white and the fire is blue.
Please give me some piece of information about restore it to original. (windows 8.1 x64, twrp 2.8.5 - and I tried to push a lower version but I dont know if it succeded)
Thank you very much!
rauliulian said:
Hi, I have a kindle fire 1st gen. The problem is like this, I can`t get into recovery, I can`t get into OS wich is custom, it is stuck at booting. In device manager I can`t see the tablet/kindle/Amazon Kindle/Android phone. When I restart the tablet right before "booting"for a few second appears in Device Manager as Android Phone. The kindle is white and the fire is blue.
Please give me some piece of information about restore it to original. (windows 8.1 x64, twrp 2.8.5 - and I tried to push a lower version but I dont know if it succeded)
Thank you very much!
Click to expand...
Click to collapse
Try powering off, connect to wall charger.
Sent from my XT1028 using Tapatalk
sd_shadow said:
Try powering off, connect to wall charger.
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
Hi, thank you for your input.
After I connect to wall charger, the tablet powers up, and I can select recovery or normal. Either one I select nothing happens, keeps saying booting.
rauliulian said:
Hi, thank you for your input.
After I connect to wall charger, the tablet powers up, and I can select recovery or normal. Either one I select nothing happens, keeps saying booting.
Click to expand...
Click to collapse
Guessing that twrp is corrupt
Flashing Twrp in FFF bootloader with fastboot.exe
Sent from my XT1028 using Tapatalk
---------- Post added at 11:53 AM ---------- Previous post was at 11:50 AM ----------
fixed link
sd_shadow said:
Guessing that twrp is corrupt
Flashing Twrp in FFF bootloader with fastboot.exe
Sent from my XT1028 using Tapatalk
---------- Post added at 11:53 AM ---------- Previous post was at 11:50 AM ----------
fixed link
Click to expand...
Click to collapse
Thank you very much man, you saved my kindle. Everything is back to normal.
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.
Like the title says my firestick 2nd gen has been unlocked and rooted for a while now but yesterday it randomly rebooted into twrp and then rebooted since then it won't go past the Amazon logo.
I've tried adb, I tried redoing the bootloader unlock process to recover my device but it's stuck on waiting for boot rom even though lsusb shows mediatek phone like it's supposed to. How can I unbrick my firestick?
MysticFTW said:
Like the title says my firestick 2nd gen has been unlocked and rooted for a while now but yesterday it randomly rebooted into twrp and then rebooted since then it won't go past the Amazon logo.
I've tried adb, I tried redoing the bootloader unlock process to recover my device but it's stuck on waiting for boot rom even though lsusb shows mediatek phone like it's supposed to. How can I unbrick my firestick?
Click to expand...
Click to collapse
my guess is you took a OTA..... You need a OTG and reinstall, then block. Just guessing though.. You dont have the right drivers if your script doesnt see it. If you are unlocked you should still have TWRP and shouldnt need to do the process again... Have you tried a OTG and boot into recovery script?
my guess is you took a OTA..... You need a OTG and reinstall, then block. Just guessing though.. You dont have the right drivers if your script doesnt see it. If you are unlocked you should still have TWRP and shouldnt need to do the process again... Have you tried a OTG and boot into recovery script?
Click to expand...
Click to collapse
If By otg you mean an otg cable, how would that help me? Is there a recovery script that I can run?
MysticFTW said:
If By otg you mean an otg cable, how would that help me? Is there a recovery script that I can run?
Click to expand...
Click to collapse
See post 3 of the unlock thread.
https://forum.xda-developers.com/fire-tv/development/unlock-fire-tv-stick-2nd-gen-tank-t3907002
See post 3 of the unlock thread.
https://forum.xda-developers.com/fir...-tank-t3907002
Click to expand...
Click to collapse
I read the post but The problem is I can't get to twrp, unless you're saying getting an otg cable and plugging in a mouse/keyboard will force it to got into recovery/twrp. Is there a script I can run on windows or Linux that will boot into recovery? I tried the recovery script included in the unlocking tutorial but it's stuck on waiting for preloader.
Even if you can get to twrp do what Michajin says. The same happened to my Fire tv stick 2 and that's the way I fixed it.
See post 3 of the unlock thread.
https://forum.xda-developers.com/fir...-tank-t3907002.
Even if you can get to twrp do what Michajin says. The same happened to my Fire tv stick 2 and that's the way I fixed it.
See post 3 of the unlock thread.
https://forum.xda-developers.com/fir...-tank-t3907002
Click to expand...
Click to collapse
Are you saying if I get an otg cable and plug in mouse and keyboard then while it's stuck at Amazon logo I can force it to go to twrp?
MysticFTW said:
Are you saying if I get an otg cable and plug in mouse and keyboard then while it's stuck at Amazon logo I can force it to go to twrp?
Click to expand...
Click to collapse
did you solve it?