-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to flash Mingda Legacy UI back onto printer? #13
Comments
Hi @bigjoncoop , Check out this issue, it has the information you are looking for: Basically, download the Original Mingda TFT35 Icons and put it on your SD card. It will have the proper images so you can revert. |
Hi. Can anyone help me find original Mingda TFT35 Icons? The link provided isn't working, thanks. @spessoni @marcellodum Do you happen to have a copy? My D2 printer keeps resetting while printing with this firmware and i might need to revert back to original. Thanks |
Try this: |
It worked. |
@marcellodum
How do I flash the Mingda Legacy UI back onto my D2 printer?
After I flashed the D2 firmware and the assets folder from the releases section, I realized that it was not configured for a BL-touch. Then without thinking I went ahead and reflashed the stock firmware.bin on to the printer, which broke the touch screen UI since the LVGL UI assets were still on the printer....
I then used Vscode to recompile the stock firmware as you mentioned,in order to get the Legacy UI assets. But after compiling I am unable to find where the assets folder is located since there are no .bmp files created.
I spent the next 5 hours trying everything I can think of, as well as searching on Google how to solve this issue with no luck. I was able to find a custom version of the stock firmware which had a TFT folder in the source code. The TFT folder contained a bunch of the stock UI icons. But after flashing them onto the printer, only half of the icons were there. Half of them are still missing...
Any help you could give me would be greatly appreciated.
Thank you
The text was updated successfully, but these errors were encountered: