emoose

> What files do we need to edit, and I assume it's just a standard hex editor that's required? Just the default.xex really, decrypt/decompress it using `xextool -eu -cu default.xex`...

@hardeejr: as @Stealthii said the addresses in my post are for the in-memory XEX, for modifying the XEX itself you can just search for the bytes I'd given (should only...

Can now read update segments properly, making sense of them is a different matter though...

Looks like hash blocks have a SequenceNumber at 0xFF0, seems xvdd compares this number to the next hash blocks SequenceNumber (0x1FF0), with the highest one being treated as the actual...

Hmm maybe, I think that 0xFF0 number only gets set for resiliency-flagged images though, but then again IIRC I did see some 0xFF0 / 0x1FF0 offsets being checked during crypto...

Extracted definitions from xvdutil, now xvdtool can read this block but haven't implemented writing yet, so leaving this issue open for now.

Well #20 adds new mutable data, but atm there's no way for us to edit existing data and then write out the edited data... should probably leave this open till...

Only having names like loc_/sub_ is usually the norm when reversing a file without symbols, I'd guess in your case with PC/Switch there could be symbol names included somewhere (PDB...

Just pushed a new release which hopefully fixes this, sorry for the delay, took me a while to figure out what the problem was >.< If you get a chance...

@Bisonfan95 ah sorry about that, the "install drivers.bat" file should have taken care of that automatically, not sure why it didn't... though there was an error with the wdi-simple file...