View Single Post
Old 07-06-2016, 11:50 PM   #9
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 knc1 View Post
@Geekmaster:
Not only do I have that exact model Kindle -
I have the Kindle that the factory loaded with that update_*.bin file.
AND
It does have a working serial port now.

Do you think we should disable that PW3 factory image until we find out what is wrong?

Oops - I didn't ask if they ran the md5sum test in the form.
I have 182 downloads of the PW3 image, plus whatever you have. How many PW3s have had reported problems? What percentage error rate deserves a temporary takedown? And yes, lets get him to test his md5sum. Perhaps he has a corrupted firmware file. If he has corrupted factory firmware, see if he can get into diags and fix it from there. I am too tired to think straight. We can continue this in the morning. Just throwing some ideas out there for you to persue when you awake.

If his md5sum is WRONG, see if you can get a copy from him and duplciate his problem on your end, then figure out how to fix it. As I said, it MIGHT require a serial port solution, but hopefully not (i.e. a diags flag file).

Last edited by geekmaster; 07-06-2016 at 11:57 PM.
geekmaster is offline   Reply With Quote