Related
Hi guys,
I just went into system apps, via Solid Explorer to grab an apk to put on my dev-host, when I got an error saying that I don't have root access.
I tried accessing other files in system root to get the same error. So I downloaded Root Checker and for some reason that's also saying that I don't have root access.
I know for a fact I have though as I've just been using root only features in ROM Toolbox Pro without an issue.
Any ideas as to why it's saying I don't have root access when I clearly do?
I'm on stock 4.2.2 and used the rooting tools in mike1986.'s thread to root once I'd flashed the stock ROM.
KidCarter93 said:
Hi guys,
I just went into system apps, via Solid Explorer to grab an apk to put on my dev-host, when I got an error saying that I don't have root access.
I tried accessing other files in system root to get the same error. So I downloaded Root Checker and for some reason that's also saying that I don't have root access.
I know for a fact I have though as I've just been using root only features in ROM Toolbox Pro without an issue.
Any ideas as to why it's saying I don't have root access when I clearly do?
I'm on stock 4.2.2 and used the rooting tools in mike1986.'s thread to root once I'd flashed the stock ROM.
Click to expand...
Click to collapse
one of those 4.2.2 roms didn't have root i can't remember which one, they forgot superuser or something
KidCarter93 said:
Hi guys,
I just went into system apps, via Solid Explorer to grab an apk to put on my dev-host, when I got an error saying that I don't have root access.
I tried accessing other files in system root to get the same error. So I downloaded Root Checker and for some reason that's also saying that I don't have root access.
I know for a fact I have though as I've just been using root only features in ROM Toolbox Pro without an issue.
Any ideas as to why it's saying I don't have root access when I clearly do?
I'm on stock 4.2.2 and used the rooting tools in mike1986.'s thread to root once I'd flashed the stock ROM.
Click to expand...
Click to collapse
Hey,
Does SU allow permission to access solid explore???
Click Thank if you find my post as useful
Aldo101t said:
one of those 4.2.2 roms didn't have root i can't remember which one, they forgot superuser or something
Click to expand...
Click to collapse
I downloaded the deodexed version which had superuser installed by using the rooting tools.
I flashed it a few days ago and have had no issues with being rooted until now. As I say, I'm still rooted but my phone's telling me I'm not and I'm not sure why.
Sent from my HTC One using xda premium
naren_viswa said:
Hey,
Does SU allow permission to access solid explore???
Click Thank if you find my post as useful
Click to expand...
Click to collapse
It already had the permissions from when I first installed solid explorer.
I just found out what my problem was. Superuser was installed by default and I downloaded SuperSU afterwards and must've disabled superuser and therefore was getting partial unroot issues.
I've now uninstalled superuser and I've got full access back
Sent from my HTC One using xda premium
Hi
I have tested the root tool from China forum. My device is SGP312 WIFI 32GB 10.3.1.C.0.136. No need to unlocked.
Download the attachment and install. One click and then it will reboot. It is rooted!
But the root-mangement software is Chinese. You can download Supersu or Superuser.
Use the Chinese root software to give Supersu or Superuser root access.
Run Supersu or Superuser and upgrade the binary. Exit and uninstall the Chinese root software.
Reboot. Then you are rooted with Supersu or Superuser.
This is the original link: http://www.mgyun.com/vroot
incredible...works on sgp321 .244......good job....juat install supersu afterwards and remove the chinese app....greatttttt
Good! I can confirm it works, just rooted my still locked SGP311FR with it.
What I don't like it's an exe file, install the app then run it to root.
If someone can extract the script and replace the root apk by superSU it would be cool.
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Anyway thanks.
Btw : @insideccw posting a link to the source, and maybe the name of the autor of this tool, would be better if it's not your own tool.
babylonbwoy said:
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Click to expand...
Click to collapse
That might be the exploit that is accessing the framebuffer causing it.
works like a charm on my sgp351 lte 16gb .244, recomended, thans for the post
Also working with Xperia sp
Sent from my C5303 using Tapatalk 4
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Word fine With 4.2.2 thx a lot
Sent from my SGP321 using XDA Premium 4 mobile app
bugger561 said:
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Click to expand...
Click to collapse
I think you need to install the alternative superuser app before deleting the Chinese one. I used superuser by chainsdd on my sp
Sent from my C5303 using Tapatalk 4
works great...thanks
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
I don't know if the info in this thread may be of any use : http://forum.xda-developers.com/showthread.php?t=1539711.
Specifically in the OP :
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
And in Post #8 :
Confirmed working fine! Recommended to install via CWM. It will replace the other (superuser) automatically so you don't have to manually remove it.
I used the above zip file and instructions a long time ago on my Galaxy S....but it may still be relevant for Tablet Z.
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
bugger
That is because you dont have /system r/w access.
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
It worked for me...I accidentally removed the Chinese app.
1. I did a reroot again.
2. installed dualrecovery and flashed the UPDATE-SuperSU-v1.65.zip.
3. It works now.
Supersu and cwm superuser caused my phone to go in a reboot loop when I tried updating the binaries. Superuser by ChainsDD is working fine though.
Sent from my C5303 using Tapatalk 4
insideccw,
Any tips on how t go about correcting this? Would I need to use adb or can I handle this form within android?
EDIT: Looks like others are having the same issue.
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Geezer said:
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Click to expand...
Click to collapse
Works on mine. Update the superuser binaries before deleting Chinese superuser app. On mine, supersu detected the Chinese one and deleted it for me
Sent from my C5303 using Tapatalk 4
bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
For those of you having this issue as I was, I just got mine to work with SuperSU. Hopefully these steps will work for you too:
-Gain root with the magical Chinese root tool
-install SuperSU
-update SuperSU binaries
-in SuperSU settings, choose "Switch superuser app"
-reboot the tablet and immediately go to the playstore and install SuperSU
-update SuperSU binaries
Let me know if it works!
SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.
has this method been verified by other users?
Share your experience please!
It's brand new...
Verified by myself
Have you maintained root after reboot?
ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done
I waiting also others to confirm
stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !
Ok guys, thanks for confirming, Sweet
Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3
*ROOT WORKING !! SMT-700 OTA 'lollipop'
Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.
Maybe ashyx could help.
What exactly didn't work for you ?
stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.
Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?
I read on another forum that Titanium Backup does not work if you're using systemless root. Can anyone verify if this is true ?
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
aparanoidandroid said:
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
Click to expand...
Click to collapse
Make backup's with TWRP.
NLBeev said:
Make backup's with TWRP.
Click to expand...
Click to collapse
I know how to make backups with TB. That wasn't my question. My question is, how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
aparanoidandroid said:
... how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
Click to expand...
Click to collapse
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
NLBeev said:
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
aparanoidandroid said:
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
Click to expand...
Click to collapse
Yes since version 2.6x.
NLBeev said:
Yes since version 2.6x.
Click to expand...
Click to collapse
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method. Do root apps need to be specifically modified for this type of rooting so it can recognize it ?
Also just to be clear, I am on stock Android 6.0 ROM, rooted and with TWRP recovery.
so the order that I would need following according to the post that you gave me is:
Flash 6.0.1 ROM
flash Update-unSU
flash SuperUser 2.61 or 2.52
Is that correct ? Can I dirty flash 6.0.1 over 6.0 ?
aparanoidandroid said:
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method.
Click to expand...
Click to collapse
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
NLBeev said:
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
Click to expand...
Click to collapse
Oh really ? From what I read, Android Pay and OTA both do work using systemless root although many people think that Google will find a way to block Android Pay again. Its one of the reasons I wanted to use systemless root in the first place.
aparanoidandroid said:
Oh really ? From what I read, Android Pay and OTA both do work using systemless root..
Click to expand...
Click to collapse
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
NLBeev said:
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
OK. Thanks for the info.
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
hayzooos said:
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
Click to expand...
Click to collapse
thanks but what happens when you wipe system ? What will I lose other than root ?
aparanoidandroid said:
thanks but what happens when you wipe system ? What will I lose other than root ?
Click to expand...
Click to collapse
Anything Xposed related will be gone, but other than that...nothing. All apps, settings, etc of mine were all retained. Wifi networks, bluetooth connections, all those stayed. Wallpaper, Nova Launcher setup/settings, stayed.
Most ROMs have built in their script to wipe the system partition before flashing anyway, so you're likely already doing it if you're flashing ROMs. I just wanted to start with a pretty clean slate and check to see if anything in data was causing issues, and nothing so far.
Titanium Backup 7.4.0.2 and System Root was working about 2 weeks ago FLAWLESSLY
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
Sorry,
I could not acquire root privileges.
This application will *not* work! Please
verify that your ROM is rooted, and try
again.
This attempt was made using the "/system/
bin/su"command."
CLETjB said:
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
Sorry,
I could not acquire root privileges.
This application will *not* work! Please
verify that your ROM is rooted, and try
again.
This attempt was made using the "/system/
bin/su"command."
Click to expand...
Click to collapse
Do you have Busybox installed? If not, that may be why. Had the same issue, installed Busybox to /su/xbin, and all is good now.
Gravity Box works with XPosed Framework, which ONLY works with "BusyBox on Rails", which I do have installed. Not sure if I can tell it where to install BusyBox, but it seems to be working now.
Does anyone have a clue to get magisk and titanium backup to work with each other... TB does not seem to ask for Root, seems to simply bypass it...
-----Nevermind, just make sure you have unticked Magisk Hide- in Settings. WORKS!
Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.