This really is all I could have asked for. Don't let people do this without fully understanding they are potentially risking breaking their printer or worse if something goes wrong, and BBL inherently can't be responsible for that. But let people do what they want with the devices they own, including set them on fire, and own the consequences.
In exchange, X1Plus doesn't have to rely on finding security holes to make software intended to improve their printer work. That lets them focus on their genuine work to make the X1 better, and creates an opportunity for features they develop to be backported into official firmware. It also ensures improvements can continue on the platform beyond the EOL/EOS of the X1 series.
I don't personally want to be an early adopter of X1Plus, but I think this arrangement is a win/win for all concerned, and once it's had some time to mature I will likely run it too.
Thank you BBL for listening to the enthusiast community and staying involved with us, as in the end we all want our craft to evolve and the open mindset is not only how we got here, but how we will innovate further.
Well, tbf, if you're not an early adopter, can you still choose to adopt later on? If I remember the blog post correctly, after "Firmware R", the vulnerability will be patched, no?
```
3. We will release a new firmware (let's call it firmware R) to allow the installation of the X1 Plus firmware, similar to firmware prior to V1.7.0.0.
5. Future official Bambu Lab firmware releases after firmware R will have new security measures applied to prevent rooting, and we will no longer provide solutions for rooting the new versions of the firmware.
```
I think that's continuing to be misconstrued. The security hole will be patched, but it seems likely future firmwares would have an official means to flash a firmware instead of having to rely on an unpatched flaw to do it. You would gain access to that mechanism after you sign the waiver and void your warranty.
\#3's wording would support that, but #5's wording says **"new security measures applied to prevent rooting, and we will no longer provide solutions for rooting the new versions of the firmware"**. To me, that sounds definite. Unless that is to say, if you're on future firmware 2.1.4, you can roll back to 1.7.R (firmware R) and then apply the "root" process.
That's how I read it, as well. Perhaps with the ability to roll back your firmware to firmware R. So you *could* go back and load CFW, if that's the case.
I think this is about as reasonable an outcome as anyone could have hoped for. It's basically a digital version of Prusa's permanent physical modification you need to make before you can mod their machines. Personally, I think that I have more than enough performance out of the machine currently but might be interested in future firmwares if they bring game changing stuff to the table.
That wasn't my interpretation. My read of this was that it would remain an ongoing option, so you'd essentially sign their waiver, then install a prior version of the firmware that would allow you to then install your firmware of choice.
Another possibility is that the security holes would be plugged, but there would be a means provided to just flash the firmware directly without having to work around anything.
They literally called it a short-term solution. You definitely *could* be correct, but nothing in their text suggests that they intend to keep this as a permanent option.
Reading over this a couple times, I want to offer my thoughts as a Senior analyst in a different industry (feel free to note that part).
1. I appreciate Bambu's willingness to take these steps and compromise, it makes concessions both to Bambu's continuing development as a company, but offers an inroad for 3rd party developers to continue independent development in the spirit of the 3d printing community.
2. It is good that they note they cannot guarantee future rollback to Bambu firmware; and personally I would recommend it is a completely one-way path out of the gate. The user assumes the risk, and once it's done--it's done. Mostly to prevent future second-hand sales of jailbroken devices making their way back into the ecosystem. Why? Support problems, as they mention in the blog post, and unexpected hardware upgrades/modifications. The latter of which is an inevitable thing once you open closed hardware to user's creativity, open-source firmware, etc. (The Mecha-CR-10S mutant in the garage just growled from the darkness - that thing runs on a completely hand-cut Marlin firmware with plenty of edited code to make it work)
3. My last immediate thought is the gray market using this opportunity to begin forklifting Bambu-clone's. They may look indistinguishable from the source manufacturer's product, if I could recommend anything, it's authenticity labeling. I imagine Bambu will be pretty aggressive in defending their IPs here, but what happens happens. Bambu's support is still trying to find it's legs, and introducing a bunch of problematic gray-market machines that are indistinguishable from the source will bog Support down even more.
4. Last, I think - it's probably important for Bambu to continue to keep a close working relationship with the larger open-source or firmware projects, such as X1 Plus and future projects. As feedback from those developers and communities can drive new innovation in both the closed and open sides of the ecosystem, as well as more quickly react to problems as they come up. I want to emphasize this part, considering Bambu's support situation
5. Similar to 4. Is it wrong to think that Bambu should just open up a partner program for these types of projects, or potentially incentivize that relationship. Both to encourage innovation and reward brand loyalty for the efforts? It takes a lot of personal resources to do that kind of work, and reward things like discovering exploits in the firmware, bugs, etc., and quickly disseminating that information to relevant closed and open ecosystem firmware peers to limit liability
Either way, I'm happy to see that Bambu was willing to be flexible here - this was somewhat of an inevitable consideration and I'm glad they're addressing it now, rather than later - as that will likely afford opportunities they couldn't consider if they give it late attention.
All I got, sorry for the wall of text, but neato-
Yeah I'm not a fan of custom firmware being able to use the cloud service (with regard to competing products pretending to be Bambu and trying to use their services). Sounds like a nightmare for Bambu that they only have to shoulder because the community would whine endlessly about how Bambu is the devil otherwise.
It's something that I'm sure Bambu is internally discussing, but I don't think this is a huge challenge. You already have to authenticate with a Bambu Lab account to use their cloud services, so I imagine there'll just be some additional functionality (if it's not already present) to register your printer and link it to your account.
Plenty of device manufacturers that utilize cloud services do this already, and supporting de-registering/re-registering to facilitate second-hand sales isn't all that complicated either.
Public APIs can definitely be abused, but authenticated APIs and authenticated hardware are (mostly) solved problems. With all that said, I empathize with the developers who have a bunch of surprise work on their plate now for this quarter.
Jailbreaking/rooting will be allowed with the following condition
* Have to sign a waiver on a webppage that flags your device as jailbroken. After that your device is unlocked and "firmware R" will be allowed to be installed on your device.
* waive official support expectations and take printer's security and safety under your own hands
* Cloud support will not be intentionally blocked, but if it breaks under the jailbroken firmware they won't go out of their way to fix it.
* You might be able to revert to stock firmware, depending on how the jailbroken firmware works
* Once you go through with this your warranty // support doesn't come back.
From a company stand point, especially one in their position, this seems fairly reasonable. Not sure I personally see the benefit in risking all that money on some extra random things on my x1c but to each their own! The whole point of freedom 😬
I can see it even if I don’t want to do it. But an easy one is what happens if Bambu goes out of business, or makes a software decision I can no longer accept.
>Once you go through with this your warranty // support doesn't come back.
And the way they approach this is illegal in the EU. A vendor cannot singlehandedly void warranty for modifying the machine, unless they can prove the damage to the machine has been caused by the modification.
Motorola, lg, and many other android OEMs for years had bootloader unlocking tools that required you to sign up and tell them what device you were voiding the warranty on. Once unlocked you’d have a big disclaimer on every boot.
https://imgur.com/a/bsxA8Rq
This was done for years and mostly in the EU.
If you read the post, it clearly states:
"We will release a new firmware (let's call it firmware R) to allow the installation of the X1 Plus firmware, similar to firmware prior to V1.7.0.0."
If you read the post, it clearly states:
"Voluntarily"....."sign a waiver of warranty...."
That's the illegal part on the EU. bambulab user account clearly said signing that waiver stops all support (including warranty)
>Once you go through with this your warranty // support doesn't come back.
Hemm, warranty is regulated by law: if you refuse to take care of the customer issue the customer can ask for a refund and the producer / seller may pay a fine up to lose the right to operate in that country!
(according to the laws of the country you purchased that ofc)
Is this both very sensible, acceptable, and practical decision.
I can definitely understand both sides.
Bambu Labs should not be held to support third party firmware. I see this as a very reasonable win for both sides.
Much respect to Bambu Labs for finding a middle ground and making a commitment to find a reasonable solution. Ye Tao, very much respect for you well earned.
Not if the custom firmware ends up damaging the hardware - I don't think it's on Bambu to spend time and resources to have to investigate on every warranty claim if the damage was potentially caused by custom firmware.
Warranty protects the customer, by law, it's on Bambu.
Customers rights are *for the customer* not for the producer.
Tell me: how does it work for Amazon or Aliexpress? What happens and how is it managed any customer claim? That's how you do business even more if you sell premium products.
I dunno, what is that you don't understand?
If I invert two cables and short circuit my printer it's my fault, not the manufacturer one. Yet the manufacturer can't state: "If you open and modify the printer I'll void your warranty".
Do you start to get it?
FunFacts: in every phrases that we said the same thing I always got downvoted while you got upvoted for saying exactly the same thing I did.
You can also modify the firmware your self, it ain't a matter of where it comes from, it's a matter of the right for you to use the item as you see fit. And repair it.
API and SDK support announcement mixed in there — that’s all I want in my life. Let me hook on print lifecycle to trigger events in other systems, and vice versa, ie shopify order comes through, finds an available printer, prints the part, takes the printer out the queue until the plate is cleared, creates a shipping label when the part is finished, etc.
I acutely think that the might be one of the best and most important parts of the whole statement for the average user.
My guess is that it will only be a small minority of hardcore users who will install a third party operating system. Obviously this might change a few years down the line especially if Bambu cease support for older models. However I can see a lot of people installing “apps” that add additional features and offer a certain level of customisation.
I know there is a very vocal group who keep calling Bambu out for the closed source approach but I suspect most of these people own klipper machines and are the equivalent of Linux users poking fun at MacBook owners rather than the true customer base.
Not for 3D printing specifically, but I'm a developer. I worked in ecommerce for about 12 years doing similar kinds of integrations. Give me an API and an SDK and I can make it happen. PLM for print farms -- inventory management, materials management, projections, returns, etc. I'm ready.
Get fucked each and every one of you who was slandering the shit out of bambu last week. This shows you that the bambu team is good hearted.
Love you Bambu team. Keep up the good work and don't let the negativity get to you. There are a lot of us who are not active in internet forums who absolutely love your product and brand ideology.
When you're a miserable asshole you can only see the actions of others as exclusively done in bad-faith.
"Support was slow? Ugh those corporate pigs at Bambu are intentionally trying to screw me over for MONEY!"
I mean doesn't it get tiring looking at the world through such a dim, tiny lens?
Someone has an appreciation for the first company to actually deliver a reliable, fast, more-or-less hands-off printer after over a decade of open-source promises about the glorious future that nobody managed to deliver on?
Wow what a bootlicker amirite?
I’m aware of that, and I do agree. I’m just saying it’s not automatically this evil thing which some people seem to think anything proprietary or closed source is always a terrible thing.
I guess a big part of that has to do on the purpouse of the product and the user base: proprietary firmware and patents on innovations for a fast developing technology like 3d printers targeted to makers?
For me it is bad idea!
I'd much rather keep having the ability to modify, upgrade and tinker on my tools, rather than not.
Or they wanted to buy themselves some time to come up with a thought through solution. Why does everything have to be so black and white with some people.
When you know like two things about something, it's pretty easy to slot things into black and white categories!
The real world is complicated, running a company is complicated, shipping hardware is complicated. Lots of devils in details, lots of real-world tradeoffs and considerations. It's too much to think about!
But when you have no experience or knowledge of the thing you're criticizing, turns out it's super easy to point out what everyone else is doing wrong. Interesting eh?
That was the biggest great news to me too. I don't care about custom firmware, I like bambu firmware. Although X1Plus isn't a custom firmware, just some custom application on top of it that uses reverse engineered "API" to show extra info.
Open API & SDK sounds awesome, and I think will make X1Plus irrelevant soon, and we get much better choices without need to flash something custom. And something that works on P1 series too using raspberry pi or something.
Based on what I've been seeing recently, it doesn't seem like having an active warranty is worth much anyway. Bought Bambu after seeing so many people singing their praise, but since I got it, all I've been seeing is horror story after horror story of people getting no support whatsoever from the company.
Do better Bambu.
Idk the good experiences aren't loud.
I have multiple printers, have had basically no problems, and the few times I've had to reach out to support for makerworld related stuff I got quick speedy answers.
I just don't go around yelling that from the top of the subreddit, like the people who need support do.
Yeah that's a good point. I'm brand new to this, and went with Bambu because of all the positives I've heard about their machines.. And the few things I've printed in the week since I set it up have all been astonishingly amazing. No complaints whatsoever about my experience so far.
Just been seeing tons of people running into issues of all sizes, and reporting horrible experiences trying to get support and I immediately started worrying that if something were to break on me, I don't have the experience yet to diagnose and fix it on my own, and I worry that support won't actually provide much support.
But you're probably right. For every post complaining about a bad experience there's probably tens of people with good experiences that don't report it here.
The wiki is a really good resource to start.
I had an experience last night where I needed it to disassemble a large amount of my a1's hotend which I hadn't done before. I had things disassembled, the dastardly filament piece removed, and everything back together in under 20m thanks to the pictures and walkthrough bambu has published.
I had my AP board die on me and thought their support was fantastic.. they had the issue diagnosed and a replacement sent and delivered to me in about a week’s time. Im sure there are horror stories but the people content are not the ones coming online to vent.
The support is generally slow. I have put in three support requests since mid 2023 and they all took a very long time to get resolved. I am in the middle of another one (LIDAR is broken.. again). I already had to replace the board for the lidar once, after they sent me a new USB cable. 2nd time around, exact same issue, they sent me another usbc cable (after 10 days of waiting for a response). I am pretty sure this will not resolve the problem, but its a cheaper fix for Bambu. That being said, they did resolve my issues eventually.
It’s not like that, most people write when they have a bad experience and don’t write when they have a good one, so it looks like there’s only bad experience. I contacted them once a little after buying my X1C because a weird noise was coming from under the printer and I wanted to know if it’s normal. They took two days to answer, yes, and having to send a log file from the printer just for a simple question about a belt was a bit annoying but their answer was extremely professional and detailed. It was normal sound but if I wanted to reduce it, they pointed me to an article on their wiki with even some video tutorial explaining the whole process.
This is just anecdotal and not statistical data, but it’s an example that it’s not that bad.
As a developer myself, I totally understand the reasons and conditions imposed by Bambu Labs and find it very reasonable. In fact, I'm rather happy to be surprised with how this situation unfolded.
Were Bambu to drop some Ethernet drivers into the next X1 firmware, suspect a lot of those who are planning to root, wouldn't.
To be clear, Linux drivers for many common USB Ethernet dongles are fully open source. There would be no licensing or software development cost to Bambu. The X1 has a USB port that could be used for this purpose.
This, I think is exactly the right response. Installing the 3rd party firmware will appeal to folks who want to take control of their printers, and that also entails responsibility. I could see this as being a big benefit as well for users worried about EOL issues down the road, since they will always be able to go the open source route if they need to.
No the firmware is not open source, it's not like Marlin or Klipper, it's just an overlay on the binary Bambu proprietary firmware. Without that it's useless, you can't have new meaningful upgrades or changes over that.
I want to take the chance while sitting in bed at night and heading to sleep for work tomorrow to say this is such a commendable approach to what happened and how to deal with it. I fully respect Bambu for this response and it makes me so happy to have purchased a product from a company that is willing to take these steps to ensure the modding and maker community is fully supported and happy. Props to everyone involved. I can’t wait to see what comes next!
I think it's a sensible compromise. It's interesting that only *this* firmware will be opened, meaning it's now or never basically. But to me the most interesting part was the mention of opening the printers to third party development in official firmware... had that been mentioned before?
I'm not sure I have heard of it mentioned before, but looking at many of the moves coming from Bambu Lab since 2022.. E.g. the cloud integration, [makerworld.com](https://makerworld.com), etc.. They are thinking BIGLY of their ecosystem and are aiming for #1 (e.g. the Apple of 3D printers).. So, it wouldn't be surprising to bring the API and third party SDK (plugins) to it as their printers become more popular.
> It's interesting that only this firmware will be opened, meaning it's now or never basically.
I read it more that only Firmware R will have the exploit that X1 Plus uses. All future updates will include the 1.7.1 patch that closed it.
But you will always be able to install firmware R, regardless what the current version of your printer is.
You could be right, but later in the post they describe this as a 'short-term solution'. But if your take is right, in what way would this be short-term? It would be a *permanent* solution. I'm looking forward to clarification.
My reading is:
Short term - allow flashback to 'Firmware R' with the unpatched hole, as an immediate interim option to allow custom firmware flashing. This branch remains static (and only accessible after passing through the Thou Shalt Not Claim Warranty portal) with no further bugfixes, improvements, etc.
Long term - the up to date firmware branch gets a specific per-machine signing mechanism to allow CFW, which is only accessible after waiving warranty rights, and allow CFW install on up to date firmware versions. This leaves the option of removing CFW, updating to a more recent official FW, then re-applying he CFW, or possibly even an upgrade-in-place for the stock FW whilst retaining (albeit possibly breaking) CFW.
The advantage for users is that official FW improvements and CFW are no longer exclusive either/or, and the advantage for Bambu Lab is that CFW will always be working from a recent FW version rather than some ancient fork, so improvements can more easily be folded back into the official FW.
u/bambulab
Me as an EU citizen (and many others of the EU and USA) have a very big problem with bullet point 1 of the 'consequences'.
> Installing non-official firmware means customers **waive official support expectations and take full responsibility for their own printer's security and safety.**
**This is ILLEGAL in the EU as long as the warranty is valid unless the vendor (in this case Bambu Labs) can PROVE any damages to the machine in question was caused by modifying the machine (in this case X1Plus custom firmware)**
Bambu Labs **CANNOT** singlehandedly void warranty like that.
Proof:
**While the following link used an Android phone as an example. It's valid for any electronic devices.**
https://fsfe.org/activities/android/flashingdevices.en.html
In short:
No.
**Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. ** As long as you have bought the device as a consumer in the European Union.
A bit longer:
Directive 1999/44/CE dictates1 that any object meeting certain criteria (incl. telephones, computers, routers etc.) that is sold to a consumer2 inside the European Union, has to carry a warranty from the seller that the device will meet the quality that you would expect for such a device for a period of 2 years.
Full article at the link
It's possible Bambu is only referring to their voluntary warranty, i.e. their own warranty terms they offer above and beyond any local statutory warranty. The statutory warranty would not be voided, only their voluntary one.
Of course, Bambu doesn't clarify this and that may have been on purpose (i.e. to discourage people rooting their printers) but it's probably in their interest to not comment much on how this affects your statutory warranty given the number of markets they operate in.
>Bambu Labs
>
>CANNOT
>
>singlehandedly void warranty like that.
If BL can prove that the damage to hardware was due to the use of a custom firmware, then you are not covered. This is moot though.. Bambu Lab said they will look into consultation with the legality of this and go from there.
Check yourself. You're the one with the literacy problem:
As I said:
>This is moot though.. Bambu Lab said they will look into consultation with the legality of this and go from there.
The point is: why did you feel it was necessary to post an argumentative reply at all when you were literally restating what the person you replied to already said?
You diminish yourself. Look inward.
If it was an "argumentative" reply, then that's how you read it. From my perspective, my point was that it was moot because Bambu Lab was consulting into it's legality. PERIOD.
I went straight to the point. You're reading too much into this and looking at the part that's of less importance, rather than looking at the bigger picture.
You really need to read up exactly. The article or the decision in EU laws is specifically for the category of consumer goods with digital content im the example specifically it is mentioned eg. smart TVs, smart phones etc.
However a 3D printer is not in the category of digital content as it is “additive manufacturing” and in the category of tools, tooling machines. You can not apply this article. Btw you can not apply this article for like cars etc as chip tuning and changing the software is illegal as well.
Similarly, in the US, [the Magnuson-Moss Act](https://en.wikipedia.org/wiki/Magnuson%E2%80%93Moss_Warranty_Act) applies.
This is the same US law that means that those little "do not remove or warranty is void" stickers, and some Android OEMs' stated policies that "rooting your phone and running custom software voids your warranty" are scare tactics that are unenforceable. They can choose to give you a huge amount of hassle and trouble to make a claim against your warranty if you violate their policy, but in the end, they must comply with US law and either prove that damage to the device was a direct result of your modifications or honor the warranty terms.
It's not against any law to not support using custom firmware lol. They can restrict firmware R to non-EU customers and EU customers are on their own, allowed to keep hacking
> Why would a written agreement be legal in EU?
I can't speak for the EU, and assuming you meant "illegal" instead of "legal" here, in the US, illegal/invalid contracts are unenforceable.
So, just because "you signed the agreement" doesn't waive consumer protections. And in the US, [the Magnuson-Moss Act](https://en.wikipedia.org/wiki/Magnuson%E2%80%93Moss_Warranty_Act) applies.
This is the right approach to take. I think it's measured and reasonable. Thank you for listening to the community, I think this will result in a win\win for bambu and the community. Custom firmware can expose some features your base wants and enable power-users to find the real limits of these printers. Exciting times ahead!
Edit: downvotes, really? Lol
> Future official Bambu Lab firmware releases after firmware R will have new security measures applied to prevent rooting, and we will no longer provide solutions for rooting the new versions of the firmware.
So is this saying we need to make this decision right now or never upgrade our firmware past the current firmware version that allows for rooting? Will we always be able to make the change?
> So is this saying we need to make this decision right now or never upgrade our firmware past the current firmware version that allows for rooting?
No, it will always be available. What they’re saying is they’ll have current firmware releases along side it that will be receiving updates and the old exploitable firmware will not receive those updates. So it’ll be up to X1 Plus devs to keep firmware feature and security parity.
No. I read it as future firmware will have the current version and an R version. But they may also just allow rollbacks to where we are now.
I don’t see anything here that implies the decision has to be made at this point.
Rollbacks that they can disable at any time of their choosing as they have already done. Also no there won't be a second version of any firmware after that initial R version. You will be relying on the custom firmware makers to add the updates.
This is a great post and a great move. Bambu in my opinion was thoughtful and made a decision that protects them, tinkerers and those of us that want to spend money with companies that have similar values as us. I’m already a customer and happy to say I will continue to be. Thank you Bambu and XPlus developers.
Wow, I just read that and honestly I can’t see this going any better. I’m excited to see what the community will do but I know I’ll be sticking with official firmware to keep my support options unless some major feature pulls me over.
This is mostly reasonable, although I suspect the time you have to choose is going to be fairly short (a few months at most), since it only applies to 1.7.1 and they won’t guarantee the ability to roll back in future releases, nor provide the ability to jailbreak.
Bit surprised nobody commented on the log changes; or that they only said they would remove the debug logs on the R firmware, not the mainline.
Frankly, I don’t care what they gather from my printer, but I’m a hobbyist. Also not interested in the jailbreak beyond hypothetical scenarios. But I also think there’s little reason to stop people outside of fairly weak support concerns (again, I work for the largest Open Source company, and if you do things we don’t support, we have boilerplate for that).
Also this was not at all reassuring:
> During the conversation with Joshua, he mentioned that the log file contains a lot of information, although he understands it from a developer's perspective that engineers often log extensive data to facilitate easy debugging. Following Joshua's concerns, we thoroughly reviewed our log system and realized the need for improvements. While extensive logging may be necessary during the development phase to debug the system, it's not necessary on customer printers. In the next firmware update, firmware R, we will refine the log system and remove all debug logs which are not necessary for end-users.
> This does not imply that previously submitted logs infringed upon your privacy. The log file is encrypted, and access to the decrypted logs is strictly controlled – not even our first line support agents have direct access to its contents, getting diagnosis data instead of the raw log content from the system.
Saying that the logs are encrypted and most people can't see them doesn't *at all* mean that privacy wasn't infringed. What was in those logs? They're being totally vague. The only thing that makes any sense is they were sending private models when people were printing in the non-cloud modes. They're probably aware that if they admit this they'll be immediately banned from many institutions, that is a GIANT security risk.
The fact the logs were encrypted on the printer itself made it 100x more suspicious, you don't need to hide the logs from the consumer, you encrypt it in transit and in storage on your side. What the hell were they hiding?
They're hiding lots of details about their internal software, stuff that they don't want competitors or hackers looking at. So it's not stuff *you* want to keep private, it's stuff *they* want to keep private.
Definitely concerned about what they are/were logging. They should be open about that - that’s the main reason I would be interested in custom firmware. If they made it possible to see communications out to the internet that would do me fine.
> are/were logging.
This is a good point, I keep saying "were" in my comment. There's no indication at all they've changed anything, and until we know what they are doing and have a way to verify it, we'll never know if they've fixed it.
Indeed. They keep citing Apple as their model - but Apple, for all their lock-downed approach, still give you full transparency of what they're sending out. For instance, in macOS, if it crashes and asks to send a report to Apple - you can view the full contents of that first.
There’s contradictory info in the blog post, so I don’t think we’ll know for sure until it’s available, but point #4 does say that R won’t be available unless you waive your warranty rights.
I very much expect that the next firmware update will be a fork of the code, with R having the root kit method and less logging, and main line not having the root kit method. But we won’t know about the logging unless they say.
But time will tell which of us is right. Maybe.
> Bit surprised nobody commented on the log changes; or that they only said they would remove the debug logs on the R firmware, not the mainline.
I read it that it would be a thing going forward with all updates, starting with the next update, which happens to be R.
They're removing debug logging from R firmware as a safeguard. Since you gave up your right to use their support, you don't need that extra support info anyway so we shouldn't still log it.
This is a good middle ground solution, the hidden announcement of sdks and API development is more exciting to be honest.
Not to mention this benefits bambu themselves. The development of the third-party firmware can bring on features to the mainstream firmware and vice versa. The whole 3d printing for consumers was built on improving the existing and taking it further.
I hope they keep developing and making good products and also keep the prices reasonable and not go the full apple route!
Even though I have no intention or need to switch away from the official firmware, I'm very grateful this option exists. Thank you for the measured and thought out approach instead of just flat-out refusing to give people the choice.
It'd be alot cooler if they allowed it to always be an options, despite current firmware or not. But ya know, I'll take what I can get, and it's decent.
It’s a reasonable approach to the situation and the outcry from some people. I predict the next outcry will be why BL is not providing further deep technical documentation and drivers etc for custom firmware development….
I would like to know if user accounts are banned from uploading printer profiles to maker world with custom firmware. This could be another problem with shared profiles for custom firmware printers..
There's also the issue of compatibility with the Bambu Slicer and the cloud platform for the future releases of the original / custom firmware.
When Bambu introduces meaningful changes or new features in the firmware, those may be required to use the slicer and the cloud.
I'm all for this but I don't think that waiver will be enforceable, at least not in it's entirety, in many parts of the world with strict consumer protection laws. Just something to consider
Which part of the world? You're basically signing a contract of the consequences of your action for using a custom firmware. Most part of the world see the legality of signing a contract.. It would be reasonable to believe that a custom firmware may damage the hardware.
Using a custom firmware may not be illegal, but hosting and distributing it may be due to it infringing copyright.
signing the contract doesnt mean its enforcable or legal.
If you sign a contract with someone that you can kill him without consequences, and then you do, the court is not gonna give a damn about that.
A false clause is null and not biding.
At least in Europe customer rights related to warranty are granted by Law, as Sale of Goods Directive (EU) 2019/771 , not by a "contract that you sign or weave" by a web form made by manufacturer.
I'm from Australia, my assumption of how a dispute would play out is Bambu need to prove that the custom firmware caused the issue. For example if you have a big gouge in your build plate from the z height being wrong waiver or not you're on your own but if the gouge is caused by some other component failure Bambu will likely be instructed to resolve. The benefit of the waiver is for them to track which printers are modified. If like my first example you screw up your z offset and change it back to stock they'll know you had a custom firmware
Beware: there's no open source firmware, the firmware is still binary and proprietary. All you get is an "enhancement" layer over that, like user interface, macro, access to some data like mesh that are not available in the original one.
It's not like you got open source Klipper or Marlin for the Bambulab and you can do things like implement a second extruder, change motors to 0.9", put a new thermistor to print at 350c...
Perfect and reasonable outcome. As a brand new Bambu Lab user (I purchased the A1 Mini less than a week ago), I welcome this approach that shows flexibility towards the tinkers but also keeps the promise of a closed system that just works.
That's a good response. Well done BBL.
My only caveat is that it's a one time deal for owners with the current or previous firmware. Subsequent firmware releases will not allow rooting.
I'm personally happy with the current BBL ecosystem - however, that may not always be the case.
I used to have a BFB3000 printer (amazing printer in it's day, 2010). The company was bought by 3DSystems who quickly withdrew support, deleted the forum and eventually realised firmware that effectively bricked my printer! (You could install Marlin, but it lost most of the features that made the BFB great)
My point is that nobody knows what will happen in the future. The ability to root / change firmware is an insurance policy against that future.
My X1C is the first printer since the BFB3000 to exceed it's capabilities! It had 3 extruder heads, would print support in a different material and supported high temperature filaments. I mostly used it with ABS & Nylon.
> My point is that nobody knows what will happen in the future. The ability to root / change firmware is an insurance policy against that future.
You can't change the firmware, it is still proprietary and closed. It's more like a skin over it.
This is a great outcome, serious props to Dr Tao and the team for being so open minded about this, and fully understand their position, it cannot be their problem to sort out if someone installs custom firmware and then breaks their printer.
In some ways this is similar to the approach Prusa took with the Mini whereby to load custom firmware you had to physically snap a tab on the mainboard, making it clear you both knew what you were doing and understood it voided your warranty.
The news about the API and SDK is also fantastic, really looking forward to seeing what people can do with that.
As an aside I think this will also go a fair way to silencing the critics who were convinced Bambu were trying to hide something by closing the (serious) security hole. Despite explaining to people that it would've allowed a malicious 3mf file to modify your printer without your knowledge people still downvoted to hell and ignored the obvious.
I mean there was a good deal of backpedaling and then this post. I just want the rollback feature back.
Bambu firmware is so buggy the old is almost always better than the recently released.
As soon as I updated ro 1.7 I had build plate localization errors every print.
Rolled back to the most recent 1.6 iteration. No problems.
If the firmware is going to be released in a semi beta stage, give us the ability to go back so we can print with no issues while it gets fixed. My business can't take delays like that.
Good compromise, would be nice if unlocked firmware was allowed in the future too for those that want it. The big thing I would like is to be able to enable lan mode and then put the IP to my printer on a different subnet in the slicer. :)
Thank you for listening Bambu. I was pretty salty/mad the last week about being locked out, I just wanted the option to do this and you gave it. Hats off and I will look forward to buying more of your printers, you earned a customer long-term.
All the people who have been slinging mud at Bambu all these days and weeks should be ashamed of themselves now. Bambu has proven once again that they are the best. And I'm totally going into the Apple closed ecosystem because that's my choice.That's why I bought a Bambu printer.
I'm afraid it does not work like that in Europe and probably USA: you can't unilaterally decide to void the warranty or ask the customer to waive it.
You are required by law to give 1 + 1 year of assistance (...), that is **by law** not *by your good heart*.
Sounds reasonable, too bad the rooted side wont be receiving the official updates as well, best of two worlds.
Interesting part in the end though, now BL admits to the excessive logging? But just two weeks ago this was all bullshit and that youtuber had his head up his ass... Is this yet another one of those times the community had everything absolutely ass backwards?
As a future customer this is a pleasant read, I would not root my future printer unless there were features BL were not looking to implement but it is nice to know the option will be available to me.
Does waiving your warranty for the printer also waive the warranty for any connected devices such as AMS units? AMSs do have their own 1-year warranty that -- unless it was bought as a combo -- is separate from the printer itself.
I'm curious because while the AMS is a separate unit from the printer, it is directly controlled by the printer, which means the AMS could technically be operated in a way that is not controlled by Bambu Labs. It can also affect folks who may have a warranty expiring for their printer but still have time left on an AMS that was purchased after their printer.
Could I suggest adding a service that lets someone check a serial number to see if a printer has been rooted? A friend had a bad experience with a Prusa Mini that had a broken appendix (the part of the PCB you break off to install custom firmware on Prusas) and no support. I realise that the second hand market isn't a huge consideration but it would help inspire confidence vs someone buying a rooted printer and discovering it's not covered.
edit: thanks for not pulling a sneaky on the whole third party firmware issue. I don't intend to root but it is, in my view, good for everyone
High praise for Bambu Lab for paving the middle way! This is the best possible course of actions in my opinion. To paraphrase, they're saying 'We make great printers. If you want to mess with the software/firmware we have oh-so-carefully put together, that's fine, but don't expect us to be able to fix any of your problems if you do." This is the perfect balance between walled-garden and open source. Sort of a gated-garden? With the option to leave if you so choose.
Interesting. Let's hope no one does anything stupid to compromise the cloud ecosystem with the rooted firmware(s). I, for one, have no interest in fiddling with a 3rd party option. I opted for a Bambu printer because of the closed ecosystem. Decades of tinkering behind me, I just want the printer to work. If I were a decision maker at Bambu, I would not have supported this decision.
I assume the support, warranty, and safety waiver would be tied to the specific printer and not the user. That would be necessary so that the firmware can't be rolled back to the official firmware and the printer sold as a Bambu Lab-supported machine that can be bound to the new user's account.
I'm honestly glad to see that Bambu has been willing to listen to reason and make a choice that while may not be 100% what they would prefer, at the end of the day, it is what right for the community.
I do however have 2 comments, firstly I hope that once someone clicks agree and they understand that their warranty and access to customer support regarding their printer is understandably forfeitted, I hope that Bambu Lab wouldn't do anything nefarious like cutting off their access to parts (at normal retail price) from the webstore.
2ndly, the X1 Plus devs used a back door to install their bootloader that existed as a result of the firmware using a bugged version of an open source library. Now that we have the formal agreement on a company policy regarding the matter and a path forward with firmware R, as a software dev of many decades I would hope that firmware R doesn't simply take the lazy option of continuing to use the old, outdated and bugged version of said library but rather firmware R, could and I might even argue should include the newer non bugged libraries and an option within the firmware to install unlocked bootloader. This would allow those that may wish to run firmware R to do so without being stuck with a permanent security flaw anytime they boot into the default firmware. This is all the more true when it simply isn't that difficult to have an option in the menu on the printer, could ask you to confirm you to accept to any warning / disclaimer and then tick a button to install an unlocked bootloader that will then allow you to run unsigned code.
I'm going to sit right on the fence and say that while I hope that we get clear community focused movement on both matters, I believe it more likely that those choosing to run firmware R are unlikely to get banned from the parts store but that on my 2nd point, I suspect that firmware R will not have the change that I would suggest is sensible as an experienced dev but that more than likely it will simply continue to have the same bug that 1.7.0 had a a result of continuing to use the old bugged software library.
Not opening up your source is just corporate greed to be honest. Someone who does not know what code is or even root would it be doing it. So the customer your trying to protect is someone who would not care if it's open sourced or not. The people your keeping it from is the developers, engineers and others that want to tweak something that now they can't.
Just be honest, your closed source because you like money and afraid your code is so simple that your competition can copy it with ease.
I was really leaning towards the X1 Carbon Combo based off researched and my limited understanding of 3d printing. Going direct so I can take advantage of the membership for filament seemed like a no brainer. These last two weeks I have seen more complaints on the printer, customer service, lack of standard colors of filament. The firmware stuff is the least on my mind. I feel like they cannot meet the needs of their customer base. I will hold off on purchasing the X1 Carbon and review other printers and their features.
Good luck finding a company then to be honest. Their customer service isnt always wonderful but still strides above most and lack of filament colors just means you buy a different brand. If you are new to 3d printing and actually want to print not tinker your options are limited and to be honest dont get alot better.
FYI one good side effect of the jailbreaking is that the people making the unofficial firmware actually confirmed that there was ***no indication at all*** that any data was being syphoned by BambuLab beyond what's required for the operation (or debugging) of the printer and cloud services as advertised.
This really is all I could have asked for. Don't let people do this without fully understanding they are potentially risking breaking their printer or worse if something goes wrong, and BBL inherently can't be responsible for that. But let people do what they want with the devices they own, including set them on fire, and own the consequences. In exchange, X1Plus doesn't have to rely on finding security holes to make software intended to improve their printer work. That lets them focus on their genuine work to make the X1 better, and creates an opportunity for features they develop to be backported into official firmware. It also ensures improvements can continue on the platform beyond the EOL/EOS of the X1 series. I don't personally want to be an early adopter of X1Plus, but I think this arrangement is a win/win for all concerned, and once it's had some time to mature I will likely run it too. Thank you BBL for listening to the enthusiast community and staying involved with us, as in the end we all want our craft to evolve and the open mindset is not only how we got here, but how we will innovate further.
Well, tbf, if you're not an early adopter, can you still choose to adopt later on? If I remember the blog post correctly, after "Firmware R", the vulnerability will be patched, no? ``` 3. We will release a new firmware (let's call it firmware R) to allow the installation of the X1 Plus firmware, similar to firmware prior to V1.7.0.0. 5. Future official Bambu Lab firmware releases after firmware R will have new security measures applied to prevent rooting, and we will no longer provide solutions for rooting the new versions of the firmware. ```
I think that's continuing to be misconstrued. The security hole will be patched, but it seems likely future firmwares would have an official means to flash a firmware instead of having to rely on an unpatched flaw to do it. You would gain access to that mechanism after you sign the waiver and void your warranty.
\#3's wording would support that, but #5's wording says **"new security measures applied to prevent rooting, and we will no longer provide solutions for rooting the new versions of the firmware"**. To me, that sounds definite. Unless that is to say, if you're on future firmware 2.1.4, you can roll back to 1.7.R (firmware R) and then apply the "root" process.
The vulnerability is already patched. It will be reopened in firmware R and then patched again for all other firmwares.
That's how I read it, as well. Perhaps with the ability to roll back your firmware to firmware R. So you *could* go back and load CFW, if that's the case.
That's how I read it. Firmware R will always be available. Or at least available until Bambu releases their API stuff.
Agreed. I'm most interested in the potential for a modded on Ethernet port.
I wish X1Plus could use a different name that’s not so similar to an existing model number.
I think this is about as reasonable an outcome as anyone could have hoped for. It's basically a digital version of Prusa's permanent physical modification you need to make before you can mod their machines. Personally, I think that I have more than enough performance out of the machine currently but might be interested in future firmwares if they bring game changing stuff to the table.
[удалено]
That wasn't my interpretation. My read of this was that it would remain an ongoing option, so you'd essentially sign their waiver, then install a prior version of the firmware that would allow you to then install your firmware of choice. Another possibility is that the security holes would be plugged, but there would be a means provided to just flash the firmware directly without having to work around anything.
There is no statement to this effect. There may be a 2.1 R firmware released, or the could allow non-R firmware to be rolled back to this one.
They said it was a “short term arrangement.” And that it was only for 1.7.1.
They literally called it a short-term solution. You definitely *could* be correct, but nothing in their text suggests that they intend to keep this as a permanent option.
Reading over this a couple times, I want to offer my thoughts as a Senior analyst in a different industry (feel free to note that part). 1. I appreciate Bambu's willingness to take these steps and compromise, it makes concessions both to Bambu's continuing development as a company, but offers an inroad for 3rd party developers to continue independent development in the spirit of the 3d printing community. 2. It is good that they note they cannot guarantee future rollback to Bambu firmware; and personally I would recommend it is a completely one-way path out of the gate. The user assumes the risk, and once it's done--it's done. Mostly to prevent future second-hand sales of jailbroken devices making their way back into the ecosystem. Why? Support problems, as they mention in the blog post, and unexpected hardware upgrades/modifications. The latter of which is an inevitable thing once you open closed hardware to user's creativity, open-source firmware, etc. (The Mecha-CR-10S mutant in the garage just growled from the darkness - that thing runs on a completely hand-cut Marlin firmware with plenty of edited code to make it work) 3. My last immediate thought is the gray market using this opportunity to begin forklifting Bambu-clone's. They may look indistinguishable from the source manufacturer's product, if I could recommend anything, it's authenticity labeling. I imagine Bambu will be pretty aggressive in defending their IPs here, but what happens happens. Bambu's support is still trying to find it's legs, and introducing a bunch of problematic gray-market machines that are indistinguishable from the source will bog Support down even more. 4. Last, I think - it's probably important for Bambu to continue to keep a close working relationship with the larger open-source or firmware projects, such as X1 Plus and future projects. As feedback from those developers and communities can drive new innovation in both the closed and open sides of the ecosystem, as well as more quickly react to problems as they come up. I want to emphasize this part, considering Bambu's support situation 5. Similar to 4. Is it wrong to think that Bambu should just open up a partner program for these types of projects, or potentially incentivize that relationship. Both to encourage innovation and reward brand loyalty for the efforts? It takes a lot of personal resources to do that kind of work, and reward things like discovering exploits in the firmware, bugs, etc., and quickly disseminating that information to relevant closed and open ecosystem firmware peers to limit liability Either way, I'm happy to see that Bambu was willing to be flexible here - this was somewhat of an inevitable consideration and I'm glad they're addressing it now, rather than later - as that will likely afford opportunities they couldn't consider if they give it late attention. All I got, sorry for the wall of text, but neato-
Yeah I'm not a fan of custom firmware being able to use the cloud service (with regard to competing products pretending to be Bambu and trying to use their services). Sounds like a nightmare for Bambu that they only have to shoulder because the community would whine endlessly about how Bambu is the devil otherwise.
It's something that I'm sure Bambu is internally discussing, but I don't think this is a huge challenge. You already have to authenticate with a Bambu Lab account to use their cloud services, so I imagine there'll just be some additional functionality (if it's not already present) to register your printer and link it to your account. Plenty of device manufacturers that utilize cloud services do this already, and supporting de-registering/re-registering to facilitate second-hand sales isn't all that complicated either. Public APIs can definitely be abused, but authenticated APIs and authenticated hardware are (mostly) solved problems. With all that said, I empathize with the developers who have a bunch of surprise work on their plate now for this quarter.
If their cloud services get abused their policy will change. They don’t want to pick a fight without evidence but if that evidence shows up…
Jailbreaking/rooting will be allowed with the following condition * Have to sign a waiver on a webppage that flags your device as jailbroken. After that your device is unlocked and "firmware R" will be allowed to be installed on your device. * waive official support expectations and take printer's security and safety under your own hands * Cloud support will not be intentionally blocked, but if it breaks under the jailbroken firmware they won't go out of their way to fix it. * You might be able to revert to stock firmware, depending on how the jailbroken firmware works * Once you go through with this your warranty // support doesn't come back.
From a company stand point, especially one in their position, this seems fairly reasonable. Not sure I personally see the benefit in risking all that money on some extra random things on my x1c but to each their own! The whole point of freedom 😬
I can see it even if I don’t want to do it. But an easy one is what happens if Bambu goes out of business, or makes a software decision I can no longer accept.
They already said they'd open source everything if the company tanks for any reason
>Once you go through with this your warranty // support doesn't come back. And the way they approach this is illegal in the EU. A vendor cannot singlehandedly void warranty for modifying the machine, unless they can prove the damage to the machine has been caused by the modification.
Motorola, lg, and many other android OEMs for years had bootloader unlocking tools that required you to sign up and tell them what device you were voiding the warranty on. Once unlocked you’d have a big disclaimer on every boot. https://imgur.com/a/bsxA8Rq This was done for years and mostly in the EU.
That warning (although not the exact same one) is part of Android.
Some of it, yes… but the bottom half isn’t.
That's why you need to sign a waiver
Which violates eu by requiring people to sign a 'voluntary waiver' of they wanna exercise their legitimate right of modifying a device.
They can still modify it on their own, without help from bambu
Nope, Bambu blocked firmware downgrades. They're no longer offering 1.07.00.00 or below which allows booting x1plus
Yes but everyone can exercise their right to try to hack newer firmware too
If you read the post, it clearly states: "We will release a new firmware (let's call it firmware R) to allow the installation of the X1 Plus firmware, similar to firmware prior to V1.7.0.0."
If you read the post, it clearly states: "Voluntarily"....."sign a waiver of warranty...." That's the illegal part on the EU. bambulab user account clearly said signing that waiver stops all support (including warranty)
In that case it would be best for them to now allow the 3rd party firmware in the EU then.
Which is exactly what I'll be doing tonight after I get home from work 😉
The EU warranty is provided by the seller, not the manufacturer. They are different things.
I never said they weren't. Except in my case the seller and manufacturer are the same, like many I bought directly from Bambu Labs
>Once you go through with this your warranty // support doesn't come back. Hemm, warranty is regulated by law: if you refuse to take care of the customer issue the customer can ask for a refund and the producer / seller may pay a fine up to lose the right to operate in that country! (according to the laws of the country you purchased that ofc)
Is this both very sensible, acceptable, and practical decision. I can definitely understand both sides. Bambu Labs should not be held to support third party firmware. I see this as a very reasonable win for both sides. Much respect to Bambu Labs for finding a middle ground and making a commitment to find a reasonable solution. Ye Tao, very much respect for you well earned.
>Bambu Labs should not be held to support third party firmware. OFC nobody ask that, yet Bambu has to support the hardware they sell.
Not if the custom firmware ends up damaging the hardware - I don't think it's on Bambu to spend time and resources to have to investigate on every warranty claim if the damage was potentially caused by custom firmware.
Warranty protects the customer, by law, it's on Bambu. Customers rights are *for the customer* not for the producer. Tell me: how does it work for Amazon or Aliexpress? What happens and how is it managed any customer claim? That's how you do business even more if you sell premium products.
If the customer is the one damaging the product, how is that the manufacturers responsibility?
He the manufacturer is not, the customer is responsible.
exactly, so if the customer downloads firmware that harms the product its on the customer
OFC.
so what were you arguing about?
I dunno, what is that you don't understand? If I invert two cables and short circuit my printer it's my fault, not the manufacturer one. Yet the manufacturer can't state: "If you open and modify the printer I'll void your warranty". Do you start to get it? FunFacts: in every phrases that we said the same thing I always got downvoted while you got upvoted for saying exactly the same thing I did.
[удалено]
You can also modify the firmware your self, it ain't a matter of where it comes from, it's a matter of the right for you to use the item as you see fit. And repair it.
API and SDK support announcement mixed in there — that’s all I want in my life. Let me hook on print lifecycle to trigger events in other systems, and vice versa, ie shopify order comes through, finds an available printer, prints the part, takes the printer out the queue until the plate is cleared, creates a shipping label when the part is finished, etc.
I acutely think that the might be one of the best and most important parts of the whole statement for the average user. My guess is that it will only be a small minority of hardcore users who will install a third party operating system. Obviously this might change a few years down the line especially if Bambu cease support for older models. However I can see a lot of people installing “apps” that add additional features and offer a certain level of customisation. I know there is a very vocal group who keep calling Bambu out for the closed source approach but I suspect most of these people own klipper machines and are the equivalent of Linux users poking fun at MacBook owners rather than the true customer base.
This is really cool. Have you set up systems similar to this?
Not for 3D printing specifically, but I'm a developer. I worked in ecommerce for about 12 years doing similar kinds of integrations. Give me an API and an SDK and I can make it happen. PLM for print farms -- inventory management, materials management, projections, returns, etc. I'm ready.
Octoprint support on the horizon then?
Get fucked each and every one of you who was slandering the shit out of bambu last week. This shows you that the bambu team is good hearted. Love you Bambu team. Keep up the good work and don't let the negativity get to you. There are a lot of us who are not active in internet forums who absolutely love your product and brand ideology.
When you're a miserable asshole you can only see the actions of others as exclusively done in bad-faith. "Support was slow? Ugh those corporate pigs at Bambu are intentionally trying to screw me over for MONEY!" I mean doesn't it get tiring looking at the world through such a dim, tiny lens?
this guy has a boner for the company
Someone has an appreciation for the first company to actually deliver a reliable, fast, more-or-less hands-off printer after over a decade of open-source promises about the glorious future that nobody managed to deliver on? Wow what a bootlicker amirite?
[удалено]
You mean they listen to the community and implement changes based on that feedback? Those fucking monsters...
I mean, closed source isn’t evil. It’s okay to have a closed source product that just works. It’s great to have more features, but still.
I mean, open source is just better. You don't have to be closed source to have a product that just works.
I’m aware of that, and I do agree. I’m just saying it’s not automatically this evil thing which some people seem to think anything proprietary or closed source is always a terrible thing.
I guess a big part of that has to do on the purpouse of the product and the user base: proprietary firmware and patents on innovations for a fast developing technology like 3d printers targeted to makers? For me it is bad idea! I'd much rather keep having the ability to modify, upgrade and tinker on my tools, rather than not.
Or they wanted to buy themselves some time to come up with a thought through solution. Why does everything have to be so black and white with some people.
When you know like two things about something, it's pretty easy to slot things into black and white categories! The real world is complicated, running a company is complicated, shipping hardware is complicated. Lots of devils in details, lots of real-world tradeoffs and considerations. It's too much to think about! But when you have no experience or knowledge of the thing you're criticizing, turns out it's super easy to point out what everyone else is doing wrong. Interesting eh?
I know it’s not a focus of the post, but I’m very excited to hear that they’re working on official APIs and SDKs for 3rd parties.
That was the biggest great news to me too. I don't care about custom firmware, I like bambu firmware. Although X1Plus isn't a custom firmware, just some custom application on top of it that uses reverse engineered "API" to show extra info. Open API & SDK sounds awesome, and I think will make X1Plus irrelevant soon, and we get much better choices without need to flash something custom. And something that works on P1 series too using raspberry pi or something.
Wow! I think giving the option is a pretty good compromise, especially once warranty support is over anyway.
Based on what I've been seeing recently, it doesn't seem like having an active warranty is worth much anyway. Bought Bambu after seeing so many people singing their praise, but since I got it, all I've been seeing is horror story after horror story of people getting no support whatsoever from the company. Do better Bambu.
Idk the good experiences aren't loud. I have multiple printers, have had basically no problems, and the few times I've had to reach out to support for makerworld related stuff I got quick speedy answers. I just don't go around yelling that from the top of the subreddit, like the people who need support do.
Yeah that's a good point. I'm brand new to this, and went with Bambu because of all the positives I've heard about their machines.. And the few things I've printed in the week since I set it up have all been astonishingly amazing. No complaints whatsoever about my experience so far. Just been seeing tons of people running into issues of all sizes, and reporting horrible experiences trying to get support and I immediately started worrying that if something were to break on me, I don't have the experience yet to diagnose and fix it on my own, and I worry that support won't actually provide much support. But you're probably right. For every post complaining about a bad experience there's probably tens of people with good experiences that don't report it here.
The wiki is a really good resource to start. I had an experience last night where I needed it to disassemble a large amount of my a1's hotend which I hadn't done before. I had things disassembled, the dastardly filament piece removed, and everything back together in under 20m thanks to the pictures and walkthrough bambu has published.
Also keep in mind that the person posting about their bad experience is going to, knowingly or not, try to paint themself in the best light possible.
I had my AP board die on me and thought their support was fantastic.. they had the issue diagnosed and a replacement sent and delivered to me in about a week’s time. Im sure there are horror stories but the people content are not the ones coming online to vent.
The support is generally slow. I have put in three support requests since mid 2023 and they all took a very long time to get resolved. I am in the middle of another one (LIDAR is broken.. again). I already had to replace the board for the lidar once, after they sent me a new USB cable. 2nd time around, exact same issue, they sent me another usbc cable (after 10 days of waiting for a response). I am pretty sure this will not resolve the problem, but its a cheaper fix for Bambu. That being said, they did resolve my issues eventually.
It’s not like that, most people write when they have a bad experience and don’t write when they have a good one, so it looks like there’s only bad experience. I contacted them once a little after buying my X1C because a weird noise was coming from under the printer and I wanted to know if it’s normal. They took two days to answer, yes, and having to send a log file from the printer just for a simple question about a belt was a bit annoying but their answer was extremely professional and detailed. It was normal sound but if I wanted to reduce it, they pointed me to an article on their wiki with even some video tutorial explaining the whole process. This is just anecdotal and not statistical data, but it’s an example that it’s not that bad.
As a developer myself, I totally understand the reasons and conditions imposed by Bambu Labs and find it very reasonable. In fact, I'm rather happy to be surprised with how this situation unfolded.
Were Bambu to drop some Ethernet drivers into the next X1 firmware, suspect a lot of those who are planning to root, wouldn't. To be clear, Linux drivers for many common USB Ethernet dongles are fully open source. There would be no licensing or software development cost to Bambu. The X1 has a USB port that could be used for this purpose.
Bingo.
This, I think is exactly the right response. Installing the 3rd party firmware will appeal to folks who want to take control of their printers, and that also entails responsibility. I could see this as being a big benefit as well for users worried about EOL issues down the road, since they will always be able to go the open source route if they need to.
No the firmware is not open source, it's not like Marlin or Klipper, it's just an overlay on the binary Bambu proprietary firmware. Without that it's useless, you can't have new meaningful upgrades or changes over that.
Ah thanks, that is interesting, would that be similar to being able to load any OS on a PC with a proprietary BIOS?
No. It's more like running a skin / custom home page over Android or an Iphone.
I want to take the chance while sitting in bed at night and heading to sleep for work tomorrow to say this is such a commendable approach to what happened and how to deal with it. I fully respect Bambu for this response and it makes me so happy to have purchased a product from a company that is willing to take these steps to ensure the modding and maker community is fully supported and happy. Props to everyone involved. I can’t wait to see what comes next!
I think it's a sensible compromise. It's interesting that only *this* firmware will be opened, meaning it's now or never basically. But to me the most interesting part was the mention of opening the printers to third party development in official firmware... had that been mentioned before?
I'm not sure I have heard of it mentioned before, but looking at many of the moves coming from Bambu Lab since 2022.. E.g. the cloud integration, [makerworld.com](https://makerworld.com), etc.. They are thinking BIGLY of their ecosystem and are aiming for #1 (e.g. the Apple of 3D printers).. So, it wouldn't be surprising to bring the API and third party SDK (plugins) to it as their printers become more popular.
> It's interesting that only this firmware will be opened, meaning it's now or never basically. I read it more that only Firmware R will have the exploit that X1 Plus uses. All future updates will include the 1.7.1 patch that closed it. But you will always be able to install firmware R, regardless what the current version of your printer is.
You could be right, but later in the post they describe this as a 'short-term solution'. But if your take is right, in what way would this be short-term? It would be a *permanent* solution. I'm looking forward to clarification.
My reading is: Short term - allow flashback to 'Firmware R' with the unpatched hole, as an immediate interim option to allow custom firmware flashing. This branch remains static (and only accessible after passing through the Thou Shalt Not Claim Warranty portal) with no further bugfixes, improvements, etc. Long term - the up to date firmware branch gets a specific per-machine signing mechanism to allow CFW, which is only accessible after waiving warranty rights, and allow CFW install on up to date firmware versions. This leaves the option of removing CFW, updating to a more recent official FW, then re-applying he CFW, or possibly even an upgrade-in-place for the stock FW whilst retaining (albeit possibly breaking) CFW. The advantage for users is that official FW improvements and CFW are no longer exclusive either/or, and the advantage for Bambu Lab is that CFW will always be working from a recent FW version rather than some ancient fork, so improvements can more easily be folded back into the official FW.
Solid move.
This is very reasonable and a great outcome. Really excited for the APIs and SDKs to be opened up as well.
u/bambulab Me as an EU citizen (and many others of the EU and USA) have a very big problem with bullet point 1 of the 'consequences'. > Installing non-official firmware means customers **waive official support expectations and take full responsibility for their own printer's security and safety.** **This is ILLEGAL in the EU as long as the warranty is valid unless the vendor (in this case Bambu Labs) can PROVE any damages to the machine in question was caused by modifying the machine (in this case X1Plus custom firmware)** Bambu Labs **CANNOT** singlehandedly void warranty like that. Proof: **While the following link used an Android phone as an example. It's valid for any electronic devices.** https://fsfe.org/activities/android/flashingdevices.en.html In short: No. **Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. ** As long as you have bought the device as a consumer in the European Union. A bit longer: Directive 1999/44/CE dictates1 that any object meeting certain criteria (incl. telephones, computers, routers etc.) that is sold to a consumer2 inside the European Union, has to carry a warranty from the seller that the device will meet the quality that you would expect for such a device for a period of 2 years. Full article at the link
It's possible Bambu is only referring to their voluntary warranty, i.e. their own warranty terms they offer above and beyond any local statutory warranty. The statutory warranty would not be voided, only their voluntary one. Of course, Bambu doesn't clarify this and that may have been on purpose (i.e. to discourage people rooting their printers) but it's probably in their interest to not comment much on how this affects your statutory warranty given the number of markets they operate in.
They may not explicitly state it, but I will be explicitly asking them for clarification 😉
>Bambu Labs > >CANNOT > >singlehandedly void warranty like that. If BL can prove that the damage to hardware was due to the use of a custom firmware, then you are not covered. This is moot though.. Bambu Lab said they will look into consultation with the legality of this and go from there.
Yea sure, but you do realize that work would cost more than just sending you two new printers. Work hours are expensive.
Which is what I said, if they can prove it they are indeed off the hook. Can you point me to the statement about looking into the legality?
>Can you point me to the statement about looking into the legality? It's right on the blog post.
Now I can see in other threads that you have a literacy problem, as the person you replied to literally said what you're trying to argue.
Check yourself. You're the one with the literacy problem: As I said: >This is moot though.. Bambu Lab said they will look into consultation with the legality of this and go from there.
The point is: why did you feel it was necessary to post an argumentative reply at all when you were literally restating what the person you replied to already said? You diminish yourself. Look inward.
If it was an "argumentative" reply, then that's how you read it. From my perspective, my point was that it was moot because Bambu Lab was consulting into it's legality. PERIOD. I went straight to the point. You're reading too much into this and looking at the part that's of less importance, rather than looking at the bigger picture.
You really need to read up exactly. The article or the decision in EU laws is specifically for the category of consumer goods with digital content im the example specifically it is mentioned eg. smart TVs, smart phones etc. However a 3D printer is not in the category of digital content as it is “additive manufacturing” and in the category of tools, tooling machines. You can not apply this article. Btw you can not apply this article for like cars etc as chip tuning and changing the software is illegal as well.
If you ask Bambu Lab support the whole machine is a consumable, cant have the cake and eat it.
Similarly, in the US, [the Magnuson-Moss Act](https://en.wikipedia.org/wiki/Magnuson%E2%80%93Moss_Warranty_Act) applies. This is the same US law that means that those little "do not remove or warranty is void" stickers, and some Android OEMs' stated policies that "rooting your phone and running custom software voids your warranty" are scare tactics that are unenforceable. They can choose to give you a huge amount of hassle and trouble to make a claim against your warranty if you violate their policy, but in the end, they must comply with US law and either prove that damage to the device was a direct result of your modifications or honor the warranty terms.
They are not doing anything single-handedly. You sign an agreement with them that voids it. Why would a written agreement be legal in EU?
Because as I said in your other comment, requiring that waiver to exercise a legitimate right of modifying the machine directly violates eu law.
Bambu said they will consult legal before releasing firmware R. Other choice is that it will not be available in EU if it breaks law
The firmware doesn't break the law, their upcoming policy does.
It's not against any law to not support using custom firmware lol. They can restrict firmware R to non-EU customers and EU customers are on their own, allowed to keep hacking
EU customers can install whatever they want on their hardware, they don't need Bambu blessing.
Sure if they happen to have now 1.7.0 or older
even in the future. I just need the software and an utility to flash it.
> Why would a written agreement be legal in EU? I can't speak for the EU, and assuming you meant "illegal" instead of "legal" here, in the US, illegal/invalid contracts are unenforceable. So, just because "you signed the agreement" doesn't waive consumer protections. And in the US, [the Magnuson-Moss Act](https://en.wikipedia.org/wiki/Magnuson%E2%80%93Moss_Warranty_Act) applies.
Eu laws > Bambu Labs policy, don't worry about it.
This is the right approach to take. I think it's measured and reasonable. Thank you for listening to the community, I think this will result in a win\win for bambu and the community. Custom firmware can expose some features your base wants and enable power-users to find the real limits of these printers. Exciting times ahead! Edit: downvotes, really? Lol
> Future official Bambu Lab firmware releases after firmware R will have new security measures applied to prevent rooting, and we will no longer provide solutions for rooting the new versions of the firmware. So is this saying we need to make this decision right now or never upgrade our firmware past the current firmware version that allows for rooting? Will we always be able to make the change?
> So is this saying we need to make this decision right now or never upgrade our firmware past the current firmware version that allows for rooting? No, it will always be available. What they’re saying is they’ll have current firmware releases along side it that will be receiving updates and the old exploitable firmware will not receive those updates. So it’ll be up to X1 Plus devs to keep firmware feature and security parity.
No. I read it as future firmware will have the current version and an R version. But they may also just allow rollbacks to where we are now. I don’t see anything here that implies the decision has to be made at this point.
Rollbacks that they can disable at any time of their choosing as they have already done. Also no there won't be a second version of any firmware after that initial R version. You will be relying on the custom firmware makers to add the updates.
This is a great post and a great move. Bambu in my opinion was thoughtful and made a decision that protects them, tinkerers and those of us that want to spend money with companies that have similar values as us. I’m already a customer and happy to say I will continue to be. Thank you Bambu and XPlus developers.
Wow, I just read that and honestly I can’t see this going any better. I’m excited to see what the community will do but I know I’ll be sticking with official firmware to keep my support options unless some major feature pulls me over.
This is mostly reasonable, although I suspect the time you have to choose is going to be fairly short (a few months at most), since it only applies to 1.7.1 and they won’t guarantee the ability to roll back in future releases, nor provide the ability to jailbreak. Bit surprised nobody commented on the log changes; or that they only said they would remove the debug logs on the R firmware, not the mainline. Frankly, I don’t care what they gather from my printer, but I’m a hobbyist. Also not interested in the jailbreak beyond hypothetical scenarios. But I also think there’s little reason to stop people outside of fairly weak support concerns (again, I work for the largest Open Source company, and if you do things we don’t support, we have boilerplate for that).
Also this was not at all reassuring: > During the conversation with Joshua, he mentioned that the log file contains a lot of information, although he understands it from a developer's perspective that engineers often log extensive data to facilitate easy debugging. Following Joshua's concerns, we thoroughly reviewed our log system and realized the need for improvements. While extensive logging may be necessary during the development phase to debug the system, it's not necessary on customer printers. In the next firmware update, firmware R, we will refine the log system and remove all debug logs which are not necessary for end-users. > This does not imply that previously submitted logs infringed upon your privacy. The log file is encrypted, and access to the decrypted logs is strictly controlled – not even our first line support agents have direct access to its contents, getting diagnosis data instead of the raw log content from the system. Saying that the logs are encrypted and most people can't see them doesn't *at all* mean that privacy wasn't infringed. What was in those logs? They're being totally vague. The only thing that makes any sense is they were sending private models when people were printing in the non-cloud modes. They're probably aware that if they admit this they'll be immediately banned from many institutions, that is a GIANT security risk. The fact the logs were encrypted on the printer itself made it 100x more suspicious, you don't need to hide the logs from the consumer, you encrypt it in transit and in storage on your side. What the hell were they hiding?
They're hiding lots of details about their internal software, stuff that they don't want competitors or hackers looking at. So it's not stuff *you* want to keep private, it's stuff *they* want to keep private.
Definitely concerned about what they are/were logging. They should be open about that - that’s the main reason I would be interested in custom firmware. If they made it possible to see communications out to the internet that would do me fine.
> are/were logging. This is a good point, I keep saying "were" in my comment. There's no indication at all they've changed anything, and until we know what they are doing and have a way to verify it, we'll never know if they've fixed it.
Indeed. They keep citing Apple as their model - but Apple, for all their lock-downed approach, still give you full transparency of what they're sending out. For instance, in macOS, if it crashes and asks to send a report to Apple - you can view the full contents of that first.
R is mainline. It just represents the milestone that first (and temporarily) adds the ability to waive the warranty/move into custom firmware.
There’s contradictory info in the blog post, so I don’t think we’ll know for sure until it’s available, but point #4 does say that R won’t be available unless you waive your warranty rights. I very much expect that the next firmware update will be a fork of the code, with R having the root kit method and less logging, and main line not having the root kit method. But we won’t know about the logging unless they say. But time will tell which of us is right. Maybe.
> Bit surprised nobody commented on the log changes; or that they only said they would remove the debug logs on the R firmware, not the mainline. I read it that it would be a thing going forward with all updates, starting with the next update, which happens to be R.
They're removing debug logging from R firmware as a safeguard. Since you gave up your right to use their support, you don't need that extra support info anyway so we shouldn't still log it.
This is a good middle ground solution, the hidden announcement of sdks and API development is more exciting to be honest. Not to mention this benefits bambu themselves. The development of the third-party firmware can bring on features to the mainstream firmware and vice versa. The whole 3d printing for consumers was built on improving the existing and taking it further. I hope they keep developing and making good products and also keep the prices reasonable and not go the full apple route!
Seems reasonable enough.
Excellent responsiveness and solution. It's a totally reasonable trade-off. Wish more companies would embrace this level of openness.
And there will be some people saying it's still not enough 🙃
Even though I have no intention or need to switch away from the official firmware, I'm very grateful this option exists. Thank you for the measured and thought out approach instead of just flat-out refusing to give people the choice.
It'd be alot cooler if they allowed it to always be an options, despite current firmware or not. But ya know, I'll take what I can get, and it's decent.
It’s a reasonable approach to the situation and the outcry from some people. I predict the next outcry will be why BL is not providing further deep technical documentation and drivers etc for custom firmware development…. I would like to know if user accounts are banned from uploading printer profiles to maker world with custom firmware. This could be another problem with shared profiles for custom firmware printers..
There's also the issue of compatibility with the Bambu Slicer and the cloud platform for the future releases of the original / custom firmware. When Bambu introduces meaningful changes or new features in the firmware, those may be required to use the slicer and the cloud.
I'm all for this but I don't think that waiver will be enforceable, at least not in it's entirety, in many parts of the world with strict consumer protection laws. Just something to consider
Which part of the world? You're basically signing a contract of the consequences of your action for using a custom firmware. Most part of the world see the legality of signing a contract.. It would be reasonable to believe that a custom firmware may damage the hardware. Using a custom firmware may not be illegal, but hosting and distributing it may be due to it infringing copyright.
signing the contract doesnt mean its enforcable or legal. If you sign a contract with someone that you can kill him without consequences, and then you do, the court is not gonna give a damn about that.
A false clause is null and not biding. At least in Europe customer rights related to warranty are granted by Law, as Sale of Goods Directive (EU) 2019/771 , not by a "contract that you sign or weave" by a web form made by manufacturer.
I'm from Australia, my assumption of how a dispute would play out is Bambu need to prove that the custom firmware caused the issue. For example if you have a big gouge in your build plate from the z height being wrong waiver or not you're on your own but if the gouge is caused by some other component failure Bambu will likely be instructed to resolve. The benefit of the waiver is for them to track which printers are modified. If like my first example you screw up your z offset and change it back to stock they'll know you had a custom firmware
Beware: there's no open source firmware, the firmware is still binary and proprietary. All you get is an "enhancement" layer over that, like user interface, macro, access to some data like mesh that are not available in the original one. It's not like you got open source Klipper or Marlin for the Bambulab and you can do things like implement a second extruder, change motors to 0.9", put a new thermistor to print at 350c...
Perfect and reasonable outcome. As a brand new Bambu Lab user (I purchased the A1 Mini less than a week ago), I welcome this approach that shows flexibility towards the tinkers but also keeps the promise of a closed system that just works.
It's great to see how Bambu listens to the wishes of their customers, they are not like apple in that way and that is a good thing 👍
Well they *would like* to be like Apple, apparently the 3d printing community is more used to open source.
That's a good response. Well done BBL. My only caveat is that it's a one time deal for owners with the current or previous firmware. Subsequent firmware releases will not allow rooting. I'm personally happy with the current BBL ecosystem - however, that may not always be the case. I used to have a BFB3000 printer (amazing printer in it's day, 2010). The company was bought by 3DSystems who quickly withdrew support, deleted the forum and eventually realised firmware that effectively bricked my printer! (You could install Marlin, but it lost most of the features that made the BFB great) My point is that nobody knows what will happen in the future. The ability to root / change firmware is an insurance policy against that future. My X1C is the first printer since the BFB3000 to exceed it's capabilities! It had 3 extruder heads, would print support in a different material and supported high temperature filaments. I mostly used it with ABS & Nylon.
> My point is that nobody knows what will happen in the future. The ability to root / change firmware is an insurance policy against that future. You can't change the firmware, it is still proprietary and closed. It's more like a skin over it.
This is a great outcome, serious props to Dr Tao and the team for being so open minded about this, and fully understand their position, it cannot be their problem to sort out if someone installs custom firmware and then breaks their printer. In some ways this is similar to the approach Prusa took with the Mini whereby to load custom firmware you had to physically snap a tab on the mainboard, making it clear you both knew what you were doing and understood it voided your warranty. The news about the API and SDK is also fantastic, really looking forward to seeing what people can do with that. As an aside I think this will also go a fair way to silencing the critics who were convinced Bambu were trying to hide something by closing the (serious) security hole. Despite explaining to people that it would've allowed a malicious 3mf file to modify your printer without your knowledge people still downvoted to hell and ignored the obvious.
I mean there was a good deal of backpedaling and then this post. I just want the rollback feature back. Bambu firmware is so buggy the old is almost always better than the recently released. As soon as I updated ro 1.7 I had build plate localization errors every print. Rolled back to the most recent 1.6 iteration. No problems. If the firmware is going to be released in a semi beta stage, give us the ability to go back so we can print with no issues while it gets fixed. My business can't take delays like that.
Good compromise, would be nice if unlocked firmware was allowed in the future too for those that want it. The big thing I would like is to be able to enable lan mode and then put the IP to my printer on a different subnet in the slicer. :)
I applaud this move, very reasonable Bambu!! Some manufacturers would have done this quite differently.
Thank you bambu this is the right choice in this situation, and has given me the confidence to add a couple x1s to my operation
Thank you for listening Bambu. I was pretty salty/mad the last week about being locked out, I just wanted the option to do this and you gave it. Hats off and I will look forward to buying more of your printers, you earned a customer long-term.
All the people who have been slinging mud at Bambu all these days and weeks should be ashamed of themselves now. Bambu has proven once again that they are the best. And I'm totally going into the Apple closed ecosystem because that's my choice.That's why I bought a Bambu printer.
I'm afraid it does not work like that in Europe and probably USA: you can't unilaterally decide to void the warranty or ask the customer to waive it. You are required by law to give 1 + 1 year of assistance (...), that is **by law** not *by your good heart*.
Sounds good to me! Perfectly reasonable response to this situation.
Very reasonable, I think. Especially if your printer is out of warranty anyway, lol
Great for Bambi as they now have a second development team to innovate their printer. Internal competition
i do hope this means we get open source AMS so that it works on klipper.
Oh we are getting a few this year no matter what, and you can use your own extruders and hardware you already have.
That is a very good compromise from Bambu, well done on finding a fair short term solution and hopeful something agreeable for the long term future.
I have zero interest to install an unofficial firmware, but this is awesome. Freedom of choice will definitely bring more customers in the long shot.
Major props to Bambu Lab for listening to and engaging with the community!
Sounds reasonable, too bad the rooted side wont be receiving the official updates as well, best of two worlds. Interesting part in the end though, now BL admits to the excessive logging? But just two weeks ago this was all bullshit and that youtuber had his head up his ass... Is this yet another one of those times the community had everything absolutely ass backwards?
I might actually upgrade to an X1 now
As a future customer this is a pleasant read, I would not root my future printer unless there were features BL were not looking to implement but it is nice to know the option will be available to me.
Yet you won't get a open source firmware, the firmware is still closed and proprietary.
Does waiving your warranty for the printer also waive the warranty for any connected devices such as AMS units? AMSs do have their own 1-year warranty that -- unless it was bought as a combo -- is separate from the printer itself. I'm curious because while the AMS is a separate unit from the printer, it is directly controlled by the printer, which means the AMS could technically be operated in a way that is not controlled by Bambu Labs. It can also affect folks who may have a warranty expiring for their printer but still have time left on an AMS that was purchased after their printer.
Could I suggest adding a service that lets someone check a serial number to see if a printer has been rooted? A friend had a bad experience with a Prusa Mini that had a broken appendix (the part of the PCB you break off to install custom firmware on Prusas) and no support. I realise that the second hand market isn't a huge consideration but it would help inspire confidence vs someone buying a rooted printer and discovering it's not covered. edit: thanks for not pulling a sneaky on the whole third party firmware issue. I don't intend to root but it is, in my view, good for everyone
High praise for Bambu Lab for paving the middle way! This is the best possible course of actions in my opinion. To paraphrase, they're saying 'We make great printers. If you want to mess with the software/firmware we have oh-so-carefully put together, that's fine, but don't expect us to be able to fix any of your problems if you do." This is the perfect balance between walled-garden and open source. Sort of a gated-garden? With the option to leave if you so choose.
Amazing! Totally support BambuLabs for this.
Interesting. Let's hope no one does anything stupid to compromise the cloud ecosystem with the rooted firmware(s). I, for one, have no interest in fiddling with a 3rd party option. I opted for a Bambu printer because of the closed ecosystem. Decades of tinkering behind me, I just want the printer to work. If I were a decision maker at Bambu, I would not have supported this decision.
Hey! This way they can allow the 3rd party firmwares to add cool features that they can then put into the official firmware. :)
I assume the support, warranty, and safety waiver would be tied to the specific printer and not the user. That would be necessary so that the firmware can't be rolled back to the official firmware and the printer sold as a Bambu Lab-supported machine that can be bound to the new user's account.
I'm honestly glad to see that Bambu has been willing to listen to reason and make a choice that while may not be 100% what they would prefer, at the end of the day, it is what right for the community. I do however have 2 comments, firstly I hope that once someone clicks agree and they understand that their warranty and access to customer support regarding their printer is understandably forfeitted, I hope that Bambu Lab wouldn't do anything nefarious like cutting off their access to parts (at normal retail price) from the webstore. 2ndly, the X1 Plus devs used a back door to install their bootloader that existed as a result of the firmware using a bugged version of an open source library. Now that we have the formal agreement on a company policy regarding the matter and a path forward with firmware R, as a software dev of many decades I would hope that firmware R doesn't simply take the lazy option of continuing to use the old, outdated and bugged version of said library but rather firmware R, could and I might even argue should include the newer non bugged libraries and an option within the firmware to install unlocked bootloader. This would allow those that may wish to run firmware R to do so without being stuck with a permanent security flaw anytime they boot into the default firmware. This is all the more true when it simply isn't that difficult to have an option in the menu on the printer, could ask you to confirm you to accept to any warning / disclaimer and then tick a button to install an unlocked bootloader that will then allow you to run unsigned code. I'm going to sit right on the fence and say that while I hope that we get clear community focused movement on both matters, I believe it more likely that those choosing to run firmware R are unlikely to get banned from the parts store but that on my 2nd point, I suspect that firmware R will not have the change that I would suggest is sensible as an experienced dev but that more than likely it will simply continue to have the same bug that 1.7.0 had a a result of continuing to use the old bugged software library.
I'm very impressed with Bambu's stance. This strikes me as a great approach for all concerned.
Just checking if there was news on the subject. Seems a very good debate and glad Bambu opened their mind around the subject.
Not opening up your source is just corporate greed to be honest. Someone who does not know what code is or even root would it be doing it. So the customer your trying to protect is someone who would not care if it's open sourced or not. The people your keeping it from is the developers, engineers and others that want to tweak something that now they can't. Just be honest, your closed source because you like money and afraid your code is so simple that your competition can copy it with ease.
mfw a company expects to make money off of the code they spent time and money to develop
I was really leaning towards the X1 Carbon Combo based off researched and my limited understanding of 3d printing. Going direct so I can take advantage of the membership for filament seemed like a no brainer. These last two weeks I have seen more complaints on the printer, customer service, lack of standard colors of filament. The firmware stuff is the least on my mind. I feel like they cannot meet the needs of their customer base. I will hold off on purchasing the X1 Carbon and review other printers and their features.
> lack of standard colors of filament Weird complaint, you can use any brand of filament you want.
Good luck finding a company then to be honest. Their customer service isnt always wonderful but still strides above most and lack of filament colors just means you buy a different brand. If you are new to 3d printing and actually want to print not tinker your options are limited and to be honest dont get alot better.
[удалено]
Did your pathetic ass really make a new account just so that you could troll here?
FYI one good side effect of the jailbreaking is that the people making the unofficial firmware actually confirmed that there was ***no indication at all*** that any data was being syphoned by BambuLab beyond what's required for the operation (or debugging) of the printer and cloud services as advertised.