Motorola Tools Mode Config Disabled

1,472 views

Skip to first unread message

Slikk Huisenga

unread,

Aug 3, 2024, 1:34:52 PM8/3/24

to lianiculet

I am attempting to install an Android app on my brand new Nexus 10. I have a .apk file. I have downloaded the Android SDK, installed "Android SDK Tools", "Android SDK Platform-tools", and Google USB Driver. I have checked the setting on my Nexus 10 for "Unknown Sources".

When I run "adb devices" from the command terminal, it doesn't list any devices. I attempted to follow this recommendation, because it was identical to a suggestion I had previously found here on Stack Overflow. After following those steps, "adb devices" still returns an empty list and to make it worse, when I connect my Nexus 10 to my PC, Windows doesn't show any folders within the device.

I have undone the steps in that link, along with everything else I have done so far, as well as uninstalling my Nexus 10 from Device Manager and reinstalling it, but I am still not seeing any folders in the device.

Sometimes ADB loses connection to the device, and needs to be reset. If you have everything else working (ie USB driver installed, Developer settings enabled on the device), and still can't see your device, you need to reset the ADB process.

After downloading the Google drivers via Android SDK Manager (available via Eclipse, Intellij or Android Studio), I had to update the driver in Computer Management > Device Manager > Other Devices > ADB - right clicking and clicking on update driver and browsing for updated driver finally did the trick.

BTW, a total nightmare for me as well. I continue to be bewildered that setting up a dev environment should be the most difficult task imaginable, with each new inexplicable failure leading to another one. Jeesh! Good luck.

Edit: I recommend you DO NOT run ADB under VirtualBox if you are using a Windows Host. Somehow I got VirtualBox to lock the device drivers on the host, eventually making it so that the ADB wouldn't work on the client nor the host for any device I plugged in. To fix, I removed VirtualBox extensions on the host and ran _devices_view.html to delete the incorrect drivers. I could not get the correct drivers to load while VirtualBox extensions were installed, and this problem was a complete bastard to diagnose and fix.

For the Blu Studio 5.5s ADB drivers, you have to go through this hoop. I am certain it is the same with all Blu phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the Blu device with USB cable and USB Debuggin off, you will see that Windows 7 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, BLU STUDIO 5.5 S (or the device you are working with). Do not bother getting the hardware ID yet - just observe that this happens (which indicates you are good so far and don't have a bad cable or something).

Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the BLU STUDIO 5.5 S or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices, in this example the name that appears is BLU STUDIO 5.5 S. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.

Now do as the instructions say above, of course customizing the lines you add the the INF file with those relating to your own phone, not the Nexus 10. Here is what to customize; when you downloaded the SDK you should have a file structure expanded from the ZIP such as this:

Find the file named: android_winusb.inf in the usb_driver folderMake a copy of it and name it anything, such as myname.infEdit the myname.inf and add the lines as instructed above only modified for your particular phone. For example, for the BLU STUDIO 5.5 S, I added the following 2 lines as instructed in the 2 locations as instructed.

Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the myname.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command "adb devices" as instructed in this tutorial and now you should see that the phone is now discovered and communicating.

For my issue and after long time suffering with Meizu C9 Pro witch require just android ADB drivers (no special drivers) referring to manufacturer and it solved in my Windows 7 PC by the bellow steps.

I was using a Samsung phone with Android 10. It was detecting earlier but stopped detecting on Windows 10 after I factory data reset the Android 10 phone. Though It was normally detected on Windows 11 PC.

When I dig a little deeper, in android phone settings inside developer options there is a configuration named Default USB Configuration [Settings -> Developer Options -> Default USB Configuration]. When I select that option, There were several options that came and none of them was selected by default.

For Windows 10, had to manually download the latest platform SDK tools from Android as the version supplied through Visual Studio 2017 EMDK for Xamarin was not sufficient. Everything else except adb.exe devices worked.

It's so easy, just turn off your Android device, and then hold down both "Volume Down" key and "Power" at the same time. Wait a few seconds till it start in recovery mode, done.Now type adb devices, and you'll see your device.

I had the same problem with my Windows 8. The Android/SDK USB driver was installed correctly, but I forgot to install the USB driver from my phone. After installing the phone USB driver ADB works fine.

Have you had an android update recently? I updated to Lollipop and all the sudden I had no adb devices. Boo! I spent awhile trying a few things to no avail. Then I went into my developer options and lo and behold, "USB debugging" had been turned off. Silly Google. After turning it back on, it immediately showed up and I'm back in business!

GoTo DeviceManager, then right click on the android device and click uninstall driver.Unplug and plug the device back...then a pop will come on your device while your pc installs the required drivers. Click "allow" on the popup.You can see your device when you type "adb devices" in command prompt.

If you've gotten this phone and computer pair to work together before, but they aren't working any more, it might be a specific program on your computer rather than a problem on your phone. Some programs install/use their own adb, and only one of these can connect to your phone at a time. I think this makes a race condition, so sometimes it'll connect fine.

1- I personally use DM to collect and analyse the messages between a mobile (UE) and a network. I use it with Qualcomm QXDM and QPST tools to analyse wireless protocol stack messages. With commercial phones, usually the DM is blocked as a security measure as it allows you to decapsulate the messages sent/received by the UE. I haven't heard about another use for it until now.

3- If DIAG mode is enabled, you can see it in your Device Manager. Here is a snapshot of mine. That means you have to install the correct drivers for the device (which was tricky with many phones). The device should has Qualcomm Chipset!

Diagnostics Mode can be used to change your device's radio band & modem settings and other stuff like changing IMEI address or MAC Address, if you have appropriate software like DFS CDMA Tool or QPST.

Note: This will work only if your phone's ramdisk has the appropriate configs enabled for the 'diag,adb' property.If that didn't work, better open /init.xxxxxxx.usb.rc (xxxxxxx represents your device's codename or chipname or whatever) and check for properties related to 'diag'.

If you mean the developer options, then as of Android 4.2 I believe, one of the things about the developer options is that the menu is just hidden now. You have to purposely enable the menu to access the options.

I have a Nvidia Shield Tablet that froze on me. After powering down it hangs on the nvidia boot up screen when I try to boot it up. Nvidia support says it is a 'soft-brick', as I can't get into recovery mode from fastboot. I am trying to get a recovery image on the tablet. However, the bootloader is locked and I'm pretty sure USB debugging was not enabled ahead of time. Therefore, I can't perform an unlock using adb, and so can't flash a recovery image. When trying to access through a platform-tools terminal, it doesn't show in a list of adb devices.

Any help is appreciated at this point, I can't think of anything else to try. Sorry in advance for mixing up terms etc. I've just been researching the past few nights and trying to find a solution. I'm far from an expert.

adb and fastboot are different modes. you can enter recovery without usb debugging. Press and hold Power + Vol Down. This is the bootloader screen. Now navigate to recovery with Vol Keys, Power to confirm. Wait a Moment. When the android symbol appears, press Vol Up + Power to enter recovery. Now do Factory reset.