Develop Bugs

[GUIDE] Everything You Need to Setup and Use ADB

Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted Android Device
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now,
1. Run SDK Manager.exe located in the android-sdk-windows folder
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r7+
1. Run SDK Manager.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Still not working?
Try this: Get ADB to recognize your myTouch 4G [Thanks importflip]
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.

Even after unstalling the HTC and myTouch 4G Drivers, when I plug my MT4G back in there's nothing to install. It automatically installs what it has to. I have no idea how to connect it with ADB.

I had to do this:
http://forums.t-mobile.com/t5/Operating-System-Software/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017

This is why after the temp root. I used root explorer to move the files to right folder . And then used the terminal app to do the rest. Really no need to use ADB..
Sent from my HTC Glacier using XDA App

Scoop24 said:
This is why after the temp root. I used root explorer to move the files to right folder . And then used the terminal app to do the rest. Really no need to use ADB..
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I did that too but insmod said can not open wpx.ko every time. No idea why, worked perfect on my G2.
Sent from my HTC Vision using XDA App

Arcadia310 said:
Even after unstalling the HTC and myTouch 4G Drivers, when I plug my MT4G back in there's nothing to install. It automatically installs what it has to. I have no idea how to connect it with ADB.
Click to expand...
Click to collapse
You ran the HTCDriver exe that is on the SDCard? Did you go into Devices on your computer with your phone plugged in and see what it is showing up as?

setzer715 said:
You ran the HTCDriver exe that is on the SDCard? Did you go into Devices on your computer with your phone plugged in and see what it is showing up as?
Click to expand...
Click to collapse
It seemed to work for me when I copied the HTCDriver.exe from the storage card to my PC and install the drivers. My device showed up as some letters and numbers, which is ok I guess I have not named or done anything to the device.

Amazing write up. ABD has always gave me a hard time. I will be following this write up when I get time to root this. Thanks a lot!
Sent from my HTC Glacier using XDA App

Four things:
1. You don't need the generic drivers from the SDK package. I haven't even tried them. You need the HTC Drivers on the SD card.
2. I start adb by SHIFT-right clicking on the tools directory in the SDK folder and selecting 'start command prompt here' in the contextual menu. In order to see if things are working, just type 'adb devices' to see if the HTC device is connected.
3. I don't need to disable mounting of the device. I can adb and have the SD card mounted on the PC at the same time.
4. I don't see the need to add the environmental variable. Perhaps I've done something wrong, but theoretically, by adding this variable, you should just be able to type 'adb' in any command prompt window and have the system recognize adb. I can't seem to get that to work. So, instead I just do #2 above.

setzer715 said:
You ran the HTCDriver exe that is on the SDCard? Did you go into Devices on your computer with your phone plugged in and see what it is showing up as?
Click to expand...
Click to collapse
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App

Arcadia310 said:
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
type
Code:
adb devices
in the command line

Arcadia310 said:
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
What does the output from typing "adb devices" give you?

grankin01 said:
What does the output from typing "adb devices" give you?
Click to expand...
Click to collapse
It says can not recognize ADB. I have had the SDK and ADB on my PC for months.

Arcadia310 said:
It says can not recognize ADB. I have had the SDK and ADB on my PC for months.
Click to expand...
Click to collapse
Sounds like you aren't in the directory that adb is in when you type it. try going into the tools directory in your sdk and run the command from there.

Arcadia310 said:
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
What version of windows are you running?

setzer715 said:
What version of windows are you running?
Click to expand...
Click to collapse
Windows XP. When i actually go to ADB and click on it it opens and closes within an instant.
Sent from my HTC Vision using XDA App

Arcadia310 said:
Windows XP. When i actually go to ADB and click on it it opens and closes within an instant.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
You don't click on it. It's a utility to use in command line. What it does is makes it easier to enter commands (along with some other useful stuff). Basically, anything you would type in terminal you can type in command line on your pc with "adb shell" pre-face. For example:
In terminal: cd /system/app
In command line: adb shell cd /system/app
Makes sense? You should really read up some guides out there

floepie said:
Four things:
1. You don't need the generic drivers from the SDK package. I haven't even tried them. You need the HTC Drivers on the SD card.
2. I start adb by SHIFT-right clicking on the tools directory in the SDK folder and selecting 'start command prompt here' in the contextual menu. In order to see if things are working, just type 'adb devices' to see if the HTC device is connected.
3. I don't need to disable mounting of the device. I can adb and have the SD card mounted on the PC at the same time.
4. I don't see the need to add the environmental variable. Perhaps I've done something wrong, but theoretically, by adding this variable, you should just be able to type 'adb' in any command prompt window and have the system recognize adb. I can't seem to get that to work. So, instead I just do #2 above.
Click to expand...
Click to collapse
Hey sorry about the driver problems... i wrote this guide based on the Nexus one and T-Mobile G1 and was asked to repost it here. If you let me know exactly what drivers you used i can change it in the OP.
The environmental variables set so that you can run adb and fastboot commands from anywhere in windows without have to be in the tools directory of the sdk. You can press SHIFT or w/e but this is a 1 time solution so u basically never have to be in that directory again...
As for the mounting, it is recommended that you dont mount your SD-Card and use adb for editing system files because that could corrupt your sd card.

Thank you, I got it working. Android is very different from winmo.

nephron said:
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Still not working?
Click to expand...
Click to collapse
This saved me... Constantly had it reverting back to USB storage device, this did the job. Thanks, a little something coming your way...
Bill

[Q] Cannot Access ClockworkMod Recovery or HBOOT.

Hello guys, as the title says..
I am unable to access a Custom Recovery Image, even though I'm rooted and have been for some time. I use ROM Manager, and recently attempted to flash a new Recovery (updated Clockwork) which didn't install, and then I tried to access the Custom Recovery to update a ROM, which didn't work, as it just went to the normal Android Recovery, highly annoying.
So I thought I'd try to access HBOOT screen, that also didn't work (when I did the button combinations), and then thought I'd access ClockwordMod Recovery via the button combination, that also didn't work.
I originally rooted my phone before Unrevoked was available for the Desire, which, I must've done it in a way in which CMR was never available when using the Recovery Image button combination from Hardboot, so I always used ROM Manager, which worked perfectly fine until today.
Any advice on how to do this? Is it possible to ADB Push the Custom Recovery Image and always have it there? It's quite frustrating in all fairness.
I'm now running Oxygen 2.0 RC3.
Dan

What happens exactly when you fail to access your custom recovery via the bootloader screen? Do you receive any errors? Have you tried re-installing ROM Manager or tried an older recovery image?
If all else fails, try flashing AmonRa recovery with unrEVOked.
Sent from my HTC Desire using XDA App

I've tried to push AmonRa with Unrevoked, and that didn't work either.
I've tried to uninstall ROM Manager and reinstall it and that didn't work, and tried to flash Clockworkmod Recovery, that also didn't work.
I don't get any errors, I just get to the Android Recovery Screen, with the Red Triangle.

from what i understand is that you are fake flashing everytrime that you use your recovery. i would recommend that you backup all your data and keep them in safe place. as long as you cannot boot into fastboot i cannot recommend you to do s-off(if fastboot was working you could try for s-off and after try to fkash recovery through fastboot). the only thing is to use an unbranded RUU and start over by using unrevoked to root and flash custom recovery(i suggest AmonRa's for the Desire) than you can restore your backed apps after flashing the desireable rom.
for the record if you boot into fastboot by pressing back button+Power on, does it go there? and if it does not go can you tell me what it say?
bigdan35 said:
I've tried to push AmonRa with Unrevoked, and that didn't work either.
I've tried to uninstall ROM Manager and reinstall it and that didn't work, and tried to flash Clockworkmod Recovery, that also didn't work.
I don't get any errors, I just get to the Android Recovery Screen, with the Red Triangle.
Click to expand...
Click to collapse

Yes, I can only use fake-flash to do everything now which gets quite annoying. I was thinking about doing that, just installing an unbranded RUU and kind of sorting my phone out fresh, which gives me a chance to partition my SD card again without having the "Format SD Card" option every time I plug my phone in.

Having the same issue here. Any clues yet on what happened?

bigdan35 said:
Yes, I can only use fake-flash to do everything now which gets quite annoying. I was thinking about doing that, just installing an unbranded RUU and kind of sorting my phone out fresh, which gives me a chance to partition my SD card again without having the "Format SD Card" option every time I plug my phone in.
Click to expand...
Click to collapse
Revert back to stock with the RUU for your phone and run unrEVOked again

Hi, sorry to ask again, i've run through a lot of tread and still cant find the answer...
i have almost similar problem, i can get access to HBOOT menu if i connect the phone through PC and removed the battery, but it only said RUU, not hboot, fastboot, recovery and usual menu... why...???
if i didnt removed the battery or start normally, i only get grey HTC logo with black background and /!\ on all the corner...
so now i can't get access to HBOOT, recovery or os, i've try to get a gold card, but adb cannot read my phone (maybe because i cant access fastboot)... GoldCardTool also didnt work...
i've ask several people, but they keep asking me to look again into all the tread available... at lease tell me what should i look for please... its been a week already...

HTC Desire (ojan) said:
Hi, sorry to ask again, i've run through a lot of tread and still cant find the answer...
i have almost similar problem, i can get access to HBOOT menu if i connect the phone through PC and removed the battery, but it only said RUU, not hboot, fastboot, recovery and usual menu... why...???
if i didnt removed the battery or start normally, i only get grey HTC logo with black background and /!\ on all the corner...
so now i can't get access to HBOOT, recovery or os, i've try to get a gold card, but adb cannot read my phone (maybe because i cant access fastboot)... GoldCardTool also didnt work...
i've ask several people, but they keep asking me to look again into all the tread available... at lease tell me what should i look for please... its been a week already...
Click to expand...
Click to collapse
you just flashed the wrong RUU and now your phone is in RUU mode (can access it through "adb shell reboot oem-78" if anyones interested), all you need to do is flash the correct RUU.
If you don't know which RUU is right for you, then you will need to make a goldcard so you can just flash the latest WWE RUU
to make a goldcard, turn on your phone and plug into usb (yes I know your phone shows triangles, ignore them, you're still in fastboot)
then type:
Code:
fastboot oem gencheckpt
This will boot you into recovery if it's there
wait for about 20 seconds, and type:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1*/cid
NOTE: if this command doesn't work, then I can't help you.. I'd suggest trying again, maybe you didn't wait long enough for recovery to start.. or maybe recovery isn't even there anymore.
this will give you a series of letters and numbers. Copy them down VERY CAREFULLY. Once you've got that, follow this guide on making a goldcard.
Once you've done that. Flash this RUU, and you should be done.

bortak said:
you just flashed the wrong RUU and now your phone is in RUU mode (can access it through adb shell reboot oem-78 if anyones interested), all you need to do is flash the correct RUU.
Click to expand...
Click to collapse
i didnt remember i've flash RUU before, by the way, how i can flash RUU if i cant get access to hboot, fastboot or recovery... should i take RUU here...???
http://shipped-roms.com/index.php?category=android&model=Bravo
really hope you can assist me all the way bortak... i got to stay awake just to have a chat (different time zone)...

I posted the whole process for you.. when you've got the goldcard plug your phone in via usb and run the RUU from your PC, it will do it... you are in fastboot mode.. just fastboot RUU.

bortak said:
you just flashed the wrong RUU and now your phone is in RUU mode (can access it through "adb shell reboot oem-78" if anyones interested), all you need to do is flash the correct RUU.
If you don't know which RUU is right for you, then you will need to make a goldcard so you can just flash the latest WWE RUU
to make a goldcard, turn on your phone and plug into usb (yes I know your phone shows triangles, ignore them, you're still in fastboot)
then type:
Code:
fastboot oem gencheckpt
This will boot you into recovery if it's there
wait for about 20 seconds, and type:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1*/cid
NOTE: if this command doesn't work, then I can't help you.. I'd suggest trying again, maybe you didn't wait long enough for recovery to start.. or maybe recovery isn't even there anymore.
this will give you a series of letters and numbers. Copy them down VERY CAREFULLY. Once you've got that, follow this guide on making a goldcard.
Once you've done that. Flash this RUU, and you should be done.
Click to expand...
Click to collapse
where i should type "fastboot oem gencheckpt"...???

HTC Desire (ojan) said:
where i should type "fastboot oem gencheckpt"...???
Click to expand...
Click to collapse
in cmd.. I take it that you have android-sdk installed?
if not, just unzip the attached file into your C:\
and then type:
Code:
cd\
fastboot oem gencheckpt
then continue with the guide from the previous post.
EDIT: if you don't know how to open cmd, it can be found under "accessories" in the start menu, and it's called "command prompt"

bortak said:
in cmd.. I take it that you have android-sdk installed?
if not, just unzip the attached file into your C:\
and then type:
Code:
cd\
fastboot oem gencheckpt
then continue with the guide from the previous post.
EDIT: if you don't know how to open cmd, it can be found under "accessories" in the start menu, and it's called "command prompt"
Click to expand...
Click to collapse
ok, i've done that, but something like this pop out...
"This application has failed to start because ADBWinApi.dll was not found. Re-installing the application may fix this problem"
Should i re-install android SDK...???

HTC Desire (ojan) said:
ok, i've done that, but something like this pop out...
"This application has failed to start because ADBWinApi.dll was not found. Re-installing the application may fix this problem"
Should i re-install android SDK...???
Click to expand...
Click to collapse
yes, seems as if you don't have it... I'm pretty sure I gave you a link somewhere in those posts
okay maybe not. Here it is http://developer.android.com/sdk/index.html you don't need to worry about downloading all the revisions.. the only things you're interested in is the tools

bortak said:
yes, seems as if you don't have it... I'm pretty sure I gave you a link somewhere in those posts
okay maybe not. Here it is http://developer.android.com/sdk/index.html you don't need to worry about downloading all the revisions.. the only things you're interested in is the tools
Click to expand...
Click to collapse
yes you has gave me that link, thanks... but i didn't know how to use it... and i've installed it to my PC (it takes 5-7 hours of downloading package and installing package)... if i re-install, it surely will take another 5-7 hours...

errrmmm.... okay, go to C:\android-sdk\platform-tools and run "adb.exe", then try again

bortak said:
errrmmm.... okay, go to C:\android-sdk\platform-tools and run "adb.exe", then try again
Click to expand...
Click to collapse
something like this pop out
C:\>android-sdk-windows\platform-tools\adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

alright well adb seems to be running then try the command to get the CID then...

bortak said:
alright well adb seems to be running then try the command to get the CID then...
Click to expand...
Click to collapse
sorry, but how i can get the CID...???

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Hellua nice guide :thumbup:
TEAM MiK
MikROMs Since 3/13/11

Man Cnexus! You are everywhere! Lol.
Nice guide. This will save lots of people :thumbup:
------------------------
Sprint Galaxy S3 "Supernexus" Thanks To Cyanogenmod
Whiplashh Rom
Look it up.

Is this method specific to the S3? I have an old S2 that I need to recover some photos from.

Hmm...boot your S2 into recovery, then connect it to your computer, run the following command and post the output for me.
Code:
adb shell ls

Hopefully I never need this guide but I think it should be a sticky. Good job!

This seems very helpful thank you.
This is a good option as well
https://code.google.com/p/androidscreencast/

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Click to expand...
Click to collapse
Thanks so much for the how-to.
I have a rooted Sprint Galaxy S3 with a broken display. I'm having a problem with getting it into recovery mode.
I believe when I hold down VolUp+Home+Power and reboot, it's loading a menu that's prompting me to select one of the boot options. It otherwise just sits there and never actually boots.
I've tried to use adb to boot it into recovery mode, but it also just sits there until I press the home key, at which point it just boots into normal mode.
Is there a way I can bypass any menus or does anyone with a working system know which option I should select at the menu?
Thanks,
Alex

Is your display broken? What does "adb devices" show when you're in that mode?

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.

loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:

Sorry, had to
Sent from my SGH-I747 using Tapatalk 2

Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest

Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest

You need to be rooted for this to work.

CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest

[Q] HTC One X System Wipe

Firstly let me apologise If I've posted this thread in the incorrect place, I only joined XDA moments ago & I'm still struggling to navigate my way around.
I know there has already been similar posts to mine on XDA as I've worn out the search button on google trying to find a solution to my problem, with no avail. So I thought I would leave a description of my own situation and see if a more tech-savvy individual could kindly help me out...
So yesterday I decided it would be a good idea to unlock my bootloader & root my device simply because I wanted to remove all the bloatware which HTC 'generously' crammed into the One X. Unlocking the bootloader was simple enough following the instructions provided. However, rooting my handset was not so effortless. The root was ineffective & I got stuck with yet another unwanted app called SuperSU! (An error message regarding missing binary codes appeared every time I tried to open the application) I tried uninstalling via both settings & google play before finally factory resetting my phone. None of these methods worked
At this point it suddenly dawned on me someone so unenlightened in the art of software development or anything android related shouldn't being toying with stuff he can't afford to break! But I figured it was too late to turn back now and continued in my moment of intellectual darkness...
In my bewildered state I accidentally 'wiped system' using CWM and now I have no iOS. My HTC will only boot until the 'quietly brilliant' slogan appear's & no further. When I connect my phone to my computer via USB I can not access the removable storage device, a removable disk appears but when clicked I am prompted to 'insert removable disk'. I am lead to believe from reading related threads that if I had access to my phones storage then installing a new iOS would be relatively straight forward. Also trying to mount in CWM just retrieves an error message reading 'CWM unable to open ums lunfile (no such directory exists)'. Where do I go from here?
Sorry for my long-winded post! I just wanted you guys to know exactly where I'm at. I would really appreciate any helpful advice which could possibly correct this idiotic error of mine.

ADB Site load
Step by step guide:
ADB: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 - WINDOWS ONLY IF MAC PLEASE ASK
ROM:http://forum.xda-developers.com/showthread.php?t=2753450
push to sd card via adb
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check connectivity:
adb devices
(should return serial number)
4)push rom to sd card:
adb push romname.zip /sdcard/ (where romname is your actual zip file name)
5)you should then be able to simply wipe and flash the rom as you normally would.
*if you can find a nandroid for your particular build,you should be able to push that,with:
adb push nandroidname /sdcard/clockworkmod/backup/nandroidname/
(again,using cw. ill update if i can determine this to work for twrp)
be patient,the nandroid is a big file,so this will take some time.
2)install from adb sideload
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check for connectivity
adb devices
(should return serial number)
4)select "install from sideload" from the recovery menu
5)in cmd,enter:
adb sideload romname.zip (where romname is your actual rom's name)
you should see it installing on the phones screen
Hope it helps

Hi Jorandobnl, thanks for your reply.
I am using windows 7 & already have the android sdk bundle which I grabbed online when unlocking & attempting to root my device. It would of been great if I had the link you provided at the time as it was such a large download for the purpose of 4 files (fastboot, adb, adbwinapi & adbwinusbapi). Please let me know if I'm missing any other adb required files and I will download them.
So here's where im at...
I followed your instructions step 1 - 3 & my fastboot folder now contains root, fastboot, AdbWinApi.dll, AdbWinUsbApi.dll, adb & crDroid.zip
When typing 'C:\fastboot>adb devices' the cmd prompt returns with:
C:\fastboot>adb devices
List of devices attached
Even though the cmd prompt didn't list any adb devices I continued to the next step anyway & here's what was returned:
Code:
C:\fastboot>adb push crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip/sdcard/
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\fastboot>
'crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip' is the name of the ROM file which you kindly provided
When my handset is attached to my PC via USB I receive a different command prompt:
Code:
C:\fastboot>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\fastboot>
When I use the cmd code 'C:\fastboot>fastboot devices' It returns:
C:\fastboot>fastboot devices
HT244W103055 fastboot
I'm not sure whether this has any relevance but I would like to give you as much detail as possible.
To quickly summarise the steps which I took so you can check if I am doing anything wrong (which is more than likely)
Firstly I downloaded the ROM (crDroid) & placed it in my fastboot folder along with the adb files I already have. I connected my phone to my computer and started bootloader mode, then I clicked 'recovery' which loaded CWM. I proceeded to check for adb devices which unfortunately returned with nothing. I attempted 'step 4' regardless which returned the cmd code I copy and pasted for you above (for obvious reasons I could not complete step 5).
Your alternative method I have not tried yet because I neither know what nandroid nor sideload means (I must sound like im either 90, amish or stupid )
Any further help you could give me would be very much appreciated & hopefully I can find a way to fix this soon :fingers-crossed:
Once again I apologise on behalf of my technologically illiterate brain!

Update:
I checked out what sideload & nandroid are & attempted to fix my device through your 2nd method, sadly I bumped into more problems...
I located the correct nandroid build for my handset (which took way longer to find than I had hoped)
My computer still won't recognise any adb devices, I've downloaded at least 3 additional adb.exe files today to confirm that the one I downloaded with the android sdk bundle wasn't out dated. I've also killed all adb.exe processes via task manager & tried running it again in case one was interfering with the other... Still nothing
I then read in a separate thread that maybe the drivers were outdated? I couldn't check for driver updates using the traditional device manager route so I downloaded drivers online but still my PC wouldn't show any adb devices. Although I doubt out dated drivers are the problem as I updated them recently when I unlocked & attempted to root my HTC.
Again I ignored this and continued with your steps anyway, then I encountered my next problem. CWM doesn't seem to have a sideload feature... I understand its supposed to be located in the 'install zip from sdcard' section right? The options I have are as follows:
choose zip from sdcard
apply/sdcard/update.zip
toggle signature verification
toggle scripts asserts
I have checked every option on CWM & sideload is nowhere to be found! I am using CWM v5.8.1.8
Maybe the reason my PC can't find an adb device is because there is no removable disk showing when I plug in my phone using USB? When I use fastbootUSB my computer plays the normal sound to show it has recognised a device but nothing is showing in removable storage.
I've wasted my whole day trying to fix this problem. Surely there has to be a way...

have the same problem same rom.... hope answer will come out.
tried it too and nothing Works... have win 8.1