Magisk Manager 5.x closing upon opening - Magisk

I have a Xiaomi Redmi x4 that has been flashed and running mokee.
I can flash Magisk 12 and the Magisk Manager 4.3.3 just fine and then flash the fix (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431) to make it unseen and the CTS profile to go green, working root etc. If I flash Magisk v13 or 13.1 I believe that it flashes okay, but when I install Magisk Manager 5.x whenver I try to open the manager it will instantly close itself. I've tried using the magisk uninstaller and trying again with fresh ROM but it seems to do the same thing.
I'm unsure if this is at all in any way a common problem, I did a little looking around and couldn't find my problem exactly. My apologies if has been answered many times before.
Thanks.

I got this problem since beta too

i have the same problem

it's know issue, just revert back to 5.0.6.
i suggest to refer to magisk manager's github topic: https://github.com/topjohnwu/MagiskManager/issues/225

Related

Magisk 11.1 and ViperOne M9 ROM issues - lost root

Hi guys - I'm having trouble with the latest version of Magisk...
My ROM - ViperOne M9 (for HTC One M9) - comes packaged with Magisk 10.6 and phh's Superuser, and it seems to work ok out of the box. However, I can't get it to pass SafetyNet checks with HideMagisk enabled, which is an annoyance as I can't use certain apps (no, NOT Pokemon GO FYI ). The Magisk Manager was advising to update itself, which I thought might help - so I did. After a reboot I have now lost root on my device, and cannot get it back.
A knock-on effect seems to have taken out phh's Superuser too, as it now complains of out-of-date binaries when the phone boots up, and I'm not getting any permission requests any more. I tried revoking Magisk's permissions, but it never tried requesting them again.
I flashed the phone using the latest TWRP, and my firmware and bootloaders are up to date also.
Not sure whats going on here - any ideas?
I could re-flash the phone, as I did a complete wipe earlier today to update ViperOne to the latest version (version 6.00) - so it's not a major headache, and should give me root back. But then I'm back to a broken hide-root/SN bypass. Again, this isnt a major problem since I'm used to not using those apps - but it would be nice to have.
Cheers.
Guys, managed to resolve my problem.
I downloaded the latest ZIP for Magisk 11.6 and phh Superuser, and flashed using TWRP. Rebooted, and all working!!
Also FWIW, I solved the problem with SN failing.... well I installed Magisk 11.6 and the work you guys did obviously did it for me, so thank you!

Samsung S5 Plus Magisk above v12 boot loop stuck on boot logo

Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please
I have also fully reinstalled the ROM with formatting everything and it still don't boot
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.
Flash your stock bootloader then try flashing magisk
I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?
No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492
cross the fingers (I hope that you say like that in English)
Fingers crossed they sort it. Would love yo be able to use magisk again
Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.
It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.

Backward switching magisk 19 (beta) -> 18 (stable) caused problem.

[Problem]
I noticed google pay not working after enjoying magisk happily for two days.
[Research]
I searched the forum and found many others have issue with google pay, too.
[Trial]
I started to do something with the hope to solve this problem.
1. I changed the update channel to beta test and installed magisk v19. Google pay was not working.
2. I then changed back to stable update channel to install magisk v18. Strange thing happened.
3. Phone booted fine but magisk manager detected no trace of magisk. I re-flashed patched_boot.img. Same thing, magisk was gone.
4. I am on stock ROM (S6 edge) and installed magisk by patching boot.img. I had no TWRP recovery. I could not do much under this circumstance.
5. So, I was in a situation of missing magisk and disabled google pay.
[Final]
I flashed the stock ROM via odin.
1. The google pay was working again in stock ROM (without root).
2. I lost magisk (and root).
I will install magisk again if google pay can work with it. The problem is the security check by google. I still hope there will be some work-around method.
You can never be certain that a dirty downgrade will work. You can of course try, but be prepared for trouble.
If I remember correctly, in this case, simply uninstalling the Manager and reinstalling the apk that comes bundled with v18.1 might have fixed things.

I've got several problems after I use Hide Magisk Manager feature

MagiskHide didn't wotk so I used Hide Magisk Manager feature. It works fine but then I encounter several problems after I used that feature. Magisk is v20.0 and Magisk Manager v7.3.5 (the latest).
My phone is Xiaomi Redmi 4X with custom ROM from AospExtended v6.7 (Android Pie 9.0).
- Youtube (or specifically Vanced) doesnt appear at all in the app drawer. I've tried reinstalling & rebooting several times using Magisk Manager but it still doesn't appear. I even installed 2 Vanced modules from Magisk Manager but I still cant find either of those in the app drawer. But then, I tried uninstalling those modules, it tells me to reboot, right? I reboot my phone but none of those are uninstalled. Both of them are still in the Magisk Module with "module will be removed at the next reboot" warning even AFTER rebooting my phone!
I also tried installing Vanced manually with the non-root version but the app wont install. Basically, I cant use Youtube at all!
- This problem with Magisk Module doesnt only happen in Vanced. I think it also happens in other module. My Blobmoji is installed but the emoji I have isn't the blobmoji, it's the built in one instead.
- I dont know if this is related but the wifi won't connect at all. It just keeps "searching" for connetion despite my home has 2 wifi routers.
It might be related, it might be not, but I've used this custom ROM for nearly a year and I havent faced any wifi problem at all. There was no major update from the ROM from the last few weeks either. Coincidentally, this problem happens after this Hide Magisk Manager fiasco, thats why I put this one here.
What happens? What should I do?

Magisk app not found after updating ROM

Hello everyone, I have a weird issue that I never encountered before. I updated my custom ROM from fastboot, and as always I had to re-root my device after updating. Im under Android 12, so I didnt use TWRP but I used the patched boot image method to reinstall magisk and have my phone rooted. Surprisingly, it seems my phone is rooted correctly, but the Magisk app shows Installed:N/A. A quick google search showed that it could be due to not unhiding Magisk before updating (even If I never did in the past and never had this issue). I tried the solution I found (unistalling magisk from adb) but it didnt fix the problem. Any idea on how to solve this?
[Discussion] Magisk - The Age of Zygisk.​Magisk 24.1 released and perfect for android 12.

Categories

Resources