Ok, let's get the prelims out of the way. First I searched the forums for this issue but was unable to find anything. That being said I am human and may have missed something so please forgive if that is the case. Next, I am an experienced software engineer so there should be no need to go over the obvious stuff, i.e. is the phone plugged in, is debugging mode turned on, is USB mode set to charge only etc (but I won't be offended if you do mention the obvious stuff). Finally I have rooted and deodexed a DX previously using the same methods and it worked flawlessly.
Quick backstory: Had a DX, rooted it, deodexed it, life was glorious, killed DX, paid $100 for a insurance replacement from Assurion. New DX came with Gingerbread and latest firmware. A year later trying to root so I can load the CM 9 beta.
What's the problem?
So I have tried two versions of the same rooting process. V1 one is the manual version with adb command line pushing su, SuperUser.apk, rageagainstthecage-arm5.bin etc. V2 is essentially the same accept using the DoRootForWindows single click package with the doroot.bat file. Both version fail in the same place. Basically pushing everything and running the .bin file all work great the problem happens when I get booted out of adb. Once that happens adb never sees the device again unless I reboot the phone but of course if I reboot the phone the work that was done by the .bin files goes away. I have tried rebooting the computer, restarting the command prompt, and changing the USB connection mode but the device never shows up again which prevents me from completing the process. Any help is greatly appreciated.