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.
iPhone 2.0 Firmware Jailbroken Already?
- Thread starter MacRumors
- Start date
- Sort by reaction score
I support these attempts, but I find it incredibly STUPID that they would release this BEFORE the firmware is out!!!! Now apple is going to change it and the work will start again! Even if they didn't release the precise method, maybe apple will add other security or change a code or something. Why do they do this?? bad form.... 
Unfortunately, just like as Verizon/Sprint use different, incompatible cellular technology than AT&T/T-mobile (CDMA vs GSM), AT&T and T-mobile actually use different spectrum frequencies for their 3G services. T-mobile's UMTS/HSPA (3G) service isn't quite launched yet, but when it does, it is going to be using the 1700mhz band where as AT&T used 850mhz and 1900mhz.
With this, people will also be able to use software to access the dock port, potentially allowing (homebrew?) hardware accessories for the iPhone.
The biggest reason of all would be that hackers need to be able to run code on the iPhone to be able to create new unlocking methods for firmware.
Obviously, unlocking is very important for a good % of iPhone users for the following reasons:
1) Not everyone lives in the few countries that the iPhone has launched in so far and many do not wish to wait.
2) Many users (like myself - I have a Touch instead) live in a state/province/area where AT&T (or the official carrier in the country) either doesn't have any service, or their service is horrible. In my case, I travel between two different locations, constantly driving between the two. AT&T doesn't even have ANY coverage for nearly 75% of my trip. AT&Ts coverage is TERRIBLY spotty in the west. Most rural areas are not even covered at all, and 3G service is rare even in many cities.
This is compared to Verizon, who has had EVDO revA service which is fast download AND upload 3G in my parents suburban/rural area in Idaho for the last 2 years.
Obviously there are probably many situations like this in other countries where the iPhone has been launched or is launching soon where the user cannot use the "official" iPhone provider for whatever reason.
3) Many users are at the mercy of their employer for what provider they use, and that provider happens to have service with someone other than the official iPhone carrier of the country.
Unfortunately, just like as Verizon/Sprint use different, incompatible cellular technology than AT&T/T-mobile (CDMA vs GSM), AT&T and T-mobile actually use different spectrum frequencies for their 3G services. T-mobile's UMTS/HSPA (3G) service isn't quite launched yet, but when it does, it is going to be using the 1700mhz band where as AT&T used 850mhz and 1900mhz.
Um.. Even when the SDK is out, there will be MANY types of applications that Apple will not allow on people's iPhones. This will be useful for not only end-user applications which would not be allowed on iTunes, but for developers to be able to use other programming languages than Obj-C on the iPhone. The hacker community already has PHP, Pearl, Python, Ruby, etc running on the iPhone. I'm sure there will be many other apps or experimental functionality that Apple won't officially allow.
With this, people will also be able to use software to access the dock port, potentially allowing (homebrew?) hardware accessories for the iPhone.
The biggest reason of all would be that hackers need to be able to run code on the iPhone to be able to create new unlocking methods for firmware.
Obviously, unlocking is very important for a good % of iPhone users for the following reasons:
1) Not everyone lives in the few countries that the iPhone has launched in so far and many do not wish to wait.
2) Many users (like myself - I have a Touch instead) live in a state/province/area where AT&T (or the official carrier in the country) either doesn't have any service, or their service is horrible. In my case, I travel between two different locations, constantly driving between the two. AT&T doesn't even have ANY coverage for nearly 75% of my trip. AT&Ts coverage is TERRIBLY spotty in the west. Most rural areas are not even covered at all, and 3G service is rare even in many cities.
This is compared to Verizon, who has had EVDO revA service which is fast download AND upload 3G in my parents suburban/rural area in Idaho for the last 2 years.
Obviously there are probably many situations like this in other countries where the iPhone has been launched or is launching soon where the user cannot use the "official" iPhone provider for whatever reason.
3) Many users are at the mercy of their employer for what provider they use, and that provider happens to have service with someone other than the official iPhone carrier of the country.
well it would be up to you if apple says you can.
Actually, the whole point of this thread is that it's not up to Apple if you care enough to jailbreak your phone.
You seem insistent on your efforts to protect people from IM clients. If Apple approves an always-connected IM client as an official iPhone app, are you going to try to argue against people from installing it?
I don't jailbreak my phone, but I would be thrilled to see an "approved" always connected IM client even at battery loss. Not everyone has the same priorities as you. Please stop trying to protect people who don't need protecting.
arn
Are you positive that this will create any significant difference or are you just speculating??? HSDPA/HSUPA may indeed be faster than UMTS, BUT they are newer standards that may have other power saving tech...
exactly. no way they would put 1700mhz on the iphone when its only supposed to be on AT&T.
Don't you think that Apple prohibiting the ways to make iChat and GPS type apps could be a sign that they want to take care of those apps personally and make it so 3rd parties can't put out rival apps for that??? I know there are some problems technically, but there has to be a way to do it and they have to be working on it because those are such HUGELY desired apps.
Clearly Apple is looking at iChat-type apps, they demoed AIM. I'm hoping that AIM is allowed to run as background, or AIM is allowed to install a background daemon.
Re GPS, I presume you mean hardware interface? My understanding is that the reason that the SDK excludes the dock connector is that Apple already has a dock-connector licensing program. Made for iPhone. There exist iPhone accesories. If a company wants to make a GPS <-> iPhone device, they have to go through that licensing program. Apple hasn't said, but you would think that those people may have special hardware access via the SDK.
arn
A good way for Apple to make firmware 2.0 solid...patch this hole, leak it again, patch it, etc. XD I'm just kidding.
Anyway, is there a reason why jailbroken applications completely reek? Not to be mean, but...Apple developed that Fighter in two weeks. EA made Spore. Now take an average developer (not EA or Apple quality)....shouldn't they be able to make that same quality in maybe two months? Best solid game I've seen is Solitaire and Pool. Everything either crashes often or just fails. MobileChat and Apollo...those crash often and the running in the background fails. Even AIM SMS is better. How come all the jailbroken applications are crashing, failing at startup, very outdated games (iZoo is like Bejeweled 1...but Bejeweled 2 is so much better...not to say Snake isn't fun...), most of the time useless applications (AppFlow, Multitouch, etc.), and all in all no point in even having the jailbreak on?
Sorry about the small rant. My real point and question is:
I mean, I know jailbreaking and the SDK are different...but aren't they both still Objective-C programmed? (I wouldn't know, since I only program with the SDK and not for jailbreak) Or are people who program jailbreak applications feel like they don't want to spend time? I'm just wondering if there was a difference.
PS. (I'd want to unlock that $99 thing...Apple's taking too long to approve of my application =[ )
Anyway, is there a reason why jailbroken applications completely reek? Not to be mean, but...Apple developed that Fighter in two weeks. EA made Spore. Now take an average developer (not EA or Apple quality)....shouldn't they be able to make that same quality in maybe two months? Best solid game I've seen is Solitaire and Pool. Everything either crashes often or just fails. MobileChat and Apollo...those crash often and the running in the background fails. Even AIM SMS is better. How come all the jailbroken applications are crashing, failing at startup, very outdated games (iZoo is like Bejeweled 1...but Bejeweled 2 is so much better...not to say Snake isn't fun...), most of the time useless applications (AppFlow, Multitouch, etc.), and all in all no point in even having the jailbreak on?
Sorry about the small rant. My real point and question is:
I mean, I know jailbreaking and the SDK are different...but aren't they both still Objective-C programmed? (I wouldn't know, since I only program with the SDK and not for jailbreak) Or are people who program jailbreak applications feel like they don't want to spend time? I'm just wondering if there was a difference.
PS. (I'd want to unlock that $99 thing...Apple's taking too long to approve of my application =[ )
This is great news! Although, it's unfortunate that it isn't this way by default. It's ridiculous that by default, I am not even allowed to install whatever I want on the phone I own. It's as if I buy a hammer and it only lets me use it on certain nails. WTF? Why should this be ok for software?
BTW: There is a difference between greed and just being a good profitable business. Look it up!
BTW: There is a difference between greed and just being a good profitable business. Look it up!
i am not trying to "protect" people from im clients and i have no problem with people using them, i could care less what you do on YOUR phone. i was simply just asking if people were aware that it would drastically decrease their battery life.
anyways, whats the point of an discussion board if you dont want to have a discussion.
raising the issue of battery life is a perfectly valid observation and i see nothing wrong with talking about it.i think if you do a quick search on the web everything will point to HSDPA being pretty harsh on battery life whether its browsing, talking or even just having your phone in standby. i dont think HSDPA and "power saving tech" should be used so close in a sentence.
i am not trying to "protect" people from im clients and i have no problem with people using them, i could care less what you do on YOUR phone. i was simply just asking if people were aware that it would drastically decrease their battery life.
anyways, whats the point of an discussion board if you dont want to have a discussion.
Apologies if so, I just took your "oh my bad i just figured you valued actually being able to use your iphone as more than a paperweight." comment as a negative one.
no worries...
arn
That is true, but HSDPA is an extension to UMTS and doesn't need to be used at all times except when you need a fast connection and IM requires very little bandwidth so HSDPA can be disabled when using IM.
Good thing FastMac is there to quadruple our iPhone battery
. (I'm actually serious)Is SMS approximately the same as an IM? I'd expect IM to hog battery a bit more, but does SMS work the same way? I have no idea how SMS actually works, lol.
This is just purely an uninformed comment. Malware is already not an incredibly difficult thing to engineer if someone really wanted to.
Mobile OSX is so similar to desktop OSX, that the code could probably be easily ported across. But the point is that only jailbroken iPhones would be susceptible to malware, and only by downloading and installing an infected/trojan program from a 3rd party source. Non-jailbroken iPhones downloading only from the Apps store will be fine.
Now if you are talking about so called auto-install "drive-by" malware/spyware, the vector is going to be an exploitable security hole in official system software such as Safari, etc. A jailbrake will have had nothing to do with this type of vulnerability.
oh my bad i just figured you valued actually being able to use your iphone as more than a paperweight.
hey if you want to carry your charging brick with you and plug in to fill your battery up during your day thats up to you.
Yeah, it's called a CHOICE. And "paperweight" is major hyperbole. Many iPhone users are probably similar to myself in not talking for hours a day on my phone and having plenty of battery life each day for AIM or similar.
And for the people who say you can run whatever you want on your iPhone just because you want to, that isn't necessarily true. Apple regulates this kind of stuff all of the time. It is illegal to run OS X on non-Apple hardware (except for virtualization of Mac OS X Sever, IIRC). Point being, when you use Apple products, you agree to their terms, and that is a contract whether you like it or not.
Unless there is something different about the iPhone, I don't see why people breaking the law should be encouraged. If I am misinformed about this issue, please correct me!
Yes, you are mis-informed. Jailbreaking your own iPhone is NOT illegal. It may be against the EULA, but that surely is not a criminal act.
Wrong again, See Above! My god... what is wrong with you people? Jailbreaking your phone IS NOT ILLEGAL. It may be against the EULA, but even those have/are being contested in courts.
1) There is no documentation for programmers. although it's a version of OSX, it's like finding your way around in the dark.
2) There has been only a VERY small amount of people even attempting to make apps for the iPhone. And most of those are amateurs and people experimenting. With the release of the SDK, you'll start to see a huge volume of developers jumping on board, and most of those offering applications will be professional developers working for software companies.
i am not trying to "protect" people from im clients and i have no problem with people using them, i could care less what you do on YOUR phone. i was simply just asking if people were aware that it would drastically decrease their battery life.
anyways, whats the point of an discussion board if you dont want to have a discussion.
i think if you do a quick search on the web everything will point to HSDPA being pretty harsh on battery life whether its browsing, talking or even just having your phone in standby. i dont think HSDPA and "power saving tech" should be used so close in a sentence.
I have to take Arns side on this one and not because he's the admin.
No one said you shouldn't discuss any topic, it just sounded like you were just being negative and sarcastic and not wanting to really discuss it. I say discuss on!
And speaking of, I don't have alot of experience with UMTS/HSPA phones as I've been on Verizon for years. 3G EVDO doesn't seem to be all that bad on the CDMA side, so I didn't assume HSDPA would be horrible either.
So do you have a ballpark of how much more power hungry HSDPA is than UMTS? How about HSUPA vs UMTS? And can you disable either HSPA and resort back to UMTS or EDGE to save power during low bandwidth requirements?
Why do people here feel the need to speak on things they don't really know anything about?
1) Jailbreaking the phone is not illegal
Apple can't sue you for jailbraiking your phone.
2) The iPhone Deb Team has not shown how they jailbroke the phone
So Apple won't exactly be patching it today. They shown pictures to prove that they've bypassed the security check when you install the 1.2.0 firmware. That's all that's been displayed, so unless Apple has a lot of free programers to look at general code they won't be patching anything anytime soon. You can also put money on the iPhone Dev Team not releasing the any exploits in firmware 1.2.0 until it's released to the public.
1) Jailbreaking the phone is not illegal
Apple can't sue you for jailbraiking your phone.
2) The iPhone Deb Team has not shown how they jailbroke the phone
So Apple won't exactly be patching it today. They shown pictures to prove that they've bypassed the security check when you install the 1.2.0 firmware. That's all that's been displayed, so unless Apple has a lot of free programers to look at general code they won't be patching anything anytime soon. You can also put money on the iPhone Dev Team not releasing the any exploits in firmware 1.2.0 until it's released to the public.
Jailbreaking isn't illegal because it's your phone (recent court ruling saying that unlocking isn't illegal...I don't see how jailbreaking can be any different [I think unlocking is actually "worse" since you're not removing a restriction for you [jailbreaking]...you're removing a restriction that says AT&T and iPhone are exclusive)...the most Apple can do is stop servicing it...which they do. If they know that a phone's been jailbroken, then that voids the warranty.
Here's the other side of the coin. Apple is getting more restrictive because of this iPhone hacking. And of course, those costumers that follow the rules are the one's pinched.
The DRM was never invented for legal owners. DRM was put in there to protect the music from hackers which can always circumnavigate it anyways. It just made it more difficult and frustrating for legal owners.
The iPhone could also turn into this. They could end up making the SDK so restrictive for developers because of these hackers. And of course, we the average, non-techy, who just follow the rules, iPhone owners will be missing a lot of could have been awesome apps.
So please, don't say that what you do with your iPhone doesn't affect others.
The DRM was never invented for legal owners. DRM was put in there to protect the music from hackers which can always circumnavigate it anyways. It just made it more difficult and frustrating for legal owners.
The iPhone could also turn into this. They could end up making the SDK so restrictive for developers because of these hackers. And of course, we the average, non-techy, who just follow the rules, iPhone owners will be missing a lot of could have been awesome apps.
So please, don't say that what you do with your iPhone doesn't affect others.
Might be a dumb question here; why sue them? I think this is great. If it makes it worse for the 'legal' people, then revolt. Be "illegal". What's so illegal about unlocking and jailbreaking the phone anyway? Don't you own it?