I pretty much have given up trying to pass or spoof Safetynet but does Snapchat use Safetynet to detect root or is there still methods to get signed in to Snapchat on Oxygen 10.5.12?
Works without issues for me. Rooted with magisk, safetynet passes and Snap hidden in magiskhide.
To pass safetynet:
Install busybox (magisk module)
Install MagiskHide Props Config (magisk module)
Reboot
Install terminal emulator for android (app, Google play)
start Terminal emulator and type:
Su (Grant root when prompted)
Props
1
F
Choose your phone model and install fingerprint.
Reboot.
In magisk, enter MagiskHide and hide snapchat.
Done. If you still can't login, clear clear snapchat app data.
Bonus: to get play store certified (after passing safetynet) clear app data for google plat store and google play services.
efex said:
Works without issues for me. Rooted with magisk, safetynet passes and Snap hidden in magiskhide.
To pass safetynet:
Install busybox (magisk module)
Install MagiskHide Props Config
Reboot
Install terminal emulator for android
Type:
Su
Props
1
F
Choose your phone model and install fingerprint.
Reboot.
In magisk, enter MagiskHide and hide snapchat.
Done.
Click to expand...
Click to collapse
That is very weird... I tried a lot of methods including yours..
But I still cant pass safetycheck as you see:
Safetynet:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magiskhide:
Fingerprint:
I have no modules enabled other then
- Busybox for Android NDK
- MagiskHide Props Config
Tried enabling Magisk core only mode with no luck
Also tried with rootcloak and exposed with no luck
XxSUPRAxX said:
That is very weird... I tried a lot of methods including yours..
But I still cant pass safetycheck as you see:
Safetynet:
Magiskhide:
Fingerprint:
I have no modules enabled other then
- Busybox for Android NDK
- MagiskHide Props Config
Tried enabling Magisk core only mode with no luck
Also tried with rootcloak and exposed with no luck
Click to expand...
Click to collapse
If you're running edxposed thats your why, safetynet cannot pass with it. I know there is a module for xposed that fakes the SN result (mostry visually), but that's useless.
If I were you I would actually use a fastboot rom to reset the device and start from scratch. Or msmdtool if that doesn't work, but be prepared to use the fingerprint enrollment fix if you do use that method.
There's just too much apps dependant on Safetynet... Netflix L1, Google Pay, Snap, among others.
efex said:
If you're running edxposed thats your why, safetynet cannot pass with it. I know there is a module for xposed that fakes the SN result (mostry visually), but that's useless.
If I were you I would actually use a fastboot rom to reset the device and start from scratch. Or msmdtool if that doesn't work, but be prepared to use the fingerprint enrollment fix if you do use that method.
There's just too much apps dependant on Safetynet... Netflix L1, Google Pay, Snap, among others.
Click to expand...
Click to collapse
What rom are you running on? and do you have TWRP installed as well?
XxSUPRAxX said:
What rom are you running on? and do you have TWRP installed as well?
Click to expand...
Click to collapse
Right now I'm on OOS11 DP4 (rooted with Magisk and SafetyNet pass with above method). I've used every availabe OOS10 FW since launch with the same setup (MagiskHide Props Config) to pass SafetyNet. I have the European model, IN2023 (8/128GB).
efex said:
Right now I'm on OOS11 DP4 (rooted with Magisk and SafetyNet pass with above method). I've used every availabe OOS10 FW since launch with the same setup (MagiskHide Props Config) to pass SafetyNet. I have the European model, IN2023 (8/128GB).
Click to expand...
Click to collapse
Just tried completely uninstalling exposed with no luck as well. Gotta keep trying to get safety check to work..
I just recall that a read somewhere that magiskhide could not hide the bootloader state anymore which may cause safetynet to fail.
Issue fixed
efex said:
Right now I'm on OOS11 DP4 (rooted with Magisk and SafetyNet pass with above method). I've used every availabe OOS10 FW since launch with the same setup (MagiskHide Props Config) to pass SafetyNet. I have the European model, IN2023 (8/128GB).
Click to expand...
Click to collapse
Ohh god.. noob mistake... I cleared Google Play service cache and now successfully bypassed SafetyNet. Thanks!
XxSUPRAxX said:
Just tried completely uninstalling exposed with no luck as well. Gotta keep trying to get safety check to work..
I just recall that a read somewhere that magiskhide could not hide the bootloader state anymore which may cause safetynet to fail.
Click to expand...
Click to collapse
That hw check (bootloader unlock check) isn't implemented by Google yet, so thats not the issue. It definetly will become an issue when it's implemented, but we're not there yet..
Another reason for fail could be the kernel, it you have some strange one flashed. If that's the case, try Omega Kernel., it always worked for me.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
XxSUPRAxX said:
Ohh god.. noob mistake... I cleared Google Play service cache and now successfully bypassed SafetyNet. Thanks!
Click to expand...
Click to collapse
Oh, thats good! also, if you have started snapchat, clear appdata for it too. And then add it to magiskhide before you start it, and you should be good to go.
I forgot to answer your question about TWRP - I don't use it, dont see the point as system is read only anyway. some apps can also scan for a TWRP or TitaniumBackup folder and "fail" the check only because those exist.. so watch out for that one.
efex said:
That hw check (bootloader unlock check) isn't implemented by Google yet, so thats not the issue. It definetly will become an issue when it's implemented, but we're not there yet..
Another reason for fail could be the kernel, it you have some strange one flashed. If that's the case, try Omega Kernel., it always worked for me.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
Oh, thats good! also, if you have started snapchat, clear appdata for it too. And then add it to magiskhide before you start it, and you should be good to go.
I forgot to answer your question about TWRP - I don't use it, dont see the point as system is read only anyway. some apps can also scan for a TWRP or TitaniumBackup folder and "fail" the check only because those exist.. so watch out for that one.
Click to expand...
Click to collapse
Whenever the bootloader check is implemented will you avoid failing the test by not updating the os or is it a hardware hotfix which you cant avoid?
XxSUPRAxX said:
Whenever the bootloader check is implemented will you avoid failing the test by not updating the os or is it a hardware hotfix which you cant avoid?
Click to expand...
Click to collapse
I don't remember exactly how its implemented, but I think it's a check in play services that Google just need to flip on. We might be able to force basic check somehow, for a while, but it probably won't take long before the advanced check is mandatory to pass..
XxSUPRAxX said:
Ohh god.. noob mistake... I cleared Google Play service cache and now successfully bypassed SafetyNet. Thanks!
Click to expand...
Click to collapse
Dude you are actually a legend, I literally didn't think of this myself after thinking of a bunch of stuff e.g. xposed and magiskhide being disabled for snapchat was causing the problem but still getting the login problems.
With that said, it still won't pass SafetyNet no matter what I do (but this is on a custom ROM on a Moto G6) but Snapchat login now works!!
Related
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
__________________________________
*UPDATED*
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
- Samsung Galaxy S7
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0+/7.0+
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V11.1 & Magisk Manager 4.1
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(If you cannot bypass with Xposed, use Root Switch!)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 4.2.6, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV11.1
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V11.1, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2. (Useless now as Magisk-V11+ has MagiskSU built into the main file and the Super User manager is built into Magisk Manager.)
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "policy", change the permissions of the file from "444" to "440". If MagiskSU pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V11.1. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
If you're still not passing, try disabling USB Debugging in Developer Options!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Great tutorial by the home looks of it! Will try tomorrow morning
RandomUsername02 said:
Great tutorial by the home looks of it! Will try tomorrow morning
Click to expand...
Click to collapse
Thanks. Been using this way to bypass for 2 months now and when I realized not a lot of people knew how to do it, I knew I needed to write a tutorial. It has only not worked with one ROM I tried but worked with a variety of other roms. XtreStoLite, Alexis, CoreUi, MIUI Port etc. Note, I did not originally "find" it but there is no real guide to follow it like how I have written it above.
Thank you for this it works great! Pokémon Go here we come ?
You could also make a "stock" kernel with only the bypass by SultanXDA to make it easier for users
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Goodluck
I've managed to get this and pass safetyNet - any news on Xposed?
Quintz said:
You could also make a "stock" kernel with only the bypass by SultanXDA to make it easier for users
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Goodluck
Click to expand...
Click to collapse
I'll look into it. I'm fairly knew to the whole Android rooting area but I will see if I can do this.
Pedroc1999 said:
I've managed to get this and pass safetyNet - any news on Xposed?
Click to expand...
Click to collapse
I'll have me and a small group of members try to test Xposed and see if it bypasses soon.
xJovs said:
I'll have me and a small group of members try to test Xposed and see if it bypasses soon.
Click to expand...
Click to collapse
Count me in, please DM me if you require testers
Pedroc1999 said:
Count me in, please DM me if you require testers
Click to expand...
Click to collapse
I suggest you join the Telegram group. It's for CoreUi but the members are very helpful in testing. (Link is under credits.)
Worked well for me on Galaxy S7 SM-G930F with SuperMan-Rom 1.18.1
I'll try with Xposed later.
Thanks for sharing this great tutorial!
EDIT : This method with Magisk 10.2 + Xposed does NOT work
very interested to see if xposed can be bypassed
Quintz said:
You could also make a "stock" kernel with only the bypass by SultanXDA to make it easier for users
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Goodluck
Click to expand...
Click to collapse
Would this be the only thing needed to pass SafetyNet? In other words, no need to hide root?
xJovs said:
I'll have me and a small group of members try to test Xposed and see if it bypasses soon.
Click to expand...
Click to collapse
Any luck?
PokemonTotalWar said:
Any luck?
Click to expand...
Click to collapse
Haven't really went and tried it yet. However I don't think it is currently possible. Been busy recently etc etc.
Also, there 'is' supposedly a bug where settings would crash and that would cause issues. If that is the case, I suggest try flashing Magisk V9 as it worked for me as well before.
not work with stock kernel. Any guide with stock kernel?
Hmmm... Twisted Kernel is only for G920F... what is F? Sorry for my ignorance. Tried googling it. Still unclear.
I have Sprint G920P. Anyone know if this would be devastating and irreversible to my phone if I tried it?
Every other method has failed for me and/or is incompatible with my Sprint phone. I'd love to try this and not brick my phone. Thanks!
F is the international variant of the s6, mainly European, might be wrong.
On my Note 4 I am currently running DevBase 3.8 rom, Enforcing RamKernel V5 R1 and Magisk 10.2.
When I enable "Magisk Hide" I don't have to fiddle with any file permissions at all, SafetyNet is passed "out of the box". :good:
Thanks you so much!
Works perfect on Nexus 6p and 5x running latest 7.1.1 stock with Elementalx kernel.
Just had some problems with changing permissions but it passes anyway. Danke!
Figured I'd start an official thread on this subject since it's a little test project of mine.
AS ALWAYS, WHEN MODIFYING YOUR DEVICE, MAKE A NANDROID BACKUP FIRST!
First off, your ROM needs to pass SafetyNet for Samsung Pay to work. Secondly, Samsung Pay looks for certain things in the ROM. If it detects these things, it will error out saying the device is rooted, even if not rooted.
In order to get Samsung Pay working on a rooted ROM, you need to use MagiskHide, hiding the Samsung Pay app. I have used both Magisk 12 and Magisk 13 beta (96f8efc) for testing.
What I've found is it looks for and throw a root error if it finds:
Not passing SafetyNet
Busybox
Test Keys in build.prop
I have found the remedy for the root error is to delete Busybox (typically in system/xbin or system/bin) and editing your build.prop, replacing Test-Keys with Release-Keys.
If you don't want to mess with these steps, here are the ROMs that I've found work and don't work with Samsung Pay out of the box:
- Pure Nexus = SP detects root, even if unrooted.
- SIX = SP detects root, probably because it's based on PN
- SCREWD = SP detects root (don't recall if this passes SafetyNet)
- Resurrection Remix = SP detects root
- Factory = SP works fine unrooted, works fine with root and Magiskhide
- Vanilla ROM = SP works fine unrooted, works fine with root and Magiskhide, works fine with stock kernel
- LineageOS = SP works fine unrooted, works fine with root and Magiskhide, works fine with stock kernel
- Crdoid (LOS Based) = SP works fine unrooted, works fine with root and Magiskhide, works fine with stock kernel
- Dirty Unicorns = SP works fine unrooted, works fine with root and Magiskhide, works fine with stock kernel
2017-06-27 Update:
Updated to Magisk Beta 54e6a79
Installed Osm0sis's Busybox, which installs as a Magisk Module
Installed HEBF Battery Optimizer
Safetynet still passes. Samsung Pay still passes.
If you feel like donating for this knowledge, feel free to do so here: [url]http://paypal.me/BradySewall[/URL]
MrBrady said:
You can remedy the Busybox error by deleting Busybox (typically in system/xbin).
Click to expand...
Click to collapse
Magisk should be able to hide its built-in busybox (up until v12) or a busybox Magisk module (like the one in osm0sis' Odds and ends thread.
Didgeridoohan said:
Magisk should be able to hide its built-in busybox (up until v12) or a busybox Magisk module (like the one in osm0sis' Odds and ends thread.
Click to expand...
Click to collapse
Great! Didn't know osm0sis had a BusyBox Magisk module.
MrBrady said:
Great! Didn't know osm0sis had a BusyBox Magisk module.
Click to expand...
Click to collapse
It's an all-in-one installer. If it detects Magisk it'll install as a Magisk module. It has to be flashed in TWRP.
Spay is working fine with root but the app can't be used since it detected root.
Has anyone manages to by pass it?
TheUndertaker21 said:
Spay is working fine with root but the app can't be used since it detected root.
Has anyone manages to by pass it?
Click to expand...
Click to collapse
That's what the OP is all about.
I'm currently on SIX (Pure Nexus base) and it's working fine. But I had to modify the build.prop, remove BusyBox and make sure the kernel is set to enforcing.
MrBrady said:
Figured I'd start an official thread on this subject since it's a little test project of mine.
Click to expand...
Click to collapse
I'm running the Pixel, I'm going to give this a run on LOS and report back. Thanks for putting this together.
Update:
Switched to a LOS rom, still had test keys in the build prop so I fixed that. Passing safetynet. Used Magisk hide on everything pay and samsung related but it is still detecting for me. Again this is on a Pixel so take my experience with a grain of salt and don't let it stop you from trying on your Nexus.
Omg
I think @MrBrady is a genius. Delete busy box and checked if release keys is there fixed the issue.
Look
This needs to be in gear 3 sections and s8 plus one too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G955F using XDA-Developers Legacy app
Sent from my SM-G955F using XDA-Developers Legacy app
pcriz said:
I'm running the Pixel, I'm going to give this a run on LOS and report back. Thanks for putting this together.
Update:
Switched to a LOS rom, still had test keys in the build prop so I fixed that. Passing safetynet. Used Magisk hide on everything pay and samsung related but it is still detecting for me. Again this is on a Pixel so take my experience with a grain of salt and don't let it stop you from trying on your Nexus.
Click to expand...
Click to collapse
Does LOS include Busybox? I noticed my Samsung Pay updated last night. It's still working though (no root detected).
MrBrady said:
Does LOS include Busybox? I noticed my Samsung Pay updated last night. It's still working though (no root detected).
Click to expand...
Click to collapse
I'm currently running the latest update as well.
Which I updated like 3 mns before I tried your trick lol
You should have some donation link.
You figured out what I was trying to solve for 3 months lol.
Sent from my SM-G955F using XDA-Developers Legacy app
MrBrady said:
Does LOS include Busybox? I noticed my Samsung Pay updated last night. It's still working though (no root detected).
Click to expand...
Click to collapse
I didn't see BusyBox in system/xbin/
TheUndertaker21 said:
I'm currently running the latest update as well.
Which I updated like 3 mns before I tried your trick lol
You should have some donation link.
You figured out what I was trying to solve for 3 months lol.
Sent from my SM-G955F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I too was trying to figure out the culprit for months and felt "stuck" to sticking with ROMs I'd prefer not to use. It's a cat-and-mouse game with the manufacturers, but I'm glad we're ahead of the curve for now.
If anyone wants do donate, you're welcome to do so here: http://paypal.me/BradySewall
pcriz said:
I didn't see BusyBox in system/xbin/
Click to expand...
Click to collapse
There are a few different places Busybox can live. I don't know all of them off the top of my head, but I'd suggest using a root file manager and search for Busybox. Alternatively, you can look in system/bin or system/xbin or /bin. I think sometimes it can be in the /vendor folder (or subfolder) as well.
MrBrady said:
There are a few different places Busybox can live. I don't know all of them off the top of my head, but I'd suggest using a root file manager and search for Busybox. Alternatively, you can look in system/bin or system/xbin or /bin. I think sometimes it can be in the /vendor folder (or subfolder) as well.
Click to expand...
Click to collapse
Yeah I searched didn't find busybox. I also missed one of the callouts for test keys, fixed that but no dice.
I will flash Dark Rom + Franco Kernel + Magisk, will test on Gear S3 and report here
It is also worth trying iSu:
https://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
Use it instead of Magisk on LOS-based roms.
Had a strange issue yesterday and unfortunately didn't take a scientific approach to it.
Installed an older May security release of Blackbird kernel (went from June or May) and also lowered my screen resolution to 1080 (makes my phone run smoother).
I think one of those things borked Samsung Pay. SP on the phone didn't report any issues but when I open it on the watch, it shows my credit card, then has an alert saying "Contact Customer Service) or something along those lines.
I undid both the things mentioned above, deleted my card, readded the card (called bank to verify) and all is good again.
Even updated to the latest Magisk beta released this morning and things are fine still.
Tried dark rom + Franco kernel + magisk 12.0 with magisk hide but safety net didn't pass. Uninstalled 12.0 and installed beta 13, safety net passed and could run Android pay too but Samsung Pay detected root even with busybox disabled and Magisk hide enabled. Any workarounds available?
raikkoni27 said:
Tried dark rom + Franco kernel + magisk 12.0 with magisk hide but safety net didn't pass. Uninstalled 12.0 and installed beta 13, safety net passed and could run Android pay too but Samsung Pay detected root even with busybox disabled and Magisk hide enabled. Any workarounds available?
Click to expand...
Click to collapse
Make sure BusyBox is deleted from the ROM, not just disabled in Magisk. Make sure build.prop says Release Keys not Test Keys.
MrBrady said:
Make sure BusyBox is deleted from the ROM, not just disabled in Magisk. Make sure build.prop says Release Keys not Test Keys.
Click to expand...
Click to collapse
I installed busybox to check if it's installed or not, it says it isn't. I anyway clicked on uninstall in the app. Also, could you guide me for replacing test keys with release keys? Do I just need to replace test with release in build prop?
Edit: changed build prop to release keys and now Samsung Pay updated to 1.5 and doesn't detect root! Thanks a ton! :highfive:
How to root Moto G5 very easy on LineageOS
Since iv been reading some very strange ways people have been rooting this device I will tell you how to root this phone very easily if you are on LineageOS
This is for LineageOS 14.1 only
For LineageOS 15 please use Magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements
Unlocked Bootloader
TWRP Recovery
LineageOS rom or based on LineageOS rom
SU zip in attachment
How To
Once you have installed LineageOS (or any rom that is based on it)
Go into TWRP Recovery
Install Zip
Select addonsu-14.1-arm-signed.zip
Wait till flash has finished
Wipe Cache
Restart Phone
Once phone has restarted do the following
Open phone settings
Go to about phone
Keep pressing on build number until it tells you that you are a developer
Go back to phone settings
Select Developer Options
Under Root access select Apps and ADB
Done - you now have a rooted phone
Don't install any other superuser/supersu app as it may conflict
Is wipe cache really needed? I don't want to setup all my apps for the third time this week (root on stock, then installing LineageOS).
NM99 said:
Is wipe cache really needed? I don't want to setup all my apps for the third time this week (root on stock, then installing LineageOS).
Click to expand...
Click to collapse
wiping cache does not delete any app data or removes any apps
Cache is a temp folder that apps use so things can load quicker - wiping the cache is always recommended after flashing any zip (the option wipe cache/dalvik will appear after flashing zip)
What you are talking about is data - wiping data would remove all user data/apps and at no point do you need to wipe data in this process
TheFixItMan said:
wiping cache does not delete any app data or removes any apps
Cache is a temp folder that apps use so things can load quicker - wiping the cache is always recommended after flashing any zip (the option wipe cache/dalvik will appear after flashing zip)
What you are talking about is data - wiping data would remove all user data/apps and at no point do you need to wipe data in this process
Click to expand...
Click to collapse
Did I mess up that bad? Jesus.
Well, sorry for that. Thanks for correcting me.
It would be interesting to know who the author of the SU is?
No_Signal said:
It would be interesting to know who the author of the SU is?
Click to expand...
Click to collapse
It's the lineageos su addon so lineageos
TheFixItMan said:
It's the lineageos su addon so lineageos
Click to expand...
Click to collapse
Appreciated, thank you TheFixItMan!
Works f... great
Have you ever come across "Manage root accesses" being greyed out in Dev Options ?? After flashing add-on su downloaded from this post and also Los site
Am running Colt OS with LOS Kernal
m-rufflesmcghie said:
Have you ever come across "Manage root accesses" being greyed out in Dev Options ?? After flashing add-on su downloaded from this post and also Los site
Am running Colt OS with LOS Kernal
Click to expand...
Click to collapse
Probably who ever built the rom hasn't used lineageos sources for rooting/settings
You will have to take it up with them
ok - i get root with this no problem, but i need superSU (standard, not addonSU) for foldermount that doesn't like the addonSU.
what to do?
zdoe said:
ok - i get root with this no problem, but i need superSU (standard, not addonSU) for foldermount that doesn't like the addonSU.
what to do?
Click to expand...
Click to collapse
Supersu zip - Flash in twrp
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
i had already in fact tried this very ZIP. now i tried it a 2nd time. flash completes, but with RAMdisk errors: Extracting RAMdisk -- failure, aborting.
and booting with it, the system boots, but i don't have root.
are you saying you've succeeded with this?
zdoe said:
i had already in fact tried this very ZIP. now i tried it a 2nd time. flash completes, but with RAMdisk errors: Extracting RAMdisk -- failure, aborting.
and booting with it, the system boots, but i don't have root.
are you saying you've succeeded with this?
Click to expand...
Click to collapse
On previous versions of lineageos 14.1 yes (but not tried it for ages as didn't use it for my root so kernel may have changed)
If you are using lineageos 15 you need to use magisk
k. i don't really fancy going back in history on lineageos...
unfortunately i can only use superSU as that's what foldermount expects to see. and the developer for it is AWOL, so he won't be fixing this anytime soon.
or - do you know of any alternatives to foldermount?
or2 - perhaps the lineageos developer could make it compatible with superSU?
zdoe said:
k. i don't really fancy going back in history on lineageos...
unfortunately i can only use superSU as that's what foldermount expects to see. and the developer for it is AWOL, so he won't be fixing this anytime soon.
or - do you know of any alternatives to foldermount?
or2 - perhaps the lineageos developer could make it compatible with superSU?
Click to expand...
Click to collapse
I would advise using lineageos 15 & then using magisk
The chances are there is a magisk module that will do the same/similar job
Linking things to sd card isn't really advised - it slows the device down & makes it laggy - the g5 has 16gb internal storage so what benefit are you looking for as just installing apps I can't see anyone filling up internal storage & anything else can go on sd card like music pictures downloads etc
TheFixItMan said:
I would advise using lineageos 15 & then using magisk
The chances are there is a magisk module that will do the same/similar job
Click to expand...
Click to collapse
is 15 better than 14.1? there does seem to be magisk module that attempts to do this, but seemingly not ready for prime time yet.
TheFixItMan said:
Linking things to sd card isn't really advised - it slows the device down & makes it laggy - the g5 has 16gb internal storage so what benefit are you looking for as just installing apps I can't see anyone filling up internal storage & anything else can go on sd card like music pictures downloads etc
Click to expand...
Click to collapse
right, it's no longer about space. it's about: setting up a removable hard drive (=sdcard), and with it, being able to houseclean for misbehaving apps. in my case it's mostly wechat, that will fill any amount of space and not provide tools to keep it operational. and yes, i got a fast sdcard, speed shouldn't be an issue.
zdoe said:
is 15 better than 14.1? there does seem to be magisk module that attempts to do this, but seemingly not ready for prime time yet.
Click to expand...
Click to collapse
Well it's oreo as opposed to nougat
Only main bug is camera apps crash after taking 1 pic but I'm sure that will be fixed in next build
Since I don't use apps like that I can't recommend anything
Thank you for creating this. I tried to root Moto g5 lineage 14.1 using SuperSU. Unfortunately it doesn't work. I tried the latest beta 2.82, 1.97, etc.
Although magisk works, it wasn't as simple as SuperSU
So this app is great substitute. I hope you can make it work for lineage 15 also
TheFixItMan said:
......
Under Root access select Apps and ADB
Done - you now have a rooted phone
Click to expand...
Click to collapse
at the end of the process,
what if i disable now dev options(toggle to deactivate) with the root access apps and adb allowed(as you described),
will i remain root?
anyway, how come i dont find any supersu app installed? did i do something wrong then? or is the addonsu-14.1-arm-signed integrated by flashing it in custom recovery?
Hey everyone!!
Greetings from my side. We were trying hard to get 100% working oneplus dialer and messaging app in oneplus 8t. and Yes, We have successfully done it.
I am very happy to share the guide with you all
WITHOUT ANY ROOT METHOD: (Thanks to some anonymous help for non-rooted )
- oos11 required
-Please download this OnePlus Dialer: Link
-Install it and open it, set as default.
-Give all required permissions only.
-Enjoy guys, this dialer app has no bugs at all.
-If you want to use OnePlus contacts and message app please download them from old method below, these two has 1 minor bug which is not noticeable in daily life, So enjoy them at fullest without rooting your device.
Root methods below:
Requirements:
- oos11
-Root
-Magisk
- OnePlus Apps v1.0 Module
-Your own responsibility before following the all steps
To root your device with magisk please follow this amazing guide by @DroidFreak32 :
- https://forum.xda-developers.com/oneplus-8t/how-to/guide-how-to-root-oneplus8t-kb2001-t4178675
NEW METHOD(Recommended): Big thanks to @shadowstep for your contribution and providing us this amazing module.
1. Download OnePlus Apps v1.0 Module from the above link.
2. Open Magisk App and select it to flash.
3. You will get Option which app you want to install from all three apps(Contacts, Dialer, and Messaging).
Because few users do not want to install all of them together and only want to install a particular app.
4. You can select them using volume keys: Volume Up for Yes, Volume Down for No. (Refer Screenshot for better understanding).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Reboot and voila, Apps has been installed successfully.
6. Please make them default apps and give all required permissions.
7. Clear Catch for dialer/messages/contact app before using them.
8. You are ready to go. Thank you.
Points to be noted:
-These apps are not permanently stored in the system storage because we cannot write in the android 11 system, So do not remove/disable magisk. Wait for TWRP to come up.
- No need to disable Module while doing OTA.
-You will not face any issues while using these apps. Reboot will not remove these apps unless you remove/disable the magisk module manually.
- If OnePlus dialer comes with your 8T and call recording is locked in your country, please download this app and enable it without even rooting your device. (This point is not for google dialer users).
- Same as other OnePlus phones, you can see the recording files in the dialer settings itself (Find out screenshots below) OR
Path: android/data/com.oneplus.communication.data/files/Record/PhoneRecord
OLD METHOD:
Please download the required dialer apk from this link:
https://drive.google.com/drive/folders/1814cAPa4y1yP2lJfvIQwkZTmoajxuEXi?usp=sharing
If you need messaging and contact app as well. I have shared it in the above link.
- Download the Busybox Module in magisk
Open the hamburger menu again like before, then head to "Downloads." In the search bar, do a search for the term "busybox" to locate the next module for this guide. Tap the download arrow once, then go to "Install" to start the install process. Once finished, tap the back arrow to return to the previous screen.
-Download the App Systemizer Module
In the search bar for the "Downloads" section, do another search for the term "app systemizer," then repeat the process like before to get the module installed. Once this one finishes installing, you can go ahead and hit the "Reboot" button at the bottom to restart your device.
-Install the Terminal App
To use the App Systemizer module you downloaded in Step 3, you'll first need to access a terminal. The module is entirely command-line based, which is why you also needed the Busybox module — it allows you to use more advanced commands with superuser permissions.
Play Store Link: Termux
-Store the dialer in some of your specific location which is provided in the above google drive link.
-Systemize the OnePlus Phone App
Open the Termux app, then type in the command below, followed by: (Please do not use " in all steps below commands)
1. "su"
When you're prompted to do so, tap the "Grant" option to give Termux full superuser privileges to your system.
2. Now that your superuser permissions have been granted, type in the next command followed by enter.
"systemize"
This command will immediately launch the App Systemizer module interface for the first time. This is easily the best way you can turn any user-installed app into a system app with minimal effort.
3. Choose option 3 only which is via .apk (Choice 1 & 2 not working in our 8T). Choice 3 was the best way to make the dialer work in 8T.
4. Now give the apk location. For me, I have placed the apk directly into storage. Enter the following line.
"/storage/emulated/0/Phone_Dialer.apk"
5. Now type 2 to install to /system/priv-app and then reboot the device.
6. Please make oneplus dialer as default phone dialer. It is very important step.
7. Now app has installed successfully. Please disable google dialer for now.
8. Please give all permissions to oneplus dialer from phone settings(calls logs,contacts,files and media,microphone, phone,SMS)
If you are facing any issue in using systemizer app, please prefer this link . This link also contains screenshots for first few steps.
If you have followed all the steps carefully, You will have a working oneplus dialer with call recording. You can enable call recording from dialer settings.
I am attaching the screenshots for your reference and I will keep updating the guide for better understanding, so please do not create multiple guides with the same steps.
It is 100% tested and working fine. If you will face any bug, Please let everyone know in the comments below.
Telegram: t.me/OnePlus8T5G
Special thanks to: @sansanc , Abhay Singh Gill, KunalShah and @Bewildered Wolf
It works folks! No way i would keep using google dialer. Everything works, even recording. Great stuff!
All working here
App systemize is working for you? Mine wasn't showing apps
I successfully enabled call recording using jOnePlus Tools. No root required, no steps. Just hit the enable switch. Is this different somehow?
Also, shouldn't this guide be in the ONEPLUS 8T GUIDES, NEWS, & DISCUSSION section?
Not working on my KB2007 TMO version
zeusofyork said:
App systemize is working for you? Mine wasn't showing apps
Click to expand...
Click to collapse
Yes, that's why you need to install via .apk. Very easy, you don't even need to start systemize interactively, just do: stemize -d /storage/emulated/0/contacts.apk
Substitute contacts.apk for another name/apk.
BTW, this magisk module has been discontinued. So the app list bug won't be fixed, unless soneone picks the development up.
---------- Post added at 01:56 ---------- Previous post was at 01:54 ----------
jwarrior319 said:
Not working on my KB2007 TMO version
Click to expand...
Click to collapse
What steps did you do? What happens?
sansanc said:
Yes, that's why you need to install via .apk. Very easy, you don't even need to start systemize interactively, just do: stemize -d /storage/emulated/0/contacts.apk
Substitute contacts.apk for another name/apk.
BTW, this magisk module has been discontinued. So the app list bug won't be fixed, unless soneone picks the development up.
---------- Post added at 01:56 ---------- Previous post was at 01:54 ----------
What steps did you do? What happens?
Click to expand...
Click to collapse
I just dont ever get the call recording option. My tmo one came preinstalled with the oneplus dialer as well. I haven't found any combination of things to make it work. I even tried the google dialer mod
Was waiting for this. Will try and report back ?
---------- Post added at 02:24 AM ---------- Previous post was at 02:23 AM ----------
jwarrior319 said:
I just dont ever get the call recording option. My tmo one came preinstalled with the oneplus dialer as well. I haven't found any combination of things to make it work. I even tried the google dialer mod
Click to expand...
Click to collapse
It's a region thing as far as i know. Even global models might not have it.
Thanks for trying. We have tested it and it's working fine. If anyone have want to add some points please share your feedback. I will add it in the guide.
AlwaysLucky said:
I successfully enabled call recording using jOnePlus Tools. No root required, no steps. Just hit the enable switch. Is this different somehow?
Also, shouldn't this guide be in the ONEPLUS 8T GUIDES, NEWS, & DISCUSSION section?
Click to expand...
Click to collapse
Did you have OnePlus dialer or Google dialer ?
zeusofyork said:
App systemize is working for you? Mine wasn't showing apps
Click to expand...
Click to collapse
as sansanc said. You have to choose .apk choice 3. First two options will not work to show app list in 8T.
jwarrior319 said:
I just dont ever get the call recording option. My tmo one came preinstalled with the oneplus dialer as well. I haven't found any combination of things to make it work. I even tried the google dialer mod
Click to expand...
Click to collapse
Download joneplustools from the playstore! It allows you to enable call recording in the oneplus dialer
zeusofyork said:
Download joneplustools from the playstore! It allows you to enable call recording in the oneplus dialer
Click to expand...
Click to collapse
This only works if you already have OnePlus dialer installed.
Shavi_Suri said:
This only works if you already have OnePlus dialer installed.
Click to expand...
Click to collapse
He said in his post that his phone, like mine, came with the oneplus dialer... We're both on T-Mobile and that is why we have it. Sooooooo yes.... It will.
zeusofyork said:
He said in his post that his phone, like mine, came with the oneplus dialer... We're both on T-Mobile and that is why we have it. Sooooooo yes.... It will.
Click to expand...
Click to collapse
Yes...
zeusofyork said:
He said in his post that his phone, like mine, came with the oneplus dialer... We're both on T-Mobile and that is why we have it. Sooooooo yes.... It will.
Click to expand...
Click to collapse
Sweet it works.
For call recording, i use the apk from here:
https://forum.xda-developers.com/oneplus-5/themes/app-enable-call-recording-boot-t3634292
Now, i couldn't find an alternative for systemize. Android 11 comes with /system read only. Remounting it read-write doesn't work. That means that you just can't manually copy the .apk to /system/priv-app like before. That's why apps like Link2SD don't work anymore. So i think we are stuck with systemize.
If you disable systemize on magisk, the apps you installed with it, will disappear. But will appear again if re-enabling it. Reboot needed. If you delete the module, the apps will be gone for good.
Not sure about this, but i think magisk modules need to be disabled when udating the ROM. Otherwise, it boot loops/freezes. So, don't forget about that.
Messages with a dark background also works. Including blocking settings, but it needs to be a system app for that.
Contacts also works, But importing/exporting don't. Call logs permision can't be set. And permissions can't be edited manually because /system is read only.
Maybe a custom kernel can override this read only limitation?
We need for Oneplus to put these apps on play store!
sansanc said:
For call recording, i use the apk from here:
https://forum.xda-developers.com/oneplus-5/themes/app-enable-call-recording-boot-t3634292
Now, i couldn't find an alternative for systemize. Android 11 comes with /system read only. Remounting it read-write doesn't work. That means that you just can't manually copy the .apk to /system/priv-app like before. That's why apps like Link2SD don't work anymore. So i think we are stuck with systemize.
If you disable systemize on magisk, the apps you installed with it, will disappear. But will appear again if re-enabling it. Reboot needed. If you delete the module, the apps will be gone for good.
Not sure about this, but i think magisk modules need to be disabled when udating the ROM. Otherwise, it boot loops/freezes. So, don't forget about that.
Messages with a dark background also works. Including blocking settings, but it needs to be a system app for that.
Contacts also works, But importing/exporting don't. Call logs permision can't be set. And permissions can't be edited manually because /system is read only.
Maybe a custom kernel can override this read only limitation?
We need for Oneplus to put these apps on play store!
Click to expand...
Click to collapse
Thanks for the valuable feedback on this. Will pin this comment and will update the guide.
Thanks for this! I gave up after seeing that Terminal systemizer App list wasn't showing up, didn't think on trying to install an apk directly
Sent from my KB2005 using Tapatalk
I installed magisk but my bank app detecting root. I passed SafetyNet and can install Netflix in Google Play. But somehow bank app detects root or unlocked bootloader. Can somebody help?
Device: OnePlus 8 Pro / OOS11_OB7 Android 11 / Magisk Canary (f152b4c2,22005) / Kernel( Omega & Stock both tried. )
Installed Magisk Modules: "ADB&Fastboot for Android NDK / MagiskHide Props Config / OOS Native Call Recording Enabler / Systemless Host"
Root obtained with boot.img patching method, not pre-patched images. I patched my own img. Passing safetynet, magisk app hidden. I can download Netflix in Google Play as I know you can't download it with not safetynet pass.
App: "Yapıkredi Mobil (com.ykb.android)"
App is soft detecting. I can login but cannot do specific abilities in app, they are disabled. App says we cannot provide this features unless we confirm you are on secure device. FYI if safetynet fails apps giving there is root popup but in this circumstances it is just soft disabling some features.
@VD171 hi. I used your app called "VD Infos" and I'm getting 4 root detection errors. Do you have any ideas about fixing them? It gives emulator tags. I used "Magisk Hide Props Config" after seeing this emulator thing but still fails.
Code:
================
-> Quantities
Total Time: 23 minutes and 57 seconds.
Total of tries: 6,062,778.
Total found: 4.
* Emulator detected.
================
================
-> ROOT
#1. [* EMULATOR]: [ro.kernel.qemu.gles]: 0
#2. [Found]: /system/lib/libsigchain.so
#3. [Found]: /system/lib64/libsigchain.so
#4. [Found]: com.dolby.daxservice.DaxApplication
================
I tried XPrivacyLua method got from the huge "Mandiri Online Thread"
I tried this module and it is failing. And I cannot permit "use tracking" ability, app crashes if I enable it.
Code:
1. Install magisk, reboot
2. Install Riru module, reboot
3. Install LSPosed module, reboot
4. Instal LSposed manager and xprivacylua, (I need reboot here)
6. Activate xprivacylua module in LSposed manager, reboot
7. Open LSposed manager module list, select xprivacylua, tick Mandiri Online.
8. Open xprivacylua app, search Mandiri Online, restrict "get applications" & "use tracking"
9. May get "something wrong" message, just tap back and reopen Mandiri Online (don't force close)
10. Done
Riru-Unshared method tried and also failed.
Tried vvb2060/MagiskDedector and it says "init.rc has been modified by magisk" this app also can detect root."
emirefek said:
I tried XPrivacyLua method got from the huge "Mandiri Online Thread"
I tried this module and it is failing. And I cannot permit "use tracking" ability, app crashes if I enable it.
Code:
1. Install magisk, reboot
2. Install Riru module, reboot
3. Install LSPosed module, reboot
4. Instal LSposed manager and xprivacylua, (I need reboot here)
6. Activate xprivacylua module in LSposed manager, reboot
7. Open LSposed manager module list, select xprivacylua, tick Mandiri Online.
8. Open xprivacylua app, search Mandiri Online, restrict "get applications" & "use tracking"
9. May get "something wrong" message, just tap back and reopen Mandiri Online (don't force close)
10. Done
Riru-Unshared method tried and also failed.
Click to expand...
Click to collapse
Try it :
7. Open LSposed manager module list, select xprivacylua, tick Mandiri Online, reboot
same here... suddenly the bank app stopped working.... is was working fine before
emirefek said:
I tried XPrivacyLua method got from the huge "Mandiri Online Thread"
I tried this module and it is failing. And I cannot permit "use tracking" ability, app crashes if I enable it.
Code:
1. Install magisk, reboot
2. Install Riru module, reboot
3. Install LSPosed module, reboot
4. Instal LSposed manager and xprivacylua, (I need reboot here)
6. Activate xprivacylua module in LSposed manager, reboot
7. Open LSposed manager module list, select xprivacylua, tick Mandiri Online.
8. Open xprivacylua app, search Mandiri Online, restrict "get applications" & "use tracking"
9. May get "something wrong" message, just tap back and reopen Mandiri Online (don't force close)
10. Done
Riru-Unshared method tried and also failed.
Click to expand...
Click to collapse
I tried mandiri app today, but I can't run it because it says there is no wifi connection and keeps loading only.
Even hiding root or not.
emirefek said:
I tried XPrivacyLua method got from the huge "Mandiri Online Thread"
I tried this module and it is failing. And I cannot permit "use tracking" ability, app crashes if I enable it.
Code:
1. Install magisk, reboot
2. Install Riru module, reboot
3. Install LSPosed module, reboot
4. Instal LSposed manager and xprivacylua, (I need reboot here)
6. Activate xprivacylua module in LSposed manager, reboot
7. Open LSposed manager module list, select xprivacylua, tick Mandiri Online.
8. Open xprivacylua app, search Mandiri Online, restrict "get applications" & "use tracking"
9. May get "something wrong" message, just tap back and reopen Mandiri Online (don't force close)
10. Done
Riru-Unshared method tried and also failed.
Click to expand...
Click to collapse
I can't get mandiri app working perfectly.
But I can bypass the root detection.
If root is detected, the app closes.
But if root is not detect, the app keeps open.
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After:
Don't know about Yapıkredi but Shamiko Module fixes Bonusflaş (Detecting root disables NFC payments and right now with shamiko, i can use NFC payments.)
There's a way to use banking apps with safetynet passing and an unlocked bootloader. Some banking apps don't work even though you pass safetynet as they detect if your bootloader is unlocked.
I found an app that allows banking apps to work by making a parallel app and this app is called island. This app can be used to clone banking apps and it solved the problem! Try it out! Disclaimer: Only Island can "bypass" this
Here's the play store link https://play.google.com/store/apps/details?id=com.oasisfeng.island&hl=en_GB&gl=US
Extreme_Ninja2099 said:
There's a way to use banking apps with safetynet passing and an unlocked bootloader. Some banking apps don't work even though you pass safetynet as they detect if your bootloader is unlocked.
I found an app that allows banking apps to work by making a parallel app and this app is called island. This app can be used to clone banking apps and it solved the problem! Try it out! Disclaimer: Only Island can "bypass" this
Here's the play store link https://play.google.com/store/apps/details?id=com.oasisfeng.island&hl=en_GB&gl=US
Click to expand...
Click to collapse
Cloning an app is not a solution.
There are many ways to detect and prevent it easily.
VD171 said:
Cloning an app is not a solution.
There are many ways to detect and prevent it easily.
Click to expand...
Click to collapse
Have u tried it? Obvs u need to pass safetynet first and then if the banking app still doesn't work then try my suggested method. It works with me which was why I suggested it. (Safetynet passed, banking app detected bootloader unlocked -> used island -> created a clone app + using work profile -> managed to to set it up + worked)
Extreme_Ninja2099 said:
Have u tried it? Obvs u need to pass safetynet first and then if the banking app still doesn't work then try my suggested method. It works with me which was why I suggested it. (Safetynet passed, banking app detected bootloader unlocked -> used island -> created a clone app + using work profile -> managed to to set it up + worked)
Click to expand...
Click to collapse
Obviously it may works on apps which does NOT checks integrity and/or signature.
I just said, it is NOT a safely recommended way for banking apps.
Extreme_Ninja2099 said:
Have u tried it? Obvs u need to pass safetynet first and then if the banking app still doesn't work then try my suggested method. It works with me which was why I suggested it. (Safetynet passed, banking app detected bootloader unlocked -> used island -> created a clone app + using work profile -> managed to to set it up + worked)
Click to expand...
Click to collapse
I wrote a guide about how to bypass the detection for unlocked bootloader.
Enjoy
[GUIDE][MTK] How to bypass detection for UNLOCKED BOOTLOADER ?
WARNINGS: First of all you should BACKUP IMEI. Remember to NEVER touch the NVRAM. People who does NOT backup imei or touches the NVRAM, are susceptible to the loss of IMEI. If you try to share NVDATA between different devices, it may cause...
forum.xda-developers.com
VD171 said:
I wrote a guide about how to bypass the detection for unlocked bootloader.
Enjoy
[GUIDE][MTK] How to bypass detection for UNLOCKED BOOTLOADER ?
WARNINGS: First of all you should BACKUP IMEI. Remember to NEVER touch the NVRAM. People who does NOT backup imei or touches the NVRAM, are susceptible to the loss of IMEI. If you try to share NVDATA between different devices, it may cause...
forum.xda-developers.com
Click to expand...
Click to collapse
We're in the Oneplus 8 pro XDA thread. Your guide works for the redmi Note 9 which is a different device and requires the user to wipe their data and the method requires a partition the 8 pro doesn't have (SECCFG). Doesn't seem worth it just to bypass unlocked bootloader detection for some banking apps that detect it. Like if my suggested method somehow doesn't work well then you're better off locking your bootloader
Extreme_Ninja2099 said:
We're in the Oneplus 8 pro XDA thread. Your guide works for the redmi Note 9 which is a different device and requires the user to wipe their data and the method requires a partition the 8 pro doesn't have (SECCFG). Doesn't seem worth it just to bypass unlocked bootloader detection for some banking apps that detect it. Like if my suggested method somehow doesn't work well then you're better off locking your bootloader
Click to expand...
Click to collapse
Does not matter the section.
The question has relevance for all Android devices.
If I didn't help you, just ignore it.
But, as I said, clonning app makes easily to inject malicious codes to the app.
So, clonning app is NOT a better way for banking apps.
I just warned, each one does what he/she wants.
Oh man, Guys and Girls.... It's very very stupid and it Highly Risky to Root a Phone and use a Bank App! Does Anyone knows what Root are? Knows anyone of you what Rooting Means? Full, Yes Full Administration Rights in your Phone and EVERY App they want to Steal some Kind of Information from You can did that with Your Permission as Su/Admin! If someone steals Money from your Banking Account! Don't cry at your Bank and Say that you Screwed from a Phishing App or YOUR STUPIDITY! No Bank would pay Back only One Cent of the Stolen Money! If anyone want to Pay via App please Buy a Phone, a Ugly Phone Without SU Permission!! Android is Linux! And if you gave them Root. Know what you did and don't ask why the Phone is Checks that Permits and why it's checks that!?! So many of you People buys Phones for over thousand Euro or Dollars and then Rooting??? Why buy a Phone for that much Money and Unlocks the Security? It's obviously extreme Kind of Stupidity...
2chillen said:
Oh man, Guys and Girls.... It's very very stupid and it Highly Risky to Root a Phone and use a Bank App! Does Anyone knows what Root are? Knows anyone of you what Rooting Means? Full, Yes Full Administration Rights in your Phone and EVERY App they want to Steal some Kind of Information from You can did that with Your Permission as Su/Admin! If someone steals Money from your Banking Account! Don't cry at your Bank and Say that you Screwed from a Phishing App or YOUR STUPIDITY! No Bank would pay Back only One Cent of the Stolen Money! If anyone want to Pay via App please Buy a Phone, a Ugly Phone Without SU Permission!! Android is Linux! And if you gave them Root. Know what you did and don't ask why the Phone is Checks that Permits and why it's checks that!?! So many of you People buys Phones for over thousand Euro or Dollars and then Rooting??? Why buy a Phone for that much Money and Unlocks the Security? It's obviously extreme Kind of Stupidity...
Click to expand...
Click to collapse
If you know what you are doing, NO.
It is not highly risky.
I root my device because I paid for the device, I bought the device, I didn't rent it.
I have 25 android devices and all them are rooted.
I'm using Fedora Linux in my personal computer for more than 11 years.
So, rooting is not a problem if you know what you are doing.
Edit: At this moment, I have exactly 49 banking apps installed on my main device. Some apps are from the same bank, just an alternate app for credit card management. They are ALL working perfectly. Some of them have more protection than others. But if you are root, you can bypass all types of protections. Capitalism is a lot of fun.
Bruh just use Shamiko and be done with it...
Extreme_Ninja2099 said:
We're in the Oneplus 8 pro XDA thread. Your guide works for the redmi Note 9 which is a different device and requires the user to wipe their data and the method requires a partition the 8 pro doesn't have (SECCFG). Doesn't seem worth it just to bypass unlocked bootloader detection for some banking apps that detect it. Like if my suggested method somehow doesn't work well then you're better off locking your bootloader
Click to expand...
Click to collapse
Thanks for the heads up !
Do you have Realme device as I cannot get through ( detected my device is mofified ... and kick me out during opening the banking apps )
My Realme 7 pro is done the old ways , Rooted, Magisk , Hide Magisk, MagiskHide Props Config, Riru , Universal safetyNet fix, LSposed , XProvacylua.....etc. (( Safetynet is passed !! ))
Wonder if anymore new methods nowadays.
** My Samsung A71 is okay ( with above procedures done ) opening the same banking apps.
Thank you very much., edmond0