[ROM][EXYNOS] LineageOS 17.1 for S10e|S10|S10+ - v1.4 (UPDATE: 2020-12-17)

[flunkyball]

Hi
[...]
The simplest way to get MicroG enabled seemed to be flashing NanoDroid (22.9.20200910) after switching the Phone to LinageOS. Unfortunately that didn't work for me (that means: signature spoofing didn't get enabled, which is apparently needed for things like push notifications).

As I didn't find any other simple solutions, I decided to try to add the signature spoofing patch myself and build the ROM with it.
These are the steps I took, that resulted in an installable, generally working build (I use Linux unless otherwise noted):
[...]

I got 2 questions:
1. By flashing NanoDroid do you mean that you tried to flash the MicroG components or did you try to use the patcher as well ?
2. Did you try to use SmaliPatcher in order to create a Magisk Module enabling signature spoofing ?

Cheers

 

[Phosphoros]

I got 2 questions:
1. By flashing NanoDroid do you mean that you tried to flash the MicroG components or did you try to use the patcher as well ?
2. Did you try to use SmaliPatcher in order to create a Magisk Module enabling signature spoofing ?

Cheers

Hey flunkyball,

I neither want to use Magisk nor to root my phone (keep it as simple as possible).
So for you questions:
1. I tried to install NanoDroid in system mode via twrp (no Magisk involved). This did not work for me with modpunk's unmodified image (autopatching apparently had no effect though there didn't seem to be an error in the logs)
2. No, I didn't

Hope that helps!
Phosphoros

 

[flunkyball]

Hey flunkyball,

I neither want to use Magisk nor to root my phone (keep it as simple as possible).
So for you questions:
1. I tried to install NanoDroid in system mode via twrp (no Magisk involved). This did not work for me with modpunk's unmodified image (autopatching apparently had no effect though there didn't seem to be an error in the logs)
2. No, I didn't

Hope that helps!
Phosphoros

Thx, this definitely helps though it seems odd that NanoDroid patcher runs through without effect and without errors.
In my case I want to use magisk and I have got very good experiences with smalipatcher but I am searching someone to confirm that this approach will work.

 

[fishnetfancy]

This ia obviously a long thread by now but this has been discussed before. There is a link to a post explaining one method in the FAQ on page one.
Or use the search thread function. But I can confirm that Smali Patcher works fine and I have a Magisk Module with Signature Spoofing installed that way. The rest is easy - you can even install MicroG from F-Droid if you like.

 

[flunkyball]

This ia obviously a long thread by now but this has been discussed before. There is a link to a post explaining one method in the FAQ on page one.
Or use the search thread function. But I can confirm that Smali Patcher works fine and I have a Magisk Module with Signature Spoofing installed that way. The rest is easy - you can even install MicroG from F-Droid if you like.

Thank you for confirming that SmaliPatcher works !

However, the link on the FAQ page regarding Magisk does not lead to a post explaining a method but confirming that it is possible after all. https://forum.xda-developers.com/showpost.php?p=83170253&postcount=660 -> not so much the answer to my question.

Searching the thread I did and as you mentioned, it is a rather long one and "microg" has been discussed several times. Thus the search provides many posts mentioning that someone has it running, wants to have it etc.
In fact after a longer search only your post describes a way of setting up MicroG. So probably your link should me mentioned in the FAQ https://forum.xda-developers.com/showpost.php?p=83436443&postcount=852

 

[flortsch]

For those interested in MicroG without Magisk, this is how I setup MicroG on this rom.

1) Make sure, the rom supports signature spoofing. For this, one usually flashes nanodroid-patcher, but as far as I can remember, nanodroid-patcher never worked for me on this rom and Android version. Although the current Android version should be supported nowadays according to the nanodroid developer, flashing the latest version also fails for me. So I connect my device in recovery mode to my linux PC, and use the commands of this shell script (https://del.dog/hulycobanu.sh, Reddit Link: https://www.reddit.com/r/MicroG/comments/fywiix/signature_spoofing_patcher_for_android_q/) to get the files from the device to the pc via adb, patch the files on the pc, and push the files back to the device via adb. Note: I pick and run the commands from this script manually. Running the whole script at once did not always work for me (often failed at detecting phone connection or right system path).
2) Next, remove the pre-installed UnifiedNlp folder from /system/priv-app that comes with this rom.
3) Reboot the device.
4) Add the MicroG F-Droid repository and install the necessary apps and location providers.
5) Finally, reboot a second time, and open the MicroG settings to tick each option and set up the permissions accordingly.

I am repeating these steps since the last 3 rom updates. Never had any problem, and my banking apps all work fine.

 

[FOLOL2011]

Hello guys,
Do you know how to backup with TWRP as /data is encrypted ?

and also how to remove a Magisk module ?
Navigate to: data -> adb -> modules -> select the module directory and delete
but modules nams are encrypted

 

[guguxfr]

Hello guys,
Do you know how to backup with TWRP as /data is encrypted ?

Er, if you used TWRP from this thread, it'as able to decrypt /data and hence do the backup.

I've done backups / restores a couple of times without problem on my s10e.

 

[FOLOL2011]

Er, if you used TWRP from this thread, it'as able to decrypt /data and hence do the backup.

I've done backups / restores a couple of times without problem on my s10e.

I'm using the modpunk recovery twrp-3.4.0-0-android-10.0-beyond1lte-3.img md5 b4b930916a0f077227315d65dd7292c7
When I'm in TWRP and mounting /data, for example /data/app dir list is all encrypted
When trying to backup /data /system (without micro sd) I have this error :
Can not create /data/media/0/TWRP/0 folder (Required key not available) Failed to make backup folder

 

[FreeRunner2017]

Hi does smali patcher work on this rom with signature spoofing and mock location hiding?

 

[Sheffield Steve]

Did you format the data partition after you installed TWRP?

I'm using the modpunk recovery twrp-3.4.0-0-android-10.0-beyond1lte-3.img md5 b4b930916a0f077227315d65dd7292c7
When I'm in TWRP and mounting /data, for example /data/app dir list is all encrypted
When trying to backup /data /system (without micro sd) I have this error :
Can not create /data/media/0/TWRP/0 folder (Required key not available) Failed to make backup folder

 

[Anghirrim]

Hi @modpunk,

trying to build an LOS based ROM using your github repos (thanks a lot for your work btw).

All went fine for S10 and S10e. But for the S10+, I am facing the issue below:
https://del.dog/alofeethyp.txt

Seems a vendor file is needed, but it's not existing on your Github (did not find in any other github repo).

Could you please help me get through this issue?

Thanks,

Edit: I found it in the vendor partition of your zip. But I guess this is not an elegant method.....

Edit 1: I also noticed that on the builds I've made, my vendor.img are much smaller than in your builds. Is it normal?

Edit 2: Even for beyond2lte, for which before building, I copied the entire vendor content into my build directly under /vendor/samsung/beyond2lte/proprietary/vendor (up to 390Mo). But in my zip, final vendor.new.dat.br is about 17.4M only.

 

[guguxfr]

I'm using the modpunk recovery twrp-3.4.0-0-android-10.0-beyond1lte-3.img md5 b4b930916a0f077227315d65dd7292c7
When I'm in TWRP and mounting /data, for example /data/app dir list is all encrypted
When trying to backup /data /system (without micro sd) I have this error :
Can not create /data/media/0/TWRP/0 folder (Required key not available) Failed to make backup folder

I don't see the exact version in TWRP but from memory I installed that one too.
I too have filenames with strange extensions in /data/app for example. But it seems to me that it comes from the fact that /data is encrypted in FBE mode (File-Based Encryption I guess).

When I launch a backup of /data and /system it first says
"attemting to decrypt FBE for user 0"
Then
"User 0 decrypted successfully"
Then
"Data successfully decrypted"

and it continues with the backup.

What bothers me is that is says too :

"backups of data do not include any files in internal storage such as pictures or downloads"

How come ?

 

[Anghirrim]

What bothers me is that is says too :

"backups of data do not include any files in internal storage such as pictures or downloads"

How come ?

Hi, this is normal.

Your sms, contacts, settings and user apps and their configs are stored in the /data partition.

Your pictures, files, etc... that you can access when you plug your phone using an USB cable are stored in /data/media.

As a factory reset only wipes everything that is in /data, except in /data/media, then TWRP only does a backup of /data, without /data/media.

And that's much better, if you have a phone with 128Gb of storage.... you don't want to save all of this.

 

[Eidluci]

Say my current firmware is dth7 then I flashed 1.1 because its the compatible rom then I decide to update to 1.2, will it bootloop?

 

[guguxfr]

Hi, this is normal.

Your sms, contacts, settings and user apps and their configs are stored in the /data partition.

Your pictures, files, etc... that you can access when you plug your phone using an USB cable are stored in /data/media.

As a factory reset only wipes everything that is in /data, except in /data/media, then TWRP only does a backup of /data, without /data/media.

And that's much better, if you have a phone with 128Gb of storage.... you don't want to save all of this.

Ok, I didn't know, thanks for the infos !

---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------

Say my current firmware is dth7 then I flashed 1.1 because its the compatible rom then I decide to update to 1.2, will it bootloop?

You mean DTI8 ? Somebody has patched that latest firmware and made it available, search the thread. Or you can get the files from Samsung and patch them yourself, from what I've understood.

 

[stm8923]

Flashing firmware bricked the device

I am on linux with heimdall (v 1.4.2). Trying to flash firmware XXS9DTI8 on my S10+ (G975FCKDDBT).

1. I downloaded Firmware for German Devices (DBT) and extracted relevant files.
2. Bootloader is not open.
3. I flashed with heimdall (like FAQ and #727) (with user root)
4. Heimdall does not complain anything. (everything 100%)
5. Reboot show splash screen Galaxy with a colored line with text in the left upper corner of the screen (unreadable)
6. Stopps booting. Device shows a black screen with the text line (like 5.) and a circle with a flash sign), while conneted via USB. Unplugging the USB cable the device switches off. Thats it.

Starting in boot mode works, reflashing does not help.

I have no Odin (Odin in Virtualbox does not connect to S10+) and JOdin does not work (heimdall paramter exception, maybe wrong Version of heimdall).

Any hints?
Thanks

 

[guguxfr]

I am on linux with heimdall (v 1.4.2). Trying to flash firmware XXS9DTI8 on my S10+ (G975FCKDDBT).

1. I downloaded Firmware for German Devices (DBT) and extracted relevant files.
2. Bootloader is not open.
3. I flashed with heimdall (like FAQ and #727) (with user root)
4. Heimdall does not complain anything. (everything 100%)
5. Reboot show splash screen Galaxy with a colored line with text in the left upper corner of the screen (unreadable)
6. Stopps booting. Device shows a black screen with the text line (like 5.) and a circle with a flash sign), while conneted via USB. Unplugging the USB cable the device switches off. Thats it.

Starting in boot mode works, reflashing does not help.

I have no Odin (Odin in Virtualbox does not connect to S10+) and JOdin does not work (heimdall paramter exception, maybe wrong Version of heimdall).

Any hints?
Thanks

I flashed from Linux with heimdall too but I don't understand, aren't you supposed to unlock bootloader etc ... then flash LOS before flashing firmware ?

 

[stm8923]

I flashed from Linux with heimdall too but I don't understand, aren't you supposed to unlock bootloader etc ... then flash LOS before flashing firmware ?

In the installation instruction #3 I read: first check and update firmware to the correct one. So I neither opened the bootloader nor installed los....

 

[angela5246]

Flashing just those few files for a necessary firmware upgrade might not be enough if you come from a stock rom with locked bootloader. Best solution would be now to reflash the whole rom, boot into the phone, unlock the bootloader, and installing LOS as per instructions. As it seems that you're using Linux, Virtualbox is working just fine for flashing the stock rom to a Samsung phone. You need to set up your virtual machine with USB3 support enabled for the guest OS. Then install the Samsung USB drivers. It works, I did it a few times already.