adb logcat read failure. hi guys i can't get logcat using adb. I've installed samsung driver . when i type adb devices i can see that my device is there but can't figured out why i can't get log.
S7
sac23 s9 port rom
Related
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Bump
Sn0w17 said:
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Click to expand...
Click to collapse
just went through this this morning too.
short version... make sure you have the newer version of adb installed and running from that directory... replace you older versions.
4.2.2 needs adb.exe 1.0.31 and can be downloaded here for windows pc.
if you have/need Linux or mac versions they are in the index of the folder too here
.
.
Hello guys i ported rom 4 my device and i have bootloop. When in cmd type "adb devices" i have message 4 verifing. But when i type "adb logcat", "adb logcat -f logcat.txt" or etc. i have message -waiting for device-. I tried with AIO Logcat but, i get this : http://prntscr.com/1rp25l
with adb logcat i gotta this http://prntscr.com/1rp2h6
Any help ? Thanks in advance.
As you can see, when you type adb devices, your device appears offline. Maybe this is caused by your ROM, maybe not, but you need to solve it first (I dunno how to do it, sorry).
Maybe you can find the problem with the Dalvik Debug Monitor (DDMs). It's part of the Android SDK.
See this thread:
http://forum.xda-developers.com/showthread.php?t=2304122
Thanks but not working "DDM"
As long you keep getting offline when you type adb devices, anything will work. As I said before, you need to fix that problem first.
I don't know how to do that !
Hello,
I'm new here and I would like to know if someone can help me with adb.
I want to use it to get a logcat and also a usage statistics.
So the problem is, I've setup adb and I've installed my phone's driver (Samsung) but when I try to list my device using "adb devices" I get this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and then it doesn't show me my device. So can I please get a solution for that?
Thank you so much!
It's seems like the forum is empty? I've wrote three posts so far and I don't get any comments. I don't know if I'm doing something wrong
Shupreme said:
Hello,
I'm new here and I would like to know if someone can help me with adb.
I want to use it to get a logcat and also a usage statistics.
So the problem is, I've setup adb and I've installed my phone's driver (Samsung) but when I try to list my device using "adb devices" I get this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and then it doesn't show me my device. So can I please get a solution for that?
Thank you so much!
Click to expand...
Click to collapse
try to reinstall the drivers, might you installed wrong drivers . also i think you should post this on your device's forum.
What is your device tho ?
I'll try to reinstall the driver. But I do know it's the right one, I've also tried to restart my computer. I have an old Samsung Galaxy Grand Neo Plus. So I think it's forum won't be as active as this one. And the problem can relate to any Android phone, it has more to do with adb and the driver maybe.
Thank you for your comment!
Shupreme said:
I'll try to reinstall the driver. But I do know it's the right one, I've also tried to restart my computer. I have an old Samsung Galaxy Grand Neo Plus. So I think it's forum won't be as active as this one. And the problem can relate to any Android phone, it has more to do with adb and the driver maybe.
Thank you for your comment!
Click to expand...
Click to collapse
Try to download the latest ADB from here XDA, also the device we are talking about is not s8 ?
hi , this is nandakishore.I have a rooted redmi 2 2014818 device but I flashed lollipop ROM (so now virtually my phone is redmi 2 prime ).Lately I have developed a great interest in using adb .My problem is that whenever I give some adb command that has some write operation involved in ,such as adb remount,adb pull build.prop it is not working.It gives me device not found error.I tried the above commands as both super user and as a normal user too.But the same thing is happening .what should I do to get the commands work .
Hello fellows...
I have a problem i never encountered before ...
If I try to connect to my phone by using "adb shell" I only receive this message:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I know, I am "just" not authorized ... but thats my problem!
The phone never asks for granting the permission ...
And I can't revoke any "granted" permissions, since my dev-menu is missing this point.
About my system:
I am running windows 10 with adb 1.0.39, fastboot is working without problems.
My phone is a Cubot X18 Plus running a treble GSI of Ressurection Remix 6.2.1 (Oreo 8.1).
Since other gsi/roms are able to use this, I would even consider the gsi as the problem, but it seems to be dead since it is oreo, but I posted in the thread anyway.
I have lost my device serial number (now 1234567ABCDEF) but this shouldn't be a problem, since it is working on stock rom.
Is there any way to get adb rights granted? Or get the menu action back to revoke all granted devices?
I can use the local shell without any problems, at least I get root access over there.
Greeting
houston
I have written a blog about how to manually add adbkey.pub to phone.
There are termux with root and TWRP on rootless phone methods.
murtezayesil.me/adb_vendor_keys-is-not-set.html
I have returned to stock, since no custom rom really worked.
But tanks for your answer, maybe other ppl will be able to use your post.