View Single Post
Old 12-28-2011, 06:42 PM   #12
geekmaster
Carpe diem, c'est la vie.
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: 6,430
Karma: 10764602
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
I think that the startup scripts check the md5sum on some things to make sure they did not get "corrupted". Any changes you make to protected stuff would need to have their md5sum recomputed and stored, or it the boot process may abort.

At least that is what it *looked* like it was doing when I looked in there...

A *lot* of developers are bricking their kindle touch lately. It is way too easy to do that...

Last edited by geekmaster; 12-28-2011 at 07:46 PM.
geekmaster is offline   Reply With Quote