Help Needed — Bricked Topping E30 II after Firmware Mistake

[gppanicker]

Hey everyone,

I’m hoping someone here can help. I accidentally flashed the E30 II Lite firmware onto my regular E30 II using the Topping DFU tool. Now the DAC powers on (shows PCM when using optical), but it’s completely unresponsive over USB — not recognized on my PC, and the DFU tool shows “No device found.”

I’ve tried:

• Multiple USB ports (rear I/O, different systems)
• Pressing the “headphone” button 5x in standby to enter DFU mode
• Using the correct E30 II_FW1.13.bin firmware file
• Reinstalling drivers

Still nothing. USB just won’t detect at all.

I know some people on this forum have recovered theirs in similar situations — has anyone dealt with this exact issue when the DFU tool doesn’t see the device?
Is there any way to flash the firmware directly using ISP/JTAG or anything else DIY before I consider shipping it out for repair?
Any suggestions would mean a lot - thanks in advance

 

[kemmler3D]

Have you contacted Topping support? I accidentally flashed the wrong FW onto my DX5 lite and they were helpful in fixing it.

 

[unpluggged]

I’m hoping someone here can help

Nobody can help apart from the seller/manufacturer. Making FW updates available to end users while not caring about implementing basic safety checks in the DFU or a backup (failover) FW image in the device is totally on the vendor. And I would (and do) avoid dealing with such incompetent manufacturers.

 

[ziggurcat]

Hey everyone,

I’m hoping someone here can help. I accidentally flashed the E30 II Lite firmware onto my regular E30 II using the Topping DFU tool. Now the DAC powers on (shows PCM when using optical), but it’s completely unresponsive over USB — not recognized on my PC, and the DFU tool shows “No device found.”

I’ve tried:

• Multiple USB ports (rear I/O, different systems)
• Pressing the “headphone” button 5x in standby to enter DFU mode
• Using the correct E30 II_FW1.13.bin firmware file
• Reinstalling drivers

Still nothing. USB just won’t detect at all.

I know some people on this forum have recovered theirs in similar situations — has anyone dealt with this exact issue when the DFU tool doesn’t see the device?
Is there any way to flash the firmware directly using ISP/JTAG or anything else DIY before I consider shipping it out for repair?
Any suggestions would mean a lot - thanks in advance

Have you tried doing a factory reset?

 

[ziggurcat]

Nobody can help apart from the seller/manufacturer. Making FW updates available to end users while not caring about implementing basic safety checks in the DFU or a backup (failover) FW image in the device is totally on the vendor. And I would (and do) avoid dealing with such incompetent manufacturers.

Hate to break it to you, this can happen with any device that has FW updates, so it's not a matter of the manufacturer being "incompetent." Plus, the OP has mentioned that this is basically a case of user error.

The OP can try to perform a factory reset from the instructions in the manual (which hasn't been mentioned in the OP), which should revert it back to its original state, and then they can update to the correct FW version.

 

[unpluggged]

this can happen with any device that has FW updates

But with devices of some specific manufacturers it is more likely to happen, as we have seen here.

so it's not a matter of the manufacturer being "incompetent."

Omitting basic compatibility checks in software that is offered to end users and can render your device a brick (and making things even worse by releasing tons of different products with similar names, but with incompatible firmware binaries) is either incompetence or carelessness.

The OP can try to perform a factory reset from the instructions in the manual (which hasn't been mentioned in the OP), which should revert it back to its original state, and then they can update to the correct FW version.

As we already have found out in similar cases, the only method to restore the correct FW is to send the unit back.

 

[ziggurcat]

But with devices of some specific manufacturers it is more likely to happen, as we have seen here.


Omitting basic compatibility checks in software that is offered to end users and can render your device a brick (and making things even worse by releasing tons of different products with similar names, but with incompatible firmware binaries) is either incompetence or carelessness.


As we already have found out in similar cases, the only method to restore the correct FW is to send the unit back.

- Arguably, it is no more or less likely to happen, regardless of the manufacturer. People's video game consoles have bricked after a FW update, and there's no chance of the end user downloading the incorrect file.

- While I would agree that there should probably be a check in place to verify that the FW is correct before installing, in this instance, the Lite and non-Lite versions of the FW updates are clearly labeled on Topping's site, and they're not even listed consecutively.

- In that example, it is the same as what I mentioned above. The DX3 Pro and DX3 Pro+ updates are clearly labeled on the site, and they're not even listed on the same page. IME, after a weird issue with my D50 III, I did a factory reset, which did drop the FW version back to the original 1.00, and I updated it back to the current v1.39.

 

[xanalog]

...can render your device a brick...

Bricks have been with us since the invention of computers, and we've all had/owned/caused at least one!
Unlike "doorstops"; bricks can sometimes be revived.
I own a Polk center speaker [w/a HeadlessPanther certificate] that will never stop being a doorstop.

 

[RKV1]

Bricks have been with us since the invention of computers, and we've all had/owned/caused at least one!
Unlike "doorstops"; bricks can sometimes be revived.
I own a Polk center speaker [w/a HeadlessPanther certificate] that will never stop being a doorstop.

"Doorstop"... good one. Thanks for explaining the difference. I'll change my usage of the terms from now on.

 

[gppanicker]

Have you contacted Topping support? I accidentally flashed the wrong FW onto my DX5 lite and they were helpful in fixing it.

Yeah, I did reach out — they were happy to help, but I’d have to send it to China. Since I’m in India, that’s not really practical because of the import/export duties. After all the back and forth, the total cost might even exceed the product’s price. So, I just went ahead and bought a new FiiO DAC instead.

 

[xanalog]

After all the back and forth, the total cost might even exceed the product’s price.

Feel charmed that you did not own a bricked 4-figure DAC, that you would've had to eat!

 

[unpluggged]

Since I’m in India, that’s not really practical because of the import/export duties.

Don't you have an exception on duties for return/exchanged goods?

So, I just went ahead and bought a new FiiO DAC instead.

Umm, but what's the point? Feiao is based in the same city as Topping (Guangzhou), and does not have a record for exceptional quality and reliability, either.

 

[ziggurcat]

Yeah, I did reach out — they were happy to help, but I’d have to send it to China. Since I’m in India, that’s not really practical because of the import/export duties. After all the back and forth, the total cost might even exceed the product’s price. So, I just went ahead and bought a new FiiO DAC instead.

Since when does one have to pay taxes/duty on a defective product they are returning product they are sending to the manufacturer to fix? Did you even try restoring the unit back to its factory settings?

 

[mhardy6647]

"Doorstop"... good one. Thanks for explaining the difference. I'll change my usage of the terms from now on.

Us old guys are at least as familiar with the term boat anchor.

https://flic.kr/p/2iL4jHs

this National communication receiver is a boat anchor. I can lift it, but not without substantial effort. On the other hand, it  is refreshingly firmware-free.

 

[RKV1]

Us old guys are at least as familiar with the term boat anchor.

https://flic.kr/p/2iL4jHs

this National communication receiver is a boat anchor. I can lift it, but not without substantial effort. On the other hand, it  is refreshingly firmware-free

Unfortunately, the new stuff is not heavy enough to be a "boat anchor"