I think that comment was referring to the checks inside microg settings, which indicate that microg has been properly installed, and not to safetynet, as some piece of the protocol used by apps to request safetynet verification is not properly implemented in microg. (see https://github.com/microg/RemoteDroidGuard/issues/24)Actually, by looking at the thread of the underlying ROM that is used to build this /e/ ROM, it seems like one person was able to install LOS+microG and have all the safety checks validated.
So when I have some time I will give a try to get the same kind of thing working on this /e/ ROM.
I guess that ideally we would want all the safety checks validated directly upon install, but I'm not exactly sure if it's technically possible to pre-patch the /e/ ROM image with those changes.
@Anghirrim do you think it would be possible ?
Yeah, as far as I know, Safetinet is broken with MicroG, whatever ROM you are using...I think that comment was referring to the checks inside microg settings, which indicate that microg has been properly installed, and not to safetynet, as some piece of the protocol used by apps to request safetynet verification is not properly implemented in microg. (see https://github.com/microg/RemoteDroidGuard/issues/24)
Before you flash, please read this post on the /e/ forums@petefoth , feel free to update the links here too!
Looks like there was a problem uploading to Android File Host. I've deleted the corrupt files and uploaded the built versions again.
Sorry I can't be much help as I don't own one of these devices .I've installed and run with success on my beyond2lte, but have 1 issue.
I can backup system (et al) with TWRP, but not data. It errors out with a createTarFork() 255 error.
All research I've seen on this error is to delete the offending file listed in the generated log, but I've tried deleting a large number of files through a large number of backup attempts. But, sadly, there is always a new file that causes the error. So, I gave up.
To be fair, this occurs on /e/ 0.12 and 0.13 also. Does anyone know how to fix or bypass this? I really can't use the rom if I can't backup and restore fully. So, for now, I've resigned myself to LineageOS 18.1, but I'd prefer /e/.
And, no, I'm not doing dirty installs - I'm wiping and formatting.
FYI - I have been able to backup data on Lineage and the stock rom - but /e/, no luck at all.
Any help or advice would be much appreciated.