|
|||||||||
|
|||||||||
|
|||
|
Another thing which is very interesting that TA forgot to mention is:
- an international phone (fulling funtional) which means the baseband is unlocked right? - pwned the international phone. It became locked. So, the saying about once the baseband is unlocked it stays unlocked is not the case here. Eventhough the BB version remains the same. - Restored the phone with original apple firmware. Hooked it up to itunes, phone fully working again. - So even if the the imei, serial/model are the same. The pwnage action (jb/act) changed things in the phone, itunes detected that and turned the phone to "lock" state.
__________________
** If you just want to support hackint0sh.org with a donation click here ** Last edited by dtube; 08-07-2008 at 07:18 PM. |
|
||||
|
Interesting read
Thanks
__________________
- Read the stickies and search the forum before posting! If you want to become a Hackint0sh supporter click here---------- Follow Hackint0sh Follow Me
|
| Sponsored links Remove advertisements | |
|
|
|
|
|
|||
|
Quote:
I can't comment on TA's findings, but what you describe here is expected. To test this theory, extract your NCK manually, then pwn your phone and pass your NCK to the baseband manually. Your phone will be unlocked again. |
|
|||
|
My experience with pwning is a little different: I live in Greece, and I just received an originally unlocked iphone 3g from Italy.
I pwned it, and when the phone rebooted the familiar please connect to itunes to activate screen came up on the iphone. With my Greek SIM card inside, I connected the iphone to the computer, and in fragments of a seconds it activated. The activation was so quick that I do not believe any communication with an apple server took place. Last edited by akouris; 08-07-2008 at 07:38 PM. Reason: wrong syntax |
|
|||
|
Comparing the behaviour of a Swisscom (locked) and Mobistar (unlocked) iPhone, this is what I found out on the iTunes-unlocked Belgium iPhone by logging all type of communication:
a.) There is a new kind of activation which is called "WildcardActivation" (in comparison to the "old" FactoryActivation) Code:
<key>ActivationRandomness</key>
<string>12345-123456-A123-ABCDE012345</string>
<key>ActivationState</key>
<string>WildcardActivated</string>
<key>BasebandMasterKeyHash</key>
<string>ABCDEFG012345ABCDEFG012345ABCDEFG012345</string>
<key>BasebandThumbprint</key>
<string>1234567890123456789012345678901234567890</string>
<key>BuildVersion</key>
<string>5A347</string>
<key>DeviceCertRequest</key>
<data>...</data>
<key>DeviceClass</key>
<string>iPhone</string>
<key>InternationalMobileEquipmentIdentity</key>
<string>268011234567890</string>
<key>ModelNumber</key>
<string>MB489</string>
<key>ProductType</key>
<string>iPhone1,2</string>
<key>ProductVersion</key>
<string>2.0</string>
<key>SIMStatus</key>
<string>kCTSIMSupportSIMStatusNotInserted</string>
<key>SerialNumber</key>
<string>ABCDEFG1Y7H</string>
<key>SupportsPostponement</key>
<true/>
<key>UniqueDeviceID</key>
<string>AABBCCDDEEFF0011223344556677889900</string>
b.) The unlock is done by sending some data (not only NCK, it looks like CERTS/KEYS are sent). The whole process seems to be working like this: a.) iPhone is connected to iTunes b.) iTunes identifies iPhone by serial no. and sends activation request to albert.apple.com c.) the activation records is created and return to iTunes d.) iTunes "syncs" the activation record to the iPhone e.) CommCenter is sending the unlock commands to the Baseband From the iPhone point of view: - A lock is signaled from baseband to ComCenter: - CommCenter asks for activation level (via iTunes) - CommCenter sends unlock commands (2 checks, 4 sequences) to baseband, succeeding it results in Code:
Lock changes state from +XLOCK: "PN",1,1 to +XLOCK: "PN",1,0 after the 4 unlock sequences have been sent BTW, the unlock does not survie a restore and it has to be re-activated after every restore. I verified this a couple of times, even with 2.01 and baseband ICE2-01.48.02 Quote:
Last edited by todro; 08-07-2008 at 10:26 PM. |
| Remove advertisements | |
|
|
|
|
|
||||
|
Hum..... very interesting...
I'm wondering how this fits in the scenarios posted by TA_Mobile. Now, if the restore "erases" the "unlock", then there are 3 options: 1) It writes over some area where the unlock state is stored (seczone?) 2) The unlock state is not in the seczone, and therefore may fall outside the protection of the bootloader sig check. 3) The unlock is actually stored as OS files, and the whole process to "lock/unlock" the baseband is controlled by a software component (some part of CommCenter?) We need to examine more evidence, and we need the expert opinion of the Dev Team... |
|
|||
|
Quote:
And yes, it seems to be the CommCenter itself which is sending the unlock sequences Last edited by todro; 08-07-2008 at 11:53 PM. |
| Sponsored links Remove advertisements | |
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|
|
|