Root ADB root issue

[mortimersnerd]

I'm trying to root my Bionic using the various one-step processes. All stop at "waiting for device". From what I can find, I need to have the ADB process active while in debugging mode, but for some reason my computer isn't loading this despite being in debugging. Any ideas on how to get this set up to work?

 

[OutOfPhase]

Before you try this see post below first.

Yes, follow the steps in this tutorial and it will set up adb to work everywhere on your PC. It is a one-click install.

New pre-packaged ADB installation

 

[OutOfPhase]

By the way what are you on (GB or ICS) and what are you trying to use to root? You should be able to root without adding adb.

Also do you have usb debugging enabled on your phone? Do you have it in charge only on GB or MTP on ICS?

 

[mortimersnerd]

By the way what are you on (GB or ICS) and what are you trying to use to root? You should be able to root without adding adb.

Also do you have usb debugging enabled on your phone? Do you have it in charge only on GB or MTP on ICS?

I'm on ICS. Debugging is on, not sure what MTP is. I'm primarily trying Motofail.

 

[OutOfPhase]

Ok. Follow these steps.

Download razorsedge and unzip it.
plug your phone in to your pc
on your phone pulled down the menu and select connected as "some name" check Media device (MTP)
go to where you unzipped razorsedge and click on the run.bat file and follow the on screen instructions.

 

[mortimersnerd]

Thanks for the links. ADB still "is not recognized as an internal or external command, operable program or batch file". Razr's Edge had the same results as other methods I've tried-hangs at "waiting for device."

 

[doogald]

Thanks for the links. ADB still "is not recognized as an internal or external command, operable program or batch file". Razr's Edge had the same results as other methods I've tried-hangs at "waiting for device."

Are you unzipping the files, or just trying to run from the zip file? Make sure that you unzip into a folder on your PC and then run from there. The "ADB not recognized" suggests to me that you are not unzipping the file first.

If that still doesn't work, do you have the latest Motorola Device Manager installed?

I think it's here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/78648/p/30,6720,8048

 

[mortimersnerd]

I'd actually found that ADB installer and tried installing it this morning. Definitely unzipped it first, have run it a few times. A window pops up, does something and disappears before I can see what it says. I've also tried installing the Google USB drives through the SDK tool. I've reinstalled Device Manager at least 3 times using version 2.3.4 (current version).

 

[OutOfPhase]

delete any drivers you installed for your phone
reboot your computer
download motohelper
reboot pc
plug your phone in and scroll through each usb connection setting (MTP etc..) and let the drivers install for each option before moving on to the next one
power off your phone and boot into fastboot by holding volume down and power button until the menu appears.
let the drivers install again
then reboot your phone by holding both volume buttons and the power button until the moto logo shows up.
when the phone reboots put it into MTP mode and try running the razors_edge again

This might sound like a lot but I want you to start from a clean slate when you give this a go.

 

[mortimersnerd]

Deleted the Motorola stuff, used USBDeview to remove the lingering bits of driveer. No difference. Still fails to show ADB in device manager. It turns up when the phone is in fastboot, but not when the phone is actually up and running.

 

[OutOfPhase]

And you have adb debugging checked under settings? Are you using the cable that came with the phone?

 

[mortimersnerd]

You mean debugging mode on the phone? Yup. This is why I'm so baffled. My phone didn't come with a cable, it was a warranty replacement for another model.

 

[OutOfPhase]

That might be an issue. Is the cable your using a moto branded cable?

looks like this Amazon.com: OEM Motorola ECOMOTO Micro USB Data Cable for Motorola Droid RARZ, RAZR Maxx, Droid 3, Droid 4, Photon 4G, Droid Bionic, Atrix 4G, Atrix 2, and Motorola Droid Xyboard 8.2 & 10.1 - Bulk Packaging: Cell Phones & Accessories

 

[mortimersnerd]

No, it isn't. I don't have one. I can't imagine it would make much of a difference, but for $3 I ordered one.

 

[OutOfPhase]

you would be surprised. moto has very strict standards where 3rd parts manufactures dont. we get reports all the time of 3rd part cables causing issues.

i am going to ask around and see if some other members have ideas.

 

[doogald]

you would be surprised. moto has very strict standards where 3rd parts manufactures dont. we get reports all the time of 3rd part cables causing issues.

i am going to ask around and see if some other members have ideas.

For what it's worth, I can use ADB on my Motorola Droid 3 with a Kindle sync cable. If a Motorola sync cable is not available, a different cable may work.

I switched from Windows to Macs several years ago, so I hardly ever use Windows these days, but I wonder about either a weird firewall setup on Windows, or an anti-malware app that's preventing the adb app from communicating?

Also, just to throw out other ideas, does the ADB client in windows need to be run as an admin-equivalent user?

 

[OutOfPhase]

For what it's worth, I can use ADB on my Motorola Droid 3 with a Kindle sync cable. If a Motorola sync cable is not available, a different cable may work.

I switched from Windows to Macs several years ago, so I hardly ever use Windows these days, but I wonder about either a weird firewall setup on Windows, or an anti-malware app that's preventing the adb app from communicating?

I thought about that to but figured that since it would see it in fastboot that it was not firewall or anti-malware.

Also, just to throw out other ideas, does the ADB client in windows need to be run as an admin-equivalent user?

No when you use that one click method it installs the Environment Variables for you allowing adb to be used from anywhere in windows with or without admin rights.

 

[OutOfPhase]

No, it isn't. I don't have one. I can't imagine it would make much of a difference, but for $3 I ordered one.

Try booting into fastboot and running razros-edge from there.

 

[johnlgalt]

Might be worth investing in some time to use HoB to root the phone....

 

[mortimersnerd]

New cable arrived today. Quite nice, complete with little Motorola hologram. No changes. also tried rooting while in Fastboot, also no changes. Mot Single ADB Interface was showing while in Fastboot. My phone is apparently invisible to computers for the purposes of rooting. I'm not familiar with HoB, any info you can share?

 

[Bruce53]

Not to step on anyones toes here just trying to help...Heres a video i used to root my bionic it may help you or it may not....just my .0002 cents.

http://forum.xda-developers.com/showthread.php?t=1254516

 

[mortimersnerd]

I appreciate the link. I'm hanging up at step 5. For some reason my system doesn't activate ADB.

 

[OutOfPhase]

here is a link to hob. SamuriHL's House Of Bionic - DroidRzr.com

if that doesnt work you might want to flash the modified 6.7.246 fxz with rsdlite from my signature to start with a fresh system then try rooting again.

 

[johnlgalt]

Resurrecting this thread b/c I found an issue recently that may have contributed to it.

OK, so some people have always had a major problem with ghost devices showing up in adb, so that they are not able to use automated tools that make use of the Android SDK platform tools. One recurring example is the emulator-5554 dummy device showing when you perform

 adb devices

It's been noted in other places that you should check out any particular software that might be listening in and creating these ghost entries. I'm happy to say that I've found at least one potential problematic software.

It's CorsairLink software. If it is installed and the service is running, the dummy item shows up breaking the root tools. Particularly this file:

C:\Program Files (x86)\Corsair\CorsairLink 2\Sierra2.GPU.exe

brought on by this service

C:\Program Files (x86)\Corsair\CorsairLink 2\SierraService.exe

.

The bigger problem here is that even though you can use a task manager to kill both files (under services) the second one will keep recurring. You'll either have to manually kill the server, manually kill the task that calls it, or uninstall CorsairLink temporarily to keep the ghost items from reappearing.

Mind you, this was the item on my system - it's not the universal cause for the emulator-5554 ghost item in adb, just one cause of it. Any other software that does any sort of similar 'listening' has the potential to cause problems when using adb, so e on the lookout.

HTH

 

[knmb323]

Resurrecting this thread b/c I found an issue recently that may have contributed to it.

OK, so some people have always had a major problem with ghost devices showing up in adb, so that they are not able to use automated tools that make use of the Android SDK platform tools. One recurring example is the emulator-5554 dummy device showing when you perform

 adb devices

It's been noted in other places that you should check out any particular software that might be listening in and creating these ghost entries. I'm happy to say that I've found at least one potential problematic software.

It's CorsairLink software...
...Any other software that does any sort of similar 'listening' has the potential to cause problems when using adb, so e on the lookout.

HTH

I was having trouble connecting a piece of software to my phone or even an emulator launched from Eclipse. I would select the device to connect to and within seconds it would indicate that no devices were connected (no longer connected?). No matter what I tried, emulator-5554 was always listed in adb devices but launching the app on that emulator did nothing. I tried killing the task with adb but it couldn't reach the port. I couldn't figure out how to make that "ghost" go away.

I discovered the solution somewhat by accident. I was running down the list in taskmanager, ending tasks, and re-running the "adb devices" command. Eventually I read the word BlueStacks and I knew immediately that I had found the culprit. Surely an application that allows you to run Android apps on a PC would be running an emulator.

BUT, hadn't I closed out the program when I booted my PC and then exited out of it via the tray icon (right-click -- Exit)? Surely, I thought, it was not running anywhere anymore. However, after an embarrassingly long period of frustration (and the suggestion by johnlgalt), I discovered it was, in fact, still listed as a running process in task manager. Maybe I had never closed it? Maybe I rebooted and forgot or got sidetracked? Whatever, once I ended it there, everything worked as intended. "adb devices" finally came up empty so I connected my phone and sent it the app I was working on without the "no connected devices" error.