[Droid Incredible Android Development] shamidude:
This is frustrating

I have been trying the various methods listed in this thread, but I still haven't had any luck so far. So I decided to post what I have done so far, hopefully others can spot what's wrong with my setup (besides bad luck).

I tested with two XP machines, and a linux box. None of these machines is brand new, and they range from couple of years to six years old. On XP, I verified that I can run "adb shell" when the phone is not in recovery mode, so I guess this means that there are no issues with my USB drivers (I used the SDK to download the USB drivers, patched the .inf file then used these files to install the drivers when Windows asked me). On linux, there is no need for special drivers, and ADB works out of the box.

I read elsewhere that some had luck by downgrading the ROM image, so I followed the instructions from the other thread, but that didn't help.

I also read that others had luck with different SD cards, so I have been trying different cards (even bought a new PNY), and I tried formatting them with FAT32. I even tried putting a lot of content on one of these cards, but that didn't help either.

The way I understand it, all the different methods are trying to interfere with the timing of the processes that are started by the phone during recovery, and if successful, then the "adbd" daemon in the phone will start in recovery mode, and then we can communicate with it via "adb shell". Based on this, I don't think that there is a real need for the loop batch file, because the "adbd" daemon would start anyway (for example, poping the card method doesn't require "adb shell" to be entered).

So this all boils down to timing when to connect the USB or insert the SD card. What frustrates me is that I can clearly see the flicker on the screen and I can hear the funny noise, both around 7-8 seconds after the white screen shows up, and a second before the black screen with triangle shows up. Yet, I can't seem to hit the sweet spot.

Can someone tell me if I should adjust my timing more close to the flickering, or towards the black screen?

I also would like to check the timing of the chimes that Windows make when the phone is connected/disconnected. When I am using the alternate method, I can hear the chiming at the following times:

- after the phone reboots (from the black screens), indicating that the phone is disconnected.

- about ten seconds after the white screen show up, indicating that the phone is connected.

- then I type "adb reboot recovery" and when the phone reboots, I hear the sound indicating the phone is disconnected.

- next, the white screen shows up, flicker/noise, insert the USB/SD card and no sound.

- about two seconds after the black screen shows up, I hear the sound back. This should indicate that the phone is connected, but the phone doesn't show up in device manager, and the phone is not recognized by the adb tool.

I wonder how this compares to what others have witnessed. After a successful adb recovery, do you hear the sound before/close to the triangle screen, or is it late like what happens to me? Also, do you see the phone in the device manager when the phone is in adb recovery?

Thanks in advance..