Database Develop

[Q] Rooting and the ADB Interface shows but...

Noob question for sure, sorry. I'm studying up and getting ready to root my Droid Bonic. I have installed the Motorola Device Manger for drivers. I checked the device manager per the instructions and yes with debugging on and the Media device (MTP) on the ADB Interface, "Mot Composite ADB Interface" does show in my device manager but I see there's an issue of some sort with "Portable Devices/ MTP !" Should I be concerned with this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks,
Marty
Sys Version 6.7.246
Android Version 4.0.4
Build 6.7.2.223
Windows xp SP3

martyslc said:
Noob question for sure, sorry. I'm studying up and getting ready to root my Droid Bonic. I have installed the Motorola Device Manger for drivers. I checked the device manager per the instructions and yes with debugging on and the Media device (MTP) on the ADB Interface, "Mot Composite ADB Interface" does show in my device manager but I see there's an issue of some sort with "Portable Devices/ MTP !" Should I be concerned with this?
Thanks,
Marty
Sys Version 6.7.246
Android Version 4.0.4
Build 6.7.2.223
Windows xp SP3
Click to expand...
Click to collapse
I'm thinking it should say "Droid Bionic" but not sure how to get it to show?? Maybe it wont in xp?
Any idea's??
-Marty

XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.

cellzealot said:
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
Click to expand...
Click to collapse
Thank You !

cellzealot said:
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
Click to expand...
Click to collapse
Thank You !

[Q] Can't get MTP to work

Hi,
I have been trying to connect my Nexus 6 to my work pc but I just can't get the MTP file copying mode to work properly. I have used the latest Google USB driver and actually it's not so bad. With USB Debugging turned ON, I see "Android Deivce > Android ADB Interface" properly installed in device manager. I even see my phone's serial no. when I type "adb devices" in command prompt. BUT the bloody MTP mode just refuses to work. It keeps showing up in Device Manager as "Other devices" > MTP, with a question mark next to it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I switch USB debug off, there's no Android ADB Interface, and the unknown MTP entry in "other devices" transforms to "Nexus 6", again with a question mark next to it.
I have tried to manually install the proper driver but for starters, if I just select the folder where the .inf files are located Windows don't seem to anything inside it and when I force it to use that file ("Show All Devices > Have Disk") it only shows ADB and Bootloader drivers:
So what am I suppose to choose there in order for MTP to work as it should?

Have you tried other pc or laptop??

Yes, the phone shows up correctly in all modes on my home pc.

Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ

DebianDog said:
Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I did that to no success but in the end, I just tried a different USB2.0 port and it worked, all drivers installed correctly. Now the weird thing is I can read from the internal memory of the phone, I can delete stuff from it, but when I try to copy something to it it says: "Error copying. The device has either stopped responding or has been disconnected" so I can't yet copy to it. This is driving me crazy right now...

I have this issue this morning. Right click and Update Drivers > Browse For Drivers > Let me pick > Portable Devices > Standard MTP Device > MTP Device.

BL unlock win10 pro

Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.

driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).

Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess i have to go on a win7 machine then?
Thanks.

I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.

I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy

How To Guide Fastboot < waiting for any device > Fix & Windows 10 Drivers

Hi everybody,
I recently went through the steps and got my Zenfone 8 Sake device hooked up with LineageOS & Magisk. Everything went exactly according to the steps, except for one big hurdle for me. For me, it was that my PC did not have the proper drivers for the phone. Downloading the drivers from Asus' official website below should fix this. I've outlined the complete steps for anybody else who is having the same issue.
At the point of the LineageOS install when you're going to use Fastboot to flash the recovery, your device should be at the bootloader and plugged into your PC via USB. At that point, your PC should have the proper drivers to handle the device. My PC didn't so it would just show this forever:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you go into the Device Manager, you should also see that Windows 10 is not recognizing your device properly:
Downloading the correct drivers and manually setting them in Windows should fix this problem and allow Fastboot to go ahead with the "flashing" step.
Instructions
Download these official drivers from Asus: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip (Look below to see how I got the link)
Extract ZIP to somewhere
Go into the extracted folder -> Windows_XP_VISTA_7_8_8.1 and take note of that Android folder and its path.
Open "Device Manager", find your device in "Other devices", right click on it and select "Update driver"
Select "Browse my computer for drivers"
Input the path that you noted earlier to the Android folder with the drivers.
Select "Next" and it should install the drivers from the path.
Reconnect your device and everything should be working properly!
Look below to see how it should look if properly working.
Where to Find Drivers Yourself
Search up Zenfone 8 on Google and go to the official page. This one: https://www.asus.com/us/Mobile/Phones/ZenFone/Zenfone-8/
Go to Support then Driver & Tools
Select the OS. As of this posting, the latest OS support is Windows 8.1. Not sure if this is a problem, but it worked just fine for me on Windows 10!
Download the USB driver listed there: "ASUS_Android_USB_drivers_for_Windows"
This is how it should look once you have your drivers setup properly for the device:
Hope this helps some people!!! Happy modding!

thanks... stuck on waiting for any devices also.. lucky for me to see your thread

Fast boot issue - Reported as '????????????' then switches to splash screen

Hey guys,
First time trying to flash a rom (using Windows 11). At first the Razer phone 2 showed up in my device manager as 'Android' with a yellow warning sign. I managed sort that by installing the latest android_winusb.inf drivers, and it shows up in the device manager As oculus Device>Andriod Composite ADB interface (not sure why it's under the Oculus tab, I didn't use the Oculus driver).
I've tried all three drivers (ADB Interface, Bootloader interface and Composite ADB interface) and the results are the same. When I send the 'fastboot devices' command, it will report
''???????????? fastboot'' and then it switches to the razer logo with 'Powered by Android' and 'Press any key to shutdown' text and is no longer in fastboot mode.
I assume the question marks are supposed to be a serial number.
Anyone have any ideas of what I might be doing wrong?
FYI, I've also tried 2 usb 2 ports, a usb 3, and two different Type A to C cables.

This happened to me. You need to run Powershell/Terminal in the path of the folder containing the Platform Tools. See example photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Also, make sure to follow this exactly. https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf

Thank you so much for your help, I will give this a try.

There is some sort of issue with Windows 11 and arter97-r12 and -r13. I was going to do a fresh install of SMR3 because of a few software issues and Google Play app updates. When booted into Recovery and making backups and moving files, I ended the session and rebooted "System" from TWRP boot menu. Upon execution, TWRP warned me there was no OS installed.. WORST NIGHTMARES. I've finally gotten it recovered, but what a MESS. Download platform-tools v33.0.1 from google and follow the directions from Razer to properly install ADB Fastboot drivers. See links below:
Platform-Tools: https://developer.android.com/studio/releases/platform-tools
Razer Driver installation: PDF attached
UPDATE: I found the issue was NOT necessarily my version of platform tools, It was my USB port. I am using a Surface Pro7 and tried multiple different cable and both the USB-C and -A ports to no avail. Would not communicate in fastboot mode, BUT, I then used a 4-port USB 3.0 hub, connected the phone, and all ADB/fastboot commands and communication functioned normally. once I figured this out, I was able to reinstall the proper drivers on Windows.

Same problem, u PC AMD?