Database Develop

Magisk is not installed

Heloo and sorry in advance if i'm making a thread that has allready been made
I have followed all the steps from the Installation Instructions (i do not have a rooted device or a custom room installed)
After flashing the patched boot image trough adb,rebooting then opening hte magisk manager i still see the Magisk is not installed
Also i am a beginer so i may not know how to post logs or where to get them
If any other information is needed please let me know

You don't use ADB to flash a boot image. Depending on your device it'll be fastboot, Odin, or whatever's applicable. What is your device?

Didgeridoohan said:
You don't use ADB to flash a boot image. Depending on your device it'll be fastboot, Odin, or whatever's applicable. What is your device?
Click to expand...
Click to collapse
My device is an allview x3 soul lite(i'm pretty sure it's a rebranded version of gionee f103 pro)

Onelas said:
My device is an allview x3 soul lite(i'm pretty sure it's a rebranded version of gionee f103 pro)
Click to expand...
Click to collapse
Ok... Don't know anything about that device... :laugh:
Fastboot is probably the way to go:
Code:
fastboot flash boot patched_boot.img
Have you used the above command?
Useful information to provide would be an installation log from when you patch the image in the Manager (there's a button for it in the Manager flashing window), what you do to flash the image, and the output when flashing.

Didgeridoohan said:
Ok... Don't know anything about that device... :laugh:
Fastboot is probably the way to go:
Code:
fastboot flash boot patched_boot.img
Have you used the above command?
Useful information to provide would be an installation log from when you patch the image in the Manager (there's a button for it in the Manager flashing window), what you do to flash the image, and the output when flashing.
Click to expand...
Click to collapse
yes i did

Here is the log from patching the boot image
- Device platform: arm64
- Extracting files
- Boot image is signed with AVB 1.0
- Unpacking boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [7470696]
RAMDISK [1897650]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465232768]
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [a741fb925935959ee34c60f918f1e9206c987a99]
DTB [79446]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_494e60652653221568df3d6988887666e1386970.img.gz]
- Patching ramdisk
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Remove pattern [,verify]
Remove [verity_key]
Save SHA1: [494e60652653221568df3d6988887666e1386970] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [fstab.mt6735] -> [.backup/fstab.mt6735]
Backup mismatch entry: [init] -> [.backup/init]
Backup missing entry: [verity_key] -> [.backup/verity_key]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Loading dtbs from [dtb]
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Patch @ 00EC8DBB [736B69705F696E697472616D6673]->[77616E745F696E697472616D6673]
- Repacking boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [7470696]
RAMDISK [1897650]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465232768]
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [a741fb925935959ee34c60f918f1e9206c987a99]
DTB [79446]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7474614]
RAMDISK [2282725]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465232768]
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [53c61054ade95d565748766a0d93ea7873ffc362]
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
- Signing boot image with test keys
*********************************
Patched Boot Image is placed in
/storage/emulated/0/MagiskManager/patched_boot.img
*********************************
- All done!

Log looks fine. What was the output when flashing the patched boot image?

Didgeridoohan said:
Log looks fine. What was the output when flashing the patched boot image?
Click to expand...
Click to collapse
this is the first time i got this error
target reported max download size of 134217728 bytes
sending 'boot' (9533 KB)...
OKAY [ 0.922s]
writing 'boot'...
FAILED (remote: download for partition 'boot' is not allowed
)
finished. total time: 0.952s
until now the failed part has never shown

Onelas said:
this is the first time i got this error
target reported max download size of 134217728 bytes
sending 'boot' (9533 KB)...
OKAY [ 0.922s]
writing 'boot'...
FAILED (remote: download for partition 'boot' is not allowed
)
finished. total time: 0.952s
until now the failed part has never shown
Click to expand...
Click to collapse
Is your bootloader unlocked? It needs to be... Keep in mind that doing that will likely wipe your device.

Didgeridoohan said:
Is your bootloader unlocked? It needs to be... Keep in mind that doing that will likely wipe your device.
Click to expand...
Click to collapse
done,i have unlocked it(i had a button for it in the developer menu)
target reported max download size of 134217728 bytes
sending 'boot' (9533 KB)...
OKAY [ 0.925s]
writing 'boot'...
OKAY [ 0.283s]
finished. total time: 1.212s
waiting for it to finish booting,i just hope i didn't brick it

Aaaand it's working now,thank you verry verry much for taking your time to help me

Hiya, Is/would Magisk work on the Essential Android P? My bootloader is unlocked, but I keep getting the Failed boot image is signed with AVB 1.0 message
Fixed: Just had to read a bit closer.

Onelas said:
Aaaand it's working now,thank you verry verry much for taking your time to help me
Click to expand...
Click to collapse
You have to run the right adb command for your device to unlock the bootloader after enabling in dev options something like
fastboot oem unlock

Magisk Installer Error

Hello. I'm using Android 8.1 arm64-v8
I'm downloaded the magisk manager for magisk modules but, gives the error:
- Detecting target image
- Device platform: arm64-v8a
- Downloading zip
... 0%
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.025 secs (42541120 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/block/mmcblk0p21]
HEADER_VER [0]
KERNEL_SZ [31739573]
RAMDISK_SZ [1602279]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-09]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.bootdevice=7824900.sdhci earlycon=msm_hsl_uart,0x78B0000 buildvariant=user]
CHECKSUM [70e61de5f33b76a1e4678c3bedd6ba760fba206d]
DTB [22328275]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
! Boot image patched by unsupported programs
! Please restore stock boot image
! Installation failed
How to fix this? Thanks
Sorry my English.

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs

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..