[Magisk] flipmode_11:
[MENTION=8544005]Vivekvkr7[/MENTION] Please provide your device details. Read the Magisk Error message. Error 1 = you need to RESTORE a

stock or unmodified

boot image.

On your internal memory is a MagiskManager folder. Inside there should be a "stock_boot.img" backup.

However if you have never successfully flashed Magisk, then I suspect your boot image is already modified (you did not mention your ROM) and the backup will not help.

I suggest you download your device firmware (matching your Device + OS) and extract the boot.img from the .ZIP or .TAR.MD5

Flash this with Odin in Download Mode, or TWRP, or TWRP on bootable SD Card, or Fast Boot in Download Mode, etc.

Now re-attempt to patch the Boot.img via Magisk Manager (option #2) OR if it has "Direct Mode" (option #3) use that to save time.

If this still does not work with a clean boot image, then the boot image you are using has already been modified by another app (e.g. ROM developer, manufacturer, etc). Visit your device forum on XDA for help on this.

There is ample documentation in the Magisk Wiki AND many already answered posts in this Magisk category on Error=1 and boot image. For further assistance and help, please ask in your Device's forum and ROM category for getting a stock boot image.

Good luck!

If you have any issues with the Lineage ROM and OS, I suggest you report the issue in the appropriate forum within the Lineage category.

Logs? What logs?

Always

attach logs with EVERY request for help if you want a quick response!

Example list of Log locations:

- ./MagiskManager/Logs/install_yyyymmdd_hhmmss.log

- ./MagiskManager/Logs/magisk_yyyymmdd_hhmmss.log

- ./root/cache/magisk (file w/o extension)

- ./tmp/recovery.log [n.b. use 'adb pull' -OR- TWRP > Advanced > Copy Log to retrieve]

- ./data/adb/magisk_debug.log

- ./data/app/magisk/cache/ (?)

- ./cache/recovery/ [file: log, last_log] (?)

- ./data/media/0/recovery.log (?)

and no doubt more....

Cannot find any logs? All logs empty? Check the status of your device's 'logd' service and that it is running.

If you cannot find a specific log, you can search for it! Download and open a terminal emulator and type 'su' (click Allow for any pop-up prompt).

Now you have elevated yourself to run commands as "Super User". Try some of these examples below to seach for a specific log, or file type or file name, should you be unable to find it:

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)

[MENTION=3760438]AZDJedi[/MENTION] Create a request detailing what you want and how the feature would work.

I did the same as wanted to know when updates were available to BusyBox NDK, for example,, not just for Magisk SU and Magisk Manager.

:good:

[MENTION=6269851]Hadookie[/MENTION]... Been a lot of strange issues and complaints with Pixel.

Please post Recovery and Installer logs (See Above or OP) and attach them here with your reply.

I know 16.4 is quite delicate. A member even created a 32bit-only version/branch, to deal with the 64bit and 32bit issues.

Have you tried or were things working on Magisk v16.0 or 16.3? Have you tried updating your TWRP to latest version???

>> https://github.com/topjohnwu/Magisk/releases

I think someone said they had to check a box in order to get it to work. There is sonething specific for Pixel users due to the way they merged partitions and stuffed things around.