[XDA-University] USA-RedDragon:
Hello all,

I've noticed the lack of a guide for pulling ADB logs for developers. Being a developer, I wanted a quick link to send people to, rather than reexplaining.

If you are looking for a GENERAL explanation on how to get a logcat, or setup your computer for pulling a logcat, look at this amazing guide here:

http://xdaforums.com/showthread.php?t=2274119

Consider this guide an extension for the above thread, making an easy how-to for developers to point people to.

What this guide is NOT:

- A guide on how to pull a logcat in general

- A guide on how to setup adb on a computer

This guide is/will:

-Assume you know how to connect via adb

-Assume you have installed drivers and adb

-A way to show common users to get the logs the developers need

So I personally build for devices I don't own. A LOT. So, should it bootloop(specifically this) or not boot at all, I NEED these logs to help fix the problem. Most users are willing to do so..... as long as you teach them. So this is my one-size-fits-all guide to this.

Note: Later, I will do a write-up on how to pull kernel logs as an extension to this in the second post

To pull a logcat during a bootloop, you need to have adb permissive. This can be done several ways. I have added to the build.prop manually before but that was in TWRP and is a pain to guide users on. It's SUPPOSED to be done with the ramdisk, but I can't ask users to pull their ramdisk and edit it and reflash. So I have made a flashable zip to extract ramdisk and add a permissive adb property to default.prop

The zip will be in the downloads below, all you need to do is flash it when you see a ROM is bootlooping.

Note: Some kernels may not work with this, and it's based off of Anykernel. If the zip fails, don't worry, it has a fallback that it will add same thing to build.prop, and that should usually work.

After flashing, hook the phone/tablet up to your computer and run this in your Terminal:

On Linux:

adb logcat > ~/log.txt

That will store logcat into your home folder.

On Windows:

adb logcat > %UserProfile%/Desktop/log.txt

That will store logcat on your Desktop.

How do I stop logging?

You can either stop logging by hitting [CTRL] + C in the terminal or by unplugging device.

How do I know when to stop logging?

Usually, you can safely stop logging after about one minute for MOST problems, BUT I believe 5 minutes of logging would be the best bet to stop logging, so all the errors are caught.

How do I get the log to the developer?

You can get a log to a developer by Dropbox, Google Drive, or a file sharing site, but personally I like pasting sites like hastebin.com, pastebin.com, or paste.ubuntu.com. This is a developers/users personal preference though. Personally, I really, really like hastebin. For a pasting site, just open it in your browser and open the log with notepad or equivalent, and do [CTRL] + A and [CTRL] + C to copy the whole log, then paste onto the site. Then share the link the site gives you with the developer.

How do I get the log, when I didn't even get to the boot animation?

Usually, this is a kernel problem, and is almost deserving of it's own write-up, and instructions will be available in the second post.

Thank you all, and should you see a problem, or need more questions answered, please tell me so in replies.

Keep it cool,

Jacob(USA-RedDragon)