I would like to start off by introducing myself (and apologize if this is in the wrong section). I'm Zach Anyways, I have a 1st gen Kindle Fire and I think I bricked it. I got the replacement one from Amazon and promptly rooted with KFU and installed CWM instead of TWRP. I later decided I didn't like CWM and wanted to go to back to TWRP. From inside of CWM, I deleted and cleared my caches, factory reset, wiped the SD card, and then put the update.zip from Amazon onto the root of my SD card while mounted from within CWM. I flashed it, rebooted, and it is now stuck at the "Kindle Fire" splash screen. Kindle Fire Utility tells me my ADB is online, however the boot status is unknown. I have basically tried every option in KFU and nothing is working. Also, the Unbrick Utility is a piece of s**t and never works, even with ADB. Am I screwed here? I really need my Kindle because there are apps on there that I absolutely require. I really don't want to order/make a factory cable either. Someone please help.
http://forum.xda-developers.com/forumdisplay.php?f=1561
Might be just in the wrong boot mode, the good people in the kindle fire q&a forum will help you.
I fixed it by doing the USB boot mode trick (taking the back off and shorting a metal contact point) everything is working fine now!
Sent from my Amazon Kindle Fire using xda app-developers app
Related
I was using a thread on here because I had installed ICS Launcher and had bricked my kindle. I followed the instructions and everything seemed to be working, but I went to pick up the kindle and accidently click the disconnect button while it was rerooting or rebooting and now its super bricked. It stuck at the Kindle Fire Logo. it doesnt even shine or anything. its a frozen logo. Is there hope for this little fella or should I post him up on Craigslist and sell him for parts?
By his description, he is in fastboot mode. There in the forum has the commands to get him fastboot mode, this happened to me too.
You would get better responses in the Kindle fire section. Anyway if your in fastboot download the Kindle Fire utility. Press 1. Then enter. Then 1 and enter again. That should fix it.
i cant because, im guessing the operation system isnt starting up and the usb doesnt recognize it. im done huh?
Well, looks like I made a mistake. I also hope I put this in the right place...
I ended up rooting my Kindle Fire, and I had installed TWRP and had a backup of the stock OS, to make sure I had somewhere to go after I screwed something up. I also installed CM7 which worked perfect, until I flashed ClockworkMod Recovery. I rebooted soon afterwards (to get into TWRP) and it wouldn't start up. Hard resetting doesn't do anything. No charge light comes on. My computer can't read it.
To me, the only thing left to do is to return in to Amazon in exchange for a new Kindle. Is there anything else that I can do to unbrick it? Any help would be appreciated.
have you read through or searched for unbricking techniques? What have you tried?
http://forum.xda-developers.com/showthread.php?t=1428428
Thanks, but since my Kindle won't turn on the computer can't see it. ;-;
I'm afraid I might have bricked my TF101.
Preceeding the "Bricking"
Rooted with (Spark)?
Flashed Prime ROM.
Got stuck in boot loop. Did a wipe and it loaded up. fast and clean. I should have left it.
THEN, I saw the revolver ROM, decided to load it.
Did a back up with Titanium. Another with Clockwork Mod.
Booted into recovery, and that is when things went south.
An error message about cannot mount sd card popped up. I tried to "go back" but couldn't.
the tablet won't recognize any SD or micro SD.
it is stuck with these two options?
1.boot into recovery: the backside of a robot with a white sign on its back " Ti amat" or something like that. it is hard to read( small font).
OR
2. normal boot pulls up the Asus EE Pad logo and stays there.
Won't let me cold boot into linux either.
Did I brick this thing?
I can't get my pc to recognize the SD on the tablet, I'm out of ideas.
Any help out there? THanks in advance and any noob bashing towards me is well deserved.
Thanks to all for your patients.
I don't have an NVflashable model...so can't help you with that...except to direct you into searching the dev section for the info on Nvflash...and hope that you have a model that supports it. Good luck.
Same opinion, if You have got a nvflashable rom You can't get bricked, just nvflash another rom on it like for example PRIME! rom.
I have a 1st Generation Kindle Fire (DO1400). I had been running 6.3.1 prior to my first attempted root. I am running windows 7 on one pc and Ubuntu Live USB on a second machine. I've been working on this about a month and a half and read and re-read the posts here on Xda and have finally run out of ideas on what to try next to fix my kindle fire.
So how did I get to where I am:
I attempted to Root Device failed using KindleFirerootNew631 tool. The process appeared to get stuck (I should have documented more at the time but was in a hurry to leave for a trip) So I did a forced shut down and left. When I came back and booted the device I ended up viewing a screen that I later learned was commonly known as 'FIREFIREFIRE'.
To resolve this issue I downloaded and ran 'Kindle Fire Utility 0.9.6'. Ran the 'InstallDrivers.bat' script. then started the app. I was able to get Root and then install TWRP, Latest FireFireFire and Google Apps. Everything is working and so I figure hey fixed it once I can again so not why not play around some more. I decide I want to look around in TWRP and see what it offers. I then end up deleting my Kindle ROM (didn't make a backup prior to messing around which was another mistake) So at this point I've got TWRP and I can mount it within windows but have no ROM.
Figuring since I have no ROM I then download the latest stock image from amazon, mounted the device using TWRP, transferred the file in the /bin directory on the kindle. I'm not certain what I selected next but I think it may have been restore defaults. The device powered off, restarted and then remained on the static kindle fire boot loader screen. Checking kindle fire utility I found that the device that ADB Status: Connected. Boot status: Unknown' When I attempted to use adb I could reboot the device, but any attempt by kindle fire utility resulted in the error ' error: exec '/system/bin/sh' failed: No such file or directory' The next time I unplugged/replugged my kindle I was not longer able to ever get the 'ADB Status: connected'. I have since found that if I uninstall the drivers provided by Kindle Fire Utility, unplug/replug in the device I am able to get it to show up as Online but still have status of unknown.
Next after reading I found that many people had utilized a Factory cable to successfully recover. So I set about creating a factory cable using a breakout board from sparkfun and following pinout shown here: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html The factory cable didn't seem to have any impact on the kindle which was confusing to me as I expected it to automatically allow me to connect. I have triple tested the pin outs to verify there are no shorts (excluding the jumper between pins 1 and 4) From further reading I think I found out the kindle fire 'factory cable' to work it must have a working boot loader.
From reading other posts I figured my last attempt would be to try the 'shorting trick' used in conjunction with FireKit Live USB repair kit. (detailed in the post http://forum.xda-developers.com/showthread.php?t=1430038 and http://forum.xda-developers.com/showthread.php?t=1650738 ) I removed the back cover without any issues. The Kindle fire still shows the static 'Kindle Fire' boot loader screen and is detected on both Windows and Ubuntu machines.
Launch Ubuntu on live usb and started firekit. Then ran firekit with command 'usb_fix_parts_and_install_fff_twrp. But was stuck waiting for the device. I also tried with the commands usb_boot_twrp, fix_parts commands while repeating all the shorting/connecting steps and tried with the battery always connected and without it connected and then reconnecting it part way through. I read that some of the firefirefire versions check that it is connected and wil halt if it is not connected. But was never able to get the fire fix to detect the device.
So where am I now:
Currently I am able to charge the battery (I verified this by leaving it running with the static bootloader screen until the battery died, then plugged it in using the charging cable over night, next day I unplugged it for 15 minutes to just see if the boot loader screen would remain on, which it did, I would guess it would go several hours on a charge as that is what it was doing when it last worked). I can still adb device connected but status is unknown. I can also issue reboot commands to the device through ADB. But can not get any tool to find the device in any attempt to install a new boot loader.
So are there any options remaining? Is there something I missed? At this point all I can think of is either trying to replace the sd/mother board or purchase an entirely new kindle fire.
I used the kindle fire utility for the 8.9 and rooted it I was where I was just trying everything and it unbricked it
Sent from my SAMSUNG-SGH-T989 using xda premium
I am in the exact same situation. If I come across a solution i will let you know. I have tried what the other comment said with no luck. If you figure something out let me know.
Sent from my PantechP8010 using xda app-developers app
ok. i successfully rooted this kindle with "root with restore by Bin4ry." i am pretty sure i was on version 7.2.1. i made an attempt at installing a second bootloader with TWRP using seokhun's noob-proof tutorial, step by step. bam, brick. maximum bootloop. i then went to use KFHD System.img restore tool, to no avail. KFFA, no-go. i made a factory cable to get it into fastboot, and it works- the only life it shows is fastboot screen or bootloop with the kf logo. only in fastboot with a regular usb does adb recognize a connection. now, my main goal is to just recover from this brick and carry on. i have scoured the forum and got the same thing every time. is it a permanent brick?
i'm not a complete noob, i have plenty of experience rooting and flashing several models of htc androids. this is just super confusing, cuz i can usually fight thru stuff like this. any guidance is appreciated!