MobileRead Forums - View Single Post - Unbricking after firmware 2.0 update dancing squares

Mrs_Often · 10-17-2012, 04:05 PM

Thanks murg. I was on a manually updated 2.1.1... I don't think it was the firmware problem as the update to 2.1.1 went more or less okay and I'd been using it without any problems.

I have no idea what did go wrong, but about 3-5 hours (I can't remember now) of constant re-resetting after looong square dancing it finally started up properly... Only to be faulty in all sorts of ways and not wanting to connect to the computer so I couldn't get to the disk... After another hour of resetting I finally got a proper startup with working connection to computer and was able to set up and update... only to still have a corrupted database somehow. Luckily though I had a backup and with the kobo mounting to my computer properly I could restore it. Then reset it again to have it nice and clean - that worked.

So, now it's all fixed and I'm happily using a manually updated 2.1.4. Shame I have no idea what went wrong in the first place though. Oh well!

10-17-2012, 04:05 PM	#53
Mrs_Often Wizard Posts: 1,775 Karma: 2694823 Join Date: Dec 2011 Location: The Netherlands Device: Kobo Touch, Glo, Clara HD	Thanks murg. I was on a manually updated 2.1.1... I don't think it was the firmware problem as the update to 2.1.1 went more or less okay and I'd been using it without any problems. I have no idea what did go wrong, but about 3-5 hours (I can't remember now) of constant re-resetting after looong square dancing it finally started up properly... Only to be faulty in all sorts of ways and not wanting to connect to the computer so I couldn't get to the disk... After another hour of resetting I finally got a proper startup with working connection to computer and was able to set up and update... only to still have a corrupted database somehow. Luckily though I had a backup and with the kobo mounting to my computer properly I could restore it. Then reset it again to have it nice and clean - that worked. So, now it's all fixed and I'm happily using a manually updated 2.1.4. Shame I have no idea what went wrong in the first place though. Oh well!