Related
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?
Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this
I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.
hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..
Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!
Mod. edit: not dev related, moved to general
Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help
well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3
Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"
Terminal: "adb remount", then push again
damn the next bad message "remount failed: Operation not permitted"
You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927
Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me
You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279
now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to
You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled
Okay thank you very much.
now it was successful
One thing I've noticed is there isn't a lot of documentation for getting set up and unlocking your bootloader on a Linux OS. Setting up your machine to get adb and fastboot to recognize your device takes a tiny bit of extra work on a Linux operating system, but what exactly needs to be done may not be clear to everyone. Whether it's because you're new to the Android SDK/adb, somewhat new to Linux, or can't simply can't seem to find the Vendor Code for the Nexus S. (For those who are looking specifically for this, it's '18d1', and I assume will be the same on all Nexus devices to come; If this means nothing to you right now, read on.)
Disclaimer: I take no responsibility if something goes wrong (if it does, it should be fixable though), Unlocking your bootloader voids your warranty (but you can lock it back), Unlocking the bootloader will wipe your entire phone, including USB Storage; so make a copy of all those family photos and other files you may have put onto the USB storage if you want to keep them.
For the sake of sanity, this guide assumes you are using Ubuntu. If you're using something else (or different applications), there are terminal commands offered, and you probably have an idea on how to adapt the given instructions to your Linux OS.
Preparation: Installing the Android SDK, ADB, Fastboot & Setting Up Your Nexus S to be Recognized
1. Download the Android SDK for Linux: http://dl.google.com/android/android-sdk_r08-linux_86.tgz
2. Save it in a folder of your choice. I chose to keep it in my Downloads folder, myself. If you'd like, you can rename it to the simpler name of 'AndroidSDK.tgz'. The rest of the guide will assume that you did, because I'm lazy, and it makes things simpler; it will also assume you saved it in Downloads. If you feel that you have the intuition to rename and edit the path names based on your own choices, then fine; but if you're utterly lost here, just stick with what I'm doing; download to 'Downloads', rename to 'AndroidSDK.tgz'.
3. Now that you have it, navigate to the folder you downloaded it to, right-click, and click 'Extract' to unzip it. If for some reason you cannot do this, open up a terminal and try this command:
Code:
tar zxvf /home/<your-user-name>/Downloads/AndroidSDK.tgz
You may have to adjust the command if you didn't save it under Downloads or didn't rename the file to AndroidSDK.tgz.
4. Now, we'll install adb and some other software packages by starting up the Android SDK and AVD Manager. Start it either by:
- Navigating to your AndroidSDK folder, going to the 'tools' folder and double-clicking the file called 'android'; if a popup opens asking you what you want to do with it click 'Run'.
- Using this command:
Code:
/home/<your-user-name>/Downloads/AndroidSDK/tools/android
5. In Android SDK and AVD Manager, click on "Available packages". Check the box next to "Android SDK Tools, revision 8" and "Android SDK Platform-tools", and click on "Install Selected" then "Install". When prompted click "Yes" to restart ADB.
6.You should now have a folder in /home/<your-user-name>/Downloads/AndroidSDK/ called "platform-tools".
7. Download fastboot here: http://developer.htc.com/adp.html
- Save it to the aforementioned platform-tools folder.
- Now, navigate to the file, right click it, click 'Properties', go to the 'Permissions' Tab and check 'Allow executing file as program'. Alternatively, run this command:
Code:
chmod +x /home/<your-user-name>/Downloads/AndroidSDK/platform-tools/fastboot
8. Now to set things up so adb and fastboot recognize your Nexus.
- Type this command into a terminal:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
- Paste this into the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
- Click save and close.
- Then, type the following terminal command:
Code:
sudo restart udev
9. Almost done with preparations! Run this command:
Code:
gedit .bashrc
And add this line to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Then save the file and close.
10. Download this file and save it to /home/<your-user-name>/Downloads/AndroidSDK/platform-tools: http://www.mediafire.com/?4pe5y906zr67nfh
10.We're ready to go!
Unlocking the Bootloader on your Nexus S and Rooting
Once again, unlocking your bootloader wipes everything on your device, including USB storage. Make a backup of any files you want to keep.
1. On your Nexus S, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
2. Power off the phone, and then hold down the Volume Up button and the Power button simultaneously to get into Bootloader/Fastboot mode. Connect your Nexus to the computer via USB.
3. Run this command to unlock your bootloader: (Once again WIPES EVERYTHING!)
Code:
fastboot oem unlock
Hit Enter and on your phone you will be prompted to confirm the action. (Use Volume +/- buttons to choose, power button to confirm choice) Confirm. At this point you will have an unlocked bootloader.
4. Copy/paste the following into the Terminal window:
Code:
fastboot flash recovery /home/<your-user-name>/AndroidSDK/platform-tools/recovery-clockwork-herring.img
5. Use the Volume +/- buttons to choose the Recovery option, then press the power button.
6. In Recovery, go to 'mounts and storage' and choose 'mount USB storage'.
7. Go to this page: http://forum.xda-developers.com/showthread.php?t=682828
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Link As..." Save that file to your desktop and then copy it to the main directory of your mounted phone.
8. Click 'Unmount'. Go back to 'mounts and storage' and choose 'mount /system'. Then Go Back and choose 'install zip from sdcard'>'choose zip from sdcard'>su-2.3.6.1-ef-signed.zip
9. When it's finshed installing, reboot. You are now rooted.
Special Thanks
Amin Sabet; I used your Mac guide as a reference and copy/pasted some things for convenience.
Koush; For first posting the unlocking information, developing ClockworkMod Recovery, and ROM Manager. You should probably hook him up with a donation. https://www.paypal.com/us/cgi-bin/w...63663d3faee8d9384d85353843a619606282818e091d0
Michael.B.; for suggesting adding the platform-tools folder to the .bashrc file.
Linus Torvalds; Without which we'd have neither Android nor Ubuntu.
Feel free to leave your comments on the guide below.
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools directories to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Click to expand...
Click to collapse
Be sure to update your username above.
Thanks a lot man, great guide. I didn't get my NS yet but this is gonna be very useful soon
ps: someone please stick this
Michael.B. said:
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
Be sure to update your username above.
Click to expand...
Click to collapse
Thanks for the tip. I added your tip and instructions for marking fastboot as executable.
Stuck due to the thread's usefulness
I forgot to ask: will this work for 64 bit systems?
nicholasbgr said:
I forgot to ask: will this work for 64 bit systems?
Click to expand...
Click to collapse
It should work just fine.
Thanks, got me rooted nice and quickly.
BlackOtaku said:
It should work just fine.
Click to expand...
Click to collapse
Yes but don't forget to install 32 libs.
Thanks for guide
Useful !
I'm waiting for cyanogen ROM so i'll able to install
Cheers
To confirm, yes it works on 64bit. I am running that
Thanks for the confirmation, guys
Good stuff, much appreciated.
I'm working on a simple shell script that should automate some of the more menial tasks while holding the user's hand through the process. I should have it up later today.
UPDATE: It's up! Link on the first page.
Sent from my Nexus S using XDA App
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
confiq said:
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
Click to expand...
Click to collapse
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
confiq said:
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
Click to expand...
Click to collapse
You shouldn't flash the recovery in the boot partition, I think that will cause problems with the phone period. :S
If you flash a custom boot.img (which this guide doesn't cover, though the script will flash Superboot) or kernel like Paul's Superboot, Supercurio's Voodoo Kernel, or Koush's insecure boot.img, OTA updates will fail to install. OTA updates will also reflash your recovery back to stock. One of the devs around here will probably start modifying them so they don't check the boot.img or reflash the recovery though.
Thanks for this! Worked perfectly
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
matroska said:
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
Click to expand...
Click to collapse
To fix the problem, before selecting zip file, you have to select mount /system. Then go to apply update.zip and proceed as usual.
Thanks
ok im stock
with this part fastboot oem unlock ware i put this code in my terminal of my pc ,,i put the cell in fasboot , i intall everiting if i put that code in my terminal
bash: /home/toshiba/.bashrc: line 2: syntax error near unexpected token `('
bash: /home/toshiba/.bashrc: line 2: `export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools# ~/.bashrc: executed by bash(1) for non-login shells.'
[email protected]:~$ fastboot oem unlock
fastboot: command not found
[email protected]:~$
what can i do or im doing wrong
I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
The last SDK Platform-Tools for Win, Linux and Mac you can always find here - https://developer.android.com/studio/releases/platform-tools
Arhive:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
sorry for being a noob and asking for another device in a different forum,
but will these adb drivers also work with nexus 4???
need them to sideload 5.0.1
IS this for android 5.0 GPE?
http://forum.xda-developers.com/htc-one/general/guide-windows-8-1-fastboot-adb-t2970692
i have anaged to get it working after expereincing the problems stated here by others ... follow my steps here for those who still have trouble
lewonsky said:
IS this for android 5.0 GPE?
Click to expand...
Click to collapse
Yes, this for all version. It' latest update from official Android SDK Platforms.
See link in OP.
Golv said:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
Click to expand...
Click to collapse
I think you forgot to mention that this is only for Windows. So it does not work for Linux or Mac.
Quick, fast, no frills, just the necessary files itself. Hopefully this thread gets updated whenever a new release comes up
thanks, nice share bro :good:
how to use those files
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
open a command window and change directory to the folder where adb.exe is installed. Then you can use adb commands. Commands syntax is as follow:
Code:
adb [target] <command>
You only need to specify the [target] if you have more than 1 android device or emulator connected simultaneously, otherwise the command will be directed to the only connected device, so the syntax will be:
Code:
adb <command>
So if you want to sideload a rom to your device, boot in your custom recovery and start the "sideload" mode.
In the command window:
Code:
adb sideload my_rom.zip
Don't forget that the rom.zip must be in the same folder where adb.exe is
If you want to use "adb push" instead of "adb sideload" then boot in custom recovery (not in sideload mode) and use the following command:
Code:
adb push my_rom.zip /sdcard
You can read more about adb commands here: http://developer.android.com/tools/help/adb.html#issuingcommands
adb sideload explained here: http://android-revolution-hd.blogspot.in/2013/12/ow-to-use-adb-sideload.html
If you have more question about what file to sideload or push a rom to your device, you should ask in the correct forum, Amazon Fire HD 6 forum is here: http://forum.xda-developers.com/fire-hd
thank u
save my day
How do you install the new adb 1.0.32 over the old version and will it work with the moto X 2014?
its dosnt work for me
and i need it ((
every phone i want use sideload , its say me , use adb 1.0.32 or newer
and when i want use adb 1.0.32 , show me this error in all adb commands :
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
what should i do ?
update adb
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
go to this website: https://fl1.androidfilehost.com/dl/...803384/minimal_adb_fastboot_v1.3.1_setup.exe?
download and install it to your computer, then try to sideload it through there.
if that doesn't work just download the stand alone SDK from the android studio website and after its downloaded, open the .rar file and extract it to a new folder to your desktop. after that open it and search for a folder that says platform tools and look for the ADB .exe file and copy it, then go to your C drive and go to programs and try to find the android studio folder, when you have located it open it and look for a folder named platform tools, then delete the adb.exe in that folder and paste the new one in there or you can probably just copy the whole platform tools folder and replace the other one in the C drive.
I hope this helps, if it doesnt just message me and im sorry for the late reply.
alishadlou said:
* failed to start daemon *
error: unknown host service
what should i do ?
Click to expand...
Click to collapse
this usually means the phone is not communicating with your PC.
- either your phone is corrupt
- the connection is corrupt
- or the cable is bad
Tip: add the path of ADB.exe to your system Environment Variables, so you can call it w/out first navigating to it.
- Right click Computer > Properties > Advanced system settings
- Environment Variables ... > edit "Path" by adding the path to ADB.exe.
ie.
Windows 10 x64, i simply add: D:\PortableApps\ADB
for other Windows, you may have to add to the end of "Path", click edit > scroll to the end > add ;D:\PortableApps\ADB;
(don't forget to add the semicolon at the end)
Now you can simply launch Command Prompt and enter: ADB sideload *file*
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
Not working on Android 6.0
This and older versions will not work on Samsung S7E for system backup and restore.
It accepts the commands, but the confirmation popup supposed to open on the device never does. For a few 6.0 users on other devices, it opened up but the backups were not really completed.
thanks bro. nice share :good:
Thanks, you save me too much time!!
my adb was working fine for my Note 4. I followed the instructions to upgrade bootloader
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Now, I keep getting device offline when used adb devices command. Do you think, upgrading ADB will solve this? thank you