Encryption and Magisk

21

These are 2 different topics:

  • encryption: see about your recovery being able to access encrypted partitions
  • install magisk: see about boot.img as directed
22

Perhaps you are right, this task can be divided into two different topics as you wrote, this is encryption and installation of Magisk, but in this case I am just interested in whether this is possible or not.

I would like to understand if it is possible to have an encrypted phone with Magisk installed

23

Addition: This method will delete the data and encryption will not work.

Reboot your device into TWRP Recovery.

Go to Wipe menu.

Go to Advance Wipe.

Select Data and go to Repair or Change File System.

Click Repair File System. (If not fix, go to step number 6)

Go to Change File System.

Select Ext2 and swipe to confirm.

Now change back to Ext4 and swipe to confirm.

Now go back and check if your portions can be mount or not from Mount menu.

If not fix, repair your Internal partition. (This may wipe your Internal storage).

OR Unlock your boot loader again

24

If you only need Magisk, ignore the recovery and etc

Focus on Magisk

1 Like
25

Thanks for your advice. I just tried to install the operating system + F-droid apk and Magisk programs and then encrypted it and in the Privacy -> Trust section I see Encryption.

It also works according to its recommendation, when I installed the operating system, encrypted it and then installed Magisk.

Yes, there is a problem when I want to install a ZIP file through Recovery, then I get an error, but for the initial installation everything worked.

I will try to find the answer in other places and write if I succeed.

I don’t understand how it works ))

26

What is your device?

27

Thank you for your reply. I am in contact with the developer, if I have any information I will definitely share it so that other users do not experience problems.

29

Hello everyone. I was told that there is such a project as Lygisk GitHub - programminghoch10/Lygisk: Your Lie in Android, if I understood correctly, then after installing Lygisk and entering Recovery, there will be no password request, but at the same time the data section is protected.
If anyone has used this program, write your feedback

30

Lygisk fixes the needed /data access in addon.d, which fails to reinstall Magisk during OTA if the device does not support FBE decryption in recovery (

For installing Lygisk, just rename the downloaded file to .zip and sideload it. If the Lygisk app doesn’t appear after installation, install the apk manually.

For installing by patching bootimages, use Magisk instead.

you got the same info above… fix your recovery OR use boot image to install magisk

31

thanks for your answer. I don’t understand what you mean, would it be difficult for you to answer this question in more detail. Maybe write commands…

  1. What’s the point of doing a restore if this function is in Lygisk? I don’t need to enter a password and do additional actions.

  2. The most important question that worries me is that it doesn’t matter whether I used Magisk or Lygisk after installing them I can’t install zip files, for example modules for Magisk or something else because I get the error

    failed to mount ‘/data’ (invalid argument)
    unable to recreate /data/media folder
    unable to mount /data/media/twrp/.twrp

32

this is the error

33

I put those files into the same directory but it complains that ‘aidl/android/hardware/boot/MergeStatus.h’ file not found.

34

My guess was correct you can transpile .aidl files to .h and .cpp files
use this command

assuming your cwd is .../bootctl/aidl/android/hardware/boot

aidl --structured --stability=vintf  --include=../../../ --lang=cpp IBootControl.aidl MergeStatus.aidl --out ../../../ --header_out ../../../

aidl command is part of Android build tools.

35

How did you build it? And I guess I need to build aidl?

36

I haven’t built bootctl yet.
I tried.
aidl is part of android sdk you don’t need to build it as F-Droid already trust android sdk as I know.
The issue is it seems there are multiple versions of IBootControl.h as you see here

image
image737×191 40.1 KB

maybe those exist for different versions of android? Idk.

and in the Android.bp file found next to bootctl.cpp (seems like a build file) they link to it

shared_libs: [
        "android.hardware.boot@1.0",
        "android.hardware.boot@1.1",
        "android.hardware.boot@1.2",
        "android.hardware.boot-V1-ndk",
        "libboot_control_client",
        "libhidlbase",
        "libutils",
    ],
37

I guess the best way to build bootctl is the standard way instead of doing build system job yourself.

I found a package in the AUR named aosp-devel maybe it would help.
it would take time though since the AUR builds it from source code.

38

Yep. :person_shrugging: I won’t try that since bootctl is not very useful. Except that Magisk shows and error message it works well.

39

Maybe it would help making Magisk reproducible.

40

It’s far away from reproducible. Magisk recently moved busybox out of the repo. Prebuild Busybox · topjohnwu/Magisk@ef81cda · GitHub Now no one knows which commit they used to build it.

41

Maybe ask the upstream which commit they use.
And get some info about building bootctl.