[Howto] install magisk and hide that OS have been modified

[piero]

Magisk installation details depends on your device type

.

Follow OFFICIAL Magisk Installation instructions

.

Magisk configuration details

.

Open Magisk settings

Hide the Magisk app

Name the app of your choice and click OK

Create shortcut when asked

Open Magisk settings again and enable Zygisk. Do not enable Enforce DenyList

Choose the apps you would like to hide from detection

Reboot to take effect.

This settings usually only work with basic detections. Before we go further, try the apps you want to use, see if it detect root or doing some strange fake bugs like connection error. If not, and you can use the apps perfectly, you do not need to hide more

If the apps are still detecting it, you need to install some modules to hide even more

You need the following modules:

• Shamiko: Releases · LSPosed/LSPosed.github.io
• SafetyNet fix: Releases · kdrag0n/safetynet-fix (Works only for REAL devices with hardware attestation)

How to install modules:

Go to modules tab and select Install from storage

.

.

[NoNeed]

Hi, thanks for the summary and tutorial, but I have two questions:

• Why not enable “Enforce DenyList”? I think without this option, marking apps in “Configure DenyList” doesnt do anything (Shamiko is of course a special case, since it requires DenyList deactivated, but uses the List to select which apps to blacklist)

• I think you need something like MagiskHide Props Config to even be able to use the SafetyNet Fix on rooted /e/ phones, or?

[piero]

For Samsung not using TWRP but “recovery-e”, that can only flash “.ZIP” files, you need to use “Heimdall” (linux/macos) to flash “.IMG” files or “Odin” (windows) to flash “.TAR” files

[HOWTO] Install magisk with heimdall

Following the great tutorial on magisk github trying to root a samsung phone, you will face the problem of samsung phones not being detected by fastboot. Fastboot is the recommended method by magisk developers, but fastboot does not work with samsung devices. On a standard e/os/ installation interact with the bootloader on samsung phones is only possible using odin or heimdall. Heimdall is multiplatform and open source so in this Howto i will use it. Get the boot.img file from the zip fil…

[purpleleaf]

Tx, i will fix the howto.

[piero]

I used to use magisk (in my case, only with universal safetynet-fix and shamiko modules)

But recently, a simplier solution has been shared to make bank apps working on an /e/OS device, thanks to @saroumane38 : modify 2 lines in the /system/build.prop file

English version in the second part of this post (deepL.translator)

Editer le fichier pour ajouter (ou modifier) ces 2 variables:
ro.debuggable=0
ro.secure=1

@saroumane38

Bonjour
En m’inspirant du lien ci-dessus, j’ai réussi à faire fonctionner l’appli Ma Banque du crédit Agricole sur /e/os 1.8.1-s
Pas besoin de Magisk!
Donc voilà en français la marche à suivre.
1) Dans Paramètres>Système> Options pour développeurs
activer Débogage rooté

2) Depuis l’ordinateur, dans le terminal ou l’invite de commande vérifier que le téléphone est visible avec ADB
adb devices

3) Ensuite passer en root avec adb root

4) Récupération en local du fichier build.prop
adb pull /system/build.prop /home/YOURHOME

5) sous linux, attribuez-vous les droits sur ce fichier sudo chmod 777 build.prop

6) Editer le fichier pour ajouter (ou modifier) ces 2 variables:
ro.debuggable=0
ro.secure=1

7) envoi du fichier modifié au téléphone avec la commande
adb push /home/YOURHOME/build.prop /system/build.prop
là j’ai eu une erreur de type read only. Pour la corriger il faut lancer adb remount

8) modification des droits sur le fichier adb shell chmod 644 /system/build.prop

9) et enfin rebbot avec adb reboot

Le test fait avec RootBeer Sample est maintenant concluant:

.
C’est suffisant pour faire fonctionner l’appli du crédit agricole.

Merci à @piero, @Kuro et @ronnz98 dont les différents posts m’ont bien aidés

English version :

Edit the file to add (or modify) these 2 variables:
ro.debuggable=0
ro.secure=1

@saroumane38

Hello
Using the link above, I managed to get the Ma Banque du crédit Agricole app to work on /e/os 1.8.1-s
No need for Magisk!
So here is the procedure in English.
1) In Settings>System> Developer options
activate Rooted debugging

2) From the computer, in the terminal or command prompt, check that the phone is visible with ADB
adb devices

3) Then switch to root with adb root.

4) Retrieve locally the build.prop file
adb pull /system/build.prop /home/YOURHOME

5) under linux, give yourself the rights on this file sudo chmod 777 build.prop.

6) Edit the file to add (or modify) these 2 variables:
ro.debuggable=0
ro.secure=1

7) Send the modified file to the phone with the command
adb push /home/YOURHOME/build.prop /system/build.prop
there I had an error of type read only. To correct it you have to run adb remount.

8) change the rights on the adb shell chmod 644 /system/build.prop file

9) and finally reboot with adb reboot.

The test done with RootBeer Sample is now conclusive:

.
It’s enough to make the french “credit agricole” app work.

Thanks to @piero, @Kuro and @ronnz98 whose different posts helped me a lot

[Infinity]

Just a question: will this method survive an OTA update? Or need to do it again and again and again?

[piero]

The magisk one don’t survive to an update

[Infinity]

That’s not entirely true. Magisk can very well survive an OTA. The steps for that are:

• download the OTA
• install the OTA but do NOT reboot
• open Magisk app
• go to “Install Magisk” (first one, the program, not the app)
• chose “install in inactive slot”
• reboot

OTA taken, Magisk preserved. Of course, this works only on A/B devices.

But my question actually was, if the trick mentioned above (changing lines under Linux) will survive an OTA.

Reason for that question is… I don’t run Linux, I don’t know Linux. So going to a friend to do this trick once is okay. But not every month.

[piero]

All in linux or android is text files,
You can modify the phone android /system/build.prop file using any text editor even running a windows machine not linux.
Data transfert betwen phone<–>pc are managed by ADB (android debug bridge) installed and running in a terminal/console/command-prompt even on a windows machine.

Good luck.

[Infinity]

Thanks Piero, that I understand. But the question is: does it “survive” an OTA update or does it need to be done again and again after each OTA?

[PraksuQ]

@Infinity

will this method survive an OTA update?

No, you need to do it again.

[piero]

A source for magisk modules

https://themagisk.com/category/magisk-modules/

[Infinity]

I followed the steps in changing the build.prop-file. Unfortunately this did not solve my problem, but later on I discovered the Magisk module of “ez-me” called “Hide UserDebug, Test-Keys and LineageOS”. That did the trick.

But now I have another problem!

Once I wanted to take an OTA to /e/OS V1.16, I got an error message. Of course, that was AFTER I (temporarely) deleted the Magisk module “Hide UserDebug, Test-Keys and LineageOS”. It still gives an error (the OTA installer downloads the update, after download it directly it just says “Error” (nothing else).

Now I’ve put back the ORIGINAL build.prop (of which I kept a copy). Now, this did NOT change anything. OTA does not work. So I am out of ideas. I am on a OnePlus 9 (Lemonade) and this is my daily driver (FOR WORK, so making mistakes or getting loops etc. is NOT an option here). There is no TWRP as far as I consider so I uses the /e/OS recovery.

My question is: can I just SIDELOAD the OTA (I have the file on my PC), and can I JUST LIKE THAT sideload / install it and will everything work? Will that overwrite the “problematic” build.prop?

And if so, is there a way to keep root directly? And do I need to turn off fingerprint unlock and passcodes?

Hope someone can help. I do not wish to stay on an old version. Thank you!

[piero]

@Infinity

My question is: can I just SIDELOAD the OTA (I have the file on my PC), and can I JUST LIKE THAT sideload / install it and will everything work? Will that overwrite the “problematic” build.prop?

Yes, it is the traditionnal way to update… (you will loose Magisk-boot).

[Infinity]

Thank you for your quick reply, Piero. But since I can’t risk a brick, bootloop or screw up… Is there any risk?

I mean, I know HOW TO sideload etc. And I can directly sideload Magisk after flashing. But is there something that can go wrong because of the build.prop that gives this error?