Firmware updated, possibly interrupted (froze), now have a corrupt audio file on startup

I updated to 591 but it froze before doing anything. I waited for a good 20 minutes and when the progress bar was still stuck at 0%, I shut down the program. I then shut everything down and restarted the firmware update, which ran successfully, except for the screaming squelch when the voice announces "The Bullet is …(screeching noise). I’ve tried updating to the beta which didn’t help and then back-rev’d. The back-rev succeeded but the audio screech remains. I don’t know if anything else is affected at this point. I was wondering if it was possible to run a clean wipe of the audio files?

1 Like

There are issues with f/w update (& driver installation). The progress bar did nothing regardless the delay (much as you describe) no matter how many times I tried. Yet others only needed to wait a bit and all was good.

I understand there may be a workable correction coming this week for both f/w update and driver installation.

Bruce

Alternative software is available called Artisan. It too has bugs.

1 Like

I have the same issue, just got my bullet, connected it to the PC for the first time and did a firmware update and now I have a distorted voice saying “The bullet is ready” in a really slow spooky way. I can no longer connect via USB either even after multiple attempts of installing Roastime/Drivers. I seriously hope I can continue roasting without problems in manual mode.

BTW, Anyone that can direct me to how to get my computer to recognize the bullet when plugged in? all I get is " Unknown USB Device (Device Descriptor Request Failed)"

Did the driver install ever finish running successfully? Are you on windows?

Can you join the slack? We have a version in beta right now that may fix your driver install issue if so:

Jumped on the Slack app and also contacted support regarding the distorted sound.
I’ll post an update here if anything pans out.

I’ve done it so not sure what to tell you….

I was happy to learn this forum has temporary and permanent Mute feature for specific topics and users.

Peace
-Damon

Yeah, as an admin I thought I had ignored him for all of us, turned out it was just for me. But now I have silenced him for good.

6 Likes

Ok, lots seems to have happened here since I last posted but to get back on topic;

My solution was manual bootloader and fresh firmware update with roast time 3(see vid.)

This cleared up the distorted voice issue and allowed my computer to recognize the bullet through USB. All is well now.

Hope this helps!

2 Likes

I’ve been down that road several times and not always cuz I had to… just the familiar path.

Bruce

As I only had access to a PC for the night It seemed like the only surefire way to get back to business…

No luck on my side. Serial 005237. The video says 4 beeps for the bootloader, I only got 3 but the application worked and I was able to download the beta version (602) which made the screech worse. Instead of saying “The Bullet–(screech noise)” it went to “The (screech noise)” I back-rev’d to the release version ( 591) and got back to “The Bullet (screech)”. This leads me to the assumption that a previous version before 591 would get me to “The Bullet is…” and the version before the previous will resolve the issue :slight_smile: (/sarcasm). At any rate, other than the screech, the Bullet seems to be working fine and the other voices are fine. Out of curiosity, is there a site location for previous versions before 591? I’ll email support and report back. Other than that, I may be preaching to the choir, but the Bullet is an excellent roaster, from the thoughtful design to the toolset, which I’ve needed, I’ve been impressed so far and I’ve only done one roast.Thanks for the quality!

I did try the version on Slack (3.3rc5) and that did not work at all. The app was not successful in loading the firmware. Also the Beta tab throws an error.

If I can borrow my friends computer again and he hasn’t deleted the files I can check what version I used.

I am sorry that you got this problem.
We have found the issue and have a fix for the corrupted voice files so it cannot happen again. However, for you to recover them you need to contact support@aillio.com and they need to schedule a teamviewer session to fix it. I don’t believe an earlier firmware version will help with this.

1 Like

I just updated my firmware to 591 and have the same issue, I ONLY get the static, there’s no comprehensible words. Will there be a fix in a future firmware or is contacting you through email and teamviewer session the only solution?

From what I read if you’re already corrupted then you need to email support so that they can work out a fix. Newest versions of firmware will prevent it happening but can’t restore it.

OK thanks, I’ll go ahead and email them and let folks know what they tell me.