being the owner of a droid bionic on the 902 update I am interested in rooting it. But it appears as I am a MAC user this is not a possibility? To be specific I use an IMAC with the lion OS. Are there instructions for doing this or is all the android development done on the bill gates machines only, our version of the Steve Jobs monopoly.
rooting with a MAC
- Thread starter dkeven
- Start date
To simplify that a bit:
- you set the phone to use USB debugging mode. Settings->applications->development->turn on USB debugging
- attach to pc = should be obvious, but attach the phone to your PC by USB cable.
- extract zip file = open the zip file that you download into a folder on your Mac
- change to the zip directory = start the Mac application Terminal. (It is in the utilities folder in your applications folder.) This will open a terminal window with a $ prompt. Switch to the Finder and change to the directory where the files you unzipped are located. If you look at the top of the finder window, you will see a blue folder icon with the name of the folder next to it. Switch back to the terminal window and type "cd " (that's the letter c, the letter d, followed by a space - do not hit enter.) Now, drag that folder icon at the top of the finder window I mentioned before to the terminal window and drop it. This will type the actual folder path next to the "cd " that you typed before. Now, activate the terminal window if it is not the active window and hit enter. You have now changed to the zip directory. (Whew! That was a lot of steps for five words!)
- invoke ?./run.sh? from a shell = type that exact phrase in the terminal window - period, slash, letter r, letter u, letter n, period, letter s, letter h, hit enter. This should start the root procedure.
Last edited:
will try that when home tomorrow thanks for the clarification, had seen the moto fail article but wasn't sure of procedure.
any idea why i get this. ive tried multiple methods for rooting the 902 system version on both mac and windows. none work.
USB debugging is on.
USB debugging is on.
Code:
unknown0026bb0d096b:platform-tools lqdboard$ ./adb devices
List of devices attached
0A3BEBD419013015 device
unknown0026bb0d096b:platform-tools lqdboard$ ./run.sh
chmod: ./adb.osx: No such file or directory
[*]
[*] Motofail: Universal Motorola Gingerbread Root Exploit (OS X version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
./run.sh: line 57: ./adb.osx: No such file or directory
[*] Device found.
[*] Deploying payload...
./run.sh: line 62: ./adb.osx: No such file or directory
./run.sh: line 63: ./adb.osx: No such file or directory
[*] Owning phone...
./run.sh: line 66: ./adb.osx: No such file or directory
[*] Rebooting device...
./run.sh: line 69: ./adb.osx: No such file or directory
[*] Waiting for phone to reboot.
./run.sh: line 72: ./adb.osx: No such file or directory
[*] Attemping persistence...
./run.sh: line 75: ./adb.osx: No such file or directory
./run.sh: line 76: ./adb.osx: No such file or directory
./run.sh: line 77: ./adb.osx: No such file or directory
./run.sh: line 78: ./adb.osx: No such file or directory
./run.sh: line 79: ./adb.osx: No such file or directory
./run.sh: line 80: ./adb.osx: No such file or directory
./run.sh: line 81: ./adb.osx: No such file or directory
./run.sh: line 82: ./adb.osx: No such file or directory
[*] Cleaning up...
./run.sh: line 85: ./adb.osx: No such file or directory
./run.sh: line 86: ./adb.osx: No such file or directory
[*] Rebooting...
./run.sh: line 89: ./adb.osx: No such file or directory
./run.sh: line 90: ./adb.osx: No such file or directory
[*] Exploit complete!
[*] Press any key to exit.
Last edited:
I don't understand how you added the .OSX extension to the ADB file.
Could you please post more instructions? I got the same fail response you posted.
Thanks
Could you please post more instructions? I got the same fail response you posted.
Thanks
straight up
1.just downloaded the SDK files.
2. Move to Desktop
3. opened up the platform tools folder
4. Moved all the files from the MotoFail folder into Platform Tools
5. Renamed the 'ADB' file to 'ADB.OSX'
6. Open Terminal
7. Change directory into Platform Tools
8. Invoke 'run.sh' file.
1.just downloaded the SDK files.
2. Move to Desktop
3. opened up the platform tools folder
4. Moved all the files from the MotoFail folder into Platform Tools
5. Renamed the 'ADB' file to 'ADB.OSX'
6. Open Terminal
7. Change directory into Platform Tools
8. Invoke 'run.sh' file.
after hours of permissions denied the MotoFail method was the only thing that worked for me
worked on my Bionic with 5.9.902
using MacOSX 10.6.8
Instructions:
* Download the required files from here
* Extract them to a folder
* Enable USB debugging mode in phone setting
* Connect your Droid Bionic to your mac
* Execute ?RUN.SH? from the extracted files
* You?re good to go.
Credit to Dan Rosenberg for this root exploit.
worked on my Bionic with 5.9.902
using MacOSX 10.6.8
Instructions:
* Download the required files from here
* Extract them to a folder
* Enable USB debugging mode in phone setting
* Connect your Droid Bionic to your mac
* Execute ?RUN.SH? from the extracted files
* You?re good to go.
Credit to Dan Rosenberg for this root exploit.
I have done everything exactly as instructed and I still get the "No such file or directory". Is there another way I can try rooting my Droid 4?
Thanks!
Thanks!
When you are in the terminal window, your terminal *must* have the current directory set to the location where the motofail files were unzipped. So, if you stored the files in your Downloads folder on your Mac, most likely it will unzip into a folder called motofail_linux_osx. So, from the terminal window, you enter the command:
Of course, you have to change that to the actual location of the files that are unzipped (i.e., run.sh.) When the prompt changes to show that you are in the motofail_linux_osx folder, you can then enter the command:
(The period slash at the beginning is important - it tells the os to run the command from the current directory.)
Followed instructions above and no error. Rooted and backed up with TiB Pro. Thanks for the easy instructions:
Is there a way to unroot using OSX as well?
Is there a way to unroot using OSX as well?
Last edited:
Followed instructions above and no error. Rooted and backed up with TiB Pro. Thanks for the easy instructions:
Is there a way to unroot using OSX as well?
I believe that you can do it right on the phone. First, if you have debloated or frozen any apps, make sure to restore them (or thaw them.) If you have installed a bootstrap/custom recovery, follow the steps to uninstall that and restart the phone. Then, see the instructions in this post - the first 6 steps (it's for the Droid 3, but the process is the same): http://androidforums.com/droid-3-all-things-root/611821-unroot-manually.html#post4904546
I followed your exact steps and I get the following errors, any clue? Mac OSX 10.8.2 Droid Bionic ICS 4.0.4:
MiniMe:motofail_linux_osx zothecula$ ./run.sh
[*]
[*] Motofail: Universal Motorola Gingerbread Root Exploit (OS X version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
failed to copy 'motofail' to '/data/local/motofail': Permission denied
Unable to chmod /data/local/motofail: No such file or directory
[*] Owning phone...
/system/bin/sh: /data/local/motofail: not found
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
[*] Cleaning up...
/system/bin/sh: /data/local/motofail: not found
rm failed for /data/local/motofail, No such file or directory
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Are you sure that you have USB debugging enabled on the phone? I don't have a Bionic with ICS, so I'm not sure where that setting is now.
nix_for_me
New member
I have the exact same problem that Zothecula does, but I'm on Linux and my phone is a Motorola Atrix 2:
It's clear that it's a permissions issue [on the phone]...but how do I fix it? If I had root power, I could fix it in a millisecond. But that's the quandary!
It's clear that it's a permissions issue [on the phone]...but how do I fix it?
If I had root power, I could fix it in a millisecond. But that's the quandary!Will it sit here for a while?
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Similar threads
Latest posts
-
-
Question HELP ASAP!!!! my mini android 4.4 generic projector got bootloop
- Latest: Hisoka_Ryuzaki
-
Trending Posts
-
[Chatter] "Where everybody knows your name ..."
- Started by zero neck
- Replies: 53K
-
Why do I keep getting these notifications on my both my Galaxy S24+
- Started by deb1113
- Replies: 5
-
-
-
Facebook
Twitter
Instagram