Note: This will not work on any custom ROM running Android 4.3 and below. This will work however from 4.4 KitKat all the way up to 7.0 Nougat (as of post date)
Second Note: This method works for Android Pay and Snapchat too, as well as any other app plagued by SafetyNet.
Tutorial is made for the international variant of the Galaxy S3 (aka the i9300) - swap files out as needed for other variants
1. Download any 4.4+ custom ROM of your choosing.
2. Download SuperSU systemless (latest version is recommended, SR1 from 15th September 2016 as of post date) from here.
3. Download suhide (latest version is recommended, 0.55 as of post date) from here.
4. Install your custom ROM via your favourite custom recovery (recommendation is twrp, from here)
5. Install SuperSU systemless.
6. In TWRP file manager, or a file manager of your choice, remove /system/bin/su and /system/xbin/su.
7. Install suhide
8. Reboot into ROM
9. Enjoy Pokémon GO
Third Note: you may flash over zips like GApps (you flash these like normal)
Final Note: If you wish to install Xposed, you must flash the one from the suhide thread and install Material Design Xposed Installer from here for Pokémon Go, Snapchat, Android Pay and other affected apps caused by SafetyNet
What apps or processes have to be added to the blacklist?
Sorry my english
So, I have a GT-I9300 for my son, who's into playing Pokemon.
Worked so far, with custom rom (Currently it is NamelessRom).
No exposed.
So, how to approach this, as with the 41.4 updete of the game, (or more likely, an update again to Safetynet), I can't get the game to work anymore.
Any suggestions for "the best" rom to use for this ?
I don't care about root on that phone, it doesn't have to be there.
Thanks
-------------------------------
Edit: Just flashed Back to n00t rom, without root, and that seems to be working at least. It's crap that it's Android 4.4.4, however at least it works for him with Pokemon.
/system/bin/su and /system/xbin/su
any rom without these files should work with Poke Go
pokemon go
Hello
I have GT-I9300, rom eleckra s5 lite aroma 4.4.2, root, super su and sushed from you page, but didint work for, me.
My step:
1. instal rom
2 super su
3.Root explorer...but in system/bin su didint exist i have sh but in system/bin/ext i have su y delet this and after this i deleat system/xbin/su
4. reebot in twrp instal sushed rebbot rom
5.instal Pokemon go, log in with cont club...and error this software is not compatible...
Help
turbolukex5 said:
/system/bin/su and /system/xbin/su
any rom without these files should work with Poke Go
Click to expand...
Click to collapse
jorgesibiu said:
Hello
I have GT-I9300, rom eleckra s5 lite aroma 4.4.2, root, super su and sushed from you page, but didint work for, me.
My step:
1. instal rom
2 super su
3.Root explorer...but in system/bin su didint exist i have sh but in system/bin/ext i have su y delet this and after this i deleat system/xbin/su
4. reebot in twrp instal sushed rebbot rom
5.instal Pokemon go, log in with cont club...and error this software is not compatible...
Help
Click to expand...
Click to collapse
SuperSU method is no longer working according to some people, due to a SafetyNet Update..
Try without SuperSU and report back
Related
Hi!
This is my question, Why I lost my ROOT when I install another ROM?
I have the following case.....
- CM with Android 4.3 and Rooted, working without problems.
- I install the ROM [JB 4.3 JWR66Y] [Linaro gcc 4.8] ♦ PURITY ROM ♦ (Mako) 24/10 with the CWM (before formating everything)
- I install the last SuperSU version with the CWM, without problems.
- I start the Nexus4, I try to open SuperSU but I receive the error "There is no SU binary installed, and SuperSU cannot install it."
- I format everything again with CWM, and I install again only the CM Android 4.3, without SuperSU or something similar.
- I have root permisions.
What I´m doing wrong, to don´t get the Purity Rom with Root??
Problem SOLVED!!
- With the CM Rom, install the SuperSU via CWM.
- Download TWRP (http://teamw.in/project/twrp2/129) and install it, but not "activate" the recovery jet.
- Open SuperSU and desactivate activate the "Super User" check, some times, but leaving at the end activated.
- Open TWRP, give root rights!!! and in options, select "Install open...:"
- Install the Purity ROM via TWRP
- Enjoy
All custom ROMs come rooted. Of course SuperSU isn't going to work; the original SU application and binary are still in place. You never had to flash anything root related.
korockinout13 said:
All custom ROMs come rooted. Of course SuperSU isn't going to work; the original SU application and binary are still in place. You never had to flash anything root related.
Click to expand...
Click to collapse
not true. many custom roms come without supersu or superuser, where it would be the users responsibility to flash either supersu or superuser.
This PURITY ROM comes without Root, thats why they say that you need to use SuperSU
After a couple of days bricking around, finally found a way to have all the goodies and still have full device encryption. Something that isn't working with custom recovery installed.
Short guide:
1. Stock ROM 5.1.1
2. Encrypt device first (!)
3. Root using Kingroot (NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk) (http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461)
4. Reboot
4. Remove Kingroot and install SuperSu using this guide (http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html)
5. Reboot
6. Download Xposed Framework sdk22, arm (not arm64) from http://forum.xda-developers.com/showthread.php?t=3034811
6. Install Xposed Framework zip trough flashfire-0.24.apk using this guide (http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593)
7. Reboot
7. Install the xposed installer
8. Good to go!
Finally have all the tweaks and no worries in case of lost/stolen device.
It's working!
Only followed steps 3 to 5 though.
Rest are not required.
Do I need to have a unlcoked bootloader?
Dinkec27 said:
Do I need to have a unlcoked bootloader?
Click to expand...
Click to collapse
no, you keep all the goodies
Please, note that according to this thread :
http://forum.xda-developers.com/z3-compact/general/kingroot-4-0-t3105593
There may be issues with privacy and your IMEI may be sent to China when you're rooting with Kingroot... Which may be bad. Pretty bad. (It allows for instance the creation of fake phones with real IMEI.)
Has anyone tried flashing Xposed through Flashfire on Android 6.0.1 Beta?
I get root with this easy method, thank you man!
I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin.
How can i resolve it?
FunkyCrime said:
I get root with this easy method, thank you man!
I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin.
How can i resolve it?
Click to expand...
Click to collapse
I think you need to install XZDualRecovery because that has the RIC fix(basically read and write permissions for system without unlocked bootloader),I had this issue as well and this solved it for me
This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
:highfive:HELLO GUYS
So Here u can Find How To Bypass Safetnet In Your Phone While Being Rooted.
As you all know safetynet is implemented by Google itself to check Security of your Device & also by Some games or apps Eg. Pokeman Go,Android pay,Snapchat etc. So If Your Phone Is Rooted SafetyNet Test Will Fail.
With failed Safetynet Test You Can't Run These Apps in Your Mobile.
Check your Safetynet Status By This App:- https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
So If your Test Failed And you can't able to run Games or Some Apps Try This method
1. Fully Unroot Your Phone In SuperSu app Go to Settings tab on the top right corner, and then click Full Unroot. Confirm with 'Continue'. 3. Once this operation is done, which takes a few minutes, you can reboot your Android & Then Flash This Unroot Script In Custom Recovery
https://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
2. Download Magisk 12.0 http://tiny.cc/latestmagisk and Flash it in Custom Recovery & Reboot **Make sure in custom recovery if a Line Appears "Boot img already patched" That means You'r Not Fully Unrooted in this case you have to flash your Stock System.img or Stock rom**
3. Now Install Magisk Manager From Play Store https://play.google.com/store/apps/details?id=com.topjohnwu.magisk
4 In Magisk manager Go To Settings Click on Enable BusyBox & Magisk Hide
5. Thats it. Now Run Safetynet test in Magisk Manager It will pass.
6.Enjoy your Games or Apps
UPDATE :- With Android Security Patch 01/04/2016 On Marshmallow Flashed SuperSu 2.79 Flashed Suhide 0.55 Flashed Magisk 12.0 Flashed Xposed 87.0 Systemless PASSING SAFETY NET Without Disabling root
Credits :-
@topjohnwu For Magisk 12.0 & Magisk Manager App
@halifax For Unroot Su Script
Hey, I have a problem:
I used this script on my Galaxy Nexus but now I decided to use SuperSU again because Magsik didn't work for me. I have just one problem: After using this script I can't install SuperSU anymore. The installation works as usual without problems but if I open the SU app it sais I need a Su file flashed. Could you please help me to fix thid problem?
Thanks in advance,
greetings Nils
yo_honey said:
:highfive:HELLO GUYS
So Here u can Find How To Bypass Safetnet In Your Phone While Being Rooted.
.....
1. Fully Unroot Your Phone In SuperSu app Go to Settings tab on the top right corner, and then click Full Unroot. Confirm with 'Continue'. 3. Once this operation is done, which takes a few minutes, you can reboot your Android & Then Flash This Unroot Script In Custom Recovery
https://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
2. Download Magisk 12.0 http://tiny.cc/latestmagisk and Flash it in Custom Recovery & Reboot **Make sure in custom recovery if a Line Appears "Boot img already patched" That means You'r Not Fully Unrooted in this case you have to flash your Stock System.img or Stock rom**
3. Now Install Magisk Manager From Play Store https://play.google.com/store/apps/details?id=com.topjohnwu.magisk
4 In Magisk manager Go To Settings Click on Enable BusyBox & Magisk Hide
5. Thats it. Now Run Safetynet test in Magisk Manager It will pass.
6.Enjoy your Games or Apps
UPDATE :- With Android Security Patch 01/04/2016 On Marshmallow Flashed SuperSu 2.79 Flashed Suhide 0.55 Flashed Magisk 12.0 Flashed Xposed 87.0 Systemless PASSING SAFETY NET Without Disabling root
Credits :-
@topjohnwu For Magisk 12.0 & Magisk Manager App
@halifax For Unroot Su Script
Click to expand...
Click to collapse
Thanks my friend, u save my day, Samsung S6 Edge +.
Flash Latest SuperSu Zip in custom recovery
MrFlashGame said:
Hey, I have a problem:
I used this script on my Galaxy Nexus but now I decided to use SuperSU again because Magsik didn't work for me. I have just one problem: After using this script I can't install SuperSU anymore. The installation works as usual without problems but if I open the SU app it sais I need a Su file flashed. Could you please help me to fix thid problem?
Thanks in advance,
greetings Nils
Click to expand...
Click to collapse
Download Latest Stable version of SuperSu zip And Flash it Using Custom Recovery. This may solve your problem.
Hello, anyone have boot img for htc 820 dual sim?
Thank you
hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
so any advice anout that problem?
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Screenshot https://i.imgur.com/6IcIvJx.jpg
slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro