Moderator: 3ne2nr Mods
http://192.168.210.104/mmrelay.com is exactly the settings that bmobile has there with their carrier update, unless you think their own carrier update is wrong.shaq090 wrote:SRASC wrote:APN: mms
MMSC: http://192.168.210.104/mmrelay.com
MMS Proxy: 192.168.210.104:8080
MMS Max Message Size: 307200
i most likely believe u need to take off the .com
well, I was rooting through the OS and I stumbled across this in the fairplayd daemon. This is on the iPod touch 4 on iOS 5 beta 1.
SRASC wrote:Was thinking it would be a good idea to link custom firmwares so that people could easily update to the latest or in some cases last firmware for their particular iPhone with no problem, so 3.1.3 for the 2G, 4.2.1 for the 3G & for now 4.3.3 for the 3GS & 4. (preferably whole not part).
In that same regard any important links or how to's that may have been posted in this thread to be highlighted in the first post, cause we can't expect someone to search all 211 pages...
iOS 3.1.3 for iPhone (2G)
For many, Marathon will invoke a wave of nostalgia; for others, this will be the first experience with the seminal Mac FPS. I hope all players appreciate Bungie's commitment to their fans. It's not every company who would support bringing a 16 year old game back to life!
TSMC stands a good chance of winning orders for Apple’s A6 processors, the paper quoted Dan Heyler, a semiconductor analyst with Merrill Lynch in Taipei, as indicating. But even if TSMC grabs all Apple’s tablet chip orders for 2012, sales generated from the orders will account for only 2% of TSMC’s overall sales for the year, Heyler was quoted as saying.
Apple reportedly continues to contract Samsung Electronics to manufacture its A5 processors, using the foundry’s 45nm process, the Commercial Times quoted industry sources as saying in a separate report. One thing for sure is that TSMC will not gain any orders from Apple in 2011, the paper observed.
iPhone Dev Team wrote:It looks like Apple is about to aggressively combat the “replay attacks” that have until now allowed users to use iTunes to restore to previous firmware versions using saved SHSH blobs.
Those of you who have been jailbreaking for a while have probably heard us periodically warn you to “save your blobs” for each firmware using either Cydia or TinyUmbrella (or even the “copy from /tmp during restore” method for advanced users). Saving your blobs for a given firmware on your specific device allows you to restore *that* device to *that* firmware even after Apple has stopped signing it. That’s all about to change.
Starting with the iOS5 beta, the role of the “APTicket” is changing — it’s being used much like the “BBTicket” has always been used. The LLB and iBoot stages of the boot sequence are being refined to depend on the authenticity of the APTicket, which is uniquely generated at each and every restore (in other words, it doesn’t depend merely on your ECID and firmware version…it changes every time you restore, based partly on a random number). This APTicket authentication will happen at every boot, not just at restore time. Because only Apple has the crypto keys to properly sign the per-restore APTicket, replayed APTickets are useless.
This will only affect restores starting at iOS5 and onward, and Apple will be able to flip that switch off and on at will (by opening or closing the APTicket signing window for that firmware, like they do for the BBTicket). geohot’s limera1n exploit occurs before any of this new checking is done, so tethered jailbreaks will still always be possible for devices where limera1n applies. Also, restoring to pre-5.0 firmwares with saved blobs will still be possible (but you’ll soon start to need to use older iTunes versions for that). Note that iTunes ultimately is *not* the component that matters here..it’s the boot sequence on the device starting with the LLB.
Although it’s always been just “a matter of time” before Apple started doing this (they’ve always done this with the BBTicket), it’s still a significant move on Apple’s part (and it also dovetails with certain technical requirements of their upcoming OTA “delta” updates).
Note: although there may still be ways to combat this, a beta period is really not the time or place to discuss them. We’re just letting you know what Apple has already done in their exisiting beta releases — they’ve stepped up their game!
scientist wrote:I'm on the iOS5 Beta 2 now...working pretty stable, installed it sat night
Bezman wrote:mentions nothing if the prepaid smart phone would be sold unlocked, also bmob would rpob charge $9000 TTD for the $350 USD iPhone 4S anyway
src1983 wrote:I don't know anyone with such an account
This sucks......
src1983 wrote:I don't know anyone with such an account
This sucks......
mojosodope wrote:src1983 wrote:I don't know anyone with such an account
This sucks......
beta 2 isnt downgradable, its best to wait for the official release anyways but im running beta 2 right now on an AT&T i4 and it's pretty stable for the most part, can't wait for the GM
devteam wrote: Also, restoring to pre-5.0 firmwares with saved blobs will still be possible (but you’ll soon start to need to use older iTunes versions for that)
src1983 wrote:I don't know anyone with such an account
This sucks......
Return to “Ole talk and more Ole talk”
Users browsing this forum: Google Adsense [Bot] and 79 guests