POSTS TAGGED: Samsung Galaxy S II
Posted July 12, 2012 at 09:00 pm by Will Verduzco
Just about three months ago, we brought you news that the Team Win Recovery Project had received a massive update to version 2.1. April’s release largely heralded the start of a new age in recoveries—where one would no longer have to deal with cumbersome menus, instead interacting with a very user-friendly GUI.
It wasn’t simply about the GUI either. In addition to bringing an unrivaled level of UI polish, TWRP 2.1 offered users many advanced features such as update.zip queuing, a basic file manager, and dual storage support for Nandroid backups. Additionally, TWRP added support for the open source scripting engine OpenRecoveryScript, which works in conjunction with the pr. . . READ ON »
Posted July 11, 2012 at 09:00 am by Former Writer
As of late, the Samsung Galaxy S II I9100 has been running into some problems. Not only is there a hard brick bug from a leaked kernel that no one should ever flash, but the bug affects many users differently. Some may be hard bricked, while others may only be soft bricked. There are many users who’ve already flashed the kernel and don’t know how to get rid of it. All in all, the LQ5 leak is quite dangerous.
The problem is a little complicated. When users flash the LQ5 leak from Samsung, they are flashing a kernel that has a hard brick bug. The bug is activated upon attempting to flash anything from recovery and from performing a factory reset. Basically, don’t wipe, format, or flash anything. For more . . . READ ON »
Posted July 10, 2012 at 07:00 pm by Former Writer
One of the biggest perks of having an Android phone is the customization. Any given Android user can make any given Android phone look and behave how they want. Even without root, there are replacements for virtually any application that comes on whatever Android device you can think of. With root, the customization gets even more ridiculous. There are custom ROMs, kernels, mods, tweaks, scripts, themes, and even fixes to issues that were on the phone since launch. Where is a user to start? For AT&T Galaxy S II Skyrocket users, you can always start with AromaKoaK.
AromaKoak, or AROMA Kang of all Kangs is a set of modifications that users can choose to install on AOSP ROMs of their choice. Created by XDA Senior M. . . READ ON »
Posted July 10, 2012 at 11:30 am by Former Writer
The march of Jelly Bean across XDA has reached a fevered pitch since it was first announced at Google I/O 2012. With a number of devices receiving a port of the new version of Android on the rise and more expected in the future now that Jelly Bean source was released, Jelly Bean has certainly hit with a splash. For Samsung Galaxy S II I9100 and HTC EVO 3D users, there isn’t an AOSP version of Jelly Bean yet. However, there is a SDK port users can check out to preview JB.
The Galaxy S II port is a little rough as expected for an alpha release but it does have a number of things working. The list includes:
. . . READ ON »
SD card (internal-only)
MTP (can’t copy files)
SM (courtesy of bp
Posted July 9, 2012 at 10:30 am by Former Writer
Although there’s talk of CM10 around the web, developers aren’t quite done yet getting CyanogenMod 9 on as many phones as possible. With the first release candidate for CM9 released, developers have a great code base to bring an AOSP-derived experience to other devices. One such build is for the Samsung Galaxy S II HD LTE.
XDA Recognized Developer and Retired Senior Moderator dsixda is responsible for bringing CM9 to the highly underrated device. Despite not being the most popular version of the Galaxy S II, the port is very well done, with only a few minor issues. The list of current things working include:
. . . READ ON »
– Adobe Flash
– Play Store
– Hardware acceler
Posted June 30, 2012 at 10:30 pm by Former Writer
Improvements in technology always bring new challenges to developers. Of course, improving technology can bring rehashes of previous challenges to solve once again. One such challenge is battery life. With the release of dual core and quad core phones, the additional cores present a double edged sword. Multiple cores improve performance in certain situations dramatically, but most of the time they also require more power to operate. Taming the multi-core processors to provide better battery life has been the challenge for quite some time now, and many devices have solutions. Now, the T-Mobile Samsung Galaxy S II has one as well.
Posted June 26, 2012 at 03:00 pm by Former Writer
It has been a long time coming. Many Samsung Galaxy S II owners have been clamoring for an HTC Sense port for a while now, with over 1500 users asking for it. There have been several attempts made with bits and pieces coming in, but the Galaxy S II has never had a bootable HTC Sense port. Now, not only is there a bootable Sense port, but it’s Sense 4.0—the latest and greatest version to date.
It took a lot of teamwork to get it this far. XDA Senior Member QuBe2 has kept track of all involved in the project and it’ll like be a lot more before the port is fully functional. So far the team, dubbed Team Sense4All, has gotten the ROM booting but aside from that, it isn’t quite clear what works and what does. . . READ ON »
Posted June 15, 2012 at 09:00 am by Will Verduzco
Not that many people have heard of the Samsung Galaxy S II HD LTE. This device is quite similar to the AT&T Galaxy S II Skyrocket, but as its name implies, features a Super AMOLED HD display. In fact, other than the display resolution differences, the two devices are nearly identical, down to the Qualcomm Snapdragon S3 processor.
Despite the similarities, root methods and recovery software is incompatible across devices. Luckily, this is where XDA Recognized Developer dsixda, of DSIXDA ROM Kitchen fame, comes in. Thanks to his work, the device now has root, recovery, and a mildly debloated custom ROM.
The recovery itself comes in the form of an unofficial port of ClockworkMod Recovery v188.8.131.52. Inst. . . READ ON »
Posted June 8, 2012 at 04:30 pm by Will Verduzco
By now, you’ve undoubtedly heard about the Samsung HardBrick bug that has reared its ugly head on various Samsung Exynos 4210-based devices including but not limited to the Galaxy Note GT-N7000, Epic 4G Touch, AT&T Galaxy S II, and the Korean SHW-M250S/K/L. In fact, we recently featured an app made by XDA Elite Recognized Developer Chainfire aimed at determining your particular device’s risk for hard brick.
Samsung is aware of the issue, which was first noted by Elite Recognized Developer Entropy512, and is in the final stages of delivering a solution. Until then, however, it is still advised to not flash any leaked kernels, or kernels in which MMC_CAP_ERASE is presen. . . READ ON »