Nook Froyo - ADB Broken - Nook Color General

Upgraded to the latest Nook Froyo image via CWR and ADB doesn't work over USB or Wireless while in Froyo. ADB over USB works fine in CWR. The ADB Wifi widget will run, but the computer cannot connect. The drivers are all set up and worked pre-Froyo.
I searched an hour ago, and found nothing else on this. Also, search is now down, so forgive me if this has been solved.
Anyone else suffering from the same? Solutions?

Mine was working for a couple minutes then broke. I reboot and went into the USB development setting and toggled the setting one more time. It started working from then on.
Sent from my PC36100 using XDA App

I had the same problem, and it is working now after toggling the usb development setting several times after a reboot. I think it took half a dozen tries or so before it started working.

Related

ADB broken after Froyo OTA?

Just wondering if anyone else is having this issue.
After waiting for the VF 2.2 OTA update, it finally arrived yesterday morning. Great. Except now ADB doesn't detect the phone.
Plugging it in, putting it in debug mode etc and going trying ADB devices shows an empty list. Putting the phone in recovery and trying fastboot devices shows it with no problems.
If I plug in my HTC Magic (on 2.1-update1) and my Nexus One, adb shows only the Magic in the device list. ddms also doesn't detect the N1 but does detect the Magic without any problems.
I've tried reinstalling the driver, reinstalling the whole SDK, installing all updates, doing a factory reset on the device and everything else I can think of. Nothing seems to fix this issue. It's been logged in the android bug tracker, but not many people seem to be having the issue. The bug is here: http ://code.google.com/p/android/issues/detail?id=9437 (sorry had to break it up because I'm not allowed to post links yet)
I'm not sure if this has anything to do with Windows 7, but from searching it seems there have been other issues with W7 and the N1 when using adb.
What I just don't get is that it's only affecting a few people. What could be so different about my N1 that's causing this and not causing it for almost everyone else? It makes no sense to me.
Having the same issue. I put an issue in http: //forum.xda-developers.com/showpost.php?p=7636799&postcount=129.
Tried ADB with a HTC Legend. No problem. But on my Nexus ONE the ADB don't announce itself on the USB bus.
Just to make sure; USB Debugging is enabled in the phone, right?
Yepp. USB debugging is on.
Sent from my Nexus One using XDA App

[Q] Help : Advice or Instructions Needed Bad : USB Port Dead

I got up this morning and decided to sync some music over to my captivate. I was surprised when I started getting errors that the device was not recognized. After four hours of trying to get the phone to sync I put it back to as vanilla as I could and brought it to ATT. After trying a new cable and just about everything else the phone has been declared to be defective. My problem is how do I get this phone back to original without a usb connection. The phone is not recognized by Odin, ADB or anything else so as far as my knowledge goes I am out of ideas. The phone works fine other wise but I thought some of the brightest on here might be able to help. Any ideas guys?
Try a different USB port.
Mine only works in the back USB ports, but won't do **** in the front ones.
I probably should have been a little more clear. The port is defective on the phone. They can't even communicate with the phone at the AT&T store through the usb port with some reader. I am trying to get the phone back to resembling stock before i send it back for warranty.
Sent from my SAMSUNG-SGH-I897 using XDA App
Try downloading adbwireless from the market. It will allow you to use adb without a wired connection.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have Windows 7 64x bit, and sometimes my connections seem dead, and I just uninstall and reinstall the drivers.
ADB wireless seems like your best bet right now
Thanks. Gave that a shot and I can connect to the phone. Now all I need to do is find the att apps.
try a factory reset and see if it recognizes your phone .
rsohne said:
I got up this morning and decided to sync some music over to my captivate. I was surprised when I started getting errors that the device was not recognized. After four hours of trying to get the phone to sync I put it back to as vanilla as I could and brought it to ATT. After trying a new cable and just about everything else the phone has been declared to be defective. My problem is how do I get this phone back to original without a usb connection. The phone is not recognized by Odin, ADB or anything else so as far as my knowledge goes I am out of ideas. The phone works fine other wise but I thought some of the brightest on here might be able to help. Any ideas guys?
Click to expand...
Click to collapse
Have you tried it on another computer?

ADB issue with captivate

Hello all I have been using a captivate for some of my dev work and all was going well but just today I can no longer see it in my devices using ddms or adb devices.
Looks like adbd is running on the phone and I can mount the sd card fine. I tried in two machines, one mac and one windows... So its something in the phone and a factory reset didn't fix it - any tips on how I should go about troubleshooting this?
It was working fine so I am a bit miffed.
Thanks so much
Jit
--
Sent from my SAMSUNG-SGH-I897 using XDA App
Still not working with a mac
All:
Just an update to the issue - the Captivate still refuses to be recognized by ADB, although it works fine on the same machine when I boot into Windows and use Samsung Kies.
On the Mac side, I can mount the files when USB debugging is on by going to the USB status icon and selecting Mount storage. The Mac even recognizes the connection as a new network connection (although I simply ignore that part). So looks like the USB subsystem on my Mac is somehow not recognizing the ADB communication. I upgraded to android release 8 and still the same problem.
Is there a way to completely reset the USB subsystem on a Mac without having to reinstall the OS?
Thanks so much - the weird thing is that the captivate worked okay for a week or so before deciding not to work with adb any more - I can still generate apks and sideload the apks into the device but I would really like to be able to do some on-device debugging.
Thanks so much for any help that you guys can give.
Jit
Edit: Nevermind
SOLVED - ADB Issue with Captivate
All:
After quite a bit of research finally figured out why ADB will not recognize the captivate (or for that matter any other android device). The problem was because I had installed EasyTether. Its a pretty nice software and pretty easy to use to tether android devices, unfortunately it kills adb's usb capabilities.
I found this issue in EasyTether's FAQ area so if anybody else is having the same problem you will need to unload the EasyTether Kernel Extension (unfortunately that didn't totally fix the problem for me - I kept losing communication intermittently so I ultimately removed Easytether from my mac as well as from the Captivate and now I can see the device in adb again).
Just thought I would share the solution with the rest of the very helpful community.
Jit

[Q] "Device not recognized" "Drivers were not installed successfully"

[Q] "Device not recognized" "Drivers were not installed successfully"
Well, crap. I don't know what else to try here.
I plug in my phone to update to 2.2 and in all 4 of my USB ports I get a "usb device not recognized" error. I've tried uninstalling/reinstalling the root hubs, nothing. I want to try to uninstall the drivers specifically for the phone, but can't find them (running windows 7 32 bit)
What the heck man?
So far ive done:
Uninstalled the samsung captivate drivers.
Uninstalled the USB root hubs.
Uninstalled Kies Mini.
Reinstalled captivate drivers.
Reinstalled USB Root Hubs.
Reinstalled Kies Mini.
Turned on debugging before plugging it in.
Turned off debugging before plugging it in.
Changed to mass storage mode.
Changed to Media Played mode.
Changed to Kies mode.
FACTORY RESET THE PHONE.
I think that about covers it. The next step I will try is to get a new usb to micro usb cord. Then, if not that, i am going to a friends house.
I shouldn't have to go through all of this crap. Especially when it was recognized about a week ago. nothing has been changed, deleted or updated since then either.
Quite frustrating.
Anyone have any ideas? I am close to just re-installing windows and then trying...ugh i just want my update! Been waiting months and months and now I can't even get it -___-
I received an error message about an idle screen, could NOT figure it out. Finally it worked after uninstalling launcher pro! Are you using a custom launcher? Try uninstalling!
WiredPirate said:
I received an error message about an idle screen, could NOT figure it out. Finally it worked after uninstalling launcher pro! Are you using a custom launcher? Try uninstalling!
Click to expand...
Click to collapse
No. I apologize I should have mentioned that.
It is not rooted and there is no custom software. Everything I've got, I've downloaded from the android marketplace.
just had the same problem...tried every possible solution..including installing fresh copy of windows..got my phone replaced..afraid to say..hardware issue
Sent from my SAMSUNG-SGH-I897 using XDA App
mariuszdziedzic said:
just had the same problem...tried every possible solution..including installing fresh copy of windows..got my phone replaced..afraid to say..hardware issue
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
So you're saying a new phone fixed it? Well I hope that's not my only option because I don't want to go through all of that.
:/
tried getting it to work for two days and i gave up. my carrier didnt give me any trouble and sent me a replacement..hope its not ur case. tell me what you tried so far?
This sucks man. Stil nothing....I am not going to replace my handset because I bought mine online! It's worked before....so what changed???
I'm giving this one last shot.
Anyone have any ideas other than replacing my entire handset??
Make sure your using the factory cable that came with your phone and unmount your external sd card.
Sent from my SAMSUNG-SGH-I896
shust82 said:
Make sure your using the factory cable that came with your phone and unmount your external sd card.
Sent from my SAMSUNG-SGH-I896
Click to expand...
Click to collapse
Yep, I am definitely using the factory cable, and I don't even have an external SD card in there right now (I tried it with and without one in and still nothing)
UPDATE:
I went to a friends house and tried to plug it in on his netbook...same exact issues, then his desktop computer...same exact issues.
So does this mean i am royally screwed and the only way I can ever connect my phone to a computer again is to get a new one? I can't even transfer files to and from the phone, so all of the music that I put on there before is completely useless now
EDIT!!!
I just totally realized something...I used to be able to use it via usb to transfer music, files, etc until I plugged it into my USB port on my kenwood car stereo's usb deck. It had given me error 19, which apparently is a connectivity error. Could these be related? Could it be possible that somehow plugging it into my stereo boned the usb functionality?
So I am not sure what the heck I did right, but it suddenly started working, and I am about 90% done with the 2.2 update.
I DID however unmount the internal SD card, then I re-mounted it and I guess that worked? Somehow there must have been a random glitch with the internal.
Anyways, if anyone else has this issue, try that!
Its a glitch in the media scanner program. Unmount your external (you can't unmount the internal), pull the card out, re install. We found this when doing the rodgers update, lot of people had this problem.
Sent from my SAMSUNG-SGH-I896
I had some issues with the drivers originally. I downloaded the wrong ones from the Samsung site. Take a look for the drivers in myriad XDA threads and see if those work, after uninstalling the ones you have loaded.
Raichu206 said:
So I am not sure what the heck I did right, but it suddenly started working, and I am about 90% done with the 2.2 update.
I DID however unmount the internal SD card, then I re-mounted it and I guess that worked? Somehow there must have been a random glitch with the internal.
Anyways, if anyone else has this issue, try that!
Click to expand...
Click to collapse
how did you unmount the internal

[Q] USB connection not recognized

Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
I have the same problem and I still don't understand if it is hardware or software related.
In my case the usb sometimes stop working for a certain time, sometime a couple of hour, some time for a full day. After that magically start to work again.
I've tried every in my knowledge but without success.
You are not alone
Air_Mike said:
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
Click to expand...
Click to collapse
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Happened to me as well. In one day i can't connect my phone to the pc but after two weeks when i connected the o2x to a pc with vista the problem was vanished. I connected to my usual pc and the same it worked. let's hope that i will not have anymore this problem. It is possibility that your phone will revive i one day. good luck.
I think I may have solved this particular mystery, I'm now able to reproduce it at will, and get usb/adb functionality back.
It happens through a combination of ADB crashes/bugs on a computer and a usb-stack crash/error on the phone.
I can reproduce it by plugging in another phone/tablet on the computer (while still having the phone connected), installing/running something from eclipse on the other device, unplug and replug the o2x and then try to run/install something on it via ADB. This invariably leads to the ADB-icon (the status-bar bug-icon) disappearing, *and* it will lead to the phones USB not working on another computer, or even another port on the same computer.
Funny thing is, if I reboot the phone, and plug it back on the same computer, this instantly leads to the same behaviour. USB will only get recognized on the same port it was plugged in the last time, and ADB will still not get activated. Trying to connect to another computer *after* this will not work.
The solution is simply to reboot *both* the phone *and* the computer (or just kill adb I guess) before plugging in anything.
Plugging in the phone while *either* the PC *or* the phone is in this confused state will lead to both devices malfunctioning in the same way as before, which is why you cannot simply connect the phone to another PC. (Although unplugging the phone, rebooting it *before* plugging in to another computer should work.)
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Air_Mike said:
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Click to expand...
Click to collapse
Hm, okay, your problem may be of a different kind. I'm not entirely convinced yet, as you don't mention having rebooted any computer. So just to satisify my curiosity, do exactly these steps in the following order:
1) Unplug the phone from the computer.
2) Power down the computer
3) Power off the phone
4) Turn on your computer
5) Re-install the LG USB drivers
6) Turn on your phone
7) Connect the phone
If this doesn't work then you indeed have a completely different problem, and we're back to speculating.
TrymHansen said:
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Click to expand...
Click to collapse
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems? I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
mparack said:
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems?
Click to expand...
Click to collapse
That's exactly what it means, yes. It's never been a hardware problem (luckily)
I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
Click to expand...
Click to collapse
You may of course have had a genuine hardware fault, after all usb-sockets are among the first things to break on any phone. I thought my phone was a goner as well, until I discovered the things mentioned in my post. It's a really sneaky affair, it would be impossible not to assume the phone is broken the first time you experience it.
EDIT: Removed invalid assumption.
Just to report that I've tried everything, including connecting phone to computer on which my friend runs Nexus S with no problem and then connecting to computer on which my phone was never connected.
Is there easy way to revert to v10d (last version I know my usb connection worked)?
I don't want to experiment too much because this is my business phone.
Maybe I'll just wait for GB and V20e (I hope it will finally be released soon) and hope that this will resolve my problem, but until them I'm missing one of main functionality
What a waist, since I get the phone with all that fuzz about it, is nothing but problem after another: rebooting, battery drain, wifi problem, usb connection... whats next?
Air_Mike said:
Is there easy way to revert to v10d (last version I know my usb connection worked)?
Click to expand...
Click to collapse
Assuming your usb isn't actually broken, yes, it's pretty easy. Download 10D from here: http://forum.xda-developers.com/showthread.php?t=1035041
Instructions here: http://forum.xda-developers.com/showthread.php?t=1008070
NOTE: The instructions are for flashing baseband only. In addition to that, you also need to select the .bin file in "Ap bin"
Thanks, but links are broken.
Air_Mike said:
Thanks, but links are broken.
Click to expand...
Click to collapse
Indeed they are, were copied from another post I made, and XDA had truncated them.
1st one: http://forum.xda-developers.com/showthread.php?t=1035041
2nd one: http://forum.xda-developers.com/showthread.php?t=1008070 (this link is also at the bottom of the first post of the first link.)
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Air_Mike said:
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Click to expand...
Click to collapse
Weird. Glad you got it working.
Looking around on different LG Forums, as useless as they are, the support-people always gives the advice that you should take out the battery, and leave it out for five minues to "clear residual memory." (This, apparently, is the solution for any kind of problem with the phone ;-)) That's always sounded completely nuts to me, but that's the advice I'm going to give the next guy with usb problems ;-)
And another one bytes the dust.
That's ultra weird. one minute everything is just fine and on the other, USB is dead.
So, apart from the procedure TrymHansen gave us a few post back, there is no known solution/diagnose/whatever for this problem, right?
SmartFlash will not detect phone...
My post from other thread which was closed:
My optimus 2x is not detected when I plug it to my laptop via USB.
Turn on mass storage" in the phone does not appear, it's like I'm just plugging in into a wall charger.
It could connect just a few days before, same laptop, same drivers (LG mobile united drivers)
Have tried it with 3 different laptops, still can't connect (drivers are installed)
A google search reveals other people having the problem as well and unable to solve it.
Can't return it yet for warranty because superuser app is still there.
Originally, I rooted it using superoneclick. Can't unroot it in superoneclick since not detected in USB.
So i unrooted it using z4root (without a pc). It's now unrooted, however superuser app is still in the app drawer.
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
fmartinezjr said:
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
Click to expand...
Click to collapse
Yes it will.
So did you try to flash a stock rom and did solved your usb problem ?
I will try with a modaco rom next we.
lol, is this fixed or not?
ive had the same problem.. when my rom is totally chrashed, and usb is like stuck?
strange is, all the other usb devices (wifi dongle, not keybord mouse) stops working when i plug in my phone? also the phone does not see that there is an data cable in him so i cant mount my storage?
is this an warranty issue?

Categories

Resources