Related
Has anybody gotten their computer to recognize their phone in fastboot yet? When I hook it up it comes up with adb interface device yet neither fastboot or adb commands work. Please don't point me to Android SDK or PDANet as I have tried those both. Pointing manually to the inf. I have even tried Moto drivers from their website still nothing. Working on bootloader **** and can't do anything at all without getting into fastboot and fastboot commands.
I can't even get to my standard recovery as I have been trying to do some mods my self and work around the boot loader. I am not able to get the adb interface to work in fastboot either. Even though I have the driver installed and shows it is working in device manager properly. I think there is definetley a driver issue with the adb for this phone.
The motor drivers worked for me adb wise not sure about fastboot are you referring to the recovery menu?
Sent from my DROID X2 using Tapatalk
wdenker said:
I can't even get to my standard recovery as I have been trying to do some mods my self and work around the boot loader. I am not able to get the adb interface to work in fastboot either. Even though I have the driver installed and shows it is working in device manager properly. I think there is definetley a driver issue with the adb for this phone.
Click to expand...
Click to collapse
Power off the phone then hold volume down while powering it on. when it says fastboot keep hitting volume down till you get to the option android recovery then hit volume up. When you get the triangle and the android push both volume up and down. You are now in recovery. Adb won't work with fastboot mode.
from what i can tell you need a newer version of fastboot.exe
chevyowner said:
from what i can tell you need a newer version of fastboot.exe
Click to expand...
Click to collapse
fastboot.exe doesn't mean anything if the device isn't recognized as a fastboot device
taylorhome11 said:
fastboot.exe doesn't mean anything if the device isn't recognized as a fastboot device
Click to expand...
Click to collapse
my droid x2 shows up in fastboot mode in device manager as "mot single ADB Interface"
i said that because i have been there
now goodluck getting me to give you a fastboot.exe that works with the x2
chevyowner said:
my droid x2 shows up in fastboot mode in device manager as "mot single ADB Interface"
i said that because i have been there
now goodluck getting me to give you a fastboot.exe that works with the x2
Click to expand...
Click to collapse
Then if you aren't going to share why post? piss off
i never said i would not share, nice wrong assumption
here you go, now you "piss off"
chevyowner said:
i never said i would not share, nice wrong assumption
here you go, now you "piss off"
Click to expand...
Click to collapse
im pretty sure "now goodluck getting me to give you a fastboot.exe that works with the x2" means im not giving it....but now you changed your mind
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!)
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
so i bricked my Firefly Mobile Allure 64 LTE which is a rebrand of Ulefone be touch they said; trying to flash ulefone's rom. and bang!
im trying to revive the phone. problem is any driver i install, whenever i plug it on computer(installed the driver needed/win10 64bit) it ignores the driver i installed and it connects to the computer like a normal connection with our without battery(normal use:file transfer etc.) can't get the phone to META mode
anyone?
jocelator said:
anyone?
Click to expand...
Click to collapse
Hello and welcome to the XDA community, the forum rules for this forum states that no bumping is allowed.
If you are able to access adb, you can do adb reboot recovery, if not, tell us the results. Try to access fastboot too via adb reboot bootloader or adb reboot fastboot. If you are able to access fastboot, you can flash the .zip or .img of your system.
RAZERZDAHACKER said:
Hello and welcome to the XDA community, the forum rules for this forum states that no bumping is allowed.
If you are able to access adb, you can do adb reboot recovery, if not, tell us the results. Try to access fastboot too via adb reboot bootloader or adb reboot fastboot. If you are able to access fastboot, you can flash the .zip or .img of your system.
Click to expand...
Click to collapse
oh... my apologies sir.
i dont know how to use adb. can you give me a guide or tutorial.
jocelator said:
oh... my apologies sir.
i dont know how to use adb. can you give me a guide or tutorial.
Click to expand...
Click to collapse
It is okay, just download and install this and connect your device. Open adb up and type adb devices, tell me what it says. Connect your phone in different modes (like recovery or bootloader) and test the adb devices or fastboot devices and report the results!
RAZERZDAHACKER said:
It is okay, just download and install this and connect your device. Open adb up and type adb devices, tell me what it says. Connect your phone in different modes (like recovery or bootloader) and test the adb devices or fastboot devices and report the results!
Click to expand...
Click to collapse
in the guide "USB Debugging MUST be turned ON in the device for ADB to see it" i dont think i can do that since i cant open the phone since it is hard bricked
jocelator said:
in the guide "USB Debugging MUST be turned ON in the device for ADB to see it" i dont think i can do that since i cant open the phone since it is hard bricked
Click to expand...
Click to collapse
But did you plug it in in different modes though? Also, try out this univeral unbricker that I wrote https://drive.google.com/open?id=0B6vSHGXxJIWmalZoWnNaTVczT0E
RAZERZDAHACKER said:
But did you plug it in in different modes though? Also, try out this univeral unbricker that I wrote https://drive.google.com/open?id=0B6vSHGXxJIWmalZoWnNaTVczT0E
Click to expand...
Click to collapse
what different modes? enlighten me
jocelator said:
what different modes? enlighten me
Click to expand...
Click to collapse
Fastboot, sideload, recovery, all kinds of stuff that enables you to access it through adb or fastboot.
Btw, that tool I gave you, I scripted it while I was tired and I didn't test it (nightly build) but this one I tested today and it works marvelous.