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.
Related
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!
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
[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.
Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help
Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break
Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8
I have Magisk 20.1 (Magisk Manager 7.5.1) currently installed on my Samsung Galaxy Tab A (2016). While initially installing it was not as straight forward as it might have been (install doc could use some work; I think it's written for folks with more familiarity with android devices on a day to day basis than those who root a phone maybe once every few years); I installed Magisk and it's been working fine.
However, this morning I had a notification that I needed to run Magisk setup. I told it to do so; it downloaded something; rebooted the tablet ( which wasn't warned of in the notification); and on coming back up ran Busybox so I'm assuming that was the setup. Going into Magisk Manager, however, I got the same notification over again. So I let it update again with the same result.
This time I told it to cancel the update/setup. I then tried to manually do the update from 20.1 (20100) to 20.3 (20300, latest available version). Update proceeded normally until repacking; which failed. Since Magisk is already installed and working (with several root level apps) on this phone; I can't see where this could be the "wrong image problem" which seems to be the most prevalent root cause of this kind of error. Unfortunately the update as distributed doesn't say anything about *why* it can't repack the image; so the message doesn't help us ordinary folks in debugging.
Any ideas as to what the actual issue is?
Android info:
Version 8.1.0
Kernel 3.18.14-1570595
Build M1AJQ.T580UEU4CSC1
Note: Busybox had an update I believe came out sometime yesterday (saw notification it updated successfully). Could it be that something in the Busybox update broke the Magisk update process?