I used a Verbatim USB to install Ubuntu (into another pen drive).

First I installed the liveCD into the USB, then plugged the usb and started the installation process.
During the installation it either froze or gave me an error (I believe it was something about a corruption in the liveUSB), so I aborted it.

After this problem, from a working ubuntu set up, from the program Disks I formatted and tried to remove the MBR from the USB which I used to try to install Ubuntu.

It took a long time (20+ mins for a 32G pen drive, with fast format) and at the end it showed an error (which I don't remember. I read it and it was fairly cryptic. All of this happened more than a week ago and I couldn't take the time to investigate it further then).

After the error, the USB has been bricked. It does not show up in Disks and Windows doesn't recognize it as well.

This is the output

$ sudo lsusb
Bus 002 Device 004: ID 25a7:2433  
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 064e:c21c Suyin Corp. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Notice that buss 02 device 04 is empty. Might it be the device I'm having problems with?
Is there a way to zero out the USB and "unbrick" it?
I really can not see how it was possible to brick a USB while formatting it, I've been installing my OSes in varius configurations for years, and while it might happen to lose data, it never happened to brick a device.

Any helpful input is most appreciated!

EDIT

This output is produced when running the command 5 seconds after plugging the USB.

$  dmesg | tail -n 25
[47513.393004] wlp3s0: authenticate with bc:f6:85:f2:b1:2f
[47513.417898] wlp3s0: send auth to bc:f6:85:f2:b1:2f (try 1/3)
[47513.419896] wlp3s0: authenticated
[47513.423604] wlp3s0: associate with bc:f6:85:f2:b1:2f (try 1/3)
[47513.428817] wlp3s0: RX AssocResp from bc:f6:85:f2:b1:2f (capab=0x431 status=0 aid=1)
[47513.428935] wlp3s0: associated
[47513.428976] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[77882.517081] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[77882.541803] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced.
[78137.396784] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[78137.421424] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced.
[78179.021282] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[78179.046081] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced.
[81115.174023] usb 2-1.2: USB disconnect, device number 3
[81118.871258] usb 2-1.4: new full-speed USB device number 4 using ehci-pci
[81118.973960] usb 2-1.4: New USB device found, idVendor=25a7, idProduct=2433
[81118.973969] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[81118.973974] usb 2-1.4: Product: 2.4G Wireless Device
[81118.973978] usb 2-1.4: Manufacturer: 2.4G
[81118.976399] input: 2.4G 2.4G Wireless Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/0003:25A7:2433.0003/input/input16
[81119.031707] hid-generic 0003:25A7:2433.0003: input,hidraw0: USB HID v1.01 Keyboard [2.4G 2.4G Wireless Device] on usb-0000:00:1d.0-1.4/input0
[81119.034970] input: 2.4G 2.4G Wireless Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/0003:25A7:2433.0004/input/input17
[81119.087831] hid-generic 0003:25A7:2433.0004: input,hiddev0,hidraw1: USB HID v1.01 Mouse [2.4G 2.4G Wireless Device] on usb-0000:00:1d.0-1.4/input1
[90119.420279] atkbd serio0: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
[90119.420289] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.