inferno0230

inferno0230 / bugreport.md

Last active 1 week ago

Like 0

inferno0230 revised this gist 1 week ago · 6cd676c

1 file changed, 46 insertions

bugreport.md (file created)
@@ -0,0 +1,46 @@
1 + # How to Report Bugs / Take Logs
2 +
3 + ## Rules
4 + \- Bug reports must be on an **UNMODIFIED** system.\
5 + \- **No Magisk / KernelSU / any root.** Reports with root will be ignored.
6 +
7 + ## Prerequisites
8 + \- ADB and Fastboot **v33 or newer** ([Platform-Tools](https://developer.android.com/tools/releases/platform-tools))\
9 + \- USB debugging enabled\
10 + \- If you don't know how to set this up, ask any LLM (ChatGPT, Claude, Gemini, etc.) to guide you.
11 +
12 + ## 1. Logcat from boot (required for any system bug)
13 + 1\. Turn the phone off and connect it to the PC\
14 + 2\. Run:
15 + ```
16 + adb wait-for-device logcat -b all > logcat.txt
17 + ```
18 + 3\. Power on the phone. Logging starts at the Google logo.\
19 + 4\. Reproduce the bug, then press `Ctrl + C`
20 +
21 + ## 2. Dmesg (right after the bug happens)
22 + ```
23 + adb shell dmesg > dmesg.txt
24 + ```
25 + Send **both** `logcat.txt` and `dmesg.txt`.
26 +
27 + ## 3. Black screen + not on ADB
28 + The phone is probably in EDL mode. Take a memory dump using [bkerler/edl](https://github.com/bkerler/edl):
29 + ```
30 + edl memorydump
31 + ```
32 + This creates a `memory` folder. Send that whole folder.
33 +
34 + ## 4. Visual bugs
35 + Also attach a screen recording (or a video from another phone if it can't be screen-recorded).
36 +
37 + ## When reporting, include
38 + \- ROM version / build date\
39 + \- What went wrong + steps to reproduce\
40 + \- Logs as **files** (no screenshots, no pasted text)\
41 + \- Screen/video recording for visual bugs
42 +
43 + ## Privacy
44 + Logs can contain sensitive info. If you're worried about that, send them to my DM instead of the group.
45 +
46 + **No logs = no fix.**