Develop Bugs

[Q] Ubuntu 11.04 amd64, r800x, fastboot waiting for device

OK, I truly believe I have done my due diligence, but I have not been able to find anything solid that can help me get beyond the problem I'm having. The irony is that I first tried this on my WinXP box at work and could not get beyond the < waiting for device > problem, so I gave up and figured I would have no problem if I patiently waited to go home and try this in linux.
So here's everything I've done so far. As noted in the topic, I run the amd64 version of Ubuntu 11.04. I installed the Andoid SDK linux x86 version (there was no option for an amd64 version). I ran the tool/android client to download the platform-tools, so I got adb. With the phone running normally, I can connect it to my laptop and run "./adb devices" and I get back:
Code:
List of devices attached
43423541314354394D58 device
so that's working. When I run lsusb while the phone is running normally, I see
Code:
Bus 001 Device 020: ID 0fce:215b Sony Ericsson Mobile Communications AB
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue. When I run lsusb in this mode, I get:
Code:
Bus 001 Device 022: ID 0fce:0dde Sony Ericsson Mobile Communications AB
As a result, I set the contents of my /etc/udev/rules.d/51-android.rules to:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="215b", MODE="0666", OWNER="procyon"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", OWNER="procyon"
and just to make sure my file permissions are ok (since that seems to bite people in the behind a lot), my rule is
Code:
-rwxr-xr-x 1 root root 197 2011-08-11 01:24 /etc/udev/rules.d/51-android.rules
So, with my udev rules reloaded, I attempt a "sudo ./fastboot boot recoveryPLAY.img" and all I get is the unfortunate
Code:
< waiting for device >
I've done just everything I could thing of, have read several (literally dozens) of tutorials, forums posts, and all manner of Google searches, but nothing seems to help me. Some areas where I think I might be having a problem:
a) Obviously, I'm running the 32 bit version of the sdk instead of the 64 bit version. Could that be an issue here?
b) I've seen lots of posts that disagree on whether the rules file should start with a 50 or a 51. Does that matter?
c) Do I need anything else from the Android SDK other than the platform tools? I don't have that directory in my path, but I'm running everything from inside that directory, and I'm running it with sudo.
I think I've provided all the information that I can. Thanks in advance for any help or any light that anyone can shed.

ProcyonSJJ said:
OK, I truly believe I have done my due diligence, but I have not been able to find anything solid that can help me get beyond the problem I'm having. The irony is that I first tried this on my WinXP box at work and could not get beyond the < waiting for device > problem, so I gave up and figured I would have no problem if I patiently waited to go home and try this in linux.
So here's everything I've done so far. As noted in the topic, I run the amd64 version of Ubuntu 11.04. I installed the Andoid SDK linux x86 version (there was no option for an amd64 version). I ran the tool/android client to download the platform-tools, so I got adb. With the phone running normally, I can connect it to my laptop and run "./adb devices" and I get back:
Code:
List of devices attached
43423541314354394D58 device
so that's working. When I run lsusb while the phone is running normally, I see
Code:
Bus 001 Device 020: ID 0fce:215b Sony Ericsson Mobile Communications AB
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue. When I run lsusb in this mode, I get:
Code:
Bus 001 Device 022: ID 0fce:0dde Sony Ericsson Mobile Communications AB
As a result, I set the contents of my /etc/udev/rules.d/51-android.rules to:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="215b", MODE="0666", OWNER="procyon"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", OWNER="procyon"
and just to make sure my file permissions are ok (since that seems to bite people in the behind a lot), my rule is
Code:
-rwxr-xr-x 1 root root 197 2011-08-11 01:24 /etc/udev/rules.d/51-android.rules
So, with my udev rules reloaded, I attempt a "sudo ./fastboot boot recoveryPLAY.img" and all I get is the unfortunate
Code:
< waiting for device >
I've done just everything I could thing of, have read several (literally dozens) of tutorials, forums posts, and all manner of Google searches, but nothing seems to help me. Some areas where I think I might be having a problem:
a) Obviously, I'm running the 32 bit version of the sdk instead of the 64 bit version. Could that be an issue here?
b) I've seen lots of posts that disagree on whether the rules file should start with a 50 or a 51. Does that matter?
c) Do I need anything else from the Android SDK other than the platform tools? I don't have that directory in my path, but I'm running everything from inside that directory, and I'm running it with sudo.
I think I've provided all the information that I can. Thanks in advance for any help or any light that anyone can shed.
Click to expand...
Click to collapse
I rooted mine last night and I figured it out. Turn your phone completely off first. Unplug everything from the computer. Then hold the "search" button or the magnifying glass while you plug the cable into the phone. There should be a solid blue LED light color at the top of the phone. Then it should work!

There's no 64-bit version of the Android SDK. I think it may have to do with fastboot's binary.

Cubsfan3493 said:
I rooted mine last night and I figured it out. Turn your phone completely off first. Unplug everything from the computer. Then hold the "search" button or the magnifying glass while you plug the cable into the phone. There should be a solid blue LED light color at the top of the phone. Then it should work!
Click to expand...
Click to collapse
Did you not read:
Procyon said:
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue.
Click to expand...
Click to collapse
@Logseman, where is the best place to obtain a good fastboot binary for linux besides the HTC distribution page?

Add -i 0x0fce to the actual fastboot command line too... I had the same problem as you

Thank you so much Blagus, that was exactly what I was missing. I was trying to follow the "Easy Way" method of rooting, as it seemed to be a method in which I would not need to bother ash or mills. Now that you've gotten me over this hurdle, I've come to realize that the "Easy Way" only works if you unlocked the bootloader first, so it appears that I must pm ash or mills anyway? Or is it recommended that I simply wait and be patient until they sort out whatever is needed to provide everyone with a single solution? Thanks again.

I don't get to see this in my R800i. I've put the fastboot binary (from HTC) in platform-tools and this folder in my path. Running "fastboot -i 0x0fce devices" simply returns me the fastboot manual.

[Q] [Help] Help needed w/ rooting

i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks

David 617 said:
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
Click to expand...
Click to collapse
ADB will not find the phone in bootloader mode. If you type fastboot devices, it should show your phone. Check device manager and see if you have an unrecognized device showing. If you do, try manually installing the drivers by clicking the update driver button under the unrecognized device's properties window.

try reinstalling the drivers...or you may need to use the google drivers in the sdk/adb package instead. Also when you plug the device into pc, go into device manager and see if shows up as android device. If it comes up unkown, then manually push the driver update.
^Ninja'd lol

fastboot devices comes up blank.
in device manager my phone comes up as other devices - android 1.0
i guess my driver is bad. where can i get a good one?
(i just installed the one from samsung.. same thing.)
what have you used

Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App

Randroidran said:
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
did that. i dont have any issues untill i am in the bootloader. adb works fine before i reboot.

I'm assuming your driver is not loaded properly. Download this driver and unzip it. Install it by using the update driver wizard in device manager. I used this same driver on my work laptop (windows 7) and have had zero issues.

thx ill try now
.
.
.
works!
thx a million

Kindle Fire "Stuck" in Fastboot

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.

[Help] Stuck at Yellow Fire Triangle

Coming from the title, my Kindle Fire is currently stuck at the FireFireFire stage. It won't even go to the twrp recovery stage.
I have been an avid follower of the Kindle Fire Forum and flashed the latest stable builds posted on the Development thread from the first Gingerbread CM7 by Sblood86 to twa_priv's recent Jellybean CM10. I just made an account today for this troubleshooting issue.
What I did prior to getting it stuck:
- updated to twa_priv's CM10/SGT7 (his latest which is 10/29/2012) via twrp.
- saw that my twrp was outdated on v2.2.0 and decided to update that as well.
- ran Vashypooh's KFU (his latest which is 5/09/2012) by installing latest twrp recovery option.
- saw that the KFU didn't recognize the kindle, so I exited KFU and installed drivers.
- rebooted my kindle to twrp recovery, windows recognizes kindle as "android device ADB" on device manager, and attempted to install twrp recovery update to v2.2.1.1
- waited for like 30 minutes and was stuck on waiting for device on KFU.
- rebooted the kindle myself and tried to install again
- kindle stuck on FireFireFire
- windows reports "USB device malfunctioned"
- cried :crying:
Help please?

Open kfu, plug your device in select 1 for changing bootmodes select 1 for normal if it hangs at waiting for device, hold the power button down while connected, then power it back on it should then boot normal. There have been minor driver changes that could be making your device unseen by windows use soupkit to fix your recovery or fix your boot mode as well. http://forum.xda-developers.com/showthread.php?t=1850038

Thepooch said:
Open kfu, plug your device in select 1 for changing bootmodes select 1 for normal if it hangs at waiting for device, hold the power button down while connected, then power it back on it should then boot normal. There have been minor driver changes that could be making your device unseen by windows use soupkit to fix your recovery or fix your boot mode as well. http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
So I got linux mint 13 running and the soupkit as described in the link, and the soupkit is saying that the kindle is offline even though it is on and plugged in. I tried to change the bootmode to normal but no dice. Still stuck on FireFireFire.
I looked at the system information app and the kindle fire doesn't even show up on the devices tree.

azndnbdub said:
- windows reports "USB device malfunctioned"
Click to expand...
Click to collapse
This line causes me to believe there is something wrong with the bootloader. I'm starting to think this type of error is caused by the way Windows deals with certain hardware.
What motherboard are you using on your Windows machine? I'd like to see if there is a correlation between yours and the configurations of other users with the same problem.
Also, open a terminal in Linux, with your device plugged in, and enter:
Code:
lsusb
You should see a device listed as "18d1:0100 Google Inc". If not, I'm willing to bet my original assessment is true and Firekit is your next step.

soupmagnet said:
This line causes me to believe there is something wrong with the bootloader. I'm starting to think this type of error is caused by the way Windows deals with certain hardware.
What motherboard are you using on your Windows machine? I'd like to see if there is a correlation between yours and the configurations of other users with the same problem.
Also, open a terminal in Linux, with your device plugged in, and enter:
Code:
lsusb
You should see a device listed as "18d1:0100 Google Inc". If not, I'm willing to bet my original assessment is true and Firekit is your next step.
Click to expand...
Click to collapse
I am using a different machine for the live linux but the windows machine is a 2010 - 2011 HP Pavilion dv6 notebook with the Nehalem based Intel Core i3 M 370 @ 2.4GHz running W7 Pro which I believe when referring to the service manual is an Intel HM55 UMA graphics and shared memory with Intel Core i3-370M processors (at least what they refer the mobo to "system board"). The Terminal windows reports that there is a Google device with "18d1:0100 Google Inc" on it.

azndnbdub said:
I am using a different machine for the live linux but the windows machine is a 2010 - 2011 HP Pavilion dv6 notebook with the Nehalem based Intel Core i3 M 370 @ 2.4GHz running W7 Pro which I believe when referring to the service manual is an Intel HM55 UMA graphics and shared memory with Intel Core i3-370M processors (at least what they refer the mobo to "system board"). The Terminal windows reports that there is a Google device with "18d1:0100 Google Inc" on it.
Click to expand...
Click to collapse
The fact that Linux is detecting your device is a good thing. Is your Linux distro 64 or 32bit?
In the terminal enter:
Code:
fastboot devices
...and see if anything shows up.

soupmagnet said:
The fact that Linux is detecting your device is a good thing. Is your Linux distro 64 or 32bit?
In the terminal enter:
Code:
fastboot devices
...and see if anything shows up.
Click to expand...
Click to collapse
Linux distro is Linux Mint 13 Maya 32bit on LiveUSB. Nothing appears when executing "fastboot devices" on Terminal.

Interesting. I wonder if Mint works differently when it comes to the script defining the udev rules.
enter the following commands in the terminal:
Code:
sudo cat /etc/udev/rules.d/51-android.rules
&
Code:
cat $HOME/.android/adb_usb.ini

When executing "sudo cat /etc/udev/rules.d/51-android.rules" the below is the result.
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
When executing "cat $HOME/.android/adb_usb.ini" the below is the result.
0x1949

azndnbdub said:
When executing "sudo cat /etc/udev/rules.d/51-android.rules" the below is the result.
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
When executing "cat $HOME/.android/adb_usb.ini" the below is the result.
0x1949
Click to expand...
Click to collapse
Strange. There's no obvious reason why it wouldn't work properly. Since it is FireFireFire, albeit an earlier version, are you able to access recovery by holding the power button on startup until it turns orange?

soupmagnet said:
Strange. There's no obvious reason why it wouldn't work properly. Since it is FireFireFire, albeit an earlier version, are you able to access recovery by holding the power button on startup until it turns orange?
Click to expand...
Click to collapse
Nope, even as I am typing this response, the kindle fire is plugged in but is frozen on FireFireFire. Can't even get into the TWRP recovery (if it's still there...)

Here's what I see...
Your Linux system seems to be configured properly to detect your device. The udev rules are set and the adb driver is in place and configured properly as well.
Linux is able to detect your device in fastboot so there must be communication with your device at some level.
The fact that the use of the power button to access recovery is failing, is worrisome. As far as I know, if there is no recovery installed, the device should at least boot to a black screen, the same way the device would boot to a black screen if no OS is installed. This leads me to believe that your bootloader isn't working properly.
But before you go as far as attempting a USBboot with Firekit, I would suggest remaking your LiveUSB and using Ubuntu to see if that makes a difference (SoupKit has only been tested on Ubuntu), although I can't see why that would make a difference. Also, be sure you are using USB2.0, not USB3.0. Afterwards, if there is no change, I would suggest USBboot with the Firekit.
Unfortunately, that's the best option I can come up with based on the information I have, and without having direct access to the device.

So I made the LiveUSB into Ubuntu, ran SoupKit, and still the SoupKit still isn't detecting it although executing the aforementioned command lines does show that Ubuntu sees the kindle fire, not the SoupKit. And the kindle is still stuck in FireFireFire even though I ran the Firekit to execute "usb_boot_twrp" I guess there's no hope for it anymore?

azndnbdub said:
So I made the LiveUSB into Ubuntu, ran SoupKit, and still the SoupKit still isn't detecting it although executing the aforementioned command lines does show that Ubuntu sees the kindle fire, not the SoupKit. And the kindle is still stuck in FireFireFire even though I ran the Firekit to execute "usb_boot_twrp" I guess there's no hope for it anymore?
Click to expand...
Click to collapse
Which "aforementioned commands" are you referring to? Does "fastboot devices" return any positive results? Have you tried issuing the command to change the bootmode to recovery?
Code:
fastboot oem idme bootmode 5001
[edit:] This will help me in determining whether the script is failing or the device itself. On that note, if you get stuck at "waiting for device" after entering the previous command, give the device a hard shutdown and start it up again to see if the command sticks.

Success!
You may find this really awkward, but...THE KINDLE HAS RESTORED NORMAL BOOT (4000) !!! :good:
Somehow when I ran my Ubuntu LiveUSB on my HP notebook and not the other machine and ran SoupKit, I issued the normal bootmode (4000). Right then the kindle flickered and I thought "There is hope after all!" After flickering twice, it displayed a regular triangle and immediately went in to the ROM which was the CM10. I then remembered that I was going to install the latest TWRP (v2.2.2.1 which you included in the soupkit), which installed sucessfully. I tested reboot one more time and FFF doesn't hang and TWRP works.
Thank you soupmagnet for being a helpful developer throughout this troubleshooting and also I can vouch that your SoupKit does work as advertised!

azndnbdub said:
You may find this really awkward, but...THE KINDLE HAS RESTORED NORMAL BOOT (4000) !!! :good:
Somehow when I ran my Ubuntu LiveUSB on my HP notebook and not the other machine and ran SoupKit, I issued the normal bootmode (4000). Right then the kindle flickered and I thought "There is hope after all!" After flickering twice, it displayed a regular triangle and immediately went in to the ROM which was the CM10. I then remembered that I was going to install the latest TWRP (v2.2.2.1 which you included in the soupkit), which installed sucessfully. I tested reboot one more time and FFF doesn't hang and TWRP works.
Thank you soupmagnet for being a helpful developer throughout this troubleshooting and also I can vouch that your SoupKit does work as advertised!
Click to expand...
Click to collapse
Developer? Not even close. But I appreciate the sentiment either way. And I'm glad it worked out for you.

[Q] Fastboot Error 2147483647: possible bug??

Hi to all
I'm trying to flash an aosp self-compiled rom but i've got a problem with fastboot. I'm using an ubuntu machine [12.04] and the fastboot version that came with the ADT IDE.
Even if I'm able to use adb and all of its functions, when i try to use fastboot (e.g. fastboot devices) it do not show me any results.
I've tryed different version of fastboot on different ubuntu machine and different usb port with different cables but nothing changed: no output from fastboot.
If I try to disconnect and then reconnect the device in bootloader mode, i get the infamous message at the bottom of the screen saying "Fastboot Command Read Error -2147483647" and nothing more.
However an old version of fastboot coming from a sdk (maybe an API level 15, i do not remember) on my macbook pro with osx is able to connect and send commands.
While i was searching in this forum for some answer, i've found different threads regarding this error: it maybe be a bug instead of a hw/cable problem?
I'm going to flash an official factory image taken from the google sites and then i'll try again, but what do you suggest?
UPDATE:
Even with the factory image, fastboot came out with the same error...

I'm having the same problem on ubuntu. I don't have a Mac to try. Thanks for the info.

peadarog said:
I'm having the same problem on ubuntu. I don't have a Mac to try. Thanks for the info.
Click to expand...
Click to collapse
Code:
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0666", OWNER="<YOUR_USERNAME>"
This worked for me. For some reason fastboot won't work with mode 0600 as adb

Does this work for you? http://forum.xda-developers.com/showpost.php?p=36772681&postcount=11
from: http://forum.xda-developers.com/showthread.php?t=2099241
He had the same error, and i wasn't able to understand if he got it to work.. I'm also wondering why robetto has a different vendor id..

bodh said:
I'm also wondering why robetto has a different vendor id..
Click to expand...
Click to collapse
that udev rule is an extract from the "Configuring USB Access" section of the Google's Getting Started tutorial. The vendor id (and also the product id) change from samsung to google when you are in fastboot mode.

Good to know. Can i also ask about ATTR{idProduct}=="4e30"- is this only for fastboot as well? I don't have linux, but i've considered setting it up..

bodh said:
Can i also ask about ATTR{idProduct}=="4e30"- is this only for fastboot as well?
Click to expand...
Click to collapse
I don't understand the question.
If you are asking about vendor/attr ids mechanism, I think that this wikipedia page it may help you understand how it's work.
Basically every device connected to your pc is identified by a pair <vendor_id:attr_id>, the first one indicating the company and is assigned per company from PCI-SIG, and the second one is choosen by the manufacturer. In this way your OS can recognise and choose the correct driver/operation to do.
If you are asking why this values change... I can't help you, sorry
What I can tell you is when your phone is normally turned on it's shown with a pair of vend/attr that is different from the one when is in bootloader mode, and the udev entry that I've suggested is useful only in this second scenario for fastboot operation.
Check out the Google's Getting Started tutorial for more infos...
hope this help...