Droid 4 Utility Gingerbread Only

---

Gingerbread only. If you are on ICS this will not work. Don't try! Get the ICS only tool here: http://forum.xda-developers.com/show....php?t=1779810

This is based on the original Droid 4 Utility with edits. Contains the complete GB fastboot files to restore your phone, root, unroot, install voodoo rootkeeper, safestrap of BG, etc. Extract after downloading and doubleclick the script to run.

Download here: Droid4 GB Only.zip - 1.19 GB
MD5 checksum posted at the hosting site.

If you have trouble connecting be sure usb debugging is on and you have the latest moto drivers installed. Moto drivers here: https://motorola-global-portal.custh...p/30,6720,8302

For menu 1 or 2 your phone must be in fastboot mode first. Enter this by using the tool option or manually by powering off, then hold both volume buttons and pressing power for a few seconds, release the power button and select "ap fastboot".

And of course be sure you have a good usb cable and a full battery if restoring your GB system.

Use at your own risk.

My phone seems to have no Android OS. It also has a dead battery. Plugging in the charger only shows the Motorola Dual Core screen. It won't turn on when connected to the pc. I can still boot to the Boot Mode Selection Menu. I also have a factory cable coming in a couple of days. Will I be able to use this utility using this cable? I can still go into Fastboot connected to the computer with the cable?

Originally Posted by badboi_zero

My phone seems to have no Android OS. It also has a dead battery. Plugging in the charger only shows the Motorola Dual Core screen. It won't turn on when connected to the pc. I can still boot to the Boot Mode Selection Menu. I also have a factory cable coming in a couple of days. Will I be able to use this utility using this cable? I can still go into Fastboot connected to the computer with the cable?

Yes, you can use this utility to reflash .219 to your phone through fastboot. Did the same thing to mine awhile ago and actually used it to reflash stock so I could upgrade to the .217 leak

Sent from my DROID4 using xda app-developers app

I'm having troubles rooting my .219 D4.

I installed the drivers, and according to the Moto device manager, I am up to date. USB Debugging is checked on.

When I try to root it using this tool (menu 3) and the phone is plugged in with charge only mode (using a stock Moto cable), this is what the command prompt spits out. It isn't instant, it's usually done over the course of 2 minutes:

It doesn't actually reboot on its own, and after rebooting manually, there is no SU app in my drawer.

I then tried to use menu 3 while in AP Fastboot mode, by using power and both volume buttons to get into the fastboot menu. I plug in my phone to the computer, and run the script and I get this:

It just hangs there for over 5 minutes and the phone doesn't do anything.

Here is the setup for my latter attempt:



Please help me figure this out. Could the drivers be corrupt? I've uninstalled and re installed the device manager from moto a couple of times. Could my anti-virus be blocking something? I think that the issue stems from a problem in the interface between the device and the computer.

Thanks in advance for any help

Hmm..it looks like the tool is possibly seeing more than one ADB server running. I'd the phone and let it up come up normal. Open up a task manager and go to the process tab. Are you seeing more than one ADB.exe process running? For some reason the tool thinks you have more than one device attached and as a result, isn't sure where to send the exploit.

This doesn't explain the troubles with Fastboot however.

When I plug in my phone and open up the tool, one adb.exe shows up in my task manager. Once I run the root script, I see a second one open. I tried killing it, and it will just open up again. How do I fix this?

If this is on the computer side, why wouldn't it explain the Fastboot problem?

SOLVED: Well, the problem wasn't really solved, but I transferred all the necessary tools to a different PC and rooted the device. So it was an issue with the original computer. MY theory is that it was an issue with the ADB interface from the Moto drivers. I'm purely spitballing on that though.

Thanks for the help anyways, guys. Time to have some modding fun!

Is there a mirror? I can't seem to download this...

Thanks for the utility!

I had some complications with the OTA update and realized that a fastboot back to stock was the only remedy. I couldn't find a linux solution (am I missing something?) so I modified the script to use moto-fastboot32. Worked great, thanks again!

Can some provide a mirror for this link? This isn't downloading...