Develop Bugs

[ROOT][WIP] root 6.2.1 / install TWRP / unbrick any ROM

A while back, I posted about forcing the Fire to boot over USB instead of from the internal memory. This trick requires you to open the back of your Fire, but after that the only tool you need is a pair of tweezers, sharp scissors, bent paperclip, or anything else with a fine point that can short two things together. After that, it's all cake to boot FIREFIREFIRE, then TWRP, then adb in and have your way with the Fire's memory.
Now that 6.2.1 is here ruining our party, it's time to package this up for anyone to use.
As useful as they are now, fastboot cables may not work in the future. They rely on the bootloader to work, and it's possible that a future OTA could disable fastboot.
For the adventurous. This is mostly untested by me, and runs a good risk of fuglifying or permanently breaking your Kindle. If you haven't voided your warranty yet, this will.
Install TWRP over USB
0) You will need a PC with Linux and working adb, the .zip attached to this post, and the installer version of TWRP[/URL]. Also a microUSB cable. And something to short the contact like tweezers or a bent paperclip.
1) Unpack the rekindle .zip and copy TWRP into the directory it creates. Change directories into rekindle/
2) Open a terminal and sudo or su to root. It's easier that way.
3) Unplug the USB or AC adapter if it's plugged into the KF. But have the USB cable's A end plugged into the PC. This is very important.
4) Turn the power completely off. Do a shutdown if actually running Android, or hold the power button until there's no LED or backlight.
5) Pry open the back cover. The iFixit teardown (Google it) gives some ideas on how to do it, but be really careful because it's easy to snap the tabs along the long sides.
6) The power must still be off. If you accidentally powered it back on, turn it back off.
7) Run:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
This will chain load aboot, FIREFIREFIRE, then TWRP.
8) Short the point shown here to the metal frame around the CPU area using your paperclip or whatever. While keeping it shorted, plug in the USB cable. This will power up the Fire with the CPU in USB boot mode.
9) If it works, you'll see some text fly by in the terminal, and you'll see the yellow triangle hopefully followed by TWRP starting up. You can follow the instructions in the TWRP post on completing the install.
Rooting 6.2.1
***This likely won't work***
There are reports of problems booting after applying this bootimage. Try the TWRP install above and one of the root update.zips instead.
0) You must already be running 6.2.1. Otherwise try a safer method.
1) Get the rooted 6.2.1 bootroot .img from here..
2) Follow the procedure to install TWRP above, but stop before step 7 (the usbboot command). You can skip downloading TWRP.
3) Run this command instead:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot flash boot 6_2_1rootboot.img
4) Then continue at step 8 until the fastboot flash command finishes.
5) Hold down the power button until it powers off (~15 seconds), and press it again to power it back up.
Windows & OSX support
Currently usbboot is built for Linux only. I had experimented with building it against libusb for Windows and OSX. Unfortunately the window to make the connection before the CPU resets again is about 2 seconds, and Windows takes a lot longer than that to enumerate new USB devices. I don't know about OSX, but I guess a libusb version (usbboot's USB code is Linux-centric) would work fine. Github is here if you want to take a crack at porting it.
Successes? Failures? Smoking hole in the ground that used to be your Kindle? Post here.

LOL really bad news for Amazon.
Can't wait for the full guide.
Thank you m8

how about a quick run down on how to do this now? I have some time and really want to mess with this thing

foxdog66 said:
how about a quick run down on how to do this now? I have some time and really want to mess with this thing
Click to expand...
Click to collapse
Moved into the main post.

EDIT
1st borked usb ports, then i got it to work
!CONFIRMED WORKING!

Proof?? Show us a pic dude!!!

How did you get the back off without scratching the hell out of it...or is it all scratched up now? Lol

foxdog66 said:
How did you get the back off without scratching the hell out of it...or is it all scratched up now? Lol
Click to expand...
Click to collapse
some scratches, and i only used 2 id/credit cards
beepFTW said:
Proof?? Show us a pic dude!!!
Click to expand...
Click to collapse
proof you say? i was in irc the whole time with Vashypooh
plus im running cm7 now

Cool! Thanks man, the whole community thanks you. Any chance of a youtube tutorial? I think many of us will need it. Haha

good work mate keep it up!

pokey9000 said:
For the adventurous. This is totally untested as of now, and runs a good risk of fuglifying or permanently breaking your Kindle. If you haven't voided your warranty yet, this will.
0) You will need a PC with Linux, adb and fastboot installed and known working, a copy of the omap4boot for Kindle Fire from this post, a copy of FIREFIREFIRE, the older TWRP 2.0 that doesn't have the FIREFIREFIRE installer (or use the other if you want to install TWRP and FIREFIREFIRE automatically). Also a microUSB cable. And something to short the contact like tweezers or a bent paperclip.
Click to expand...
Click to collapse
Hi, a silly question here, as you did say one will need a linux machine, but...
Can it be done under Windows 7 64bit?
If so - what software will I need apart from adb shell access, FIREFIREFIRE and TWRP 2.0?

dalogrus said:
Hi, a silly question here, as you did say one will need a linux machine, but...
Can it be done under Windows 7 64bit?
If so - what software will I need apart from adb shell access, FIREFIREFIRE and TWRP 2.0?
Click to expand...
Click to collapse
this has linux only binaries, use on linux

So just to be clear this works with 6.2.1 so would allow a downgrade to 6.2 or a sidegrade to the hacked 6.2.1 image with root enabled?
Sent from my Kindle Fire using xda premium

Should allow you to flash anything that can be flashed by fastboot.

Very cool. I was wondering if this CPU supports leaving it like that but still being able to boot normally, much like FIREFIREFIRE where it starts in fastboot mode, then after a short time, switches to normal boot. There is a hack for the Galaxy S phones that works like this. You short a point on the board, then leave it that way. Now when you boot, it will try to boot from USB, and if that fails, switches over to internal flash. This would be a very nice mod to have.

ttabbal said:
Very cool. I was wondering if this CPU supports leaving it like that but still being able to boot normally, much like FIREFIREFIRE where it starts in fastboot mode, then after a short time, switches to normal boot. There is a hack for the Galaxy S phones that works like this. You short a point on the board, then leave it that way. Now when you boot, it will try to boot from USB, and if that fails, switches over to internal flash. This would be a very nice mod to have.
Click to expand...
Click to collapse
Yes, it does, but it would take some soldering and more than shorting just one pin. Also we haven't identified all the boot mode pins.

dalogrus said:
Hi, a silly question here, as you did say one will need a linux machine, but...
Can it be done under Windows 7 64bit?
If so - what software will I need apart from adb shell access, FIREFIREFIRE and TWRP 2.0?
Click to expand...
Click to collapse
Not silly, I've tried to get usbboot to work on Windows when I developed a Nook Color version, but the Windows USB stack sucks. If it were to work, it would piggyback on either libusb or the Google USB driver, either of which have 32 and 64 bit versions. Windows gurus are welcome to lend a hand.

Stuck on Kindle...
I have the 6.2.1 update so tried this.
I followed the instructions but when I `fastboot reboot` the screen goes black. When I power it down manually and then turn it back on it hangs on the initial Kindle boot screen, it never gets to the animated Kindle boot screen.
Code:
# ./usbboot aboot.bin u-boot.bin; fastboot flash boot 6_2_1rootboot.img
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
< waiting for device >
sending 'boot' (3234 KB)...
OKAY [ 0.814s]
writing 'boot'...
OKAY [ 1.155s]
finished. total time: 1.969s
MintBookPro kindle # fastboot reboot
rebooting...
finished. total time: 0.001s
#
I noticed the fastboot command didn't have ./ in front of it so tried that with the same results, it just hung on the Kindle boot screen.
Out of curiosity I tried the TWRP image and that worked so I was able to install the full rooted 6.2.1 (not just the boot image) from TWRP and now I have 6.2.1 rooted.
So I don't think there was anything wrong with your app, that seemed to work fine, but the plain 6.2.1 boot image seems not to work. Which isn't your issue but anyone that tries this needs to be aware of it.

Great work pokey9000! Very interesting what you are doing.
A couple of questions if you can spare the time.
1) What bootmode is it that shorting the pin enables?
2) As I have a factory cable, would this do the same without popping the case?
Also, and this is off topic and possibly already asked and answered, but I'm curious of your thoughts of the possibility to just select boot from usb on power up from the device, maybe through a utility such as TWRP or some other. Seems that if that could be done, one could greatly increase the size of storage, effectively circumventing the current internal storage limitation. And since the usb is removable and rewritable, you could revert to an earlier version archived on a pc if any updates get pushed that break something.

mikbe.tk said:
I have the 6.2.1 update so tried this.
I followed the instructions but when I `fastboot reboot` the screen goes black. When I power it down manually and then turn it back on it hangs on the initial Kindle boot screen, it never gets to the animated Kindle boot screen.
Click to expand...
Click to collapse
Corrected my directions to hard power off. Reason is that the boot mode gets detected on cold reset, and the reboot warm resets and so doesn't detect the new bootmode. I suppose we could add something to override the boot mode when you call reboot if it detects that USB is the boot device. Code is already there to do something similar with bootmode 4003.
I noticed the fastboot command didn't have ./ in front of it so tried that with the same results, it just hung on the Kindle boot screen.
Click to expand...
Click to collapse
My bad, fixed.
Out of curiosity I tried the TWRP image and that worked so I was able to install the full rooted 6.2.1 (not just the boot image) from TWRP and now I have 6.2.1 rooted.
So I don't think there was anything wrong with your app, that seemed to work fine, but the plain 6.2.1 boot image seems not to work. Which isn't your issue but anyone that tries this needs to be aware of it.
Click to expand...
Click to collapse
Don't know about this, these directions were created w/o a Fire in my possession. I'll make a note in the OP to try the TWRP method.

Unbricking My Kindle Fire

About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM

a very nice post for people who have bricked their kindles and need a factory cable!

Thanks for the kind words Steve. I hope this cable gives you confidence in flashing your Kindle long into the future. Glad it worked out for you.
Oh, and you did not see any evidence of modification because I do not modify the cable, I just cut off the original micro connector and install my own, already modified of course with a resistor and all I have to do is re-solder the 4 wires back onto their original pins and then fill the entire casing with 400 degree SureBonder PDR Hot Glue (the worlds strongest known hot glue, according to them anyway lol)... That way it looks and feels like a true manufactured store bought cable. However, doing it my way is still in fact more work, but the end result clearly justifies it.
Anyway, again glad I could be of service to you and my fellow XDA friends.

Where do I run the command from?

The3rdEye said:
Where do I run the command from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3

smoen02 said:
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
Click to expand...
Click to collapse
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!

andersonrel said:
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
Click to expand...
Click to collapse
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.

kinfauns said:
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
Click to expand...
Click to collapse
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?

andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.

andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I´m gonna try this and will post results. Thanks a lot.

kinfauns said:
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
Click to expand...
Click to collapse
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?

Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have

andersonrel said:
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Click to expand...
Click to collapse
Fix your drivers. Read this:
http://forum.xda-developers.com/showthread.php?p=23747671
djsaxon said:
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
Click to expand...
Click to collapse
First, fix your drivers:
http://forum.xda-developers.com/showthread.php?p=23747671
Then:
http://forum.xda-developers.com/showthread.php?p=25400963

kinfauns said:
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
Click to expand...
Click to collapse
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.

maw230 said:
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
Click to expand...
Click to collapse
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963

soupmagnet said:
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
Thank you.

hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?

jakelongryan said:
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
Click to expand...
Click to collapse
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.

soupmagnet said:
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
Click to expand...
Click to collapse
great advice and exactly what im gonna do. been searching for 2 weeks now reading and learning and still stuck so be looking out for my thread

My Kindle Is Maybe Gone Forever!!!

My Kindle Fire is now maybe gone, forever!
It was a smooth and easy life for me and my Kindle Fire, we've been through root, recovery, bootloader and everthing. She was running fine, until the recent day.
I installed the 1.4 FFF from Hashcode, it was good, I loved the blue Kindle Fire logo. But then the next day I saw an update of 1.4a, so I booted into TWRP recovery and uses ADB (since I'm using Kernel 3.0 without ADB) and does the command:
adb push <filename> /sdcard
Sdcard: Read-Only File System
That was really weird, we all know sdcard is never a read-only, so I thought something was wrong here, I copy the FFF.bin file from my PC to my Sdcard using Mount USB (Still Working)
I tried the second command to install the FFF 1.4a:
adb shell
dd if=\......
And it says I/O error.
I thought I would reboot and live with 1.4 then, but when I reboot system in TWRP, the Kindle never came on again.
It was at 73% battery so there's no chance of a battery drain, but know when I press the power button, NOTHING, no green light, no backlight, it does NOTHING! When I was holding it, it was very very hot at the area around the power button, everywhere else it's cool. I hold it for 20 seconds, left it there and in the evening that area is cool again!
SO I doubt a hardware error, that separate the power button with the CPU,RAM,ROM to power it on or what--so--ever. But the Kindle was smooth until I tried to flash the 1.4a, and what was the problem with the "Read-Only SDCARD", even I can still Mount it to PC and Copy it over. What should I do, should I bring it to the Hardware Fixing Store? Or throw away my Kindle Fire!!!

Try wiping everything
Inviato dal mio Kindle Fire con Tapatalk 2

Recinded

Thepooch said:
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
That's a factory cable isn't it? The problem is my Kindle won't power on, I'm doubting is hardware, will plugging in the factory cable turn on my device, now it's like a REAL BRICK, NOTHING!!!

Recinded

Thepooch said:
Yes that's a factory cable or try this http://forum.xda-developers.com/showthread.php?t=1430038
A factory cable will force your kindle to power on. http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
I hate to bother you like this, but even with no power button working and no backlight? I do think my case is rare, I mean it has to power on to do the commands right?I mean the Kindle is still hot while plug in and charge so I'm guessing it's energy problem? No offense so don't misunderstand this, but if the charger fails in powering on the Kindle Fire, why should the factory cable be a success? (Sorry my English is bad so it sounds offensive)

No offense taken but the factory cable acts as a short and puts your kindle in a state where you can fix the problem so keep reading on how to use this cable. you can also issue fast boot in kfu then power your device on after.

Thepooch said:
No offense taken but the factory cable acts as a short and puts your kindle in a state where you can fix the problem so keep reading on how to use this cable. you can also issue fast boot in kfu then power your device on after.
Click to expand...
Click to collapse
I see now, I guess I will order the cable now! Anyway I was browsing the forum and I see a guy who has the similar problem to mine (which also helped by you!) here: http://forum.xda-developers.com/showthread.php?t=1636107
So there is a problem of the Kindle leaving it can't power on and I'm not the only one that have it! What seems to be the cause and how to prevent this in the future for me and everyone else!

read my thread: bricked after installing fff1.4
Sent from my Amazon Kindle Fire using xda premium

lovejoy777 said:
read my thread: bricked after installing fff1.4
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
There were so many replies in that thread that blurry me, can you tell me how did you unbrick it??
PLEASE HELP!!!

Its not something you can explain in a few short sentences. You have to research it.

Make a usb stick that loads ubuntu, put fk at the root of it.
Take the back of your kindle off, short a certain point on the motherboard, plug your kindle into the computer and run the last command in the list for firekit.

tombombman said:
Make a usb stick that loads ubuntu, put fk at the root of it.
Take the back of your kindle off, short a certain point on the motherboard, plug your kindle into the computer and run the last command in the list for firekit.
Click to expand...
Click to collapse
You make it sound SO easy. Where were you when Lovejoy777 needed help?
(BTW that's a joke, so don't get bent out of shape)

it turned out it was my pc that caused most of my upset. im still sorting it now. iv'e had to wipe my hard drive and start again. just updating ubuntu 11.10 (not upgrading to 12.04 as i think thats when the fun & games started)
next is sdk/adb/fastboot etc :-(
my only tip is read the top link from the first page from tom (and i mean read it) then follow it to the t (no short cuts) and your kindle will boot i'm sure
if you get stuck at a certain bit post back with some detail of where you are at in the process etc. and people will help
Sent from my Amazon Kindle Fire using xda premium

[Q] Kindle fire totally unresponsive after bootloader flash

After flashing firefirefire and twrp 2.1 to a friend's Kindle Fire, the kindle is totally unresponsive. (Yes, I believe I flashed the bootloader incorrectly. I probably flashed the actual .zip rather than a binary.)
Anyways, now:
- The power button never lights, no matter what I do. A/C plugged in, USB plugged in, after holding power button for minutes, after battery disconnected and USB connected, nothing.
- When plugged in to the USB port (Linux running), no messages appear in the syslog that indicate it even recognizes that a device has been connected
- usbboot (with the shorting trick) did not help
- disconnecting battery, then trying usbboot (with the shorting trick) does not help
For what it's worth: I actually accidentally performed the shorting trick on the wrong Kindle (mine) and effectively made it not boot. I WAS able to fix mine using the usbboot (with the shorting trick) and get it back booting. So, I know how this works. One difference I note, when I plugged in my Kindle, and tried the usbboot trick, it did not work (stuck on waiting for OMAP44xx device forever). But when I unplugged the battery, and plugged in the usb cable, at least Linux logged that the USB device was connected, and the power button flashed green, on and off. This other one does absolutely zero - nothing.
It's almost like the USB jack on this Fire is completely hosed. How could flashing the bootloader and recovery do this?
After extensive research, I'm beginning to feel like I'm out of options. The factory usb cable is the only thing I have not tried.
Thanks.
This is the thread I have been following to try to recover. It worked for mine, but not for my friends.
http://forum.xda-developers.com/showthread.php?t=1636883
Update: if you want to know what i did:
sudo ./fastboot -i 0x1949 flash bootloader ~/Downloads/Kindle/u-boot-firefirefire-1.2.zip
(Yeah, I know, just wasn't thinking.)
Update:
I just, on whim, with the battery unplugged, tried the usbboot short trick again, and it worked!
I think I'm back in business.
Update:
After several successful attempts at communication with the device, I was able to get the bootloader overwritten and twrp installed. I had to customize the "usb_fix_parts_and_install_fff_twrp" script to get it to go through. It kept coming back to 'waiting for device'. Maybe I didn't wait long enough. It seemed stuck. Here is my customized script. (I removed the oem format and xloader).
#!/bin/bash
FKDIR=$(pwd)
echo "Loading FFF through USB..."
./usbboot $FKDIR/aboot.bin $FKDIR/u-boot.bin
#echo "Fixing partitions..."
#./fastboot oem format
#echo "Installing x-loader..."
#./fastboot flash xloader $FKDIR/mmcblk0p1
echo "Flash FFF..."
./fastboot flash bootloader $FKDIR/u-boot.bin
echo "Flash TWRP..."
./fastboot flash recovery $FKDIR/twrp2-blaze.img
echo "Resetting bootmode to standard boot..."
./fastboot oem idme bootmode 4000
echo "Loading TWRP..."
./fastboot boot $FKDIR/twrp2-blaze.img
Note: I was running this from my personal Linux (non VM linux system) as root. I just extracted firekit into my download dir and called the commands manually, since I didn't want to bother with a USB stick (since I run linux).

kcburge said:
After flashing firefirefire and twrp 2.1 to a friend's Kindle Fire, the kindle is totally unresponsive.
- The power button never lights
- When plugged in to the USB port (Linux running), not message appear in the syslog that it even recognizes that a device has been connected
- usbboot (with the shorting trick) did not help
- disconnecting battery, then trying usbboot (with the shorting trick) does not help
For what it's worth: I actually accidentally performed the shorting trick on the wrong Kindle (mine) and effectively made it not boot. I WAS able to fix mine using the usbboot (with the shorting trick) and get it back booting. So, I know how this works. One difference I note, when I plugged in my Kindle, and tried the usbboot trick, it did not work. But when I unplugged the batter, and plugged in the usb cable, at least Linux logged that the USB device was connected, and the power button flashed green, on and off. This other one does absolutely zero - nothing.
It's almost like the USB jack on this Fire is completely hosed. How could flashing the bootloader and recovery do this?
After extensive research, I'm beginning to feel like I'm out of options. The factory usb cable is the only thing I have not tried.
Thanks.
Click to expand...
Click to collapse
Unfortunately a factory cable won't help, so save your money. This is caused by a bad bootloader flash. Usually from flashing a corrupt file or a .zip instead of a .bin
If you're using a VM, instead of straight Linux or LiveUSB, that could cause problems as well as the Linux version you are using. It's possible you were able to get yours to work with your current setup because the bootloader was still intact on your device.
Only you would know for sure but it's possible if the battery was low enough then it might have died while installing the bootloader, which would be the only reason you should get a factory cable.

Update:
After several successful attempts at communication with the device, I was able to get the bootloader overwritten and twrp installed. I had to customize the "usb_fix_parts_and_install_fff_twrp" script to get it to go through. It kept coming back to 'waiting for device'. Maybe I didn't wait long enough. It seemed stuck. Here is my customized script. (I removed the oem format and xloader).
#!/bin/bash
FKDIR=$(pwd)
echo "Loading FFF through USB..."
./usbboot $FKDIR/aboot.bin $FKDIR/u-boot.bin
#echo "Fixing partitions..."
#./fastboot oem format
#echo "Installing x-loader..."
#./fastboot flash xloader $FKDIR/mmcblk0p1
echo "Flash FFF..."
./fastboot flash bootloader $FKDIR/u-boot.bin
echo "Flash TWRP..."
./fastboot flash recovery $FKDIR/twrp2-blaze.img
echo "Resetting bootmode to standard boot..."
./fastboot oem idme bootmode 4000
echo "Loading TWRP..."
./fastboot boot $FKDIR/twrp2-blaze.img
Note: I was running this from my personal Linux (non VM linux system) as root. I just extracted firekit into my download dir and called the commands manually, since I didn't want to bother with a USB stick (since I run linux).[/QUOTE]
Nice good job

This is a rather extreme example of excessive quotation of a previous post, something that seems to be endemic to this site. I have seen few if any other web forums, blogs or whatever where people habitually quote fully a long comment that was posted previously, especially when it is likely to appear on the same web page. It's generally considered good practice to quote only the particular statements you are discussing, and to refer back to the post you are discussing by giving its author's id and/or the comment number.
And there is a Thanks button, after all!

aarons510 said:
This is a rather extreme example of excessive quotation of a previous post, something that seems to be endemic to this site. I have seen few if any other web forums, blogs or whatever where people habitually quote fully a long comment that was posted previously, especially when it is likely to appear on the same web page. It's generally considered good practice to quote only the particular statements you are discussing, and to refer back to the post you are discussing by giving its author's id and/or the comment number.
And there is a Thanks button, after all!
Click to expand...
Click to collapse
Sorry, it won't happen again.

How to recover when a bad bootloader flash puts your Fire completely out
I had this same problem, and it came from flashing u-boot.zip instead of the u-boot.bin it contains.
Once flashed and rebooted, the Kindle Fire became completely unresponsive. No power/charge light, USB port appeared completely dead. I called Amazon support and they sent me a new Fire. But I just couldn't accept that it was unfixable, so I kept trying. And I figured it out.
Here's the procedure:
Disconnect the USB cable.
Remove the Fire's back cover.
Disconnect the battery. This step is critical! It ensures that the CPU is completely powered off.
Have your USB cable plugged into the computer, but NOT into the Kindle yet.
Ground the "USB boot" pad on the Fire's motherboard, as described elsewhere (the USB boot shorting trick). Keep it this way for the next step.
Plug the USB cable into the Fire. At this point, the Fire has been turned on in USB boot mode and is being powered exclusively by the USB port. You can now stop grounding the USB boot pad.
Now reconnect the battery. This step is critical!
Use usbboot as documented elsewhere to send a good bootloader via USB and boot with it. You should end up in fastboot mode. AND your power light should be back on, probably green! NOTE This only boots with the bootloader you sent, it does not flash it. The bad bootloader is still installed.
Now use fastboot to install a good bootloader, and a recovery if you want. Or use a firekit script...
Finally you can reboot for real. Make sure it will really reboot before you put the back cover on. You may have to change the bootmode back to 4000.
You now have a working Kindle Fire again.
Why it works. This is conjecture based on my findings:
First, as long as the battery is providing power to the Kindle, the CPU is not powered completely down, even in this case where the device seems totally dead from a bad bootloader flash. Therefore, grounding the USB boot pad does nothing, because the CPU only honors this on powerup. Disconnecting the battery and USB forces the CPU to power down. If you then ground the USB boot pad and connect the USB, the CPU powers up and goes into USB boot mode.
It's possible that if you wait a long time (maybe many days) so that the battery discharges to the point that the battery protection circuitry stops all further drain, you might get the same effect without disconnecting the battery. I didn't have the patience to test this.
Second, the bootloaders I used (two firefirefire versions) apparently check whether the battery is connected, and halt if it is not. I suspect this is true of most/all available bootloaders. So even if you get into USB boot mode and send over a good bootloader, once the Kindle starts booting with that bootloader, if it finds that the battery is not connected, it quits: it never gets into fastboot mode. Hence the "waiting for device" messages noted earlier in this thread. Therefore, as soon as you have gotten the CPU in USB boot mode, but BEFORE you've run the usbboot command, you need to reconnect the battery.
The only thing that remains is to listen to the angel choirs sing.
And wonder why you had to brick the replacement Kindle that Amazon sent--and break some of the tabs on its back cover in the process of fixing it--in order to fail at proving to yourself that you did not cause the problem in the first place. And decide whether you're glad that you now own TWO Kindle Fire's with loose back covers...

Great write up hope I never need to use it but lots of people get stuck in your situation so it should come in handy

That's basically what I did. The problems I had were:
1) not performing the short correctly
I used the wands (not sure what they are called) from an ohm meter (disconnected from the ohm meter) to make the contact with the rail. On one of the Kindles it was easier than the other. I must have tried 20 or 30 times on the one that I had the trouble with. After I had resigned that it was not going to work, I decided to try "one last time", and it worked. So, as someone else said. "Don't give up."
2) not performing the short with the battery unplugged.
I performed the whole operation of booting and overwriting the bad bootloader with the battery unplugged.
Thanks for you input.

switched off...need help
I have kf, its switched off and dont switched on, with the USBboot
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
kf switched on, but its loaded once to yellow triangle then switched off, then i turn on kf and no more yellow triangle.... all do in ubuntu, windows dont recognazes kf. and the firekit allows ones do one of his scripts, and that all. i stuck on firekit, whats i need flash on kf to do it works?

Hi. Thank you for your explanation, but I am having trouble understanding one part. Step 5: Ground the "USB boot" pad on the Fire's motherboard, as described elsewhere (the USB boot shorting trick). Keep it this way for the next step.
Is there somewhere I can see a picture of this or get detailed instructions? I don't want to do it incorrectly. I screwed my Fire 8.9 up after trying to root using the Bin4ry Tool and appropraite 8.9 drivers. Now I have an unresponsive Kindle Fire 8.9. It won't power on at all.
Thank you for any help.

Yeah ... I was looking for a bit more detail on that part.... I just super-bricked my Kindle Fire 7" and am hoping that this Shorting Trick works... but I also am confused at what a Boot Pad is
[email protected] said:
Hi. Thank you for your explanation, but I am having trouble understanding one part. Step 5: Ground the "USB boot" pad on the Fire's motherboard, as described elsewhere (the USB boot shorting trick). Keep it this way for the next step.
Is there somewhere I can see a picture of this or get detailed instructions? I don't want to do it incorrectly. I screwed my Fire 8.9 up after trying to root using the Bin4ry Tool and appropraite 8.9 drivers. Now I have an unresponsive Kindle Fire 8.9. It won't power on at all.
Thank you for any help.
Click to expand...
Click to collapse

Found this buried in the forums
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51

Old thread, I know, but where can I find how to do the shorting trick

Nandr0idC0nsumer said:
Old thread, I know, but where can I find how to do the shorting trick
Click to expand...
Click to collapse
[INDEX] Kindle Fire Development
Sent from my KFFOWI using XDA Labs

sd_shadow said:
[INDEX] Kindle Fire Development
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Maybe I'm being dumb but I can't find it :silly:

Nandr0idC0nsumer said:
Maybe I'm being dumb but I can't find it :silly:
Click to expand...
Click to collapse
post #4 Unbricking
http://forum.xda-developers.com/showpost.php?p=61563704&postcount=4
Sent from my XT1060 using XDA Labs

sd_shadow said:
post #4 Unbricking
http://forum.xda-developers.com/showpost.php?p=61563704&postcount=4
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
Alrighty I've gotten it recognized on my Linux PC as OMAP444x USB Device!
I haven't a clue what to do next. thanks in advance!

Stuck at Kindle Fire Logo [Bricked]

So I downloaded KFU to root a Kindle Fire, And when I chose root permanently with super user, the Kindle rebooted and got stuck at the Kindle Fire logo. The computer won't recognize it anymore so I can't do anything with the usb. It says unknown device in device manager. Is there anything I can do? I'm willing to buy a factory reset cable if need be.

Try the Kindle Fire Unbrick Utility
The "Thanks" button never hurt anyone.

NewPwnage said:
Try the Kindle Fire Unbrick Utility
The "Thanks" button never hurt anyone.
Click to expand...
Click to collapse
I've tried that, but when I click the "stuck at logo" button, it says waiting for device twice, then it says that my device should be unbricked now. Unfortunately, the device remains stuck.
I think the major issue which needs to be addressed is that the computer is not recognizing it as a kindle. Once that is fixed, unbricking it shouldn't be too difficult.

Me too!
Hi,
I just joined specifically so I could post in this thread, because I have exactly the same problem - only difference is the device manager has "android adb interface", with a yellow exclamation point sign, nested under "android phone". The unbrick utility says the Kindle should be unbricked, but it manifestly is not.
Is buying a factory cable the only way to go? Is that very likely to work? Is there any chance at all I can still root it? This is actually the 2nd KF which has had the exact same issue after giving the root command in KFU...

Josepho1997 said:
I sent you a PM.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Really? I'm not seeing it. Would I find it somewhere other than "private messages"?

If you find yourself stuck in fastboot after using kfu and it did nothing but sit and say waiting for device- After a few minutes of sitting simply just long press on the power button till it turns off -then power it back on. the instructions in the terminal literally say just that. It will then send all the required files to your kindle if you selected the permanent root option. Make sure you have allowed installation from unknown sources and have closed the usb connection application prior to making any selection.

Thepooch said:
If you find yourself stuck in fastboot after using kfu and it did nothing but sit and say waiting for device- After a few minutes of sitting simply just long press on the power button till it turns off -then power it back on. the instructions in the terminal literally say just that. It will then send all the required files to your kindle if you selected the permanent root option. Make sure you have allowed installation from unknown sources and have closed the usb connection application prior to making any selection.
Click to expand...
Click to collapse
Is fastboot the mode where it only shows the kf logo? I thought that was the boot loader...or am I just confusing things?
Anyway, thanks for the info, I sincerely hope it will help someone else, but unfortunately I don't know what I could do with it now - I've unplugged it, and now the device isn't recognized by kfu or my PC - and of course, it's stuck at the KF logo. And I'm not positive, but pretty sure that once the kf froze after I issued the root command, I did power it off then back on. Seems like the logical thing to do.

This happened to me. You have to use a factory cable or USB pin short trick which I did. After that it reinstalled my drivers and I then got twrp flashed and then perfection!
***if you choose to do the USB pin trick I'm not responsible for any hardware malfunctions or anything that will make you kindle into a paper weight I'm simply saying its what I did.***
Sent from my SAMSUNG-SGH-I727 Skyrocket on CM10 JELLYBEAN

Me too! please help!
Hello everyone! I feel like I have this exact same problem! My kindle is stuck at the blue and white kindle logo for about 2/3 seconds and then it just completely goes dark! I plug it into my computer and it doesnt even recognize my kindle anymore under my computer, nor does it show "adb android phone" on device manager.. PLEASE HELP ME!!
SUPER urgent! All help would be greatly appreciated!!!

Glad it was an easy fix chrisleealee enjoy the modified stock for awhile but when you do decide to move on here is my pick http://forum.xda-developers.com/showthread.php?t=1778010 don't forget to add system to your scheme of wipes when changing systems good luck and have fun

Wrong thread. Sorry. Glad your issue has been resolved.
---------- Post added at 07:53 PM ---------- Previous post was at 07:46 PM ----------
Use a factory cable. It will make life easy. Sticker on that logo too, same situation. I created my own factory cable and that solved it. Hope this helps.
Also, try to check your adb drivers.