There are differences between e-2.9-s-20250321478216-OFFICIAL-herolte and the newly created, as yet untested e-2.9-s-20250423-UNOFFICIAL-herolte referred here to as “update”, e.g. in the digital signature, and there is no OTA update for this UNOFFICIAL-herolte.
My Galaxy S7 has /e/OS e–2.9-s-20250321478216-OFFICIAL-herolte installed along with e-Recovery v2.9. Nevertheless: This UNOFFICIAL “update” by @ronnz98 works. Murena MDM is not pre-installed.
All right ! So I did install the ROM @ronnz98 gently made and MDM did disappear, which is great news. However, my device still belongs to an organization, and it’s still impossible to setup shelter, which I was previously able to do.
Looks like the bug is a bit deeper than what we thought. This build should do the job for most S7 user that would just like to get rid of this spying app, but it doesn’t fully solve my issue. Thanks anyway for the ROM !!
i think there is something related to MDM activation written into /data or /data/sdcard (aka available “internal storage” for normal user)
Maybe document your findings so far on the gitlab issue:
I’d like to bu i can’t connect my regular gitlab account… Says that this username is incorrect…
As I noticed it, murena mdm went back when i restored the boot image (when i tried to uninstall it using debloater app and a rooted phone). I think something is stored in the boot.img file.
The GitLab instance for e.foundation is hosted on their own servers, it’s not the same as gitlab.com. You need to create an account on their instance. Unfortunately they’re blocking just about every email domain outside of Murena so you have to use a murena.io email. If you don’t have one already, set up a workspace account at murena.io and use the email supplied by the workspace.
If you have difficulty registering the regular way Report an issue with this difficulty Getting an error message in new ID creation on /e/OS Gitlab? you can follow the advice there and ask for help from admins here.
Alright, I’ve shared a little summary with screenshots of what has been happening here until now. Hope that will help the team to find out what’s causing the bug.
Gael finally posted his 2025 roadmap. He’s talking about MDM in it. Murena tries to enlarge and offers solutions for companies and businesses.
I just noticed that after installing the umofficial /e/ by @ronnz98, my phone got rooted again and mdm is shown as removed in the debloater app history, which means that it has not really been removed. If i unroot my phone, it’ll be back… Can’t I get rid of this ?
Ps: I’m thinking, is there a way to get the log from a specific app ? Maybe i could get the logs from shelter and see where it fails in the process despite mdm being deactivated ?
Also, seems that my admin is still doing lot of things on my smartphone…
Greaaaat… Still haven’t found a solution
I dont’ think so, because :
Installing Magisk for the first time REQUIRES a full data wipe (this is NOT counting the data wipe when unlocking bootloader).
Hello @Xxpsilon !
I’m willing to try this method but cant find out how to do.
I’ve renamed the magisk.29.0.apk into magisk.29.0.zip and tried to “flash” it via the magisk app : did not worked.
Tried to “flash” it via e/recovery : did not worked.
Can you give me/us some more insight ?
Release notes for V3.0 say :
Settings
- Murena MDM is not included in /e/OS builds anymore
true, cannot see the MDM-App in security-settings nor in apps list anymore
yet still: the lock screen (after reboot only!) of my 3.0-s-20250528496287-official-herolte still states “this device is owned by your organization”
Same statement in swipe down-Quick menu (two swipes) that leads to info on “device administration” (or the like in Englisch)
This is the same for me here …
They closed the issue:
But for me it looks like a new kind of level or is it the same as before?
before the App foundation.e.mdm was present in Apps list and device security settings (but not active, least in my case, despite the statements/notifications that said otherwise)
Now it is not present anymore from what I a can tell
Only the statements/notifications are still present, which is odd…
So Yes, it is different
S7 was somewhat special with regards to the behaviour of the MDM implementation - from what I observed in the forum … it still is … obviously 
Haven’t done the update already but i suspected it would still be impossible to use shelter or parental control. This issue isn’t solved. MDM concerns have been heard and this is great, but i don’t now that the two issues are related…
I’ve done his method so i can explain. You hace to rename the magisk.apk into magisk.zip and then flash it using a recovery. I recommend you to use TWRP. Click on install, select the zip and that’s all. However, be careful about the modules you install as these can cause the phone to bootloop.
I can activate parental control now, that’s not the issue anymore, MDM is not in the way of anything nor does it actually hinder me from doing anything anymore, nor is the app present! - least in my case and as far as I can tell.
It is only the statements/notification from the system side that is odd - appears as if it were hardcoded (which I rather doubt) and not removed together with the app…(?)
edit… please refer to gitlab issue as it is a bit more complex obviously
