Hey, I was just wondering what I could be doing wrong. I'm running Slim bean RC1 on my sprint galaxy nexus with Franco Kernel. I enabled logging and event logging in my kernel manager. But when I go into terminal and adb logcat, it just says waiting for device and doesn't show logging. I am confused. Why can't I view the logcat? Also tried alogcat and catlog and none of them load any lines of log. Please help thank you.
Sent from my Galaxy Nexus using xda premium
PowderdToastMan said:
Hey, I was just wondering what I could be doing wrong. I'm running Slim bean RC1 on my sprint galaxy nexus with Franco Kernel. I enabled logging and event logging in my kernel manager. But when I go into terminal and adb logcat, it just says waiting for device and doesn't show logging. I am confused. Why can't I view the logcat? Also tried alogcat and catlog and none of them load any lines of log. Please help thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Do you have USB debugging on, under developer options?
sent from my Google Galaxy Nexus
PowderdToastMan said:
Hey, I was just wondering what I could be doing wrong. I'm running Slim bean RC1 on my sprint galaxy nexus with Franco Kernel. I enabled logging and event logging in my kernel manager. But when I go into terminal and adb logcat, it just says waiting for device and doesn't show logging. I am confused. Why can't I view the logcat? Also tried alogcat and catlog and none of them load any lines of log. Please help thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Either you don't have USB-Debugging enabled,
or you don't have to necessary drivers installed.
I forgot to mention that I used the android terminal emulator not terminal on a desktop. But yes I do have android debugging enabled.
Should I just try getting a logcat from adb via USB? I don't really understand adb though and I have a Mac so it's not really a development friendly environment either.
Sent from my Galaxy Nexus using xda premium
PowderdToastMan said:
I forgot to mention that I used the android terminal emulator not terminal on a desktop. But yes I do have android debugging enabled.
Should I just try getting a logcat from adb via USB? I don't really understand adb though and I have a Mac so it's not really a development friendly environment either.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You don't need to type "adb" when you're working from your device - adb is for connecting to a remote device...
Related
I triy to type "adb shell" in cmd which works but upon typing "su", it throws me a: "permission denied" and on the screen it says: "shell has been denied Superuser permissions.
In the superuser app, there is no record of ever accepting or denying "shell" and clearing Superuser's apk data doesn't help. Everything else related to root works besides giving adb root permissions.
What to do? In some other forum, someone said it was kernel related?
You need to go to settings then developers options and enable root access to adb.
Sent from my Galaxy Nexus using xda premium
jhernand1102 said:
You need to go to settings then developers options and enable root access to adb.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not running CM9 anymore, though, but I have no such option? I'm running stock.
Theshawty said:
Not running CM9 anymore, though, but I have no such option? I'm running stock.
Click to expand...
Click to collapse
*facepalm*
Stock rom does not come rooted, so having that option under stock settings menu wouldnt make any sense.
And you still remember that you opened this because of a feature of cm9, that you were not familiar with at the time?
Sent from my i9250 using Forum Runner
bk201doesntexist said:
*facepalm*
Stock rom does not come rooted, so having that option under stock settings menu wouldnt make any sense.
And you still remember that you opened this because of a feature of cm9, that you were not familiar with at the time?
Sent from my i9250 using Forum Runner
Click to expand...
Click to collapse
Well obviously I have rooted my phone and now when I tried that command again (for like the 30th time) it magically worked.
I don't know why, though. "Shell" couldn't seem to get superuser permissions when everything else that required root worked perfectly?
If youre talking about stock, Kernel/boot.img is secure
But it should work.
Sent from my i9250 using Forum Runner
bk201doesntexist said:
If youre talking about stock, Kernel/boot.img is secure
But it should work.
Sent from my i9250 using Forum Runner
Click to expand...
Click to collapse
I've never understood what the difference between "secure" and "insecure" boot.img is.
Hi, has anyone managed to get ADB working with Jelly Bean? I'm running CM10 and I can't seem to get ADB working. I've downloaded the drivers from the SDK but windows still says it can't find the driver, even when I manually specify where the driver is.
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
I'm aware of that
strumcat said:
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Click to expand...
Click to collapse
Alright, will do. Not at home now. I've never had any ADB drivers installed as this is a clean windows 7 install.
geoffcorey said:
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yep, pretty sure I do.
adbWireless
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
Can you get a log through fastboot? I need to get a log of boot loop
RichyRicho said:
Can you get a log through fastboot? I need to get a log of boot loop
Click to expand...
Click to collapse
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Even today, a friend of mine installed the naked drivers, started adb, device found
I watched him as he did it, guiding him through the commands to push, reboot recovery, the works, and Windows 7 pulled it quite well.
I don't use windows at home, but he did it without troubles at all.
So yeah. ADB has been around for ages, and it will be coming back.
And it's the second proof I see: most of these so called issues with drivers, should be handled on <insert host OS here> forums and not on xda. Most of times, users just don't get it.
Sent from my i9250
Pirateghost said:
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
RichyRicho said:
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
Click to expand...
Click to collapse
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
k786 said:
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
Click to expand...
Click to collapse
Sorry I have an Xperia S...didnt realise which forum i was in...i dont think the S has naked drivers and the 64 bit ones here dont even work
Hi all, I wanted to make a logcat, because, believe me, even I hate submitting a bug without a logcat.
So, I searched up on Google and and learnt how to do one using terminal emulator. My questions:
1: Does the terminal emulator session run even after flashing a mod to your rom, and let's say, the phone doesn't boot up?
2. How to stop the the logcat and save it? The command, logcat > /sdcard/ apparently doesn't work because new things keep on happening and I can't type that fast.. So how do I do it?
(And BTW, I have tried using alogcat but doesn't work on jb)
any help would be appreciated.
Thanks!
https://sites.google.com/site/androidsamurai/Home/adb-for-dummies-1
http://forum.xda-developers.com/showthread.php?t=1747544
http://mobility.forumsee.com/a/m/s/p12-9379-050574--installing-adb-sdk-and-how-make-logcat.html
https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
Lloir said:
https://sites.google.com/site/androidsamurai/Home/adb-for-dummies-1
http://forum.xda-developers.com/showthread.php?t=1747544
http://mobility.forumsee.com/a/m/s/p12-9379-050574--installing-adb-sdk-and-how-make-logcat.html
https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
Click to expand...
Click to collapse
Thanks a bunch, the links were helpful, especially the last one. But I still can't save it, I can't type that fast! Its like i type the word 'logcat' and something new happens and its gone!Or is it just impossible to do from terminal emulator?
Sent from my One V using xda app-developers app
do the following
su
logcat > /sdcard/namehereforlogcat.txt
Lloir said:
do the following
su
logcat > /sdcard/namehereforlogcat.txt
Click to expand...
Click to collapse
Great.
But q no. 1..?
Sent from my One V using xda app-developers app
you dont, you run it via adb logcat on your pc terminal
This has been mentioned a lot of times but I still can't figure it out.
I'm running 4.2.2 on my Galaxy Nexus stock and the Adb is Offline in fastboot and in the Galaxy Nexus Toolkit.
What can I do to make it online?
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
This has been mentioned a lot of times but I still can't figure it out.
I'm running 4.2.2 on my Galaxy Nexus stock and the Adb is Offline in fastboot and in the Galaxy Nexus Toolkit.
What can I do to make it online?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try to Enable USB debugging under Developer Options?
Yes its enabled.
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
Yes its enabled.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
while connected to the computer you are trying to ADB from, toggle debugging OFF and then toggle it back ON. you should see a security authorization question to allow access from that computer and the option to remember your choice.
in 4.2.x, they seem to have added a layer of security and if you simply enabled debugging with no computer connected at the time, you won't have gotten this prompt. if you connect to a different computer at some point and need ADB functions from that one, you'll need to be connected, disable debugging, then enable it and answer the security question for THAT computer as well.
tgeery said:
while connected to the computer you are trying to ADB from, toggle debugging OFF and then toggle it back ON. you should see a security authorization question to allow access from that computer and the option to remember your choice.
in 4.2.x, they seem to have added a layer of security and if you simply enabled debugging with no computer connected at the time, you won't have gotten this prompt. if you connect to a different computer at some point and need ADB functions from that one, you'll need to be connected, disable debugging, then enable it and answer the security question for THAT computer as well.
Click to expand...
Click to collapse
Correct. Although you don't need to disable/re-enable USB debugging before connecting to another host. Android will pop-up the "security question" again. At least on Linux hosts.
@OP, make sure you are using latest ADB binaries. Read efrant's 101 stickied on Q&A.
Sent from my Nexus
Still says offline. And I can't issue any commands in fastboot.
I'd thought I'd let everyone know though that Wugs toolkit seemed to work fine. I'm now rooted with A custom recovery
I'd like to thank everyone for helping! Or at least trying. :thumbup:
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
Still says offline. And I can't issue any commands in fastboot.
I'd thought I'd let everyone know though that Wugs toolkit seemed to work fine. I'm now rooted with A custom recovery
I'd like to thank everyone for helping! Or at least trying. :thumbup:
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then you need updated adb binary. Fastboot only works on fastboot interface, not Android. But you might need to update both adb and fastboot binaries. The toolkit probably already updated them, that's why it works, not because you're using a toolkit, learning nothing.
Sent from my Nexus
I've actually entirely used fastboot prior to 4.2.2, I've updated binaries and adb. I still can't issue commands in fastboot and the device is still listed as 'offline'.
I'm only using the Galaxy Nexus temporarily as my S3 is at repairs. So I'm not concerned about it
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
I've actually entirely used fastboot prior to 4.2.2, I've updated binaries and adb. I still can't issue commands in fastboot and the device is still listed as 'offline'.
I'm only using the Galaxy Nexus temporarily as my S3 is at repairs. So I'm not concerned about it
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, you're holding it wrong. It works. 4.2.2 brought new binaries for adb and fastboot. Anyways... Hope you get that S3 fast enough. *sigh*
Sent from my Nexus
I'm not a noob I promise. I'm just too sick to try hard.
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
I'm not a noob I promise. I'm just too sick to try hard.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Feeling better now?
I just rooted the S3 using ODIN, but I still can't get into the data partition. [adb backup -f data data.img] doesn't seem to work (it asks me to confirm it on my phone...broken screen), and neither does [adb pull /data/data %userprofile%\desktop]. It's on 4.3 and usb debugging is disabled. The only thing I need is to have usb debugging enabled and I can take it from there. I've tried editing the settings.db file in com.android.providers.settings, and when I use [adb devices], it lists the S3 but it says it's offline (probably because I have to allow it on the phone, but the touchscreen is broken). Any suggestions?
tl;dr I need to pull files from /data/data, keep getting denied. If I can get usb debugging to work on 4.3 I may be able to figure out the rest myself.
edit: I couldn't find one (three days of searching), but if anyone knows of a 4.3 ODIN file with usb debugging enabled for all computers, please let me know.
edit 2: By broken, I mean completely shattered.
You may want to push Wireless ADB.I believe it does turn on Debug by default. Then there's ADB Commander or suchlike app for PC. It can get to the Partition.
Perseus71 said:
You may want to push Wireless ADB.I believe it does turn on Debug by default. Then there's ADB Commander or suchlike app for PC. It can get to the Partition.
Click to expand...
Click to collapse
Android Commander is a godsend, but I've installed every Wireless ADB through play.google.com to the S3 and I've had no luck. [adb devices] still shows the S3's serial number, but it still says that it's offline. Is there any ODIN tarball that has usb debugging enabled by default? or is there a way I can downgrade to 4.1.2 from 4.3?
Youll probably need an insecure kernel.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Youll probably need an insecure kernel.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I can't find any ODIN-able insecure kernels, but I can get into ADB while I'm in recovery. How would I go about flashing an update.zip I put in /sdcard through adb? Thanks in advance.
Ill try to make one for you in a while. What rom/build were you running?
Sent from my SGH-T999 using Tapatalk
Hetes the kernel thread. Its in general section.
http://forum.xda-developers.com/showthread.php?t=2407583
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Hetes the kernel thread. Its in general section.
http://forum.xda-developers.com/showthread.php?t=2407583
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ah. I've found that thread yesterday while searching for an insecure kernel after reading your reply. However, I couldn't seem to find one for my ROM. Thanks though!
DocHoliday77 said:
Ill try to make one for you in a while. What rom/build were you running?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
That would be great! But the ROM I'm using is the root66 T999_UVUEMJC from this thread. It was the earliest one that would flash without a NAND write error and the only other ODIN root I could find; I tried using CF-root but it didn't seem to stick.