Good, now you have shown what is really happening, and it is serious.
The pool zroot imports, but the datasets inside it (like zroot/ROOT/default) do not exist anymore.
This is why you cannot mount anything.
You are importing an "empty" pool structure, the vdev is there, but no filesystems, no datasets.
This situation is consistent with massive internal destruction of the ZFS filesystem hierarchy, even though the pool is readable, the internal object set is lost or broken.
Summary of your situation:
zpool import shows zroot ONLINE.
zpool list shows almost zero ALLOC (only 508K allocated out of 144G).
zfs list would show no datasets if you try it. (sudo zfs list)
zfs mount fails because no dataset zroot/ROOT/default exists.
zdb -l /dev/gptid/924f1166-7c66-11ef-83b7-001d7dc7be43 shows the uberblock, but it points to no datasets.
What caused this?
Most likely:
The ZFS MOS (Meta Object Set) or dataset tree was wiped or corrupted.
Something zeroed or damaged key metadata.
The pool header (labels) survived, but the internal filesystem structures did not.
