MobileRead Forums - View Single Post - K5 Backing Kindle Touch up before upgrading firmware

vedg · 03-21-2019, 10:35 AM

I've just created a complete system's backup of my Kindle with the script.

If I understand correctly, there are no straightforward instructions for complete system recovery from the backup. A script user has to decide on his own which files to restore.
I've read Original "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard and have a few questions regarding non-bricked Kindle system recovery (firmware downgrade):
(I) Can the recovery/downgrade be done in normal, non-fastboot mode if USB networking works with the new firmware?
(II) Will the following simple restoration process work?

Extract the backups archive into visible USB storage.
Swap dd's if and of arguments in mkbackup.sh's commands that create *.bin files; replace "skip" with "seek" in the first 3 dd commands; execute the modified dd commands for all backups/*.bin files.
Restore /proc/config.gz by swapping cp's SOURCE and DEST arguments.

03-21-2019, 10:35 AM	#6
vedg Member Posts: 13 Karma: 10 Join Date: Jan 2019 Device: Kindle Touch with Wi-Fi, ad-supported	I've just created a complete system's backup of my Kindle with the script. If I understand correctly, there are no straightforward instructions for complete system recovery from the backup. A script user has to decide on his own which files to restore. I've read Original "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard and have a few questions regarding non-bricked Kindle system recovery (firmware downgrade): (I) Can the recovery/downgrade be done in normal, non-fastboot mode if USB networking works with the new firmware? (II) Will the following simple restoration process work? Extract the backups archive into visible USB storage. Swap dd's if and of arguments in mkbackup.sh's commands that create .bin files; replace "skip" with "seek" in the first 3 dd commands; execute the modified dd commands for all backups/.bin files. Restore /proc/config.gz by swapping cp's SOURCE and DEST arguments.