"Upgrade to full magisk to finish the setup" loop

[catfromplan9]

I cant get into magisk, please help

[catfromplan9]

It says downloading for a couple sec when i click okay, then that closes, and nothing happens

[catfromplan9]

I see this in the logs: java.io.FileNotFoundException: https://f-droid.org/repo/com.topjohnwu.magisk_30600.apkv30.6/Magisk-v30.6.apk

[pixincreate]

without logs, can't help.

[Br3nnabee]

Am having the same issue. What logs would you like to help resolve this?

[pixincreate]

follow this bug report template:

<!--

## READ BEFORE OPENING ISSUES

All bug reports require you to **USE DEBUG BUILDS**. Please include the version name and version code in the bug report.

If you experience a bootloop, attach a `dmesg` (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as `last_kmsg` or `pstore ramoops` are usually not enabled by default. In addition, please also upload the result of `cat /proc/mounts` when your device is working correctly **WITHOUT MAGISK**.

If you experience issues during installation, in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the `boot.img` or `recovery.img` that you are using for patching.

If you experience a crash of Magisk app, dump the full `logcat` **when the crash happens**.

If you experience other issues related to Magisk, upload `magisk.log`, and preferably also include a boot `logcat` (start dumping `logcat` when the device boots up)

**DO NOT** open issues regarding root detection.

**DO NOT** ask for instructions.

**DO NOT** report issues if you have any modules installed.

Without following the rules above, your issue will be closed without explanation.

-->

Device:
Android version:
Magisk version name:
Magisk version code:

[catfromplan9]

Am having the same issue. What logs would you like to help resolve this?

Fixed by rebooting into fastboot and re-flashing the rooted bootloader image (can also re-flash the stock one and start from stratch iirc)

[pixincreate]

should i be adding as an faq to the repo?

[Br3nnabee]

2 re-flashes later, I managed to get it working. I followed the exact same steps each time and it wasn't working, but this time it did (no clue, don't ask)? I did have to manually update the apk using the apk release from here, I couldn't do it by just via the download button that's there in PixeneOS (although I did this in previous attempts too and it didn't work). As was noted earlier, the only standout thing in the logs is a filenotfound, but for me it tries to fetch the actual pixincreate one instead of the topjohnwu one: java.io.FileNotFoundException: https://github.com/pixincreate/Magisk/releases/download/canary-30700/app-release.apk

I can send the logs if you'd still like, but I don't know if there's anything of value in there.

[pixincreate]

but for me it tries to fetch the actual pixincreate one instead of the topjohnwu one

this is expected since i've made the app to point to my repo. i'll look into this 404 issue asap.

[pixincreate]

i think this 404 was caused by the release-channel transition.

until 30600, this fork was publishing canary builds like canary-30600. upstream later stopped publishing canary builds, so this fork also moved to normal versioned releases like v30.6 and v30.7.

that means canary-30700 intentionally does not exist. 30700 corresponds to the stable v30.7 release.

please install or update to the latest apk from the Releases page:

https://github.com/pixincreate/Magisk/releases/latest

if the "Upgrade to full Magisk" loop still happens on the latest v30.7 release, please reopen/comment with a fresh Magisk app log so i can check the exact url it is trying to download.

[pixincreate]

i did also push a fix to the ci to release tag names instead of app-release.apk just so that stub does not break.

https://github.com/pixincreate/Magisk/actions/runs/28913988160

[pixincreate]

Rechecked this independently from the Android 17 / Zygisk work. This issue should remain open for now.

The currently shipped stub constructs this stable URL:

https://github.com/pixincreate/Magisk/releases/download/v30.7/Magisk-v30.7.apk

However, the existing v30.7 release contains app-release.apk, not Magisk-v30.7.apk, so the stub URL still returns 404. v30.6 has the same mismatch. The workflow now renames APKs to Magisk-${RELEASE_TAG}.apk for future releases, but that does not repair assets referenced by already-shipped stubs.

Closure criteria: backfill Magisk-v30.6.apk and Magisk-v30.7.apk as aliases of the corresponding signed app-release.apk assets (or provide another compatibility path that works for existing stubs), verify both URLs return the APK, then close. This is independent of #30/#32/#34.