How your razr hd (in AP Fastboot Mode) look in Windows 7 x64 device manager? I need the screenshot with device ID. Maybe wrong driver were installed cause device dont show correct usb device id (for example in BP Tools, ADB interface not install driver, before i edit the INF file of drivers). Mine as default installed it as Mot Single ADB Interface in the Fastboot Mode (!!!) looks like there is the problem why it not flashed correctly. Help please!
Related
It's been bugging me for a while that I can't use ADB while in recovery. It's a matter of getting the drivers installed correctly, I think, I just don't know exactly how to do it. When the phone is booted I can use ADB and MTP just fine. Odin sees my phone in download mode as well. The only problem is in recovery. I'm using TWRP 2.3.3.0, but I've had the problem on previous version of TWRP and CWM. I have the Samsung USB drivers installed, and when the phone is booted Device Manager (in Windows 7) says the drivers being used are from Samsung. However, when in recovery Device Manager shows SAMSUNG_Android_SCH-I535 with the yellow '!' and says no drivers are installed. I can try to choose the drivers to install manually, but if I point to the Samsung USB Drivers folder, Windows can't find the right drivers automatically and there are 25 subfolders with somewhat cryptic names, so I don't know which to choose.
Does anyone know how to get ADB working in recovery?
EDIT: Got it working. I don't know anything about how drivers work, but I dug around a little and it turns out the device shows different Hardware IDs when booted versus when in recovery. The drivers .inf has to contain one of the Hardware IDs given by the device so after finding the driver being used by Windows (by searching for the Class GUID given in the driver details when the phone was booted and searching through all the .infs in the Samsung drivers folder for the matching string) I just added a line with one of the Hardware IDs given in recovery so Windows would install the driver. I tested with adb devices, adb shell and adb pull default.prop and each worked fine.
For anyone interested the driver being used is in 25_escape. In the file ssudadb.inf just add the line
Code:
%CompositeAdbInterface% = ssud.Install, <Hardware ID>
under [Google.NTx86] and [Google.NTamd64], where <Hardware ID> is one of the Hardware IDs given by your phone when in recovery. In Windows, go to the Device Manger > right click your phone > Properties > Details tab > Hardware IDs in the drop down. Mine was
Code:
%CompositeAdbInterface% = ssud.Install, USB\VID_18D1&PID_D001
Then update the driver, browse for drivers, pick the 25_escape folder, and you're good to go. The driver will fail a security check because you've modified it, I ignored it.
I imagine this could cause a problem if some other device uses the same Hardware ID (e.g. if it's some sort of generic or default one that's given in recovery) but I'll cross the bridge if I come to it. There may be some safer way to force driver installation.
EDIT: After doing this you'll get a warning when you plug your phone while it's booted. It will say something to the effect of Hardware ID missing or not being able to identify the device plugged in. This isn't a problem though, ADB and MTP still work fine and the device is identified properly in Device Manager.
my moto g3 with cm 13 nightly doesnt appear on windows explorer on my windows 10 pc and it doesnt appear on command window when i write {fastboot devices } . so does any one know how to fix this problem
Install drivers, set charging mode to data transfer in notifications
i already installed drivers and its read on command window but doesnot appear on windows explorer please replay if you know how to fix this
When the phone is in fastboot, it won't appear on pc via file explorer.
If it's not showing up as a media device, connect it to pc, press windows key+X and select device manager. See if moto g3 icon has a yellow triangle, that would mean that some drivers are missing or not installed properly. You will need to install them again.
Sent from my Moto X Pure using Tapatalk
i have connected my phone to pc and opened device manger and there is no moto g3 tag but there is an unknown device in section called other devices
and i already installed the device drivers and prove of that is when i write fastboot devices in command window the device serial appear
so can you help me
Then the MTP drivers are not installed properly. Check if adb devices command recognizes your phone. If yes, then adb and fastboot drivers are fine and only MTP driver is not properly installed. Go to start>seach for 'devices and printers' open it, it should open a control center page. Check if the phone appears there, and if it's there, check for a yellow triangle. If there is a yellow triangle present, just right-click and select remove device. Then reboot the PC and reconnect the phone, it should install all the drivers again.
Sent from my Moto X Pure using Tapatalk
yes as you said the mtp drivers arenot installed and tried the meathod that you wrote it but iam still facing the same problem is there any meathod to install mtp drivers manually
You try searching on the internet for .inf driver files for android mtp. Or try this : http://www.driverscape.com/download/android-mtp
Broadcasted from Zeta Reticuli
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.
I have a phone which is Oppo A5s, where my cousin change the password and forgot it, so I tried to search how to format it, and after several days of searching I found SP Flash tool, Miracle Box and other Software like DrFone etch, but only SP FLASH TOOL has progressed, so I watch videos on youtube and download compatible ROM then I stuck on a problem (enabled-verified-boot opporeserve2).
So I found a youtube video that needed an SGPT file, but since there was nothing SGPT file in extracted OFP, I search again how to generate it, then Youtuber said that I just need to use the WWW MTK tool and do READBACK and Format it on Format Tab in SP FLASH TOOL, which is the cause of my problem now. So as of now my Phone doesn't open, so when I try to connect it via USB it says - Unknown USB Device (Device Descriptor Request Failed). hope there is someone who can help me with my problem, I will really really appreciate it. Thank you in Advance.
If USB debugging is enabled on your device and suitable correct ADB driver is installed on your PC, then your PC should recognize your Android device as an ADB device:
NOTE: Usually, the ADB entry will show under the heading "ADB Interface", or "Android Phone" (or similar), but sometimes it will show under the manufacturer name instead (e.g. "Samsung", "HTC", etc).
xXx yYy said:
If USB debugging is enabled on your device and suitable correct ADB driver is installed on your PC, then your PC should recognize your Android device as an ADB device:
NOTE: Usually, the ADB entry will show under the heading "ADB Interface", or "Android Phone" (or similar), but sometimes it will show under the manufacturer name instead (e.g. "Samsung", "HTC", etc).
Click to expand...
Click to collapse
But ADB Interface is not showing even I installed ADB driver or Universal ADB Drivers not showing at all. It's just saying "Unknown SB Device".