Hi,
I’ve been trying to run the firmware updater for asmedia but get an error message that I’m trying to run a 32bit app in a 64 bit environment?
Thanks.
Help be greatly appreciated.
PS: Anyone care to do performance benchmarks of usb3 per firmware driver version? Be interesting.
You need to create a bootable DOS USB Flash drive. Use a tool such as Rufus. Once bootable drive is created, copy contents to the flash drive then restart computer and boot from it.
I do not have any benchmarks, but after updating firmware my USB 3.0 is solid as a ROCK. No more sporadic computer crashes/freezing/hangs when I plug in random USB 3.0 devices. I have copied at least 150GB+ back and forth on random devices with out issue. Believe me, it was very frustrating so I had stopped using the USB 3.0 ports all together. I was even on the verge of upgrading my computer because I really need USB 3.0 speeds.
I am not the only one either. If you google Asus Z68 USB 3.0 issues, there are tons of threads on stability issues. People thought it was just a manufacturer defect, but thanks to this thread that is not the case. :c)
About two weeks ago, i flashed firmware on my Asus Maximus V Gene. It has ASM1042, i used firmware from post #36.
Also flashed discrete controller from Delock (Sata ASM106x and USB ASM1042 combo) with same FW, all worked well (but i can’t flash fw for sata controler on delock card).
Looks like I have a Nec uPD720200a chip. Oops. My mistake. Found appropriate module from the usual place and upgraded. Had to reset my device in device manager to get it to work though. Probably needs a driver reinstall now. Thanks for the help anyhow.
@ lordkag:
Thank you very much for your efforts to help our Forum members to update their ASMedia 104x USB 3.0 Firmware.
Just because I am interested to know more about this topic, I just have checked the ASMedia 104x USB 3.0 Firmware version of my ASRock Z97 Extreme6 board. It is 140124_10_10_04 (SVID:SSID=0x1849:0x1142).
The related dumped Firmware file is attached.
Questions:
1. Is the v14124_10_10_04 the latest ASMedia 104x USB 3.0 Firmware version for my system?
2. Since the required Firmware depends on the ASMedia 104x Chip and not on the mainboard chipset, can the ASM104x Firmware of my system be used with other systems?
Asm104x_FW_v140124_10_10_04.rar (24.5 KB)
Is 130125_00_02_00 still the latest firmware for the ASM1042 chip?
@Fernando
Thank you for this new firmware. I was almost 99% certain it was an ASM1042A firmware and I was right. There is little chance we will see another ASM1042 firmware, since the chip was removed from ASMedia site altogether.
Yes, this is the latest firmware for your card. I only had 131025_10_11_03 (ASM1042A) until now. Since your mainboard is rather new, probably it was the last firmware in production. And with the new ASM1142 USB3.1 released, probably it is ASM1042A turn to be retired.
Probably yes, it can be used with other ASM1042A controllers, no matter if internal or external. This firmware was extracted from the chip itself and has a full header, so no modding needed. Users with ASM1042 should use 130125_00_02_00 from the previous page, while users with ASM1042A should use this new 140124_10_10_04 firmware.
@Fernando
@lordkag
Hi guys, thanks for all your great work. I need your expertise please…
I have the same Z97 Extreme 6 mobo & lost my 140124 fw when I forgot to make a backup before trying 131025 !!!
I have just updated using your file from post #85 but getting strange result - the updater says it’s updating from 131025_10_11_03 to 140124_10_10_04 and completes without error.
However, re-running with the display switch after the update says I’m now on 120507_00_10_1b !
Any ideas why this is or how to fix ???
Thanks
@ staveley:
Welcome at Win-RAID Forum!
Please wait until lordkag is online and has read your post. He knows much more about these things than me.
Regards
Dieter (alias Fernando)
@Fernando
@lordkag
Hi Guys, I’ve done some more testing & it looks like the .bin file size is the problem. All my other versions of 104x firmware are 64KB but Fernando’s file is 128KB.
When I run the update with the 128KB file I get this:
Current: 131025_10_11_03 Update to: 140124_10_10_04
update host[0] firmware… Miss Compare PASS!!
SRC 00000000 00 00 01 00 30 00 32 31
DST 00000000 00 00 00 00 00 00 00 00
PASS!!
Re-run with display switch shows FW 120507_00_10_1b
If I then hex edit the .bin file and truncate to 64KB and run the update I get:
Current: 131025_10_11_03 Update to: 140124_10_10_04
update host[0] firmware… PASS!!
Update firmware…PASS!!
Re-run with display switch now shows FW 140124_10_10_04. Yippee !!
Hope this will help others performing the update.
Edit - 64KB update files attached.
Edit 27/02/15 - updated file attached with corrected fw filename
asm104x_140124_10_10_04_2.rar (179 KB)
@ staveley:
Thanks for your report.
It is fine, that you succeeded at least with the ASMedia 104x USB 3.0 Firmware update.
Please attach the truncated firmware file.
File added to post #90
To quote myself : no problems so far, no more lock-up since the driver+firmware upgrade.
@lordkag : big thanks again !!
Possible flash back the whole Default Motherboard Firmware or Edited From UBU tools. The Asmedia USB will live again? thanks
@staveley
It is funny that the flasher can’t properly analyse the same firmware it dumped. Anyway, it seems the flasher reads the header of the firmware, gets the declared size of 0x10000, then somehow thinks the rest of the padding is a part of the firmware or a new firmware. Weird stuff, but you soon learn to move past those glitches and just feed the flasher what it expects. Just two observations: in the pack you uploaded, the u.bat still points to 131025.bin, in case anyone is getting another error of “file not found”; the second one is that you updated 104XFW.CFG with new values, that might not work for every controller, but the good thing is that you left them commented, so no real danger there.
@daffie
Nothing to thank me. It is not like I coded the firmware myself. On one hand you can thank ASMedia for fixing the bugs, but on the other hand you can complain about their policy of not releasing the firmware to the public. I still don’t understand this practice of “they don’t ask, we don’t tell” when it comes to firmwares and OROMs, the secrecy of releases. What’s the point of fixing your firmware if not to release it to all customers? It is not like they have to compile it for every OEM and then test it with every board. It either works or it doesn’t. I hope we will see a public release of all/important firmware, someday. And not just for ASMedia.
@9tailsfox
If you flashed ASMedia_asm104x_131025MOD (!!! MOD !!!), then I already posted a reply here, right bellow the image. There is nothing I can add, because it will range from rudeness to offensive. You have to live with your own mistakes. But if you flashed another image, then you will need to add: what image, what controller, what board.
People tend to skip to the end when it comes to such things which can only be dangerous. Still, if you tell me which post contains this ready-to-brick-your-controller firmware I can delete it and avoid any such issues in the future. 
Regarding not releasing up-to-date firmware I couldn’t agree more and have one thing to say: cough…CLEVO…cough (not even BIOS, go figure…)
If only this was the case! I sometimes do this, skip to the end and go backwards until I have enough info. But they jumped right to the post where I posted a modded firmware and ignored the warnings, ignored the next post with Hanson’s reply. That is why I have no help for them.
It is this post that seems to be stuck in people’s mind. The file Asmedia_asm104x_131025mod.rar is the blame, the other is fine. Can you add a big warning that this file bricks controllers and maybe also delete it?
Can’t you edit your old post yourself?
I thought it is impossible to edit a post after this long time, since I already had a similar situation some months ago, where a 2 weeks old post couldn’t be edited. But I tried and it worked. Kind off, because it deleted every file but the one I wanted. I had to remove all other pictures and files before I could delete the one I wanted.
Now there should be no more complaints.