Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
Related
In command prompt, I typed "fastboot -i 0x0fce getvar version"
And, it stays at <waiting for device>
I'd like to point out that I succeeded at flashing custom ROM last time, but now, it won't connect in fastmode.
I've installed the SDK (obviously)
Added the .inf file from SE site
Installed drivers from Flashtool folder
LED goes blue when connecting.
I've tried different ports, different OS, different PC altogether, but everything ends up with <waiting for device>.
Is the problem on the phone? How can I fix it?
Drivers seem to be fine...
Does your phone really go into fastboot? Blue LED stays on, nothing on the screen. If yes, check drivers once again! Does Windows detect the device?
Someguyfromhell said:
Drivers seem to be fine...
Does your phone really go into fastboot? Blue LED stays on, nothing on the screen. If yes, check drivers once again! Does Windows detect the device?
Click to expand...
Click to collapse
Yes, the LED is blue, the screen is off.
Windows does make sound when connecting, and it doesn't pop up "new device" wizard.
Hey! Just noticed something.
When uninstall the drivers connect the device, Device Manager says "S1boot fastboot" briefly before going into "SEMC Flash Device"
How can I disable it from going to SEMC Flash Device?
And it happens only when I have drivers uninstalled. Seems they install once I connect the phone. Tried again without uninstalling drivers, and it goes straight to "Flash device"
Then maybe wrong drivers installed?
Someguyfromhell said:
Then maybe wrong drivers installed?
Click to expand...
Click to collapse
Maybe:
I've reinstalled the SDK - didn't work
Added .inf file from SE site - didn't work
Installed Flashtool drivers - didn't work
But now, I'm waiting for Lollylost100 to reupload the drivers he once uploaded on Megaupload - I think those ones worked last time (hopefully)
I'll install Debian and try again with new OS, with no installed drivers or whatever...
USB debuging is on?
Just wait a few seconds after connecting you phone in fastboot mode, sometimes computer takes time process.
Theonewithideas said:
In command prompt, I typed "fastboot -i 0x0fce getvar version"
And, it stays at <waiting for device>
I'd like to point out that I succeeded at flashing custom ROM last time, but now, it won't connect in fastmode.
I've installed the SDK (obviously)
Added the .inf file from SE site
Installed drivers from Flashtool folder
LED goes blue when connecting.
I've tried different ports, different OS, different PC altogether, but everything ends up with <waiting for device>.
Is the problem on the phone? How can I fix it?
Click to expand...
Click to collapse
2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar
Dont forget to thanx if this helpfull...
xbox360k550 said:
USB debuging is on?
Click to expand...
Click to collapse
Yes.
hsrbnr said:
Just wait a few seconds after connecting you phone in fastboot mode, sometimes computer takes time process.
Click to expand...
Click to collapse
Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.
Lasanda said:
2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar
Dont forget to thanx if this helpfull...
Click to expand...
Click to collapse
Okay, I will try this and post the results.
Actually, will this work with Mini?
Theonewithideas said:
Yes.
Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.
Okay, I will try this and post the results.
Actually, will this work with Mini?
Click to expand...
Click to collapse
I think it also works with mini as well.just try it.
Installed everything again, on Ubuntu. I've reached the Windows checkpoint: it again says "<waiting for device>".
Could this be a phone-related error?
Theonewithideas said:
Installed everything again, on Ubuntu. I've reached the Windows checkpoint: it again says "<waiting for device>".
Could this be a phone-related error?
Click to expand...
Click to collapse
try my method in windows pc.it dont works in ubuntu.it seems,there is no problem in your device.it may be there is some thing missing what you want.try my method back with windows pc and post clearly the resault with steps.if something wrong.i will help you.don't worry....
Windows drivers do not work on Ubuntu, the same vice-versa also.
Lasanda said:
2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar
Dont forget to thanx if this helpfull...
Click to expand...
Click to collapse
Okay, if you say so:
first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed...
This didn't work, it's SEMC Flash Device again, and fastboot doesn't work.
.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder...
Can't find the drivers. It will not help, every fastboot folder is the same.
.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
... or, you can just type "cd" and then location to fastboot.
Theonewithideas said:
Okay, if you say so:
first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed...
This didn't work, it's SEMC Flash Device again, and fastboot doesn't work.
.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder...
Can't find the drivers. It will not help, every fastboot folder is the same.
.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
... or, you can just type "cd" and then location to fastboot.
Click to expand...
Click to collapse
ok.i got that.another thing i need to know is when u do first step is that the device manager recognized your device,if does,is it updates your device drivers when u point the drivers location to x64 or x86?(when u do that it must show android adb interface drivers installed, when u check device manager)which version of windows u used to do those steps? and tell me your device name and model.i will upload a correct fastboot program for u.just keep your hopes alive....
EDIT
Theonewithideas said:
When uninstall the drivers connect the device, Device Manager says "S1boot fastboot" briefly before going into "SEMC Flash Device"
Click to expand...
Click to collapse
just have to mention u one thing..now i read this post u quoted before.it seems there is no any problem in your device.when u uninstall drivers u says this "S1boot fastboot" shows on your device manager it meens your device works well.S1boot fastboot meen device fastboot hardware it exactly not installed yet.u need to update drivers of this "S1boot fastboot" as my methods first step.just send me the progress and answers for my questions thats all.i will send a fix.
Can't connect in fastboot mode
Hi!
I want to unlock the bootloader of my Xperia Arc S (Lt18i) but i can't connect my phone in fastboot mode. When i connect the cable to PC, the LED flashes blue, but just for a few seconds and turns red. The message that appears in command prompt is "waiting for device". I tried so several solutions but no one worked.
Could you help me?
Thanks.
---------- Post added at 11:37 PM ---------- Previous post was at 11:11 PM ----------
Gioo25 said:
Hi!
I want to unlock the bootloader of my Xperia Arc S (Lt18i) but i can't connect my phone in fastboot mode. When i connect the cable to PC, the LED flashes blue, but just for a few seconds and turns red. The message that appears in command prompt is "waiting for device". I tried so several solutions but no one worked.
Could you help me?
Thanks.
Click to expand...
Click to collapse
Sorry for my last post. When searching in some forums, I discovered that I can not unlock the bootloader. It seems that is a definition of the system.
Thank You And sorry. :crying:
Go to Service Mode to see if it can be unlock.
brixe said:
Go to Service Mode to see if it can be unlock.
Click to expand...
Click to collapse
Thank you! I've done that and the result is this: "bootloader unlock allowed: NO".
SAme Same
Theonewithideas said:
Yes.
Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.
Okay, I will try this and post the results.
Actually, will this work with Mini?
Click to expand...
Click to collapse
Having the same problem with my SE LWW.
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Do you have usb debugging enabled?
Sent from my HTC One X+ using Tapatalk 4 Beta
Roodenburgertje said:
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Click to expand...
Click to collapse
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
reaper90 said:
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
Click to expand...
Click to collapse
Yes im trying to adb acces from recovery without succes
is it win 8 or 8.1 ?
Win 8.
And i have a international hox+
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
wrong wrong wrong, shut up, NasaGeek
Roodenburgertje said:
Yes im trying to adb acces from recovery without succes
Click to expand...
Click to collapse
Works for me without problems on Windows 8. I don't know what driver version i have, i think i installed the driver with htc sync from my phone and uninstalled htc sync later.
Try the following:
1. Connect your phone to your computer and reboot in recovery.
2. Open command line and navigate to the folder where your adb/fastboot files are.
3. Type "adb start-server" and wait some minutes (as i said it may take some minutes to recognize the phone in recovery)
4. Type "adb devices" and now your device should be listed there as in recovery. If not, wait some more time and try again. Shouldn't take longer than 10 minutes. Otherwise there's probably something wrong with your driver and/or adb/fastboot files.
NasaGeek said:
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
Click to expand...
Click to collapse
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You are quite correct. I don't know what I was thinking. I'll edit my post.
The driver that comes with htc sync works just fine...
Alternate is Koush's universal ADB driver...
Hi,
I'm trying to unlock my Huawei Ascend Y300 but I'm stuck in fastboot.
I followed this guide: (not allowed to post outside links but you can find the guide by looking for "Free Huawei bootloader unlock tutorial"), but got my unlock code sent from Huawei by mail since the dc-unlocker tool didn't work as well (probably the same problem as with fastboot).
When the phone is turned on I can see it with "adb devices" but once I'm in fastboot mode (pink screen) no device can be found with "fastboot devices".
When the phone is in fastboot mode and being plugged into the computer it is recognized by Windows.
I tried two kinds of Huawei Drivers: "Huawei_U8680_U8730_U8800_U8860" and "Huawei_Android_driver" (for the last one: see the guide stated above). I also tried three different computers.
I'm using Windows 7 64bit if that helps.
Edit:
Same problem in Ubuntu, found in "adb devices" but not in fastboot mode.
Any idea anyone?
Thanks,
Patrick
Anybody?
SirBelial said:
Anybody?
Click to expand...
Click to collapse
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Maurice5813 said:
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Click to expand...
Click to collapse
SirBelial said:
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Click to expand...
Click to collapse
does you phone have a bootloader?
Maurice5813 said:
does you phone have a bootloader?
Click to expand...
Click to collapse
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
SirBelial said:
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
Click to expand...
Click to collapse
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Maurice5813 said:
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Click to expand...
Click to collapse
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
SirBelial said:
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
Click to expand...
Click to collapse
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Maurice5813 said:
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Click to expand...
Click to collapse
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Enable USB Debugging
SirBelial said:
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Click to expand...
Click to collapse
I encountered this but then started the phone and enabled USB debugging and it then found the phone.
did u get this going? im having exactly the same issue. cannot get the phone detected in fastboot, either in Linux or windows
I had the same issue. Took my hours, different Systems, Cables... Try the following:
Code:
adb reboot-bootloader
.
Hope this helps! Your phone should stay at the Huawei Logo (no pink screen!)
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
eriknors said:
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
Click to expand...
Click to collapse
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
dottat said:
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
Click to expand...
Click to collapse
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
eriknors said:
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
Click to expand...
Click to collapse
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
Click to expand...
Click to collapse
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
eriknors said:
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
Click to expand...
Click to collapse
Not an install. Unzip and run cmd prompt from there. Note that your fastboot commands will start HTC_fastboot
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
eriknors said:
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
Click to expand...
Click to collapse
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Got it
dottat said:
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Click to expand...
Click to collapse
No dice. ADB worked just fine but still no fastboot
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Uzephi said:
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Acoustichayes said:
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Click to expand...
Click to collapse
Well tbh I've been trying on both just to see if anything works.
eriknors said:
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Click to expand...
Click to collapse
He asked that because if you use mine you need to use htc_fastboot devices
Otherwise you will be using the fastboot from sdk install.
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Had the same issue tried every thing, but eventually end up installing uBuntu that solved every thing.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Its due to the missing device descriptor.
Royal PITA, I have yet to get it working. I just keep a win7 laptop around.
The only way this could be "fixed", would be if we had a newer eng-hboot that had the descriptors set.
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
Me too !
Drivers are here: https://developer.android.com/studio/run/win-usb
These are the ones I use for ADB/Fastboot.
May I ask if anybody solved this already?
Having the same issue, tried various drivers, but fastboot won't find my phone
Help is highly apperciated!
Clock
If you using windows 10 have you disable the drivers signature verification.. And search on here (XDA) for Min ADB & Fastboot tools, easier than using SDK tools unless you modding apks ect..
Okay, I got this working.
When in fastboot mode, you have to go to the device manager, update driver, and manually choose the google fastboot driver. Then the ! is gone and it works.
Fastboot drivers for Xperia XZ1
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode.
Click to expand...
Click to collapse
I add a hint to the solution that is working for me (Windows 7, 64 bit): https://forum.xda-developers.com/showpost.php?p=79221714&postcount=44
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
when u connect phone to pc choose no data transfer then open cmd and write: adb reboot fastboot
Click to expand...
Click to collapse