Discuss Question about future baseband 2.10.4 unlock. at the Ultrasn0w (3G(S)/iPhone 4 unlock) - Hackint0sh.org; ...
Question about future baseband 2.10.4 unlock.
I am new to the forums and new to the whole jailbreak/unlock stuff.
I have an old iPhone 3G which came factory unlocked (from Italy) but I am in the US right now and I am really thinking about getting an iPhone 4 here.
Problem is they are already on 4.1 with baseband 2.10.4 when sold in the Apple Store here (I checked by buying one and then returning it ).
Now I know that the Dev Team is working on a Jailbreak release for 4.1 however there are numerous comments that make me tend to believe that they will never release a new Unlock for the baseband 2.10.4...
Comments from the Dev Team such as:
...hatís because to use redsn0w at 4.1, you need to already have updated to official 4.1 from Apple. If you do that, you lose the ultrasn0w unlock (possibly forever)....
really make it sound like whilst there will be a Jailbreak for 4.1, there will not be a new release of Ultrasnow (that is the one right?) for the baseband firmware to which your iPhone 4 will update if you accept the iTunes update to 4.1 or which comes with the ones sold at the Apple Store now.
Thereís currently no known way to revert your baseband ó if you update your baseband youíll lose the ultrasn0w unlock, possible forever.
One forum post I read somewhere here (in a sticky I believe?) actually said there isn't even any talk whatsoever about a new version of UltrasNow and that they do not think that there will be a new version until iOS 5... how reliable that is I don't know...
I was just wondering if you guys have perhaps heard anything?
Great... the first response is from a bot lol...
If you look at the release pattern for yellowsn0w and later ultrasn0w you see a clear trend. One new injection vector (baseband exploit) per major iOS cycle.
Some might say that this could just be coincidence but for the team to have a new exploit ready for iOS 3.0 and another days before iOS 4.0 was released looks more like strategy to me.
Yellowsn0w doesn't entirely fit this pattern (released with iOS 2.2) - I think there are a couple of reasons for this (the baseband chip was new and had a more restrictive security model). However despite not being ready for iOS 2.0 there was only one unlock released for iOS 2.x
You can also see this trend with the push to encourage users to adopt tools to prevent baseband update. (pwnage train for 3G and 3GS, tinyumbrella for iPhone4).
The only glaring exception to this is blacksn0w - which was released by geohot.
Geohot has left the iPhone scene now. So we can't rely on him to transform a discarded exploit into an unstable unlock. Trust me, it is a good thing geohot has given up on unlock.
It's getting harder and harder to find baseband exploits that can be turned into unlocks.
My money is on no new unlock until iOS 5. Only new bootrom 3GS cannot prevent baseband update - all other existing iPhone owners else has no excuse for staying on 4.0 baseband (or earlier).
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!
By agustincingolani in forum PwnageTool
Last Post: 06-03-2010, 06:40 PM
By mossssom in forum iOS 3.x (iPhone OS 3.x)
Last Post: 06-05-2009, 08:32 AM
By jawnsixteen in forum iPhone "2G" (Rev. 1)
Last Post: 02-09-2008, 09:18 AM
By Jackal_007 in forum iPhone "2G" (Rev. 1)
Last Post: 01-29-2008, 05:49 PM