Code:
c:\logcat>adb logcat > logcat.txt
- waiting for device -
error: protocol fault (no status)
- waiting for device -
c:\logcat>
what does that suppose to mean? i need logcat for my miui port and i get this message.
the logcat.txt is saved in logcat folder
butr the file is blank.
Do adb devices and see if it can actually see your phone.
Sent from my HTC6435LVW using xda app-developers app
no it doesnt not while booting. does how ever see phone in recovery fastboot and adb sideload strange
well nevermind i lost all adb functions im dead in the water.
wheres that adb.ro.sercure=0 maybe thats the issue
Related
I need logcat in adb to be able to get logfiles while testing android app on my P500!!! But when i enter in cmd:"adb.exe logcat > somefile.log"
it doesn't do anything and only creates somefile.log file that says:
Unable to open log device '/dev/log/main': No such file or directory
What is the problem? I am using PerfectPeso2.2!
i have confirmed that device is connected to PC when i type adb devices, i get serial number of my device so don't know whats the problem... got debbuging mode on, and in sdk manager downloaded all under the column "tools" and "extras"}
help please!!!
Echelonex said:
I need logcat in adb to be able to get logfiles while testing android app on my P500!!! But when i enter in cmd:"adb.exe logcat > somefile.log"
it doesn't do anything and only creates somefile.log file that says:
Unable to open log device '/dev/log/main': No such file or directory
What is the problem? I am using PerfectPeso2.2!
i have confirmed that device is connected to PC when i type adb devices, i get serial number of my device so don't know whats the problem... got debbuging mode on, and in sdk manager downloaded all under the column "tools" and "extras"}
help please!!!
Click to expand...
Click to collapse
In folder android-sdk / platform-tools / u can find ddms so run it..if u will see your connected device everything is OK and u will see after that logcat..if not your sdk instalation si corrupted or wrong..
mastershefis said:
In folder android-sdk / platform-tools / u can find ddms so run it..if u will see your connected device everything is OK and u will see after that logcat..if not your sdk instalation si corrupted or wrong..
Click to expand...
Click to collapse
thx tried that, but in that window in text column it still says that message...!?
"Unable to open log device '/dev/log/main': No such file or directory"
i read somewhere it it due to kernel logging disabled...:/ How to make enabled...?
You would need to either recompile the kernel to enable logging or install another kernel if the problem is that it isn't enabled in the kernel.
Sent from my LG-P500 using xda premium
Didnt want to further muck up the CM9 development thread. CM9 .04 doesnt want to boot for me, and potentially others with an 8gb NT. I'd love to get help and potentially help others but Fattire has requested logs in order to help figure out the problem. Problem is I'm very new to this and could use some help generating whatever log files I can. I'm on a windows machine, no knowledge of Linux. CM9 reboots right after the Cyanoboot screen(can still use cyanoboot to access recovery etc). If its too much of a hassle to help me figure this out, no worries, I can stick to stock for now.
http://forum.xda-developers.com/showthread.php?t=1474956
To output logcat to a txt file:
adb logcat > logcat.txt
First confirm you have ADB working. Then try the above command just after you turn the NT on. It will log everything up until the NT reboots itself.
lost101 said:
http://forum.xda-developers.com/showthread.php?t=1474956
To output logcat to a txt file:
adb logcat > logcat.txt
First confirm you have ADB working. Then try the above command just after you turn the NT on. It will log everything up until the NT reboots itself.
Click to expand...
Click to collapse
I got the NT to appear as Android Composite ADB Interface in the device manager(it also appears as Usb Mass storage), however I cant get it to appear when when I check adb devices in cmd. Tried uninstalling and re-installing the drivers still no luck. In Cm9 I verified that Usb Debugging is enabled but it still doesn't want to appear.
Try rebooting; or perhaps: http://forum.xda-developers.com/showthread.php?t=1550603
Maybe the 'Usb Mass Storage' entry should actually be installed as Android Composite ADB.
lost101 said:
Try rebooting; or perhaps: http://forum.xda-developers.com/showthread.php?t=1550603
Maybe the 'Usb Mass Storage' entry should actually be installed as Android Composite ADB.
Click to expand...
Click to collapse
Ok, I got it to output a log file from within .03, and it shows up under adb devices. I tried installing .04 and starting the log just as i start up, but all I seem to get is CMD saying -waiting for device-. The NT appears to be resetting before windows notices the device. It creates the logfile but its empty. I miss something?
Here's the sit: A very good developer is trying to blind port a JB ROM to his sister device which happens to be my device. There's some issues and he needs a logcat starting as early as possible. I tried to run logcat from terminal emulator but it didn't output a log to the directory I specified. In the logcat tutorial thread it says to end logcat by pressing control+c; obviously that's not possible on the phone itself. So, is it even possible for a shell script to start logcat, end it via terminal emulator and the log then created?
Sent from my LG-P999 using xda premium
Волк said:
Here's the sit: A very good developer is trying to blind port a JB ROM to his sister device which happens to be my device. There's some issues and he needs a logcat starting as early as possible. I tried to run logcat from terminal emulator but it didn't output a log to the directory I specified. In the logcat tutorial thread it says to end logcat by pressing control+c; obviously that's not possible on the phone itself. So, is it even possible for a shell script to start logcat, end it via terminal emulator and the log then created?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Download and install the android SDK
Then in terminal or cmd prompt type
Adb logcat
Sent from my HTC PH39100 using Tapatalk 2
Hi all,
I'm rooted and running Cyanogenmod 10.2.0. I'm trying to access some files on my device through ADB that require root access. I can change to the directory but when I attempt to list the contents of the directory I get a "permission denied" error.
I did enable Root access for "Apps and ADB" in the developer options on the phone.
Any ideas what's going wrong or (most likely) what I'm doing wrong?
TIA!
Sailing_Nut said:
Hi all,
I'm rooted and running Cyanogenmod 10.2.0. I'm trying to access some files on my device through ADB that require root access. I can change to the directory but when I attempt to list the contents of the directory
Click to expand...
Click to collapse
Will you please provide which command did you execute in cmd?
Please write it in same syntax as in adb
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Here are the commands I executed
Code:
adb shell
CD data/data/com.whatabou.pixeldungeon/files/
ls
The ls is where I get the error. It does change to the directory but it won't list the files. I have verified that I can see the files with root explorer.
Sailing_Nut said:
Here are the commands I executed
Code:
adb shell
CD data/data/com.whatabou.pixeldungeon/files/
ls
The ls is where I get the error. It does change to the directory but it won't list the files. I have verified that I can see the files with root explorer.
Click to expand...
Click to collapse
I have 2 answers. First - Go to adb
Code:
adb start-server
adb devices
adb shell
su
cd data/data/com.whatabou.pixeldungeon/files/
ls
Don't forget "su" command
When you give "su" command (depending on your phone) screen shows toast message or Superuser access for shell. In latter case give access.
Second- if above doesn't help
Then this will help to pinpoint problem.
Install terminal emulator from Play Store. Open and give Superuser access.
Code:
su
cd data/ /data/com.whatabou.pixeldungeon/files/
ls
Don't forget "su" command.
If 2nd method works then there is a problem with adb. If second method doesn't work then problem in phone.
Press thanks if helped
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Thanks for the response.
I KNOW the problem was that I forgot the su. Stupid me! I was assuming that since I was rooted that the shell was automatically elevated.
But now I have a different problem. I'm unable to use the original PC that I was working with and I've switched to another. Now I can't seem to get ADB to connect to my device. As first it showed no devices when I did the devices command. I realized it was likley because I didn't have the Samsung drivers installed, so I installed those and now I see the phone but it shows offline.
Any ideas what might be going wrong now?
I'm going to do a bunch of Googling to try to figure it out, but if I'm not successful maybe someone here will have an answer.
Thanks tons!
OK all solved!
I'm not sure what along the way I did that fixed my device offline problem. (It may just be that I never saw the RSA fingerprint notification on the phone the first bunch of times.)
The su took care of not being able to see the files when executing ls.
Thanks @hnkotnis
Sailing_Nut said:
OK all solved!
I'm not sure what along the way I did that fixed my device offline problem. (It may just be that I never saw the RSA fingerprint notification on the phone the first bunch of times.)
The su took care of not being able to see the files when executing ls.
Thanks @hnkotnis
Click to expand...
Click to collapse
Glad to help you.
I also had the adb saying offline problem. First it wouldn't show device. Then after Computer and phone reboot, it showed offline. I reinstalled Samsung adb drivers. It said I already have drivers. I said yes still install and rebooted. Problem solved. It occurred once again, but was repaired automatically.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Hey all I hope I'm not in the wrong section and I tried searching for an already similar if not identical thread but couldn't find one(probably not looking too hard) but I have a rooted LG G2 and I have ADB up and running but I don't know the commands I'm assuming. I type "ADB shell" and it connects and finds device but the only command that works for me is "reboot system". I've tried "boot recovery" and a few iterations but no luck.. Do I just not know the correct commands to tell it?
Sent from my LG-D801
DurbanPoison24 said:
Hey all I hope I'm not in the wrong section and I tried searching for an already similar if not identical thread but couldn't find one(probably not looking too hard) but I have a rooted LG G2 and I have ADB up and running but I don't know the commands I'm assuming. I type "ADB shell" and it connects and finds device but the only command that works for me is "reboot system". I've tried "boot recovery" and a few iterations but no luck.. Do I just not know the correct commands to tell it?
Sent from my LG-D801
Click to expand...
Click to collapse
It would help if you told us what it is you're trying to do. If you just want a full list of every command then there's threads and websites that have it all. If you're trying to do something specific then let us know and we'll try and give you the correct commands.
The most common you'll use are:
adb devices - To ensure phone is connected correctly.
adb shell - To access the phone shell (?).
adb push [filename] /path/to/destination - Send a file from PC to phone, usually the sdcard.
Mr_JMM said:
It would help if you told us what it is you're trying to do. If you just want a full list of every command then there's threads and websites that have it all. If you're trying to do something specific then let us know and we'll try and give you the correct commands.
The most common you'll use are:
adb devices - To ensure phone is connected correctly.
adb shell - To access the phone shell (?).
adb push [filename] /path/to/destination - Send a file from PC to phone, usually the sdcard.
Click to expand...
Click to collapse
If it makes any sense I really wasn't trying to do anything specific I just wanted to make sure everything was working right. And as for what wasn't working for me was telling the phone to go into recovery. That's honestly the only thing I was trying.
Sent from my LG-D801 using xda app-developers app
You don't need a shell for this
adb reboot recovery
Should do the trick, opening a shell gets you into the phones file system which is not needed to reboot to recovery
Just do a quick Google search and you will find many guides on this, especially here in xda
Sent from my Nexus 7 using XDA Premium 4 mobile app