On my AFTV2 I had flashed sloane pre-rooted 5.2.4.0 and TWRP Recovery V3. I decided I wanted to rollback to 5.0.5 because of FireStarter not working. I checked all the boxes under the Advanced Wipe section of TWRP and got the "Warning no OS installed..." error. I rebooted and I am stuck on the white Amazon logo with a slow flashing white LED. Through several attempts to use rbox's unbrick method, I never get past the "Waiting for preloader" stage. My computer detects the fire box but comes up with an error when installing the drivers. I don't know how to go about any repairs if I can't even get connected to it. I see others out there with issues similar to this but never quite find a solution for the lack of usb connectivity to make repairs.
From what I've read, you never wipe /system and then reboot.
It's a shame you did not read the red bold print on the AFTV2 ROMs page here: https://forum.xda-developers.com/fire-tv/development/firetv-2-sloane-prerooted-stock-images-t3309783
It says: WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER
Everything I've read says if you do this you now have a paperweight.
You are indeed correct on all fronts... Thing is I never got to the rollback point. I never even attempted to install the old version over the new one. I got stuck right after the wipe not being able to do anything else. I would gladly take back what I already installed at this point.
WARNINGS
•It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
•It is also extremely important to never reboot after wiping /system.
Lesson learned. I thought it would reboot back into TWRP... I guess not.
I think I may be in this same boat. For some reason, my USB keyboard may have wigged out and ticked System, too.
Ugh
So is there really no solution at all, if you reboot after system wipe in TWRP?
Hello, I had the same issue. Wiped system and had to restart, at least I tought I had to.
So there is no solution than to get the fire tv alive again?
Related
Hi all, I am completley new to all of this side of technology, and rooting my kindle fire seemed an easy task, and it probably is but i think i have well and truly messed it up and any help will make me a happy man again!!!
I carried out the procedure using the KFU, at first my device was not online, so i used the method described via device manager which worked fine, the device was online and i carried out the permanent root with super user, everything went fine, i then went on to install from the extras the google play bit.
This is where things have gone wrong i think, as now the kindle will turn on but it gets stuck on a screen with kindle fire written across it the fire bit is an orange colour, i can get it to boot into twrp screen via the recovery boot aswell.
But everytime i try to connect to the KFU its always say offline no matter what i do. Is there a way to start over agan????
Like i said im new to all of this and have read a few how to's and explanation threads but i get easily confused, lol!!!!
Cheers
You can try clearing the cache/dalvik cache using TWRP and rebooting, but that probably won't help. If you are prepared to lose all of your settings, installed apps, etc. do a factory reset in TWRP and reboot. It should complete the boot process then. Otherwise, you're looking at reflashing the stock software and starting over... in which case, I recommend you just flash modaco and be done with it.
Whatever the case may be, learning about how your device works will help you out in the long run...
http://forum.xda-developers.com/showthread.php?t=1552547
Go back to the Kindle fire utility and press option 1(bootmode) then normal boot (4000) no matter if it says offline it will still work m8.:good:
Give it a shot
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Hmm, off flashing from fastboot should typically work, since you were attempting to flash cm 10.2 I have to ask something because I am slightly uncertain of this myself, but did you ever get twrp running at one point before all this happened, and second if so did you ever wipe any of the partitions or try to flash the ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Unfortunately no. I was never able to get into TWRP as the blue logo has never appeared. Directly after my first attempt at this I rebooted and got the red screen or wall of fire. I "fixed" that by reflashing stock boot, bootloader, recovery, and system image partitions to 8.1.4. Yet instead of a working device I now have either a boot loop or a fixed orange logo. I have gotten the device into stock recovery once (haven't been able to reproduce this result) but it shutdown while the process was underway(About half way??). I have also gotten the device to boot into a animated logo that then proceeded to a data corruption screen, but before I could even read the entire message the device shut off and began another set of boot loops. It looked like a amazon stock os prompt screen. Before this even began I had a normal Kindle fire that I had rooted. I forget what software version it was on before all of this unfortunately.
Sounds like the system image is slightly corrupted or something if the os had that kind of error about data corruption but you said the md5's march so that is weird. You try reflashing the boot partition again since reflashing system didn't work? This is frustrating, mainly because with out adb access from a decent recovery I have no Linux commands to work with, if worst comes to worst I think there's a way to reform at the system partition from fastboot but I wouldn't go for that just yet, I don't know the command offhand but if you did the wrong one I think there's a way it would clear all data on all partitions which would be very very bad. I'll ask hashcode what he thinks cause this is weird.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I have tried flashing all partitions before. Will try again soon. Also, I have another piece of information as well even if it isn't relevant. I originally bricked my Kindle at first, flashed the wrong bootloader. So I bought a for-parts Kindle (Same model) that had a busted screen and took out its motherboard and placed it into my device. Then I rooted the stock os on the new MB and the rest of the story is already in this thread. It still charges and fastboots but nothing other than a static orange boot screen so far. Thank you for helping me out on this; really hope that this can be fixed.
Thinkwithportals said:
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Click to expand...
Click to collapse
"I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick."
I have the same problem but when I try fastboot mode the computer wont even find the device
Alrighty, well. I woke up this morning and decided to re download all of the system, boot, and recovery image files. I flashed them to the device and it again boot-looped for about an hour. I set it up next to me and started reading through the forums for repair via soldering eMMC to SD card reader. I look down and what is starting back at me? A fully working Kindle waiting in initial setup for input... Yet within about a minute it is back into the old boot looping game again. Hardware problem? A short maybe???
possibly or maybe it has a bad emmc chip.
Sent from my LG-P769 using xda app-developers app
Hm, well I think I might just give up on this MB then. I am considering looking into my hard-bricked motherboard and using Kurohyou's pin-out. Even if my soldering skills are a bit rusty.
Thank you anyway for your help. I will report my progress in the other thread from here on out.
Careful not to melt the contact pads, I just ruined one of my Xbox 360 controllers today unsoldering a trigger, cheap parts.... Long story short controller falls in dogs water bowl, circuit board goes in rice, rice gets stuck under a trigger, I ruin controller unsoldering trigger... Least I have 4 more. But anyways yea careful, I suggest at least an st7 tip and not to let it get to hot, read someone else managed to melt a contact on a kf2 I think it was.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi everyone. I have an old firetv that I haven't updated ever since I rooted it.
TL;DR: I would like to update the firmware to either the latest rbox custom rom or the latest official to get external USB disk functionality.
Unfortunately, I can't get past the white fire tv logo screen no matter which method I use (both bootleg rom and the official amazon update process).
adb reboot recovery => white logo. There are no USB devices attached to the firetv fyi while I'm booting.
I rooted my device using the adbfire tool and I distinctly remember I never got the clockworkmod and the bootloader unlock steps to work. I figured I don't really need that anyway, so I've been using the device just fine with Kodi. BTW, the device is not bricked. I just have to replug the power when it gets stuck on the white logo screen for it to go back to normal.
I think I somehow corrupted the recovery partition (if that makes any sense?).
Because I wasn't going anywhere with the unlock->bootleg rom process, I decided I don't care about root anymore.
I reenabled updates (pm enable com.amazon.dcp) and let the device download the latest rom though the amazon system menu. I saw the progress bar go 100% and the device rebooted... alas white logo screen. I gave it half hour then hard boot it. I'm back to my old rom... still works just fine but I need this external usb function for my vacation...
Regarding the boot unlock, the "partial unlock" steps work for me. i.e. I get "Attempting to unlock… All done!". However, the full unlock binary doesn't seem to have any affect after the autoreboot. aftv-full-unlock gives me the long random string as expected before it goes rebooting, but after it reboots and I 'adb shell', it gives me the [email protected] instead of root[email protected] (meaning the unlock didn't work).
How can I recover my recovery?
Just an update, I managed to fix this.
In my case, the aftv full unlock did not give me the root prompt (#) on adb shell. I was running 51.1.0.1.
On a whim, I decided to install the stock recovery (because I couldn't get into cwm) and try upgrading to 51.1.0.2 manually using these instructions http://forum.xda-developers.com/showthread.php?t=2796067
As soon as the system update finished and the firetv booted, I adb shell'd in and voila... root shell. I didn't even have to run aftv full unlock again. Apparently it was already fully unlocked, and I just had to upgrade from 51.1.0.1.
From there, I installed the latest ClockworkMod, upgraded to 51.1.4.0, installed the boot menu, then finally upgraded to the pre-rooted 51.1.6.3!
Hi all, I basically registered here to ask this question, so I hope there's somebody can help me.
I've just applied the rbox root process as defined here : <link removed as I'm a new user and can't post urls, but it's basically the instructions on aftvnews>
There were a few ups and downs along the way, but I sorted out all the minor things in the end and completed the process. Unfortunately my FireTV is now stuck at the white amazon logo.
I can access TWRP recovery, and while I am here I can connect via adb.
I applied rbox's unbrick process to see if that helped matters, power cycled and came back to TWRP (I think I should have been expecting to go to a direct boot there, but not entirely sure). From TWRP I went to do a reboot but it asked me if I was really sure as there was no OS. That sounded like a bad idea to reboot so I reapplied the rooted 5.0.5.1 r1 image that was sitting in my /sdcard directory. Back to the original problem - stuck at the white amazon logo.
I've cleared the cache, cleared the system, reapplied the rooted rom and everything else I can think of, but I always end up back at the same issue. All roms applied using md5 checking, so the files weren't corrupted when I transferred them via adb or anything.
Since I can access TRWP I can't be competely screwed. Really hoping somebody has a suggestion (that will also get my kids off my back as they are currently without netflix )
Nobody?
I can't help feeling this is almost there if I can just get over this last problem!
[SOLVED] (sort of)
OK, in case anybody reads this, this one solved itself. I basically left the fireTV plugged in for several days and when I connected it back to the screen it was working. Not a clue what it was that sorted itself out, but very odd
So, I have this Kindle Fire 1st Gen (2011), and lately I got this urge to customize it and install some further version of Android. Though, with ups and downs I managed, I was pretty much not satisfied with the stability of the customs ROMs.
It was then that I thought the stock firmware was the only best choice for an outdated device like the Kindle fire. So I made my mind to revert back to Stock, wherein I screwed up real bad, left no stone unturned, yet I'm stuck in the rut.
Need Your Help
Let Me Walk you through it all so you'd get a hint where and how I screwed up
1. Rooted the Kindle Fire 1, and installed TWRP 2.2.2.1
2. Tried Installing Custom ROMs, but there was nothing much available for the Stock Bootloader.
3. So opted for the OtterX Bootloader, as they had a variety of ROMs, for which a newer version of TWRP is required, 2.7.X.X, I believe.
TECHNICALLY, EVERYTHING WAS FINE UP TILL HERE
This is where I screwed up while trying to do a roll back..
1. While I was supposed to replace the OtterX Bootloader with the Stock one, I accidentally flashed TWRP 2.2.2.1, first.
2. Clearly, I couldn't boot up into recovery since then, cuz the 2.2.2.1 might be specifically designed for the AMAZON STOCK BOOTLOADER.
3. Before all of that I had wiped away the OS from the device, so I'm stuck here with no OS n no recovery, either.
4. Thought ADB and Fastboot could help, but I kinda remember I screwed up with that too (don't remember exactly what I did).
So this is the current situation
1. NO OS
2. NO RECOVERY
3. I can only setup the fastboot mode, but windows says, it doesn't recognize the device (probably something to do with the drivers, but I've literally rubbed my ass off finding the particular drivers, but to no good)
IF ONLY I COULD SOMEHOW GET FASTBOOT TO WORK, I'D BE GOOD BY MYSELF, I'LL TAKE CARE OF IT ALL, BUT CAN'T, JUST CAN'T
JayZ996 said:
So, I have this Kindle Fire 1st Gen (2011), and lately I got this urge to customize it and install some further version of Android. Though, with ups and downs I managed, I was pretty much not satisfied with the stability of the customs ROMs.
It was then that I thought the stock firmware was the only best choice for an outdated device like the Kindle fire. So I made my mind to revert back to Stock, wherein I screwed up real bad, left no stone unturned, yet I'm stuck in the rut.
Need Your Help
Let Me Walk you through it all so you'd get a hint where and how I screwed up
1. Rooted the Kindle Fire 1, and installed TWRP 2.2.2.1
2. Tried Installing Custom ROMs, but there was nothing much available for the Stock Bootloader.
3. So opted for the OtterX Bootloader, as they had a variety of ROMs, for which a newer version of TWRP is required, 2.7.X.X, I believe.
TECHNICALLY, EVERYTHING WAS FINE UP TILL HERE
This is where I screwed up while trying to do a roll back..
1. While I was supposed to replace the OtterX Bootloader with the Stock one, I accidentally flashed TWRP 2.2.2.1, first.
2. Clearly, I couldn't boot up into recovery since then, cuz the 2.2.2.1 might be specifically designed for the AMAZON STOCK BOOTLOADER.
3. Before all of that I had wiped away the OS from the device, so I'm stuck here with no OS n no recovery, either.
4. Thought ADB and Fastboot could help, but I kinda remember I screwed up with that too (don't remember exactly what I did).
So this is the current situation
1. NO OS
2. NO RECOVERY
3. I can only setup the fastboot mode, but windows says, it doesn't recognize the device (probably something to do with the drivers, but I've literally rubbed my ass off finding the particular drivers, but to no good)
IF ONLY I COULD SOMEHOW GET FASTBOOT TO WORK, I'D BE GOOD BY MYSELF, I'LL TAKE CARE OF IT ALL, BUT CAN'T, JUST CAN'T
Click to expand...
Click to collapse
have you looked at my thread
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT1096 using Tapatalk