If you fired up Pokemon Go yesterday just to find that you weren't able to connect, there's one potentially good reason behind it. It appears that Google recently updated how their SafetyNet detections work, and the new changes are able to pick up some previous root-hiding methods. If you are using Magisk, the current workaround is to set it to operate in "core only" mode via settings in Magisk Manager. Read More
In the wake of recent problems, a partial fix has been pushed for SuperSU. Root loss on older (pre-4.4/Kit Kat) phones should no longer be an issue. Unfortunately, this latest update doesn't fix the bootlooping some Sony Xperia phones are experiencing. If you're using SuperSU on one, you should continue to stick with 2.79 for now. Read More
Users of SuperSu might want to hold off on updating things for a short while. Over the last couple days, some people have reported that the latest updates, 2.80 and 2.81, have been causing some issues on specific devices. Problems cover a range of minor inconveniences, from temporary loss of root on some older devices to bootloops on specific phones. None of these should be significant issues for those with the technical knowledge to root their devices, but they might be enough of a potential concern to hold off updating for a bit. SuperSU developer Chainfire has said that he is aware of the problems and is working towards a fix. Read More
If you've already updated to Android 4.3, whether via an OTA or by flashing it manually, and rooted it, you're more than likely using Chainfire's SuperSU, which carefully works around the new restrictions Google put in place. Cody has a good write-up about why they did it and what's going on, so go read that if you're interested in the details.
Chainfire created the Android 4.3-compatible root method and the updated SuperSU back when the first leaks showed up for the Galaxy S4 but hasn't updated it for a few weeks. During that time, a good portion of users have discovered that sometimes SuperSU causes CPU spikes and starts eating up 100% CPU. Read More
In an almost superhero-like act, Koushik Dutta (a.k.a. Koush of ROM Manager fame) has pushed his completely rewritten Superuser app to the Play Store just 15 days after first announcing it on Google+. This version introduces several improvements upon the original Superuser. In the last two weeks, the feature list has grown to include fully functioning multi-user support, secure PIN protection, and support for the x86 and ARM architectures. Additionally, the interface has been revitalized with a clean looking Holo theme and a tablet UI.
Koush didn't stop there – he also added a feature to make root-seeking apps more visible. Read More
Koushik Dutta, the author of ClockworkMod Recovery and such iconic Android apps as ROM Manager and, more recently, Carbon, has decided to tackle a new subject that is also very dear to the Android community - Superuser and root access control. Koush's latest app, now in beta and coming soon to the Play Store, is called simply ClockworkMod Superuser.
How Is It Different?
How does the new Superuser compare to the existing Superuser by ChainsDD and SuperSU by Chainfire, both very respectable root gatekeeper apps? There are indeed several important differences, the most important one being that Koush's Superuser is open source and free, with code available in his Github repo for thorough examination. Read More
"If it's not broken, don't fix it" is a wise and popular mantra among anyone who fixes anything. Developers, on the other hand, couldn't care less. Enter SuperSu. While Superuser has been a staple of root usage for a long time now, XDA developer Chainfire (who has also brought us many other fantastic apps), has taken what already works and made it even better.
SuperSU performs the usual tasks of managing superuser access, with a few added benefits, including logging superuser access, temporary unroot, and it even works in recovery. Here's the full list of features:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
One of the first examples of a reason to temporarily unroot that comes to mind is to use Play Movies, though a quick search through the thread on XDA reveals that users have tried with mixed results. Read More
Well, that's the easy part done. The DROID X2 has been rooted, huzzah! The device was found to be vulnerable to one of the known root exploits out there (Gingerbreak) - apparently Moto couldn't be bothered to patch up the hole (the fix has been backported to 2.2 from AOSP, according to our own Justin Case.) This hasn't been fully confirmed yet, but it seems plausible, given that all previous Motorola Froyo builds have been susceptible to this exploit.
Next on the list: cracking open that bootloader (good luck.)
Droid-life Read More
The Galaxy Tab 10.1 hasn't even been in our hands more than 12 hours, but it has already been rooted. Turns out Samsung left absolutely no protection on the device, and rooting it is even easier than rooting a XOOM, and that says a lot (the XOOM was meant to be easily unlocked and rooted).
For comparison, the XOOM root requires fast oem unlock and data wipe, while the Galaxy Tab 10.1 root process is as simple as mounting the file system for writing and copying su and SuperUser.apk to it, all of which is packaged into a nice flashable zip file. Read More
We have some great news this morning for the rooting/ROM fans out there - a new milestone of OpenEclair has been reached and version 1.3 is now available for download here.
If you are interested in the discussion around this release, head over here.
What Is OpenEclair?
OpenEclair is a community ROM based on the AOSP (Android Open Source Project) 2.1 source code (with lots of Cyanogen mixed in).
The goal of OpenEclair is to bring to the community a fast and stable Eclair 2.1 ROM, with contributions from numerous ROM developers.
To clarify what may not be obvious on the OpenEclair site, the ROM is aimed at 2 devices specifically:
- HTC Dream - T-Mobile G1
- HTC Sapphire - T-Mobile myTouch 3G
OpenEclair is actively developed (just look at the number of filed and fixed bugs), maintained, and tested by the community which means frequent releases, attention to users and testers, $0 price tag (of course), and all the great stuff open source software development brings with it. Read More