Database Users

Why can't I get ADB to work?

I never had a problem with the g1 but am having trouble setting it up for the g2.
When developer mode is on it doesn't install the adb drivers. I used the drivers that were downloaded with the sdk setup. Tried installing them manually through the device manager and it wouldn't accept the drivers.
I'm using windows 7 ultimate x64. I'm not computer illiterate by any means and never had trouble in the past so it's really bugging me.
Thanks in advance!
Sent from my T-Mobile G2 using Tapatalk
EDIT: Crap, meant to put this in G2 Development...

Jorsher said:
When developer mode is on it doesn't install the adb drivers. I used the drivers that were downloaded with the sdk setup. Tried installing them manually through the device manager and it wouldn't accept the drivers.
Click to expand...
Click to collapse
Probably because sdk setup driver's inf file doesn't have entries for G2.
If you have linux desktop, connect your phone and use lsusb to find the VID & PID. You can add those to the inf file and perhaps it will work properly.

jashsu said:
Probably because sdk setup driver's inf file doesn't have entries for G2.
Click to expand...
Click to collapse
That's what I figured and the reason I gave up trying.
Is the driver available somewhere, can the information be added manually (I suppose I can open the inf file when I get home), or do I just have to wait for Google to release an updated driver?

VID and PID
vendor id: 0bb4
product id: 0c91

themadbogart said:
vendor id: 0bb4
product id: 0c91
Click to expand...
Click to collapse
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.

ADB drivers installed no problem for me with my G2. I already had PdaNet installed. Windows 7 32-bit. They do have a 64-bit version listed, too:
http://junefabrics.com/android/download.php

now the big thing is does it recognize the device as online or offline? for some reason and i haven't played with mine yet cuz it is at the house and i'm at work. but in the dev forum they are having that issue... working on root already

Not sure how it worked for you seancneal.
Anyway, thanks, added the entries, installed without issue.
I know you can get to recovery/bootloader through ADB, but is there a way I can without using ADB?

Jorsher said:
Not sure how it worked for you seancneal.
Anyway, thanks, added the entries, installed without issue.
I know you can get to recovery/bootloader through ADB, but is there a way I can without using ADB?
Click to expand...
Click to collapse
Hold volume down while powering on the phone and you will get to bootloader, from there you can select recovery
Sent from my T-Mobile myTouch 3G Slide using XDA App

tubaking182 said:
Hold volume down while powering on the phone and you will get to bootloader, from there you can select recovery
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Nice, thanks.
Yesterday when I was trying to get to it, I tried holding power/voldown, power/volup, power/camera, etc.
Guess I just needed to press the power button instead of holding it.

Any tips for getting this to work in Ubuntu?
lsusb shows the device, and adb devices shows "??????? no permissions"
Edit -- found it in another thread, sorry.
To re-post: Add this line to /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Then run
adb kill-server
sudo service udev restart
adb start-server
adb devices

uplinked said:
Any tips for getting this to work in Ubuntu?
lsusb shows the device, and adb devices shows "??????? no permissions"
Click to expand...
Click to collapse
Ding ding ding! Congratulations on being the 1,000,000 person to ask this question. Please run adb as root to claim your prize.

jashsu said:
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.
Click to expand...
Click to collapse
Thanks! I was having problems getting it going on my comp too

jashsu said:
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.
Click to expand...
Click to collapse
I added these 2 lines of code under both of the sections in the .inf file. It installed fine but when I try adb get-state it says unknown, when I try adb devices it comes up blank. Not sure what I'm doing wrong.

SlicedKuniva said:
I added these 2 lines of code under both of the sections in the .inf file. It installed fine but when I try adb get-state it says unknown, when I try adb devices it comes up blank. Not sure what I'm doing wrong.
Click to expand...
Click to collapse
Do you have USB debugging enabled?

jashsu said:
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.
Click to expand...
Click to collapse
thanks this works. should be stickied.

I've tried this and a few other ways of getting adb but no luck. Any more suggestions are welcomed. Thanks guys.

Download PDA Net on your PC and install it, it will automatically install the drivers for you. You can uninstall PDA Net afterwards if you want and the drivers will stay.
There seems to be a problem with Win7 x64 when installing the drivers using the SDK (which looks solved by the posts above, but if those don't work, try PDA Net).

Thanks. I already tried that, still no luck.
Sent from my T-Mobile G2 using XDA App

USB Debugging got it to work for me, after much toiling.

Stuck installing TWRP w/ Kindle Fire Utility 0.9.1

Here's what I'm seeing...I've restarted the Kindle 4 times now and nothing is happening.
Any ideas?
Here's a link the pic : img18.imageshack.us/img18/6505/image1cb[dot]png

What are you seeing on your Kindle now? Are you in fastboot (Yellow Triangle with fire)?

I don't have FireFireFire installed. Basically I ran the Kindle Fire Utility and did a Permanent Root (after I unrooted using BurritoRoot)...and then ran latest install of TWRP....and everytime it gets to the actually instal part...I see that screen....
and when I restart my kindle (like it says to do in Kindle Fire Utility) it just restarts normally and then goes to USB connected screen.

Steps:
1. Download this .img for twrp.
2. Place it in the adb folder. (where ever you have to cd to)
3. Do the following commands:
adb shell
su
idme bootmode 4002
reboot
4. Download fastboot and place it in the adb folder and do:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5. Enjoy your newly added recovery.

I'm now stuck in fastboot (yellow triangle with fire)
I tried to just press the power butter to load into recover but it didn't work.
I tried adb reboot, but it says no device is found...
Any ideas?
Edit: I saw a post that I need to re-install the drivers?
Which one:
Image: img809.imageshack.us/img809/7474/image3si[dot]png

did you do
idme bootmode 4000
to get it to boot normal?

adb commands arent working....do i need to reinstall the drivers? if so which one...it gives me three choices...
ADB interface
Bootloader Interface
Composite ADB Interface...
I'm assuming once I get adb commands working again...then I can use idme bootmode 4000 to get into regular boot mode again.
Edit: I tried chaning to Normal boot with Kinde Fire Utility...didn't work...
Really wondering if I should reinstall the drivers and try agian...but the KFU doesn't really seem to be playing nice with my device.

Not to say KFU is bad but I never used it. If you started with the directions that came with twrp we might not need so many topic about twrp help.

I just ran into the same problem!
ADB and fastboot commands don't work for me too, and I also tired to reinstall the drivers and still didn't work..
edit: try using KFU on another computer, and then changing to normal boot!
that seemed to work for me!

try to uninstall old/faulty drivers:
disconnect kf and use:
http://support.microsoft.com/kb/315539/en-us
connect KF and select the last installed driver (which you installed by running "install_drivers.bat") manually (check the date/time on selection)

Yeah, the KFU has just been a headache for me.. I finally got it working though, i have to use burrito root everytime I want to do anything after a reboot in KFU, but it works perfectly fine after that. Make sure you have good drivers installed under android phone also! Don't use the install_drivers.bat from KFU, just caused me more headaches...

i used the drivers from kfu - but after a cleanup - that seems to be the point
the difference is they are te only ones with entries for device 18D1 you'll nedd in fastboot mode or you can add the entries to your drivers under "kindle" or "kindle fire" or what it is called in your android_winusb.inf:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01

Well I was assuming they used a root method that already had them set up their own driver files etc. already.

no they don't - they try to provide drivers that are working in every bootmode - i've made corrections in the driver installer script for non english os which vashipooh implemented off ver. .9 - i have also device 18D1 in my adb_usb.ini - if it helps ? - but there's no downside

Maybe I'm just too tired (its 4:30 AM here) But I don't understand what you said... And the current version of KFU has a bad install_drivers.bat, it replaces the mass USB storage driver and it made my ADB stop working...

i think it don't replace the mass storage driver, it just reinstalls it - that's not they'r fault - it's the tool they are using from microsoft (devcon) to update existing drivers - devcon seems to be working this way - good or not ? - who know's ?

Wait, are you talking about the most current 9.1 or 9.0? Because 9.0 works fine, the new 9.1 kills USB storage, and for me ADB which kind of destroys the point.

9.0 - will download 9.1 and take a look - perhaps i can help to sort the problems out and contact vashi to correct the issue - thanks for the hint !!!

No problem, haha I knew there was something missing in that conversation, hope you guys can figure it out!

tec2030 said:
adb commands arent working....do i need to reinstall the drivers? if so which one...it gives me three choices...
ADB interface
Bootloader Interface
Composite ADB Interface...
I'm assuming once I get adb commands working again...then I can use idme bootmode 4000 to get into regular boot mode again.
Edit: I tried chaning to Normal boot with Kinde Fire Utility...didn't work...
Really wondering if I should reinstall the drivers and try agian...but the KFU doesn't really seem to be playing nice with my device.
Click to expand...
Click to collapse
Here is how to manually install the drivers step by step.. If you think you may have a problem with the drivers that you have on your computer it would be smart to get download another .android folder and put it on the root of your c:drive just to be sure that nothing is wrong with it before you attempt this
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
Hope that helps..!

Help kindle fire not recognized

Adb isn't. Finding my kindle fire 6.2.2 NEED HELP IM TRYING TO ROOT IT

Did you set up the device drivers as outlined in this?

http://forum.xda-developers.com/showpost.php?p=22145030&postcount=6

Adb still says its offline

When you go into device manager, what does it display it as?

It says Android Composite Adb Interface

Th3-Chronikk said:
It says Android Composite Adb Interface
Click to expand...
Click to collapse
This is what I recommend: if you installed Android SDK, go ahead and uninstall it. It's only an absolute necessity if you're a developer or running it a virtual environment. Clean all traces of any part of Android drivers or leftovers files and folders. Next, uninstall the drivers from Device Manager under Computer or My Computer. Reboot your PC or laptop.
Next, download vashypoo's Kindle Fire Utility, available in the Kindle Fire's Android Development forum, and extract it. Inside of the extracted folder should be a .bat file to install drivers. Right click, select Run As Administrator, and follow the on-screen instructions. Once it's completed, reboot.
Inside one of the KFU folders (I can't remember if it's files or tools) is ADB. Right click while pressing Shift on your PC keyboard, open a command window, and type the following:
adb devices
If all goes well, your Fire should be listed. These are the steps I followed when I ran into this exact same issue. I hope it works!
Sent from my Kindle Fire using xda premium

Thats what I did I truer both the SDK method and the kindle fire utility my kindle fire isn't recognized by either one

Does anyone know what I can do

did you try to cold-reset ? hold pwr ~20sec and pwr on again
sometimes restarting the computer helps ...

Yes tryed that and still no luck

the driver (android composite adb interface) is the right one
did you check the adb_usb.ini file in .android folder in your personal folder ?
ist should include 0x1949 & 0x18d1 - if not add in a new line
restarting adb : adb kill-server
check again: adb devices

I did that already

sorry i'm really running out of ideas at this point ...
adb relies on:
adb_usb.ini in .android folder with the correct entries:
0x1949 & 0x18d1
drivers with the correct entries in android_winusb.inf (drivers of kfu do):
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
in the 32 and 64 bit section

Did that.... still not recrecognized

Have you tried a different usb port? My Fire is finocky about which port i use.
Sent from my Kindle Fire using Tapatalk

WhoRuJudge said:
Have you tried a different usb port? My Fire is finocky about which port i use.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Yes I did no luck

This is before doing anything to it yet? (just to make sure we're on the same page)
Does it show up as an external drive in Windows? Windows, right?
Seems possible to me that if you haven't done anything at all yet and it doesn't show up in Windows you might have a bad USB cable or port on your device.
If you haven't done anything yet, have you tried calling Amazon for troubleshooting / possible replacement?
(Sorry, I'm just trying to cover the things that haven't been asked.)

gadgetman13 said:
This is before doing anything to it yet? (just to make sure we're on the same page)
Does it show up as an external drive in Windows? Windows, right?
Seems possible to me that if you haven't done anything at all yet and it doesn't show up in Windows you might have a bad USB cable or port on your device.
If you haven't done anything yet, have you tried calling Amazon for troubleshooting / possible replacement?
(Sorry, I'm just trying to cover the things that haven't been asked.)
Click to expand...
Click to collapse
It is recognized by windows as a storage device but what I'm saying is that it wouldnt show up on Adb even after I added the kindle fire driver

Use the app in unlockroot.com you won't need driver
Sent from my LG-P500 using xda premium

[HELP]Bricked kindle fire very hard

i bricked my kindle fire ... like flash update.zip and then my fatal mistake i reboot kindle then i was bricked so hard please help me

a bit few information !
what exactly have you done ?
what display on kf ?
fff & twrp installed ?
kfu available ? - and moved and renamed to c:\kfu ?
status in device manager ?
os/bit ?

i install update.zip from kindle fire utility
then i reboot. it sticks on second kindle fire logo whit lower light ,no TWRP,no fff

that means you tried to restore it to pure stock
do you want to return it ?
if not gimme a pm and we can try to get to fastboot mode - reinstall fff & twrp - then it's possible to reinstall a rom of your choice
if it's not possible to get to fastboot then you'r up to a factory cable - sorry

can u give me skype on pm i will show you

Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw

Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
Follow the following after you KF to your PC:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk

I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?

josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
Try to use KFU to install Windows driver and changing the booting mode to normal
Sent from my Amazon Kindle Fire using Tapatalk

josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
furthermore check the adb_usb.ini in the .android folder in your personal folder
it should include 0x1949 (and i use to add 0x18d1 also)
would not use the sdk at all - you can save a lot of space and the drivers of the sdk don't have all the necessary entries
the sdk also messes around with the adb_usb.ini and deletes your allready made entries
would recommend to use kfu only (like in the linked in post) - you don't even have to run it but:
- the drivers are in c:\kfu\drivers\kindle and have all necessary entries
- the tools directory (c:\kfu\tools) has all commands you'll ever need (you can run all your adb and fastboot commands from here manually)

I'll try these suggestions out. I've done a wide array of changing in the .android fold and keying in the 01x.... but it hasnt been to any avail. I'll try it in the order that you've introduced.

I've tried the above mentioned and was looking in the actual driver android_winusb file and I can see that the hardware id listed on it and the actual hardware id that my kindle shows are different. It has the same VID but the PID ends in 005 instead of the 006 that is supposed to.
So I created a copy of this and altered the driver file to reflect the PID as 005, and was able to get the driver file to eventually show up as an ADB Device in the hardware description with the driver, but it still would not interact with ADB itself.

adb_usb.ini usually reflects the vid only and is necessary for adb to work
the only other vid's i'hv read that some had success are 0x006 and 0x0e79
you may add them also to adb_usb.ini - if it don't help it don't harm
furthermore would recommend to kill the adb server every time if you have changed something at the drivers with "adb kill-server"

So far, I've gotten Windows to recognize the kindle as and ADB device. Trying to get the .android file to reflect the change hasn't worked at all. The VID isn't really much of and an issue. It's the PID that seems to be different from any post that I have seen. I wish that I could force ADB to recognize the connection, but that's a bar above me. I'm an amateur at best compared to some of the people.
I'm really vying on the power of XDA here; because, this problem is so similar to the other issues that are similar with the driver issue, being stuck at the kindle fire homescreen. However when I tried the update in twerp of the update.zip file, it somehow screwed the pooch on my adb. I have a backup both on the kindle and my computer. I just can't do anything until I get ADB to recognize my KF.

maybe give firekit a try ? no windows - no drivers
http://forum.xda-developers.com/showthread.php?t=1430038

Try to use another computer. If this impossible, Install new Windows in VMWare and connect Kindle to virtual machine. Then use KFU.

Well, I've tried firekit, and ubuntu wouldn't even recognize my kindle fire... I'm half tempted to use the usb trick, but I really dont want to start taking the kindle fire apart if i dont have to.

Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.

josh24923 said:
Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.
Click to expand...
Click to collapse
What exactly do you see when you start up your KF? The stock "kindle fire" logo or the yellow triangle logo? Does the screen ever go black before getting "stuck" on the logo?
If all you ever see is one of these logos without it ever going black, it's in fastboot mode. You'll never get adb to recognize your KF in this state regardless of what drivers are on your machine. adb will only see your device when it's in recovery or booted into the OS. In fastboot mode, you can only issue fastboot commands to the KF.
You say in post #15 that you've gotten Windows to recognize it as an ADB device. What device is shown in the the device manager when you connect it? Please be specific.

[Q] Really messed up kindle fire

I hacked my kindle fire and installed cm7 about two weeks ago. Everything was fine untill I dropped it and the touch screen stopped working. After the touch screen started to work again I decided that I would just go back to stock os. My problem was that after installing from a restore point using twrp I accidently erased my sd card. Im now stuck on twrp yellow triangle. I've tried everything, kindle fire utility, kindle fire unbrick utility and nothing works. Did i screw it up or is there hope? Any help is appreciated
oh yeah and my computer wont recognize the fire anymore

I kinda had this issue. The way I fixed this was by restarting the kindle being connected to my PC. You need to update the vendor id and also the pid in your google extras folder. When you have done that you can type in command prompt "fastboot
devices" then after that you should see a device then if you do make sure you put a cm7 or the 6.2.2 file which if you use it will return your kindle to like new condition no twrp no fff. You need to put this file into your platform-tools folder and then in your command prompt "CD c:/program files/Android/Android-sdk/platform-tools/" then say the file name is update.zip now in command prompt type "adb push update.zip /sdcard/update.zip" then after file transfer you can flash the image using twrp. Hope this was helpful for you.
Sent using my CM7 Kindled Fire.

Not to sound like a noob but how do I update the vendor id

in your c:\users\.android\adb_usb.ini file add 0x18d1
also in your c:\program files\android\extras\google\usb driver\android_winusb.ini add these following lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
reboot the kindle and as you come up on the yellow fff screen type in "fastboot devices" then after that you should see a device and then type "adb push update.zip /sdcard/update.zip"
ensure that before you do this though that you have downloaded either a version of android you want to run or the original 6.2.2 from amazon. Then boot into TWRP if you arent already and flash it to your kindle. I can tell you that if you make it go into recovery from the beginning after you reboot it you can still communicate with it through command prompt.

So I added 0x18d1 but when I go to add singleadbinterface under google android winusb where do I add it under or does it matter? Sorry if Im making this harder than it should be. I'm pretty frustrated and stressed over this.

maybe this can help you:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
starting at point 3
furthermore i would never flash the original rom from amazon cause you loose fff,twrp and root
use one of the prerooted stock images instead:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
and as you can see i don't use the sdk at all - you can adapt the commands for use with sdk or use kfu

I'm still having the hardest time with this. Is there anyone willing to work on my kindle if I ship it to them, I would pay of course, 50 dollars? Or is there any one that can do screen shots walking me step by step through the process of being able to get this back up and running, ill pay for that too. Just want this to get back up and running.
Thanks for your help

If you wanted to send me your kindle if that's even legal to do with these forums I would be willing to get it back up for you.
Sent using my CM7 Kindled Fire.

Have you tried updating the latest driver. When you plug the kindle into your PC, is there an unrecognised device or there is nothing at all?