Quote:
Originally Posted by geekmaster
@ixtab: I thought you were going to use tzVar instead of locale. As we discussed in PMs shortly after you discovered the tar bug, tzVar does not clobber the locale settings.
|
Yeah, I had thought about using tzVar for a moment as well. But IMO this may cause even more problems (on my Kindle, the file doesn't even exist, and I have no idea what should go in there or how it is used). I think "resetting" the locale to the factory defaults is a good compromise, because a) the file always exists, with predictable contents;
b) normally, when you apply the jailbreak, you didn't even have a chance to customize the locale yet (changing locales needs our WIP localization package, which in turn requires a jailbreak);
and c) there is an easy way to get back to fully localized.
Quote:
Originally Posted by geekmaster
Unfortunately, locale and tzVar only work on the Touch. They do not work on the K4NT.
The only *universal* payload destination that works on both the Touch and the K4NT is the one I found that *might* survive your tar bug getting disabled (because no shared dependencies). My payload destination can be triggered using mutliple methods, and we had agreed that it could be saved until yours gets burned because the K4NT already has a developer mode method.
If the goal here is to create a single jailbreak that works on both the Touch and the K4NT, we will have to use my payload destination and trigger method, and just hope that amazon does not fix ALL the trigger mechanisms for it.
|
As far as I understood, yifanlu has an idea about K4NT. I cannot be of any help with that device. So yeah, let's keep a stack of possible exploits for later, and keep looking for others while we have full access
