View Single Post
Old 02-10-2012, 05:07 AM   #30
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,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by geekmaster View Post
I still have to find out where the dastardly "malformed idme var flash packet" is hiding and kill it, so it stops killing my idme vars.
I think I killed the "bad flash packet". I zeroed out all the "user" partitions and let the kindle rebuild them on next bootup. I copied the main and diag partitions, and main and diag linux kernels, from my good k4nt to my bricked k4nt. All worked but registration with amazon. After an amazon tech reassociated my serial number and wifi MAC address, registration worked and all is well. Now that it is upgraded to 4.0.1, I have not seen any more MMC corruption problems.

I am working on a tool to automate and simplify this repair procedure. Read more here:
https://www.mobileread.com/forums/sho...48&postcount=4

Last edited by geekmaster; 02-10-2012 at 05:10 AM.
geekmaster is offline   Reply With Quote