How-to: Recognize a Failbr3ak

‘Tis the season for failbr3aks, and it is good for everyone to be able to recognize them on a moments’ notice. Why? Because it can help prevent heartbr3ak (see what I did there?), by not having you fall into the trap of believing in a jailbreak program or exploit that has questionable credibility. That isn’t to say that a single person with computer knowledge can’t rise up to the challenge, but, in general, most don’t.

Luckily, forum user Appman created a guide to recognizing these fraudulent jailbreaks.

… if they give an ETA and/or they continually delay they jailbreak, that should raise suspicion.

This is one of the most prevalent clues as to whether the jailbreak is fake. Since failbr3ak developers have nothing to release, they repeatedly make promises to release on a certain date. That date comes and goes, and nothing happens. Circumstances such as these are what should, in your mind, separate the legitimate developers and the fake ones.

They spend most of the time replying to almost all the comments.

And this is the second sure-fire way to recognize the frauds. Instead of proving their knowledge and credibility through actions, they feel as if they have to prove themselves by reacting and responding to anything in their comments, regardless of if it is criticism, questions, or anything else. Since they don’t have a program to release, they have nothing better to do. Frequent updates on social media sites, such as Twitter are also another big clue, for the same reasons as above.

Read on for the full guide!

A failbr3ak is a fake jailbreak, and since there have been many Failbr3aks recently, I’m putting together a guide so you can tell if it’s a Failbr3ak or not.

1. The Dev or dev team. If it’s not from one of the well known devs or dev teams, obviously that should already be a sign.

2. The creation/release date. Usually failbr3aks are started during the time when a new device/firmware comes out, or when a legit dev team is in the process of creating a real jailbreak. Or when a firmware hasn’t been jailbroken for a while.

3. The proof. Usually they seem to stay away from giving any proof, but when they do, notice signs in the picture or video.
If the “proof” is blurry, choppy,or you can’t see the whole device and it’s firmware version, etc. Then it’s most likely fake.
A jailbreak video should follow along the lines of this guide.

4. Suddenly refuse to release. I have seen this happen many times, the fake devs say they won’t be releasing. They usually blame it on the public saying something on the lines of “We are not releasing because we have had too many comments saying it’s fake.” Also if they give an ETA and/or they continually delay they jailbreak, that should raise suspicion.

5. They announce they need beta testers. They will usually say this to keep the people thinking that this “jailbreak” is real. And they’ll randomly pick people for the beta.

6. The name they choose. This isn’t probably one of the most important things, but if they more worried about the name of the failbr3ak rather than the actual program, it’s most likely fake. Also, if they choose a weird alphanumeric name like “0re0c00ki3″, that should raise mild suspicion.

7. Unusually short working time. If the jailbreak progress goes from 10% to 90% in a short amount of time, you can tell it’s fake.

8. Some more small signs that may tell if it’s a failbr3ak are:
A url that ends in or
Claims that their jailbreak can do what the others can’t.
They spend most of the time replying to almost all the comments.

Known Legit Devs:
ChronicDev Team (don’t know what happened with them)
Sherif Hashim

Post a response / What do you think?