Okay. I have been trying to do other things with rooting other phones. I've rewritten a exploit so it will work on Mac. But this is a general problem. I deleted the Emulator and every single thing but the platform-tools on the windows side of my computer. So the only thing I have on my computer is the platform-tools folder (aka fastboot and adb) So I have tried what almost every forum has said. The adb kill-server. I restart it. Still there. I've tried to individually kill it still there. I've unplugged my device and ran adb still there. This is one reason that stopped me from rooting on a windows because this stupid emulator won't go away and it never has. I've never ran eclipse on the windows side or to say that never anything but the adb and fastboot. Only the Mac side have I done other things. Please if anyone could help that would be nice. It'd save me time from having to take the .bat files and changing them to sh files and opening with text edit, editing the file to work with terminal, then sh install.sh run the file and it not work then back to the drawing board which after rewriting some stuff over and over is a miracle to see it finally execute the exploit. Thanks for any help. I would gratefully appreciate it. Thanks. Sorry this kind of a off topic thing. O yeah that is the other reason from keeping me going s-off to. It's annoying and I would really love to fix the issue. I will take any advice. Just saying though the adb kill-server and a lot of other commands are not working and not doing the process. Please anyone who would like to help. Just put anything :$ Please and Thank you.
Related
Since i'm bored, i wanted to experiment with ADB, i know what it is, and what happens on it.
I've never used it, but i want to start
i just downloaded android SDK
idk what else to do, i searched ADB on the windows search thing, but i get 3 results, 1 is from something else, and another when i try to open says adbwinapi.dll is missing from your computer. try reinstalling the program to fix this problem.
i can't find adb on the folder i downloaded, whats wrong?
can someone tell/link me to a step-by-step instruction?
Sorry nobody got back to you sooner.
ADB is usually hidden in the android-sdk-windows\platform-tools folder.
I'm not sure which file you extracted yours to, but I extracted mine to C:Android so my path in cmd looks like C:Android\android-sdk-windows\platform-tools>
Once in there type adb and hit enter for a list of commands. Connect your phone and type adb devices to see if it can find it etc.
Good luck. You can really F stuff up with adb.
Not sure where else there are tuts but I learned from the ADB for dummies tut in the G1 development section (when I had my G1).
I would link but I'm on my phone and can't figure out how/if it can can be done w/ the app. Just go to the informative links sticky. Theres lots of basic android info there. Some translates to vibrant some doesn't. But good reading nonetheless.
Good luck
XDA Mobile
Can use terminal emulator to run adb commands.
can someone pm me, or we can facebook IM to get adb working
i've been flashing roms since i had my mytouch 3g and even then, i could not get it to work. i do not wish to use droid explorer because i am a big kid and wish to know cmd lines to learn more.
here's where i'm at. installed sdk/renamed/placed into root of c:
after that i need help. please.
I can get in touch with you tomorrow and really go over it. Once you've got it set up properly, it's simple. I'd help now, but i'm off to the bar!
Until then, this might help you.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
ipetloudog said:
here's where i'm at. installed sdk/renamed/placed into root of c:
Click to expand...
Click to collapse
Your next step would be setting the path variable for wherever the ADB file is in the SDK (the Tools folder). The link I sent covers the path variable. Once you've done that you should be able to open command prompt and type 'adb devices' without the quotes and it will tell you what devices you get. If you get anything OTHER than "'adb' is not recognized as an internal or external command,
operable program or batch file.'" , you've made progress.
Heres the deal. I have a MAC with a newly installed hard drive. On my old hard drive I had everything setup with SDK and Adb but that was when I had an HTC Hero. My problem is this: When in terminal my damn computer keeps prompting me for a password but it doesnt allow me to type anything except control C which aborts the program. It never was like that with the old hard drive.
2. Ive dl SDK for MAC unzipped it and saved it to my desktop and my hard drive.
3. When I click on tools it says "adb_has_moved.txt"
4. It says the adb tool has moved to platform-tools/ and if you dont see this directory in your SDK, launch the SDK and AVD manager and install "android SDK Platform-tools and also update my path environment variable to include the platform-tools/ directory, so I can execute adb from any location. What the heck does this mean and how do I fix it. Also how do I know if SDK is installed correctly.
5. I DL some version of eclipse that was recommended from SDK but I dont know how to use that either.
6. I have tried all the root methods shown here in XDA except the on with the Dock since I dont have a dock.
7. Also ADB does not recognize my device and my debug is selected. I cannot get it to find my device.
8. One last question when some instructions say unzipped and move the root exploit to /data/tmp/ is that the file labeled under sdcard/data or is it the one inside the Android Folder listed as "data"
Please anyone help if possible.
let me try that
Stupid question but How do I launch SDK?
laraiza said:
Stupid question but How do I launch SDK?
Click to expand...
Click to collapse
Make sure your phone has USB Debugging Mode enabled. Otherwise, adb will not recognize your device.
Check this thread: http://forum.xda-developers.com/showthread.php?t=879701
However, you will have to modify for MAC.
In my opinion the easiest way to root the Photon is still using the dock method. Otherwise, try the One Click Root method (Torpedo) as mentioned above. Then you don't have to worry about issuing all the commands.
I got it done I got it done. What I did was borrow my daughters windows netbook and the one click method worked on the first try. Thanks to all who replied. I will definitely hit your thanks buttons.
Sent from my MB855 using XDA App
im sorry.. my tool was a one click i dint think i needed to give it instructions.. especially teh part of how to run it on your computer... just fyi.. when invoking sudo (to do things as admin/root) on your computer. you are asked to enter in your password.. as a privacy/security feature it will NOT display any characters.. ergo it looks blank...
as you arent teh first one to run into this issue ill add instructions for mac users ( i know anyone running linux can figure out how to run a bash script, and windows users have a bat file after installing 209387249087 drivers... but they still figure it out ;P)
I've tried on windows 7 and Ubuntu 12.10 and no matter what I do,no matter how many times I update the SDK or uninstall and reinstall the SDK,ADB version is still 1.0.29...tried killing server,restarting adb, etc.
Trying to ./extract files from cm10.1 for compiling CM but ADB must be updated to connect to JB devices...
Someone please help!!! I've googled for hours and tried everything..still getting nowhere.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
:SOLVED FOR ME:
so what i did (and i dont know why all of a sudden its working) but,
i opened up the terminal and did the following
lsusb
This should kick out a list of plugged in devices. Most likely the last one is the phone. There were references to Samsung and Galaxy so it was pretty easy to figure out. On that same line, there is an ID number in this format...xxxx:xxxx. Write that number down for reference.
Now a few more commands:
cd
sudo gedit /etc/udev/rules.d/99-android.rules
When the rules open, copy/paste the following with the id "lsusb" gave you:
replace the ####:#### in the above string of text with the number you got from "lsusb"
Then save and exit.
sudo service udev restart
sudo adb devices
# XXXXXXXXXXXX offline
sudo ./extract-files.sh
GOT THE WINDOW POPUP ON MY PHONE
check always accept from this computer
then everything went smoothly....hope this somehow or another helps someone...if it does,please hit thanks.
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
just tried sudo cp ~/android-sdk-linux/platform-tools/adb /usr/bin
it seemed to have copied since the original adb there was like 577kb and the new one is 1.2mb but still same issue.. i dont care to get it working on windows anyways...just thought i was strange it wont work on either platform...any other suggestions??
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
sinner99 said:
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
Click to expand...
Click to collapse
I had to sign up for this forum just to tell you, THANK YOU!!!! For the life of me, it was ridiculous that I couldn't find just simple information on how to do stuff. This is my first time looking into this stuff, So I couldn't even figure out how to update individual tools like that, which is what I've been spending the last 2 hours or more trying to figure it out.
It really was those three files in the Windows directory this whole time. Now my device is online, and adb shows the right version. Amazing. It's absolutely pathetic that google has their program screw up the entire adb functionality by putting these broken versions of the tool in the Windows directory.
I had to add to the path variable the location folder of the appdata platoformtools abd.exe.
I'm sorry if this has been answered already. But I'm having a hell of a time getting ADB to work. I have the latest drivers installed as well as Android dev tools. I connect my G3 to my laptop and put it in "Ethernet" mode with USB Debugging checked off. I open up a command prompt and cd to my platform-tools folder. I then type adb devices. No matter what, it won't recognize it. I've rebooted phone, laptop and even deleted the "adbkey" file to see if that would fix it. Any ideas guys? I'm on Windows 8.1. It's not a huge deal because I can just use Terminal Emulator to execute most of the commands. But it would be nice to have ADB working. Never had a problem with it on my G2.
Fuse8499 said:
I'm sorry if this has been answered already. But I'm having a hell of a time getting ADB to work. I have the latest drivers installed as well as Android dev tools. I connect my G3 to my laptop and put it in "Ethernet" mode with USB Debugging checked off. I open up a command prompt and cd to my platform-tools folder. I then type adb devices. No matter what, it won't recognize it. I've rebooted phone, laptop and even deleted the "adbkey" file to see if that would fix it. Any ideas guys? I'm on Windows 8.1. It's not a huge deal because I can just use Terminal Emulator to execute most of the commands. But it would be nice to have ADB working. Never had a problem with it on my G2.
Click to expand...
Click to collapse
I sometimes have to reinstall the drivers while the phone is connected.
Thanks. I'll give that a shot
Wow, it worked! Thanks so much. I spent hours trying to figure this out :x