Hi Guys
Until now I never used a TWRP Backup I took and restored it. Therefore this question:
I am right now on LOS19.1
Is it possible to take a full TWRP backup
- metadata
- Data
- Boot
- Cache
- Dtbo
- EFS
- Modem
- Super
(all except Recovery)
Then Flahs MIUI 13.8 test something (If Google Pay is working there) and when I am finished testing just restore the full TWRP backup und my phone is on the same state as it is right now, without loosing Data?
wuslschweiz said:
Hi Guys
Until now I never used a TWRP Backup I took and restored it. Therefore this question:
I am right now on LOS19.1
Is it possible to take a full TWRP backup
- metadata
- Data
- Boot
- Cache
- Dtbo
- EFS
- Modem
- Super
(all except Recovery)
Then Flahs MIUI 13.8 test something (If Google Pay is working there) and when I am finished testing just restore the full TWRP backup und my phone is on the same state as it is right now, without loosing Data?
Click to expand...
Click to collapse
Restoring an AOSP rom to a Miui rom will not work and vice versa.
NOSS8 said:
Restoring an AOSP rom to a Miui rom will not work and vice versa.
Click to expand...
Click to collapse
Thank you for your reply
Hmm, why does it not work?
Or does someone know a link with some detailed information about android and roms?
wuslschweiz said:
Hmm, why does it not work?
Or does someone know a link with some detailed information about android and roms?
Click to expand...
Click to collapse
Not the same OS(google and Miui).
Use one or more third-party apps for ,sms,mms apps.
It's as if you wanted to restore a Miui backup on an apple (I'm talking about the system, etc, of course).
I am not sure we have fully understood the question. I think the OP might be saying he will test MIUI and if he does not like it can he safely use the TWRP backup to go backwards and fully restore LOS 19.1 fully working as before ? ?
NOSS8 said:
Not the same OS(google and Miui).
Use one or more third-party apps for ,sms,mms apps.
It's as if you wanted to restore a Miui backup on an apple (I'm talking about the system, etc, of course).
Click to expand...
Click to collapse
Ok, thx
So if I understand right, when I am on MIUI I can flash LOS19.1 over it and on this LOS I can restore the twrp backup I took from my actual LOS installation and I am back on current state?
HiQual said:
I am not sure we have fully understood the question. I think the OP might be saying he will test MIUI and if he does not like it can he safely use the TWRP backup to go backwards and fully restore LOS 19.1 fully working as before ? ?
Click to expand...
Click to collapse
Yet I wrote "Restoring an AOSP rom to a Miui rom will not work and vice versa." It seemed clear to me since there were no objections.
Restored to the same rom should work but sometimes TWRP is finicky.
wuslschweiz said:
Ok, thx
So if I understand right, when I am on MIUI I can flash LOS19.1 over it and on this LOS I can restore the twrp backup I took from my actual LOS installation and I am back on current state?
Click to expand...
Click to collapse
If you back up systems etc on los 19 and install los 19.1 it can't work.
NOSS8 said:
Yet I wrote "Restoring an AOSP rom to a Miui rom will not work and vice versa." It seemed clear to me since there were no objections.
Restored to the same rom should work but sometimes TWRP is finicky.
Click to expand...
Click to collapse
Yes you are right
Had to flash roms to often during last weeks und I am tired of setting it up again. I just have paranoya
Just want to get that dmn google pay to work
But thank you for your patience!
wuslschweiz said:
Yes you are right
Had to flash roms to often during last weeks und I am tired of setting it up again. I just have paranoya
Just want to get that dmn google pay to work
But thank you for your patience!
Click to expand...
Click to collapse
For Google pay to work, you must take a certified rom or root and use Magisk.
NOSS8 said:
For Google pay to work, you must take a certified rom or root and use Magisk.
Click to expand...
Click to collapse
Are LOS19.1 or CrDroid8 not certified?
Does Google pay not responde with an error message if the rom is not certified?
Which Magisk module do I have to use?
When I install the SafetyNet check app it says passed.
wuslschweiz said:
Are LOS19.1 or CrDroid8 not certified?
Does Google pay not responde with an error message if the rom is not certified?
Which Magisk module do I have to use?
When I install the SafetyNet check app it says passed.
Click to expand...
Click to collapse
I can't really answer you, I don't have this device and no AOSP rom currently.
To find out if the phone is certified with the rom installed: play store/settings/about.
Even with a certified rom sometimes google pay does not work but usually the Op reports it.
I was using Magisk settings Hide.
NOSS8 said:
I can't really answer you, I don't have this device and no AOSP rom currently.
To find out if the phone is certified with the rom installed: play store/settings/about.
Even with a certified rom sometimes google pay does not work but usually the Op reports it.
I was using Magisk settings Hide.
Click to expand...
Click to collapse
Thx, I will give it a try
wuslschweiz said:
Are LOS19.1 or CrDroid8 not certified?
Does Google pay not responde with an error message if the rom is not certified?
Which Magisk module do I have to use?
When I install the SafetyNet check app it says passed.
Click to expand...
Click to collapse
Los is passing safety net.
With magisk and right settings also.
Laptapper said:
Los is passing safety net.
With magisk and right settings also.
Click to expand...
Click to collapse
I assume on your LOS phone, Google pay is working?
wuslschweiz said:
I assume on your LOS phone, Google pay is working?
Click to expand...
Click to collapse
Can't say. No NFC and don't use pay
Related
I successfully built 8.1.0 AOSP from source for Pixel (Sailfish).
This is my first ROM and there could be issues I'm not aware of.
Not Working:
Dialer keeps crashing when making or recieving phone calls
Working:
Camera and Flash
Speaker
Fingerprint sensor
LTE
Wi-Fi
Bluetooth
Auto brightness
If you encounter any other issues, please tell me and we can try to resolve them.
Requirements:
Unlocked bootloader
Newest fastboot installed and set up correctly
Stock 8.1.0 should be installed prior to flashing this
This will delete all your data, make backups of everything
Download:
https://drive.google.com/open?id=1vQRNRpSYQP2BrlCpzIpQpQNQrmlBYvTb
Installation:
Reboot your phone into bootloader
Open a terminal where the AOSP-sailfish-v1.zip is located
fastboot -w update AOSP-sailfish-v1.zip
I recommend installing F-Droid as gapps for 8.1 aren't available yet.
What I want to figure out now is why the dialer crashes when making calls and also how to make this TWRP flashable.
I also plan to update the ROM every month as new security patches become available, just like on the stock ROM.
If anyone wants to replicate the build, I just used the main 8.1.0 repo and the 8.1.0 driver images:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-8.1.0_r1 --depth=0
https://developers.google.com/android/drivers#sailfishopm1.171019.011
Any testing and help would be greatly appreciated.
Thanks.
Great effort! Gonna try and flash it and then possibly help you debug the dialer problem.
I really want to flash this, but I cant be w/o a functional dialer. Can you try disabling the stock dialer and sideloading the dialer from the play store?
computercarl said:
I really want to flash this, but I cant be w/o a functional dialer. Can you try disabling the stock dialer and sideloading the dialer from the play store?
Click to expand...
Click to collapse
There's no Google apps available for 8.1 as far as I know, so no play store. I installed Dialer2 from F-Droid but it seems like third party apps can't replace the actual calling interface that pops up when you make or receive a call.
And I wouldn't install this on a device that you plan on relying on just yet. Wait a few days until the issues are fixed. As far as I can tell from my use these past couple hours, the only major issue is the dialer.
HeavyHDx said:
There's no Google apps available for 8.1 as far as I know, so no play store. I installed Dialer2 from F-Droid but it seems like third party apps can't replace the actual calling interface that pops up when you make or receive a call.
And I wouldn't install this on a device that you plan on relying on just yet. Wait a few days until the issues are fixed. As far as I can tell from my use these past couple hours, the only major issue is the dialer.
Click to expand...
Click to collapse
try https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-14-0-176716531-release/ ? Sure it's not optimal, but, might get a functional dialer for the time being, until the real issue can be resolved.
It needs bunch of dependencies which cannot be installed this way. Eg Dialer framework
It appears though if this https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412
works better. You do get few crashes, but only once, the second time you try same thing, it works.
Couple of questions:
1. When you say this will delete all data, do you mean that internal storage will also be wiped?
2. Is it rootable? And if so, any idea whether SuperSU or Magisk is needed?
Thanks.
just wondering, why would I want to use this over stock?
jmiller3342 said:
just wondering, why would I want to use this over stock?
Click to expand...
Click to collapse
No additional services running, no gapps prerolled in, bare minimum. Think of this as LineageOS 15.
My plans are to run it, install the smallest gapps I can to get gmail and calendar working, install Elemental X and Magisk to hide unlocked bootloader.
Fast and Lean.
pavanmaverick said:
Couple of questions:
1. When you say this will delete all data, do you mean that internal storage will also be wiped?
2. Is it rootable? And if so, any idea whether SuperSU or Magisk is needed?
Thanks.
Click to expand...
Click to collapse
1. Yes this will wipe everything. Back up all files that you want to keep.
2. I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
HeavyHDx said:
I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
Click to expand...
Click to collapse
Not sure which version you tested, but https://forum.xda-developers.com/pi...-12-5-2017-t3715120/post74749046#post74749046 talks about what ver seems to work on 8.1 stock.
HeavyHDx said:
1. Yes this will wipe everything. Back up all files that you want to keep.
2. I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
Click to expand...
Click to collapse
Ah, thanks for the update. Do you think it'll be okay if I use TWRP to wipe Cache, Data and System, and then install this ROM, but without the "-w" option? The internal storage shouldn't affect the ROM, right?
pavanmaverick said:
Ah, thanks for the update. Do you think it'll be okay if I use TWRP to wipe Cache, Data and System, and then install this ROM, but without the "-w" option? The internal storage shouldn't affect the ROM, right?
Click to expand...
Click to collapse
Yeah should work just fine. Just delete the userdata.img from the zip (there's basically nothing in there anyway)
Any plans of a Marlin release?
HeavyHDx said:
Yeah should work just fine. Just delete the userdata.img from the zip (there's basically nothing in there anyway)
Click to expand...
Click to collapse
All right! Gonna try it out over the weekend. Will report back...
AlexBrookes said:
Any plans of a Marlin release?
Click to expand...
Click to collapse
I can build and upload it real quick, but I wouldn't be able to test anything.
HeavyHDx said:
I can build and upload it real quick, but I wouldn't be able to test anything.
Click to expand...
Click to collapse
I'd be willing to test it. Thanks!
computercarl said:
No additional services running, no gapps prerolled in, bare minimum. Think of this as LineageOS 15.
My plans are to run it, install the smallest gapps I can to get gmail and calendar working, install Elemental X and Magisk to hide unlocked bootloader.
Fast and Lean.
Click to expand...
Click to collapse
oh cool . thanks brah
Have you guys tried going to the default apps section and setting Phone as the default dialer? Fixed it for a few other ROMs i've tried that ran AOSP bases for other devices, might be applicable here.
EDIT: No-go, wierd.
HeavyHDx said:
I successfully built 8.1.0 AOSP from source for Pixel (Sailfish).
I recommend installing F-Droid as gapps for 8.1 aren't available yet.
Thanks.
Click to expand...
Click to collapse
Gapps are kicking around now...
Check 'em from here ( https://forum.xda-developers.com/pi...os-15-1-pixel-xl-marlin-t3725985/post74976717 )
...
cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
Upgrade to the latest version or install persona's b632 if you have kirin 620
..
cmmx said:
I already have the latest, b632.
I can't see how a custom rom could succeed where the stock one fails, though. Still I rather keep the phone stock ftm, at least until I get to decide what changes are applied and how.
Just reset and updated the app and no change. Phone isn't rooted.
Click to expand...
Click to collapse
I still get this problem some times if i switch from custom rom to stock, and i just reinstall rom again with a clean install and all is good, device get certified by google
Enviado desde mi hi6210sft mediante Tapatalk
...
cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
If You have root! Best Way to bypass It root Your phone with Magisk root
...
cmmx said:
I don't have root, and can't see why that would affect it, because what it says is the certification is for the device's hw (not sw), so it shouldn't matter if it's rooted or a custom rom or whatever (and I'm on stock Emui, anyway).
And it has nothing to do with Safety net either, because Magisk Manager (now) says it passes both cts and basic integrity (a week ago, the same version (other install) only passed basic integrity, and a couple months ago (other version) it didn't pass either one, with someone on Magisk thread even telling me that's because Magisk itself wasn't installed - guess what: it still isn't, yet it now passes both...).
Either way, I haven't noticed any problems from it, so far, so I'm just puzzled.
Click to expand...
Click to collapse
Bugged Google Play,just wipe data for gplay app.
...
https://download.mokeedev.com/?device=z2pro
bug-reports
https://bbs.mokeedev.com/c/bug-reports
I strongly suggest install "PieBridge" to saving battery.
settings crash at select sim
https://streamable.com/3c5xf
Everything works good . When I was on 3.5.300 there was not LTE . With fw 3.5.259 all seems to be good . As far I feel good with this rom
I strongly suggest install "PieBridge" to saving battery.
There is problem with ctsprofile . I was managed to remove inbuilt root access but it was not helped to get safetynet .
downloading now ir now and mk 71 work on z2pro very smoothly and evwrything work well, just see how is mk 81, i love mk's kernal
mvp3 said:
I strongly suggest install "PieBridge" to saving battery.
Click to expand...
Click to collapse
What exactly is piebridge?
devilred666 said:
What exactly is piebridge?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=me.piebridge.brevent
mar.ur said:
There is problem with ctsprofile . I was managed to remove inbuilt root access but it was not helped to get safetynet .
Click to expand...
Click to collapse
This rom have Xposed integrated. So you never pass safetynet with this system
jhobc said:
This rom have Xposed integrated. So you never pass safetynet with this system
Click to expand...
Click to collapse
No , this rom has no xposed
mar.ur said:
No , this rom has no xposed
Click to expand...
Click to collapse
So download this Magisk module and see if it will fix the Safetynet
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
jhobc said:
So download this Magisk module and see if it will fix the Safetynet
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Click to expand...
Click to collapse
Yes , I was thinking about it . I uninstalled Magisk 16 and then installed Magisk 14 and safetynet fix V2 . It works . Later I will update to Magisk 16 and check if it works .
edit
Magisk 16 gets cts failed . If you want to pass seftynet on Mokee you should use Magisk 14
Could anyone who uses this rom tell me if there is option to set different ringtones for both cards? I mean native option in settings, not using some app.
I remember having it in RR 5.7.4 on my Moto X Play. However it's missing in AEX 4.6 (not only on ZUK).
And how about Slim Recents? KK Mokee had Slim Recents, but I've never used LP+ Mokee on any of my devices.
(deleted)
bug-reports
https://bbs.mokeedev.com/c/bug-reports
Gents,
Anyone tested this Mokee 8.1 (updating 11/03) and saw if Magisk 16 is operational concerning SafetyNet?
I ask it because on Mokee 8.1 (date 09/03) just works SafetyNet on Magisk 14 and with Universal SafetyNet Fix. For any superior Magisk version does not work the SafetyNet.
UPDATING: Magisk 16 still not working about SAFETYNET (ctsprofile) on Mokee 8.1.0 (date 12/03). I'm backing to Magisk 14.
Prefer Aegis to Brevent by Piebridge
mvp3 said:
https://play.google.com/store/apps/details?id=me.piebridge.brevent
Click to expand...
Click to collapse
Would very much like to see Aegis in 8 and not use Brevent Piebridge.
John
Folks, started getting "vendor image mismatch" after recent Nightly. Phone, Lawnchair, and some other apps keep stopping. Tried going back a few versions, no joy. Clear Dalvik, cache, data, and still no good.
Not clear if and how I should install a new vendor image. Many posts out there refer to installing a new one,where to get it, but say to install in the Vendor partition. But I can't find a vendor partition. Advice? (Help!)
John
JBoy53 said:
Folks, started getting "vendor image mismatch" after recent Nightly. Phone, Lawnchair, and some other apps keep stopping. Tried going back a few versions, no joy. Clear Dalvik, cache, data, and still no good.
Not clear if and how I should install a new vendor image. Many posts out there refer to installing a new one,where to get it, but say to install in the Vendor partition. But I can't find a vendor partition. Advice? (Help!)
John
Click to expand...
Click to collapse
Update: Wiped caches, data, system. Reinstalled latest Mokee 8.1 nightly and latest Gapps. All is working. But still getting the vendor image mismatch. Updated TWRP from 3.2.1-0 to 3.2.1-1 and now have capability to flash to vendor partition. But don't know what vendor.img to flash. Any suggestions?
John
JBoy53 said:
Update: Wiped caches, data, system. Reinstalled latest Mokee 8.1 nightly and latest Gapps. All is working. But still getting the vendor image mismatch. Updated TWRP from 3.2.1-0 to 3.2.1-1 and now have capability to flash to vendor partition. But don't know what vendor.img to flash. Any suggestions?
John
Click to expand...
Click to collapse
I've installed last night version , gapps and magisk 16 via 3.2.1-1 twrp . After that factory reset . All is ok .
so i was just searching in xda and i found a thread for realme x2 pro that makes all the Chinese app go away for good and make coloros CN version tolerable.
I TRIED IT AND IT WORKS ON REALME X2.
and below is the link to that thread which is made by kkarnaout and im personalty thankful.
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-removal-china-related-apps-making-t4010019
Is the fingerprint scanner still working after the process?
Can you remove com.oppo.market and com.nearme.themestore ?
nothing happen to fp. everything works just fine.
well i couldnt remove the market and didn't try it with theme store.
Hi
Hi. Does it work on realme UI or only colors version?
This seems interesting. Please confirm whether this works on realme UI.
maxs8007 said:
This seems interesting. Please confirm whether this works on realme UI.
Click to expand...
Click to collapse
Yes it works on m X2 CN
You can use debloater magisk module and remove all the Chinese apps including theme store, market, phone manager etc. Everything works fine without any issue.
maxs8007 said:
You can use debloater magisk module and remove all the Chinese apps including theme store, market, phone manager etc. Everything works fine without any issue.
Click to expand...
Click to collapse
If it's stock rom + magisk module, will the safetynet check break?
It's returned to stock rom now.
I plan to unlock again and flash the recovery, then delete the .apk files in recovery. Finally relock again.
I think the safetynet check would be okay after this. Hope I'm correct.
nickyip123 said:
If it's stock rom + magisk module, will the safetynet check break?
It's returned to stock rom now.
I plan to unlock again and flash the recovery, then delete the .apk files in recovery. Finally relock again.
I think the safetynet check would be okay after this. Hope I'm correct.
Click to expand...
Click to collapse
Please avoid unlocking relocking bootloader multiple times. It may get hardbricked anytime.
Stock rom with magisk modules will not break the safetynet unless you flash xposed.
Just make sure you hide the magisk manager from settings and hide all banking apps or all those apps that detect root and you'll be good to go.
I'm on stock with magisk +modules and debloated all Chinese apps.
com.coloros.assistantscreen - breeno feed
com.heytap.speechassist - breeno voice , long power click
com.heytap.quicksearchbox - global search cant be change to english[?]
any fix to this problem ?
130|RMX1991CN:/ $ pm uninstall --user 0 com.heytap.market
Failure [DELETE_FAILED_INTERNAL_ERROR]
good evening. I have a problem and I want to know if it happens to someone too. I can't find any custom rom that has NFC support. All the ones I've tried don't even have an option to activate it. Does this have a solution? my device is redmi note 10 pro sweet. Thanks.
I've tried PixelOS and Xiaomi.eu and both have NFC options and can link with Google Pay (I've tried xiaomi.eu NFC pay and it worked, I didn't try PixelOS, but it has the options)
I remember someone asking this before a while back, and my response is frankly the same (and just as puzzled) - I don't think I've ever seen a sweet ROM that *didn't* have NFC support.
In M2101K6R Japanese versions, nfc does not work on aosp based roms. I am having the same problem
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
wuslschweiz said:
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
Click to expand...
Click to collapse
install safetynet fix 2.1 with magisk, then try again.
install safetynet test via playstore and run it. this should be passed now.
If gpay isnt working, go to magisk/settings and activate zygisk. after this, add all google services (use search with "google" and "gms") to the denial-list, reboot phone and try again
if this doesnt the trick, change ROM ;-)
Lineage OS 19.1 is just great. GPay and MIUI Cam working like charme.
links in my signature
I think phone should be encrypted for working NFC (payments).
ottili81 said:
install safetynet fix 2.1 with magisk, then try again.
install safetynet test via playstore and run it. this should be passed now.
If gpay isnt working, go to magisk/settings and activate zygisk. after this, add all google services (use search with "google" and "gms") to the denial-list, reboot phone and try again
if this doesnt the trick, change ROM ;-)
Lineage OS 19.1 is just great. GPay and MIUI Cam working like charme.
links in my signatur
Click to expand...
Click to collapse
I checked with this SafetyNet Test app. All tests passed without magisk. Anyway I would expect a fault message in google pay if something safety related is not ok, same as in banking apps, which are working fine.
Was also thinking to change to lineage but right now I am not motivated to reinstall the phone completely because its my daily driver^^
@otttili81 how can I see your signature?
wuslschweiz said:
I checked with this SafetyNet Test app. All tests passed without magisk. Anyway I would expect a fault message in google pay if something safety related is not ok, same as in banking apps, which are working fine.
Was also thinking to change to lineage but right now I am not motivated to reinstall the phone completely because its my daily driver^^
@otttili81 how can I see your signature?
Click to expand...
Click to collapse
Use Desktop PC to open XDA
Google Pay (well, Wallet now) can be incredibly finicky. Also sometimes it might seem like it has a security issue, but actually it's something else, like the card not being set up properly (but appearing like everything's fine).
Case_ said:
Google Pay (well, Wallet now) can be incredibly finicky. Also sometimes it might seem like it has a security issue, but actually it's something else, like the card not being set up properly (but appearing like everything's fine).
Click to expand...
Click to collapse
Yes everything looks fine in the wallet itself. Only when it comes to payment, the terminal refuses it. I tried several cards. Also reinstallation of the app.
Is there a possibility to check or test it except on the payment terminal?
@wuslschweiz What kernel are you running? Some kernels can cause issues like this.
I just came off a clean install of the current crDroid with Flame GApps last week and Google Pay was working perfectly fine, I didn't have to do a thing except the usual Zygisk deny list setup.
Case_ said:
@wuslschweiz What kernel are you running? Some kernels can cause issues like this.
I just came off a clean install of the current crDroid with Flame GApps last week and Google Pay was working perfectly fine, I didn't have to do a thing except the usual Zygisk deny list setup.
Click to expand...
Click to collapse
@Case_
Standard crDroid kernel 4.14.290-sigmaKernel-v1.0
I havent rooted my phone so no Magisk or Zygisk.
But good to know that Google Pay is working on your phone so the problem is my phone.
Now when you mention kernel I remember I seem to have a firmware problem (notification volume level is related to sound volume)
Maybe also something NFC/GPay is related to this.
Is it better to flash MIUI 13.8 firmware with miui flash tool or twrp?
Flash it with twrp
wuslschweiz said:
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
Click to expand...
Click to collapse
GPay is a bit of hit and miss. Make sure it says 'Device is certified' in Playstore settings. It usually won't work without it. It's also very dependent on Kernel. There is also an option to reset NFC in settings, which helped me a few times.
Seems like I am just to dumb for Google Pay.
I reflashed Miui 13.08 firware via TWRP and then LOS 19.1L. Installed Magisk to restore Apps and Appdata wirh Alpha Backup Pro. Uninstalled Magisk (I dont need Root) Installed Google Pay, Still not working, same as bevore.
If I am motivated, maybe I try Google Pay on Stock MIUI...
Thx to all for the help
wuslschweiz said:
Seems like I am just to dumb for Google Pay.
I reflashed Miui 13.08 firware via TWRP and then LOS 19.1L. Installed Magisk to restore Apps and Appdata wirh Alpha Backup Pro. Uninstalled Magisk (I dont need Root) Installed Google Pay, Still not working, same as bevore.
If I am motivated, maybe I try Google Pay on Stock MIUI...
Thx to all for the help
Click to expand...
Click to collapse
Storage is encrypted? It won't work with out it.
pablo.see said:
Storage is encrypted? It won't work with out it.
Click to expand...
Click to collapse
I havent done anything special to encrypt it but when I boot into TWRP it requests a PW to decrypt so I assum it is encrypted