you will find tens of threads about that missing pkg and correspondent solution.

In year 2015, however you should NOT use a discontinued, never properly finished tool, particularly with new operating systems like 8/8.1 and 10.

The missing package error however is a simple software error that prevents XBOOT to actually run, it is not possible that it is connected to the issue you describe, i.e. it is not possible that it has locked the USB thingy.

As well, though your attempts with diskpart or gparted make little sense they cannot possibly have locked anything.

It is more likely that it is a coincidence something (already defective) in the USB stick got triggered by the steps you took.

If - by any chance - you bought that USB stick from - say - e-bay and got it for a very convenient price, it is likely that it is a "fake", a device that only apparently has the capacity on the sticker and that can happen to be "locked" when the real capacity (usually 8 Gb or less) is filled.

Or it is well possible that it is an "original" that just broke (but it is not the fault of Xboot, gparted or diskpart).

In some cases (it greatly depends on make of the controller chip and model) it is possible to "reset" the device, but not always and documentation on this is very scarce.

In any case the first thing is to identify EXACTLY the device.

You need to run at the very least two (better if three) tools to attempt identify the device and post results.

Several years I had a similiar issue with a Sandisk Cruzer USB that I had bought only a month before. But Gparted couldnt format it, diskpart said it eas write-protected. Zerofilling the dtive worked but it still couldnt be formatted. This all happened afterI had used SARDU to create a multiboot USB. I was never able to make it uduable again even after a month of trying different things. In all likelihood your drive is probably bricked forever.