No. I always insert the SIM only after the system has started successfully.
In your photo of your S9+, the error message gives an important hint: device 14 binary 13.
This means that the stock Android ROM you want to flash has a binary 13, while the S9+ has a binary 14. Samsung usually does not allow you to flash to a lower binary than the one present in your device. At the very beginning I had asked about the bootloader version, remember?
My idea now is to flash the latest January 2021 version of stock Android 10 TEL-G965FXXSEFUA1. Please wait a few minutes …
Combined correctly. Then installed with the /e/asy installer /e/ OS 'O’reo ‘stable’. Since then, the same stock Android version can not be installed completely.
How do you explain the difference of the binaries: Device 14 - Binary 13 (Android 10)?
Please scroll up a bit more and get a comprehensive picture - and please let us know your assessment.
Haha… I get it. But for me, I actually paid the $3 so I didn’t have to install more WIN software Once I have this phone sorted (very excited about S9+ /eOS) I am then looking at solutions to replace my MacBook Pro (MBP) as I am soooo over the Apple / Google spy-ring The Samsung S9+ hardware seemed to me to be a 9/10 for quality, similar to the iPhone hardware… but to replace the MBP, I dont know of a good solution… quality hardware that runs Ubuntu or Tails or Qubes… hmmm…
What is your “rig” ? (that’s just me trying to sound cool)
Then it locked up my MacBookPro WIN 10 and it auto-restarted the Mac… BUT the phone looks good… its booting in what looks like A10… waiting for me to run through the set up… country select etc.
ok to do that… ?
Once I have this phone sorted (very excited about S9+ /eOS) I am then looking at solutions to replace my MacBook Pro (MBP) as I am soooo over the Apple / Google spy-ring 
The Samsung S9+ hardware seemed to me to be a 9/10 for quality, similar to the iPhone hardware… but to replace the MBP, I dont know of a good solution… quality hardware that runs Ubuntu or Tails or Qubes… hmmm…