Thanks! That's all I needed to know. I'll wait for the next update, no problem.Bug with blank Downloads was already fixed in Magisk Manager Canary build (latest MM Canary is v7.3.3 (228))
Thanks! That's all I needed to know. I'll wait for the next update, no problem.Bug with blank Downloads was already fixed in Magisk Manager Canary build (latest MM Canary is v7.3.3 (228))
flashing magisk on these devices breaks locksreen and samsung accountDo you know if this issue happens on all Samsung recent devices or only this particular model?
I'm not sure what developer you might need to ask about that, but this is the wrong place for module requests
It has been discussed a lot/often in previous posts about some apps still detecting root although MagiskHide enforced (and SafetyNet passing)I got an issue with magiskhide.
When i'm going to open western union app in my samsung s5 (custom rom RR 7.0.2), its just close & saying rooted device. Even though i already used magiskhide...!
I got an issue with magiskhide.
When i'm going to open western union app in my samsung s5 (custom rom RR 7.0.2), its just close & saying rooted device. Even though i already used magiskhide...!
If you're using Magisk 19.3, try downgrading to Magisk 19.2 - I don't know why, but on my phone there's a difference. Toreba gives Connection Error -1103 on 19.3, but on 19.2 it's happy.When i'm going to open western union app in my samsung s5 (custom rom RR 7.0.2), its just close & saying rooted device. Even though i already used magiskhide...!
Appreciate the guess, and your consideration of this ongoing issue. When I turned off the option, a message came up making a positive reference to securing the device and now requiring a reboot to complete the action. Never saw that before on a developer option, and am hoping the reboot won't wipe the device or lose root, or make any other unwanted changes, or is that not possible...@duh1 Here's a thought on your old Netflix issue:
I recently had a troubleshooting session with a user that had issues with an app that would report that the bootloader was unlocked even though Magisk would successfully mask that state. Turned out that the app in question would look for the OEM Unlocking allowed option. Simply turning that off in Developer Options (not locking the bootloader again or anything like that) would let the app function again.
Worth a shot, I guess...
Appreciate the guess, and your consideration of this ongoing issue. When I turned off the option, a message came up making a positive reference to securing the device and now requiring a reboot to complete the action. Never saw that before on a developer option, and am hoping the reboot won't wipe the device or lose root, or make any other unwanted changes, or is that not possible...
Did you hide also Google Play Store? BTW, Magisk Canary is working well for you so don't update or switch channels or anything else until PoGO f*cks up again.I flashed the stock ROM on my J7 2015 and still, with Magisk 19.3 hidden and Magisk hide enabled, Pokemon detect that my phone is rooted, I fixed it by installing the Magisk Canary version, so far Pokémon Go hasn't detected Magisk
I have oem unlocking turned off on my pixel 2 after rooting with magisk. I turned it off a while back to see if it was preventing me from receiving update and I'm still able to fastboot flash updates.It won't wipe the device. But you should of course always have a backup of any important data so you should be fine...
Did it have any effect?
Edit: to clarify, what is referenced is FRP (factory reset protection). If I remember correctly it's only enabled if that switch is set to off.
Can you show screenshot from the main Magisk app screen, to see what is displayed there (Installed, etc)
Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.I'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Not pushed yet according to my magisk app.Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")... PWI have always have problems with magisk and bug reports think I have even failed with the debug version lol, although its closed I have added that the bug is not present with the debug version
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about itI'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?