Database Users

Device won't root. Cannot get the device "offline"

Hope this isn't a post that will really piss everyone off, but I'm not sure really where to go from here. Tried about 20 times. I run the loop command, it shows up for about 1 line and goes away.
I am still getting an Android 1.0 error of some sort. I've been reading about how to get this driver installed correctly. I uninstalled everything and started over (USBDeview, HTC Sync...The one for the Slide, SDK, Updated it with SDK Updater)
Windows 7 x64
Just went to Computer> right click> Manage> ABD Testing Interface....
I have a little yellow exclamation point next to this... Tried updating the driver. Not really sure though what driver I need or where it's at or the place I need to download it.
You ever feel like you've surfed cyberspace to the end of the megacluster? Yeah that's pretty much where I'm at frustrated, broken hearted, and wanting a one-click root procedure like the g1/mytouch.
Is it rude to wave money in developers faces for help? Does this make you feel like a stripper?
Ahhhh I'm just stuck.... Help would be so awesome.

I'm not a dev but I do feel like a stripper, but for unrelated reasons... Anyways. On my win7 64 I had to use pdanet and actually have the program running. For whatever reason when I tried closing pdanet it wouldn't work, so give that a shot. It also stopped the android 1.0 driver issues. I also gather from wes garners' twitter page he's working on a method of rooting that runs the adb scripts and **** for you. Maybe just wait it out.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

DaemionIX said:
Fermunky, I've been following your problem because I was having it too. What finally got it for me was, I formated a different sd card, put it in the phone, removed all software ( htc sync, pdanet) and removed all drivers I could find using usbdeview. Then rebooted with phone unplugged, installed pdanet following all their instructions, then the loop worked perfect. Good luck
Tl;dr version, i tried it all at the same time and it worked
Click to expand...
Click to collapse
That was on a win x64 system. Honestly I think it was the sd card, as weird as that sounds, because I tried all the usb stuff for about 4 hours to no avail, swapped out the sd card, rooted the first try.

I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.

2Noob4U said:
I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.
Click to expand...
Click to collapse
Just pdanet

Alright I'll give it a whirl. I'll let you know how it goes.
-------------------------------------
Sent via the XDA Tapatalk App

Took me a day to figure this out too. Uninstall all the drivers then install pda net and reboot .. you must reboot .. then try the process . I wasn't rebooting after removing drivers and it wouldn't work until I did ..
-------------------------------------
Sent via the XDA Tapatalk App

You should really have looked at the other thread on this already. Any driver will work, as long as you can get "adb devices" to show your phone when the phone is booted normally. Whats worked for many others, especially myself after 4 days of trying, was using a different, freshly formatted SD card. Good luck.

To no avail!
Just tried again. Tried without rebooting the computer the first time and "offline" would hang for a little longer than before. Still wouldn't stay. Should I have tried recovery a few more times? (I did try about three times.)
Uninstalled and reinstalled everything. Then tried "loop". "offline" doesn't even show up. Tried an old SD card too after I reformatted it. Does it matter the size of the SD card?
fermunky- I've been following your posts pretty regularly and I think I'm having the same problem. Yes I do have ADB devices showing up if the phone is on normally and running through the SDK. Had a problem for a while where it wouldn't recognize the device, but it does now.
C:\>cd android\tools
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 device
If I do figure this out I want to post up a step-by-step in this thread of what exactly I did to make it easier on people like myself.

It goes like this
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
Is there a way to catch it offline?

It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.

sk8rbebop said:
It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.
Click to expand...
Click to collapse
Am I doing it right overall though.
1. Switch out SD card right before getting into recovery so there is absolutely nothing on the SD Card. (I've noticed if you let it boot it puts a LOS.DIR file or something of that sort.
fermunky had a similar problem and said once he installed everything a certain way he got it "offline" right away.
Is there a step-by-step I should be trying? Maybe another post I haven't read yet?
I'll keep trying, but it's kind of seeming like a lost cause. I've only been trying 2 days (Ha ha) After I surpass 4 days or so I'll give up and wait for Wes for the hook up.
Money for him!

Ultimate fix for device detection!!!
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.

Thanks
mtjnkee said:
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.
Click to expand...
Click to collapse
Haven't tried this yet.
Do it in a few hours. I've been at this all day and need some food and beer! Beer always makes computer/smartphone problems disappear.

sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.

Straight to "recovery" not "offline"!
Ok is this good or bad? It's not what the video nor website says, but it's different and different is good!
Just lists the HT........ recovery over and over??? Can I start everything from here?
Dude if this works I'll buy you a beer!

I'd be glad to move it.
HighRidas said:
sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.
Click to expand...
Click to collapse
No biggie man. Just wanna figure it out and you can move this at will if you like.

If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App

sk8rbebop said:
If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Tried... It wouldn't push said failed

Then it is an issue with your PC. Do what mtjnkee said and uninstall everything Android. Then use HTC Sync's drivers.

Eclipse, Adb, Device = ADB crash

I am trying to get a development environment setup and running into all sorts of problems with ADB when I have an actual device attached to the system. I am using eclipse and can use the emulators with no problems, until I attach an actual device to the system. At that point, even when trying to debug on the emulator, ADB keeps crashing. I can start a debug session on the actual device, but if I try to switch to the DDMS view, ADB crashes.
I am running on windows 7 and have even go so far as to do a complete reinstall of the system and only install the development tools only to have this problem show up again. I can't believe that this is normal, how could anything get developed with this type of issue?
I have been searching for answers and not been able to find anything helpful. I restart ADB only for it to immediately crash again. All the software is updated to the most recent versions. This problems occurs on both my desktop and laptop so don't think it is a hardware issue with my systems. Only thing really in common is the device, my EVO.
Any help would be appreciated. This is driving me nuts. I need to get this working for some projects but I feel like I am pounding my head on a brick wall trying to get it to work.
If this isn't the best place for this thread, could you please point me in the right direction? Thanks.

First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.

jr10000 said:
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
Click to expand...
Click to collapse
ADB is working fine like this. My phone shows up in the devices command. I can shell to it. Push/Pull files. All with no problems. It's not until I try running a debug session from eclipse (either in the emulator or on the device) that it crashes.

No one here that can help?

To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.

Rootstonian said:
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Click to expand...
Click to collapse
The problem is I can't use EITHER when the phone is connected. So even if I wanted to debug on the phone, I can't.

i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3

NoEnd said:
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
Click to expand...
Click to collapse
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.

edboston said:
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
Click to expand...
Click to collapse
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!

awrnsmn said:
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
Click to expand...
Click to collapse
No luck. Eclipse reported it couldn't run adb because it needed elevated. Thanks for the suggestion.

yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??

NoEnd said:
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
Click to expand...
Click to collapse
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.

edboston said:
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
Click to expand...
Click to collapse
please do and reply back

NoEnd said:
please do and reply back
Click to expand...
Click to collapse
Just tried running it on 32bit windows. Same problems. ADB crashing.

edboston said:
Just tried running it on 32bit windows. Same problems. ADB crashing.
Click to expand...
Click to collapse
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD

NoEnd said:
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
Click to expand...
Click to collapse
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.

I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott

edboston said:
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
Click to expand...
Click to collapse
Okay. Tried it with the stock ROM/Kernel with the same results. ADB crashing.

Delvorak said:
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
Click to expand...
Click to collapse
your reply can be summarize in few points:
1- its a library or code you used in that app that crashes ADB.exe (as u said only this app)
2- it maybe an app in the phone, the apps i suspect is SU(for rooted phones) or Whatsapp(because it's runs a service that stops as soon as the USB mode activated)
i hope this Thread doesn't die, because it's the only one on the WEB.

One thing I checked between the v7 and v8 of the SDK is adb.exe is the same version in each of these. So the thought about the DDMB being a possible culprit is a good possibility. Because outside of eclipse debugging, I have no problems with ADB at all.

{Q} CM7 Nook Color not recoginzed in either Linux or Windows

Hello, I have CM 7.0.3 encore with the overclocked kernel on my nook. Lately I have not been able to get the thing to connect to my computer in either windows or Linux. (It's XP and "Lucid Lynx" 10.04 Ubuntu if that helps)
If I connect my cable to either the front of back USB ports (because I have tried both under both OSs) at best I get my windows install to see and start to run auto hardware install. This, of course does not work and the machine will inform me that my new hardware (which it correctly ids as a nook until this point) may not work correctly. And, it does not. It displays as 'removable drive' and clicking on it pulls up an 'insert disk please' message.
In Ubuntu the Nook will show up as B&N Ereader. Both SD cards (the internal and the card in slot) show as the same thing. Clicking on them brings up a message that this drive is not a folder and cannot be opened as such.
This thread leads me to think that there should be a notification in windows about the usb being connected...and as soon as I post this I will be restarting to check that... but I really rather do this under Ubuntu. ETA. This does not work for me. Canceling the install software wizard does not work either. (I have been uninstalling the faulty installs each time and rebooting the comp without the nook attached. Oh, and the Nook IS awake too. )
Searches bring up nothing, and I'm a bit lost.
I must be missing something so basic and simple no one has had this issue but me. I mean, Android is a Linux variant, right? They should be able to talk to one another!??

If your trying to accomplish what I think you are then it doesn't matter what your computers says. Plug your Nook into the PC and open your notifications window. There should be a USB icon on the status bar waiting for your input. Just follow the prompts.

Given you have gone through the process of installing the Android SDK, in Linux, from the terminal you need to change to your target folder to
Code:
~/android-sdk-linux_86/platform-tools
then you need to log in as root and kill, then start the server. make sure to exit root when you are done.
Code:
su : enter password
# ./adb kill-server
# ./adb start-server
# exit
then it should pick it up.

I have the same problem as OP and went crazy trying to figure out what I was doing wrong. It's not as simple as everyone suggests.
To be clear I'm using Linux, Ubuntu Natty. I have a Samsung Vibrant also running CM7 nightlies. Start adb, plug in Vibrant, shows up in adb devices list without any problem. Plug in the NC no device in adb. running lsusb there is no android vendorID for the NC but there is for the Vibrant. The NC only shows a vendorID for the mass storage just like the OP says.
The NC is booting with CM7 nightlie on the SD card, not eMMC. Will that make a difference?

IFLATLINE, Thing is, there is no notification popup on my Nook for me to tap.
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
I did manage to brick the nook trying to update the build last night so I'm in the middle of reflashing it. So, as soon as I finish making a boot micro SD (I know, I should just have one I keep for this but I don't) I will be flashing phiremod's version of CM7 on the nook.
digver, I did find somewhere on here that the OC kernel was causing some people grief and that once they removed it they had no issues connecting the the computer... but I think they were windows. I'm not sure if that will fix this very annoying little problem.

katsrevenge said:
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
Click to expand...
Click to collapse
personally i <3 linux. It's the only way to fly esp with dealing with Androids. Android Central has a GREAT write up on how to install the SDK on your Linux unit.
I'll have to look up the link @ home. I'm at work and WebSense blocks 99% of everything.

[Q] ADB - Device Not Found (v6.2.1)

Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.

CrimsonSentinel13 said:
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
Click to expand...
Click to collapse
BurritoRoot causes the normal adbD to behave as an unsecure one, but if your not seeing the kindle under adb devices then you have PC side problems likely.

I figured it might be PC side. I've tried everything I could after updating the Android SDK. Updating everything with what's needed for the Fire to be seen hasn't worked. I'm a bit at a dead end for ideas... I tried even using the USB3 controller on my mobo but no luck either.
Edit: Fixed!
I uninstalled the Kindle Fire from the Device Manager & got it reinstalled. It now works perfectly with ADB. I'm in the process of rooting it as I type this.

I have the same problem.
However, I have 2 fires, one running CM7 and the other 6.2.1.
The PC recognizes the one running CM7 but not 6.2.1.
So, I don't think it is the PC.
No matter what I do, adb and fastboot, device not found.
Can not access the one with 6.2.1.
Does not show up in device manager.
I have read and try various things from xda, Rootzwili and Liliputing.
​

follow this video thats wht helped me get past that part ur on
http://www.youtube.com/watch?v=KapnjR89ICA&feature=player_embedded
u have to make sure u update the drive for ur kindle with the driver from sdk
this is also helpful tooo
http://forum.xda-developers.com/showthread.php?t=1409120

What worked for me was following this guide up to step 3. Then, with the device manager it launches, i deleted ALL my adb/android devices and then I let windows re-install the driver when I plugged the kindle (you may need to choose the driver manually), then I could finally access fastboot/adb via cmd..

Solved problem, Thank You.
I have many drivers on my PC, Motorola, Samsung, HTC and Android.
I noticed on one boot the Kindle was listed as Samsung Android Phone.
I uninstalled the Samsung drivers.
Connected the Kindle. All is fine.
Connected my Samsung SGS II, it found the drivers.​

Crimson, thanks for sharing your fix of uninstalling then reinstalling. Worked for me.

hi, i would like to apologize in advance, i am new to adb so i'm not sure if i'm even doing it right, but i have successfully rooted and installed cm7, after much googling. i did it a while ago and used the clockwork mod method. i would like to replace it with twrp but the only way i have found to do it is by using adb or the kindle fire utility, which if i understand correctly uses adb. the only problem with that is that i can't get adb to recognize it. i'm assuming it's because i don't have the proper drivers for the "cm7 kindle" because i install them for the stock kindle. please help me. i have no idea how to fix this. thanks
edit: ok guys i'm really sorry, i'm an idiot, i forgot that i had turned off usb debugging. turned it back on, worked perfectly. again sorry.

ADB not seeing TPT

I am hoping someone can help me before the ICS OTA hits in the US.
I am trying to root, but I can NOT get ADB to see the TPT.
I am using win 7 64 bit, and have downloaded the adb driver and modified the .inf. It shows up in dev man under android phone as thinkpad adb, but when I run adb devices...nothing.
I installed that latest Java dev and android stk but still nothing.
The TPT is on OTA 2.5.
I have searched everywhere but cannot fined any answer.
Any ideas?
Thanks!

Is USB debugging enabled on your tpt? Did you try a different USB cable/port? On your PC are you in the same directory as adb.exe?

Yes, Yes, and Yes.
ADB is running fine...it just cant see the TPT even tho windows can.

I'm sure you're a little frustrated. I had that happen, and it turned out there were two adb processes running. A reboot fixed that. I'm sorry I don't have the answer.

It IS frustrating, but I appreciate your suggestions!

try running the emulator and make sure you can connect to it via adb, as a check to make sure adb deamon is starting up correctly.

True. Worked for me.

For whatever reason, it was my system that I do all my adb work on....just refuses to see the TPT.
Used my notebook with nothing installed and it went just fine.

My Win7-64 PC could only see my TPT as a portable device, and was listed between drive letters. I wanted to see it under "Android Phones."
After about 6 hours of searching, having installed the Lenovo-provided drivers probably 40 times, I went out on a limb and opened the Device Mangler, individually uninstalled each of the portable devices, including the TPT. Rebooted my PC. Plugged in the TPT, and finally it appeared under Android Phones, and ADB recognized it (I typed "adb devices" in the command prompt and it was listed).
What it came down to is the driver that wanted to be the default was trumping the one I wanted. Beware the Diva. She's not all that.
I should add that I also unplugged a usb card reader (that was making all the drive letters) because I thought that might be the culprit, but it still showed up in the Device Mangler, so I don't think unplugging it made a difference.
I miss Win2K.