Thx a lot Sam!
Can't tell you how much I appreciate your work here.
Thx a lot Sam!
Can't tell you how much I appreciate your work here.
Lets get ready for a class action lawsuit. Or think about it for a while. If these rotten apple geeks damage our iphones without our consent then we got them. We can collect the needed contact information for everyong welling to join. We Look for a firm who will do it for the exposure (free) and we nail them.
Thanks Sam and the Team for keeping us informed on this matter. I'm happy with the current settings on my iPhone, so I think I won't be doing an update. :)
For now, I'd say to Apple, bring it on. So we will know what this update is all about. :)
Guys, re-read carefully what Steve Jobs et al. stated. They didn't say anything about bricking anyone's phones.
Good luck with the court case. You're going to need it. Would love to be one of Apple's lawyers. It would take me exactly 2 minutes to defeat all of your lawyer's arguments based upon your blatant violation of the terms and conditions that you accepted by opening the box of your iPhone.
We voided our warranty the day we jailbreaked and unlocked it too.. They worded their statements carefully. Basically saying hack at your own risk.
And 'hack at your own risk' is fair enough.
I am sick of the cry-babies who choose to hack their iPhones, modify the firmware and then cry foul when Apple says, "hey when we release a firmware we assume that the user hasn't made any modifications and something may go wrong that bricks the phone". They word it more strongly of course for the usual CYA reasons, but that is the essential message.
This update is not forced on you - the decision to take the risk to install it is yours and yours alone. Much like the one that you made to make changes to the firmware to unlock it. Decisions have consequences, some of them unintended, but that's the risk willingly taken. It's called personal responsibility dammit.
I mean look at all of the vitriol the Dev Team have worn from some users who downloaded the unlock patch and something went wrong leaving the phone unusable. For some reason, these users always believe that their problems are somebody else's fault. Now the vitriol is being directed at Apple.
However, from my point of view this problem could have been solved technically instead of by press release. What Apple should have done is include a routine that computes a checksum of the firmware. Then when it is about to do the update it runs this routine and if there is no match it could refuse to install. People would still whine, but at least the iPhone would be no worse off.
Cheers, Chris W.
Is it wrong to call for everybody to just relax. Wait this out a bit. There is no proof that this will go either way. Besides that there is no "need" to do the update. With the talent of the people that have provided us with all of these fantastic solution's, there is no reason to believe there will not be a fix for what ever Apple counters with.
Even if there are a few really nice features in this firmware update, just wait. A model could be done on the homebrew side to imitate it. I for one and not stressing about not being able to access the iTunes music store via wi-fi, all the while pooring more $$$ into the accounts of Apple after they have (maybe) intentionally wrecked a few hundread thousand phones of their customers.
This is a great product no matter how hard Jobs is going to try to fuc it up! Enjoy it as is and wait for 3rd party apps to get better.
Just my two cents, on a pretty big over reaction based on speculation.
This is a pretty big issue actually, seeing as other cell phone manufacturers will not tell you that by unlocking the phone, you have voided your warranty. That is a very big step seeing as it is legal to unlock a cell phone and it is not legal for a company to sell a product without warranty as these products are not sold as-is.
Now there is something I do agree with, if for whatever reason the unlock program causes a specific problem that apple has noticed, then they would at least tell us that fact. Apple, in my opinion gains nothing from non working phones, imagine the designers and programmers knowing that what they have put all of their effort into, all the time they spent to make a beautiful device that is easy to use and useful only have thousands potentially hundreds of thousands (assuming at least 10% have unlocked) of phones go to the graveyard.
Moreover apple should be worried that they are forcing everyone to study the programming out of fear of this "bricking" threat that eventually these guys the real guys that get things done eventually have better ideas and fixes than apple themselves.
Man..... People like naximus and patvg need to get a clue.
First off. How many people here actually read Apple's statement? Snowbird did. Probability says at least chrisw, bulldogge, and bezman did too. How about all you ranting about putting up lawsuits? Obviously didn't.
Nowhere does it say Apple intends on bricking through an update.
Nowhere does it even say it will brick on update.
All this talk about bricking comes from somebody freaking out, jumping to conclusions, and claiming it's truth.
It says software out there "can" do irreparable damage. "can" is right. It can, such as the people with the bootstrap errors (1011 or 1004 or whatever it is). As a matter of fact, any embedded device which has the bootloader modified or has had the flash chip written to directly risks permanent bricking. Duh.
Does it do irreparable damage? We actually don't know. Apple doesn't know either since they didn't develop the baseband firmware. (How many of you knew there's at least 3 things "firmware" can be referring to when talking about the iPhone?) DevTeam and geohot doesn't know either because they didn't develop the baseband firmware either, and only patched a section without a full analysis of what the effects are. (I say that because reading through the entire firmware to understand what a specific memory address does is not a good use of their time anyways. It's like trying to make a firefox debug menu appear by opening firefox in a text editor and staring for a couple of years instead of going through a prefs file.) It appeared unlocked, and voila, the hack was released. You know why it's called a hack, now, right? (I'm not disrespecting them either, as their accomplishment is quite impressive.)
Is any of this Apple's fault? No. Are they lying? No.
The message as I see it is: "Hack at your own risk, but be warned that unlocking fucks with your baseband firmware in an unknown manner."
Nothing about trying to brick your phone on an update.
If you're curious what "irreparable" in their language means, feel free to ask me. I can write up a post explaining what the heck actually makes a phone tick based off some phone hacking investigations myself. But I ain't going to spend the time if people arn't interested.