I can confirm I succesfully installed and booted this ROM on my T230NU (codename 'degas').
It took a few retries (1st issue: Odin was not transfering correctly, 2nd issue: ROM was not booting properly) before I managed to get passed the Android boot splashscreens , so here are the steps I took:
- install AIDA64 or CPU-Z (or equivalent) to confirm your device is compatible (mine is a T230NU)
- free some space on the internal storage. You need at least 1GB to upload the ROM archive, and the installation process may require more. Personally I had 2GB available.
- download the most recent ROM (cm-11-20181216-UNOFFICIAL-degaswifi.zip) from secretwork98's link above.
- upload cm-11-20181216-UNOFFICIAL-degaswifi.zip onto the tab storage, for example via the traditional USB access (MTP).
- install a recovery tool (which lets you backup your system, wipe RAM/storage, install a ROM, etc), I chose TWRM (https://eu.dl.twrp.me/degas/):
- install Odin v3.09 (I think I got transfer errors when trying to use later version v3.14.1)
- download the TWRM package which matches the T320 : TWRP 3.5.0_9-0-degas.img.tar
- boot your T230 into download mode (maintain menu-button + volume-DOWN + power-on, until the device boots then displays a warning screen, then confirm with the volume-up button). You reach a 'download in progress' screen.
- connect your T230 to your computer with a proper, fully functional, USB cable.
- open the Odin GUI, click on the "AP" (=APplication) button and select file TWRP 3.5.0_9-0-degas.img.tar
- untick the 'auto-reboot' option to block the tablet from rebooting after transfer, which may cause the factory bootcode to be restored and TWRM to be overwritten.
- click 'START'. In a few seconds, Odin should confirm that it can access the T320, and then install the TWRM application in less than a minute. If Odin cannot properly communicate or write to the device, the GUI buttons will be all greyed out. Just wait for 60 sec to reach the execution timeout, and Odin will cancel execution properly. Waiting for timeout is better than to kill the Odin process and risk bricking your tablet.
- If Odin completes succesfully, then you are done installing TWRM. Congrats!
- please boot the T230 into recovery mode (maintain menu-button + volume-DOWN + power-on, until the device boots). You should reach the TWRM menu.
- create a back-up of the original system (I skipped this step, may be unwise)
- go in to the WIPE menu, and click on advanced wipe : select Dalvik/cache/system/data and confirm the wipe. If you wiped the storage by mistake, you may have deleted the ROM you just uploaded on step 4. To reupload the ROM, you may have to use the 'adb' tool if you cannot use mount the tablet via MTP protocol.
- go back to TWRM home menu, then click "INSTALL". Select the file cm-11-20181216-UNOFFICIAL-degaswifi.zip, and click "Install Image" (don't try to enable the ZIP signature check, or installation will simply error out). TWRM installs the ROM to the tablet storage.
- Reboot and enjoy!
In my first and unsuccesful attempt, I failed to wipe the dalvik memory of step 8. It did not brick the device but it caused the ROM to loop forever on the Android animation (on 1st boot, the expected sequence is : samsung T230 splash screen, then Cyanogen animation, then "Android with some light reflections" animation, then you reach Android's initial configuration pages).
To address the endless bootloop:
- I forced the device to power off (power button during 5-10 secs)
- rebooted to recovery mode (volume-up + menu-button + power) to open TWRM
- performed the step8 correctly, and rebooted
- the following reboot completed succesfully.
MAIN ISSUE:
- Google keeps locking the associated Google account, and notifying that there were some suspicious activity on the google account associated to the tablet. Is it frequent? Luckily, I created an account with use limited to this tablet.
found bugs:
- the default web browser (bottom-right icon of main screen) is crashing immediatly. But I can use Chrome 81 without a trouble. Mozilla does not provide Firefox packages thru the appstore.
- some other apps from the marketplace can be successfully installed from the marketplace, but crashes on execution. I guess that is because neither the app developer nor Google cares to validate the application release on KitKat.