Develop Bugs

Computer not "finding" device

Hi,
Before I start: I have "scoured the earth" for this, and I can't seem to find this exact problem in any other sites/threads.
I have an HTC Desire Z. I've switched a couple of times between CM7 and MIUI.
Any time I plug my device into a computer, the phone will charge, but the computer will not recognise that the device is plugged in.
The SD card works fine, because I can use it with an external reader.
The cable/drivers work fine, because I can plug in a Nexus S with the same cable.
Been tested on Windows 7, Fedora 15, Xubuntu 11.04.
Code:
~$ lsusb
Bus 005 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 13d3:5702 IMC Networks
Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Would anybody be able to suggest a way I can go about rectifying this? (already: removed/cleaned sd card, rebooted computer(s), rebooted phone, changed cable)

What's your computer's OS?

As above, tested with fedora, windows 7, and xubuntu.
Sent from my HTC Vision using XDA App

denbeigh2000 said:
As above, tested with fedora, windows 7, and xubuntu.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Okay, that's what I get for not reading the whole OP. Did you try on regular old Ubuntu?

blackknightavalon said:
Okay, that's what I get for not reading the whole OP. Did you try on regular old Ubuntu?
Click to expand...
Click to collapse
I did when I had ubuntu installed. Still no dice

As an interesting side note, I think the last time this worked properly was when I was using the MoDaCo Custom ROM with Sense (Maybe this is a kernel issue/hardware driver issue?)
(Note, currently on CM7 nightly build (06252011), this feature did not work on MIUI or CM7.0.2 stable)

Did you check to see if USB debugging was enabled? Sometimes it's stupid things like that that do it.

blackknightavalon said:
Did you check to see if USB debugging was enabled? Sometimes it's stupid things like that that do it.
Click to expand...
Click to collapse
Yeah, it's been enabled the entire time
Sent from my HTC Vision using XDA App

Usually, it's one of the rules in etc/udev/rules.d, but in your case, lsusb doesn't even recognize your device. It should have a vendor ID of 0bb4, but isn't there.
Have you tried plugging your phone in someone else's computer? I suspect it is a hardware issue with your phone.

gee one said:
Usually, it's one of the rules in etc/udev/rules.d, but in your case, lsusb doesn't even recognize your device. It should have a vendor ID of 0bb4, but isn't there.
Have you tried plugging your phone in someone else's computer? I suspect it is a hardware issue with your phone.
Click to expand...
Click to collapse
Yes, I have. However, it worked under a MoDaCo custom ROM. So I'm feeling it might be an issue with the kernel... Is anybody else running CM7 or MIUI?
EDIT: (I'm operating under the impression that kernel configures the hardware for the software)

anybody had this before? :\

Ok: i've just flashed my DZ with sense 3.0 (virtuous fusion ROM), and the tethering and mounting work perfectly. So, there must be an issue with the software. Is anybody else on this forum running a DZ without sense? If so, do you get this bug?
Sent from my HTC Vision using XDA App

Fixed with a fix permissions from recovery. Thanks all round! (marking thread as solved)

[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]stuck on kindle fire logo - tried KFU&Soupkit

Kindle stuck on kindle fire logo, try using kindle fire utlity with windows xp and 7(64bit):
xp> 'unkonown device' ("install failedand (unsigned)", In system properties I changed the default driver signing option but nothing)
KFU adb status offline and boot status unknown SOUPKIT nothing
w7> driver ok but unknown usb device when plugin. nothing with KFU or linux+soupkit
tried all with normal usb cable. then opened the back and tried with "short the point". nothing. retry today with a factory cable...nothing!
used also firekit in linux...nothing at all.
I don't know anything about this kindle, because I got it from a friend that got it somewhere!!

In Linux, what is the output of 'lsusb' with the device plugged in?
"That's a special kind of stupid. The kind that makes me laugh."

[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 001 Device 002: ID 079b:004a Sagem XG-760A 802.11bg
Bus 001 Device 005: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
Bus 001 Device 006: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 003 Device 002: ID 0461:0010 Primax Electronics, Ltd
Bus 003 Device 003: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse
ADD> could be a problem of the kindles usb? cable ok, tried 2 different

When you tried the short trick, did you use it with Firekit? How exactly did you implement it? Did you make sure the device was completely powered down before trying it?
"That's a special kind of stupid. The kind that makes me laugh."

used firekit and soupkit...tried different ways. kindle completely powered down, short trick, reconnected usb. <waiting for divice> ...so repowered down, ecc ecc...nothing. tried also with factory cable, same results

trinitylau said:
used firekit and soupkit...tried different ways. kindle completely powered down, short trick, reconnected usb. <waiting for divice> ...so repowered down, ecc ecc...nothing. tried also with factory cable, same results
Click to expand...
Click to collapse
Are you using a 32 or 64 bit linux install?
"That's a special kind of stupid. The kind that makes me laugh."

ubuntu-12.04.1-desktop-i386.iso

so...there is something that I can try to do? some advice, some procedure to follow?

In windows, does device manager recognize it?

trinitylau said:
so...there is something that I can try to do? some advice, some procedure to follow?
Click to expand...
Click to collapse
[Edit:] Confused this with another thread

awidawad said:
In windows, does device manager recognize it?
Click to expand...
Click to collapse
xp> 'unkonown device' ("install failedand (unsigned)", In system properties I changed the default driver signing option but nothing)
w7> driver ok but unknown usb device when plugin.

soupmagnet said:
All I can really say is that Firekit works for what it does. What it can't do is make up human error. And I have no way to see exactly what your are doing so I have no idea if your problem is related to your procedure/technique/whatever, or if there is something more going on. The best advice I can giver you is to keep trying...be persistent and don't give up.
Click to expand...
Click to collapse
I followed all the instructions ... keep trying!!
always better to try with linux?

trinitylau said:
I followed all the instructions ... keep trying!!
always better to try with linux?
Click to expand...
Click to collapse
SoupKit will only work with Linux...
Yes, use Linux.
"That's a special kind of stupid. The kind that makes me laugh."

I'll post a custom driver in a bit try it on windows 7 when I post link
---------- Post added at 01:32 PM ---------- Previous post was at 12:55 PM ----------
HERE is the custom driver. Replace the driver in the KFU driver folder with this one, then re-run the driver installation (run.bat) and rename it to "android_winusb.inf" without the quotes

soupmagnet said:
SoupKit will only work with Linux...
Click to expand...
Click to collapse
yes, sorry, I meant to continue with linux

trinitylau said:
yes, sorry, I meant to continue with linux
Click to expand...
Click to collapse
Try the windows 7 drivers... It might work

awidawad said:
I'll post a custom driver in a bit try it on windows 7 when I post link
Click to expand...
Click to collapse
ok, thanks! try also this way!

nothing...driver install without problems but still "unknown usb"

trinitylau said:
nothing...driver install without problems but still "unknown usb"
Click to expand...
Click to collapse
Very strange... What firmware was your device running?

I don't know, I got it from a friend, stuck at kindle fire logo

[Q] Kindle Fire stuck at boot animation after LCD Density change

Hi everyone,this is my first post on the XDA forum.Recently,i had installed the Stock Jelly Bean 4.2.1_r1 for the Kindle Fire made by Hashcode.Things have been working well,untill today.I found an app call LCD density modder(2.4.2) and i installed it.After i apply my density change(160 to 200),the system reboot.However,it only passed the Kindle Fire Red logo and then stuck at the Jelly Bean 4.2.1 animation boot.
I have tried to connect the Kindle Fire to my pc and tried to use the Kindle Fire Utility but my ADB is set at offline.I have tried everything,uninstall driver to normal boot-turn off device trick,but none of them has work.I'm a newbie,so this is really confusing for me right now.If anyone know how to fix this,please help me !!!
P.S:Sorry for my bad English.It isn't my native language !!!
UPDATE:
So I've try using Ubuntu 12.10, install Soupkit, It didn't work: ADB status is Offline.
Switch to Ubuntu 12.04. and tried to test something, and I think maybe there is sth wrong.
First I hit this, with my KF plug in
[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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Bus 002 Device 007: ID 1949:0005 Lab126
Click to expand...
Click to collapse
Then I remove my KF and did it again, this time it showed this
[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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Click to expand...
Click to collapse
So my guess it my PC still recognised it as Lab126.
Then I did another test, I type in
sudo gedit /etc/udev/rules.s/51-android.rules
Click to expand...
Click to collapse
And this showed up:
# 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"
Click to expand...
Click to collapse
So I think that my system need some adjust. Can anyone help me please?
Update: I saw that on when I got lsusb it supposed to say Bus 003 Device 026: ID 1949:0006 Lab126 or something. but I got 0005.
Maybe this is the problem, I don't really know. Can anyone take a look and see what happend to my KF Id.

if you boot to your recovery (twrp) you should have adb available.
then you can set the density back in the build.prop in the system folder.
take care of the permissions !

But i can't boot into TWRP.
My kindle doesn't show up the yellow triangle.It just show up the regular kindle fire logo

gave you a pm ...

I'm trying on Soupkit but it said that "Device Offine", and I really don't know what to do next, first time on Ubuntu and have tried some solutions but they just don't work. Anyone can help?

with ubuntu no drivers are needed - try a other cable first - then maybe contact soupmagnet for further help

Two things...
1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
2) I've seen the PID of 0005 in only one other situation before and it resulted in having to replace the bootloader. But your device has moved past the bootloader and on to the boot animation so your situation may be different...or not. You could try to change your udev rules to match the PID indicated by the device and then reload the udev rules:
Code:
sudo udevadm control --reload-rules
...if that doesn't work, you'll need a factory cable to get the device into fastboot so you can access recovery. Even then, you may be looking at usbboot to fix the bootloader.
"That's a special kind of stupid. The kind that makes me laugh"

1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
Click to expand...
Click to collapse
The PM was wrong, the code when I used was wrong, I type in
Code:
sudo gedit /etc/[B]e[/B]dev/rules.d/51-android.rules
So It was obviously wrong ( but I copy the code from your thread )
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.

Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look

raulmadrid1998 said:
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.
Click to expand...
Click to collapse
What an interesting coincidence...the one other situation where I've seen a PID of 0005 was from a guy in Vietnam. I wonder if there is a connection somehow.
raulmadrid1998 said:
Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look
Click to expand...
Click to collapse
Everything that guy is talking about, is done automatically in SoupKit when you install it.
Get your factory cable then we can work from there.

Please help
b63 said:
gave you a pm ...
Click to expand...
Click to collapse
My kindles TWRP is gone after i tried installing the kindle os so i can remove jelly bean. Now my kindle wont boot, and wont show up in KFU so i can fix it. When i turn it on it show KINDLE FIRES original logo bright then black outs in like 5 seconds and show it again with a dimmer light. Do you have any idea how i can fix this because ive been searching for 4 weeks now and cant find one thing. thank you.

4 weeks really? Okay well a couple things did you do a full wipe when you flashed stock? My guess is no. What was the charge level of your battery when you flashed update.zip? If you didn't do a full wipe your kindle is stuck trying to handle the data left behind. This requires a factory cable to fix. If your battery was near depleted when you flashed it the problem could be compounded by a 5 second boot loop. My guess is the prior improperly flashing of stock without a full wipe buying a cable and leaving it on charger is your best bet for a fix. Cables can be puchased here http://forum.xda-developers.com/showthread.php?t=1392693 post 9 and worth every penny. Good luck

[SOLVED] help resetting back to stock (flo) (Q)

hi, I just installed the beta build of the AOSP Oreo Rom and soon after finding working-ish gapps twrp was gone, and I hadn't had a chance to root yet, and so i went to my computer to manually flash recovery but my device refuses to get recongized, i have installed latest google and universal drivers, but they dont show up for me to set them to my nexus. Im running Latest win10 on my desktop, using a known good usb cable and have switched between the only usb 2.0 ports i have (2) i've tried in normal boot state and in fastboot, but the drivers wont match up to proceed. does anyone know anything about this, is this an issue with win10 or is it something else?

Do assuming that no one has encountered this before I guess I'll just wait until a app that can root comes out for Oreo and hopefully that can get me fixed up but if in the meantime someone comes across this and actually has some insight any help would be very much appreciated.

deathblade said:
someone comes across this and actually has some insight any help would be very much appreciated.
Click to expand...
Click to collapse
Since fastboot does not work then do the following:
win10 may be broken, check for flo ID = 18D1:4EE0 using alternative OS - if it still does not work then...
repair broken N7 USB port or re-seat the wide silver cable to fix USB data lines
:good:

Thank for your suggestion, I'm downloading the iso right now, will post back after following instructions, hope this works

ok, just followed your instructions, and this is what i got
[email protected] ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 13fe:5500 Kingston Technology Company Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $
I dont see the ID you are referring to

Also I reseated the cables with no change and visually inspected the port and solder joints and all seem ok, here are a few pics ( I apologise about any quality issues, I'm not a photographer) EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive, is there anyway to use an otg flash drive to force auto install a custom recovery?

deathblade said:
EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive
Click to expand...
Click to collapse
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.

Had a comparable issue recently due to win10 preferring some default driver over Google driver for fastboot.

k23m said:
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.
Click to expand...
Click to collapse
Ok just tried with usb 2 and 3.0 ports same result, but oddly the listing does differ from my previous, it is now show an Intel device (I assume my CPU or a chipset) that wasn't listed before. But still no Nexus. Will try with a different cables later today as I have to hunt one down (just moved)

ok, so i just found another cable (with builtin otg usb port ) and even in windows 10 it worked just fine, thank you so much for your help. the cable i was using before was an anker gold tipped nylon braided 10ft usb cable, my guess is that at 10ft it has too much resistance to actually work properly for such data based tasks. I will at some point get another (smaller) anker cable to test this theory