Alright guys here is the first version of the USB key injector.
http://www48.zippyshare.com/v/AFBviDgi/file.html
How it works?
Put a seeprom_inject.bin (a copy of your dumped seeprom.bin file) with the modified USB seed at offset 0x0B0 of the file to the root of your sd card. Run the program from HBL. The application will inject the data and dump a new fresh seeprom.bin to your sd card which then should have the new seed in it.
The application does explicitly not inject the full seeprom.bin to avoid bricks through wrong values for boot parameter and such. Also only bytes 0xB4-0xC0 are injected. The first 4 bytes of the seed are always the console ID and cannot and should not be replaced. So the application automatically limits the injection range to offsets 0xB4-0xC0.
I tried it out and injected zeroes into the USB seed. My USB drive was not recognized anymore. Then I injected back my original seed and it is recognized again.
The fact that the first 4 bytes of the seed are the console ID makes the seed not changeable to another consoles seed. Thus making usb drive key bound to a console. This could probably be worked around if we patch ios crypto at the correct position to use another key on the fly. Since we don't have that yet the only way to transfer an USB drive to another console is to decrypt the full drive using the combination of OTP usb key and seeprom usb seed and re-encrypt the drive with the key combintation results from another console.
This should be safe and not brick anything as only the usb seed is injected into the eeprom. You can inject whatever you like into that seed part. It only affects the USB drive being mountable or not. But you need to be aware that the functions used are really low level (I don't think you can go lower than that on the Wii U) and I take no responsibility if you manage to brick somehow with this.
http://www48.zippyshare.com/v/AFBviDgi/file.html
How it works?
Put a seeprom_inject.bin (a copy of your dumped seeprom.bin file) with the modified USB seed at offset 0x0B0 of the file to the root of your sd card. Run the program from HBL. The application will inject the data and dump a new fresh seeprom.bin to your sd card which then should have the new seed in it.
The application does explicitly not inject the full seeprom.bin to avoid bricks through wrong values for boot parameter and such. Also only bytes 0xB4-0xC0 are injected. The first 4 bytes of the seed are always the console ID and cannot and should not be replaced. So the application automatically limits the injection range to offsets 0xB4-0xC0.
I tried it out and injected zeroes into the USB seed. My USB drive was not recognized anymore. Then I injected back my original seed and it is recognized again.
The fact that the first 4 bytes of the seed are the console ID makes the seed not changeable to another consoles seed. Thus making usb drive key bound to a console. This could probably be worked around if we patch ios crypto at the correct position to use another key on the fly. Since we don't have that yet the only way to transfer an USB drive to another console is to decrypt the full drive using the combination of OTP usb key and seeprom usb seed and re-encrypt the drive with the key combintation results from another console.
This should be safe and not brick anything as only the usb seed is injected into the eeprom. You can inject whatever you like into that seed part. It only affects the USB drive being mountable or not. But you need to be aware that the functions used are really low level (I don't think you can go lower than that on the Wii U) and I take no responsibility if you manage to brick somehow with this.