Database Develop

How To Solve Find Device Storage Corrupted & Couldn't Add Fingerprint -Redmi Note 4X

How To Solve Find Device Storage Corrupted & Couldn't Add Fingerprint -Redmi Note 4X
Hello Everyone,
** I am writing my problem in details if that help you to diagnose my problem, and sorry if my English is not good enough..
I Purchased Redmi Note 4X around two weeks ago. Unfortunately, my device got stolen one week ago, and with the help of MI Cloud, I was able to get it back.
After getting back my phone, I found my device was flashed or reset and locked with MI cloud locker.
Then I flashed my device again with MI PC Suit and Disabled my device on MI cloud.
Since then, I found everything is working fine except following two problems.
Problem One: I am unable to add my fingerprint. Whenever I try to add one I receive following message: "couldn't add Fingerprint, try again." It should be noted here that when I try to add it, I feel 11 vibrations on my phone and see a progress of fingerprint add-on device. The message appears at 12 steps.
Problem Two: I am also getting Following Error message "find device storage corrupted your device is unsafe now error" whenever I try to locate my device through MI cloud > Find Device > Locate Device.
To Solve these problems, I tried following methods But Didn't Work for Me.
1. I made a Factory reset. (Hard & Soft)- Didn't work.
2. I updated Latest Stable Global Rom (System Update Method) - Didn't work.
3. I installed Latest Developer Global Rom ( First Boot Method) - Didn't work.
4. Cleared Wipe Cache Data, Wipe Reset in Xiaomi MIUI 8 through Mi recovery settings. - Didn't work.
** I am from Bangladesh. This device is officially not available here, So no hope for official warranty or support. You guys are my last hope. So please help me.
Any kind of help to resolve the problems will be highly appreciated.
Thanks and Regards

Bhai same problem help me too.. Plz

Install TWRP from this link, when it asking password, press CANCEL.
Then wipe DATA, that's your factory reset

I have same problem .... Would u get any solution ?? If yes then tell me ...plz

Bro Just Unlocked bootloader .
And Flash Twrp .
And Use any custom rom
Your fingerprint will work fine .
All sensor to......

as long as the bootloader is unlocked, those features are disabled and/or you get those error messages. Reason is that the fingerprint has to be saved somewhere. Unlocking the bootloader gives people access to that storage (after all, you can get root access). The device is "unsafe" because of the unlocked state. Go to settings -> additional settings and look if the developer settings are available. There you can check if your device is unlocked.

I have installed miui 9 custom room I my lava pixel V2 and after few days my phone start rebooting it self when download a gamer or other help need

I have the same problem not able to use wifi on my redmi 4x even i have tried fastboot rom flash but not working on custom rom its working fine i dont know why.

Couldn't verify. Wait a minute or two

Hi, im not a really new user of santoni. But i have being frustated because that i cant unlock my device bootloader since last year. The main problem seems i cant bound/add my device into settings-development-mi unlock status, it always say COULDNT VERIFY. WAIT A MINUTE OR TWO. So when i insist to unlock it via mi unlock tools, it always fails at 99% and say CURRENT ACCOUNT NOT BOUND... i have my unlock permission since january. And i think, for now, unlock permission didnt required anymore
I have tried to enable find device, remove account, reset, recovery flash update. accessing i.mi.com
i have searching all around websites
but no luck.
Im using stable latest ROM 9.5.10.0 NAMMIFD nougat 7.1.2
Really, i want to migrate into dev version. Or even a custom ROM such as LOS or else.
miflash tools are useless because my device still locked. I cant do more.
Really, i need help from this forum to figure it out. Maybe there are people that having problem same as me. :crying:
PS : My fingerprint doesnt work too. it said couldnt add fingerprint, and sometimes a small pop up shown said : FIND DEVICE STORAGE CORRUPTED. YOUR DEVICE UNSAFE NOW. i think its because at the first time i having this, im bypassing micloud. ( I buy this phone secondhand. And previous owner seems forgot to sign out and reset this device. so i try to bypass micloud screen ) since that, the issues and popup come. IPlease help me

Phone doesnt register z axis gyroscope reading - compass spins erratically

Hey!
Ive been noticing an issue with my device, since I think the update to MIUI 11 (but not sure).
Description:
- The compass (and other apps using compass like Google maps) gives incorrect readings, when put horizontally. When put horizontally and kept still, the compass will spin regularly ca 2 degrees per second completely independent from the actual pointing direction. When the phone is kept vertically the compass works normally. I have made a video displaying the correct reading when vertically, and the spinning when kept horizontally: https://youtu.be/xgC4fHqH4Ys
- When checking the underlying gyroscope functionality with "Sensor Multitool", I have come across what I think is an erratic z axis reading. When I spin the phone randomly, the gyroscope in the x and y axis registers adequate readings, but the z axis stays completely flat. I have produced a video showing this behavior: https://youtu.be/1dY_xdF5Nz8
I have found this thread from Aliosa007 ( https://forum.xda-developers.com/showthread.php?t=3972249 ) that describes a very similar issue, but this user had recently flashed a new rom and the problem is attributed with the flashing. The users there assume the issue being a corrupt persist.img and most problem solving techniques involve flashing etc. But my phone is locked and not rooted. Could I also have received a corrupt persist.img during the normal update process recently to MIUI 11.
Currently trying to figure out, what the best way forward is. Wait and hope that this will be fixed with the next update or go the warranty route?
Thanks for helping me out with this one!

Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.

Tistou52 said:
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Click to expand...
Click to collapse
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda

schnodda123 said:
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
Click to expand...
Click to collapse
Hey,
well I couldn't really tell if it's related to an update : I got my mi 9T pro like two or three weeks ago and updated to 11.0.3 the day I got it...
The weird thing is that I noticed the problem one first time, and then two or three days later the issue solved itself without me doing anything particular and my compass started working normally again... And then two or three days ago it started spinning continuously again... I just hope it's software related and not an hardware issue...
I think I'm just going to wait for the next system update and if doesn't solve the problem I may send the phone back (but I don't wanna ... The phone otherwise is so great...).
I'll update the thread if I find something.
Good luck

Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.

hoopsnake said:
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
Click to expand...
Click to collapse
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!

schnodda123 said:
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
Click to expand...
Click to collapse
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you

hoopsnake said:
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
Click to expand...
Click to collapse
Sorry sir, but i think you cannot flash persist.img thru fastboot, because it read-only partition ,

I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?

Tistou52 said:
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Click to expand...
Click to collapse
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.

schnodda123 said:
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
Click to expand...
Click to collapse
Hola @schnodda123, ¿Logaste darle solución? No he podido arreglar mi eje z en mi caso en un Redmi Note 8, estoy algo incomodo, si bien el celular funciona bien el tener el sensor mal es fastidioso
Hi @ schnodda123, Did you manage to give it a solution? I have not been able to fix my z axis in my case on a Redmi Note 8, I am somewhat uncomfortable, although the cell phone works well, having the wrong sensor is annoying

Bypass FRP Google protection

Hi i'm another victim of xiaomi mi 8 issue (no WiFi, no SIM detected, and random reboots), not find a solution yet but still hope!
Unfortunatly when i reset the phone i was logged with google account and now, so i'm stucked in 'chose language' 'chose region', ecc. because without any connection i can't log in google account.
how can i bypass frp protection at least i can use my phone for photos, because the one i have now for replace is not so good camera as mi 8
MIUI 10
Android 9
Unlocked bootloader
i can also downgrade to older version of this with fastboot ROMs, just at least want my camera back!
So i have to bypass frp throught fastboot or with something in twrp, i don't know

Go check the persist thread, again. I was able to solve the persist issue

What/Where is the persist thread?

Hard bricked

Yesterday updated to Android 10 and all were ok until I decided to fix the broken fp.. With stock recovery i tried through adb to lock bootloader. That's it.. Now phone only vibrate every 2 secs with Realme logo appeared and disappeared. I can't enter on recovery or bootloader. I tried all button combinations with no luck. I think that the only solution is to visit a technical center. :crying:

The CN version is like this. Fingerprint can be used to unlock the BL lock phone. However, C7 should pay special attention to the fact that root and fingerprints cannot coexist. It should be officially added verification. Fingerprints are disabled when root is detected. It is said that the official detection of root is not very accurate. After all, magisk is still very powerful, everything is normal when entering the system, and C7 does not need a patch to close magisk core mode like C6. C7 safetyNet checks are also true. So how does the official know? Because the current magisk solution uses boot.img, that is to say, as long as it is not the original boot, the fingerprint will be disabled.
******** The above is only a personal guess.

Goddamn Similar Issue
Realme should've shared this important information about being stuck at bootloop when locking bootloader. Fed up of trying all the button and still no response. Had to wait for the service centre to be opened. Don't know when this will be fixed. XDA developers. you're the only one who'd be having any solution to this milisecond boot loop on realme x2 pro.. Didn't flashed any rom, just tried perfectly all step to lock bootloader. I hope xda developers guys might've the solution to this. Also unable to boot to fastboot nor to any recovery mode.

Had no issues on C23 with locking BL with stock recovery.
First thing I did was resetting the phone and then locking BL.

tidschi said:
Had no issues on C23 with locking BL with stock recovery.
First thing I did was resetting the phone and then locking BL.
Click to expand...
Click to collapse
Any help on what I can do to turn on my device??

EdoKai's Realme X2 Pro said:
Realme should've shared this important information about being stuck at bootloop when locking bootloader. Fed up of trying all the button and still no response. Had to wait for the service centre to be opened. Don't know when this will be fixed. XDA developers. you're the only one who'd be having any solution to this milisecond boot loop on realme x2 pro.. Didn't flashed any rom, just tried perfectly all step to lock bootloader. I hope xda developers guys might've the solution to this. Also unable to boot to fastboot nor to any recovery mode.
Click to expand...
Click to collapse
Did you contact realme Service Center What did they say ? i Have the exact same issue please help

Only realme service centre can help you.