Hi.
I have a question regarding how supersu installs on LineageOS.
I recently flashed LineageOS ROM over OnePlusOne cyanogenMod.
With the help from members in Q&A forum I successfully flashed supersu.
Upon completion, the settings in Developer Option showed 2 options for Root access.
1. ADB-only 2. Disable (see screenshot). I selected adb-only. Installed root checker and Titanium backup and was able grant root permission and execute Titanium bkup.
I was under the impression, you must choose (adb and apps) for root access, but as you see on my screenshot that option is not available.
(Q): How did I get supersu root access for apps using adb-only?
Installation Performed:
After several failed attempts trying to install supersu, I went to my original TWRP backup and did a full restore of LOS and GAAP.
Copied supersu zip from PC to Phone internal storage, selected, Install and rebooted. (did not wipe).
When finish, selected adb-only (as I stated above) and supersu worked. (see screenshot).
I am aware there is a LOS extras patch available to install, having Root access (adb and apps) option, but I cannot understand why it worked with the option I choose.
Does LOS have an internally supersu root (all) flag built in their release that can be triggered by adb-only? I tried selecting adb-only and failed having Sultans LOS zip installed, before doing a full TWRP restore of my files as a last option.
The LOS build I used was 14.1-201707703-Nightly bacon.
The Supersu I installed was Update-Supersu-v2.82-20170528234214.
Thanks.
TC.
@tomx2x
I prefere LOS's addonsu.
Out of interest, why SuperSU? Have you given Magisk a try?
vikashhero said:
Out of interest, why SuperSU? Have you given Magisk a try?
Click to expand...
Click to collapse
Is there any advantage besides that safetynet thing?
kurtn said:
Is there any advantage besides that safetynet thing?
Click to expand...
Click to collapse
Modules
vikashhero said:
Modules
Click to expand...
Click to collapse
Mostly looks like solutions for problems which I don't have as long as I don't install magisk.
vikashhero said:
Out of interest, why SuperSU? Have you given Magisk a try?
Click to expand...
Click to collapse
kurtn said:
Is there any advantage besides that safetynet thing?
Click to expand...
Click to collapse
Some people prefer Coca-Cola, others prefer Pepsi. The nice thing is that there are choices, and we can use whatever solution we like (I use SuperSU, myself, as I've not encountered a situation where I'd need Magisk).
My preference is beer. But in AEX they only served that brown lemonades.
tomx2x said:
(Q): How did I get supersu root access for apps using adb-only?
Click to expand...
Click to collapse
Did you try to run SuperSU without adb-only? I think, these buttons are only beer bottle openers for addonsu. Thy have no effect on your lemonades. AEX has no built-in opener at all.
kurtn said:
Mostly looks like solutions for problems which I don't have as long as I don't install magisk.
Click to expand...
Click to collapse
Well there's modules, and the fact that it's open source whereas SuperSU is not. If Chainfire still owned it, I'd worry less, but I'd want some transparency behind a third party application used to handled root access on such a personal device.
I'm not suggesting that CodingCode is doing anything dodgy with SuperSU, but it does give me peace of mind using something open.
vikashhero said:
Well there's modules, and the fact that it's open source whereas SuperSU is not. If Chainfire still owned it, I'd worry less, but I'd want some transparency behind a third party application used to handled root access on such a personal device.
I'm not suggesting that CodingCode is doing anything dodgy with SuperSU, but it does give me peace of mind using something open.
Click to expand...
Click to collapse
Did anyone try the open source alternative pph's SuperUser?
Looks like the LOS addonsu is open source: https://review.lineageos.org/#/q/project:LineageOS/android_system_extras_su
kurtn said:
Did anyone try the open source alternative pph's SuperUser?
Looks like the LOS addonsu is open source: https://review.lineageos.org/#/q/project:LineageOS/android_system_extras_su
Click to expand...
Click to collapse
phh's one was good, yeah
The LOS one works fine too, as you'd imagine. That's the one I'm currently using, but if I need to use Android Pay (on some weekends I do make use of it) then I'll switch over to Magisk.
Related
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
kroogar said:
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
Click to expand...
Click to collapse
First flash a good recovery. Personal opinion PhilZ touch---first go though the page and u can notice an super user option first do that it'll remove all root environment then install Busybox on Rails app from playstore, though i've been using TWRP since a long time coz of it's simple UI themable too but it's having binary-update script issues (root-->need busybox ---environment issues) , then u can use either on of em Superuser/SuperSu disable Superuser in CM to use SuperSU.
kroogar said:
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
Click to expand...
Click to collapse
Also try uninstalling both rebooting & reinstalling Superuser.
OffcerClancy said:
Also try uninstalling both rebooting & reinstalling Superuser.
Click to expand...
Click to collapse
are you even able to remove stock superuser that's baked into the rom?
t1.8matt said:
are you even able to remove stock superuser that's baked into the rom?
Click to expand...
Click to collapse
Can't answer categorically, but, w/ROM I am running it was listed in Settings, Apps, Downloaded, and allowed for Uninstall option.
OffcerClancy said:
Can't answer categorically, but, w/ROM I am running it was listed in Settings, Apps, Downloaded, and allowed for Uninstall option.
Click to expand...
Click to collapse
Yeah, then it can be uninstalled. But on a rom like CMetal that I'm running right now, you can't uninstall superuser like that, it's baked in which might be what the OP is dealing with. To not use the built in superuser you just flash supersu over it and the system uses that for root access and not superuser.
I have been trying to Google this but am a little confused on all the steps I need to (and don't need to) take at this point, especially since I am a little behind. So I wanted to ask for help on forums, if anyone is willing to give some advice on this.
First of all, I have a Sprint version of the HTC 10. I don't know if that matters or not (I recall back when I was trying to figure out the original Magisk, someone mentioned that a Sprint model HTC 10 could be an issue, but I am not sure why).
Also, so far all I have done in terms of rooting it is:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Ummm, anyone?
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Its all there in the op of the magisk thread.
I read that thread, as I said, I still don't understand some parts.
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Have you tried posting in the dedicated Magisk thread?
Try installing leedroid nightly latest it has magisk available when you install rom
i did not try it, till now. I read something a few weeks ago.
But in the magisk thread the op said something that SuperSu is not the supported SU method? only phh superuser?!
I would ask the question in magisk thread.
Firstly: You ask a lot of semi-related questions, a lot of these are already answered, out there, in the appropriate threads.
Let me systematically try to answer your questions
What you have done:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
Click to expand...
Click to collapse
When you install the TWRP recovery, you actually install it to the recovery partition of your device.
the option the "not modify system" has nothing to do with installing TWRP, but with installing other mods/roms
It's there so you can make a backup without modifying the system partition, that way you can go back to a working isntall if you do happen to mess something up.
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
Click to expand...
Click to collapse
SuperSu *should* break safetney and thus should break android pay, as Chainfire says in the following thread: http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
"In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU."
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Click to expand...
Click to collapse
Installing SuperSu trough TWRP installs the dependencies (the actual root) and the application (which just manages the root access), the magisk guide tells you to first flash the preferred root (SuperSu or SuperUser phh's) trough recovery and then install the correct manager app trough the playstore.
This is probably so John doesn't have to keep on updating his zips everytime the makers of the manager apps update their apps, users can just download the latest version.
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
Click to expand...
Click to collapse
Resetting to stock is important for 2 reasons:
1. it cleans out all "old" root apps and methods
2. it cleans up a patched boot.img (kernel)
Then again, if you haven't flashed any other mods, you would probably be safe to install magisk on your rom.
One important thing everyone will always tell you: make a backup! (make a nandroid)
To do this, boot to TWRP and choose "backup" make sure to select: Boot, System and Data
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Click to expand...
Click to collapse
The proper steps would be:
0. Make a nandroid backup in TWRP!!
1. Open SuperSU and choose to completly unroot (somewhere near the bottom of the settings menu)
2. Boot to TWRP and flash Magisk
3. Flash the phhh superuser zip file (from the magisk thread)
4. boot android and install the superuser app from the playstore
5. boot twrp and install AutoMagisk
That's it!
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Click to expand...
Click to collapse
Radio shouldn't be broken unless you flash very old zips, don't worry about it
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Click to expand...
Click to collapse
I allmost enver use official OTA's so I can't say for certain buttttt as you used SuperSU, the root should be systemless so it should accept OTA updates..
What I would do:
1. make a nandroid
2. install OTA
3. See if everything works as expected
4. restore backup if something doesnt work properly =D
I would install the OTA before trying Magisk
Thank you, that was very helpful. I did try Googling all this, but couldn't find clear answers, which is why I am asking here.
And yes, I am definitely going to make a backup before messing with it. Is there any reason to make a Titanium backup too, or will the nandroid one be enough?
As for removing SuperSU, what would that system/boot stock reset delete? Would it delete any installed applications or application settings? Or undo updates to pre-installed system apps? Or reinstall apps that came with the phone that I uninstalled?
Got it working, thanks. (Though, AutoMagisk seems to only be available as an APK, not as a zip that can be installed from TWRP).
Seems like a few configuration settings got wiped due to the system partition being reset, but other than that most of my data seems perfectly intact.
I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Isn't root enabled via settings? Maybe turn it off in the settings or reflash and don't enable root?
I tried that but the system is still seen as rooted
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Click to expand...
Click to collapse
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
mrrocketdog said:
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
Click to expand...
Click to collapse
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
hmmmmm well just for something to try , how about reflasing superSU then see if it will open. idk. just something to try
"err on the side of kindness"
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install SUHide v0.54
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will hide your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
-Test Pokemon Go. You should have no problems!
6. Need a GPS spoofing app? I use Fake GPS (well worth the $2.99). It allows you to pin favorite locations (I bounce quickly between spots where I can hit multiple lured PokeStops at once), and has settings to randomly move within a radius at whatever intervals and speed. They also have a GPS Joystick and Routes app that I have not yet tested since they don't offer a trial or free version. I'll update on that if they do offer a trial.
I have fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
**UPDATE 10/7/2016 ** - edited to use updated suhide v0.54
FuNKSioN said:
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install suhide v0.53
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will spoof your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
Test Pokemon Go. You should have no problems!
***UPDATE***
I have just fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
Click to expand...
Click to collapse
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Shack70 said:
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Click to expand...
Click to collapse
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
FuNKSioN said:
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
Click to expand...
Click to collapse
Wow! Thanks I appreciate it.
Shack70 said:
Wow! Thanks I appreciate it.
Click to expand...
Click to collapse
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
FuNKSioN said:
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
Click to expand...
Click to collapse
Thanks for your help. I updated yo the newest nightly build, did a full factory reset and deleted the 2 su files. After rebooting i re-downloaded the newest version of Pokémon and installed it. Game is working fine.
I don't use root much so I'll see how it goes without root and if I need root i can put the su files back(I made copies and put them in Dropbox) or try superSU/hideSU.
I know the s3 is slow but I'm putting off an upgrade until i have to upgrade. Until i upgrade I won't really realize how slow my phone is
Sent from my SGH-T999 using XDA-Developers mobile app
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
FuNKSioN said:
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
Click to expand...
Click to collapse
Yeah i get this is a temporary solution. Thanks for all your help. You've really gone above and beyond
Sent from my SGH-T999 using XDA-Developers mobile app
no problem man!
Thanks!
FuNKSioN said:
no problem man!
Click to expand...
Click to collapse
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
romehu2 said:
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
Click to expand...
Click to collapse
Glad to help. I was in the same boat: so much info in all directions and none of it seemed to work. I keep up with ChainFire's G+ account. He had a few posts linked directly back to XDA. Those few posts had everything needed. I just put it in simple steps. All thanks to him really
Sigh
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
romehu2 said:
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
Click to expand...
Click to collapse
reflashed CM13 + GApps, used ADB to rename system/xbin/su & system/bin/su to /su-off, and SafetyNet is happy (and thus, so is PoGo). but now, of course, phone isn't rooted.
---------- Post added at 05:18 AM ---------- Previous post was at 05:05 AM ----------
on the plus side, CM13 comes with File Manager which allowed me, without root, to install the v39.1 PoGo apk that I downloaded last week.
Sit back and wait for an SU update... It's only been a hot minute.
Hi Everyone,
I'm currently looking for a way to hide SU so that i can use my banking app, but with so many threads i'm reading, i can't find a reliable source and procedure. I'm currently studying how magisk work but some says that it doesn't work.
If i missed out a good and updated thread on hiding root, please do let me know.
You can use root switch
https://www.asus.com/zentalk/tw/thread-173542-1-1.html
Back when I was trying to get PokemeonGo to work, I tried a couple of different apps and hacks, and very few of them work, and even fewer of them work well. That was before I switched to Magisk, which I was skeptical about at first (I've been using SuperSu for years), but it really does work quite nicely.
I use Magisk, with no SuperSU. IIRC, Magisk is a systemless root, meaning it doesn't touch your /system, it flashes into your /boot. I flashed my ROM, Kernel, Magisk zip, and then downloaded the app from the play store. Inside the Magisk settings, there's a toggle for "Magisk Hide". Simply switch that on, and everything works! Your SafetyNet checks work, your banking apps work, your PokemonGo/MarioRun work, etc. Apps that already have root will continue to work, but any new apps will not be able to obtain root unless you unhide.
crazyates said:
Back when I was trying to get PokemeonGo to work, I tried a couple of different apps and hacks, and very few of them work, and even fewer of them work well. That was before I switched to Magisk, which I was skeptical about at first (I've been using SuperSu for years), but it really does work quite nicely.
I use Magisk, with no SuperSU. IIRC, Magisk is a systemless root, meaning it doesn't touch your /system, it flashes into your /boot. I flashed my ROM, Kernel, Magisk zip, and then downloaded the app from the play store. Inside the Magisk settings, there's a toggle for "Magisk Hide". Simply switch that on, and everything works! Your SafetyNet checks work, your banking apps work, your PokemonGo/MarioRun work, etc. Apps that already have root will continue to work, but any new apps will not be able to obtain root unless you unhide.
Click to expand...
Click to collapse
Thank you for sharing you experience with Magisk! i'm also skeptical with this but i will try it later, see if it will works with me. Thanks!
crazyates said:
Back when I was trying to get PokemeonGo to work, I tried a couple of different apps and hacks, and very few of them work, and even fewer of them work well. That was before I switched to Magisk, which I was skeptical about at first (I've been using SuperSu for years), but it really does work quite nicely.
I use Magisk, with no SuperSU. IIRC, Magisk is a systemless root, meaning it doesn't touch your /system, it flashes into your /boot. I flashed my ROM, Kernel, Magisk zip, and then downloaded the app from the play store. Inside the Magisk settings, there's a toggle for "Magisk Hide". Simply switch that on, and everything works! Your SafetyNet checks work, your banking apps work, your PokemonGo/MarioRun work, etc. Apps that already have root will continue to work, but any new apps will not be able to obtain root unless you unhide.
Click to expand...
Click to collapse
Just a quick question, did you just restore your boot image then flashed the magisk zip? then downloaded the app manager from play store?
yoorie016 said:
Just a quick question, did you just restore your boot image then flashed the magisk zip? then downloaded the app manager from play store?
Click to expand...
Click to collapse
I switched to Magisk at the same time I was switching ROMs, so I did a complete wipe and flash. You could do a dirty flash, but I would reflash your /system and /boot withOUT wiping cache or dalvik or anything. I don't know what (if) your previous root installed anything into /system, in which case it probably won't like it.
So what I would do If I were you is boot into recovery, re-flash your ROM/Gapps (no need to wipe cache), reflash your kernel (optional), flash the magisk zip, reboot, install magisk manager from Store, and you're good to go!
crazyates said:
I switched to Magisk at the same time I was switching ROMs, so I did a complete wipe and flash. You could do a dirty flash, but I would reflash your /system and /boot withOUT wiping cache or dalvik or anything. I don't know what (if) your previous root installed anything into /system, in which case it probably won't like it.
So what I would do If I were you is boot into recovery, re-flash your ROM/Gapps (no need to wipe cache), reflash your kernel (optional), flash the magisk zip, reboot, install magisk manager from Store, and you're good to go!
Click to expand...
Click to collapse
Thanks! i'll try it later, hopefully i dont brick my phone. LoL.
I use PureNexus with Magisk, AndroidPay, snapchat or pokemon go works but not my banking app(ANZ GoMoney Wallet), I have yet to find a solution, give magisk a try and see if it works for you. The producure is basiclly wipe system in twrp - flash purenexus - flash magisk zip - boot and install magiskmanager from play store
P.Fan said:
but not my banking app(ANZ GoMoney Wallet), I have yet to find a solution
Click to expand...
Click to collapse
Did you manage to get this working?
I'm using latest Magisk, and I always fail/error when it's performing the encryption for the wallet functionality.
mouth said:
Did you manage to get this working?
I'm using latest Magisk, and I always fail/error when it's performing the encryption for the wallet functionality.
Click to expand...
Click to collapse
No, PureNexus will not bypass the root check in the banking app despite passing safetynet for some reason. However, since then I have switched back to official stock ROM with magisk installed and haven't had a problem so far.
I use a star Finanz banking app that fails with Magisk.
The solution I found is to uninstall Magisk manager when I need to use the push TAN app and then reinstall it(Magisk manager) from my internal storage when I'm done. Seems to work for me now.
Dumb question, but you guys are using Magisk Hide for the app bank's app right? Your device is showing up as certified in the play store settings correct?
OhioYJ said:
Dumb question, but you guys are using Magisk Hide for the app bank's app right? Your device is showing up as certified in the play store settings correct?
Click to expand...
Click to collapse
Yeah, it used to not work at all. Now on latest Magisk it hides it successfully 50% of the time.
Found it easier to just uninstall the manager and reload it after. Since I only need the push TAN for online transfers.
Android pay works without a problem for me.
I installed adaway after rooting. Configured hosts file and rebooted. The system went into bootloop. How should I install it? Any additional steps? I am using miui 11 with agni kernel.
ashbk37 said:
I installed adaway after rooting. Configured hosts file and rebooted. The system went into bootloop. How should I install it? Any additional steps? I am using miui 11 with agni kernel.
Click to expand...
Click to collapse
Did you acquire root correctly? How did you root? Did you install magisk manager? Was the device working perfectly after rooting? Did you flash ARB 4?
Prathamesh 27 said:
Did you acquire root correctly? How did you root? Did you install magisk manager? Was the device working perfectly after rooting? Did you flash ARB 4?
Click to expand...
Click to collapse
Yep root is alright. Everything works perfectly. I rooted by flashong magisk. Also installed magisk manager. Didnt flash ARB 4.
ashbk37 said:
Yep root is alright. Everything works perfectly. I rooted by flashong magisk. Also installed magisk manager. Didnt flash ARB 4.
Click to expand...
Click to collapse
Did you check on Magisk manager settings>systemless hosts?
SubwayChamp said:
Did you check on Magisk manager settings>systemless hosts?
Click to expand...
Click to collapse
Yeah. I enabled systemless hosts before installing adaway. I flashed everything again. I'll try Adaway once more and see if it works properly this time. Is there anything I should configure in the Adaway settings before I proceed with it?
Also I would like to add Energized hosts to adaway amd I clearly dont know how that works. It would be helpful someone gave some steps for that.
ashbk37 said:
Yeah. I enabled systemless hosts before installing adaway. I flashed everything again. I'll try Adaway once more and see if it works properly this time. Is there anything I should configure in the Adaway settings before I proceed with it?
Also I would like to add Energized hosts to adaway amd I clearly dont know how that works. It would be helpful someone gave some steps for that.
Click to expand...
Click to collapse
First two silly question; it is included in some custom ROMs. Are you sure that you didn't install it over other version?
And, the systemless hosts have to be activated then device have to be rebooted for first time and then update hosts on AdAway and then reboot again.
The better is to start for a clean install, tap on the Adaway icon and go to settings of the app, clear cache and then clear data and finally uninstall it.
It may be the version, I use the 4.2.6 and never did give me errors.
Regarding include Energized hosts you can add it navigating with a browser to Energized site, you will find different extensions (Spark, Blu, Ultimate, etc; according the target you want, I should use the txt format then open AdAway and upper to the left you will find the option to add a source inside "Hosts sources" then tap on + , paste the txt copied before, check the link that https is not duplicated or something like this, after that apply it so it can update it.
SubwayChamp said:
First two silly question; it is included in some custom ROMs. Are you sure that you didn't install it over other version?
And, the systemless hosts have to be activated then device have to be rebooted for first time and then update hosts on AdAway and then reboot again.
The better is to start for a clean install, tap on the Adaway icon and go to settings of the app, clear cache and then clear data and finally uninstall it.
It may be the version, I use the 4.2.6 and never did give me errors.
Regarding include Energized hosts you can add it navigating with a browser to Energized site, you will find different extensions (Spark, Blu, Ultimate, etc; according the target you want, I should use the txt format then open AdAway and upper to the left you will find the option to add a source inside "Hosts sources" then tap on + , paste the txt copied before, check the link that https is not duplicated or something like this, after that apply it so it can update it.
Click to expand...
Click to collapse
Okay. Thanks for that. And I've flashed stock miui rom. So its not included. I'll do it again following your advice. ?