andybno1
Suspended
if they just released it and never bothered to make sure it worked ppl like you would try it find it doesn't work and possibly damage your iphone and winge to high heaven your iphone was damaged.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
New Baseband Exploit Found [Updated 2/11]
- Thread starter thelatinist
- Start date
- Sort by reaction score
As you've made clear many times, you have no clue how much work it is to create an unlock. Indeed, you seem to think that exploits are files and that all one has to do is figure out where they've been hidden. The fact that you post so cavalierly on here about your ability to write an OS from scratch or create an untethered jailbreak if only someone would tell you where Apple hid the "24Kpwn file" makes it clear that you have no idea what you're talking about. iPhone hacks do not happen in a day.
Quite the contrary, finding a weakness like this in a baseband is only the first step in a very long process of software development. A way to exploit the crash and inject code must be developed and tested, a payload must be developed which will disable the SIM unlock without negatively impacting the rest of the baseband, methods must be found for preventing conflicts with other software, with commcenter, and with the baseband itself. Each stage of the process requires extensive testing and debugging to make sure that things like blacksn0w's WiFi connectivity issue don't pop up. In the end we are talking about literally hundreds or even thousands of hours spent staring at a screen all so that you can have your unlock. And the Dev-Team does this all for free as volunteers. Every one of them has a day job or studies that rightly take priority over unlocking 5.12.
You really need to start thinking before you post and stop acting so entitled and childishly impatient. Maybe then you would stop whining and show a little gratitude. But I'll not hold my breath.
dhlizard
macrumors G4
pcs has indeed made all these claims.... I must concur
a baseband crash is a very long way from a reliable unlock
Mr_Brightside_@
macrumors 601
I'm just wondering- while I realize this is a valuable exploit they've found, does it not stand to reason that once Apple is aware that 5.12.01 is vulnerable, they will update it for 3.2/4.0? I mean, I don't see Apple releasing anything else with 5.12.01, regardless of whether or not a stable unlock is yet publicly available.
Applejuiced
macrumors Westmere
They can't fix what they don't know.
Update what code and where exactly? Just renaming the baseband version has nothing to do with patching up an exploit.
Vandam500
macrumors 68000
Yep. As long as they don't release the unlock then Apple won't know where to look to fix it which is why it doesn't make any sense to release it now for such a insignificant upgrade that is 3.1.3
bradl
macrumors 603
But that's the point. We're not counting on the premise that Apple might find the baseband exploit themselves, and patch it themselves. If they did that, all the effort that went into finding this and trying to develop an unlock on this baseband is now worthless, and wouldn't work for a 3.1.4/3.2/4.0.
Just becase Apple doesn't know about it NOW, doesn't mean that they couldn't find it (possibly, on their own). Does it seem logical that the Dev Team or Geohot or someone waits to do something until the next OS based on the contingence that Apple doesn't find anything? If they do, the work they've done in finding this is completely invalidated.
BL.
Applejuiced
macrumors Westmere
Apple will not try to patch something or go thru all the trouble in finding something that might be developed to an exploit based on what someone posted online. Heck they knew about the 3GS exploit used previously onthe iPod touch and they took a while to close that hole.
Highly doubt that they will find it on their own or even if they will bother trying. Their first priority is not playing the cat and mouse game with hackers.
Tensakun
macrumors 6502
Unlock vs JB
This is a good point. From this I'd conclude that even if the exploit were distributed in a usable form, it would not necessarily (or probably not) provide a solution for those of us who just want to return to tethering using MiWi from Rock after applying Blackra1n (i.e., JBing). Right?
This is a good point. From this I'd conclude that even if the exploit were distributed in a usable form, it would not necessarily (or probably not) provide a solution for those of us who just want to return to tethering using MiWi from Rock after applying Blackra1n (i.e., JBing). Right?
jav6454
macrumors Core
bradl
macrumors 603
Who said it had to be based on what someone else posted? If one of the iPhone OS developers work on updating the baseband on their own, and discover the exploit on their own, not only will they have the ability to fix that exploit going forward with 3.2/4.0, but can also backport it to 3.1.4 and release that prior to anything new in June/July, making all the work that the Dev Team and others do with this exploit completely moot. So wouldn't it be better to not hold on to it on the contingent that Apple won't find it (because they quite possibly could find it)?
If they work on it and release something, not only will the JB community have something, but it also keeps Apple honest on their OS development until the next exploit is discovered in the next/future OS releases.
Otherwise, this is pretty much like a hunter saying that they have wild game that they've shot, but they are going to put a net over it to save it, based on the contingency that other carnivores around don't know how to tear through the netting to get to the game. You can't count on that; it's poor contingency planning.
BL.
pixelated
macrumors 6502a
If you squint and look between the lines you can just make out a baby crying for his jailbreak.
dhlizard
macrumors G4
Very well said. I was afraid a few whiners might creep into this thread.
Besides, everything posted here is irrelevant anyway. DevTeam has the exploit, they will do with is what they want in their own timeframe. 🙂
Precisely. And I trust them implicitly to have the best interests of the jailbreak community at heart. If they think it's worth waiting for the next major upgrade, then it surely is.
Hudzilla
macrumors 6502a
Thats exactly why Geohot quit hacking the iPhone, because of people who think they know better demanding they release tools ASAP.
iphonegeek786
macrumors 6502
2 Days later: MuscleNerd: We are sorry but we have lost all data on jailbreaking due to someone (^^^^^^^^). We are sorry but jailbreaking is no longer possible.
At the risk of being called a "whiner" or being told that my input on a discussion board is "irrelevant," I'll just say that I was talking this over for a few minutes last night with a friend of mine, and both he and I are on 5.11.07, so we're not clamoring for an unlock...in fact, we're both fairly happy with AT&T and don't see anything down the road that would make us want to jump ship to another carrier anyway.
That said: I completely understand what bradl is saying here. Yes, if the Dev Team releases an unlock for 5.12.01 in the next two weeks, say, then there's probably a 50% probability that Apple will have enough time to research and patch it for OS 3.2 and, say, a 95% chance they'd patch it for OS 4.0 (note: all numbers pulled out of posterior but are based on prevailing trends in the market😀)
So, should the Dev Team sit on the exploit and wait for 3.2 or 4.0 before releasing it? Well, what are the chances that Apple, or other embedded systems and software engineers working on baseband firmware (forgive me, I don't know who manuf. the cell radio chip(s)) find the repeatable crash and fix it before 3.2? 25% chance? What about before 4.0? A 50% chance?
I guess another thing to think about is this: what are Deav Team's goals in unlocking cell phones? The nobility of unshackling users from the bonds of their carriers? Sticking it to the big, bad evil carriers/Apple? A mix of both?
1st bottom line is this: if a user chooses to buy an iPhone and can only use it in their location by unlocking it from the official carrier retailer, then it's that user's responsibility to make sure he/she heeds all the advice of the Dev Team and follows the rules of engagement pertaining to their unlock (that is to say: don't update without first checking with the Dev Team!!!).
2nd bottom line: if it's Dev Team's goal to help as many new or would-be users get on the iPhone/unlock train, then they should try to release exploits every chance they get. Problem with this is, though, that Apple has infinitely more resources to throw at patching and closing exploits.
Double-edged sword, I say!😀
(note: I'm relatively new to the jailbreak and unlock sagas, and it's nothing if not entertaining to watch!
That said: I completely understand what bradl is saying here. Yes, if the Dev Team releases an unlock for 5.12.01 in the next two weeks, say, then there's probably a 50% probability that Apple will have enough time to research and patch it for OS 3.2 and, say, a 95% chance they'd patch it for OS 4.0 (note: all numbers pulled out of posterior but are based on prevailing trends in the market😀)
So, should the Dev Team sit on the exploit and wait for 3.2 or 4.0 before releasing it? Well, what are the chances that Apple, or other embedded systems and software engineers working on baseband firmware (forgive me, I don't know who manuf. the cell radio chip(s)) find the repeatable crash and fix it before 3.2? 25% chance? What about before 4.0? A 50% chance?
I guess another thing to think about is this: what are Deav Team's goals in unlocking cell phones? The nobility of unshackling users from the bonds of their carriers? Sticking it to the big, bad evil carriers/Apple? A mix of both?
1st bottom line is this: if a user chooses to buy an iPhone and can only use it in their location by unlocking it from the official carrier retailer, then it's that user's responsibility to make sure he/she heeds all the advice of the Dev Team and follows the rules of engagement pertaining to their unlock (that is to say: don't update without first checking with the Dev Team!!!).
2nd bottom line: if it's Dev Team's goal to help as many new or would-be users get on the iPhone/unlock train, then they should try to release exploits every chance they get. Problem with this is, though, that Apple has infinitely more resources to throw at patching and closing exploits.
Double-edged sword, I say!😀
(note: I'm relatively new to the jailbreak and unlock sagas, and it's nothing if not entertaining to watch!
the dev team did the work, they can pick the date. I could care less when/if they release an update.
That being said, however, I hope they wait a month at least to let the morons who updates (most of them, AGAIN), to think about their stupidity. I realize that there are a few people who might have accidentally updated, or thought the only way to restore was to update. In all honesty, they fail for not researching or not being careful with their device. If you know your device requires special software, you make damn sure it is available. Common sense.
That being said, however, I hope they wait a month at least to let the morons who updates (most of them, AGAIN), to think about their stupidity. I realize that there are a few people who might have accidentally updated, or thought the only way to restore was to update. In all honesty, they fail for not researching or not being careful with their device. If you know your device requires special software, you make damn sure it is available. Common sense.
Applejuiced
macrumors Westmere
Applejuiced
macrumors Westmere
rwilliams
macrumors 68040
Congratulations to Sherif, but I'm surprised that they even announced that the exploit was found. If I were them, I'd keep quiet about it until they released their update for 3.1.3 or 4.0. Now this just gives Apple a heads up and sends them back looking for the exploit themselves.
Penguissimo
macrumors 6502a
Applejuiced
macrumors Westmere
Did they give you an application or an interview yet?
If they ask for referrences you can put me and thelatinist down😀