P.S.A.- Jelly Bean And How to Avoid the Galaxy Nexus Reboot Issue
So just in case you were living under a rock last week Google took the covers off the newest version of its Android operating system, dubbed Jelly Bean. The new O.S. promised to bring the usual upgrades, faster scrolling, smoother transitions, slicker interface, but it also brings a whole bevy of iOS fighting ingredients to the table. I will get to those later after some use and review. In the meantime the big news for all of us Galaxy Nexus users out there was that someone screwed up and left a version of 4.1 Jelly Bean sitting out loose on Google’s server and before they realized it, the software was leaked and ROMs were being cranked out!
So I swiftly went over to my friendly Rootzwiki Forum and looked around at some ROMs. I chose Vicious Toro JellyBean and flashed away. For one whole day it was glorious! My phone has never been so smooth and slick. Everything worked and I was a happy camper. Along about 10pm I got off the phone and set it down on the counter. I poured a drink and came back to my phone rebooting and on the black Google screen. Ok fine, I said. It is a leak some reboots are bound to happen. Except my phone was frozen the Google screen for the next 10 minutes. I tried some battery pulls with the same result. Time to say to hell with it and flash my backup right? Into CWM I went and everything was going smoothly until a Data Restore error message came up. The backup ROM I flashed also ended in a softboot, as did EVERY backup I attempted to flash. So after reaching out to my usual peeps on Google Plus (thanks again Alvin) I swiftly found out that I was not alone. The reboot issue was striking GNex owners across multiple ROMs so I cannot solely blame Vicious. The link from XDA below shows you the way out of this little mess. You will have to truly and thoroughly wipe your phone and attempt to flash the exact same ROM. I attempted this 3 times and on the 3rd attempt my phone came back up. Not only did it come back up but all of my apps and data were restored too. All this after attempting to restore 2 different ROMs and doing the most thorough wipe of my life. Once I was back up and running I started looking at ROMs again. Jelly Belly stood out to me in that it came out after this issue had been discovered and promised to have it fixed. I spoke with the developer behind this ROM, Jake Day, last night and here is what he had to say about finding the problem, “I was playing with the dump and noticed that booting was throwing some errors. Looked into the partitions and how they were setup and what the mounts were doing. Looked over the init scripts and the updater script too. All of the above needed correcting. Made the entire process more standard and corrected the partitions and mount points, as well as what the init scripts were doing with them.”
So after taking care of this small but major problem we finally have a ROM that will not lock you into the soft boot hell that some other JB leaks ROMs will. Already Varnibean and other ROMs are using Jake’s patch to keep this from happening to their users. So for all of you that are out there having these reboot issues look no further than Jake’s Jelly Belly ROM. Once again leave it to the aftermarket of Android to make sure that our user experience is a good one!! I have included links below to both the XDA page showing you how to fix the issue and the Jelly Belly ROM so you can enjoy Android 4.1 Jelly Bean without worrying about bricking your Nexus!
XDA-Jelly Bean Fix
RootzWiki-Jelly Belly ROM
JKeene, AndroREV Editor
We Are AndroREV, WE ARE!!!!!!
