Related
I have a US t mobile samsung galaxy note 3 n900t. I do apologize for making this long but I wanted to share what I have done in case it helps to solve the problem I am having. I do not remember what version was first on it but I rooted it using the method of chainfire cf auto root through odin. It was the first time I rooted so I am new to the root. Everything was good at that point. I made the mistake of deleting google play services in the attempt of debloating. I couldn't get google play store to work after that and I could find where I could redownload google play services. I ended up connecting to kies3 to do a restore in hopes it will replace it. Kies3 tells me that the lollipop 5.0 update was available so I ended up doing the update, now I have lollipop 5.0. I did the root process again The same way I did before in addition to adding the twrp recovery. The problem I am having now is that I am unable to set the screen lock with pin. When I try to set it up, I enter my 4 digit code, exit out of the settings and then try to see if it works but it doesn't. When I press the power button expecting to put my pin in, no pin pad shows up, I swipe then I am in my phone. When I try to set the screen lock with pin again, I enter my 4 digit code, try again and the same result. Screen lock will not activate. Another thing I noticed is after several tries to set it up, it tells me the pin I enter is wrong, I know I am entering it right. I then log into google and do a reset pin on my device from there. I have searched for a solution but I keep finding ways to bypass lock screen, I want to activate it with my 4 digit pin. I don't know what else to do. Thank you for your help!
I am looking for any ROM that can be installed and allows Android Pay to work. I sometimes forget my wallet and would like to have the ability to use Android Pay. I was excited when I got AICP to install and pass safety check, but it doesn`t actually work at the terminal. I now read that all AOSP based roms have problems with NFC payments.
Does anyone have this working on an M8. There are some old threads, but none that actually report that it works.
Are you rooted with Magisk?
redpoint73 said:
Are you rooted with Magisk?
Click to expand...
Click to collapse
Yes. So far I have tried AICP 7.1 Rom, which passed safetynet check, but would not actually work on a store's terminal. Perhaps an NFC issue with AOSP Rom? I also tried Lineage 15, but could not get it to recognize google play services and could not get the play store to work as a result. I am now on lineage 14.1, which agains passes safetynet check but will not work at the terminal.
As I am aware, Magisk only allows Android Pay to be installed, but when it comes time to validate the purchase, there is either an NFC problem or something prevents the purchase from being validated.
So if anyone has a non stock rom that works with android pay on the m8, I would like to know about it. There have been a few threads, but none seem to offer a current resolution.
I'm not personally a user of AOSP ROMs, nor Android Pay, so my advice is limited. Just chiming in, as long as you are passing SafetyNet, and have Magisk Hide enabled (in Magisk Manager settings) than I don't think it's a safety net or root issue. Like you said, it might be an issue with AOSP ROMs and NFC.
I tried Resurrection Remix. Same result. Passed safety check but would not work at the store terminal.
Cannot use payments on nougat. Have to go to marshmellow.
NFC works, but HCE does not, which is whats required.
Success. I went to ViperOneM8 6.1.0. Installed the rom. Then deactivated Su in the Su app. Then properly installed Magisk by creating a new boot.img file and then flashing that new boot.img file with twrp. Magisk 14 showed safetynet passed both test. Off I went to the store to buy a chocolate bar, unlocked the phone, tapped it on the terminal and buzz buzz, payment approved. Very nice.
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Google Pay can be used under rooted device?
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
sb1893 said:
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Click to expand...
Click to collapse
JD_dadada said:
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
Click to expand...
Click to collapse
I've always been able to leverage the root hiding capabilities offered by the root providers I have used. Originally suhide for SuperSu...then when I moved to Magisk MagiskHide. Both have worked well for my root (and unlocked bootloader) hiding purposes. I've always been able to use Android/Google Pay, banking apps, alarm system apps, Netflix, etc...Occasionally, the cat and mouse game catches up with the root hiding solution, but the developers have been pretty quick to overcome any of the challenges encountered thus far.
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Zaczero said:
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Click to expand...
Click to collapse
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
javlada said:
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
Click to expand...
Click to collapse
Looks like I found the problem (at least in my case).
Some ROMs got issues with fingerprint scanner. I noticed that in my bank app after adding the fingerprint unlock it started to crash. Also in google play I couldn't add fingerprint as payment confirmation.
In Google Pay one of the steps of verifying cc is fingerprint check. I think that this fingerprint bug may cause the google pay to fail.
After installing a ROM with fingerprint scanner working properly (now I'm on LineageOS) the issue went away. Got my cc verified successfully with root and rom
Hey folks, I have a note 10+ n975f and used to root all my older phones in past for freedom and a bit of a change to customising etc... Anyhow tried using magisk to disguised my banking apps before on other phones but them and a few others still won't work, the apps crash, tried a few rooms and all do the se thing, restored phone to factory and they all work. As its been years since I used to root my phones am I missing something? I've followed as many guided here as I can but can't seem to get around this issue.
possible the apps have learnt to detect it better, security is a cat and mouse game and firms are getting better at stopping people using their stuff on devices they don't want them to, you may have to look into certain apps for specific ways to bypass the detection. but chances are a lot of apps are now designed to detect the things blocking the detection of the phone being unlocked.
sad fact is if you want to use secure stuff on your phone the only really bulletproof option is to keep the phone locked.
Yea I know what you mean. Aww I used to have oneplus 6 and it's software was amazing but love the note for its size and camera etc but software just seems so bloated and it's got double the ram like
I know what you mean, but for me personally I just disable the stuff I don't need and use Lawnchair launcher to get the phone running like a Pixel device, but on the other hand the Samsung software can often give extra features that havent gone into base Android yet.
I had apps that wouldn't work because it detected root. So I did this: Magisk/Settings/Hide Magisk Manager. My apps worked after that.
Eagle 3 said:
I had apps that wouldn't work because it detected root. So I did this: Magisk/Settings/Hide Magisk Manager. My apps worked after that.
Click to expand...
Click to collapse
Thanks for the reply however not meaning to be rude, I stated I already tried Magisk in the original post. It doesn't work for some apps like banking apps etc.
cruisinbeatz said:
Thanks for the reply however not meaning to be rude, I stated I already tried Magisk in the original post. It doesn't work for some apps like banking apps etc.
Click to expand...
Click to collapse
You were very unclear about what you did in Magisk. Did you use Magisk Hide or Hide Magisk Manager?
Eagle 3 said:
You were very unclear about what you did in Magisk. Did you use Magisk Hide or Hide Magisk Manager?
Click to expand...
Click to collapse
I used Magisk Hide from what I recall. Opened it up, safenet etc was all green and good to go, it worked for snapchat etc but would not work on 3 of my banking apps, those are the only ones it wouldn't work on. From memory, I when I opened Magisk, I checked safety net was goo, it was. so went and hid root from each app I knew would look for safety net. The apps in question are Co-Operative Bank, Ulsterbank and Dansk (Mobile Bank in store) They will not open, they try, a quick flash on the screen and it returns back to home screen. Tried 3 different roms and they all done same thing.
cruisinbeatz said:
I used Magisk Hide from what I recall. Opened it up, safenet etc was all green and good to go, it worked for snapchat etc but would not work on 3 of my banking apps, those are the only ones it wouldn't work on. From memory, I when I opened Magisk, I checked safety net was goo, it was. so went and hid root from each app I knew would look for safety net. The apps in question are Co-Operative Bank, Ulsterbank and Dansk (Mobile Bank in store) They will not open, they try, a quick flash on the screen and it returns back to home screen. Tried 3 different roms and they all done same thing.
Click to expand...
Click to collapse
As I stated in my first reply to you, you need to Hide Magisk Manager. This is different than Magisk Hide. Go to Settings and select Hide Magisk Manager. You will get a popup for new name, leave it as Manager, tap OK.
Then open Manager, you will get a message to update Magisk Manager, tap OK.
Restart the phone. Your banking apps should work now.
I had the same problem as you in that the apps didn't work by just selecting the apps in Magisk Hide. They did after Hide Magisk Manager. So you have to do both.
Hello everyone.
Today I decided to update my phone (12.5.8 Enhanced) to the latest MIUI version. I was kind of skeptical going into it, but still went with it thinking "why not?" When the update finished and the phone booted, it immediately rebooted and I thought maybe that's supposed to do that, but then it rebooted again, this time to MIUI Recovery mode. And now I discovered that whenever the phone tries to connect to the WIFI or Mobile data, it reboots. Every time. When the internet is turned off, it doesn't. And I noticed that my phone has become a bit laggy and not as responsive as with the previous version of MIUI I had on it, even the refresh rate isn't working properly, it says 120hz but clearly it's 60hz. The update rendered my phone hardly usable. What could be the problem? Has any Poco F3 users encountered these problems? What should I do next? Should I really consider flashing a custom ROM?
Thank you in advance, any help is kindly appreciated.
Wow. This is just with a System update on a phone with a locked bootloader?
You could try to format data... aka. Factory Reset.
If you unlock your bootloader, you must be aware of the downsides. Some apps won't work (atleast not without a workaround), like Banking apps, Netflix, Super Mario Kart, Google Pay.
That's cuz Google's SafetyNet API reports to those apps that the Security-Status of your phone is "Fail", because of the unlocked bootloader.
You can hide it with Custom ROMs that specifically list "SafetyNet passed" or by using Magisk Root with a SafetyNet Fix Module. Or Both idk whatever.
I use Xiaomi.eu Custom ROM on Android 12 with Magisk Root. Everything works, but this stupid cat & mouse game with Google and Android Modders definitely sucks.
I have a POCO F3 phone. No problems. Hope you used windows_fastboot_first_install_with_data_format.bat. In your case, you must not use the windows_fastboot_update_rom.bat option.
I have been using MIUI 13.0.3.0.SKHEUXM for a while. There was no problem.
Now I'm on MIUI 22.3.2 / 3 (weekly). I recommend. Works great, amazingly smooth, great option for new sidebar widgets ...
Of course, you need to have an unlocked bootloader. Look here: https://xiaomi.eu/community/threads/howto-install-fastboot-image-update-info-no-ota-download.64508/
I have an unlocked bootloader. NETFLIX and Google Pay work without any problems.
Rule no.1 of miui: never update until the community approves of the update. there are always bugs, sometimes some are fixed, but other show up.
Im sure that there'll be a new update which will solve these problems soon, but who knows what kinds of issues you'll have after that. Maybe you should unlock the bootloader and flash back to miui 12.5x stock, so that you can actually use your phone.
arkadia_1969 said:
I have a POCO F3 phone. No problems. Hope you used windows_fastboot_first_install_with_data_format.bat. In your case, you must not use the windows_fastboot_update_rom.bat option.
I have been using MIUI 13.0.3.0.SKHEUXM for a while. There was no problem.
Now I'm on MIUI 22.3.2 / 3 (weekly). I recommend. Works great, amazingly smooth, great option for new sidebar widgets ...
Of course, you need to have an unlocked bootloader. Look here: https://xiaomi.eu/community/threads/howto-install-fastboot-image-update-info-no-ota-download.64508/
I have an unlocked bootloader. NETFLIX and Google Pay work without any problems.
Click to expand...
Click to collapse
Exactly, all are said here ... No probleme with stable and weekly version ... Balaam custom kernel can help also on those rom.
After any major OS update ( I mean moving from one version of android to another) It is recommended to do a factory reset to your phone just after the update finishes.
I always do it for my phones and I did the same for my Poco F3 and had no issues so far. The phone works great, battery improved drastically for me and overall feels fresh.
Try to do a factory reset and see how it goes. MAKE SURE TO BACKUP YOUR DATA.
Thanks for the replies.
Bl4Ck R34Ct0r said:
Try to do a factory reset and see how it goes.
Click to expand...
Click to collapse
The thing is, in order to do a factory reset on the phone I have to connect to the Internet which is the thing that's causing the phone to reboot.
Can I do it like through the MIUI Recovery panel? Is it the same?
portugalas said:
The thing is, in order to do a factory reset on the phone I have to connect to the Internet which is the thing that's causing the phone to reboot.
Can I do it like through the MIUI Recovery panel? Is it the same?
Click to expand...
Click to collapse
Yes you can do that, you either boot to recovery from option in the update menu or hold volume up and power while the phone is turned off, then select wipe data. Just make sure to delete Mi account from setting and google account ( I know you have no internet but just making sure so you won't get stuck if somehow you forget your password). Good luck.
Got the same problem with the refresh rate.. 120hz option doesn't work and just does 60hz. I'm using the update my phone gave me. No beta or custom stuff. Just got the 13.0.3 global stable update. 120hz isn't working. Are there any better options for me now? I was thinking about flashing the previous 12.5 update back again. I heard someone here say I can use the xiaomi.eu custom ROM which works to root that one.. where can I find that ROM? And how do I flash that. (I've rooted phones before with magisk) but forgot most of it haha. So what's my best option here? I need my 120hz
tcvdh said:
Got the same problem with the refresh rate.. 120hz option doesn't work and just does 60hz. I'm using the update my phone gave me. No beta or custom stuff. Just got the 13.0.3 global stable update. 120hz isn't working. Are there any better options for me now? I was thinking about flashing the previous 12.5 update back again. I heard someone here say I can use the xiaomi.eu custom ROM which works to root that one.. where can I find that ROM? And how do I flash that. (I've rooted phones before with magisk) but forgot most of it haha. So what's my best option here? I need my 120hz
Click to expand...
Click to collapse
Yeah, the refresh rate not working as intended is frustrating. As with the downgrading and flashing, I'm afraid I can't help you with it, because I haven't done anything with flashing/rooting and all that kind of stuff. Wishing the best for you.
Kindest regards and best of luck
portugalas said:
Yeah, the refresh rate not working as intended is frustrating. As with the downgrading and flashing, I'm afraid I can't help you with it, because I haven't done anything with flashing/rooting and all that kind of stuff. Wishing the best for you.
Kindest regards and best of luck
Click to expand...
Click to collapse
Yoo. Some dude on Reddit found the solution!!!! You have to disable miui optimisation. Go to developer settings. Then all the way down somewhere it says: reset to default values. Click that a few times. Now a setting a bit down should pop up saying: "enable miui optimisation" enable that if it isn't already. Then disable it again. Now go to display settings and switch to 60 then back to 120 and there you go. You can now enjoy your 120hz again
tcvdh said:
Yoo. Some dude on Reddit found the solution!!!! You have to disable miui optimisation. Go to developer settings. Then all the way down somewhere it says: reset to default values. Click that a few times. Now a setting a bit down should pop up saying: "enable miui optimisation" enable that if it isn't already. Then disable it again. Now go to display settings and switch to 60 then back to 120 and there you go. You can now enjoy your 120hz again
Click to expand...
Click to collapse
Thanks, that worked for me too!
Regards
I had the same reboot problem with WiFi an mobile data. I could fix it with restoring all previously debloated apps. I am not sure which app exactly caused the reboot issues but now it works normal again.
tHoMaS-1 said:
I had the same reboot problem with WiFi an mobile data. I could fix it with restoring all previously debloated apps. I am not sure which app exactly caused the reboot issues but now it works normal again.
Click to expand...
Click to collapse
Thank you, that worked for me! I installed everything back I had debloated and uninstalled everything again and it seems to be working as of now.
Regards
Banking apps
dreamytom said:
Wow. This is just with a System update on a phone with a locked bootloader?
You could try to format data... aka. Factory Reset.
If you unlock your bootloader, you must be aware of the downsides. Some apps won't work (atleast not without a workaround), like Banking apps, Netflix, Super Mario Kart, Google Pay.
That's cuz Google's SafetyNet API reports to those apps that the Security-Status of your phone is "Fail", because of the unlocked bootloader.
You can hide it with Custom ROMs that specifically list "SafetyNet passed" or by using Magisk Root with a SafetyNet Fix Module. Or Both idk whatever.
I use Xiaomi.eu Custom ROM on Android 12 with Magisk Root. Everything works, but this stupid cat & mouse game with Google and Android Modders definitely sucks.
Click to expand...
Click to collapse
Banking apps work if you don't root the phone. Descendant ROM for instance passes SafetyNet as long as you do not install Magisk.
jadephyre said:
Banking apps
Banking apps work if you don't root the phone. Descendant ROM for instance passes SafetyNet as long as you do not install Magisk.
Click to expand...
Click to collapse
Yup, I mentioned that in my comment. But depends on the Custom ROM of course, not all pass SafetyNet. The devs usually mention it tho.
Hi, is there a way to use MIUI launcher instead of Poco launcher on poco f3 MIUI 13 locked bootloader ?? Thanks !
Since the upgrade, the audio from my phone cuts out after a few minutes and I have to restart it. I use bluetooth earphones to listen to the 'BBC Sounds' app over my home wifi. It doesn't cut out if I use a Redmi Note 8 pro nor a Samsung A5 in the same circumstances.
I don't know if it related but sometime I receive a warning notification tha I've been wearing my earphones too long. I didn't receive this warning before the Miui 13 upgrade.
Can anyone suggest what I can do to resolve the problem with the audio on my Poco F3 ?