• Your favorite

    Apple

    ,

    iPhone

    ,

    iPad

    ,

    iOS

    ,
    Jailbreak
    , and
    Cydia
    site.
  • UPDATED -- 10.5.6 Breaks DFU Mode?


    Update #2:
    Three official options from dev team

    1. Replace the following plugin kexts from within IOUSBFamily.kext with the ones from 10.5.5 and then rebuild kextcache.
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriver.kext
    2. Use a USB hub in-between the DFU device and the Mac and insert/reinsert the iPhone’s USB cable.
    3. Use a PwnageTool created .ipsw on Windows.

    Cash Update: So I've been playing with this for a few hours now. 10.5.6 will not let you use DFU mode to restore custom firmware to a phone that IS NOT already pwnd. Replacing MobileDevice.framework with the previous version does not seem to matter either -- have not tried replacing the framework and downgrading iTunes or replacing other frameworks/haven't ahd time to dig in to the drivers and replace yet. A USB hub will work just fine with no issues at all to pwn on 10.5.6 with the latest iTunes. Had zero issues with my powered USB hub. Tired now and not interested in restoring anymore tonight so some updates from our members. One report says that QuickPwn works fine. If your iPhone is ALREADY pwnd and you need to restore with a custom firmware it has been reported to work. Windows users report no issues at all (of course) this is just a mac thing with the 10.5.6 update.

    According to some iPhone news sites, the latest Mac OS X release (10.5.6) disables the use of DFU mode. This can be bypassed by plugging your iPhone into a USB hub. The Dev Team has been notified on this and a fix will probably be here soon. For now, do not update to 10.5.6 if you want to jailbreak your device unless you absolutely have to...or have a spare USB hub.

    Basically it scattered reports are claiming that everything will work properly if you are connected to a USB hub instead of directly to the computer. The idea behind this is that the drivers for the USB hub will still allow you to connect in DFU and do your thing where the updated drivers in 10.5.6 when you connect directly to the computer would be fubared. What also would probably work is if you took the 10.5.5 [script]drivers[/script] framework and stuck it on 10.5.6.

    Here at MMi we will confirm things sometime tonight. If you have tested this out yourself post up!

    Oh and thanks to strchris for making his first post on our forums earlier today to warn the rest of us jailbreakers of the potential problem.

    Via [iPhoneAlley and TUAW]
    This article was originally published in forum thread: UPDATED -- 10.5.6 Breaks DFU Mode? started by DoerrFan View original post
    Comments 47 Comments
    1. cricketlang's Avatar
      cricketlang -
      good to know. even though i dont work with macs i will keep this info on file. the approach seems similar to the one with the new macbooks. dev team will rise about all
    1. Poseidon79's Avatar
      Poseidon79 -
      Uuuuuh... this is gonna sound dumb, but what's a USB "hub" and why does this bypass the issue?
    1. cricketlang's Avatar
      cricketlang -
      a usb hub is like one of those things you plug into a laptop or computer to get more usb ports......like this:

    1. Je5's Avatar
      Je5 -
      Ok so how does this not affect the phone it is using a USB isnt it...?
    1. cricketlang's Avatar
      cricketlang -
      its probably something to do with drivers. the hub uses its own drivers usually as it packs 4 ports into one so it has to do something special. just use a hub....its simple
    1. tattoojack's Avatar
      tattoojack -
      thank god i just got an externally powerd hub!
      because the one listed above will not work for iphones.
      not enough power to charge.
    1. cricketlang's Avatar
      cricketlang -
      ^^^^yeah i was just showing an example of what a hub was. thats all. it was the first one that showed up on google. hahahahaha
    1. jiniej's Avatar
      jiniej -
      Uuuuuh... this is gonna sound dumb, but what's a USB "hub" and why does this bypass the issue?
      Heh heh heh
      That made me chuckle.

      And yeah, using the hub probably has something to do with the drivers, like cricket lang said. Just reiterating...
    1. toothy17's Avatar
      toothy17 -
      Now The Next Thing We Will Have To Worry About Is Apple Getting iTunes To Disable It But Thats Y We Love The Dev Team To Fix These Encounters
    1. Chase817's Avatar
      Chase817 -
      Oops. I could've used that warning before I upgraded 5 MINUTES AGO.
    1. StevenSimpson's Avatar
      StevenSimpson -
      Quote Originally Posted by Chase817 View Post
      Oops. I could've used that warning before I upgraded 5 MINUTES AGO.
      me too!!

      Oh well...I have a USB hub around here somewhere...
    1. ddfilms's Avatar
      ddfilms -
      I am on 10.5.6 and i just jailbroke and unlocked an iPhone today with quickpwn, DFU worked fine.
      FYI
    1. StevenSimpson's Avatar
      StevenSimpson -
      Quote Originally Posted by ddfilms View Post
      I am on 10.5.6 and i just jailbroke and unlocked an iPhone today with quickpwn, DFU worked fine.
      FYI
      What hardware are you running?
    1. jackyk's Avatar
      jackyk -
      I'm successfully restoring with a custom 2.2 ISPW on 10.5.6. Instead of putting the iPhone into DFU, I put it into regular recovery mode.

      When in this mode on the iPhone the iTunes logo and the USB cable is shown (Apple default), or "Steve" (Standard Pwnage) or your custom recovery logo.
      1. Disconnect iPhone from your PC/Mac if not done already.
      2. Hold Power/Sleep until the red slider shows up, slide to shut the iPhone down. If this aint work hold Power/Sleep and Home until the iPhone shuts down. Put it aside.
      3. Start iTunes on your PC/Mac and make sure to have the latest version.
      4. On the iPhone press Home button and keep holding it while connecting the iPhone to your PC/Mac.
      5. iTunes will detect an iPhone in recovery mode, the iPhone shown the recovery logo.
    1. 808mp5's Avatar
      808mp5 -
      hehe... this post should have came before the update one
      bootcamp FTW
    1. ddfilms's Avatar
      ddfilms -
      Quote Originally Posted by StevenSimpson View Post
      What hardware are you running?
      macbook pro with 10.5.6.

      maybe i got lucky.?.

      but it did work fine.
    1. LrdBane's Avatar
      LrdBane -
      LOL like i was saying in the 1st 10.5.6 update post. Its really strange that Apple would do this to try to not use DFU. There would be much more effective ways. And with a simple USB hub as a easy bypass is kinda funny too. I dont know whats going on in Cupertino but if they truely wanted to lock it down they could. And even then where there's a lock, theres an unlock
    1. boneheadxan's Avatar
      boneheadxan -
      What about for the Unibody Macs? Last I remember, I couldn't enter DFU mode through them
    1. Je5's Avatar
      Je5 -
      Wow yeah this actually worked I just upgraded and pwned my buddies iPhone and it worked and I upgraded last night... !!
    1. pranz518's Avatar
      pranz518 -
      Quote Originally Posted by LrdBane View Post
      LOL like i was saying in the 1st 10.5.6 update post. Its really strange that Apple would do this to try to not use DFU. There would be much more effective ways. And with a simple USB hub as a easy bypass is kinda funny too. I dont know whats going on in Cupertino but if they truely wanted to lock it down they could. And even then where there's a lock, theres an unlock
      My guess is that Apple isn't trying to break pwnage but there's just an incompatibility in the drivers. Or, since most "normal" iPhone owners don't ever need DFU, they may have just disabled it since it's not necessary. Like you said, there are far more effective ways to block Pwnage if Apple cared, but they don't - more jailbreaking = more iPhones sold.