Update using Direct Install doesn't update Magisk

Update using Direct Install doesn't update Magisk - 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..

Related

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!

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

TS10 firmware Image [ WAS IMPOSSIBLE TO ] root

Hi fellows
I have an Android Headunit based on TOPWAY TS10 firmware
I tried to patch the boot.img but when fhask to headunit, it enters in bootloop mode
Can anyone here help me rooting this image please ?
Link to GDrive image here -> TS10_BOOT.7z
I will be greatfull with the one who roots this boot (I need to user Alpha Backup Pro to backup my Spotify Gygabites of data in case I reset the unit to be abre to recover my APK with all the data and without root privileges, is impossible)
Thanks in advance

Here below the Magisk v23 LOG ---
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [2]
KERNEL_SZ [17090572]
RAMDISK_SZ [779984]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [161962]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2020-02]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [3ee1e2a9b7347c65779485fed4ab909a2f546ca4000000000000000000000000]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- 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=[false]
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]
Patch @ 00D2DB4C [736B69705F696E697472616D667300] -> [77616E745F696E697472616D667300]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [2]
KERNEL_SZ [17090572]
RAMDISK_SZ [779984]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [161962]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2020-02]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [3ee1e2a9b7347c65779485fed4ab909a2f546ca4000000000000000000000000]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER [2]
KERNEL_SZ [17090572]
RAMDISK_SZ [1088243]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [161962]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2020-02]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [8472aa1bd1126888f4bea8ac2c7745935f7b4897000000000000000000000000]
****************************
Output file is written to
/storage/emulated/0/Download/magisk_patched-23000_6cyCZ.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!

Found the problem while disassembling: take a look below
Code:
Image file a44a385a-9cbf-11ea-bb71-8bb1f7c98e0b.decrypted open successful, size = 36700160 byte
Found ANDROID BOOT IMAGE
Config header info save to firmware\cfg\a44a385a-9cbf-11ea-bb71-8bb1f7c98e0b.cfg
CFG section add to firmware\config.ini
ATTENTION! Unknown format for kernel block, magic= 0x14328000
kernel block save to firmware\kernel\zImage (size = 17090572 bytes)
Found GZIP format for ramdisk block
GZIP unpack successful...
Found CPIO format for ramdisk block
firmware\ramdisk\apex
firmware\ramdisk\avb
firmware\ramdisk\avb/q-gsi.avbpubkey
firmware\ramdisk\avb/r-gsi.avbpubkey
firmware\ramdisk\avb/s-gsi.avbpubkey
firmware\ramdisk\debug_ramdisk
firmware\ramdisk\dev
firmware\ramdisk\fstab.ums512_1h10
firmware\ramdisk\init
firmware\ramdisk\mnt
firmware\ramdisk\proc
firmware\ramdisk\sys
CPIO unpack successful...
Unpacked ramdisk save to firmware\ramdisk\
List of files and folders with their UNIX-attributes save to firmware\cpiostatfile.txt
Unknown format for dtb block, magic= 0x00000DD0
Error in dtb block, data save to firmware\dtb\dtb_tmp.img
Error in dtb block
Unpack a44a385a-9cbf-11ea-bb71-8bb1f7c98e0b.decrypted fail
Now.... let's work to find a solution

boot image uncompressed (this is the original "a44a385a-9cbf-11ea-bb71-8bb1f7c98e0b" file)

{
"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"
}
Whell I have this error while using Android Boot Image Editor with a magisk patched image
It looks like magisk is not doing what he is intended to do correctly !!!

Here my little project:
NO AVAILABLE IN GITHUB ANYMORE
This will allow you to have root privileges in original firmware, but read VERY CAREFULLY as this method int NOT SAFE at all
At least for me it do the trick as I expected

Can anyone here download the file TS106Magisk from 4PDA forum ?
https://4pda.to/forum/index.php?showtopic=1015856&st=853
And share the file here ? please ?

mariodantas said:
Can anyone here download the file TS106Magisk from 4PDA forum ?
https://4pda.to/forum/index.php?showtopic=1015856&st=853
And share the file here ? please ?
Click to expand...
Click to collapse
I also tried, but seems it is 404.

Andason74 said:
I also tried, but seems it is 404.
Click to expand...
Click to collapse
Yes, only for registered users !

... and I'm searching a registered user to download and share that file so we ca install magisk root in our devices !

mariodantas said:
... and I'm searching a registered user to download and share that file so we ca install magisk root in our devices !
Click to expand...
Click to collapse
Let us know what ya find!

Andason74 said:
Let us know what ya find!
View attachment 5340897
Click to expand...
Click to collapse
Well, it seems that you, @Andason74 will be my new xda hero !!!!
Will try to flash it today and come back to you with updates !

Project to ROOT any TS10 Firmware
Read it very CAREFULLY !
(NOT AVAILABLE IN GITHUB)

Andason74 said:
Let us know what ya find!
View attachment 5340897
Click to expand...
Click to collapse
Did you have any success with this firmware @mariodantas ?

iceze said:
Did you have any success with this firmware @mariodantas ?
Click to expand...
Click to collapse
No, that solution send me 400$ ownice K7 to the trash
That's why I created TS10-Firmware Workbench

Hello, I have a 4GB and 32GB TS10 android radio, the unit shows a message on the screen in red letters that says hardware does not support 360 viwe and it keeps going in and out of the application, I need to change the software, can you help me please

Database Develop

welcome

Update using Direct Install doesn't update Magisk - Magisk

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

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

Related

Magisk is not installed after flashing patched_boot.img

Magisk Installer Error

Unable to repack boot image

Infinite loop with patched magisk boot.img

TS10 firmware Image [ WAS IMPOSSIBLE TO ] root

Categories

Resources