Just a quick question.
Im unable to access fastboot or bootloader mode through adb command line.
I turned on usb debugging, connected phone to usb cable with my pc, run command line in platform-tools - adb devices and nothing happens.
I think i know the answer, but i want to be sure. Is it because i dont have unlocked bootloaded (OEM Unlock, still 6 days to wait)
Do you have the proper drivers? Try downloading the universal ADB drivers.
Sent from my Lenovo P2a42 using Tapatalk
Switch USB mode to PTP instead of MTP. I don't know why, but it works like that after Android KitKat/Lollipop release. Used this trick on LG G2 mini and now on my P2
I dont know if i have correct drivers, but i think so
https://dl.google.com/android/installer_r24.4.1-windows.exe
http://download.oracle.com/otn-pub/...m=1498221676_80503fd7b283f64cfa8ae7825b0021e2
My Xiaomi Redmi phopne is detected correctly, but its rooted and OEM unlocked
edit:
It's fine now. Its unbelivable what a mess is with adb files/usb drivers and similar. There is so much that can go wrong.
I wiped everything and installed minimal adb and fastboot + lenovo usb/mtp drivers
Now pc detects my phone.
Related
adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.
No ideas?
I can connect adb over WiFi, but ofcourse it says offline.
USB debugging ticked?
A
Adb doesn't work in the bootloader. Only fastboot commands
Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.
Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.
Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
Hi all!
I'd like to unlock my bootloader, but fastboot just saying "waiting for any device". ADB works fine and i use "adb reboot bootloader" command to enter fastboot mode.
I think that i have installed all drivers. I tried three different computers and usb 3.0 and 2.0... nothing. ADB works with every machine, fastboot doesn't.
What can i do? Is there any other way to get Device-ID? Need help. Stock ROM is awful
sorry for the wrong section, can you move this to Q&A
My phone has exatly the same issue...The key is the usb driver...With the stock LG drivers the fastboot did not work to me either.
1, uninstall any lg drivers from your os
2, install PdaNet universal usb drivers
3, enjoy!
When i finish with the fastboot, i installed back the LG drivers for the correct MTP communications, but it's not neccesary!
Give it a try, good luck!
Use Ubuntu Linux on USB Stick
no driver issues just works
Pixel XL (Verizon) Not Being Recognized via "ADB Devices" command on Windows 7.
So I got my 128gb pixel xl from Verizon today. It's still 7.1.0 (Build NDE63P) so I want to unlock the bootloader asap. I was able to get the phone booted up and mostly set up without taking the OTA update (I pulled sim card before booting the phone for the first time, and I skipped the wifi setup).
I intended to follow the instructions here to use dePixel8 to unlock the bootloader. I got USB debugging enabled on my phone, and ABD/Fastboot installed on my computer (Windows 7 laptop). The problem is the phone doesn't come up in the list when I use the "adb devices" command from the command prompt within the SDK folder. Looking at the device manager, it appears my laptop is automatically installing the "Google Nexus ADB Interface" driver for the phone, is this not the correct driver? I downloaded the USB drivers from here and tried pointing the Device Manager at them to force a driver update, but the device manager tells me the drivers are already up to date.
Can someone please explain to me how to get my computer (Windows 7) to recognize my phone via ADB so I can push dePixel8 and unlock the bootloader? I feel like I'm so close to being able to unlock the bootloader, but my phone not being recognized via ADB is driving me freaking crazy.
Thanks!
EDITED TO ADD: If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
TonikJDK said:
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Thanks for the prompt reply. I'm currently uninstalling Android Studio and SDK I downloaded, and will install the one you linked.
I think this is still a problem related to the driver Windows 7 is automatically installing for my phone. If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Replace adb by fastboot in fastboot mode
ex instead of
adb reboot
type
fastboot reboot
You've to use the fastboot command instead of adb. Please note that fastboot doesn't have all adb features, e.g. install, shell, etc
[email protected] said:
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
adb commands only work when phone is turned on and connected to pc using ADB.. it wont work n fastboot mode. In fastboot mode the command is fastboot.
example:
in adb-> adb devices
in fastboot-> fastboot devices