Database Users

Resurrection Remix ROM 6.8 Build running Kernel 6.2 - Bootloop Issue Zenfone 5

Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!

Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?

tank0412 said:
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
Click to expand...
Click to collapse
Yup. Tried all this.

Just format again and re flash rom with xposed it fixed my bootloop.

The solution is,
Go back to stock rom. ???

Can anyone tell me how to back stock ROM from resurrection remix???

yasin0005 said:
Can anyone tell me how to back stock ROM from resurrection remix???
Click to expand...
Click to collapse
Download latest firmware from Asus' Support Page. And flash it via adb sideload.

I m now on Stock Rom without any problems no screen freeze no bootloops ...

can't update past LineageOS 14.1 20171013

Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I'd say do a clean install. If i have any issues with a rom booting i'll factory reset and install again. If i still have issues i'll just use another rom.

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I am in the same situation. Have tried all combinations of wiping and resetting with all 3 of the latest nightlies and still cannot boot. I can successfully boot into a stock rom but, I'd rather not. I guess I will go back to the 10/13 nightly since it worked (mostly) before this debacle. Hopefully next week's update will solve this problem.

Thanks for your reply, islandlife98. I'm not super-confident at this ROM thing yet so backing up, wiping and reinstalling is something I'd undertake reluctantly. I was hoping this was a common situation with a simple fix that I just had been unable to find. Always prefer to actually solve a problem if possible rather than just wipe it out. (Although when it comes to tech, wiping it out is often the best or only solution. Almost always the quickest.)
JBealZy, thank you for letting me know you're in the same boat! After seeing no mention of this issue here, I assumed it was some weird glitch with my phone rather than a problem with the updates. If you've done a full wipe and re-install but still haven't been able to boot into any of the last three releases then I'm glad I hesitated. (That was a concern I'd had: that it might not work even after a clean install.) Think I'll stick with 10/13 for now and keep trying the new releases; easy enough to roll back if it fails now that I've figured it out.

Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
I am using Paranoid ( latest version) and everything works flawlessly.
Sent from my LEX727 using XDA Labs

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.

fraxby79 said:
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
Click to expand...
Click to collapse
Yea i'm downloading Paranoïd right now for testing it .. Don't want a broken operating system on my phone haha

If anyone's still interested, I first tried flashing Lineage after wiping all but internal storage and still couldn't get past the boot animation. Then did a full factory-reset wipe including the internal storage, re-flashed, and it finally booted. The first OTA update since then came through today and went off without a hitch so all seems well for now.
I did take a look at Paranoid before going back to Lineage. One big reason I use a custom ROM is to get security updates quickly and LOS reports the security patch level in the settings; I couldn't find this info in PA. Also, I use a pattern to unlock my phone and there didn't appear to be a way use a larger grid than the default 3x3. On the plus side (sort of), PA includes the LeEco remote control app, which seems to be the only way to use the IR hardware on this phone, but it asks for more permissions than I want to give (which, of course, is not PA's fault). So admittedly I didn't really give it a full and fair trial but those few little issues sent me back to the (usually) reliable familiarity of LOS.

I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).

Heistergand said:
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Click to expand...
Click to collapse
Sorry, can't help you with that since I have a LEX727 which is apparently quite different from the LEX722. Official LineageOS is only supported on the LEX720 and LEX727: [ https://wiki.lineageos.org/devices/zl1 ]. The LEX722 (Elite) has it's own section here on the LeEco Pro 3 forum so check that out and see what they've come up with.

SystemUi constantly restart

Hi, I've been using this phone for last 2 weeks and ive experience this SystemUi constantly restart by itself. No error or crash popup, just the mobile data goes to error sign -> no sim card -> mobile data. Sometimes rebooting the device does help but most of time it does not.
Ive excounter this problem either unroot or root.
Have anyone experience this issue too?
OnePlus 6t, 8gb, Matte Black, International Ver
Stock OOS, Stock Kernel

Yeah I've noticed something like that. It's frozen up for a few seconds. Screen touches become unresponsive. Last time it happened I was just going back pages on Amazon app and it froze. Unrooted T-Mobile latest update. Maybe that's why they have a on/off schedule in settings.
Sent from my OnePlus6TSingle using XDA Labs

I had the same issue. I tried to recover by restarting. Now i am stuck in boot loop and constantly rebooting. Please help here.

This isuue happened to me since upgraded to OB1. My phone was rebooting randomly after booted for just a few minutes. I have tried get rid of all Magisk modules, dirty flash rom, reflash twrp and magisk. Etc ... After that I can't access the phone anymore. The phone just kept on shutting down after logged in. So i tried to get it recoverd by twrp but sadly, twrp didnt show the login screen so the data was encrypted including my backup recoveries.
I ended up fixing by rebranding with stock ota fastboot.
I think you should first backing up your data to external storage if you still have access to twrp. And just do whatever needs after that.
Don't be dumb like me and Good luck.
Sent from my ONEPLUS A6013 using Tapatalk

Downgrade from Pie (Official Stock Beta) to Oreo (Official Stable Nov. Patch) Issues

Hello Guys,
Recently i forced my Mi A1 to install official Pie Stable update by using VPN Method (Which Worked Fine). After Success full install of Pie Rom my Phone went in boot-loop.
Here are the details ->
1 - Mi A1 was rooted w/ Magisk. So I unrooted my phone, worked fine after removing magisk.
2 - After unrooting, Phone was working smooth no issues there.
3 - Locked boot-loader, after restart it was still working like earlier.
4 - Used VPN to connect to Netherlands Server, Cleared data from google framework & got the update.
5 - Took 8-10 mins. to get it flashed
6 - After restart Phone went straight to Boot-loop. I waited almost 40-45 mins. then forced shut down.
7 - Again restarted it but phone was again in boot-loop. So i booted my phone in recovery (stock). Cleared all data / cache. After restart the boot-loop was still there.
8 - i checked here at XDA if anyone else was facing any problem, i guess this one was unique.
9 - i then downloaded the official 8.1 stock ROM from miui website & clean installed using Mi Flash tool Successfully.
10 - After restart, my phone was continuously restarting. All I can see on screen was mi logo & android one logo. After that phone restarts itself.
11 - Again I checked if I missed any step from instruction provided by Developers, all of them were followed as described.
12 - After that I thought it must be Xiaomi's Anti-rollback feature that must be not letting my phone run Oreo. So I checked if that’s the issue, but anti returned null value. Which means it was not enabled on my device.
13 - So I looked for Mi A1 Stock Pie fast-boot Rom, Luckily I got beta Rom & so I flashed that. Which worked.
14 – Now the issue is, why I cannot go back to 8.1 & install that official stable pie? What should be my next step? What should I do to get stable build? Or is it possible that I could get stable pie TWRP rom?
Any help is appreciated.
Please guide me to get pass this issue.
Thank you for your time.

How did you installed fastboot rom without unlocking bootloader? Im facing same issue.

Try this
Hey try this, it might work for you:
1. Downgrade to Nougat by flashing it on EDL mode on MiFlash
2. Surely it won't boot so hotboot TWRP and restore the Boot, Modem and EFS Backup that someone uploaded some days ago (search on Questions & Answers or Guides)
3. Flash Nougat on EDL again
4. You'll notice that your IMEI will be 0 or not your phone's IMEI
5 To fix that, install TWRP Installer, reboot to recovery and install Latest Magisk
6. (Search on Youtube) Restore IMEI using DualWriteIMEI
7. Reboot
8. Flash latest Oreo Stock Build by normal Fastboot mode (not EDL)
9. That's all! You should be able to flash anything else that you want!
ADVERTISE: I have the Dual SIM variant, that because i've used DualWriteIMEI, idk if works too with Single SIM one, maybe it does.
Hope that it works for you, greetings!

Mirdeusz said:
How did you installed fastboot rom without unlocking bootloader? Im facing same issue.
Click to expand...
Click to collapse
boot-loader was unlocked when i first flashed magisk.

MallBrawl said:
Hey try this, it might work for you:
1. Downgrade to Nougat by flashing it on EDL mode on MiFlash
2. Surely it won't boot so hotboot TWRP and restore the Boot, Modem and EFS Backup that someone uploaded some days ago (search on Questions & Answers or Guides)
3. Flash Nougat on EDL again
4. You'll notice that your IMEI will be 0 or not your phone's IMEI
5 To fix that, install TWRP Installer, reboot to recovery and install Latest Magisk
6. (Search on Youtube) Restore IMEI using DualWriteIMEI
7. Reboot
8. Flash latest Oreo Stock Build by normal Fastboot mode (not EDL)
9. That's all! You should be able to flash anything else that you want!
ADVERTISE: I have the Dual SIM variant, that because i've used DualWriteIMEI, idk if works too with Single SIM one, maybe it does.
Hope that it works for you, greetings!
Click to expand...
Click to collapse
I will surely try this, thank you for your help

iammilind said:
Hello Guys,
Recently i forced my Mi A1 to install official Pie Stable update by using VPN Method (Which Worked Fine). After Success full install of Pie Rom my Phone went in boot-loop.
Here are the details ->
1 - Mi A1 was rooted w/ Magisk. So I unrooted my phone, worked fine after removing magisk.
2 - After unrooting, Phone was working smooth no issues there.
3 - Locked boot-loader, after restart it was still working like earlier.
4 - Used VPN to connect to Netherlands Server, Cleared data from google framework & got the update.
5 - Took 8-10 mins. to get it flashed
6 - After restart Phone went straight to Boot-loop. I waited almost 40-45 mins. then forced shut down.
7 - Again restarted it but phone was again in boot-loop. So i booted my phone in recovery (stock). Cleared all data / cache. After restart the boot-loop was still there.
8 - i checked here at XDA if anyone else was facing any problem, i guess this one was unique.
9 - i then downloaded the official 8.1 stock ROM from miui website & clean installed using Mi Flash tool Successfully.
10 - After restart, my phone was continuously restarting. All I can see on screen was mi logo & android one logo. After that phone restarts itself.
11 - Again I checked if I missed any step from instruction provided by Developers, all of them were followed as described.
12 - After that I thought it must be Xiaomi's Anti-rollback feature that must be not letting my phone run Oreo. So I checked if that’s the issue, but anti returned null value. Which means it was not enabled on my device.
13 - So I looked for Mi A1 Stock Pie fast-boot Rom, Luckily I got beta Rom & so I flashed that. Which worked.
14 – Now the issue is, why I cannot go back to 8.1 & install that official stable pie? What should be my next step? What should I do to get stable build? Or is it possible that I could get stable pie TWRP rom?
Any help is appreciated.
Please guide me to get pass this issue.
Thank you for your time.
Click to expand...
Click to collapse
FOLLOW THE INSTRUCTIONS CAREFULLY
i went back to nougat using this guide
https://forum.xda-developers.com/mi-...-beta-t3876533
in step 9 move that file "2018-12-06--15-41-27_PQ1A181205006" to straight TWRP folder....it will present inside backups folder so move it and delete backups folder then you can roll back to nougat/oreo then do anything

Selvakmr123 said:
FOLLOW THE INSTRUCTIONS CAREFULLY
i went back to nougat using this guide
https://forum.xda-developers.com/mi-...-beta-t3876533
in step 9 move that file "2018-12-06--15-41-27_PQ1A181205006" to straight TWRP folder....it will present inside backups folder so move it and delete backups folder then you can roll back to nougat/oreo then do anything
Click to expand...
Click to collapse
Your url link is bad.

barrack1 said:
Your url link is bad.
Click to expand...
Click to collapse
If you wish to downgrade....i think it is the only way for now.... This is not my creation i just followed the method...worked perfectly... If you don't want to modify system then stay in pie update bro..
I think using Netherlands vpn is bad as this...because installing other regions will mess up something within our mobile...we don't realised it yet

iammilind said:
Hello Guys,
Recently i forced my Mi A1 to install official Pie Stable update by using VPN Method (Which Worked Fine). After Success full install of Pie Rom my Phone went in boot-loop.
Here are the details ->
1 - Mi A1 was rooted w/ Magisk. So I unrooted my phone, worked fine after removing magisk.
2 - After unrooting, Phone was working smooth no issues there.
3 - Locked boot-loader, after restart it was still working like earlier.
4 - Used VPN to connect to Netherlands Server, Cleared data from google framework & got the update.
5 - Took 8-10 mins. to get it flashed
6 - After restart Phone went straight to Boot-loop. I waited almost 40-45 mins. then forced shut down.
7 - Again restarted it but phone was again in boot-loop. So i booted my phone in recovery (stock). Cleared all data / cache. After restart the boot-loop was still there.
8 - i checked here at XDA if anyone else was facing any problem, i guess this one was unique.
9 - i then downloaded the official 8.1 stock ROM from miui website & clean installed using Mi Flash tool Successfully.
10 - After restart, my phone was continuously restarting. All I can see on screen was mi logo & android one logo. After that phone restarts itself.
11 - Again I checked if I missed any step from instruction provided by Developers, all of them were followed as described.
12 - After that I thought it must be Xiaomi's Anti-rollback feature that must be not letting my phone run Oreo. So I checked if that’s the issue, but anti returned null value. Which means it was not enabled on my device.
13 - So I looked for Mi A1 Stock Pie fast-boot Rom, Luckily I got beta Rom & so I flashed that. Which worked.
14 – Now the issue is, why I cannot go back to 8.1 & install that official stable pie? What should be my next step? What should I do to get stable build? Or is it possible that I could get stable pie TWRP rom?
Any help is appreciated.
Please guide me to get pass this issue.
Thank you for your time.
Click to expand...
Click to collapse
Hello you have said at step 3 that you locked the bootloader and at step 9 that you have flashed via fastboot with locked bootloader how did you do that ? thanx

Selvakmr123 said:
If you wish to downgrade....i think it is the only way for now.... This is not my creation i just followed the method...worked perfectly... If you don't want to modify system then stay in pie update bro..
I think using Netherlands vpn is bad as this...because installing other regions will mess up something within our mobile...we don't realised it yet
Click to expand...
Click to collapse
he was saying that when we click this link you've posted we get a page 404 because the link is broken.

sergioricardojsj said:
he was saying that when we click this link you've posted we get a page 404 because the link is broken.
Click to expand...
Click to collapse
My bad guys
Follow this link
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533

Bootloop while Downgrading and network issue
VoLTE isn't working in pie beta rom on my device( mi a1) after several unsuccessful downgrades from pie to oreo.

tsrnb said:
VoLTE isn't working in pie beta rom on my device( mi a1) after several unsuccessful downgrades from pie to oreo.
Click to expand...
Click to collapse
maybe thats because we forced our phone to flash pie beta, it's modem may not support our LTE bands for VOLTE service.
we will have to wait for stable release, after that we will be able to flash that modem & use volte service.

cheaterel said:
Hello you have said at step 3 that you locked the bootloader and at step 9 that you have flashed via fastboot with locked bootloader how did you do that ? thanx
Click to expand...
Click to collapse
my bad, please consider bootloader was unlocked at the time of flashing.
i should have included that.

Screen Lock security issue G975F Q Beta 2

Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.

kazim.asghar said:
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
Click to expand...
Click to collapse
Same issue with me as well. Can anyone help..

kazim.asghar said:
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
Click to expand...
Click to collapse
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..

mykenyc said:
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
Click to expand...
Click to collapse
I intalled beta 2. Everything was working fine. But when I restarted my phone, it stopped accepting my 4 digit pin. Then i hard reset the phone and factory reset. But after that it not accepting any new Pin or Pattern to register.
What should I do know as there is no screen lock on my phone

mykenyc said:
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
Click to expand...
Click to collapse
I did a clean install fresh firmware for beta 1, clear cache for beta 2.
I am not sure how many unlocks but i took few days after beta 2. My phone was waorking fine in morning as I unlock my phone in car using pin. But in after noon when I used the pin it showed me wrong pin. Every thing related to security wont work. Cant register finger print or face. But if you do same in secure folder everything will work fine.

Okay if it happens to me I will try to track down how it happened.

You did something and screwed up. A lot of people are using beta 2 already and have not encountered this issue, myself in it. I have done a lot of restarts and I have changed my pin successfully.

NickosD said:
You did something and screwed up. A lot of people are using beta 2 already and have not encountered this issue, myself in it. I have done a lot of restarts and I have changed my pin successfully.
Click to expand...
Click to collapse
What about other people who are affected by it? Read comments in Android 10 beta thread on page after 135. You will find people reporting this issue.
I didnt do anything with my phone just updating with beta.

I'm another that's been affected, had to do a factory reset via bootloader.
Currently stuck on Beta 2, Smart switch won't downgrade.
No security options available and an extremely buggy phone.

A new update has been pushed out. I just received it on my phone. Will be performing a factory reset once the update is installed and will setup the phone from scratch.

ashwinrajsr said:
A new update has been pushed out. I just received it on my phone. Will be performing a factory reset once the update is installed and will setup the phone from scratch.
Click to expand...
Click to collapse
Update me if it has fixed the security issue.

i installed *emergency update* , no wipe,no reset ,things go back to normal

Everything is cool as the phone has not been blocked. Otherwise there is no way to upload the update.
I wonder why they can't release the patch to upload it via ODIN, that would solve the problem.

Wait what !?!?, the same thing happened to me
Even worse - i rolled back to P, where i was able to add a pin but it would always forget it. I ended up going to a samsung center where they changed the board (in warranty), they said my unique device key was corrupted - likely due to internal storage error
So it is a beta problem then
Please provide feedback in the samsung members app. Those that cant, send feedback in the official thread at samsung forums.

Beta 2 is Terrible, having all kinds of Problems with it. Beta 1 was Much Better. Hope another Update comes out soon or will just go back to PIE. G975U S10+

I do have the same problem on my Zenfone 6z. After I relocked my bootloader I couldn't set up a pin. Asus still haven't rolled out an update.