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.
Related
After installing the magisk as I was rooted, I installed 2-3 mods ie flashed in twrp but after I rebooted my root is gone. Magisk manager is showing not rooted and when I re flashed supersu in twrp, installation was successful but still no root. What happened I don't know. Also I didn't install any phh supersu or busybox. Please help me regain my root.
HELP
It was a known bug in Magisk that you would lose root.
Magisk
v10.2
- [Magic Mount] Remove apps/priv-app from whitelist, should fix all crashes
- [phh] Fix binary out-of-date issue
- [scripts] Fix root disappear issue when upgrading within Magisk Manager
Click to expand...
Click to collapse
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
brichardson1991 said:
It was a known bug in Magisk that you would lose root.
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
Click to expand...
Click to collapse
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Vaibhunk786 said:
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Click to expand...
Click to collapse
After installing from play store, did you "FLASH" magisk ?
brichardson1991 said:
After installing from play store, did you "FLASH" magisk ?
Click to expand...
Click to collapse
No I didn't flash anything. It was an automatic process which installed magisk and prompted me that installation success and reboot. Then I rebooted and root was gone
Now should I run magisk unstaller zip in twrp followed by supersu and then again flash magisk v10. 2 via twrp.. Should I follow these steps to gain my root again.. Anyone please help. I'm stuck @brichardson1991
Try installing PHH superuser from play store.
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Same problem here, have to investigate whats going on.
MattBooth said:
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Click to expand...
Click to collapse
yeah flashing the stock rom was the only viable option i think .
I have the same problem with latest magisk. After i installed mods root is gone and i can not root again. Only with supersu i have root. Magisk is very bugy.
Yeah it does appear the latest version now causes you to lose supersu
Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this, but figured better to investigate the issue before I attempt to reinstall.
From what I understand here, v10 won't have this problem, and its only on v11 that its cropped up again? Can anybody with v10 confirm this?
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
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Keagel said:
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Click to expand...
Click to collapse
Try flashing Magisk in recovery.
jhedfors said:
Try flashing Magisk in recovery.
Click to expand...
Click to collapse
It's what I did, that's where it tells me to install SuperSU first :/
Keagel said:
It's what I did, that's where it tells me to install SuperSU first :/
Click to expand...
Click to collapse
Can you give more details? What ROM, Magisk version, logs, etc?
I would suggest flashing osmOsis's UnSU zip, then Magisk v11.2.
Keagel said:
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Click to expand...
Click to collapse
Your boot image is pre-patched for SuperSU. Flash a clean boot image.
Yeah I found the original boot.img of the stock rom my rom is based on and flashed it and it fixed it! Thanks guys
how to find the original boot.img?
ydstark23 said:
how to find the original boot.img?
Click to expand...
Click to collapse
in twirp
restore> select correct folder > check boot > flash
ydstark23 said:
how to find the original boot.img?
Click to expand...
Click to collapse
In the ROM zip.
In case it has built-in superuser, I would suggest flashing osmOsis's unsu zip as well.
Is MagiskSU just another name for Magisk? A module I want to install has the following requirements:
Requirements:
Magisk v13.x/14.0
MagiskSU
I have Magisk v14.5 installed so does that mean I automatically have MagiskSU or is that something additional I have to add?
alryder said:
Is MagiskSU just another name for Magisk? A module I want to install has the following requirements:
Requirements:
Magisk v13.x/14.0
MagiskSU
I have Magisk v14.5 installed so does that mean I automatically have MagiskSU or is that something additional I have to add?
Click to expand...
Click to collapse
That requirement is probably a remnant from when Magisk also was compatible with SuperSU. It's not anymore, so when installing Magisk you get MagiskSU along with it.
Didgeridoohan said:
That requirement is probably a remnant from when Magisk also was compatible with SuperSU. It's not anymore, so when installing Magisk you get MagiskSU along with it.
Click to expand...
Click to collapse
Thanks! I was confused by that and I couldn't find a good answer when searching. Your help is greatly appreciated!
Oddly, I don't have any root after installing Magisk v15 via recovery. Magisk is working, integrity tests are both green, can install all the modules with no problem and integrity tests are still green, but no root.
Interesting, isn't it?
How i know i've got magiskSU?
Leogur said:
How i know i've got magiskSU?
Click to expand...
Click to collapse
Did you install magisk? Or is it included in your rom? Do you see magisk manager app?
Yes i've. But i still can't fix safetynet problem.
Thought I'd share how I upgraded my T-Mobile Galaxy S6 to Nougat (G920TUVU5FQE1 ) with root, deep sleep and SafetyNet bypass.
*** Read all step before starting as you will need to download and copy several files to your phone first ***
NOTE: This method will trip Knox!
Reboot into Download Mode
Flash G920TUVU5FQE1_G920TTMB5FQE1_G920TUVU5FQE1_HOME.tar.md5 with Odin (I used v3.10.6)
Download from Android File Host | Google Drive.
Reboot into Download Mode
Flash TWRP img.tar with Odin
Flash Magisk zip with TWRP and reboot to system
Install Magisk Manager (and enable Magisk Hide in Magisk Manager settings)
NOTE: The steps below will re-enable Deep Sleep
Install Flashify
Flash stock recovery.img with Flashify
Download from Android File Host | Google Drive.
Wipe cache (twice for good measure) and reboot
(Optional) Flash TWRP img using Flashify and reboot to system
Enjoy Nougat with root and SafetyNet bypass on your G920T! :good:
You do know that Google pulled Magisk from the Play Store....
The Sickness said:
You do know that Google pulled Magisk from the Play Store......
Click to expand...
Click to collapse
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
KaneHusky said:
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
Click to expand...
Click to collapse
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
The Sickness said:
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
Click to expand...
Click to collapse
Uh... I linked to the main Magisk thread on XDA, not Google Play.
KaneHusky said:
Uh... I linked to the main Magisk thread on XDA, not Google Play.
Click to expand...
Click to collapse
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
The Sickness said:
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
Click to expand...
Click to collapse
Wow. Ok, dude. Do you see an edit anywhere for my post? No. I specifically linked to the XDA thread because I know it was taken off Google Play. :good:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
BigDaddy38 said:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
Click to expand...
Click to collapse
It's pulled straight from Smart Switch so everything is 100% stock.
KaneHusky said:
It's pulled straight from Smart Switch so everything is 100% stock.
Click to expand...
Click to collapse
Sweet gonna give it a shot, Thankyou!!!!
i have no idea where to find magisk manager any help would be appreciated
BigDaddy38 said:
i have no idea where to find magisk manager any help would be appreciated
Click to expand...
Click to collapse
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
KaneHusky said:
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
Click to expand...
Click to collapse
Your right i found it, the link didnt work earlier when i tried thankyou
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
EncryptedCurse said:
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
Click to expand...
Click to collapse
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
crashff said:
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
Click to expand...
Click to collapse
Yeah, to fix deep sleep not working after the first TWRP flash.
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
BigDaddy38 said:
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
Click to expand...
Click to collapse
Read my rom thread and kernel thread.
KaneHusky said:
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
Click to expand...
Click to collapse
Everything was working fine last night, but I seem to have lost root during some point today. Magisk Manager still says that Magisk is installed, but that I am "not rooted." Any ideas? Should I try to reflash Magisk or will that trip SafetyNet?
Quick disclaimer
-I am not the founder of this @Chainfire made this and @joemossjr is the founder of this method.
-I am also not responsible for a raise in gas prices getting cheated on by your wife and a bricked device
So for you that don't know already: "SuHide" is a application which hides root from other apps that detect it (Snapchat, Hulu, banking apps, etc.) And will allow you to use these apps while rooted.
In other words you pass safetynet
PLEASE READ THIS:
AFTER YOU INSTALL "SUHIDE" DO NOT INSTALL XPOSED IT WILL CAUSE A BOOT LOOP WHICH IS UNRECOVERABLE WITH OUT THE STOCK FIRMWARE FLASH
DO NOT INSTALL SYSTEM TWEAKS (PERFORMANCE TWEAKS FLASHED THROUGH TWRP) THEY WILL ALSO CAUSE I BOOTLOOP
**If you do brick your phones here is the link to the stock firmware flash**
T-Mobile: https://drive.google.com/file/d/0B1tqDJm_qQf4YWxreUJSWXJWeVk/view?usp=sharing
Sprint: https://androidfilehost.com/?fid=889964283620761146
-------------------------------------------------------------------------------------
STEPS TO INSTALL:
But what you want to do for root is.
1. Download the configurer. http://download.chainfire.eu/1121/SuperSU/AROMA-SuperSUConfig-v1.00.zip
2. Download the latest SuperSU. http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
3.Download the latest suhide. http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
FLASHING
4a. Boot into TWRP
4b. Flash the configure file and chose these options.
1st page= Last option should say 8.0 sbin mode
2nd page=Choose the second option on all sections.
3rd page= leave everything defaulted
5. now after that's done flash SuperSU the suhide. Then boot and it should reboot a few times but it will boot and you will have suhide
6. Open up the new app in your app drawer named "SuHide" and Grant superuser permission
Have Fun
(Tell me if it worked please)
This worked perfectly for me. I am on the stock T-Mobile August build and no longer have to fire up the hotspot and use my old VZW Z Force for Android Pay. Thanks for putting this guide together!
WeUseLord- said:
...
PLEASE READ THIS:
AFTER YOU INSTALL "SUHIDE" DO NOT INSTALL XPOSED IT WILL CAUSE A BOOT LOOP WHICH IS UNRECOVERABLE WITH OUT THE STOCK FIRMWARE FLASH
...
Click to expand...
Click to collapse
Do you think it is related to Suhide presence or to installing SuperSU on /sbin?
(to be clearer, installing SuperSU on /sbin is safe with Xposed?)
enetec said:
Do you think it is related to Suhide presence or to installing SuperSU on /sbin?
(to be clearer, installing SuperSU on /sbin is safe with Xposed?)
Click to expand...
Click to collapse
I honestly do not know I believe the reason is because XPOSED is detected differently than SuperSU which is why it won't work
DarkFalconX said:
This worked perfectly for me. I am on the stock T-Mobile August build and no longer have to fire up the hotspot and use my old VZW Z Force for Android Pay. Thanks for putting this guide together!
Click to expand...
Click to collapse
No problem thanks for clarifying that it works