Therefore, I can confirm that the new baseband is not "patched" and TSIM still working in downgraded iphones.
With 1.1.1 it was not working but maybe something went wrong, so I will retest this later. Now I'll install the "Exploitable" and will test it.
Yep it'd be interesting to see which message is displayed in that case or in an old baseband to be sure that my test is correct (should be as I said but I can make mistakes as well as Skinny07 can confirm )
Or it could be a new error code returned by the baseband that is handled by 1.1.1 and ignored by 1.0.2, as the test validates if Applesaft reached its final initialization stage
Last edited by Zf_; 11-10-2007 at 06:41 PM.
I reprogrammed the TSIM with the "exploit" in a 6230i, SET with the AT&T card in the iphone and switched to vodafone. Whenever I select "Exploitable" I get OK, regardless of using AT&T or vodafone card. So everything looks unchanged.
1.1.1 test to follow...
Wow. Just wow. This supports the hypothesis of additional return codes added in the baseband firmware then, and the application OS telling it to stop.
Truly amazing. The initial bug was pretty lame, but the fix is even worse
Where do you select "Exploitable"?
You are getting OK on a 1.1.1 and a 04.02.13_G Modem Firmware?
Please explain how? I already tried that and got
have there been many independent tests of using 1.1.2 with a TurboSIM though? I've only heard of one from Skinny07 which resulted in strange issues with the phone app crashing, but I'd want to hear a few more reports before being sure that it's not another issue causing this in an isolated case?
I am using a TurboSIM but until there's an activation method I can't help out, as I have no way of activating legitimately with AT&T. Once that hurdle is overcome, I'll happily test this out. Currently running TSIM with 1.1.1, no worries. The fact that you can even register on the network under 1.1.2 seems to suggest the TurboSIM is doing it's thing, and if there's any checks they're in the software. Surely that seems unlikely though...
it's not a isolated case
everyone I have spoken to is aware of the phone/sms app thing, and it is not simply a turbosim problem.
and that is the only thing stopping the TSIM from working under 1.1.2 (the new phone/sms security feature)