App will not run, says device is rooted

that’s my output

ich@ich:~$ adb logcat | grep RootBeer
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /data/local/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /data/local/bin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /data/local/xbin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /sbin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /su/bin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/bin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/bin/.ext/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/bin/failsafe/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/sd/xbin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/usr/we-need-root/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/xbin/su Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /cachesu Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /datasu Absent :(
07-15 20:06:42.260  4690  4690 I RootBeer: LOOKING FOR BINARY: /devsu Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /data/local/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /data/local/bin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /data/local/xbin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /sbin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /su/bin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/bin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/bin/.ext/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/bin/failsafe/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/sd/xbin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/usr/we-need-root/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /system/xbin/su Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /cachesu Absent :(
07-15 20:06:42.377  4690  4690 I RootBeer: LOOKING FOR BINARY: /datasu Absent :(
07-15 20:06:42.378  4690  4690 I RootBeer: LOOKING FOR BINARY: /devsu Absent :(

as you can see, the app needs saftynet and thousand other goolag play services. That’s why it never will work on eOS

No more positives there :slight_smile:

@trond is probably right that the different error code corresponds to a different test, most likely a different library or something custom.

Maybe the full log contains more hints?

Edit: I thought /e/ had a sandboxed version of safetynet for this purpose?

no, no safetynet on eOS

What makes you say that? It says there is in my microG settings, ref screenshot.

1 Like

From my knowledge, safetynet is always failing on eOS because of missing services.

pls have a look here Advanced permissions management

He was talking about rooted roms, but that’s not the case for me at least. I’m running unrooted on a FP3 with a locked bootloader. I might need to install “droidguard helper” though. I thought “available” meant “available on my device”, but perhaps not?

On my recently reinstalled /e/, I seem to have “microG DroidGuard Helper” installed and running (found via Settings -> search “droid”). Not sure how microG uses this, though - in microG Settings it says “Google SafetyNet - Enabled / official server”, and when I press it, I get the same “Google SafetyNet” screen that you do.

@harvey186

You’re right, I have it running as well.

@harvey186, do you have the same setup as us?

I do have standard eOS with MicroG and unlocked bootloader on a Mi 5s.
So it’s the same as yours

have you tried ‘safetynet test’ from Aurora ??

SafetyNet was working on /e/ before summer 2019 thanks to MicroG, but sadly Google changed the way SafetyNet works and MicroG isn’t able to bypass it anymore. That’s why there is this useless SafetyNet section in MicroG.

2 Likes

We (me and @trond) both have a locked bootloader. That could be a difference. I’ll try the test app.

Edit: It fails for me too. MicroG core crashes consistently during the test.

Ok. I would like to thank you both @aig and @harvey186 for your efforts - as a normal /e/ user I really appreciate it!

It seems that changing build mode to user makes the Rootbeer checks pass, but there are still security tests in the Vipps application that fail, and we don’t know which. Is that an accurate summary of the situation?

yes and I have tried some other hacks and getting errors like 2-5-6 :frowning:

OK, thank you @harvey186 for testing stuff! I assume this included the “how to install banking apps” with Magisk and Busybox that you linked to very early in this thread, back in May?

I guess that’s as far as we come, at least this time. Thank you to you and @aig once more.

Yeah I guess this is as far as we get for now. We know that a user build would solve one problem, but that others remain. I think it’s likely that we’d need safetynet to work, but that’s up to MicroG to resolve.

Thanks to you too @trond, I hope we can get it working at some point in the near future :slight_smile:

Hey! As you can see by looking through this thread, there is no solution yet. @harvey186 and @aig got one step closer by setting build mode to user, but there are still problems with SafetyNet and it’s probably up to microG to solve it. :slightly_frowning_face:

Hi, I know this was supposed to be without root, but the only way I got this app working was of course with root.
So to anyone it might concern: use magisk, magisk hide (microg core, vipps and phone, rootbeer uses phone) and hide magisk manager.

1 Like