moonglow / flashforge_firmware_tool

:cyclone: FlashForge firmware tool allow you to decrypt and encrypt firmwares from FlashForge 3D printers, Dremel 3D20 and PowerSpec Ultra 3D

flashforge_firmware_tool's Issues

Bypass boot password lock

• Affected models: Dreamer v2.14.20191123, Dreamer NX v1.9.20191123
• Workaround: You will need to create file in root of your external SDCard with name: j6&^%$#@-'s#&%%z@3#{}.txt

Summary of bugs.

I just realise that when i print an object from repetier to The Dremel 3D20, the ETE time display seems accurate, but the ETA is completely off... Ex. : ETA 23 17 14 DAY 22 !!!

While the stock thermocouple in the printing head (when not printing since a long time), should display the temperature of the room, it gives me readings between 27 and 28..At the same time I have connected a HT-NTC100K B3950 thermistor to NTC1 and another to NTC2 with some precision resistor of 4.7k pull up to the 3.3v (pin1). They gives different temperature with the presets 11, 61 and 1000.... but more accurate than the thermocouple, reallyb around the room temp. (22 - 23). But the worst part, is that i no longer can upload a new firmware... Here's why: everytime I power it up, it shows the boot images, and just after the marlin logo, the RED SCREEN OF DEATH : ERR MAX TEMP E2 PRINTER HALTER PRESS RESET...

I think it is a ONE WAY - DEAD END... what do you think? Do I throw the printer from the 3rd floor...?
But I know exaxtly where the Shit Hit The Fan! When I put back the TEMP_1_PIN to -1 in the file pins_FF_MOTHERBOARD.h (Even if the rem says (-1 means... /* skip checking, change to ADS1118 CH1 */ ) it didn't because i didn't put back the ... #define TEMP_SENSOR_1 to -666 and let it at 1000.. causing the shit to prepare it's trajectory .. in conditionals_post.h around the lines 680ish and more.. my mistake passed trough the code.... it should not, but it did.... E2 became a custom sensor with no reference define as well as no pin definition.

I was about to give you a lot of small things to do, but I did the big ONE !! That is what happen when you only sleep 2 hours in 2 days... Good night... When I wake up, I hope to have some good news, but my expectations are very low, consirering the fact that I think it is almost impossible to upload a different firmware... Let me know..

Unable to execute binary files

While using the program on Ubuntu I was able to use it to encrypt the files a couple of weeks ago but after applying some system updates ( I don't know everything that updates I allow the updater to update everything), the command no longer encrypts the firmware. Instead I receive an error that ff_fw_tool is unable to execute binary files. So far I have tried changing the file type of the ff_fw_tool from no type to .exe and .sh and have gotten the same error each time. I have also regenerated the tool using the main.c file but so far nothing has worked.