I've tried looking through lots of other threads, but I can't find a problem similar to this.
I tried to root my kindle fire using these instructions:
http://forum.xda-developers.com/showthread.php?t=1568340
It all worked until I got to the
fastboot -i 0x1949 flash recovery <name of recovery image here>
step, which appeared to hang. I was doing this on a mac, so I thought that was the problem. It was late so I went to bed. In the morning I tried to boot my Kindle Fire, but now I can't access it at all.
Without the USB cable plugged in it won't boot at all. With the USB cable connected the yellow logo comes up for a few seconds, disappears and continues in that loop. Pressing and holding the power button does not change anything.
I can't get the Mac to recognise a USB device when it is plugged in. I tried linux (under VMWare) and lsusb reported nothing either.
Does anyone know what I can do to get the KF back to a state where I can at least communicate with it?
jdswain said:
I've tried looking through lots of other threads, but I can't find a problem similar to this.
I tried to root my kindle fire using these instructions:
http://forum.xda-developers.com/showthread.php?t=1568340
It all worked until I got to the
fastboot -i 0x1949 flash recovery <name of recovery image here>
step, which appeared to hang. I was doing this on a mac, so I thought that was the problem. It was late so I went to bed. In the morning I tried to boot my Kindle Fire, but now I can't access it at all.
Without the USB cable plugged in it won't boot at all. With the USB cable connected the yellow logo comes up for a few seconds, disappears and continues in that loop. Pressing and holding the power button does not change anything.
I can't get the Mac to recognise a USB device when it is plugged in. I tried linux (under VMWare) and lsusb reported nothing either.
Does anyone know what I can do to get the KF back to a state where I can at least communicate with it?
Click to expand...
Click to collapse
I think you have a dead battery....
http://forum.xda-developers.com/showthread.php?t=1623244
FWIW, I've noticed a number of Mac fastboot problems being posted here lately. I tried this for myself to see what was going on. Although it will respond to 'fastboot devices' and 'fastboot getvar product' commands, it stalls while trying to send the image to the KF. I've tried several different copies of fastboot and they all do the exact same thing for me. No "fastboot flash" or "fastboot boot" commands will get past the sending stage.
VMWare might also have issues with fastboot as I've heard some rumblings about that as well. I'm a Parallels Desktop user and I've never really encountered any problems along these lines in my Windows or Linux VMs.
I think your next best bet is to build a Ubuntu Live USB system on a thumb drive and try using that on your Mac.
I've been speaking with kinfauns about this fastboot/Mac problem that's come up recently. I've been using Mac since I rooted my Kindle Fire and I've never had a problem with it in regards to adb or fastboot.
Have you installed any OSX software updates lately?
Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.
Jared631 said:
Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.
Click to expand...
Click to collapse
When you say, " the bootloader diddn't seem to install", could you be more specific?
What does your boot screen look like now?
Were there any error messages?
Did fastboot hang at "waiting for device"?
Do you have custom recovery installed?
Of so, what custom recovery do you have installed?
soupmagnet said:
When you say, " the bootloader diddn't seem to install", could you be more specific?
What does your boot screen look like now?
Were there any error messages?
Did fastboot hang at "waiting for device"?
Do you have custom recovery installed?
Of so, what custom recovery do you have installed?
Click to expand...
Click to collapse
1. Boot screen is saying "KindleFire" the stock one not FFF.
2. No error messages
3. Yes, it hangs at "waiting for device"
4. No I don't
That's what I meant by "It diddn't seem to install".
Okay, the "waiting for device" simply means the drivers aren't working properly. I do not use Windows so I cannot offer any real help other than to tell you to reinstall them. There is a world of different suggestions for fixing the driver problem that you can find by searching the forums or even Google, but they're all hit and miss.
I will tell you to work on the driver issue until you can't take it anymore and then consider, possibly, other options.
Well, I might as well as just use soupkit, as I am dualbooting Ubuntu and Windows XP Pro. I have to wait a bit untill I can use it but, I have it all setup, so I'll get back too you when I get to try it out. If this doesn't work I will do the reinstall drivers, like you said, and hopefully that works. Thanks, for the help!
Update:
Soupkit diddn't work. (FK, not USBboot)
So, now onto Windows XP driver reinstallation.... Yay...
If this doesn't work I guess ill have to do the shorting trick.
Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.
UPDATE:
Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"
I also have this same issue as well, was going to root my stock 6.2.1, but unplugged it on accident, no FFF, and stuck on the stock orange kindle fire logo.
Jared631 said:
Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.
UPDATE:
Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"
Click to expand...
Click to collapse
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
soupmagnet said:
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
Click to expand...
Click to collapse
thanks, mine showed up what you wrote and changed to normal mode, and finally used ZombiePiratez unbrick tool and worked:good:
soupmagnet said:
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
Click to expand...
Click to collapse
Thanks. I'll check that out. So to be clear it should just inform me of what mode it is in, correct? Not fix it.
What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.
Yay.... Progeress?
soupmagnet said:
What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.
Click to expand...
Click to collapse
Alright, here is what I got.
Bus 002 Device 003: ID 1949:0006 Lab126
So that means it is in normal mode, correct?
----------------------------------------------------------------------------------
Don't know if this helps but,
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.
What does "lsusb" give you in fastboot mode?
Adb devices
soupmagnet said:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
Click to expand...
Click to collapse
This is what happens.
Code:
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb kill-server
[email protected]:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:~$
soupmagnet said:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.
What does "lsusb" give you in fastboot mode?
Click to expand...
Click to collapse
Also, what is the output of...
sudo /etc/udev/rules.d/51-android.rules
Jared631 said:
Alright, here is what I got.
Bus 002 Device 003: ID 1949:0006 Lab126
So that means it is in normal mode, correct?
Click to expand...
Click to collapse
Before you guys get too far off track...
1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader. These two numbers alone are insufficient to determine the "mode" of the device, so you might very well be in fastboot mode. If you get these numbers, you have to take a look at the bcdDevice value.
Code:
lsusb -v | grep bcdDevice
1.00 is the bootloader.
2.16 is one of the others.
More info here...
http://forum.xda-developers.com/showthread.php?t=1668159
sudo /etc/udev/rules.d/51-android.rules
soupmagnet said:
Also, what is the output of...
sudo /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
Code:
[email protected]:~$ sudo /etc/udev/rules.d/51-android.rules
sudo: /etc/udev/rules.d/51-android.rules: command not found
[email protected]:~$
Here is what I have in the file it's refering too.
Code:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.
Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.
Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.
As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)
kinfauns said:
1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader
Click to expand...
Click to collapse
I knew that. I just forgot, that's all. ::looks around::
soupmagnet said:
Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.
Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.
Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.
As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)
Click to expand...
Click to collapse
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)
Jared631 said:
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)
Click to expand...
Click to collapse
If (when) you try the shorting trick, it's best to use a sharp pair of tweezers or a safety pin to keep from losing the connection while plugging the USB cable in. And the picture of the actual point posted on Pokey's thread is a little misleading...it's considerably smaller.
Howdy all,
I have a 1st Gen Kindle Fire that I apparently have corrupted. I pushed TWRP onto the device prior to rooting it and rebooting, and the device is stuck at the orange "kindlefire" logo. I've tried the KUU but the device is not detected by adb or fastboot. I've unloaded and reloaded the drivers to no avail. The device is detected as an "Android ADB Interface" which i'm not sure if that's the proper device name or not. I've tried not only the amazon provided kindle drivers, but the google drivers from the platform sdk and some of the other drivers from the forums here. In all cases, I'm unable to query the device via "adb devices" or "fastboot devices."
My last hope was to buy a fastboot cable to try to force the unit into fastboot mode, however it doesn't appear to be doing anything. The device boots and continues to stay in the kindlefire logo.
I checked the cable with a multimeter and I am indeed getting +5 on pins 1 and 4, so I can confirm the cable is a fastboot cable.
At this point, I'm pretty much out of ideas. Does anyone have another way of getting into fastboot mode? Is there a way to do it via an internal circuit short or pin jumpering?
Dirty Pete said:
Howdy all,
I have a 1st Gen Kindle Fire that I apparently have corrupted. I pushed TWRP onto the device prior to rooting it and rebooting, and the device is stuck at the orange "kindlefire" logo. I've tried the KUU but the device is not detected by adb or fastboot. I've unloaded and reloaded the drivers to no avail. The device is detected as an "Android ADB Interface" which i'm not sure if that's the proper device name or not. I've tried not only the amazon provided kindle drivers, but the google drivers from the platform sdk and some of the other drivers from the forums here. In all cases, I'm unable to query the device via "adb devices" or "fastboot devices."
My last hope was to buy a fastboot cable to try to force the unit into fastboot mode, however it doesn't appear to be doing anything. The device boots and continues to stay in the kindlefire logo.
I checked the cable with a multimeter and I am indeed getting +5 on pins 1 and 4, so I can confirm the cable is a fastboot cable.
At this point, I'm pretty much out of ideas. Does anyone have another way of getting into fastboot mode? Is there a way to do it via an internal circuit short or pin jumpering?
Click to expand...
Click to collapse
So, I'm an idiot -- when I was running fastboot I was not specifying "-i 0x1949" in my arguments, which apparently was necessary to make fastboot find the device. I've now done that and have unbricked the unit successfully.
To reiterate, when using fastboot on a kindle fire, be sure to have -i 0x1949 so fastboot can find the unit properly.
I have searched and read a bunch and have not stumbled upon my situation.
Hopefully someone can shed some light on my use of a factory cable.
Bought a cable from SkOrPn - great guy and very helpful. We thought maybe the problem was the cable so he sent out another. TO BE CLEAR, ISSUE IS NOT WITH SkOrPn's CABLE. Both cables yield the same results.
So, here's the deal:
I have 2 KFs that where bone stock. I used KFU to root, install TWRP and FFF 1.5 Bootloader. All worked fine and I subsequently installed CM11. So all is good.
Now when I try to use the Factory Cable as instructed
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Click to expand...
Click to collapse
But when I plug the Fcable into the fire it immediately powers on and boots normally, skipping fastboot mode. This happens with or without plugging the other end into the PC.
So SkOrPn suggested I try plugging into the PC 1st and then the fire. This does boot to fastboot mode. So now I unplug the Fcable and using a "normal" cable plug the fire back into my PC. Now I get an error message saying that the USB device cannot be installed and of course KFU/ADB/fastboot does not recognize my device. So I am (or appear to be) in fastboot mode, but can't communicate with my fire. Keep in mind I have KFU working, so I know drivers are installed.
Any thoughts?
And the above is the same for BOTH fires.
Luckly I am fully rooted with FFF 1.5 and CM11, so I really dont need to use the factory cable. But I would like to figure this out BEFORE I need it!
micl9 said:
...So SkOrPn suggested I try plugging into the PC 1st and then the fire. This does boot to fastboot mode. So now I unplug the Fcable and using a "normal" cable plug the fire back into my PC. Now I get an error message saying that the USB device cannot be installed and of course KFU/ADB/fastboot does not recognize my device. So I am (or appear to be) in fastboot mode, but can't communicate with my fire. Keep in mind I have KFU working, so I know drivers are installed.
Any thoughts?
And the above is the same for BOTH fires...
Click to expand...
Click to collapse
Just because you can run kfu, and you got your kindles rooted, that doesn't necessarily mean your drivers are installed properly.
I would uninstall and reinstall your drivers just to check.
Also, when you plug in your kindle in fastboot mode, does you're computer list it as a fastboot device? (Command Prompt, cd to folder with KFU tools are and adb.exe and fastboot.exe are, then type fastboot devices; a string of characters is good, while nothing is bad)
If that doesn't work, can you use kfu to reboot your kindles into fastboot?
Sent from my Nexus 7 using Tapatalk
I tried uninstalling and re-installing drivers - might try a fresh computer
When connected in fastboot mode devices command comes back with nothing.
I will try using KFU to put the kindle into fastboot when I get home tonight.
Update:
OK so KFU can put it into fastboot - witch matches behavior using cable, so now I know that works.
And my PC does not recognize the kindle in fastboot mode. Tried UN-installing and re-installing drivers with no luck. As this has been my "hackers" laptop for quite a while there is no telling what driver ghosts remain.
Will give it a shot on another PC.
Still kinda odd that my Kindles require a different factory cable procedure to get into fastboot mode.
Post once you try it on a fresh PC.
Sent from my Nexus 7 using Tapatalk
Ok most issues are resolved
KFU
Apparently while in fastboot mode KFU will report status unknown, but using bootmode menu to change back to Normal works.
Also using adb devices in fastboot mode returns nothing, using fastboot getvar product returns kindle!
For these 2 I should have read more - sorry
USB reporting device cannot be installed after having device in fastboot mode via factory cable.
OK this one I got some bad info that said the factory cable is not used for flashing - only for getting device into fastboot mode.
What I was doing wrong - using Fcable to get into fastboot and then swapping the Fcable out for a std USB cable - this results in the device cannot be installed error and kindle not being seen by fastboot commands.
What I should do - using Fcable to get into fastboot mode AND using it for the data communication as well (ie DONT unplug the Fcable!).
Last (and still open) issue
Why my devices don't use the normal factory cable process (plug into Kindle and then PC) - but only works by plugging PC end 1st and then Kindle.
but I am not sure this matters anymore.
jma9454 thanks for chiming in!
I just did "adb reboot recovery" and my FTV1 turned off and never came back on. Unplugged everything, plugged back in, nothing. Then I went to the bedroom where there's another FTV, and its dead also. How did I do this and is there a fix?
edit: by dead I mean it wont even power on. Neither FTV can get to the first white amazon logo. No video output, no light on the front.
Try plugging into your computer and monitor the status of the USB device drivers being loaded. If the computer seems to be recognizing it, try 'adb devices' or 'fastboot devices ' to further check the status of the device. A simple 'adb reboot' or 'fastboot reboot' may get it booting again.
mrlaugh01 said:
Try plugging into your computer and monitor the status of the USB device drivers being loaded. If the computer seems to be recognizing it, try 'adb devices' or 'fastboot devices ' to further check the status of the device. A simple 'adb reboot' or 'fastboot reboot' may get it booting again.
Click to expand...
Click to collapse
Do you mean connect the FTV to my pc? with USB? Not sure I have a cable like that (fat usb on each end). The FTV is not the slightest bit warm when the power cable is plugged in so I doubt I can adb to it.
It can't hurt to try the USB a to USB a cable thing. If your stuck what do you have to lose? Were you rooted/ unlocked / and on a pre-rooted rom?
Michajin said:
It can't hurt to try the USB a to USB a cable thing. If your stuck what do you have to lose? Were you rooted/ unlocked / and on a pre-rooted rom?
Click to expand...
Click to collapse
I'll have to get one of those cables. Does quality matter? Found it direct from China for under $1: http://www.ebay.com/itm/30CM-High-S...ata-Transfer-Charger-Cable-Cord-/282210741043
I was on rbox's latest pre-rooted rom. I updated the FTV1's on different days yet they both died at about the same time. Right after I gave one of them the adb command "reboot recovery."
I misread your post and was under the assumption you were using a Fire Stick. But USB ADB should be possible. Here's a quick search result: https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-to-fire-tv-device
mrlaugh01 said:
I misread your post and was under the assumption you were using a Fire Stick. But USB ADB should be possible. Here's a quick search result: https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-to-fire-tv-device
Click to expand...
Click to collapse
sorry for delayed response, was out of town and didnt want to think about my two FTV paperweights.
I looked at that link and it says this:
"If you plan to connect your computer to your Fire TV device using a USB cable, turn on USB Debugging."
I never did USB debugging so I never turned that on and even if I did I'm fairly certain the FTV is not turning on since its not even slightly warm. Do you think I should order the USB A to A cable anyway and try?
I cant believe I'm the only one that has had this happen...
Yes I believe it'll work still... The Fire devices have a system 'adb mode' when it first boots up. Booting up TWRP on a Fire Stick is a similar process you can probably follow. But if you're not getting my power, or it's not not powering up, you may have bricked it.