Database Users

Can't get Fastboot to recognise Nexus 7 under Win7 x64

I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?

Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Same thing happening with me, i want to re-lock my bootloader but when i am in bootloader mode windows does not want to recognize the device, i have tried everything too.

Did you install the correct drivers?

When connected and in the bootloader open the device manager in windows. You should see "android 1.0" near the top.
Update that driver. It should work.
Sent from my Nexus 7 using xda premium

Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Hey, As i said earlier i was having the same problem...try switching your usb cable then try. That is what fixed my problems.

ive done all mentioned above, even tried 3 different cables, no luck, anyone have suggestions

I dont know about what you want to do, but if you want to root and unlock use the wugfresh took kit. Its the bomb and as soon as I figure out where I can thank him and give a big kudos I will give thanks.
Sent from my Nexus 7 using xda app-developers app

I could be wrong, but I don't think adb works from bootloader, but the fastboot command should. I think you can also use Google's Composite ADB Interface driver too for it (I can't reboot my N7 atm or else I'd find out).
I don't have any other android-related drivers on my system either, only Google's USB driver from the SDK. I'm also on Windows 8, but I would assume Google's USB driver would work fine on Windows 7 too.
Also certain USB filter drivers may cause issues too, such as libusb, or even AMD's USB filter driver (however, I had no problems). Or if you want to wipe out any/specific USB drivers, I recommend getting: http://www.nirsoft.net/utils/usb_devices_view.html

Fastboot is dead? I can't start fastboot on my device.

I am sure I have properly installed usb driver for my nexus 7, since I have unlocked and rooted my device.
When I reboot my device to bootloader, my PC detected a new device connected, but fail to recognize it.
Also, I can't do anything when I am in fastboot mode, e.g. no effect for pressing power, vol + or vol - button.
Now, I want to return to 4.1.2 stock image, but I cannot do that on fastboot mode.
Any solution/ work arround to save my device??

Looks like drivers got screwy.. Install PDANet and let it install the drivers for your device..
http://junefabrics.com/android/download.php
One your drivers are up to snuff and you can access your device when in the bootloader again you can remove PDANet and the usb drivers will stay in place.

styckx said:
Looks like drivers got screwy.. Install PDANet and let it install the drivers for your device..
http://junefabrics.com/android/download.php
One your drivers are up to snuff and you can access your device when in the bootloader again you can remove PDANet and the usb drivers will stay in place.
Click to expand...
Click to collapse
I re-installed driver by PDANet, still I can connect Nexus 7 on normal state, but not in bootloader/ fastboot mode.
I am guessing the fastboot is dead and not related to usb driver issue.
Since there is no any response when I am pressing the button. The fastboot mode is hanged.

ADB doesn't work

When I plug in my phone to my PC the only thing that happens is it begins charging. Doesn't show signs of adb working, only thing that happens beside charging is my pc says it's an Unknown Device.
I tried all sorts of things, like USB Debugging on and off, MTP on and off, PTP on and off, I think even fastboot doesn't work. I tried to install all kinds of drivers (official, unofficial, uninstalling them afterwards if they didn't work ofc), I tried Wug's toolkit, nothing. I tried killing adb server then restarting it - nope. I even tried all of my USB ports, both 2.0 and 3.0. Also tried 3 different roms/kernels (L dev preview, Purity and Mahdi), didn't work aswell.
Things seem pretty hopeless at this point :/

Download wugfresh toolkit... look In the section of driver installation... They'll help you out
Sent from my Nexus 4 using XDA Free mobile app

driver installation...

As I said, I already tried the driver thing in Wug's Toolkit. Also my Windows allows unsigned drivers.

Bump :/

monitobeko said:
Bump :/
Click to expand...
Click to collapse
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.

venu123 said:
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
Click to expand...
Click to collapse
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.

monitobeko said:
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
Click to expand...
Click to collapse
Might be windows 8/8.1 giving you driver signature grief. Try the Universal adb drivers:
http://www.koushikdutta.com/post/universal-adb-driver

Windows 10 won't Recognize my Phone in Fastboot Mode but ADB Is working

Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk

There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.

madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established

Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button

Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.

@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*

Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.

Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works

KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.

Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..

I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.

Moto e4 magisk manger trying to instal magisk hide props config says install failed

happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself

Safety net says the response is invalid does that affect ny device being rooted

happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?

Fastboot not finding device

Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance

If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.

Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated

Up

Gearninja said:
Up
Click to expand...
Click to collapse
Down