Related
Anyone else experiencing this?
I was coming from Stock rooted, modified boot.img, superSU 2.52Beta, ElementalX Kernel.
Fastboot flashed 6.0.1 Radio, System, Vendor, rebooted to TWRP 2.7.82, flashed modified SuperSU 2.61 systemless.
Everything works fine. Band 12 works fine. WiFi calling is enabled, turned on, and set to preferred.
Phone status reads IWLAN and network disconnected. WiFi data works.
Don't know what to do. Any help would be great.
It seems to only work on stock boot.img, SuperSU 2.6X breaks WiFi calling when it modifies boot.img
Can i refresh the stock boot.img and use SuperSU 2.52 for root?
Sent from my Nexus 6P using Tapatalk
You need a modified boot.img to root. SuperSU 2.60/2.61 (systemless root) modifies the boot image on the fly as it installs. The boot image from the "traditional" root method broke the camera on 6.0.1 for me when I followed the guide in the General forum. Not sure if a new modified boot image is up yet that works with traditional root.
Works on stock not rooted with Project Fi. Sorry can't help with your exact situation.
WiFi calling is working for me on stock 6.01 rooted sytemless su 2.61
zgroten said:
It seems to only work on stock boot.img, SuperSU 2.6X breaks WiFi calling when it modifies boot.img
Can i refresh the stock boot.img and use SuperSU 2.52 for root?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Any luck with this? Systemless root with SuperSU 2.66 broke wifi calling on my Nexus 6 and I'd like to get it back.
If I unroot, wifi calling works fine, but as soon as I do systemless root, it breaks.
Works for me on stock rooted 6.0.1 on tmobile (no fi) Check your apn. I seem to remember some of my settings were changed when I flashed.
I'm having the same issue with systemless root. If I put the phone in airplane mode wifi calling works on Fi, but not when airplane mode is off.
Hello ^^
I am hoping that some of you guys can help me out of a little issue that i am having, i will try and explain what has happened up until now as best i can:
As many people know, the latest update to Pokemon GO, knocks out rooted users. I did not know this and updated last night, however, dispite running a custom ROM (PureNexus) and being rooted, my game loaded up like normal and let me play. It wasn't until i checked that my SuperSU that i found that root wasn't actually working at that time, so i re-flashed the latest Super SU and all was good, but, obviously, this knocked out Pokemon GO.
I read up on the trick of using Magisk to be able to turn off root and when was needed as to get the game to work, so i went about trying to get it working. I unrooted via Super SU and then rebooted and flashed the Magisk installer and PHH Superuser (as i heard this was best for compatability). After the phone rebooted i, installed the Magisk launcher and the PHH SU program from the Play Store, but when i opened any app that reuqited root, it was still telling me i wasn't rooted anymore, and thus, when i opened PGO, it worked.
I am kinda lost from here, i want to get my phone rooted again, and i want to get Magisk working so i can still enjoy PGO and some of my occasionally used apps that require root, so my questions are as follows:
1. Can you re-flash an SU over an old one to get root back, or do i need to fully un-root and root again?
2. If i was to re-flash SuperSU (with Magisk support), would this get me rooted again and allow me to flash Magisk as normal?
I am a little lost here, any and all help would be appreciated.
Thanks to all in advance.
Have you tried Root Cloak xposed module?
Sent from my Nexus 6P using Tapatalk
jxcorex28 said:
Have you tried Root Cloak xposed module?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
i have, it doesnt work as PGO uses safetynet, like Andriod Pay
Ohh snap, well that's all I had...I don't play PoGo
Sent from my Nexus 6P using Tapatalk
For magisk to work, you have to use it to root and unroot. From what I understand, it temporarily removes root system wide when you do this. Basically it's a more convenient way to root and unroot.
Android Police has an article on it right now. The instructions for installation and usage are correct.
The problem is probably related to a failure to make sure all traces of previous SuperSU installations are gone.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk
For magisk to work it's best to fully unroot, maybe try unsu.zip,
Then have a 100% stock system and boot (kernel)
And before flashing magisk and phh, try the SafetyNet checker app in the playstore. (PoGO uses SafetyNet to check for root, same as Android Pay)
If you pass then go ahead and flash magisk, phh, and then phh app followed by magisk manager
In the magisk thread are all the instructions to follow
Sent from my Nexus 6P
Hi! I'm losing my root access in random times. I'm using RR 5.8.3 20170523
Edit: Now, I can't get it anymore.
DogeLordTR said:
Hi! I'm losing my root access in random times. I'm using RR 5.8.3 20170523
Edit: Now, I can't get it anyway.
Click to expand...
Click to collapse
1) This often happens when magisk hide is enabled.
You will either need to:
- Disable magisk hide
- Disable magisk busybox
- Or go to battery optimization settings and disable battery optimization for magisk manager
2) In some custom roms (known: LineageOS), enabling
the Magisk busybox will make root unstable
If you experience root loss issue, disable busybox
in MagiskManager.
Boomshiva said:
1) This often happens when magisk hide is enabled.
You will either need to:
- Disable magisk hide
- Disable magisk busybox
- Or go to battery optimization settings and disable battery optimization for magisk manager
2) In some custom roms (known: LineageOS), enabling
the Magisk busybox will make root unstable
If you experience root loss issue, disable busybox
in MagiskManager.
Click to expand...
Click to collapse
Thanks for solution but the problem is: I can't disable/activate magisk hide and magisk busybox after losing root access.
DogeLordTR said:
Thanks for solution but the problem is: I can't disable/activate magisk hide and magisk busybox after losing root access.
Click to expand...
Click to collapse
I don't have access to my zenfone right now. So can't help you much about magisk . And magisk is partially supported right now so its obvious you will run into such situation . Try reflashing magisk +patched kernel . That's what i can say for now . Thank you .
DogeLordTR said:
Hi! I'm losing my root access in random times. I'm using RR 5.8.3 20170523
Edit: Now, I can't get it anymore.
Click to expand...
Click to collapse
clean flash the latest build, to get root access flash su adon.no need of magisk
I am planning to eventually root the stock rom of SM-T580 to use AdAway and Greenify.
What sort of problems / side effects if any might I run into after rooting the stock rom?
Also I do not plan on using SuperSU as I will be using Magisk.
Some apps can not be installed anymore. (Netflix from playstore, super mario). Magisk does not prevent this. Use a browser with an ad blocker.
bert73 said:
Some apps can not be installed anymore. (Netflix from playstore, super mario). Magisk does not prevent this. Use a browser with an ad blocker.
Click to expand...
Click to collapse
Not even with Magisk hide enabled?
Not on my tab s2 with magisk.
Netflix working fine here with Magisk 13.0 and Stock Android N. But on my OnePlus One Netflix isn't available even with Magisk.
Shadowghoster said:
Netflix working fine here with Magisk 13.0 and Stock Android N. But on my OnePlus One Netflix isn't available even with Magisk.
Click to expand...
Click to collapse
When updating Magisk is it better to use the uninstaller zip and flash Magisk again or is using the built in updater fine?
You can't go wrong any way you use magisk. Mostly everything can be flashed directly from magisk. Remember magisk is root and has control. You won't have any problem updating magisk right from it's interface. The only time I've had a problem, has been from flashing a magisk module that doesn't support my device. Best regards.
Watsapp and some other apps still detect root even after using Magisk hide. Any suggestions ?