|
TOTA - APPLE iPHONE & iPAD & Mobile News Thread PT1 (CLOSED) (pg. 97)
|
View this Thread in Original format
| E2EK1EL |
| quote: | Originally posted by malek
just got 3909 kbps! |
Unacceptable, you must get at least 7.0mbs on that 3GS! Even I got 3.1 mbs, and the 3G can only max out at 3.6mbs.
Come dude, you can do it ... are network can do 21mbs now! |
|
|
| malek |
hehe, thats from my house, I bet distance and line of sight has something to do with this...
I'll try tomorrow from my office on the 13th floor. |
|
|
| E2EK1EL |
Dev Team Jailbreak 3.1
This is the low down on our tools for use with the 3.1 firmware from Apple, please read the whole post in full before attempting anything. Because of changes with Apple’s update techniques (that complicate the 3GS upgrade process) this will be a multipart release. This release starts with PwnageTool 3.1 for Mac OS X - this application supports the iPhone 1st Generation (2G), the iPhone 3G and the iPod touch 1G. NB: THIS DOES NOT SUPPORT THE 3GS OR 2G/3G IPOD TOUCH. redsn0w for Mac OS X and Windows will follow sometime in the near future, please don’t bug us about it - we’ll release when we have something ready.
1.GOLDEN RULE: If you are using a 3G iPhone with ultrasn0w and rely on ultrasn0w to obtain cellular service, then you should only upgrade to 3.1 with a PwnageTool created .ipsw. - Stay away from Apple’s direct updates as described here and here please get up to speed on the whole subject by reading the information contained in these posts.
2.If you have an original iPhone (1st generation) then 3.1 unlock works with this PwnageTool release. iPhone 3G users upgrading to 3.1 will need to continue using ultrasn0w with a PwnageTool created 3.1 .ipsw
3.Please read all parts of this post before downloading and using these tools.
4.Read items 1, 2 and 3 again and again.
5.At the bottom of this post are the bittorrent files for the 3.1 capable version of PwnageTool.
6.This app is suitable for the recent 3.1 release.
7.This version of PwnageTool will NOT work for the iPhone 3GS.
8.PwnageTool WILL work for Original iPhone (1st Generation), Original iPod touch (1st Generation) and the iPhone 3G.
Baseband 101
The ‘baseband’ is the generic nickname given to the internal components of the iPhone that handle the phone calls and Internet access. This ‘baseband’ is a tiny and unique independent computer system that runs inside your iPhone, it is separate to the main system that handles the applications (such as email and google maps) and it talks to the main part of the phone over an internal communications network. Think of it like a cable modem or other peripheral that is attached to your home PC that needs occasional updates. When a software update is released and presented to you within iTunes the baseband is sometimes updated (to fix bugs or add new features). The 3.1 update for the iPhone 3G contains such an update, so running the vanilla updater straight away with iTunes will reprogram and update the baseband.
SIM Free/SP Unlocked/Factory Unlocked iPhone 3G
This applies if you bought your iPhone 3G for $$$$$$$. This model of iPhone 3G doesn’t have an Service Provider lock (aka factory unlocked) and you are able to put any SIM card into the phone and get service. Your phone is already unlocked so you do not need to worry about baseband updates, simply upgrade to 3.1 using iTunes and then use PwnageTool to create an ipsw and then use this to jailbreak your phone.
iPhone 2G (1st Generation)
Use PwnageTool to do the magic and then restore with iTunes using your newly created .ipsw ‘nuff said, you don’t need to worry about anything, the baseband will be unlocked, the phone jailbroken.
iPod touch 1G (Original iPod Touch)
Use PwnageTool to create a firmware image and restore with that .ipsw using iTunes.
iPod touch 2G
Sorry, no support at this time within PwnageTool, use Redsn0w for an earlier (pre 3.1) firmware release instead.
iPod touch 3G (New iPod Touch)
Sorry, no support at this time within PwnageTool
Official Bittorrent Releases -
•PwnageTool_3.1.dmg.5089960.TPB.torrent
•SHA1 = ccc1e5db026362fc7eb9a40c76322b1fdcc90332
**** No updating to 3.1 for me **** |
|
|
| DigitalMP |
Favorite Blackberry Apps?
Google maps (gps), poynt (gps), facebook, viigo (awesome news app), Slacker Radio, Pandora, ScoreMobile (sick sports scores app), extralight (flashlight app -- you can find it on Crackberry.com), BBLight (lights up screen for SMS and/or e-mail -- also on Crackberry)...those are all free.
Berrybuzz is $6 and lets you set a different LED color for calls, sms, email, facebook, etc. You can even make custom colors, as there's a disco color that flashes all the colors at once...I use that for my incoming call. It's nice to know what kind of message you have just by the LED color.
BBSmartAlarms is a great alarm app...$5. You can set multiple alarms or a quick alarm (i.e. 90 minutes from now...great for naps). |
|
|
| DJ Mach X |
| quote: | Originally posted by DigitalMP
extralight (flashlight app -- you can find it on Crackberry.com), |
YES GUY! Been looking for a free one! All the ones on AppWorld cost and ain't bothering with that! Need something simple and quick to help rifle through the CD books when DJ'n...
You know of any other ones? I know there are some expensive ones on AppWorld that will turn the entire screen into a flashlight making it all white (or whatever color red/blue/green) at the highest brightness... but looking for free ones. |
|
|
| E2EK1EL |
Stay the F*CK away from 3.1
Reading reports from the non-JB units, these problems are occuring to 20% of units that have updated.
1) Slower
2) Batt damage <--- no joke
3) Batt life
4) Units are randomly powering off
5) Exhange Server Problems
6) BRICKING
Batt Damage
3GS owner went in to get something checked out, Apple tested it and after 3.1 ... the unit suffered major batt damages.
iPhone 3.1 problems flood our tip box
by Josh Carr (RSS feed) on Sep 15th 2009 at 6:30PM
In the last week, we have had a constant barrage of iPhone issues break through the lines... so much so that we feel it is our duty to inform the two of you who haven't updated what you could experience by updating to version 3.1 of the iPhone OS. This is no small problem, as you can read from the discussions on Apple's website here, here, here, and here.
The first two links are where we're getting the majority of our tips -- random shutdowns and very poor battery life. The second two, bricked phones and general slowness are still worth a mention -- even prompting our own Erica Sadun to do a live walk-through for debrickifying iPhones. We received a lot of praise for her help in that session and we'd encourage you to go back and read through the chat if you're experiencing trouble with a bricked iPhone.
I've spent quite some time reading the hundreds of posts about the "mysterious random shutdowns" and have determined that it really is what it is. As of this writing, there have been 409 posts and 28 pages in that discussion -- I've seen very little repeats and no real solutions. Some people have said that they've gone to Apple and received replacement phones because of this issue but for those of us who have out-of-warranty phones, Apple has merely said "It's $199 for a replacement." I have to agree with our tipsters -- this needs to be addressed. These people simply did not break their phones, it's a well-documented issue which we, as consumers, shouldn't have to pay to fix.
Battery life is a completely different debacle. I cannot seem to find a trend in the discussions at all. Some people claim to have removed certain apps, some claim that MobileMe sync is the culprit -- all of them agree that there is an issue with 3.1 and that battery life shouldn't dramatically decrease overnight. I'd really love to get into one of these phones and replace the battery to see what happens because the hardware guy in me says that it's not impossible. However, deductive reasoning says that there's something in the software. Whether there's a memory leak in 3.1 itself, or some apps that we're running aren't as "compatible" as they should be... we need to see another update soon to help alleviate the issues with version 3.1 of the iPhone OS.
Please feel free to use our comment system to express your concern, anger, resentment... whatever. Try to be helpful if you've come across a solution and be nice if you're not having these problems. Until Apple issues a fix or acknowledges the problem at all, just hope that you're still in-warranty. |
|
|
| beatjunkie |
WTF?? I read this 5 mins after upgrading and now my text messages wont go through because the unit changes the numbers in my contacts (rather just scrambles the numbers)
Is there a way to go backwards back to the old 3.0?
What should I do now?? |
|
|
| E2EK1EL |
| quote: | Originally posted by beatjunkie
WTF?? I read this 5 mins after upgrading and now my text messages wont go through because the unit changes the numbers in my contacts (rather just scrambles the numbers)
Is there a way to go backwards back to the old 3.0?
What should I do now?? |
3G or 3GS?
I know Cydia guys posted how to downgrade a 3GS back to 3.0. |
|
|
| chinamon |
| quote: | Originally posted by DJ Mach X
YES GUY! Been looking for a free one! All the ones on AppWorld cost and ain't bothering with that! Need something simple and quick to help rifle through the CD books when DJ'n...
You know of any other ones? I know there are some expensive ones on AppWorld that will turn the entire screen into a flashlight making it all white (or whatever color red/blue/green) at the highest brightness... but looking for free ones. |
nothing beats a real flashlight though. i keep a small one on my belt whenever im working. great for grabbing security's attention if needed as well. |
|
|
| beatjunkie |
| quote: | Originally posted by E2EK1EL
3G or 3GS?
I know Cydia guys posted how to downgrade a 3GS back to 3.0. |
Its the 3GS, non JB.
What I found that its actually doing is treating the mobile number as the home phone. When I go to text someone it tries to text the home number....so aggrivating. |
|
|
| beatjunkie |
| quote: | Originally posted by E2EK1EL
3G or 3GS?
I know Cydia guys posted how to downgrade a 3GS back to 3.0. |
Its the 3GS, non JB.
What I found that its actually doing is treating the mobile number as the home phone. When I go to text someone it tries to text the home number....so aggrivating. |
|
|
| E2EK1EL |
You can find the below post here: http://www.saurik.com/id/12
I just wanted it to be both on here and there... enjoy!
Caching Apple's Signature Server
Please, for the love of all that is holy, do not e-mail me if you have problems. Instead, go to ModMyi.com, where there is a special forum called 3G[S] Downgrading, created for the purposes of this article.
Seriously: there is no way I could possibly hope to answer even the number of e-mails I'm currently receiving regarding this, and the article isn't even out yet. There is this wonderful scene from Bruce Almighty where Bruce sees his e-mail inbox: that happens to me every day.
I have very little respect for Apple at this point: I make no secret of this fact. Apple, as a company, has turned into a corporate hypocracy, embodying the very ideals that it claims to be rebelling against. "Think Different", as a slogan, has become a cold criticism of their own actions with regards to their product lines.
The Next Hope
Apple is not just a computer company: Apple is a movement. This concept was finally and truly cemented in the public mindset when Apple carved itself a lasting place in the history of marketing with its for Macintosh.
Styled after the classic Orwellian distopia, 1984, this commercial was set in a future where all aspects of individuality had been stamped out by the overlords, constantly vigilant, watching from their television monitors.
This world, as well as everyone in it, was rendered in a blue and gray: some believe we are to see the overlords as IBM, well reknowned for their corporate beaurocracy, and soon to be hated for trying to control our very thoughts with their bland machinery.
Others, including the creative director of the commercial, Lee Clow, state that the commercial represents the abstract struggle of "the few against the many": Apple's Macintosh standing as a symbol of "empowerment". [Wikipedia]
The True Enemy
However, as time grew on, Apple's real stance on individual expression and "empowerment" in particular, became clear: they are staunchly against it. Apple's insistence on controlling the experience of their products sounds very similar to the "garden of pure ideology" expoused by the Big Brother in their own commercial.
Today we celebrate the first glorious anniversary of the Information Purification Directives. We have created, for the first time in all history, a garden of pure ideology: where each worker may bloom, secure from the pests of any contradictory... thoughts.
Our Unification of Thoughts is more powerful a weapon than any fleet or army on Earth. We are one people: with one will, one resolve, one cause. Our enemies shall talk themselves to death and we will bury them with their own confusion. We shall prevail!
The Point of Jailbreaking
This is why many of us (upwards of 10% of all iPhone users, in fact) "jailbreak" our devices: we want choice. We believe that Apple has maintained its lead as the best mobile hardware platform provider, and we encourage that innovation by purchasing not only their devices but also numerous applications from their App Store; but, and this is important: we want more.
Sometimes, it is "only" marketing restrictions: there is no fundamental reason why only the 3G[S] can record video (although the quality of the camera on the iPhone 2G and 3G is not very high), or why the iPhone 2G is somehow unable to do MMS.
Applications like Google Latitude or Voice are likewise "rejected" (Apple likes to claim that they didn't reject these applications, they simply "didn't accept" them...) from the App Store because they might "confuse" the user by replacing functionality that exists with better equivalents.
Our need for "more", however, goes deeper: jailbreaking isn't just about applications that Apple "rejected", but is also about taking provided tools and going in a new direction. The most popular packages available in Cydia aren't even "applications", but are "extensions": seamless and pervasive modifications to existing software.
An Exploit a Day...
On desktop computers such markets are implicit: the computer is yours, and you can do whatever you want with it. You can purchase any kind of hardware, download any kind of software, and make any modifications you feel to be fit. However, Apple doesn't want us treating our iPhones like computers, no matter how similar they seem.
This means that those of us who demand to have the freedom to use the device we rightfully own the way we want to use it are in a constant battle with Apple. Each time they release a new product, or even just a software upgrade for an old one, we have to go to work defeating any new protections.
This arms race is what defines the "homebrew" community on most devices: each upgrade to the PlayStation Portable, for example, brings not only new features but also new restrictions, requiring users to find a new "exploit" to defeat the new defense.
What makes the iPhone platform special, however, is PwnageTool from the iPhone Dev Team: the trust chain on these devices has been completely defeated, and only with new hardware can Apple fix the issues to keep us out.
The Signature Server
Of course, new hardware comes every year, and Apple decided to strike hard with the new iPhone 3G[S]. Rather than just throw in new local protections, Apple decided that every restore of the device would be verified as being valid and safe by Apple itself.
To do this, during the restore process, users see "Verifying restore with Apple...", during which time a challenge/response protocol is used between the iPhone and Apple: a "partial digest" of the firmware files being used is sent to a server, which can then decide to sign off on the result... or not.
Not only does this allow Apple to keep custom firmwares from getting loaded onto the device, but it also allows them to recall existing firmwares by keeping people from restoring to them in the future. To do this they simply would refuse to ever sign, for example, iPhoneOS 3.0 again.
However, to make this model secure, one must verify that their system is not subject to a simple "replay attack": where one just stores a copy of Apple's sign off and then returns it at a later point. This is a "beginner's attack", and one that is easily mitigated by any of a number of strategies.
For a Purple Ra1ny Day
Apple's 3G[S] security mechanism, however, fails this test. Rather than even using a simple random number, they use a hardcoded challenge per device. The specific number they have chosen is the device's ECID, or "unique-chip-id", a number that all devices have so far had, although we haven't seen any previous use for it.
This means that, given an ECID, one can ask Apple's signature server to sign any firmware that they currently consider "OK" (which returns a blob that includes the critical SHSH, which is the signature hash) and then store the result forever.
In practice, there is only one critical file that we need signed: the one with the bug. ;P This is the iBSS, which is one of the modes of iBoot. Given that ECID/iBSS signature, one can load the buggy code and then continue with the jailbreak.
This is, in fact, what purplera1n.com was doing: it returned to you a file that contained just the signature hash for the iBSS file, as that is "sufficient". Eventually someone may write a tool to use this file.
Personalized Firmware
What iTunes does with these blobs is to "personalize" the firmware file, integrating the ECID, SHSH, and CERT blocks into it, so that the iPhone can verify the result. It does this in a temporary directory where users can actually just watch and grab the files.
So, many users have gone in and carefully gotten both the iBSS and iBEC files from this personalization mechanism. The iBSS file from this process actually contains no more information than the tiny purplera1nyday file.
However, and this is unfortunate: just because this information is "sufficient to jailbreak", doesn't mean it is convenient. Without someone writing a special jailbreak tool that uses these files as input you are pretty much stuck.
Your iPhone 3G[S] has an ECID SHSH on file.
Instead, what you really want, is to store the entire personalized firmware set required by iTunes to do a restore (or, more realistically: a full set of SHSH blobs). At this point you should be able to use iTunes to do a "normal" restore of the device.
This functionality was offered, very near to the end of the window, by Cydia: one needed only to agree to have the process done, and your ECID was used on Cydia's server to generate and store a full set of SHSH blobs using Apple's signature process.
In doing this, over 50,000 3G[S] devices got their ECID SHSHs "on file", and are now prepared to continue to restore to iPhoneOS 3.0 indefinitely.
A Narrow Window
Unfortunately, due to the timing of the release (it took a while for me to figure out how to do this effectively), many users failed to get their ECID's in by Apple's cutoff. However, while this means these users will not be able to downgrade to (or even stay at) 3.0, an exploit has (supposedly) been found in 3.1.
This means that, at some point in the tangible but unknown future, users will be able to use iPhoneOS 3.1 on their 3G[S] to jailbreak their devices.
To faciliate this, the Cydia "on file" system is going to come back online tonight and start signing ECIDs using the 3.1 firmware, to prepare for the coming release from Apple when users will once again be locked out.
Hopefully, by then, we'll have hundreds of thousands of users fully protected against Apple's "Information Purification Directives".
Bypassing the Overlord
To this end, I have constructed a server that duplicates the functionality exposed by Apple's signature server, except using "on file" results rather than live requests.
All we need, then, is to make iTunes use it. Luckily, most operating systems also have the ability to locally define bypasses on specific hostnames through a file called hosts. Using this, we can redirect requests to Apple's signature server to Cydia.
So, open the file C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (Mac OS and add the following entry to the bottom of the file.
74.208.105.171 gs.apple.com
Now, when iTunes thinks it is talking to Apple, it is talking to Cydia instead. Doing this will allow iTunes to access signatures already stored by Cydia's "on file" feature.
This server will also act as a cache for any SHSH blobs it hasn't seen, acting as an intermediary to Apple's server. This effectively registers your device with the "on file" mechanism, which means you can now enjoy the protections of being able to downgrade your firmware in the future even if you aren't jailbroken.
This point should be stressed: even if you don't jailbreak, and even if you never intend to jailbreak, you should consider using the new "on file" service.
Let's say that Apple releases an OS upgrade in the future, you take it, and they break something important. Maybe they break your e-mail account, or your todo list. Your business is now crippled.
If only you could downgrade, right? Alas, Apple won't let you anymore. That's where the new signature cache server comes in: by doing your restores through this server you secure your ability to not accept upgrades from Apple if the need is dire.
Performing the Restore
Now, one would have hoped that the process would be as easy as "restore using the 3.0 IPSW". If only we were that lucky. The first problem is that a downgrade from 3.1 to 3.0 must be initiated in DFU mode.
So, we begin: hold down the lock and menu buttons (some call these the power and home buttons) for 10 seconds, letting go of the lock button but continuing to hold menu until iTunes recognizes the device with the message: "iTunes has detected an iPhone in recovery mode. You must restore this iPhone before it can be used with iTunes.".
Note that, at this point, your iPhone's screen should be entirely black. Many people confuse "DFU" with "recovery" (and in fact, iTunes itself glosses over this), but they are quite different. If you see anything on your screen, such as the iTunes logo and a sync cable, or a cartoon of Steve Jobs swearing in Cyrillic, you are in recovery mode and need to try again. One can find videos online that may help.
At this point, you should do a "normal" restore to the 3.0 software. When doing this, remember to hold down the option key (on Mac OS or the shift key (Windows) while clicking the Restore button in iTunes. Select the firmware (which is probably named iPhone2,1_3.0_7A341_Restore.ipsw), and things should be on their way.
Please note that I do not have signatures for 3.0.1, only for 3.0. For some very small number of users I also have a signature for 3.0.1, but I ran out of time hitting the Wednesday deadline getting the code for this working and generalized.
If you would like to try restoring to 3.0.1 with my server, therefore, to see if you have 3.0.1 keys on file you can try, but it may fail late in the process with a very weird error. All users "on file", however, have 3.0 ready to go.
Upcoming 3.1 Exploit
If you encouter "unknown error (3002)", you probably do not have your ECID SHSH's for 3.0 "on file" with Cydia. Unfortunately, as Apple is no longer allowing users to sign the 3.0 firmware, it is no longer possible to register your device with Cydia.
Luckily, it has been reported that iPhoneOS 3.1 is vulnerable to another exploit. This means that, once a jailbreak is released for 3.1, users be able to prepare themselves for future jailbreaks even if they missed the first round of signature storage (which I unfortunately was only able to start very late in the 3.0 game).
Once you even attempt to use this service (or if you tell Cydia to "make your life easier") you will be signed up for the signature tracker, and Cydia HQ will do its best to manage your ability to restore.
And again, if you have any issues with this process, please please please do not e-mail me. Instead, go to ModMyi.com, where there is a special forum called 3G[S] Downgrading, created for the purposes of this article.
NAND Format Invalid
OK, if you were already using 3.0 then this process should "just work". However, if you had already upgraded to 3.1 you will encounted a nasty error: "The iPhone "iPhone" could not be restored. An unknown error occured (1015).". This is expected behavior
For people who are curious, what has happened is that a section of the NAND storage has been slightly reorganized in 3.1, and the 3.0 iBoot can no longer parse it. If we pulled out iRecovery and checked the iBoot logs over USB we'd see the following messages (the typos are Apple's).
Quote:
[WMR:ERR] NAND format invalid (mismatch, corrupt, read error or blank NAND device) [WMR:ERR] boolSignatureFound false boolProductionFormatVerified true nSig 0x0 ************************************************** **************************** ************************************************** **************************** AND: NAND initialisaton failed due to format mismatch or uninitialised NAND. AND: Please reboot with reformatting enabled. ************************************************** **************************** ************************************************** **************************** NAND FTL failed initialisation
The first time this happened to me I actually spent a while with MuscleNerd working out how to do what it asked: "reboot with reformatting enabled". That was a severe waste of time: after you fix this, it still won't boot, and you will need to go through a second restore to finish the process.
However, it turns out a second restore also formats the NAND correctly by itself. So, without bothering to do anything else to the device (leaving it in the recovery mode it is now in: DFU is no longer required), just start the restore over again in the same manner as before, once again selecting the 3.0 firmware.
Stuck in Restore
Unfortunately, this second restore is also going to fail (*sigh*), and irritatingly enough it is going to cause the exact same error message: "The iPhone "iPhone" could not be restored. An unknown error occurred (1015).". This is still expected behavior.
For those who are again curious, what has happened is that when the device turns on it has to decide what it is going to do: wait for instructions over USB, or continue into the boot process. This is determined by an NVRAM variable named auto-boot, which is currently set to "false".
Normally this is set at the end of the restore process, but technically we were unable to finish the restore: it is my understanding that this is because upgrading to 3.1 installed the 3.1 baseband (which is currently not unlockable, btw), and the baseband upgrade in the 3.0 release then fails, stopping the restore.
However, that seems to be the last and least important part of the restore, so we technically won: we are never, though, going to be able to restore back to 3.0 without hitting this 1015 again, though.
Jailbreak with redsn0w or purplera1n
You have two. The first is to use iRecovery to manually set auto-boot to "true", and the second is to just go ahead and jailbreak your device.
We will go ahead and do option #2 (jailbreak), as even just getting iRecovery working on your computer is something that I don't look forward to trying to describe. ;P (In fact, it still isn't working on my Windows computer.)
At this point, you can just run your jailbreak tool of choice, which should jailbreak the device and boot it into the normal operating system. Congratulations, you just overthrew your Orwellian overlord, and have taken back control of your device.
At least today, we will prevail!
Copyright © 2008–2009 — Jay Freeman (saurik)
****************************
Sorry dude, I dont have a 3GS and not at that firmware ... hope this leads you to success. |
|
|
|
|
