View Single Post
Old 04-09-2012, 01:09 AM   #152
geekmaster
bit basher & pixel pusher
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,687
Karma: 7581653
Join Date: Nov 2011
Location: A young man living in an old man's body.
Device: Too many.
Quote:
Originally Posted by qtybest View Post
Is it necessary to flash the origional mmcblk0p2 in order to make a successful update to 5.0.4?
I do not think that the update changes (or cares about) mmcblk0p2. The version with SSH does not have any changes except adding missing files, so should not be a problem.

It is possible that the previous update attempt failed because the partition and kernel did not match, but left the partition in an unstable condition. This latest failed update may have changed the kernel and/or main partition, so you should flash a new 5.0.0 kernel, and use "dd" to copy a new 5.0.0 main partition to /dev/mmcblk0p1. Then perhaps run a "factory_reset" script to erase any residual /var/local settings that might interfere with an update.

In my case, I was able to successfully update to 5.0.4 after flashing a fresh 5.0.0 kernel and using "dd" to copy the "forensic" 5.0.0 main partition image, so you should be able to do that too...
geekmaster is offline   Reply With Quote