Database Develop

TWRP asking for password

Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?

Please search next time...
The password is as follows: (type or exactly as written below)
default_password

Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow

you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.

xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...

kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me

TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.

xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app

ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?

sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.

yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?

sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.

ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.

Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone

Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...

mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?

i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?

sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.

seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.

sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .

[Q] Nexus 6 Won't Boot Into Recovery

Hello. Sorry if this issue already exists and I'm being negligent, but I have an interesting issue with TWRP. Whenever I try to boot to recovery, the screen stays at the teamwin splashscreen for a short time as it should, but then the device reboots normally and never allows me into the recovery. I've tried reflashing numerous older versions of TWRP via "fastboot flash recovery..." but the reboot still occurs. Just before this started happening I tried doing an "adb push..'" and that resulted in a permission denied. So I remounted using "mount -o rw,remount,rw /system" and the push succeeded. I'm pretty sure that this is at fault because I was able to get into recovery one time after playing with the writable and read only forms of the aforementioned command and wiping the cache via fastboot. Any ideas?

try deleting it first, via fastboot, then reflash it.

simms22 said:
try deleting it first, via fastboot, then reflash it.
Click to expand...
Click to collapse
I ran "fastboot erase recovery", reflashed TWRP, and the reboot still occured at the splashscreen.

It might be a long shot. Try and flash within Android using an app called Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Very simple app to use. :good:

Maverick-DBZ- said:
It might be a long shot. Try and flash within Android using an app called Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Very simply app to use. :good:
Click to expand...
Click to collapse
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?

Astrophysicist789 said:
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Click to expand...
Click to collapse
Yeah, enter your password.

Astrophysicist789 said:
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Click to expand...
Click to collapse
Glad to hear it.
Sure, it's really simple, use your lock screen password. If you have a pattern lock you need to envision your pattern lock into numbers. The below example should help you out.
1 2 3
4 5 6
7 8 9
If you're still having problems, then just turn off pattern lock or use a regular numbered password. On the off chance what I said doesn't solve your problems, you can try one last thing.
Backup anything important on your phone before doing any of these steps below. Make sure lockscreen password is off. You can turn it back on once you've confirmed this worked.
1) Flash a modded stock boot image via Flashify, this will disable forced encryption.
2) Boot into bootloader and use fastboot format userdata
The command will wipe your phone to factory setting, so make sure you backed up! Flash a custom kernel after if you want.

Maverick-DBZ- said:
Glad to hear it.
Sure, it's really simple, use your lock screen password. If you have a pattern lock you need to envision your pattern lock into numbers. The below example should help you out.
1 2 3
4 5 6
7 8 9
Click to expand...
Click to collapse
I thought they got rid of this method and replaced it with something more pattern-lock like, in latest 2 versions?

danarama said:
I thought they got rid of this method and replaced it with something more pattern-lock like, in latest 2 versions?
Click to expand...
Click to collapse
It has been awhile since I've checked, so I had a look at the change logs and you're right, pattern lock was added in build 2.8.6.0. This should make it easier for @Astrophysicist789

Maverick-DBZ- said:
It has been awhile since I've checked, so I had a look at the change logs and you're right, pattern lock was added in build 2.8.6.0. This should make it easier for @Astrophysicist789
Click to expand...
Click to collapse
Further, if he hasn't set a lock, there should be a default TWRP one somewhere in the thread.

Password doesn't always work.

My 4-digit password works just fine during normal use. But after upgrading to oxygenOS 5.0.1 (OTA) , I decided I wanted to revert back to nougat. So I load my backup in twrp and reboot, and it asks for my password rather than fingerprint to unlock screen because of reboot. And that's when my password is not recognized.
This is the only password Ive ever used for my phone so its definitely the right one. I can also see notifications and accept calls, it just won't unlock the screen. I also tried the default code for my simcard but even removing it doesnt make a difference.
Next, I restore my backup for 5.0.1. that I made prior to restoring nougat, and the same thing happens, password doesn't work. I had to do a factory reset to get my phone working again.
Still determined to get good old android 7 back, I install the original recovery as to upgrade from the oneplus website. And upon booting to recovery my password is once again not recognized.
I'm now back on twrp and have no problems with my passcode. But I think this is strange so maybe someone here has an idea about what's going on.

If you're restoring a backup, you have to remove gatekeeper.pattern (or password).key and locksettings.db, once removed it will work

I moved those files from data/system to data and it worked. Thank you very much!
I noticed this also removes the lock if you set it from another computer using the 'my devices' section of your google account. But it does not remove the lock notification, to do that you simply have to set a new password from your phone.

And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.

ast00 said:
And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.
Click to expand...
Click to collapse
AFAIK stock recovery allows only sideloading via adb

przemcio510 said:
AFAIK stock recovery allows only sideloading via adb
Click to expand...
Click to collapse
Not sure about Oneplus, but we have a Prestigio tablet here and I managed to delete an entire partition from the stock recovery. Wipe data didn't help a bootloop so I actually wiped it for good.
I hope other manufacturers aren't that foolish, but I'm not sure they know better.

Stuck With Secure Start-Up !

Hi Friends,
I setted-up secure start up ( i.e a pattern lock appear when booting the device) when i installed lineage os, but i soon got annoyed with it. My problem is I don't know how to turn it off.
SOLUTIONS tried:-
1. I checked Each and every setting on my phone to turn it off but couldn't found any on lineage os
2.I tried flashing even a different rom , Havoc OS but the secure start up pattern lock still persist
3.when setting up havoc os , i tried disabling it by clicking 'no' when havoc os startup asked to enable secure start up but nothing happened
And Now even my TWRP recovery has a pattern lock due this problem and Wiping my phone didn't solve it.
Any Help PLease????
Solved:
goto>fastboot mode (bootloader)>connect to pc with adb running>type in cmd>fastboot erase userdata

PreciousPulkit said:
Hi Friends,
I setted-up secure start up ( i.e a pattern lock appear when booting the device) when i installed lineage os, but i soon got annoyed with it. My problem is I don't know how to turn it off.
SOLUTIONS tried:-
1. I checked Each and every setting on my phone to turn it off but couldn't found any on lineage os
2.I tried flashing even a different rom , Havoc OS but the secure start up pattern lock still persist
3.when setting up havoc os , i tried disabling it by clicking 'no' when havoc os startup asked to enable secure start up but nothing happened
And Now even my TWRP recovery has a pattern lock due this problem and Wiping my phone didn't solve it.
Any Help PLease????
Click to expand...
Click to collapse
Some people can clear the password by setting a new password and selecting No for secure boot. But that has never worked for me.
See the discussion here https://forum.xda-developers.com/on...ageos-15-1-oneplus-3-3t-t3739169/post76890649
So, try that first and if it doesn't work, the only other option is to reformat the data partition. You'll lose everything in your internal storage, so back it up on external storage.
Sent from my OnePlus3T using XDA Labs

The only way to make it go away is to wipe your phone. Including the internal storage.
I was pissed when I found out.

BillGoss said:
Some people can clear the password by setting a new password and selecting No for secure boot. But that has never worked for me.
See the discussion here https://forum.xda-developers.com/on...ageos-15-1-oneplus-3-3t-t3739169/post76890649
So, try that first and if it doesn't work, the only other option is to reformat the data partition. You'll lose everything in your internal storage, so back it up on external storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Thanks For the reply But I have Tried wiping my phone, everything including internal storage but nothing seems to help. Any other solution?

ast00 said:
The only way to make it go away is to wipe your phone. Including the internal storage.
I was pissed when I found out.
Click to expand...
Click to collapse
Thanks For the reply But I have Tried wiping my phone, everything including internal storage but nothing seems to help. Any other solution?

PreciousPulkit said:
Thanks For the reply But I have Tried wiping my phone, everything including internal storage but nothing seems to help. Any other solution?
Click to expand...
Click to collapse
Plug your phone into a computer, go to bootloader mode and then use cmd to type "fastboot erase userdata".
This should decrypt your device. Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.

ast00 said:
Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
Click to expand...
Click to collapse
But it won't set boot password up on its own though

przemcio510 said:
But it won't set boot password up on its own though
Click to expand...
Click to collapse
True. But I consider encryption itself a curse. There really should be a way to decrypt without wiping the phone.

ast00 said:
True. But I consider encryption itself a curse. There really should be a way to decrypt without wiping the phone.
Click to expand...
Click to collapse
Consider that if you lose your unencrypted phone or it gets stolen, a thief can read your data, access all your accounts and bypass FRP.

przemcio510 said:
Consider that if you lose your unencrypted phone or it gets stolen, a thief can read your data, access all your accounts and bypass FRP.
Click to expand...
Click to collapse
If it's rooted encryption doesn't help. Secure startup does, but it introduces so many problems with simple things like restoring a backup that it's not worth it for me.
And like I said, encryption alone doesn't make a difference as long as you TWRP.

ast00 said:
Secure startup does, but it introduces so many problems with simple things like restoring a backup that it's not worth it for me.
Click to expand...
Click to collapse
Never had such issues
ast00 said:
And like I said, encryption alone doesn't make a difference as long as you TWRP.
Click to expand...
Click to collapse
Actually encryption without secure startup doesn't make sense at all

przemcio510 said:
Never had such issues
Actually encryption without secure startup doesn't make sense at all
Click to expand...
Click to collapse
Which is exactly why forced encryption on every single damn phone is stupid. Ask the user on the first startup if they want this or not. If someone is too stupid to decide this for themselves after a simple, one paragraph explanation, they don't deserve a smartphone.
But the current implementation is unreliable and frustrating to anyone looking to modify the software on their phone. Granted, we are the minority.

ast00 said:
Plug your phone into a computer, go to bootloader mode and then use cmd to type "fastboot erase userdata".
This should decrypt your device. Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
Click to expand...
Click to collapse
Thanks This Worked Very well

ast00 said:
Plug your phone into a computer, go to bootloader mode and then use cmd to type "fastboot erase userdata".
This should decrypt your device. Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
Click to expand...
Click to collapse
Does this mean a Gapps ROM as stock would encrypt it too?

SchwarZWeiSs said:
Does this mean a Gapps ROM as stock would encrypt it too?
Click to expand...
Click to collapse
Not sure what you mean by gapps rom.
Stock Oxygen OS is the only thing that will encrypt it. You can use custom roms based on Oxygen OS though.

ast00 said:
Not sure what you mean by gapps rom.
Stock Oxygen OS is the only thing that will encrypt it. You can use custom roms based on Oxygen OS though.
Click to expand...
Click to collapse
Thanks!

Question Xiaomi Note 11 stuck to rebooting into recovery mode 5.0 after unlocking the screen

Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.

I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...

Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001

asabaraba said:
Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001
Click to expand...
Click to collapse
It's really weird that it happens to other people too!

AdonysGames said:
I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...
Click to expand...
Click to collapse
That might be it since it happens not only to me.

Same problem happening for me too from today. Anyone know a fix for it ?

hrishi654 said:
Same problem happening for me too from today. Anyone know a fix for it ?
Click to expand...
Click to collapse
Did a second data wipe and it worked this time, the phone's been running all night without any issue. I disabled xiaomi updates for the time being

Same issue here, please any solution, I've not been able to do anything since 48 hours

Is there a way to go through this without losing my data and files?

same problem i will try to wipe data again and see if it works

ReaperCat65 said:
Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.
Click to expand...
Click to collapse
I didn't put mine to charge and this happened

mateuszzsa said:
same problem i will try to wipe data again and see if it works
Click to expand...
Click to collapse
Can you give us an update if it works? I also post the problem on Reddit and some people there were also able to fix it by wiping the data.

Will wiping the data fix the issue, if it does, please do let us know

Dr_toluwani said:
Will wiping the data fix the issue, if it does, please do let us know
Click to expand...
Click to collapse
47 minutes since i wiped the data by the second time and my phone its working, I don't know until when.

Does anyone know of way to save the data? Surely it must be accessibl.

ishouldbeworking said:
Does anyone know of way to save the data? Surely it must be accessibl.
Click to expand...
Click to collapse
I found a way to do so. The problem is that once the phone is unlocked you have a few minutes before it gets booted into recovery mode. So:
Step 1) Have the phone connected to a computer before booting it up, with file explorer in the "this pc" category (where the phone storage will appear)
Step 2) boot the phone and input the password (if any)
Step 3) QUICKLY pull down the notification bar and press the usb options notification
Step 4) QUICKLY press the second option for file transferring
Step 5) QUICKLY open phone storage from pc once it pops up (at this point the phone screen will probably be black with a white loading circle but the phone storage is still accessible!!! You now have a few minutes to transfer any data you want)
Step 6) QUICKLY search through phone storage for any important data and copy/paste it to your computer
Sooner or later the phone will be booted to recovery mode and the mi logo will appear and the phone storage will disappear from the computer so repeat above steps until all your data is backed up.
If a file transfer gets stopped while running, copy/paste the data again on the next "run" and choose to ignore files that are already copied. With this method I managed to backup all my photos and files before wiping the phone.

This problem might be due to a problematic firmware update. My phone was running MIUI version 13.0.12(RGKEUXM) (europe version). I wiped the data and updated my phone to version 13.0.13(RGKEUXM) after setting it up just in case. I will update this thread if the problem reappears.

I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.

akallabeth said:
I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.
Click to expand...
Click to collapse
did you try to perform 2 wipes? apparently my device is working properly after that.

mateuszzsa said:
did you try to perform 2 wipes? apparently my device is working properly after that.
Click to expand...
Click to collapse
Which wipe method did you do? Just a factory reset or a reflash?