View Single Post
Old 07-15-2017, 07:49 PM   #1793
knc1
On Holiday
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: 16,234
Karma: 17256900
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Rosscuro View Post
- - - -
What gets me confused in the first place are the "code names" each model of Kindle has. I have the Kindle Basic Black (with serial G000 K905) which I'm not sure if it is a KT2 or a KT3, or maybe a totally different one.
I will not tell you to "read the forum"
I do suggest that you re-read the first post of the current jail break:
https://www.mobileread.com/forums/sh...d.php?t=275877

The names used by Amazon Marketing are not stable over time nor consistent across geographical areas.
Which is one reason for the nicknames.
Another reason is that all packages with the name format: update_*.bin are model locked.
Since for years we used Amazon's internal installer, our locking had to be the same as theirs. Which is based on the model substring of the serial number.

Now - the first 'read the directions':
Quote:
Step #1 below describes how to learn what nickname your device has here based on its serial number.
You needed to do that as the very first step.
It is critical to the process and to using this forum.
Quote:
Originally Posted by Rosscuro View Post
Secondly, even though I had doubts about which file to download and use, I managed to JB my Kindle (probably this is the part I messed up) with the hotfix too, then proceeded to installed MrPI and Kual through it, then the python extension and the Collections manager that uses it.
You do not mention replacing the factory-use-only firmware with a customer firmware version.
Nothing that we provide here was ever intended to run on anything other than publicly released, customer firmware.

That is the next: 'read the directions'
Specifically Steps #7 and #8
Do them after reading them.
Quote:
Originally Posted by Rosscuro View Post
Everything was working fine for a couple of weeks but after like 4 days I didn't use my Kindle, I went to check it and the collections I imported from Calibre were gone and all my books were in one folder so I tried to open KUAL and a window that says "Application error: The selected application could not be started. Please try again." appeared. I never Reseted my Kindle since the JB.
Your third: 'read the directions':
Quote:
None of our add-ins are protected across updates, you must always re-install them.
- - - -
These update_*.bin package name format packages must be re-installed after each firmware update.
Which is at the start and the end of the directions.

Plus you where not using the 'OTA blocker' described in Step #7, plus you threw another curve at the process by letting it OTA update from the factory-use-only firmware while our add-ins where installed.

Quote:
Originally Posted by Rosscuro View Post
If I'm correct this shouldn't happen because I installed the "survival code" and no further update from Amazon should affect the JB.
That is correct, the jailbreak and the update bridge code survives, they auto re-install, they are viral.
See above portion of my reply, you where told you would have to re-install everything other than the jailbreak yourself - TWICE.
The final few sentences of the first post, those following Step #8, give you additional information on that.
Quote:
Originally Posted by Rosscuro View Post
Some guidance would much appreciated.
I can't not think how you could have missed so many critical details of the process,
unless you where not following our directions (the original) and instead where following some abbreviated version you found on the 'net somewhere.

The best advice I can give you, is to read the first post of the current jail break from the first word to the last word, including the content of all spoilers.
Keep an eye out for things you might not have done, I can't guess at the exact state your device is now in.

Last edited by knc1; 07-15-2017 at 07:56 PM.
knc1 is offline   Reply With Quote