Database Users

Guide: Setting up Android Pay on a rooted Note 5

***THIS GUIDE DOES NOT WORK. THIS SIMPLY ALLOWS CARDS TO BE ADDED TO ANDROID PAY. PAYMENTS WILL NOT PROCESS. THIS IS A WORK IN PROCESS.***
Unfortunately us rooted users are unable to use Samsung Pay. Samsung Pay is superior to Android Pay due to its MST feature which allows the use of any card reader to take payments from the phone. Samsung Pay as of this time doesn't support a lot of cards, So Android Pay is a great backup. Just as Samsung tries to stop rooted users from using Samsung Pay, Google tries to stop them as well by blocking Android Pay. This guide will show you how to get around that.
1.) You need a non rooted phone to start.
You can either flash your Note 5 completely back to stock, or use another phone to do it. Whichever phone you use MUST be able to be rooted or this will not work. This guide will assume you will use a second device to setup Android Pay, as I did, so that you don't have to wipe your Note. If you use your Note 5 to do this, just modify the guide as needed.
2.) Download the Android Pay app from the Playstore to your non-rooted phone
3.) Setup Android Pay application fully with all your bank cards and info
4.) Force close Android Pay app
5.) Root the device
6.) Install Titanium Backup
7.) Make a backup of the Android Pay app using Titanium Backup
8.) Move the Titanium Backup folder to either a computer or OTG drive
- If you only backed up Android Pay, there should be 3 files inside of the folder.
9.) Move your Titanium Backup folder to your rooted Note 5
10.) On the Note 5 download and install Titanium Backup
11.) Open Titanium Backup and select: menu - preferences - backup folder location
- Point the backup folder location to wherever you moved the Titanium backup folder to on the phone.
12.) Close and reopen Titanium Backup if it does not automatically do this when you exit settings
13.) Select menu again and then "batch actions"
14.) Select restore missing apps with data
- Android Pay should be the only app being restored
15.) After the app is restored, DO NOT OPEN IT.
16.) Open the superSU app and select: settings - "Enable Superuser" (uncheck the box) and let it finish
17.) Reboot
18.) When the phone boots up, open Android Pay and set it up as normal
19.) Open the superSU app and select: settings - "Enable Superuser" (check the box) and let it finish
20.) Reboot
21.) Done.

I do not think it'll work when making a purchase...
You can install "cigital safety net playground" from the play store to test if the state of your phone will allow it to pass Android Pay verification.
I my experience (I was using Android Pay on a rooted Moto X 2015), the only way to get Android pay to work with root, is to use Chainfire's systemless root and NOT to modify anything "major" in the system (host file and minor files edit are okay, replacing or adding a system app breaks it)

Hmm, the app says failed. I will test the pay function right now. I just need to run to the store.

seh6183 said:
Hmm, the app says failed. I will test the pay function right now. I just need to run to the store.
Click to expand...
Click to collapse
Yup... no surprises there.
Now try this:
- Back to stock, unlocked bootloader
- Install and setup your cards in Android pay
- Install TWRP or any custom recovery
- Try rooting with the latest systemless root (you may have to force a systemless install by typing "echo SYSTEMLESS=true>>/data/.supersu" on shell before install the zip in TWRP)
- Remove the folder "/su/xbin_bind" and reboot for Android pay compatibility
- Try "Cigital safety net playground" it should pass.

timeToy said:
Yup... no surprises there.
Now try this:
- Back to stock, unlocked bootloader
- Install and setup your cards in Android pay
- Install TWRP or any custom recovery
- Try rooting with the latest systemless root (you may have to force a systemless install by typing "echo SYSTEMLESS=true>>/data/.supersu" on shell before install the zip in TWRP)
- Try "Cigital safety net playground" it should pass.
Click to expand...
Click to collapse
Isn't systemless for android 6.0+ only and the kernel has to support it? I have it on my nexus but didn't think it was possible on the note.

seh6183 said:
Isn't systemless for android 6.0+ only and the kernel has to support it? I have it on my nexus but didn't think it was possible on the note.
Click to expand...
Click to collapse
From the man himself in the linked thread: "If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image (...)"

timeToy said:
From the man himself in the linked thread: "If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image (...)"
Click to expand...
Click to collapse
This is amazing news and will be implementing this immediately.

Yup it failed at the card swiper.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Booted to CWM and flashed "unsu.zip" which removed all superuser from the phone. Then flashed beta 2.61 because they say it's the last working version for Android Pay. I rebooted from CWM and chose not to install root. When it Booted the phone was not rooted. I don't have a folder in /data. Supersu says this when I open it:

Wiped everything and reflashed my rom and still doesn't work. I am getting this error in CWM after flashing the superSU zip:
- Extracting ramdisk
--- Failure, aborting
I'm going to Odin back to stock and try again.

seh6183 said:
Wiped everything and reflashed my rom and still doesn't work. I am getting this error in CWM after flashing the superSU zip:
- Extracting ramdisk
--- Failure, aborting
I'm going to Odin back to stock and try again.
Click to expand...
Click to collapse
About the ramdisk issue, make sure you have the stock kernel and use the latest version v2.65, it fixed a lot of compatibility issues. To enable Android pay compatibility on v2.65 you need to delete the folder "/su/xbin_bind" and reboot.
I am not yet able to test this (waiting for my Samsung promos to go trough before messing up with KNOX), but Chainfire's himself is reporting it working:
Chainfire said:
(...)It's working great on my Note5 (G920T) on OJ5 and S6 on OI9(...)
Click to expand...
Click to collapse

I got systemless root installed.
My kernel (Arter) wasn't compatible with the systemless flash and that was causing the error. Had to switch back to ext4 and flash a modified stock kernel to get it to work.
Now here's the problem. You can't flash a custom rom without a custom recovery and you can't boot with a custom recovery unless you have a modified kernel. So that means you need a kernel and recovery at minimum if you want a custom rom. Once you install those 3 android pay fails to work again.
The only way I can get it to work is totally stock. That's boring. I need at least a custom rom. I was thinking that maybe I can flash my rom, flash unsu.zip, my kernel, and then somehow Odin my stock recovery back. Then setup android pay, then reboot and go back to a custom recovery to flash root.
Thoughts?

Flashed stock recovery and rebooted. Android pay still didn't work. Rebooted and flashed stock kernel and now it hangs on the first splash screen lol
Back to the drawing board. Going to ODIN back to stock and try different kernels I guess.

seh6183 said:
(...)Now here's the problem. You can't flash a custom rom without a custom recovery and you can't boot with a custom recovery unless you have a modified kernel. So that means you need a kernel and recovery at minimum if you want a custom rom. Once you install those 3 android pay fails to work again. (...)
Click to expand...
Click to collapse
Android pay will ONLY work with a 99.9% stock system partition. (no custom ROM that I know of)
Maybe this can work:
- Back to 100% Stock
- Install custom kernel and custom recovery
- Reboot into recovery, then install stock Kernel, no reboot, then flash systemless root, no reboot, then flash back stock recovery, then reboot.
That should get you systemless root with Android pay. No ability for full ROMs but the ability to run an Ad Block and disable the bloat...

timeToy said:
Android pay will ONLY work with a 99.9% stock system partition. (no custom ROM that I know of)
Maybe this can work:
- Back to 100% Stock
- Install custom kernel and custom recovery
- Reboot into recovery, then install stock Kernel, no reboot, then flash systemless root, no reboot, then flash back stock recovery, then reboot.
That should get you systemless root with Android pay. No ability for full ROMs but the ability to run an Ad Block and disable the bloat...
Click to expand...
Click to collapse
My rom is a stock deodexed, debloated rom. I am trying something, well two things, that may get me working. Otherwise I am confident that I can get a stock rom, debloated myself, systemless root, custom kernel, xposed, and android pay all working. I can live with that. I will update my guide when I make it happen.
So far the things to remember is that systemless root needs a certain kernel format to be able to flash, and android pay needs certain things in the rom to be present or it wont work. I know the chroma rom for nexus devices has working android pay with systemless and its heavily modified. I doubt the dev will share how he did it though

Didn't work. Can't get any modified rom to work. I just booted two different roms with a stock kernel and stock recovery and it failed the safetynet check. Wiped all and am reflashing stock as I write this and will do it one step at a time to see what causes the safety check to fail.

Flashed a stock rom with ODIN and booted. It passed safety check. Flashed CWM recovery and it passed. As soon as I flashed a custom kernel it failed the check and I haven't even gotten to the rooting part yet. As of right now I don't want to give up a rom AND a kernel simply for android pay. I will be updating this guide to have the mods take it down.

Latest Xposed installed stock rom rooted. Couple questions about xposed.

I am rooted using the latest Su and i just installed xposed. Now I get some of the stock apps crashing and i have to reboot the device for them to work. I havent even downloaded or installed any modules. Is anyone else experiencing issues with the latest Xposed? Is it stable for you? Just want to know if its worth having it installed with it causing apps to crash.

have you tried setting selinux to permissive? i couldn't use it with enforcing without issues.

What ROM are you running? Did you do a clean wipe? Which xposed version you install?
I am currently running xTraFactory with xposed and its super smooth. I have some module install and haven't had a problem.
Follow this guide to install it properly
Xposed for Marshmallow
BTW don't install the module call swipeleft. That's particular one didn't work for me. Might be different for you but everything else is working

peconaut said:
What ROM are you running? Did you do a clean wipe? Which xposed version you install?
I am currently running xTraFactory with xposed and its super smooth. I have some module install and haven't had a problem.
Follow this guide to install it properly
Xposed for Marshmallow
BTW don't install the module call swipeleft. That's particular one didn't work for me. Might be different for you but everything else is working
Click to expand...
Click to collapse
I am on the stock rom 6.0.1... I unlocked the bootloader, installed twrp and su 2.66....I wiped davlik cache and cache in twrp then rebooted and it fixed it. But I uninstalled it after. I followed the directions in the link you provided. I was on v79

Well I am glad everything is working

From stock 4.4.3 to latest 5.0 (RU1.1.34) with Magisk v9 (xposed not yet working)

A short summary of upgrading my YotaPhone 2 to run Magisk v9 on the latest RU lollipop build (1.1.34) because I've seen no threads about Magisk here yet and writing my experience down might help others (or myself in the future).
Background: Got the phone last week from bestgear, and I'm surprised at how great it is. The EPD is much more responsive than I expected. And the phone looks just great! So much has changed/improved in the modding community in the last years (and I got out of touch with it), that I decided to go cutting edge with systemless Xposed through Magisk with root hiding, having no experience with either.
Lollipop
The phone had exactly the same about screen as in the lollipop upgrade thread so I sort-of followed that and subsequently went for the latest Russian version (RU1.1.134).
However, my setup prevented flashing directly to any of the 5.0 versions. The YotaPhoneFlasher showed that flashing /system failed (which can be seen by scrolling up on the prompt about flashing the user data). Probably due to the file size being too large. However, this procedure seemed to do the trick (see above thread for details):
Flash 5.0.0-RU1.1.124. Booting hangs at the 'Powered by Android' screen.
Flash 4.4.3-S01-003-RU1.0.3.61a. Booting succeeds.
Somehow, it now knows that it can perform an OTA update and proceeds through several versions to get to RU1.1.134
Not sure whether the RU version is worth it though, because it adds some bloatware like a Russian NFC payment app, a Russian air plane app and a dictionary app that primarily supports to/from Russian.
TWRP
Subsequently the recovery was flashed to TWRP 2.8.5.0. This seems a rather old version of TWRP though, perhaps too old to flash Magisk v9, see below. (This is my first TWRP experience as well, absolutely fabulous compared to older recoveries!)
Magisk
Magisk v9 refused to install directly. Flashing Magisk-v9.zip always ended up with either "E: footer is wrong" or "E:Error executing updater binary in zip". I tried to 'Install' from TWRP and to 'adb sideload' from both TWRP and modified stock recovery. Googling these errors lead me to believe that it might be related to the TWRP version. (The download was fine, because the zip file was exactly the same as the one that the Magisk Manager installed.)
In the end it was rather simple:
Flash Magisk-v8.zip
Install the magisk version of phh's superuser (and the corresponding Superuser app).
Install Magisk Manager
Upgrade Magisk to v9 from within the manager.
The "Emoji One" module proved that Magisk works (by replacing all the smilies). However, couldn't get Pokemon Go to login, so the root hiding might not work, but I didn't try PoGo before installing Magisk, so could be another issue.
Xposed
My actual goal was experimenting with Xposed, but the Xposed Installer keeps saying that the "Xposed Framework is installed, but not active." I'll keep you posted if I manage to get it working.
Some more notes:
A windows 10 laptop was used for all of the flashing (because the YotaPhoneFlasher software is windows only it seems).
Several reboots and cache/data wipings were omitted from the above. These did make the process take ages though, updating all the apps etc. all the time.
Thank you for all the information on this forum that let me get this far. I'm very happy with having a Lollipop YotaPhone with root.

Thank you for your detailed experience. I read the magisk thread here on XDA buy I didn't understand why is it for? And another question, why are you installing xposed? Are there benefits or special added features added to our Yotaphone?

I'm both new to Magisk and Xposed myself, and indeed it is not directly clear 'what these are for' from their xda posts. So I decided to just try them out and see for myself.
Xposed allows hundreds of modules to be installed to alter the OS in one way or the other. I'm most interested in Xprivacy, which should allow the user to limit what data / functionality apps can access and provides apps with mock data and such. Like a fine grained permission system I think.
Magisk also allows modules to alter the OS, but there seem to be only a handful, including Xposed. The selling point of Magisk is, if I understand correctly, that it does not alter the system partition. This makes it easy to apply future OTA updates etc. Supposedly it can also hide itself and root from certain apps.
It's not that important to me, so not sure whether I'll continue my exploration soon. (The Magisk threads are many, many pages, so it could take quite some research to get it to work properly.)

Did you get any further with Magisk & Xposed? My YD201 just arrived and I'm trying to decide how to proceed with hacking the crap out of it.

hippy dave said:
Did you get any further with Magisk & Xposed?
Click to expand...
Click to collapse
Not yet hippy dave. The Marshmallow beta came out soon after my initial experiments and I decided to wait for the official Marshmallow release before experimenting further. My concern was that I didn't want to redo the entire process every other week, and I messed something up so I can't boot to recovery...
The final Android 6.0 rom seems to take a while, so maybe it is worthwhile to continue with the latest beta. My plan is to first fix my recovery partition somehow, then upgrade to the latest Marshmallow beta, and then try Magisk again. I don't want to use the 'normal' system-partition-modifying Xposed because I like the cleanliness that Magisk promises. I haven't followed the Magisk development since, so maybe things have changed.
Your experiences would be welcome.

BlackShift said:
Your experiences would be welcome.
Click to expand...
Click to collapse
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc, so I tried Magisk out on the latest Russian LP. First I tried the latest release of Magisk 11.x, and then the latest unofficial source build 12.x, and tho it installed (with TWRP 3 latest version) and worked fine in terms of root, I couldn't get Magisk Hide to work and pass SafetyNet. Tried all the tips I could find like turning off USB debugging, turning things off & on in Magisk in a particular order with reboots in between etc. So I gave up for now and didn't get as far as trying Xposed for Magisk or any other modules.
For the time being I decided to go with the tried and tested stuff, standard root and regular Xposed, and will reevaluate when Marshmallow gets an official release or if I hear of improvements to Magisk Hide.

hippy dave said:
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc
Click to expand...
Click to collapse
The official MM came out a couple of days ago, but so far, no more success than you got.
Updated to MM. Forgot how, it refused to update over the air, so think I adb sideloaded the full 1.34 OTA with TWRP. Safetynet check from Magisk manager successful (of course).
Installed TWRP 3.0 and the official Magisk 12. However, the Magisk root seemed to have failed, also after a reboot. Safetynet check failed.
Installed SuperSU systemless by typing echo SYSTEMLESS=true>>/data/.supersu in the TWRP command prompt because SuperSU failed to install systemless automatically. Magisk Hide claims it doesn't operate that well with SuperSU, and safetynet check failed.
So Magisk and root access works, but not root hiding. Which kinda defeats the point of using Magisk. I didn't try many of the clever tricks you refer to though and I gave up for now. It is supposedly cleaner than other methods of rooting, so I'll keep it anyway. Next up is
(Not really relevant to this thread.) Getting 800Mhz band to work
Getting XPosed installed systemless.
Perhaps send a boot image to the Magisk team so they can improve the support for our yotaphones? Not sure how this process works.

Hi, has there been any more progress with Magisk and Yotaphone? My bank finally started using Android Pay, so I'm keen to have another crack at hiding root. I don't think there have been any changes to Yotaphone firmware since you last posted, but I don't know what progression there's been with Magisk. Maybe when I have the chance I'll try to send the Magisk people whatever they need to try and get it working.

I haven't made any attempts since last time and probably won't soon. Let us know if you are successful.

Ok I did a fresh install of the latest Russian MM (kept my data tho), installed the current Magisk release version (14.0), and it just worked straight off, Android Pay is running happily and root is working in the few root apps I've tried so far. Only downside so far is no Xposed, there's an unofficial Xposed for Magisk but it doesn't pass Safety Net so would presumably break Android Pay. I'm gonna see what Magisk modules are available and if they can fill the void, and decide from there I guess.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.

hippy dave said:
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.
Click to expand...
Click to collapse
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk

stanley321 said:
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Sure thing, I'll attach it to this post. You might know that you have to fix the file contexts when you replace the original library with the patched one - I'd boot into TWRP and use adb push to put the file into place, then adb shell and use the following command in the right directory:
chcon --reference=libandroid.so libandroid_runtime.so

[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
It should work when you flash it, but using it is still a try at your own risk procedure.
Our device comes with forced encryption and, more important,
verity which checks at every boot if /system partition has been changed or not.
If /system has been changed, verity won't allow booting your device which means
you can't flash anything unless you disable verity.
So, you must be sure to keep /system in ReadOnly mode in TWRP and don't try to alter it unless you're using a custom Kernel/boot to disable verity.
Of course, custom ROMs come with custom boot, so no worries about verity security with Lineage or AOKP for example.
Click to expand...
Click to collapse
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on moto.shreps.fr.
Changelog:
twrp-3.0.3-n2-athene_shreps.img
- Kernel and boot update - should be compatible with more variant
- Some TWRP fixes
twrp-3.0.3-n1-athene_shreps.img
- Qseecom and crypto stuff updated to N
> I'm able to decrypt my /data partition (F2FS) - Tested on XT1650-03_NPL25.86-17-3
- Fully rebased on AOSP Recovery 7.1
- TWRP bump to 3.0.3, with a lot of fixes
- Dark Material Theme
- Removed cursor pointer
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z, Tool/Utility for the Moto Z
Contributors
Shreps
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2017-01-30
Last Updated 2017-03-07

[ROOT] How to root with latest N firmware NPL25.86-17-3
Simple procedure:
Unlock your BL
Flash this TWRP Recovery
Download the superuser zip (thanks to phh)
Flash it through TWRP
Reboot
Install phh's SuperUser app from play store
Enjoy

Shreps said:
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
Click to expand...
Click to collapse
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again

erfanoabdi said:
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again
Click to expand...
Click to collapse
Use superuser systemless root, has mentionned in post #2. It's safer.

Shreps said:
Use superuser systemless root, has mentionned in post #2. It's safer.
Click to expand...
Click to collapse
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser

erfanoabdi said:
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser
Click to expand...
Click to collapse
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser

[email protected] said:
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser
Click to expand...
Click to collapse
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser

erfanoabdi said:
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser
Click to expand...
Click to collapse
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2

Shreps said:
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2
Click to expand...
Click to collapse
Currently I'm using phh without any issue but FlashFire doesn't work with this, it requires SuperSU

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP

erfanoabdi said:
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP
Click to expand...
Click to collapse
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA

kethsawant said:
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA
Click to expand...
Click to collapse
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
I tried that in Stock rom but ended up in bootloop..

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)

kethsawant said:
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)
Click to expand...
Click to collapse
OK use my TWRP and flash this super su
This is not modded version just old version of stock superSU
Please test it and tell how is it.

Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.

paulnorinn said:
Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.
Click to expand...
Click to collapse
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.

Shreps said:
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.
Click to expand...
Click to collapse
Ok, thats fix it. I can now touch the screen. Guess I have to do it on every boot?
Thanks for the tip.

OK I formatted my partitions in twrp and it was formatted as ext4. I read somewhere that the moto Z uses f2fs by default. Is this true and I just reduced performance of my phone because of a bug in twrp? I couldn't find an option to format as f2fs.

[Finally SOLVED] [Reverted back to supersu] Problem with magisk

Final Edit: I reverted back to supersu. Magisk still had issues with remembering which apps already had requested root after each reboot. After so many attempts to get everything working i got tired and rolled back to using supersu.
Edit:My mistake. It turns out my data partition was f2fs instead of ext4 the whole time (checked with the app diskinfo). Now my problem is fixed. I flashed the f2fs loopback bug workaround module through twrp and now magisk works as it should. I'm sorry for the inconvenience
OK. so i keep getting into more and more issues with magisk. so i decided to overhaul this thread completely (no replies so far except my own so i think its unnecessary to open up a new one)
just switched to latest stock rom through clean flash (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module (or any other one) fails to install in magisk (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After googling about the issue i saw that many ppl say it has to do with f2fs loopback which doesnt really help since my phone is using ext4
I also tried flashing the module in twrp. it flashed successfully but doesnt show up in magisk
And for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement (and yes i checked. those apps are really uninstalled and frozen)
Edit: just tried to install busybox module through magisk. it flashed successfully but after reboot its gone

Edited op. Forgot to mention that the bootloader is unlocked and i have twrp (duh xD)
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs

Edit: completely changed topic and thread to the current issue. since i was the only one so far to reply i thought opening a new thread again was unnecessary as i just opened this thread yesterday

Issues seem similar to what someone else has/had in another unrelated thread (Moto with permissions problem). Was also going to mention that it was probably f2fs related until you mentioned you're using ext4. Hmm.
Could you try the busybox zip instead via recovery. Both the module and zip are from the same dev. The zip will detect Magisk and install as a module. If/when it fails you can save a recovery log that might have more details on what happens.
See this conversation starting with I think the following post. Maybe it gives some ideas.
http://forum.xda-developers.com/showthread.php?p=76451850
Also, the busybox zip is in the OP of that thread.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3

GodOfPsychos said:
EDIT:My mistake. It turns out my data partition was f2fs instead of ext4 the whole time (checked with the app diskinfo). Now my problem is fixed. I flashed the f2fs loopback bug workaround module through twrp and now magisk works as it should. I'm sorry for the inconvenience
OK. so i keep getting into more and more issues with magisk. so i decided to overhaul this thread completely (no replies so far except my own so i think its unnecessary to open up a new one)
just switched to latest stock rom through clean flash (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module (or any other one) fails to install in magisk (see screenshot)
View attachment 4496088
After googling about the issue i saw that many ppl say it has to do with f2fs loopback which doesnt really help since my phone is using ext4
I also tried flashing the module in twrp. it flashed successfully but doesnt show up in magisk
And for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement (and yes i checked. those apps are really uninstalled and frozen)
Edit: just tried to install busybox module through magisk. it flashed successfully but after reboot its gone
Click to expand...
Click to collapse
edit: problem solved by flashing latest f2fs loopback module

Final Edit: i reverted back to using supersu because of too many issues with magisk

What was the other issue?

bluenote73 said:
What was the other issue?
Click to expand...
Click to collapse
It's in the top of OP.
Remember that this all was happening to me on stock 1.2.0 B10.
It might work much better in custom roms as Resurrection remix or AOSP extended etc

Magisk works fine for me. 16.4