Droid Razr will NOT root -_- Stuck on "daemon started successfully)

[Airman1947]

Hey everyone,

I hope someone can help me. I showed my friend at work my rooted Droid 4, and now he wants his Droid Razr rooted. I figured that wouldn't be a problem given the fact that there are so many tools out there to make this happen...fast forward three hours later, and his phone still isn't rooted. :P

I don't know what's wrong. I've tried using Matt Groff's program (Droid Razr Utility), and made sure I was using the correct version. My friend has ICS 4.0.4 on his phone, so I'm using version 1.8. The program opens, and detects the phone, and gets as far as "daemon started successfully" and then just hangs. It doesn't go any further. I've found a number of similar programs for rooting the phone, and they all do the same. I've checked all of the settings. The phone is in USB Debugging mode, and connected as a Media device (MTF). I also tried turning on Unknown Sources, and Allow Mock Location, and same thing.

I tried disconnecting and reconnecting the USB cord while the program was hanging. I tried rebooting the phone both during hang, and in between rooting attempts. Same problem. I tried two different USB cords, and four different computers, three of which had Windows 7, and one had XP. I tried uninstalling and reinstalling the drivers on the computer, and it makes no difference. I even went as far as trying different driver versions. I tried getting the driver right from Motorola, and I also tried the drivers that came with some of the root programs...nothing seems to work.

I think I've tried almost every suggestion I've found for this sort of problem, and we're both on the verge of giving up, thinking it's just a stubborn phone. Anyone have any ideas? We're desparate. Thanks so much in advance.

[Sydman]

Inside of the Razr Utility folder there are some failsafe batch files, as well as a readme that tells you what to do with them. You could try those and see if it works correctly, you basically copy them over to the main folder and then just double click on the batch file you want to use.

It is all of the operations of the utility without the menu. I would try copying over all of them and then just run the one to root the phone. Also make sure you have the utility extracted fully into it's own folder.

[Airman1947]

Inside of the Razr Utility folder there are some failsafe batch files, as well as a readme that tells you what to do with them. You could try those and see if it works correctly, you basically copy them over to the main folder and then just double click on the batch file you want to use.

It is all of the operations of the utility without the menu. I would try copying over all of them and then just run the one to root the phone. Also make sure you have the utility extracted fully into it's own folder.

Thanks for the input. We did extract the utility into it's own folder, but we didn't try the failsafe batch files. We can try that next time I see my friend. But, I don't think that's going to work.

I forgot to mention one detail. The computers that we tried all apparently didn't see the phone as an ADB Interface. The driver called "Mot Composite ADB Interface" didn't show up in Device Manager. The phone showed up under "Portable Devices," but not "ADB Interface." It looks like it needs to be detected that way in order to use ADB.EXE. I know for a fact that the drivers are not corrupted, because I plugged my Droid 4 into one of the computers that we used (Droid 4 uses the same drivers), and that ADB Interface thing in Device Manager came up just fine. In fact, I ran the ADB.EXE file in a command prompt, and it detected my phone.

So, I'm wondering if my friend's phone is just messed up. Any idea if a factory reset might help? Thanks again for the help. I appreciate it

[jpcalhoun]

Thanks for the input. We did extract the utility into it's own folder, but we didn't try the failsafe batch files. We can try that next time I see my friend. But, I don't think that's going to work.

I forgot to mention one detail. The computers that we tried all apparently didn't see the phone as an ADB Interface. The driver called "Mot Composite ADB Interface" didn't show up in Device Manager. The phone showed up under "Portable Devices," but not "ADB Interface." It looks like it needs to be detected that way in order to use ADB.EXE. I know for a fact that the drivers are not corrupted, because I plugged my Droid 4 into one of the computers that we used (Droid 4 uses the same drivers), and that ADB Interface thing in Device Manager came up just fine. In fact, I ran the ADB.EXE file in a command prompt, and it detected my phone.

So, I'm wondering if my friend's phone is just messed up. Any idea if a factory reset might help? Thanks again for the help. I appreciate it

You can try a factory reset if you'd like. The only disadvantage is you'll have to put all the user apps back on...that might not be a big deal for your friend. It certainly won't hurt. If Device Manager is not seeing the phone as an ADB device I would select "portable device", right click on mouse...delete drivers and then re-install drivers again. Drives can be particular how they are installed particularly if an older or corrupt driver exist (you probably know that). Just to be sure I'd delete the drives associated with portable device and re-install a fresh update set of drivers. Just a suggestion.

[Airman1947]

You can try a factory reset if you'd like. The only disadvantage is you'll have to put all the user apps back on...that might not be a big deal for your friend. It certainly won't hurt. If Device Manager is not seeing the phone as an ADB device I would select "portable device", right click on mouse...delete drivers and then re-install drivers again. Drives can be particular how they are installed particularly if an older or corrupt driver exist (you probably know that). Just to be sure I'd delete the drives associated with portable device and re-install a fresh update set of drivers. Just a suggestion.

Yeah, replacing all of the user apps would suck. And I'd hate to have him do it, especially if it didn't work. I think it's his work phone too. I was just asking in case anybody here had a similar problem, and knew for sure that it would fix it. If it's just a theory, I'm not gonna make him do it.

Anyway, thanks for the input. Actually, I did try that idea of deleting the portable device drivers already, and reinstalling the drivers. No dice :P I'm thinkin his phone is just fubard for some reason. Maybe he's got some app or setting on there that's messing with ADB. Well, I think I'm gonna try one more thing. I saw a thread where somebody had a similar problem, and managed to get ADB to work on a different operating system other than Windows. I'm gonna try it on Ubuntu and see how we make out. Thanks again for all the help.

[jhayes1022]

Are you sure your razr is set on debugging. Mine was not I set it and bingo it worked.