ADB Devices - Offline - Motorola Droid 3

I'm all Googled out, searched this forum looking for a solution.
Here's the back story :
Phone : Bell Canada XT860 4G, bought on release day with 2.3.4
1) When I got the phone, there was no rooting process available
2) PSouza came up with one, successfully rooted on the first time I tried it
3) Installed Bootstrap, made some backups
4) A few months later, 2.3.6 was released and installed it via update.zip file, not OTA
5) Trying to root this release since I first got the update, but have been unable to do so.
6) Tried 6 different PC, running anything between Windows XP and 7.
So, everytime is try to root my phone, I try the ADB DEVICES command, and always find my device to be offline. Tried a few times to unplug, toggle USB debugging, plug the phone again, run the command, still offline. As I said previously, tried that one 6 different PCs, always yields the same results. Also tried all the USB ports on each PCs, as well as 3 different USB cables (2 from Moto, 1 from a Blackberry).
Also, for the ADB drivers to install the first time I plug in the device to a new PC, I have to put the phone in "Motorola Phone Portal" mode. "Charge Only/None" only installs disk drives drivers.
So here I am, still trying to root this phone since I installed the update. What bothers me is that it worked so flawlessly the first time I tried, but since the update, it almost looks like ADB isn't running on the device itself.
Do guys have any other idea ?
I'm using USB drivers from Motorola 5.2.0.
Do you know if there is a command I can run in Terminal Emulator that can force the ADB service or whatever you may call it on the device ?

Related

[Q] USB Not Recognised

Hello guys,
To cut a long story short, my cousin wants me to hack is Samsung Galaxy GT i9000.
I rooted his phone in August and it was working perfectly (I play around with my Desire quite a lot) and since then he's tried to get rid of the root to update to official Froyo and something has happened to the USB.
I have tried to install every driver known to man kind to get this phone recognised by 3 laptops and a Desktop PC. 1 XP, 1 Vista and 2 Windows 7. I have been using USB Debug Mode, I've tried it without Debug mode, I've tried every USB slot, I've uninstalled and reinstalled the drivers, kies, even deleted the phone from Device Manager and retried that... and nothing has happened. I can also get in to Download mode but unfortunately the computer still doesn't recognise the USB so therefore I cannot use Odin to flash the phone.
Any help? Cheers
Dan
bigdan35 said:
Hello guys,
To cut a long story short, my cousin wants me to hack is Samsung Galaxy GT i9000.
I rooted his phone in August and it was working perfectly (I play around with my Desire quite a lot) and since then he's tried to get rid of the root to update to official Froyo and something has happened to the USB.
I have tried to install every driver known to man kind to get this phone recognised by 3 laptops and a Desktop PC. 1 XP, 1 Vista and 2 Windows 7. I have been using USB Debug Mode, I've tried it without Debug mode, I've tried every USB slot, I've uninstalled and reinstalled the drivers, kies, even deleted the phone from Device Manager and retried that... and nothing has happened. I can also get in to Download mode but unfortunately the computer still doesn't recognise the USB so therefore I cannot use Odin to flash the phone.
Any help? Cheers
Dan
Click to expand...
Click to collapse
Are you using x86 or x86_64 OS? Both of these drivers are available at: http://code.google.com/p/insanity/downloads/list -- try 'em?
QwertyManiac said:
Are you using x86 or x86_64 OS? Both of these drivers are available at: http://code.google.com/p/insanity/downloads/list -- try 'em?
Click to expand...
Click to collapse
Tried all that already mate, but I tried again just in case, and nope.. No avail whatsoever. This is majorly frustrating now.
I can access Android Recovery (eventhough originally Clockworkmod was on there, but my cousin has done some strange things to this phone) so I think if I can find a verified signed update.zip, I can install something through that no problem, via the Internal SD Card + "apply: update.zip"?
Oh and another thing, when I put the USB Cable in to the Computer and in to the SGS, the option for Charging, Mass Storage, Tethering etc doesn't come up..
Any light whatsoever?
Swyped from my Deoxygenated HTC Desire

USB connection problems! [solved]

Ok I spent a few days searching and I just can't seem to find anyone with the same problem!
I got a used T-mobile G1, can't bypass the activation screen (touching the 4 corners in the a certain order doesn't work, believe me i tried!) so I thought of installing the recovery through adb, except adb doesn't see it!
The only thing i see in Device manager or usbdeview is "HTC Android Phone Device" "K:\" under Portable Devices. I cannot update it to the Google drivers, not from here or from the SDK. I tried un-installing it, from device manager and from usbdeview.
I thought it might have been the data cable, so I ordered another one from a different seller off of ebay.
I think i should note that when in fastboot mode, pluging in the usb does not change where it says Serial0 to anything else. I would of thought it change to USB if cable is connected like the older HTC devices.
What am I doing wrong? You're help is appreciated.
Follow this guide, it should help you fix your problem.
Thanks for the reply. But I already tried this guide, every step.
First, this phone doesn't have a custom recovery, so I can't do any fastboot updates.
Second, windows does not accept replacing the HTC Android Phone USB Device with the usb drivers from the guide. It just says "The folder you specified doesn't contain a compatible software driver...". I'm using 64bit Win7 so obviously I'm using the 64 bit drivers. I tried 3 different downloads from different sites just to be sure the drivers weren't corrupt. The other odd thing is that the HTC ANdroid Phone USB Device is under Disk Drivers in the device manager...
Third, I tried uninstalling using USBDeview, but still Windows automatically installs drivers back as soon as i replug.
Fourth, I cannot bypass the Activation screen, so I can't set USB to debuggin mode.
I know it's hard to suspect that it could be the cable, but I ordered another one from different site just in case.
Most peeps say I should see 3 HTC devices in the device manager, but I don't. Only thing that pops up in there is HTC Android Phone USB Device under Disk drivers and "K:\" under Portable Devices.
Got another cable today and it still doesn't show any other device other then the one in Device Manager... I ran of out of things to try. Anyone can advise? It's possible that my device is defective even though it boots normally.
After playing around for a few days, ended up somehow rooting and flashing Amon's latest recovery and then BAM windows detected new device and install the ADB interface.

[Q] Bricked Captivate -- Unique Situation?

I've flashed 6-8 ROMS on a couple different phones, so not a total noob, but I bow to the vastly superior knowledge here:
My Captivate was running CM7.1 stable from October with no further mods since. I hadn't flashed anything or really messed with the phone in awhile. I was just using the same phone in the same config I had been for 6 months.
A few days ago, CM7 started to force close all my programs. Annoying, but not a problem that rebooting wouldn't probably fix. Rebooted into bootloop (skater logo). 3 Button didn't put me into CWM Recovery, nor would any button combos get me to download mode.
Homemade a jig and got the phone into Download mode, with Odin One Click up and ready to flash to stock. Odin read the phone and I started the flash, but it hung at DO NOT TURN OFF TARGET for a couple hours. I checked on this forum to see what was next. All the previous posts just said to pull battery, re-jig, and start again.
This time, I didn't get the skater, I got the comp!phone. All button & USB combos I've read here bring me comp!phone (even the "hold until two blank screens" one). My PC won't recognize the phone now (so neither will Odin or Heimdall), even after I've reinstalled the Samsung drivers. I've read here that you can flash from the comp!phone screen, but the PC has to see your phone first, obviously.
So I guess I want to know how screwed I am. Magic tips on a easy fix would be just outstanding, too! Is the fact that I wasn't flashing or anything when it bombed interesting to anyone? Thanks in advance...
not sure it's identical but this worked for me: http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
OP,
Check out the "Connection Issues..." Stickied Thread in this forum.
Sent from my SAMSUNG-SGH-I777 using xda premium
Zadig won't load drivers for Heimdall 1-click
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
If you are still stuck...
Did you actually load a full version of Heimdall? Once I used unbrick as a mini-program. Another time I had to install a full version on my computer in order to get my phone and computer to communicate (that may be the missing driver step).
I know you have probably already done so but search the threads for AdamOutler and his work with Heimdall.
If you're using windows, windows update might be installing the drivers automatically. You might want to disable this feature, uninstall the current drivers and install new ones.
You can also try another pc that doesn't have any installed drivers - just to make sure...
Sent from a Captivate using XDA
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
Did you try manually installing the Samsung/Google usb drivers ? That's the usual culprit since stock are Samsung drivers and roms ( if its Aosp/Cyanogen) the Google drivers prime in that case.
Nearly Identical Problem
I've got the same problem with my Captivate...tried everything I've found in the forums but nothing works.
Background:
I had connection issues before trying to flash, but thought it was a driver issue with my Windows 7 machine. Which is why I had loaded the file onto the SD card when I attempted to upgrade to ICS. During the flash the phone hung and I eventually removed the plug and battery to see if I could reboot. I can get up to the Galaxy S I9000 screen, or the "Downloading..." screen, but I cannot get to the recovery menu or past the initial boot screen. My wife's captivate (same batch) IS recognized by the computer in "download mode" and in the USB transfer mode.
Attempts:
- Installed/uninstalled Kies many times
- Bought and tried a new data cable
- Installed/uninstalled the Galaxy S driver and the Captivate driver many times
- Tried Zadig, Odin, Heimdale, and Adb
- Used programs to remove USB devices and clean registry
- Installed Linux and tried within that OS
- Re-installed Windows 7
- Tried most of the above on my Windows XP system
Has anyone been successful in getting the computer to recognize a Captivate in this circumstance?
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
if u r still facing the problem..and problem isnt solved then just clean the pin of usb connector pin of ur phone...with a thin metal pin..or something like that...
and then u r good to go...
If all else fails...
I managed to brick my Captivate trying to get MUIU off my phone and flash back to Cognition. After many frustrating hours, I contacted Josh at mobiletechvideos.com. He fixed my phone and upgraded me to ICS for $50.00. I mailed my phone to him on a Thursday and received it back the following Friday.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

Help trying to root with Hasoon2000's toolkit

For whatever reason, when I'm trying to get my Token ID, I get as far as entering fastboot, and when trying to get the second command prompt to retrieve my token, it just gets stuck at "Waiting for Device".
I've made sure I'm using a USB 2.0 port ON THE BACKSIDE of my PC (I've tried 3.0, and front ports as well, all yield the same results)
USB debugging IS ENABLED.
I've tried with, and without fastboot disabled.
I've tried uninstalling ALL android related drivers on my PC, and re installing ONLY the HTC ones (I have a rooted nexus 7 2013 as well)
nothing seems to make a difference, everything works great right up until my device reboots into fastboot, then it becomes unrecognisable.
At the same time, windows shows a failed driver installation ONLY AFTER I unplug the device, and it shows it trying to install "HTC MTP DEVICE".
I've run out of ideas for a way to fix this by now, anyone have any other suggestions?
Install the driver from here and re try
However, i think is better unlock without a toolkit, but it's a choise
Toolkit's are usually just easier for me, I've only owned 3 different android devices.
My old Inspire which I rooted manually
My 2013 Nexus 7, rooted froma kit
and my HTC One, which is the only device I've encountered problems with so far.
Edit: I just attempted it yet again with the drivers you linked, still stuck at waiting for device.
Edit2: THANK GOD I FINALLY GOT IT WORKING!!!!!
When my phone boots into bootloade,r it runs on an "Android 1.0" driver. I went into my device manager, and updated that "Android 1.0 device" with the drivers you linked above, and everything magically connected, and I can now get my token ID!!!

device not found in recovery

some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.
i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.

Categories

Resources