Develop Bugs

[solved]win7 doesn´t recognizes my device into fastboot

okay ... a new question and also soo weird....
I want that my 2 PC´s recognize my device when its in bootloader mode
1º pc recognizes it well and its running UBUNTU.
2ºmy sister´s PC RUNNING WIN7 doesn´t recognize my DHD into bootloader mode.. but if i look the screen of the device the device automatically was changed his status to "HBOOT USB PLUG" but here is the problem:
When windoze7 detects and recognizes my device It issues a sound, but when I connect my DHD it issues different other one, that is to say detects it but it does not recognize her, then the usb mode I cannot use it
but if i boot my dhd and put her in debugging mode and run adb parameters windoze recognizes the device perfectly...
i am not an experienced user in windows
and i don´t know whats the problem. its strange..
any advise?thx in advance

Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?

Mr_JMM said:
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Click to expand...
Click to collapse
lololol we have a lot of problems Especially with windows i hate it
but she is afraid of not being able to handle it if I am not in house (SHE HAS ANOTHER DHD) in addition she likes the Microsoft OFFICE. LOL (and not open office)
Yes i had installed htc sync drivers, and sdk working well in usb debugging mode with the DHD turned on

Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?

Mr_JMM said:
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Click to expand...
Click to collapse
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically

SERGI.3210 said:
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
Click to expand...
Click to collapse
the problem appears into fastboot and into bootloader
ok in fastboot mode into sdk shell write fastboot devices and shows me a message:
"unable to initialize the aplication because ADBWINAPI.DLL not found

Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).

Mr_JMM said:
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Click to expand...
Click to collapse
ok tried another socket but the PC says to me :LOL
good idea mate... if i create aN ubuntu root/live cd i can try with the konsole
windoze please... burn in the ****ing hell
edit:with ubuntu works well again

.........................................................................................

spike_14 said:
.........................................................................................
Click to expand...
Click to collapse
good apreciation to the forum mate... LOL

okay... in advance thank´s again to my friend Mr_JMM for help me again (pressing your thank´s button AGAIN lol)
i solved my problem with "winfuck"7 (windows for microsoft´s friends)
ok when i was tried to input a fastboot code the CMD (shell) of windows returned me:
"unable to initialize the program because ADBWINAPI.DLL does not exist...
well i browsed for this file and its a library file for adb.exe commands.
under my experience fastboot parameters shouldn´t be afeccted by the ausence of this file but when i was downloaded it (a zip file with adbwinapi.exe, adbwinusbapi.dll and adb.exe) and i have put it in the folder "tools" of the sdk (Rightly where it shelters fastboot.exe) VOILÀ!!!!
i tried to enter:
"fastboot devices"
and returned to my
"HT.........."
also i tried to rebbot the device from fastboot with
"fastboot reboot" and WORKS WELL!!!!
END OF THIS THREAD.... SOLVED!!!!!!!!!!

[Q] Help with ADB....Question

I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob

i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.

diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....

I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....

adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...

I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit

j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.

copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.

device not found

adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.

No ideas?
I can connect adb over WiFi, but ofcourse it says offline.

USB debugging ticked?
A

Adb doesn't work in the bootloader. Only fastboot commands

Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).

kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.

Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.

Fastboot Issues

I have searched the net high and low for a answer to this question but nothing I have tried works.
I have used every adb and fastboot installer i could find, but nothing i do get fastboot working on my 5t. ADB is recognised and i can reboot to the bootloader from a command shell. But as soon as i type "fastboot devices" it shows nothing.
I have been into device manager and it shows issues with the fastboot driver, i have tried everything i can think of to fix this issue.
I would really love to root my 5t and and have never encountered this many issues on any of my previous devices.
Running a 64gb OP5T and Windows 10
Thank you for your help

I have now re-installed windows 10, re-installed all drivers and ADB and fastboot. ADB is still working but nothing from fastboot. It's recognised properly in device manager but nothing shows up when I type fastboot devices or fastboot OEM unlock. Any tips would be great.

http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html
check this link specially driver signature enforcement disable part, it may help

When you say "nothing shows up", what exactly is the response?
How are you getting into the bootloader? Use this from recovery or system:
Code:
adb reboot bootloader
Then proceed.

ADB is working fine. But as soon as I reboot to fastboot mode the phone doesn't respond. I can't work it out have tried everything.

djmcnz said:
When you say "nothing shows up", what exactly is the response?
Click to expand...
Click to collapse
^^

It just says waiting for device or says nothing and brings up a new line. I'm guessing the fastboot driver is the problem. I have installed the Oneplus drives included with the phone. I've installed the universal ones, still nothing.
Is there an individual fastboot driver I could manually install through device manager?
Appreciate the help.

The issue is finally fixed! I went into device manager and changed the driver from a list of drivers on my pc to WINUSB and now its working

Same problem here pal, how did you change driver to winusb, seems I've got all the gear just no idea... By gear I mean files/drivers lol. Rooted so many devices I thought this would be easy, looking forward to getting it sorted. I love a custom rom

[HELP] MI a2 lite Fastboot Exits aAutomatically

I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).

Check if you have installed drivers and run "fastboot devices" to see if device is recognised.

Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.

hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.

I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll

CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out

Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA

capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate

CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.

I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/