ok so i have done lots and lots of research on this because as it turns out you need the android sdk for just about everything.. i dont know if it is just me or im not reading sumthin correctly or i jus dont understand but i read the instructions over and over agen on how to install this dam thing and it never works.. can somebody please help me intall this?
Lot of people install it so it does work. The trick is uninstalling the windows driver and replacing it with the adb driver. I assume that's what you want to use. "Install" I think is the wrong word to use, because you don't install anything in the sdk except the driver.
cd to the path of adb.exe in the command prompt. The inital command is 'adb devices' it will show the serial number so you know the phone is detected.
i type that in the cmd and it just says list of devices attached then theres nuthin attached to it.. i read through the instructions on the android website several times and all it really tells me about getting the sdk is adding the full path to the tools\ directory path.. i did this and then what do i do after?
Did you activated "debugging" in USB-Options?
on the phone or on the pc? i have it turned on on my phone but if that is even possible to do on a pc then no i dont...
Related
Hello, I install the android SDK correctly and install all correct drivers, all correct files from the google repository, and reading on unlockr, you need to type CMD and enter a few commands, the final one being ADB devices, which is meant to bring up your device serial/id but doesnt show nothing for me, i deleted all drivers with a program, and it re-installs them, I put the phone into debug mode too, but whatever i try, i cant root my magic (32B), please help!!!!
i have followed every single guide but cant blooming root my phone!!!
HELP!!!!!!!!
Hi guys.
Sorry for this noobish post, but i cannot remember for the life of me on how to install things by using 'adb' - i know there is an option on the phone, but where bouce is it? I used it when rooting, but i just cant find it.
I'm trying to install a new boot image, but when i go into cmd i type "adb remount" and the reply is "device not found"... AndroidSDK is in my C directory.
Another EDIT; I just rebooted my device into the recoverymode, and i didn't see ndroid back up thing, does that mean my phone hasn't actually been rooted... - But my phone is deffently debranded.
Thanks if anyone can help my noobish style.
Slim.
When in recovery mode you must have the driver installed. If you enter 'adb devices' it should give you the serial number of your device, if the driver is installed correctly.
To enter the recovery menu you must run the recovery-windows.bat from modaco if using windows or a similiar file (recovery-linux.sh, recovery-mac.sh) according to your operating system. The file should be run when in recovery-mode or else it returns a whole bunch of errors.
Awesome, thanks mate. Just what i needed! Could i have advice what driver i need to be able to acsess the adb?
I just use the driver supplied in the newest version of ADB.
You can get it here. usb_driver.rar
Or else just install HTC Sync from htc.com. It also has the driver files needed.
Remember to have USB Debuging enabled from the Programs/Development menu.
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Try this
shug24 said:
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Click to expand...
Click to collapse
Try resetting your phone and your computer then try again
like a reboot? that hasn't helped yet...
yeah exactly- hmmm try re-installing the drivers
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
shug24 said:
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
Click to expand...
Click to collapse
you have to get the drivers through android sdk
(with phone usb connected)
device manager
Android Device
right click
update drivers
click browse my computer then next and then click install
if it doesnt give you that option let me know
okay I am having problems there. First, it doesn't recognize an android device, it says unknown device and it won't take any drivers I have followed the pdanet steps, and I have tried the galaxy s drivers with no luck...
okay there is your problem now we are getting somewhere,
do you have android sdk
if yes do you know how to install packages
I have tried this on two 64bit machines and one x86 the one I am on now.. and can't get it to work. I feel like a total newb but this is not a new thing to me ( rooting/unlocking etc) I have had a g1 since the release, then a nexus one since release and just got the nexus s yesterday and have struggled with this one..
what do you mean by install packages, and I appreciate your help
okay no problem it took me a bit to figure it out too.....there arent samsung drivers for this phone they come straight from google through android sdk. im assuming you have it and im going to assume its in this directory if you did eveything right with your n1
c:/androidsdk
in the directory there is a file called SDK setup.exe open it
once it opens do yourself a favor and click cancel dont ask why just do it
now thats out of the way there is 5 options on the left pane of the android sdk window click settings.
then at the bottom of that window is a box under misc. by force http..make sure its checked
then on the left pane goto then available packages
click them all to save yourself trouble and then on the bottom right install packages
let me know when thats done
doing it now - not sure if this helps or not but I had done this last night on a different pc - unfortunately that is at home and I am on my work laptop right now.
and... done.
okay now go back into the device manager and right click on unknown device
update/re-install/install whichever it says then when it asks search or browse
BROWSE
c:/androidsdk/googleusb driver
and watch the magic happen
okay a few things: first it says e: now for the phone under portable devices second, there is no google usb drivers, so I tried it just under the AndroidSDK folder and all the following and it said:
The best driver software for your device is already installed. WPD Filesystem Volume Driver
thoughts?
go back to the sdk setup.exe expand the boxes under available packages and read me what you see
is this where you are asking me to display from? http://www.twitpic.com/3gwnus
OR here: http://www.twitpic.com/3gwo9i
let me save you the trouble
unzip cut and paste to your androidsdk folder
http://www.multiupload.com/Y3T61793BP
yes and paste the file i sent you into that folder
now it still says the best driver is already installed...
uninstall your phone
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
so i transferred my music from my laptop to my tab, but while looking at my music on the tab it all of a sudden exits and asks me to either force close or report. Anyone have any idea why this could be happening? I thought all was good once i got the files to tranfer, but then this happened...
could you try reproducing the issue with logcat running?
Sure, would you mind explaining how to do that though? Not wuite sure what logcat is... Appreciate all the help! Hope to get this squared away.
yeah, I figured I would have to do that but I hate writing out instructions just to find out that the person already knows everything I had to say.
I'll write this assuming you're using windows.. hopefully that's not a mistake
this may be a lot more work than you're willing to do and it may not give any useful results. you're certainly more than welcome to try it though.
for a much easier, but less helpful method, skip to the end.
first, install the adb driver. there is a link floating around somewhere to just the driver, but I can't find it so you're probably better off just installing samsung kies. this will install the drivers for you.
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
then, you'll need to download the android sdk.
http://developer.android.com/sdk/index.html
download it, open the sdk manager and then let it install it's stuff. all you really need is "Android SDK Platform-tools, revision X." I believe the most recent revision is 5, but it doesn't really matter.
now, open a command prompt. in windows 7, you can just hit start and then type cmd. in xp or vista I believe if you have to use start->run or windows key + r, then type cmd and click run.
from here, change directory to the platform tools folder of your sdk. most likely something like this
Code:
cd C:\Program Files\android-sdk-windows\platform-tools\
though it will depend on where you installed your sdk
now go into settings->applications->development and check "usb debugging" on your tablet. after that is done, connect it to your computer with usb and type
Code:
adb devices
if something shows up, your device is recognized. otherwise.. ask for help, I guess
finally, type
Code:
adb logcat -c
adb logcat
and then try to reproduce the error. this will give you tons of information about what's going on in the system. hopefully, it will give you some idea why it is crashing.
Note: the "-c" will clear all previous logs
now, for the short version.
In the android market, download "Android Terminal Emulator"
attempt to reproduce the error then open the terminal emulator and type
Code:
logcat &
this will show you all logs since the last reboot, assuming you haven't cleared them with "logcat -c." It might be a good idea to use "logcat -c" before you start trying to reproduce the error.
hope that helps,
Sam
First of all cant thank you enough for trying to help out. So i went with the second option as to limit my chances of having to ask more questions...yeah about that. With option 2 i could not run the "logcat -c" and after reproducing the error and running "logcat &" i get a permission error... Ideas? Thanks again!
hard to say, man.. what does the error say exactly?