Related
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
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...???
Ok there are some other guides here on the forums for this but they all require you to download the Android SDK. That can be very time consuming and confusing if you run into issues. I have been looking at a way to have the capability to push and pull files using my laptop but i really didnt want to go through downloading and setting up the whole SDK just to use adb.
If anyone has followed any of my threads, you know I am all about trying to get things done in the easiest way possable to help the people that are new to Android. This method has worked for me but there is no guarentee that it will work for you and I am no way responsable for anything that happens to anything unless it works great for you. Then I will take all credit j/k. With that being said:
The first method is for Windows based OS. I have tested it on XP but I would imagine it will work on any Windows OS. If I am informed of something different I will update it here. The Mac version is in post #2 and takes less than 1 minute to do. Much thanks to kwbdc and stlouie65 for the help on this.
Instructions for setting up Adb/Fastboot (windows)
1. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
2. Install drivers on your PC. This is done on the MT4G/HTC devices by going onto your sd card and clicking on the HtcDrivers.exe file while viewing the files on your PC. It should automaticly install them to your PC. If you are using another phone or have trouble installing the ones from your sd card you can try pda.net or HTC Sync for the drivers. Here are links for pda.net 32-bit Windows 7/Vista/XP and for 64-bit Windows 7/Vista. Install the program by hitting "Run" and follow the instructions. You can remove it at a later time.
3. Download the file at the bottom of these instructions to your desktop and extract the contents. There is 1 folder and a install note (these instructions) that should extract. You can use a program called 7-ZIP (google it, its free and a great tool).
4. Open your "Start" menu and click on "My Computer". Then choose "Local Disk C:".(You can now click and drag the adb folder you extracted to the C: drive.
5.Open a command prompt and type cd\adb and hit enter. You should now see something that looks like this C:\adb>
6.Type adb devices then hit enter in the command prompt and it should list your device.
7. You can also type fastboot devices then hit enter in the command prompt an it should list your device. (you must be in the bootloader for fastboot to recognize your device)( adb command= adb reboot bootloader )
You should now be ready to send commands to your phone via ADB or Fastboot. You will need to repeat steps 5-6 anytime you want to use ADB/Fastboot. To send a file using Adb or fastboot make sure to put the file in your "adb" folder before giving the command to send it to your device.
If this helped you please use the "Thanks" button to show your gratitude.
____________________________________________________________________
Please feel free to ask any questions you want and I will help in any way I can.
DOWNLOAD MIRROR
Here are some commands for Adb/Fastboot.
DO NOT USE ANY COMMANDS THAT YOU ARENT SURE OF OR DONT KNOW WHAT THEY DO. I AM NOT RESPONSABLE FOR ANYTHING THAT YOU DO TO YOUR PHONE.
ADB Commands
adb devices - list all connected devices
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 install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal 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 specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader 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 the 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 updated.
- 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 priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed
Click to expand...
Click to collapse
.
Fastboot Commands
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Click to expand...
Click to collapse
Mac Instructions
Download THIS FILE Extract the 2 files inside it and place them on your Macintosh HD root. Plug in your phone to the usb, open terminal and type /adb devices.
It should now give u a serial #
To send a file using adb/fastboot the file must be placed in your mac HD Root or you must give the location in your command path.
Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again
92drls said:
Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again
Click to expand...
Click to collapse
Not a prob...Please let me know if this works good for you.
Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?
92drls said:
Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?
Click to expand...
Click to collapse
Put the file you are trying to push in the same folder you created.
ReName it bootanimation.zip
To push your file use this command after you cd into the folder you created.
You also need to be in recovery with your system mounted.
adb push bootanimation.zip system/customize/resource/bootanimation.zip
That is the location of the bootanimation on that rom.
Hope this helped
Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again
92drls said:
Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again
Click to expand...
Click to collapse
I do know how to change it but would rather you have the fulfillment of learning how to do it yourself You can find a great guide and splashscreens in the thread by Iriscience. Make sure to thank him for it.
Back on topic, I'm glad this worked good for you. It really is pretty simple. I dont have have a donation link (I do this for the love of helping people mod their phone) but I would appreciate it if you hit the "Thanks" button at the bottom of any post that have helped you.
Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.
@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.
30Glock said:
@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.
Click to expand...
Click to collapse
geoffott said:
Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.
Click to expand...
Click to collapse
Thanks Guys, I appreciate the kind comments! My whole intention of this thread is to help people that couldnt or didn't want to set up the Android SDK have a good solid way of pushing and pulling files to their phone.
Great guide Drew! I'll finally be giving adb a shot! I've always been intimidated by it.
This helps for sure.
Sent from my HTC Glacier using XDA App
thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?
dominicanman912 said:
thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?
Click to expand...
Click to collapse
You must be in fastboot (bootloader) for fastboot to recognize your device. You can get there by by turning off your phone then holding down the volume down button and the power button at the same time. Our you can use this command via adb (usb plugged in):
adb reboot bootloader
Your device should automatically go into fastboot from the bootloader. If it doesn't you can scroll to fastboot using the volume button and hit the power button.
Thank you for answering my question! I have been reading a lot about adb over the past few days and I feel more comfortable with this way than the pain in the ass sdk method! When I get back on the pc, I will be sure to hit that thanks button because you have been a great help.
Sent From my ICE COLD HTC Glacier aka MyTORCH4G!
How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153
koolkid09 said:
How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153
Click to expand...
Click to collapse
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img
TrueBlue_Drew said:
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you so much!! I have been trying to do this for the past hour now! lol
Awesome post! Saved me a (potentially painful) convo with a friend who's just getting into modding his MT4G.
error
I feel like an idiot, idk what im doing wrong, in command prompt i get this message, 'adb' is not recognized as an internal or external command, operable program or batch file......what am I doing wrong?
my GT-N5100 got stock in loop boot after I install the driver of chainfire3d..
i tried to restore it factory default..erasing cache...but nothing seems to work...
I already resolved it using adb
This is How I fixed mine..
I search several forum and and no one has the complete tutorial on how to use adb..
so I created my own step by step tutorial on how I did it just in case I need it again or someone needs it...
I hope this fixed yours as well..
Download ADB here: http://developer.android.com/tools/help/adb.html
1. extract the file you just download
2. put it in C: (so you can access it easily)
3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
4. open SDK Manager.exe
5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
6. Boot your device to recovery mode (hold volume up + power) hold it until it is turned on
7. connect your device through usb to PC (it should automatically install your usb driver if not download samsung usb driver)
8. go to CMD
9.type cd c:\Android-adb\sdk\platform-tools
or
9.1 press windows + pause/break
9.2 click Advance tab
9.3 click Environment Variables
9.4 search "path" under System variable
9.5 click edit (there is a value for Variable value in default)
9.6 at the end of the default value add this ;C:\Android-adb\sdk\platform-tools
9.7 click ok
10.
type this
adb
adb shell
[email protected]:/ $ su
adb shell /system/lib/cf3d_uninstall.sh
11. your device will reboot...after that it should be fine...
NOTE:
if you encounter device not detected or something try this..
adb kill-server
adb start-server
>.<
Please read before installing anything.
Chain fire works for gingerbread. .. DOESN'T WORK with ice cream sandwich and jelly bean
Sent from my GT-N5100 using Tapatalk 2
actualy I didn,t download it from from google play...
that **** bastard site didn't include that warning...
sorry chainfire for not buying it from google play maybe thats my karma..haha..
but my gt-N5100 is fine now..I google for a solution and I found 1..
Edit: if chainfire manage to make it compatible with JB, I'll promise to pay for it next tym.. I wanted to play some THD...
Sent from my GT-N5100 using XDA Premium HD app
jhonuy03 said:
actualy I didn,t download it from from google play...
that **** bastard site didn't include that warning...
sorry chainfire for not buying it from google play maybe thats my karma..haha..
but my gt-N5100 is fine now..I google for a solution and I found 1..
Edit: if chainfire manage to make it compatible with JB, I'll promise to pay for it next tym.. I wanted to play some THD...
Sent from my GT-N5100 using XDA Premium HD app
Click to expand...
Click to collapse
Where did you read or see its compatible with JB
Sent from my Galaxy Nexus using XDA Premium HD app
Same issue stuck at boot logo
Could you please let me know how to solve this issue using adb
I am having same issue :crying:
Thanks in advancex
FIXED
ankitwase said:
Could you please let me know how to solve this issue using adb
I am having same issue :crying:
Thanks in advancex
Click to expand...
Click to collapse
This is How I fixed mine..
I search several forum and and no one has the complete tutorial on how to use adb..
so I created my own step by step tutorial on how I did it just in case I need it again or someone needs it...
I hope this fixed yours as well..
Download ADB here: http://developer.android.com/tools/help/adb.html
1. extract the file you just download
2. put it in C: (so you can access it easily)
3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
4. open SDK Manager.exe
5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
6. Boot your device to recovery mode (hold volume up + power) hold it until it is turned on
7. connect your device through usb to PC (it should automatically install your usb driver if not download samsung usb driver)
8. go to CMD
9.type cd c:\Android-adb\sdk\platform-tools
or
9.1 press windows + pause/break
9.2 click Advance tab
9.3 click Environment Variables
9.4 search "path" under System variable
9.5 click edit (there is a value for Variable value in default)
9.6 at the end of the default value add this ;C:\Android-adb\sdk\platform-tools
9.7 click ok
10.
type this
adb
adb shell
[email protected]:/ $ su
adb shell /system/lib/cf3d_uninstall.sh
11. your device will reboot...after that it should be fine...
Help
jhonuy03 said:
This is How I fixed mine..
I search several forum and and no one has the complete tutorial on how to use adb..
so I created my own step by step tutorial on how I did it just in case I need it again or someone needs it...
I hope this fixed yours as well..
Download ADB here:
1. extract the file you just download
2. put it in C: (so you can access it easily)
3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
4. open SDK Manager.exe
5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
6. Boot your device to recovery mode (hold volume up + power) hold it until it is turned on
7. connect your device through usb to PC (it should automatically install your usb driver if not download samsung usb driver)
8. go to CMD
9.type cd c:\Android-adb\sdk\platform-tools
or
9.1 press windows + pause/break
9.2 click Advance tab
9.3 click Environment Variables
9.4 search "path" under System variable
9.5 click edit (there is a value for Variable value in default)
9.6 at the end of the default value add this ;C:\Android-adb\sdk\platform-tools
9.7 click ok
10.
type this
adb
adb shell
[email protected]:/ $ su
adb shell /system/lib/cf3d_uninstall.sh
11. your device will reboot...after that it should be fine...
Click to expand...
Click to collapse
I tried the above at last it is showing device not found
wew
ankitwase said:
I tried the above at last it is showing device not found
Click to expand...
Click to collapse
that's how exactly how I did it...
at least that what I remembered I did..
and it works for me..
is your device rooted?
Help
jhonuy03 said:
that's how exactly how I did it...
at least that what I remembered I did..
and it works for me..
is your device rooted?
Click to expand...
Click to collapse
Yes i think it is rooted
Do i need to do wipe data in recovery mode ?
I think so because I wipe my cache and reset to factory default before I used ADB...
Sent from my GT-N5100 using Tapatalk HD
just ignore step 9.1 to 9.7...
Sent from my GT-N5100 using Tapatalk HD
jhonuy03 said:
I think so because I wipe my cache and reset to factory default before I used ADB...
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
Tried after wiping cache getting some problem "device not found"
Drivers are also installed correctly
r u sure u r in recovery mode and device is attach to usb?
Sent from my GT-N5100 using Tapatalk HD
Help
jhonuy03 said:
r u sure u r in recovery mode and device is attach to usb?
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
Yes i m in recovery mode, and when i am typing adb devices it is showing a serial number, i checked and found if device is connected
and if i issue adb devices then it will show serial number if device is connected
did you install google usb driver in sdk manager?
Sent from my GT-N5100 using Tapatalk HD
adb
When you type adb this should be the output
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb
Android Debug Bridge version 1.0.31
-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 <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
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 [-l] - list all connected devices
('-l' will also list device qualifiers)
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 command 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] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <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
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
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 get-devpath - prints: <device-path>
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:\Windows\system32>
Help
jhonuy03 said:
did you install google usb driver in sdk manager?
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
Yes i have installed it
please see the attachment
oh wa8 i remembered something...
try to type in cmd
adb stop-server
adb start-server
Sent from my GT-N5100 using Tapatalk HD
Help
jhonuy03 said:
oh wa8 i remembered something...
try to type in cmd
adb stop-server
adb start-server
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
C:\Windows\system32>adb
'adb' is not recognized as an inte
operable program or batch file.
Hi friends,
a short tutorial for rooting Ventos 10.1 from simple user Linux Ubuntu, when ADB doesn't recognise the device using Root_with_Restore_by_Bin4ry_v33 from this thread.
Disclaimer: The following rooting guides take software from third-party sources and are not products of danjde. I cannot be held responsible for any effects on your device resulting from this rooting guides. Please attempt only after reading through and understanding the guide(s) and proceed with caution.
ATTENTION: TABLET BATTERY MUST BE CHARGED!!
ALL FROM LINUX CONSOLE/TERMINAL WITHOUT EXTERNAL APPLICATIONS
1) edit from super user editor and add the correct USB Ids to /var/lib/usbutils/usb.ids:
2207 RocketChip
now lsusb should show the device properly
lsusb
Bus 001 Device 012: ID 2207:0010 RocketChip
2) add udev rule in /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"
3) restart udev service
service udev reload
4) optionally add vendor id in ~/.android/adb_usb.ini or in the same adb location
0x2207
5) extract the content of Root_with_Restore_by_Bin4ry_v33 and give executions permission to all fro semplicity (compessing whith zip have lost attributes)
chmod -R 755 "extracted-folder"
6) cd into the utility "Root_with_Restore_by_Bin4ry" directory
cd stuff
7) restart adb server
./adb kill-server
./adb start-server
8) connect Ventos and enable usb debugging.
9) now adb devices shows the device.
./adb devices
224DDD88E8722FA848300A20B9F8XXXX device
10) run as normal user
./RunMe.sh
[IMPORTANT: if you obtain on 64bit linux machine: "/stuff/adb: error while loading shared libraries: libncurses.so.5..."
install lib32ncurses5: apt-get install lib32ncurses5 and try again]
11) select normal mode
12) wait until 5 minus
finish!
tested :good:
Dear Danjde,
I habe a Trekstor Surftab Ventos 10.1 that I would like To root.
It appears, however, hat there exist At least 2 Version oft the tablet.
In Android settings it is called ST10216-2A.
Can you confirm your Version?
Also, is it possible To root the device fron a local shell via the same commands AS in the *.SH file?
Thank you so much!
Andreas
Hi der.einstein,
I confirm that two are the ventos 10.1 versions,
mine is the second, and from my research the method shown applies to both models.
For the second question the answer is: no
ciao!