My phone has been rebooting many times recently. I have read about people mentioning a logcat when connected via USB. I am keen to help shed light on reboots so want to know what I need to do after a reboot.
Do I simply hook up the phone to my PC via USB and run a command to dump some sort of error log file?
Darren
ADB is your friend
DarrenNewsgroup said:
Do I simply hook up the phone to my PC via USB and run a command to dump some sort of error log file?
Darren
Click to expand...
Click to collapse
Yes. You shall use ADB for viewing log from PC.
I use the ADB included with SuperOneClick 2.1.1
Download it from here: ftp://shortfuse.org/SuperOneClick/Packages/SuperOneClickv2.1.1-ShortFuse.zip
Inside the zip there is an ADB folder. First, if on windows, try just invoking adb.exe from a command prompt (cmd), it will spit out the parameters.
For log viewing, connect USB to phone and start "adb.exe logcat".
If you want to redirect the output to a file, you can use "adb logcat > output.log", for example.
Cheers,
timara
So, what is the best way/app to get a command prompt on my tab? I'd like to be able to enter linux command in the shell directly.
Also, what is the best say/app to install a ssh server on the device, so I can enter these same commands trought SSH with putty.
Thanks
I personally turn to Better Terminal Emulator Pro and for remote SSH access to my pad I use SSHDroidPro, both costs a little but are well worth the money
I don't know how to use the cmd prompt. I've looked at the other posts on this forum and on other sites but their solutions don't seem to work for me. If I copy and paste this C:\Program Files\Android\android-sdk\SDK Manager.exe I get a reply saying it is not recognised as an internal or external command, operable program or batch file. Now if I copy and paste this "C:\Program Files\Android\android-sdk\SDK Manager.exe" it opens up SDK manager but I'm unable to input anymore text into the cmd prompt window.
I can't get my system to recognise adb devices but I have installed all the drivers for my Nexus One and I can identify my N1 through windows. I've also installed Eclipse.
I'm wanting to install another ROM on my handset( unlocked ) but if I can't get my device recognised via the cmd how can I do that? ?
I'm sure that I'm doing something wrong but I can't figure out what! Can you please advise me?
I'm still trying to figure it out but getting nowhere fast! ?
EUREKA!
At last it works, or, At last I can do it!
My device now shows up when I use cmd fastboot devices. I reinstalled the sdk direclty to C:\ . . . . don't why that would make any difference.
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
craterib said:
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
Click to expand...
Click to collapse
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
sz_gergo said:
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
Click to expand...
Click to collapse
Code:
[email protected]:/etc/udev/rules.d$ more 51-android.rules
# Sony Ericsson Mobile Communications AB
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6168", MODE="0600", OWNER="kuisma"
Using this, you don't have to run the adb server as root. Use the "lsusb" to get Vendor and Product id for your device.
Also, change "kuisma" to your user, of course, unless toy happen to be me.
Restart udev (/etc/init.d/udev restart) once you've edited this.
sz_gergo said:
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Click to expand...
Click to collapse
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
bronzext said:
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
Click to expand...
Click to collapse
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
I did not see anybody here mention Knives-And-Forks Tools which is easiest way to Install adb and Fastboot on multiplatform computer. I did it and works like a charm
sz_gergo said:
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
Click to expand...
Click to collapse
hello i have question how to insert vid in hex notation...
digitized007 said:
hello i have question how to insert vid in hex notation...
Click to expand...
Click to collapse
Well therefor you will need an editor. I have used vi , but it is possible to use any editor.
2. step open the file in the editor
3. in a terminal window type " lsusb -v " that will give you the information of all the usb devices
look for the line beginning with idVendor of your device
for me it looks like: " idVendor 0x12d1 Huawei Technologies Co., Ltd."
4. copy the hexcode: 0x12d1 (yours may be another number) into the file
5. save the file
6. restart the server
only that number is needed nothing else
for every device you will get such a code , and each device code should came into a separate line
Hope that helps
br
sz_gergo
when I type adb devices cmd in the terminal it does not list my device and its plugged in....
when I try to type adb usb it says no devices found...
for the record nothing is wrong with my USB connection cable because, I'm able to connect my HTC ReZound via USB cable to my macbook, the CDROM and STORAGE auto mounts to my desktop so i know the connection is working, because I'm able to copy files, update music via winamp sync playlists, also my paid EasyTeather copy works, etc.
I updated & installed most recent Android SDK adt-bundle-mac-x86_64-20130917 and updated the device manager for my ver 4.0.3 and all tools, even tryed using a stand alone platform-osx-tools.zip that contains a adb and fastboot...\
I read up on this and found nothing tryed everything....
adb kill-server > adb start-server - does nothing
adding device in the adb_usb.ini didn't help either.
chmod a+r /etc/udev/rules.d/51-android.rules after creating file didn't help.
rebooted many times .
i've attached a terminal cmd window below to show.
USB debugging is enabled on the device, yes? Does the "USB debugging enabled" notification show up when you plug it into the computer?
MaxxPayne said:
when I type adb devices cmd in the terminal it does not list my device and its plugged in....
when I try to type adb usb it says no devices found...
Click to expand...
Click to collapse
are you doing proper methods in command prompt for sdk's adb such as directing it to the folder its in...example did you type cd c:/androidsdk/platform_tools/ in command prompt for example
I used to have a mac ....but here
Download htc sync for mac
http://www.iskysoft.com/convert-mobile/sync-htc-to-mac.html
Download the sdk and all you need is a folder called platform tools
http://developer.android.com/sdk/index.html
Extract the platform tools folder Put it on your desktop
Open terminal type "cd" then hit space then drag and drop the platform tools folder into the terminal after that hit enter
Then you can run any command just make sure to put "./ " before the command without quotations so if you wanna flash a boot you would put
./fastboot flash boot boot.img and hit enter
Note that adb works perfectly well on my Mac without the HTC Sync drivers.