Samsung Galaxy S II you may want some custom ROM love on the device. User pulser_g2 over on the XDA forums has offered up version 1.0 of the VillianROM custom ROM loader for the S II smartphone. The VillainROM 1.0 for the Galaxy S2 smartphone definitely use at your own risk. The author of the software notes that he lacks the smartphone to test his software on.
Samsung Galaxy S II has only been on the market for a short while - and units are still in high demand - but we've already seen one of the first hacks of the smartphone. MoDaCo's Paul O'Brien has come up with a custom GSII insecure boot image that allows for adb shell root and adb remount. The ROM itself doesn't actually root the Galaxy S II, but it will allow owners to push the su binary and Superuser APK required for root. It also disables the flash-recovery script, replacing it with a call to /data/local/custom-scripting.sh. It's not the first root - one method was released at the tail end of April - but we're definitely excited to see more modders turn their attention to the Galaxy S II. While the phone itself impressed us in our review, we also saw plenty of potential as a platform for custom ROMs.
we reported that Skype for Android had a vulnerability which allowed a third party to harvest a user's data without their consent. Skype replied that they were taking action, but didn't tell us what it was. Now we know. Skype has solved the issue for now by removing the ability of a hacker to do so. And there's more ...
we reported that bloggers had found a vulnerability in the Skype App which allows hackers to harvest data from a user's Android handset with no need to root a phone or gain special permission. The problem was discovered during the testing of a leaked version of Skype for Android's new Video App. But it didn't take long to notice that the flaw was carried over from the already released Skype for Android App that's currently in the Market. Skype has responded to the news in their security blog, admitting that the flaw exists and they're working hard to fix it. But what can a user do to protect themselves in the meantime?