AT+XSIMSTATE=1:


+XSIM: 2

+XLOCK: "PN",3,0,"PU",5,0,"PP",5,0,"PC",5,0,"PS",5,0

based on what I'm seeing, the 3 after PN would indicate that the unlock attempt limit has been reached. Not good for me at all.

I guess we are in the right track. Let's watch and work on this thread. I will stop woking on the new thread i opened. It seems that some how we reached the limit of unlocking and something is locked forever.

Let me just restore one more time and then try the minicom again

I will post the outcome soon.

tandalti

well, I am still restoring my phone but in the meanwhile I tried to issue the command in one of the iphone I already successfully unlocked and see what it says.


here is the output from the good unlocked iphone

AT+XSIMSTATE=1
+XSIM: 2

+XLOCK: "PN",4,0,"PU",5,0,"PP",5,0,"PC",5,0,"PS",5,0

OK

Originally Posted by tandalti

well, I am still restoring my phone but in the meanwhile I tried to issue the command in one of the iphone I already successfully unlocked and see what it says.


here is the output from the good unlocked iphone

AT+XSIMSTATE=1
+XSIM: 2

+XLOCK: "PN",4,0,"PU",5,0,"PP",5,0,"PC",5,0,"PS",5,0

OK

Makes sense. Since -"PN",4- means that the phone is unlocked. While iPhones with -"PN",3- as the outcome are now consider unlockable due to the restriction on unlock attempts .

Not a good sign for me at all....

Is this counter in the hardware? Can it be reset?

OK here is the outcome from the iphone that i am not able to unlock and which I just restored in itune (my # 101 restore+unlock attempt.).



AT+XSIMSTATE=1
+XSIM: 2

+XLOCK: "PN",3,0,"PU",5,0,"PP",5,0,"PC",5,0,"PS",5,0

OK



Its 3 means==>>>>limit has been reached.


Man this is a brand new iphone from apple. I am sure I did not do anything wrong during my first unlock attempts. I am 100% sure. I am a unix guy to begin with!


SAM and the rest of the dev-team. We need real help here!

How to reset the counter and start all over.



regards,
Tandalti

I suggest you be careful with automated mega-reflashing tools.

The NOR flash is good for a finite number of erase/write cycles. This is a big number, rated by Intel to be "Minimum 100,000 erase cycles per block" for the iPhone memory. This is impossible to reach with any kind of manual procedure, but you can do it with an automated script. It's very very unlikely that this is your problem, but you should take note of it if you are hammering on the system.

(Re-flashing manually once every 10 seconds for 10 non-stop hours per day, you would have to work for a solid 27 days to hit this limit.)

Well, unless this counter get reset I will not do a reflashing no more. I initially did it as part of a script that I created to run in the iphone vt100 terminal with nohup. I was running it for 7 days. each time I check the unlock status, if it's not unlocked I then cleanup and start all over.



anyway, we ared looking for the dev-team to help.

Hi,

Thanks for trying to solve this. I have a 8Gb unit with "No Sim installed error". I have tried restoring and all the software unlock methods available.

AT+CLCK="PN",0,"00000000"
ERROR
AT+CLCK="PN",2
+CLCK: 0

Seems like it is unlocked.

AT+XSIMSTATE=1
+XSIM: 0

+XLOCK: "PN",4,0,"PU",5,0,"PP",5,0,"PC",5,0,"PS",5,0

OK

Still seems like it is unlocked.

The unit dont recognise any SIM card and hasn´t showed ICCID anytime.

In /var/root/Lockdown I have:
data_ark.plist
device_private_key.pem
device_public_key.pem
pair_records

Should I have more files?

Any ideas? Is this Apples new way of stopping us unlocking our phones?

Originally Posted by tandalti

Well, unless this counter get reset I will not do a reflashing no more. I initially did it as part of a script that I created to run in the iphone vt100 terminal with nohup. I was running it for 7 days. each time I check the unlock status, if it's not unlocked I then cleanup and start all over.



anyway, we ared looking for the dev-team to help.

We really NEED the help of devteam.

IN this webpage http://chickenenchiladagrilledstuftburrito.info/u.htm says that the nor file developed from devteam avoid the checking of NCK, we need they smart guy that found the address in the nor file or in the memory, that check for the locker counter, and put a 0 in this counter