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
Comments
10 thoughts on “JailbreakMe 3.0 and BiteSMS Conflict, Boot Loop Crash”
yup. just had a heart attack when i re jailbreak my iphone with jailbreakme and then installed bitesms. when i opened bite sms the page will de-colourised and crash, and iphone wil reboot.
after 3 straight times crash when opened bitesms, my phone had the boot loop, and i was scared that i cant get to the locksscreen..after some research, i did a recovery mode on my phone and now its fine again.. i need bitesms for its convenience, so after this i think ill just jb using the redsnow..
FML…I’ve restored my device 3 times today…and just now found this article!!! UGH…what a waste of a day…I guess I’ll go redsnow it up…
I think more than a “few” people are experiencing problems with the camera connection kit. I know I am.
i had a problem with installous 4 (invailed ipa) i found on google i have to uninstall appsync & install the current appsync for my ipad 2 4.3.3 so i did & it did not work so i tried to install my old appsync from hackulo but then i had many crashes and cydia is not download nor installing any thing from my sources so now i’ll have to restore my ipad 2
I am running bite sms with no issues (jailbreakme/4.3.3/ip4), but did suffer the crash with girlfriends ip4. crash loop as soon as she tried to reply on bitesms. dont know if it means anything or not, but my phone is a very early ip4 while gfs is brand new this week. but bite works perfectly on mine anyway.
I am running bite sms with no issues (jailbreakme/4.3.3/ip4), but did suffer the crash with girlfriends ip4. crash loop as soon as she tried to reply to a message on bitesms. dont know if it means anything or not, but my phone is a very early ip4 while gfs is brand new this week. but bite works perfectly on mine anyway. as to hers? only way out was a full restore
should have added i was on bitesms 5.4 Though being twitchy, and despite having used it since the day JBME3 went live, I just uninstalled it as knowing my luck it will do something bad just when I dont want it to
Seriously, unless you guys are a developer interested in tweaking or on an iPad 2 there’s really not much reason why JailbreakMe 3.0 will appeal to you especially if you use applications like BSMS. Just stick to redsn0w or greenpois0n.
I keep trying to think of a reason to update to 4.3.3. Articles like these leave me feeling smug about my 4.2.1 greenp0ison jailbreak. I have my phone customised and running as I want. The only thing that intersted me about 4.3.3 was the increased Safari performance but my iphone 4 and girlfriends white iphone 4 running 4.3.3 unjailbroken load pages at identical speed on both our wi-fi and respective 3g networks.
My only other performance issue is 2 second delay entering wiggle mode which is caused by an addon used by scrollingboard, five column sprigboard amongst others. Cant recall name of mobile substrate add on they all use but wondering if any 4.3.3 can report an improvement there. I’m guessing not as any UI slowness is normally down to too many mobile substrate addons and the one controlling the above mention tweaks (and a lot more) is a biggy. Since 4.3.3 uses more RAM than previous version anyway it’s unlikely this issue will be better.
Used the Jailbreak Me 3.0 with a Verizon Iphone4 with IOS V4.2.8 (CDMA) and Bite SMS 5.4. My phone was crashing after ending every single phone call. I uninstalled Bitesms, and now my phone is working beautiful. I’m sure this will be fixed soon as Bitesms is a really awesome app, even with phone crashing.