ADB Command Prompt Can No Longer See My Fascinate

cocatholicdad#AC

Active member
Mar 12, 2010
32
3
0
Visit site
I have a Verizon Fascinate that was on CM7.1. I used Odin to flash Atlas Pit 2.2.2 with Repartition checked, along with the stock rom. I have done this before and never had a problem. Once Stock updated to Froyo 2.2.2 I attempted to root using my pc Command Prompt Window.

Changed directory to point to my root files.

Then attempted the adb devices command.
It indicated the daemon started successfully, then showed attached devices as blank.

Since it could not see my Fascinate I could not continue.

I confirmed debugging mode was set.

I then flashed geewiz rom and tried again and got the same results. Since geewiz is pre rooted the root worked fine but adb still can't find my phone.

Any ideas how I can fix this?
 

Landshark

Well-known member
Jan 11, 2011
4,434
1,382
113
Visit site
I have a Verizon Fascinate that was on CM7.1. I used Odin to flash Atlas Pit 2.2.2 with Repartition checked, along with the stock rom. I have done this before and never had a problem. Once Stock updated to Froyo 2.2.2 I attempted to root using my pc Command Prompt Window.

Changed directory to point to my root files.

Then attempted the adb devices command.
It indicated the daemon started successfully, then showed attached devices as blank.

Since it could not see my Fascinate I could not continue.

I confirmed debugging mode was set.

I then flashed geewiz rom and tried again and got the same results. Since geewiz is pre rooted the root worked fine but adb still can't find my phone.

Any ideas how I can fix this?

When you went to CM7.1 did you uninstall the Samsung drivers from your computer and install the Nexus drivers so your phone would be recognized in ADB? If you did, now that you are not running CM7, you will need the Samsung Fascinate drivers since your phone is once again being seen as a Fascinate and not a Nexus. That would be the only reason I could think of as to why your phone is not being recognized. If that's not the case, perhaps just an uninstall and reinstall of the Samsung drivers may help.
 

cocatholicdad#AC

Active member
Mar 12, 2010
32
3
0
Visit site
No. I made sure of it. My wife has a stock Fascinate that has never been rooted and it could see her device fine. I notice I can not connect via usb to my PC on mine anymore either. The drivers no longer recognize my phone apparently.

Also just to be sure I reinstalled the drivers to no avail.

Reflashing stock with the pit did not help either.
 

Landshark

Well-known member
Jan 11, 2011
4,434
1,382
113
Visit site
No. I made sure of it. My wife has a stock Fascinate that has never been rooted and it could see her device fine. I notice I can not connect via usb to my PC on mine anymore either. The drivers no longer recognize my phone apparently.

Also just to be sure I reinstalled the drivers to no avail.

Reflashing stock with the pit did not help either.

Try plugging your phone into the computer with the usb cable while you have usb debugging enabled on your phone. Don't pull down the notification bar and try to connect to the computer, just make sure you have usb debugging checked under menu=>settings=>applications=>development. Also make sure usb settings is set to mass storage. Then while the phone is plugged into the usb cord, restart your phone. This has often times corrected the problem you are describing.
 
  • Like
Reactions: cocatholicdad#AC

Trending Posts

Forum statistics

Threads
942,376
Messages
6,913,742
Members
3,158,380
Latest member
knowledge is power