Recently I downloaded an unofficial version of e/os, I don’t think it matters but it’s 3.2 version. My device is a Samsung device, Galaxy M12, with Exynos. And if I am not wrong looking inside of the zip and the logs, one of the first steps are to resize partitions inside of the super partition, by creating a group of a defined size. And I can’t install the os because the group size is too small, and the last partition don’t fit. So I have a question, can I just edit the file inside of the zip and make the group size bigger? And won’t this break my device? Usually I just mess around knowing that I can just flash stock and everything will be fine, but if I am right the reflash don’t fix partitions.
Do the devs give any indication of how or why the sizing might be problematic, did you check for instance if it might have worked on an earlier Android version but fails now?
@aibd The consequences are just if I will have the e/os or I will not I guess. So either I accept them or not. It’s not something I do out of nowhere, it’s part of the update script, if I didn’t had to do that I wouldn’t.
No, I never really needed that, I think they are just the stock ones. Since I know it have a super partition then it have the dynamic partition I guess. So is it safe to just increase the group size in the zip to get this working? And will it be enough to do this step? By this I mean will I have to also have to decrease the size of for example data partition or something else manually?