.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Thibor69 said:
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try I get this ERROR:
.
Please any thoughts on this ???
Thanks
.
Click to expand...
Click to collapse
Try plugging in the phone to the computer while in recovery mode. I always found there were more drivers to be installed. Verify that usb debugging is active. Also I think you need most recent Java dev edition up to date. Those are the only handfuls I can think of.
The Root said:
Try plugging in the phone to the computer while in recovery mode. I always found there were more drivers to be installed. Verify that usb debugging is active. Also I think you need most recent Java dev edition up to date. Those are the only handfuls I can think of.
Click to expand...
Click to collapse
All items you mentioned have been checked but still can not connect via adb Any other thoughts ?
Thank you
.
Thibor69 said:
All items you mentioned have been checked but still can not connect via adb Any other thoughts ?
Thank you
.
Click to expand...
Click to collapse
Unlock OEM bootloader in dev options?
The Root said:
Unlock OEM bootloader in dev options?
Click to expand...
Click to collapse
Thank you but ... been there done that. See picture of device manager bellow if it helps ?
Thibor69 said:
Thank you but ... been there done that. See picture of device manager bellow if it helps ?
Click to expand...
Click to collapse
I haven't had to use ADB since the GS4. It's everything done through recovery or download mode?
The Root said:
I haven't had to use ADB since the GS4. It's everything done through recovery or download mode?
Click to expand...
Click to collapse
Really ?? Well I am using a guide that says to flash the SU binaries via Odin in download mode. What other method is there without a
custom recovery, like TWRP ?
If I could achieve root without Odin and adb please tell me : )
Thank you
Google for and install the system wide adb. You restart your computer lately? Simple as that sounds I've had it not work until I restart.
Not sure what guide you're fallowing but look into something called FlashFire.
If all else fails make ANOTHER ADB help thread.
---------- Post added at 12:21 AM ---------- Previous post was at 12:18 AM ----------
Additionally did you even Google "error cannot Connect to daemon"? Or just start making help me threads cause in 2 seconds I found all kinds of solutions and people saying what worked for them...
Thibor69 said:
Really ?? Well I am using a guide that says to flash the SU binaries via Odin in download mode. What other method is there without a
custom recovery, like TWRP ?
If I could achieve root without Odin and adb please tell me : )
Thank you
Click to expand...
Click to collapse
I believe while I ODIN'd the eng kernel, that I ran ADB only with it booted up and connected to W10.
Try to open cmd prompt as administrator
Sent from my SM-G935T using XDA-Developers mobile app
krad42 said:
Try to open cmd prompt as administrator
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah forgot that is part of the instructions.
Sent from my SM-G935T using XDA-Developers mobile app
Related
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?
Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?
Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that
Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.
I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.
aval1392 said:
I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.
Click to expand...
Click to collapse
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?
How about "fastboot devices"?
Heisenberg said:
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?
Click to expand...
Click to collapse
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did
aval1392 said:
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did
Click to expand...
Click to collapse
We already have a detailed guide right here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hello, I've bought the HTC U Ultra for my birthday at a very good price (250€) and I'm very satisfied about this phone!
Only, it's been 3 months since I try to root without any success. I can not find the "fastboot" mode in the bootloader and I do not know how.
Yet I followed all the tutorials to the letter (French expression I do not know if you go to understand ... x)) but I have never reached that point. I have the ADBs and all the other files needed.
Also, I made all the updates at the first launch of the phone. Is that why it's blocked?
Thank you in advance.
PS: I also unlocked the bootloader in the development options.
PS n°2: I post here because the French forums are desperate desert for this phone.
Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.
bc Yume said:
Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.
Click to expand...
Click to collapse
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.
SofianeLasri said:
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.
Click to expand...
Click to collapse
The computer is unable to recognise your phone. Maybe another port.
bc Yume said:
The computer is unable to recognise your phone. Maybe another port.
Click to expand...
Click to collapse
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.
SofianeLasri said:
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.
Click to expand...
Click to collapse
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?
bc Yume said:
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?
Click to expand...
Click to collapse
I use minimal adb 1.4.2 and i don't installed htc sync.
I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.
bc Yume said:
I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.
Click to expand...
Click to collapse
Yes but I must to download a lot of GB to user these abd. :/
I've just install htc sync, I tell you more if it work.
UPDATE : Oh it work! x) I never thought it would work! I thought htc sync was a software like those samsull that block the phone.
cool but i've now s-on and a i can"t install twrp with this. x)
SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
You can install TWRP as long as your bootloader is unlocked, regardless of the status of S-ON or S-OFF
SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
double check "Allow USB debugging" for the computer. From Developers "Revoke USB debugging Auth" . Unplug & plug back USB cable should come up with dialog box for auth. You may (not sure) this from cmd: adb reboot fastboot which could come up with error msg: "error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."
You cant find fastboot mode because it is now called download mode...
Hi
sorry if post is duplicated , i search but not found on this topic
When i connect my mobile to pc and then run command to go to bootloader ,
it shows Daemon not running. Starting it now on port 5037
then goes to bootloader
in bootloader no command work there , means only adb reboot bootloader works
even fastboot devices shows nothing
please advise me what i have to do
Sorry for my bad English
Thanks
if from your pc you type:
adb reboot bootloader
does it go to the bootloader?
If so, while the bootloader is displayed, from the pc if you type:
fastboot devices
Are you saying it responds with nothing?
minhas4all said:
Hi
sorry if post is duplicated , i search but not found on this topic
When i connect my mobile to pc and then run command to go to bootloader ,
it shows Daemon not running. Starting it now on port 5037
then goes to bootloader
in bootloader no command work there , means only adb reboot bootloader works
even fastboot devices shows nothing
please advise me what i have to do
Sorry for my bad English
Thanks
Click to expand...
Click to collapse
So I'm confused.
If I type "adb reboot bootloader" with my phone connected; it boots into fast boot mode and will accept fastboot commands.
it shows the "Fastboot" screen with the option to start the device if the power buttoned is pressed.
What are you trying to do?
Are you saying you don't get the screen?
Zargone said:
if from your pc you type:
adb reboot bootloader
does it go to the bootloader?
If so, while the bootloader is displayed, from the pc if you type:
fastboot devices
Are you saying it responds with nothing?
Click to expand...
Click to collapse
Thanks
when i enter fastboot devices
it does nothing just go to next prompt
nothing happen
i want to unlock bootloader and root
Thanks once again
tech_head said:
So I'm confused.
If I type "adb reboot bootloader" with my phone connected; it boots into fast boot mode and will accept fastboot commands.
it shows the "Fastboot" screen with the option to start the device if the power buttoned is pressed.
What are you trying to do?
Are you saying you don't get the screen?
Click to expand...
Click to collapse
Thanks
with me when I type "adb reboot bootloader" with my phone connected; it boots into fast boot mode but in fastboot no command works
i want to unlock bootloader and root
thanks
Did you remember to go into the developer options and enable USB Debugging and OEM Unlock?
jhs39 said:
Did you remember to go into the developer options and enable USB Debugging and OEM Unlock?
Click to expand...
Click to collapse
That was my next question.
jhs39 said:
Did you remember to go into the developer options and enable USB Debugging and OEM Unlock?
Click to expand...
Click to collapse
Yes
tech_head said:
That was my next question.
Click to expand...
Click to collapse
Yes
I root many phones
its easy
even i try other cables and 3 different laptops and pc
and the result was same
minhas4all said:
Yes
I root many phones
its easy
even i try other cables and 3 different laptops and pc
and the result was same
Click to expand...
Click to collapse
What drivers are you using.
I presume you are on a Windows laptop?
yes on windows 10
Sent from my PH-1 using XDA Free mobile app
Sounds like you're using an older fastboot, so you'll need to do fastboot -i 0x2e17 <whatever_command>
Or you can get the latest platform tools from https://developer.android.com/studio/releases/platform-tools#downloads
Did you install the essential phone drivers?
not sure about version but download some days back from links provided.. any ways thanks download from ur link then let u know
thanks
Sent from my PH-1 using XDA Free mobile app
ziddey said:
Sounds like you're using an older fastboot, so you'll need to do fastboot -i 0x2e17 <whatever_command>
Or you can get the latest platform tools from https://developer.android.com/studio/releases/platform-tools#downloads
Click to expand...
Click to collapse
not sure about version but download some days back from links provided.. any ways thanks download from ur link then let u know
thanks
crixley said:
Did you install the essential phone drivers?
Click to expand...
Click to collapse
Thinks so but can u provide me the links? thanks
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it