Database Develop

[Guide] Oneplus 3 Magisk Install (Android pay W/ Root and Xposed)

Okay so basically. topjohnwu has released another marvelous mod that allows you to use android pay with xposed and root by unmounting root.
ALL CREDITS GO TO HIM : http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 (buy him a beer)
I'm making this guide just for oneplus 3 users, some people might be scared of breaking there device or maybe couldn't understand the instructions too clearly. As I don't want to be held accountable, I am not responsible for anything that happens to you while following this guide.
EDIT: You can find your boot.img just by extracting your rom or opening it with some type of archiving program such as Winrar or 7-zip
IF YOU ARE ON V3 or lower please use the uninstaller first before upgrading. LINK HERE IF YOU NEED IT
(Then follow the same steps)
Update : Topjohnwu has updated most of the API ( I will post a tasker script when I test it a bit more) . Also Magisk is now a seperate apk signed by him.
Requirements :
100% stock system + boot (This is recommended, I simply just flashed boot.img and uninstalled supersu and xposed). I am on 3.2.2
Remove supersu and xposed (If you're not going to be completely go stock.
Downloads : (Things you're going to need)
Magisk v6 : Link Please go to the original thread and make sure it's the latest one
Magisk Compatible phh's SuperUser v17: Link
V1.2 Magisk ManagerNeeded for toggling
You're also going to have to download the manager for it : (Here)
These are the steps I took thus me creating the guide
Steps :
Step 1 : If you aren't completely stock go ahead and flash boot.img. Here's the link to the boot img from OOS 3.2.2 (Click)
-So to flash a boot img all you have to do is use adb and run the command
Code:
fastboot flash boot boot.img
then
Code:
fastboot reboot
Step 2 : When you flash the boot.img, you're going to have to flash TWRP after that as it'll be gone.
Step 3 : Flash the Magisk zip
Step 4 : Flash phh's SuperUser Zip (reboot the phone and make sure everything is still working) and then download the root manager from the playstore. You can test by opening up Magisk and toggle "Root Mount Toggle" and try to add a card in android pay
Step 5 : Install Systemless xposed (I'll give a step by step underneath here)
Download and install Material Design Xposed Installer (Here)
You can open up Material Design Xposed Installer then click "Systemless" tab and click install/update (make sure it says sdk23), This didn't work for me so if it does not work download the latest one :HERE
Profit!?
If you guys want any explanation or help, post here and i'll help you out . You can also donate to me here CLICK HERE (Hint : It's not my donation link)
Also mods, if this is somehow against the rules, feel free to delete this. I just want to help out some fellow users.

Wonderful guide. Got Android Pay working this way.
At the time of writing this, I think the reason step 5.2 doesn't work on Material Design Xposed Installer was partly because xposed 86.2 was the highest version available for me. In order for Magisk to work, you'll need xposed 86.3 which is provided by the OP.
Well done!

First off, great guide. I'd like some information if that is okay.
So according to the original thread this doesn't enable the option to use CM 13 and still have Android Pay, no custom roms. Is that correct? If so, what is the actual use? Because Android Pay works on stock, so why root if you can't change a rom?

Just one information: on phh' site there are 3 different superuser zips :
[ ] superuser-r170.zip 2016-01-31 22:25 3.7M
[ ] superuser-r197.zip 2016-04-12 13:29 3.6M
[ ] superuser.zip 2016-01-31 22:25 3.7M
Which one i have to flash? I thought the latest one (197) should be fine.
Thank you in advance.

Pengod said:
First off, great guide. I'd like some information if that is okay.
So according to the original thread this doesn't enable the option to use CM 13 and still have Android Pay, no custom roms. Is that correct? If so, what is the actual use? Because Android Pay works on stock, so why root if you can't change a rom?
Click to expand...
Click to collapse
Okay, this is a hard question to answer but it should work on an official release of cm 13. Not a nightly, as those aren't CTS run. I will try and get it running on my Oneplus one. The only thing though is if you do decide to go for it. CM comes pre-rooted so you might have to find a way to delete it from the system.
However, you can still flash this and test it, if it doesn't work then just report back and i'll try and come up with something should it be in my power . Always make a backup though through TWRP .

wolfrules said:
Just one information: on phh' site there are 3 different superuser zips :
[ ] superuser-r170.zip 2016-01-31 22:25 3.7M
[ ] superuser-r197.zip 2016-04-12 13:29 3.6M
[ ] superuser.zip 2016-01-31 22:25 3.7M
Which one i have to flash? I thought the latest one (197) should be fine.
Thank you in advance.
Click to expand...
Click to collapse
Download the one from the link I put in my post. It has a couple of changes in it. It also includes
Code:
"# phh's open source root for Magisk
# by topjohnwu
#"
In it's update-binary.

katsumex said:
Download the one from the link I put in my post. It has a couple of changes in it. It also includes
Code:
"# phh's open source root for Magisk
# by topjohnwu
#"
In it's update-binary.
Click to expand...
Click to collapse
Thank you very much,great work.

Will this mod help you pass the safetynet test?
And by flashing the boot.img will you wipe your apps/data?

SysAdmNj said:
Will this mod help you pass the safetynet test?
And by flashing the boot.img will you wipe your apps/data?
Click to expand...
Click to collapse
Yes , it'll unmount the whole root and pass the safetynet till you remount it.
No it will not wipe all your data. It'll only wipe your recovery and possible your root.

Question.. does root mount need to be toggled to ON for adaway to work? if so, with that being ON will you be able to use android pay at stores (understood that credit card will be added after toggling root to off).. I guess I am asking what to do after you successfully add a card to android pay. Can the toggle be changed to mount root and still have android pay work in stores?

Wonder if there is a way to control this via Tasker?

androidbuff123 said:
Question.. does root mount need to be toggled to ON for adaway to work? if so, with that being ON will you be able to use android pay at stores (understood that credit card will be added after toggling root to off).. I guess I am asking what to do after you successfully add a card to android pay. Can the toggle be changed to mount root and still have android pay work in stores?
Click to expand...
Click to collapse
Whenever you want to use it, you have to toggle it.

dustintinsley said:
Wonder if there is a way to control this via Tasker?
Click to expand...
Click to collapse
Not yet. I made a request so let's see if he'll add some functionality

I had mount root set to on and I was able to withdraw cash from a bank of America ATM. One possible reason why that worked could be because for ATM use all it takes from android pay is the card information. You do have to input the pin after.
Sent from my ONEPLUS A3000 using Tapatalk

androidbuff123 said:
I had mount root set to on and I was able to withdraw cash from a bank of America ATM. One possible reason why that worked could be because for ATM use all it takes from android pay is the card information. You do have to input the pin after.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Very interesting, maybe it'll work for one boot cycle. I restarted my phone and had to toggle it to bypass pay again.

Works perfectly! Now I can use my banking app in New Zealand (ASB)

What about custom kernel user ?

otonieru said:
What about custom kernel user ?
Click to expand...
Click to collapse
It works with everything. It's just you won't get Android Pay on non-stock phone.
I personally use this on RR with ElementalX 'cause I don't care for Pay at all.

Personal tested Android Pay with 2 purchase and all work.
Unlike chainfire systemless root method, systemless phh's SuperUser work without disabling Xposed.. Plus, no reboot is required.. Using Oneplus 3 stock rom.

ThomasC1970 said:
Personal tested Android Pay with 2 purchase and all work.
Unlike chainfire systemless root method, systemless phh's SuperUser work without disabling Xposed.. Plus, no reboot is required.. Using Oneplus 3 stock rom.
Click to expand...
Click to collapse
How does Magisk compare to SuperSU? Is everything the same "on the outside" (user experience, etc).

[ROM]Multi-Rom Tripl3t B594 Odex

http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2 + John Miller . The Lineage part is @XePeleato and the Aosp of @haky86.
Too much for you?
More novice users should not be scared because the installation and configuration is incremental and that is why I say that it fits any user profile.
User Profiles:
Depending on the concerns that are most suited to your profile you should take the installation to the point that best meets your needs.
As a user I want ...
1- I want a stock experience with some extras but without Root.
You must install the rom file by TWRP and dot. The rom is the same as the cerberus V2 but comes with no root.
It incorporates among others ..., gyroscope, call recording, multiwindow ...
REQUIRED REQUIREMENTS:
-Bootloader Unlocked.
-TWRP
- Android 6 - C432B594 Stock - Recommended.
2- I want you to have root access too.
After installing the rom you must enter the store and download the application magisk manager and ready. You already have root access and get the most out of the rom, but not only that, but root access can be hidden to play PoGo or use payment applications and pass the SafetyNet test.
3- I want to activate extra functions and transform and customize the rom butt.
Well what you have to do is install this file from TWRP point.
We will achieve the following:
- Activate Multiuser
- Enable Local Update
- You can choose whether to install the Huawei magnifier or not
- Busybox, Viper4Android and SLC disappear
- You can choose to install the busybox and the viper in a systemless way and in this way the SLC is no longer necessary
- Advanced Reset
- New lock screen 100% customizable.
- The screen automatically turns on and off when opening and closing the mobile phone case
- Incorporates system apps uninstaller
- Total Commander
- Greenify
- Etc...
4- I want to be able to choose which rom to start the smartphone.
For that it is necessary to have followed steps 1, 2 and 3 and it is necessary to configure magisk to have default access to all requests per adb and applications and install the multiboot option.
To install Dualboot you must go to the file EXTRAS.ZIP that you will find inside the system folder of the rom. Uncompress your content in the external memory and install the DualBoot app and keep the files in memory because we will need them for later.
Then we start the dualboot application to be granted superuser permissions automatically. Then with SimpleReboot we restart a recovery and make a backup of boot.img in case something goes wrong, since it will be the only thing we will need to repair a possible failure or error.
VERY IMPORTANT: We need to have 3Gb of available space in the External SD for each additional rom we want to install, that is, if we are going to install Lineage and Aosp we will need 6Gb of available space.
4.1- I want AOSP.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.1- I want LineageOS.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.3 I want the 3 Roms at a time.
Then follow steps 4.1 and 4.2
Restarting the system will take us directly to the last ROM installed. Once started and configured we installed the dualboot app that we had left on hand in the external SD. Repeat the operation on each of the additional roms installed. Once installed dualboot in all you can remove the app from the sd and of course all the corresponding installation files.
To change rom you have to enter the dualboot app and choose which one to start the system and restart.
MENTAL NOTE 01:
The 3 roms will have the same bugs as the originals. I am not yet qualified to fix them or even try, but I think that to be my first job is more than enough.
MENTAL NOTE 02:
The DualBoot application also installs an app called Leaks that controls possible bugs to send them to the original DualBoot developer.
I do not want to forget to give credits and thanks for:
@topjohnwu for creating magisk
@chenxiaolong for creating DualBoot and @BrainNotFound for portarlo
+ John Miller to create CerberusV2
@haky86 for creating Aosp and CWMR
@XePeleato for creating LineageOs and TWRP and Kernel
Greetings from Barcelona (Catalonia)

Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Please delete, XDA app crashed while writing

Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Link please :laugh::laugh::good::good:

kilroystyx said:
Link please :laugh::laugh::good::good:
Click to expand...
Click to collapse
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1

Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Click to expand...
Click to collapse
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor

hi6120sft ale-l21 said:
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
Click to expand...
Click to collapse
Because it is cool, no more reasons sorry

I stucked on a first logo

blewko said:
I stucked on a first logo
Click to expand...
Click to collapse
Try a factory reset with stock recovery and flash again.
It helps in most cases

Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.

arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
he should work... i have magisk and xposed but on C432B596 ROM

arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
xander33 said:
he should work... i have magisk and xposed but on C432B596 ROM
Click to expand...
Click to collapse
Are you passing Safety net?

arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It works. Flash Xposed and don't forget to wipe cache.
Phone will start in about 30 minutes.
It works. Use SDK 23 for this rom

Vinnipinni said:
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
Are you passing Safety net?
Click to expand...
Click to collapse
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok

xander33 said:
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
Click to expand...
Click to collapse
I can confirm Xposed works. Not the Magisk one though.
Use the one from the mega root thread https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994.
I also know the xposed torch works. Like to recommend xEmui module.

future of SuperSU vs. Magisk

The guy who made SuperSU, @ChainfireXDA , retired from SuperSU. 2.82 SR5 was his last beta release. Some Chinese owned company named CCMT bought SuperSU a while back, but @ChainfireXDA retired from the aforementioned on 03OCT2017 (10th anniversary). https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ
https://desktop.firmware.mobi
https://www.chainfire.eu
SuperSU at XDA
https://forum.xda-developers.com/apps/supersu
So, since nothing has yet been posted by CCMT for SuperSU (as of 14NOV2017), it seems that @topjohnwu Magisk will become more prominent.
Magisk at XDA
https://forum.xda-developers.com/apps/magisk

The purpose of this thread was what exactly?

choosing rooting app for OEM unlocked Moto Z2 Force
TheKnux said:
The purpose of this thread was what exactly?
Click to expand...
Click to collapse
Since Moto Z2 Force Sprint and T-Mobile variants are OEM unlockable, the long term choice of a systemless root for an OEM unlocked Moto Z2 Force seems to be a relevant topic for discussion and/or news for Moto Z2 Force. I wanted SuperSU to be developed further by @ChainfireXDA , but his retirement from SuperSU likely means that to get the most up-to-date systemless rooting app for my OEM unlocked Moto Z2 Force, I will have to soon switch to @topjohnwu Magisk.

The point of this thread was that we had to work extra hard for magisk support and we now have it via mine and @Uzephi kernel we have figured out why there are bootloops and will be adressing here shortly

On OEM unlocked T-Mobile Moto Z2 Force with latest TWRP (as of 15NOV2017), I just switched to Magisk 14.3 beta from SuperSU 2.82 SR5 beta w/SU Hide 1.09. In this long process, I lost all my data because Magisk 14.3 beta did not properly disable force encryption! I really didn't think it was going to be as hard as it was. It absolutely refused to boot properly with default upstream kernel (i.e., that comes along with latest TWRP; kernel probably soon to be tweaked per previous post) and latest Magisk 14.3 beta no matter how many times I formatted data, etc. I ended up having to use SuperR's Kitchen free for Linux.
SuperR's Kitchen free for Linux
https://forum.xda-developers.com/apps/superr-kitchen/kitchen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
SuperR's Kitchen donate version for Windows/Linux
https://forum.xda-developers.com/apps/superr-kitchen/windows-linux-superr-s-kitchen-v3-0-0-0-t3601702

jhofseth said:
On OEM unlocked T-Mobile Moto Z2 Force with latest TWRP (as of 15NOV2017), I just switched to Magisk 14.3 beta from SuperSU 2.82 SR5 beta w/SU Hide 1.09. In this long process, I lost all my data because Magisk 14.3 beta did not properly disable force encryption! I really didn't think it was going to be as hard as it was. It absolutely refused to boot properly with default upstream kernel (i.e., that comes along with latest TWRP; kernel probably soon to be tweaked per previous post) and latest Magisk 14.3 beta no matter how many times I formatted data, etc. I ended up having to use T-Mobile 05AUG2017 kernel, no-verity-opt-encrypt-5.2 (attached), and Android Terminal TWRP Installer. But the important thing is Magisk 14.3 beta is finally working with latest Moto Z2 Force TWRP!
Click to expand...
Click to collapse
Interesting experiment... two questions:
1. have you tried using flashable zip to unforce encryption for "any kernel" by @erfanoabdi on our device?
2. since latest TWRPs by @joemossjr come with a (little) modified/recompiled kernel, why don't disable forced encryption by default on them?

enetec said:
Interesting experiment... two questions:
1. have you tried using flashable zip to unforce encryption for "any kernel" by @erfanoabdi on our device?
2. since latest TWRPs by @joemossjr come with a (little) modified/recompiled kernel, why don't disable forced encryption by default on them?
Click to expand...
Click to collapse
i didn't read thread and other posts but please don't install my zip here
that will harm the device in worst way
1) Z2 have a/b boot partition
2) different fstab and partition table
@enetec remove my flashable zip from your old post

erfanoabdi said:
...
@enetec remove my flashable zip from your old post
Click to expand...
Click to collapse
:good:
P. S. : Welcome back pal!
P. P. S. : we *want* you on Z2!!!

re-encrypting not due to upstream kernel with TWRP
enetec said:
Interesting experiment... two questions:. ....
2. since latest TWRPs by @joemossjr come with a (little) modified/recompiled kernel, why don't disable forced encryption by default on them?
Click to expand...
Click to collapse
The re-encrypting was not the fault of the upstream kernel with TWRP, it was that the 14.3 beta Magisk didn't properly disable force encryption in a stock boot image. It errored & told me to use a stock boot image during Magisk direct install (i.e., inside Magisk manager), so I dd flashed a stock boot image and FlashFire flashed Magisk right afterward. Yeah.....force encryption fun! Eventually, I ended up having to use SuperR's Kitchen free for Linux. All's well that ends well.
SuperR's Kitchen free for Linux
https://forum.xda-developers.com/apps/superr-kitchen/kitchen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
SuperR's Kitchen donate version for Windows/Linux
https://forum.xda-developers.com/apps/superr-kitchen/windows-linux-superr-s-kitchen-v3-0-0-0-t3601702

jhofseth said:
The re-encrypting was not the fault of the upstream kernel with TWRP
Click to expand...
Click to collapse
Never intended that... I was only asking why don't include directly in modified kernel the possibility to remain unencrypted...

enetec said:
Never intended that... I was only asking why don't include directly in modified kernel the possibility to remain unencrypted...
Click to expand...
Click to collapse
I think @joemossjr and @Uzephi try, but this encryption can be frustrating. Many techniques that are supposed to stop it don't work properly. Somehow SuperSU 2.82 beta SR5 does a good job of stopping it when installed systemlessly. No version of Magisk that I've tested stops encryption on our phone--even though it is supposed to stop force encryption by default.

jhofseth said:
I think @joemossjr and @Uzephi try, but this encryption can be frustrating. Many techniques that are supposed to stop it don't work properly. Somehow SuperSU 2.82 beta SR5 does a good job of stopping it when installed systemlessly. No version of Magisk that I've tested stops encryption on our phone--even though it is supposed to stop force encryption by default.
Click to expand...
Click to collapse
user data is formatted f2fs and system/boot/etc ext4. SU decrypts both while magisk sees f2fs and decrypts only f2fs partitions.

Flashable unencrypter must format data will not work on stock kernel. But will with twrp.
https://drive.google.com/file/d/1Cr-7SiSiHpUDM9HYpyeXVsPHEB9Z9wym/view?usp=drivesdk

enetec said:
Never intended that... I was only asking why don't include directly in modified kernel the possibility to remain unencrypted...
Click to expand...
Click to collapse
the "encrypt" part is in /system, not kernel. I can add a module when I build with anykernel to do the same thing as joemoss's zip. But it isn't the kernel. The kernel will work both encrypted and decrypted.

Uzephi said:
the "encrypt" part is in /system, not kernel. I can add a module when I build with anykernel to do the same thing as joemoss's zip. But it isn't the kernel. The kernel will work both encrypted and decrypted.
Click to expand...
Click to collapse
I could be wrong, but I have maturated the idea that disabling force encryption is one of (many...) things which can be done both working on /boot or /system....
I had posted @erfanoabdi script for Moto Z (Griffin) even to have it studied for an eventual porting... (I'm quite sure it works on /boot... )
More... I think even SuperSU method could work on /boot: if it worked modifying /system, a kernel reflashing shoudn't disable it's tweak... am I wrong?

enetec said:
I could be wrong, but I have maturated the idea that disabling force encryption is one of (many...) things which can be done both working on /boot or /system....
I had posted @erfanoabdi script for Moto Z (Griffin) even to have it studied for an eventual porting... (I'm quite sure it works on /boot... )
More... I think even SuperSU method could work on /boot: if it worked modifying /system, a kernel reflashing shoudn't disable it's tweak... am I wrong?
Click to expand...
Click to collapse
AnyKernel pulls apart the boot image and injects the kernel. it doesn't put the image back correctly. to try this, dd pull your boot image and play with AIK (linux solution to manually add a kernel). Don't edit anything and it will lose root as well when you reflash the repacked boot image. it is something in the ramdisk that doesn't get saved.

Uzephi said:
AnyKernel pulls apart the boot image and injects the kernel. it doesn't put the image back correctly. to try this, dd pull your boot image and play with AIK (linux solution to manually add a kernel). Don't edit anything and it will lose root as well when you reflash the repacked boot image. it is something in the ramdisk that doesn't get saved.
Click to expand...
Click to collapse
Understood. But @ChainfireXDA should have found a solution to this... or not?

enetec said:
Understood. But @ChainfireXDA should have found a solution to this... or not?
Click to expand...
Click to collapse
How can he? he doesn't have the device to test this out. He just patches the boot image the normal way like other devices. (albeit it took some community testing to get the boot image and ramdisk to work for our device, but hey, you get what you can when the dev doesn't have your device)

enetec said:
Understood. But @ChainfireXDA should have found a solution to this... or not?
Click to expand...
Click to collapse
@Uzephi wrote, "data is formatted f2fs and system/boot/etc ext4. SU decrypts both while magisk sees f2fs and decrypts only f2fs partitions."
So, I think that's why when we formatted data ext4 in TWRP, SuperSU 2.82 beta SR5 was OK but not so for Magisk.

Ok what uzephi is trying to say is encryption in handled in our fstab.qcom. which if you have a stock kernel it's gonna be in there and one's gonna be in system and another in system_root. So in the fstab there is this line for userdata which isn't used as you can see the # means it's not used. When magisk sees this because it's right above our userdata it modifies the "forceencrypt" part to "encryptable" which allows decryption on the f2fs partition but we don't use that. Follow me? Now below that one is ours. And where you see the term "fileencryption" that's just another term for force encrypt. So when magisk is flashed it only sees the one above it and changes it and goes on. Now the difference between magisk and supersu is supersu looks for terms like "verify" for dm verity and "forceencrypt" for encryption and also "fileencryption" and removed the verify term to remove verity and changes all the above terms if noticed to "encryptable" instead of going line by line supersu does it better. Now if you have twrp it has a fstab in it that patched already but what I forgot to check is where twrp puts it and where it puts it is n in the root of our device where it doesn't belong. So that's why I made a flashable zip that sends that modified fstab to system where when the system boots it will see the new modified fstab and realize that it can boots.
#/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,forceencrypt=/dev/block/bootdevice/by-name/metadata
/dev/block/bootdevice/by-name/userdata /data ext4 nobarrier,noatime,nosuid,nodev,discard,data=ordered,noauto_da_alloc wait,check,formattable,fileencryption=ice

[CLOSED][DEV] Magisk Canary Channel - Bleeding Edge Builds

Canary Magisk Manager: Link
Canary Magisk Manager (Debug): Link
Latest Release Notes: Link
All Canary Files: Link​
The Canary Builds are similar to Google Chrome's: bleeding edge of the source.
Be warned: Canary can be unstable.
The binaries from debug channel are built with debug flag ON
Install Canary Magisk Manager and go to Settings > Update Channel and switch to either Canary or Canary (Debug)
If you need a clean start, download the Canary Uninstaller to uninstall any version of Magisk
How to Report:
Only report bugs/logs using the debug channel!!
Magisk installation failure:
In TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
In MagiskManager: Choose to save logs after installation and upload
Magisk bugs:
Magisk logs are placed in /cache/magisk.log (For A/B devices, they are actually in /data/cache/magisk.log)
If you cannot boot or stuck in bootloops, grab logcats (and kernel dmesg if possible) on boot
Magisk Manager bugs:
Grab logcat (NOT magisk logs) when the crash occurs, upload the logs and report how to reproduce
SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
Ignored

I just installed this on one of my Nextbook Ares 8A's, x86, Android 6.0.1. It was previously on @ianmacd 's unofficial build. So far, it appears to be working great. I un-installed my previous MM, before I install the new one, downloaded the Magisk.zip in MM and flashed it through TWRP.
How much overhead does the extra logging create? I don't notice any difference. Do you think it will affect battery life?
When I check the magisk.log it does appear that it is continuously logging, because each time I check it the time stamp is updated.
If I am not mistaken, on non debug builds the magisk.log is only created at boot and not updated again until next boot?
Thanks, @topjohnwu for creating this new channel for testers.

Wew, downloading and testing on my 7.1.2, so far so good. Thanks.

Aye official snapshots! Awesome. Been using @kantjers up until now. Thanks for this
Sent from my LG Nexus 5X using XDA Labs

Testing now. Thanks ?
No issues with any of my used modules ?

When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.

jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
Yes, I think Magisk Manager should ask for the storage permission on first launch and not later when the actual storage permission is need. I have been bit by the storage permission a few time in other instances of using MM.
Good find @jcmm11 , I have not used that option to patch the boot.img.

Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.

New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
This issue is resolved, thank you for your report!
def-g said:
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
Click to expand...
Click to collapse
I'm aware of this issue, will try to figure out the cause of the issue

topjohnwu said:
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
This issue is resolved, thank you for your report!
I'm aware of this issue, will try to figure out the cause of the issue
Click to expand...
Click to collapse
Cool. To be honest, only a minor inconvenience. Your work is greatly appreciated.

I just installed this build and it appears to be fine on my device. The logcat was taken in Logcatx using the per app logcat for Magisk Manager. If you would like a full system logcat, let me know, or if you would like any other info such as last_kmsg or dmsg, let me know.
I have been installing through TWRP, since recently I have twice experienced data corruption issues with the direct install method in unofficial builds, noted in the unofficial thread.
As always, Thanks

Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.

BustedFly said:
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
Click to expand...
Click to collapse
I suggest you download MM from here and try to install it. I have been flashing Unofficial builds of Magisk for some time and this appears to be a common issue. It should not happen if you did a full wipe of the ROM though.
The latest Canary Magisk Manager.apk download:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/app-full-debug.apk
Direct download for all of the latest Canary builds:
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds

Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times

BustedFly said:
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
Click to expand...
Click to collapse
By fullwipe, I presume you mean full wipe of the ROM? If not, you must remove the Magisk Manager of the unofficial build before installing this one, as it is signed with a different key.

Yes.. I mean fullwipe by twrp and clean Installation of the Rom

BustedFly said:
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
Click to expand...
Click to collapse
After flashing Magisk and rebooting, the app-full-debug.apk will not install? That is a strange issue. Maybe someone else can help.
On one device with @kantjer 's latest build, I first un-installed his Magisk Manager, installed the app-full-debug.apk, opened it, set up the custom update channel to the link in the op: https://bit.ly/2MPKGY5 and hit install, download Zip only, then rebooted to TWRP and installed that downloaded Magisk.zip and rebooted to a working Magisk install.

Hey @topjohnwu,
I've noticed a line just after rebooting using the Canary:
Code:
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: decode with protobuf from [/data/property/persistent_properties]
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: prop [persist.magisk.hide] does not exist
I'm not sure if it's important or not for magisk functionality, however I wanted to report it just in case something is off.
I'm using OnePlus 6 with Open Beta 2 (Pie, 9.0).

I'm going to make it my duty to delete any and all posts that are not relevent to what the developer wants or is asking for.
I'll be checking this thread daily from here on out. If I find myself deleting a ton of any reoccurring member's posts, I'll be escalating to consequences.
Please, thoroughly give your posts some thought prior to submitting them, and ask yourself if whether or not it fits into how or what the OP is asking.
Thank you

So, tried last canary, nothing critical to report apart that FGO doesn't work (it crashes like before with error 61), here there are both magisk log and catlog.
Catlog (too big for xda, dunno why): https://mega.nz/#!LUoBQY6L!X--KKkCCzQn4SLwaIX1hYsmrKzzNfx1TTSGCh1b-0E4
Magisk log attached.
OnePlus 6 OOS 5.1.11, 8.1 July Patch
If anything else is needed I'll provide it right away

[TOOL] Magisk Module Manager for recovery v2.5 (Magisk 19)

Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk

Great work dev[emoji106], thanks

doesn't works for me (doesn't list modules)

mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
To list modules the script needs to write on /cache or /data. It will choose by itself.
Please send some screenshot of issue.

Looks very promising, especially enjoy having a GUI for this.

mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
I'm working to make script use no external files, so script will depends completely on your recovery binaries.
Hope to release it soon.

I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.

mikeos said:
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
Click to expand...
Click to collapse
I don't know if I got it correctly.
Well... commonly modules won't survive after Magisk removal.
If you can't access TWRP for flash Magisk uninstaller or disable the problematic module, you can try to flash or even boot the ROM's stock kernel through fastboot.
But if such module did others modifications into data, so you'll have to reflash whole ROM.

Are you planning on publishing this on magisk repo?

This has saved my bacon at least 4 times since installing it, many thanks Adriano

Saved me from bootloop module, works like a charm!

Adriano-A3 said:
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Click to expand...
Click to collapse
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."

Thx bro, you saved my day

PixelHead0_0 said:
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Click to expand...
Click to collapse
Same here, on Samsung S10+ with August update, latest Magisk and Twrp.

very useful for android 10, thank you sir !

I can't understand how to run it on the terminal

will it work with Magisk 20.0??

Sivabalan said:
will it work with Magisk 20.0??
Click to expand...
Click to collapse
have you tried it? does it work on magisk 20.1

Confirmed working with Magisk 20.1, thanks a ton for this!

working on 20.2 + android 10