I did the systemless root method and installed cataclysm rom and elementalx kernel but when I check SuperSu it says "No SU Binary Installed". Anyway to fix this that won't cause me to give up android pay? That was my only reason to go the systemless root route. Thanks y'all.
As far as I know systemless root doesn't work with elementalx yet.
Correct me if I'm wrong though.
Casmo said:
As far as I know systemless root doesn't work with elementalx yet.
Correct me if I'm wrong though.
Click to expand...
Click to collapse
I'm not using systemless, but several in the ElX thread have reported it working. It is necessary to flash the stock modified boot image before ElX though. Just do a search in the thread for "systemless".
adrman said:
I'm not using systemless, but several in the ElX thread have reported it working. It is necessary to flash the stock modified boot image before ElX though. Just do a search in the thread for "systemless".
Click to expand...
Click to collapse
I tried systemless, but then I saw ElX didn't work with it, so I went the traditional way.
I don't use AP anyways, and I think that's pretty much the only thing why people currently want systemless.
Related
Hey,
I'm trying to make Secure Settings work but I think the app is not compatible with systemless root (if this is not true, tell me please). I went with systemless root at first because it was the latest and what everyone was talking about but, tbf, Android Pay is not even available where I live so I see no point on staying with systemless.
I'm on Cataclysm and ElementalX. What's the best way to go from systemless root to system root?
Thanks
Sorry for reviving an old post - but same here. I flashed the latest SuperSU zip without knowing it was systemless.
I believe you can unroot usign SuperSU and then flash an earlier version of the SuperSU zip that works with Marshmallow.
I have installed Magisk on my XT1575, for those who dont know, its a method in which Xposed can be installed systemless, with the benefit of taking OTA's. And as a bonus, things like android pay work (with a on-the-fly toggle) to turn off root check, snapchat works, etc.
Pre-requisites (MARSHMALLOW)
1. Stock rom (this is mandated by the developer @topjohnwu ) preferably stock kernel, but i am using frankenclark
1A. TWRP (Download Link Here) https://dl.twrp.me/clark/twrp-3.0.2-0-clark.img.html
2. Magisk manager zip (Download Link Here) http://forum.xda-developers.com/devdb/project/dl/?id=19632&task=get
3. Custom superuser PHH-Superuser (Download link here) http://forum.xda-developers.com/devdb/project/dl/?id=19633&task=get
4. Custom Xposed (Download Link Here) http://forum.xda-developers.com/attachment.php?attachmentid=3832615&d=1470276932
5. Custom Superuser app from the playstore (Download Link Here) https://play.google.com/store/apps/details?id=me.phh.superuser
6. Custom Xposed Installer (Download Link Here) http://forum.xda-developers.com/devdb/project/dl/?id=19668&task=get
Steps:
1. Start with clean stock marshmallow 18-4 (i used the firmware flash and did it that way)
2. Install TWRP (1A)
3. Boot into TWRP recovery (do not select system writable. leave it stock, this ensures the chances of OTA support, unless you dont care, then set it writable)
4. Flash frankenkernel, if you want, if not continue on
5. Flash MAGISK (2)
6. FLASH custom superuser (3)
7. Flash Xposed framework (4)
8. reboot into marshamallow
9. Before opening MAGISK, install the custom superuser app from the playstore (5)
10. Install the custom XPOSED installer (6)
11. You should now see that xposed 86.3 is active
12. Profit, make sure to check MAGISK and see if the toggle between rooted and unrooted works, but it should.
MAGISK thread http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Links #3 and #4 are dead.
Do I need PHH-Superuser or can I use SuperSU? It looks like I only need PHH-Superuser if I want to use android Pay.
betarepeating said:
Links #3 and #4 are dead.
Do I need PHH-Superuser or can I use SuperSU? It looks like I only need PHH-Superuser if I want to use android Pay.
Click to expand...
Click to collapse
Correct, if your not interested in the whole android pay thing. Its because i havent updated to the version 2 links yet
aer0zer0 said:
Correct, if your not interested in the whole android pay thing. Its because i havent updated to the version 2 links yet
Click to expand...
Click to collapse
What are you running for a stock, rooted systemless supersu ROM that passes safety net?
SR3TLAW said:
What are you running for a stock, rooted systemless supersu ROM that passes safety net?
Click to expand...
Click to collapse
whelp, the whole reason i had a xpure was because my 10 was getting uh oh'd for a broken display, and that took 2 weeks. When i wrote the post, magisk and phh was rollin in the regards that android pay (safetynet) had been beat, so i wrote a writeup on how to do it. Now safetynet has been upgraded to the point where magisk is beat, afaik.
Magisk screwed with my banking app, and i didnt use it for anything else, so i stuck with systemless supersu & xposed instead, no magisk on my 10.
Honestly, im not sure why people want android pay, all the places i used it, charged me extra for using, like a 1.50 pepsi cost 2.10 out of our vending machines at work.
Couldn't agree more. For the systemless root - all you did was install SuperSU from play store and run that command in twrp?
Sent from my XT1575 using Tapatalk
Titanium backup will not gain root access. Can someone help?
dkeepitabuck said:
Titanium backup will not gain root access. Can someone help?
Click to expand...
Click to collapse
Is your phone rooted?
Sent from my XT1575 using Tapatalk
Cdub1976 said:
Is your phone rooted?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I fixed it but I need help getting secure settings to work. I did something to get it working earlier but it caused TB to break.
I am running TruPureXMM ROM, can i still flash phh's superuser even though i already have SuperSU systemless root that came with the ROM?
SnowBlacks said:
I am running TruPureXMM ROM, can i still flash phh's superuser even though i already have SuperSU systemless root that came with the ROM?
Click to expand...
Click to collapse
No, Magisk is only designed for stock, unrooted roms. It doesn't get around SafetyNet anymore anyway, Android Pay, Pokémon Go, and most financial apps won't work anyway.
acejavelin said:
No, Magisk is only designed for stock, unrooted roms. It doesn't get around SafetyNet anymore anyway, Android Pay, Pok�©mon Go, and most financial apps won't work anyway.
Click to expand...
Click to collapse
Yeah, i wanna use suHide but i need magisk first. Can i just unroot and then flash phh superuser?
SnowBlacks said:
Yeah, i wanna use suHide but i need magisk first. Can i just unroot and then flash phh superuser?
Click to expand...
Click to collapse
Nandroid and try a full unroot and reboot... It might work since it's largely stock, but it doesn't work in most custom roms
So I have the stock (OTA) MM rom installed and rooted with SuperSU flashed, however Android Pay will not work. I've tried disabling root in SuperSU, but that doesn't work for AP. Is there another method that actually works to allow? All the info I can find about it from last year.
Look around the frankenclark thread in development. I think they might have had a working setup with magisk in the discussion there.
macville said:
So I have the stock (OTA) MM rom installed and rooted with SuperSU flashed, however Android Pay will not work. I've tried disabling root in SuperSU, but that doesn't work for AP. Is there another method that actually works to allow? All the info I can find about it from last year.
Click to expand...
Click to collapse
jason2678 said:
Look around the frankenclark thread in development. I think they might have had a working setup with magisk in the discussion there.
Click to expand...
Click to collapse
It's been a while since others and I posted about that, so that method doesn't work anymore. I don't use Magisk now. It might be working again, but I won't test, so here's my setup without Magisk:
SuperSU flashed as systemless + update SuperSU to 2.78-SR5 + suhide 0.55 + Root Switch 1.3.3.2
Flash in that order.
Use Tasker or Automate to automatically disable and re-enable root when Android Pay and Google Play Services is/is not used, or disable/enable root from within the Root Switch app itself.
Confirmed that it works on stock rooted Marshmallow here.
Anyone know why it wont stay
Ssys no batty
Says no binary installed
pbedard said:
Says no binary installed
Click to expand...
Click to collapse
1st, did you flash the SU file? 2nd, what rom are you on?
Yes 5 times 2 im using dev digitals rom im on sprint
pbedard said:
Yes 5 times 2 im using dev digitals rom im on sprint
Click to expand...
Click to collapse
The latest SU File? which is SR3 2.79? if it didnt work try the Unsu.zip file to remove SU and then flash the SU file again. see if that works.
Devdigital help me thanks
pbedard said:
Devdigital help me thanks
Click to expand...
Click to collapse
did you flashed the unsu file then flashed the Su file?
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
pbedard said:
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
Click to expand...
Click to collapse
AAhh i see. Now i know where you are standing at. you are using magisk. But do you have magisksu ? or keep having supersu as main root but magisk installed? . What i mean to say is, when you go into the magisk app, in the 2nd box of the main screen, does it shows supersu as root method? or magisksu? if it is magisksu then you dont need supersu, now, if it does says supersu, then you do have to fix the issue of supersu to unroot by using supersu function and then go directly into recovery mode and flash magisksu once again.
It says majisksu
pbedard said:
It says majisksu
Click to expand...
Click to collapse
then you dont need su (unless you want it). It is because you already have magisksu (which is pretty much doing the same as su). one overrides the other and then one gets thrown out. Usually to install magisk manually, one does as follows:
1) install magisk app from playstore
2) give supersu access (granted to magisk su)
3) use unroot function in supersu
4) flash magisk zip in recovery mode.
Now, there are other methods to achieve magisksu but the point is that maisksu has changed the binary (which is what SuperSU is telling you that you dont have).But that doesnt mean you are not rooted. you are already rooted with magisk and can achieve pretty much anything that you could achieve with supersu. (it will ask you for prompts asking you whether you want to give su access to "x" or "y" app. etc... Now, if you want SuperSU, you could try to flash the magisk uninstaller. Then do the process of rooting that has been specified for your phone. That should return the SU binary to normality . (this assuming you try to unroot and then flash SU back but didnt work)
hey guys bought my ls997 used. has root because i get the flash screen (untrusted)and twrp is installed and working. how do i find out which to flash ? any advantages to use supersu over magisk ?
i installed magisk manager and it states no root found.
Majisk u have to turn root access on majisk works alot better
@pbedard
Did the help @jinkerz9430 gave work for you?
Yws
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2