-
Notifications
You must be signed in to change notification settings - Fork 13k
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.
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
Flashing from V19.4 to v24.1 Gives Bootloop & V19.3 working but gives only "magisk su" permissions not modules support #5466
Comments
@canyie Looking for your help btw! |
Note that the latest magisk manager cannot recognize early versions of magisk. So if you need to test whether v19.3 is working or not, you should install Magisk Manager v8.0.7 (can be found in releases) |
I used version 8.0.7 but no magisk detection but su only working!! |
Ohh... You can check if magisk daemon is running by executing `magisk -v`.
|
|
Seems to be a duplicate of #5148 |
Really, Is there a fix for this yet? |
No fix yet. It seems like a kernel restriction and we don't even know where the restriction is without kernel source. Please continue the conversation in #5148. |
Duplicate of #5148 |
Device: Vivo V5
Android: 6.0
Magisk version name: magisk canary 25
Magisk version code: 24102
I flashed all latest versions via patch boot.img from v19.4 to v24.1 all giving bootloop (Maybe bcoz of overlay.d)
. So, I tried flashing v19.3 and it flashed successfully without any bootloop but the problem is that it wont installed magisk fully, I have access to only "magisk su", I mean root access only, not modules or even magisk hide which was present in v19.3!! I even read about this issue in the old issues but everyone got fixed when they updated to new version but here I'm facing a whole new issues which is I'm unable to flash new version of magisk and old are not fully working!!
P.S: I can't flash magisk via recovery bcoz my device doesn't have custom recovery. So, flashing only via fastboot with unlocked bootloader.
The text was updated successfully, but these errors were encountered: