P2S inoperative after firmware 01.01.0300 update

I am having a very bad experince with the Bambu support tickets, and hereby I am trying to expose my case, and trying to get a solution for my 3 months old printer under waranty.

After updating My P2S to firmware 01.01.0300, my printer became inoperable.
The hotend temperature now reads 0°C (it should at least show room temperature), the hotend fan runs at maximum speed, and attempting to home the printer results in an Extrusion Force Sensor Signal is Abnormal.

I attempted to roll back to the previous firmware version, but the issue persists with identical symptoms.
I also powered the printer off and disconnected it for several minutes, with no improvement.
I tried performing a factory reset, but I cannot complete it because the printer requires unloading the filament. Since the hotend does not heat, unloading via software is impossible. I manually cut and removed the filament, but the printer still insists that filament must be unloaded, even when none is present, so unable to do a fatory reset.

I have followed below checks:

I have reseated all cables, double checked all connections, with same results.
The hotend temperature still reads 0°C and no home is possible.

According to the above link the issue is related with comunication problem with MC‑TH boards.

To be 100% sure I followed this one to test the NTC:

Measured the NTC with a multimeter : +/- 100Kohms - correct

After completing all the requested tests, it became clear that I needed to file a warranty claim, so I opened a support ticket to explain the issue and obtain a solution.
After more than a week of back‑and‑forth messages, the experience has been extremely disappointing. The replies felt automated or AI bot, tests were repeated unnecessarily, and the same information was requested multiple times. yet no real progress or solution was provided.

When I finally asked what the proposed fix would be, I received the following response:

“Unfortunately, the hot-end heating assembly is not covered under our warranty. You will need to purchase it separately from our online store.”

This conclusion makes no sense. A faulty hot-end heating assembly could explain a constant 0°C reading, but it does not explain the homing failure. Based on the tests performed, it is quite clear that there is no MC‑TH communication, which strongly suggests an issue with the TH board, not the hot-end.

Is there any way to escalate this ticket so it can be reviewed by a qualified engineer?
I would appreciate a proper technical analysis of the case.

1 Like

@SupportAssistant kindly review this case.

Firmware Downgrade | Bambu Lab Wiki

Software Bambu Handy | Bambu Lab

The wiki will show you hot to downgrade the firmware , see if that can help , while you wait for support to get back to you

Hi @Neiljt thanks for your reply.

I have downgraded the firmware using the instrutions you have mentioned.
Also I forgot to mention, that Ihave downgrade, then update it again, with same results.

The idea behind the firmware downgrade is to see if the error persists, not a fresh update

1 Like

yes, after downgrade, the problem persists, and I did mention that on my initial post.

maybe we both missed it , wait on support

Please send me a private message with the ticket number, and we will double-check it.

Considering the shared details, there could be a problem with the hotend heatings assembly connection, or the TH board where this is connected.

Once I get the ticket ID we can find out more.

1 Like

How is this even possible when the only published firmware for the P2S is Version 01.01.01.00?

The All-Round Best Value Workhorse | Bambu Lab US

Is this a beta firmware?

I found out their support is currently short staffed due to Chinese New Year and are not taking any escalations till after Feb. 23/24. I’m not suggesting anything about you, but for myself, I had to re-assess my wording, ask for a human and no more Ai responses and I asked very nicely. I kind of started off rude—cause I was peeved. After I calmed down and realized when I support people in my own career I always give better support to nice people, I used a more professional, nice approach and wording and have experienced responsive and understandable non-Ai responses from support. Hopefully you get this thing escalated and fixed up with their help after new years over. GL

2 Likes

I’m still using 01.01.00.01 or whatever they called it and I’ve never updated. I print for my own charity, so I’m a “zero risks” kinda guy these days. I wait until things like this to happen before I update, hence still being 3 versions back.

The reason for them only having 1 good update is simple: They don’t care about the P2S until the H2 series is perfect. Have you seen the changelogs for the H2 series? It’s getting 100x as much dev time as the P2S and it shows.

I kinda think they just tried to have AI do low-effort updates in .02, .03, and .04 hence the issues.
I don’t even really expect them to patch this again. They might, or they might just tell people to use .01 while they work on the H2 series. That’s my prediction. Given that only 1 of 4 updates has been fully functional, that gives us a 75% chance of .05 having issues still.

1 Like

I just wanted to remind everybody that Bambu labs was going to be on holiday till February 24. They still had some support staff, but they are going to be behind because of all this and because people are currently out right now.

1 Like

It’s terrible that your brand spanking new P2S is bricked and the support is far less than ideal.

I have been printing literally every day, sometimes 16-18 hrs per day since I bought my P2S on Black Friday, as soon as it was available for sale in the US.

My intent is not to make you even worse but I wanted to add to the thread that I have my P2S set to auto update and it’s currently running the latest version 01.01.03.00 and I have no issues.

I am only posting to see how prevalent are update related issues. If it’s somewhat commonplace, I may change my printer settings not to update automatically.

2 Likes

no, it is a stable version.

UPDATE: The case has been resolved.

Although the initial support was disappointing, after this post I was contacted by another representative who promptly diagnosed the issue and provided a solution.

In summary, it appears to have been an unfortunate hardware failure, not related to the firmware. My TH board had died, they sent a replacement, and the system is now functioning correctly.

3 Likes

Yes!, Yes!, Yes! Not sure if I can find an emoji that expresses my happiness for you. This is as good as I could find. So happy for you buddy!!! ✺◟(^∇^)◞✺

Looks like i probably have the same issue on my P2S. Had another strange issue though P2S kept rebooting… and now same issue as you have i suspect TH board is the issue too.

1 Like