For anyone having an issue with installing TWRP and FFF on a mac here's my two cents on how to help.
Make sure you have the sdk, as well as platform-tools downloaded.
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, but find the correct mac fastboot.exe.
Once you've done all of this, here's what you need to do.
Go to the rootzwiki, or the XDA threads for doing TWRP and FFF on linux. Once you get there, follow ALL of the directions. HOWEVER if you haven't set ADB up with directories( i think this is what it's called) you'll do a little difference.
instead of doing cd Path to ~/androidsdk/platform-tools (or whatever you have your SDK named as) you are simply going to remove the Path to and run it as
cd ~/androidsdk/platform-tools
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
I honestly have NO idea why I have 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, 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.
I hope this helps the other mac users I'm sure are here that 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!
It's not a mac thing, you just aren't getting the directories right. Find where you put in in Finder, note how you got there. Once you get a terminal prompt, you need to go to that directory or add it to your PATH.
The easiest place to put the SDK directory is your user directory. In Finder, on the left side, find your username. Copy the SDK directory there. Then your terminal prompt should open to your user directory. Do an "ls" and you should see it listed. "cd" into it, then into platform-tools. Now you should be ready to go.
Once in platform-tools, do "./adb" and it should spit out a bunch of help text. If not, something is still missing. Note that the "./" is required.
Related
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
Click to expand...
Click to collapse
Go into the directory and see if there is a file called adb in there...if it's not check the other folders like tools or something like that i'm at work so i don't know the exact name of the directories...
duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This is a PC error message stating that the file adb.exe is no longer in the AndroidSDK directory. As zervic mentioned, check and see if the file adb.exe is in that directory.
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
duckredbeard said:
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
Click to expand...
Click to collapse
Just reinstall (or unzip if I remember right) the Android SDK into that directory
I started the "update all" in the "installed packages" window. If that doesn't fix it, I shall follow your advice.
Edit: The "update all" didn't fix it.
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
duckredbeard said:
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
Click to expand...
Click to collapse
Just so you know that may be a little unstable. It may be worth your while to check the "platform-tools" folder and see if adb is in there, i believe that's where it is by default and it also may be worth your while to run adb from that folder instead of where you jerry rigged it to run. But, on the other hand, it may work the way you have it. You never know. Just figured I'd throw that out there.
While rooting my Nook Color, I came across a recommendation for a free app in the market called adbWireless.
It's AWESOME! No need to use USB or worry about drivers, just install the app, push the big huge button and then type the adb command it shows you to connect to your device. Worked absolutely perfectly on my Nook... haven't tried it on my Aria, but next time I need to ADB something on it, you can bet I will!
did anyone check their tools directory?
ie: C:\android-sdk-windows\tools
LOL
Been trying to get Unknown Sources on my phone for the better part of 2 weeks. Have tried everything I can find on google, tried SuperOneClick, and tried the guide on here at least 10-15 times. http://forum.xda-developers.com/showthread.php?t=867637
There are a few replies in the guide i just linked where people are having the EXACT same errors I am but said it was fixed by manually running the script...
I know NOTHING about scripting and have no clue what it means to manually run a script. Anybody know another way to do it or can anybody explain to me how to manually run the script?
I know this is a highly noob question but i'm out of choices. As I said I've done EVERYTHING i know how. Been working to the point that I now hate this phone.
When the poster mentioned running it manually they were talking about using adb to push the altered files to the correct location. That's what I had to do to get it working since the script didn't execute properly.
you have to take the settings.db files out of the zip at the end of the first post and put them in the same directory as your adb.exe (depending on your OS this could be in a few locations). Note you don't want to push the same settings.db to both locations, there are 2 files. The file structure of the zip file matches that of the phone so you just need to drill down into the zip file to find the right files.
adb push settings.db /data/data/com.motorola.android.providers.settings/databases/
adb push settings.db
/data/data/com.android.providers.settings/databases/
So by using
Code:
adb pull /system/ [destination folder name]
I can pull every file off of my android phone's foreseeable memory, correct? Every time I have flashed or pushed anything through ADB, I never quite understood where things were located or what exactly I'm doing. I feel like pulling every file/directory off of the phone will give me some insight into how the hierarchy works, especially being able to browse it with a GUI.
Am I correct, or is there something I'm missing?
I'm not familiar with adb, but a file explorer is an easy way to poke around the file system and learn where things are. Just don't go on a deleting spree and you'll be fine.
epic4GEE said:
I'm not familiar with adb, but a file explorer is an easy way to poke around the file system and learn where things are. Just don't go on a deleting spree and you'll be fine.
Click to expand...
Click to collapse
I have done that, was just kind of hoping for a better GUI alternative. I'm much faster with a Mouse and Keyboard than I am with a touch screen.
Although attempting to pull a directory has resulted in an interesting problem - when using the command above, it doesn't pull all the files. It pulls some and then stops. Any idea why?
From your PC, type 'adb shell'. Now you're logged on to your phone in an interactive session with a shell prompt, and can explore from your PC terminal window.
It's linux, so you'll have to learn some linux commands, if you don't know them already. For exploring the filesystem, 'cd' and 'ls' are the main ones you'll need.
Sent from my mind using telepathitalk
dwallersv said:
From your PC, type 'adb shell'. Now you're logged on to your phone in an interactive session with a shell prompt, and can explore from your PC terminal window.
It's linux, so you'll have to learn some linux commands, if you don't know them already. For exploring the filesystem, 'cd' and 'ls' are the main ones you'll need.
Sent from my mind using telepathitalk
Click to expand...
Click to collapse
Hmm, well I've used adb shell before. Wasn't sure what to do from here, though. Will all linux commands work or just some?
rjhall said:
Hmm, well I've used adb shell before. Wasn't sure what to do from here, though. Will all linux commands work or just some?
Click to expand...
Click to collapse
I believe all the basic commands will work.
cd, ls, mkdir, rmdir, rm, ect,ect.
I like Droid Explorer:
http://de.codeplex.com/
looks like and works like Windows Explorer, lets you browse both the "phone" storage (system, etc) and the sdcard. Pure GUI.
When I try to cd to any of my directories on my phone, it says access denied. Do I need root? And is there a way to manually gain root with the Epic 4G? I tried the whole one click root BS, it doesn't work - just freezes. I'd rather do it manually anyway, but I can't seem to find a single guide with a comprehensive file list! None of the stickies seemed to match what I was looking for either, or the links were dead.
I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.
hello
i just see how to root KF and it's so hard !!
i don't know how to use ADB
This seems pretty helpful in figuring out adb
http://forum.xda-developers.com/showthread.php?t=502010
When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.
http://rootkindlefire.com
Watch the YouTube video or do the step by step method. You do need to download Android SDK and install an USB driver as well. Took maybe 15 minutes all together
Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)
I just did it following this guys video. Quality is great and so are the instructions.
Shows:
-how to install adb
-how to edit the appropriate files
-how to root KF with superoneclick
http://www.youtube.com/watch?v=f409qNgpzSA&feature=related
mewshi said:
When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.
Click to expand...
Click to collapse
I'll second this. It's extremely simple and straight forward. Much simpler than the Windows method if you're at all comfortable with the command line. And as the OP said you don't even need Linux installed you can use a live CD.
Sent from my HTC Flyer P512 using Tapatalk
sum182 said:
Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)
Click to expand...
Click to collapse
This is what I had to do basically.
I created a folder android, and wouldnt let me name it .android
So in command prompt i renamed it, then I put an empty txt file, renamed it to the necessary ini, pasted that line they tell you and it worked first try.