Firmware 4.31.19086

[Terisa de morgan]

Originally Posted by ownedbycats

Does the patch allow you to sync? I haven't had any issues so far, but if I need to revert again it might be useful.

I don't know because I never sync through Wi-Fi.

[jiminrussell]

Originally Posted by ownedbycats

Does the patch allow you to sync? I haven't had any issues so far, but if I need to revert again it might be useful.

Have you looked at the "Always show confirmation dialog before upgrading:" patch? That has no impact on sync from my experience and using this patch you are prompted before it downloads the update so it will never be applied unless you want it to be. Though you do have to respond to the prompt each time you sync until you do finally decide to upgrade.

[jfp555]

Originally Posted by davidfor

It is unlikely that an update actually bricks a device. About the only way for it to happen would be to lose power at exactly the wrong time. Your post where you requested the image mentioned doing a manual restore by holding the button down for 30 seconds. All that does is forcibly turn the device off. A manual factory reset requires the device to be connected by USB when turn on and the power button is pressed down.

The other reason a device might seem to be bricked by an update is if the SD card is failing. And if that was the case, then it would only be a matter of time before it happened. The update might trigger it, but, mainly because it is writing to different parts of the SD card.

Others have reported issues with different updates. But, from what I can tell, the issues are already there and the reboot needed to install the update just means that the actual problem is finally noticed.

At this point, you may as well try the update. It will probably work. But, if it fails, then you have the image and can restore it. If the update is a problem for you, there is probably a patch to block it.

Thanks again. I took your advice and mustered the courage to update, and it worked this time! There was definitely something wrong the first time around. Update worked properly this time.

[Quoth]

Originally Posted by ownedbycats

Does the patch allow you to sync? I haven't had any issues so far, but if I need to revert again it might be useful.

I don't use sync.

I suppose I could block *.kobo.com on the router, but that's not reliable.
I'm at post 19 reading thread.

Edit
This is from 2014 and despite title people were actually trying to force updates!
https://www.mobileread.com/forums/sh...d.php?t=234211

So not what I need.

[Terisa de morgan]

Originally Posted by Quoth

I don't use sync.

I suppose I could block *.kobo.com on the router, but that's not reliable.
I'm at post 19 reading thread.

This is the patch I was talking about: Block WiFi firmware upgrade, inside libnickel.

Description below:

Spoiler:

WARNING! THIS IS A DANGEROUS PATCH! READ THE INFORMATION BELOW CAREFULLY!

THIS PATCH IS UNTESTED, as there is no way to be sure it still works until
the next firmware version is released. If it works then the firmware will
not be upgraded during a WiFi sync, but you will still be able to upgrade
manually or by syncing with the Kobo desktop.

THIS PATCH COULD RESULT IN A BOOT LOOP when signing out of your Kobo account
(Settings > Accounts > Sign out) or when invoking a factory reset from the
device information menu (Settings > Device information > Factory reset).
REMOVE THIS PATCH BEFORE USING EITHER OF THOSE OPTIONS.
A factory reset invoked using the hardware methods (such as holding down the
light button while switching on) should not be affected.

[Quoth]

Originally Posted by Terisa de morgan

There is a patch for blocking Wi-Fi updates. I think it says that can be damage your ereader, but I've got in place for years and nothing has happened (not exagerating about years).

Where is this useful patch?

Edit:
Isn't there an issue that patches are for a particular Firmware? Does such a patch exist for any reasonable Elipsa FW version?

[Terisa de morgan]

Originally Posted by Quoth

Where is this useful patch?

Edit:
Isn't there an issue that patches are for a particular Firmware? Does such a patch exist for any reasonable Elipsa FW version?

You can find it here, or at the proper thread for your FW (this patch hasn't changed in a lot of time). Sorry, I don't know which are the Elipsa FW.

[JSWolf]

Originally Posted by Terisa de morgan

You can find it here, or at the proper thread for your FW (this patch hasn't changed in a lot of time). Sorry, I don't know which are the Elipsa FW.

The Elipsa is using the same 4.31.19086 firmware as most other Kobo.

[davidfor]

Originally Posted by ownedbycats

I think I know what happened. I tried to sync my Kobo and got a message saying it needed to update. I clicked the 'not now' button thinking that would prevent it entirely. But I guess that just queued it up for download anyways.

Nice to see Kobo doing the Windows Update thing.

The prompt is asking if you want to install the update right then. If you say yes, the install happens and the device restarts. If you say no, the update files are left on the device and will be installed at the next opportunity. That could be when you do a sync, in which case it won't need to download the files again. But, it they will also be installed the next time you connect and disconnect from the computer. This is how it has always worked. Personally, I use it as a way to grab files from the device before the update happens.

[ownedbycats]

It's the first time I've ever picked 'not now' on that dialog, so I thought it'd just indefinitely delay it.

What was frustrating that the dialog had popped up just after I finished a book so I had no option to avoid it. I suppose I should check the auto-sync settings.

I haven't had any issues since the second upgrade though. Maybe the first one didn't go right.

[JSWolf]

Of course, you could do what I do. Keep WiFi off and don't sync.

[ownedbycats]

Originally Posted by JSWolf

Of course, you could do what I do. Keep WiFi off and don't sync.

Hmm. Nah.

[MGlitch]

I might have missed this in a previous firmware but when I’m charging my Sage now if I pull up the battery from the top menu it gives me an estimate of how long it’ll be before the battery is fully charged. It also tells me the source, I presume it would vary between USB (which is what it displayed when I looked) and the power case (which I don’t have and AFAIK is still unavailable to order).

Note this is different than just showing the battery percentage when the battery menu is tapped. It gives a time in minutes for the estimate.

[ownedbycats]

Sigh, ran into the issues again:

- Sideloaded a new book onto my device. Ejected to let it import.
- Connected a second time to upload cover and metadata. Got the 'There's a problem with this device' message. (As usual, it disappeared before I could actually do anything.)
- Uploaded the cover, disconnected. Device stopped saving reading position.
- Rebooted device, it started saving reading position again.

Thankfully, no issues when I re-connected the device again. Integrity check went fine and it didn't reset itself when I ejected.

[Sirtel]

Originally Posted by ownedbycats

Sigh, ran into the issues again:

- Sideloaded a new book onto my device. Ejected to let it import.
- Connected a second time to upload cover and metadata. Got the 'There's a problem with this device' message. (As usual, it disappeared before I could actually do anything.)
- Uploaded the cover, disconnected. Device stopped saving reading position.
- Rebooted device, it started saving reading position again.

Thankfully, no issues when I re-connected the device again. Integrity check went fine and it didn't reset itself when I ejected.

Obviously there are bugs in the latest firmware.

For my part, I'm not going to update my Kobos until Kobo releases a fix (or rather several fixes). I don't sync and seldom use wifi, so I can wait.