Hi
I have install on my PC Android SDK Tools and Android-setup-1.4.3 tool on my PC with OS Win 10
I was tried to run and connect by adb console with my OnePlus One in fastboot mode but it doesn't see device.
What I have do wrong.? On win devices manager I see my OPO as Android Bootloader Interface, even I change driver and see OPO as Android ADB Interface I still cant connect with OPO by adb console.
Any Help?
My OPO is freezing after normal booting or safeboot mode. I can boot it to stock recovery or to fastboot mode,
Try different USB cable
Related
Software version : MA 1.7.12 N8
Total Disk Space : 8G
Adb in normal startups and fastboot in bootloader mode ( after pressing power + volume down ) are not working
Could anyone tell me how to solve this Thanks in advance
Have you enabled USB Debugging?
I don't think there's an option to enable USB Debugging in the original system before getting into fastboot and rooting the device.
Are you able to boot into the ROM? You just can't use adb & fastboot?
Yes I can boot into the ROM. It's the original ROM. And I can't use adb or fastboot.
You have a start button? Try start + power to boot into fastboot mode.
Thanks for your reply&time.
I believe that power + volume down is the way to boot into fastboot now, and after booting into fastboot and connecting the USB line, (fastboot devices) command in the computer (tried Mac OS X 10.8, Windows XP virtual machine and Windows 7) shows no device connected. When using start+power, my device boots normally into the original rom.
All right. I think I just got rid of the fastboot issue. There's something missing with the driver. I'll post my solution after I verify it and flash DPRom successfully.
The problem is acutually pretty silly. A proper adb driver is required for fastboot.
I installed tineprogramming's adb driver to fix it.
(http://forum.xda-developers.com/showthread.php?t=1454685)
http://forum.xda-developers.com/showthread.php?t=2472970
Only thread I found in my quick search that was well, my problem.
After accidentally hitting Factory Reset, I managed to lose all USB connectivity functionality.
I CAN boot into bootloader.
I CAN boot into recovery.
ADB - no response.
Fastboot - no response.
Connecting my computer USB cable to my phone in the bootloader screen doesn't even change to "Fastboot USB" anymore.
I have Windows 8 on my desktop and I just tried connecting it to my buddys laptop to see if that would change, and no luck.
Fastboot pulls zero devices in command prompt, and adb (obviously) doesn't either.
Mounting SD/USB in Recovery does nothing and isn't detected by either pc's.
Any ideas?
Windows 8 64-bit
TWRP Recovery - 2.6.3.0
HTC BMP USB Driver 1.0.5375
HTC Driver Installer 4.5.0.001
Android Debug Bridge 1.0.31
SuperCID
TKTAB911 said:
http://forum.xda-developers.com/showthread.php?t=2472970
Only thread I found in my quick search that was well, my problem.
After accidentally hitting Factory Reset, I managed to lose all USB connectivity functionality.
I CAN boot into bootloader.
I CAN boot into recovery.
ADB - no response.
Fastboot - no response.
Connecting my computer USB cable to my phone in the bootloader screen doesn't even change to "Fastboot USB" anymore.
I have Windows 8 on my desktop and I just tried connecting it to my buddys laptop to see if that would change, and no luck.
Fastboot pulls zero devices in command prompt, and adb (obviously) doesn't either.
Mounting SD/USB in Recovery does nothing and isn't detected by either pc's.
Any ideas?
Windows 8 64-bit
TWRP Recovery - 2.6.3.0
HTC BMP USB Driver 1.0.5375
HTC Driver Installer 4.5.0.001
Android Debug Bridge 1.0.31
SuperCID
Click to expand...
Click to collapse
What recovery/
Sent from my HTC One XL using XDA Premium 4 mobile app
When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.
I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.
Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.
I can us adb command in pc windows 10 but when i try to go into fastboot mode pc stop recognise my device . Even when my device connected to pc like data storage option and i restart my device it disconnected. I have tried installing every driver and also tried using android app callled bugjaeger to check my fastboot but it also doesn't not in this app when i give command to restart into bootloader it show null in device status and so in pc. I can use adb sideload in pc and flashed pixel experience rom but i want to switch rom so my device not respond to any fastboot command i am not even able to flash stock rom please help ! Pc is ryzen based and i use aosp recovery comes with pixel experience any help is appreciated !
Hello, i have a really weird problem. When the phone is power up and working i can adb devices and see in the list my phone,. But when im in fastboot adb devices show empty. The phone is recognized in my device list with the drivers in fastboot mode.
I have installed a lot of drivers
i have tried in windows 10 and windows 7
thanks in advance.
When you're in fastboot mode you need to use the fastboot command, not ADB...
Try fastboot devices.