ADB Device Not Found

Search This thread

kp12584

Member
Feb 18, 2014
13
0
Hey all,

After flashing Loki's EnSec I cannot access my Omate as an ADB device via my Win7 command prompt. Also, I cannot flash Dee's Bluetooth ROM through any method. I simply get the Installation Aborted screen in recovery when I try and Goo Manager fails also.

I'm sure it is me, but I cannot figure it out.

Watch: Omate 1/8/1900
Laptop: Win7, SP1

Thoughts?
 
Last edited:

kp12584

Member
Feb 18, 2014
13
0
ADB found...still can't flash.

After resetting some SDK stuff, I can now execute some ADB commands from the command prompt. However, I cannot flash anything. I simply get the 'waiting for device' prompt...and I wait...and wait...and wait.

Thoughts on this new problem?
 

Lokifish Marz

Inactive Recognized Developer
Mar 13, 2011
3,848
3,748
Olympus Mons, Mars
martian-imperium.com
  1. Can you transfer files to and from the device while connected to the PC?
  2. Is "USB Debugging" enabled on your watch?
  3. Have you used another root method prior to trying to install the patch?
  4. What firmware are you on?

Installing the SDK is not needed. Only Universal ADB Drivers.
 

kp12584

Member
Feb 18, 2014
13
0
@Loki

  1. Can you transfer files to and from the device while connected to the PC?
  2. Is "USB Debugging" enabled on your watch?
  3. Have you used another root method prior to trying to install the patch?
  4. What firmware are you on?

Installing the SDK is not needed. Only Universal ADB Drivers.

1: Yep - transfer files is working
2: Yep - debug enabled
3. No other root besides yours
4. Omate_TrueSmart_EnSec_20140302_V2.0
 

kp12584

Member
Feb 18, 2014
13
0
Old release

EnSec 20140302 ? That version was pulled the day it was released and is five releases old. The current release is EnSec + Operative 20140318. I would suggest you flash stock (20140120 firmware only) and start over.

I see. I guess I haven't checked on updates in a bit - but where would I go to find that info?

Thanks
 

Top Liked Posts