Connect with us

smartphones

Rooting Android 6.0 Devices Now Possible Without System ROOT -Chainfire

Published

on

According To ChainFIRE A Popular XDA Developer and Moderator
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
Idea
To have root on modern Android versions, we need our files to be executable and our daemon to be started on boot. We normally do this by making modifications to /system, tapping into binaries and scripts executed by init. If we’re also modifying the boot image, then we should be able to do all this without modifying system at all. A benefit of this is that it makes OTAs easier – reflashing the boot image is less hassle than reflashing system.

As the binaries should still be updatable, and we don’t know the space we have available in the boot image itself, we’re mounting a (writable) ext4 image with /su as mount point from /data, and modifying PATH accordingly. Interestingly, for reasons yet unknown to me, if the image is mounted r/o by init, later remounting it r/w causes a bunch of issues. So we’re keeping it r/w (for root) for now.

An overlayfs/unionfs solution would be even more ideal, transparently placing files in /system without modifying the actual partition, but I have not been able to find one that is (a) compatible with all Android architectures and (b) not kernel dependent and (c) not GPL – or even just one of those requirements, really. It’s technically all possible, it just needs to be done.

Caveats
– Apps with hardcoded paths to su (seriously?) will bork
– Factory reset unroots
– Factory reset wipes pin
– …
– Bugs… Bugs everywhere!

Instructions
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with eachother. The installer for this experiment will not clean up old root files.
– Flash stock /system
– Flash the attached boot image
– Flash the attached SuperSU ZIP in TWRP

Ramdisk modifications
– include (post above this one)
– init.rc (devs: please open file for reference)
— on init
—— mkdir /su …
— on post-fs-data
—— copy image from cache to data (for rooting without access to /data in custom recovery)
—— mount image to /su
— service daemonsu
– init.environ.rc
— export PATH, prepended with /su/bin
– file_contexts
— /su(/.*)? uRooting Android 6.0 Devices Now Possible Without System ROOT -Chainfire 1bject_r:system_file:s0

NOTE
– Not all SuperSU options are supported yet in this mode
– I have not tested with encrypted devices
– /system should never be remounted r/w, I hope I didn’t miss anything here
– Root with modifying /system is also still operational. I can’t predict what the exploiters will need.
– I’m not sure where we’re going with this. Future roots may require a clean system.

Michael Ajah is a Computer Science Student of The University of Port Harcourt and a Chelsea Fan. He loves RnB and a little mix of Trap Music. An awesome tech reviewer and analyst. Email - [email protected]

Continue Reading
Advertisement
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

smartphones

MTN Instabinge 1GB For N200 Now Valid For 3 Days

Published

on

MTN Instabinge 1GB For N200 Now Valid For 3 Days 2

Instagram addicts MTN has something special for you guys. The MTN Instabinge 1GB for N200 is now valid for 3 days.

MTN Instabinge 1GB For N200 Now Valid For 3 Days 3

The MTN Pulse InstaBinge bundle comes in two bundles rate which is 250MB for N100 and 1GB for N200 valid for 3 days..The offer is exclusive to Pulse users, meaning you need to migrate to Pulse by dialing *406#.

MTN Instabinge

Fam! The #MTNInstabinge heavy bundle is now valid for 3days and keeps getting better and better #JustForYou. Dial *406# to begin. pic.twitter.com/Pzs7vwHJtn

MTN Nigeria (@MTNNG) May 7, 2019

Before now, it was valid for just 24 hours, but MTN took to their social media handle to announce the new changes to 3 days validity.

To check InstaBinge bundle balance, dial *559*39#.

Continue Reading

smartphones

Android 10 / Android Q beta is now available for Tecno Spark 3 Pro and 20 other devices

Published

on

Android 10  / Android Q beta is now available for Tecno Spark 3 Pro and 20 other devices 4

Google has been working round the clock to release the next version of Android and now Android 10 (Android Q) beta is now available for Tecno Spark 3 Pro and about 20 other smartphones.

android q beta

It’s rather interesting to see a Tecno Spark 3 Pro added to the list of devices that are available for Google’s Android Q beta program but I’m still skeptical if it’s going to work well for now, not just on the Tecno but some other devices on the list.

If you have been following up the Android Q features lately you’ll know that Android 10 comes with a couple of new features – A native screen recording feature and of course dark mode.

Android 10  / Android Q beta is now available for Tecno Spark 3 Pro and 20 other devices 5

Android Q Beta 3 – Supported devices

  • Google Pixel
  • Google Pixel XL
  • Google Pixel 2
  • Google Pixel 2 XL
  • Google Pixel 3
  • Google Pixel 3 XL
  • Sony Xperia XZ3
  • Xiaomi Mi MIX 3 5G
  • Xiaomi Mi 9
  • OnePlus 6T
  • Nokia 8.1
  • LG G8
  • Huawei Mate 20 Pro
  • ASUS ZenFone 5Z
  • realme 3 Pro
  • OPPO Reno
  • Vivo NEX A
  • Vivo NEX S
  • Vivo X27
  • TECNO SPARK 3 Pro
  • Essential Phone

If you are already on Android Beta Program,  you’ll get the OTA updates automatically but for other devices, you can get the download link from Android developers website.

Continue Reading
Advertisement

New Arrivals

Recent Comparisons

Trending