Page 4 of 8 FirstFirst 12345678 LastLast
Results 31 to 40 of 76
Discuss Confirmed up- and downgrade from 1.02 to 1.1.1 to 1.02 with IPSF unlocked phone at the iPhone "2G" (Rev. 1) - Hackint0sh.org; Originally Posted by petemag What are you even doing here on this forum? sorry? me? ...
  1. #31
    Zibri's part-time barrister Array

    Join Date
    Aug 2007
    Posts
    145
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    Quote Originally Posted by petemag View Post
    What are you even doing here on this forum?
    sorry? me? and you?


  2. #32
    iPhone DevTeam Array

    Join Date
    Aug 2007
    Location
    Always sunny Los Angeles, California
    Posts
    421
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    The IPSF unlock doesn't leave an invalid token in the secpack like the free unlock does. That's why the IPSF unlock still works after doing 1.1.1->1.0.2 with 4.01.13_G firmware still in place.
    Last edited by MuscleNerd; 09-30-2007 at 07:44 PM.

  3. #33
    Professional Array

    Join Date
    Sep 2007
    Posts
    71
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    10

    Default

    Quote Originally Posted by MuscleNerd View Post
    The IPSF unlock doesn't leave an invalid token in the secpack like the free unlock does. That's why the IPSF unlock still works after doing 1.1.1->1.0.2 with 4.01.13_G firmware still place.
    So when the dev team figure out how to re-lock phones unlocked with the Dev Team method, and then unlock it without any invalid token remaining behind in secpack, then we should expect to have the same results as IPSF's unlock.

    Correct me if I am wrong anyone ...

  4. #34
    Zibri's part-time barrister Array

    Join Date
    Aug 2007
    Posts
    145
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    Muscle, could be right: but is supposed that ANYTHING is rewrote during updates. I can believe that Apple does not have "reverse enginereed" iUnlock & ISPF software to lock us out. The main question is: HOW can survive the upgrade?

    because she (the pach) survived. and is healty and working.
    Last edited by iRev; 09-30-2007 at 07:52 PM.

  5. #35
    iPhone DevTeam Array

    Join Date
    Aug 2007
    Location
    Always sunny Los Angeles, California
    Posts
    421
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    If the secpack needed by 4.01.13_G were available, the dev team's free unlock method could be easily ported to the newer firmware. The address to patch to ignore the lock status is easy to find (well, easy now...not so easy before it was found in 3.12 and found again in 3.14).

    But, that secpack is not available. It's on the firmware dmg that hasn't been decrypted yet. So, the dev team's free unlock method cannot be ported yet.
    Last edited by MuscleNerd; 09-30-2007 at 08:07 PM.


  6. #36
    Zibri's part-time barrister Array

    Join Date
    Aug 2007
    Posts
    145
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    i've understood, but this is not the point. IPSF seems does not affect in any way the secpack, and, vicariously, is not affected...

  7. #37
    mr_
    mr_ is offline
    Senior Professional Array

    Join Date
    Sep 2007
    Posts
    100
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    12

    Default

    Quote Originally Posted by MuscleNerd View Post
    The IPSF unlock doesn't leave an invalid token in the secpack like the free unlock does. That's why the IPSF unlock still works after doing 1.1.1->1.0.2 with 4.01.13_G firmware still in place.
    Makes sense. But why does the dev team's token create all these problems? How is what it writes different from what would have been generated by an attempt by the user to unlock with the wrong code (00000000)?

    And if a valid unlock token is needed, how come ISPF unlock works, unless, of course, the unmodified secpack contains the valid unlock token to begin with (unlikely), or ISPF can generate valid tokens (also unlikely).
    Last edited by mr_; 09-30-2007 at 08:15 PM.

  8. #38
    iPhone DevTeam Array

    Join Date
    Aug 2007
    Location
    Always sunny Los Angeles, California
    Posts
    421
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    The IPSF method exploits the fact that nulling out the version string in the firmware itself lets you do things you'd otherwise need the secpack for.

    Their method was reverse engineered within a day of its release. But the dev team (at least sam) has said on this forum that they wouldn't go off and copy the IPSF method...that they would stick to their own method (hacker ethics, etc).

  9. #39
    Rookie Array

    Join Date
    Sep 2007
    Posts
    11
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Can you dump the baseband and send it to the dev team?
    Maybe it comparing it to the locked - by anysim - baseband will help them?

  10. #40
    iPhone DevTeam Array

    Join Date
    Aug 2007
    Location
    Always sunny Los Angeles, California
    Posts
    421
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    The 4.01 NOR dump is already available. (You need to go to that older version of the wiki page that I've linked because the NOR dump url was removed later on due to copyright violations).


 

 
Page 4 of 8 FirstFirst 12345678 LastLast

Similar Threads

  1. Replies: 1
    Last Post: 07-28-2008, 02:53 PM
  2. 1.1.2 IPSF Unlocked Phone to 1.1.3? How to?
    By mongoose8p in forum iPhone "2G" (Rev. 1)
    Replies: 4
    Last Post: 02-12-2008, 04:54 AM
  3. IPSF with an HW-unlocked phone
    By fabiopigi in forum iPhone "2G" (Rev. 1)
    Replies: 5
    Last Post: 10-17-2007, 01:51 AM
  4. Replies: 10
    Last Post: 10-07-2007, 05:04 PM
  5. Replies: 11
    Last Post: 09-11-2007, 03:57 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin®
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 05:53 AM.
twitter, follow us!