Database Develop

Bein Sport app refuses to work with my rooted Z3C

Hi everyone!
I have a rooted Z3C and it is a fantastic phone, I love it. The problem is that I bought a television sport service that includes the possibility to watch games on your phone, it's called Bein Sport. This app is able to detect root and refuse to play any videos so the service I bought becomes kind of useless
The worst part is that I don't want to mess around, just want to watch games on my phone and use the service for what it was thought. Si I thought i'd give a shout here, has anyone been able to bypass that annoying feature? I don't even understand why they don't like rooted phone
thanks!

McGuigew said:
Hi everyone!
I have a rooted Z3C and it is a fantastic phone, I love it. The problem is that I bought a television sport service that includes the possibility to watch games on your phone, it's called Bein Sport. This app is able to detect root and refuse to play any videos so the service I bought becomes kind of useless
The worst part is that I don't want to mess around, just want to watch games on my phone and use the service for what it was thought. Si I thought i'd give a shout here, has anyone been able to bypass that annoying feature? I don't even understand why they don't like rooted phone
thanks!
Click to expand...
Click to collapse
There is an Xposed module for masking root on your phone, not sure if it will work or not. There is another Xposed app that offers help as well.
Installing Xposed can sometimes be tricky, make sure you find the right arm zip or you could be facing bootloops.
The place to start if you want to go down that road is here

Didgesteve said:
There is an Xposed module for masking root on your phone, not sure if it will work or not. There is another Xposed app that offers help as well.
Installing Xposed can sometimes be tricky, make sure you find the right arm zip or you could be facing bootloops.
The place to start if you want to go down that road is here
Click to expand...
Click to collapse
Hey Steve, thanks for answering. I am willing to try your solution so I read the page you showed me to install Xposed. I downloaded the last version of the ARM (note arm64, or x86), should I boot into recovery and flash it now? I reaaally don't want to mess up and have to reinstall it all! Is the Z3C part of the phones that have problems with Xposed? cheers!

McGuigew said:
Hey Steve, thanks for answering. I am willing to try your solution so I read the page you showed me to install Xposed. I downloaded the last version of the ARM (note arm64, or x86), should I boot into recovery and flash it now? I reaaally don't want to mess up and have to reinstall it all! Is the Z3C part of the phones that have problems with Xposed? cheers!
Click to expand...
Click to collapse
I use Xposed, it's very popular and works fine on the Z3c. I think the emphasis is to read about it before you do it, as many people rush in, go to downloads, install the one with the latest build number and then come crying to the forum about bootloops.
The fact that you have read ahead on the page before you did anything assures me that you won't mess it up :good:
If it reassures you, I am using xposed-v80-sdk22-arm.zip on a 5.1.1. build. But there are more recent versions out now, although I don't know what the advantages of using those are. Perhaps later versions cover the use of MM. Can anybody enlighten me on that?
Edit: Once you have flashed the installer in recovery, restart the phone and then install XposedInstaller_3.0_alpha4.apk
With that installed and running you can find the modules and install them.
Each install or change of settings requires a restart.

Didgesteve said:
I use Xposed, it's very popular and works fine on the Z3c. I think the emphasis is to read about it before you do it, as many people rush in, go to downloads, install the one with the latest build number and then come crying to the forum about bootloops.
The fact that you have read ahead on the page before you did anything assures me that you won't mess it up :good:
If it reassures you, I am using xposed-v80-sdk22-arm.zip on a 5.1.1. build. But there are more recent versions out now, although I don't know what the advantages of using those are. Perhaps later versions cover the use of MM. Can anybody enlighten me on that?
Edit: Once you have flashed the installer in recovery, restart the phone and then install XposedInstaller_3.0_alpha4.apk
With that installed and running you can find the modules and install them.
Each install or change of settings requires a restart.
Click to expand...
Click to collapse
Thanks! I'm gonna procede and give you a heads up! cheers

I am unable to flash the xposed.zip in recovery (Philz). It says "failed to set up expected mounts for install". I have tried on internal SD, external SD and even USB... any idea?

McGuigew said:
I am unable to flash the xposed.zip in recovery (Philz). It says "failed to set up expected mounts for install". I have tried on internal SD, external SD and even USB... any idea?
Click to expand...
Click to collapse
Check you have root, install SuperSU and make sure it's up to date

Didgesteve said:
Check you have root, install SuperSU and make sure it's up to date
Click to expand...
Click to collapse
Yep, installed, up do date, and some apps even use my root without any issues

If anyone comes here, here is what happened to me: I tried to install Xposed to try this trick but my phone would'nt falsh because it couldn't mount /system. I assumed that it was a problem with partitions. I tried deleting root manually but the app always found root even when I wasn't rooted anymore (beware, this app is pretty smart). I ended up having to go back to stock which sucks because the battery is really bad in comparison, but anyway I can watch football! Cheers

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

[Discussion] Bypass root detection Fidor banking app

Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...

h0l said:
Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...
Click to expand...
Click to collapse
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs

DarkSJ1998 said:
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
I did. And rebooted. And reinstalled. And combinations of those.
A short screenrecord of what is happening as soon as I try to open the app can be found here (youtube link)

I have the exact same Problem
Everything works: Netflix, other banking apps, etc.. Just Fidor. I do not really know how their detection works, but I assume it's not just a root detection.
The weird thing is, it worked flawlessly 2 years ago Now it's just annoying..
Waited a few versions oft Magisk now, however nothing changes.
You're not alone

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Same problem here ... since the new fidor version v3.14 is out, no way to getting it to work. Downgrade to 3.12 is futile, it forces the update to 3.14 immediately.

As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98

Thank you, the issue seems to have been addressed there. But as far as I can see, the canary version does not have the optional modules, correct? So I think, unfortunately I will have to wait for an adapted release of the regular magisk.

rpc75 said:
But as far as I can see, the canary version does not have the optional modules, correct?
Click to expand...
Click to collapse
I have no idea what that means... Magisk modules works just fine on the Canary releases.

Didgeridoohan said:
As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98
Click to expand...
Click to collapse
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!

dagoban said:
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.

alike03 said:
Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.
Click to expand...
Click to collapse
Check the link, one post before yours...

Didgeridoohan said:
Check the link, one post before yours...
Click to expand...
Click to collapse
Thanks, I was already going through that one.
Turns out the Banking app was detecting the Original Magisk Package.
Hiding Magisk Manager itself fixed my problem. Thanks for the link.

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
Still did not get Fidor to work. Crashes after the initial first 2-3 seconds. If I uninstall Magisk it works again. Disabling modules, delete files from sd-card, etc. didn't change a thing.
This also seem not to be the problem, since it works after uninstalling Magisk.
Fidor is hidden from Magisk, Magisk is repacked with other name.
Mind giving specific instructions on what you did to make Fidor work on your device?

Thyrador said:
Mind giving specific instructions on what you did to make Fidor work on your device?
Click to expand...
Click to collapse
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...

Didgeridoohan said:
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...
Click to expand...
Click to collapse
So basically same setup. Still doesn't work with latest Fidor Release.

Thyrador said:
So basically same setup. Still doesn't work with latest Fidor Release.
Click to expand...
Click to collapse
When you say "basically", what's the difference?

Didgeridoohan said:
When you say "basically", what's the difference?
Click to expand...
Click to collapse
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.

Thyrador said:
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.
Click to expand...
Click to collapse
You're going to have to start digging deeper then...

Bank app detecting root or modified system

I'm trying to use this app: play.google.com/store/apps/details?id=br.com.banrisul
I've added to the hiding list and enable core only mode, it still closes at startup after saying my phone is either root or running a modified system. I've tested with rootbeercheck and it doesn't detect root in any of its tests.
i.imgur.com/60Zs5IH.png

No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Didgeridoohan said:
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
Click to expand...
Click to collapse
but what exactly would trigger it? The link talks mostly about methods to hide magisk, I didn't find anything about what to do if magisk is working but the check fails. I've uninstalled titaniumbackup and rootbrowser. I've disable adb and developer options, I've deleted any folder or downloaded file related to magisk or those apps.
I'm running lineageos, would that be it? How would I go about it?

Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.

Didgeridoohan said:
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Click to expand...
Click to collapse
It passes both checks.
I am running lineage OS 14.1 (Android 7.1.2) on a moto g4.

My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.

Didgeridoohan said:
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Click to expand...
Click to collapse
Yes, after searching around a bit more I found about why. I completely forgot that I had flashed supersu on my phone before flashing magisk. So I guess that's what the app was freaking out about. So I flashed a supersu removal and reflashed my ROM, now the app is working normally
Thanks for the help!

Same problem
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it

hammohammo said:
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
Click to expand...
Click to collapse
What version of the application do you want?

I have the latest version installed and it does not detect root

Im rusty, mr 0 , 2 ,3 ?

No rom dev.
Can't get magisk in.
Dk magisk anyways
Xposed is doa? Or past it's prime.
Ok, how to gain root? Flash kernel which won't flash? Ow.

ǀcey said:
No rom dev.
Click to expand...
Click to collapse
Uh... you can try GSIs on this phone after unlocking bootloader. Most of the phone's functionality work with GSIs at the moment.
ǀcey said:
Can't get magisk in.
Click to expand...
Click to collapse
Recently Magisk has changed its way of distribution so there's only an apk now. But if you rename the Magisk apk into a zip, you can then flash it from TWRP (which you can access by flashing arter97's kernel).
ǀcey said:
Dk magisk anyways
Click to expand...
Click to collapse
Nowadays if you're to root the most ideal approach would be Magisk, which allows you to modify the system without directly touching the system partition, as well as hiding its presence from certain sensitive apps so Safety Net can still pass.
ǀcey said:
Xposed is doa? Or past it's prime.
Click to expand...
Click to collapse
If you're saying it's past prime... in some aspects, yes, thanks to the fact that you can't have both Xposed and Safety Net passing at the same time.
Still, if you're interested, you may consider looking for EdXposed or LSposed. I haven't tested it myself as I don't really have a use case at the moment, but these might be useful.
ǀcey said:
Ok, how to gain root? Flash kernel which won't flash? Ow.
Click to expand...
Click to collapse
You mostly need to just unlock bootloader following official instructions. After that you can proceed to flash kernels and GSIs through fastboot.
PS: I think this thread should best be posted in the Q&A forum...
EDIT: Just noticed your other post. If that was your real question... well, you were in the stock recovery and not the bootloader so fastboot commands obviously won't work there.
To enter bootloader, power it off, hold VOL- and POWER buttons until you see something like "Restart Bootloader", then you should be able to use fastboot.

Thank you, for all of your information!
It helped me by heaps!
The biggest problem I was having, was thinking the phone was in fastboot when it wasn't.
When I figured that out, the phone was quickly up n running on Phh-Treble with GApps Gsi.
Magisk Manager vs apk uses were confusing. It's Modules I can more easily blindly understand due to knowing XPosed.
Magisk went in smoothly & successfully via the change extension fastboot method which you explained.
But it appears the same as before inside the OS It's there but not really in type of thing.
Everything but the f2fs file and Magisk did complain.
I have no idea what kernel actually made it in now.
Safetynet! Hahaha! Is a new thing for me.
My phone is PlayStore bonafide uncertified also now.
PlayStore, I tried some other gapps nothing really changes, it just reupdates back to where it was, if it does, anyways(I think).
I tried registering device too. Failed that!
Being Uncertified = no netflix, no bank apps(deal breakers to me). GPhotos 1/2-ish working. Gvoice, Gmail working great! Razer Themes.apk + Pandora disappeared. I miss Razer Themes Lockscreens alot! Razer gives only a play link.
I installed older Netflix & Bank app. Both working.
Play ignores netflix but updated Bank. The same Bank app did stop working on a deemed outdated device in the past. It's not Chase but close.
I did try hiding things from the launcher via an other installed launcher.
An old Selinux(sp?) showed set to permissive. I changed to enforced, rebooted and it appeared to stick.
I installed Greenify(old) and stopped everything then did my monthly banking business, paid, xferred, etc. All transactions were confirmed. Boot still unlocked.
Soon afterwards, I installed Aptoide which informed me of root.
The Gsi's package Installer, won't install anything from within Es(I'm a diehard Es file manager user). The built-in file manager must be used to call the installer. The built-in file manager also crashes when searching.
A buggy installer I can deal with. Banking without it's app, I can not.
A halfbaked PlayStore is doable but not ideal.
The gsi itself on a RP2 is beautiful. The darks darker. The flashlight toggle works now! The fingerprint sensor never worked, still doesn't. 120fps, few games bake that capablity in. I haven't tested yet. No sound in Wyze app.
I recommend having your fav most used .apks dled before leaping onto it.
First boot was loud! Be prepared!
Then nothing.
2 days later, I noticed all alarms & notifications were set to silent sound.wav.
Idk, where to go from here. Stick to where it is now & wait for fixes. Go back. Or to go patch crazy if I can manage to get Magisk in.
I'm happy enough where it is now and it feels pretty secure. Will relocking the bootloader wipe it? The adult in me thinks.
But! I love tweaking...zzz

Relocking undoes it

LSS4181 said:
Uh... you can try GSIs on this phone after unlocking bootloader. Most of the phone's functionality work with GSIs at the moment.
Recently Magisk has changed its way of distribution so there's only an apk now. But if you rename the Magisk apk into a zip, you can then flash it from TWRP (which you can access by flashing arter97's kernel).
Nowadays if you're to root the most ideal approach would be Magisk, which allows you to modify the system without directly touching the system partition, as well as hiding its presence from certain sensitive apps so Safety Net can still pass.
If you're saying it's past prime... in some aspects, yes, thanks to the fact that you can't have both Xposed and Safety Net passing at the same time.
Still, if you're interested, you may consider looking for EdXposed or LSposed. I haven't tested it myself as I don't really have a use case at the moment, but these might be useful.
You mostly need to just unlock bootloader following official instructions. After that you can proceed to flash kernels and GSIs through fastboot.
PS: I think this thread should best be posted in the Q&A forum...
EDIT: Just noticed your other post. If that was your real question... well, you were in the stock recovery and not the bootloader so fastboot commands obviously won't work there.
To enter bootloader, power it off, hold VOL- and POWER buttons until you see something like "Restart Bootloader", then you should be able to use fastboot.
Click to expand...
Click to collapse
I have one of the faulty charging ports so cannot do anything with USB. I do have my bootloader unlocked so is there any way to get the gsi's, twrp and root onto the phone via SD card? Any help is appreciated.