Related
I dont know if this is the correct forum for this and i dont know if it has been posted before but hey, what the heck, as long as i can help out.
If you don't use Windows or adb has no problem with your device,
you can skip this.
If your G1 or HTC Magic is not properly recognized by ADB under
Windows, then your prayers are answered.
The bottom line: Make sure to enable Home > Settings >
Applications > Development > USB debugging on your G1 or HTC Magic
*before* you plug it in Windows the very first time.
If you read this after the fact, googling why "adb doesn't recognize
my device under Windows", here are the steps to fix it:
This concerns both the G1 and HTC Magic and all flavors of Windows. I dont know if it works for any other devices out there but its worth a shot.
1- Remove existing drivers
2- Plug your phone
3- Open the Device Manager
4- Remove any driver for [ADB Interface > HTC Composite ADB
Interface] and [Disk Drives > HTC Android Phone USB Device] if you see
them
5- Unplug phone
6- Edit the registry (Disclaimer: be careful what you do in regedit. If you're not sure, then do not proceed to fix your issue and get a someone who is more knowledgeable than you are at this.) Open the Registry Editor (Start > search/run > regedit) You *may* need to be administrator to do this.
7- Search for "vid_0bb4&pid_0c02" in keys or values. (This may take a
while. If you find it in a value, delete the whole key folder.)
8- Some keys may be "locked" and you will not be able to delete the keys. If this happens right-click the folder where the key is located and add "everyone" with "full control" permissions. Then delete the key folder.
9- Repeat the search till no more instances are found.
10- Close regedit.
11- Before your plug in your phone, Make sure to enable Home > Settings > Applications > Development > USB debugging on your G1 or HTC Magic
12- Plug the phone in. Windows should now ask you for a driver. (Do NOT selected to search the Windows Update. Instead select "I
will choose a driver" or the equivalent.)
13- Make sure to give the *full* path to the x86 or x86_64 driver, e.g: C:\SDK\usb_driver\x86\ or C:\SDK\usb_driver\x86_64\
If you just select "SDK/usb_driver", Windows will take the wrong
architecture and complain the driver can't be installed.
I hope this helps anyone out there.
For Droid 2's on Gingerbread, click link below to find info to Root your phone
http://www.droid-life.com/2011/09/0...roidx2-droidx-and-droid3-running-gingerbread/
One Click Root Version for Linux and Works for Mac, too!
This is still a work in progress! Gonna call it 3.3 (I went through 3 previous versions). It takes the 2.2.1 version and adds a user interface. Nice, easy, clean. In order to run this script, you need to chmod (change permission) of the .sh file, and then execute it.
Download the file here: http://kimete.com/droid/beta/dorootv3.sh
It is good for both Linux and Mac. All you have to do is execute it and the script will download all the appropriate files for you!
How to run this in Ubuntu/Linux
How-to video here: http://www.youtube.com/watch?v=gvlB3e_UE8I
Note: General idea. You no longer need to update android-sdk, though.
1. Download the file.
2. Right-click the file, choose properties, choose the permission tab, and check executing file as program, close window
3. Double-click the file, choose Run in Terminal, and it'll start.
4. Choose 1 for install and root. Choose 2 for root process only. Only good if you've rooted using this method before, or you need to reroot your phone. Choose 3 to unroot. Choose 4 for credits/donation information. Choose 5 to exit. Choosing other numbers...
How-to for Mac
How-to video here: http://www.youtube.com/watch?v=d7s8dtfYyHI
Note: General idea. You no longer need to download and install android-sdk anymore.
1. Download dorootv3.sh. Best to put it on your desktop.
2. Open a terminal. Go to the magnifying glass and type in terminal, and then select it.
3. Next, you need to change permissions. Type in the terminal chmod 0755 followed with a single space. Then drag the dorootv3.sh into terminal.
You should see something like this chmod 0755 /user/(file path)/dorootv3.sh. Press enter.
4. Now run your file by dragging the file into the terminal again and pressing enter!
5. Now choose and option...
New version of rooting for Linux and Mac! Version 2.2.1!
Linux 2.2.1: http://www.kimete.com/droid/beta/DoRootLinux_221.zip
Mac 2.2.1: http://www.kimete.com/droid/beta/DoRootMac_221.zip
General Instructions:
1. Extract the files.
2. Change the permissions on the doroot.sh file
3. Run doroot.sh file.
Instructions for Linux and Mac
1. Extract the respective files to somewhere accessible. Your home directory or desktop is idea. The file comes in a .zip file. Just open it up and drag and drop the DoRootMac or DoRootLinux folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the folder in terminal.
example: [cd /DoRootMac or cd /DoRootLinux]
4. enter [chmod 0755 doroot.sh] then run it [./doroot.sh]
5. Let it run.
6. That's it, you are done.
One Click Root for Windows
Here's the Windows version. Facelessuser pushed this through and worked his magic. Give it a try. Very exciting stuff. I haven't used it yet, but according to him, it should work!
Download here, Ver. 2.1.4:
http://www.kimete.com/droid/beta/DoRootWin_2.1.4.zip
Instruction for Windows:
How-to video here: http://www.youtube.com/watch?v=B7RGVikpQ8o
1. Extract the folder from the DORoot zip file to your desktop. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom righ, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot.bat
5. Let it run.
6. That's it, you are done.
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Many thanks to facelessuser for working his magic!
====
====
How-to Videos
Video of the Rooting Process for D2 and DX by [email protected]
For Windows/Mac/Linux
http://www.youtube.com/watch?v=u5l3MDomDSc
Video of the Rooting Process for D2 and DX by DarkOnion
For Windows
New: http://www.youtube.com/watch?v=B7RGVikpQ8o
Old: http://www.youtube.com/watch?v=gzlg9a-H42w
How to use the ADBDL.sh file by DarkOnion
For Mac and Linux
http://www.youtube.com/watch?v=9cHpGXfEudM
=====
=====
Frequently Asked Questions
Why does my anti-virus tell me that the files contain Trojan's?
The files are exploits and hack your phone. Don't worry, they are clean. However, to be safe, do not download from any other source than the ones linked in this post.
I've gotten countless hate mail and comments on Youtube users about rageagainstthecage-arm5.bin being detected as a trojan. It is an EXPLOIT. If you are scared that the files I hosted are going to give your computer a virus. Look else where, like Z4Root, though, my understanding is that Z4Root also uses rage.
http://forum.xda-developers.com/showthread.php?t=853704
What is do these files/programs/scripts do?
These scripts will root your Droid 2 or Droid X phone with the least amount of user input as possible.
Why should we use this method and not another method?
All the methods are based off the same process/procedure. If you feel like doing MORE work, we can't stop you. The reason why we wrote all these scripts is to expedite the process, make the procedure easier, and to reduce human input which reduces the chance of human error.
Is there anything I need to know in order to successfully root my phone?
Yes. READ THE DIRECTIONS. Read the directions first. A lot of people make errors because they don't read the directions. I've also provided links to my video and another video which outlines the root process. Both are only a few minutes long.
Root failed! What do I do?
Run the script again! Most people succeed on the first or second try. Usually the rest by the third try.
Do I have to install Android SDK and update it?
It depends. The new Linux/Mac version does not require you to. The windows one, we are still working on.
Does this work on other phones?
I can't answer that. I know it works for Droid 2 and Droid X.
Wait a minute, this isn't really one-click! What's the deal?
Deal with it. Don't like it, try the 25+ step process.
When I open up the Superuser app, I get a blank screen.
That is NORMAL. Superuser lists the processes/applications that you've allowed superuser access to. If you haven't allowed anything, then it will be blank.
How do I test if I have root or not?
Try downloading an app like Wireless Tether (published by Google), and running it.
What USB connection mode do I set my phone to?
PC Mode or Charge Only. Choose the one that comes up with USB Debugging.
I am not very good with computers. Is this something I can do?
Oh yes! The key to success is following the directions.
How do I update Android SDK?
On Windows, you just need to double click the SDK Manager.exe. On Linux/Mac, you need to go into terminal, navigate to the tools folder in the android sdk folder, and run this command ./android update sdk. More information can be found in the SDK Readme text file. On Windows, double-click and run the SDK Manager.
I am getting stuck at the "daemon not found/daemon is starting" part. What do I do?
You need to fumble with the settings on your phone. You don't need to close the terminal. Change between PC Mode and Charge Only mode until it starts to continue. If that still doesn't work, also try disabling then enabling USB debugging for each mode.
=====
=====
Reporting an Error or a Problem
You can report errors right here in this thread. Make sure you give us as much information as possible. List what operating system you are on, what phone you have, at what part of the script you had errors, and anything else you may have tried or done. The more information you provide us, the better we understand situations. Posting up pics or logs of the terminal is extremely helpful.
=====
=====
Change log for 1-2-3 Root
Version 0.0 - 25+ step tutorial on how to root D2 on Windows and Mac
Version 1.0 - Initial scripts to streamline processes and reduce user error in Ver. 0.0.
Version 2.0 - Streamline of multiple scripts into 1 script. Minimal commands. Minimal work. With error checking and reporting.
Version 2.1 - addressed issue where remnants of a previous root would not allow root to complete
Version 2.1.1 -
-Cleanup code.
-Address issue where I thought I was killing a hanging rage, but I wasn't (It was a syntax thing)
-Fix for ERROR6 or ERROR5 (this was drastically different than what I did in windows. I wasn't returning exactly a string in format I thought when doing the check, so I had to do some ridiculous stuff to process it.)
-Better error resolution. (more error checking)
-Refined unroot.
-Reboot if you had files from a previous root
-Now the script will automagically download needed root files if they are not in your folder. (If you are behind a proxy, make sure your mac or linux has curl or wget configured for proxies respectively)
-Longer wait before remount (I had it not remount because it was busy once)
Version 2.1.2 -
Linux and Mac
Contains everything windows 2.1.1
Unroots non bootstrapped phones too
All
Contains option to unroot
Version 2.1.3 - Added dounroot.bat
Vesion 2.1.4 -
-Fix bug where people were getting a false ERROR5 because they already had Superuser.apk
-Hide killing of busybox before unroot
Version 2.1.4 - Files are standalone. No need to download Android SDK anymore.
Version 2.2.0 -
-adb included, no SDK needed
-abort if cannot find adb
-remove alternate busybox at /system/xbin and /system/bin when unrooting
-remove alternate busybox at /system/xbin when rooting and installing busybox at /system/bin
-No more hang in exploit...I hope
-Clean up code
Version 2.2.1 - minor revision to code (curl related)
DarkOnion's DoRootv3
Version 3.0 - set-up menu's, added error checking, will detect which OS you are on
Version 3.1 - fixed issues with ADB SDK User interfaces
Version 3.2 - adapted to DoRoot 2.2.1
Version 3.3 - edited code for easier understanding and modifications
=====
=====
References:
Original procedure produced by Sebastian Krahmer
http://forum.xda-developers.com/showpost.php?p=7838000&postcount=1
Tutorial/How-to Root Droid 2 on Windows by DarkOnion
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
Tutorial/How-to Root Droid 2 on Linux/Mac by DarkOnion
http://forum.xda-developers.com/showpost.php?p=8103311&postcount=340
====
====
Appreciate my work and/or help, feel free to send donations my way! Poor college student here who just got a speeding ticket! Doh!
This is outdated information and should be used as a reference only! All updated versions have moved to POST #1.
Hi all. Made it to the front page of XDA Developers.
http://www.xda-developers.com/android/easy-rooting-method-for-droid-2/
I just want to make sure credit is given where due. First of all, the original procedure was produced Sebastian Krahmer. From there I wrote an indepth tutorial to root the Droid 2. I took a vague instruction set and help it grown into something that the average person could understand. Understanding the need to simplify the process, I decided to write scripts to further streamline the process. What started out as a 3 part script that involved 8 or 9 commands eventually became a two part script that involved 3 or 4 commands. I have no programming background, by the way. Having trouble getting the process down into one part, facelessuser volunteered to take my work, and put a bunch of neat things into it to get it to work as one thing with error checking! So, with that said, I'd like to thank everyone that had a part in the project, especially facelessuser for his dark magic arts that made the script run, matt4542 for constantly testing my various scripts, and everyone who directly or indirectly ran the scripts!
We are moving forward!
===
Hi all.
We (me), facelessuser, and a few others are working furiously to get an easy one step program out for you guys. In the mean-time, I have a pretty safe, and clean, and easy 2 step method for Windows, Mac, and Linux. I am still cleaning stuff up, but for the most part, it all runs well.
What you need:
Android-SDK for your operating system which can be found here:
http://developer.android.com/sdk/index.html
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
And the files/scripts/programs to root for your OS:
Want to try the one step process, go down to post #2!
Windows [1.0]: http://www.kimete.com/droid/DORootforD2Windows.zip
Mac/Linux [1.0]: http://www.kimete.com/droid/DORootforD2Linux.zip
Instruction for Windows:
GO DOWN TO POST #2 AND DOWNLOAD THE ONE STEP
1. Extract and Update Android SDK package to your computer. The file comes in a zip file. Just open it up and drag and drop the android-sdk-windows folder to your C drive. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom right, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot1.bat
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes before it boots you out.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthecage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to DOS, enter or double click doroot2.bat
8. That's it, you are done.
Instruction for Linux and Mac:
GO DOWN TO POST #2 AND DOWNLOAD THE 1-STEP!
1. Extract and Update Android SDK package to your computer. The file comes in a .tar.gz file. Just open it up and drag and drop the android-sdk-linux folder to your home directory or desktop. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the tools folder of your android-sdk
[cd /android-sdk-linux_x86/tools]
4. enter [chmod 0755 doroot1.sh] then run it [./doroot1.sh]
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthe cage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to command prompt, [./doroot2.sh]
8. That's it, you are done.
Enjoy my works? Want to show your gratitude? Just want to help a poor college student out, donate via PayPal to: [email protected]. All donations are greatly appreciated. Money will be spent on escorts, food, adult beverages, higher education and its bs fees, paying off my phone, and the wonderful speeding ticket I got this week!
Hey Thanks alot for writing this! I just tried it out and ran until completion.
A few things I found.
In the dos prompt, part2 the program asks user to input a few commands. Commands 2 and 3 should end in .sh. The program dosent mention this.
Thanks again
Typo in the 3rd step. You forgot to add '.sh'.
lockdownx1x said:
Typo in the 3rd step. You forgot to add '.sh'.
Click to expand...
Click to collapse
Doh. Good catch y'all. I will take care of that now!
Problem
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
The " ./ " before doroot.sh tells linux to look in the current directory for the file to run. Make sure you in the tools directory of the sdk and that the script is there as well.
Sent from my DROID2 using XDA App
Yep i definitaly made sure of that but same error. It doesnt matter though i have rooted my droid 2 through the manual proccess
NiteSite said:
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
Click to expand...
Click to collapse
Did you do cd data/local/tmp in adb shell before doing the chmod and ./doroot2.sh?
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
NiteSite said:
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Weird. I am going to send you a PM. Hit me up on Google Talk.
-Kevin
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
mjones1052 said:
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
Click to expand...
Click to collapse
I am working on it. Hahaha. I don't have any programming background. So I am learning on the fly, but progress is being made.
Though, I have to say that the process is much much much easier than what it originally began as. So... moving in the right direction.
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Kenny Strife said:
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Click to expand...
Click to collapse
Just follow the instructions. Launch the doroot1.bat file. The .bat file will launch you into ADB shell. chmod the doroot2.sh file, then run it. adb shell again. chmod the doroot3.sh file and run that. Hope that helps. I am on google talk if you need help.
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
please help!
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
chrismouro said:
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
Click to expand...
Click to collapse
You are okay. Superuser lists the program you've allowed superuser access to. You haven't given any apps access, therefore blank!
Kenny Strife said:
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
Click to expand...
Click to collapse
Kenny, did you get this resolved? I am experiencing the same issue.
I'm getting kicked the ./doroot2.sh: not found as well. Anyone get past this point?
Linux users please go HERE (thanks to bloodychaos)Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
UPDATE: Not necessary for Windows 7 is installng adb drivers automatically after plugging the device and fastboot ones after rebooting the connected device to bootloader. To get the HTC USB Drivers on different Windows version download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
fonpacific said:
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Click to expand...
Click to collapse
Method 3:
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Good Idea!
Have put a link to this within the GUIDES section of [INDEX][22 SEP 11] ROMS/RECOVERY/ROOT/HBOOT/RADIOS/TWEAKS/GUIDES/etc
I believe that the guide would be more useful if you put in a link to a URL for the HTC Drivers and moved the advice about enabling USB Debugging to the top!
I can now point people at this guide rather than manually instruct them, Thank's you probably just saved me loads of time and aggravation!
Nice Work, Great Help
Excellent! Exactly what I needed. Thanks for showing us this.
Hi an thank you. Good guide.
I believe one important information is missing in the guide:
Before installing the HTC drivers (or HTC sync) it is necessary to temporarily disable AntiVirus software on Windows machines. If you don't do that, Windows won't recognise your phone. After the installation is finished, enable AntiVirus again.
I got this advice somewhere and it was true for me personally. I'm using Windows 7.
Sent from my HTC Desire S using XDA App
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
mimirom said:
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
Click to expand...
Click to collapse
It's very useful, Thanks!!
Doing all this the phone has to be turned off, on, or power button and volume down?
Desire S said:
Doing all this the phone has to be turned off, on, or power button and volume down?
Click to expand...
Click to collapse
You do not need a phone for this guide It is setup for PC
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
This is exactly the purpose of point 4 of the guide (global path setup)
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
bonesy said:
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
Click to expand...
Click to collapse
Agree, added to the first post.
Sent from my Desire S using Tapatalk
Instructions for Linux users???
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
On my Linux system I have installed Java and the whole Android SDK and the set the path of course. If you are a Linux user you should know how to do this. Also there are guides for other devices that are basically the same
amidabuddha said:
Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive (Mirror @MediaFire) or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
Method 3:
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Click to expand...
Click to collapse
Nice work mate
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
OP edited - there is a link to a guide for Linux users
fonpacific said:
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
Click to expand...
Click to collapse
Thank you for the remark, I hope it will help the users with the same problem
Hey Guys, I need help!
after an installation of adb all I get is error:device not found
i entered a code adb shell and hit enter, than i entered
dmesg | grep mmc0, since you cannot put two lines of code at once (I'm a rookie)..
where did I put it wrong?
I can get to recovery of my device, but I get error like:
/I]E:Can't open /cache/recovery/command
I made revolutionary S-OFF..
Thanx for a help!
Rocks
You have to enable USB debugging in the settings.
And while in recovery it should work too
Sent from my HTC Desire S
Hey guys, this is my first post, so if I did something wrong, don't strangle me.
In this guide, we're going to use djrbliss's Motochopper tool. The download will be attached, as I can't place outside links.
As said in the title, this will work ONLY on the AT&T i337 and Verizon i545.
This root WILL work on Linux/Ubuntu, Windows, and Mac.
Step 1. Go to Settings->More->About device then hit “Build Number” about 5-10 times until you see “Developer mode has been enabled” message.
Step 2. Next hit the Back button and you should see a new option called “Developer options”, hit that option.
Step 3. Make sure Developer options is checked ON and also check “USB debugging” ON.
Step 4. Connect a micro-USB cable from your Galaxy S4 to your computer, you should see a “Allow USB debugging” window pop-up on your phone, hit OK. If you don’t see it yet, just skip this step and check back on Step 7. Sometimes this won't show up, but it should.
Step 5. Mac and Linux users can skip this step, because you don't need to install drivers. Windows users: go to Device Manager on your computer and make sure you have something like “Samsung Android ADB Interface” or some type of “ADB Interface”. If you don’t see it, you don’t have Galaxy S4 USB drivers installed, download and install Galaxy S4 Windows drivers. (The link to the drivers is attached in a file, because I can't post outside links, yet)
Step 6. Download Motochopper.zip (attached) and unzip, you should find a bunch of files in it.
Step 7. For Windows, double-click on “run.bat” to start the rooting script.
For Mac or Linux, go to terminal/cmd (whatever you have), and type:
cd Downloads/motochopper
cd motochopper
chmod 755 *
sudo sh run.sh
Step 8. On your keyboard, hit "enter" to begin the rooting process.
If you skipped Step 4, you should now see “Allow USB debugging” window pop-up on your phone, hit OK.
Make sure to hit “Agree” on your phone if you see a “Verify apps?” window pop up during rooting.
Step 9. When the process is done, hit enter on your keyboard. The rooting process will finalize and reboot your phone.
Congratulations, your phone is now rooted!
To make sure it worked, go to your app drawer, and look for an app called "Superuser". If it's there, your phone is rooted!
Now, you can download apps that have "root" in their names in the Play Store.
Once again, congrats for your new rooted phone! Have fun!
If I helped you with rooting your GS4, please hit the thanks button! :victory::laugh:
*can't wait until the bootloader is unlocked* Btw, this is my first Android, so cheers!
This thread already is covered here http://forum.xda-developers.com/showthread.php?t=2283918
Always read search and study before you post duplicate material. But thank you for the guide.
Thread Closed
Hi everyone, I would like to share my experience regarding two methods that I have used to revive a Nexus 5 whose power button just will not work. Please use this guide if your Nexus 5 dies due to a low battery and you want to boot (start) it without power button. Following methods have been successfully tested on Win 7 and 10. You can use this guide and keep using your Nexus 5 without repairing the power button. There are other guides and posts which can help you attain locking, unlocking of the screen and remapping the hardware buttons such as volume keys to perform as a power button.
Method 1
Step 1: Download adb/fastboot binaries or use Android SDK for adb/fastboot. If downloaded as a zip, extract it in a folder. It is better to download adb/fastboot minimal, as it is small and can be handy.
Step 1a: Download your phone drivers and install them. If it is a zip folder then extract it in a folder for later use.
Step 2: Plug in the micro USB in your phone. Hold both volume keys on the phone and while holding the keys plug the USB cable in to your PC’s/laptop’s USB port. Your phone will reboot in Bootloader mode where you will see START written at the top of your phone screen which is the prompt to start the system but you cannot select it, as your phone’s power button does not work.
Step 3: Open Command Prompt in windows, which is cmd . Navigate to your adb/fastboot folder which you created while extracting the zip or you might be able to use the commands from anywhere in command prompt if you have installed Android SDK.
Step 3a: Commands only work if you installed adb/fastboot correctly or you are in the binaries folder. While in the corresponding folder,
Type: fastboot devices
123456789 fastboot
The command will show devices connected in fastboot mode just like the above example
If your phone does not appear here then go to control panel>device manager search for any unknown device such as unknown device or android device ; Right click on it and choose update drivers. Do not select the auto search for updated drivers. Select browse my computer for driver and then browse to the folder where you had extracted the drivers choose the right folder and windows should install your device as android bootloader interface device.
Once installed properly, you should see your device by typing the above command again. When successful
Type: fastboot reboot
Now your phone should reboot and start normally.
Method 2
Step 1: Download Wug's Nexus Root Toolkit by Wugfresh.
Step 1a: Download your phone drivers and install them. If it is a zip folder then extract it in a folder for later use.
Step 2: Plug in the micro USB in your phone. Hold both volume keys on the phone and while holding the keys plug the USB cable in to your PC’s/laptop’s USB port. Your phone will reboot in Bootloader mode where you will see START written at the top of your phone screen which is the prompt to start the system but you cannot select it, as your phone’s power button does not work.
Step 3: Run Nexus Root Toolkit. Let it complete its initialisation and when done its main window will pop up on your desktop. If your using it for the first time it will ask for your phone model and android version. Input the details appropriately, if you do not know the android version you are running choose any build which is at the end of the list.
Step 3a: The toolkit might ask for any dependency files to be downloaded, which it will download automatically. You might be able to skip it but if you use any build or wish not to download them but it won’t harm if you download them as you might wish to use the toolkit later.
Step 4: After completing the above step. Toolkit will finally be ready to use. From the main window of toolkit click Launch under the Advanced Utilities.
Step 5: Choose Reboot System and your phone will reboot normally.
If Toolkit returns, No adb/fastboot device found then follow the next step.
Additional Step: Go to control panel>device manager search for any unknown device such as unknown device or android device ; Right click on it and choose update drivers. Do not select the auto search for updated drivers. Select browse my computer for driver and then browse to the folder where you had extracted the drivers choose the right folder and windows should install your device as android bootloader interface device.
Once drivers are installed, go to Step 5 and it should work for you.
The above methods have been used on Nexus 5 and might be helpful on other Nexus or completely different devices from other brands
For Mods: I have done my good faith search before making this guide. Please let me know if a similar guide exists or I have posted it in a wrong place.
If it has helped anyone please consider a Thanks. By the way it is my first post.
For downloads, please use search engines and you will be happily served.
No responsibility is taken, whatsoever.