• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Rooting for Mac

No need to install any USB drivers

No need for a hex editor to write the goldcard image to the micro SC card.

Use the *nix command dd from terminal.app. specfically:

Code:
sudo dd bs=512 if=~/Downloads/goldcard.img of=/dev/disk1

replacing of course the path here with your path and disk

Source and more details (guide is written specifically for Japanese Sapphire/Magic aka ht-03a but making the goldcard is not specific)
 
Upvote 0
I'm a noob when it comes to rooting. I need a tutorial on how to root (latest build) 1.47.651.1, unlock nand protection (full access) while using a Mac.

I'm not sure what a goldcard image is, I've been looking for a Mac specific video tutorial.

Oops. My fault spank me. :eek: You don't need a gold card for the Evo. That is awesome. (a goldcard is a specially formatted micro SD card that tricks the SPL in to executing code that the security checks would normally not allow)

Here is the latest guide, which exploits a flash vulnerability (go figure :rolleyes:).

---==={ROOT GUIDE}===--- | 1.47.651.1 ROOT method | - xda-developers

This is by far the simplest guide I have ever seen thanks to adobe!

There is also a video tutorial.

The guide on XDA is completely non specific to macs or PCs. When it says "PC" just mentally replace that with mac. Be sure to read read and read some more before starting

0. Make sure you have an Intel mac

1. You need to setup the SDK and a java environment. There are plenty of mac guides for this on the web.

After you setup the SDK and java environment, you need to add the tools folder of the SDK to your path. Open up Terminal.app and type the following
Code:
ls -a ~
If you don't see a file called ".bash_profile", then you will need to create one. If you are not comfortable with vi, you can you TextEdit.app. Create a new text file (Format > Make Plain Text) and type in the following text, using of course the path to where ever you saved the SDK and the name of the SDK folder if it is different than the example below.
Code:
export PATH=${PATH}:/Users/SBS/Documents/android-sdk-mac_86/tools
Now save the file as .bash_profile (the dot is important) and say OK to the warning about this creating a system file or something like that. Do not add the extension txt, though sometimes Mac OS will add it anyway so you need to verify the name of the file.
Code:
ls -a ~
If you see .bash_profile.txt, do the following.
Code:
mv .bash_profle.txt .bash_profile
Now you should be able to type in adb commands without having to switch to the tools directory.

2. Connect your phone by USB

3. in terminal.app on the mac type
Code:
adb devices
to confirm you phone is connected.

4. begin following the directions on the above XDA site.
Code:
adb shell
You type adb shell in terminal.app and what happens is it opens an interactive shell on your handset. You are typing commands directly in to the phone. To exit the shell type.
Code:
exit

EXTRA TIPS: When at all possible verify the md5 checksums of every file before flashing to your phone or using that file to execute commands on the phone. The current SDK has the following checksum:

c92abf66a82c7a3f2b8493ebe025dd22

After downloading the SDK do this in terminal:
Code:
md5 ~/Downloads/android-sdk_r06-mac_86.zip
verify you get the correct hash.

Code:
MD5 (/Users/SBS/Downloads/android-sdk_r06-mac_86.zip) =
c92abf66a82c7a3f2b8493ebe025dd22

Do this with every file that has a checksum

HTH.
 
Upvote 0
Okay, I am TOTALLY new at this whole mess.
I have a mac.
I am trying to root, I have the newest update.
I downloaded the MAC SDK
When I open terminal and type ls -a ~
I see no .bash_profile, just .bash_history
So I created a file saved it in the same file as my mac sdk.
But I am stuck there.
What am I missing here
(other than my intelligence)
 
Upvote 0
Okay, I am TOTALLY new at this whole mess.
I have a mac.
I am trying to root, I have the newest update.
I downloaded the MAC SDK
When I open terminal and type ls -a ~
I see no .bash_profile, just .bash_history
So I created a file saved it in the same file as my mac sdk.
But I am stuck there.
What am I missing here
(other than my intelligence)

I have the same problem my friend.
 
Upvote 0
is it not necessary to install SDK Components when setting up the SDK? If so which one do I need 2.1?

The starter package comes with SDK tools, which should be all you need.

Okay, I am TOTALLY new at this whole mess.
I have a mac.
I am trying to root, I have the newest update.
I downloaded the MAC SDK
When I open terminal and type ls -a ~
I see no .bash_profile, just .bash_history
So I created a file saved it in the same file as my mac sdk.
But I am stuck there.
What am I missing here
(other than my intelligence)

I have the same problem my friend.

Sorry, I wasn't clear. In unix, the tilde ~ is a shortcut to your home folder. when I said do ls -a ~, that means to show invisible files in your home folder. If you don't see .bash_profile, you need to create it in your home folder.

so you should have something like this.
Code:
ls -a ~
.			.config			Downloads
..			.cups			Library
.CFUserTextEncoding	.dvdcss			Movies
.DS_Store		.fontconfig		Music
.Trash			.lesshst		Pictures
.Xauthority		.local			Public
.android		.ssh			Sites
.bash_history		Desktop			Wine Files
[B].bash_profile[/B]		Documents
There are other ways to add commands to your path, but for people that aren't familiar with unix, this is the best way because it only has you mucking around in your home folder, where the other ways have doing things in the root folder (highest level directory).

you can trouble shoot by doing
Code:
echo $PATH
Which will return all folders that are in your path. If you don't see the SDK tools folder then it is not in your path.
Code:
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:[B]/Users/SBS/Documents/android-sdk-mac_x86-1.6_r1/tools[/B]
You may need to quit terminal and start a new session for the setting to take effect.

If you just can't get it to work, you can do everything from within the tools directory by prefacing each and every command with ./

This forces tells the computer to look in the current directory for the command.
Code:
cd ~/Documents/android-sdk-mac_x86-1.6_r1/tools/
./adb devices
List of devices attached 
K???	device
cd is the command to change directory. (since rooting, I get a funky number when I do adb devices, it shouldn't be "K???" but that doesn't cause any issues.

EDIT: for clarity the last example using ./ was done after I purposely renamed my .bash_profile file so that adb was NOT in the path.
 
Upvote 0
I got all the way to step 11 where you have to reboot to flash the pc36img
I get the "this version is older than the main version" error!
According to the end of the post this is a common error. I don't quite understand though. It says the error is caused when your SD card isn't mounted properly and you can push the files manually. The files are on my phone.
So, I do not know where to go from here.
Help?
 
Upvote 0
I got all the way to step 11 where you have to reboot to flash the pc36img
I get the "this version is older than the main version" error!
According to the end of the post this is a common error. I don't quite understand though. It says the error is caused when your SD card isn't mounted properly and you can push the files manually. The files are on my phone.
So, I do not know where to go from here.
Help?

I can help you with the mac specific steps but not with general rooting because I don't even have an evo.

adb push is used to move files from the computer to either the nand on the phone or the SD card, so for example (and this is just an example), if you wanted to push a file (let's call the file data.img) in your Documents folder, to /data/local on the phone you would do this
Code:
cd ~/Documents
adb push data.img /data/local
Be careful, though.
 
Upvote 0
I got all the way to step 11 where you have to reboot to flash the pc36img
I get the "this version is older than the main version" error!
According to the end of the post this is a common error. I don't quite understand though. It says the error is caused when your SD card isn't mounted properly and you can push the files manually. The files are on my phone.
So, I do not know where to go from here.
Help?
at least u make it to step 11. i don't understand any of this
 
Upvote 0
I strictly use a Mac and have had no issues. I downloaded the SDK and placed only the tools folder on my desktop. Open terminal you should see:

yourcomputername:~ youraccount$

type cd [space][now drag the tools folder to the cursor]

you should now see:

yourcomputername:~ youraccount$ cd /Users/[youraccount]/Desktop/tools
hit enter and you will see:
yourcomputername:tools youraccount$

now to execute any adb command just type [./adb shell]

your phone must be connected at the point you start the adb commands.
 
Upvote 0
SBS,

I see the .bash_profile now. But when I type in 'adb devices' nothing shows up under 'List of devices attached.'

However, when I typed in the code, 'echo $PATH' the SDK tools are in my path.

Did you enable USB debugging on the phone? If you don't then you can't connect to you computer. Obviously phone must be on. Also try reconnecting the cable.

If you got output from adb devices, that means you've successfully added the tools folder to your path, as you confirmed with echo. If it wasn't added to your path, you would have gotten "-bash: adb: command not found" instead of output indicating no devices are connected.

I strictly use a Mac and have had no issues. I downloaded the SDK and placed only the tools folder on my desktop. Open terminal you should see:

yourcomputername:~ youraccount$

type cd [space][now drag the tools folder to the cursor]

you should now see:

yourcomputername:~ youraccount$ cd /Users/[youraccount]/Desktop/tools
hit enter and you will see:
yourcomputername:tools youraccount$

now to execute any adb command just type [./adb shell]

your phone must be connected at the point you start the adb commands.

This is basically what I said previously that you can force bash to look in the current directory with ./

But you will always have to be in the tools directory to execute commands, so it is much better to add tools to your path.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones