Develop Bugs

[ROOT] Magisk AutoRoot: Magisk + phh's SuperUser for Nougat (No TWRP required)

People are panicking about TWRP not working on the latest Nougat firmware.
As an advanced user like me, I cannot live with a device with no root, so here is my solution.
Oh, and of course, your device need to be either bootloader unlocked, S-OFFed, or both.
What Is Magisk
Maybe.... you live under a rock?
Magisk Subforum on XDA
What This Will Do
Following the instructions here will install Magisk v9.1 (nearly same as official v9 with some fixes for cache support) and phh's SuperUser to your device.
You DON'T need any custom recovery, and your system partition is NOT touched at all.
Files and binaries are stored in the cache image, Magisk will move them to /data in the next reboot.
You can upgrade Magisk, phh root, and install other Magisk Modules within the Magisk Manager app!
Instructions
If a prebuilt boot image is available:
Download "magisk+phh_arm64_cache.zip", your prebuilt boot image, and unzip both
You should get "patched_boot.img" and "magisk_cache.img"
Install Magisk Manager and phh's SuperUser app
Reboot your device to download mode (adb reboot download)
Manually flash the images:
Code:
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
Reboot and you're done!
If you are using other bases, then grab your boot image from your OTA package, and follow the instructions:
Download "magisk+phh_arm64_cache.zip", "magisk_boot_patcher.zip", and unzip both
You should get "magisk_cache.img", and a folder with scripts and tools
Grab ANY rooted device >Android 5.0 to do the patching. Running the scripts on an unrooted device will create an unbootable boot image!
Follow the instructions in the README.txt of the tool, it shall guide you to patch your own boot image
Downloads:
Prebuilt Cache Images:
ARM64(HTC 10): magisk-v9.1+phh-r266-2_arm64_cache.zip ​Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zip​Magisk Manager:
Latest Magisk Manager​phh's SuperUser app:
​phh's SuperUser (PunchUp Beta 9)​

Reserved
Reserved

Just installed on US Unlocked HTC 10 running Stock Android N. Works great. I now have root back. Thanks for doing this.
Also, @topjohnwu correct me if I'm wrong, but if you install a Magisk Module that prevents your phone from booting, you can just re-flash the cache image. That would remove all modules you may have added and start back with just root.
And as an added bonus, I am also passing SafetyNet which I was not before do to the unlocked bootloader. Great work.

Sorry if it's already been answered in a different form it has been a while since I've been on here butt Am I able to just pull the boot image file out of the roms zip I am using or could I use the backed up boot image from the nand backup I have. Or do I have to do the Adb method. Thanks in advance.

Works great! Thanks for your work and share! @ topjohnwu
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------

This works well thank you. Has anyone been able to get xposed to work within it? I've tried to download all 3 and it will not install them - says Can't load the content at the
moment
EDIT - didn't know Xposed need SDK 24 for N... So disregard last bit

Will this work with Viper10 rom based on 2.28.401.6?

sardroid said:
Will this work with Viper10 rom based on 2.28.401.6?
Click to expand...
Click to collapse
it already has magisk/phh superuser. so there is no need to try this.

Excellent, device rooted..
Question : Now, can i delete Magisk Manager ??

Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk

I don't understand how to proceed if not US version :/

..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
GhastlyTT said:
Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Do you have any MicroSD inserted ? If yes, remove it.

psicobelico said:
..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Do you have any MicroSD inserted ? If yes, remove it.
Click to expand...
Click to collapse
Thanks for the reply. I had thought of that and removed it-still boot looping.

@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.

serophia said:
@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.
Click to expand...
Click to collapse
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?

jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.

jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.

GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
serophia said:
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.
Click to expand...
Click to collapse
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.

GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
I was in fact using Magisk. I took the OTA with Magisk and Root installed. In fact, i have the AOSP lockscreen still lol.

jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
Yes I was but i thought flashing stock boot.img will remove magisk seeing as how it allowed me to ota onto Android N perfectly fine.

Root 3.2.8 bootloop

Hi guys i really appreciate if someone could help me rooting my oneplus 3 stock from 3.2.7 to 3.2.8.
I've tried flashing full rom 3.2.8 over 3.2.7 and latest SuperSu but is not working.. i also tried to do a complete restore starting from 3.2.8 but it's the same result i get bootloop everytime.. also with phils supersu and magisk
The phone only boot on 3.2.8 if i don't have root.. i don't understand what's the problem, i really like to update the phone for the new features but aswell keep the root.

No error in the TWRP's log when you flash ?
I see that you're trying to flash magisk, but do you flash suhide 0.55 ? Suhide can be a reason of a bootloop

Thanks for the quick reply No error when i flash SuperSU or phh's.. Everything works fine till I reboot..
And no I didn't flash suhide

the_sider said:
Thanks for the quick reply No error when i flash SuperSU or phh's.. Everything works fine till I reboot..
And no I didn't flash suhide
Click to expand...
Click to collapse
what version of SuperSU, did you try the latest sr5?

I Tried sr4 and sr5... But got the same result... Maybe it's a security patch issue with latest update??

the_sider said:
I Tried sr4 and sr5... But got the same result... Maybe it's a security patch issue with latest update??
Click to expand...
Click to collapse
Super weird. Never had issues with Super SU on stock OOS.
I'm running Magisk v9 with phh SU magisk r266-2.
Used MagiskManager v2.5 to get Xposed up and running on OOS 3.2.8

Had same issue, asked on reddit and someone told me to try this:
BETA-SuperSU-v2.74-2-20160519174328-forced-systemless
and it worked

Are you using F2FS filesystem? It doesn't work well with root. Root disappears periodically like that.

AvivEliyahu said:
Had same issue, asked on reddit and someone told me to try this:
BETA-SuperSU-v2.74-2-20160519174328-forced-systemless
and it worked
Click to expand...
Click to collapse
i'm gonna try with that one!!

Tikerz said:
Are you using F2FS filesystem? It doesn't work well with root. Root disappears periodically like that.
Click to expand...
Click to collapse
yeah i was using ElementalX Kernel... i don't know if that was the problem.. but i don't think because i made a full restore of the phone with stock kernel

@AvivEliyahu
after a factory reset and flash 3.2.8 it worked.
I still don't know what was the problem but anyway thanks to everybody that tried to help me! cheers!!!

How to chose the right version of SuperSU.zip for flashing?

I flashed TWRP on my ZE551ML (Z00A-WW-2.20.40.198) and wanted to root a clean stock rom. I have successfully done so before on the same device by installing "BETA-SuperSU-v2.67-20160121175247.zip" downloaded from the official Chainfire site. I thought it would be better to have the newest version, so this time I tried to install "SR1-SuperSU-v2.79-SR1-20161221223537" from the same source. However, after installing that file, the phone stayed in a bootloop for around 10 minutes.
1. Is it normal for it to take that long, or does that mean that the second file is incompatible with my phone?
2. Did I chose the wrong file, and should I have tried to install "BETA-SuperSU-v2.67-20160121175247.zip"?
3. Which zip should I install?
I have uninstalled again, and my phone boots. What I am asking about here is which file to install.

Fiksdal said:
I flashed TWRP on my ZE551ML (Z00A-WW-2.20.40.198) and wanted to root a clean stock rom. I have successfully done so before on the same device by installing "BETA-SuperSU-v2.67-20160121175247.zip" downloaded from the official Chainfire site. I thought it would be better to have the newest version, so this time I tried to install "SR1-SuperSU-v2.79-SR1-20161221223537" from the same source. However, after installing that file, the phone stayed in a bootloop for around 10 minutes.
1. Is it normal for it to take that long, or does that mean that the second file is incompatible with my phone?
2. Did I chose the wrong file, and should I have tried to install "BETA-SuperSU-v2.67-20160121175247.zip"?
3. Which zip should I install?
I have uninstalled again, and my phone boots. What I am asking about here is which file to install.
Click to expand...
Click to collapse
Use the zip that worked before , you might have to update ...binaries after ..is all
Why you don't update to M is beyond me , the N lineage ROM is back on track by dev jrior too

timbernot said:
Use the zip that worked before , you might have to update ...binaries after ..is all
Why you don't update to M is beyond me , the N lineage ROM is back on track by dev jrior too
Click to expand...
Click to collapse
Thanks!
I've tried M already, but my favorite Xposed modules didn't work.
Is Xposed working on N?

Fiksdal said:
Thanks!
I've tried M already, but my favorite Xposed modules didn't work.
Is Xposed working on N?
Click to expand...
Click to collapse
You said the same a month back but yet you are having trouble with root
What will you miss exactly ?
Security updates to me are far more important

timbernot said:
Use the zip that worked before , you might have to update ...binaries after ..is all
Why you don't update to M is beyond me , the N lineage ROM is back on track by dev jrior too
Click to expand...
Click to collapse
timbernot said:
You said the same a month back but yet you are having trouble with root
What will you miss exactly ?
Security updates to me are far more important
Click to expand...
Click to collapse
Root is working beautifully on L, I've already installed the same SuperSU. Xposed modules are really important to me. One of my favorite modules, NetworkSpeedIndicator, didn't work for me on M. So I'm sticking with L for now. If I can get all my Xposed modules to work on M or N then I will happily upgrade

Help With Root

I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?

So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?

jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.

sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?

jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that

sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?

jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet

sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?

jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones

If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.

jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.

It worked, I'm officially rooted .Thanks for the help!

jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.

Rooting original 7.1.1 on Moto Z Play

Hi at all,
I own this device for two months now and I have read a lot about rooting and flashing. It seems to be quite difficult compared to my former Samsung and Xiaomi devices...
To avoid any kind of bricking my phone I wanted to ask if there's a way to root it. I (still) have a locked bootloader and I installed the latest update to 7.1.1 with 1st July security patch.
Is there any safe way to root and install TWRP (and afterwards some ROMs of course)?
Thank you. :fingers-crossed:

I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.

jst98 said:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
Click to expand...
Click to collapse
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come

f_ries said:
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
Click to expand...
Click to collapse
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!

Martin-cai said:
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Click to expand...
Click to collapse
If you are in 7.1.1, unlock your bootloader, download TWRP of @Alberto97 version 3.1.1-0(https://dc4.androidfilehost.com/dl/...673368273298955814/twrp-3.1.1-0-addison.img), flash it, download this kernel( https://drive.google.com/file/d/1i8PfTQ1e-WQkZ5-zD52HzWO3LZ5luaq_/view?usp=drivesdk) and the attached Magisk.zip.
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.

xdaVTU said:
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
Click to expand...
Click to collapse
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone

Martin-cai said:
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Click to expand...
Click to collapse
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky

xdaVTU said:
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
Click to expand...
Click to collapse
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly

Martin-cai said:
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Click to expand...
Click to collapse
I think creating a new post won't be necessary because kernel is already in @tomparr post, but in the last page of it, the twrp you cam download from Alberto's post, and magisk from the official thread(it's actually one of the most famous threads for now hahaha), but maybe if someone else have any issue with 7.1.1 i can create the post!
Edit. If i plan to try xposed again I tell you!

I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.

logotoy73 said:
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
Click to expand...
Click to collapse
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?

Bug camera help me
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...

xdaVTU said:
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Click to expand...
Click to collapse
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
Gean Teixeira said:
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
Click to expand...
Click to collapse
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.

Artim_96 said:
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Click to expand...
Click to collapse
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.

Gean Teixeira said:
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Click to expand...
Click to collapse
Well then go back to stock first

Artim_96 said:
Well then go back to stock first
Click to expand...
Click to collapse
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...

Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?

Artim_96 said:
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Click to expand...
Click to collapse
I'm enganed...ZIP is rooted with magisk ,flashed , It,s ok...no insue

Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk

sergiomc22 said:
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
Stock post shamu17...dez patch, root magisk