Related
I am still a green beginner when it comes to making a custom firmware but I basically only do it for my personal needs and offer the result for everyone.
However, there is one thing really nagging me ith the X96 and that is to get updated GAPPS to work properly and with all Google apps.
The basics like Playstore, Framework and Play Services and managed to get going but only by disabling some "features" in the firmware and with the box showing up as uncertified.
Real problem is to get the TV GAPPS working at all.
No matter how I spoof the build.prop, disable services and manully add permissions, the TV Gapps claim be on an unsupported device and demand dowgrade / removal of updates.
For a chinese phone I would simply flash an internation rom and be done with it but not so much on a chinese TV box
What I tried so far for the TV GAPPS:
Using custom roms claiming to work for several boxes including the X96.
Here the rom either fails to boot unless I modify it or if it boots then nothing, and I mean nothing all works.
Funny enough that some user of a X96 say they have no problem with the same rom...
Next was to clean the original firmware from all Google related apps, services, scripts and libraries, then manually installing the TV GAPPS.
For this I always get the error that the device is not compatible.
Even if in the build.prop a Mibox or Nvidia Shield is spoofed together with ro.build.characteristics=tv.
Last but not least the Open GAPPS TV version.
Flashing works just fine and with no errors, on a cleaned and on a standard rom.
After that it is all over.
Setup Wizard crashes, if disabled or removed the other Google apps and services crash, usually starting with the TV Wizard and TV Customisation.
TV Playstore again claims the device is not compatible in the rare case it does start otherwise I get an error that the Play services are missing on the device.
But of course all is installed completely....
What I would love to know is how and where these chinese roms disable the Google compatibility.
Here is what I think I found so far that does not make much sense to me:
The supplied Playstore is signed with different key than anything else on the system partition.
The same version number from APKMIRROR fails to install or work if replaced in the rom.
I tried signing with the Amlogic platform, test and release keys to no avail.
Both by zip aligning before or after the signing.
Other apps I sign with these keys perform just fine.
Just to be able to use the Open GAPPS through TWRP I had to disable a PPoE apk that runs presistent - with that active no open Gapps pack works (claiming device is incompatible or simply crashing).
There are a bunch of additional certificates installed in the ETC folder than when removed or renamed cause the system to fail - I had no time so far to do a one on one check to figure out for what each cert might be used.
When comparing fstabs with other roms it seems the X96 has lot more than what would be required but my understanding of all that is still too limited.
I guess the big question is:
Does anyone know what is causing all these problems in chinese roms and how to fix it without flashing a firmware for different TV box?
Update:
On my X96 I am slowly making progress with the GAPPS.
Found a PPPoE app and service that are set to run persistent.
According to some funny Google translations from chinese websites using persistent services to block genuine Google stuff is one available option.
By disabling the PPPoE persistent stuff and only leaving the normal PPPoE stuff active Ethernet and WiFi still work fine but now the Open Gapps installation actually works.
Well, not fully but at least the Nano package works flawless.
With that it is not problem to install the missing Google apps through the Playstore, including Google TV and Music.
Sync and backup works fine too.
Only downside is that without spoofing the device will be listed as uncertified - but all updates and installs so far went with no problems.
But even the Google NOW and Pixel launchers can be installed and used if someone likes them.
Different story though for the TV Gapps, wether modified or not.
Build.prop mods and fakes, using the latest and older versions of the playservices and framework - they all fail.
I managed a few times to find combinations that at least booted into the leanback launcher and that were usable except for the Google stuff but it was no fun.
No matter how I try to spoof or change the installation the setup wizard never works, which indicates the services fail to work.
In the rare case where I get somewhere I am told that I should unistall all updates as this version of Plastore or services is not compatible.
Will do some more digging on services and apps that should not be there but the chinese really like to disguise things they don't want anyone to see LOL
Hi. I have the same box and installed latest official firmware android 9.
My problem is that is not possible to update the Google play store, stuck on version 13. All other apps are updated by the stor with no problems.
But i cant find a way to updaye the play store.
When i try to update it, always give package error, simple instalation fail.
I have not found a working twrp for it, so no gapps for now.
Do you know of a solution ?
Many boxes from China do not have certification from Google, that's why you cannot run native TV apps on them. If you want these TV apps, buy those boxes labelled with "Google certified", which are of couse more expensive and with inferior hardware--certification needs extra cost, man.
You can try install magisk, whill will tell u Safenet test failed and some CTS failure, that's what I said above.
On Angler (Nexus 6p) I flashed the latest stock rom. (After a complete wipe) Afterwards I flashed TWRP and unzipped Magsik. Subsequently I did update to the latest version. After that I changed the packagename of Magsik manager. Furthermore I installed Xposed framework. Afterwards I enabled root hide for the TAN app:
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=en
This software is meant to give you the tan without using sms services.
Still, the app crashed right at the start without any error notification. Android Version is 8.1 and Magsik is v16. While I did the test, the bootloader was unlocked and TWRP was still the recovery. Can these two things affect the verification of the Banking app? I tried this several times ago in the past, but I was never to make this app running.
If anyone would be able to give helpful advice here, it would be very much appreciated.
Best,
scarline
I have heard that DKB Tan2Go does not work with newer Android versions like Oreo 8.1.x at all.
I can also confirm that. I tried it on a Sony cellphone. The cellphone was not rooted and with a completely new and 'clean' ROM. It was to no avail.
A friend has been forced to buy a chip reader. I am fortunate to be able to use normal TAN lists at the moment. If the DKB tries to exclude me from online banking, I will change the bank.
DKB Tan2Go seems to be one of the worst and most insecure apps ever. The reviews in Google PlayStore confirm this conclusion.
Maybe there will be a solution someday?
DKB TAN2go works with Magisk:
1. Install the TAN2go app (but don't open it)
2. Add the TAN2go app in Magsik Manager in the menu "Magisk Hide"
3. Reboot the phone (I don't know if this is necessary)
4. Open TAN2go, works fine.
**** DKB and this stupid security features which bring absoltuely no security.
That's exactly what I tried - without success. I read that it only worked with an old, obsolete version of Tan2Go. However, I could not find this version and I'm not sure if it still works at all. Did you have the latest version of Tan2Go from Google PlayStore? According to DKB, the recent Tan2Go does not work with devices that was once rooted or had a CustomROM. Even if you go back to stock the Root Counter changed and DKB Tan2Go will never work on this device. Unfortunately, I have to confirm that.
I am working on it to change the bank, because of that.
exaveal said:
DKB TAN2go works with Magisk:
**** DKB and this stupid security features which bring absoltuely no security.
Click to expand...
Click to collapse
Indeed!
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
I tried that to no avail. I heard once the root counter has a value other than 0, one can't go back. Probably it is also the Sony bootloader and it is different with other devices?
exaveal said:
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
Click to expand...
Click to collapse
I have a Xiomi Mi5 rooted with Magisk and Tan2go used to work for the last year or so. But yesterday I tried to make a transaction and BOOM! App crashed without an error message. Tried to use a newer Magisk, tried reinstalling the App, nothing helped.
The worst thing is that I do not know if some of my programs have a battery checker or a screen reader plugin that I am not aware of, or if Tan2Go suddenly detects my root. Regardless, crashing without an explanation is like the worst programming practice ever.
Since I do not need this kind of ****e in my life I will probably change Bank, I mean what good is an internet Bank if you cannot do transactions over your mobile device?
Well, willy-nilly I try to use the only other option from DKB: the German TAN Generator. Every other bank equips you with such a device, if they want you to use it. The DKB does not. Actually, I ordered the 3rd TAN Generator and fully paid for it. The first one drains the battery within days. The second one let me type in all the numbers and for no reason the TAN code does not show up on display.
These devices are very annoying anyway, because you have to type in a lot of numbers for every money transfer, the characters are very small (on the laptop) and you have to carry the TAN Generator + the DKB debitcard all the time. Of course this is less secure.
I would change the bank immediately, but want to keep the Visa credit card. I have higher limits on it. That's the only reason. As soon as I found an alternative bank in Europe, I will leave the DKB for good.
It dont worked with Lineage 14.1 but with 15.1 unoffical build on Samsung S4 together with latest Magisk .Rom from here
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-galaxy-s4-lte-android-8-1-oreo/
Works for me
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
DKB already updated their app - they patched it
kyodhin said:
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
Click to expand...
Click to collapse
The app version from September (version 2.3.0) does work, the newer app version from 4.4.19 (version 2.4.0) does not...
Tested working combination: Magisk 18.0, Magisk Manager 6.1, DKB version 2.3.0
Can confirm that, working with magisk and 2.3.0. Not working anymore with 2.4.0.
I have another Tan app from another bank and with the new version it also stops working. Seems that magisk is now quite to popular and they working on better detection. Magisk hide is useless on the recent version of these tan apps.
That really sucks. No way to get 2.4.0 working. Hoping for a magisk fix. Are the magisk developer informed that there are problems with magisk hide? I think others will have similar problems too.
I successfully got 2.4 working again, after it got updated and refused to start.
Following the steps from this post made it work again (German):
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
I installed Magisk 19.0 (beta) but contrary to the above mentioned post I left my Magisk modules installed as they were before the update.
Both the Magisk modules as well as TAN2Go 2.4 are now working again.
I had to authenticate the new TAN2Go installation by adding it as a "new device" using SMS verification.
I was not able to get it to run with the above mentioned instuctions.
Device: Nexus 6P (angler), ROM: LineageOS 15.1-20190419, Magisk modules: MagiskHide Props Config (required for ctsProfile test), Busybox for Android NDK (required for MagiskHide Props Config).
DKB Tan2Go crashes immediately when started.
Same for me. The above instruction doesn't work.
Downgrade to 2.3.0
I experienced the same problem. Had to do an important transfer yesterday. And of course Tan2Go-2.4.0 crashed. I'm using Magisk v18.1.
Today I did a downgrade via Aptoide to 2.3.0 and had to register the smartphone again via SMS. This worked without any problems.
To avoid the update problem and keep with 2.3.0:
Start Titanium Backup
Select the DKB Tan2Go App
Long click on the App.
Connect with Google Play Store (forced)
Long click the App again.
Disconnect from Google Play Store
Hope it helps. I don't think there's much to change in the DKB Api. I'll use 2.3.0 until they block it via the API.
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
musv said:
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
Click to expand...
Click to collapse
I have the same issue. Hopefully it can be fixed via Magisk one day.
Worked with T2G 2.4, 19, 7.1.1
Walhalla said:
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
Click to expand...
Click to collapse
Hi Walhalla,
Hi All
In Settings "General">"Hide" via other apk name it worked for me. V19.0, v7.1.1, Tan2Go 2.4
Apparently, my bank updated the app with a new feature that doesn't let me access it anymore, it says that the operating system is not supported, i use a custom rom(AEX) in my Redmi 4x, i believe that the rom is the problem, the root is being hidden with MagiskHide and i have no problems with SafetyNet, maybe i can change some parameter in build.prop to make it work? i did something similar to try to run Fortnite in my phone a while ago, any ideas on what parameters may be relevant to that?
It's a brazilian bank(Banco Inter)
Need Solution for this Problem as Well
I have the same problem.
The new app version 8.4.6 is not working while up till version 8.4.5 it was working just fine.
Their support is absolutely clueless on how to help, but as @Levyks said, apparently they are blocking custom roms now.
Is it possible to make the custom rom look as an original rom from manufacturer?
Same problem.
I'm with the same problem...
IMHO has nothing to do with fact whether it's a Custom ROM or a Stock ROM. Any app ( banking apps included ) easily can find out whether present Android OS got tampered or not.
Same problem any help? Can't use my bank app... WhatsApp also can detect I have a custom ROM, any solution?
Incomtus said:
Same problem any help? Can't use my bank app... WhatsApp also can detect I have a custom ROM, any solution?
Click to expand...
Click to collapse
Many apps like banking / payment apps today detect whether Android is got rooted or not: it's an easy for them to do so.
Same problem here in Lineage OS 18.1. My non-rooted device pass safetynet and CTS by default. But many Banking application had started detecting that I am using custom rom and don't open at all. Then I rooted my device with magisk and enabled 'magisk hide' but no success.
Hi! A solution that worked for me: use the renaming function in Magisk (you can find it in the Settings).
I had the same problem on a Redmi 4X, LOS 16, no working banking app even with Magisk hide. After renaming Magisk, I was able to log in and use it as intended. Also I left Magisk hide turned on.
My guess is that these kind of apps are looking specially for Magisk, and if it's detected, they just won't let you use them.
Expert Summary
Use Displax's USNF Mod to pass the new Play Integrity check, fixing Google Wallet etc.
Symptoms
This might be relevant for you if you have rooted your phone and can no longer pay or add cards using Google Wallet or Google Pay. You may see a message in the app telling you that your "Phone doesn't meet security requirements". You may also notice that you can't find Netflix in the Google Play Store.
Background
In the arms race of detecting/hiding rooted devices Google has stepped it up a notch and now uses hardware backed attestation in its Play Integrity API. The long and short of this is that we can no longer rely solely on the Magisk DenyList and the Universal SafetyNet Fix Magisk module to hide root from apps.
There is currently a workaround - we can use a modded version of the USNF Magisk Module to "spoof" the device fingerprint of a device that doesn't support hardware backed attestation (i.e. a device running Android 10 or lower), thereby falling back on the basicIntegrity attestation of the SafetyNet API that we can circumvent using the tools mentioned above.
This will get Google Wallet working, cause Netflix to appear back in the Play Store, etc.
---
Instructions
These instructions are suitable for a freshly rooted device. If you have already been hiding root from apps then you can probably skip to the "Spoof device fingerprint" step.
Enforce DenyList
Tap Magisk -> Settings icon
Toggle Zygisk on
Toggle Enforce DenyList on
Tap Configure DenyList
Check Google Play Store and whatever app you're trying to hide root from, e.g. Google Wallet
Install Displax's USNF Mod
Download the latest USNF Mod Magisk module
Tap Magisk -> Modules -> Install from storage and install the zip file
Reboot once they're both installed
(Optional) Check that USNF passes
Download and install the latest YASNAC (app)
Open the app and tap Run SafetyNet Attestation
Check that Basic integrity passes. If it doesn't pass then the rest of this guide won't work - ask for help here.
Clear app caches and reboot
Tap Settings -> Apps -> Manage apps
Tap Google Play Store -> Clear data -> Clear all data
Note: if you have a Wear OS smartwatch then clearing the Google Play Store cache will mean you have to fully reset it in order to reconnect it to your phone. Unfortunately this is unavoidable!
Repeat for Google Wallet
Tap Google Play services -> Clear data -> Manage space -> CLEAR ALL DATA
Reboot your phone
And that's it - you should now be able to use Google Wallet as normal, find Netflix in the Play Store, and so on. At least until Google workaround our workaround
If you're trying to hide root from a new App all you should have to do is add it to the DenyList (first step) and clear its cache and reboot (last step)
Thank you
If you try a different fingerprint with your device then let us know whether it works
This workaround actually works! thank you!
However, in my case, I side effect is that the phone no longer connects to my Galaxy Watch 4.
My bet is that the fingerprint spoofing is preventing the phone watch supporting apps to connect properly.
I attempted to add every WearOS and watch apps on Denylist and rebooted, but still doesn't work.
Any ideas?
rodrigofd said:
I attempted to add every wear* and watch* apps on Denylist, and rebooted, but still doesn't work.
Any ideas?
Click to expand...
Click to collapse
I've read that you have to re-set up your watch from scratch if you clear Play Store cache. I think it was this guy. Sorry, I don't have any experience with these watches.
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
aricooperdavis said:
I've read that you have to re-set up your watch from scratch if you clear Play Store cache. I think it was this guy. Sorry, I don't have any experience with these watches.
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
Click to expand...
Click to collapse
Exactly I didn't know that it was caused by cleaning Play Store data, but I simply thought of giving the full reset a try, and indeed it worked.
Thanks!
rodrigofd said:
Exactly I didn't know that it was caused by cleaning Play Store data, but I simply thought of giving the full reset a try, and indeed it worked.
Thanks!
Click to expand...
Click to collapse
Okay, I'll add a warning to the post - thanks for letting me know, glad you got it sorted!
@aricooperdavis I think your thread should get way more exposure than simply being a subthread under
Xiaomi Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Perhaps you can request moving it to a general section? (like the Magisk forum with a bunch of Google Pay-related threads).
You could also put more keywords in the title, or as keywords of the thread itself....
Just some ideas
P.S. I did all this on a Samsung Galaxy S22 Ultra (Android 12) + Galaxy Watch 4
Working on Oneplus 9. Thanks!
rodrigofd said:
@aricooperdavis I think your thread should get way more exposure than simply being a subthread under
Xiaomi Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Perhaps you can request moving it to a general section? (like the Magisk forum with a bunch of Google Pay-related threads).
You could also put more keywords in the title, or as keywords of the thread itself....
Just some ideas
P.S. I did all this on a Samsung Galaxy S22 Ultra (Android 12) + Galaxy Watch 4
Click to expand...
Click to collapse
Hey I have a galaxy note 10 plus and I was wondering what steps you did exactly. I can pass safety check. but when I use root beer it can detect root. I am hoping someone can help.
Try to hide rootbeer and reboot
My device fingerprint isn't listed in the official list - what should I do? Redmi Note 11 Pro 5G
Speedy15928 said:
My device fingerprint isn't listed in the official list - what should I do? Redmi Note 11 Pro 5G
Click to expand...
Click to collapse
Try selecting the model mentioned in the OP:
POCO F2 Pro Europe (10)
That's what I did (on my Galaxy S22 Ultra) and everything went well
Speedy15928 said:
My device fingerprint isn't listed in the official list - what should I do? Redmi Note 11 Pro 5G
Click to expand...
Click to collapse
What @rodrigofd said - you want to spoof the fingerprint to a similar device that only supports Android <10. Try the one in the post and see if it works for you.
No dice I keep getting this screen:
I did see some error messages though when setting the fingerprint though - not sure if that would affect the process or anything.
Speedy15928 said:
I did see some error messages though when setting the fingerprint though - not sure if that would affect the process or anything.
Click to expand...
Click to collapse
Yeah you shouldn't see any error messages - can you repeat the process and note the errors so we can help you troubleshoot?
aricooperdavis said:
Yeah you shouldn't see any error messages - can you repeat the process and note the errors so we can help you troubleshoot?
Click to expand...
Click to collapse
I did that just now.
After which it says "working please wait" then asks to reboot. Did I copy the wrong part of the fingerprint? This doesn't happen when switching back to my original one.
Speedy15928 said:
After which it says "working please wait" then asks to reboot. Did I copy the wrong part of the fingerprint? This doesn't happen when switching back to my original one.
Click to expand...
Click to collapse
Don't copy anything, just use the built in Poco F2 Pro (Europe) key by following the instructions in the OP.
aricooperdavis said:
Don't copy anything, just use the built in Poco F2 Pro (Europe) key by following the instructions in the OP.
Click to expand...
Click to collapse
Ah right I was looking in the Xiaomi section and couldn't find it because I thought poco was part of Xiaomi now since I saw a poco phone in there - probably a partnership.
That worked thank you very much guys! Will the fingerprint have any unexpected side effects though such as issues with updating?
Hi everyone, i've been out from the custom rom world for a while and i noticed that some things have changed; i read that rooted devices cannot run banking or securtity apps or even applications like netflix ect ect...
I recently decided to upgrade my old poco f1 to a Android 13 rom, but i stopped because i need banking apps to work and i don't know thant much anymore about the topic, is there anyone that could help me find a rom that supports the use of banking apps or any rom is good unless the device is rooted?
Thank yall in advance.
If the ROM passes SafetyNet out of the box then there should be no issues with the majority of the banking/financial apps provided you don't root your device. If you do root your device (with Magisk) you will need to use the Shamiko Magisk module to hide root. There's 2-3 additional steps which you can easily Google. In my case I can use every such app in all my rooted devices. Root breaks SafetyNet but most apps with the exception of Google Pay work just fine. To fix SafetyNet you can flash the Universal Safetynet Fix module. I don't know about others but after flashing this module Google login doesn't work. I can't add another Gmail account for example or use my Google credentials to newly log into apps etc. Since I don't use Google Pay much it's OK and I keep the USNF module disabled. Currently I am using crDroid A12. Will switch to it's A13 flavor in the coming months.