Related
How To Play Pokemon Go with Superuser (Root enabled)
Note:
IT MIGHT CAUSE BOOTLOOP OR MIGHT BRICK YOUR DEVICE. MAKE SURE YOU HAVE A BACKUP.
Requirement:
Fresh Installation of Rom or Dirty Flash of your current rom (I tested it on CM and RR- Fresh.It might work on other custom roms.)
TWRP Recovery
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
unSU Script : http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
Steps:
1. Reboot into Recovery
2. Flash unSU Script and Magisk in order.
3. Reboot into System. (Mobile should boot without bootloop, otherwise you have to reinstall the ROM and try again)
4. Install Phh Superuser from here: https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en.
4. Open Magisk Manager ( Update it,if it is asked) and it will ask you for SU permission. Allow it.
6. Go to Settings and Tick " Enable Magisk Hide " and Reboot your phone.
7. Once again Magisk Manager and it will show status of SafetyNet at 3rd row and It should Passed.
Install PokemonGo and Enjoy
Credits:
@topjohnwu
@phhusson
@Hw4ng3r
@Tikerz
Updates:
8/1/17
Updated the steps with New Magsik version 10.2
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Jowhee said:
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Click to expand...
Click to collapse
This guide is for keeping root AND passing SafetyNet.
BTW, this method also works on CM13 and OOS.
It didn't mention keeping root in the title.
Jowhee said:
It didn't mention keeping root in the title.
Click to expand...
Click to collapse
Sorry for the confusion.
Updated the thread.
SafetyNet Helper fails after following the steps:
SafetyNet request: success
Response Validation: success
CTS profile match: failure
Click to expand...
Click to collapse
Do we need to go back into fastboot and disabled the bootloader unlock?
nphillips said:
SafetyNet Helper fails after following the steps:
Do we need to go back into fastboot and disabled the bootloader unlock?
Click to expand...
Click to collapse
Not necessarily. Some kernels such as blu_kernel bypass the bootloader check. Try it out.
svprm said:
How To Play Pokemon Go with Superuser (Root enabled)
Click to expand...
Click to collapse
can Xposed work along with PoGo ?
samnaction said:
can Xposed work along with PoGo ?
Click to expand...
Click to collapse
I'm not sure. I didn't test it.
But you can install the Xposed Framework module through Magisk Manager.
In CM builds you don't need all this you just need this simple app:
http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
I'm gonna assume this doesn't work with CM12.1 right?
Yepi69 said:
I'm gonna assume this doesn't work with CM12.1 right?
Click to expand...
Click to collapse
I didn't try.
But you can try and post the result here that would help others.
I followed the steps in the first post and everything went OK. I'm using oxygen Os nougat 0.9
Thanks for your tutorial.
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
rdar_93 said:
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
Click to expand...
Click to collapse
Yes, cm 14.1 could pass safety net with this.
This works for sure. But if you're running a secondary ROM using MultiROM the modified boot.img will cause safetynet to indeed fail. I hope they do bring an update soon to fix this though.
Daft question, but i'm unable to use an online banking app, due to being rooted. I know this relates to PokemonGo, but wondering if this could fool the banking app?
I am using H2OS beta (Nougat) and I followed the below steps, but safety net is failing.
1. Dirty flash current ROM
2. Flash UnSU.zip
3. Flash magisk and phh zips
4. Reboot
5. Install Magisk Manager and Phh superuser
6. check safety net
Is there anything which I'm doing wrong? Can you help me please. Thank you
Edit: A reboot and everything worked fine. Thank you so much
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
topjohnwu said:
If you're using Magisk v7+ with Magisk version of phh's superuser , or rooted with Official Systemless SuperSU (Android 6.0+ only)
If you choose to use SuperSU (only support Android 6.0+)
Click to expand...
Click to collapse
So I am really wondering about your step 2 ...
svprm said:
2. Flash unSU Script, Magisk and phh's SuperUser Magisk.
Click to expand...
Click to collapse
pathologo said:
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
So I am really wondering about your step 2 ...
Click to expand...
Click to collapse
Actually i didn't try with SuperSu.So i mentioned phh's SU.
It might work with SuperSu too.
Is there any way to use Android Pay on rooted device?
OOS 4.0.2
franco Kernel (I have red that it baypass unlocked bootloader for Android Pay?)
TWRP
Root (SuperSU)
I tried to turn off root in SuperSU but it still detects root or unlocked bootloader
extra2 said:
Is there any way to use Android Pay on rooted device?
OOS 4.0.2
franco Kernel (I have red that it baypass unlocked bootloader for Android Pay?)
TWRP
Root (SuperSU)
I tried to turn off root in SuperSU but it still detects root or unlocked bootloader
Click to expand...
Click to collapse
Remove SuperSU, download magisk 11 - flash it (contains its own root solution). Franco kernel is all good., When your back in your phone, install magisk manager from the play store, open it, go to settings, enable magisk hide and reboot and you should pass the safetynet test (look on play store for safetynet its the first app with a green square icon). If you pass that, your all good!
just only tipp (i don't use Android Pay) - SuperSu also has a hide similar functionality - Options >> Enable Superuser []
... i'd first try it, instead of uninstall/replace
Hmmmm.... I tried to unroot in SuperSU, now my device stay stuck at the splash screen and won't boot. I'm on FreedomOS, I guess it's incompatible; just a heads up to those users.
EDIT: Nevermind, flashed the zip and all is well!
manor7777 said:
Remove SuperSU, download magisk 11 - flash it (contains its own root solution). Franco kernel is all good., When your back in your phone, install magisk manager from the play store, open it, go to settings, enable magisk hide and reboot and you should pass the safetynet test (look on play store for safetynet its the first app with a green square icon). If you pass that, your all good!
Click to expand...
Click to collapse
I hope I don't need to wipe all data?
EDIT:
And one more thing: would Android Pay work on FreedomOS?
extra2 said:
I hope I don't need to wipe all data?
EDIT:
And one more thing: would Android Pay work on FreedomOS?
Click to expand...
Click to collapse
I'm using it right now! Latest FreedomOS, and Magisk 11 to root. I didn't wipe all data, i just didn't install SuperSU when i installed FreedomOS and instead installed Magisk as it has its own SU solution. Easiest way do it and i use android pay more than once a day!
manor7777 said:
I'm using it right now! Latest FreedomOS, and Magisk 11 to root. I didn't wipe all data, i just didn't install SuperSU when i installed FreedomOS and instead installed Magisk as it has its own SU solution. Easiest way do it and i use android pay more than once a day!
Click to expand...
Click to collapse
Thanks, I'm gonna flash FreedomOS and do as you said. It's just you know I'm on the stock OOS and it'll be first custom ROM for this phone (yes it's again oos but anyway). I'll let you know if it (android pay) works for me
[EDIT]
Yeah dude, works great. Thanks
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk
Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep
uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.
Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?
Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.
Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.
So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?
Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.
thany2 said:
So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?
Click to expand...
Click to collapse
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk
Dirty flash should remove all su or magisk, then you can install magisk again
abacate123 said:
Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.
Click to expand...
Click to collapse
Uninstalling Magisk results in a boot loop, like I said. So it's a no-go.
What other reasons could it have when SafetyNet doesn't pass with that error message?
tropicanapure said:
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
SuperSU has that option greyed out because of a locked binary, like I said, so that won't solve anything.
adekboreanaz said:
Dirty flash should remove all su or magisk, then you can install magisk again
Click to expand...
Click to collapse
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.
thany2 said:
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.
Click to expand...
Click to collapse
No it is not, dirty flash is flashing your rom again without deleting /system /data partition, that can replace your boot.img with the stock one, so the supersu will be disappeared
reflash boot.img from the rom you used via twrp on img mode (click zip or img to switch between modes) or reflash your desired custom kernel.
Hi, I use pixel fasher to update the firware of my phone, I also use it to install magisk (my bootloader is unlocked). Everything is going fine except the installation of magisk. Only magik manager was installed.
With my former phone I installed magisk.apk renamed magisk.zip in recovery and then magisk manager, how do you proceed with Pixel 7?, Is it possible to use adb? Or pixel has its own recovery?
Thanks for your answer.
well. with pixel flasher, it should work too that is what I did. Did you patch the init_boot.img in pixel flasher before starts flashing? Else just for rooting, you can refer something like this too https://forum.xda-developers.com/t/rooted-my-pixel-7.4505525/
Hi Creezalird, you're right, I just forgot to patch the init_boot.img before flashing, Thank you for your answer.
does your magisk pass safetynet? even with safetynet fix i get "CTS PROFILE MATCH" fail.. how do you fix that? thanks.
seities said:
does your magisk pass safetynet? even with safetynet fix i get "CTS PROFILE MATCH" fail.. how do you fix that? thanks.
Click to expand...
Click to collapse
Did you use this safetynet fix mod?
I had a problem with my banking app but solved with shamiko magisk module