Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Droid 4 Utility for Windows/Mac/Linux

OP skylarmb

29th February 2012, 06:51 AM   |  #1  
OP Junior Member
Flag Santa Cruz
Thanks Meter: 12
 
19 posts
Join Date:Joined: Aug 2011
Donate to Me
More
Hey all! This is the new home of the Droid 4 Utility (NOW WITH SAFESTRAP THANKS TO HASHCODE) for Windows/Mac/Linux!


There are (still) no fastboot files as of writing this (2/28/2012) so use Safestrap at your own risk
Once they come out I will be making a full version that includes fastboot restore. For now, the utility is only a few MB compared to a GB+.


From this point forward I will be taking charge of updating the Droid 4 Utility for Windows/Mac/Linux

This way mattlgroff has a little less work on his hands and can focus more on IMPORTANT things like bootloaders, ICS, etc...

MAC/LINUX: Be sure to read the instructions below (or README file) if you are not familiar with using terminal as root or executing bash scripts!

-Changes
~~as of 2/18/ 11:30PM PST
Fixed bug where Superuser.apk was pushed to /data instead of /system/app/
Fixed unroot script to properly remove Superuser.apk
~~as of 2/19 4:30 PM PST
Fixed chmod in root method from 4775 to 6775
~~as of 2/28 6:15PM PST
Added Safestrap recovery!!
~~as of 3/2
fixed script to chmod +x ./files -R so that you can actually run the files on mac and linux (that would be important huh?)




DOWNLOADS

WINDOWS
Size: 7.75 MB
MD5: f82bf8d8a085ff95b696712b8caa0f1b
Link: http://tinyw.in/KKB8

MAC
Size: 7.19 MB
MD5: dc8468d051d59963914a0b8a054b83b8
Link: http://tinyw.in/vx2A

LINUX
Size: 7.26 MB
MD5: 0c082efbff48e614b9d8ebffc7eca3eb
Link: http://tinyw.in/tpt0

Here's how:

Windows:

Simply Unzip the files, and run Droid4Windows.bat as administrator (right click>run as administrator)

Mac/Linux:

Simply extract the zip then


Code:
su
Then enter the root password NOTE: This is not YOUR password, this is the ROOT password. If you dont know it, you can always use

Code:
sudo passwd
to reset the root password

Next run:

Code:
cd /the path to where you extracted the files/
for example, heres what I have to type:

Code:
cd /home/skylar/Desktop/Droid4UtilityLinux/
next run the appropriate bash script:

Code:
bash Droid4linux
OR
Code:
bash Droid4mac


I'm sorry to say I don't actually own a Droid 4, so I'm doing this blind. Please report any problems or bugs you have.

Have fun and I hope you enjoy! [/SIZE]






CLICK HERE TO DONATE






SCREENSHOTS






CLICK HERE TO DONATE
Last edited by skylarmb; 3rd March 2012 at 08:47 AM.
The Following 2 Users Say Thank You to skylarmb For This Useful Post: [ View ]
29th February 2012, 09:01 AM   |  #2  
Member
Thanks Meter: 0
 
43 posts
Join Date:Joined: Jan 2009
I can not get this to unroot.



Quote:

---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK

Note: This removes superuser from both possible locations
So seeing one error of now finding Superuser is NORMAL!
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing busybox
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- pushing unroot script
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- rebooting
The system cannot find the path specified.
ALL DONE
Press any key to continue . . .
The system cannot find the path specified.

Please make a selection or hit ENTER to return:

Last edited by prodigyweb; 29th February 2012 at 09:22 AM.
29th February 2012, 11:11 AM   |  #3  
mattlgroff's Avatar
Recognized Developer
Flag San Diego
Thanks Meter: 2,416
 
2,263 posts
Join Date:Joined: Dec 2011
Donate to Me
More
Quote:
Originally Posted by prodigyweb

I can not get this to unroot.

Sounds like you aren't running this inside the folder that also contains the /files/ folder. If you have it by itself of course the path's won't find it...because you moved it or you aren't "cd" into the directory of the utility.
29th February 2012, 04:55 PM   |  #4  
Member
Thanks Meter: 0
 
43 posts
Join Date:Joined: Jan 2009
appears after a phone/computer reboot and canceling the ADB process in my tasks it now is rebooting the phone and working. Thanks!
Last edited by prodigyweb; 29th February 2012 at 05:02 PM.
29th February 2012, 04:58 PM   |  #5  
Senior Member
Thanks Meter: 25
 
241 posts
Join Date:Joined: Feb 2009
Donate to Me
Quote:
Originally Posted by prodigyweb

My setup is: http://i.imgur.com/Surbz.png

should it be within the adb package from android itself?

Is your USB Debugging Mode enabled and "Unknown Sources" in your application settings?
2nd March 2012, 12:11 PM   |  #6  
Recognized Developer
Flag Los Angeles
Thanks Meter: 255
 
814 posts
Join Date:Joined: Sep 2009
Donate to Me
More
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
2nd March 2012, 12:51 PM   |  #7  
Senior Member
Thanks Meter: 25
 
241 posts
Join Date:Joined: Feb 2009
Donate to Me
Quote:
Originally Posted by highlandsun

Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???

While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
2nd March 2012, 01:19 PM   |  #8  
Recognized Developer
Flag Los Angeles
Thanks Meter: 255
 
814 posts
Join Date:Joined: Sep 2009
Donate to Me
More
Quote:
Originally Posted by reigndropz

While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.

This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
2nd March 2012, 02:04 PM   |  #9  
Senior Member
Thanks Meter: 25
 
241 posts
Join Date:Joined: Feb 2009
Donate to Me
Quote:
Originally Posted by highlandsun

This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.

Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
2nd March 2012, 09:37 PM   |  #10  
Recognized Developer
Flag Los Angeles
Thanks Meter: 255
 
814 posts
Join Date:Joined: Sep 2009
Donate to Me
More
Quote:
Originally Posted by reigndropz

Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....

Hm, haven't done anything with theming tweaks. Dunno, sorry.

You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.

By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
Last edited by highlandsun; 2nd March 2012 at 09:40 PM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes