Foreword: don't start hating on my wording. iDevices can't be bricked unless there is some sort of hardware failure, but "Bricking" seems to be the commonly understood Kindle Fire form of saying: the dang thing's in a bootloop. DO NOT WRITE THIS OFF AS MORE OF THE SAME!!! INFO: Windows 7 Ubuntu 10.10 Kindle Fire on 6.3.3 firmware I rooted my brothers Kindle Fire on firmware 6.3.3, using the KFU. It did NOT go smoothly; i was forced to uninstall the KF's drivers on my Windows 7 PC through Devices and Printers. After that i belive i ran the drivers installer after that. This time when i ran the "run" file, the driver was online, bootmode 4000 (Normal of course!) ***NOTE: I noticed later when i side-loaded the SU app i had to repeat the "Delete drivers" process from Devices and Printers*** Later his Kindle decided to download the new firmware, which i belive is 6.3.3, but have no way of being sure. Sadly it started to get stuck in a bootloop, at the FIREFIREFIRE bootlogo. That's not good. At first it was easy enough to get out, but now it's completely stuck in the bootloop. It stays black when unplugged, but as soon as i plug it in it gos back into the bootloop. I didn't think this would be a problem, because i could flash a rom or get it out of Fastboot (I belive Fastboot is 4003???). When i plug it into my computer it doesn't recognize it. I would go into Devices and Printers and repeat the drivers uninstallation (Yes, i understand that is not a word ), but it doesn't show up!!! It doesn't show up in Computer either for that matter. I HAVE adb. I HAVE the android SDK. I DO NOT have a factory cable, nor could i make one. (I guess my grandfather could, he's great at that stuff, but i'd rather not have to have him do that.) I never installed FFF, but it's obviously there because i keep seeing the yellow triangle. I tried two different unbricking utility's, but neither worked because my computer will not recognize the Kindle Fire. I tried looking on XDA, and there's a kajillion different guides, but the ones i haven't tried are waaaaaaaaayyy beyond me. I know HTML and some PHP but none of those are remotely helpful here. Can you help me? If you need any more details AT ALL i will add them quickly. Thanks... if you can help me I won't be $200 poorer... P.S. I added the fasboot key to the adb driver in the .android folder. For the Kindle Fire it's 0x1949... and don't just tell me to go to XDA, i already have. P.P.S Sorry for the grammar and spelling, i whipped this thing out in like ten. P.P.P.S Man, i haven't been on here for awhile huh?
First of all, bricking on any device is when the device is only useful as a brick, if your fire is bricked then it's unrecoverable. People call boot loops bricks all the time, but they are not correct. Do other computers not recognize the Fire as well?
Well it is about as useful as a brick right now. To answer your question no, it is not recognized on any of the PC's I've tried it on (win7, another win7 and a Windows XP)
Not big on Android, especially Kindle Fire, but I have gotten boot loops in a MyTouch 3G and Galaxy S and I honestly don't know exactly what I did but I just kept putting them into different modes and trying different programs (Even though it was not always picking up) until it would show up on my pc then I would reflash stock FW. Unless someone knows what to do, I say play with the different modes. If it is indeed bricked, going to have to get a new one. But again, I had these problems on 2 phones and I got them working again. the MyTouch literally took me a week to get working.
I don't remember what I used to flash, but I just put it into Recovery mode and wiped it and did pretty much all the things I could from the phone itself until my PC picked it up.
Just hold down a sequence of random buttons while plugged into a computer and see what happens, worked for me.
UPDATE! Now using fastboot and adb through CMD i can bring up the commands needed, but when i use them it says <no device detected> or is blank under devices connected Please help
