Print

[victorgman]

  Hi Everyone.. I'm a noob to this site, and to Pleo in general. As a new Pleo Owner I made the classic mistake of updating my Pleo RB with v2.01 Firmware, rendering my little friend useless,  . which in turn led me to google and this wonderful forum. As suggested I tried the downloads OS section for Pleo RB. After updating V1.0 low level firmware successfully, I couldn't update V1.0 female or male firmware, without an error. Tried various SD cards but to no avail. After a lengthy research, I found another forum (Pleo-web.de). And searching through the firmware, I noticed a difference in sizes for both files,which could only mean a different version. After flashing low level again, I then flashed the male Firmware V1.1, and my Friend is back! Not sure why my RB didn't accept V1.0. If anyone else is having this problem, try the later V1.1 Files, might just revive your Pet! Good Luck

[Talon]

Good tip and welcome to the forums! I'm glad you were able to rescue your friend.
Talon

[InmemoryofRomeo]

Welcome, glad you got your little guy back up and running

[victorgman]

if anyone is in need of these files just ask and I'll share them. tried to upload to the downloads section, but says files not accepted

[Talon]

Hi, Victorgman. Thanks for your attempt to upload these files. You have to send a personal message to mweed, our administrator first in order to get them approved. Good luck!
Talon

[grumpy]

I checked the two uploads.   Both the male and female files for the V1.0 load a complete new image into the pleo memory.  Both of the V1.1 files do not, they simply update one file, the file that differentiates the two sexes.  So, the V1.0 update has additional files the V1.1 file doesn't.  The V1.0 also appears to have an extra folder level, which may confuse some people.   The one file that is different was released only five days after the V1.0 file, so I'm not sure how much difference there is.

If someone wants to play, you could try removing the automon.txt and pleo.img files from the V1.0 to match the file structure of the V1.1 and see if that fixed the problem with the update failure.