I have unlocked bootloader installed twrp and rooted with magisk. The fingerprint enroll feature now fails. I have tried changing dpi (small medium large) but still fails. Has anybody rooted and still had access to fingerprint sensor?
Bump
purpse said:
Bump
Click to expand...
Click to collapse
I have rooted and fingerprint works fine. I did not use Magisk though. I just flashed super user via twrp. There are so many threads and different methods to root it was overwhelming. Luckily the way I chose worker. Go back to stock unrooted and root a other way.
Sent from my BTV-W09 using Tapatalk
Yes I tried both magisk and supersu, same result. Are you on android 6 or 7?
purpse said:
Yes I tried both magisk and supersu, same result. Are you on android 6 or 7?
Click to expand...
Click to collapse
7
Sent from my SM-N920P using Tapatalk
purpse said:
Yes I tried both magisk and supersu, same result. Are you on android 6 or 7?
Click to expand...
Click to collapse
<< 6 installed twrp, su, xposed it works here.
Got it working now. Unlock bootloader, install twrp, SET UP FINGERPRINTS. Lastly install super su.
Installing su before settling up fingerprints broke the sensor for me.
Finally happy with my M3
Related
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 guys I just unlocked my A7 and Im not able to flash the latest Supersu zip. When I begin flashing it freezes on "Extracting Files" then the phone reboots and stays off. Anyone had this issue before?
perez6991 said:
Hi guys I just unlocked my A7 and Im not able to flash the latest Supersu zip. When I begin flashing it freezes on "Extracting Files" then the phone reboots and stays off. Anyone had this issue before?
Click to expand...
Click to collapse
Try this version 2.65 I think this is the only working one, after flashing it you can update the su bin through the app.
I flashed this version via twrp but after a brief boot to zte screen it goes back to black, it's been sitting over 5 minutes and hasn't rebooted... Anybody have any ideas? On b20 currently
On unlocked b27 and I'm wondering if it will work flashing supers 2.65 to get root
Sent from my ZTE A2017U using XDA-Developers mobile app
troy5890 said:
On unlocked b27 and I'm wondering if it will work flashing supers 2.65 to get root
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
I did this last night on unlocked B27 - flash SuperSU 2.65 - it works
tabletalker7 said:
I did this last night on unlocked B27 - flash SuperSU 2.65 - it works
Click to expand...
Click to collapse
Thank you very much, I'll try it after I make a twrp backup.
Sent from my ZTE A2017U using XDA-Developers mobile app
Unfortunately it's not "true" root. Xposed works (latest version), but trying to debloat the ROM via Titanium backup doesn't work. So editing system apps isn't doable yet. And updating busybox doesn't seem to work either.
perez6991 said:
Unfortunately it's not "true" root. Xposed works (latest version), but trying to debloat the ROM via Titanium backup doesn't work. So editing system apps isn't doable yet. And updating busybox doesn't seem to work either.
Click to expand...
Click to collapse
That seems a little disappointing at the moment. I'm just glad I can run Ubuntu and other distributions now.
Sent from my ZTE A2017U using XDA-Developers mobile app
perez6991 said:
Unfortunately it's not "true" root. Xposed works (latest version), but trying to debloat the ROM via Titanium backup doesn't work. So editing system apps isn't doable yet. And updating busybox doesn't seem to work either.
Click to expand...
Click to collapse
If you mean SuperSU 2.65, yes it is a true root. /system is write-protected even if you unlock your bootloader and root. Once you disable write protection, you can do TiBu fine, AdAway fine, etc. Just a one-liner: http://forum.xda-developers.com/axo...to-persist-t3440276/post68206618#post68206618
perez6991 said:
Unfortunately it's not "true" root. Xposed works (latest version), but trying to debloat the ROM via Titanium backup doesn't work. So editing system apps isn't doable yet. And updating busybox doesn't seem to work either.
Click to expand...
Click to collapse
That's because of ZTE's write protection. You have to do 'adb shell reboot disemmcwp' to disable it. I had the same problem but after I did this everything worked flawlessly
Hi Everyone, l have a question about this Magisk Mod and its directed to s7 & s7 edge users. If anyone is using this Mod, may you please tell us how you got it to work, coz l have tried and failed many times. Your help would be kindly appreciated..
King Addies
Root and install xposed.
I have used a stock rom, as it says on the magisk thread and followed all the instuctions and still failed.. lm not really botherd about using the mod anymore, but l made this thread so all the other people who are in my situation can get help or a tutorial on how to install it on s7 & s7 edge. Coz l could not really get much help from the official thread.
King Addies
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Mr. Orange 645 said:
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Click to expand...
Click to collapse
Thanx for your input on this issue mate, hope the info you have provided helps all those that want to use this Mod on their s7 or s7 edge phones..
King Addies
One more step, sorry. You have to also install Phh's SU app from the Google Play store.
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Galactus said:
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
Click to expand...
Click to collapse
kevinwu128 said:
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Click to expand...
Click to collapse
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Galactus said:
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Click to expand...
Click to collapse
Maybe I did have it working then, the only thing I tested it with Pokemon go and it didn't work.. so I just assumed it wasn't working, so I reverted all changes. I spent way too much time than I had hoped
Cheers Buddy
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Devilover said:
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Click to expand...
Click to collapse
Magisk is pointless right now. Simply having an unlocked bootloader causes SafetyNet to fail. The latest version of magisk also removed the checkbox to turn root on and off. To use Snapchat YOU MUST login before any modifications. Make a titanium backup of Snapchat logged in, then you can restore it whenever you want.
silverrum said:
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Click to expand...
Click to collapse
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
PoTBrain• said:
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
Click to expand...
Click to collapse
What part of S7/S7Edge do you fail to understand?
Or, boot into TWRP, format data to unencrypt then flash latest magisk and reboot. Once booted, open magisk manager hit menu button and open settings, check magisk hide. Exit settings, open menu and open magisk hide, there you can check any app you want to hide from root. done.
So I possibly did something stupid?
Flashed supersu over cm14-111417. How I've lost root. Can't seem to get it back. Super su crashes when I open it, and the root option under developer options gives me two options: disable and ADB only. I'd rather avoid a factory reset if I can help it. Thoughts?
Sent from my Nexus 6P using Tapatalk
Droid_JD said:
So I possibly did something stupid?
Flashed supersu over cm14-111417. How I've lost root. Can't seem to get it back. Super su crashes when I open it, and the root option under developer options gives me two options: disable and ADB only. I'd rather avoid a factory reset if I can help it. Thoughts?
Click to expand...
Click to collapse
Which version of SuperSU did you flash? Did you disable root in CM since you decided to use SuperSu?
Latest su, sr3.
Initially I did not disabled cm root. Things stated being word though, I tried to remove su, root stopped working, I lost root-app access. Though of I disabled cm root, and flashed su again it would fix itself... Nope!
Sent from my Nexus 7 using Tapatalk
Hey,
I have an Exynos S7 Edge with G935FXXU1DQB3 (nougat) stock rom. It's unlocked, supersu 2.79 rooted systemless, and has TWRP.
I've been trying to install Magisk to no avail.
When I try to flash Magisk on top of supersu systemless, I get a "not enough space in the boot partition" error. If I flash the original boot image, flash phh's superuser, then I get no prompts for superuser requests for apps.
Another interesting thing, with phh's, magisk says the device is rooted, but no root access is authorized (Grey error box).
Regardless of this problem, if I flash magisk on top of phh's, then I end up with a boot loop.
In theory, magisk should work with systemless supersu.
Any ideas?
I think you need to install magisk first then install supersu or phh on top of it if you want.
Magisk have it's own root though if you don't know.
Sent from my SM-G935F using Tapatalk
I tried to flash magisk before all else, and still, bootloop.
I'm assuming this is an incompatibility with the stock rom and I just need to look into a custom rom.
Sent from my SM-G935F using XDA-Developers Legacy app
ScreAmeR01 said:
I tried to flash magisk before all else, and still, bootloop.
I'm assuming this is an incompatibility with the stock rom and I just need to look into a custom rom.
Click to expand...
Click to collapse
I am wondering could it be because stock rom has encryption enabled and custom roms dont perhaps?
simonbigwave said:
I am wondering could it be because stock rom has encryption enabled and custom roms dont perhaps?
Click to expand...
Click to collapse
I doubt that. A whole bunch of ROMs are encrypted, yet Magisk works on them. I'm thinking deoxed, but I can't be sure.
One thing I know is that I tried everything I could think of.
I'm going to try one of the super stock ROMs, and see how it goes. I'm weary though, people complain about WiFi issues, camera issues, mic issues... Don't know.
Sent from my SM-G935F using XDA-Developers Legacy app
NonXtreme said:
I think you need to install magisk first then install supersu or phh on top of it if you want.
Magisk have it's own root though if you don't know.
Click to expand...
Click to collapse
Noob question (I had a rooted S4 but new to G935F) , so if we install no need to root with Chainfires SuperSu then right? Then why flash SuperSu on top?
simonbigwave said:
Noob question (I had a rooted S4 but new to G935F) , so if we install no need to root with Chainfires SuperSu then right? Then why flash SuperSu on top?
Click to expand...
Click to collapse
Yes.
The reason why people flash supersu on top might be because of some compatibility issue that might rise from magiskSu since magisksu is still quite new but supersu have been exist for a long time.
I have never face any issue with magisksu though.
Sent from my SM-G935F using Tapatalk
Update: over the last 24 hours, I've been using SuperStock 2.5 ROM. I have to admit that I am pleasantly surprised. Here's a quick review, for those who might be interested:
1. I switched from stock. Flashed it dirty, meaning system partitions only. My data and apps were kept intact.
2. Aroma installer is cool, loved the options.
3. No camera issues, no Bluetooth issues, no WiFi issues, no mic issues. In fact, so far, no issues none whatsoever.
4. My accounts, WiFi passwords, and Bluetooth pairings were gone. I wasn't expecting that. I reversed back to my original stock (always back up), made titanium backups for those, switched back to the ROM, then restored them back.
5. Magisk and supersu is working fully. Android pay also works. I also installed Google assistant thru magisk. I'm loving it.
6. No xposed yet, since it's nougat. It sucks, but it's not the ROMs fault.
7. I did not flash the Bluetooth and modem. I like what I had, and I'm keeping them
8. I don't do GApps. I like the stock apps.
For those of you who are looking for a variety, I recommend SuperStock. I tried lineage, remix and a few others, SuperStock seems to fit me the most. Magisk is the obvious benefit, and battery seems to be the same as before.
Sent from my SM-G935F using XDA-Developers Legacy app
One more update: someone asked me about snapchat and Pokémon, whether they work. I have no idea, I'm too old for those things.
Sent from my SM-G935F using XDA-Developers Legacy app
ScreAmeR01 said:
One more update: someone asked me about snapchat and Pokémon, whether they work. I have no idea, I'm too old for those things.
Click to expand...
Click to collapse
i have also never ever used snapchat or pokemon .. lol.