Magisk Versions Post 23.0 Fails on Fresh install
akano12 opened this issue · comments
Device: Galaxy J6+ (SM-J610f)
Android version: 10
Magisk version name: 81658d4
Magisk version code: 27002
Tried flashing latest canary and flashing failed, also note that flashing 23.0 works well, after phone boots with v23 i can upgrade to latest canary without issues, initial flashing with anything post 23 fails.
if other logs are needed i can provide
Below you can find dmesg and recovery logs
dmesg.log
recovery.log
- Device is system-as-root
- Legacy SAR, force kernel to load rootfs
- No vbmeta partition, patch vbmeta in boot image
- Target image: /dev/block/mmcblk0p23
- Device platform: armeabi-v7a
- Constructing environment
- Unpacking boot image
Parsing boot image: [/dev/block/mmcblk0p23]
HEADER_VER [0]
KERNEL_SZ [12466999]
RAMDISK_SZ [871500]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2021-04]
PAGESIZE [2048]
NAME [SRPRF05A008KU]
CMDLINE [console=null androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1]
CHECKSUM [82788b6ef3b8f1668d515d1834585789cc67a1c2000000000000000000000000]
KERNEL_DTB_SZ [1710255]
ZIMAGE_KERNEL
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
SAMSUNG_SEANDROID
unexpected ASN.1 DER tag: expected SEQUENCE, got APPLICATION [19] (primitive)
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
Value too large for defined data type (os error 75)
Failed to process cpio
! Unable to patch ramdisk
Originally posted by @akano12 in #5040 (comment)
#8013 has the similar error in the log, not sure if completely a duplicate or not however since there are perhaps a couple issues being discussed over there, and Direct Install seems unaffected here.
Tried flashing latest debug version from github actions, now flashing finishes without errors (takes ~7 minutes to finish repacking) but upon rebooting to system device hangs on Galaxy J6+ logo (doesn't reach Samsung logo).
Post the initial flash recovery.log again from latest CI for comparison as well please.
Post the initial flash recovery.log again from latest CI for comparison as well please.
It seemd you are updating magisk while your boot image is already magisk-patched this time. Wow, looks like another regression 😂
Can you try again with stock boot image to see if the original regression disappears?
It seemd you are updating magisk while your boot image is already magisk-patched this time. Wow, looks like another regression 😂
Can you try again with stock boot image to see if the original regression disappears?
This is stock boot image, nothing flashed before magisk. I made sure to flash stock rom and start over each time i sent logs here lol, so that's really odd.
Will try to wipe all partitions from TWRP then flash stock again and see the outcome
Upload your boot image here.