I didn't find any mentions of this in the other threads or a thread dedicated to this, but just wanted to point out that it is very easy to do this on a Mac.
You will need to follow the same instructions in the other guides, but you can do it all from the Mac OS Terminal easily and no need to install drivers, just like you would with Linux.
In case someone wants step by step instructions, here they are modified for Mac OS:
Original instructions by chuckhriczko http://forum.xda-developers.com/showthread.php?t=581577
Step 1:
First you need to download the Android SDK. You can get it from http://developer.android.com/sdk/index.html. Download the Mac OS version and remember where the android-sdk-mac folder is (most likely in your Downloads folder)
The next thing we download is asroot2. This is a script that was developed that runs an exploit in Android's linux that allows us to run root. The link for that is here: http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154. Unzip that file and place it in a directory of your choice (I used android-sdk-mac/tools). Also download http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.2.3.img and place that into the same directory you extracted asroot2.
Step 2:
Connect the phone to the USB port.
Open a terminal and cd into the directory that you extracted the sdk into. Then cd into the tools directory. Then run the following commands:
sudo ./adb push /directory_you_placed_asroot2/asroot2 /data/local/
sudo ./adb shell chmod 0755 /data/local/asroot2
sudo ./adb shell /data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
type exit until you are back to your Mac's prompt.
Now your phone is officially rooted! We arent done yet though. Now you need to flash the recovery image. If you are still in adb shell type in exit until you are out. You should be in the directory where you extracted the recovery image. If not go there. Type in the following:
sudo /.adb push recovery-RA-heroc-v1.2.3.img /sdcard/
Once that is done, type in sudo ./adb shell. If your command prompt is a dollar sign then type in su and press enter. If it is a pound sign you are good. Then type in the following:
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
Once that is finished you are done. To reboot into recovery type in
sudo ./adb shell reboot recovery
If you are already in the shell, just type
reboot recovery
You should reboot into recovery mode and you can go from here. You can do a nandroid backup and then follow the other guides to install a different ROM or any other things you want to do.
If there are no instructions for Mac, just follow the Linux/Ubuntu instructions as they will be very similar if not the same.
Actually...
http://forum.xda-developers.com/showthread.php?t=581686
This is the thread I used to root my Hero CDMA from my Macbook, worked just fine...Thanks anyways for giving some love to macusers, guides are usually windows only.
I thought it was weird that there wasn't a Mac dedicated thread. I guess the search doesn't like 3 letter words.
Been talking to Lekky and we have all these great things grouped into one thread. One important thread is side mounting the captivate.
Things it gives you are SDK which can be downloaded for PC or Mac.
Drivers again PC or Mac.
Then Root access no biggie
Busy box no biggie.
Then it goes into the CMD language for PC on how to edit the database file using CMD prompts to enable the sideloading of APKs directly on the phone.
What we are looking for is someone to translate this into mac terminal command lines. Here is how it reads now:
Connect USB to phone with USB Debugging ON
Command prompt
cd to SDK install directory
cd tools
adb shell
su
cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db.backup
exit
exit
(This should bring you back to your windows command prompt.)
adb pull /sdcard/settings.db %userprofile%\desktop
(This should copy the settings.db to your desktop in Windows. Keep your cmd window open, you'll need it again.)
Install SQLite Manager Plugin for Firefox
Open SQLite Manager Plugin within Firefox (Tools->SQLite Manager)
Click Database
Click Connect Database
Find settings.db
Expand Tables
Click secure
Scroll down to ID 6, "install_non_market_apps". Double-click.
Change value ( TEXT ) from 0 to 1
Close SQLite Manager
(Back to that cmd window)
adb push %userprofile%\desktop\settings.db /sdcard
adb shell
su
cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings
busybox chown 1000 /dbdata/databases/com.android.providers.settings/settings.db
busybox chgrp 1000 /dbdata/databases/com.android.providers.settings/settings.db
reboot
Disconnect USB from phone. Your phone should be rebooting.
Done! I tested this and was able to install siriusxm.apk from siriusxm.com/android.
Who knows Mac Terminal commands well enough to translate this so that it can be posted in this sticky thread along with the windows version for us?
put ./ before each command
./adb pull /sdcard/settings.db %userprofile%\desktop
./adb shell
then carry on like normal
su
cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings
busybox chown 1000 /dbdata/databases/com.android.providers.settings/settings.db
busybox chgrp 1000 /dbdata/databases/com.android.providers.settings/settings.db
reboot
then do the ./ again
./adb push %userprofile%\desktop\settings.db /sdcard
Also, if you *read* the sticky, it provides these notes, in blue, to make it more pronounced.
yea was on androidforums not here they didnt have the mac side, found it here after u guys mentioned it, awesome ty.
The Absent-Minded Professor and I just installed adb on Ubuntu; here is how to set up adb on Ubuntu Linux, Gutsy through Maverick.
Our port of the BX theme to CM6 stable is forthcoming.
first command after installing and updating sdk and extracting the tgz file to your home directory is== sudo gedit /etc/udev/rules.d/70-android.rules
NOTE: In the above file replace ## with the number 50 if you are running Gusty/Hardy/Dapper (50-android.rules) or with the number 70 if you are running Karmic Koala/Lucid Lynx(70-android.rules
after the window pops write this in the file==SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″ then save and close
the follwing commands is== sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Then reboot.
Open a terminal and type== sudo gedit .bashrc
The file contents should be as follows== export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
Save and close.
Run the command== adb devices
If you see a serial number like this:
List of devices attached
HT99PHF02521 device
then you are done.
If you get error messages such as "no such command," cd to /home/user/android-sdk-linux_x86/tools and use the adb commands in this way:
./adb devices
./adb shell
etc.
If you get an error message here referencing insufficient device permissions, do the following:
./adb kill-server
sudo ./adb start-server
Now ./adb devices should work.
Courtesy of laie1472 and The Absent Minded Professor
Thanks to Esau Silva (http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/) and Tobias Eisentrager (http://www.mail-archive.com/[email protected]/msg14211.html).
Requesting Removal
This thread is of no use. Please remove.
Thank you!
WEM97 said:
Introduction
I am sure many of you have run into this problem before. Your flashing a ROM and on your marry way to enjoying the yummy goodness that comes with a fresh flash. You boot up and suddenly you hit with FC's and reboots that never seem to end and come out of nowhere. That or your device doesn't even flash at all. This occurred to me when I attempted to leave Oneplus's ALPHA Build of Lollipop for the device. In fact, some of my partitions were downright gone. Now before you run off and try to re flash CM11S, there are some things you should know. There is a high possibility it will fail and you will be enjoying a $350 brick. For help with such, view this tool here. However if you haven't gotten to this point yet and still have access to recovery, fastboot, etc... then this guide is here for you (and anyone else needing to fix their partitions)!
Repairing Your File System
> Connect your device to your computer while booted into Android
> Make sure Root Access for ADB is enabled in Developer Options
> If Developer Options are not enabled on your device go to Settings > About and tap Build Number 5 times. Now Developer Options will be displayed in Settings
> Press Windows + R, type "cmd" and press Enter
> Type:
Code:
adb devices <press enter>
Your Device should be displayed in a list below. If it is not showing up, try a different USB port and check to make sure you have all of your device drivers installed.
> Next Type:
Code:
su <press enter>
fsck_msdos -p -y /dev/block/vold/179:9 <press enter>
> And:
Code:
fsck_msdos -p -y /dev/block/vold/259:3 <press enter>
If your device's partitions need to be repaired, you will be prompted with a yes or no option.
> Type:
Code:
Y <press enter>
And you're done!
> Note: Since different devices may have different mounts, you can check yours by typing this command in Terminal Emulator :
Code:
mount | grep sdcard <press enter>
> Congratulations! Your partitions should be good to go! Happy flashing
Credits
Twiq
Click to expand...
Click to collapse
Does this erase my data? My data partition is corrupt since I can't perform nandroid backup
WEM97 said:
Introduction
I am sure many of you have run into this problem before. Your flashing a ROM and on your marry way to enjoying the yummy goodness that comes with a fresh flash. You boot up and suddenly you hit with FC's and reboots that never seem to end and come out of nowhere. That or your device doesn't even flash at all. This occurred to me when I attempted to leave Oneplus's ALPHA Build of Lollipop for the device. In fact, some of my partitions were downright gone. Now before you run off and try to re flash CM11S, there are some things you should know. There is a high possibility it will fail and you will be enjoying a $350 brick. For help with such, view this tool here. However if you haven't gotten to this point yet and still have access to recovery, fastboot, etc... then this guide is here for you (and anyone else needing to fix their partitions)!
Repairing Your File System
> Connect your device to your computer while booted into Android
> Make sure Root Access for ADB is enabled in Developer Options
> If Developer Options are not enabled on your device go to Settings > About and tap Build Number 5 times. Now Developer Options will be displayed in Settings
> Press Windows + R, type "cmd" and press Enter
> Type:
Code:
adb devices <press enter>
Your Device should be displayed in a list below. If it is not showing up, try a different USB port and check to make sure you have all of your device drivers installed.
> Next Type:
Code:
su <press enter>
fsck_msdos -p -y /dev/block/vold/179:9 <press enter>
> And:
Code:
fsck_msdos -p -y /dev/block/vold/259:3 <press enter>
If your device's partitions need to be repaired, you will be prompted with a yes or no option.
> Type:
Code:
Y <press enter>
And you're done!
> Note: Since different devices may have different mounts, you can check yours by typing this command in Terminal Emulator :
Code:
mount | grep sdcard <press enter>
> Congratulations! Your partitions should be good to go! Happy flashing
Credits
Twiq
Click to expand...
Click to collapse
There is some discrepancy in these instructions. It sounds like you're implying we use Windows to perform the above commands but 'fsck' is not a Windows-compatible command. You even say to press the Windows key + R and run 'cmd' which to me says Windows, but grep is def not Windows....what's the deal?
I really would love to be able to do this, but these instructions have me baffled. Can you please help?
bgibson72 said:
There is some discrepancy in these instructions. It sounds like you're implying we use Windows to perform the above commands but 'fsck' is not a Windows-compatible command. You even say to press the Windows key + R and run 'cmd' which to me says Windows, but grep is def not Windows....what's the deal?
I really would love to be able to do this, but these instructions have me baffled. Can you please help?
Click to expand...
Click to collapse
There aren't any discrepancies in this tutorial. If you pay attention those commands are being given to the connected Android device via adb, that's why they're Linux commands, because they're being issued to a Linux device.
Transmitted via Bacon
You're correct! Apparently I was not in the platform-tools directory in windows when issuing the adb commands which is why they weren't working for me. My bad.
I think you meant to write that users need to enter the commands like su, fsck in adb shell....
Is that it?
Anyway, I have an OPO in recovery mode, the the devices you mention are not appearing (i.e. there is no /dev/block/vold/179:9 )
C:\Users\Admin\Desktop\android-sdk-windows\platform-tools>adb devices
List of devices attached
dff430e0 device
C:\Users\Admin\Desktop\android-sdk-windows\platform-tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
What am I doing wrong?
Nexus5-32GB said:
What am I doing wrong?
Click to expand...
Click to collapse
There should be a
Code:
adb shell
in front of the
Code:
su
command.
thanks, have another problem:
Code:
D:\opotoolbox\OPO>adb shell
←7←[r←[999;999H←[6n
←[email protected]:/ $ su
su
←7←[r←[999;999H←[6n
←[email protected]:/ # fsck_msdos -p -y /dev/block/vold/179:9
fsck_msdos -p -y /dev/block/vold/179:9
** /dev/block/vold/179:9
Can't open: No such file or directory
8|[email protected]:/ #
I can gain root access but thats it Have tried run cmd as Administrator, same results...
running Win 8.1
I can't seem to type anything after typing adb shell su
Code:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell su
[email protected]:/ #
at this point, I'm typing away on my desktop keyboard and nothing is happening. of course when I disconnect the phone or when reboot it, all the crap I typed while at the superuser promt appears.
what am I doing wrong?
same error
[email protected]:/ # fsck_msdos -p -y /dev/block/vold/179:9
fsck_msdos -p -y /dev/block/vold/179:9
** /dev/block/vold/179:9
Can't open: No such file or directory
for both commands
tried a few adb drivers just in case
any suggestions?
heisenberg said:
there aren't any discrepancies in this tutorial. If you pay attention those commands are being given to the connected android device via adb, that's why they're linux commands, because they're being issued to a linux device.
Transmitted via bacon
Click to expand...
Click to collapse
────────────────────░███░
───────────────────░█░░░█░
──────────────────░█░░░░░█░
─────────────────░█░░░░░█░
──────────░░░───░█░░░░░░█░
─────────░███░──░█░░░░░█░
───────░██░░░██░█░░░░░█░
──────░█░░█░░░░██░░░░░█░
────░██░░█░░░░░░█░░░░█░
───░█░░░█░░░░░░░██░░░█░
──░█░░░░█░░░░░░░░█░░░█░
──░█░░░░░█░░░░░░░░█░░░█░
──░█░░█░░░█░░░░░░░░█░░█░
─░█░░░█░░░░██░░░░░░█░░█░
─░█░░░░█░░░░░██░░░█░░░█░
─░█░█░░░█░░░░░░███░░░░█░
░█░░░█░░░██░░░░░█░░░░░█░
░█░░░░█░░░░█████░░░░░█░
░█░░░░░█░░░░░░░█░░░░░█░
░█░█░░░░██░░░░█░░░░░█░
─░█░█░░░░░████░░░░██░
─░█░░█░░░░░░░█░░██░█░
──░█░░██░░░██░░█░░░█░
───░██░░███░░██░█░░█░
────░██░░░███░░░█░░░█░
──────░███░░░░░░█░░░█░
──────░█░░░░░░░░█░░░█░
──────░█░░░░░░░░░░░░█░
──────░█░░░░░░░░░░░░░█░
──────░█░░░░░░░░░░░░░█░
1. Go to build description
2. Press 4 times to unlock Developer menu
3.Enable Debugging and OEM unlock
4. Plug USB cable to PC with ADB installed
5. Do ADB Devices and verify that your unit has a serial number
6. at the ADB prompt, go ADB shell
7. Make sure you have a Arm7 "su" inside your ADB folder.
8. At the adb shell prompt, type "[email protected]"
9. Type "su" , you should see "alps5000#"..that means you have superuser privileges now
10. type "remount"
11. type "exit"
12. type "adb push su /system/bin"
type "adb push su /system/xbin"
type "adb push su /vendor/bin"
13. type "adb chmod 0677 su /system/bin"
14. type " adb shell setenforce 0"
15. type " adb reboot system"
Now check if you have permanent root when the unit reboots..
codecxbox said:
7. Make sure you have a Arm7 "su" inside your ADB folder.
8. At the adb shell prompt, type "[email protected]"
9. Type "su" , you should see "alps5000#"..that means you have superuser privileges now
10. type "remount"
11. type "exit"
12. type "adb push su /system/bin"
type "adb push su /system/xbin"
type "adb push su /vendor/bin"
13. type "adb chmod 0677 su /system/bin"
14. type " adb shell setenforce 0"
15. type " adb reboot system"
Now check if you have permanent root when the unit reboots..
Click to expand...
Click to collapse
Or you can just install TWRP and root it in one go from there
problem with the FF-5000 is that system and vendor partitions are read only..you can upload twrp but youll get cannot modify errors..you need to unlock and remount these partitions first with the passworded su and then you can modify with twrp..the 9213ja is another type of software, its already userdebugged from stock, its partitions are already R/W from factory
Why complicate things so much OP? A much simpler way is to install TWRP recovery and then root, ViperFx and anything else u might want.