[myTouch 4G Q&A, Help & Troubleshooting] ibrokeditgood:
Nope.....it's blank under devices and gives me a time it took to tell me that..lol..

if I do the adb commands do nothing.

now ,if i do fastboot commands, for devices, I get a response (while in the fastboot menu on the phone) , it is a 12 character alpha numeric result.

if I use ruu.exe (with the actual HTC drivers) I can go all thru the menus in the ruu prog, asks me if i want to update to the same version number that I have, agree, and it goes back to the "......reboot bootloader...." or "....waiting for bootloader...."

go and look at the ruu log files and I can see this:

<T075739><DEBUG><CMD>fastboot devices</CMD>

</DEBUG></T075739>

<T075741><DEBUG><OUT>SH183RM02457	fastboot</OUT>

</DEBUG></T075741>

<T075741><DEBUG><CMD>fastboot -s SH183RM02457 getvar boot-mode</CMD>

</DEBUG></T075741>

<T075742><DEBUG><OUT>boot-mode: FASTBOOT</OUT>

</DEBUG></T075742>

<T075747><DEBUG><CMD>adb devices</CMD>

</DEBUG></T075747>

<T075748><DEBUG><OUT>List of devices attached

</OUT>

also:

<T075504><DEBUG><CMD>fastboot devices</CMD>

</DEBUG></T075504>

<T075505><DEBUG><OUT>SH183RM02457	fastboot</OUT>

</DEBUG></T075505>

<T075505><DEBUG><CMD>fastboot -s SH183RM02457 getvar boot-mode</CMD>

</DEBUG></T075505>

<T075506><DEBUG><OUT>boot-mode: FASTBOOT</OUT>

</DEBUG></T075506>

<T075506><DEBUG><CMD>fastboot -s SH183RM02457 getvar version-main</CMD>

</DEBUG></T075506>

<T075508><DEBUG><OUT>version-main: 2.32.531.1</OUT>

</DEBUG></T075508>

<T075514><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>

</DEBUG></T075514>

<T075514><DEBUG><CMD>adb devices</CMD>

</DEBUG></T075514>

<T075515><DEBUG><OUT>List of devices attached

</OUT>

and:

<T075438><DEBUG><CMD>fastboot -s SH183RM02457 getvar boot-mode</CMD>

</DEBUG></T075438>

<T075440><DEBUG><OUT>boot-mode: FASTBOOT</OUT>

</DEBUG></T075440>

<T075440><DEBUG><CMD>fastboot -s SH183RM02457 getvar battery-status</CMD>

</DEBUG></T075440>

<T075441><DEBUG><OUT>battery-status: good</OUT>

</DEBUG></T075441>

<T075441><DEBUG><PAGE>====== VerificationDlg ======</PAGE>

</DEBUG></T075441>

<T075441><DEBUG><CMD>adb devices</CMD>

</DEBUG></T075441>

<T075442><DEBUG><OUT>List of devices attached

</OUT>

and every once in a while i get :

<T075521><DEBUG><CMD>fastboot -s SH183RM02457 oem rebootRUU</CMD>

</DEBUG></T075521>

<T075607><DEBUG><OUT>... FAILED (status read failed (Too many links))</OUT>

</DEBUG></T075607>

soooooo............lol...any suggestions?

like i said before, it "sees it, but it doesn't"

(keep in mind this is the RUU.EXE log file clips) <--but, I get the same results if I use adb or fastboot manually in the cmd prompt as well....

So I'm going to "guess" that inside the OS , "fastboot is on", "usb debugging is on", and probably "usb power only is on"....Just a guess, cause I cant remember what they were set at before it looped and then froze up and then hung on the boot menus, but the logs point that way-in my opinion... but then again, I'm no pro.:D

EDIT:================

I was finally able to get the connection with the pc to read "android composite device", had to fiddle with the drivers a bit, change usb ports, disable my webcam...lmao! can now get the pc to "see" it in hboot AND fastboot mode, as far as the "safely remove hardware" in the task bar is concerned...adb program still acts just the same, killed the server, started the manager after a reboot to make sure it knows where everything is and configured.....also, any idea why it (adb) says loading on port 5*** and not usb, and when i cmd adb usb i get device not found.....hey, the environment variables should be adb and pointed to the platform-tools directory, correct? cause i've actually tried it to the tools AND the platform-tools.....7hrs today and thats all I got...oy! think my rear is taking root to the recliner.....