Related
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
Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.
thequietone said:
Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.
Click to expand...
Click to collapse
Are you opening up the case each time you use usbboot?
What Firekit script are you using to boot the device?
What happens when it fails to fully boot in to the system?
Is your battery charged?
usbboot only loads a bootloader into memory temporarily. Once you've got the device booted, you need to flash a new bootloader permanently onto the device. I suggest FFF 1.4a...
http://forum.xda-developers.com/showthread.php?t=1632375
usb boot only
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.
Get it booted temporarily disconnect the battery then reconnect it let it continue to charge via usb maybe it will correct your problem. Or replace your system with something stock like without going fully stock paul has a new release http://forum.xda-developers.com/showthread.php?t=1439916 good luck
usb boot only
So unplugging the battery while plugged in via USB doesn't work, however I am able to get it to boot into ICS I just have to unplug the USB right after the script says Flash FFF... That would lead me to believe it's a problem with the boot loader, but I have tried several times to flash it with fff-u-boot_v1.4a.zip with no luck.
thequietone said:
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.
Click to expand...
Click to collapse
The fact that you are able to use those scripts indicates you are in usbboot mode (4003) or the hardware is defaulting to usbboot on its own which probably indicates that something about your bootloaders is a little off...
Try using the "fix all" script (I don't recall the exact name). This will return your partition table back to stock and then flash both the 1st and 2nd stage bootloaders.
Also try flashing FFF 1.4a again with TWRP and take note of the output it gives you if it fails.
usb boot only
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB
thequietone said:
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB
Click to expand...
Click to collapse
See if you can set the bootmode back to normal and reboot it. Running as root...
Code:
usbboot /root/firekit/aboot.bin /root/firekit/u-boot.bin; fastboot oem idme bootmode 4000; fastboot reboot
usb boot only
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)
thequietone said:
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)
Click to expand...
Click to collapse
Did you ever have Hashcode's CWM recovery installed on your device or have you always used TWRP?
Have you run those Firekit scripts again after you installed FFF 1.4a?
The only other thing I can think of is that your device's bootmode is set to USB boot and that's why it doesn't load up the bootloader already installed on your Kindle Fire. It's seems to be waiting for you to use usbboot to send it a bootloader. Get to TWRP again, flash FFF 1.4a and run these adb command to set the bootmode to 4000 and reboot...
Code:
adb shell idme bootmode 4000
adb reboot
The problem is I can't get FFF 1.4a installed. When I try to do it via TWRP which is the only utility I have tried it appears to load successfully, but when I do the reboot, the screen won't come on and there is no power light. So I hold down the power button for the 20 seconds then run the FireKit commands hook up the USB and it boots back up, but won't boot on it's own.
Have you found a fix yet? I may have a solution from my experience with mine, which was bricked beyond imaginable (don't ask how ). I was able to install FFF+TWRP and restore to stock perfectly fine.
It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.
thequietone said:
It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.
Click to expand...
Click to collapse
You didn't answer the question of whether or not you've used Hashcode's CWMR.
From TWRP, run these commands...
Code:
adb shell idme ?
adb shell parted /dev/block/mmcblk0 unit b print
and paste the output here.
Also, if you can load ICS, download/install smirkit...
http://forum.xda-developers.com/showthread.php?t=1500935
and try to install FFF 1.4a that way. Using smirkit will raw write the bootloader image directly onto the partition.
Here is the screen shot. Couldn't get smirkit installed.
Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!
Still Unresolved
Nope I am still having the same issue. Right now, I just try to keep it charged hoping it won't die, because if it does then I have to USB boot to get it back up and running
dmp2007 said:
Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!
Click to expand...
Click to collapse
shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.
I haven't heard of it responding to touch. Mine works perfectly except for always having to USB Boot if it dies or if someone holds down the power button too long.
QUOTE=dmp2007;28967427]shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.[/QUOTE]
I too get this, I've been through what feels like every thread on here about this, only a few of these show up as the 'usb boot only' though and they all end in no answer. I have tried all forms of partitioning up to and including dd'n the p1.img over top of xloader and p2.img on top of bootloader.
With usb, i can go back fully stock (however, even fully stock wont boot without usb boot.. so its got to be busted xloader or bootloader), i can get TWRP installed, any ROM and its all usable.. until as OP said.. power out or reboot needed. It's bothering me enough just wanting to fix it I keep rebreaking perfectly good installs thinking some nugget I found/missed re-reading endless posts is the one.. just in case someone else comes through with this, here are my findings:
happened to me as originally I bricked to the point had to crack it open and short it to get it to boot via usb, finally working well using liveUSB firekit. However, from that point on, would NEVER boot on its own, and would NEVER shutdown/reboot without needing 20-30s of power button molestation. perhaps this is left over issue of the pin short... dunno
Once i figured out I could usbboot, basically went on with everything as normal. recovery, roms, back to stock, back to rom, etc etc. What seemingly never works, or simply oui can never get to, is the bootloader. All indications that I have known/been able to check seem to think its iinstalling, perhaps we are just never making it to it (xloader death)
So then I went crazy and tried everything from adb/fastboot raw on Mac, windows and linux, setting bootmode to 4000 every way with every tool listed on this site possible.. no joy.. usbboot is a must. Tried zeroing the mmcblk0p1/p2 and writing good versions on top, nothing.
Current state.. if I, via adb/fastboot/twrp/recovery do a reboot or shutdown.. the kindle shuts down screen and led's only (sometimes even leaving the green power light on, but almost ALWAYS just all black, but not off) .. dmesg notes that its stuck in a usb connect/disconnect loop, with an error:
new high-speed USB device number 33 using ehci_hcd
unable to get BOS descriptor
New USB device found, idVendor=0451, idProduct=d00f
New USB device strings: Mfr=33, Product=37, SerialNumber=0
Product: OMAP4430
Manufacturer: Texas Instruments
USB disconnect, device number 33
rinse, repeat, about every 3 seconds.
As you can see, BOS descriptor can't be found.. which is just a little stupid because the port its plugged into is 2.0
bcdUSB 2.00
but maybe there is still something there? not changing any port though, usbboot has no problem.
I sniffed the traffic of the usb bus while plugging in the USB cable after shutting down via 30 second hold, and its pretty much the same thing, just bouncing the connection before it has time to get started.. so it seems to be hitting this "issue" both on shutdown/reboot and startup. As I can't really tell, with usb being the only way for me to talk to the KF, I can only assume after a hard shutdown when I push the button again its probably doing the same thing (no lights, no screen), but I can confirm once I plug in the usb and it tries to boot itself.
Only sort of difference is sometimes it can go down into the dark reboot and I am able to run usbboot and it comes back up (usb never unplugged) but its been sporadic so I haven't chased it.
At this point I just want to figure out exactly what bit needs flipped in the front somewhere so I can reboot my KF like all the cool kids so I'll probably keep hacking on this issue until I really really brick it or hopefully help comes along or I figure it out myself. One good sign is I know have completely working dev/hack environments on OSX, win7, liveusb ubuntu AND linux mint debian so, I guess that is something.
YOU ARE NOT ALONE USBBOOT ONLY PEOPLE!! one love. =P
I want to wipe everything off my Kindle including the recovery and bootloader, is there a command I can issue to do this? (I'll be using firekit /w the short trick and adb push to reinstall my rom/bootloader/recovery)
I can't even begin to tell you why that's a bad idea and completely unnecessary.
Do you mind me asking what you are trying to accomplish with this and why you think it's necessary?
I had the old version of TWRP and bricked my Kindle, I got it to load the new version of TWRP with firekit and it unbricked my Kindle. Next, I set boot mode to normal because I wanted to flash a new rom, however then I got the blinking yellow triangle of death again, I ran usb_fix_parts_and_install_fff_twrp (how I unbricked it before) and shorted it but this time it didn't work and I got the blinking triangle again. So I though if it worked before with new version of TWRP maybe if I removed it completely and the re-ran "usb_fix_parts_and_install_fff_twrp" it would unbrick my Kindle again
Sorry for the long explanation
Oh I forgot, The reason I put it back in normal mode is because I thought I fixed everything and thought the battery would begin to recharge again, so I figured just downloading the rom to kindle itself would be easier than using adb push to transfer it from my computer, but then I couldn't even get back to twrp after the first time
The blinking triangle is due to a dead battery, not the bootloader installation.
Unplug the device and hold the power button until it shuts down completely.
Plug the device into your computer's USB (2.0) port and immediately hold the power button until it shuts off again.
If you can get it to shut down without starting up again, leave it plugged in for at least half a day to let it charge.
aullys and
I'll try that, thank-you
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Since you rooted and unlocked the boot loader... No warranty...so I guess try flash stock ROM...
Sent from my mighty Xperia Arc S
It won't turn on for me to do that in the first place, though.
Mods - I just realized that I posted this in the wrong forum. I apologize for that.
so backstory first:
mother-outlaw drops off her kindle fire..... its stuck in a boot loop ( just keeps cycling the 'kindle fire' logo)
I initially had no idea what version of anything this was but later found S/N and determined to be KF 1
I have run all the utilities KUU, KFU, Etc.... none do anything
when I plug to the wall nothing at all just loop no lights.... when I initially turn it on I get a quick flash with some illegible pixels on screen like its trying to boot but then straight to loop
when I hook to computer using an actual data cable not normal USB.... after sitting overnight the orange light will at some point during the night come on and stay on..... today I let it sit with light on for about 8 hours while gone..... and when I reboot after the light has been on it will stay on as long as connected to computer
I truely have no idea of battery state, ie if its charging, if its charged, where its at, etc
I CAN see the device and issue reboot commands etc through ADB from computer
I am not opposed to total wipe/flash if needed.... of course since this is for my computer illiterate mother-outlaw Im sure it would be better to not start over ( I have confirmed with her however there is nothing that needs to be saved on the device, its for browsing and games only)
Suggestions? Fixes?
I have read hundreds of pages on this forum and others and its all just a jumbled mess in my mind by now..... so now Im calling for HELP
Latest system version 6.3.3 doesn't work well with KFU or unbrick utility
Likely need a fastboot cable
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT907 using Tapatalk