Related
(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.
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.
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?
In the last week I received my xperia x compact completely stock. First thing I do when I get a new phone before even activating it is root it. I was utilizing this guide to root my xperia x compact "Guide: Root + Custom Kernel + Clean rom + TA for X Compact" and I am stuck on the step where you are instructed to flash the modified XC-GenesisKernel-v1.04-nodrm kernel and SU. Flashing this kernel always results in a boot loop (Ive waited more then 30 minutes for it to resolve). I reflash the stock service exchange unit - 34.1.A.1.198 MM firmware to get back a functioning phone. The guide recommends:
"Run xperifirm and download the "service exchange unit - 34.1.A.1.198" firmware for posterity and latest rom for your region."
Am I supposed to use the most current nougat firmware for the following steps and only use the service exchange unit firmware if I need to downgrade to the lower original firmware? The thread for the XC-GenesisKernel states it is for nougat roms, which would explain a boot loop when I try to use the service exchange unit MM rom. Ideally Id like to stay on MM so that I can use xposed. Root and the phone being fully functional with no loss of camera and such is my main desire, xposed is secondary. I have a Backup TA of my DRM keys, the phone bootloader is unlocked, and I am looking for a little direction / clarification, any help in this respect is greatly appreciated.
Thanks
efaustus9 said:
help in this respect is greatly appreciated.
Click to expand...
Click to collapse
Click the first link in the guide and read it.
XperienceD said:
Click the first link in the guide and read it.
Click to expand...
Click to collapse
Thanks, I read through it and I see indeed the latest nougat firmware is what I should use in the later steps of tuten1000's guide and is the source of the boot loop I am experiencing.
If possible I would like to stay on marshmallow so I can used xposed framework. Are you aware of or can you recommend a kernel I can flash that will give me root, fingerprint, and use of most DRM functions while still on marshmallow.
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
itandy said:
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
Click to expand...
Click to collapse
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
efaustus9 said:
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
Click to expand...
Click to collapse
You're all good to begin with MM stock ROM.
itandy said:
You're all good to begin with MM stock ROM.
Click to expand...
Click to collapse
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
efaustus9 said:
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
Click to expand...
Click to collapse
This is a common request but the answer is no.
itandy said:
This is a common request but the answer is no.
Click to expand...
Click to collapse
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
efaustus9 said:
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
Click to expand...
Click to collapse
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
itandy said:
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
Click to expand...
Click to collapse
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
efaustus9 said:
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
Click to expand...
Click to collapse
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
itandy said:
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
efaustus9 said:
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
Click to expand...
Click to collapse
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
itandy said:
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
Click to expand...
Click to collapse
Great, I will definitely check out your app. Ideally Id like to mimic what I believe is called the "immersive mode" in supported apps. In this mode the app takes up the full screen and the icons are replaced with three persistent minimal dots.
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...
HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.