Jump to content


xSellize For Sale

All offers should be directed here


Evasi0n makes today sunday funday yet again!

22 Dec 2013

Posted By sadam in iDevice News

Seems like there is no stopping the evasi0n team they have been working tirelessly to make a jailbreak for us this time they have not created any buzz or hype before release date seems to have come out of the blue, There is not much else for me to say apart from go get it from the link below




Evasi0n Jailbreak Compatible with all iPhone, iPod touch, iPad and iPad mini models running iOS 7.0 through 7.0.4



  6288 Views · 7 Replies ( Last reply by rochellezc11 )


iOS 6.1.3-6.1.5 Jailbreak P0sixspwn Released By @iH8sn0w...

31 Dec 2013

Posted By PigPox in iDevice News
On Monday, December 30, 2013 an iOS 6.1.3 - 6.1.5 untethered jailbreak was released by @iH8sn0w and @winocm for all iOS 6X devices, but was the loss of a valuable exploit too high a price to pay? (Photo:Twitter)

On Monday, December 30, 2013 an iOS 6.1.3, 6.1.4, 6.1.5 untethered jailbreak all iPhones, iPads and iPods was released by @iH8sn0w and @winocm. Its name is p0sixspwn. While many in the jailbreak community should be pleased — particularly those with the iPhone 3GS and other iDevices which don't support the latest iOS 7 jailbreak — it seems this iOS 6.1.3-6.1.5 jailbreak came at a high cost, as other exploits reportedly could have been used to produce the same result.


On Monday morning, Evad3rs team member and evasi0n7 creator Cyril Cattiaux aka @Pod2g posted a series of tweets with regard to how the new p0sixspwn jailbreak was created and released.

While the jailbreak community has been extremely torn by the events of the last week, and few know where to place their loyalty, this latest drama seems like just one more hit to those who simply want to enjoy the freedom jailbreaks provide to their iOS devices.

@winocm @iH8sn0w it's silly that they called it "drama free" though wink.png

— pod2g (@pod2g) December 30, 2013

Throughout the evasi0n7 debacle, @pod2g has been the most vocal of the evad3rs team members, writing two public letters to the community to explain the situation that developed with TaiG while also taking responsibility for the damage done and working to rebuild the bridge that was burned with @Saurik. But this morning's tweets seemed to show some frustration with the on-going drama that runs even deeper than has been completely told. It seems in releasing their new jailbreak for iOS 6X, @iH8sn0w and @winocm burnt some incredibly valuable exploits which have been kept carefully by the jailbreak developers for use in research when new iOS devices and firmwares are released. The most unsettling part of all is that burning that exploit was not a necessity.

.@pod2g @comex and they have two other invaluable exploits that could have been used instead sad.png — Nikias Bassen (@pimskeks) December 30, 2013

So what does all of today's drama mean for the jailbreak community? In speaking to @pod2g this morning, it seems the loss is not a small one.

In hearing this description, numerous questions came into my mind. What will happen in the future if Apple patches this exploit? Could it be used in a downgrade tool? If Apple doesn't patch the exploit will a 7.1 jailbreak be released? Both @pod2g and @comex were gracious enough to give me some comment on these points.

"They talked a lot of sh-- about us, but now they've burnt valuable stuff just for 6.1.x ... nobody looked at their jailbreak tool, but they burnt something allowing root on all devices without any effort. Something that jailbreakers were aware of for years now. Something that's usually the entry point for jailbreak research on new iOS versions and devices. Root code execution. Something that usually requires multiple exploits to achieve."


A valuable exploit that Comex discovered in iOS was burned in the creation of p0sixspwn, but the security researcher says, it doesn't make future jailbreaking impossible.

According to @comex, though the exploit burned is valuable, it does not completely negate the ability to create future jailbreaks. According to the former jailbreak developer, "it makes things more difficult, but not impossible."

To that

@pod2g added,

 "Implications are that it'll make life of jailbreakers even harder for future iOS jailbreak developments. And I suppose that we'll never find another root execution and injection exploit of this kind in the future. Basically, it allows files to be made available in the device file system (injection) and allows to execute code as root. For example, we could setup afc2 on new iOS versions to play with the file system and find vulnerabilities."



This exploit, along with some others, was the same one @chpwn used last fall when he produced the infamous iOS 6 failbreak, which prematurely raised the community's hopes. In seeing the value that this particular exploit holds, I asked Cyril if a downgrade tool was in the works, or if by chance, Apple doesn't patch the exploit in 7.1, would the evad3rs be releasing an iOS 7.1 jailbreak using it.

Here is how he replied.

As to a possible iOS 7.1 jailbreak, this was his response.

"A downgrade tool is a completely different story. It requires breaking the boot chain of trust."

To that he added,

"It depends on what Apple patches ... let's say we'd want to burn it for iOS 7.1, we would also need a unsigned code execution vulnerability, a kernel exploit, and a way to stick that at boot."

To emphasize just how valuable the exploit is, @pod2g takes his explanation a bit further.

"But even if we still had that injection and root stuff, not sure that we would release it, because of its value."

"A jailbreak is a whole chain of exploits ... that exploit of @comex's that we did not want to burn in evasi0n7 [would require] 5 vulnerabilities to do the same thing. That's why it is so valuable. The fact that Apple did not patched it in years also is important. It means that it is probably the last thing you'd like to burn when there's nothing remaining."

As a final question, I did ask Cyril what his thoughts were on why @winocm and @iH8sn0w would burn such valuable exploits in the iOS 6.1.3 - 6.1.5 p0sixpwn jailbreak released Monday. Was it truly spite?

To that there seems to be no answer. Cyril's only response was:

I have reached out to @winocm and @iH8sn0w for a response, but thus far have received no reply. If they submit a rebuttal, I will update this post. To download and install @winocm and @iH8sn0w's iOS 6.1.3 - 6.1.5 jailbreak, visit p0sixspwn.com

"Why? I dunno. Perhaps they were not aware it still works on newer versions."



via idesigntimes

  4632 Views · 2 Replies ( Last reply by rochellezc11 )


Donald Trump: I've hounded Apple into producing large...

25 Mar 2014

Posted By sadam in iDevice News
In a tweet that reflects his confident opinion of his power and influence, the TV personality and businessman reveals that his pressure on Apple will soon bear fruit.

Success in business is largely about taking credit.

Just ask the co-founders of Twitter. Or, more accurately, those who say they're the co-founders of Twitter.

It is said, indeed, that Steve Jobs used to take credit for too much at Apple. But now that he's gone, a new creditor has stepped into the limelight he so appears to enjoy.

Donald Trump, he whose name is on hotels and the "Celebrity Apprentice," seems to be taking credit for Apple's latest iPhone.

True, no one's actually seen Apple's latest iPhone. But Trump revealed on Monday that he knows what's coming. And what's coming has been thanks to the deep and influential pressure he has massaged and kneaded into Apple CEO Tim Cook.

In a tweet that was a forthright as it was human, Trump wrote: "I wonder if Apple is upset with me for hounding them to produce a large screen iPhone. I hear they will be doing it soon -- long overdue."

I may have a response to his wonderment.

Apple is as upset with Trump for his hounding as it's upset with Simon Cowell for no longer being on "American Idol." He's made Cook as cross as has the man who invented the cronut.

Indeed, I suspect that Cook has felt as hounded by Trump as he's felt hounded by the Lumberjack Marching Band at Stephen F. Austin State University.

True, Trump has used his megaphonic platform to call for a larger iPhone. In October of last year, he used Twitter to ululate: "As an addition, Apple must go to a larger screen now -- asap! They're losing their standing in the market!"

It's clear since then that Apple has, indeed, lost much of its standing in the market. Apple stores are closing all around the world and people are keeping their iPhones in their purses and pockets, for fear of being seen with them.

The fact that Trump has revealed that Apple is releasing a large screen iPhone "soon" surely means the company will be doing it "soon."

  2489 Views · 2 Replies ( Last reply by rochellezc11 )


Top 10 Apple iOS 7 problems and complaints

12 Oct 2013

Posted By sadam in iDevice News

Apple’s iOS 7 redesign has been available to download for three weeks now since it went live on 18 September. Apple revealed soon after that 200 million devices have downloaded the software, and that number is no doubt higher now.

However, it is fair to say that not everyone has been won over by the new design as demonstrated by our head to head review of iOS 6 and iOS 7, which has seen numerous V3 readers complaining about issues, glitches and irritations with the new OS.

As such, we’ve put together 10 issues we've seen repeatedly raised, and some we’ve experienced ourselves, and that we hope Apple will be working to address in any major overhaul in the near future. 

10. iMessage bug still not fixed


Since iOS 7 came out there have been complaints that messages sent over Apple’s iMessage platform between devices, especially to those still on iOS 6, are failing to deliver.

Coupled with this is the fact the notification of the failure often does not arrive until much, much later, meaning a user may not be aware an important message has not been sent, until it is far too late.

This is something Apple has promised to fix but until it does, the issue remains one of the top frustrations with the new operating system.

9. Battery drain complaints


A number of users who have installed iOS 7 on older devices, such as the iPhone 5 and iPhone 4S, have reported a dip in battery life since installing Apple's fancy new software.

iPhones already don't have a great reputation when it comes to battery life, so it's fair to say this issue hasn't gone down too well among iOS 7 users. Some have said their battery is draining twice as quickly as before installing the software, while other are claiming their handset struggles to make it through just a few hours.

The iPad is also reportedly affected by the issue, but given its longer battery life, owners of the tablet haven't been so quick to moan about it. Apple is yet to issue a fix, but iOS users have found a few workarounds. These include turning off Apple's motion features, disabling 'Background App Refresh' and turning off the Airdrop feature.

8. Illegible fonts


Several V3 readers commented that they found Apple's stylish new font choice difficult to read in many situations. The combination of a high-resolution screen coupled with very thin vertical lines is causing a great deal of strife.

Steven Cogorno wrote: "It's basically unreadable. The fonts are too thin, and the translucent background is gimmicky and distracting."

It's worth noting that it is actually possible to alter various aspects of the font in iOS 7, including size and boldness. Furthermore, there are options to change the contrast of the device.

With that being said, it would seem Apple didn't take non-20/20 vision into account when designing iOS 7's default appearance.

7. Concerns linger over security issues


While Apple has rolled out two fixes since it launched iOS 7, we can’t help but wonder about the other perils that lurk in the system. The passcode bypass techniques came to light fairly sharpish, and Apple has now fixed this.

However, as the 41 fixes in the iOS 7 update showed when Apple rolled out the new software, the firm is always having to patch issues as it goes.

In this respect Apple is not so different from Microsoft, but it would be nice if the launch of its new software wasn’t so immediately followed up with a raft of security concerns.


6. Calendar app loses daily updates


The Calendar app in iOS 7 no longer offers an overview of the day's events when you're in the Month view. Daily information can be accessed via the reworked Notifications menu – which offers Today, All and Missed views – or by clicking through to each individual day from the month view, but after using this for a couple of weeks we found ourselves missing the original and handy monthly view.

Apple has also reworked the Calendar app to fit its new streamlined, clean look and feel. Gone are the grey lines dividing up each day, and blue banner highlighting today; in comes rows of numbers with a grey circle underneath each digit, and today highlighted by a bright red circle. Although the thinking behind Apple’s disposal of lines and boxes for other apps and features of iOS 7 makes sense, in this case it seems users would prefer a calendar that looks like a calendar.

One V3 reader noted: "For older users removing calendar summary is a disaster and faded headings, taking out grey boxes, leaving glaring white pages and faded writing, along with replacing icons with vibrant icons is unsuccessful not to say hurts your eyes. Wish I had stayed with iOS 6."

5. Update is slowing down older devices


Those who haven't picked up either an iPhone 5C or iPhone 5S and who have instead installed iOS 7 on their current iPhone - or iPad - are likely experiencing a downgrade in speed, with hoards of angry iOS users slamming Apple for the slow-down they are experiencing.

The V3 team has installed iOS 7 on a third-generation iPad and an older iPhone 4, and the dip in performance is very noticeable. This is likely due to the updated operating system's fancy new motion effects, design features and reworked applications.

While Apple is yet to comment on this issue, Apple fans have been hasty in finding a quick fix for the issue, which involved turning off the newly-implemented motion effects and the translucent visuals within the redesigned interface.

So, if you want iOS 7 without a dip in performance, it looks like you'll have to settle for a compromise for now.


4. Universal search disappears


With the arrival of iOS 7, Apple has changed the search feature to remove rather than add functionality. Rather than swiping from left to right on the homescreen to search, you now tap the top of the screen. We found this takes some getting used to when moving from iOS 6 to 7, but isn't too inconvenient.

However, we didn't like the fact that you can no longer carry out a single search across your device and the web. In iOS 7, the OS will search everything stored in your device, but you need to visit a browser and carry out a separate web search.  The universal search feature of previous iOS versions was a very useful feature, and one that many users would like to see returned.

One V3 reader commented: “Sorry I 'upgraded'. Most significantly, the very easy search function on the earlier version, which was accessed by swiping your finger across the home screen and which showed all possible data in the phone AND ALLOWED A WEB SEARCH for data not in the phone, has been replaced with a search function that only looks at matching data in the phone. Terrible loss of functionality!”

3. Motion sickness


Not one we’ve been unlucky enough to suffer from at V3, but scores of people have complained that the movement between applications on iOS 7 is inducing motion sickness.

This is said to be because of the way the phone ‘lurches’ in and out of apps. Furthermore, because the platform has a 3D effect called the parallax effect, this means apps and text are always adjusting to display at the viewer's angle.

All said, whether or not this is Apple’s fault is slightly irrelevant. Anyone made to feel sick using their phone can only feel justified in feeling aggrieved.


2. Design gripes


Apple has based its success on having the best looking devices and software. This focus on beauty and elegance has made Sir Jony Ive the toast of the design world, earning him a knighthood in the process.

However, it is fair to say many are distinctly unimpressed with the new design of iOS 7. Criticisms seen on V3 have ranged from people describing it as making their phone look like “a Fisher Price toy” and as if it was designed “by a 13-year-old girl”.

Other issues focusing on more specific areas of the redesign include the over use of white backgrounds, which are hard to look at on apps such as Notes: "The Notes pages used to have lines and made your text far clearer and readable but not now," as one reader noted.

Furthermore, the use of a foggy grey shade for folders and the fixed app bar at the bottom of the screen is fairly uninspiring. These criticisms could well hurt Apple and maybe it will consider a minor refresh to the platform when it unveils its next new iOS products. We, and many others, certainly hope so.

1. No downgrade option to iOS 6


Often if you buy something and then regret this decision, you can take the item in question back to the shop and get a refund. However, with software it is not so simple and Apple has removed any chance of a backwards downgrade to iOS 6 for those really hating the new OS.

For some V3 readers this has proved an immense irritiation: "I have just written direct to Apple to complain about the fact that they are actively denying customer satisfaction by not allowing those of us who absolutely hate iOS 7 to change back," wrote one.

The reason Apple removes the option to revert to an old system is because it wants as many devices as possible across its ecosystem on the same platform. This helps the firm maintain a controlled environment, unlike the wild west of Android where device fragmentation is rife.

As such, if you’re on iOS 6 now and are yet to upgrade, and concerned these issues will frustrate you, you may just want to hold out as a modern day Luddite on an old iOS platform, and wait for a major update to iOS 7 to address all the above issues.

  9235 Views · 6 Replies ( Last reply by fliemicoene )


Apple and Samsung heading back to court after mediation t...

14 Feb 2014

Posted By PigPox in iDevice News





Apple CEO Tim Cook and Samsung's mobile chief and co-CEO JK Shin reportedly met last week to try and thrash out a settlement to their long-running intellectual property dispute. The meeting, while unconfirmed by either party, is being reported by multiple Korean news outlets and adheres to the companies' promise to try and come to an amicable agreement before resuming their legal antagonism next month.

Sources indicate that the mediation effort was unproductive, which comes as no surprise given the history of animosity between Apple and


Samsung and the fact that similar talks were fruitless back in 2012.

Shin was expected to fly out to the US next week, ahead of a February 19th deadline for conducting these talks, but Chosun reports he's presently in Korea and has no plans to leave the country before that date — suggesting that he has already been to the US and met with the Apple CEO. Although Tim Cook has repeatedly expressed his distaste for legal entanglement, this particular disagreement appears to be intractable enough to keep the companies returning to the courtroom time after time.


via TheVerge




  2200 Views · 1 Replies ( Last reply by fliemicoene )


Why Apple's Recent Security Flaw Is So Scary

23 Feb 2014

Posted By CydiaPkg in iDevice News





On Friday, Apple quietly released iOS 7.0.6, explaining in a brief release note that it fixed a bug in which "an attacker with a privileged network position may capture or modify data in sessions protected by SSL/TLS." That's the understated version. Another way to put it? Update your iPhone right now.

Oh, and by the way, OS X has the same issues—except there's no fix out yet.

If you understand what that release note meant in full, chances are you were first in line for the iOS update. If it reads like deleted scene from Sneakers, here's what it means for you and your Apple devices.

What Is SSL?

SSL stands for Secure Sockets Layer, and it's what helps ensure that communication between your browser and your favorite websites' servers remains private and secure. TLS, or Transport Layer Security, is a more recent protocol that does essentially the same. In brief, SSL/TLS is a cryptographic key that lets a browser and a server know they are who they say they are, a secret digital handshake that keeps your financial information safe when you make an Amazon payment or log into wellsfargo.com.

This all happens in the background; your only direct interaction with SSL/TLS is when you notice the lock icon in your search bar has clamped shut. That means you've got a direct, private, secure line.




While Apple recently patched a major security flaw for iOS, the same vulnerability continues to affect OS X. Until Apple releases a fix--which it… Read…

The Apple bug in question—which, again, has been patched in iOS but not yet in OS X, though Apple tells Reuters that fix is coming "very soon"—means that Safari or one of these other affected applications can't actually know for sure if the servers it's talking to are who they say they are. Which leaves you and everything you transmit over the web vulnerable to a Man in the Middle attack.

What's a Man in the Middle Attack?

A Man in the Middle Attack, which we'll call MitM from here for brevity's sake, is basically high-tech eavesdropping. A MitM attacker intercepts the communication between your browser and a site, monitoring, recording, seeing everything that transpires between you.

Gmail. Facebook. Financial transactions. OK Cupid flirting. All of it read, in real-time, by a complete stranger. Here it is in oversimplified chart form:


Normally attacks like this are are foiled by SSL/TLS (encrypted handshakes are hard to get in the middle of), or at least rendered too difficult to be worth it. But this Apple bug makes it painfully easy. That "privileged network position" an attacker needs to be in, referenced in the release notes? That just means he's in the same Starbucks as you.

And this has been going on since September. Of 2012.

How Serious Is It?

If you're still scratching your head over what all of this means and how bad it is, the simplest way to explain it is that developers who understand it deeply weren't even willing to talk about it openly, for fear of giving hackers more ammunition than they already had:

.@grittygrease @csoghoian It's not just Safari — using any Mail.app, iCal, or any service that relies on TLS on the iPhone/Mac is vulnerable

— ashkan soltani (@ashk4n) February 22, 2014

Dear everyone: do *not* use Safari until Apple patches their SSL code in Mac OS X. Man-in-the-middle exploits are already in the wild.

— Nick Sullivan (@grittygrease) February 22, 2014

Ok, yes, the iOS/OS X bug does break SSL completely. Like @matthew_d_green I'm going to keep quiet. Patch quickly.

— Adam Langley (@agl__) February 22, 2014

I'm not going to talk details about the Apple bug except to say the following. It is seriously exploitable and not yet under control.

— Matthew Green (@matthew_d_green) February 21, 2014



That same Matthew Green, a Johns Hopkins cryptography professor, also explained to Reuters that it was "as bad as you could imagine, that's all I can say." So there you go!

You can afford to take a little bit of a deep breath; obviously there's not a hacker lurking in every coffee shop, and your personal information is never as interesting to others as you think it is. And if you've updated your iPhone or iPad to 7.0.6, you're fine.

But knowing that this has been going on for a year and a half is troubling just on principle. And knowing that it's been this widely publicized and hasn't yet been fixed for MacBooks means it's worth taking a few extra ounces of precaution.

How Did This Happen?

Nobody knows, and Apple's understandably not saying. But theories range from the plausible to the tin foil hatted. Let's start with what probably happened and work our way up.

Google's Adam Langley detailed the specifics of the bug in his personal blog, if you're looking to stare at some code. But essentially, it comes down to one simple extra line out of nearly 2,000. As ZDNet points out, one extra "goto fail;" statement tucked in about a third of the way means that the SSL verification will go through in almost every case, regardless of if the keys match up or not.

Langley's take, and the most plausible? That it could have happened to anybody:

This sort of subtle bug deep in the code is a nightmare. I believe that it's just a mistake and I feel very bad for whomever might have slipped in an editor and created it.



Wow. Nothing is sacred. The Washington Post has discovered that the NSA and FBI have teamed up to tap into the servers of nine US tech… Read…

It doesn't take too much of a stretch of the imagination, though, to draw a few shaky lines between this bug and the NSA's PRISM program. No less an Apple devotee than John Gruber did just that last night, pointing out that the "goto fail;" command first snuck into iOS 6.0, which shipped just a month before Apple was reportedly added to the spy agency's info-snooping PRISM program.

If you want to go full tinfoil hat based on that timing, you're welcome to, but it's highly unlikely that Apple intentionally added this bit of code. It's entirely possible, though, that the NSA found out about it before Apple did, and has been secretly exploiting it for its PRISM purposes.

How Can I Prevent It?

If you're on an iOS device, you need to download 7.0.6 immediately. If you've got a 3GS or an old iPod touch, you can download iOS 6.1.6 instead. And if you were looking for an indication of just how seriously Apple is taking this, the fact that they're supporting an iOS version that they are incredibly eager to phase out should be as good an indicator as any.

So far, though, you're out of luck if you're on OS X. The vulnerability is still there, and now that it's been widely publicized, bad guys are going to be keen to take advantage while they can. There's an unofficial patch floating out there, but please know that it's not for beginners.

Your best option in the meantime is to use Chrome or Firefox, which aren't affected on OS X. Also make sure you stay on secured networks, and if you do wind up on a shared network to play it smart (no financial info, no transactions, no personal details). That's a good rule of thumb generally, but especially important until this is made right.

Oh, and to hope that a fix "very soon" means hours or days, not weeks.




via Gizmodo

  2900 Views · 1 Replies ( Last reply by fliemicoene )

  0 Views · 0 Replies


Chicago Woman Arrested Trying to Sell Child on Craigslist...

14 Feb 2014

Posted By PigPox in iDevice News




South Side Chicago native Kathy Stevens was arrested today after the Chicago Police Department received a tip that the woman was looking to sell or trade her child on Craigslist in exchange for a iPhone 5 with the Flappy Bird App.





The Hugely popular mobile app Flappy Bird was removed from the market by the creator Dong Nguyen and has caused the price of phones still containing the App to go as high as $20,000 and more on ebay.

Police say the woman was a troubled 28 year old who was determined to leverage her child to obtain the Flappy Bird App.



via IactAfool

  2222 Views · 2 Replies ( Last reply by pkmaximum )

  0 Views · 0 Replies

  0 Views · 0 Replies

Latest Discussions

Site Navigation

Online Users

3 members, 137 visitors and 0 anonymous users

Bing, Yahoo, chankapo119, xmzk, +saleen392

  • 558360 Total Posts
  • 527085 Total Members
  • chankapo119 Newest Member
  • 12756 Most Online

140 users are online (in the past 15 minutes)

3 members, 137 guests, 0 anonymous users   (See full list)

Bing, Yahoo, chankapo119, xmzk, +saleen392

Portal v1.4.0 by DevFuse | Based on IP.Board Portal by IPS
IPB skins by Skinbox