Albert, If X would not launch then you would normally end up in a 'terminal' console. If it is tty type then problems like yours are unlikely. But many laptops get configured to use a framebuffer console, for better fonts and colors. Then there could be a machine specific framebuffer module issue.
I don't know if that's still valid but back in the days one could append a 'nofb' kernelparemeter to the grub (bootloader) menu entry. There were several other parameters achieving the same result, like 'nomodeset' or 'vga=0'. https://wiki.archlinux.org/title/Linux_console If you can access the grub boot menu (where you also chose between default boot or advanced, like rescue mode) then enter the grub internal editor with an escape key, i think it was 'e' - but better RTFM. https://wiki.debian.org/Grub If a new kernel parameter solves the issue then you can make the setting permanent by editing the file /etc/default/grub (for Debian; which in turn will be applied to the /etc/grub.d/xx_linux file) to contain this kernelparameter. You need to run the command (sudo) update-grub to activate it. Another thing that might be worth trying is to switch to a tty console with Ctrl+Alt+F1 then back to the X screen with Ctrl+Alt+F7. There were reports that the screen was reinitialized properly just by that. (or just switch with repeated Alt+Arrow-left until X is reached. Which from tty1 should be just the next one to the 'left'.)
