For anyone having an issue with installing TWRP and FFF on a mac here's my two cents on how to help.
I am in no way responsible if you mess something up, you are voiding your warranty, ninja's will attack you, and some other **** about how I'm not liable if you mess up your device.
NONE OF THIS IS MY WORK, ALL CREDIT IS TO JCASE.
THIS IS WHAT WORKED FOR ME ON MY MAC, IT MIGHT NOT WORK FOR YOU, I CLAIM NO RESPONSIBILITY IF IT DOESN'T WORK FOR YOU.
Now,
Make sure you have the sdk, as well as platform-tools downloaded. If you don't know how to do this, go into your sdk, and read the files in there, it will tell you how to download platform-tools.
Once you've downloaded these things, you're going to need the correct fastboot.exe for macs (rename this fastboot.exe, will probably come as fastboot-mac.exe), I don't remember where I downloaded it, nor do i want to break any rules or piss any people off by posting where, but find the correct mac fastboot.exe through google or some other means.
Once you've done all of this, here's what you need to do.
THIS IS NOT MY WORK, I TAKE NO CREDIT FOR IT, IT IS ALL JCASE'S WORK, NONE OF MINE. ALL I AM DOING IS ADDING HOW TO GET TO ADB, FOLLOWED BY THE FEW THINGS YOU NEED TO ADD BECAUSE IT'S A MAC VS. LINUX.
Go to JCASE's thread on rootzwiki, or here, and it will give you the guide. It's his guide, not mine, just add the things I mentioned and it might work. It did for me.
FOR ROOTING:
now you need to first navigate to your platform-tools folder in your android sdk folder using terminal.
Go to utilities in the applications tab in finder. Open up Terminal.
Now type the following line to navigate to the platform-tools folder.
cd ~/androidsdk/platform-tools
for me it is this because my SDK folder is named "androidsdk", if your's is named differently, insert it's name where androidsdk is.
followed by that you can start using ADB. Instead of running things as
adb root, or adb reboot, you need to include
./ before the commands, IE: ./adb root, or ./adb push
IE THE FIRST STEP IS "adb root", rewrite this is "./adb root"
from then on, include that ./ before any command.
____________________________________________________
FOR FFF AND TWRP:
THIS STUFF IS ALL THE WORK OF THE AUTHORS OF THE POSTS AS WELL AS THOSE WHO DID TWRP AND FFF, NOT MY WORK, I'M SIMPLY ADDING WHAT WAS REQUIRED FOR THE GUIDE TO WORK ON MY MAC.
Go to the thread for FFF and TWRP for Linux.
Start off the same by navigating to the platform-tools folder as stated above.
Now when using the SUDO command in the guides for linux for installing FFF or TWRP you will write the commands as:
"sudo ./fastboot" followed by the rest of the command.
INSTEAD of "sudo fastboot"
_____________________________________________________
I honestly have NO idea why I had to do everything this way, from what I remember it has to do with directories or something, but either way it's what fixed everything for me.
Don't consider this a guide or anything I simply added what I was missing for the linux guide to work on my mac, as I don't want to be someone who people blame if it didn't work for them, as I'm simply doing what works for me. AND in the end, this is all Jcases work, and those who wrote the guide for TWRP and FFF linux installs.
I hope this helps the other mac users that I'm sure are here and are struggling, cause I had to remember how to do all this stuff before I realized why I was ****ing up doing all this stuff.
Good luck!
Or just use this: KindleWater
Related
Is it possible to complete the whole process on a mac? I don't have a PC.
i found this.
http://www.droidfilez.com/Evo4GRoot.html
dont know what it is/how it works though.
proceed at your own risk.
yes, all you need to root is adb!
download the adb sdk for mac and use the terminal app in utilities to execute adb commands
after you set up the sdk execute the commands, like the examples :
./adb devices
./adb shell
./adb push
just follow the guides to root and wheerever it says to use adb use ./adb instead because your on a mac.
hope you got the jist of what im saying
i wouldnt use the above post "automated rooter" just yet... you're new to this, you should research mroe about the automated rooter and if it does what it says it does. wait till it comes up on xda?
EDIT : follow the guide that waterboy100 posted below if you want to do it without adb. i would encourage you to learn adb though as its simple and will help you learn more about rooting in the long run.
this guy should have a post up soon too
http://forum.xda-developers.com/showthread.php?t=701152
chim4ira312 said:
yes, all you need to root is adb!
download the adb sdk for mac and use the terminal app in utilities to execute adb commands
after you set up the sdk execute the commands, like the examples :
./adb devices
./adb shell
./adb push
just follow the guides to root and wheerever it says to use adb use ./adb instead because your on a mac.
hope you got the jist of what im saying
i wouldnt use the above post "automated rooter" just yet... you're new to this, you should research mroe about the automated rooter and if it does what it says it does. wait till it comes up on xda?
EDIT : follow the guide that waterboy100 posted below if you want to do it without adb. i would encourage you to learn adb though as its simple and will help you learn more about rooting in the long run.
Click to expand...
Click to collapse
I am downloading the sdk now and I am interested in this. I have the 1st root completed and I am trying to get the second section done and I am having a hell of a time :/
you can totally do every rooting ability in Mac. I got a hackintosh and downloaded the ADB kit and just plug in the phone and ADB recognized in an instance. No need to install driver like Windows.
I just did the rull NAND unlocking with root on my Mac.
Awesome I downloaded the files and I'll try doing it today. I wanted to remove some Sprint Apps and maybe flash a ROM later one when the builds become more solid and bugs get worked out.
By the way I'm playing Pocket Empires to kill time and it's pretty cool. If I root will I have to start the game all over again?
i've done everything on my mac...works great!
I'm lost as hell. I found this thread:
http://www.androidpolice.com/2010/0...-write-permissions-to-system-incredible-next/
I did the unrevoked thing and I see this icon called SuperUser Permissions in my app list.
Am I able to proceed and fully root or do I have to re-do the root with the Toast method? This looks too complicated and by the way I tried the ./adb thing on my mac and I get errors saying "No such file or directory".
im trying to push the pcimg to sdcard and its saying access denied
Why do you guys say "Oh, I did it on my mac" without saying HOW you did it on your mac? Regular instructions dont work so you obviously did something special to make it work... I keep getting permission denied BS
Here you go dude. Step by step instructions along with the download links. I followed this to the T and it worked out find for me:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
So, I have had an EVO since day one, loving it, but have held out on rooting, especially since I am on a mac, and applied the recent SW updates.
I have read most of the threads on how easy it is on a windoze machine, but can't seem to find any easy, step by step instruction for doing it on a mac..
Am I a douche, or did someone post detailed instructions for this already?
I JB'd all my Iphones, and am an advanced geek, so I am not afraid to try anything..
thanks all!
This method should work for you, provided you know some adb basics. Both are linked below:
forum_xda-developers_com/showthread_php?t=718889
forum_xda-developers_com/showthread_php?t=694250
Edit: Sorry, I cant post links. Replace the _ with . please!
I rooted my evo on my mac. Just download the android sdk for mac. Copy the files that you need to your memory card as it says in the guide. Then open a terminal, type cd and then drag the tools folder from the sdk to your terminal. You should be in the tools directory on your terminal. Then just drag the adb file from the tools directory to the terminal. Now you can use adb commands. I followed the windows guide. It works the same way. There is no need for adb drivers to be installed. It just works on mac. Hope that helped. Sorry, I'm not the best at explaining things.
Section 5 from this guide may be an easier read.
forum_xda-developers_com/showthread_php?t=721055
Where he says paste "adb-windows shell" just paste "adb shell" instead and it should work. I don't have a mac so im not positive tho :/
./adb shell
thanks guys, these are good tips!
Ive tried the black prince video, the unlockr method and the original xda perm root guide and my G2 will not perm root. Seriously need some help.
do you have adb and sdk installed?
>
no such thing!
its just smarter than you (;
lol
it is funny that you mention the black prince video, because that is what i used. im not sure, but i followed that video exactly and got it my first try. just watch the video very carefully, and follow EVERYTHING that he does and it should work. if not, then i am really not sure. obviously, you just need "S-off"
Are you using Visionary ? I would suggest the rage method, IMHO it's a lot more reliable and you can see if anything goes wrong because you're using individual commands.
i know its possible because I rooted my friends G2 just days before I got mine. I don't have adb, to be honest as soon as i see that it takes more than just installing a program on my pc, i flee, and its not because im new to android or rooting or anything like that, i just don't have a whole lot of spare time. And i DO have S-OFF. Like ill do everything in the blackprince video, then after I'm done I'll got and test the root by typing SU in terminal, and it says permission denied. Or for any of the other methods, same thing.
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
adamtheindien said:
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
Click to expand...
Click to collapse
Download HTC Sync from the HTC website (look in the downloads section), and install that on your PC. That'll give you all the USB drivers you need.
Download the Android SDK from http://developer.android.com/sdk/index.html and install it on your PC. Be sure to read the guide on installing it at http://developer.android.com/sdk/installing.html
Plug your phone in to your PC using the original HTC cable (do not use a third-party cable for this) and type "adb devices" at your PC's command prompt, and tell us if it can see your phone. It should show up your phone's serial number (don't tell us exactly what that is, this is a public forum), but if there's an error then we need to sort that first.
Edit - partially prompted by this request, I've started an "adb for Noobs" guide (very much a work-in-progress) at http://forum.xda-developers.com/showthread.php?t=865685
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
http://www.youtube.com/watch?v=A1SOSXwkc_8
adamtheindien said:
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
Click to expand...
Click to collapse
when you type adb devices does it recognize your device?
Super easy way.... http://forum.xda-developers.com/showthread.php?t=834228 just copy paste the codes.
Your phone might be s-off, but not allowing you to do any su commands. Mine was, but I just installed rom manager and it flashed clockwork recover no problem, then I flashed cyanogen and everything was good. Go into hboot and just make sure it says s-off, then do the rom manager bit. Try it and see if it works.
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
yeah, but i cant use rom manager since i dont have super user permissions. do i just temp root then try to install a rom? that seems sketchy. haha.
Earlier you said that you have S-OFF. If this is the case, then just open up Market and download Superuser by ChainsDD. Then you should be good to go.
adamtheindien said:
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
Click to expand...
Click to collapse
When you type "adb" on your PC, Windows needs to know where to find the "adb" program to run it. So you either need to specifically add the directory containing adb to your Windows PATH variable (which you can do in the environmental variables section, which will be in different places on different operating systems - on XP you need to right-click on My Computer, then select Properties, then Advanced, then the "Environmental Variables" button) - or you need to cd to where adb is stored under where you installed the Android SDK, and run it from that folder.
pretend youre explaining this to a five year old...
ok, which operating system do you have on your PC ?
Where did you install the Android SDK, i.e. which folder on the PC did you put it in ?
never mind guys, did what that dude said and just installed a rom with temp root and im all good now. thanks for everyones help though, sorry for my lack of knowledge in adb and what not.
The guides/walkthroughs seem to cover windows but I use OS X...are there any guides/walkthroughs to root a G2 using OS X?
I'm getting frustrated
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
dadewy said:
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
Click to expand...
Click to collapse
I am following this guide
steviewevie said:
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
Click to expand...
Click to collapse
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
bobbytomorow said:
I am following this guide
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
Click to expand...
Click to collapse
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
gee one said:
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
Click to expand...
Click to collapse
That helped me out perfectly, I just rooted my G2, YAY!
Thank you everyone for your help
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.