Related
THIS IS STRICTLY A GUIDE TO PRE-PARE YOU ON HOW TO SET-UP ANDROID SDK AND ADB DEVICES(DRIVERS), IF YOU ALREADY HAVE THAT SET-UP YOU CAN SKIP TO EUGENE'S POST ON HOW TO ROOT MYTOUCH SLIDE.
Last Updated:6/29/2010 at 11:36PM
Any other issues to deal with the actual process to root your mytouch slide should be directed toward his thread. Thank you for reading.
Okay so after about 4 hours of reading and asking questions I finally got my device rooted. My biggest problem doing this was that the guide in this forum was basically showing you how to root the phone if you had previous experience with androids and android SDK which I did not.
Note: If you have SDK installed already on your pc please delete your SDK folder and start from scratch for best results with my guide.
1. download Android SDK.(You will not have to use Android SDK physically but you will need it installed on your pc to root your phone) Save it to your PC where you can find it.
2.Extact the .zip file, do not rename just yet for the sake of my guide you also may delete the .zip file of it to keep clean.
3a. Move android-sdk-windows* out of the android-sdk_r06-windows folder onto the root of your C:/ drive.
*=the name of the folder may be different if you use a different operating system but since I do not own the other systems I cannot really tell you what the folders name.
3b.Now that you have the folder in the correct place you can rename the folder from "SDK-Anroid-Windows" to something easier such as "SDK" "Android" or something else which you will remember has to do with SDK.
This next part is not required, if you do not feel comfortable doing this, then don't, there is other ways around this.
3c.You also have the option to change your the path of your directory on your system. To do this, follow the instrustion here on step 2.( I would like to thank fermunky for his input)
My directory was pointed to the C:/Program files so I switched it to C:/android/tools , for those who do not know what this does it simply makes it so you do not have to change directory in step 7 (CD), you will only have to open your command prompt and then your ready to enter "ADB devices" .
4.Install the correct ADB drivers from pdanet . Select the proper download based on your OS if you do not know what bit you are using click start, right click computer, click properties, the system type will show you the proper file to download. and save it to your computer where you can find it.
5.Start the installation process for the ABD drivers, Follow the on-screen directions to install the drivers ( make sure your phone is not plugged into the pc at this time)
6.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools**
**=your file directory might be different than this, it depends what you renamed your folder
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.***
***=If it is correctly connected you will see a device listed and under attached it should say device.
After you have this all set up you are ready to root your phone via the guide from Eugene.****Remember you need to add the contents from his root.zip file into the tools of your SDK folder in order to root your phone.
****=Eugene's guide has changed since I wrote this but you still are ready to follow his steps. I plan on rooting someones slide soon based off his steps and will edit here if I need to add anything)
Thanks for reading.
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
the other guide mentions to create a new variable such as:
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Click to expand...
Click to collapse
so would i follow this? or list that directory under the already-enabled PATH variable?
Yeah just use the existing PATH variable, and only need the path, no need to include variable names.
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
For the uninitiated, and yes it's common sense
When I was using Windows (as I'm using Ubuntu now), and reading all the adb guides, for ease of use and to prevent people from getting confused, they name the sdk as "android-sdk-windows", which is fine for a newcomer (it's the same for Ubuntu except the "windows" part and the slash direction \ vs. /). However, you can name it whatever you want. You just need to make sure to have the same name in your path. For example, I'm lazy and my typing skills aren't that great. I don't want to type 19 characters (yes, I counted). So I just named it simply "android". 7 characters from 19. Its way more efficient for me. I've contemplated naming it "andy" or something to shorten it further. But, again, you don't even need to name it anything android related. You can choose to name it r2d2 (see what I did there?) if you want! Just my 2 cents. Thanks!
Yeah I could of renamed it something different but I didn't think about that til after it was written, I will fix it as soon as I am on an actual pc. I will also include how to do it via mac and ubuanta(sorry if I miss spelled)
kingofyo1 said:
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
Click to expand...
Click to collapse
Thanks kingofyo. Glad I could give back to this forum after all it has done for me. And if I find any other helpful tips to help make rooting easier I'll be sure to include it.
Sent from my T-Mobile myTouch 3G Slide using XDA App
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
I will leave that as an option for others to pick if they want to do that, as some might not want to change their directory to follow that path.
oo, this cleared up a few things for me! thanks!
eff0rtless said:
oo, this cleared up a few things for me! thanks!
Click to expand...
Click to collapse
ah what pat of seattle do you live in? I live up in mukilteo.
rlacsamana1989 said:
7.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools (your file directory might be different than this, it depends what you renamed your folder)
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.
Click to expand...
Click to collapse
when typing in 'adb devices', i get this message:
Code:
adb server is out of date. killing...
* daemon started successfully *
however, it does continue to list my device as attached.
the full message is:
Code:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HTxxxxxxxx device
*the x's do represent a valid serial number
-------------------------------------------------------
is this a problem? and will i run into any problems trying to successfully root?
note: i have done a search on this and the results returned as the program DroidExplorer being the culprit, however, i do not have that program installed.
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
rlacsamana1989 said:
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
poetik517 said:
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
Click to expand...
Click to collapse
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
cdt82002 said:
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay my guide is to set you up to root, you need to download slideroot.zip from eugene's how to guide. It will download a folder so you need to save it somewhere you will find it. Once you have it saved extract the files and the files within that folder you need to put in the tools of the sdk directory. Do not just drop the folder as that would change the directory even more to another folder. A file in that folder is what actually makes the loop feature work and there are other things you will need from that folder to root.
And to this. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
you just need to delete "Program Files (x86)\QuickTime\QTSystem\"
and then replace it with your directory to your C:/
rlacsamana1989 said:
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Click to expand...
Click to collapse
a successful uninstall & reinstall of the sdk worked for me. i no longer get the 'adb server is out of date' message when trying to list devices.
when reinstalling all of the packages in sdk, i did note this message:
Code:
'Downloading Usb Driver package, revision 3
Installing Usb Driver package, revision 3
Installed Usb Driver package, revision 3
Updated ADB to support the USB devices declared in the SDK add-ons.
'adb kill-server' succeeded.
ADB: * daemon not running. starting it now *
ADB: * daemon started successfully *
'adb start-server' succeeded.
but its a good thing =]
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
poetik517 said:
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
Click to expand...
Click to collapse
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
usbdeview
rlacsamana1989 said:
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think the program you're trying to remember may be "usbdeview"? This program allows you to disconnect or uninstall drivers.
rooted via ubuntu and have recovery
i tried doing stuff in windows, but it wont install the drivers properly.
SO I NEED HELP!
what do i do to get this to work?
i want to be able to install 3rd party apps and get rid of att bloatware.
i have no idea where to start.
HELP!!!!!!!!!
thanx
ubuntu or windows...
download the Android SDK for Windows
http://developer.android.com/sdk/index.html
install and download ONLY THE USB DRIVERS
open cmd window, connect usb cable, navigate to the <folder>\tools where you installed, ie. c:\android\tools
paste the following into a small batch file, call it anything you want dot bat,
ie. c:\android\tools\yourname.bat
---cut here--
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
-- cut here--
ok i'll try right now
still must be missing something
what setting is my phone on when i plug it in? recovery? or just regular charge only or hard disk mode?
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
when i run that .bat file it says a bunch of things, but basically says device not found.
please start from step #0.
there is no one place that has every single step we need to do.
it makes it next to impossible to get this to work.
dh4645 said:
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
Click to expand...
Click to collapse
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
ocswing said:
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
Click to expand...
Click to collapse
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
dh4645 said:
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
Click to expand...
Click to collapse
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Shad0wguy said:
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Click to expand...
Click to collapse
so what is the point of the sdk...other than to have the tools folder to run that .bat? so i'm the only one that can't get the sdk usb drivers to work?
and by good to go, u mean i can install 3rd party apps?
how do i get rid of the the at&t bloatware?
There are other threads explaining how to install third party apps and remove ATT bloatware.
Sent from my HTC Liberty using XDA App
The problem with trying to do a step-by-step guide is that things like rooting, removing bloatware, and sideloading apps are all separate processes that require different steps and can be done in multiple ways. Some stuff requires you to be in recovery, some stuff doesn't, and other methods may require additional software. That's why there are specific separate threads that discuss them.
You've rooted your phone already, yay! Now you decide what you want to do next. Remove the bloatware? It's important that you don't lump everything together when trying to figure out what you need to do.
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
ocswing said:
....
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
Click to expand...
Click to collapse
thanks for the reply.
yeah i rooted via the ubuntu disc, but then all the other steps people were telling me were using the sdk, getting the drivers, htc sync, yada yada. via windows. so thats the method i've been trying.
is there a step-by-step guide on how to allow 3rd party apps using the ubuntu disc? or... removing bloatware?
is it the same steps, but you just dont have to worry about the drivers?
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
ocswing said:
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
Click to expand...
Click to collapse
ok cool thanks a lot!
i didn't even think to go back to linux to try this stuff until today at work.
i'll check it out later tonight after i mow the lawn and eat dinner....priorities...
i tried in windows one last time. it actually found the htc sync drivers (i in/uninstalled htc snyc earlier...i guess thats what did it)
adb devices command finds my phone, but when i try and run that .bat file, it goes through a bunch of things, but basically says:
remount failed: operation not permitted
failed to copy...
permission denied
all those types of things. then it says to hit enter and then it restarts my phone
???
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
b_atman said:
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
Click to expand...
Click to collapse
i said i did that above...that was the only way i got the usb drivers to work/recognize my phone...the sdk ones didnt work)
my phone is recognized when i run adb devices command
i'm having issues when i run the .bat file as i said in my last post
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
b_atman said:
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
Click to expand...
Click to collapse
uuu, no, whats that?
i thought i just had to open cmd and run the .bat file
so what did i miss now? ha
thanks for your help!
i ran this .bat file
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
I installed the SDK and have run my ADB scripts for my samsung Vibrant before, I got home today and got a "The Program can't stat because AdbWinApi.dll is missing from your computer" error. I uninstalled the SDK and reinstalled it rebooting my computer after each just to make sure. I also tried moving the AdbWinApi.dll file to my Windows/System32 folder along with the Adb.exe.
I am running windows 7 64bit
Core I7 920 @2.67 GHz
6 GB ram
ATI 5750 Vid card
Any help would be great.
Cheers,
i figured it out
download daemon tools. install the free version. close cmd
open cmd
re type your path. and your computer should stop complaining about a missing driver.
This worked for me and i now have full access. hope this helps
Try this.
Shift + Right Click on folder C:\android-sdk-windows\tools, go to command mode option from there, and you should see it coming up with a command screen, type in adb devices with your phone plugged into the computer. If it shows your daemon is killing server, don't kill the window yet. Just wait...
It was meant to do this someway or whatever since I have a custom built PC for gaming and other purposes. I just didn't get the tech nerd answer right away for every problem solved, but it was all from you guys in XDA-developers, so I had this same error from trying to run 'adb' from start panel, and it didn't work because it was telling me my adb was needed to be re-installed and my AdbWinUsbApi.dll was missing from my folder, and It didn't tell me what folder, so I remembered my old way of learning how to run adb for the first time with my device.
Shift + Right Click tools folder from C:\android-sdk-windows as in C:\android-sdk-windows - Shift + Right Click RUN COMMAND PROMPT MODE. It should be fine after running this commands for your devices to show in the list.
type:
adb devices
adb remount - This is if your connected to a device already after.
adb install C:\android-sdk-windows\tools\setcpu.apk - example of your first apk file install.
Running the daemon killing server isn't gonna do anything to your phone like technically ruin it or trash it but its not, honestly, I never seen my phone ruined from this daemon killing server part, so if anyone cared to explained?
alekosy said:
Try this.
Shift + Right Click on folder C:\android-sdk-windows\tools, go to command mode option from there, and you should see it coming up with a command screen, type in adb devices with your phone plugged into the computer. If it shows your daemon is killing server, don't kill the window yet. Just wait...
It was meant to do this someway or whatever since I have a custom built PC for gaming and other purposes. I just didn't get the tech nerd answer right away for every problem solved, but it was all from you guys in XDA-developers, so I had this same error from trying to run 'adb' from start panel, and it didn't work because it was telling me my adb was needed to be re-installed and my AdbWinUsbApi.dll was missing from my folder, and It didn't tell me what folder, so I remembered my old way of learning how to run adb for the first time with my device.
Shift + Right Click tools folder from C:\android-sdk-windows as in C:\android-sdk-windows - Shift + Right Click RUN COMMAND PROMPT MODE. It should be fine after running this commands for your devices to show in the list.
type:
adb devices
adb remount - This is if your connected to a device already after.
adb install C:\android-sdk-windows\tools\setcpu.apk - example of your first apk file install.
Running the daemon killing server isn't gonna do anything to your phone like technically ruin it or trash it but its not, honestly, I never seen my phone ruined from this daemon killing server part, so if anyone cared to explained?
Click to expand...
Click to collapse
Sorry guys
Its been about a week since I have been trying on google, unlockr as well as xda forums for unlocking bootloader for nexus S, and I STILL am stuck at my device not showing up when I type 'adb devices' even though I have tried SDK drivers, PDAnet drivers, etc...countless restarts, countless uninstalls, following each and every method to the letter. The closest I have come is to alekosy's issue above where daemon kills the process as he describes and then, nothing. I keep waiting. Every time once daemon starts, whenever I type adb devices, I only get this 'list of devices attached'...and nothing else. in device manager, device driver shows installed correctly...
I would be heavily indebted to anyone who could show me the light (get my device show up in adb devices and then allow me to root).
Thanks a bunch!
(Frustrated beyond belief!! )
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Thanks espentan. That worked for me.
An easier way
[fastboot does not work, adb works]
No need to fiddle with environment variables. This should do it:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
..\tools\fastboot.exe devices
etc.
Explanation: the dll's (along with adb) were moved to platform-tools. Issuing fastboot from this directory, using '..', which means "up one directory level", with 'tools' then picks up the dll's.
Thank you very,very much....that worked like a charm..after hours of head aches...
twistadias said:
Thanks espentan. That worked for me.
Click to expand...
Click to collapse
espentan said:
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse
That worked for me too. Very easy explanation...!!! Thanks
Alot easier fix, go to google type in adbwinapi.dll and download it.
Put it in sdk/tools
Done
Sent from my SGH-T959 using Tapatalk
alekosy said:
Try this.
Shift + Right Click on folder C:\android-sdk-windows\tools, go to command mode option from there, and you should see it coming up with a command screen, type in adb devices with your phone plugged into the computer. If it shows your daemon is killing server, don't kill the window yet. Just wait...
It was meant to do this someway or whatever since I have a custom built PC for gaming and other purposes. I just didn't get the tech nerd answer right away for every problem solved, but it was all from you guys in XDA-developers, so I had this same error from trying to run 'adb' from start panel, and it didn't work because it was telling me my adb was needed to be re-installed and my AdbWinUsbApi.dll was missing from my folder, and It didn't tell me what folder, so I remembered my old way of learning how to run adb for the first time with my device.
Shift + Right Click tools folder from C:\android-sdk-windows as in C:\android-sdk-windows - Shift + Right Click RUN COMMAND PROMPT MODE. It should be fine after running this commands for your devices to show in the list.
type:
adb devices
adb remount - This is if your connected to a device already after.
adb install C:\android-sdk-windows\tools\setcpu.apk - example of your first apk file install.
Running the daemon killing server isn't gonna do anything to your phone like technically ruin it or trash it but its not, honestly, I never seen my phone ruined from this daemon killing server part, so if anyone cared to explained?
Click to expand...
Click to collapse
Thanks!!!! This helped me after hours of trying to use adb, now it finally works! I just have to right click that folder and use the command prompt that way every time in order to use adb, weird but it works so i'm fine with that. Thanks
Thanks espentan
espentan said:
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse
It worked perfectly for me.
Thanks
espentan said:
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse
nice!
it seems only win7 users have to do the steps while xp do not
espentan said:
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse
This solved it for me
sgtmedeiros said:
Alot easier fix, go to google type in adbwinapi.dll and download it.
Put it in sdk/tools
Done
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
I have done this. It worked perfect. thank you mate!
sgtmedeiros said:
Alot easier fix, go to google type in adbwinapi.dll and download it.
Put it in sdk/tools
Done
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Much easier thanks. Xp here
You don't need to google for it, it's in platform-tools, along with adb.exe
help pls
Guys,
I am getting the same error about the missing .dll file when I try toi install the exe from revolution.
I tried changing the environmental variables, no luck
tried just downloading the .dll from google and dropped it into sdk/tools, no dice!
Can someone please help me to get this to work, have a brand new Sensation sitting here and I can't deal with Sense. Thanks
the error I get when trying to install is of course:
Adbwinapi.dll is missing
GreatWall2 said:
It worked perfectly for me.
Thanks
Click to expand...
Click to collapse
Thanks a lot, this worked for me too... The only thing i changed was the name of the directory from 'platform-tools' to 'tools' cause the file was in there.
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
I would take the time to learn ADB or wait until a one click is out. Learning ADB while rooting your phone could easily break it.
what os are you using?
svalle713 said:
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
Click to expand...
Click to collapse
Honestly just take the time to read the procedure, other help topics on these forums, and take your time when actually going through the procedure.
I had never used ADB either or rooted an android phone for that matter, and I gotta say, rooting the TBolt was cake.
I just took my time with it ensuring I typed in the commands properly.
But if you need a video, here you go: http://www.droid-life.com/2011/03/22/video-rooting-the-htc-thunderbolt/
what drivers do we need for the process, are they only the htc sync drivers? where can these be found?
Android SDK should be extracted/installed straight onto the C:\ directory to make it easy. Open the android-sdk folder and in it is a program sdkmanager.exe, open that and you can reject all of the downloads but scroll down and install one called the "google usb driver package" which may be necessary, I'm not sure (you should also have the htc sync drivers installed)
The contents from the "exploit.zip" should be extracted into the folder "platform-tools" within the android-sdk folder. Plug in your phone to the usb and open the command prompt. To get started open the command prompt (like a dos prompt) and get the prompt into the folder 'platform-tools' and type "adb devices" then hit enter. If your phone is connected and you have "usb debugging" enabled on your phone from the settings, your phone should appear and you can begin the instructions from jcase
Hello all, I've been really happy with my XPS ever synce I've root it and everything is working clockwork, except there is something eating my battery.
I've used "BetterBatteryStats" app, and i've got a parcial wakelock "AlarmManager" in 1st place.
I've read that to know eacly what app is waking the phone i've got to connect the phone to a Pc, run "ADB" and type "adb shell dumsys alarm > C:\alarm_log.txt".
This will creat a log file that will show what app is generating all those wake numbers, and then unistall or limit it.
The problewm is... what is ADB.EXE??? Where can i get that program for the pc? Does the phone have to be in USB debuggin mode? If someone help me I'll post a guide to anyone in need to find the problematic apps that eat battery for others noobs out there!
Here
Sent from my ST25i using Tapatalk 2
As the above is saying you should search n read a lot... there are guides all over in net in many n here xda as well... Its a good start by learning urself from the help already here..
1. ADB is included in SDK here. get it ...http://developer.android.com/sdk/index.html
2. Here is a guide to set up SDK... http://www.talkandroid.com/guides/developer/android-sdk-install-guide/
4. Browse to folder platform-tools adb.exe is inside... but u can't just click open it.. adb is used via command prompt (cmd)
5. Easy way to open cmd to adb is Shift+ right click -> click open cmd here
6. To connect phone in adb u have to enable usb debugging mode as u said..
7.Then start typing commands....
Thank you a lot for the aswer!
I DID goodle for the answer, but I had an hard time undestanding what I should do, I'm a pharmacist, not a technician.
That beeing said, the other part of the info I posted I found using the search funcion.
Anyway, thank you a lot for that answer, I'll try it now.
s-X-s said:
As the above is saying you should search n read a lot... there are guides all over in net in many in here xda as well... Its a good start by learning urself from the help already here..
1. ADB is included in SDK here. get it ...http://developer.android.com/sdk/index.html
2. Here is a guide to set up SDK... http://www.talkandroid.com/guides/developer/android-sdk-install-guide/
4. Browse to folder platform-tools adb.exe is inside... but u can't just click open it.. adb is used via command prompt (cmd)
5. Easy way to open cmd to adb is Shift+ right click -> click open cmd here
6. To connect phone in adb u have to enable usb debugging mode as u said..
7.Then start typing commands....
Click to expand...
Click to collapse
To perform this actions, is it mandatory that phone needs to be rooted?
Because, i followed all the steps, when i executed the command in cmd prompt, i got below info
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/system/bin/sh: dumsys: not found
What should i need to do now if phone doesn't needed to be rooted?
For using adb not necessarily ur phone rooted... but if u need to get anything insdie system folder ur phone needs root access... you can pull/push files from adb.. but it makes more easier if u do those for sdcard via windows explorer after connecting via usb..
In short its for rooted devices mostly.....
Ok, still need help on this one.
I've followed all the steps, installed SDK, phone in development, command line accepted, but then I check the log file I get this:
/system/bin/sh: dumsys: not found
So... Why is it now finding my phone? any idea? When am i supposed to connect the phone to the pc?
Thank you for the help!
Miguel Pereira said:
Ok, still need help on this one.
I've followed all the steps, installed SDK, phone in development, command line accepted, but then I check the log file I get this:
/system/bin/sh: dumsys: not found
So... Why is it now finding my phone? any idea? When am i supposed to connect the phone to the pc?
Thank you for the help!
Click to expand...
Click to collapse
dumpsys, not dumsys. With a P.