Android OS: Android Development
If you just want to see how I got adb working with my new Toshiba Excite AT7-C, skip to the end.
Recently I started developing an Android application. It's a simple inner solar system simulation (or at least it started simple). I prototyped it using the LÖVE game engine. I then ported this early alpha to the Moai game framework.
Everything was moving along nicely with first Windows development and eventually actual android builds. The problem was the only Android device I had to test with was a Nexus 7. It was easy to talk myself into "investing" in a nice Android phone, so I added a Galaxy Note 4 to my (now growing) list of devices.
That left me with two high-end Android devices so I wanted a third lower end device. Enter the Toshiba Excite 7. It's not a great tablet, it really isn't. But at $79.99 the price was right, so I picked one up at my local Office Depot. When I played with the in-store tablet, I verified that it could be set to development mode, so I figured I was safe. Surely it would work with the Android Development Studio builds and the adb tool in particular.
Wrong! This little bugger refused to talk to the adb. It practically refused to drop its MTP device driver in favor of its ADB device driver. But after some time I got it to eventually tell me "The hash file is not present in the specified catalog file". That proved to be enough to find this stack overflow thread. I tried various suggestions posted there, but this is what made it work for me. At a command line (administrator privileged):
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Follow this up with a restart, install the driver, and then put things back as they were:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Hope this helps.