The release of the Corona untethered jailbreak for iOS 5.0.1 hasn’t come with its fair share of problems, which led the Chronic Dev Team to update the tool a couple weeks ago to fix the Launchctl error.

Unfortunately, this update was not enough to fix all the problems inherent to Corona. The main issue that users have been experiencing is with the iBooks app, which would just display an error message at launch. We shared a few workarounds with you to fix this problem, but we knew an official fix was on the way…

According to Saurik, Corona has been updated to version 1.0-5, and fixes the iBooks problems as well as the launchctl error mentioned above.

 

Now you have two options. If you installed Corona from Cydia, just launch Cydia and install the update when prompted. If you jailbroke using RedSn0w, simply go to Cydia and install Corona from there. This will supposedly take care of all your problems.

If you had previously installed iBookFix, I’m not 100% sure, but I assume it’d be wise to first uninstall it, then install/update Corona.

For those of you who haven’t jailbroken their device yet, we urge you to look at our jailbreak section. You’ll learn everything you need to know about jailbreaking.

  • I just see ” jailbreak” and I get my hopes up.
    -_______-

  • Eric Morgan

    My iBooks is still broken.

  • mattsuperman148

    I want a jailbreak. NOW :'(

    • Anonymous

      I have one.

  • i jailbroke my iphone on iOS 5.0.1 via the latest redsnow and then did the manual iBooks fix with ssh
    if i install corona will it remove the the manual iBooks fix automatically?

    • No it won’t

      • so i assume i would have to remove the manual ibboks fix before i install corona 1.0.5 but i have no idea how to remove it its not in the cydia auto install folder anymore

      • You should just be able to run Corona on top. It *shouldn’t* affect anything

      • i installed corona 1.0.5 and the iBook from the appstore is working like a charm but the second iBooks is still there how do i remove it?

      • I think you have to remove manually w/ iFile/SSH from /Applications, but don’t take my word for it. I’m fixing to find out myself.

  • Didn’t work for me. Ibook don’t work even after a reboot. Try to uninstall ibookfix and reinstall corona. Reboot and doesn’t work 🙁

  • Sebastion,
    iBooks doesn’t crash, it tells you a configuration error and makes you quit the app.

  • i don’t know..just curious about that ibooks problem..just installed mine..opened it..didn’t crush or whatsoever.. I didn’t even download corona.. i’m on ios 5.0.1 jailbroken using redsnow

    • Like I said before, iBooks doesn’t crash on this untether, it simply tells you that it can’t be used.

  • iBooks is still broken for me even after rebooting a couple of times and attempting to reinstall the new version of Corona.

  • Anonymous

    I don’t see anything but the 1.0-3. What source is it in. Btw anyone else notice that an ipad1 split keyboard doesn’t move up and down like it did before I jailbroke it

    • Make sure the package updates. I only had seen .3 until after the update

  • Works and smooth like a sugar

  • I’m having the same issue as stated above. No update is shown only version 1.0.3 which I currently have installed over redsn0w.

  • This just trashed my i4. Immediately after install, gmail started screaming that password was wrong. When I went into settings and put it in again, it said could not verify google.com. Rebooted, and now stuck at boot logo

  • Anonymous

    Just applied this to 3 idevices in my household and removed the ibooksfix2 from cydia first and deleted the ibooks app manually with ifile. no problems everything is working great!

  • i download it and it worked fine reading book right now 😛

  • Anonymous

    corona update crash my safari camera ….

  • Iphone keep rebooting after installing Corona (5.0.1 untether) 1.0-4

    please help!

  • it works!!!

  • Anonymous

    I did my update now my Typophone 4 doesnt work anymore, wth????

  • Anonymous

    tnx 4 this update, it also fixed some little thing that was messing with my “Wired memory” (RAM)
    dont know what it was… but it aint consuming as fast as before