Im using CM 7.2 RC1 hero ported to X8 but when i want check logcat it just blank doesn't appear anything.
Anyone knows about it ?
PLease help
Advance thanks.
weird ...maybe it is a problem with the rom or maybe it is a bug
The ROM it's self have logcat in system/bin/
Others all fine but only this logcat give problem....
Actually i was updated rooting system to SuperSU and Binary plus changed busybox to 1.19.4 version and toolbox too.
Do you thing it's happen because of this updating ?
VillainZ said:
The ROM it's self have logcat in system/bin/
Others all fine but only this logcat give problem....
Actually i was updated rooting system to SuperSU and Binary plus changed busybox to 1.19.4 version and toolbox too.
Do you thing it's happen because of this updating ?
Click to expand...
Click to collapse
I am having a similar concern. Mine says "waiting for device", but nothing happens. The logcat file exists but is blank.
jnow2 said:
I am having a similar concern. Mine says "waiting for device", but nothing happens. The logcat file exists but is blank.
Click to expand...
Click to collapse
do you have usb debugging enabled?
fifo171 said:
do you have usb debugging enabled?
Click to expand...
Click to collapse
Yes, usb debugging is enabled. I am able to copy files between pc and phone, push adb commands via terminal, etc. Logcat is the only issue I'm having.
I was able to find help in another forum. My problem was that I was using adb commands through Terminal Emulator. I initially entered "adb logcat > /sdcard/logcat.txt". As long as you type "su" and receive "#" prompt, type the same command above eliminating" adb". It works. Hope this helps!
Sent from my LS670 using XDA
MIT activity manager
jnow2 said:
I was able to find help in another forum. My problem was that I was using adb commands through Terminal Emulator. I initially entered "adb logcat > /sdcard/logcat.txt". As long as you type "su" and receive "#" prompt, type the same command above eliminating" adb". It works. Hope this helps!
Sent from my LS670 using XDA
Click to expand...
Click to collapse
My adb logcat shows:
W/WindowManager( 152): Window Window{2b2f8b10 com.crashapps.easypccontrol_android/com.crashapps.easypccontrol_android.ServersActivity paused=false} destroying surface Surface(name=com.crashapps.easypccontrol_android/com.crashapps.easypccontrol_android.ServersActivity, identity=152), session Session{2b254ba8 uid 10071}
I want to open it in MIT activity manager any ideias?
Related
Hey guys i downloaded z4 root from xda. When i try to install it blocks my install attemp for security reasons . I then enable usbdebugging and z4 root still wont install. Seems like I'm the last one to do this. Please help.
Use SuperOneClick instead. The default AT&T rom blocks sideloading of apps.
Or just enable USB debugging and then use "adb install z4root.apk". Done.
Dear all
I am using new firmwave
P1000DXJM2 just release today . 11.1.2011
Cannot use z4root. After running for a while the program force to close. .
Before i used version DXJJ1 and z4root working well
Any idea about this or any information to root again
Thank you
-------------------------------------
Sent via the XDA Tapatalk App on Tab
Use SuperOneClick
AT&T are dirty dirty people and do not allow "fun" on the Tab. Just flash the euro version then superoneclick and you wont have that problem
JaysFreaky said:
Or just enable USB debugging and then use "adb install z4root.apk". Done.
Click to expand...
Click to collapse
That was freakin genius! So easy and simple. Thank you.
JaysFreaky said:
Or just enable USB debugging and then use "adb install z4root.apk". Done.
Click to expand...
Click to collapse
What do you mean by "adb install z4root.apk"? Is that a command in the Linux terminal that you run?
synapseguru said:
What do you mean by "adb install z4root.apk"? Is that a command in the Linux terminal that you run?
Click to expand...
Click to collapse
You open adb.exe on your pc, then put the z4toot1.3.apk in your tools directory (our wherever adb.exe is), then type "adb devices" to verify your connection to your phone, then type the command mentioned earlier, but make sure you type the z4root name of the file.
Hi
I'm new to ADB and all the stuff, I just tried to use "adb root" on my LGO2X, to use the "adb logcat > file.txt" without getting an "acces denied" error.
The thing is that "adb root" says that it can't be run on a production build.
i'm stuck there, could someone help me ?
Thx.
1695 said:
Hi
I'm new to ADB and all the stuff, I just tried to use "adb root" on my LGO2X, to use the "adb logcat > file.txt" without getting an "acces denied" error.
The thing is that "adb root" says that it can't be run on a production build.
i'm stuck there, could someone help me ?
Thx.
Click to expand...
Click to collapse
You don't need a root shell to use logcat...
And no root shell on stock, you need to shell in then 'su'.
What is it ? ADB Shell . is it CMD command on Windows or what ?
muslimbaha said:
What is it ? ADB Shell . is it CMD command on Windows or what ?
Click to expand...
Click to collapse
https://developer.android.com/tools/help/adb.html
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Sorry, but i know what it is now, how do i run it though? im trying to follow the htc desire hd guide to root my phone, which everything is done up until the point i have to test that i have root in debug mode. Not sure how to do this? run abd.exe? it just showed me a cmd window which runs and then dissapears.
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
bitdomo said:
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What is likely to be the problem if it says SU permission denied?
If you are on stock, that means that you have no root access. If you have cm10 or cm10.1 you have to enable adb root access somewhere in the settings. I am sorry but I can not tell you at the moment where to enable it because I am on stock right now.
Sent from my LG-P990 using xda app-developers app
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Thanks Bro for this information
Hey guys,
I'm just trying to port a Rom...
I changed some settings and it installs clearly now, but it has a bootloop...
I'm trying to port the paranoid android rom from HTC One X, I think it's V3.10...
I just googled and searched around and I know that I should get a log via ADB...
The PC finds my device, in device manager it is in "portable devices" as "P880", but doesn't show it in "Computer"... There is just my HDD and my cd burner shown...
I start CMD before debugging phone on PC and type "adb logcat", ADB starts and the message "Waiting for device" appears...
I plug the phone in, boot it and the computer finds the device in device manager... But ADB still "waits for device"... When I open another CMD Window and type "adb devices" it shows a device which is "offline"...
I have installed the latest ADB drivers (needed them for unlocking BL) and LG Software drivers...
Is there any other way to show a log while booting or at least turn the device to "online"?
Thanks in advance!
The phone should be detected as adb device in device manager do you see any driver contains adb in it - you can try droid explorer for log cat but I think it depends on working adb too
Thanks, I will try it later!
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
Thanks for your reply, I have the newest SDK so I think newest ADB, too, so that's not the problem...
thank you for this hint, I will look into it and will search that string....
I'll report when I find it
Since you have SDK, use ddms.
Tested and.... Nothing -.-
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
Paulo87 said:
Since you have SDK, use ddms.
Click to expand...
Click to collapse
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
BlackDuty said:
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
Click to expand...
Click to collapse
you can stay with ddms, it's better IMO
now you can try to change "ro.secure=1" to "ro.secure=0", compile and try again now adb should start as soon as possible, even on kernel level
Argghhh
Why didn't you tell it earlier?
Just joking, thank you!
Will try and report...
Another try went wrong...
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
BlackDuty said:
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
Click to expand...
Click to collapse
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
laufersteppenwolf said:
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
Click to expand...
Click to collapse
Unfortunatly I can't use linux, just with a terminal over cygwin :|
I will try that method tomorrow, now I have to sleep
Thank you again, you make me feel a little bit smarter then I am atm
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Paulo87 said:
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Click to expand...
Click to collapse
As you can see in the attached picture in my previous posts, there is already the "ADB Interface" on device manager, or is there any difference between "Android ADB Interface" and "ADB Interface"?
I will try to reinstall it and look into the link to install USB-Drivers you wrote here, later!
Thank you for that many tries to help me! I hope we will find the right way...
Hey, some news:
@Paulo87 : I tried to reinstall the google drivers and use the device as Android ADB Interface and it worked when I am in recovery...
Looked at monitor and ddms, they found a device but there was no "online" or "offline", but a "??"
I flashed the files and rebooted, plugged data cable in and... There is still this MTP-Device shown, no Android ADB Interface...
Tried the same steps there but it told me that in the folder google drivers are no drivers for this MTP device...
I think I will kill me in the next hours
Nah, just joking, but this is really annoying...
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Paulo87 said:
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Click to expand...
Click to collapse
I already tried, but it hangs on the last step, it says that "last_kmsg" wasn't find... So if it doesn't exist , it's logical that you can't move it... Something like this
And you really don't want to know how near I am to do that thing what the guy in your picture did... :silly:
Any other suggestions?
BlackDuty said:
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Click to expand...
Click to collapse
this seems like the rom wasn't flashed?! or the rom has no su binary included...
and when it says, that last_kmsg wouldn't be found, it's most likely that you've got a serious problem with your kernel...
what kernel source are you using?
Honestly, i have no more ideas mate...
Good luck.
Glück
Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....
xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this
Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message
ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)
nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think
Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key
Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed
KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.
http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app
Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:
mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood