Database Users

Rooting Stock XT1575 Marshmallow 6.0

This device seems to be a little trickier to root compared to my old Galaxy S3.
I just received a brand new Moto X Pure, XT1575 (North American variant I'm assuming since I bought it from the US).
It's currently running Marshmallow 6.0, and has been OTA updated to the Feburary 2016 security update.
I want to keep the stock ROM, but I want it to be rooted. XPosed would be nice as well, but not necessary. I do not want any custom ROMs, just the stock ROM rooted.

To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Fantastic advice!
Sent from my XT1575 using XDA-Developers mobile app

You'll have to use a very specific - older systemless root though. I think supersu-2.64, but I'll let someone else confirm that. The other superusers will not work.

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Sorry I been away from the rooting methods for too long (since my note 2) I already unlocked the bootloader on my phone but to install twrp can I still follow this tutorial? TIA
https://youtu.be/iPspDlbRf88
Sent from my XT1575 using XDA-Developers mobile app

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Thanks!!! that little line of code for TWRPs built-in terminal did the work

rmaspons said:
Thanks!!! that little line of code for TWRPs built-in terminal did the work
Click to expand...
Click to collapse
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu

martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.

martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
It didn't work for me via adb command.... Had to use TWRPs built-in terminal. Just wrote wrote the line, as it is, go back to the main menu and flash Supersu (I used the latest one: 2.67) just as you normally do. Then reboot. No more stock in the M logo

jason2678 said:
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.
Click to expand...
Click to collapse
Thanks! This did work for me. I am now rooted.

I am using twrp 3.0.0.0 I used 2.62 however when I tried to click the option in the terminal keyboard for the = (equal sign) I keep getting a blue screen. 3.0 keyboard works ok. I entered the, echo "SYSTEMLESS=true" > /data/.supersu and pressed the go button. It showed up on the main terminal screen. Im a bit confused at this point....do I flash supersu from my pc using flashboot on the bootloader page? or download the supersu.zip to my phone and use twrp to flash it? When twrp asked to flash supersu I did that and wound up stuck on the big M again. I think I restored my phone about 6 times so far. lol

Flash in recovery. Use 2.62-3.

So using 2.62.3 will void having to type SYSTEMLESS=true" > /data/.supersu. or do u still have to type that in terminal? Plus using the twrp-3.0.2-0-clark. Should I use and older version?

No just flash.

Flashed Supersu 2.76 on top of xt-1575 18-4 image without any problems usung TWRP 3.0.2.
I did add .supersu text file to /data just as an insurance.

Nuts. Didn't see the part about doing a backup first (hitting head, as this isn't my first rodeo). Too anxious I guess. Now I'm stuck at the M android screen. (didn't do the "SYSTEMLESS=true" > /data/.supersu" command). Any way to fix or am I just screwed?
I can get to TWRP, so theoretically, I could flash a stock version of Android back onto it. Anyone know where I can pick one up?

Did the same ****. Was so excited getting the phone and didn't read the systemless =true crap for M. Didn't do a back up but got a system file from Motorola. You can pick one up here to start over. http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

Anxiety might lead to unexpected results
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance

eat-man said:
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance
Click to expand...
Click to collapse
Not really sure what you need a video for, the process is simple and the same for all Gen3/4 Moto devices... the chanced of "breaking" something are near zero. You need fastboot working, that is on you.
1) Unlock the bootloader
2) Download the latest TWRP and SuperSU. Place TWRP img in your fastboot directory and SuperSU zip on your device so you know where it is, internal storage or SD card is not relevant.
3) Start the bootloader, either with `adb reboot bootloader` or power off and hold VOL DN and then press and hold POWER until the menu comes up
4) Start TWRP with `fastboot boot twrp-3.0.2-0-clark.img` and backup
5) Go to TWRP's Advanced menu and select Terminal
6) Enter `echo SYSTEMLESS=true>>/data/.supersu` press enter , exit, and Home button
7) Install (Flash) SuperSU ZIP file, clear caches if you wish but it isn't necessary.
8) Reboot
That is all there is too it

man u are awesome it took me a while and just stumbled on to this and u couldnt have made it less confusing

Moto X Pure and Magisk Support

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

super su

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

Magisk v11.6 compatible with Droid Turbo Stock ROM

I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Pics or it didn't happen

And last, but certainly not least...

So I can root without unlocking the bootloader using sunshine?

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.

Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.

Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.

TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.

Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.

More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU

y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.

TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?

y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.

It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^

Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).

.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.

I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.

Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?

Working BusyBox for Oreo

I did a semi search on how to get busybox working on Oreo, found chatter of using this app for busybox but for a different phone. I figured it wouldn't hurt to try. I needed BusyBox for Cerberus app to work and block the status bar access.
I downloaded this app https://play.google.com/store/apps/details?id=ru.meefik.busybox
Go to it's settings and change your install path *if your using supersu like I am path is:
/sbin
After you set your path, install. Then reboot.
After boot the BusyBox app used states that busybox wasn't installed but when I used a BusyBox checker app it's installed and working. My Cerberus app works too and blocks the status bar from locked screen. Busybox has been working after reboots. It sticks
Anyways, busybox is working on Oreo ver.11

Question: Now that you've installed that, can you still boot TWRP on your device and have it still ask to decrypt your file system? I've attempted 3 times with different types of busybox install locations, and each time I install it to anywhere in /system/, TWRP no longer prompts for the decryption key or password to access the file system.

ToolB0x said:
Question: Now that you've installed that, can you still boot TWRP on your device and have it still ask to decrypt your file system? I've attempted 3 times with different types of busybox install locations, and each time I install it to anywhere in /system/, TWRP no longer prompts for the decryption key or password to access the file system.
Click to expand...
Click to collapse
I boot to TWRP using fastboot boot TWRP.img it works for me. I still get the decryption prompt. I didn't install in system/
I installed in /sbin
Please look at pic

Rooted?
Sent from my Pixel XL using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
I mean do you have root after boot? What version of su are you using?
Sent from my Pixel XL using Tapatalk

Does this Busybox/method make V4A work on Oreo? Anyone with any success?

I think this is the best busybox. It does not break Root. Flash in recovery.

Tulsadiver said:
I think this is the best busybox. It does not break Root. Flash in recovery.
Click to expand...
Click to collapse
Full thread?

sliding_billy said:
Full thread?
Click to expand...
Click to collapse
This is where it came from but I wouldn't flash the latest. Stick with this one for now.
https://forum.xda-developers.com/and...archs-t3348543

Tulsadiver said:
This is where it came from but I wouldn't flash the latest. Stick with this one for now.
https://forum.xda-developers.com/and...archs-t3348543
Click to expand...
Click to collapse
That link doesn't work.

sliding_billy said:
That link doesn't work.
Click to expand...
Click to collapse
Try this one.
https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

That worked. Thanks.

Thanks, this thing worked, just make sure to mount system first before flashing=)

Stericson Busybox has been updated and is in the Play Store. Installs to the default location. All works after install and after reboot including root (I am using SuperSU 2.82 SR4), suhide and Adaway. Patience pays off in this case. I have always had the best luck with this dev's work.

sliding_billy said:
Stericson Busybox has been updated and is in the Play Store. Installs to the default location. All works after install and after reboot including root (I am using SuperSU 2.82 SR4), suhide and Adaway. Patience pays off in this case. I have always had the best luck with this dev's work.
Click to expand...
Click to collapse
Been waiting for this. Thanks for the update cuz it made my day... And if all my Fantasy teams and the Vikings win...that will really make my day. Lol
Sent from my Pixel XL using Tapatalk

I just updated to Stericson Busybox. I Installed to /sbin/supersu/xbin and all functioning as expected. Even after re-boot.

Deleted: nevermind, good to go now

Did this, lost root. Re-Flashing Su does not work (no root no su app) Cannot uninstall busybox due to lack of root.
Any suggestions on how to fix this?

I've had success installing busybox via the Magisk Manager as they have it as a module you can install. It was as easy as installing Magisk, choosing their BusyBox module, and restarting my phone. Now I can use Lucky Patcher / any other app that requires it without a problem, Systemless-ly rooted, no custom recovery or kernels.

Any update!??

Its called osm0sis BusyBox for ndk