adb doesn't detect my Defy (Motorola MB525) after I call adb kill-server (rageagainstthecage exploit). Any ideas? I'm trying cyanogen's mod approach to root my Defy. I can do adb shell, it works as intended. But after I run adb kill-server and try an adb shell I get

error: device not found


It seems my phone just decides to not be connected anymore when I call kill-server. I need to physically reboot it and start everything again.

This is the complete command session I did:

[~]$ adb devices
List of devices attached 
0A3AA8D5195599849BN device

[~]$ adb shell      
$ exit
[~]$ adb kill-server
[~]$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[~]$ adb devices
List of devices attached 

[~]$ adb shell
error: device not found
[~]$


This is driving me nuts. I've searched about this problem, but there simply isn't a solution in entire Google's database. I want to use this rageagainstthecage root approach because I can see the exploit source, I'm a little nervous about using something in my personal phone that I don't know what it does (an explanation about rageagainstthecage, and a compact explanation)...

Anyone here at SE network have seen a similar problem - or have a suggestion?

I'm doing this in a Macbook Pro machine (OS X 10.6.8). My phone has Android 2.2.1.

(PS: Even without using the exploit, just doing adb kill-server and adb start-server, my cell phone isn't shown anymore on adb devices, thus receiving error: device not found. So this seens to be a problem with adb kill-server)
I had the same problem (Rom: 34.177.3.MB525.Retail.en.DE). The only rooting method that worked was Gingerbreak ( http://project89.com/root-defy-without-pc-gingerbreak-200/ )