Macbook Pro (2016) can only enter Verbose Mode and no other boot settings

ThyAllMighty wrote:

…

Is there no way I can pull the hard drive in order to put into an external enclosure and plug it in via USB-C to the new laptop?

Other than that there is no hard disk drive here, and no easily-swappable SSD storage, sure. Not Touch Bar models can be swapped, but Touch Bar storage AFAIK cannot. And storage is usually encrypted, regardless. In far fewer words, swapping an HDD or SSD into a sled isn’t a path here.

Target Disk Mode might get you access.

Transfer files between two Mac computers using target disk mode - Apple Support

There are also no backups here, or no recent backups, presumably.

I'm no expert on verbose messages...but this looks like very early ROM boot - possibly the messages related to finding and loading the Preboot Volume, which seems to fail...

That said, RBSDP in the line starting #[EBIFS:RBSDP] usually stands for Remote Boot Server Discovery Protocol, so the boot might have failed a few lines earlier at #[EB.CS.AUVIVU!] Err(0xF) 0x00030000 and tried to automatically look for a netboot server because local booting failed.

Regardless, it doesn't look good - although even letting the battery die and then plugging it in shouldn't damage the system like that, unless something else was already wrong.

of those, the simplest you could invoke is holding Option at Startup, to invoke the startup manager, aka Boot Picker.

This should draw blank gray screen, and over the next several minutes, add an Icon for each potentially-Bootable Volume. (There may be none bootable.)

To get the gray screen, no drives are required to be working. The code that runs this feature is all ROM.

Slightly more complex is Recovery Mode. it unpacks a 2 GB disk image from ROM, then starts up that MacOS Base System to support Utilities, including Disk Utility. Again, no drives are required to be working, but you must be patient.

with Boot drives integrated onto the mainboard, these subtle distinctions are not so valuable as in the past.

Just as MrHoffman suggests, Your Mac likely needs service, and if your mainboard is replaced, your files may not be returned to you.

Given all that does not work here, contact Apple Support.

It would appear this MacBook Pro is headed for a repair, or replacement.

Official Apple Support

Hopefully you have Time Machine or other backups, as the data here may not be recoverable.

And Diagnostics tries to load (slowly) within the minimal functional hardware for testing.

This issue looks vaguely related to wireless networking.

As a long shot: has a TP-Link Wi-Fi or other third-party Wi-Fi driver been loaded here?

Normalized orientation:

Yeah, I was looking at the EB.B.MN Err(0xE) error, which has been tied to Wi-Fi issues, and occasionally to add-on Wi-Fi drivers.

(But then I’ve also spent way too much time wading around in ACPI over the years.)