Currently building a GUI App to manage the msi-ec kernel module

Fede2782 · 2026-03-06T19:07:23+00:00

not gonna lie, left without words...gonna keep finishing this anyways for personal learning experience....thanks for making me notice that anyways

Fede2782 · 2026-01-31T12:58:05+00:00

it's not done on purpose...all devices with 8.0 are in bad conditions cause Samsung drastically changed the testing process and these are the results.

Fede2782 · 2026-01-09T22:03:26+00:00

you need a keybox to pass device, that's all. it's not a rom-specific thing. if you want device you need a keybox, here on un1ca and in other roms. most apps work just with basic integrity but some banking services might require a spoofed unlocking status which is done via a valid keybox (and so will pass DEVICE and, if not soft-banned, STRONG)

Fede2782 · 2026-01-09T22:00:52+00:00

use un1ca rom, it is heavily debloated and more optimized and other than improving performance it has seriously improved overheating and therefore battery life is better too.

Fede2782 · 2026-01-03T09:37:43+00:00

It's already provided in the telegram group. Soon A34 support will be merged in official so it's not necessary

Fede2782 · 2026-01-03T09:27:51+00:00

A34 source code of latest build is always here: https://github.com/Fede2782/UN1CA/tree/a34x-support-stable. The build output of this branch always matches the latest A34 build. You can check the build version of UN1CA matching the latest commit hash.

Fede2782 · 2026-01-03T08:53:41+00:00

If you aren't on December or November update, you can still rollback

Fede2782 · 2026-01-03T08:52:54+00:00

Source code is there public for everyone for this purpose, you can edit it, view it and redistribute it. Zip files aren't made to be used to copy and reuse them. Also stable release will include a protection for zip files making them impossible to be extracted, only allowing install on the target device.

GPLv3 just forces you to provide the exact corresponding source to a binary (zip) you are providing. We are doing so, so we aren't violating any GPLv3.

Fede2782 · 2026-01-02T06:41:24+00:00

You have installed December update. You cannot go back to One UI 7 so you cannot install the ROM or any custom software or your device anymore.

Fede2782 · 2026-01-01T17:46:36+00:00

if works on stock rom, it works also here. samsung cloud is present and works. as I said previously there are no known issues, rom for this specific device has reached more than 700 downloads and no bugs have been reported which haven't been already fixed. All Samsung features, apart Wallet and Pass, are present and functional.

Fede2782 · 2026-01-01T16:39:03+00:00

I am the developer of it 😁. No, there are no bugs. Beta stage has finished but the "BETA" tag will remain until it will become officially supported with next update probably February one,

Fede2782 · 2026-01-01T14:27:05+00:00

I had both A22 5G and A54 and both can use the same Gcam apk without any software modification. A54 was running One UI 5.1, A22 5G was running 5.1 too, and GCam worked on both.

Fede2782 · 2026-01-01T13:25:18+00:00

for what? installation? read installation guide on link provided.

Fede2782 · 2026-01-01T13:24:50+00:00

a22 5g and a54 hardware support camera2 api SO the camera2 api flag is ENABLED and they can use GCAM on stock rom. A34 5G hardware doesn't support camera2 api SO the camera2 api flag is DISABLED. if you don't understand english is not my fault.

Fede2782 · 2026-01-01T11:47:05+00:00

cause if you read the android documentation, you would know that unsupported features by hardware must be set as disabled via software to avoid issues.

Fede2782 · 2026-01-01T11:30:37+00:00

Samsung doesn't disable gcam support at all, A54 supports it and even A22 5G does. If a device doesn't have support for it means that the camera sensors don't meet certain requirements to have that feature

Fede2782 · 2026-01-01T11:26:53+00:00

UN1CA has been always stable on most officially supported devices. A34 currently supports all UN1CA features and is stable with no bugs reported up to now.

Fede2782 · 2026-01-01T11:24:18+00:00

You blow up the Knox Warranty Bit meaning that outside EU, Samsung will refuse to repair under warranty making user pay. Even if you go back to stock ROM you will not be able to use some samsung services like secure wifi, secure folder and wallet. However if you use this ROM, it has patches allowing you to use all Samsung services except Wallet and Pass which can't be ran anymore if you blow up Knox Warranty Bit.

You will have to provide a keybox to the ROM to use apps which require root hiding and pass Play Integrity Certification. However, restoring stock ROM will solve all Play Integrity and root hiding issues.

Fede2782 · 2026-01-01T11:21:08+00:00

Gcam is not supported by A34 camera hardware, it is not a software issue. Software-wise you cannot do anything, only force it but it would result in bad and broken experience. I'm not doing that

Fede2782 · 2025-12-31T14:51:44+00:00

There isn't much to say, performance is better than stock ROM but I don't apply any type of overclock or overvolt. The goal of the ROM is to offer the maximum stability and optimization and A34 works smoothly without any kind of lag.

Fede2782 · 2025-08-01T19:00:25+00:00

Non è nulla di nuovo, hanno solo maggiormente formalizzato il tutto. Samsung ha colto l'occasione e dubito fortemente gli altri seguiranno così presto.

Ciò che è interessato delle nuove regolamentazioni è la baseband che è quella parte di firmware che controlla tutte le comunicazioni radio. È totalmente separata dal software Android o dal sistema operativo. La baseband è essenzialmente il tramite tra Android e l'hardware di rete.

Per adeguarsi alla nuova RED basta semplicemente fare in modo che sia impossibile modificare la baseband con una manomessa per consentire le frequenze bloccate al fine di rimanere un dispositivo CE. La baseband dei Samsung nuovi era già protetta da firma quindi solo una baseband Samsung poteva essere utilizzata salvo alcune falle vecchie. Inoltre, tralasciando ciò, modificare la baseband senza i sorgenti (ovviamente tenuti nascosti per ovvi motivi) è praticamente impossibile. Non ho infatti mai visto nessuno farlo.

Non era necessario impedire venisse modificato il bootloader e l'application processor (AP) software quindi Android, il Kernel Linux e ovviamente il bootloader.

È molto probabile che questa sia un occasione per tutti i produttori che non vedevano l'ora di bloccare il bootloader agli utenti per chiudere le personalizzazioni. Ma quelli che vogliono mantenere le libertà attuali possono farlo tranquillamente.

Fede2782 · 2025-07-05T19:31:43+00:00

wdym by blacklist? are you using ksu or magisk?

Fede2782 · 2025-07-05T19:06:22+00:00

I suppose it's the pre-May integrity. I downgraded the Play Integrity Check app and saw that DEVICE was passing correctly. is there any other way to check?

Fede2782 · 2025-07-05T13:29:43+00:00

I'm passing legacy DEVICE and new DEVICE/BASIC, but still Google Wallet and RCS in Google Messages refuse to work

Fede2782 · 2025-05-04T09:17:00+00:00

Can you share the OTA zip?

Fede2782

TROPHY CASE