And as I said before, following all the steps is a must. And once you get the gist, it's a matter of 10 minutes at mostNow it will have to be root and Magisk, I did a lot research, sadly this is the only way now
And as I said before, following all the steps is a must. And once you get the gist, it's a matter of 10 minutes at mostNow it will have to be root and Magisk, I did a lot research, sadly this is the only way now
What your experiencing is exactly what can happen as a result of wiping the framework data. I myself only wiped Google play services, wallet and Google play and all is fine for me. The link in my previous post explains everything. You may have to wait some days or weeks for all the apps to start working correctly again.Yes, I did.
Yeah, I just flashed Magisk Delta, perfectly solved banking issueAnd as I said before, following all the steps is a must. And once you get the gist, it's a matter of 10 minutes at most
You cannot. PIF module is not a static change to be patched to the ROM.And how to patch firmware? Well here on the 9th the problem appeared, the next day here posted a stable firmware with a fix and contactless payment worked without installing root and magisk, then on the 18th it disappeared again, maybe there are instructions on how to patch the firmware, so that I myself patch the latest firmware version with the latest patch and install it as usual, without playing with magisk?
Well, I guess I'll just have to wait. Hopefully all the notifications will start working automatically again soon. Anyway, thanks for the explanation!What your experiencing is exactly what can happen as a result of wiping the framework data. I myself only wiped Google play services, wallet and Google play and all is fine for me. The link in my previous post explains everything. You may have to wait some days or weeks for all the apps to start working correctly again.
Then how was it implemented in the firmware stable rom? Previously, I just installed the firmware and everything worked, so I thought there was a way to patch it into the firmware and flash it.You cannot. PIF module is not a static change to be patched to the ROM.
PIF module runs as a Zygisk service - hence you need Zygisk started by Magisk at the time of booting (when Magisk initializes)
Well, I did clear all data in the framework too, but I never experienced any delay in the notification department... I guess not everyone has issues with thisWell, I guess I'll just have to wait. Hopefully all the notifications will start working automatically again soon. Anyway, thanks for the explanation!
Perhaps @Kacper Skrzypek should mention this in his original post.
Try Magisk delta, it's not open source but better at hiding it's activityHi the wallet works now using this way but 2 of my banking apps no longer work as they wont run on a rooted phone, they did work before this latest workaround for wallet. Does anyone know what to do to make them work, i have already tried configure deny list for barclays and it doesnt work.
Use twrp, it's much easierHey Guys, I m on fuxi and I tried to follow the guide but I m stuck on extracting the init_boot.Img... Cant find a tool which can do it. Its says always invaild file or damaged. please help
windows cant open it, winzip, winrar, virtual clone drive, anyburn... which too should I use?
Yes but step 2 is to unpack init_boot.img. And it seems the files is damaged. Cant unpack itNo. Meant install Magisk.apk or Magisk.zip in TWRP.
That Barmer app ?After a new install (latest stock A13, then TWRP, xiaomi_eu, ...), my Poco F5 Pro passes YASNAC basic and Play Protect is certified. Wallet set up worked, ING bank app is fine, too.
Just one app (for health insurance) gives a "keychain attestation failed" error, I can't use FP or face unlock to log in because of this. Does one know which apps or OS parts are to exclude, apart from this app? Or which Magisk module I need to fix this?
Thank you! w.
Youre not supposed to unpack that, it's means you get that .IMG after unzipping rom. Guide needs a little wording tweak i guess.Yes but step 2 is to unpack init_boot.img. And it seems the files is damaged. Cant unpack it
Gesendet von meinem 2211133G mit Tapatalk
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation