Originally Posted by vanger1

997TT
to save you some time - dont downgrade to 1.1.1
go all the way back to 1.0.2
the tiff isnt't gonna work on 1.1.1 after 1.1.2 restore

Of course it works, it always worked. Please stay put and read what I write because I'm no noobie.
When you downgrade, you also introduce the TIFF exploit again in Safari, simple matter.

Originally Posted by 997TT

Of course it works, it always worked. Please stay put and read what I write because I'm no noobie.
When you downgrade, you also introduce the TIFF exploit again in Safari, simple matter.

ok
i think it's where you are wrong
but not gonna argue since i am not a pro

please do post your findings
since i am not going to bed only becouse i wana see how far i you going to get

Originally Posted by vanger1

my question is if the tiff hole would get back
is it in the baseband?
if yes
than yeah i could just downgrade the baseband
upgrade to 1.1.1 and if the tiff exploit is not fixed i can try again and again and again

The tiff hole is in the main filesystem part of the "firmware". Specifically, it's in one of libs used by Safari and other apps. It is not in the baseband. So, regardless of your baseband version, if your "firmware" is anything prior to 1.1.2 then the tiff hole exists.

By the way you have touched upon a key point. If you are using bootloader 03.09 and have a backup of your seczone, so far it seems that every possible jam you can get into with software methods is recoverable. In some cases it takes a little persistence, but you are on the cutting edge after all.

Originally Posted by MuscleNerd

The tiff hole is in the main filesystem part of the "firmware". Specifically, it's in one of libs used by Safari and other apps. It is not in the baseband. So, regardless of your baseband version, if your "firmware" is anything prior to 1.1.2 then the tiff hole exists.

Very well explained. Thanks. I just re-applied the OktoPrep patch in 1.1.1 and I'm preparing for the 1.1.2 update.

Btw: do you by any chance know where I could find a AnySIM1.2u REPO? Thanks.

@vanger1: I can't be wrong, I'm an iPhone Moderator. *LOL*

i sucessfully updated to 1.1.2 that is jailbreaked. did not need to haev activated iphone, and correction wit the itunes update. Do not click restore, click shift +CHECk for Update buttona nd choose the 1.1.2 restore file, that way u dont lose any data on the fone.

Will test on the unlock of anysim now.

Originally Posted by hco

i sucessfully updated to 1.1.2 that is jailbreaked. did not need to haev activated iphone, and correction wit the itunes update. Do not click restore, click shift +CHECk for Update buttona nd choose the 1.1.2 restore file, that way u dont lose any data on the fone.

Will test on the unlock of anysim now.

Well, the instructions were pretty clear from the beginning (just the prefs://11 not, actually it needs to be prefs:// only but it works anyway ).
The only issue I had so far seems to be AnySIM1.2u and I'm not sure what went wrong. Still looking into it...and trying again. Right now my iPhone is updating to 1.1.2 again...WITH the OktoPrep patch.

Originally Posted by 997TT

do you by any chance know where I could find a AnySIM1.2u REPO? Thanks.

Sorry, I don't have any information about an Installer.app repo for it. I'll post in this thread if I hear of one.

BTW you are right that the "u" version should have come with an explanation about what changed. The elite wiki now has that additional information.

It would be great if someone who has read the instructions, and FOLLOWED them could comment if it works or not? Not saying i did restore and now oktoprep is gone, etc....

Hey

Should i use the patched lockdownd before the windows.bat file or first activate it with att then jailbreak and then replace the lockdownd or do the windows.bat does not require activation before running it.

thanks

MuscleNerd
Thanks for the explanation.
I kinda thought the same way, but i just don't get why the Appsnap wouldn't work for me than???

I applied iPhone1,1_1.1.1_3A109a_Restore.ipsw.
Is there a way to tell if tiff exploit is fixed in here?