C:\Documents and Settings\SilenT>cd c:\android\tools
C:\android\tools>adb usb
error: device not found
C:\android\tools>adb devices
List of devices attached
debugg mode on/off ...same problem
and my recovery img dosent work when i enter the recovery mode Exclamation Point with android guy
os: win xpsp3 ... drivers unninstaled\instaled from everywhere ~X( still no luck sombody pls hlp !!
I am not sure yet on all your errors, but you do have debugging enabled on your phone?
---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------
no need for two threads
You really need to give a bit more info. It looks like your PC isn't seeing your phone. This could be due to a number of reasons, including wrong driver, bad usb cable, phone not set up correctly (adbd not started), etc...
What exactly have you done? From what you've posted I've no idea if you phone is even hooked up with a cable...
OP, go into Device Manager on your PC with your N1 plugged into USB. Is there a yellow warning triangle with an exclamation point next to the entry for ADB Device/Nexus one?
On Windows 7 i've always had to install N1 drivers manually from a package i found here:
http://forum.xda-developers.com/showthread.php?t=613217
Related
Hello,
before you delete this post as duplicate let me say it is not the case.
I have a problem that I can't debug from eclipse my Samsung galaxy s+.
First of all I must say that under windows I have installed latest kies with drivers for I9001 and device is visible on windows (in devices) in both mode kies or mass storage.
After I installed all explained in "Android Development Tutorial" my device couldn't be found in eclipse.
Than I searched for similar posts and tried all explained in post "[Q] Problem with usb debugging mode miui.us in eclipse".
Again no positive result.
Than I connected Samsung galaxy s I9000 from my friend and his device was found without problem.
Than again I tried to find mine but again without any progress.
I also tried with another device from another friend which also have I9001 and his device also can't be found.
I'm using windows XP and latest drivers and eclipse as explained in your "Android Development Tutorial".
I still think that something with drivers for eclipse is problematic. Can you please help?
Thanks!
Kind regards,
Beco_os
What about the normal adb command line interface?
What happens when you use "adb kill-server" and then try a "adb shell"?
If the above commands do not work: if you use windows OS, what is displayed in device manager while the phone is connected in USB debug mode?
wintel_mac said:
What about the normal adb command line interface?
What happens when you use "adb kill-server" and then try a "adb shell"?
If the above commands do not work: if you use windows OS, what is displayed in device manager while the phone is connected in USB debug mode?
Click to expand...
Click to collapse
Hello,
I tried in both usb modes on Galaxy S+.
1) Mode when Galaxy S+ was in mass storage mode:
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb kill-server
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
On Windows in devices I found 2 mass storage:
*Disk drives
- SAMSUNG GT-I9001 Card USB device
- SAMSUNG GT-I9001 Card USB device
2) Mode when Galaxy S+ was in Kies mode:
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb kill-server
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
On Windows in devices I found:
*Modems
- SAMSUNG Android USB Modem
*Universal Serial Bus Controllers
- SAMSUNG Android USB Composite Device
So it seems that still adb drivers doesn't work for GT-I9001.
Kind regards,
Berislav
And USB Debugging is enabled on the phone? Settings - Applications Development - USB Debugging
It works fine for me on both XXKPS and XXKPU.
Hi,
thanks for support, but it seems I'm special case
I have 2.3.6 XXKPH version, maybe that can be the cause of problem.
I'm left without idea. I tried reinstallation of all drivers on my PS but nothing is working.
Never the less my friend have galaxy s plus with firmware 2.3.5 XXKPG (this is originally installed on phone when you buy it in Croatia) and have same problem.
Is it possible that someone who don't have problem test this versions of firmware for debugging?
KR,
Berislav
I red somewhere that low powered USB could cause this on i9001, so I bought powered USB Hub and issue is still there. Tried it on Mac OS/X 10.6.8 and no way, Ubuntu 10.10 and no way. I tried XXKPH and XXKPI, editting ~/.android/adb_usb.ini and added Samsung Vendor and/or device id without any approach.
Galaxy S II and Galaxy S are detected properly on these computers.
Bad news
Plysovej_Kaktus said:
I red somewhere that low powered USB could cause this on i9001, so I bought powered USB Hub and issue is still there. Tried it on Mac OS/X 10.6.8 and no way, Ubuntu 10.10 and no way. I tried XXKPH and XXKPI, editting ~/.android/adb_usb.ini and added Samsung Vendor and/or device id without any approach.
Galaxy S II and Galaxy S are detected properly on these computers.
Click to expand...
Click to collapse
I have some bad news about this. I tried another gt-i9001 and it was perfectly detected without doing anything special ( XXKPH ). Visually, this device differs from non working model by missing caption "with Google TM" on the backside and added sticker "DIGITAL BY QUALCOMM" on the top side between jack connector and usb connector. Below battery, both has same information:
MODEL: GT-I9001
SSN: -I9001GSMH
RATED: 3.7 V; 1000 mA
FCC ID: A3LGTI9001
MADE BY SAMSUNG
Non working device has note R176 on sdcard slot, properly working one has G140 there.
... so it seems, we are ****ed. This is something hardware-based.
Same problem here
Hello,
before you delete this post as duplicate let me say it is not the case.
I have a problem that I can't debug from eclipse my Samsung galaxy s+.
First of all I must say that under windows I have installed latest kies with drivers for I9001 and device is visible on windows (in devices) in both mode kies or mass storage.
After I installed all explained in "Android Development Tutorial" my device couldn't be found in eclipse.
Than I searched for similar posts and tried all explained in post "[Q] Problem with usb debugging mode miui.us in eclipse".
Again no positive result.
Than I connected Samsung galaxy s I9000 from my friend and his device was found without problem.
Than again I tried to find mine but again without any progress.
I also tried with another device from another friend which also have I9001 and his device also can't be found.
I'm using windows XP and latest drivers and eclipse as explained in your "Android Development Tutorial".
I still think that something with drivers for eclipse is problematic. Can you please help?
Thanks!
Kind regards,
Beco_os
Hello, I have a same problem, I ve opened back case and the number on sd card slot reads 512S. Could this really be the hardware issue?
I ve bought my phone in Serbia.
BR
Dragan
Hello
I have similar problem but I found that my computer see ”Samsung Android Composite ADB Interface” in device manager when phone is power off. So command ”adb devices” finds my device. But when I power my phone on, at the moment when Samsung logo is shown, my device manager detects change of hardware reloads and ADB interface is missing. It is the same behavior on other computers with Win 7 x64 and Ubuntu 32bit.
At Windows I tried both Google drivers from SDK and Samsung KIES which detects ADB as I wrote. By the way KIES normally detects my phone when the device is on. I have USB Debugging mode enabled, but it seems it doesn't work. I have i9001 European distribution and I'm using stock rom I9001XXKPK, before I was using I9001XXKI2 but the problem was the same.
Have you got any ideas what to do? Where is the problem? Is there any command to force enable USB debugging through ADB?
Thanks for advices.
My pc windows 7 installed google nexus adb interface once i plugged in my nexus 6 but dosent show up in devices with removable storage or pop up open file once plugged in. I checked in the device and printer area and see the nexus 6 under unspecified section. Im stuck please help me figure this out
MrJesseJay said:
My pc windows 7 installed google nexus adb interface once i plugged in my nexus 6 but dosent show up in devices with removable storage or pop up open file once plugged in. I checked in the device and printer area and see the nexus 6 under unspecified section. Im stuck please help me figure this out
Click to expand...
Click to collapse
I had no issues and used the latest Google USB drivers which aren't hard to find.
You could also try using Wug's Toolkit I believe it will also install all the necessary divers for everything to work 100%
turn off USB Debugging.
Uninstall the Drivers through Device Manager.
Unplug and then plug back in.
It should install the Nexus 6 drivers.
Did all these methods still no good. Does with my PC have to connected to the internet or something?
MrJesseJay said:
Did all these methods still no good. Does with my PC have to connected to the internet or something?
Click to expand...
Click to collapse
my computer and drivers just dont mix. i used most everything in this link to flash the drivers and more, flawless
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Switch the USB connection from MTP to camera. Then drop anything you wanna drop from your computer in the " picture " folder that your PC picks up from the phone. Then with a file explorer move your contents to wherever you wanna move them in your phone
---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------
It's a workaround
So thanks to the awful instructions on how to root the phone (https://forum.xda-developers.com/le-2/how-to/guide-unlocking-rooting-restoring-to-t3515555) my phone seems to be bricked now
I managed to get TWRP flashed. I format'ed Data, did a backup, and thats where it went wrong.
The instructions say to go to Mount > Enable MTP
There was no " Enable MTP" button. Just a "Disable MTP" button. I tapped it and it turned into "Enable MTP", I tapped that again. Nothing seemed to happen.
Since I couldn't do anything, I rebooted the phone with TWRP, and now it just sits at the "LeEco" screen forever.
when I plug the phone into the PC, ADB see's it but it is showing up as "unauthorized" and I cannot reboot into the bootloader. Google tells me I need to recheck the USC debugging option on the device, but apparently my device no longer can boot to the OS so I cannot check that option.
I can hold down Vol + and Power and get into the EUI Recovery, which says I can flash an update.zip or erase data. But when I do this, ADB doesn't see it at all, and Windows doesn't see it to put any files on it.
I've tried several drivers, none seem to make any difference. And as a side note, given that there are zillions of drivers out there, and having the exact correct ones seems pretty important, why in the world do these rooting guides not link to the correct one?
Any advice, or is it time to box it up and ship it back?
Is it boot in recovery
I can boot into recovery but it's the le Eco recovery. The directions killed the phone before TWRP was flashed.
So at this point I have the phone stuck at the Le Eco boot up screen.
I have the ADB driver installed, and adb devices shows the device, but it says "unauthorized".
there are 3 "Android Device" entries in my Device Manager with yellow exclamation points next to them. I have no idea which driver it is looking for. When I manually browse to the drivers, I get 3 options, "ADB interface, Bootloader interface, or Composite ADB interface"
I am unable to reboot into recovery via adb because the device is unauthorized
1. download the rom from this ppst:
https://forum.xda-developers.com/le-2/how-to/leeco-le-2-x520-stock-firmware-t3657689
2. Then unzip the rom and open the folder, make sure there are no spaces in the folder name and its parent folders.
3. Then youll find a file named multi-brush, with the extension '. Bat' change the extension to '.bat' i.e. remove the space.
4. Then power on the mobile while pressing vol-down and power button, to enter fastboot mode and connect it yo the PC.
5. Then double click this multi brush file and wait for it to finish.
Important, this will wipe all your data!!
It worked for me,simple and error free,only for snapdragon le2
---------- Post added at 01:18 AM ---------- Previous post was at 01:18 AM ----------
https://forum.xda-developers.com/le-2/how-to/repair-hard-bricked-phone-x52x-sd-t3648348
I had that problem with the enable mtp step. Turns out it's a driver issue. This is a rough guide as my pc isn't with me right now so i may have misremembered a step or two.
During that step with your phone connected,
Goto device manger
> android devices
> right click the driver there
> click update driver
> manual update
> "let me pick"
> you'll see some drivers listed, pick one that has either MTP or usb composite device in it's name.
> install it
> your phone should now show up as a storage device
> if not, on your phone disable then enable mtp.
If your phone doesn't show up on your system unplug and replug your phone, re enable MTP.
If it still doesn't work, repeat above steps and pick a different driver.
On another note, I'm pretty sure that you were supposed to authorize your system for usb debugging before starting the rooting process, which is why the steps in that post say you should boot into recovery through adb i.e to ensure your system is authorized.
---------- Post added at 11:35 PM ---------- Previous post was at 11:28 PM ----------
I should probably post this on the rooting thread as well… but I prolly won't, I excel at procrastinating.
Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5
raver445 said:
Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5
Click to expand...
Click to collapse
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Yes usb debug mode is on...
Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
I have even tried updating the drivers and it keeps saying it can't update it even if I use the manual update settings
Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
How can I get the drivers installed then? It's driving me crazy.
raver445 said:
How can I get the drivers installed then? It's driving me crazy.
Click to expand...
Click to collapse
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.
Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.
th3cavalry said:
Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.
Click to expand...
Click to collapse
I have just rebooted my computer I'll see how it works in just a moment but I don't know if it's going to see it or not. it is still not seeing it.
Gamesoul Master said:
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.
Click to expand...
Click to collapse
So what can I do to fix this? It's driving me insane.
raver445 said:
So what can I do to fix this? It's driving me insane.
Click to expand...
Click to collapse
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
After I update it the software drivers for the computer it says Razer phone 2 but it doesn't work right. I tried doing one of those scripts to reflash to stock software and it doesn't do Jack squat it sits there waiting for device.
use samsungs usb driver installer and change adb driver to Samsung's version in device manager. should see fastboot device now .
celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
i got it to work for the fastboot devices ...but still unable to relock it
has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period
ghost9640 said:
has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period
Click to expand...
Click to collapse
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well ?
https://forum.xda-developers.com/and...ndows-t3999445
got it
JDBarlow said:
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well
https://forum.xda-developers.com/and...ndows-t3999445
Click to expand...
Click to collapse
my laptop was not seeing the device my pc is, now im trying to flash arter97 kinda stuck but thx bud
The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved
decode2533 said:
The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved
Click to expand...
Click to collapse
Lol okay..that's about as random as "hey anybody reading this thinking about getting an S20 Ultra or one of the others"
I am....
I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.
Hi All,
Thought I would post this on here for you all, might help someone else like it did me.
What ImperialMe said is correct and I was able to do both my Razor 1 and 2 using it.
imperialme said:
I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.
Click to expand...
Click to collapse
The easy method is to download the Ubuntu Image for Windows (ubuntu.com/download/desktop)
Once you have it, burn it to USB using Rufus (rufus.ie)
Boot into the USB on your PC and when prompted just run as is, no need to install.
Once running, open a terminal window and with internet access and run the following:
Code:
sudo add-apt-repository universe && sudo apt-get update
Now run:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
When promoted press Y and enter
Now run:
Code:
sudo adb start-server
Connect your phone, turned on and on the home screen for example. Run the following
Code:
sudo adb devices
You should see your device listed as unauthorised and get a prompt for ADB access on the mobile phone.
run it again to confirm its authorised and then enter:
Code:
adb reboot bootloader
Once rebooted, use the menu to select boot into fastboot on the phone
Now back to the terminal window, enter:
Code:
Fastboot devices
You should now see your device listed and commands should work as expected.
If you need to copy anything over to the temporary USB OS then use another USB drive and copy them to it before you boot the OS.
I tried this in a VM and VMWare and HyperV both failed as the drivers they use are still Windows based and failed. Only a full OS worked.
Hope this helps someone else!
Hello Everyone.
My ROG Phone II (WW_16.0631.1910.44.0) is not showing up in ADB (Terminal and Powershell) It only shows 'List of devices attached' but shows no actual device.
I also have a Xiaomi 4x (Santoni) which my computer is able to detect in CMD.
Troubleshooting done:
Ensured that my 'USB Debugging' is 'On'.
Tried selecting each option one by one: PTP, MIDI, No data transfer, etc, while also keeping my display on.
Platform-tools I have downloaded is r29.0.5.
I have a Windows 7, and when I connect my ROG II it said that it installed the drivers successfully. Restarted my computer & phone numerous times.
Please help.
Platinum_Pyth0n said:
Hello Everyone.
My ROG Phone II (WW_16.0631.1910.44.0) is not showing up in ADB (Terminal and Powershell) It only shows 'List of devices attached' but shows no actual device.
I also have a Xiaomi 4x (Santoni) which my computer is able to detect in CMD.
Troubleshooting done:
Ensured that my 'USB Debugging' is 'On'.
Tried selecting each option one by one: PTP, MIDI, No data transfer, etc, while also keeping my display on.
Platform-tools I have downloaded is r29.0.5.
I have a Windows 7, and when I connect my ROG II it said that it installed the drivers successfully. Restarted my computer & phone numerous times.
Please help.
Click to expand...
Click to collapse
I think you are missing Asus drivers. Install these drivers as I encountered same problem and in device manager I found out that drivers were missing.
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
Drivers are given in Guides section under thread "Latest guide to covert......1910.35" on page 7.
zohaibshafijutt said:
I think you are missing Asus drivers. Install these drivers as I encountered same problem and in device manager I found out that drivers were missing.
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
Drivers are given in Guides section under thread "Latest guide to covert......1910.35" on page 7.
Click to expand...
Click to collapse
Thank you very much! Couldn't find the drivers anywhere.