New F/W: 4.43.23418 + 4.38.23429

[compurandom]

Originally Posted by DNSB

Yes, Pocket is removed from the Kobo and that deletes all the articles. You can migrate your content from Pocket to Instapaper which saves most of your articles. The ones that didn't transfer for me were items which no longer existed.

I exported my articles from pocket and extracted the csv file from the export and started going through them by hand.

I found a lot of articles I wanted to read but pocket never made them available.

I found a few articles that no longer exist, but luckily I was able to grab them via internet archive anyway!

[geek1011]

Originally Posted by akadaedalus

I let the update proceed because I felt a false sense of security about the failsafe mentality of Nickel*. I do have a feeling it was due to my battery being too low to successfully upgrade. My bad.

I guess with my refurb LIbra 2 replacement I'll probably still put some mods on it, but will also make a mental note to remove the mods before allowing an update to proceed. Or just consider it an old device and never update it again.

Hmm? I did just say the Nickel* mods and patches wouldn't be the cause of this issue (so there isn't really a need to remove it before updating).

Low battery (or anything else which would cause an update to abort at some point in the middle) can definitely cause problems if you're unlucky though (I've had that happen on my Mini a couple of years ago, which I later recovered by rebuilding the rootfs and firmware partitions on the SD card).

Side note: I don't remember (it's been a long time) if the Libra 2 is one of them, but there's a few eMMC Kobo devices which may still be recoverable from this kind of state over USB.

[geek1011]

Originally Posted by JSWolf

Would you please be able to check if the list of the patches I've posted (earlier in this thread) just need a new offset in the new firmware? Thanks.

I saw those a few days ago. I haven't checked, but about half of those should need new offsets (manually since they're a bit more complex due to patching longer functions), and the others (e.g., 24 line spacing values) need to be rewritten since a few versions ago.

Might take a proper look next week, but no promises.

[GrandNeko40]

just wanted to add another data point to this thread...

in the 48 hours after the firmware was first released, i tried about a dozen times to encourage my Libra 2 to update itself over the air, but was never successful. then, i downloaded the update via the link on pgaskin.net, and the device updated without issue. i had (and still have) nickelmenu installed, though after having installed it last year, i'd never gotten around to deciding what i wanted to do with it, so it was essentially unconfigured.

[roguexuk]

I was lucky, my 2x Libra 2's updated fine. But only had Nickelmenu & Koreader on - nothing fancy.

I did start updating my Aura One and only remembered about the Aura issues when it froze on the three dots.
After a quick panic, I did a manual reset. I think I was one of the lucky few when the restore screen came up.

I'll have to check my Clara HD, I don't know if it updated automatically or not.

Sent from my SM-X110 using Tapatalk

[Number9]

I think I'll have to take a raincheck on this update for my Aura One. 😒

[Pam R]

Hi, haven't been on the site for a long time but thought I would throw my 3 penn'orth in.

I have a VERY well used 6 year old Clara and don't keep wifi on at all except for every so often when I check for updates. I looked at the pgaskin site today and saw was a firmware update. I have just installed this on the Clara and it installed perfectly. (she says touching wood).

I didn't even have to reload the piece of code that geek1011 gave me some years ago because I can still reset the activity each time I charge the battery, so I can see how long it is lasting.

OCD moi?

[DNSB]

Originally Posted by Pam R

OCD moi?

Nope. The issue shows mostly on the Kobo Aura H2O Edition 2 & the Kobo Aura Edition 2 for the older devices. It has also been noted on the Libra Colour, Clara Colour and Clara BW. The firmware rollout for those devices has been paused.

Heck, it even worked on my Kobo Mini.

[Brianrh]

My Kobo Touch N905C updated okay but I'm turning the wifi off again now.

[u100009]

Originally Posted by Plastivore

Fellow Libra 2 Boot Loop of death here. I didn't ask for the update but woke up to a bricked Kobo yesterday morning, so I guess it attempted to apply it overnight.

I tried to do a factory reset but even keeping the page turn and power buttons pressed for more than a minute doesn't do anything (well, it doesn't seem to register that I'm pressing the page turn button, so it keeps turning on and off every 10-15 seconds.

I'm not sure yet if the data is corrupted or if the SD card just gave in (device is 3 years old). I'll try to flash the SD card (I really struggled to get that thing out of its port, the waterproof coating seems more to be an excuse for us not to attempt to change the SD card) and see…

I wonder how many of us are impacted and if having installed something third party (NickelMenu and KOReader) is one of the causes for this.

I'm not really impressed, though. It's the second Kobo I've had bricked by a Firmware update. My old Kobo Touch was one of the early ones which didn't have an SD card yet, so that was it then. It was kind of my fault for attempting an update with very low battery, but now this… I really like the Kobo ecosystem, but I'm not sure I'll buy another one if I can't revive my Libra 2.

Another Libra2 owner that has now a bricked device.. I did try to salvage the SD card by taking a backup image and try to write a new SD cards (32GB) by using a new image for the FW rev F, but the image is somehow corrupt and the FAT32 partition just shows up empty after the process is completed. I'm wondering if someone has a functioning image I could use for the Rev. F of the KL2 board.. ?

I've chatted with the support too online and got directed offline to e-mail exchange with the customer service. After proving by image and account information all the details, they replied that they are going to offer an exchange, but I'm worried about the new device not being as pristine and well taken care as mine (it's a white edition)...

[PennyDred]

All working fine on my Aura H2O (original) and the original Elipsa. I updated the Elipsa first which possibly helped. Instapaper switch was completely painless, though it takes ages to re-download everything.

[rogerinnyc]

Just adding my experience with my Libra 2, which was only modified with patches, but nothing else. Downloaded new firmware from pgaskin.net and extracted to .kobo. Ejected and waited...and waited. But eventually (> 1 minute) rebooted and update was fine.

To get Instapaper to show you need to sync your Kobo. Then the option to link with your Instapaper account shows and you're off to the races.

Thank you Kobo and Instapaper for stepping into the Pocket void so well and fast!

[akadaedalus]

Originally Posted by u100009

After proving by image and account information all the details, they replied that they are going to offer an exchange, but I'm worried about the new device not being as pristine and well taken care as mine (it's a white edition)...

I was going to say I doubt they'd give you a refurb with an original case but I thought I'd wait for mine before commenting this. Granted I have the black one but today the replacement came in a box clearly identifying it as a refurbished model and yet it looks pristine on the exterior.

[Alfirin]

Long story short I've got a Kobo Sage model N778 firmware 4.38.23038 I bought in november 2024.
Would you advise on updating or is it too much of a risk in your opinion?

[DNSB]

My Sage hasn't shown any issue with 4.38.23429. The main issues seems to have been with the Aura Edition 2 and the Aura H2O Edition 2 which have had the firmware rollout stopped.