Results 1 to 8 of 8
Discuss Back To iPhone From Android With 4.1 BB 02.10.04 at the iPhone 4 - Hackint0sh.org; After one year on the Android camp, I returned to the iOS camp with 2 ...
  1. #1
    Senior Professional Array kwanbis's Avatar

    Join Date
    Jan 2008
    Posts
    104
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    14

    Default Back To iPhone From Android With 4.1 BB 02.10.04

    After one year on the Android camp, I returned to the iOS camp with 2 new iPhone 4s, and while I have Jailbroke/Unlocked iPhone 2G, 3G, and 3GS in the past, the iPhone 4 scene is a little bit more scarier.

    One of the iPhones I bought came already unlocked. It has a limera1n icon on the desktop, it is at iOS 4.1 with modem firmware 02.10.04.

    The other is NOT unlocked, and it is also at 4.1 with BB 02.10.04.

    I have been checking the forums and iClarified, but I'm a little bit confused.

    What I understand is that 4.2.1 is still not simple, because it is a tethered jailbreak/unlock, and that I should wait for something more final.

    Since both phones are at 4.1/2.10.04, it seems that that is the iOS I should stay at, but I'm not 100% sure.

    I also read about SHSS or something that I should have stored, but now it is a little late.

    So, considering that i need to UNLOCK the phones, the questions are:

    1) should I try to jailbreak/unlock 4.1?
    2) what method is safer? pwnagetool, limera1n, greenpoison, redSnow?
    3) do i need to do something before the jailbreak/unlock?
    4) do i try to re-flash the ALREADY unlocked iPhone?
    5) are iClarified tutorials still among the best, or should i try something else?

    Thanks, and sorry for the re-newbiness.



  2. #2
    Super Moderator Array n1ckn4m3's Avatar

    Join Date
    Mar 2009
    Location
    USA
    Posts
    2,717
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    145

    Default

    Hrm. You've got some conflicting information there, let me address one point at a time:

    1) You say you've got an iPhone 4 running 4.1 with the 02.10.04 baseband which is unlocked, but presently, no unlock exists for the 02.10.04 baseband on that device. Is the phone a factory unlocked model? If not, it's not really possible for the device to be unlocked at that baseband (yet). Do NOT attempt to re-flash this device, if you get stuck in recovery mode and can't break out, you will be forced to upgrade to 4.2.1 and that is not going to get you any closer to what you want.

    2) You're correct, 4.2.1 is less than spectacular at present -- the jailbreak is tethered for the iPhone 4 and several of the key software packages have not yet been updated to be 100% stable on 4.2.1. It is recommended that you stay at 4.1 if possible.

    3) You're correct about SHSH files. At this point you can only obtain an SHSH for 4.2.1, meaning if you have to restore either of these phones, you will ONLY be able to restore to 4.2.1 and will not be able to restore 4.1 again. It doesn't matter that you're currently running it, as Apple is only signing 4.2.1 now. I'd still recommend getting your SHSH on file for 4.2.1 as you may need it in the future for other jailbreaks or unlocks.

    4) With regard to the other questions: we primarily recommend using PwnageTool or redsn0w, depending on the specific iOS variant. It also depends what your ultimate goal is going to be. Because you can't unlock either of these right now, I'd recommend waiting before doing anything or attempting to upgrade the devices -- if you end up on 4.2.1 with the latest baseband, you'll find yourself in an even worse boat than you're in right now -- at least you have an untethered jailbreak on 4.1! You should always complete a full backup of your device before a jailbreak so that you can restore from it if anything terrible happens, but it's not 'required'. And yes, iClarified is still pretty solid on their instructions -- the jailbreak and unlock wizards cover all current devices and all current firmware and baseband revisions, so with the right information you can really get a very clear indicator of the current state of jailbreak/unlock for your phone.

    Good luck!
    The preceding forum post has been brought to you by the letter "N" and the number 42.

    iPhone 4, 32GB (iOS 6.1.2 | evasi0n | SHSH: 4.0 - 6.1.2)
    iPad 2 3G, 64GB (iOS 6.1.2 | evasi0n
    |
    SHSH: 4.3 & 4.3.3 - 6.1)

    Restore problems? Read this: http://www.hackint0sh.org/f137/130802.htm

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


  3. #3
    Senior Professional Array kwanbis's Avatar

    Join Date
    Jan 2008
    Posts
    104
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    14

    Default

    First of all, thanks for taking your time to respond.

    I'm confused about the BB. Mine is at 02.10.04, but I see there are other BB which appear to be NEWER, that are unlock-able: 04.26.08, 05.11.07, 05.12.01, 05.13.04, 06.15.00, or 01.5.

    I understand that 06.15.00 is an iPad BB, and I should try to stay away from that.

    But the others looks like legit iPhone4 BBs, so I was wondering why can't I first somehow upgrade the BB to either of those, and then be able to unlock.

    Is it because of some type of Apple signature?

  4. #4
    Super Moderator Array n1ckn4m3's Avatar

    Join Date
    Mar 2009
    Location
    USA
    Posts
    2,717
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    145

    Default

    Quote Originally Posted by kwanbis View Post
    I'm confused about the BB. Mine is at 02.10.04, but I see there are other BB which appear to be NEWER, that are unlock-able: 04.26.08, 05.11.07, 05.12.01, 05.13.04, 06.15.00, or 01.5.
    They appear newer but are in fact not. There is only one newer iPhone 4 baseband than the one you have (the iPad BB 06.15 hack is ONLY for 3G / 3GS phones, it does not work on the iPhone 4, entirely different chip, don't try it!), and that revision is 03.10.01, which comes with iOS 4.2.1 (also not unlockable at present).

    Keep in mind that since the baseband on the iPhone 4 is a different chip than the 3G/3GS, it uses a different numbering scheme, so while the other numbers may appear to be from newer revisions, they're not -- just lower numbered revision of the software for a different baseband itself.
    The preceding forum post has been brought to you by the letter "N" and the number 42.

    iPhone 4, 32GB (iOS 6.1.2 | evasi0n | SHSH: 4.0 - 6.1.2)
    iPad 2 3G, 64GB (iOS 6.1.2 | evasi0n
    |
    SHSH: 4.3 & 4.3.3 - 6.1)

    Restore problems? Read this: http://www.hackint0sh.org/f137/130802.htm

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


  5. #5
    Senior Professional Array kwanbis's Avatar

    Join Date
    Jan 2008
    Posts
    104
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    14

    Default

    I understand now. So, what are the BB levels for iPhone 4? And I assume there is no way to downgrade the BB as of now.


  6. #6
    Super Moderator Array n1ckn4m3's Avatar

    Join Date
    Mar 2009
    Location
    USA
    Posts
    2,717
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    145

    Default

    Quote Originally Posted by kwanbis View Post
    I understand now. So, what are the BB levels for iPhone 4? And I assume there is no way to downgrade the BB as of now.
    First and foremost, you're correct -- the iPhone4 is one of the rare models that DOES allow for a baseband downgrade, BUT it requires an SHSH check based on a randomly generated number, so it's not susceptible to the man-in-the-middle attack that the iOS SHSH was. As such, it's not possible to request and 'store' the SHSH response to allow for downgrading. This means that it IS possible to downgrade the baseband on the iPhone 4 to any current baseband that Apple is signing, for example, for the 2 weeks or so that Apple was signing both 4.1 and 4.2.1, you could install 4.2.1, upgrade the baseband, then do a factory restore back to 4.1 and it would downgrade the baseband back to the 4.1 baseband.

    In response to your question about basebands, here you go:
    Code:
    iOS 4.0    - 01.59.00 (Release version)
    iOS 4.0.1  - 01.59.00
    iOS 4.0.2  - 01.59.00
    iOS 4.1    - 02.10.04
    iOS 4.2    - 03.10.01
    iOS 4.2.1  - 03.10.01
    Last edited by n1ckn4m3; 12-14-2010 at 02:25 PM.
    The preceding forum post has been brought to you by the letter "N" and the number 42.

    iPhone 4, 32GB (iOS 6.1.2 | evasi0n | SHSH: 4.0 - 6.1.2)
    iPad 2 3G, 64GB (iOS 6.1.2 | evasi0n
    |
    SHSH: 4.3 & 4.3.3 - 6.1)

    Restore problems? Read this: http://www.hackint0sh.org/f137/130802.htm

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


  7. #7
    Senior Professional Array kwanbis's Avatar

    Join Date
    Jan 2008
    Posts
    104
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    14

    Default

    Thanks so much for explaining everything.

    So, Im stuck with an unlockeable iPhone for the foreseable future =(

  8. #8
    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 n1ckn4m3 View Post
    for example, for the 2 weeks or so that Apple was signing both 4.1 and 4.2.1, you could install 4.2.1, upgrade the baseband, then do a factory restore back to 4.1 and it would downgrade the baseband back to the 4.0.1 baseband.
    In my testing it was more like 2 days (for the iPhone 4) where Apple was signing both 4.1 and 4.2.1 (after the official release of 4.2.1)

    The primary use for this feature is to allow legitimate beta users (developers) the ability to downgrade to a stable iOS version during the beta period.

    Anyone else who wants to use this baseband downgrade feature has to be very quick and lucky.

    Quote Originally Posted by n1ckn4m3 View Post
    As such, it's not possible to request and 'store' the SHSH response to allow for downgrading.
    It is actually possible to request and store the SHSH for a baseband restore/downgrade, but as you correctly say it serves no useful purpose because of the randomly generated number. The random number is large enough that it's extremely impractical to request and store a SHSH for all possible permutations of the number.
    Last edited by Olethros; 12-13-2010 at 11:13 PM.
    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. MacNN: T-Mobile back to losing subs without iPhone, new Android
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 02-25-2011, 06:00 PM
  2. MacNN: iPhone claws web share back from Android
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 06-01-2010, 05:10 PM
  3. MacNN: iPhone claws web share back from Android
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 06-01-2010, 05:10 PM
  4. MacNN: SoftBank gets HTC Desire to back iPhone with Android
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 03-29-2010, 06:00 PM
  5. MacNN: SKT to hit back at iPhone with Android mix
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 01-14-2010, 03:40 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 07:02 AM.
twitter, follow us!