1. Welcome to the new MacRumors forums. See our announcement and read our FAQ

iOS 4.2.1 Has Baseband Requirement

Discussion in 'Jailbreaks and iOS Hacks' started by Applejuiced, Nov 23, 2010.

  1. macrumors Nehalem


    Apple has created another roadblock for jailbreakers and unlockers with the introduction of a baseband requirement for iOS.

    BigBoss relays the following information from Semaphore.

    It seems that Apple has decided to put a baseband requirement on iOS. So at this point, if you are using Saurik’s server or tiny umbrella and trying to restore 4.2.1 on an iPhone 4, you will end up in recovery mode and tiny umbrella will not be able to pull you out of recovery. In this case, you will have to restore 4.1 again or you will have to restore 4.2.1 stock and be tether jailbroken. (Of course, I recommend 4.1 and not bothering with 4.2.1 at all). If you are an unlocker, this is a no brainer. Do not update to 4.2.1 even to test it at this point.
    So the iphone 4 trick where you used TU to update while maintaining your Baseband doesnt work any more. Only way to go around it would be with a custom IPSW that doesnt update the BB.
    This sucks.
  2. macrumors 68020


    Surprised it took so long for you to post this. It's been out for several hours :)

    Let the games begin!!
  3. macrumors Nehalem


    I know, I'm usually quicker:)
  4. macrumors 65816

    this news really bites. Preserving baseband with TU was such an easy process compared to coaching noobs through custom ipsw creation.
  5. macrumors 603


    The Giant is trying every possible way to break the Jailbrake/Unl0cked community.
  6. macrumors Nehalem


    They can't do anything about the limerain exploit so they went after the baseband preservation now.
    Hope The Dev Team puts out an updated pwnage version soon.
  7. macrumors 603


    I wonder if this is what's delaying the release of PwnageTool. Usually PwnageTool for the old bootrom devices is out before Redsn0w. Presumably they have to patch this new baseband check out of the custom ipsw.
  8. macrumors 601


    Hm. Well, I preserved my baseband although I don't need to unlock.

    I guess I'll wait for more things to become suited with 4.2.1 before updating anyways, thanks for the info.
  9. macrumors 603


    That's most likely the case. They're trying to circumvent this new problem. Hope they can hack it soon.
  10. macrumors 603


    Me too! I've been needing to restore, and I've been holding off for 4.2.1.
  11. macrumors 6502

    this is funah

    Apple is doing a good job at making jailbreaking more complex and unattractive for an end user with this move.

    Things are starting to get scary when Tinyumbrella cannot kick the iDevice out of recovery mode.
  12. macrumors 65816

    Patience. Everything that can be locked can be unlocked. The engineers at Apple aren't Gods above mortal men. :)
  13. macrumors newbie

    i'm relatively new to the jailbreaking/unlocking scene. I jailbroke my first iPhone a few months ago and was wondering why this is such a problem all of a sudden? I am not too good with computers, but I was able to create a custom ISPW for my iPhone with ease? So wouldn't this be the same concept as before?
  14. macrumors newbie

    I hope you're right! I too am eagerly awaiting an unlock, as I'm stuck in China, with a 3G on 4.1 with 5.14.02 :mad::confused:
  15. macrumors 6502

    Creating a custom IPSW is easier than using TU with Pwnage. That is all I ever use to JB.

    The tutorials at iClarified make it so easy a caveman could do it.
  16. macrumors 68000

    this is just for the iphone 4??

    or 3gs and 3g too?
  17. macrumors 6502a

    Only on IP were you previously able to use TU to update and keep baseband. In essence, with the 4.2.1, it forces the IP4 to also update the baseband like 3G and 3GS all along.

Share This Page