Related
So I am running full stock on my Pixel that is updated to Oreo. I've read through the latest thread (HERE) on the new beta for Magisk that supports Pixel devices and wanted to know what steps folks may have followed to get this installed and working. The regular thread details some steps but it appears that those are driven towards other devices and doesn't account for the difference of Pixel devices.
Thx!
loaded up fine on my pixel!
eqbirvin said:
loaded up fine on my pixel!
Click to expand...
Click to collapse
Are you able to share the steps you took to get it loaded? It would seem that it isn't the same as other or previous version since those didn't apply to pixel devices.
Thx
Do modules work?
There's an offical Magisk Pixel (XL) Thread
I'm running it on Pure Nexus July build now. I ended up having to re-flash (dirty) the ROM to clear up the old goodwin_c Magisk install.
Seems okay for now. I have a couple of modules loaded but haven't had the opportunity to test whether they actually work. AirAudio at least doesn't fire a warning that the module isn't found.
There is a new update today. Mods were broken. Supposedly fixed now.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post73966889
Steps on 8.0 were as follows
make sure youre on stock boot
boot into system once with stock boot
then boot into android 0 twrp
flash magisk
reboot to system
finished
HD8 2018 6.3.1.5 (and 6.3.1.4) issues
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.5 (6.3.1.4) on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
HD10 2017 40.6.5.0_user_650601220 issues
Well, what do you know ... I finally took the plunge to do the unlock and install TWRP on my Kingoroot rooted HD10 2017 (thanks @k4y0z !). I backed up all the apps via Titanium Backup, and then backed up the internal sdcard via Total Commander to a zip, which later nicely restores things back with the proper timestamps (yay!). It's very difficult to restore timestamps, but Total Commander with root can do it.
In my optimism, after getting TWRP, I immediately installed the latest FireOS, 40.6.5.0_user_650601220, with Magisk, and Xposed installed into system (xposed-v89-sdk22-arm64.zip). And, just like HD8 2018, the moment I activated Xposed modules, the tablet started rebooting when WiFi was on. If I managed to hit WiFi off button before it did so, it seemed stable. So both HD10 2017 and HD8 2018 appear to have the same Xposed bug in the latest FireOS versions!!! I wonder if it's related to the fix of MTK-SU issue.
I also ran into Google Play & battery drain issues. Tired of several attempts of troubleshooting, I actually ended up backtracking all the way to 40.6.2.6_user_626533320, which is the version I started with. Once Google Play went south after my 1st restore, I could not fix it over multiple tries, and I had to do a Factory reset again and restore apps via Titanium Backup a bit more carefully, starting with the latest versions of Google Play apps without data (rather than just all at once). Now everything appears to be working as before, with TWRP, and the same old FireOS version that I already had
The battery drain issue was an interesting one, apparently, Vanced Youtube helper app, microg_YouTube_Vanced_0.2.6.17455, creates a lot of battery drain via needless Wakelocks, which can be fixed by running the following commands:
Code:
adb shell
su
pm disable com.mgoogle.android.gms/org.microg.gms.people.ContactSyncService
P.S. A week ago I unlocked HD8 2017 (OS version 50.6.3.6_user_636558520), and successfully cloned HD8 2016 to this 2017 via TiBa & Total Commander. That attempt went without a glitch, and that's why I thought I could also do HD10 in no time, but HD10 gave me all kinds of issues.
bibikalka said:
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.4 on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
Click to expand...
Click to collapse
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Michajin said:
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Click to expand...
Click to collapse
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
bibikalka said:
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
Click to expand...
Click to collapse
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Michajin said:
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Click to expand...
Click to collapse
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
The camera works on both 16.0 and 14.1. But 14.1 is by far more stable at this time. Bluetooth and headphones (plus more- see thread) issues on 16.0. The only issue on 14.1 is the headphone jack doesn't work (but i think someone has found a fix for it but it hasnt been updated in the rom). Backup in TWRP and install 14.1 and give it a shot, i am on 16.0. 14.1 was working really smooth. I have not tested skype on either. 14.1 seemed smoother and less buggy than fireOS right at Beta.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
Observation regarding custom ROMs is one reason I typically hang with 'stock' and tune to my liking. LOS 14.1 for this device/gen (and a few others) is an exception; worth considering. LOS 16.1 is less refined ATM with no meaningful advantage over 14.1.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
I needed to have headphones working, so I didn't try LOS 14 until recently. I'm extremely happy with it. It's so much snappier than stock for me, and videos load so much faster, like in Netflix, for example. I'm also using Magisk and Xposed with no issues.
I didn't realize the new build is up with fixes... Going back to 14.1, I think he is working on 17.0 (Kaijones23) 17.0 was updated last night....
https://github.com/mt8163/android_device_amazon_karnak/branches
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
xantiux said:
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
Click to expand...
Click to collapse
Have you unlocked the bootloader (prerequisite):
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
xantiux said:
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
Click to expand...
Click to collapse
This help?
https://forum.xda-developers.com/hd8-hd10/general/lineageos-14-1-fire-hd8-2018-t3936242
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
xantiux said:
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
Click to expand...
Click to collapse
Supposedly renaming .bin to .zip allows flashing from twrp. I'd be wary of other partitions such as recovery and aboot which could trigger a bad day.
Headphone fix for LOS 14 has been applied in the latest version of the ROM. If you don't feel like reflashing entire ROM, there is a flashable zip containing only the headphone fix (module). I don't have the links handy but it's all available on this forum.
Updated post #1 and described HD10 '17 Xposed WiFi crashloop as well.
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
bibikalka said:
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
Click to expand...
Click to collapse
Welcome back!
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Thanks it works great
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
AwkwardUberHero said:
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
Click to expand...
Click to collapse
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Thank you so much for the link to this!
I reported it as an issue right after I saw it, but had not heard back.
I appreciate you linking me.
This fixed my problem with face unlock. Thanks so much ?
What does this do exactly? My wife's face unlock works but she has a constant notification to re-enroll. I told her if she did that it most likely wouldn't work unless she factory resets. Honestly the notification being there annoys me more than her but she refuses to factory reset. I would just try it and see if it was my phone but I'll be sleeping in the backyard if I screw hers up for any length of time....lol
Worked perfectly on my phone! Spreading the word! Thanks for the module!
https://twitter.com/kingbri_aahs/status/1258148276513189888
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Hey man thanks, I tried it. It didn't work for me. I wish you nothing but the best of luck with this fix bro. It's really needed. I miss my camera lol
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
This worked for me, Pixel 4 not XL
On may factory image
Thanks
TechOut said:
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
Click to expand...
Click to collapse
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
It's working for me aswell on May version. Could you explain where Is the problem? What does this module?
tmoore3496 said:
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
Click to expand...
Click to collapse
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Okay there seems to be a lot of confusion from people in this thread so while I am not the OP I will try to clear things up.
Some people are having face unlock issues that can first be observed when setting the device up after flashing April and/or May images. During set up, it will say something along the lines of "Could not enroll face ID" or "Hardware not available" if dirty flashing one of the updates.
Some of us are having this issue even if we never upgraded to the Android R Developer Preview 3 or 4.
Others of us are having the issue after trying the DP 3/4 then rolling back to Android 10, April or May update.
The last monthly update that did not have Face Unlock issues for any of the above affected is March.
This module is created to help fix that and get Face Unlock working again and it is a Magisk Module that requires root to install.
However, a small few are still having issues even after trying this module (from my understanding).
You do not need this module if your face unlock works on April/May updates because this seems to be a kernel related issue that only affect some for a weird reason that I am too lazy to research right now. I'm sure this will be updated in the coming months.
So if you're Face Unlock doesn't work on April or May update, try this module. If it still doesn't work, you can use the March update and Face Unlock will work. There are no feature changes between now and March update. The March update include the auto dark mode, and the other feature drops from that month. Both April and May are only security patches and very minor fixes. While it is not the latest security patch you still have all the latest features.
Awesome!
Worked perfect on my pixel 4 xl. Flashed dev preview and got the enrollment error. Thanks for your module! working like a charm on May update
fuadtaufiq said:
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Click to expand...
Click to collapse
yeah April, May update breaks it, but magisk module fixes it. Temporary fix until Google fixes it.
anyone tried this on Jun update...
i will try, no need to wait
will report back...
---------- Post added at 04:14 PM ---------- Previous post was at 04:03 PM ----------
Adnansaeedhamed said:
anyone tried this on Jun update...
i will try, no need to wait
will report back...
Click to expand...
Click to collapse
i can confirm this working perfectly with me in Jun update
Hi! This happened to me today:
I installed the Android 11 Public Beta 1 today from June Android 10 version. I have an unlocked 4 XL. I flashed (trough fastboot) the June update and my facial recognition got broken. I did factory reset it but nothing was fixing it. I went back to Android 11 Public Beta 1 and it worked. Then I downloaded and flashed January Android 10 version and it is working right now. Will update if after setting it up and updating it to last update will still work.
basically what this does is patches sepolicy and adds the files required for face unlock. If you run a dmesg when trying to enroll there is something blocking the process from finding the files(likely sepolicy)
Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!
I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk
I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.
Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.
qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.
Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.
kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11
Hello everyone,
About six months ago I flashed Android 13's Evolution X rom, don't remember which version right now. Important: No root. After that I installed all of my apps, including SafetyNet Test app from BITS Apps. Test was passed with no issues. Problem came when I tried to add the same credit card I always used on every rom (MIUI, ArrowOS, CrDroid, ...). Once I accept the issuer terms, Wallet says "Processing card details" and the error comes in:
Couldn't finish card setup for tap to pay
To resolve this, you'll need to contact your bank. You can still pay with this card on Google and across other apps and sites.
Click to expand...
Click to collapse
After this, I immediately contacted both my bank and Google. Both say the same: everything is ok on their side, no bans, no blocks, no limits reached. To be honest, over these six months I even requested brand new credit cards. Same thing happened. Tried them on other Android/iPhone devices and they work. So it's obviously something wrong on the phone. Re-flashed stock MIUI V13.0.3.0.SJUMIXM from bootloader using Mi Flash Tool (latest version, yes). Locked the bootloader, tested SafetyNet, Play says device is certified, MIUI on developer settings says bootloader is locked and device is safe.
Any ideas...?
Since I bought the phone on Amazon (from a third party store which is not POCO/Xiaomi) and done it under the Prime advantages, it's still under warranty so I am about to ask a replacement or refund and maybe buy a newer model. Please keep in mind I don't want to blame in any way Evolution X rom or its devs. It's a magnificent rom which I admire.
I have attached a screenshot from the error. Many, many thanks in advance for your comments.
I also have this issue on crDroid 9 (A13). I haven't found a solution yet.
I have done the same steps. Google and banks are in good standing, doesn't seem to be any issue on their end.
That's another point I didn't mention. It started with Evolution X six months back but now it's happening with every rom. Tried ArrowOS, xiaomi.eu, CrDroid...
Anyways, in 2 days Amazon will either let me choose to get a new device or get a refund. I'll might ask a refund and buy the X4 GT. I don't want this to happen again any time.
Do you have selinux set on premssive or enforcing?
Doesn't really matter. Tried that too before.
Right now I'm even on stock MIUI (10.0.3) with bootloader locked (flashed through Mi Flash Tool) and not working.
Jaftdroid said:
Doesn't really matter. Tried that too before.
Right now I'm even on stock MIUI (10.0.3) with bootloader locked (flashed through Mi Flash Tool) and not working.
Click to expand...
Click to collapse
Wow I'm on miui eu 13.0.8 rooted and I got it working
Try GPay SQLite Fix magisk module
I as well can't add card to gpay, because too many times i installing different roms. And always adding card. Then i waiting around week on that same rom and just then i can add card to gpay.
jacky3362 said:
Wow I'm on miui eu 13.0.8 rooted and I got it working
Try GPay SQLite Fix magisk module
Click to expand...
Click to collapse
Tried it too. Nothing changed. Also Props, Universal SafetyNet Fix, etc... That module is anyways outdated and not supported anymore from what it says at GitHub.
irmas5 said:
I as well can't add card to gpay, because too many times i installing different roms. And always adding card. Then i waiting around week on that same rom and just then i can add card to gpay.
Click to expand...
Click to collapse
Yeah, that's what I thought on the beginning, reason of why I waited up to six months. I even requested new credit cards to the bank. Same error when trying to add them.
I am anyways pushing the warranty. Will get a new device soon. Still thinking if getting another X3 Pro or just step ahead towards X4 GT.