Revision history for MagiskHelpBugs


Revision [1043]

Last edited on 2021-12-11 12:59:10 by didgeridoohan
Additions:
~-//**dmesg**// Can be run directly from the device or through ADB, but root is necessary. The command is simply "dmesg > /sdcard/dmesg.txt" (or whatever path you want to use or file name you want to give it). If running through ADB, put "adb shell su -c" in front of the command.
Deletions:
~-//**dmesg**// Can be run directly from the device (if root is working) or through ADB. The command is simply "dmesg > /sdcard/dmesg.txt" (or whatever path you want to use or file name you want to give it).

Revision [1042]

Edited on 2021-12-11 12:57:25 by didgeridoohan
Additions:
~- //**The device doesn't boot/bootloops**// - A logcat during boot (either through ADB or a boot script) or dmesg are the only thing that really could show what's going on. A Magisk log might be good for complementary information.
~- //**Something doesn't work right**// -If something about your system or Magisk just doesn't work right, a dmesg or boot logcat might show what's wrong.
~-//**dmesg**// Can be run directly from the device (if root is working) or through ADB. The command is simply "dmesg > /sdcard/dmesg.txt" (or whatever path you want to use or file name you want to give it).
Deletions:
~- //**The device doesn't boot/bootloops**// - A logcat during boot (either through ADB or a boot script) is the only thing that really could show what's going on. A Magisk log might be good for complementary information.

Revision [987]

Edited on 2021-02-23 08:48:20 by didgeridoohan
Additions:
~- //**Installation of Magisk or modules fail**// - If installing from recovery, you'll need the //recovery log// and if installing from the Magisk app you need to save the installation log.
~- //**The Magisk app crashes**// - A logcat when the crash occurs will be necessary.
~- //**Installation log**// from the Magisk app (press "Save log" after installing Magisk or a module). If you experience errors when installing Magisk or modules in the Magisk app.
~- //**Magisk log**// save from the Magisk app or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below. **Note that when reporting about issues and bugs it is required to use verbose logging (//see "Verbose logging" below//).**
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]], an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] or a logcat bootscript (see below). It might be a good idea to start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Magisk app is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
Deletions:
~- //**Installation of Magisk or modules fail**// - If installing from recovery, you'll need the //recovery log// and if installing from the Manager you need to save the installation log.
~- //**The Magisk Manager crashes**// - A logcat when the crash occurs will be necessary.
~- //**Installation log**// from the Manager (press "Save log" after installing Magisk or a module). If you experience errors when installing Magisk or modules in the Manager.
~- //**Magisk log**// save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below. **Note that when reporting about issues and bugs it is required to use verbose logging (//see "Verbose logging" below//).**
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]], an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] or a logcat bootscript (see below). It might be a good idea to start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.

Revision [906]

Edited on 2020-10-05 07:23:47 by didgeridoohan
Additions:
All bug reports should be made on the [[https://github.com/topjohnwu/Magisk#bug-reports | the Magisk Github repo]]. The same tips that are outlined above apply.
Deletions:
All bug reports should be made on the [[https://github.com/topjohnwu/Magisk | the Magisk Github repo]].

Revision [905]

Edited on 2020-10-05 07:22:28 by didgeridoohan
Additions:
When reporting a bug, make sure you have the latest [[https://github.com/topjohnwu/Magisk#bug-reports | Canary bleeding edge build]] installed on your device. Otherwise any bug you're reporting may already be fixed upstream. It will also have much more detailed logging enabled (see below).
All bug reports should be made on the [[https://github.com/topjohnwu/Magisk | the Magisk Github repo]].
When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://github.com/topjohnwu/Magisk#bug-reports | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, this is a requirement.**
Deletions:
When reporting a bug, make sure you have the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]] installed on your device. Otherwise any bug you're reporting may already be fixed upstream. It will also have much more detailed logging enabled (see below).
When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, it is required to use the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]] and the verbose logging.**

Revision [886]

Edited on 2020-08-11 02:48:49 by didgeridoohan
Additions:
rm -f /cache/bootlog.log
Deletions:
rm -f /cache/bootlog.log ${Loc}/bootlog.log

Revision [859]

Edited on 2020-06-01 01:44:49 by didgeridoohan
Additions:
logcat -f /cache/bootlog.log &
kill %1
do
[ -e ${Loc}/bootlog.log ] && mv -f ${Loc}/bootlog.log ${Loc}/bootlog_last.log
cp -f /cache/bootlog.log ${Loc}/bootlog.log
rm -f /cache/bootlog.log ${Loc}/bootlog.log
Deletions:
logcat -d -f /cache/boot.log
do
[ -e ${Loc}/boot.log ] && mv -f ${Loc}/boot.log ${Loc}/boot_last.log
cp -f /cache/boot.log ${Loc}/boot.log && rm -f /cache/boot.log

Revision [848]

Edited on 2020-05-17 01:08:00 by didgeridoohan
Additions:
sleep 30
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.
Deletions:
sleep 60
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.

Revision [847]

Edited on 2020-05-17 01:06:05 by didgeridoohan
Additions:
sleep 60
logcat -d -f /cache/boot.log
until [ -e ${Loc}/testx ]
do
touch ${Loc}/testx
rm -f ${Loc}/testx
cp -f /cache/boot.log ${Loc}/boot.log && rm -f /cache/boot.log
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.
Deletions:
# Wait to make sure props have been reset
while [ $(getprop sys.boot_completed) == 1 ]; do
# Pause until boot has been completed
until [ $(getprop sys.boot_completed) == 1 ]; do
sleep 15 # Number of seconds to keep recording after boot is completed.
logcat -d -f ${Loc}/boot.log
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. This will record until boot has completed and an additional 15 seconds, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.

Revision [846]

Edited on 2020-05-16 10:52:18 by didgeridoohan
Additions:
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. This will record until boot has completed and an additional 15 seconds, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.
Deletions:
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.

Revision [845]

Edited on 2020-05-16 10:51:16 by didgeridoohan
Additions:
# Wait to make sure props have been reset
while [ $(getprop sys.boot_completed) == 1 ]; do
# Pause until boot has been completed
until [ $(getprop sys.boot_completed) == 1 ]; do
sleep 15 # Number of seconds to keep recording after boot is completed.
logcat -d -f ${Loc}/boot.log
Deletions:
sleep 60
logcat -d -f /cache/boot.log
until [ -e ${Loc}/testx ]
do
touch ${Loc}/testx
rm -f ${Loc}/testx
cp -f /cache/boot.log ${Loc}/boot.log && rm -f /cache/boot.log

Revision [844]

Edited on 2020-05-15 15:54:00 by didgeridoohan
Additions:
do
Deletions:
do

Revision [843]

Edited on 2020-05-15 15:53:21 by didgeridoohan
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put the following code snippet in it (thank you [[https://forum.xda-developers.com/member.php?u=8340552 | jenslody]] and [[https://forum.xda-developers.com/member.php?u=4487388 | jcmm11]] for help with the script). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put the following code snippet in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh

Revision [842]

Edited on 2020-05-15 13:35:15 by didgeridoohan
Additions:
cp -f /cache/boot.log ${Loc}/boot.log && rm -f /cache/boot.log
Deletions:
cp -f /cache/boot.log ${Loc}/boot.log
rm -f /cache/boot.log

Revision [841]

Edited on 2020-05-15 11:48:57 by didgeridoohan
Additions:
cp -f /cache/boot.log ${Loc}/boot.log
rm -f /cache/boot.log
Deletions:
mv -f /cache/boot.log ${Loc}/boot.log

Revision [840]

Edited on 2020-05-15 10:30:09 by didgeridoohan
Additions:
} &%%This will save a logcat to a file named boot.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.
Deletions:
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.

Revision [839]

Edited on 2020-05-15 10:29:51 by didgeridoohan
Additions:
logcat -d -f /cache/boot.log
[ -e ${Loc}/boot.log ] && mv -f ${Loc}/boot.log ${Loc}/boot_last.log
mv -f /cache/boot.log ${Loc}/boot.log
Deletions:
logcat -d -f /cache/bootlog.log
[ -e ${Loc}/bootlog.log ] && mv -f ${Loc}/bootlog.log ${Loc}/bootlog_last.log
mv -f /cache/bootlog.log ${Loc}/bootlog.log

Revision [838]

Edited on 2020-05-15 10:28:44 by didgeridoohan
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put the following code snippet in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh

Revision [837]

Edited on 2020-05-15 10:28:13 by didgeridoohan
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automated script creation process you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Below you can find a very simple example script that you can use, but I highly recommend the you try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes. If you want to do it manually, read on: Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs.

Revision [836]

Edited on 2020-05-15 10:26:43 by didgeridoohan
Additions:
sleep 60
logcat -d -f /cache/bootlog.log
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 60 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs.
Deletions:
logcat -f /cache/bootlog.log &
sleep 30
kill %1
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs.

Revision [835]

Edited on 2020-05-15 10:25:21 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Below you can find a very simple example script that you can use, but I highly recommend the you try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes. If you want to do it manually, read on: Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
logcat -f /cache/bootlog.log &
sleep 30
kill %1
until [ -e ${Loc}/testx ]
do
touch ${Loc}/testx
rm -f ${Loc}/testx
mv -f /cache/bootlog.log ${Loc}/bootlog.log
exit
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs.
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/service.d, give it execution permission and put the following code snippet in it (thank you @jenslody and @jcmm11 for help with the script). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in service.d.%%#!/system/bin/sh
until [ $(getprop sys.boot_completed) == 1 ]; do
logcat -d -f ${Loc}/bootlog.log
exit $$
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automatic setup you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.

Revision [834]

Edited on 2020-05-15 10:24:32 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/service.d, give it execution permission and put the following code snippet in it (thank you @jenslody and @jcmm11 for help with the script). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in service.d.%%#!/system/bin/sh
until [ $(getprop sys.boot_completed) == 1 ]; do
logcat -d -f ${Loc}/bootlog.log
exit $$
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs. If you want a more automatic setup you can try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes.
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Below you can find a very simple example script that you can use, but I highly recommend the you try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes. If you want to do it manually, read on: Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
logcat -f /cache/bootlog.log &
sleep 30
kill %1
until [ -e ${Loc}/testx ]
do
touch ${Loc}/testx
rm -f ${Loc}/testx
mv -f /cache/bootlog.log ${Loc}/bootlog.log
exit
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs.

Revision [833]

Edited on 2020-05-14 04:19:53 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Below you can find a very simple example script that you can use, but I highly recommend the you try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable (the boot script option can be found under the logcat menu) and can also be used for a number of other information collecting purposes. If you want to do it manually, read on: Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Below you can find a very simple example script that you can use, but I highly recommend the you try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable and can also be used for a number of other information collecting purposes. If you want to do it manually, read on: Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh

Revision [832]

Edited on 2020-05-14 04:08:49 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Below you can find a very simple example script that you can use, but I highly recommend the you try the [[https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260 | TeMeFI App]] by XDA recognised contributor [[https://forum.xda-developers.com/member.php?u=5417899 | DiamondJohn]]. It is highly customisable and can also be used for a number of other information collecting purposes. If you want to do it manually, read on: Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh

Revision [784]

Edited on 2020-01-03 02:28:06 by didgeridoohan [Reverted to previous revision]
Additions:
logcat -f /cache/bootlog.log &
Loc='/data/media/0'
until [ -e ${Loc}/testx ]
do
sleep 1
touch ${Loc}/testx
done
rm -f ${Loc}/testx
[ -e ${Loc}/bootlog.log ] && mv -f ${Loc}/bootlog.log ${Loc}/bootlog_last.log
mv -f /cache/bootlog.log ${Loc}/bootlog.log
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but if this isn't enough you can adjust the sleep time in the script to fit your needs.
Deletions:
rm -f /data/media/0/bootlog_last.log
[ -e /data/media/0/bootlog.log ]&&mv /data/media/0/bootlog.log /data/media/0/bootlog_last.log
logcat -f /data/media/0/bootlog.log &
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but of this isn't enough you can adjust the sleep time in the script to fit your needs.

Revision [708]

Edited on 2019-08-09 11:10:05 by didgeridoohan [Reverted to previous revision]
Additions:
Certain issues require different kinds of logs. Here's a list of examples (see further down for details on how to acquire the logs in question), but it's far from a complete list and only meant as an example of what logs may be useful:
Deletions:
Certain issues require different kinds of logs. Here's a list of examples (see further down for details on how to acquire the logs in question):

Revision [706]

Edited on 2019-08-07 05:22:42 by didgeridoohan [Reverted to previous revision]
Additions:
rm -f /data/media/0/bootlog_last.log
[ -e /data/media/0/bootlog.log ]&&mv /data/media/0/bootlog.log /data/media/0/bootlog_last.log
logcat -f /data/media/0/bootlog.log &
} &%%This will save a logcat to a file named bootlog.log and save it to your internal storage (/sdcard) as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but of this isn't enough you can adjust the sleep time in the script to fit your needs.
Deletions:
rm -f /cache/bootlog_last.log
[ -e /cache/bootlog.log ]&&mv /cache/bootlog.log /cache/bootlog_last.log
logcat -f /cache/bootlog.log &
} &%%This will save a logcat to /cache/bootlog.log as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but of this isn't enough you can adjust the sleep time in the script to fit your needs.

Revision [674]

Edited on 2019-07-27 02:37:25 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**The device only boots to bootloader/recovery**// - After the reboot, grab the kmsg file.
~- //**kmsg/last_kmsg**// If experiencing random reboots or booting to bootloader/recovery, the kmsg files, found in /proc, might show what's going on.
Deletions:
~- //**last_kmsg**// If experiencing random reboots, the last_kmsg file, found in /proc, might show what's going on.

Revision [647]

Edited on 2019-07-18 02:45:49 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**The device randomly reboots**// - After the reboot, grab the console-ramoops and/or last_kmsg.
~- //**console-ramoops**// If experiencing random reboots, the console-ramoops file, found in /sys/fs/pstore, might show what's going on.
~- //**last_kmsg**// If experiencing random reboots, the last_kmsg file, found in /proc, might show what's going on.
Deletions:
~- //**The device randomly reboots**// - After the reboot, grab the console-ramoops.
~- //**console-ramoops**// If experiencing random reboots, the console-ramoops file, found in /sys/fs/pstore might show what's going on.

Revision [634]

Edited on 2019-06-17 15:20:54 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Other apps/my system are/is misbehaving/crashes**// - A logcat showing the issue will be necessary.

Revision [628]

Edited on 2019-05-30 04:28:53 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**The device doesn't boot/bootloops**// - A logcat during boot (either through ADB or a boot script) is the only thing that really could show what's going on. A Magisk log might be good for complementary information.
Deletions:
~- //**The device doesn't boot/bootloops**// - The Magisk log and a logcat during boot (either through ADB or a boot script) might show what's going on.

Revision [623]

Edited on 2019-05-27 04:21:40 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Logs!//** A bug report or a report about some kind of issue that is not accompanied by logs will likely be ignored. __Always provide logs!__ And when providing logs, do **NOT** paste them into your post. Attach as a file or upload the file somewhere and provide the link. If you can't provide logs for some reason, at least try to give detailed instructions on how to reliably reproduce the issue.
==**But what if I can't get logs?**==
Most of the time you can get some kind of log showing what is going on. Keep reading below to see what tools you have at your disposal.
But, if you really cannot get hold of any logs at least try to give as detailed instructions as possible on how to reliably reproduce the issue.
Deletions:
~- **//Logs!//** A bug report or a report about some kind of issue that is not accompanied by logs will likely be ignored. __Always provide logs!__ And when providing logs, do **NOT** paste them into your post. Attach as a file or upload the file somewhere and provide the link.

Revision [618]

Edited on 2019-05-19 11:16:24 by didgeridoohan [Reverted to previous revision]
Additions:
==**Which log?**==
==**Get the log**==
Could also mean it's faulty somehow. Try grabbing a logcat and see what happens //(see above)//.
Deletions:
**Relevant logs include:**
Could also mean it's fully somehow. Try grabbing a logcat and see what happens //(see above)//.

Revision [617]

Edited on 2019-05-19 09:51:02 by didgeridoohan [Reverted to previous revision]
Additions:
**Relevant logs include:**
Deletions:
~**Relevant logs include:**

Revision [616]

Edited on 2019-05-17 16:58:16 by didgeridoohan [Reverted to previous revision]
Additions:
Certain issues require different kinds of logs. Here's a list of examples (see further down for details on how to acquire the logs in question):
~- //**Installation of Magisk or modules fail**// - If installing from recovery, you'll need the //recovery log// and if installing from the Manager you need to save the installation log.
~- //**Magisk/modules/MagiskHide isn't working as it should**// - The Magisk log should as a rule always be included whenever there are issues with Magisk core features. Some modules provide their own logging for if there are issues (see the specific modules thread/documentation).
~- //**The Magisk Manager crashes**// - A logcat when the crash occurs will be necessary.
~- //**The device doesn't boot/bootloops**// - The Magisk log and a logcat during boot (either through ADB or a boot script) might show what's going on.
~- //**The device randomly reboots**// - After the reboot, grab the console-ramoops.
~- //**Etc...**//

Revision [615]

Edited on 2019-05-02 04:03:33 by didgeridoohan [Reverted to previous revision]
Deletions:
If you're here because MagiskHide, ""SafetyNet"", Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work //(also see [[MagiskHideBasics | "Requirements"]])//.

Revision [601]

Edited on 2019-02-25 14:32:32 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery. **Note that this log HAS to be saved right after you've done whatever you're trying to save a log of. If you reboot inbetween there is a good chance that the info will be lost.** The log might still be found in /cache/recovery after rebooting, but any subsequent reboots to recovery will overwrite the relevant information.
Deletions:
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery. **Note that this log HAS to be saved right after you've done whatever you're trying to save a log of. If you reboot inbetween, the info will be lost.**

Revision [600]

Edited on 2019-02-25 06:12:42 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**console-ramoops**// If experiencing random reboots, the console-ramoops file, found in /sys/fs/pstore might show what's going on.

Revision [599]

Edited on 2019-02-24 09:20:22 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Module log**// Sometimes modules have their own set of logs that might be useful when troubleshooting issues with a particular module. See the module documentation for details.

Revision [597]

Edited on 2019-02-24 02:53:10 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11). Tip: press the "Grab" button below the code block to download a file ready to be renamed and placed in post-fs-data.d.%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11):%%#!/system/bin/sh

Revision [596]

Edited on 2019-02-23 16:23:35 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody and @jcmm11):%%#!/system/bin/sh
{
rm -f /cache/bootlog_last.log
[ -e /cache/bootlog.log ]&&mv /cache/bootlog.log /cache/bootlog_last.log
logcat -f /cache/bootlog.log &
sleep 30
kill %1
exit
} &%%This will save a logcat to /cache/bootlog.log as soon as possible during boot and you won't need a PC or other device to run ADB from. The first 30 seconds will be saved, but of this isn't enough you can adjust the sleep time in the script to fit your needs.
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody):%%#!/system/bin/sh
rm -f /cache/bootlog.last_log
mv /cache/bootlog.log /cache/bootlog.last_log
​
logcat -f /cache/bootlog.log%%This will save a logcat to /cache/bootlog.log as soon as possible during boot and you won't need a PC or other device to run ADB from. Make sure to remove this script and reboot as soon as you're done or it might fill up your /cache partition.

Revision [595]

Edited on 2019-02-23 11:25:19 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody):%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody):%%#!/system/bin/sh

Revision [594]

Edited on 2019-02-23 11:24:30 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat boot script**//. This is useful if your device won't boot for some reason. The script might even work when ADB logcat doesn't (since ADB won't work until later in the boot process). Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody):%%#!/system/bin/sh
Deletions:
~- //**Logcat boot script**//. Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody):%%#!/system/bin/sh

Revision [591]

Edited on 2019-02-19 03:07:15 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]], an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] or a logcat bootscript (see below). It might be a good idea to start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
Deletions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]], an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] or a logcat bootscript (see below). Always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.

Revision [590]

Edited on 2019-02-19 03:06:19 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]], an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] or a logcat bootscript (see below). Always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
~- //**Logcat boot script**//. Place a file (doesn't matter what you name it) in /data/adb/post-fs-data.d, give it execution permission and put this in it (thank you @jenslody):%%#!/system/bin/sh
rm -f /cache/bootlog.last_log
mv /cache/bootlog.log /cache/bootlog.last_log
​
logcat -f /cache/bootlog.log%%This will save a logcat to /cache/bootlog.log as soon as possible during boot and you won't need a PC or other device to run ADB from. Make sure to remove this script and reboot as soon as you're done or it might fill up your /cache partition.
Deletions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] (always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app). Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.

Revision [569]

Edited on 2019-01-21 01:27:02 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Detailed description//** of the issue and what you've tried so far, what has worked and what hasn't (as an example, did you [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps | test MagiskHide]]?).
Deletions:
~- **//Detailed description//** of the issue and what you've tried so far.

Revision [559]

Edited on 2019-01-06 13:26:26 by didgeridoohan [Reverted to previous revision]
Additions:
Could also mean it's fully somehow. Try grabbing a logcat and see what happens //(see above)//.

Revision [556]

Edited on 2018-12-31 10:01:58 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery. **Note that this log HAS to be saved right after you've done whatever you're trying to save a log of. If you reboot inbetween, the info will be lost.**
Deletions:
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery. **Note that this log HAS to be saved right after you've done whatever you're trying to save a log of. If you reboot inbetween, the info will likely get lost.**

Revision [555]

Edited on 2018-12-27 04:44:32 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk log**// save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below. **Note that when reporting about issues and bugs it is required to use verbose logging (//see "Verbose logging" below//).**
Deletions:
~- //**Magisk log**// save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below. **Note that when reporting about issues and bugs it is required to use verbose logging (see below).**

Revision [554]

Edited on 2018-12-27 04:42:52 by didgeridoohan [Reverted to previous revision]
Additions:
==**Verbose logging**==
When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, it is required to use the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]] and the verbose logging.**
Deletions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, it is required to use the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]] and the verbose logging.**

Revision [553]

Edited on 2018-12-27 04:40:39 by didgeridoohan [Reverted to previous revision]
Additions:
When reporting a bug, make sure you have the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]] installed on your device. Otherwise any bug you're reporting may already be fixed upstream. It will also have much more detailed logging enabled (see below).
Deletions:
When reporting a bug, make sure you have the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]] installed on your device. Otherwise any bug you're reporting may already be fixed upstream. It will also have much more detailed logging enabled (see below).

Revision [514]

Edited on 2018-12-09 03:40:01 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk log**// save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below. **Note that when reporting about issues and bugs it is required to use verbose logging (see below).**
Deletions:
~- //**Magisk log**// save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below.

Revision [513]

Edited on 2018-12-09 03:38:02 by didgeridoohan [Reverted to previous revision]
Additions:
~**Relevant logs include:**
Deletions:
~**Relevant logs may include:**

Revision [510]

Edited on 2018-12-06 01:11:29 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk log**// save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below.
Deletions:
~- //**Magisk log**// save from the Manager or in /cache through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below.

Revision [464]

Edited on 2018-10-03 09:44:26 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Logs!//** A bug report or a report about some kind of issue that is not accompanied by logs will likely be ignored. __Always provide logs!__ And when providing logs, do **NOT** paste them into your post. Attach as a file or upload the file somewhere and provide the link.
Deletions:
~- **//Logs!//** And when providing logs, do **NOT** paste them into your post. Attach as a file or upload the file somewhere and provide the link.

Revision [459]

Edited on 2018-09-28 02:45:27 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, it is required to use the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge debug build]] and the verbose logging.**
Deletions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, it is required to use the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]] and the verbose logging.**

Revision [457]

Edited on 2018-09-25 13:27:08 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. **When reporting about Magisk bugs, it is required to use the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]] and the verbose logging.**
Deletions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. When reporting about Magisk bugs, this is required.

Revision [450]

Edited on 2018-09-11 12:05:59 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. When reporting about Magisk bugs, this is required.
Deletions:
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above.

Revision [449]

Edited on 2018-09-11 12:05:28 by didgeridoohan [Reverted to previous revision]
Additions:
===**Reporting a bug**===
When reporting a bug, make sure you have the latest [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]] installed on your device. Otherwise any bug you're reporting may already be fixed upstream. It will also have much more detailed logging enabled (see below).
~- //**Verbose logging**// When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above.
Deletions:
~- //**Verbose logging**// Sometimes it's useful to have more verbose logging. If the //Magisk log// isn't showing anything useful, you could consider installing the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. Just consider that it is a bleeding edge build and may be quite unstable. //Only install of you know what you're doing!// If you have the Canary build installed, the log is saved just as the normal Magisk log, described above.

Revision [438]

Edited on 2018-09-07 05:51:48 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Verbose logging**// Sometimes it's useful to have more verbose logging. If the //Magisk log// isn't showing anything useful, you could consider installing the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. Just consider that it is a bleeding edge build and may be quite unstable. //Only install of you know what you're doing!// If you have the Canary build installed, the log is saved just as the normal Magisk log, described above.
If you're here because MagiskHide, ""SafetyNet"", Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work //(also see [[MagiskHideBasics | "Requirements"]])//.
Deletions:
~- //**Verbose logging**// Sometimes it's useful to have more verbose logging. If the //Magisk log// isn't showing anything useful, you could consider installing the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. Just consider that it is a bleeding edge build and may be quite unstable. //Only install of you know what you're doing!//
If you're here because MagiskHide, SafetyNet, Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work //(also see [[MagiskHideBasics | "Requirements"]])//.

Revision [437]

Edited on 2018-09-07 05:50:26 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk log**// save from the Manager or in /cache through recovery if you don't have root access. If the log is empty, see //"The Magisk log is empty"// below.
~- //**Verbose logging**// Sometimes it's useful to have more verbose logging. If the //Magisk log// isn't showing anything useful, you could consider installing the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary bleeding edge build]]. It has debug logging active and will show much more useful information. Just consider that it is a bleeding edge build and may be quite unstable. //Only install of you know what you're doing!//
Deletions:
~- //**Magisk log**// (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version, so if you're having issues it might be a good idea to switch to the beta channel to get better logs.

Revision [423]

Edited on 2018-09-04 01:58:45 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk log**// (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version, so if you're having issues it might be a good idea to switch to the beta channel to get better logs.
Deletions:
~- //**Magisk log**// (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~- //**Magisk debug log**//. //Not available since Magisk beta v16.6. Use the Magisk log.// If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. If you currently can't access/data/adb, because of root loss, etc, you can boot to a custom recovery (i.e. TWRP) and access it from there. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.

Revision [366]

Edited on 2018-07-20 00:41:24 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk debug log**//. //Not available since Magisk beta v16.6. Use the Magisk log.// If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. If you currently can't access/data/adb, because of root loss, etc, you can boot to a custom recovery (i.e. TWRP) and access it from there. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.
Deletions:
~- //**Magisk debug log**//. If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. If you currently can't access/data/adb, because of root loss, etc, you can boot to a custom recovery (i.e. TWRP) and access it from there. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.

Revision [301]

Edited on 2018-07-07 00:19:48 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Magisk debug log**//. If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. If you currently can't access/data/adb, because of root loss, etc, you can boot to a custom recovery (i.e. TWRP) and access it from there. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.
Deletions:
~- //**Magisk debug log**//. If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.

Revision [297]

Edited on 2018-06-13 01:25:30 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] (always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app). Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. **If you can't get root access** it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
Deletions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] (always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app). Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.

Revision [289]

Edited on 2018-05-01 15:33:40 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Logs!//** And when providing logs, do **NOT** paste them into your post. Attach as a file or upload the file somewhere and provide the link.
Deletions:
~- **//Logs!//** And when providing logs, do **NOT** paste them into your post. Attach as a file, upload the file somewhere (or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]]) and provide the link.

Revision [286]

Edited on 2018-04-30 06:47:42 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery. **Note that this log HAS to be saved right after you've done whatever you're trying to save a log of. If you reboot inbetween, the info will likely get lost.**
Deletions:
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery.

Revision [275]

Edited on 2018-04-25 01:24:27 by didgeridoohan [Reverted to previous revision]
Additions:
If you're here because MagiskHide, SafetyNet, Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work //(also see [[MagiskHideBasics | "Requirements"]])//.
Deletions:
If you're here because MagiskHide, SafetyNet, Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work //(also see [MagiskHideBasics | "Requirements"]])//.

Revision [274]

Edited on 2018-04-25 01:24:09 by didgeridoohan [Reverted to previous revision]
Additions:
If you're here because MagiskHide, SafetyNet, Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work //(also see [MagiskHideBasics | "Requirements"]])//.

Revision [273]

Edited on 2018-04-25 00:14:27 by didgeridoohan [Reverted to previous revision]
Additions:
If your Magisk log is empty, it's likely that you have Android logging disabled. Try enabling it.
Deletions:
If your Magisk log is empty, it's likely that you have logging disabled. Try enabling it.

Revision [262]

Edited on 2018-04-05 03:22:57 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Logs!//** And when providing logs, do **NOT** paste them into your post. Attach as a file, upload the file somewhere (or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]]) and provide the link.
Deletions:
~- **//Logs!//** And when providing logs, do NOT paste them into your post. Attach as a file, upload the file somewhere (or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]]) and provide the link.

Revision [261]

Edited on 2018-04-05 03:17:18 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Logs!//** And when providing logs, do NOT paste them into your post. Attach as a file, upload the file somewhere (or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]]) and provide the link.
Deletions:
~- **//Logs!//** And when providing logs, do NOT paste them into your post. Attach as a file or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]] and provide the link.

Revision [259]

Edited on 2018-04-02 14:11:39 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]] (always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app). Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
Deletions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.

Revision [251]

Edited on 2018-03-25 11:46:59 by didgeridoohan [Reverted to previous revision]
Additions:
It might also be that your kernel/ROM wipes the /cache directory during boot, thus removing the log. See [[https://forum.xda-developers.com/showpost.php?p=73230207&postcount=17612 | here]] for details.
Deletions:
It might also be that your kernel/ROM wipes the /cache directory during boot and thus removing the log. See [[https://forum.xda-developers.com/showpost.php?p=73230207&postcount=17612 | here]] for details.

Revision [250]

Edited on 2018-03-25 11:46:43 by didgeridoohan [Reverted to previous revision]
Additions:
If your Magisk log is empty, it's likely that you have logging disabled. Try enabling it.
It might also be that your kernel/ROM wipes the /cache directory during boot and thus removing the log. See [[https://forum.xda-developers.com/showpost.php?p=73230207&postcount=17612 | here]] for details.
Deletions:
If your Magisk log is empty, it might be that your kernel/ROM wipes the /cache directory during boot and thus removing the log. See [[https://forum.xda-developers.com/showpost.php?p=73230207&postcount=17612 | here]] for details.

Revision [235]

Edited on 2018-03-24 07:23:40 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
Deletions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB.

Revision [208]

Edited on 2018-02-18 13:39:06 by didgeridoohan [Reverted to previous revision]
Additions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB.
Deletions:
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues.

Revision [207]

Edited on 2018-02-18 02:02:29 by didgeridoohan [Reverted to previous revision]
Additions:
~- **//Detailed description//** of the issue and what you've tried so far.
~- **//Details//** about your device, Android version, ROM, custom kernel, mods, etc.
~- **//Logs!//** And when providing logs, do NOT paste them into your post. Attach as a file or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]] and provide the link.
~- //**Recovery log**// from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery.
~- //**Installation log**// from the Manager (press "Save log" after installing Magisk or a module). If you experience errors when installing Magisk or modules in the Manager.
~- //**Magisk log**// (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~- //**Magisk debug log**//. If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.
~- //**Logcat**//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues.
Deletions:
~- Detailed description of the issue and what you've tried so far.
~- Details about your device, Android version, ROM, custom kernel, mods, etc.
~- Current and previous root solution (and what you've done to remove it, if applicable)
~- Logs! And when providing logs, do NOT paste them into your post. Attach as a file or use a service like [[https://pastebin.com/ | Pastebin]] or [[https://hastebin.com | hastebin]] and provide the link.
~- //Recovery log// from installation (in TWRP, go to Advanced - Copy log).
~- //Installation log// from the Manager (press "Save log" after installing Magisk or a module).
~- //Magisk log// (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~- //Magisk debug log//. If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.
~- //Logcat//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues.

Revision [204]

Edited on 2018-02-09 15:20:04 by didgeridoohan [Reverted to previous revision]
Additions:
~- //Recovery log// from installation (in TWRP, go to Advanced - Copy log).
~- //Installation log// from the Manager (press "Save log" after installing Magisk or a module).
~- //Magisk log// (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~- //Magisk debug log//. If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.
~- //Logcat//. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues.
Deletions:
~- Recovery log from installation (in TWRP, go to Advanced - Copy log).
~- Installation log from the Manager (press "Save log" after installing Magisk or a module).
~- Magisk log (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~- Logcat. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log.
~- If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.

Revision [203]

Edited on 2018-02-08 02:44:35 by didgeridoohan [Reverted to previous revision]
Additions:
===**Asking for help**===
===**Logs**===
~**Relevant logs may include:**
~- Recovery log from installation (in TWRP, go to Advanced - Copy log).
~- Installation log from the Manager (press "Save log" after installing Magisk or a module).
~- Magisk log (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~- Logcat. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log.
~- If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.
Deletions:
~~**Relevant logs may include:**
~~- Recovery log from installation (in TWRP, go to Advanced - Copy log).
~~- Installation log from the Manager (press "Save log" after installing Magisk or a module).
~~- Magisk log (from the Manager or in /cache through recovery if you don't have root access). If the log is empty, see //"The Magisk log is empty"// below.
~~- Logcat. Grab it via [[https://forum.xda-developers.com/showthread.php?t=1726238 | ADB]] or an [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | app]]. Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log.
~~- If you’re having issues with Magisk, please install the [[https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 | latest beta]]. It has more verbose logging and a magisk_debug.log will be saved in /data/adb. There’s always a beta version of the current Magisk release available, the only difference between the releases being the more verbose logging in the beta version.

Revision [198]

The oldest known version of this page was created on 2018-02-05 15:44:31 by didgeridoohan [Reverted to previous revision]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki