Related
hello i'm mi 5s 4gb/128gb user
yesterday, i was using cyanogenmod 13 but i want to use miui again
so i restored nendroid backup from twrp recovery
that was start of diaster..
after this. fingerprint scanner mostly doesn't work
sometimes fingerprint scanner work correctly after reboot, it doesn't work.. and sometimes... it works...
i did many many method (global rom, china rom via edl mode, fastboot mode) but everything has same result,
so i looked at my logcat
it says
QFP : QfpThreadMatch::execute: match result -3: QFP_INSUFFICIENT_COVERAGE
with my finger or not logcat said same result
why my fingerprint scanner doesn't work?
is it hardware issue?
sorry for poor english
yesterday, i was using cyanogenmod 13.......is it hardware issue? .......
jlmcr87 said:
yesterday, i was using cyanogenmod 13.......is it hardware issue? .......
Click to expand...
Click to collapse
???
Maybe placebo effect but people are saying Global rom had improved fingertip detection rate.
If i were you, i would flash as stock as possible, recovery, bootloader, lock status, everything, just to determine software versus hardware failure.
Hope for the best, as this kind of life cycle premature failure freak me out, first stucked autofocus sensor now this!!!
jpg3927 said:
???
Click to expand...
Click to collapse
You change the software and then ask if it´s hardware?
jlmcr87 said:
You change the software and then ask if it´s hardware?
Click to expand...
Click to collapse
yes it's strange
jpg3927 said:
yes it's strange
Click to expand...
Click to collapse
I had a problem which seemed to be hardware related after flashing the Chinese developer ROM and then later restoring a Miui EU ROM from a backup. My problem was with audio - there was no sound coming from the speaker or headphone output. I did diagnostic tests which failed - indicating a hardware problem.
It was only after re flashing the EU Miui ROM that the problem was resolved.
EpicSauce said:
I had a problem which seemed to be hardware related after flashing the Chinese developer ROM and then later restoring a Miui EU ROM from a backup. My problem was with audio - there was no sound coming from the speaker or headphone output. I did diagnostic tests which failed - indicating a hardware problem.
It was only after re flashing the EU Miui ROM that the problem was resolved.
Click to expand...
Click to collapse
i solved it
i think this was problem of driver
so i needed rollback of driver
first. i flashed 6.10.13 eu rom over 6.12.29
it occurs bootloop
second. i flashed 6.12.29 over 6.10.13 again. and fingerprint works like charm again!
Exists the cyanogenmod for Mi5s?
Still very buggy. We have to wait for xiaomi to release the source code to get nice CM .
The fingerprint happened to me too, it just stopped working.
Flash the stable global using fastboot, it will erase everything, and will be great again.
Don't restore with Titanium backup, I had all kind of weird problems everytime I tried.
One of the worst fp sensors ever. I tried all the tricks mentioned in several places, detection rate stays very low.
Sent from my MI 5s using Tapatalk
LucaOwner said:
Exists the cyanogenmod for Mi5s?
Click to expand...
Click to collapse
Linage os
Help ! My fingerprint scanner suddenly not working, it shows“ fingerprint hardware not available” , wipe cache and reflash rom already, but still doesn't work. Anyone has the same issue or face this issue before ? Pls help , I'm in oxygen os beta 11 with elemental x kernel
Ocean Fong said:
Help ! My fingerprint scanner suddenly not working, it shows“ fingerprint hardware not available” , wipe cache and reflash rom already, but still doesn't work. Anyone has the same issue or face this issue before ? Pls help , I'm in oxygen os beta 11 with elemental x kernel
Click to expand...
Click to collapse
Flash a full stock ROM zip, with the included firmware. If that doesn't work then send it off to OnePlus.
Ocean Fong said:
Help ! My fingerprint scanner suddenly not working, it shows“ fingerprint hardware not available” , wipe cache and reflash rom already, but still doesn't work. Anyone has the same issue or face this issue before ? Pls help , I'm in oxygen os beta 11 with elemental x kernel
Click to expand...
Click to collapse
Go to Settings and register a new fingerprint ?
Reflash full stock if still doesn't work It's a hardware problem and needs RMA'd
liam_davenport said:
Reflash full stock if still doesn't work It's a hardware problem and needs RMA'd
Click to expand...
Click to collapse
I go to the dialer app and type *#808# , and to the fingerprint test , passed , but still not working . I can press the sensor to go to home but fingerprint sensor not working ? Maybe a software issue ?
Ocean Fong said:
I go to the dialer app and type *#808# , and to the fingerprint test , passed , but still not working . I can press the sensor to go to home but fingerprint sensor not working ? Maybe a software issue ?
Click to expand...
Click to collapse
Have you flashed full stock and the issue is still there?
You need to flash 3.2.8 official version. It wilk bring back your fingerprint sensor.
Have you registered a new fingerprint in settings?
liam_davenport said:
Have you flashed full stock and the issue is still there?
Click to expand...
Click to collapse
Yes tried already
Perseus09 said:
You need to flash 3.2.8 official version. It wilk bring back your fingerprint sensor.
Click to expand...
Click to collapse
This will wipe all my data right ? Any other ways ?
rob rich said:
Have you registered a new fingerprint in settings?
Click to expand...
Click to collapse
Nope , can't even do that
Same Issue with me
I am also facing the same issue. Done everything I guess what I have seen over the internet but, still it saying fingerprint hardware is not available. What to do bro please help me if your issue has been solved
Guys do a full clean install. Somehow something is messed up. Try the unbrick guide it will reset your phone fully from then you should upgrade to the latest version of OOS and then if everything is working consider a custom rom.
Good evening together,
I have opened a new topic so that we can do everything together regarding a fix for the fingerprinter.
This is known to be broken when we open the bootloader.
I really hope that together we can find out how we can fix this.
I once looked at all files between de Realme X and the X2.
Unfortunately, I have almost no discernible differences.
Thus, the fix of Realme for the X might also be in the bootloader itself.
Where Widevine is still set from L1 to L3.
Maybe you have an idea?
Up for this topic.
Try to fix fingerprint. Its available only for a17 ROM.
Flash in twrp or unpack and replace files by hands.
also may be need wipe dalvik-cashe.
Fingerprint FIX
djsven said:
Good evening together,
I have opened a new topic so that we can do everything together regarding a fix for the fingerprinter.
This is known to be broken when we open the bootloader.
I really hope that together we can find out how we can fix this.
I once looked at all files between de Realme X and the X2.
Unfortunately, I have almost no discernible differences.
Thus, the fix of Realme for the X might also be in the bootloader itself.
Where Widevine is still set from L1 to L3.
Maybe you have an idea?
Click to expand...
Click to collapse
after update to version V.13 Fp working with boot-loader unlocked ...
amit000in said:
after update to version V.13 Fp working with boot-loader unlocked ...
Click to expand...
Click to collapse
without fix? and what about security certifications instead?
UPDATE:
temblor55 has made a Magisk patch for this problem, which he posted on 18 september::
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Pat57 has confirmed that it works for him.
________________________________________________________________________________________________________
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Elinx said:
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Click to expand...
Click to collapse
I had similar problem, but i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it (or if you already have a recovery backup of persist just restore it)
loopypalm said:
.... i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it .....
Click to expand...
Click to collapse
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Elinx said:
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Click to expand...
Click to collapse
yes, on paper the problem sounds like it has nothing to do with persist
but as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
loopypalm said:
...... as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
Click to expand...
Click to collapse
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Elinx said:
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Click to expand...
Click to collapse
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
loopypalm said:
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
Click to expand...
Click to collapse
Ok I will try after backup
Which RN8 batch have you? Which camera didn't work?
Elinx said:
Which RN8 batch have you? Which camera didn't work?
Click to expand...
Click to collapse
what do you mean by batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
loopypalm said:
... batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
Click to expand...
Click to collapse
The batch date 11-2020 is the phone with problems.
First the problem with FW 12.01. This is the only phone that can't be flashed with that version. If you did with twrp, you had a brick.
Second the HW change of the selficam. I have seen I'm not the only one with Andoid Q "not connecting" to this specific cam.
On LOS 17 topic a saw there is a formel bug report published about this issue
I can use all other cams without problems. The error is only with selfiecam and A10. Not with Miui and not with A11.
That is why I think of a missing driver.
I read something about adding missing drivers, but think it isn't easy.
Also I understand that the vendor image contains the hardware drivers.
So trying kernels only hasn't influence on HW changes
I can imagine that A11 custom uses also later vendor images, that's why these roms work with selficam.
Next question would be.
Are vendor images for Ginkgo intechangable?
Elinx said:
That is why I think of a missing driver.
Click to expand...
Click to collapse
have you tried A10 latest stable FW ? (it has updated drivers in it)
Elinx said:
Are vendor images for Ginkgo intechangable?
Click to expand...
Click to collapse
as far as i tested(A10), they are all almost the same, except for some roms have some carrier overlays and BT in it and other have them in system
also audio mods and enhancement, some roms have it and other don't
loopypalm said:
have you tried A10 latest stable FW ?....
...
as far as i tested(A10), they are all almost the same, except for some roms ...
Click to expand...
Click to collapse
Yes I have the latest stable FW. First I thought that these contains the HW drivers.
But reading, I learned that with latest Android versions all drivers are inside vendor image.
That is why updating FW and kernel doesn't make any difference for RR.
Because of all brick/EDL troubles I'm being carefull what I flash.
I have made for now a twrp backup of vendor and efs partition.
The persist parttion must be backup with adb or terminal
My phone is still an empty phone so I can format data and so on.
I saw that Miui vendor files are downloadable.
The latest Global is 11.0.11
Elinx said:
The persist parttion must be backup with adb or terminal
Click to expand...
Click to collapse
use also recovery (you never know) ...
Elinx said:
I saw that Miui vendor files are downloadable.
Click to expand...
Click to collapse
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
you can wipe everything and flash rr since your data is not important
loopypalm said:
.....
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
...
Click to expand...
Click to collapse
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Elinx said:
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Click to expand...
Click to collapse
i flashed a rom (Don't remember the name) and i did a mess in vendor ,so instead of reflashing, i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
of course error like app x stopped working popped off,so this is not a fix
this is just a crazy suggestion to test the compatibility of the drivers
also test this cam :
ɬɧɛ Ɩųŋąɬıƈ in Dtuxed Roms Public Group
t.me
it has updated libs
maybe it will work
loopypalm said:
...., i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
.....
maybe it will work
Click to expand...
Click to collapse
Ok you flashed vendor.img with twrp
The download link is Miui camera.
There where no HW drivers inside
I already found also such a zip with libs, but without result
It is for improving camera results
Elinx said:
There where no HW drivers inside
Click to expand...
Click to collapse
i made a mistake in the zip
the cam that i wanted to give you is in the same group
i will see if i can find it
Try this bro
Thank you, I surely want to try this Magisk mod file, but the file isn't accessible without requist.
Maybe you have your reasons for that, but in that case it isn't possible to download.
I have tried to comment this with the video too, but you have disabled comments there.
temblor55 said:
Try this bro
Click to expand...
Click to collapse
temblor55 you forgot to make the file public
Sorry guy's made it public now
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Hi, All
These are some issues that currently facing with Oxygen OS on Chinese Variant LE2120
1. Getting NV Backup Warning - Invalid VIP NVs:2500
Tried Backing and Restoring NV Backup Data, But Not Working
2. Phone Freezes Randomly
3. Google Play System Cannot be Updated
Google Play System Update Section is Totally Missing
4. Camera App Freezes Randomly
5. Settings - About Page - Verification Section is Missing
Aathif Mahir said:
Hi, All
These are some issues that currently facing with Oxygen OS on Chinese Variant LE2120
1. Getting NV Backup Warning - Invalid VIP NVs:2500
Tried Backing and Restoring NV Backup Data, But Not Working
2. Phone Freezes Randomly
3. Google Play System Cannot be Updated
Google Play System Update Section is Totally Missing
4. Camera App Freezes Randomly
5. Settings - About Page - Verification Section is Missing
Click to expand...
Click to collapse
Hello! What hardware number do you have?
kezz93 said:
Hello! What hardware number do you have?
Click to expand...
Click to collapse
Hardware Number Means? Model No is LE2120
Aathif Mahir said:
Hardware Number Means? Model No is LE2120
Click to expand...
Click to collapse
I mean build number
Aathif Mahir said:
Hi, All
These are some issues that currently facing with Oxygen OS on Chinese Variant LE2120
1. Getting NV Backup Warning - Invalid VIP NVs:2500
Tried Backing and Restoring NV Backup Data, But Not Working
2. Phone Freezes Randomly
3. Google Play System Cannot be Updated
Google Play System Update Section is Totally Missing
4. Camera App Freezes Randomly
5. Settings - About Page - Verification Section is Missing
Click to expand...
Click to collapse
@Aathif Mahir you do know the Chinese gov. Doesn't allow phones to be sold with google and play services. I would download oxygen updater and update to global or eu. I'm on eu and have the same model as you. If you don't know how to local update pm me and I will walk you through it
toolhas4degrees said:
@Aathif Mahir you do know the Chinese gov. Doesn't allow phones to be sold with google and play services. I would download oxygen updater and update to global or eu. I'm on eu and have the same model as you. If you don't know how to local update pm me and I will walk you through it
Click to expand...
Click to collapse
Do you experience the issues that i shared above?
kezz93 said:
I mean build number
Click to expand...
Click to collapse
Here’s the build number, Oxygen OS 11.2.4.4LE15DA
Aathif Mahir said:
Do you experience the issues that i shared above?
Click to expand...
Click to collapse
No
toolhas4degrees said:
No
Click to expand...
Click to collapse
Can you share me screenshot of NV Pararmeters
instructions
- *#268# - Nv Parameters
Aathif Mahir said:
Can you share me screenshot of NV Pararmeters
instructions
- *#268# - Nv Parameters
Click to expand...
Click to collapse
Idk know about nv parameters, all the other issues you are having, I'm not
yes I have faced this issue during the Teas Exam Taker........but don't worry it will be setteled
toolhas4degrees said:
Idk know about nv parameters, all the other issues you are having, I'm not
Click to expand...
Click to collapse
can we see the screenshot of your about phone section?
I also have empty verification section on the about us phone. Other than that all good. Im on EU build on the Chinese variant
Aathif Mahir said:
Hi, All
These are some issues that currently facing with Oxygen OS on Chinese Variant LE2120
1. Getting NV Backup Warning - Invalid VIP NVs:2500
Tried Backing and Restoring NV Backup Data, But Not Working
2. Phone Freezes Randomly
3. Google Play System Cannot be Updated
Google Play System Update Section is Totally Missing
4. Camera App Freezes Randomly
5. Settings - About Page - Verification Section is Missing
Click to expand...
Click to collapse
i have this same issue, can u please guide how to fix it ? i even did factory reset and i still have the same error
Alminaaz said:
i have this same issue, can u please guide how to fix it ? i even did factory reset and i still have the same error
Click to expand...
Click to collapse
Why don't you just press "never show"? It's normal as region is different and backup app (only for debugging) can't handle it
Butnit would be better if its not present
Aathif Mahir said:
Here’s the build number, Oxygen OS 11.2.4.4LE15DA
Click to expand...
Click to collapse
now Oxygen OS 11.2.5.5LE15DA is available please update than check again
Hello,
I have the same issue, with the same model, I have updated with the new build Oxygen OS 11.2.4.4LE15DA, but still have the message.
Same problem here. Any solution?