Develop Bugs

[Q] ADB Won't see my KF

So I have read the all about KF guide, I read the how to set up adb guide, and I used the KF utility to install my drivers for adb, I checked device manager to make sure I have the correct drivers installed but when I execute "adb devices" there is nothing.. So, I installed ubuntu on a machine, spent hours setting it up for adb, got it all up and running and same thing, adb devices = nothing. So my KF is on 6.3.1 stock software, my goal here is to root, and I'm wondering if it is the new software that is screwing me up?? I already asked if the 6.3 root process will work which someone said it should work just fine.. But I don't know what I'm doing wrong... Any suggestions? I have a friend that is a electrical engineer major who is making me a factory cable... So maybe that is my answer? Thanks

Are you getting an error with adb or are you getting no devices?

I've had usb port problems on my desktop where it wouldn't recognize and ADB device, but switching to a new port worked. Specifically a usb port on a hub, but I imagine this was a very unique case to me, but trying different usb ports is always a good debug step.
Also, usb cables sometimes are bad as well. I have a micro usb cable that only charges, doesn't do any data. I would recommend a new cable as well.
Thirdly, try a different computer if possible. Basically you're trying to isolate the problem is in fact your computer and not your Kindle.

soupmagnet said:
Are you getting an error with adb or are you getting no devices?
Click to expand...
Click to collapse
ADB starts the server, and then says
List of devices attatched
thats it.. So looks like adb is working properly.. Just no devices listed.

superxpro12 said:
I've had usb port problems on my desktop where it wouldn't recognize and ADB device, but switching to a new port worked. Specifically a usb port on a hub, but I imagine this was a very unique case to me, but trying different usb ports is always a good debug step.
Also, usb cables sometimes are bad as well. I have a micro usb cable that only charges, doesn't do any data. I would recommend a new cable as well.
Thirdly, try a different computer if possible. Basically you're trying to isolate the problem is in fact your computer and not your Kindle.
Click to expand...
Click to collapse
I've tried 2 different cables, that will transfer files and charge, and 3 different computers now... My work computer, my home desktop, and my new linux build.. So I don't think its a issue with a cable or a port..

In Windows it's most likely a driver problem. With Linux, you have to make sure you set up your udev rules.

westlandnick said:
So I have read the all about KF guide, I read the how to set up adb guide, and I used the KF utility to install my drivers for adb, I checked device manager to make sure I have the correct drivers installed but when I execute "adb devices" there is nothing.. So, I installed ubuntu on a machine, spent hours setting it up for adb, got it all up and running and same thing, adb devices = nothing. So my KF is on 6.3.1 stock software, my goal here is to root, and I'm wondering if it is the new software that is screwing me up?? I already asked if the 6.3 root process will work which someone said it should work just fine.. But I don't know what I'm doing wrong... Any suggestions? I have a friend that is a electrical engineer major who is making me a factory cable... So maybe that is my answer? Thanks
Click to expand...
Click to collapse
I had the same problem in my Mac environment first time I tried to connect adb. It would not connect until I edited the adb_usb.ini file under my .android directory. If the file doesn't exist, create it and add 0x1949 on a line by itself. If that doesn't work you probably have a driver issue as stated previously.
UK

ukchucktown said:
I had the same problem in my Mac environment first time I tried to connect adb. It would not connect until I edited the adb_usb.ini file under my .android directory. If the file doesn't exist, create it and add 0x1949 on a line by itself. If that doesn't work you probably have a driver issue as stated previously.
UK
Click to expand...
Click to collapse
I think you are right with the driver issue.. Just for fun at home I plugged my HTC Supersonic in and adb didn't see it either, but at work I have set up drivers for my HTC and adb can see it here... And my work computer has that file. I'll try to add that file to my computer at home when I get there and see if it fixes it. Thanks for that, I figured it had to be something simple/stupid.

soupmagnet said:
In Windows it's most likely a driver problem. With Linux, you have to make sure you set up your udev rules.
Click to expand...
Click to collapse
I don't think I set up any udev rules on my linux.. I will check that out as well.

I have a similar problem, and followed probably every adb guide in the forums, along with several other... I bricked my gf's KF accidentally when I was distracted by her son, and missed a step or 2 for the "Kindle Fire Utility", but I THINK the problem started even before that attempting to use the "SuperOneClick" tool to root it... I did everything correctly with the tool BUT from what I've read it is no longer working correctly... The KF is stuck at the boot logo, but I can still turn it on and off... I've added/edited the "adb_usb.ini" file, added myself to the udev group, etc. but the device is still not listed under the "adb devices" command, there is no error, no question marks, no nothing... I've seen it listed as "Google Inc" on some guides under the "lsusb" command, and one with "Lab126" which is what mine is listed as... Also killed/restarted the servers, restarted my computer, shut down my computer, tried different cables (all of which have transfering capabilities), etc. so I am completely lost... Not to mention that the LiveUSB was giving me trouble so instead I erased the Windows 7 partition to fully install Ubuntu 12.04... I've been trying to figure this out for about 3 days to no avail... Any advice???
Thanks in Advance!!!
CJ
(Edit: Just tried the "lsusb" command, and it doesn't even show up like that anymore)

yeah run andadb on your machine do steps 1-4 in terminal http://forum.xda-developers.com/showthread.php?t=1670405 just right click on andadb go to properties permissions allow it to be executed and run it after all 4 steps are done and you have followed the threads instructions use sudo for your fastbboot commands

@Thepooch alright, that took me a BIG step in the right direction, thanks!!! The "lsusb" command now shows that it's connected as "Lab126" again, BUT "adb devices" still comes back with nothing... I'm sooo close, but still so far from getting this thing right...
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse
Bus 002 Device 002: ID 0408:03f5 Quanta Computer, Inc.
Bus 003 Device 002: ID 0bda:0186 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 1949:0006 Lab126
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached

Yeah I'm not seeing the Google driver in the list did you run the sdk and select the top two and Deselect the rest if so that's fine. Power your kindle off type sudo fastboot getvar product plug your kindle in it should power on and terminal output should be product: kindle then type sudo fastboot reboot your kindle will then reboot.

Honestly, I don't know... There was another guide (not sure exactly which one) where I had to install Eclipse and run the sdk and install drivers/platforms from there and I'm not sure exactly which ones it had me install... I tried to do it from the guide that you posted as well but for some reason the part where the sdk was supposed to open etc. didn't work as it was supposed to... The rest worked fine though... I'll have to re-check it, but hopefully that piece of information is what I've been searching for, but at the same time if it is, I'm going to feel even more "special" lol...
Edit: Not sure if the SDK is the same when using Eclipse or not, but the "Android SDK Tools" and "Android SDK Platform Tools" are my first 2 and they were already installed... Did everything you said from there,and I've been "< waiting for device >" for a good 5 minutes now... Is it always this complicated or did I just really screw things up???

Lab126 is your device booted normally or in recovery. As Lab126 you can only issue adb commands. lsusb > Bus 001 Device 005: ID 1949:0100 Lab126
Google inc. is your device in fastboot mode. As Google inc. you can only issue fastboot commands. lsusb > Bus 001 Device 005: ID 18d1:0100 Google Inc.
What seems to be the problem is, what you think to be fastboot is kind of misleading. The stock Kindle ROM has the Kindle Fire logo for its boot animation as well as the bootloader. So, if you're stuck in a boot animation bootloop it could very well seem like you're stuck in fastboot. But that's just a guess.
Enter "adb devices" and see if you're connected.
[Edit:]Also, double check your adb_usb.ini to make sure it's configured properly.

Not sure exactly who you're suggestions are meant to be towards but it fits right along with my problem, and it's put in a much more informative way than I could've put it ... How would I/is it possible for me to get into fastboot while it's still recognized as "Lab126"??? All of my files including "adb_usb.ini" are configured to the best of my knowledge...

When you open adb_usb.ini does it have 0x1949 on its own line and nothing else on that line?
And when you enter "sudo gedit /etc/udev/rules.d/51-android.rules", do you see this...
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"

Yup, the only difference is on the 51 rules file, I switched "OWNER="root"" to "OWNER="CJ""...

sdfyhpromotions said:
Yup, the only difference is on the 51 rules file, I switched "OWNER="root"" to "OWNER="CJ""...
Click to expand...
Click to collapse
and you can't get adb to connect?

Not in the 9,837 times I've tried it ... Oh, and it was originally "root" until I read somewhere that it's supposed to be you're account username but I'll try to change it back and see if it makes a difference...

[Q]Another Bricked Kindle Thread: No Pwer, wont turn on

Hello
Im now the proud owner of a bricked first gen kindle fire. I decided to go ahead and successfully installed this ROM on my device. After messing around with the apps the screen froze, i decided to do a hard reset and now my device wont turn on and im not seeing any lights when its plugged in. After some investigation ive come to the conclusion that the device has a bootloader error of some kind. Ive tried using fire kit and the shorting trick to get around this issue but its seems that im out of my depth. Im messed around with "soupkit" and have gotten the drivers installed on my linux distro (ubuntu) howver when i run "adb devices" im not seeing my device. I occassionally see the device pop up in my listing when i run "lsusb" however.
any help would be greatly appreciated.

what you linked as a rom is not a rom unless you flashed update.zip but everything would surely go wrong if you flashed the kindle fire utility??? Power on issues are usually from a completely dead battery. It could fail to turn on depending on what you did flash if it was way off the chart incorrect. So I`m confused about your post you must clarify. You will certaily need firekit to repair if it fails to power on with a full battery pm me I will try to assist you in fixing your completely brain dead device.

0beah said:
Hello
Im now the proud owner of a bricked first gen kindle fire. I decided to go ahead and successfully installed this ROM on my device. After messing around with the apps the screen froze, i decided to do a hard reset and now my device wont turn on and im not seeing any lights when its plugged in. After some investigation ive come to the conclusion that the device has a bootloader error of some kind. Ive tried using firekit and the shorting trick to get around this issue but its seems that im out of my depth. Im messed around with "soupkit" and have gotten the drivers installed on my linux distro (ubuntu) howver when i run "adb devices" im not seeing my device. I occassionally see the device pop up in my listing when i run "lsusb" however.
any help would be greatly appreciated.
Click to expand...
Click to collapse
The "shorting trick" will work...but rarely on the first shot. Keep trying and don't give up.
A few things to note before trying the shorting trick:
* Be sure you aren't using a USB 3.0 port
* Make sure the power is completely off. Even if there are no outward signs of life, the device can still be on and the Firekit will fail. Hold the power button for 15 seconds or so to make sure there is no power to the device before plugging in and attempting the shorting trick.
* Be sure you fully understand the instructions in the Firekit/Rekindle threads. There is important information there that can easily be overlooked if you aren't attentive.
Unfortunately, the USBboot method is one of the few things you're completely on your own with. No one here can help you with it. That being said, it's one of those things you just need to be persistent with it. Everyone I've seen use the Firekit, has succeeded, eventually.

shorting trick again.
So I've done the shorting trick again. Connected the 3rd dot on the board to the metal case around it. Fire kit sees something obviously and my usb port pick up this:
Bus 001 Device 016: ID 0451:d00f Texas Instruments, Inc.​
Still no light still no power and fire kit moves from:
waiting for OMAP44xx device...​
to:
< waiting for device >​
and just hangs there. I've been informed that for custom roms it will take a while, but how long is that exactly? i've left it there fro roughly about half an hour.
advice?

0beah said:
So I've done the shorting trick again. Connected the 3rd dot on the board to the metal case around it. Fire kit sees something obviously and my usb port pick up this:
Bus 001 Device 016: ID 0451:d00f Texas Instruments, Inc.​
Still no light still no power and fire kit moves from:
waiting for OMAP44xx device...​
to:
< waiting for device >​
and just hangs there. I've been informed that for custom roms it will take a while, but how long is that exactly? i've left it there fro roughly about half an hour.
advice?
Click to expand...
Click to collapse
BTW the rom i used was gotten from here

Yeah leaving it <waiting for device> really does nothing If you dont get any action within 3 or 4 mins start the procedure again. You must keep the short until it runs through as well 30 mins is overkill. Make sure you are contacting the correct test point here it is shown circled in red http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 .

Thepooch said:
Yeah leaving it <waiting for device> really does nothing If you dont get any action within 3 or 4 mins start the procedure again. You must keep the short until it runs through as well 30 mins is overkill. Make sure you are contacting the correct test point here it is shown circled in red http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 .
Click to expand...
Click to collapse
Yeah thats exactly what i did. Unfortunately im busy with work now but im gonna leave it plugged in and the fire kit running for the rest of the day and see if there's any change.

You can leave it plugged in for 10 years and firekit running and if your not shorting it there never will be a change.

same hinesAn
So I'm definitely not sure if I'm shorting this properly. I have set up a pin to touch the point and the frame to leave my hands free. Running some diagnostics. Not sure if its relevant but I'm in the 11.10 environ of ubuntu btw. I'm noticing the device keeps getting disconnected by the system with the following message:
device: 38 was not an MTP device
USB disconnect, device number 38
checking on some libmtp things maybe the issue is that my linux install just doesn't recognize the device?

Use the intel 86 desktop CD image http://releases.ubuntu.com/precise/

Okay so ive made a live cd off of the link provided (cant make a bootable usb at the moment). Same issue as before except now i get the following according to th logs:
[ 3824.857537] usb 1-1.2: new high-speed USB device number 24 using ehci_hcd
[ 3824.950355] usb 1-1.2: unable to get BOS descriptor
[ 3825.427367] usb 1-1.2: USB disconnect, device number 24​

A live CD will not work because of persistent only a live USB has this capability sorry. You could try my iso its possible that it may work as a live CD http://forum.xda-developers.com/showthread.php?t=1413358 post 7 but I have never tested use the per instructions to created the CD. Sorry for the large download but its totally prefab create boot and use nothing else needed. The way you're doing it when you reboot no Soupkit changes will be saved to the CD.

Thepooch said:
A live CD will not work because of persistent only a live USB has this capability sorry. You could try my iso its possible that it may work as a live CD http://forum.xda-developers.com/showthread.php?t=1413358 post 7 but I have never tested use the per instructions to created the CD. Sorry for the large download but its totally prefab create boot and use nothing else needed.
Click to expand...
Click to collapse
Im sorry im not following exactly why i NEED persistent? is it only the adb drivers? cause ive gotten those dld via PPA. Just would like to now out of curiosity really. Regardless i'll grab a 4gb USB ASAP.

The persistent or Casper r/w allows for changes to be save between reboots on a live USB that's why it will not work on a CD because no data including udev rules aren't preserved. Soupkit is intended to either be ran on a live USB or a full install. I recommended 12.04 because through the process of testing Soupkit well over 200 times that I found there to be some mild issues that accompanied the use of 11.10. I tested every viable distro that allowed for persistent xubuntu,kubuntu, multiple distros of Ubuntu and Linux mint mate and found that 12.04 Ubuntu and Linux mint mate 32 bit worked the very best with less hassles to the user.

rsomeoe Having
I now have 12.04 tried running the firekit tool while doing the "shorting trick". Still no change as from before. Still getting:
[ 716.828012] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 716.960808] usb 1-2: unable to get BOS descriptor
[ 719.962054] usb 1-2: USB disconnect, device number 8​

0beah said:
I now have 12.04 tried running the firekit tool while doing the "shorting trick". Still no change as from before. Still getting:
[ 716.828012] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 716.960808] usb 1-2: unable to get BOS descriptor
[ 719.962054] usb 1-2: USB disconnect, device number 8​
Click to expand...
Click to collapse
So i now have a pen drive. installed soupkit. ran the firekit install on in and now im now stuck at "waiting for device:". Any assistance?

[Q] Stuck at boot animation while computer recognizes device but ADB and KFU don't

here's what happened:
flashed new ROM (SmoothROM v1.2) in TWRP 2.2.x.
loaded up new ROM where the dock was missing and the background was black. figured something wrong happened on bootup, so I did a hard reboot. (thinking back on it, I think I forgot to install a launcher, which was really, really dumb of me. I've done this a million times and just assumed if I didn't choose one then it would use a default.)
Kindle Fire logo shows up (no animation), quickly flashes off and back on, and then gets stuck at the CM10.1 boot animation.
I can get my computer (Windows 7 64-bit) to recognize the device as an Android Composite ADB Interface in Device Manager only if I install the drivers manually, otherwise it fails. shows up as Amazon Kindle Fire under Devices and Printers.
it isn't recognized in ADB or KFU, which is my biggest concern. (before all this it was recognized just fine.) it's always "Offline" or "error: device not found" or "waiting for device."
I feel like I've literally tried everything at this point. uninstalled and reinstalled EVERYTHING, different ports, different USB cables, different computers, different OSes, pushing commands through ADB...
does anyone have any solutions or suggestions for me at this point? if you want to know what all I've tried I'd be happy enough to type out all I can remember.
cheers,
Rachel

Do you have FireFireFire installed? Are you able to access TWRP using FireFireFire?
Sent from my KFHD 8.9 using Tapatalk 2

soupmagnet said:
Do you have FireFireFire installed? Are you able to access TWRP using FireFireFire?
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
ha, I was thinking you'd be the first one to respond. I don't know how many of your posts I have read trying to figure out a solution to this problem...
I rooted my KF over a year ago, and if my memory serves me correctly, I never installed FFF...

Shame on you.
You need to get into fastboot so you can access TWRP. Even then, you'll need to be able to send fastboot commands. Windows can compound the issues you're dealing with so to save yourself the trouble, you need to get a Linux LiveUSB set up and install SoupKit. That will make sure your your ability to send and and fastboot commands isn't being hindered by the operating system.
Sent from my KFHD 8.9 using Tapatalk 2

soupmagnet said:
Shame on you.
You need to get into fastboot so you can access TWRP. Even then, you'll need to be able to send fastboot commands. Windows can compound the issues you're dealing with so to save yourself the trouble, you need to get a Linux LiveUSB set up and install SoupKit. That will make sure your your ability to send and and fastboot commands isn't being hindered by the operating system.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
shame on me indeed.
alright, I'm going to do what you said and report back if I have any problems.
thanks!

got Linux 12.04 and Soupkit. tried the shorting trick today with different commands to no avail. I tried changing the bootmode to Normal and Recovery, then install_fff_twrp_from_stock and usb_fix_parts_and_install_fff_twrp.
am I on the right track? what can I do now?

rachste said:
got Linux 12.04 and Soupkit. tried the shorting trick today with different commands to no avail. I tried changing the bootmode to Normal and Recovery, then install_fff_twrp_from_stock and usb_fix_parts_and_install_fff_twrp.
am I on the right track? what can I do now?
Click to expand...
Click to collapse
I don't think you need to be doing the shorting trick just yet. Just use SoupKit to try and install a new bootloader.
Sent from my KFHD 8.9 using Tapatalk 2

same problem
soupmagnet said:
I don't think you need to be doing the shorting trick just yet. Just use SoupKit to try and install a new bootloader.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
i am actually facing a somewhat similar issue. i had flashed a jelly bean rom on my KF and then used twrp to flash the stock 6.3.1 however, i dont think i did it right. KF would then reboot every 10 sec. Initially it asked me to force close android.processes.acore and calender storage thing. I was able to get rid of these two msges with a "clear data" on the contact storage and calender storage. But KF still reboots every 5-10 sec.
i also tried using soupkit but in the terminal, it say
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
Device Status: Device Offline (press enter to refresh)
Pl help.
i can use both windows 7 and linux mint14
thanks

soupmagnet said:
I don't think you need to be doing the shorting trick just yet. Just use SoupKit to try and install a new bootloader.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
alright, I tried installing a bootloader with no luck.

navshinder said:
i am actually facing a somewhat similar issue. i had flashed a jelly bean rom on my KF and then used twrp to flash the stock 6.3.1 however, i dont think i did it right. KF would then reboot every 10 sec. Initially it asked me to force close android.processes.acore and calender storage thing. I was able to get rid of these two msges with a "clear data" on the contact storage and calender storage. But KF still reboots every 5-10 sec.
i also tried using soupkit but in the terminal, it say
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
Device Status: Device Offline (press enter to refresh)
Pl help.
i can use both windows 7 and linux mint14
thanks
Click to expand...
Click to collapse
You need a factory cable to get into fastboot because you didn't wipe system AND factory reset before
flashing a ROM.
rachste said:
alright, I tried installing a bootloader with no luck.
Click to expand...
Click to collapse
Make sure you're not using a USB3.0 port and post the output of the command 'lsusb' from the terminal.
Sent from my KFHD 8.9 using Tapatalk 2

soupmagnet said:
Make sure you're not using a USB3.0 port and post the output of the command 'lsusb' from the terminal.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
definitely no USB 3.0. all are 2.0.
here are the results:
[email protected]:~$ lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 045e:076d Microsoft Corp. LifeCam HD-5000
Bus 001 Device 004: ID 056a:0084 Wacom Co., Ltd
Bus 001 Device 005: ID 1532:0016 Razer USA, Ltd
Bus 001 Device 006: ID 046d:c31b Logitech, Inc. Compact Keyboard K300
Bus 001 Device 007: ID 0bc2:0503 Seagate RSS LLC
Bus 002 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
Bus 002 Device 004: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
Bus 002 Device 005: ID 1949:0005 Lab126
Click to expand...
Click to collapse

rachste said:
definitely no USB 3.0. all are 2.0.
here are the results:
Click to expand...
Click to collapse
Well that's good, but you may need a factory cable to get into fastboot. Once you can get into fastboot, SoupKit should take care of the rest.
enter the following and post the results:
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'

soupmagnet said:
Well that's good, but you may need a factory cable to get into fastboot. Once you can get into fastboot, SoupKit should take care of the rest.
enter the following and post the results:
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'
Click to expand...
Click to collapse
I get no results when I enter that.
[email protected]:~$ lsusb -vd 1949:0006 | grep 'bcdDevice'
[email protected]:~$
Click to expand...
Click to collapse

Erp... 1949:0005
Sent from my KFHD 8.9 using Tapatalk 2

soupmagnet said:
Erp... 1949:0005
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
here we go:
bcdDevice 2.16
Click to expand...
Click to collapse

rachste said:
here we go:
Click to expand...
Click to collapse
Yep, you need a factory cable.
Sent from my KFJWI using Tapatalk 2

soupmagnet said:
Yep, you need a factory cable.
Sent from my KFJWI using Tapatalk 2
Click to expand...
Click to collapse
haha, works for me. thanks for your guidance!

[Q] I have a cable but what now?

I got a Kindle Fire and I tried to flash a new ROM. This Rom is called Beanstalk and did not work out as I wished. After installing TWRP and wiping my multiple caches, I flashed on beanstalk on my Kindle Fire. When I turn it on, The Kindle Fire logo pops up, followed by the Beanstalk animation. The device boots up like normal, however when I get in to the actual ROM, the popup says "Unfortuantely setup wizard has stopped" and when I click on the pop-up it just comes back on. I was told to get a factory cable to get it into fastboot mode and from there to recovery. However, when I use the cable on the win7 computer it doesn't stay in fastboot, but when I do on my win8 computer it does but the drivers do not work on it. When it miraculously does work on the win7 computer I try to send commands to it through a cmd prompt and tried using soupkit but it would not detect the device. Is there anyway I can reach debug through the ROM which has the error? How do I detect the kindle during fastboot? IF I can detect it, how do I switch it in to recovery? Thanks for all and any replies!

When you say your device doesn't stay in fastboot on the Win7 computer, can you elaborate on this? How are you determining whether the device is in fastboot or not? Also, where did you get your factory cable? Is it homemade, or did you purchase it? If you did purchase it...where?
The computer itself should have no bearing on whether or not the factory cable will work as intended unless (maybe) you are using a USB3.0 port rather than a USB2.0 port.
Also, if you would, in Linux, enter the following command(s) with the device plugged in and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
If that doesn't give you anything, try the following:
Code:
lsusb | grep 'Lab126'

soupmagnet said:
When you say your device doesn't stay in fastboot on the Win7 computer, can you elaborate on this? How are you determining whether the device is in fastboot or not? Also, where did you get your factory cable? Is it homemade, or did you purchase it? If you did purchase it...where?
The computer itself should have no bearing on whether or not the factory cable will work as intended unless (maybe) you are using a USB3.0 port rather than a USB2.0 port.
Also, if you would, in Linux, enter the following command(s) with the device plugged in and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
If that doesn't give you anything, try the following:
Code:
lsusb | grep 'Lab126'
Click to expand...
Click to collapse
I'm determining if it's in fastboot when it's stuck at the kindle fire logo, When I plug the factory cable in to my win7 cable, it boots up as if I was using a charging cable for some reason, but when I plug it in to my win8 computer it does stay in fastboot. I purchased the factory cable online. I believe the USB3.0 port may be the problem i'll try that a second time. As for the Linux, thing, I'll try that asap. Thank you for the input!

Another bricked Kindle Fire post. No fastboot, no adb, help!

First of all, I've spent many, many hours reading everything and trying everything I could find so sincere apologies if I have missed the solution to my problem.
So I have a Kindle Fire which I got months ago and have never been able to make work. It appears to have been almost completely wiped. It can do two things as of now:
1. Be stuck in a bootloop: displays FireFireFire logo, restarts, rinse, repeat.
2. Get into TWRP
Regardless of which of these states the device is in, neither my Windows PC (which has drivers, SDK, tools etc installed) OR my Ubuntu machine (on which I used SoupKit to install the necessaries) can see the device. It doesn't show in Device Manager in Windows and neither fastboot nor adb show any entries for the device when I run them on EITHER platform and in either of the states I can get the device into.
Any input from people more experienced than me would be appreciated. I got a factory cable in the post today so if that will help I have that option available to go. Oh and finally solutions using my Ubuntu machine rather than the Windows one would be strongly preferred although I can do either if I have to.

Boot into TWRP and see if your device shows up under 'lsusb'
...if it does, then use TWRP to "reboot bootloader" and check 'lsusb' again.

Thanks for the quick reply, and sorry for my slow reply back
The device isn't showing when I run lsusb - I assume you would have mentioned if it was not going to obviously be the KF. Anyway just in case, here is the output:
Bus 001 Device 003: ID 0ac8:c33e Z-Star Microelectronics Corp.
Bus 003 Device 002: ID 04f3:0234 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Anybody got any insight as to what I should do next?

kindlesean said:
Anybody got any insight as to what I should do next?
Click to expand...
Click to collapse
Is it safe to assume you don't have a factory cable?
Also, does the usb cable you're using seated tightly or is it kind of loose?
If it's loose, try this...
Enter the following command in the terminal (Linux) and try to finagle the USB to see if it is a bad connection:
Code:
while true; do lsusb | grep 'Lab126'; done
If you have a bad connection, due to the cable or USB connector, as soon as a good connection is made you will see it output to the terminal. Just remember to ctrl+c to end the loop when you're done with it.

some inforeff
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.

kindlesean said:
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.
Click to expand...
Click to collapse
Before I switched to the black USB cables from Amazon for their quick chargers, my device would do sort of the same thing. I had to pull up or push down on the connection before it would detect. If you have a factory cable made by Skorpn try that one to see if a connection is made. IIRC, Skorpn's factory cables fit very tightly so it might make a difference. Either way, try what I suggested earlier to rule out any hardware based issues with the USB.

I just tried what you suggested with both two different regular USB to Micro USB cables and also with my factory cable. In all cases there was no output in the terminal. I tried it both from TWRP and from the FFF logo screen (which no longer bootloops btw, it seems to just be hanging at the FFF logo now if I don't press power to get into TWRP).
Thanks again

Anyone able to help further? Situation is still the same as in my last post.

kindlesean said:
Anyone able to help further? Situation is still the same as in my last post.
Click to expand...
Click to collapse
You can try to usbboot, but it would require opening your device.

soupmagnet said:
You can try to usbboot, but it would require opening your device.
Click to expand...
Click to collapse
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?

kindlesean said:
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?
Click to expand...
Click to collapse
Check the Firekit thread in the Dev section

soupmagnet said:
Check the Firekit thread in the Dev section
Click to expand...
Click to collapse
Will do, thanks again Soup!