Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Requires Additional Setup" #8409

Closed
fooooter opened this issue Sep 22, 2024 · 8 comments
Closed

"Requires Additional Setup" #8409

fooooter opened this issue Sep 22, 2024 · 8 comments

Comments

@fooooter
Copy link

fooooter commented Sep 22, 2024 •
edited
Loading

Device: Motorola One Vision XT1970-3 (kane)
Android version: 14 (LineageOS 21)
Magisk version name: 4f18a66
Magisk version code: 27008

Each time I launch Magisk Manager, I get the "Requires Additional Setup" prompt. Upon hitting OK and reinstalling Magisk directly through the app, I get the following output:

- Target image: /dev/block/by-name/boot_b
- Device platform: arm64-v8a
- Installing: 4f18a66d (27008)
Parsing boot image: [/dev/block/by-name/boot_b]
HEADER_VER      [1]
KERNEL_SZ       [33394700]
RAMDISK_SZ      [14277819]
SECOND_SZ       [133209]
RECOV_DTBO_SZ   [0]
OS_VERSION      [14.0.0]
OS_PATCH_LEVEL  [2024-09]
PAGESIZE        [2048]
NAME            []
CMDLINE         [loop.max_part=7 androidboot.boot_devices=13520000.ufs]
CHECKSUM        [f1c4dd524609d2bd84543ccda9708c583237affd000000000000000000000000]
- Unpacking boot image
KERNEL_FMT      [raw]
RAMDISK_FMT     [gzip]
unexpected ASN.1 DER tag: expected SEQUENCE, got APPLICATION [1] (primitive)
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Magisk patched boot image detected
Loading cpio: [ramdisk.cpio]
Extracting entry [.backup/.magisk] to [config.orig]
Restore [.backup/init] -> [init]
Removed entry [.backup]
Removed entry [overlay.d]
Removed entry [overlay.d/sbin]
Removed entry [overlay.d/sbin/init-ld.xz]
Removed entry [overlay.d/sbin/magisk.xz]
Removed entry [overlay.d/sbin/stub.xz]
Dumping cpio: [ramdisk.cpio]
- Patching ramdisk
No space left on device (os error 28)
- Pre-init storage partition: sda4
Loading cpio: [ramdisk.cpio]
Add file [init] (100750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add file [overlay.d/sbin/magisk.xz] (100644)
Add file [overlay.d/sbin/stub.xz] (100644)
Add file [overlay.d/sbin/init-ld.xz] (100644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/init-ld.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/stub.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add file [.backup/.magisk] (100000)
Dumping cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/dev/block/by-name/boot_b]
HEADER_VER      [1]
KERNEL_SZ       [33394700]
RAMDISK_SZ      [14277819]
SECOND_SZ       [133209]
RECOV_DTBO_SZ   [0]
OS_VERSION      [14.0.0]
OS_PATCH_LEVEL  [2024-09]
PAGESIZE        [2048]
NAME            []
CMDLINE         [loop.max_part=7 androidboot.boot_devices=13520000.ufs]
CHECKSUM        [f1c4dd524609d2bd84543ccda9708c583237affd000000000000000000000000]
KERNEL_FMT      [raw]
RAMDISK_FMT     [gzip]
unexpected ASN.1 DER tag: expected SEQUENCE, got APPLICATION [1] (primitive)
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER      [1]
KERNEL_SZ       [33394700]
RAMDISK_SZ      [14277819]
SECOND_SZ       [133209]
RECOV_DTBO_SZ   [0]
OS_VERSION      [14.0.0]
OS_PATCH_LEVEL  [2024-09]
PAGESIZE        [2048]
NAME            []
CMDLINE         [loop.max_part=7 androidboot.boot_devices=13520000.ufs]
CHECKSUM        [f1c4dd524609d2bd84543ccda9708c583237affd000000000000000000000000]
- Flashing new boot image
- All done!

After a reboot and redoing these steps, problem persists with the same results.

Magisk log:

---Magisk Logs---
4f18a66d (27008)

09-18 12:14:14.570  4300  4300 I : �Magisk 4f18a66d(27008) daemon started
09-18 12:14:14.572  4300  4300 I : �* Device API level: 34
09-18 12:14:14.664  4300  4302 I : �** post-fs-data mode running
09-18 12:14:14.703  4300  4302 I : �* Initializing Magisk environment
09-18 12:14:14.999  4300  4302 I : �* Running post-fs-data.d scripts
09-18 12:14:15.001  4300  4302 I : �* Setup internal mounts
09-18 12:14:15.004  4300  4302 E : �No space left on device (os error 28)
09-18 12:14:15.004  4300  4302 W : �mount: preinit dir not found
09-18 12:14:15.004  4300  4302 I : �* Running module post-fs-data scripts
09-18 12:14:15.004  4300  4302 I : �* Loading modules
09-18 12:14:16.469  4300  4302 I : �** late_start service mode running
09-18 12:14:16.469  4300  4302 I : �* Running service.d scripts
09-18 12:14:16.469  4300  4302 I : �* Running module service scripts
09-18 12:14:44.011  4300  4302 I : �** boot-complete triggered
09-20 07:49:24.057  4300  6935 I : �denylist: initializing internal data structures

Magisk was installed using TWRP.
@JasonKhew96
Copy link
Contributor

as docs stated https://topjohnwu.github.io/Magisk/install.html#custom-recovery

Installing using custom recoveries is only possible if your device has boot ramdisk. Installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the Patch Image method.

@fooooter
Copy link
Author

as docs stated https://topjohnwu.github.io/Magisk/install.html#custom-recovery

Installing using custom recoveries is only possible if your device has boot ramdisk. Installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the Patch Image method.

I've just tried to patch the boot.img and flash it with fastboot, but it ended up the same. I've also tried to boot the image using fastboot and flash it within the app, but again, without success (all of this was done after a complete uninstall of the previous instances, of course).

@aviraxp
Copy link
Contributor

aviraxp commented Sep 23, 2024

  • Patching ramdisk
    No space left on device (os error 28)
  • Pre-init storage partition: sda4

what partation is sda4 on your device？

@fooooter
Copy link
Author

  • Patching ramdisk
    No space left on device (os error 28)
  • Pre-init storage partition: sda4

what partation is sda4 on your device？

lrwxrwxrwx 1 root root  15 2024-09-22 18:13 persist -> /dev/block/sda4

"persist"

@fooooter
Copy link
Author

This problem most likely cannot be resolved due to lack of space in "persist" partition. It would be necessary to resize it using tools like parted, but it would be extremely dangerous due to it being almost at the beginning of the partition table. Closing this issue.

@aviraxp
Copy link
Contributor

aviraxp commented Sep 23, 2024

I am curious, what's the size of your /persist? Preinit files only take a few kbs.

@fooooter
Copy link
Author

I am curious, what's the size of your /persist? Preinit files only take a few kbs.

:/ # df /dev/block/by-name/persist
Filesystem      1K-blocks  Used Available Use% Mounted on
/dev/block/sda4     27632 26980       652  98% /mnt/vendor/persist

Creating a single empty file is impossible.

@fooooter
Copy link
Author

Screenshot_20240923-123511_Material Files.png

Heh, I guess I found what is taking so much space. I assume those logs are safe to be deleted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aviraxp @JasonKhew96 @fooooter