[Magisk] flipmode_11:
Need Help? Have an error? Things not working?

Please provide

full details

of your device, software and issues to get a quick resolution!

» Device and specific model?

» ROM (stock/custom) and OS version?

» Kernel (stock/custom) and version?

» Magisk and Magisk Manager versions?

» Attach the Magisk Logs or LogCat!? (see list below)

» Steps to replicate and reproduce the error? (Action? Install? Update? Module? Hide? Crash?)

» What error message did you receive?​

Example list of Log locations:

%internal%/MagiskManager/Logs/install_yyyymmdd_hhmmss.log — Installation & Rooting Issues

%internal%/MagiskManager/Logs/magisk_yyyymmdd_hhmmss.log — Magisk Manager Issues

./tmp/recovery.log — Recovery Log [use 'adb pull ...' -OR- TWRP > Advanced > Copy Log to save]

./data/adb/magisk_debug.log — Magisk SuperUser Beta debugging log output

./root/cache/magisk — File w/o an extension

./data/media/0/recovery.log — Recovery-related logs [?]

./cache/recovery/ — Recovery-related logs [file: log, last_log] [?]

./data/app/magisk/cache/ — Including sub-directories [?]

./data/user/0/com.topjohnwu.magisk/ — Temporary storage location prior to reboot [?]

and no doubt many more...

NOTE:

%internal% = ./mnt/sdcard/ or ./storage/sdcard/ or ./storage/emulated/0/ [Device Dependent!]

[?] Query?! = To be confirmed and confirm stable/beta path status.​

You may also use a LogCat ADB shell tool to pull and save system log events (all errors, warnings, stack traces, etc). When an error occurs, key information pointing towards the source of failure is output in this log, making it a very useful tool for troubleshooting. You may search the forums or the web for 'aLogCat', 'CatLog' & 'MatLog' example ADB commands.

Cannot find any logs? All logs empty?

Check the status of your device's 'logd' service and that it is running. If the 'logd' service is running and you cannot find a specific log, you may search the device for it! Install and open a terminal emulator and type 'su' (click Allow to the pop-up prompt). Now you have elevated yourself to run commands as "Super User". Try some of these examples below to search for a specific log, file type or file name:

find -name 'magisk*.log' (for magisk_yyyymmdd_hhmmss.log and magisk_debug.log)

find -name 'install*.log' (for install_yyyymmdd_hhmmss.log and similar)

find -name 'recovery.log' (for recovery output logs)

find -name 'last_log' (for previous recovery output logs)

find -name '*20180501*.log' (search saved logs for a specific date)

There are 3 solutions for this.

One I have experienced a few times is where you check and see if this file exists: /data/property/persist.magisk.hide

If it does exist when Magisk Hide is not working, force stop Magisk Manager, delete 'persist.magisk.hide' file, open Magisk Manager and enable Magisk Hide.

I documented 3 solutions here under "TROUBLESHOOTING MAGISK HIDE" @ https://xdaforums.com/showpost.php?p=75644509&postcount=2

I have documented a bunch of common Magisk-related issues, hints and tips there too.

Look (or search) for "stock_boot.img" backup within the /data/ directory. If you patch via download mode I don't think it creates a backup - Magisk will only create a backup if the boot image is not modified...

Yes you can open Magisk Manager, click "Uninstall" and choose "Restore Images" (i.e. restore the stock boot Image). Or manually flash 'stock_boot.img' via TWRP.

I've documented a bunch of common Magisk issues, hints and tips here: https://xdaforums.com/android-stick...logic-s905x-s912x-faq-backup-switch-t3752897/

Create the file /sbin/.core/img/.core/hidelist with CHMOD 0600

Try again.

---------- Post added at 05:17 ---------- Previous post was at 05:10 ----------

Check post #2 here, where I have documented 3 methods to fix "Magisk Hide" not working.

Have you tried downgrading to an earlier version? v16.3? v16.0? v15.3? First find the Magisk Flashable ZIP (e.g. v16.0). Open Magisk Manager, slide the left menu and click Modules, then click + and navigate to the Magisk Flashable ZIP and it will be flashed (downgraded). Reboot.

Did you enable "Hide Magisk" to rename and repackage the Magisk Manager?