why does my computer only recognize my g1 in adb when it's in recovery mode? I can't push/pull any files through adb, when i'm not in recovery mode.
Is this because of the 1.6 firmware or does it have anything to do with the android-sdk>?
I tried uninstalling/reinstalling the drivers countless times.. any info would be appreciated.
DAKIDD236 said:
why does my computer only recognize my g1 in adb when it's in recovery mode? I can't push/pull any files through adb, when i'm not in recovery mode.
Is this because of the 1.6 firmware or does it have anything to do with the android-sdk>?
I tried uninstalling/reinstalling the drivers countless times.. any info would be appreciated.
Click to expand...
Click to collapse
Mine appears just fine in adb when the phone is on. I'm also on 1.6, CM 4.1.8.
You should see "USB debugging connected" when you plug in the USB, click it and make sure usb debugging is enabled. If it is, don't know what else to say. I'm on a mac, but that shouldn't make a difference.
Have you made sure you have check "USB debugging" in Settings>Applications>Development?
ill try that, thanks for the suggestion!
definitetly did work, thanks for the quick response AdamPI and AdrianK
Related
I have my phone plugged in and USB debugging selected but can't seem to get the Android Debug Bridge(adb) to see the device. Same thing when I boot into fastboot and run the command in terminal to check connected devices but it returns blank.
Any help and guidance would be much appreciated.
thanks
kind regards
tabutcher said:
I have my phone plugged in and USB debugging selected but can't seem to get the Android Debug Bridge(adb) to see the device. Same thing when I boot into fastboot and run the command in terminal to check connected devices but it returns blank.
Any help and guidance would be much appreciated.
thanks
kind regards
Click to expand...
Click to collapse
What rom are you running? Sense needs to have htc sync on pc installed for adb to work.
race55 said:
What rom are you running? Sense needs to have htc sync on pc installed for adb to work.
Click to expand...
Click to collapse
The phone is running on CyanogenMod
tabutcher said:
I have my phone plugged in and USB debugging selected but can't seem to get the Android Debug Bridge(adb) to see the device. Same thing when I boot into fastboot and run the command in terminal to check connected devices but it returns blank.
Any help and guidance would be much appreciated.
thanks
kind regards
Click to expand...
Click to collapse
Do you have USB driver for nexus one installed in your PC? It sounds like you don't have the driver installed.
taodan said:
Do you have USB driver for nexus one installed in your PC? It sounds like you don't have the driver installed.
Click to expand...
Click to collapse
Im using a macintosh computer and from what I've read, I don't think you need to install extra drivers.
I have a Samsung Galaxy Ace (S5830), a week ago when i woke up i released that it was not working. Before that i tried to change my imei, and i couldn't. But it worked after my fail at changing imei, than after a few hours it stopped working. When i try to power on, backlight turns on and off, sometimes it happens twice or thrice or till it's battery is over. Just turns on light and off. It goes on download mode, and ramdump mode. Recovery mode doesn't work. When i try to flash a rom via Odin, pc identifies my phone, odin starts but after Odin says "close serial port...", it tries to reboot but it cannot again, turns on and off the backlight again.
So, i think something is wrong with booting section, do you have an idea about this problem?
Thanks for reading.
Do you have all the USB drivers for the ace?
Does your Odin show the yellow box when you connect your phone?
If you can reach dl mode, you have a greater chance of unbricking! But I fear you will lose your imei and you wont be able to call..
Sent from my Ex-Hard bricked Galaxy Ace!
galaxyace152 said:
Do you have all the USB drivers for the ace?
Does your Odin show the yellow box when you connect your phone?
If you can reach dl mode, you have a greater chance of unbricking! But I fear you will lose your imei and you wont be able to call..
Sent from my Ex-Hard bricked Galaxy Ace!
Click to expand...
Click to collapse
Yes odin shows the yellow box, and i can reach dl mode. But as i said, via Odin or Power button when my ace tries to reboot, it just turns light on and off. I cannot do anything.
you tried adb for recovery? Connect phone in download mode and use adb to go to recovery mode.
Xr01d_GT said:
you tried adb for recovery? Connect phone in download mode and use adb to go to recovery mode.
Click to expand...
Click to collapse
i've never heard about it, i'm trying right now! Hope it works, thanks a lot.
edizkralll said:
i've never heard about it, i'm trying right now! Hope it works, thanks a lot.
Click to expand...
Click to collapse
sorry about flooding, but how can i use it to get to the recovery mode? can you explain it? Thanks.
edizkralll said:
sorry about flooding, but how can i use it to get to the recovery mode? can you explain it? Thanks.
Click to expand...
Click to collapse
When i try "cd c:\android-sdk\platform-tools" and "adb -d reboot recovery" i get an "device not found" error. I use win77x64, i have "Samsung USB Composite Device" under my device manager/usb devices list. I've installed google drivers via sdk manager but it doesn't seem on my device manager. what should i do ?
edit: as i understand, it is necessary to be checked "usb debugging mode" for my pc to see my phone as an adb device. my phone is closed and i cannot power it on, can i do this ? i think adb works for my problem, but i couldn't use it. it always says "device not found".
edizkralll said:
When i try "cd c:\android-sdk\platform-tools" and "adb -d reboot recovery" i get an "device not found" error. I use win77x64, i have "Samsung USB Composite Device" under my device manager/usb devices list. I've installed google drivers via sdk manager but it doesn't seem on my device manager. what should i do ?
edit: as i understand, it is necessary to be checked "usb debugging mode" for my pc to see my phone as an adb device. my phone is closed and i cannot power it on, can i do this ? i think adb works for my problem, but i couldn't use it. it always says "device not found".
Click to expand...
Click to collapse
OK..try these things..
Code:
adb start-server *to start adb*
adb get-state *it'll show whether device is connected or not*
adb reboot recovery *to go into recovery mode*
Correct Me if I'm wrong, but usually USB debugging is enabled by default I think.
BTW, when you plug in your device, does it light up or shows any activity?
I've installed google drivers via sdk manager but it doesn't seem on my device manager.
Click to expand...
Click to collapse
Google drivers as in? Samsung USB Composite Device should be there when You connect your phone, that's your phone drivers.
P.S:I'm attaching My ADB (I don't use the whole SDK) if you think you need them, copy them to any folder and open command prompt from there (shift+right-click combo),and run the adb daemon from there.
Xr01d_GT said:
OK..try these things..
Code:
adb start-server *to start adb*
adb get-state *it'll show whether device is connected or not*
adb reboot recovery *to go into recovery mode*
Correct Me if I'm wrong, but usually USB debugging is enabled by default I think.
BTW, when you plug in your device, does it light up or shows any activity?
Google drivers as in? Samsung USB Composite Device should be there when You connect your phone, that's your phone drivers.
P.S:I'm attaching My ADB (I don't use the whole SDK) if you think you need them, copy them to any folder and open command prompt from there (shift+right-click combo),and run the adb daemon from there.
Click to expand...
Click to collapse
When i connect my phone there seems "samsung usb composite device" it's ok.
when i write on cmd;
"cd c:\android-sdk\platform-tools\"
"adb start-server"
it says "daemon started succesfully"
and when i write "adb get-state"
it says "unknown".
i'm checking google now, hope find something about it. can you help me with it?do you have an idea?
edit: i've searched a lot on google, but i couldn't find anything. i think i must edit an adb_usb.ini file but i don't know what to do. my problem is adb doesn't see my phone, i don't know if it works after adb sees my phone but i want to try it. i cannot use my phone for 2 weeks and i'm really tired about it.
edizkralll said:
When i connect my phone there seems "samsung usb composite device" it's ok.
when i write on cmd;
"cd c:\android-sdk\platform-tools\"
"adb start-server"
it says "daemon started succesfully"
and when i write "adb get-state"
it says "unknown".
i'm checking google now, hope find something about it. can you help me with it?do you have an idea?
Click to expand...
Click to collapse
unknown it means your device is not detected..did you connect device to PC when in download mode??!
Xr01d_GT said:
unknown it means your device is not detected..did you connect device to PC when in download mode??!
Click to expand...
Click to collapse
Of course, yes.
Has anybody actually tried the adb reboot recovery? It doesn't work, you need to use the button combination.
Type 'adb devices' to see if your phone is recognized.
Sent from my GALAXY Ace.
tomb20 said:
Has anybody actually tried the adb reboot recovery? It doesn't work, you need to use the button combination.
Type 'adb devices' to see if your phone is recognized.
Sent from my GALAXY Ace.
Click to expand...
Click to collapse
Thanks for answer but i've already tried that command "adb devices", nothing listed.
tomb20 said:
Has anybody actually tried the adb reboot recovery? It doesn't work, you need to use the button combination.
Type 'adb devices' to see if your phone is recognized.
Sent from my GALAXY Ace.
Click to expand...
Click to collapse
Who said it doesn't work? I always use that, kind of never get the buttons combo
---------- Post added at 10:12 PM ---------- Previous post was at 09:59 PM ----------
edizkralll said:
Of course, yes.
Click to expand...
Click to collapse
OK. Then this is the last resort. Uninstall all the phone drivers and re-install them. Win 7 automatically downloads from the internet if the windows update is on.Then via adb try for recovery.
Xr01d_GT said:
Who said it doesn't work? I always use that, kind of never get the buttons combo
---------- Post added at 10:12 PM ---------- Previous post was at 09:59 PM ----------
OK. Then this is the last resort. Uninstall all the phone drivers and re-install them. Win 7 automatically downloads from the internet if the windows update is on.Then via adb try for recovery.
Click to expand...
Click to collapse
i tried it thrice, uninstalled everything and re-installed. tried on another pc, but it didn't see my phone again. should i change something in adb_usb.ini ?
any more ideas ?
I' ve purchased a "usb jig", but when i plugged it to my phone it started to turn light on and off action again. i'm really bored about it, what else can i do?
So I need help XDA fams. I am currently trying to update my N6 to 5.0.1. The issue i'm having is that my pc wont connect to my N6 while in bootloader. When in bootloader the usb seems to work fine, im assuming, since im getting "transfer mode: usb connected" on the very bottom of the phone screen. But when i adb and check to see if its connected, under "list of devices attached", nothing shows up.
When the N6 is booted up normally it works perfectly fine. I'm able to adb into my phone and it shows up under "list of devices attached".
Ive read around and know windows 8.1 and usb 3.0 drivers might be an issue. So I tried both usb google drivers and the universal naked drivers. I've uninstalled and reinstalled a crap load of times and nothing.
This thing is pissing me off. CAN ANYONE HELP OUT!
Adb is for Android. When you are in the boot loader, you use fastboot.
Try "fastboot devices"
El Daddy said:
Adb is for Android. When you are in the boot loader, you use fastboot.
Try "fastboot devices"
Click to expand...
Click to collapse
Wow lol. I feel stupid. Thanks man. Didnt know that.
But im still having an issue with it being recognized. I go into recovery mode and select the "apply update from adb". When trying to sideload the zip file i keep getting "error: device not found".
Any ideas?
jrforlife said:
Wow lol. I feel stupid. Thanks man. Didnt know that.
But im still having an issue with it being recognized. I go into recovery mode and select the "apply update from adb". When trying to sideload the zip file i keep getting "error: device not found".
Any ideas?
Click to expand...
Click to collapse
Check your device manager in Windows. Make sure it says "ADB Composite Interface" or something similar. If not, you'll have to install the drivers again.
Also, make sure you have the latest ADB package from the SDK.
I’m a noob when it comes to android adb but I'm an IT guy so what the hell I want 5.1.
I am following some directions on line on how to side load the OTA update seems easy, just a few commands and it should work. Here is what I'm doing and where I'm getting stuck any help?
Loaded Android SDK
Enabled Dev options, USB Debugging and OEM Unlock.
adb Devices - shows my device
adb reboot bootloader – restarts into the bootloader.
Select Recover Mode
Hold Power button, then press once the Volume Up button. To get Recovery Mode
This is where I get stuck, I'm reading I need to send the command “adb sideload <filename of update.zip>” but at this point ADB no longer sees my nexus 6? Nothing happens when I run this command and nothing is reported when I run ADB Devices?
Now I'm thinking drivers but I loaded the drivers? Can someone point me in the right direction?
I'm trying on a Windows 8 PC
Also when I'm looking at the device manager everything shows up fine until i enter the recover. At this point nothing shows up in device manager and when i resead the USB cable nothing happens no sound like im disconnecting something and reconnecting it, not device manager refresh, weird.
update! got it working.
So it turns out the device manager dose not show anything until you get into adb sideload options then the wrong driver is loaded and i had to manual pick Android adb driver. once i did this i was able to side load the ota update and now on 5.1.
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
tom1226 said:
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
Click to expand...
Click to collapse
Thanks you are right you have to be in the adb sideload options for the phone to show up in device manager and at this point it was not seeing the right driver, once i picked android adb driver i was able to update Thanks!
Awesome, glad it worked out for you!
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?
I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse
Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!