understanding FW updating and downgrading

arslonga · 08-30-2017, 10:16 AM

Good day.

I understand that one way to manually update the firmware on the KA1 is to download the appropriate .zip file and extract it into the .kobo folder of the eReader. However, I was wondering if the procedure is the same to revert to a previous version. I have noticed that the .zip file contains a folder called "upgrade" that may be self-explanatory. Thank you for your attention.

DNSB · 08-30-2017, 11:48 AM

Quote:

Originally Posted by arslonga

Good day.

I understand that one way to manually update the firmware on the KA1 is to download the appropriate .zip file and extract it into the .kobo folder of the eReader. However, I was wondering if the procedure is the same to revert to a previous version. I have noticed that the .zip file contains a folder called "upgrade" that may be self-explanatory. Thank you for your attention.

Yes, the procedure is the same. A couple of cautions: when downgrading firmware, I prefer to do a factory reset and then upgrade from there and do not downgrade to a version earlier than the factory reset version.

The upgrade directory contains uboot boot loaders and uImage Linux kernel files.

davidfor · 08-30-2017, 07:37 PM

@arslonga: As DNSB said, you can downgrade in exactly the same way as the upgrade. But, it isn't supported, and doing it via a factory reset is the recommended way. But, it will usually works. The only proviso I have is not to go to far. And that there are some versions where it might not work. Going back to the previous version will almost always work. But, going back four or five is more likely to cause problems. Plus, there are some upgrades that fiddle with the database in a way that isn't backwardly compatible. From memory, the last one was somewhere in the 4.1.x firmware.

the.Mtn.Man · 09-03-2017, 09:48 AM

For what it's worth, I've never had a problem with freely upgrading or downgrading the firmware on my 1st gen Aura, even when upgrading/downgrading across several revisions.

08-30-2017, 10:16 AM	#1
arslonga Connoisseur Posts: 59 Karma: 10 Join Date: Jul 2011 Device: none	understanding FW updating and downgrading Good day. I understand that one way to manually update the firmware on the KA1 is to download the appropriate .zip file and extract it into the .kobo folder of the eReader. However, I was wondering if the procedure is the same to revert to a previous version. I have noticed that the .zip file contains a folder called "upgrade" that may be self-explanatory. Thank you for your attention.

09-03-2017, 09:48 AM	#4
the.Mtn.Man Guru Posts: 710 Karma: 2483502 Join Date: Jul 2011 Device: Kobo Aura	For what it's worth, I've never had a problem with freely upgrading or downgrading the firmware on my 1st gen Aura, even when upgrading/downgrading across several revisions. Last edited by the.Mtn.Man; 09-03-2017 at 09:51 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Downgrading from 5.7.2 firmware	knc1	Kindle Developer's Corner	48	03-12-2016 09:56 AM
Downgrading	renew	Kindle Developer's Corner	5	02-03-2015 08:26 AM
Downgrading K4 firmware from 4.1.0 to 4.0.1	anontemp123	Kindle Developer's Corner	4	11-07-2013 05:39 AM
Touch Downgrading to 1.9.4	actiss	Kobo Reader	4	07-09-2011 01:51 PM
Downgrading K2 firmware	hmemcpy	Amazon Kindle	7	05-17-2009 09:36 PM

08-30-2017, 07:37 PM	#3
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	@arslonga: As DNSB said, you can downgrade in exactly the same way as the upgrade. But, it isn't supported, and doing it via a factory reset is the recommended way. But, it will usually works. The only proviso I have is not to go to far. And that there are some versions where it might not work. Going back to the previous version will almost always work. But, going back four or five is more likely to cause problems. Plus, there are some upgrades that fiddle with the database in a way that isn't backwardly compatible. From memory, the last one was somewhere in the 4.1.x firmware.

Advert