Related
Hi guys,
about a week ago my rooted P9 with Lineage 14.1 crashed and was stuck in the boot screen for hours. I waited until it completely discharged and tried rebooting again but that didn't help either. The only way I could resolve this was to boot to recovery (TWRP) via fastboot and do a factory reset. After that it worked just fine except for setting up fingerprints.
In the settings menu there were no fingerprints set up and I couldn't register fingerprints from the fingers I previously had registered, but I could add a fingerprint I haven't used before. After that, however, all the old fingerprints still worked to unlock the phone even if they don't show up in the settings menu.
Do you know where these old fingerprints are stored and how to delete them manually?
Thanks for the help!
Suggesting to report custom ROM issues under the corresponding custom ROM threads - higher chance that somebody who is familiar with the particular custom ROM can spot and help
zgfg said:
Suggesting to report custom ROM issues under the corresponding custom ROM threads - higher chance that somebody who is familiar with the particular custom ROM can spot and help
Click to expand...
Click to collapse
Thanks, I'll try that.
Hello, I flashed my mi8 like I do every week.
This week I flashed the xiaomi.eu weekly rom, used it for 10hours, then my phone randomly restarted, and now it don't detect SIM cards and don't turn on WIFI, and the phone restart every X minutes.
I think the persist partition has gone. I can't find it on TWRP.
Any help?
Thank you
eRvY said:
Hello, I flashed my mi8 like I do every week.
This week I flashed the xiaomi.eu weekly rom, used it for 10hours, then my phone randomly restarted, and now it don't detect SIM cards and don't turn on WIFI, and the phone restart every X minutes.
I think the persist partition has gone. I can't find it on TWRP.
Any help?
Thank you
Click to expand...
Click to collapse
Which TWRP did you use?
alone_in_dark said:
Which TWRP did you use?
Click to expand...
Click to collapse
I used the same I ever used, but a very old one? Do you think it's related to twrp?
eRvY said:
I used the same I ever used, but a very old one? Do you think it's related to twrp?
Click to expand...
Click to collapse
Follow his posts:
https://forum.xda-developers.com/search.php?searchid=461808923
Hope it might help you.
eRvY said:
I used the same I ever used, but a very old one? Do you think it's related to twrp?
Click to expand...
Click to collapse
Have you solved your problem? Can you please tell which TWRP were you using specifically?
alone_in_dark said:
Follow his posts:
https://forum.xda-developers.com/search.php?searchid=461808923
Hope it might help you.
Click to expand...
Click to collapse
i cant find that post?
I have the same problem.
Have you tried installing all possible ROMs nothing resoved?
Does anyone have a solution?
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
I'm having the same issues, I'm running the latest official TWRP. The thread you linked won't open.
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
Not solved ..
Anyone with a solution ??
Are you guys having the same issues as I?
Phone boot, don't detect SIM or Wifi, and reboot after 3-5mins?
Anyone find the solution?
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
eRvY said:
Are you guys having the same issues as I?
Phone boot, don't detect SIM or Wifi, and reboot after 3-5mins?
Anyone find the solution?
Click to expand...
Click to collapse
not yet, and I think it will be difficult,
but so many people with the same problem xiaomi will have to solve ..
Everyone should ask xiaomi support I already made my request I'm waiting for response.
sk3lt said:
not yet, and I think it will be difficult,
but so many people with the same problem xiaomi will have to solve ..
Everyone should ask xiaomi support I already made my request I'm waiting for response.
Click to expand...
Click to collapse
I sent my phone to checked by a professional, because it fell from the couch in the afternoon, and everything is working, no shorts.
Now I was almost 100% that the 19/12/2019 update ****ed my phone.
I already bought a realme x2 , because this is my 2nd xiaomi that die out of nowhere, the last one was a Mi4, random shutted down, and never went back to life.
Is your Mi8 chinese or globa versionl?
Mine is chinese
Same problem (global version). Did you fix It?
Hey guys, im from brazil and have same problem, anybody have a help?
Im trying unlock my fastboot for downgrade rom.
I found a fix, remove SIM card, wait 10 seconds, power off phone, put SIM cards back inside and boot the phone
tmcsword said:
Hey guys, im from brazil and have same problem, anybody have a help?
Im trying unlock my fastboot for downgrade rom.
Click to expand...
Click to collapse
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
tsongming said:
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
Dear look, my fastboot is locked, for install twrp ( do you have some instruction for instal TWRP ? ) I think the bootloader need be unlocked, sure?
Thanks for try help me.
tmcsword said:
Dear look, my fastboot is locked, for install twrp ( do you have some instruction for instal TWRP ? ) I think the bootloader need be unlocked, sure?
Thanks for try help me.
Click to expand...
Click to collapse
If you are meaning that your bootloader is locked then the only option ( if your phone is linked to your MiCloud account) Is to return to a stock rom using Miflash or by downloading a fast boot images rom and using the flash all.bat method. The link that I provided earlier has a fast boot images rom linked.
Clarify whether or not you can access fastboot. If you can in fact access fast boot, and you previously used custom ROMs the instructions for installing TWRP are on the official TWRP website. You simply use ADB to push it yo the recovery partition.
tsongming said:
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hey whats up man,I hope u still answers questions I really hope you do because I'm in a dire situation where is my xiaomi mi8 cant connect to my sim card .It all started this year after a use of this phone since 2019 january.After my trip overseas , I got my own national sim card in again after that it occurs the problem at first was not that consistent,sometimes it detects, sometimes its good,after a while I thought that the sim card is loose so I wedged the simcard with a bit of paper,about sometime it works and then it starts to overheat when it doesn't detect the sim card inside and starts to reboot on its own, if I remove my simcard,its all good I can use wifi without overheating,how can I actually solve this problem? i quite believe that mi account /micloud that is causing all of this? whats your opinion on this? Im not an expert at all.Thanks for your time of reading this
Hello, guys! After installing the latest update on my Galaxy A6 (A600FN) the touch screen stopped working. I tried flashing all 3 ROMs for my region that had the version 5 bootloader with Odin and none of them fixed the issue. One of them was Android 10 and 2 were Android 9. ROMs with an older version of the bootloader would fail the flash because apparently you can't downgrade it. It shows this error: Sw rev. Check fail. Device: 5, binary 3. I'm certain it's not a hardware issue because I had this happen on 2 A6 devices right after the update. I thought of trying a custom ROM but I can't find one for A6, only A6+. What can I do here? Can I trick it somehow to downgrade it? Is there some command I can send through adb shell to fix the touchscreen? Any help would be greatly appreciated!
BTW, I can access the device via a USB OTG mouse and it works perfectly fine.
Bump. Please, any help is appreciated!
Do you tried factory reset from recovery?
Zevnor said:
Do you tried factory reset from recovery?
Click to expand...
Click to collapse
That was the first thing I tried. Didn't help.
robert335 said:
That was the first thing I tried. Didn't help.
Click to expand...
Click to collapse
Is your phone carrier-branded? If yes, try to flash unbranded firmware.
I managed to fix it, will update this post soon with how I did it.
robert335 said:
I managed to fix it, will update this post soon with how I did it.
Click to expand...
Click to collapse
HI, if you have a solution to this problem can you share it please? I have the same phone with the same issue .
barthab said:
HI, if you have a solution to this problem can you share it please? I have the same phone with the same issue .
Click to expand...
Click to collapse
First make sure you aren't RMM locked: https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Then get yourself TWRP: https://forum.xda-developers.com/galaxy-a6/development/recovery-twrp-3-2-2-0-galaxy-a6-t3819741
Afterwards, I installed this custom ROM which is pretty close to stock Pie: https://forum.xda-developers.com/galaxy-a6/development/rom-pa6-rom-a6-t3943573
Maybe you can try this one too, I haven't tried it: https://forum.xda-developers.com/galaxy-a6/development/phonezippy-microrom-t4083579
After installing the ROM, make sure to install "no-verity-opt-encrypt" and "RMM Bypass v3". This is VERY IMPORTANT, otherwise your device will become RMM locked and brick itself until you flash stock firmware again.
I fixed both of my phones but looks like I messed up on one and after I restarted it had RMM state Prenormal. Does anyone know how to fix this? OEM is unlocked in developer settings but flashing twrp from Odin yields "only official binaries are allowed"...
Has anyone experienced something like this? It’s happening on my Xiaomi K20 Pro after I just updated it to MIUI 12 directly from the settings app
here's a video: youtu.be/ Mv-Qbgb0rR8 (I don't know where else to post this video, but I'm not allowed to post links)
Just in case the video wasn’t very clear, basically when I try to boot everything seems to boot fine to the lock screen, but if I try to unlock the phone with my pin it will just go back to the boot screen again, if I click on the emergency button it also does the same thing and if I just wait a little bit the same thing happens too.
It kinda reminds me of that wallpaper bug that bricked people’s phones, but I didn’t have any problems in MIUI 11 and my wallpaper is from the Google wallpaper app so I don’t expect that to be the problem.
I think it might be because my phone is running the international/global Rom instead of the original rom? I bought this phone used, and the software is saying that its a Mi 9T Pro instead of K20 Pro.
Can someone help me solve this? Or would I need to just factory reset? The phone is also already unlocked, so I was able to back everything up via a custom recovery, but reinstalling and setting everything back up again is just going to take a while, so maybe someone can help?
Maybe I could do something from the custom recovery (currently using orangefox recovery) to save this? I really don't want to factory reset
yes i am facing the same issue
At this point I wouldn't hold much hope on avoiding a clean install.
If you can access the data OK in TWRP/OF, I would suggest backing up your personal data, then try the following.
Dirty flash the MIUI 12 recovery ROM again.
If that fails, clean flash the MIUI 12 recovery ROM.
If that fails, clean flash the MIUI 12 fastboot ROM.
Personally myself, I would go straight to flashing the fastboot ROM, as it's the option almost guaranteed to work.
You can also try to factory reset your phone. Do you have TWRP?
M.isa said:
Has anyone experienced something like this? It’s happening on my Xiaomi K20 Pro after I just updated it to MIUI 12 directly from the settings app
here's a video: youtu.be/ Mv-Qbgb0rR8 (I don't know where else to post this video, but I'm not allowed to post links)
Just in case the video wasn’t very clear, basically when I try to boot everything seems to boot fine to the lock screen, but if I try to unlock the phone with my pin it will just go back to the boot screen again, if I click on the emergency button it also does the same thing and if I just wait a little bit the same thing happens too.
It kinda reminds me of that wallpaper bug that bricked people’s phones, but I didn’t have any problems in MIUI 11 and my wallpaper is from the Google wallpaper app so I don’t expect that to be the problem.
I think it might be because my phone is running the international/global Rom instead of the original rom? I bought this phone used, and the software is saying that its a Mi 9T Pro instead of K20 Pro.
Can someone help me solve this? Or would I need to just factory reset? The phone is also already unlocked, so I was able to back everything up via a custom recovery, but reinstalling and setting everything back up again is just going to take a while, so maybe someone can help?
Maybe I could do something from the custom recovery (currently using orangefox recovery) to save this? I really don't want to factory reset
Click to expand...
Click to collapse
Facing the same issue now. How did you solve it? I also have the Google wallpaper and just updated
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
baleskoil said:
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
Click to expand...
Click to collapse
Did you find a solution?
Nope
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
baleskoil said:
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
Click to expand...
Click to collapse
As of right now me and you are the only two that seem to have this issue.when I get home from work I'm going to go ahead and I'm actually going to relock my bootloader and and do everything and then I'm going to unlock it and see what happens.I can let you know in this thread if it works for me and that way you don't have to waste your time unlocking and relocking
Yes please
i would say lock and unlock again and just install everything again
baleskoil said:
Yes please
Click to expand...
Click to collapse
So i locked the bootloader ,then unlocked it and did a fresh install of 11 and i have face unlock back
Good .
I need to reflash the Factory image before relocking right ?
To be safe
baleskoil said:
Good .
I need to reflash the Factory image before relocking right ?
To be safe
Click to expand...
Click to collapse
I locked the bootloader then rebooted back into the boot loader and unlocked it and then flashed
Works for me too.
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
neo_lithic3K said:
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
Click to expand...
Click to collapse
I tried that and it's a no go. Looks like bootloader is the way for now.
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
seipersei said:
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
Click to expand...
Click to collapse
I had the exact same problem as you. face unlock became unreliable after the Android 11 upgrade, so I deleted face data and tried to set up again. It keeps saying 'fit face into frame' no matter the angle or the lighting. Did a factory reset and no improvement. I have never rooted or unlocked the bootloader on this phone. I informed google support and they are sending me a replacement.
Just to share an experience with the community: After android 11 update I was having glitches with face unlock. (Totally stock, no root & all latest ota) This got worse until it wouldn't work at all. Deleting face & starting over didn't work as it just refused to even acknowledge trying to register anything. Then the auto brightness starting flicking up and down and finally half the screen disappeared under green flickering. A factory hard reset made no difference. I even did it twice but the welcome screen on rebooting was still covered in green flickering. Searching for a new phone reluctantly. I picked up my pixel 4xl again to see if I could think of a way of selling it for any purpose & it was fine! Set up & reinstalled a backup & everything including face unlock works perfectly like new. What was all that about!?
Can you describe full algorithm for noob, please?
Stiil don`t working
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
I've done relocking bootloader, but it didn`t help, face unlock still not working, OC is stock, latest.
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
kingkong0821 said:
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
Click to expand...
Click to collapse
This is a known problem, and so far Google has not fixed it. Unsure if they ever will.
Sent from my Pixel 4 XL using Tapatalk