View Single Post
Old 06-09-2017, 11:26 AM   #58
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Hexadecimal View Post
Yes, just as you described.
- - - -
Which is very strange - -
The normal, customer, Amazon update files are 'model locked'.

But we have here a PW3-32 running a PW3-4 u-boot binary.
I.E: The Kindle updater installed the u-boot from a different model PW3 image file.

That **should not** happen with a normal, customer, Amazon update file.
BUT...
It could happen using one of our 'factory, production line test' update files.
Those are not model locked and there is no telling how many places on the 'net they have been copied to.
The O.P. mentions: "bad translation of directions" -
There are a lot of those out there, and most have their own copy of the 'factory initial' files.
Since the site had a "bad translation" - that may include not describing what image file was being provided.

= = = =

Note:
A 'stock' PW3-32 WILL try to install a PW3-4 'factory initial' file.
A reader tried that during the first week of the jail break release and they confirmed it bricked their new device.
That was when I put the bold PW3-32 model warning in the directions.

Last edited by knc1; 06-09-2017 at 11:30 AM.
knc1 is offline   Reply With Quote