For the owners of Samsung Galaxy SII and Galaxy S III, they are indeed familar in using the operating system of Android 4.0 Ice Cream Sandwich. Currently, there is no update available yet officially for the latest Android 4.1 Jelly Bean. Thanks to xda-forum members who always try so hard to develop the system into the better choice to put into the one that is not provided with the update.
For those who want to taste the latest Android 4.1 Jelly Bean on their Samsung Galaxy S II and Galaxy S III, on this article i will show you the steps to upgrade the system using the Custom ROM made by the members of xda-forum. However, this custom ROM is still buggy and there is many thing that does not work so far and waiting to be developed further.
- device boot
- SD card (internal-only)
- MTP (can't copy files)
- Network Data (courtesy of stormtroopercs)
- Google Now/Google Search
- anything else.
Considering there are many thing that does not working now, so you have to consider firt wether this upgrade is useful for you or not. We are not responsible for any damage on your device. and we recommend you to follow the tutorial carefully.
Preparation you need to do before upgrading:
- Download JellyBeanAlpha.zip, Kernel (to fix mobile data): zIMAGE-JB.zip, SuperUser fix: CWM-SU-v0.89_fixSU.zip.
- Create a full NANDroid backup.
- Backup your /efs partition to an external location, such as your computer. A great tool to do this is provided by lyriquidperfection — EFS Pro.
- Ensure that you're running a 5.x version of ClockworkMod Recovery.
Steps to upgrade:
- Using CWM, make sure to wipe data/factory reset, then wipe cache, and then go into advanced, and wipe the Dalvik cache too.
- From there, flash the ROM (JellyBeanAlpha.zip).
- Afterwards, repeat the wipe step (step #1).
- Continuing on, go into advanced and fix permissions.
- After fixing the permissions, go back and flash the kernel (zIMAGE-JB.zip) — this will fix the mobile data connection. Then flash CWM-SU-v0.89_fixSU.zip, it will get SuperUser working on the ROM.
- Finally, reboot the device.