Are you able to boot again into grub menu,
select Additional Options for Zorin,
choose previous kernel generic version listed,
boot that and test/report back.
You should be able to access the Grub Menu and Recovery Menu - thereby giving access to network and terminal.
Enable networking in Advanced Options for Zorin by choosing a kernel under (Recovery), then arrow key down to Root - drop to prompt and run
No critical issues had occurred while folowing the steps. During the boot, it still showed the same things as my previous screenshot. Still a horizontal cursor blinking at the top left corner of the screen screen.
here is an unusual part that happened. Before the solutions were provided by the others. I attempted to load a repair boot from the USB stick zorin os, but was giving me an UEFI issue with the bios.
I turned off the UEFI only, and then this happened.
i didn't install the boot on my nvme, but it shows there. In fact, I can load my linux there now, BUT I was supposed to load it through the SSD. That's where I'm stuck right now. The Repair boot doesn't exist in the normal boot, either.
in addition to being able to temporarily access it, I am currently stuck at 1024x768 resolution. I am currently remedying that one, as it might have been the cause of the issue...will update soon
I was able to solve the issue. By temporarily booting up Zorin through the NVME (still not sure why that appeared), I decided to follow one of the solutions from @Aravisian from this solution. Did some tinkering first because nvidia-driver-535 and nvidia-driver-545 fixed the resolution, but permanently set the color to warm for some reason. Downgraded it to nvidia-driver-525 and it solved the color issue, and I can boot it up again from the SSD without the previous issue.
In other words: the update that I did to my graphics driver caused a boot-up error, and purge-install it fixed the issue. Thankfully, if it weren't for the NVME boot to Linux, I wouldn't have been able to remedy the situation.
Once you are happy that things are OK, please mark the post that helped you (or your last post that exlained the fix) by clicking on Solution under the post.