Database Users

[Guide]How to install Xposed on the j700p

(Obvious words of legality, etc. I take no responsibility for anything that happens to your phone. I managed this on my own and everything worked. If you messed it up, I'm sorry, but it's not my problem)
Ok, now the good stuff! Hello all!
As you may know, user messi2050 managed to get us root on our phones (yay!). We don't yet have a custom recovery, and this is a usual requirement for Xposed, but fear not! I have figured out how to install it without a custom recovery. I'll try and be as clear as possible and provide all direct links to the files needed, but if something confuses you please let me know!
1. Root your phone
2. Download and install FlashFire
3. Samsung has weirdness associated with their roms and the way they do things under the Android hood, so you can't use the normal Marshmallow xposed module. You will need the Unofficial Xposed for Samsung Marshmallow by Wanam (HERE is a link directly to the APK you need)
4. Install the Xposed Installer for Marshmallow (Again, there is a direct link to the APK HERE[/URL
5. Open up FlashFire and press the (+) button. Select "Flash ZIP or OTA"
6. Choose the file downloaded in step 3
7. IMPORTANT! DESELECT "MOUNT /SYSTEM READ/WRITE"! Make sure everything is deselected! Then click the "✓"
8. Moment of truth y'all. Press the "FLASH" button at the bottom of the screen. You may get warnings, accept or clear them and continue
9. Your phone will shut down, show a bunch of text, and reboot after installing. THE REBOOT TAKES A LONG TIME, SEVERAL MINUTES AT LEAST! Don't be afraid, it will take quite a while to reboot. When it is done, it will "optimize apps" and then you should be all set!
Some xposed modules may not work for this phone! You run the risk of constant crashes and reboots with some modules. There are compatibility issues, especially if you neglect to read the warnings of each module, so read carefully! I'll give a list of modules I've installed with no issues, which will give yo a decent place to start (NOTE: There are individual settings in many of the modules, I haven't tried everything. So I can only tell you that the installation of the module is safe, NOT each setting).
Burnt Toast
Disable Fullscreen Keyboard
GPM Notification Seek Bar [L-M]
Greenify
Marshmallow SD Fix
Media Notification Seek [L-M]
NoSafeVolumeWarning
Notification Count
Wanam Xposed
XTouchWiz
If you happen to have success with any others, let us know and I'll update this list. Hope you guys enjoy, I'm so happy we finally got root and Xposed on this phone!

Followed your instructions (thanks) and have
BootManager
MinMinGuard
Swype Row and
Xinsta
Running.
It seems like most xposed modules work. Anyone interested should just follow the above instructions and give it a shot.

garyf said:
It seems like most xposed modules work. Anyone interested should just follow the above instructions and give it a shot.
Click to expand...
Click to collapse
Glad it works for you!
Yeah, I don't think there will be too many problems, I only mention the warning because if you're not careful, there are many modules that haven't been updated in years. If you're careless, you may install something from 2014 and it isn't compatible with Marshmallow and may cause constant crashes and force closes. Because we don't have a custom recovery, it's that much more important to be careful, as a mistake will requi9re a reflash and wipe everything. =S

Followed instructions and everything went just fine. Working great. Thank you!
EDIT: Having trouble finding Wanam Xposed. Can anyone help?

SonOfAnarchy0210 said:
Followed instructions and everything went just fine. Working great. Thank you!
EDIT: Having trouble finding Wanam Xposed. Can anyone help?
Click to expand...
Click to collapse
I see Wanam exposed in the list, however, it looks like XTouchWiz is similar, made by the same guy (Wanam), and is made for Marshmallow. Givev that a shot?

rainbowtuba said:
I see Wanam exposed in the list, however, it looks like XTouchWiz is similar, made by the same guy (Wanam), and is made for Marshmallow. Givev that a shot?
Click to expand...
Click to collapse
Yeah I must have been half asleep or something when I posted that because it is definitely there haha thank you though!

Opened Xposed this morning and this popped up. And when I go to downloads, there is no list. When I refresh, this keeps popping up. Any ideas as to what I should do?

Hi. Do you know how to install Xposed on j700f running mm?
Sent from my SM-J700F using XDA-Developers mobile app

Opened Xposed this morning and this popped up. And when I go to downloads, there is no list. When I refresh, this keeps popping up. Any ideas as to what I should do?
Click to expand...
Click to collapse
Sopn of Anarchy, I have no idea, sadly. Everything is working okay from my phone. No such issue
SankyLucky said:
Hi. Do you know how to install Xposed on j700f running mm?
Click to expand...
Click to collapse
If you have it rooted I would assume it's fairly similar. If there is any difference in the processor you will want to download the appropriate file, but using Flashfire and the Wanam version of xposed should be the correct move. Best of luck!

SankyLucky said:
Hi. Do you know how to install Xposed on j700f running mm?
Sent from my SM-J700F using XDA-Developers mobile app
Click to expand...
Click to collapse
Wrong thread ! For your answer here you go buddy: How to Root, TWRP and Install Xposed Framework on J7 (SM-J700F) (Screenshots inside)

Worked!
THANKS!

Hey, guys, just wondering if it's possible to flash this xposed through twrp? Or does having a working twrp alter the process or results in anyway?

acesavant00 said:
Hey, guys, just wondering if it's possible to flash this xposed through twrp? Or does having a working twrp alter the process or results in anyway?
Click to expand...
Click to collapse
Yes, I flashed this through twrp and got J700H xposed

Is there a way to keep the processor from overhearing?

SykkNyzz said:
Is there a way to keep the processor from overhearing?
Click to expand...
Click to collapse
Assuming you meant overHEATING on Snapdragon, try using the phone without aftermarket cover and without charger plugged in.
Also check out this extended guide: http://forum.xda-developers.com/galaxy-j7/how-to/marshmallow-battery-drain-overheating-t3439274

natri23 said:
Assuming you meant overHEATING on Snapdragon, try using the phone without aftermarket cover and without charger plugged in.
Also check out this extended guide: http://forum.xda-developers.com/galaxy-j7/how-to/marshmallow-battery-drain-overheating-t3439274
Click to expand...
Click to collapse
No, the phone heats up in my hand without charger and I don't even own a cover. I misspelled my word on accident so I understand why you would correct me.
---------- Post added at 01:42 PM ---------- Previous post was at 12:51 PM ----------
But that is now an old issue since I used the debloated version

I am running the modules and they all seem to work perfectly:
HideBatterylowAlert,
Neo power menu,
PMP,
YouTube background playback,
And flat style bar indicators.
Thank again!

I have the sm- j700p Boost and tried this but it bricks the phone. The apk installs fine but the phone never boots up fully after installing the framework. I tried with twrp and flashify.

worked perfect on J700T Tmobile.
maybe you should post this in the J700T Section or i can do it?

Solved
newsense2004 said:
I have the sm- j700p Boost and tried this but it bricks the phone. The apk installs fine but the phone never boots up fully after installing the framework. I tried with twrp and flashify.
Click to expand...
Click to collapse
OK finally got it working I don't know if I had the wrong file somehow or if using twrp to flash but I started over. Re-download the files and used flashfire to flash the zip. Worked perfectly this time, this phone has no compass sensor. Wish I knew that as I only wanted Xposed for the module that mimics a gyro.

Magisk

Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.

tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
Was wondering about this too. Not entirely confident about what things to reflash in case things go wrong otherwise wouldve tried this.

So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?

reddrago said:
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
Click to expand...
Click to collapse
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...

tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.

piskr said:
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
Click to expand...
Click to collapse
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?

tdgillihan said:
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
Click to expand...
Click to collapse
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.

ultramag69 said:
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
Click to expand...
Click to collapse
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.

piskr said:
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
Click to expand...
Click to collapse
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.

tdgillihan said:
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.

piskr said:
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
Click to expand...
Click to collapse
If you're running a custom ROM it may or may not work. Some are saying it does and others not. But if we're talking about the A7 here that'll be stock for now.
Always thank those who are helpful...and just ignore those who aren't.

tdgillihan said:
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...

ultramag69 said:
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
Click to expand...
Click to collapse
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.

tdgillihan said:
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Don't know , I just downloaded the root manager Tenfars recommended from play store...
It works fine...

Are there any new reports on this subject? I have been able to successfully install Magisk and PHH SU on a Nexus 6P , but using the identical procedure on my Axon 7 (U) does not work. I am puzzled.

Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.

lokissmile said:
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
Click to expand...
Click to collapse
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?

lokissmile said:
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
Click to expand...
Click to collapse
that's my thought too, since magisk seems not to create a log in /cache as it should and doesn't reaveal itself via logcat it looks like it doesn't realy get executed.
The guys in the common magisk were not realy able to help, guess we have to dig more into the init.rc script / boot.img patch. But might be that it get's fixed with v7 anyway, hope @topjohnwu is able to get it done quickly (or maybe has some ideas he how to debug it more, i didn't get an answer from him in the common, probably way too crowded magisk thread - goddamn pokemongo!)

Subscribing. Would like to get this working as well.

Edit: I've gone ahead and opened up a thread so it is easy to find: http://forum.xda-developers.com/axon-7/how-to/guide-installing-magisk-systemless-phhs-t3524270
We're up to Magisk V9 now and it still doesn't work. I'm almost certain it has to do with the execution of the patched boot.img, due to the write-protected /system partition. I finally got it working by using the the method in the guide I posted.

Google assistant

Has anyone received Google Assistant on their phones yet? Just curious.

Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520

I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.

SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.

misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.

SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.

"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?

misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...

deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.

deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.

misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?

SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it

I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?

It's here! I literally just this minute got Google Assistant!

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?

misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.

Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?

How to install Xposed correctly??

Hey everyone!
I have a G4 Play, trying to get xposed to work, but can't make it work no matter what.
I have already unlocked the bootloader, flashed a Deodexed stock image (i believe is this one https://www.androidfilehost.com/?fid=745425885120714391).
What I've tried so far:
- Install from Material xposed installer (arm SDK23 87.3), will not get past the boot logo (using magisk root).
- Install from recovery without magisk installed, same as above.
- Install it systemless through magisk, worked once and then black screen, any other attempt to install it leads to a black (blank?) screen, after boot animation, screen lights up, but nothing happens, cannot even turn off the screen and nothing happens even if I let it be for a couple hours.
I just really want to use xposed, I miss it so much from my previous devices, if someone can help or recommend a Working ROM for it (or with it already integrated), that would be so cool.

I have xposed moto g4 play since I needed it for pandora patcher. My current setup for months now is cyanogenmod-13-moto-g-play.
Did Xposed for marshmallow, android 6.0. I'm offering the option I've personally tried. What negative thing I experience in my whole setup is it downloads data on the background and I needed to force my cellular provider to disable my data. Only using it for wifi.
*I'm just returned from XDA from 3+ months of non-xda forums login so I needed to catchup, hoping others would suggest better setup than mine (moto g4 play CM 13 + xposed for MM).

Bump?

bidomo said:
Bump?
Click to expand...
Click to collapse
Unlocked device with stock ROM and SuperSU 2.8x branch. Xposed 87 went in without a hitch and has run smoothly for nearly a year. Guessing Magisk is the culprit.

Davey126 said:
Unlocked device with stock ROM and SuperSU 2.8x branch. Xposed 87 went in without a hitch and has run smoothly for nearly a year. Guessing Magisk is the culprit.
Click to expand...
Click to collapse
Will try your combo and see how it goes, will post back, thanks for letting me know

Davey126 said:
Unlocked device with stock ROM and SuperSU 2.8x branch. Xposed 87 went in without a hitch and has run smoothly for nearly a year. Guessing Magisk is the culprit.
Click to expand...
Click to collapse
Didn't work, systemless root 2.82 SR3 and xposed v87 SDK23 ARM, doesn't work, would not get past the boot logo, I don't know if it's the ROM or whats wrong.

bidomo said:
Didn't work, systemless root 2.82 SR3 and xposed v87 SDK23 ARM, doesn't work, would not get past the boot logo, I don't know if it's the ROM or whats wrong.
Click to expand...
Click to collapse
Using 2.82 stable systemless on pure stock. Probably need to roll back or pursue another Xposed friendly ROM. If you prefer stock (works well) one has the a question the value of going deodexed unless theming or have another specialized situation. Read up on transitioning between Magisk and SuperSU. Some claim a painful experience; others switch with ease. Possible Magisk remnants were present in your last test. Good luck.

Davey126 said:
Using 2.82 stable systemless on pure stock. Probably need to roll back or pursue another Xposed friendly ROM. If you prefer stock (works well) one has the a question the value of going deodexed unless theming or have another specialized situation. Read up on transitioning between Magisk and SuperSU. Some claim a painful experience; others switch with ease. Possible Magisk remnants were present in your last test. Good luck.
Click to expand...
Click to collapse
I'm gonna flash a fully stock ROM and directly try it, the reason a got a deodex is that I messed up the stock ROM and found it easier to install the deodex as I didn't have my laptop, will do as soon as I get back from work

[Magisk] How will I install Android 10 when I receive it without losing root?

Will it be the same way as the small security updates?
I.e. (from Magisk) install to inactive slot before restarting the phone.
Also, Android 10 has the faster security updates feature which installs them without restarting the phone. So when I do get Android 10, and receive a security update, won't it directly install and remove root even before I reboot through magisk?

I think clean flash should be the best option (I'm talking about the update from 9 to 10).

onliner said:
I think clean flash should be the best option (I'm talking about the update from 9 to 10).
Click to expand...
Click to collapse
I don't wanna lose my data ?

usaid.shafqat said:
I don't wanna lose my data
Click to expand...
Click to collapse
If you dont know how to back up your data, then you have no business rooting your phone. Leave it stock, or better yet, get an iPhone.

thedrizzle said:
If you dont know how to back up your data, then you have no business rooting your phone. Leave it stock, or better yet, get an iPhone.
Click to expand...
Click to collapse
I use titanium but what I meant by "not losing my data" was that I would want to avoid logging into all my accounts again as much as I could.

usaid.shafqat said:
Will it be the same way as the small security updates?
I.e. (from Magisk) install to inactive slot before restarting the phone.
Also, Android 10 has the faster security updates feature which installs them without restarting the phone. So when I do get Android 10, and receive a security update, won't it directly install and remove root even before I reboot through magisk?
Click to expand...
Click to collapse
Which version 6t do you have?

twinnfamous said:
Which version 6t do you have?
Click to expand...
Click to collapse
Running the latest: 9.0.16

usaid.shafqat said:
Running the latest: 9.0.16
Click to expand...
Click to collapse
I meant is it T-Mobile or international?
The T-Mobile one is most likely going to be difficult

Hi there...
I've just clean this thread slightly. This is a thread in the Q&A forum, which allows to ask EVERYTHING that is somehow related to this device. There hasn't been a similar thread yet i.e. it was fine to create one.
If someone doesn't like the topic, some questions or answers simply continue your journey and refrain from posting here.
Your friendly neighbourhood watch

Guys don't expect things to work with the new update immediately. Android 10 has a file system rehaul so stuffs gonna work differently. That being said I'm excited. I'm just sad I won't get to use desktop mode since our USB Cs arent new or powerful enough to use as an HDMI out *sadfate*

twinnfamous said:
I meant is it T-Mobile or international?
The T-Mobile one is most likely going to be difficult
Click to expand...
Click to collapse
Oh, it's International, unlocked.

usaid.shafqat said:
Oh, it's International, unlocked.
Click to expand...
Click to collapse
Before you do any of this make sure you disable any magisk modules you may have
Do local upgrade method but don't reboot.
Then go to magisk and select modules click the plus and find twrp installer zip once that's done.
Choose install to inactive slot after ota
Then reboot.

twinnfamous said:
Before you do any of this make sure you disable any magisk modules you may have
Do local upgrade method but don't reboot.
Then go to magisk and select modules click the plus and find twrp installer zip once that's done.
Choose install to inactive slot after ota
Then reboot.
Click to expand...
Click to collapse
Hello, when you say to disable the Magisk modules, should you simply uncheck the modules installed in Magisk or press "uninstall" and "restore images" on the Magisk home page?

PàllGuizi said:
Hello, when you say to disable the Magisk modules, should you simply uncheck the modules installed in Magisk or press "uninstall" and "restore images" on the Magisk home page?
Click to expand...
Click to collapse
I never uninstall magisk and restore images. Because I allways keep magisk. I just select to remove modules on next boot because they cause me problems.
As long as u keep magisk u can flash twrp with magisk.

twinnfamous said:
I never uninstall magisk and restore images. Because I allways keep magisk. I just select to remove modules on next boot because they cause me problems.
As long as u keep magisk u can flash twrp with magisk.
Click to expand...
Click to collapse
I prefer to ask to be on, because some also do like this: uninstall Magisk (without reboot), installation of the update (still without reboot) Magisk installation from the manager and reboot! I know it's more for OTAs but in the end I found on the forums that some processes like that for any ROM.
Anyway thank you for your answer I will try now: D
Edit : It does not work for me, nothing starts and it tells me directly "Failure of the installation of the home system" when I try by the local upgrade I would do with twrp this does not matter

Let's just disregard this silly post please.
Thank you.
Incidentally, this might be a sound method for upgrading Stable Pie to Stable Q:
https://forum.xda-developers.com/showpost.php?p=80812793&postcount=12