They could be detecting the Superuser app. Or any number of things. It's all speculation without any logs .i have wierd problem.... i am able to pass safety net ..... pokemongo works fine ..... even magisk hide works well on some apps like titanium , terminal emulator ... but there are some apps which still detect root even after selecting them in the magisk hide app list.... any thought about what might be the problem ... i am on a lineageos based rom.... which had cm root before i flashed magisk..... currently i am using phh superuser installed by magisk automatically ......
As CaptainThrowback suggested, some apps simply detect superuser is installed. The AT&T U-verse app does for sure. I did some experimenting with that. Removing the app without unrooting made it not detect root (I don't recommend this) and installing superuser without rooting made it not work. This is how I figured it out. No solution though.i have wierd problem.... i am able to pass safety net ..... pokemongo works fine ..... even magisk hide works well on some apps like titanium , terminal emulator ... but there are some apps which still detect root even after selecting them in the magisk hide app list.... any thought about what might be the problem ... i am on a lineageos based rom.... which had cm root before i flashed magisk..... currently i am using phh superuser installed by magisk automatically ......
Hello, I've got everything working with root and xposed but I just can't pass the safetynet check, I don't really need to but the ocd in me can not stand to see that big red box saying failed.
I am uaing this ROM (I guess is the problem)
It comes rooted but I did a full unroot in superSU and restored boot image.
Then flashed latest magisk in TWRP,
Then installed systemless xposed and phh superuser to manage permissions. Magisk works to hide root which I tried with root checker. But I'm guessing there is some other system modification in this ROM being detected by safetynet?
I've attached some screens and logs as well.
Magisk Hide have never been able to hide Xposed. I believe you can disable Xposed (and reboot) though to pass Safety Net, but I don't use it myself so I've never tried. I'd suggest you should read the Official announcement thread. Pretty much all you need to know in there. If you've got questions after that, search this thread. Most questions have already been asked and most of those have been answered (several times).
And by the way... Why so many apps on your hide list? Do all those really need to have root hidden? Youtube? Or where you just hiding stuff on random trying to make things work. For Safety Net nothing needs to be hidden on the list. It's just for apps that don't use SN to find root... Too many hidden apps might actually break your root in certain circumstances (again, read the Official announcement thread).
Yeah I'm not sure as it won't even pass without xposed. Oh and I'd just hidden everything while messing about. I'd actually unticked everything before I copied them logs. So nothing is hidden now anyway. I guess I'll just leave it as is now seeing as it all works and I don't actually use any apps that use safety net. I've read all of the announcement thread and searched as much as I can but nothing I do will let me pass the check..I guess I'll give up and leave it. It's not affecting anything. I'll look into it again if I ever need one of these apps that detects modified systems.
Thanks anyway though
I tried flashing this on my Honor 8 and it seems to work, boot, and pass safety net, the only issue is it seems to break the fingerprint reader. The Fingerprint ID menu gets removed from Settings. It can be found by searching, but will not let you add a Fingerprint to it, and also removes some of the other features tied into Fingerprint ID, such as swiping down to open notifications. The button itself still works as I can still set and use that. I then flashed stock boot.img back and everything was working again. I don't know if it's something such as a prop that is getting set that disables it based on security or if it's just in the way that it modifies the boot.img and is breaking something in Huawei's implementation. I grabbed two logcats, one before flashing magisk and one after. Unfortunately I don't know enough about where to look or what I'm looking for exactly to try and figure it out. If anyone could help out that would be greatly appreciated, if not, it's not a big deal as I have my HTC 10 with Magisk working quite nicely.
This happened to me! Yesterday I updated Magisk to v10.2 on my Honor 8 and the fingerprint stopped working. What should I do to fix it? I need root on my phone for so many things and I need to have fingerprint working, since it saves a lot of time. I can't just unroot it
I pulled the getprop log as suggested by Captain Throwback and didn't find anything different. I think it's something to do with the way Magisk is modifying the boot.img and probably related to the way Huawei codes. Even in the logcat it looks like everything initializes and then it just errors out. I just used the Charles app method to flash the latest N beta, so I'll unlock bootloader and try flashing Magisk on that to see if it works on N.
This is incredibly annoying. I come back home just to sleep and I don't have to time to play around and see how to make it work again.
Could someone explain me how to unroot ( I have magisk v10.2 + phh superuser) so I can install magisk v9 that used to work? I have Honor 8 and Android 6. When unrooted I'll also update the phone ( Not to android 7)
I have a Pixel 4A without a custom recovery. I use fastboot to install MagiskHi from greece! I have a pioneer SDA8TAB android 9,followed the magisk steps for recovery method as the tablet doesn't have ram disk but it doesn't work, I can't try other method cause this device does not have custom recovery and I cant find a way, anyone can help? I have full system dump made from emmc easyjtag
The point of Magisk is to *not* patch the system image.Thanks! Yes it boot to recovery, tried few times but root not working, there is a forum but they don't know something, I also sent the the files to try, yes sda835a, in greece yes different name, is any other way? Any way to patch the system. Img may be? Or someone who can make twrp for this device?
You might be able to patch the boot image. Sometimes it works, even though the original boot image does not have a ramdisk.
I have NOT read all the posts. But to flash the boot image, I do NOT go into recovery, it is dlashede in fastboot. CAn you get into fastboot? and can your PC "see" the phone in fastboot mode?Thanks! Yes it boot to recovery, tried few times but root not working, there is a forum but they don't know something, I also sent the the files to try, yes sda835a, in greece yes different name, is any other way? Any way to patch the system. Img may be? Or someone who can make twrp for this device?
As mentioned by @J.Michael, I think you have likely already succeeded in flashing root w/ Magisk in recovery ramdisk since it flashed without errors, and you don't get bootloop.
Hm, funny things happening. I was thinking this is upgrade of HW attestation, but it is DOWNGRADE actually.
Yep, I have sent a Pull Request with the fix like an hour after v2.1.0 was released.Removed the @Displax safety net mod fix and applied the latest USNF 2.1.0 from @kdrag0n.
Attestation is passed and device is compliant in company portal too with my original device name 1+8 Pro and not Pixel.
This is done over the latest Alpha Magisk.
Update: My In-display fingerprint hardware is not working anymore, I think the fix is already committed. Hopefully it will be resolved in the next version.