Page 1 of 4 1234 LastLast
Results 1 to 10 of 39
Discuss PwnageTool 2.1 on new unibody MacBook/MacBook Pros at the PwnageTool - Hackint0sh.org; Out of interest, has anyone tried using either PwnageTool or QuickPwn on the new MacBook ...
  1. #1
    Newbie Array

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

    Exclamation PwnageTool 2.1 on new unibody MacBook/MacBook Pros

    Out of interest, has anyone tried using either PwnageTool or QuickPwn on the new MacBook and MacBook Pros?

    I've been trying to pwn an iPhone 3G with a MBP but have been getting 2001 errors in iTunes 8.0 all the time. And putting the iPhone into DFU mode (either via iTunes or with PwnageTool/QuickPwn open) was nada!

    Any feedback would be much appreciated!



  2. #2
    J to the T. Shaken, not Stirred Array thecompkid's Avatar

    Join Date
    Jul 2007
    Posts
    1,152
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    75

    Default

    I'm going to have to file this under coincidence simply because I really don't want to imagine that Apple is hack-proofing their computers now too. When they start pulling that BS with OS X, I'm out, no question about it.

    How many times have you tried? Sometimes doing the DFU button ritual takes a little getting used to.

  3. #3
    Newbie Array

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

    Default

    Oh, trust me... I've done it enough times to know that the way I'm going around doing it is the right way.

    I've got my old Alu MBP sitting right next to me, and DFUing with that machine is not a problem.

    At the same time, I have tried different methods in trying to make it work on the new AU MBP... but still end up with the same error!

    While I was trying to find a solution, I was reading a piece where a user had described how hardware could be to blame for an unsuccessful j/b attempt - which is why I wanted to see if anyone else has experienced similar problems.

    Don't think Apple has done this on purpose - but just the fact that the AU MBP *does* have a new hardware design, somewhat.
    Last edited by kras; 10-22-2008 at 06:22 AM.

  4. #4
    Supporter/Apple CEO
    Newsreporter
    Array secretmrx's Avatar

    Join Date
    Feb 2008
    Location
    New Zealand
    Posts
    468
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    49

    Default

    im not sure how they can stop that with a new laptop, I mean going to the effort of stopping 1 exploit on 3 devices with a whole new laptop seems kinda strange... anyway, i am not sure how they would since it's on the iPhone end (unless its some special Mac OS X and/or iTunes but highly unlikely)

    like thecompkid I will put it down to coincidence... Not saying you are bad with iPhone but maybe its a bit slower to interface with the new MacBook. Try another USB port maybe thats the prob.

  5. #5
    Newbie Array

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

    Default

    That *might* be the case... I will try it again when I have the chance, as I was working with my friend's iPhone last night and I had to return it - so nothing for me to test at this stage.

    I agree that Apple would not pull a stunt like this. But I do suspect that there might be a slight hardware change on the new MacBooks that is not allowing PwnageTool/QuickPwn to put the iPhone/iTouch into the special DFU mode required for the firmware upgrade.

    Just to confirm - does iTunes 8.0.1 and PwnageTool 2.1 / QuickPwn work well with one another, irrespective of Mac hardware being used? Google doesn't seem to give me a straight answer to this...


  6. #6
    Professional Array

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

    Default

    I have successfully used pwnage 2.1 with iTunes 8.0.1 on my Mac Mini across a first gen iPhone and a first gen Touch. No issues whatsoever.

    I suggested in HF that it might be a different build of iTunes on these machines (just like QT and OSX is slightly different on these machines) causing the 'issue.'
    Try downgrading iTunes to 7.7.1 or 7.7 (or even just 8.0) to see if pwnage will work that way. Make sure you remove the .kext files metioned in the following website (http://ja1me.net/iTunes_and_Oops/the_whole_deal.html) before installing the older iTunes software. Using Time Machine to backup the 'original' .kext and app files would be a good idea too, just in case.
    Last edited by GenesisDH; 10-25-2008 at 11:09 AM.
    HowardForums member, active in the Apple and related subforums.
    Member of the Samsung Blackjack Users Group

  7. #7
    Professional Array

    Join Date
    Oct 2007
    Posts
    88
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    You guys might want to check this out

    http://www.iclarified.com/entry/index.php?enid=2050

    5. The MacBooks run a special build of OS X, not yet released to other Macs

  8. #8
    Newbie Array

    Join Date
    Feb 2008
    Posts
    9
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    yes I have the same problem with my unibody macbook! When pwnage finish and i successfully enter dfu itunes gives me an error -2001. Anyway i restart the phone and then plug it again holding the home button ... Choose my firmware and restore.. Works great

  9. #9
    Newbie Array

    Join Date
    Oct 2008
    Posts
    1
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    I have to report the same problem. I spent all of last night trying to pwn my iPhone using both QuickPwn and PwnageTool, making custom IPSWs and using the easy installs. Nothing worked, I kept getting iTunes errors and/or having QuickPwn and PwnageTool crash.

    I finally busted out my old MacBook Pro and it worked brilliantly the first time without any problems at all.

    This may just be an issue with different configurations, maybe the new OS X build, I really don't know, but it's definitely a problem.

  10. #10
    Senior Professional Array

    Join Date
    May 2007
    Posts
    122
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    13

    Default

    I have to report the same problem. I have done this hundreds of times and I was totally confused over this error... I am on the new MacBook and I am getting 2001 and 21 errors all the time. It is not possible to set dfu correctly.

    After reading this thread I am now running the procedure on another Mac.

    Hopefully the devs are fixing this in a later release.


 

 
Page 1 of 4 1234 LastLast

Similar Threads

  1. Replies: 0
    Last Post: 09-10-2009, 11:20 AM
  2. Replies: 0
    Last Post: 09-10-2009, 04:00 AM
  3. MacNN: Apple deals: unibody MacBook and MacBook Pros
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 05-06-2009, 12:50 AM
  4. MacNN: Apple refurbs: unibody MacBook and MacBook Pro
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 04-08-2009, 01:00 AM
  5. Replies: 0
    Last Post: 12-05-2008, 11:42 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 09:14 PM.
twitter, follow us!