(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!
Related
It's released
Thread link- here
I got it working..
Post #6
May be we should make a list of what modules are currently working on our lollipop moto e to keep a track.
Some one reported that xinternal SD is working.
This type of list will help all. What do u say??
Any one who got a module working can report here.
I read the comments youtube adway was working,,I didn't tested it on my moto e,will report and update the status soon..
Sure if anyone finds it can report I don't have any problems..
Not working on moto e 5.0.2 tried it yeterday, it flashes correctly via twrp but when u try to install apk it never installs, system becomes very very laggy.
iTudorS said:
Not working on moto e 5.0.2 tried it yeterday, it flashes correctly via twrp but when u try to install apk it never installs, system becomes very very laggy.
Click to expand...
Click to collapse
That's sad,I will try it on mine and report here..
Edit:Not working op updated..
Wait..what?!?
{
"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"
}
It isnt working.... ie. framework not installing
and side effects are:
-All my apps on sd went missing(after restoring system partition i got it back)
-storage space was low it asked to clear out 250mb of space from system.....
-Lagged (maybe due to the storage issue in system)
anyway some 1 posted this:
Working on my OnePlus one. It wasn't working at first, but I got it by doing this
1. Flash framework
2. Install apk
3. Go back to recovery and flash the framework again
Click to expand...
Click to collapse
and other post
Using nexus 5 , purity ROM (lollipop version) tried two ways:
way 1:
1. flash the zip
2.install apk
shows xposedbridge.jar active , app_process doesnt
way 2:
1.install apk
2.mount system
3.flash zip
shows xposedbridge.jar active , app_process doesnt
i understand many people have it , but wrote it so you will save some time doing the steps i did.
EDIT - SOLUTION FOUND :
the solution is to install random modul (i choose chromepie) apply it and reboot - have fun using xposed
Click to expand...
Click to collapse
Can some1 try this?
It wasn't working when I first installed,I got full storage and phone lagged...
what I do to get it working was to reboot to recovery and factory reset,after reset I rebooted the phone,it took about 10-15 mins,after booting up I rebooted to recovery and flashed the supersu then xposed zip again,after reboot everything was normal no storage space error or anything,I installed the apk and all is working fine as of now..
gaurav2009 said:
It wasn't working when I first installed,I got full storage and phone lagged...
what I do to get it working was to reboot to recovery and factory reset,after reset I rebooted the phone,it took about 10-15 mins,after booting up I rebooted to recovery and flashed the supersu then xposed zip again,after reboot everything was normal no storage space error or anything,I installed the apk and all is working fine as of now..
Click to expand...
Click to collapse
Thanks mate for reporting. Even i had the lag issue. All apps on sd disappeared and a notification of 250 mb storage or something like that poped up and i went back to KK. I'll flash lollipop tomorrow. And report it here.
some modules that work good right now:
http://www.xda-developers.com/xposed-modules-to-install-right-now-on-lollipop/
App Settings [Lollipop Alternative by rovo89] [1]:
This was by far one of my favorite Xposed modules back when I wasn’t running Lollipop, and certainly the one I missed the most. With this baby you can change DPI per app (which allows you to keep whatever DPI you want on the rest of the SystemUI), as well as the application’s font scale, immersive mode, RAM pinning, and insistent notifications for those that don’t want to miss their valentine’s texts (and lose their heads over it).
Xposed GEL Settings [1][2]:
For those fans of the “pure Google experience”, this module can let you further customize your Google Launcher by letting you hide the search bar or individual applications, change grid, icon and text sizes, remove labels and more. It doesn’t make it quite as flexible as Nova, but it’s definitely a good module to have for those that love the Google integration of their launcher, and the cleanness and optimization of it.
RootCloak [1]:
Some apps detect root and either prevent access or limit your features as a preemptive method for security. While it is understandable some might want to further fortify their application, us XDA tinkerers can be left out of services due to this. This module hides root for the apps you choose, simple as that. We can’t specifically tell you what to use this module for, but if you’ve had problems like this before, look no further.
Advanced Power Menu+ [1]: This module lets you customize the power menu of your phone to add or remove items in any order you want. There are extra reboot options (soft boot, recovery boot, bootloader), a screenshot option, a quick-dial to call whoever, some connection toggles and a handy flashlight. I always have advanced power menus on my phones, and an Xposed module alternative is much easier than flashing additional zip’s. If this doesn’t work for you, the new Lollipop Power Menu module might.
XToast [1]:
This was one of my favorites back then, as it lets you add the Toast notification’s app origin into the message box by adding the corresponding app’s icon. That in itself makes it useful, but you can also customize said icon and add the name, or change the toast style back to older versions. The duration, transparency and where it appears also can be chosen. Basically, toasts are at your control to make them more informative and personal. You won’t know how awesome it is until you try it!
Lollipop Notification Ticker [1]:
This one was meant to restore the ticker on the status bar that informed you of the contents of your latest notifications. It was made before Xposed for Lollipop came out, which was a daring move that worked… partially. According to reports, it breaks heads-up notifications alongside fixing the ticker. If you dislike those in the first place, though, you might want to give it a try.
Native Clip board [1]:
Copying and pasting on smartphones was never the most fluid thing, nor the most consistent. This module adds clip-board management straight to the text-selection menu, and it allows you to theme the new menu, black-list apps and further customize it. If you happen to be working on your phone because there’s a document you might need to edit on the bus, this will prove useful.
BootManager [1]:
A must-have to those that want their device to be slim and efficient on boot. This module allows you to select which applications run when you power up your device, and those that don’t get allowed to do so usually stay dormant until you fire them up. If you’ve got a good amount of things that you don’t need right away but are hesitant to greenify, this can alleviate the dilemma of your user experience.
gaurav2009 said:
It's released
Thread link- here
I got it working..
Post #6
Click to expand...
Click to collapse
Does the dpi change work?
i try install on my phone, but i got only Bootloop :crying:
Official Xposed Framework released for Lollipop
Anybody tried official lollipop veesion?
Here: http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Adarsh1998 said:
Anybody tried official lollipop veesion?
Here: http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Click to expand...
Click to collapse
Thats the version that we are talkin about here...
and @gaurav2009 thanks for giving me hope..... now i know the exact steps to install lollipop without factory resetting the device..... (not very diff from the method stated there)
anybody know how to fix the low storage issues? my phone get laggy
just reflash the root.zip or re-root your MotoE. for me it fix the low memmory issues,
just reflash the root.zip or re-root your MotoE. for me it fix the low memmory issues said:
Deleting both caches (cache + Dalvik cache) immediately after flashing before reboot does it for me. Everytime.
Without that: lags, space issues, always a restore necessary to get a working device
Click to expand...
Click to collapse
All Builds In This Thread Are Considered Stable And Final.
I Am Not Responsible For Any Use Of Information Or Files Posted By Myself Or By Any Other User.
New is built from XAC T700XXU1ANL2 Firmware
This was made for us by @jrkruse who doesn't even own the device but still put it together for us:good:
I thank him greatly for that!
Requirements
Rooted SM-T700 With Custom Recovery
Download
STOCK_T700XXU1ANL2 https://www.androidfilehost.com/?fid=95916177934550989
rooted, deodex, Init.d support, zip aligned
Download
T700XXU1ANL2_Debloated https://www.androidfilehost.com/?fid=95916177934551122
Rooted, DeOdex, Init.d support, Zip Aligned
Boot Sound and USB Connect Removed
All Non-Samsung Removed
Xposed, Root Browser and Quick Boot Added
If you would like something back in that was removed please let me know
Download
EMPTYGALAXYROM T700 v2 https://www.androidfilehost.com/?fid=95916177934551888
- T700XXU1ANL2 Extremely DeBloated
- Deodex, Rooted, BusyBox, Init.d support and ZipAligned
-SFinder and Quick Connect Removed From Pulldown
-Boot And USB Connect Sounds Removed
*Apps Left In App Drawer
BusyBox Free
Calculator
Camera
Clock
Gallery
Google
Google Settings
Internet
Music
Nova Settings
Play Store
Quick Boot
Root Explorer
SPlanner
Settings
SuperSU
Voice Search
Xposed Installer
Recommended Instructions
Download Rom To SdCard
Boot Into Recovery
Wipe Dalvik Cache, Cache, System, Data and Internal Storage [optional]
Install Rom and Reboot
Go through Wizards
[EGR Go To Settings And Sign In To WiFi, Add Google Account and Set Time Zone]
Reboot And Wait For SuperSU Update Notification And Update It
Update SU Binary Normal And Reboot
It's All Yours From There!
OLD DOWNLOADS
EMPTYGALAXYROM v1.3 https://www.androidfilehost.com/?fid=95916177934535221
- A backup ran through a rom kitchen and cleaned up. [Assumed US firmware until I hear different]
- T700XXU1ANL2 Extremely DeBloated [libs, files and *apks]
- Deodex, Rooted, BusyBox, Init.d support and ZipAligned
-Aosp Tick
-SFinder and Quick Connect Removed From Pulldown
-Boot And USB Connect Sounds Removed
*Apps Left In App Drawer
Calculator
Calendar
Camera
Clock
Gallery
Google Settings
Internet
Music
^Nova Settings
Play Store
Quick Boot
Root Explorer
Settings
SuperSU
Xposed Installer
^Nova is the default and only launcher
Special Instructions For Google Now Launcher
You Must First Install Google Search Before The Google Now Launcher
*******************************************
STOCK VERSIONS OF T700XXU1ANL2
Recommended Instructions
Download Rom Of Choice
Boot Into Recovery
Wipe Dalvik Cache, Cache, System, Data and Internal Storage
Install Rom and Reboot
Go Through Set Up Wizard
Reboot
Completely_Stock_T700XXU1ANL2 https://www.androidfilehost.com/?fid=95916177934532866
Rooted And Busybox As Is Odexed Untouched Stock.
T700XXU1ANL2_DORBIZ https://www.androidfilehost.com/?fid=95916177934532867
Deodex, Rooted, BusyBox, Init.d support and ZipAligned
All Bloat. All. I will update this if someone else doesn't make an NL2 debloated.
DRBIZ_T700XXU1ANL2 https://www.androidfilehost.com/?fid=95916177934533222
Same as above without knox, boot & usb connection sound.
Added in data/ Xposed, Reboot & Root Browser
SystemUI.apk https://dl.dropboxusercontent.com/u/9398026/SystemUI.apk
with SFinder and Quick Connect Removed From Pulldown
Use a root browser to replace current in system/priv-app
*WARNING*
This can be a little tricky as the system will force close before you can change permissions.
Instructions
download to SDCard
copy and paste SystemUI.apk to System/priv-app [overwriting current]
quickly reboot
change permissions [you should just need to click off "others/write"]
EMPTYGALAXYTHEME flashable in custom recovery https://dl.dropboxusercontent.com/u/9398026/EGT_V0.1.zip
Theme Info
This is only recommended to be used with stock NL2 Roms for Tab S 8.4
Contains - pngs, xmls and SystemUI.apk
It is very far from done but I figured I'd post it because I use it so maybe you'll want to.
I'm stuck on compiling errors and without time to figure it out. If I add a significant amount of themed parts I'll update it.
{
"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"
}
*******************************************
Developers
Feel Free To Use These Builds How You Like
Although I Would Wait For Official Firmware
This Is An OTA Back Up Ran Through Ricky's Kitchen
Special Thanks To
@Ricky Divjakovski
@EMSpilot
@akash_bd
tbd
tbd
_________________________________________
_________________________________________
Empty galaxy rom...
I just wanted to let you know that I have it installed and have been messing with it for about an hour. Everything seems to be running quickly. So far the only thing I have noticed is that it seems to be running a little warm. I will report back with anything else I come across. Good work!!
I've been working on the theme but the ui is new to me. Still finding stuff. Thanks though @ITSAHERO hopefully as it set in it evened out the temp.
Couple questions
Hello there,
I am interested in installing the completely debloated version you did. Is the IR Blaster and the finger print unlocking the device working? Thanks in advance!!
I haven't tried the ir but finger print works. And you're very welcome.
I'll try the ir and report back. I'm in the middle of an install so it'll be a few..
Added
IR: Tested and fully operational
Best rom I've used.
Hi, downloaded the empty ROM on my tab s t700. Personally I'm not a fan of Nova so I tried installing google now launcher but it doesn't work for me? It installs and stuff alright but it just force closes on me. Now, I'm coming to this ROM from ironrom on which I was running google now launcher but I just can't get it to work on here. Am I the only one a facing this problem?
I'll download and try and report back.
Added-
Yes. You're right.
I removed Google search, sometimes I use yahoo so I like it out.
To use Google Now you need to first install Google search and go through initial setup then download and install Google Now.
The OP has been updated and the Empty Galaxy version has been updated to 1.3.
I had hoped to add a theme to it but it's taking more time than I thought to find everything.
If I get to a usable point with it I'll upload.
The rom ive been waiting for.. thanks dev.. what kernel suits best with it? Can you recemmend any?
I've been using the stock kernel so I can't really recommend yet. I'll give what's available a try today.
I'm using sky-high kernel with this rom, I have to say, my tab S 8.4 has never been smoother, almost as quick as my nexus 9.
Is this a US firmware? I have been using it and lost access to wifi channels 12 and 13. The tab could not detect my home network anymore. Europe here... Thx for all the work you've put into this.
Brgds
Sent from my GT-I9505 using xda premium
Everything has been working well for me with the stock kernel. Great ROM. :good:
rlrmineiro said:
Is this a US firmware? I have been using it and lost access to wifi channels 12 and 13. The tab could not detect my home network anymore. Europe here... Thx for all the work you've put into this.
Brgds
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
My apologies, that didn't even cross my mind. This is a backup ran through a rom kitchen and cleaned up. But it was an ota so I've got to assume it's US. If I get a chance I'll look into it.
Best RoM used yet! Keep up the good work.
Thanks.. I'm not sure where I'm at with development on the tab s. Glad the roms are getting used. I'm still waiting for the official nl2 download. My favorite thing about the tab is having a device not connected to a carrier! And it really makes it so we don't need very many apps to start.
reggie cheeks said:
Thanks.. I'm not sure where I'm at with development on the tab s. Glad the roms are getting used. I'm still waiting for the official nl2 download. My favorite thing about the tab is having a device not connected to a carrier! And it really makes it so we don't need very many apps to start.
Click to expand...
Click to collapse
Agreed, it's so relaxing.
Setup time on a fresh install is so short
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?
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!!