Need Neato_4.5.3_189.tgz Firmware package

[crunchtime2k]

Desperately looking for Neato_4.5.3_189.tgz firmware package for us based neato.

Neatos online updater has been broken for a year for the d3 d5 d6 d7 models.


If anyone has this file , i know a few do from back in 2020 please share my way. Much appreciated.

[eyespy]

Also desperate for this. I did a reset for a battery change on a D3 and reverted to 3.0 without realizing I could not update again, so have no no-go lines now.

[crunchtime2k]

I got the firmware , flashing it is a little tricky , i will post a writeup this week.

[magnetchief]

Would be interested in this too.
Neato has been of no help, stuck on the original firmware, can't update. Need my room zones back ! Thanks for posting the update procedure. Will give it a go once it's posted.

[crunchtime2k]

************This is the original firmware with the expired cert https://www.dropbox.com/s/ldpuj82do06ft ... 9.tgz?dl=0. ***********


See below for modified firmware that has new cert and easy to load.

[eyespy]

I took crunchtime2k's file and replaced the crt in it with one from the most recent official Vorwerk firmware download. I noticed they have identical key identifiers, which means that the developers are just renewing their signing cert with the same CSR over and over.

https://www.dropbox.com/s/68zjvoaroq0p6 ... 9.tgz?dl=0

This mean that this file is usable as-is. It does not require anything special. Put the tgz in the RobotData folder on the root of your USB stick, plug it into the dongle, and plug the dongle in the robot. If you clear the logs and black box files on your bot first using Toolio, it should take about five minutes to upgrade. If you have a bunch of logs, it could take hours or get hung.

You may have to do a right bumper network reset and readd the bot to the app.

[magnetchief]

Looking forwards to giving this a go this weekend. Thanks

[bobbo]

It works! Thanks Guys! I simply placed eyespy's file in a folder named "RobotData" on a fat32 formatted usb stick (mine has a dual connector including a micro usb so no otg adapter required) and about an hour or so later it updated
I previously tried on a cheapo usb stick with the otg adapter but that was no good.

[eyespy]

Awesome! Thanks for the feedback. Out of curiosity, if you still have it, would you mind sharing the size of your RobotLogs folder on the USB drive? I'm trying to get an idea of what sizes amount to what install times. Also wondering if the cheapo stick was low capacity. My first test, my RobotLogs folder was over 1100 MB, and took around and hour. On subsequent tests, I used Toolio to purge black box files and log files from the bot before the update, and my update time was down to 5 minutes or so. Basically it seems like all of the files on the bot transfer down to the USB RobotLogs folder prior to the update, so the length of the update time is really dependent on how many logs are on the bot.

[crunchtime2k]

Eyespy , yes it appears the usb drive is in 1.1 mode and slow , some bots have 200 mb logs l i had a d7 with 1400 mb logs. I would recommend to flush them with neatotoolio for sure before the upgrade

[bobbo]

Awesome! Thanks for the feedback. Out of curiosity, if you still have it, would you mind sharing the size of your RobotLogs folder on the USB drive? I'm trying to get an idea of what sizes amount to what install times. Also wondering if the cheapo stick was low capacity. My first test, my RobotLogs folder was over 1100 MB, and took around and hour. On subsequent tests, I used Toolio to purge black box files and log files from the bot before the update, and my update time was down to 5 minutes or so. Basically it seems like all of the files on the bot transfer down to the USB RobotLogs folder prior to the update, so the length of the update time is really dependent on how many logs are on the bot.

Sure... the logs are 1.05gb in size. Interestingly I note that the upgrade file has gone. Do you know if the logs are copied or moved over?
Also, the cheapo usb drive is only 256mb, but it looked like it refused to access it, so it may have been simply incompatible.
Thanks again - you have achieved what neato support has been unable to do in months!

[eyespy]

Pretty sure it moves the files, at least when successful. It may be copying all then delete. My last test was under 25Mb in total.

I believe it also decrypts the fw file and puts it in the log directory. I believe it is the one that is around 25MB. Strangely, on mine it is named 4.6.3 something. Not sure if that is because I got the crt from that version or if it is because that is the highest version that has been installed on this bot. There are definitely still some mysteries, but everything seems to work fine.

Thanks for the follow up!

[magnetchief]

"RobotData" on a fat32 formatted usb stick

FAT32 ? Also heard NTFS

I guess I'm trying FAT32 first.

Still awaiting OTG cable

[eyespy]

Yeah, I don't think it really matters. You should not be hitting any FAT32 filesystem limits, and the Neatos of this age appear to be able to mount either filesystem without a problem. Can always try the other in troubleshooting if it doesn't work the first time.

[magnetchief]

Well that didn't work out as expected.
1Gb USB drive formatted FAT32

created a file RobotData and inserted the 3 files from the download.

Cleaned the files from the D7 using Toolio as suggested.

Attached USB to D7 using OTG cable.

Two lights on the D7 alternately light up, I assume downloading.

After 15 mins or so D7 beeps.

remove OTG, replace bin.

Check update, nope still on 102.

USB now contains 2 files.
One is RobotLogs from the D7, the other RobotData including just one file, Signing.crt. 2 have I assume been uploaded to the D7.

Tried a few times, reformatting the drive as NTFS, same results.

Going to try another drive. Any other suggestions?

[JEfromCanada]

Try again with a larger capacity USB stick but repeat the cleanup procedure you tried the first time.

[magnetchief]

No change there.
Larger USB drive 16Gb

Same process same results.

Still stuck on 4.2.0.102

Either I’m not understanding the process or our cleaner is truly screwed up.

[eyespy]

created a file RobotData and inserted the 3 files from the download.

Going to try another drive. Any other suggestions?

Try just dropping the tgz in the RobotData folder. You should not need to decompress although it may not matter. 15 minutes of alternating green/blue and beep is about what I would expect, unless the drive filled up with logs, but you mentioned that you purged those.

[magnetchief]

TGZ? You mean the zipped file?

[magnetchief]

Bingo. That sorted it out.

I was overthinking things and extracting the 3 files and putting those onto the drive rather than the zipped file.

Back to the latest a firmware version and I can now set zones again.


Thanks guys.
Hopefully I can pass on advice to another user.