adb logcat on ubuntu - Xperia Play Q&A, Help & Troubleshooting

hello,
I am trying to get ics aosp working on the Xperia Play
but it doesn't boot. so I want to make a logcat so i can see what is wrong in the ICS build.
i have got adb running and installed eclipse with ADT plugin
how can i see the logcat (when i do adb logcat in ADB i get a message with waiting for device when I plug in usb and turn phone on the message disapear)
nick

Is the device being recognized? Type "adb devices" to see if it is. If it shows you a "???????????????? no permissions" it's not recognized and you need to do the following.
Fire up a terminal, type lsusb. It will list the USB drivers, and you'll see one slot which is occupied by your mobile phone, like this:
Code:
Bus 001 Device 004: ID XXXX:YYYY Sony Ericsson Mobile Communications AB
So, create a rules file like this:
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
and paste the following inside the file:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="XXXX", ATTRS{idProduct}=="YYYY"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{ACTION} --device=$env{DEVNAME}"
Save the file, reboot your computer and you're done.
More info here: http://www.webupd8.org/2011/01/how-to-get-adb-to-work-on-ubuntu.html

Logcat is working when i use cm 7 fxp 047
But when i want to make a logcat for ics i get no logcat!

Related

[HOWTO] ADB for Macintosh Users Only for complete beginners!

I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU CAUSE!
So you are stumbling around XDA and you really want some kind of app or something, but you think you cant because you have a Mac, well I am here to tell you wrong.
The biggest and most used mistake for mac users when trying to use ADB is this:
HTML:
Inas-iMac:~ Hans$ /AndroidSDk/tools
-bash: /AndroidSDk/tools: is a directory
Inas-iMac:~ Hans$
Well this is how you do it!
Watch this!
http://www.youtube.com/watch?v=GLAMG4xU_lE
To make your phone go into debug mode go to settings/applications/development and check debug
DO NOT MOUNT PHONE! Just let it be
I did not go to deep into the process because this is made for complete beginners!
Why not follow the official SDK install instructions and add the path to bash_profile..
developer.android.com/sdk/installing.html#Installing
In my opinion that's not too hard for a newbie.. (i managed to do that) And after doing that you don't need to change directories with cd command, you can just type adb whatevercommand from your home dir which is the default location when you open the terminal.
Drag and drop is a little a fail.... one can add "alias" (linux can do it, probably mac too)
Little How-to:
Code:
$ nano ./bashrc
add and adapt the following line to bashrc:
Code:
alias adb="/home/carbonyle/android-sdk-linux_86/tools/adb"
now you just have to type "adb" from a terminal emulator to run it, eg:
Code:
$ adb shell
# reboot recovery
or
Code:
adb install ./Download/myFavortiteApp.apk
and so on...
ps: we don't need to "adb remount" at worst we can just "adb kill-server" then "adb start-server" if the device is not accessible

Run Logcat at Phone Boot Time

Hello,
I'm trying to troubleshoot why some kernels result in bootloops on my phone and others work just fine. (For example, KingxKernel CFS #8 would work, but not #9-#11)
I read somewhere about running a logcat during boot, but I have no idea how to successfully do this.
Any Suggestions?
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Cool man thanks for the tips.
This is def. A needed logcat command.
Sent from my PC36100 using XDA App
Try using ddbt, very useful for debugging in real time
Sent from my PC36100 using XDA App
sqeet said:
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Click to expand...
Click to collapse
Just to expand...
adb -d logcat>mylogfile.txt
if you want to save your output to a file. Though you are not going to see anything on the screen until you breakout (control c). Just type...
type mylogfile.txt|more
to view the file (or you could use notepad).
sorry meant ddms, not ddbt. It should be in the tools directory along with adb
Just to add that if you want to save the log file and see the output to the screen in real time you can
Code:
adb -d logcat &> log.txt
and then run
Code:
tail -f log.txt
provided that the command tail is available to your system.
Great stuff
sqeet said:
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Click to expand...
Click to collapse
Not a useless post at all. I landed here because I was searching for it. Thanks.

[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] htc desire drivers.

Hi guys what is the easiest way to check if i have installed the adb drivers or something like that.Thx
open console ('cmd' in windows) and type 'adb', while your phone is plugged to computer. If it'll write many lines of help about adb you have it installed. And then plug your phone and typa 'adb devices' if it'll write 'list of devices attached'
and your phone serial number, you've got htc drivers installed.
StylishPirat said:
open console ('cmd' in windows) and type 'adb', while your phone is plugged to computer. If it'll write many lines of help about adb you have it installed. And then plug your phone and typa 'adb devices' if it'll write 'list of devices attached'
and your phone serial number, you've got htc drivers installed.
Click to expand...
Click to collapse
If your computer is like mine, cmd will want adb.exe and adbwinapi.dll in the path you are using.
e.g. If adb is setup in
Code:
c:/android-sdk/tools
and your cmd path is (what it often is)
Code:
c:\users\username
then it will not work, so you have to specify the correct path using
Code:
cd [path for adb.exe]
Unless you add it to your windows environment variables first
Sent from my HTC Desire using Tapatalk

Rooting Trekstor Surftab Ventos 10.1 from Linux ADB if the device is not recognized

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!

Categories

Resources