I know this is an ES, but it seems they use quite a lot of the 360S design.

Looks like the SMC is still there and i think the displays next to the presenter's thumb are POST monitor (then again ES, so it might be something different).
It looks like there are a few JTAG ports on the board and it does look like the Jaguar SoC is solid enough to prevent the Xenon design failures, though 16 DRAM chips is a bit scary (heat-wise) to begin with (when you consider the chips run at 2133).
Seeing all of this makes you think that MS going for the cheapest possible hardware (DDR3/4Gbit IC, less APU cores than PS4) which is disappointing, especially when you consider that they plan for 5-8 years lifespan and this hardware is not high-end, even by today standards.

Interesting things from security standpoint will be the VM usage to separate XBOX OS from Windows Kernel and the custom Hyper-V.

You want to use XeLive, so you can get online and when they ban your KV, you would just put a new key, is that what you want to achieve? Cause if it is - better quit, no one here is going to help getting JTAG/RGH online. Plus working Xbox is like $100 you can easily get one do not modify it at all and use it online - safe and sound.

Sounds like a 1BL memcmp vuln, but we'll see.

You should REALLY REALLY consider giving it to someone else. XBR is history and by the sounds of it you are trying to directly open the binary file with Windows, instead of giving it as an argument to NandPro. E79 is common in JTAG's with bad wiring or f***ed up FS. Check that the console you have is actually JTAG-able and redo your wiring using transistors (hint hint: BlackAddr).

Get POST reader and get the secondary error code - it may narrow down the list of problems. Also check the STBY_CLK, almost everyone destroy these trying to connect the CPLD

If hardware is involved and high-precision is required, might be something like the Infectus bruteforcer that was released in the early days, im not sure thought, but i doubt we'll see something never seen-before.

Haha cute, like the XLSP/SDK is the problem.

It does look like after the initial XeLive euphoria, every kids from s7 is trying to get online.

Sounds like grounding issue. Keep in mind if HANA gets really hot could've been already burnt.

You hook the network function after the packet is decrypted, save everything, than reverse it.

Decompile them in IDA. There are not only patches, but custom functions too, so its not so simple. If your intend is getting in LIVE, think twice, you'll need a lot more than minimum patches.

Get the drive and KV from another console and you're done. Although if MS have detail info about every console white-listed, you'll get banned eventually.

Why running it, when you can reverse it?

Its a .NET executable - just use Reflector and you'll get a code close to the original. If i remember correctly GOD containers are basically ISO's with appended LIVE package header and split into chunks.

Keep in mind most of the programs are actually meant to write/read files from the table, not recover files without proper index, meta etc.

try FATXplorer sometimes you can recover deleted files with it

If no hardware damage is present, sounds like a KV issue.

You buy a TX product, you ask for support on TX forums.

You don't restore your drive, you flash another drive data to yours, essentially cloning the other drive. While that works, you don't actually restore your drive to its original state. Im not sure what hddhackr backs up, but if its the firmware - every hdd firmware is unique to its drive, based on the plates, P/Q lists etc.

How many first time posters are coming here to try and save the HDD's? You're boned get over it, there are manuals and you should read them before you attempt something.

Every backup is unique and even if someone send a HDDSS backup you won't be able to restore your drive. You've been warned, use it as it is or sell it.