Swizzy

Video works from XellLaunch, however... reading the NAND doesn't... (MMC coronas) other consoles work just fine... this also means that nothing from the NAND can be used by XeLL, including getting your real MAC Address Well, it improves USB drive support, which is great... it also handles badblocks better....The recompilation i spoke of is only related to Corona video

It doesn't automatically mean you can use any Libxenon homebrew, they need to be re-compiled with the new libxenon toolchain...How to install it? well, read the readme and you shall know... otherwise, wait for an updated xeBuild GUI, J-Runner, AutoGG or whatever, they will all have this

If you dumped before writing (like you should have) just rebuild using the correct key and reflash it using etheir xell (if that still boots) or using hardware flasher like NAND-X or similar Otherwise just use xeBuild GUI with the key you built with to extract kv etc. put them in the data directory (all decrypted variants of them without the name part that says if it's encrypted or decrypted (kv.bin, smc.bin, smc_config.bin)) then just build with the correct key...

A quick update: In order for the CPUKey extraction to actually work you'll need to have Dashlaunch 3.01 or newer installed, any older dashlaunch version is incompatible (cOz added the feature i use with this version) It's beta yes, but the read/write code for the nand has been tested for a very long time, i haven't heard of anyone having any major issues (the issues reported to me has been caused by faulty usb memories, which isn't really related to my tool in the first place)The reason i released it as a beta is because of the new features that haven't been tested for hours... i've done some tests, but not every single possible way... the features that make it a BETA:CPUKey extraction - Not tested a whole lot, but... it should work perfectly fine as it's afaik the same as the function which Team FSD have in F3, and the same that should be in the Dashlaunch installer (which also requires Dashlaunch 3.01 or newer in order to work)Automode - Well, it's for pre-defined commands, it might fail at some point, it shouldn't do that... but... i haven't really tested it out a shitload, just made sure that it runs the command expected...

It'll work with any networking connection you might have, wireless, wired doesn't matter... i'm working together with BlakCat right now to add some security to it so that it's safe to use, most won't even notice it since most of the time the transfer of the NAND goes fine, but... for the times that the transfer for whatever reason fails (say your cable sucks ballz or your wireless connection drops in the middle of the transfer, and comes back up losing data or whatever) Simple 360 NAND Flasher won't write anything (because it'd obviously be a bad thing to write a bad image

Try rebooting your console (turn it off and start it back up again) and make sure to start FSD 3.0.402 before you start any other version of FSD...