doesn't work on devices with Broken TEE like oneplus devices or rog3
doesn't work on devices with Broken TEE like oneplus devices or rog3
Whaaat, I don't know why that happen XDBootloaderSpoofer + KeyAttestation 1.3.4 bootloader shown as locked
BootloaderSpoofer + KeyAttestation 1.4.1 bootloader shown as unlocked
What could be the reason for this?
Rog3 has a broken TEE but in a good way xDdoesn't work on devices with Broken TEE like oneplus devices or rog3
InstaPay doesn't check bootloader status, I have latest Magisk Alpha (26102) + Shamiko and I can bypass it
No, I saw a post in Reddit with people complaining about this app.
No, just Paypal
Thanks
Ok np give me your paypalNo, I saw a post in Reddit with people complaining about this app.
No, just Paypal![]()
In previous appdome versions attestationspoofer works well?Hi. Has anyone researched Bet365 authenticator? It uses appdome and since new versions it started checking bootloader state. This app doesn't work, probably because it checks certificate issuer. Could someone help me with it?
It is not needed cause Appdome started checking bootloader just in a new version
Yeah, it checks your bootloader status and detect injection like Xposed. Sorry but I can't help you more, if you want to use that app you must lock your bootloaderHi. Has anyone researched Bet365 authenticator? It uses appdome and since new versions it started checking bootloader state. This app doesn't work, probably because it checks certificate issuer. Could someone help me with it?
I could bypass xposed detection but not bootloader... It checks that certificate issuer is Google and detects it as Strong play integrity does. That's sadYeah, it checks your bootloader status and detect injection like Xposed. Sorry but I can't help you more, if you want to use that app you must lock your bootloader![]()
How could you know if you bypass Xposed detection? Also the app can't check Strong because isn't in Google Play...I could bypass xposed detection but not bootloader... It checks that certificate issuer is Google and detects it as Strong play integrity does. That's sad
There are different messages for them. For instance, for frida, for magisk, for developer settings and for bootloader.How could you know if you bypass Xposed detection? Also the app can't check Strong because isn't in Google Play...
you know how they check bootloader status?
I hooked bootloader check in keystore bia xposed. I hooked it to throw exception and app crashed. Without throwing exception app closes on its behalf but with it it crashes without any messages
Which method did you hook and which throw class did you use ?I hooked bootloader check in keystore bia xposed. I hooked it to throw exception and app crashed. Without throwing exception app closes on its behalf but with it it crashes without any messages
Yep, you must make your super.img partitions read-write and modify it from recovery. You can modify it unpacking the .img or using systemRW script from here link this:
This has (happily) proved to be incorrect.Uber driver requires Strong integrity, you must install stock rom and lock bootloader to use it.
A long trial and error procedure, I will attach the procedure below...
As I said even I locked bootloader still tee broken and can't restore strongintegrity so I will continue using device with root and ignore this bank app cause everything is working good no issues faced.As I said, this generally means OEM messed up... And I've never heard of post production fixes for this...
I believe even China hardware/firmware should support AVB/key attestation correctly even when Google APIs are not used...
So you could complain/enquire of Xiaomi but doubtful if they can/will help...
Or continue using rooted with root fixes supporting broken keymaster, but when/if banks start enforcing strongIntegrity you would be able to restore that by locking...
There is a slim chance you've messed up /persist as Poco users (notably) experienced, but Symptoms look different to me... You have L1 and other stuff working it seems... Please say if you have issues with SIM, BT, WiFi, seeing IMEI and S/N etc (normally /persist corruption signs, even if stock/locked)...
PW
I tried it before but with Magisk magic and it worked! But I will need to study how to implement this in better way. I just throw an exception in engineGetCertificateChain, Momo don't detect it due it's not injection.Not exactly what I was hoping for but thanks for your answer nonetheless
Yep, you must make your super.img partitions read-write and modify it from recovery. You can modify it unpacking the .img or using systemRW script from here link this: