VCI-400 SE New Firmware mismatch!ERROR! no ACK still in bootloader mode! help!!!Pls!!
Hi everybody got a big Problem:
Wanna upgrade via PC load Current firmware Version…browse for v2.0…start and FirmUp says: ACK not found!..The VCI is still now in bootloader mode and i can’t use it…got my next session on Dec. the 1st. WAHHH need help please!
Notes: Got VCI-400 SE / Win 7 (64bit) / Vestax ASIO Driver 1.52 / Vestax v2.0 firmware (Standalone Mixer) / Ean Golden firmware v1.0 (0007004)
Well, resolved the problem…for everyone who wanna know it:
make a factory reset in org. vestax firmware tool in OSX, after that load up org. vestax firmware v2.0 (standalone mixer update)…at the end get firmware updater from techtools for upgrading to techtools vci 400 se v2.0 (with PC only)…
…connect with my make loading up .tsi for Traktor 2.6 Done!Works fine until now
I had the same problem “ERROR!! ACK is not found”. Unfortunately, doing the factory reset on MacOSX and installing the standalone mixer firmware did not fix my VCI. It’s still stuck in bootloader mode! Can you explain more clearly how you were able to do the DJTT v2 update at the end of the standalone mixer update?
I hope the other user replies, for I am having a similar problem–although may/may not be the exact issue.
My VCI 400 unit is not stuck in boot loader mode. It is unable to get into boot loader mode. The reason this all happened is, I attempted to upgrade to the recent Vestax 2x firmware, and it seemed to cause a conflict with the existing firmware. So now, I’m attempting to restore to factory settings, yet, I cannot get into boot loader mode in order to do this. I have contacted Vestax, DJTT, and Flashflooder, and await a response. If I find out a solution, I’ll be sure to follow up to this thread.
When I press “get Version”: there is no reply
When I press “Start”: ERROR ACK is not found
My hardware conditions occurred with Mac OS, and (Toshiba) Win 7, and Win 8, using Traktor 2.6, with Flashflooder 2.5.1 mapping.
I thought I’d share what I experienced with other users… The reason I think I was unable to get into boot loader mode (instead of being locked within boot loader mode), was because the USB/Power lights did not behave as they normally would–indicating the boot mode is enabled.
After going through many re/installation procedures, I eventually got to a clean reinstall (including the Flashflooder goods). Yet I was only certain on a few attempts, if ‘boot loader mode’ was in fact enabled, because the of lights.
I later experienced what being locked in boot loader mode was, but I quickly recovered from it. So… there’s 2 different problematic scenarios.
On other reinstall attempts, the firmware updater app would message, ‘no reply’, which also did not indicate ‘boot loader mode’ was actually on/off.
I researched through others’ related issues. I didn’t read a mention of the scenario, I’ve just described. I hope this information makes sense and helps. If I can help more, let me know. For now, I’m staying clear of any future firmware updates until further notice, or unless those updates come from Flashflooder.
For the record, I did not need to downgrade to the FW1 flashflooder ware, nor do a factory reset.