Related
i just rooted my droid 1 with the superone click method. it went well, but when i tried to install the apps for rooted users, it failed. can some help me with that? please. mark
I didn't work if you cannot installed root required apps.
What version of Android are you using?
kramy24 said:
i just rooted my droid 1 with the superone click method. it went well, but when i tried to install the apps for rooted users, it failed. can some help me with that? please. mark
Click to expand...
Click to collapse
It is possibly the "Root" app is installing older script (busybox old version?) that might not function fully enough on your phone.
Better find a newer version or other method(prefer OR) to Root with newer script installed.
i flashed the latest cf root 5.6 kernel with cwm and mo..the phone.rebooted afterward...bur the kernel doeant look like its been changed.from stock? can someone confirm it for me from yhe attachment? thanks
Check if you have SuperSU and/or CWM app installed. If so - then it's working. Kernel version signature might be the same as rooting replaces your kernel with the same version - but rooted.
yes, I have both of them installed thank you for your help
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.
My device is S-ON (UNLOCKED, TWRP, HBOOT 1.61, flashed SuperSU 2.78, Android 5.0.2, stock 7.18.709.151). The only way to s-off is paid money. So I flash AdAway_systemless_hosts_v2.zip in TWRP, but I have problem.
There's no error shows when install AdAway_systemless_hosts_v2.zip, but after install it and reboot to system then install AdAway v3.1.2 apk, enable AdAway and download host, restart system, I found AdAaway didn't enable every time I restart.
I also use this way, but I can't find any "su" folder in my phone, also read these way, B can't be update by APP, C looks not safe and old, A didn't work (/data/data/hosts). I already flashed Xposed, and it seems work fine, Root Checker also shows I have root access, so I think I got root right.
Is there anyone tell me how to make AdAway_systemless_hosts_v2.zip work in my S-ON M7? Thanks!
matif525 said:
My device is S-ON (UNLOCKED, TWRP, HBOOT 1.61, flashed SuperSU 2.78, Android 5.0.2, stock 7.18.709.151). The only way to s-off is paid money. So I flash AdAway_systemless_hosts_v2.zip in TWRP, but I have problem.
There's no error shows when install AdAway_systemless_hosts_v2.zip, but after install it and reboot to system then install AdAway v3.1.2 apk, enable AdAway and download host, restart system, I found AdAaway didn't enable every time I restart.
I also use this way, but I can't find any "su" folder in my phone, also read these way, B can't be update by APP, C looks not safe and old, A didn't work (/data/data/hosts).
I already flashed Xposed, and it seems work fine, Root Check also shows I have permission, so I think I got ROOT right.
Is there anyone tell me how to make AdAway_systemless_hosts_v2.zip work in my S-ON M7? Thanks!
Click to expand...
Click to collapse
I think systemless root and everything related to it is Android M feature, and it doesn't work on M7. Someone please correct me if I'm wrong here
donkeykong1 said:
I think systemless root and everything related to it is Android M feature, and it doesn't work on M7. Someone please correct me if I'm wrong here
Click to expand...
Click to collapse
Thank you! So, I can't use AdAway normal in S-ON Android 5.0.2?
matif525 said:
Thank you! So, I can't use AdAway normal in S-ON Android 5.0.2?
Click to expand...
Click to collapse
You can use the normal adaway, not the systemless one. Find it in xposed
donkeykong1 said:
You can use the normal adaway, not the systemless one. Find it in xposed
Click to expand...
Click to collapse
Thansk you very much!
I searched "AdAway" in http://repo.xposed.info/module-overview, nothing useful, but found hosts Enabler, are you talking about this?
matif525 said:
Thansk you very much!
I searched "AdAway" in http://repo.xposed.info/module-overview, nothing useful, but found hosts Enabler, are you talking about this?
Click to expand...
Click to collapse
I just remembered. You are on stock kernel, right? Because stock kernel has system write protection and you can't use AdAway. You can flash a custom kernel with system write protection disabled and you should be fine