Closed GoogleCodeExporter closed 8 years ago
This is bound to happen. Zibri and co please explain how anySIM 1.1 works. I
understand that they belong to dev team and it's your right if you guys choose
not to
explain.
Original comment by bentfing...@gmail.com
on 23 Oct 2007 at 4:51
Fairly simple explanation:
anySIM 1.1 doesn't change the seczone on your phone like anySIM 1.0 and
iPhoneSIMFree
do. Instead, it modifies the phone's firmware to skip the lock check and work
with
SIM's from any provider.
In the older anySIM and current IPSF releases, they attempt to set the phone's
lock
status to unlocked. With the new anySIM release, they don't bother trying to
set the
lock status and instead modify the code on the phone to not care about the lock
status at all.
None of these are doing a "proper" unlock where you somehow determine the
correct
unlock code and pass it to the phone. All of them have the potential (or are
known)
to cause problems when the phone is upgraded.
The current anySIM release will definitely NOT remain unlocked after a firmware
update since all of its changes would be overwritten by the new version. It is
however probably unlikely to brick the phone unless Apple specifically checks
for its
presence in a future release.
Older anySIM, as we know, caused corruption in the seczone area of the phone
and made
iBricks.
IPSF has so far survived upgrades, but it depends on a bug in the current phone
firmware. Apple did NOT fix this bug from 1.0.2 to 1.1.1, and so anySIM phones
didn't brick. If Apple were to patch that bug, odds are IPSF phones would
brick.
Additionally, while the corruption done in earlier anySIM was to an area of the
phone
which is identical across phones, IPSF causes damage to an area which is known
to
differ between phones. That is, while anySIM's damage could be undone, IPSF's
is
permanent unless you or IPSF has a backup of what was changed.
Original comment by pendorbo...@gmail.com
on 23 Oct 2007 at 5:53
See wiki
Original comment by czim...@gmail.com
on 26 Oct 2007 at 3:09
Original issue reported on code.google.com by
bentfing...@gmail.com
on 23 Oct 2007 at 4:50