I used fingerprint unlock with my Note Edge (N915G) and had the occasional pseudo-reboot issue that required me to enter the password, but all in all it was usable. However, with the latest update (security patch from April 1, kernel 3.10.40patch from April 18) I can no longer use it. When I lock the phone and try to unlock it, the phone tells me I need to enter the password.
Note that my phone is not rooted and that I do use KNOX (for work email).
Any way to overcome this issue?
Thanks!
oren_b said:
I used fingerprint unlock with my Note Edge (N915G) and had the occasional pseudo-reboot issue that required me to enter the password, but all in all it was usable. However, with the latest update (security patch from April 1, kernel 3.10.40patch from April 18) I can no longer use it. When I lock the phone and try to unlock it, the phone tells me I need to enter the password.
Note that my phone is not rooted and that I do use KNOX (for work email).
Any way to overcome this issue?
Thanks!
Click to expand...
Click to collapse
There is a way if you really want, but you might not do it. Downgrade to the version before the April version. It's very simple and uses Odin.
Can it be done without rooting the phone and without tripping KNOX?
Same problem without root stock rom
Related
OK, here goes. I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
So, has anyone running COS 12.1 had any luck with Android Pay? Thoughts, comments, suggestions are all welcome.
Hurricane Andrew said:
OK, here goes. I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
So, has anyone running COS 12.1 had any luck with Android Pay? Thoughts, comments, suggestions are all welcome.
Click to expand...
Click to collapse
Yes I have also fyi - there is also another thread talking bout Android pay and what we got it working on and which roms it does not work with. Did you try it with root enabled?
playya said:
Yes I have also fyi - there is also another thread talking bout Android pay and what we got it working on and which roms it does not work with. Did you try it with root enabled?
Click to expand...
Click to collapse
I first tried it with root enabled, then when that didn't work I did the full unroot. I will try with just disabling SU over the weekend and see what happens.
Hurricane Andrew said:
I first tried it with root enabled, then when that didn't work I did the full unroot. I will try with just disabling SU over the weekend and see what happens.
Click to expand...
Click to collapse
yeah with stock no need to full unroot. you can have bootloader unlocked root added and all that. Its just when you set it up make sure its stock root and not by using the supersu zip file. My findings was when I flashed Supersu it did not work but if I flashed stock rom then let TWRP inject root it worked. Of course I unchecked the option in supersu set up Android Pay then found one of those coke machines that take Android pay and tested it out.
The US version of the ZC520TL (X008DC) has a firmware/software update available that will take you from MRA58K.US_Phone-13.1.4.17-20161011 to MRA58K.US_Phone-13.1.4.43-17-20170215. Still Android version 6.0.
This downloaded before I could get a LogCat to capture the ASUS storage address.
Could some one else please capture a LogCat and post it here so we can download the firmware/software in order to help us gain root access?
I have the same model and there us no update?
So if there is no update, why did I receive a new software notice, go through the update and install process and then see my version numbers change? Also, the security patch changed from August 2016 to January 2017.
That sounds like all the parts that qualify as an update to me.
tcaudill01 said:
So if there is no update, why did I receive a new software notice, go through the update and install process and then see my version numbers change? Also, the security patch changed from August 2016 to January 2017.
That sounds like all the parts that qualify as an update to me.
Click to expand...
Click to collapse
I went and manually check for the update and yes ,there is a new update, let me update and see if I can give the information you are looking for
regards
Hi,
Just updated my phone yesterday and had problems with my pattern unlock, it just doesn't work anymore, as every time you reboot your phone it asks for your pattern, even with a fingerprint unlock enabled I can't pass lock screen, anyone having same issues? Weird thing is that even missing the pattern several times (close to hundred) it never blocks for 30 seconds or asks "Did you forget you pattern?" to try my google pass instead...
Any help is appreciated, no debug mode enabled, so no adb/fastboot either...
Thanks in advance!
Can anyone tell me if there is a root for this device on 7.0 ? Thank you.
FatKris said:
Can anyone tell me if there is a root for this device on 7.0 ? Thank you.
Click to expand...
Click to collapse
Yes, try this method https://forum.xda-developers.com/zenfone-3/how-to/actual-solution-to-rooting-crisis-t3672618
work for me
I have a regular Sprint S7 (SM-G930P). I just updated to nrd90m.g930pvpu6brd2 and I want to go back to the previous version. Is it possible to do without rooting? Is there a way to root without losing all the data on my phone? I would like to use the version just before the March 2017 security update.
Thank You
You cannot flash lower firmware even with root because your bootloader has been updated, cannot downgrade anymore
Even though they are both 7.0 roms? Has the bootloader been unlocked yet?
Bootloader remains locked for all snapdragon models. You should be able to side step in version, but not go back. Even though it's all still android 7.0, bootloader versions continue to update, so there's several for 7.0.
I figured that. I would like to remove the security patch that messed with mock locations. Thank you
( Main question below at the end in Bold Italic ) ...... So here's what happened.
I was using ( probably Sept 2020 ) Security Patch on my phone and everything was well. Then there were 2 software updates from Samsung, both were security updates. I initially didn't upgrade to October update, because the phone was already nearing 4 years from launch and I did have a bit of experience with Samsung where I felt it sometimes got slower especially in end updates , and this update was given in one month from sept update which was weird for a 3.5 year old phone, but later January 2021 Security update was also out and I decided to upgrade to at least October patch. Upon upgrading to October Update my Sensors stopped working ( - Iris scan, accelerometer, gyroscope , light sensor - they just turn on for a sec and stop working, I still believe it isn't a fault with Sensor microcontroller,. So I then did all the steps like clearing cache partition, etc as described in various threads & forums. None helped and finally I upgraded to January patch and yet the problem isn't gone.
The bootloader has been upgrader to some 'B' version as from what I can say from my current PDA Version G950FXXSBDUA3 which was earlier G950FXXSADT1I . So That was bootloader version A I assume. Before which there has been One Bootloader version 9 - which I prefer to downgrade to and then turning off auto update system from dev options.
----------------------------Main Question ------------------------------------------------------
So my main doubt was :- If I Download the July firmware which has those 4 files in it, not load the old bootloader file and then flash it via ODIN, will KNOX TRIP ? will it be 0x1 ? Because I want to continue using Samsung Pay , Samsung Health , Secure Folder and other apps. P.S. Do share if you have done anything like this on any other Samsung phone ( after 2014 - when e-fuses were introduced in them ) and did it trip KNOX ?
**I don't remember, but I did it trip on a Galaxy Note 3 when I was a kid. Can't experiment much with ODIN. Before it used to be one PDA file, now I am wondering if flashing only AP file works ?
---------------------------------------------------------------------------------------------------
Got some part of my answers. Odin won't flash older firmware - at least if you don't turn on OEM Unlocking in Developer options, and it prevents Knox from tripping. I won't try OEM Unlocking as of now. I tried loading only the old AP file and not the bootloader file, and it failed ( got suck in middle ), then I tried all 4 files of old firmware, and still, it failed. So overall got the answer can't downgrade without tripping KNOX as of now. There is something like a developer bootloader or so, but I don't know about that.
Hello Guys,
I Just wanted to know how I root my pixel 3 with android 12 just guide mn or is there already a thread than give me a link but plz for android 12
Rooting Android 12 works exactly the same as Android 11 on the Pixel 3.
Since there were no obvious guides, I just wrote one for the Pixel 3. Here you go.
Thanks for help
Can u tell me is there any twrp for android 12
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Hmm so how we install custom roms
rocketrazr1999 said:
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Click to expand...
Click to collapse
Update... Android 12 can be rooted using Magisk Canary
I was able to take an OTA update to Android 12 on my BL unlocked, rooted, custom kerneled Pixel 3! I started the update accidentally by hitting that pop up reminder and after a minute of thinking what to do (i did not want to lose my data!!!), I held down the power button to force it to reboot during the update. I have had this work to stop an OTA update and restore it perfectly to previous state. Anyway, it did NOT work this time, and it updated to A12 perfectly! No loss of data, no loss of custom kernel, but i did of course lose root. Also.... when i checked the update version in settings, it wanted to update AGAIN, from Oct 21 to Feb 22 (which is just an Emergency Dialer patch). My phone still shows Oct 21 security patch in settings, but shows the Feb 22 firmware (...016.C1), which suggests the patch was only a tiny fix to the 911 Dialer and did not affect anything else. So this time i let it update, which i started to think was stuck or looping after waiting about an hour, but finally i checked the progress and it was done, requesting a reboot! So i rebooted it and behold, its now running final security update to the Pixel 3, and all i need to do now is root with Magisk and install SafetyNet Fix. Which is the ONLY thing i can think of as to how it was able to do a factory OTA update while rooted and BL unlocked! The SafetyNet Fix patch may be so good that it bypasses the Google security measure that refuses to allow OTA updates on rooted, unlocked Pixel 3s. Yup, on a GOOGLE PIXEL! I used to have to unroot and install the factory kernel to do an OTA sideload on my old Essential in order to update and not lose data, but i was told that you could not update to new Android versions without losing your data on the P3, so Ii just figured my Sept 21 A11 firmware was the final update until a phone upgrade. Anyway, just wanted to pass on the good news that you CAN perform a factory OTA update from A11 to A12 on the Pixel 3 WHILE rooted and unlocked and with a custom kernel, but I of course have to recommend you do so on your own, and if anyone has an unused or non-daily driver P3 that want to confirm this good news, please do so and help convince the disbelievers ! The ONLY thing i would recommend is that you have the latest "Android 12" version of SafetyNet Fix installed with the switches on in Magisk, which is what i had. Its the only thing i can think of that would allow Google's Safety Net to bypass the security restrictions. OK then, hope a few of you give it a try to show im not a nutcase, lol.
Question kind of related to this... Was the P3 kernel updated in Android 12 to fix that race condition that causes freezes if using systemless hosts? With A11 I always had to make sure I installed a custom kernel before Magisk and enabling systemless hosts to keep my P3 from freezing.