What EXACTLY do I need to do to format and setup an install USB for the Full Rom firmware?

I’m not quite sure on what I need to do. I have done everything I can to ensure that the USB is proper for booting, but the device still will not recognize it.
I am attempting to chrultra the Samsung Chromebook 4. No USB storage devices I have attempted to use have worked. I may be able to use a Micro SD or SD but that is not ideal.
So far, the OS’s and things I have tried are:
Tiny11 22H2, tried installing in MBR, GPT, will not install. Using Rufus as my program to flash said USB.
Linux Mint and LMDE: same things as Windows, plus I gave BalenaEtcher a try.

Kind of lost and I’m gonna be kinda bummed out if its completely bricked now.

Any help appreciated, thanks!

what does this mean? That the USB doesn’t show up in the Boot Menu? The FAQ on my site addresses that, but more often that not it’s an issue with handshaking between edk2 and the USB device itself.

NOTHING TO DO WITH HOW YOU WROTE THE DATA ON IT.

The short answer is to use a different USB stick and write the USB properly (not MBR)

Ah. I apologize. I have since fixed the problem on my own. Used the SD Card slot instead and it worked.
Ended up using Full FW for a while, worked great, thank you for your work on this

Ended up trying to use Legacy_RW so I could mess with ChromeOS and I guess it isn’t very happy about not having NVRam, so I’m kinda bootlooped
That being said, I don’t need anymore support, I just wanted to let you know my issue is resolved, I will be ordering a SusyQCable for it to flash the stock firmware.

Thanks,
Sasha

if you went back to stock and flashed RW_LEGACY, there is no need to reflash anything. Boot your device to recovery mode and perform a USB recovery. Then boot ChromeOS and reset any boot flags you may have set

So, funny story, I have done that. ChromeOS just won’t boot. Did Tab on the initial “Chrome OS is missing or damaged.” screen, and it is complaining about NVRAM and TPM.
The way I flashed the firmware was I went from Full to Stock to RW_Legacy. My guess is ChromeOS updated and now that’s part of the process to start it, in my non-expert opinion.
I’m gonna try and recover the oldest ChromeOS version for Bluebird if it will let me.

Went ahead and did an older version, still doesn’t wanna boot. Same exact error. Gonna even see if Thorium or Chromium will boot, but it’s looking bleak.
I’ll let you know how it goes.

Just figured this should be on everyone’s radar.

do you have a ch341a USB flasher? that’s the easiest way to resolve this

Not on hand. Was planning on getting a dinky lil SusieQ Cable adapter thingy, but I’m guessing that’s just not gonna work? I can get the ch341a no problem if so, just gonna take me a couple of weeks.

either one should work here

Cool, when I get one, I’ll have a look at the guides and stuff. I know your probably a busy person and stuff so I don’t wanna bother you lol

Sorry for my weird ass hardware doing weird ass shit
Google and Samsung be doing they thing sometimes