View Single Post
Old 08-11-2017, 04:01 PM   #2435
nicolasmart
Sometimes active.
nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.
 
nicolasmart's Avatar
 
Posts: 132
Karma: 484026
Join Date: Mar 2015
Device: KT2, PW2
Quote:
Originally Posted by knc1 View Post
Are you also making the *.sig files to match?

There is one of me, I answer more than one person's questions at a time, I am also trying to do my own work.
So making things clear helps.

Would you please disable the tapatalk advertisement when you post here?
I don't know am I doing something wrong or KindleTool has some problems but I'm trying to sign the recovery2 package of a stock 5.8.10 with the pubprodkey02.pem (just to check would it install if it ever was unpacked) and when it's done, it says "unknown bundle". If I sign it with developer key or pubprodkey01.pem it works but the Kindle doesn't like that one (the certificate used from Amazon is pubprodkey02.pem) and it gives me Update Error 4.

When I give KindleTool argument "-k" and link it to the psig certificate I extracted from the original firmware, KindleTool just overrides my key with the default one.

Could someone tell me if they had that problem with KindleTool before?
nicolasmart is offline   Reply With Quote