When my device became bricked, one interesting thing to note is that the lights lit up multicolored just for a second or so before they all went dark and the device started boot looping. This is different to the successful upgrade I did from version 50 → 52 where the lights stayed lit up for ~10 seconds before rebooting.
Is it possible that you’re still having issues reading from certain flash drives? When I went from 50 → 52 I had to try 3 different flash drives, each formatted to FAT slightly differently (block allocation size, partition size, etc). And at one point, the app was even showing the new update, but upon clicking “update” the device would just reboot like nothing happened. Randomly though, I seem to have finally found a flash stick + format the worked, and I have no idea why that combination worked for 50 → 52 and the others didn’t.
That being said, I did not use that same flash drive when I tried the version 56 upgrade, instead I just used one of my other FAT32 formatted memory sticks. I know you said you have FAT32 working, but maybe there’s still issues and the reading of the file becomes corrupted part way during the transfer or something. The flashing lights + reboot happened quickly enough for me to suspect the update did not fully install. Likewise, another reason I suspect the Flash drives/format being the issue is that those of us with the issue have been reporting that we used FAT32 formatted flash sticks. So perhaps the device is able to see the update file on FAT32 device, but it’s still buggy when actually reading the data.
Hi Sanath, you could check if there’s other MVA files on disk. And if no, make sure the file is fully copied, could verify the md5 checksum for the file on disk.
Thanks for the info, I’ll keep this in mind in the testing.
And one more point, we’ll on holiday until Feb 18, so could consider to not upgrade firmware because we might have little response in customer service.
My device bricked. I got the prompt for update, confirmed it, all lights lit up and then the worst happened. Looping between stand by and bluetooth. What do I do next?
Yes @optionaltoast . Previous upgrade to 52 happened very smoothly. So I was very confident that the current upgrade would happen successfully. But it turned out to be otherwise. So we are 4 with bricked units. Ok. Lets wait for their response. Its going to be a long wait as they are on holidays till 18th. Fortunately, I have a A50+ amp which I can use till a solution is found for B50.
I’m dumb… I bought a used B50 and didn’t read this forum thread completely before upgrading today. Before that it was running.
I wonder if there is a possibility to do a factory reset…?
Can you elaborate on the last sentence. Does connecting the B50 to a PC via HDMI fix all the errors or is this temporary and the device remains bricked when not connected via ARC?
UPDATE: I have no idea why or how, but when there is an HDMI cable in the ARC slot (it doesn’t have to be connected to anything at the other end) the device is discoverable via bluetooth, the app works, I can select inputs via the app and the volume knob. Which if what @zpl1025 has said is true and the device is recoverable via a software programme when connected to PC via usbdac there may be some hope for these bricked amps. @bwyazel@Sanath@Topher52 Can you check and confirm @arboeh 's findings?
with an hdmi cable plugged in the device is recognised !!! AND WORKS
usb 1-10.1.2: New USB device found, idVendor=8888, idProduct=1717, bcdDevice= 1.00
[11195.836399] usb 1-10.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11195.836402] usb 1-10.1.2: Product: Up2Stream USB Audio
[11195.836405] usb 1-10.1.2: Manufacturer: Arylic
[11195.836407] usb 1-10.1.2: SerialNumber: 20190808
[11195.862405] usb 1-10.1.2: Warning! Unlikely big volume range (=4096), cval->res is probably wrong.
[11195.862413] usb 1-10.1.2: [2] FU [PCM Playback Volume] ch = 2, val = 0/4096/1
[11195.866612] input: Arylic Up2Stream USB Audio as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10.1/1-10.1.2/1-10.1.2:1.2/0003:8888:1717.000B/input/input27
[11195.918176] hid-generic 0003:8888:1717.000B: input,hidraw10: USB HID v2.01 Device [Arylic Up2Stream USB Audio] on usb-0000:00:14.0-10.1.2/input2
[11195.918263] usbhid 1-10.1.2:1.3: couldn’t find an input interrupt endpoint
For the first time in a week I’m beginning to feel confident. The big test is does it persist after a restart and the hdmi removed.
So, I can remove the HDMI cable and the B50 still works! but when I restart the amp, it now flashes between STBY and DAC, but significantly the amp is still recognised as a usb device!
It’s fixed temporary. If you turn off the device you have to put the HDMI cable in again to “wake up” the B50 or it stays in “bricked mode” again.
Strange.
Mine is now swapping between STBY and DAC, and I’m not touching it again until @zpl1025 gets back from his holidays as I think it can be working on if a PC recognises it.
Number 5.
Firmware is on 56-0bf6cc3e-8 now.