Since Filament update never stops

Yesterday there was a firmware update, ever since when I add/change the filament in the device in BBS the updating spinney thing spins forever. Only with generic filament, not BBL filament and on the A1 and A1 mini. Anyone else see this, is it a bug, has it been reported? It seem to print OK.

Current firmware:
A1 mini:
01.06.00.0
AMS:
00.00.08.08

A1:
01.06.00.00
AMS:
same

1 Like

Same problem with my A1 after the update on my A1, the spool #4 has now a never ending spinning arrow in Bambu studio. I tried a different filament, then turned the A1 on and off, still spinning, so I tried load then unload the filament no change. So I printed a part and had no problem printing, it just keeps spinning, oh ya I reinstalled Bambu studio no change :frowning:

2 Likes

Pull the filament out of the feeder and reinstall it .Fixed the problem for me.

1 Like

pulled filament and reload like you asked, it stops but when I turn A1 and the A1 mini off and on the printer IT"S BACK, oh ya my A1 mini has the same problem since the last update never had it before…IT IS FROM THE UPDATE… And only slot #4 does it.

On both A1 and A1 mini just slot #4.

1 Like

oh ya one more thang all filament is Bambu labs.

Didn’t fix it for me. Of course BBL is asleep at the wheel on this, nothing I have seen from them.

Sorry for the suggestion. I noticed that it didn’t work after I turned my printer back on.
The only way to stop it is to downgrade the firmware which I have done.(1.05)

2 Likes

downgrade did it for me, both the A1 and A1 mini work ok now.

1 Like

it happen to me after I updated the Ai and AMS Lite firmware to latest, i was told that there is a glitch in the latest firmware, to be fix some time in the future and to roll back to a earlier firmware…

Still an issue as of 9/6/25

1 Like

Having the same issue. I am rolling the printer firmware 1.06 → 1.05 now.

Update: Seems like the printer heats up, and then on the part where it’s suppose to get the filament purged and ready, the AMS just stalls.

Same here…facing this issue too