My GPS/Location isn't working after I unlocked bootloader flashed twrp and rooted. It's rooted with magisk. I don't have xposed installed. I have tried google maps, earth, mapquest, and waze. It says I'm somewhere different than where I am. I don't get any error messages. Has anybody else dealt with this?
My speak to text also isn't working. I don't know that it's related.
Update the firmware. 50.2.A.3.77
Related
So, I am running a rooted stock lollipop rom of the latest version thanks to another thread.
Now I am trying to find a toggle app or switch to force "4G LTE only" mode because it keeps dropping to 3g and it's driving me crazy. Every app I have tried on the google play store says incompatible with my device or it just crashes. I'm at my wits end. I have tried searching for a solution but found none.
Does anyone know or can recommend a good app that will function with this infuriating phone? Frankly i'm amazed that I was even able to obtain root after the bootloader lock mess.
Running the G900V
Lollipop 5.0
PB1 Firmware
Edit:
I managed to find a solution in this thread.
http://forum.xda-developers.com/android/apps-games/widget-toggle-network-type-5-0-xda-t2945406
It works so far as i can tell.
Hello Forum People,
I have my bootloader unlocked, build MHA-L29C432B198, TWRP recovery and I use Magisk v14.5 however I cannot seem to pass SafetyNet with Magisk failing on ctsProfile and basicIntegrity and "SafetyNet Test" (from the Play Store) passing Safety Net Request but failing Response Signature Validation ("Response Payload Validation Failed").
I have a suspicion that this is due to the unlocked bootloader as I have removed Magisk and anything else I think might have tripped SafetyNet but always the same issue.
Can anyone confirm if this is the cause or otherwise and if having my bootloader unlocked is 'causing SafetyNet to fail then is it safe to relock after re-installing Magisk and returning recovery back to stock or is there some kind of work around?
Muchos appreciated in advance!!
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
ante0 said:
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
Click to expand...
Click to collapse
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
beejkitsune said:
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
Click to expand...
Click to collapse
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
beejkitsune said:
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
Click to expand...
Click to collapse
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
beejkitsune said:
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Surfinette said:
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Click to expand...
Click to collapse
Thanks for the reply. My solution ended up being to. Rebrand and then update to the Oreo release MHA-L29C432 8.0.0.361. Play Store now certified and passing SafetyNet with no issues. I'm still not 100% sure what tripped SafetyNet originally, nothing seems to be consistent with other people's experiences but I have now a resolution albeit not the desired approach, nor solution.
Is anyone else having this issue. Started yesterday for me after years of being rooted without fail. Is there a Google Services update that now runs root check for fingerprint login?
Same here did you get it to work?
Same on my OP 8 pro, Magisk hide, reboot and reinstalling etc didn't work either
Ok, I thought I was going crazy, I have the same problem since last couple of updates... Anybody figured out how to fix it? Maybe an older version of chase mobile?
The new chase app update fix the fingerprint started to work again i got root with magisk and edxposed instaled.try to update the app
Doesn't work for me with app version 4.262 (updated December 15, 2021).
Moto G7 Play (channel), LineageOS 18.1 20211226-NIGHTLY, Magisk v23.0.
As far as I can tell, fingerprint login is the only thing that doesn't work. edit: Quick view balances also does not work.
Just for comparison, everything works with the Bank of America app, including fingerprint login.
I had fingerprint working with root by installing older version and then updating but now I can't get it to work anymore.
Can anyone confirm whether the fingerprint works without root (but with bootloader unlocked and custom ROM installed)?
I'm seeing this issue still in Feb 2022. Rest of app works. Funny how whatever it detects isn't reason enough to block access, just block fingerprint.
supeRUUser said:
Can anyone confirm whether the fingerprint works without root (but with bootloader unlocked and custom ROM installed)?
Click to expand...
Click to collapse
Yes. I just reset my device and reinstalled LineageOS. The fingerprint worked. I then flashed Magisk (and enabled Hide for the Chase app), and the fingerprint continues to work. It seems you just need to set it up *before* rooting.
A strange thing happened to me:
I received an automatic update yesterday. Everything went normally, everything worked normally.
Later in the store I saw that Google Pay does not allow payment because firmware is Root (it is not) or illegal firmware is installed. And Google Play has shown that the device is not certified.
I tried resetting to factory settings ... without success.
It wasn’t until I installed the older August firmware via Odin that the phone became “legal” again.
This is the firmware INS 20211030.
Has anyone else had such problems?
Edit: it was October Update
darko150 said:
A strange thing happened to me:
I received an automatic update yesterday. Everything went normally, everything worked normally.
Later in the store I saw that Google Pay does not allow payment because firmware is Root (it is not) or illegal firmware is installed. And Google Play has shown that the device is not certified.
I tried resetting to factory settings ... without success.
It wasn’t until I installed the older August firmware via Odin that the phone became “legal” again.
This is the firmware INS 20211030.
Has anyone else had such problems?
Click to expand...
Click to collapse
As you said this is strange, I did not receive any updates in November. All I got was the October 2021 security patch update.
I flashed U1 recently on my Snapdragon S22 Ultra (after sending it in for repairs) and now Google Wallet gives me an error stating that the device does not meet "security requirements".
Samsung pay continues to work well. Does anyone know what causes Google Wallet to present with this error?
Can you give more information? Did you flash all the files in the zip file? It could be you didn't flash the CSC
I flashed all of the files.
Did you flash the beta?
If so the betas do not in fact meet the security requirements as it's not a signed image (I think I recall that being the root cause) either way if on beta, Google pay won't work.
That makes sense. I did upgrade to the Beta version, had no idea this was the case. Thanks!
I can't even get samsung wallet to work. It just says failed to connect to server when trying to add a card.. I've reinstalled a couple times. Currently using google wallet on my watch..