View Single Post
Old 01-17-2012, 10:11 AM   #93
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
@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.

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.

Last edited by geekmaster; 01-17-2012 at 10:55 AM.
geekmaster is offline   Reply With Quote