[TouchPad General] smithylovestouchpad:
"Download the posted file and keep it on the USB Media Partition at all times."

Are you saying that if /boot becomes corrupted and the user does not reboot, so they are still in TWRP, that it is not possible to copy this zip to the TouchPad. If not, why is it necessary to keep this zip on the the /media partition at all times?

I don't get all your concern and work to create a way to recover /boot when in all these years, there has NEVER been a problem with corruption of /boot in the past when restoring a Nandroid backup. And yet you still continue to say that TouchPad users aren't capable of doing such simple things like keeping track of the charge on their device or following the instructions in your guide IF they are adequately emphasized. What possibly be so difficult for you to properly warn your followers by putting this in place of what is at the top of your OP and in your guide on how to use TWRP?

IMPORTANT, if you should decide to restore the backup you made before using my guide, DO NOT RESTORE THE /BOOT PARTITION!!!

You don't even acknowledge or give credit to J.C. Sullins for the work he did in helping TouchPad owners recover their tablets when they mysteriously quit working. He created an application or method for "Debricking" a TouchPad that no amount of charging would bring it back to life as you claim will. You say a TouchPad cannot be Bricked. Too bad that Mr. Sullins is not around to educate you on what a Bricked TouchPad was. It was a real issue that had nothing to do with letting a TouchPad battery drain too low. I don't know where you were at the time when he was helping thousands of TouchPad owners. Or read the discussions on Mr. Sullins thread for Debricking TouchPads. A bricked TouchPad had nothing to do with letting the battery drain down so low it automatically shut down. In such a case, adequate charging eventually gets the TouchPad working again. But with a Bricked TouchPad no amount of charging helped. But if you care to do a little reading, have a look here:

https://xdaforums.com/showthread.php?t=2126307

I'm sorry HPTP, even with all your denials, and blame game, I'm not buying that you did not discover, after what happened to me, that something in the way a TouchPad is configured for Swap, Rom Reducer and an alternate kernel and the tweaks you make to get it all to work that restoring a Nandroid backup appears to corrupt /boot. And honestly, I don't care if it does as long as you properly and adequately warn anyone who tries out your method. What's so hard about that?

I've owned several TouchPads since they were first sold 9 years ago. I still own two now. I've tried out virtually every Rom built over that time. I've used numerous versions of CWM and TWRP to backup and restore and even swap the installation on one TouchPad over to a different TouchPad. It's been a while since I had used Novacom to install a Rom via TouchPad Toolbox, so it took a bit for me to get back up to speed on that, and if it had not been for the stupid PC refusing to run Novacom, all would have gone smoothly on the first try. BUT, I have never had a problem with restoring a Nandroid backup. I have always used TWRP as it comes configured by TeamWin which means that by default it backs up /boot and restores /boot. I've done the ACMEInstaller and ACMEUninstaller stuff too.

I think what you have figured out is pretty slick. I wonder why no one figured it out before now? However, after testing your method on PIE and CM11, there is some sort of instability that causes random reboots on both. I don't like the lack of certain functions when using Rom Reducer. Straight CM11 does it for me. It's stable, has all the functionality needed, doesn't randomly reboot, runs any program I need it to. And it does it without swap, Rom Reducer or any modified kernels. I will leave all the pushing it to the limits to you and your minions.

Smithy