[UNOFFICIAL BUILD] Samsung Galaxy M12 / A12S for /e/OS-S 3.0.x

/e/OS Devices UnOfficial Builds
1

Samsung Galaxy M12 / A12S for /e/OS-S 3.0.x

m12
e-3.0.4-s-20250715-UNOFFICIAL-m12.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-3.0.4-s-20250715-UNOFFICIAL-m12.zip/download

a12S
e-3.0.4-s-20250715-UNOFFICIAL-a12s.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-3.0.4-s-20250715-UNOFFICIAL-a12s.zip/download

Please see sources and install instructions including recovery here:
https://xdaforums.com/t/closed-dead-unofficial-ota-lineageos-19-1-for-samsung-galaxy-m12-f12-m127f-m127g-f127g.4462533/ 129

Unfortunately the development seems to be not continued…

Use it at you own risk!
Please support the developer(s)!

2 Likes
2

sorry , but how it fix ?

rrr
rrr680Ă—1278 133 KB

3

@idea same for me, a person in the older version also had the same issue, and he said it’s about the custom recovery, but we can’t know more because the topic is closed. You tested it on e/os recovery, I tested on twrp (same error), and on adb sideload with signature error. I will try now the older, 2.4 version end edit it to let anyone know

EDIT: same with older version. I will try to look if maybe there is a workaround to adb sideload verification, because then the stock recovery with just adb sideload would work

EDIT2: or I heard magisk can now install zips, I will just reflash my phone to root (because twrp ALWAYS broke my phone even if it worked for everyone else) and try it

EDIT3: I realised that because I am flashing an os, I can’t really use magisk for that, BUT I found a guide to building your own twrp, so it finally should work and I will have a normal twrp

4

@idea @finorest

does LineageOS version works ?
did you follow instructions from there ?

.

but the guy is still active…

5

Please try this builds:

e-3.2-s-20251118-UNOFFICIAL-a12s.zip

e-3.2-s-20251118-UNOFFICIAL-m12.zip

Source:

https://xdaforums.com/t/unofficial-crdroid-8-11-for-samsung-galaxy-m12-m127f-m127g-f127g.4525951/

6

@piero it’s impossible to follow since it’s impossible to get the recovery, the page says something like not found when trying to download anything from this project.

@ronnz98 thanks, I will try it over the weekend, since I am tired with re-flashing and getting the needed apps, and looping it over days, I won’t need these apps this much.

And generally I will try to do everything possible in this time, I will try to build this twrp thing, I already tried but I had no idea that just using a repo thing will cause my PC to lose all of it’s remaining space and while the download it was lagging a lot, and it wasn’t even building yet. And apparently repo can’t restore syncing, so I was just done with that, but I will try to do this again in a few days.

If twrp will fail, I saw an option in stock recovery “apply update from SD card” maybe and I hope it won’t have the signature verification. I guess the new version of e/os is the same, and still will get me the same error as the person up here gets (something with dynamic partitions), and I don’t even hope that it will have working signature thing.

So generally I hope I will build the twrp with success

EDIT: @ronnz98 I don’t really understand what you meant by source, I haven’t found anything related to e/os there, if you meant the recovery then it’s not possible to download too :frowning:

7

you need a “cutom” recovery to install “custom” android OS

Hard job, you already have the “recovery-e”

8

@piero I thought all custom recoveries and similar was just adb sideload but with small differences, good to know.

But where can I find the e recovery for my device? Binary 9, Galaxy M127F. If it exist I hope it would work better than twrp, since all it can do for my device is boot and browse files, sometimes flash, but if I will even touch the data partition the entire device is unbootable (I used with other rooms to reflash recoveries just to use the format /data function with stock recovery), but with e/os it throws the same error as a person up here, so something with dynamic partitions.

10

@piero Wait, I am kind of lost. So firstly, I heard from you I need an e-recovery. In last minutes, I did some research, and apparently if I am not wrong it is based on aosp recovery. And my device is treble supported, so I guess there is a exact same recovery for everything. The twrp wouldn’t work I think, since somewhere else I heard it do something with /data partition, and my twrp can’t accept that (not only /data, but it also fails to mount some other partitions, like /vendor and /odm and 2 more that I forgot [/system?]). Data could be fixed, because if I format /data using stock recovery then twrp randomly starts to work, but about other partitions I don’t know, for example if I remember good, trying to do something with /system manually (with manually and only it, because zips has got access to it), it says something about unsupported emmc file system. So, I kind of guess even the e-os that would be treble compatible for multiple devices has more chances of working than my twrp, but I guess nothing to lose, since I can just reflash.

11

you are right in saying both stock recovery and TWRP wont works

they are very detailled

sorry, i was thinking the photo was your’s.
extract it from ronnz98’s .zip

12

@ronnz98 @piero exact same error. Exactly same as the one thatrrr

rrr680Ă—1278 133 KB person here gave. I used e/os recovery, and 3.2 zip. But I used from sd card. I followed the instructions.

EDIT: I even double wiped data before install, and all of this 2 times just to be sure. Now I am restoring, waiting for more help

EDIT2: If needed, and if this is similar to building twrp I can provide the “I know it works” .img’s, like recovery and other from the AP

1 Like
13

@ronnz98 Hello,

I just have a quick question, will there be a fixed version to this device, since to later install the e/os faster and maybe provide more info I am on root for now, but some of the apps don’t really work with it well, so I don’t really know if it’s worth staying with this for 20 mins saved when installing. Also please don’t think I am trying to make you do this faster, if you will be working on this then take your time. Regards

14

I don’t think so, no developer seems to be currently active for this device. I made an /e/OS build from the sources outlined - I did not test and I do not even know if the ROM works

15

@ronnz98 I tested, as I said up here there is an error with something related to dynamic partitions while installing the zip. So It don’t really can even get into booting. I tried 3 versions, the 3.2.x, 3.0.x, and 2.2.x (?), all of them giving the exact same error. Also, when looking at your previous version post for this device, it seems like another person had the exact same issue, and said it was just an issue with the custom recovery (person used twrp in the screenshot). I used both twrp and your recovery.img, with both of them giving the exact same error. Adb sideload need signature verification. If you have any ideas thanks in advance

16

hmm. best read here:

Unfortunately the ROM and recovery of the original thread is not available anymore.

You can try any of the recoveries that are here:

https://xdaforums.com/f/samsung-galaxy-m12.12181/?prefix_id=33

https://xdaforums.com/f/samsung-galaxy-a12.12125/?prefix_id=33

17

Thanks a lot, I will test them tomorrow and inform whatever works for anyone still interested and using in this device if they exist, thanks again

2 Likes
18

it look like “classic” instructions , excepting this part :

If you have ever used TWRP, we STRONGLY RECOMMEND YOU TO REFLASH STOCK (AP, BL, CP, CSC) USING ODIN SINCE WE’VE HEARD THAT IT CAUSED A LOT OF WEIRD ISSUES SUCH AS “Try again in 1425 minutes” AND NO LONGER BEING ABLE TO SET A PIN ON STOCK AND LINEAGE, just to make sure nothing can go wrong when using lineage!

19

@piero Good to know, I remember this line but for some reason I didn’t really process the word “ever”, thanks a lot, I will try with complete reflash

20

@piero @ronnz98 I’ve spend hours now, trying everything, as my last piece of hope I tried to fix it the same way as I got the e-recovery, so I got all of the .img and .img.lz4 files from the zip, compressed to .tar and flashed, I felt like it was going to work because it took it a longer time to flash zip, but still error at assert update dynamic partitions. BUT in the middle of writing this I am pretty sure I got an idea that would fix your zip, but I am asking you first so I wont break my phone, BUT I AM 99% SURE THIS WILL FIX. So I looked around your zip, there is one file, I think it was that dynamic_partitions_op_list, and there was a thing with adding samsung group and then adding and making partitions bigger. And based by the logs, I think the size of the group is bad, and too small. Here are the logs:

[liblp] Partition system will resize from 0 bytes to 2769661952 bytes

[liblp] Partition vendor will resize from from 0 bytes to 267796480 bytes

; propably some more resizes but I cant scrool into them, so part of what I can see

will resize from 0 bytes to 2058285056 bytes

[liblp] Partition odm will resize from 0 bytes to 925696 bytes

[liblp] Partition system_ext is part of group samsung_dynamic_partitions which does not have enough space free (1638584320 requested, 5096669184 used out of 6014631936)

[liblp] Failed to resize partition system_ext to size 1638584320

And then what is in the console, not hidden in the logs, assert failed.

I dont know, this os can take whatever even from my /data, as long as it will work, I will be waiting for more help with hope that this will work

Partition setup during installation
21

@ronnz98 please look into this when you will have time, thanks in advance