JailbreakMe 3.0 and BiteSMS Conflict, Boot Loop Crash
When you think about the amount of downloads JailbreakMe 3.0 has had, there are not really many problems. Ok there a few but nothing really bad, the latest issue with this jailbreak is the JailbreakMe and BiteSMS conflict. A few days ago there was a problem with a few users mentioning the iPad Camera Connection Kit was not working after downloading the new jailbreak, and now the BiteSMS conflict.
What is BiteSMS (For those that do not know): BiteSMS offers lots of features such as quick compose, privacy, quick reply, smileys, scheduled SMS, passcode lock, signatures, delivery reports and much more. Using biteSMS to send messages is potentially a lot cheaper to send messages. But we guess most of you know about biteSMS, so please read on about the problem it has with JailbreakMe 3.0.
There are many reports coming in that BiteSMS (Jailbreak Tweak) is conflicting with JailbreakMe 3.0, after users downloaded the new JailbreakMe users found that sending text messages via BiteSMS’ quick reply feature saw a few crashes, apparently it crashes your device and sends it into an infinite boot loop, looks like you may have to restore your device if you have experienced this problem.
If you visit JailbreakQA’s main page, you will find a report that says “Jailbreakme users also report that BiteSMS’s Quick Reply feature causes a boot loop (if you need this, restore and re-jailbreak with redsn0w instead).”
iDB suggests that this will get sorted out soon via an update, but they do recommend that users do NOT install BiteSMS if you plan on using JailbreakMe 3.0 or alternatively jailbreak 4.3.3 with RedSn0w.
JailbreakMe is a very good jailbreak, so the problem above does not mean it is buggy and full of problems, what it could me is that it is the first jailbreak tool that uses the unionfs concept. Comex has reported before that previous jailbreaks needed ‘stashing’ large file directories within iOS and moving symlinks from the original location to a new one. Does this mean that the code is getting confused? iDB explains that “One explanation could be that the reason conflicts may be manifesting themselves is that some jailbreak applications such as BiteSMS have in the past relied on the altered directory locations from older jailbreaks, instead of Comex’s unionfs method of jailbreaking.”
We would like to hear from our readers if they are having problems with the JailbreakMe 3.0 and BiteSMS conflict, we would love to know if anyone has found an answer to get out of the boot loop. Is there an answer to stop users restoring their devices? Please do use the commenting area below and have your say, any answers or questions you have please do them here. Thanks