System after install empty

[NigrumTredecim]

the installer fails flashing in download mode as my drivers are setup for odin so i manually packed "%appdata%\ubports\s3ve3g\firmware\halium-unlocked-recovery_s3ve3g.img" into an odin tar as boot.img and recovery.img as this is where heimdall would flash that image according to that error, i flashed it then clicked ignore and proceded with the install

then it asks to unplug the phone and let it reboot to a screen with little red text which i did, then the install proceeded normally and finished

the the phone boots into recovery mode and loaded for a few minutes before putting me into a normal recovery screen,
where i pressed reboot to system

afterwards i landed on the same bootscreen with the little red text where i let it sit for a good 15 minutes after that i got impatient and connected adb and found out /system is empty

so where did i go wrong and are there any manual install instructions
as the auto installer dies to the mess of drivers on my pc

[MrT10001]

@nigrumtredecim you need to use Linux , preferably Ubuntu (works for me) and install Heimdall (open source Samsung drivers). You also need to use the installer. It works now every time this way. If you have no access to a Linux machine, run Linux in a windows virtual machine.

[NigrumTredecim]

wtf am i doing wrong here,
flashed stock with odin (reformat and nand erase all ticked to avoid any weirdness)
the used the ubports installer .deb package in a kde debian live iso (apt --fix-missing has also been run)
and i still have the exact same behavior
so installer finishes the phone reboots into recovery and i press "reboot to system" wait for 15 mins, go into adb check /system and its empty/not mounted

[MrT10001]

@nigrumtredecim I would use Ubuntu in a VM and not a live environment. Install Heimdall drivers and the UT installer. I use VMware for this and it works. Also be patient, the device may pause for a while at the Samsung splash screen.

[NigrumTredecim]

@mrt10001 thats why i checked system with adb,
it also says halion 5 so that means its based of android 5 but there is no android 5 stock rom for this device does this mean i need to use lineage/cm as a base and not stock rom?

update: it now shows a loading screen with a jumping orange dot
fixed by changing my csc from dtb to dtm and back to dtb dont know how the f that worked but it did (probably also other stuff involved)

and it just booted up

thx for your help