Develop Bugs

Xposed framework and ota updates

I know that if I uninstall or freeze anything that came in my rooted stock rom, subsequent ota updates may not install correctly. (is that true?)
Will installing Xposed Framework also cause problems when installing an ota system update?
Thanks.

Anderson2 said:
I know that if I uninstall or freeze anything that came in my rooted stock rom, subsequent ota updates may not install correctly. (is that true?)
Will installing Xposed Framework also cause problems when installing an ota system update?
Thanks.
Click to expand...
Click to collapse
if an ota fails and no factory images are available, just flash the previous image with the no wipe option (edit the flash-all.bat with notepad++ and remove the -w paramater iirc) and take the ota

Thanks for the work around.
But does installing Xposed Framework affect the core stock rom in a similar manner?

Anderson2 said:
Thanks for the work around.
But does installing Xposed Framework affect the core stock rom in a similar manner?
Click to expand...
Click to collapse
It depends on the update. If it checks /system/bin/app_process it will fail as that's the file Xposed replaces.

Thank you. I was not clear as to how Xposed worked.

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

Update SuperSU

@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.

nujackk said:
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
Click to expand...
Click to collapse
Just dismiss the notification.

rbox said:
Just dismiss the notification.
Click to expand...
Click to collapse
I've been doing that, just wondering if i can/should update ? Will It cause problems if i flash latest version?

got the same idea: just flash super su 2.79 sr3 should work?

That's what I'm thinking, just wanting rbox to confirm it shouldn't hose anything. I know some roms on phones don't work with latest versions. And since he is using such an old version, I'm think that might be the case here

Hmm i think i will try it next time. Create a backup and flash supersu.

Spillunke said:
Hmm i think i will try it next time. Create a backup and flash supersu.
Click to expand...
Click to collapse
flashing/updating SuperSU is not working and you will lose root

Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.

Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs

rainman74 said:
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
Click to expand...
Click to collapse
What FW where you on & what method did u try using ?

- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...

rainman74 said:
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
Click to expand...
Click to collapse
Although it is much more of a pain to do fresh installs. I think when dealing with root it should be more stable to mess with it that way.
One can also do the build.prop mod to stop updates if one wants to test older FW versions.

Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
First thanks for the link to the xposed fix:good: And now that you mention it I don't know why i didn't think of that sooner, should be relatively easy to just replace the files in the zip with 7zip DUH. Only problem is I have everything all setup perfect.

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

How to install Magisk and Xposed on Note 4?

I know this is basic stuff but I needed some assitance please.
My goal is to have a systemless root with Xposed and Magisk so I can run apps like Netflix.
Besides not being able to use Netflix I'm rather satisfied with my current setup. Which is:
Note 4 Verizon / 6.0.1 / Paulpizz Rom which includes Xposed.
My problem is I've tried to install Magisk, but get stuck at a neverending load at the Verizon load screen.
I understand Netflix uses google Safetynet and I think that even if I did have Magisk installed the fact I have a custom Rom would make the check fail anyways.
Also, when I tried installing Xposed on my Stock Rom, it failed due to the compatibility issues with this combination.
So how can I change my current setup to one where I have Xposed and Magisk (or something else) that will allow me to pass Safetynet?
Thank you in advance.
Freddiesilva

freddiesilva said:
I know this is basic stuff but I needed some assitance please.
My goal is to have a systemless root with Xposed and Magisk so I can run apps like Netflix.
Besides not being able to use Netflix I'm rather satisfied with my current setup. Which is:
Note 4 Verizon / 6.0.1 / Paulpizz Rom which includes Xposed.
My problem is I've tried to install Magisk, but get stuck at a neverending load at the Verizon load screen.
I understand Netflix uses google Safetynet and I think that even if I did have Magisk installed the fact I have a custom Rom would make the check fail anyways.
Also, when I tried installing Xposed on my Stock Rom, it failed due to the compatibility issues with this combination.
So how can I change my current setup to one where I have Xposed and Magisk (or something else) that will allow me to pass Safetynet?
Thank you in advance.
Freddiesilva
Click to expand...
Click to collapse
In order to install magisk on anything now you must patch the boot IMG prior to booting for the first time . xposed needs to be your api and touvhwiz compatible . I think wanam does a version for samsung

mojoswagger1980 said:
In order to install magisk on anything now you must patch the boot IMG prior to booting for the first time . xposed needs to be your api and touvhwiz compatible . I think wanam does a version for samsung
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock rom by @PaulPizz from here and installed Magisk with stock boot.img, and installed the Xposed version from @wanam.
Special thanks to @PaulPizz and @wanam

freddiesilva said:
Thanks for your help. I was able to flash stock rom by @PaulPizz from here and installed Magisk with stock boot.img, and installed the Xposed version from @wanam.
Special thanks to @PaulPizz and @wanam
Click to expand...
Click to collapse
Nice !! That's the much stabler method I was gonna say modestrom is the stock Samsung 6.0.1 base with magisk and boot patch installed as the root method, but you pretty much did that (I'm pretty sure the kernel he made would work the ROM was built from the stock Verizon ROM )

Thanks for the info on this post I was having trouble installing xposed but now I got it working using wanam xposed on my Note 4 n910v.