Maybe not necessary, i just extracted the boot.img from the .ZIP using basic /e/OS,
and I think the s7 recovery allow flashing from internal storage,
BUT
better is to wait @Xxpsilon for fresh and precise instructions,
As i don’t own the device, and my experiences with Magisk were a few years ago, when i wanted to use my Bank app (credit agricole) that need a Magisk module to mask the “non-GogolOS”. Now i simply use the browser…
To flash the patched-boot.img, i used to use TWRP,
I don’t know how to deal with the recovery-e that only manage .ZIP.
But again, native /e/OS can create a .ZIP from a .IMG file…
This is french expression translation,
Better traduction in English language could be : "Really ?? " or “Oh, nice ! !”
I often see bad reactions on this forum due to “language barrier” missunderstanding.
and was hurting myself sometimes.
be cooler man ! (mean confident and relax in french, not cold)
@VinK3645 is a regular user of this forum he know for sure that you are a serious personn…
(regular, ah ah, another double meaning adjective, but well adapted this time)
Flashing a MagisK patched boot.img is one way to root the Galaxy S7 - and the most proclaimed installation method on the WWW.
The method I used also works - with the advantage that rooting a non-root /e/OS installation subsequently does not delete any data. In addition, Magisk creates a backup of the boot.img with my method, so that the original boot.img (unpatched) is restored after a self-uninstallation of MagisK.
My recommendation:
Study the Magisk Wiki of @topjohnwu carefully and learn something new, Monsieur @cool_piero
I’ve already read this wiki, and as @piero underlined it, i’ve seen that a data wipe is necessary to install magisk.
As i’m apparently not able to understand a thing of this wiki, i’d really like if you @Xxpsilon could clearly share your famous methode so that we can enjoy a rooted /e/os without any data loss and a “mdmless” system.
The stroke of genius comes from @topjohnwu. I only use the potential of this powerful Android tool.
@VinK3645 it’s like in school: you don’t learn anything by copying. Trying things out yourself improves your own knowledge and you don’t have to rely on others.
In the meantime, I’ve removed @ronnz98’s /e/OS-U 2.9 on my Samsung Galaxy S7(herolte) and installed further builds/e/OS-S official-herolte starting from /e/OS-S e-2.4.1-s-20241008439849-official-herolte.
Murena MDM App v6.03 (not activated) is implemented in /e/OS-S from version e-2.6.3-s-20241217455357-official-herolte.
The Murena MDM app is not displayed under > All apps (25 apps installed), but can be found with “Search setting”.
In e-2.9-s-20250321478216-official-herolte, as in /e/OS-U 2.9, I’ve subsequently installed MagisK without data loss, bootloop or other malfunctions. Then used the De-Bloater app (with root rights) to eliminate the unwanted Murena MDM app.
Last but not least, Magisk was instructed to uninstall itself again without leaving any residue. Thought - done. Now e-2.9-s-20250321478216-official-herolte runs flawlessly without Murena MDM.
If you don’t believe it but still want to know - try it out for yourself. Now!
You are totally right, but not everybody have some spare devices to make experimentations.
.
As example, Since Yesterday for the first time in 5 years, one my s4mini refuse to be flashed, (Heimdall 1.4.2, Heimdall 2.1.0, Galaxy-Flasher, Odin Linux, Odin windows, and Eros android)…
I have error when trying to flash TWRP, even stock full firmware with nanderase and repartition enabled is not accepted by Odin3 !
Ok, for the first time, i was managing partition table, trying to adapt an alternative method originally for the s3,
the howto was not very well written and i have a newer version of the used tool…commands was not exactly the same,
i was confused at the end, i loose my mind when i see unusual red lines in TWRP log, (now i think it could be corrected at the moment), panicked, i quickly decided to go back to stock considering it as a safe base to restart from scratch, so i loose TWRP and the device is now stuck in stock SamsungOS android 4.4.2 : stock recovery, system read only…
.
I want to install full e-2.3-r on the s4mini (including Advanced Privacy),
I already achieved to build without the famous “out of space” error,
Now i need to enlarge SYSTEM partition on the device…
I gave up with the “custom.PIT” way because signed since the s2
i will have a go to learn how to buld a custom TWRP that way is promissing but impressionning…
and use flashable repartition script (a bit like to trebelize pre-Oreo device)
(I still have 2 working devices…they cost 20€)
Let’s take our great GSI and ROM assebler @Colors and @ronnz98 as an example. Especially @roonz98 builds private CustomROMs, in colloquial language “unofficial” ROMs, in huge, unprecedented numbers and with racy speed, without owning the devices himself. He offers them to the community with the addition “Use it at your own risk!”
If no one has the corauge to take a risk to test these debut work, then we all won’t know if the builds work. Accordingly: No risk, no fun!
I would really like to follow your advice and go for it, but there is one thing you may have not understood here : this is my personnal phone and i only have one. Which means that i will not take the risk to experiment something that may brick my phone or corrupt its boot process. I don’t have lots of spare devices as you. It’s fun when you’ve got an old free phone and you just try to do something. It’s not the same when it’s about your personnal phone.
I will not try if i don’t know the steps i have to follow. If you don’t want to share your methode, fine. I guess i’ll try with adb myself and if it fails i’ll switch the system until /e/ removes mdm. Which will cause a data loss… So i don’t really have the choice.
I rooted my OnePlus phone using the Magisk app for the purpose of using a module to change the recents provider. In my case I copied the boot image to user storage using a shell command from adb root rather than trying to pull it out of the /e/os ROM zip file. Then I applied it from within the Magisk app. It was a fairly painless process and nothing was deleted.