Develop Bugs

"Compatibility Patch" LG G4

"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.

I didn't get this "comp patch" as an individual update. Last week, I got the update with the security patches from July 1 (German G4, no branding), and it looks like that this patch was included. It now shows in the list of installed LG applications, where it didn't appear before. My wife (LG G3) got this patch as a single install (~1 week ago).

I have got this compatibility patch too, and in description of this app is 20160809 so it is 1 week old. But what was going about in that "fix"... :/

I've got the patch today too. But haven't rebooted yet.

U talking about this one? What is that supposed to do?

I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.

akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
If you have the encryption on then turn it off and reboot. That should resolve the issue and then you can turn it back on. Hope it works for you.

akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.

Problem with the Patch
I got the same patch on my LG V10. Thinking nothing of it I agreed to install and reboot. Once I had done so, I now have the Yellow Boot Warning at every boot. And also a bunch of my system apps stopped working. Camera, Phone, Music. I don't remember ever flashing a ROM that would trigger the warning seeing as how I got the update to 6.0.1 a few days before and hadn't done anything since. So I flashed back to stock with LGUP and the problems still persist. This is my first post ever, any advice. I apologize as I know this is a LGG4 thread.

If you did anything to the system image, you may have issues applying the OTA. @SixTheAmateur: did you modify in any way your V10? Did you flash a KDZ not officially available to your V10?

Index100 said:
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.
Click to expand...
Click to collapse
Yes that was the problem. Solved after disabling encryption

Guys the compatibility patch dissappeared??? Help yesterday it showed up Today nothing

Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?

Copperwolf said:
Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?
Click to expand...
Click to collapse
I've had massive compatibility issues with my g4 and apps I like to use. I noticed this today and definitely installed it. I have been able to use the apps I hadn't been able to use.
It seems to be going well so far. I'd say do it.
It seems to be frozen/disabled after installing, odd.
Sent from my LG-H811 using XDA Labs

Press and hold on notifications to see which app is giving them

Compatibility Patch Mystery to T-Mobile and LG
I got a notice for a compatibility patch several weeks ago.
Rather than click I contacted LG, who knew nothing of it.
So I contacted T-Mobile, my carrier, and they knew nothing of it and suggested I don't down load it.
It popped up again today and I'm going to ignore it until I understand what it will do.
Good Luck!

Similar experience. I had issues with my phone afterward and had to get a new one.
Similar experience. I had issues with my phone afterward and had to get a new one.
nikooe said:
"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.
Click to expand...
Click to collapse

OP3 random restart

sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/

My congrats for the great autonomy ?
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?

Simone98RC said:
My congrats for the great autonomy
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Click to expand...
Click to collapse
everything is stock, still new of android so and ty

athais said:
everything is stock, still new of android so and ty
Click to expand...
Click to collapse
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?

Simone98RC said:
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Click to expand...
Click to collapse
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset

athais said:
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
Click to expand...
Click to collapse
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.

Simone98RC said:
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Click to expand...
Click to collapse
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?

Flash another room
Seems to be an issue with OOS, I had the same problem, and flashed MIUI 8 and had 0 reboots. But when I flashed Fredoom OS based on OOS 3.2.7 my phone kept rebooting.

athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Are you using a case? I had a cheap eBay clear case on my phone and it wasn't moulded properly over the power button, there was no indent on the inside for the button to sit in so it used to turn off in my pocket and back on later and produced battery graphs similar to yours.
Hope this is a help.

athais said:
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Click to expand...
Click to collapse
Did your problem solved? I am having same problem.

I have the same problem. I am currently on 3.2.8 and also had this problem on beta 9. Few days ago it happened in front of me, the phone was on the desk nothing running in the background. That was kind of the soft reboot, didn't triggered my locked sim, (my sim card is locked needs to enter PIN when phone startup) and after that I checked Settings=>About Phone=>Status, the uptime didn't affected too, seemed nothing was happened. I think this also happened to some other people but they just didn't realize it.

Karthi91 said:
Did your problem solved? I am having same problem.
Click to expand...
Click to collapse
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Click to expand...
Click to collapse
Yes.. I'm on 3.2.8 and did factory rest also. No use
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Same for me. Is your problem solved? Please help me. It is really annoying. I have Pin setup for restart so when boot happens in night, if no input for pin phone stays off.

Can this be related to SIM carrier:Radio drivers?

I dont think so.. Because i havent changed Sim

Karthi91 said:
I dont think so.. Because i havent changed Sim
Click to expand...
Click to collapse
Try using non 4G/LTE SIMS.
I am facing the same problem.
My device is at service center.
Day one:No reboots.I asked them to put some SIM & then check.

I did that after reading your post. No luck. Are they replacing it? How many days since it is in service center?

Facing problem from last 2 weeks.
I submitted once last week.They clean flashed older rom.Worked fine for one day,then reboots started again.
Then this technician had remote session and flashed the rom OnePlus3_16_A.17_161118(OOS 3.2.8):Reboot frequency went too high.
Had to go to Service center for diagnose. 2 days now.No proper response from them.

I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that

Belyakovni said:
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Click to expand...
Click to collapse
Seriously? That sounds like one of those hilarious Microsoft Answers sort of posts! Running the battery down will not get rid of "electricity or static from the phone", apart from anything else the battery protection circuit would not allow the battery to drop to zero volts as it's not good for li-on batteries.
The Oneplus 3 seems to like to soft restart, mine sometimes decides to do it 3-4 times a night (rarely during the day) and then is fine for awhile. Tell tale sign is the battery graph showing large gaps in the usage pattern. I would suggest that there is an inherent firmware issue judging by the number of people reporting the same issue on a number of different forums.

Unable to install latest M8s OTA update v2.20.401.1

Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help

Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:

spiderwebmkd said:
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Click to expand...
Click to collapse
If you are willing to, you can unlock the bootloader from http://www.htcdev.com/bootloader/ and flash a stock sense ROM or other custom ROMs and that might solve the app crash problem.

bilal.fanatic said:
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
Click to expand...
Click to collapse
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore

spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.

ckpv5 said:
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
Click to expand...
Click to collapse
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?

spiderwebmkd said:
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
Click to expand...
Click to collapse
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)

spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:

bilal.fanatic said:
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
Click to expand...
Click to collapse
I'll try with @ckpv5 suggestion, to install 2.10.401.1 RUU and then try OTA upgrade to 2.20.401.1. If it fails, or if it succeeds but apps are still crashing as they were before, I'll definitely switch to cm, whatever version is stable at the moment. Double tap to wake is really annoying and I don't need it, I don't use 3rd party camera apps, and I guess I'll have to live without boomsound Thanks for the tip, though.

ckpv5 said:
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
Click to expand...
Click to collapse
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)

does someone have stock marshmallow twrp backup. I accidentally deleted mine and now stuck with cm only

spiderwebmkd said:
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
Click to expand...
Click to collapse
I can't access that site but it is the same file that I have that I got from different link.
Yes .. use that one.

I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing

parser said:
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
Click to expand...
Click to collapse
It passed after you flashed the RUU? the same procedure that I'm about to do?

spiderwebmkd said:
It passed after you flashed the RUU? the same procedure that I'm about to do?
Click to expand...
Click to collapse
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.

parser said:
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
Click to expand...
Click to collapse
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!

spiderwebmkd said:
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
Click to expand...
Click to collapse
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.

parser said:
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
Click to expand...
Click to collapse
I don't have a backup of v2.20. I flashed the v2.10 from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC) , and then I downloaded the OTA update on top of it.

spiderwebmkd said:
https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
Click to expand...
Click to collapse
no no not that. I mean TWRP backup. I dont want to go back to zero relock the phone and flash the zip and re-unlock the phone root again bla bla.
Since you did the same process, I thought maybe you took a backup of the rom after you updated it.
I made a mistake by not taking a backup of it so now it is a problem for me :/
Edit: damn! thanks anyway. I have a long night in front of me clearly. I hate this phone :/

V4A is not working anymore with the latest update. Is it me or everyone has the same problem.

Fixed Beta 2 security screen problem.

Hi, A lot of people are having issue regarding security of device as you cant change your pin and it wont let you enter your pin by showing wrong pin. You cant even have any security after doing a factory reset.
I have done everything to fix it , even took it to samsung repair center, still no success so I have sent it to samsung warranty today.
I have done these things to fix it but nothing worked.
1. Tried online samsung and google "find my phone" service" to fix it as it is shown on some sites for older phones.
2. Reset the phone through recovery.
3. Install fresh firmware through Odin. Then installed both beta versions.
4. Installed orignial firmware mine was VAU.
5. Installed the first firmware of s10 plus. With Nand reset and partition using PIT file.
6. Took it to samsung, they tried 2 different firmwares to fix it but all in vain.
In the end Samsung told me that it might be issue after security patch done for screen protector. They cant do anything at the moment and I have to wait for a fix through update but I have sent my phone to warranty.
I posted this issue in Q&A last day after having issue. But now I can see There are a lot of people affected by this. In my opinion it is Beta 2 issue.
Once you encounter this issue, you are helpless until samsung fixes it. Until then just keep your data, no need to do factory reset or new firmware, as it wont do any help.

What?... Never had any of these issues dude

twoxa said:
What?... Never had any of these issues dude
Click to expand...
Click to collapse
I also got this first time. It is very frustrating and I spend 7 hours to fix it but nothing worked. Until now i have seen 5-6 people who are facing this issue after beta 2. More might come.

I'm also facing this problem, hope Samsung fix this ASAP.

Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?

madvinegar said:
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
Click to expand...
Click to collapse
I sideloaded it.

To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?

madvinegar said:
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
Click to expand...
Click to collapse
I did rolled it back but didnt work for me. my issue is persistent and even samsung service centre could not fix it. I gave my phone in warranty because I am not sure how much samsung will take to fix this issue and they might be able to fix it. Lets see what samsung will say.

am not having any of these issues on S10+ Beta 2

I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.

bomp306 said:
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
Click to expand...
Click to collapse
You can use odin to go back to normal build but there is high probability that it wont fix the issue.

Does this have anything to do with the recent update in the biometrics (fingerprint issue).?
I cannot understand why this bug was not seen right after the update to Beta2, but only after 3-4 days...
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
The good thing is that this bug affects also the ones who officially enrolled to the Beta program, so this means that Samsung must be working to release a fix. At least I hope...

kazim.asghar said:
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Click to expand...
Click to collapse
I'm on latest android 9 stable via ODIN but the problem with biometrics and pin lock keep in the phone, I did every wipes with no results

Hotfix rolling out now OTA

Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.

AshishV95 said:
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
Click to expand...
Click to collapse
It's already shared in the appropriate thread.

Intratech said:
Hotfix rolling out now OTA
Click to expand...
Click to collapse
Fixed!!
Just need to restore all my apps again now..

should change the thread to SOLVED now that samsung has released a hotfix for it

bomp306 said:
Fixed!!
Just need to restore all my apps again now..
Click to expand...
Click to collapse
Is it fixed? Can you change pin code?

I flashed it and I have absolutely non of the issues you're having. I have an unlocked S10+ on Verizon and I'm running the ZSJF build

Question RE : SD1A.210817.037

My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait

You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip

miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?

Yes

I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.

miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?

NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?

old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.

NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?

old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.

Do I need to root my phone before manually updating using the OTA file?

speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No

Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!

I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers

virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal

From Orange France is 036, from Google store is 037

Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine