FORUMS

[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot

569 posts
Thanks Meter: 1,644
 
By USA-RedDragon, Senior Member on 28th November 2015, 05:43 AM
Post Reply Email Thread
17th June 2016, 09:26 PM |#11  
Senior Member
Flag Sion
Thanks Meter: 240
 
Donate to Me
More
Quote:
Originally Posted by Sun Shower

But the adb via usb need an authorization to enable,how to get pass when bootloop?

Sent from my MI 2C using XDA-Developers mobile app

use adbd
19th June 2016, 02:50 AM |#12  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by Gayos24

use adbd

Thank you to answer me,is there any thread or guide can help me,I don't know how to use it.
19th June 2016, 10:52 AM |#13  
Senior Member
Flag Sion
Thanks Meter: 240
 
Donate to Me
More
Quote:
Originally Posted by Sun Shower

Thank you to answer me,is there any thread or guide can help me,I don't know how to use it.

just donwload the file and extract adbd in system/xbin (rom)

and the command is the same as normal logcat

sorry for my english
Attached Files
File Type: zip adbd.zip - [Click for QR Code] (172.8 KB, 564 views)
The Following User Says Thank You to Gayos24 For This Useful Post: [ View ] Gift Gayos24 Ad-Free
20th January 2017, 07:41 PM |#14  
agriculture's Avatar
Senior Member
Flag Telangana
Thanks Meter: 337
 
More
awsome, just awsome
21st January 2017, 09:39 AM |#15  
Junior Member
Flag Surabaya
Thanks Meter: 2
 
More
what command did you type?
11th August 2018, 03:59 PM |#16  
Account currently disabled
Flag New Jersey
Thanks Meter: 330
 
More
I am currently testing out Custom ROMs for DEVs and I cannot find how to take a Log if I cannot Boot the device or get into TWRP. With newer devices, for example, I am currently working on a OnePlus 6, with A/B Partitions. If the device does not boot on A, it is supposed to Boot on B, so with this application, how to take a Log before the device switches Partitions and Boots on the Partition that CAN Boot?
13th October 2018, 06:59 PM |#17  
Senior Member
Thanks Meter: 17
 
More
I tried the adbd archive but there is no xbin folder for me, I just put in sbin folder. I cant get a logcat from boot because it says waiting for device the code i'm trying is this one adb logcat > logcat.txt
12th October 2019, 04:55 PM |#18  
Sutan99's Avatar
Junior Member
Flag Brebes
Thanks Meter: 1
 
More
Quote:
Originally Posted by USA-RedDragon

So your kernel didn't boot. Well dang. This can be one of the worst problems. So, I'm going to HOPE you have TWRP, since CWM is pretty much dead.

This is more advanced, because you have to use Terminal command in TWRP.

Now, don't be daunted by this, since it's terminal commands, it's quite easy.

As a general rule of thumb(there are different devices with different kernel logs, though), 3.10 kernels(pretty much anything in the last 2 years) have a log in /sys/fs/pstore/console-ramoops and 3.4 and prior kernels have /proc/last_kmsg.

You can see kernel version in Settings -> About Phone

So to pull these logs, you need to be in TWRP DIRECTLY after a failed boot.

Go to Advanced->Terminal Command and type these commands in. One will fail the other will work. Should both of them fail, restart and try to boot again, then go back to TWRP.

Code:
cp /proc/last_kmsg /sdcard/kernellog.txt
Code:
cp /sys/fs/pstore/console-ramoops /sdcard/kernellog.txt
Now you can restore your backup and boot normally. Once you've booted up, you can either share the files with Google Drive or Dropbox or whatever in Android, or you can pull them to your computer with these Terminal commands:
On Linux:
Code:
adb pull /sdcard/kernellog.txt ~/kernellog.txt
That will store log into your home folder.
On Windows:
Code:
adb pull /sdcard/kernellog.txt %UserProfile%/Desktop/kernellog.txt
That will store log onto your Desktop.

Then share log like you would in the above post

sorry but in my device wasn't have this "/sys/fs/pstore/console-ramoops" I was browse, and did not found it... only have "sys/fs/..." if I try, still work it or not?
2nd June 2020, 09:56 PM |#19  
Member
Thanks Meter: 9
 
More
I have a couple of questions and I'm hoping that this forum can provide a response.

1. adb logcat not found
I have a linux laptop and have installed platform tools and have used fastboot, adb sideload quite a bit. But adb logcat just does not work.
see below while inside TWRP

5x $ adb devices
List of devices attached
00ca0a5e7fe31c03 recovery
5x $ adb logcat
/sbin/sh: exec: line 1: logcat: not found
5x $ adb shell
~ # logcat
/sbin/sh: logcat: not found

whats missing?

2. When should adb logcat be run if I wanted to capture logs when my phone keeps spinning on google animation? Can i run adb logcat > foo while I'm in recovery and then reboot from recovery or is there a different method?

thanks
7th June 2020, 07:35 PM |#20  
Member
Thanks Meter: 9
 
More
I was hoping that someone could respond to the right way to capture logs during bootloop.
My problem:
Trying to capture logs on a bootloop of andrid 10 pixel experience on nexus 5x.

What I have do so far?

Flashed the ROM and zip and rebooted. No logcat seen.

My specific question.
OP says this.

After flashing, hook the phone/tablet up to your computer and run this in your Terminal:
On Linux:
Code:
adb logcat > ~/log.txt


My problem is that when the phone is rebooting, adb devices does not show anything and thus adb logcat always displays a <waiting for device> message. Thus, how can any log be captured to debug the problem?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes