Apologies for the thread title, but this board is so active, important requests get lost in many other topics that are either duplication of existing material (if only people searched) or are trivial requests that again have been discussed several times before and can be fixed (if only people searched) :-)


I have followed this whole scene for months now (from the beginning), and whilst not part of the dev team, have helped many people by having a good understanding of all the processes that led up to today which many people might have missed coming into the scene later on.

Now I still could be wrong about certain things, I'm not ashamed to admit that but I will now get onto the issue at hand :-)

I spoke at length on IRC the other night with a guy who is having an unlock problem. I could tell this guy knew what he was doing which is why I was intrigued to see why he was still having trouble. He was getting an "error" trying to issue the Facility Lock/Unlock command which is common for other reasons but I knew the usual 'novice' problems were not apparent here.

After investigation, I got him to run an AT+XSIMSTATE=1 and tell me the results.
The results showed that the Unlock Count have been reached

He has correctly re-flashed the firmware several times which proves that this does not help once the unlock count has been reached!

What I would like to know is if its possible Grey, Guest184 or the other guys, with their knowledge of reversing the firmware are able to bypass the 'Unlock Count' routine in much the same way that they bypassed the 'NCK" routine.

This would provide a perfect nor solution then, thus allowing any phone to be unlocked, even if the unlock counter has been reached.



Thanks in advance for your time.






.

__________________
Aka: drh on the IRC channels


To Donate, Click Here.

bump guys keep this topic up

this sounds serious... there's a limit to the number of unlock done..

If there is a limit to number of unlock attempts that can be made on the iPhone, THIS THREAD MUST BE MADE A STICKY.

It's important to warn people about this limit. It would suck bad if you bought an iPhone with the unlock limit reached or exhausted the attempt count yourself.

It would have helped me a lot b/c it would seem that my iPhone is now unlockable. BE WARNED, PEOPLE!!

Related thread:
http://hackint0sh.org/forum/showthread.php?t=7609

i think problem should be somthing else as we are not entering som sort code or wrong NCK or somthing like that by which usally maximum counter reached problem accure mostly
BUT here we are patching firmware itself so there is no question atall for unlock limits really its logical

@healeydave

Can you please post the result he got with AT XSIM STATE command?


wbr

yousha

__________________
INDIAN

wwwDotVirasatElectronicsDotCom

I will take a look into it later this day and tell you the point to patch some time tonight.

Thanks Sam.

__________________
Aka: drh on the IRC channels


To Donate, Click Here.

His XSIMSTATE response is:

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

The Three after the "PN" denotes the unlock counter has been exceeded.

The patched nor that the software (and hardware) unlock used only circumvents the requirement for a valid NCK (e.g. "00000000") !!!

It does not circumvent the Facility Lock/Unlock process which is why you still have to do the AT+CLCK command. If this has been entered wrong through typos, cutting & pasting errors etc, it does not take much to enter this command in wrong a few times!

As I have already said, this guy has re-flashed the FLS and the EEP files with virgin files and the lock counter has stayed intact so further circumvention is required (against the Lock Counter) for a perfect solution!




.

__________________
Aka: drh on the IRC channels


To Donate, Click Here.

Please keep me informed about this (with any result)i will be thankfull

wbr

yousha

__________________
INDIAN

wwwDotVirasatElectronicsDotCom

healeydave , maybe u can let us know roughly how many times did you try doing the unlocking procedure.
if any pals here did more than you did, maybe it could be some code error or wrong insertion of commands..