Four reasons to choose anysim 1.1 over ipsf for unlocking your *virgin* phones.

1. anySIM is free. But dont forget to donate. http://iphone.fiveforty.net/wiki/ind...i:Site_support
2. Like IPSF, anySIM 1.1 doesn't touch your nvram or seczone.
3. After unlocking using anySIM 1.1, when you upgrade your phone, your phone will get re-locked. Where as IPSF unlock is permanent. This may appear as a disadvantage, but it is not.
If you have some issue like dead pixel some hardware related issue, and you have luckily used anySIM instead of that paid method, all you need to do is to upgrade your firmware (downgrade+upgrade if needed) and send it to apple. They will not be able to find out anything about your unlocking stuff. (http://www.hackint0sh.org/forum/show...t=11629&page=3 - see comment by baalbeck). So you dont lose your warranty!
4. And finally didn't I mention that anySIM is FREE!!!!

Also, anysim community support is way better.

Just some technical clarifications (no politics intended):

2) anySIM 1.0x didn't directly write to the seczone either. But as a consequence of the particular patch used, the baseband itself ended up creating the 0049 condition in the seczone.

3) A phone that has been IPSF unlocked can be relocked again by restoring the original seczone. Granted, not many people are saving their original seczones (if people were doing that, there wouldn't be so many anySIM 1.0x users stuck at FW 1.0.2 right now, unable to upgrade).

Originally Posted by MuscleNerd

Just some technical clarifications (no politics intended):

2) anySIM 1.0x didn't directly write to the seczone either. But as a consequence of the particular patch used, the baseband itself ended up creating the 0049 condition in the seczone.

3) A phone that has been IPSF unlocked can be relocked again by restoring the original seczone. Granted, not many people are saving their original seczones (if people were doing that, there wouldn't be so many anySIM 1.0x users stuck at FW 1.0.2 right now, unable to upgrade).

Your second point is interesting. I think no post any where mentioned the need for backing up seczone before unlocking. Ok, is it possible to use the seczone extracted from some other 1.02 phone and restore it in our phone. If yes, please provide some guide for doing this.

Originally Posted by iphoneindia

Ok, is it possible to use the seczone extracted from some other 1.02 phone and restore it in our phone. If yes, please provide some guide for doing this.

Unfortunately, no. Among other things, your IMEI is encrypted into the seczone too. So using someone else's seczone will only give you grief.

As if right now, people should use NORDumper before using any unlock by anyone. That way they also have their original seczone to go back to, in case anything unexpected happens in the future.

Originally Posted by MuscleNerd

Unfortunately, no. Among other things, your IMEI is encrypted into the seczone too. So using someone else's seczone will only give you grief.

As if right now, people should use NORDumper before using any unlock by anyone. That way they also have their original seczone to go back to, in case anything unexpected happens in the future.

So if I have a NOR dump of my phone prior to unlocking it should be completely restored to virgin state? Is that correct?

Hi there,
paranoid as i am i also created a nordump file before unlocking with anysim 1.02.
Does that mean my iphone is a virgin & upgradable to 1.1.1. if i flash the nordumped file ?

If yes and to prevent another noob of bricking his beloved iPhone could you post how to flsh the file created by nordump ? ( status -> unlocked & working 1.02 FW, File generated by nordump is 4.194.304 Byte )

Thanks, not all hope is lost, right ?

:-)

Ender

To clean up with a urban legend, you CANNOT write seczone through secpacked write cmd in bootloader or any known method.

So it's not possible with any way, i.e. fls, rewrite NOR to bb or whatever to restore your seczone like that.

A upcoming virginizer will work diffrent. And it will come, but please be patient, working it out is a sucking slow task.

Originally Posted by sam

To clean up with a urban legend, you CANNOT write seczone through secpacked write cmd in bootloader or any known method.

So it's not possible with any way, i.e. fls, rewrite NOR to bb or whatever to restore your seczone like that.

A upcoming virginizer will work diffrent. And it will come, but please be patient, working it out is a sucking slow task.

Thanks for all the hard work Sam.

Thanks for making it clear!