Most of this article doesn't only apply to Telegram+ -- it just happens to be an example that got a lot of coverage elsewhere, with many authors or commentators putting the full blame on Google, Telegram, the Telegram+ developer or even WhatsApp Inc (eh?). In this article, we'll try to look at the different aspects to provide a clear view of what actually happened, and what can (and hopefully will) improve with regards to developers in general and the Play...
Root Achieved on the Samsung Galaxy S III
Not too long ago, we went hands-on with the Samsung Galaxy S III. In fact, XDA Elite Recognized Developer Chainfire, who was later kind enough to go on camera for a fun interview and unboxing, even made a brief cameo in the video as we tested USB Host functionality on the SGS3 using his popular DSLR Controller app. Needless to say, much of the Android community is eagerly anticipating the launch of Samsung’s new flagship.
However, many people won’t bother with devices that aren’t rooted. Luckily this has been quick to achieve on Samsung devices in the past, and the Galaxy S III is no different. Before the official release, Chainfire has managed to root the SGS3. While Chainfire is currently unable to release the insecure boot image because it may be traceable, this most likely won’t be the case for long. In his words:
Unfortunately, I am not able to share the “insecure” kernel with you at the moment, because of fears it is traceable to the leaker (this is said to be the last traceable firmware revision).
This root is, as expected, trivial. It was a simple matter of repacking the stock kernel, with a modified adbd binary that thinks ro.secure=0 (even if ro.secure=1). This gives access to all adb root commands (see screenshots). Then SuperSU was installed manually.
Kernel – The modification was trivial, because this time around, Samsung is using the standard boot.img format, instead of the zImage format used for SGS1, SGS2, SGNote, etc, that is much harder to repackage.
Recovery – The recovery partition is also being used this time around. And thus we can flash recoveries separately from the kernel.
Bootloaders – There was no warning triangle at boot-up after flashing the modified kernel, but download mode did show a custom kernel flash counter which increased. Whether or not flashing a custom recovery also triggers this counter is as of yet unknown.
Final note – This was all tested on a current (release candidate) SGS3 firmware. There may be a newer firmware on true retail/production devices. Though some things may change, it is unlikely to changemuch. Let’s hope nothing
Also, Triangle Away did not work. They have hidden the boot partitions again as on the latest SGNote firmwares.
(No, I don’t have an SGS3 yet, everything was done remotely)
Now if you take a closer look at that last line, you’ll see what is perhaps the most impressive aspect of Chainfire’s achievement. Not only is he the first to root the device, but he did so working remotely, sight-unseen.
What are you waiting for? If you’re lucky enough to have your hands on a pre-release SGS3, head over to the original thread to learn more. This is exciting news even if you don’t yet own the device, but wish to purchase one in the near future!
Want something on the XDA Portal? Send us a tip!
Ever since custom recoveries and roms became popular, nandroid backups have been the fall back method for all android enthusiasts, irrespective of their confidence levels. They allow easy backup and restore in case things go wrong, which happens invariably when a modification is being tested. With that being said, how relevant are Nandroid Backups to this day? Back in 2011, when the world of Android was being awed by the likes of the Samsung Galaxy S2, a little modification made its appearance...
While HTC's latest flagship brings many new features, the aesthetic design of the device remains largely untouched in comparison to its predecessor. Many Android enthusiasts throughout the community were expecting a large redesign of one of the most beautiful handsets ever released, but what we got is something more along the lines of an 'HTC One M8S". So this begs the question, is the M9 worth the upgrade if you already own the M8? Current HTC One M8 users chime in and let us know your thoughts.