I'm running Magisk 15.3 on latest Nitrogen OS 8.1, Oneplus 3T.
Magisk Manager 5.5.4 was working perfectly. But in 5.5.5, it appears not to save my SU choices at all and is asking me for every time when a app needs root permission.
And since it is auto- downloading and upgrading without asking, it seems that if in the first time I didn't cut my internet in-time and let Magisk Manager download the upgrade file to nowhere I could find, it'll try to upgrade to 5.5.5 for everytime it runs, no matter how I uninstall and re-install in TWRP except do a full-wipe.
My system language was ZH-CN and when I change it to EN-US, everything works well.
Change back and the issue occurs again.
Can you fix this?
Related
Again I face a problem, now if I hide any application the application doesn't work or open, every time it crashed.
My device: Honor 8
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Logs?
Aid777 said:
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Click to expand...
Click to collapse
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
MechanicaIMan said:
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
Click to expand...
Click to collapse
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
I'm getting this exact same issue, I've attached logcat and magisk logs after hiding the Play Store with Magisk Hide, then attempting to open it (and having it immediately crash). Magisk 17.1, latest Magisk Manager app, Pixel 2XL, Oreo 8.1 (July patch). Apps open again after deselecting them from Magisk Hide. Was working fine on 16.4, stopped working after 17.1, and a complete Magisk uninstall/reinstall did not fix it.
Magisk Log, Logcat.
Aid777 said:
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
Click to expand...
Click to collapse
I had the problem after updating from 16.0 with 5.8.3 to 17.1 with 5.9.1, but I also tried using the newest manager with 16.0, and that didn't work either. So there must be some kind of issue with the newest version(s) of the manager. I completely uninstalled 17.1, flashed 16.0, updated manager to 5.9.1 (crashing returned), then uninstalled 5.9.1 and installed the 5.8.3 apk without changing Magisk. If you have 17.1 installed now, then you might want to try just replacing manager with an older version before you bother with completely uninstalling/downgrading Magisk. You can simply uninstall the manager app without uninstalling Magisk, but I don't know if Magisk 17 will work okay with the older versions of manager, since I haven't tried that myself and don't really know anything about Magisk.
It is the same with me
Google Play Store crashed
Same here guys with LG g6, I installed the 17.1 by direct installation (within the app) and then when I go to magisk hide, it keeps crashing!
I've had the exact same experience as @mechanicalman on my V30+ (US998).
Any solution guys.
same with me, would appreciate somebody to have a look.
Magisk Hide tickboxes in Magisk Manager make Oreo crash
Hi, same with me: Oneplus3 with stock OOS 5.0.5 (oreo), dm-verity warning at boot since when I was a superSU user.
Everything was fine with Magisk 16. Since update to 17.1 and MagiskManager 5.9.1, the Magisk Hide menu keeps crashing. I've reflashed the stock ROM, reinstalled magisk 16 and 17.1, used the magisk deinstaller. The problem seems tied with MagiskManager 5.9.1
- In the MagiskHide menu, sometimes I can check 5 to 10 apps before it crashes.
- In the MagiskHide menu, sometimes only 1 check or 1 uncheck makes the phone crash.
When MagiskHide crashes it:
- blacks out the screen for a few seconds
- then starts a reboot (a soft reboot where I am not asked my device password, which I have set to be asked during boot)
- then it eventually launches Android after a very long time (usually OOS 5.0.5 opens after 20 cycles of the animation, but after a MagiskHide crash, it can take 200 cycles (from which I stop counting))
I attached the Magisk log immediately after reboot, which doesn't say much (some lines similar to previous and following ones removed).
MagiskManager: "Preserve force encryption" is on (default), "Preserve AVB 2.0/dm-verity" is off (default), Modulues are Busybox, MM for recovery, Xposed, YouTube Vanced, rest of settings are default.
I hope that helps narrowing down the problem.
I'm coming here with this issue occurring on my LG V30+ and Magisk 17.1
Hi, I'm having the same problem as a couple of people, magisk 17.1, newest Magisk Manager, then when I try to go into the magisk hide menu, the app crashes to home screen.
I enabled core only mode to see if it was any of my modules but the problem persists.
lenovo p2 same problem of manager crashing when entering hide menu
Same problem on my Nexus 5, Dirty Unicorn with Oreo 8.1
Same problem here on the V30+. Anyone able to confirm downgrading works?
Also, what do most of y'all use hide for? I was gonna try to use it to set up chase pay for that 5% rewards. lol
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk Manager v6.0.0, OOS9.0 OnePlus 6. App crashes while opening Magisk hide menu. Thanks
I'm currently using Huawei's EMUI 8.1 on a P20 and trying to hide Magisk Manager by using the random renaming feature. It all works perfectly until I restart the phone. After restarting, it will produce a second Magisk Manager as I believe it can't find the original installation name and hence loads a placeholder version. I can confirm this happens if I completely uninstall the apk, reboot and Magisk Manager is still in the app drawer.
Is there a bug whereby after changing the package name, it's not remembering what the renamed package is called?
bump
Did you find any solution for this? I am having the same issue for the same phone
I noticed something strange, on my phone and I'm trying different ways to solve it, but it just does not "work".
I have 2 x Magisk icons in my phone and I cannot remove them, so that I only have 1 x Magisk.
Here's some background,...
My phone: OnePlus 6 [OP6], with stock Oxygen OS 9.0.9 [OOS 9.0.9] Android and running custom kernel [Omega].
I had been running a ROM [xXx NoLimits] which is a Magisk Module.
For last 11+ months, I have had no issues with my phone, no issues with Magisk, and no issues with root really.
I updated to Magisk v20.0 (but it seems it was the Beta / Canary channel) and also,
I had used the "Hide Magisk Manager" feature, for 1 specific app. to work.
Just this week, I noticed some issues with my phone or that I had 'lost' root
This happens rarely, and I just reinstall Magisk, but it resolves itself.
So, I went looking and saw an odd thing: 2 x Magisk icons.
Since then, I have tried:
- Magisk Uninstaller [Magisk-uninstaller-20191011.zip]
- Flashed unpatched BOOT.img file, Flashed TWRP. Then, rebooted to TWRP.
- Flashed Magisk, flashed the custom kernel.
Still, I saw 2 x Magisk icons.
I could see 1 Magisk was on STABLE channel, while other was on CANARY channel.
This was strange.
So, I changed the CANARY to STABLE, etc. etc...
Anyway, too many combinations of uninstalling and removing root, reinstall Magisk, etc... and I still don't know how to really uninstall Magisk and start from ZERO again.
I have lost Magisk's association to my Magisk modules too.
Can anyone help or advise?
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
I think I resolved my issue now...
I uninstalled Magisk using the official Magisk Uninstaller.
I also uninstalled the 2 x Magisk apps in my launcher, using this .APK ---> "Uninstalled SystemApps" ( https://github.com/nicolaserlonghi/UninstallSystemApps )
Then, I had to go through re-installing the BOOT.img, Magisk and most importantly, the ROM (which itself was a Magisk module).
Slowly, it populated the Magisk module list and 'SuperUser' lists, and I think I got the phone back into how I had it.
Didgeridoohan said:
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
Click to expand...
Click to collapse
Yes, exactly.
Thanks for this tip, but I reached this conclusion anyway...
and used another .apk (Unsinstall SystemApps) to remove the Magisk Manager (which was the result of using "Magisk Manager Hide",
but then I must have mixed up Stable & Canary builds of Magisk on the phone, etc.)
Didgeridoohan said:
Sounds like you just have two Managers installed.
Click to expand...
Click to collapse
One thing weird though is, quite a few modules that were previously installed are missing from the Magisk "modules" section.
When I 're-install' them, they still don't show in the "modules" section.
For Example:
Vanced, Advanced Charging Controller, etc... all have been installed, but not showing up in Magisk.
I just had a weird situation of 2 different Magisk installs (at first it seemed like 2 x Managers), but it could be 2 different Magisk builds:
stable and canary
I don't know how to explain it, but maybe the Magisk Uninstaller doesn't work properly on Canary builds?
Anyway, my issue now is modules don't get listed in the Magisk Manager.
No, you did not have two different Magisk builds installed at the same time. Can't happen...
And without more to go on (logs, etc) it's gonna be real hard to help with the module issue.
I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.
Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.
UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:
I am having OnePlus7T which does not have TWRP. Magisk was installed through patched boot image while rooting many months back. At that time Canary version was recommended and I had installed that.
I have updated the ROM, Magisk Manager and Magisk in these months via OTA.
Everything works except this app, https://play.google.com/store/apps/details?id=in.org.npci.upiapp&hl=en. It detects even though hidden with MagisK Hide. Magisk package manager is also hidden but this app does not work. It opens, registers the user but later detects root.
Since last few days Magisk is crashing when opened for no apparent reason. Restarting the phone didn't make any difference. If I long click on the app and select Magisk Hids or Supeuser or Modules it opens but when I try to go to main Manager screen it crashes. How to resolve this? Phone is still working as intended and I have root access for apps not hidden in Magisk Hide.
How do I update Manager from Canary to Stable? Can I just download a stable Manager apk and install it on top of the Canary? Which version should be used? Will Magisk also need to be installed again? Will I lose root?
Can anyone explain the steps in detail as I am bit confused.
My Magisk also crash like this