Results 1 to 4 of 4
Discuss Unlock 05.14.02 (not possible currently) at the Ultrasn0w (3G(S)/iPhone 4 unlock) - Hackint0sh.org; Hey guys after an unintentional upgrade to 4.1 by my brother I am unable to ...
  1. #1
    Newbie Array

    Join Date
    Sep 2010
    Posts
    3
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default Unlock 05.14.02 (not possible currently)

    Hey guys after an unintentional upgrade to 4.1 by my brother I am unable to revert to the previously unlocked state (no service problem now). Can anyone help me? Below is more info:

    Current version: 3.1.3 (7E18) (jailbreak after downgrading from 4.1)
    Current baseband: 05.14.02
    Serial number: 86903
    Model: MB046LL

    I know the problem now is baseband 05.14.02 is there anyway at this point of time that I can unlock it or downgrade the baseband?

    Thank you all



  2. #2
    Super Moderator Array Olethros's Avatar

    Join Date
    Sep 2007
    Location
    Norway
    Posts
    8,360
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    439

    Default

    No unofficial unlock (ultrasn0w) possible at that baseband. There are no plans or rumours about any update to ultrasn0w to unlock that version. Based on past history I would not expect another ultrasn0w update until iOS 5.

    You have an AT&T locked iPhone they refuse to offer official unlock.

    The only chance you have is if your iPhone has the 3rd to 5th digits of the serial number xx827xxxxxx or lower. Then you can maybe use fuzzyband.
    Please read the stickies & search forum before posting!
    How to report an iTunes restore/update fail in a useful manner
    -

    iPad 3G 64GB (4.3.3, Redsn0w) oldest SHSH 3.2.2
    iPhone 4 32GB (4.2.1, Redsn0w JB-monte) oldest SHSH 4.1
    iPhone 3GS 32GB (4.3.3; Pwnagetool) factory unlocked oldest SHSH 3.1
    iPhone 8GB (3.1.3; Pwnagetool) AT&T Locked - Unlocked with bootneuter

    -
    Did we solve your problem? Got a dollar or two spare ? Donate!

  3. #3
    Newbie Array

    Join Date
    Sep 2010
    Posts
    3
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    So it means that the road block here is the baseband itself? After some research i found that even if the dev comes up with a jailbreak for 4.1 it will be achieve by persevering the older baseband thus allowing user to unlock it using currently available means.

    Does this means that for those of us who unfortunately already upgraded to 4.1 now has little chance of saving our iphones even if new jailbreak for 4.1 is available?

  4. #4
    Super Moderator Array Olethros's Avatar

    Join Date
    Sep 2007
    Location
    Norway
    Posts
    8,360
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    439

    Default

    Quote Originally Posted by fabuloso View Post
    So it means that the road block here is the baseband itself? After some research i found that even if the dev comes up with a jailbreak for 4.1 it will be achieve by persevering the older baseband thus allowing user to unlock it using currently available means.

    Does this means that for those of us who unfortunately already upgraded to 4.1 now has little chance of saving our iphones even if new jailbreak for 4.1 is available?
    Yes. People who accidentally upgraded or ignored this clear message Dev-Team Blog - It's a trap! from the iPhone Dev Team are possibly stuck without unofficial unlock for ever.

    TinyUmbrella can block baseband upgrade for iPhone 4. See Twitter / semaphore: I've also updated my blog ... for details.

    iPhone 3G and old bootrom 3GS must use custom IPSW (pwnagetool) to avoid baseband update. There are no official updates for pwnagetool to support iOS 4.1 (yet)

    As of now, I don't know any way that would block baseband update for new bootrom 3GS. There was a technique that worked from 3.1.2 to 3.1.3 ( Preventing baseband update as a last-ditch effort [iPhone Dev Team] ) I have not received any confirmation that this works for iOS 4.0 or higher. I seem to recall that there was a post from p0sixninja saying it would not work with 4.0 due to changes in the restore process.

    You have a 3G but you must have purchased it recently, most 3G owners learnt this the hard way with iOS 2.2.1 or iOS 3.1.x. My point is this is old history and a quick search would have produced hundreds of threads with this same information.

    Closing this thread, I have provided all the relevant information. This is an old issue and well documented already.
    Please read the stickies & search forum before posting!
    How to report an iTunes restore/update fail in a useful manner
    -

    iPad 3G 64GB (4.3.3, Redsn0w) oldest SHSH 3.2.2
    iPhone 4 32GB (4.2.1, Redsn0w JB-monte) oldest SHSH 4.1
    iPhone 3GS 32GB (4.3.3; Pwnagetool) factory unlocked oldest SHSH 3.1
    iPhone 8GB (3.1.3; Pwnagetool) AT&T Locked - Unlocked with bootneuter

    -
    Did we solve your problem? Got a dollar or two spare ? Donate!

 

 

Similar Threads

  1. Replies: 18
    Last Post: 03-03-2008, 10:09 PM
  2. Replies: 2
    Last Post: 02-14-2008, 04:55 PM
  3. Replies: 0
    Last Post: 01-29-2008, 02:17 PM
  4. Replies: 8
    Last Post: 01-24-2008, 06:39 PM
  5. Replies: 0
    Last Post: 09-27-2007, 03:30 PM

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 12:25 AM.
twitter, follow us!