09/15/2010, 01:42 PM
Even with all the AUPT features, the safest way (and Best advice) is to remove ALL patches, kernels, and kernel modules before updating. I think Rod posted something like this a while back, but everybody is relying on AUPT to work correctly, and as we know nothing works 100% of the time. In my experience, doing it this way saves you a ton of hassle later if things go wrong.
The cliff notes for what to do BEFORE the update are:
1) Run Preware and UPDATE the SAVED PACKAGES LIST (this saves a list of all your installed patches, programs, etc.)
2) Run Save/Restore & save/backup data (just in case you accidentally erase the Preware Saved Packages List later).
3) Run Preware and remove any Themes & Scrims, Restart Luna
4) Run Preware and go to AVAILABLE PACKAGES, LINUX APPLICATION, UTILITIES, select EMERGENCY PATCH RECOVERY and run it. This will run a script that removes ALL PATCHES at once. It may take a while if you have a lot of patches installed.
5) Restart phone when prompted
6) Optional: Run Preware and run EMERGENCY FILE VERIFICATION (also in Linux Application). This verifies all files were successfully returned to stock.
7) Install the WebOS update...
After the OS update is installed, & phone is operational again after rebooting:
1) Run Preware, update feeds (necessary to get the patch feeds to load from the correct v1.4.5 repository, otherwise you won't see patches for your correct OS version, and hopefully you have all the feeds named correctly so it does this automatically)
2) In Preware, go to SAVED PACKAGES LIST to load the saved list of all patches that were on your phone prior to the update, from step 1 above (do NOT hit update, or this will erase your old saved list, and over write with whats currently on your phone, i.e. nothing!!!)
3) At this time, you can re-load the patches manually, or by hitting INSTALL ALL. I prefer to do it one at a time, simply going through the Saved Package List myself, trying to be cautious about the order. This makes it easier to see what causes a problem by installing one at a time.
Updating patches run into the errors in above posts when a file is either mangled, not put back to stock properly, or partially updated, etc. If the checksum doesn't match, then you can't remove a patch to put the file back to stock, and if you can't update it you're stuck. Doing the above process puts everything back to stock to the update will install correctly, then you re-install all patches cleanly.