Database Develop

Magisk installation problem on stock firmware

Hello,
I have a problem installing Magisk. I have a tablet Oysters T74Mai 3G with MTK processor and stock android 5.1 with unlocked bootloader and without root. There is no any custom recovery for that model.
I installed Magisk Manager 5.8.3 and let it patch the stock boot image. After that I flashed the patched image with fastboot, but when the tablet is powered on, it is stuck on the boot animation. When I flash the stock boot image back with fastboot, the tablet boots normally. I tried to patch the boot image with Magisk 16.0 and 16.7, but the result is the same - stuck on the boot animation.
This is the log from Magisk Manager when patching the boot image:
Code:
- Copying image locally
- Target image: /data/data/com.topjohnwu.magisk/install/boot.img
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_21f9cec6deb5897d8707666e6b64e5c29055ed76.img.gz]
- Patching ramdisk
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Save SHA1: [21f9cec6deb5897d8707666e6b64e5c29055ed76] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading dtbs from [dtb]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7094175]
RAMDISK [928004]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [10c3a516cc474a38eed500fe1208f27707cce10a]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/sdcard0/MagiskManager/patched_boot.img
****************************
- All done!
This is the /cache/magisk.log
Code:
08-09 01:38:39.369 204 204 I Magisk : ** Initializing Magisk
08-09 01:38:39.370 204 204 I Magisk : * Creating /sbin overlay
08-09 01:38:39.685 204 204 I Magisk : * Mounting mirrors
08-09 01:38:39.687 204 204 I Magisk : mount: /sbin/.core/mirror/system
08-09 01:38:39.687 204 204 I Magisk : link: /sbin/.core/mirror/vendor
08-09 01:38:39.687 204 204 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-09 01:38:39.687 204 204 I Magisk : * Setting up internal busybox
08-09 01:38:39.770 210 210 I Magisk : Magisk v16.7(1671) logger started
08-09 01:38:39.771 207 207 I Magisk : Magisk v16.7(1671) daemon started
08-09 01:38:39.779 207 212 I Magisk : ** post-fs-data mode running
08-09 01:38:39.780 207 212 I Magisk : * Mounting /data/adb/magisk.img
08-09 01:38:40.085 207 212 I Magisk : * Running post-fs-data.d scripts
08-09 01:38:40.086 207 212 I Magisk : * Running module post-fs-data scripts
08-09 01:38:40.086 207 212 I Magisk : * Loading modules
08-09 01:38:40.086 207 223 I Magisk : * Starting MagiskHide
08-09 01:38:40.086 207 223 I Magisk : hide_utils: Hiding sensitive props
08-09 01:38:40.087 207 223 I Magisk : hide_list: [com.google.android.gms.unstable]
Does someone know what can be the reason for this problem and how I can solve it?

The fact that you have a Magisk log is a good sign.
You could try enabling "Preserve dm-verity" when patching the boot image to see if it makes a difference. Right now I can see you have it disabled. It's also possible that the "Preserve forced encryption" option could help, but be careful with this if you have previously removed encryption on your device. It'll re-encrypt...
Since you have a Magisk log, you could also try grabbing a logcat via ADB during boot, to see where it hangs.

Thank you very much for your reply.
I have patched the boot image with "Preserve dm-verity" enabled, but again it is stuck on the boot animation.
This is the log from Magisk Manager when patching the boot image:
Code:
- Copying image locally
- Target image: /data/data/com.topjohnwu.magisk/install/boot.img
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_21f9cec6deb5897d8707666e6b64e5c29055ed76.img.gz]
- Patching ramdisk
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]
Save SHA1: [21f9cec6deb5897d8707666e6b64e5c29055ed76] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7094175]
RAMDISK [928008]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [8dd621ec0dbb737eeedadbf8b8681f6a04b6409b]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/sdcard0/MagiskManager/patched_boot.img
****************************
- All done!
This is the /cache/magisk.log
Code:
08-09 12:30:31.285 203 203 I Magisk : ** Initializing Magisk
08-09 12:30:31.286 203 203 I Magisk : * Creating /sbin overlay
08-09 12:30:31.599 203 203 I Magisk : * Mounting mirrors
08-09 12:30:31.601 203 203 I Magisk : mount: /sbin/.core/mirror/system
08-09 12:30:31.601 203 203 I Magisk : link: /sbin/.core/mirror/vendor
08-09 12:30:31.601 203 203 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-09 12:30:31.601 203 203 I Magisk : * Setting up internal busybox
08-09 12:30:31.686 209 209 I Magisk : Magisk v16.7(1671) logger started
08-09 12:30:31.687 206 206 I Magisk : Magisk v16.7(1671) daemon started
08-09 12:30:31.695 206 211 I Magisk : ** post-fs-data mode running
08-09 12:30:31.696 206 211 I Magisk : * Mounting /data/adb/magisk.img
08-09 12:30:31.912 206 211 I Magisk : * Running post-fs-data.d scripts
08-09 12:30:31.912 206 211 I Magisk : * Running module post-fs-data scripts
08-09 12:30:31.912 206 211 I Magisk : * Loading modules
08-09 12:30:31.913 206 222 I Magisk : * Starting MagiskHide
08-09 12:30:31.913 206 222 I Magisk : hide_utils: Hiding sensitive props
08-09 12:30:31.914 206 222 I Magisk : hide_list: [com.google.android.gms.unstable]
I have attached the logcat via ADB during boot. It seems that there is a pattern that repeats forever. Any thoughts?

Magisk is not installed after flashing patched_boot.img

Hi guys,
I'm sorry for this new thread but I'm trying to install Magisk without any custom recovery but I have obtained poor results for now.
I'm working on a single-board computer i.MX7D with Android Things 1.0.8. I have installed Magisk Manager, I have patched the new boot.img e next I have flashed it into boot_a and boot_b partitions using fastboot:
fastboot flash boot_a patched_boot.img
Code:
target reported max download size of 419430400 bytes
sending 'boot_a' (14720 KB)...
OKAY [ 0.490s]
writing 'boot_a'...
OKAY [ 0.604s]
finished. total time: 1.094s
fastboot flash boot_b patched_boot.img
Code:
target reported max download size of 419430400 bytes
sending 'boot_b' (14720 KB)...
OKAY [ 0.481s]
writing 'boot_b'...
OKAY [ 0.636s]
finished. total time: 1.117s
The system reboot correctly, but Magisk is not installed.
What I am wrong?
This is the install log:
Code:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [9741613]
RAMDISK_SZ [5083265]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-10]
PAGESIZE [2048]
NAME []
CMDLINE [init=/init androidboot.hardware=imx7d vt.global_cursor_default=0 consoleblank=0 rootwait ro earlyprintk loglevel=7 console=ttymxc4,115200 androidboot.console=ttymxc4 buildvariant=userdebug]
CHECKSUM [3db586c24cd1a96871cf6bec185525a1f83a4249]
Invalid DTB detection at 0x1b31: size (16793940) > remaining (9734652)
DTB [45509]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_722068a856e0e11321dbd6254b18f03fd754e3e9.img.gz]
- Patching ramdisk
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [9741613]
RAMDISK_SZ [5083265]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-10]
PAGESIZE [2048]
NAME []
CMDLINE [init=/init androidboot.hardware=imx7d vt.global_cursor_default=0 consoleblank=0 rootwait ro earlyprintk loglevel=7 console=ttymxc4,115200 androidboot.console=ttymxc4 buildvariant=userdebug]
CHECKSUM [3db586c24cd1a96871cf6bec185525a1f83a4249]
Invalid DTB detection at 0x1b31: size (16793940) > remaining (9734652)
DTB [45509]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [9741613]
RAMDISK_SZ [5328429]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-10]
PAGESIZE [2048]
NAME []
CMDLINE [init=/init androidboot.hardware=imx7d vt.global_cursor_default=0 consoleblank=0 rootwait ro earlyprintk loglevel=7 console=ttymxc4,115200 androidboot.console=ttymxc4 buildvariant=userdebug]
CHECKSUM [76fc9c4cf236a4b64329fbc2d9fffbd129c41d65]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/emulated/0/Download/patched_boot.img
****************************
- All done!

Unable to repack boot image

Trying to patch a bootloader image. Error message: Unable to repack boot image.
Magisk Manager 7.4.0 (253). G6 Play XT1922-4 Pie. Screenshot attached.
Code:
- Device platform: armeabi-v7a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes transferred in 1.006 secs (1594019 bytes/sec)
1045+1 records in
1045+1 records out
1070668 bytes transferred in 0.020 secs (53533400 bytes/sec)
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER [0]
KERNEL_SZ [1986939136]
RAMDISK_SZ [1869570592]
SECOND_SZ [543516513]
EXTRA_SZ [169964133]
PAGESIZE [1635151433]
NAME [lid page size
]
CMDLINE [sing kernel image: start
oting normally]
CHECKSUM [007265626f6f74696e6720746865206465766963650a004f4b4159007265626f]
Segmentation fault
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER [0]
KERNEL_SZ [1986939136]
RAMDISK_SZ [1869570592]
SECOND_SZ [543516513]
EXTRA_SZ [169964133]
PAGESIZE [1635151433]
NAME [lid page size
]
CMDLINE [sing kernel image: start
oting normally]
CHECKSUM [007265626f6f74696e6720746865206465766963650a004f4b4159007265626f]
Segmentation fault
! Unable to repack boot image!
! Installation failed
Any ideas?

It works for boot.img

And there's your answer...
You're not supposed to do anything to the bootloader. Only boot image, or if you have an A only SAR device the recovery image.

Ok. Thank you.

Infinite loop with patched magisk boot.img

I flashed the patched magisk boot.img and I get an infinite loop showing this key: 80012A99-867FDA48-4E357816-0E549F1B-B067FBD5
I used Magisk Manager 7.4.0. G6 Play XT1922-4 Pie. Screenshot attached.
Code:
- Device platform: armeabi-v7a
- Copying image to cache
- Boot image is signed with AVB 1.0
1566+0 records in
1566+0 records out
1603584 bytes transferred in 0.030 secs (53452800 bytes/sec)
1045+1 records in
1045+1 records out
1070668 bytes transferred in 0.020 secs (53533400 bytes/sec)
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [10251215]
RAMDISK_SZ [1508130]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom androidboot.memcg=false user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 firmware_class.path=/vendor/firmware_mnt/image loop.max_part=7 vmalloc=400M buildvariant=user]
CHECKSUM [77549a9032634b395110bb3a9eb0227033621915000000000000000000000000]
KERNEL_DTB [896823]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Remove [verity_key]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Backup missing entry: [verity_key] -> [.backup/verity_key]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [kernel_dtb]
Found fstab in dtb.0000
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
Found fstab in dtb.0001
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
Found fstab in dtb.0002
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
Found fstab in dtb.0003
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
- Patching fstab in kernel_dtb
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [10251215]
RAMDISK_SZ [1508130]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom androidboot.memcg=false user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 firmware_class.path=/vendor/firmware_mnt/image loop.max_part=7 vmalloc=400M buildvariant=user]
CHECKSUM [77549a9032634b395110bb3a9eb0227033621915000000000000000000000000]
KERNEL_DTB [896823]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [10247087]
RAMDISK_SZ [1770428]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom androidboot.memcg=false user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 firmware_class.path=/vendor/firmware_mnt/image loop.max_part=7 vmalloc=400M buildvariant=user]
CHECKSUM [3a228177359924a940499d2a84e7dcc6ec41deca000000000000000000000000]
- Signing boot image with verity keys
****************************
Output file is placed in
/storage/emulated/0/Download/magisk_patched.img
****************************
- All done!

If I patch and flash recovery.img it boots but Magisk is not installed.

If I sideload Magisk.zip it falls into the infinite loop again.

Kaka0 said:
I flashed the patched magisk boot.img and I get an infinite loop showing this key: 80012A99-867FDA48-4E357816-0E549F1B-B067FBD5
I used Magisk Manager 7.4.0. G6 Play XT1922-4 Pie. Screenshot attached.
Code:
- Device platform: armeabi-v7a
- Copying image to cache
- Boot image is signed with AVB 1.0
1566+0 records in
1566+0 records out
1603584 bytes transferred in 0.030 secs (53452800 bytes/sec)
1045+1 records in
1045+1 records out
1070668 bytes transferred in 0.020 secs (53533400 bytes/sec)
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [10251215]
RAMDISK_SZ [1508130]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom androidboot.memcg=false user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 firmware_class.path=/vendor/firmware_mnt/image loop.max_part=7 vmalloc=400M buildvariant=user]
CHECKSUM [77549a9032634b395110bb3a9eb0227033621915000000000000000000000000]
KERNEL_DTB [896823]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Remove [verity_key]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Backup missing entry: [verity_key] -> [.backup/verity_key]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [kernel_dtb]
Found fstab in dtb.0000
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
Found fstab in dtb.0001
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
Found fstab in dtb.0002
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
Found fstab in dtb.0003
Found entry [system] in fstab
Found pattern [,verify]
Found entry [vendor] in fstab
Found pattern [,verify]
- Patching fstab in kernel_dtb
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [10251215]
RAMDISK_SZ [1508130]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom androidboot.memcg=false user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 firmware_class.path=/vendor/firmware_mnt/image loop.max_part=7 vmalloc=400M buildvariant=user]
CHECKSUM [77549a9032634b395110bb3a9eb0227033621915000000000000000000000000]
KERNEL_DTB [896823]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [10247087]
RAMDISK_SZ [1770428]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom androidboot.memcg=false user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 firmware_class.path=/vendor/firmware_mnt/image loop.max_part=7 vmalloc=400M buildvariant=user]
CHECKSUM [3a228177359924a940499d2a84e7dcc6ec41deca000000000000000000000000]
- Signing boot image with verity keys
****************************
Output file is placed in
/storage/emulated/0/Download/magisk_patched.img
****************************
- All done!
Click to expand...
Click to collapse
What did u do to fix this?? Cuz that's exactly what mine is doing but I can't get it to open fastboot

Update using Direct Install doesn't update Magisk

I am on a POCO M4 Pro (Fleur).
I have updated the Magisk App to 25100, and am trying to update Magisk (the system) to 25100.
I click "Update" and select "Direct Install (recommended)" and it appears to work:
- Target image: /dev/block/sdc34
- Device platform: arm64-v8a
- Installing: 25.1 (25100)
- Unpacking boot image
Parsing boot image: [/dev/block/sdc34]
HEADER_VER [2]
KERNEL_SZ [10700167]
RAMDISK_SZ [20106515]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [130308]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2022-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [c8138edce860b616048123e7d5f3ead3b3c3d79a000000000000000000000000]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Magisk patched boot image detected
Loading cpio: [ramdisk.cpio]
Remove [.backup]
Remove [.backup/.magisk]
Remove [overlay.d]
Remove [overlay.d/sbin]
Remove [overlay.d/sbin/magisk32.xz]
Remove [overlay.d/sbin/magisk64.xz]
Remove [.backup/.rmlist]
Move [.backup/init] -> [init]
Dump cpio: [ramdisk.cpio]
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [dtb]
- Repacking boot image
Parsing boot image: [/dev/block/sdc34]
HEADER_VER [2]
KERNEL_SZ [10700167]
RAMDISK_SZ [20106515]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [130308]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2022-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [c8138edce860b616048123e7d5f3ead3b3c3d79a000000000000000000000000]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER [2]
KERNEL_SZ [10700167]
RAMDISK_SZ [20137863]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [130308]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2022-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [f8b2da7b9c90934ce9d6a95c40f017fc576840f9000000000000000000000000]
- Flashing new boot image
RULESDIR=/dev/cyEUC5/.magisk/mirror/metadata/magisk
- All done!
Click to expand...
Click to collapse
So I click "Reboot" and the phone reboots. I open the Magisk app and I'm given the "Requires Additional Setup" message because the Magisk version doesn't seem to have updated:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know why this doesn't work?
I have updated manually by:
- flashing the stock boot.img using fastboot
- patching the stock boot.img using Magisk
- flashing the patched boot.img using fastboot
I'd rather not have to do this every time.

same thing here. same action taken.
Lenovo Tab M10 HD TB-X306X
TB-X306X_S230294_220517_BMP

Could you add your device to the issue on GitHub to highlight the bug and aid in debugging?
Direct Install reports success but doesn't update Magisk · Issue #6051 · topjohnwu/Magisk
Device: POCO M4 Pro (Fleur) Android version: 11.0.0 Magisk version name: 9183a0a Magisk version code: 25101 I am trying to update to v25.1 so I update the Magisk App to the most recent debug build,...
github.com

i couldn't. new guy

Ah that's a shame! I'll note your device and link here.

tq sir

just to reinstate.
im having the same issue.
Lenovo Tab M10 HD TB-X306X
TB-X306X_S230294_220517_BMP
Android 11.
now using magisk 24.3 without any glitch.
unable to update to 25.1.
requires additional setup loop.
sigh.
please help

Can you reflash your stock boot.img, install Magisk 25.1, use it to patch your stock boot.img then flash that patched img?

yup, i am thinking of doing it later today.....my last resort before i accept the fate that this tab will be stuck with magisk 24.3 forever. thank you sir.

i will let u know the outcome

aricooperdavis said:
Can you reflash your stock boot.img, install Magisk 25.1, use it to patch your stock boot.img then flash that patched img?
Click to expand...
Click to collapse
yes sir. it works!!!! thank you so much. salute!!!

Yep same issue.. On Lenovos the Direct method does NOT work..