Nah, it's not bricked.
There is a hidden menu that you can get to that allows you to turn on IP downloads and set a static IP address, but the easiest way is to just use a USB cable.
The 2nd easiest way is to put an image on an SD card and boot it with the card inserted.
To do that, on the Crimson file menu, choose Save Image, and name it "image.ci3"
When the unit boots up, if it finds a file on the root of the SD card with that exact name and with a newer date than the one it already has in memory, it will load it.
Note that in many cases, the first time you boot with an image file, it will include firmware that is newer and it takes a minute or two to complete. During this process you might see a screen complaining about "VERSION MISMATCH" That happens when the unit already has an image file and you are updating firmware but haven't yet updated the image. Just wait and let it finish and it should load with new firmware (to match your Crimson 3.1 build) and the application will come up and run.
Subsequent power cycles will skip all this (unless you update the image on the SD card) and boot up and run in about 10 seconds.
I always try to leave an image.ci3 file on a memory card installed even on units that aren't doing any logging. It makes replacing it as simple as popping that card into the new hardware and powering it up. If you are logging data, that data will also be present on that memory card and available to trends soon after you power up even if you have to replace the hardware.
There are some cases where the SD card won't be properly recognized by the HMI. Older version required FAT16 format and 2GB max disk size, but it's been my experience that newer versions ... at least the CR series ... will work with larger disk sizes formatted FAT32.
For that reason, I also include in the application a screen that shows the status of the SD card, free percent and a button (with confirmation) to format it. Note that formatting the card from the application will erase any image file that is present on it as well as all the log files so you only want to do that if the disk is corrupted or not recognized due to format.