Aghisna-HMP-Lavender-2023-03-18-37.zip
10.7 MB
KSUuuuu
Build took 6 minute(s) and 14 second(s). | For Xiaomi Redmi Note 7/7s (lavender) | gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Build took 6 minute(s) and 14 second(s). | For Xiaomi Redmi Note 7/7s (lavender) | gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
👍2
There are two ways you can get logs.
The non-rooted way (you will need a PC)
1. Download the latest platform-tools for your operating system
• Windows
• Linux
2. Extract the zip to a folder and move into that folder in Command Prompt or Terminal:
cd <folder_location>
3. Plug in your device and accept the debugging prompt (turn on ADB in Settings > Developer Options if you don't see it).
4. Verify your device is recognized by typing adb devices
5. Take your log:
• logcat: adb logcat -d > test.log
• dmesg: adb shell dmesg > dmesg
6. Send the logs here and tag the maintainer.
The rooted way
1. Install termux or any other terminal app
2. Type su
3. Type cd /sdcard
4. Take your log:
• logcat: logcat -d > logcat.log
• dmesg: dmesg > dmesg
5. Send the logs here.
Other way
= HOW TO TAKE LOGS =
[ if rom stuck on boot animation or need regular logs ]
0. in twrp mount System and delete file /system/phh/secure and then reboot
1. while you see bootanimation connect phone to PC
2. adb logcat -d all > logs.txt
[ if rom not allowing adb (device unauthorized) ]
0. reboot to twrp
1. connect phone to the PC
2. run command from
*nix: adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
windows: adb push C:\Users\%PutHereYourUsername%\.android\adbkey.pub /data/misc/adb/adb_keys
3. now you can take logcat logs
[ if phone stuck/bootloop at splash ]
0. reboot to twrp right after stuck-splash or bootloop
1. try to find that logs:
/sys/fs/pstore/console-ramoops
/proc/last_kmsg
/proc/kmsg
2. copy logs to PC
(for sample, with command "adb pull /proc/last_kmsg lastkmsg.txt")
Or get logs without pc using this app:
https://play.google.com/store/apps/details?id=com.tortel.syslog
The non-rooted way (you will need a PC)
1. Download the latest platform-tools for your operating system
• Windows
• Linux
2. Extract the zip to a folder and move into that folder in Command Prompt or Terminal:
cd <folder_location>
3. Plug in your device and accept the debugging prompt (turn on ADB in Settings > Developer Options if you don't see it).
4. Verify your device is recognized by typing adb devices
5. Take your log:
• logcat: adb logcat -d > test.log
• dmesg: adb shell dmesg > dmesg
6. Send the logs here and tag the maintainer.
The rooted way
1. Install termux or any other terminal app
2. Type su
3. Type cd /sdcard
4. Take your log:
• logcat: logcat -d > logcat.log
• dmesg: dmesg > dmesg
5. Send the logs here.
Other way
= HOW TO TAKE LOGS =
[ if rom stuck on boot animation or need regular logs ]
0. in twrp mount System and delete file /system/phh/secure and then reboot
1. while you see bootanimation connect phone to PC
2. adb logcat -d all > logs.txt
[ if rom not allowing adb (device unauthorized) ]
0. reboot to twrp
1. connect phone to the PC
2. run command from
*nix: adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
windows: adb push C:\Users\%PutHereYourUsername%\.android\adbkey.pub /data/misc/adb/adb_keys
3. now you can take logcat logs
[ if phone stuck/bootloop at splash ]
0. reboot to twrp right after stuck-splash or bootloop
1. try to find that logs:
/sys/fs/pstore/console-ramoops
/proc/last_kmsg
/proc/kmsg
2. copy logs to PC
(for sample, with command "adb pull /proc/last_kmsg lastkmsg.txt")
Or get logs without pc using this app:
https://play.google.com/store/apps/details?id=com.tortel.syslog
👍2❤1