Hi, I was able to build my first CyberBrick the Truck. I got the transmitter and receiver paired and was able to drive it. I decided to start changing the configurations for the modules in the android app, the app was in the middle of synchronizing a setting and it stopped working.
Only the transmitter works, the receiver stopped working. Anyway that I can reset the module?
Thanks in advance.
Edit: May 31, 2025
Here are more details. I tried the second receiver the module came with and it works fine. Seems to be that I closed the app or exit the synchronization for the config midway through.
I submitted a ticket as well to Bambu labs to see what they can say. The still don’t have a category for CryberBrick products such as the app, so I don’t even know if this ticket is going to get looked at.
Exactly same issue have. I have submit a ticket to bambu support. They updated that they are aware of the bug and working on a firmware fix. Support suggest to use phone app for a more “stable” connection but regardless phone or PC, it is the same for me.
Not sure how its possible to update firmware if both PC and phone unable to connect at all. Still waiting for Bambu Support to revert.
I had the same, it seems that a wrong configuration can boot loop the esp. In my case it has some integer in it where it expected a string. I created the config with the official android app.
Finally I was able to solve it by powering it to a proper wall charger via the usb-C port. I then was able to send the original config again.
I gave this a try and it didn’t worked for me, I’m still waiting on a reply from Bambu Labs. I’m pretty sure as people start playing with the config of the modules other people might run into this bug that if the module disconnects midway the config synchronization it might run into this state where it doesn’t connect to the phone.
Tested both button, it stuck in same state as Gabosky describe. When attempt to connect its static green light then follow by blue light and the app show connection failed.
Seems there is no way to connect at all once you hit the bug.
Surprisingly my second receiver got no issue even after multiple config change.
Same for me, reset doesn’t do anything different it seems. I think the problem is that whatever got programmed into the esp is all wrong. I think the only way to fix this is to flash it via USB the same way they do in the assembly. If only the Cyberbrick software had a flashing option to reset the device with the original firmware.
Edit: I’m trying to see if I can flash it. Looking into the API website.
You may have corrupted the FW download to the ESP32 RX, bricking it.
The reset button doesn’t do anything a power cycle doesn’t do.
But. You can get a bricked ESP32 in to bootloader mode by holding both buttons down while powering up the board. Once in bootloader mode you ought to be able to download the FW to it again…
When the ESP32 is connected to your PC, you should see a COM port assigned to the USB connection. Any Terminal program can be connected to the COM port to see what the ESP32 is saying while it runs.
If you install the Arduino IDE and install the ESP32 board type, you can program the ESP32 as well as monitor its serial port from within the IDE.
If you plug the board in and don’t get a COM port, but you do see a USB device (look in Device Manager), the ESP32’s FW is corrupt and you need to put it in bootloader mode to program it.
Mouse over your device below your project folder, click sync project to device and this should upload an empty micropython script into your cyberbrick core
Please take note only try this if you’re comfortable with programming and messing with the script. I could not 100% make sure that it would fix your issue.
Two things, First up there is a public holiday over there this weekend, and
I think the support team is off until Tuesday their time.
Second, And I don’t wanna be that guy but did you try powering it with a different battery/new AAAs ?
I get this connection issue occasionally with mine if the AAAs are dead, or the LiPo needs a charge, in a similar way to @topdrob getting it fixed by directly powering over usbc.
@kido I tried to follow your steps, but that doesn’t work. I think I had made a mistake, I should had wait for your message, before flash erasing the device. Now I’m in big trouble.
I guess I shouldn’t had gone mad and erase the flash and then load a new flash. To then see if I can flash it with some cyberbrick firmware, which I don’t even know if that exists.
ohh no, likely you have wiped cyberbrick firmware. In this case my step will not work. Best bet now is to wait for Bambulab release cyberbrick firmware or get support to help.
Which is the same microcontroller they are
using for the Cyberbrick controller core module. This should be a pin to pin compatible swap.
I will desoldered the one from Amazon and resoldered into the Cyberbrick module. I will have to flash my own code since there’s no way to flash the original firmware from Cyberbrick.
Unless somebody can point to where I can find the original firmware and download it.
