As the title says, I have a Goodix fingerprint sensor, and I've tried all of the methods I could find but none of them works, at least perfectly. In some cases where I applied the patch and used a custom kernel, it kinda works, but very inconsistently.
Further explanation: It only detects my finger about 20% of the time I touch it during the fingerprint setup. Even when it does detect it, sometimes it says "Couldn't process fingerprint. Please try again." After successfully setting up a fingerprint, the phone soft reboots, and then later when I try to unlock it using fingerprint, it doesn't work. Adding more fingerprints does not help in anyway, neither is deleting them.
EDIT: Only with custom ROMs, with MIUI it works fine. Sorry for the misunderstandings.
are you sure, you have goodix version?
ASDFking said:
As the title says, I have a Goodix fingerprint sensor, and I've tried all of the methods I could find but none of them works, at least perfectly. In some cases where I applied the patch and used a custom kernel, it kinda works, but very inconsistently.
Further explanation: It only detects my finger about 20% of the time I touch it during the fingerprint setup. Even when it does detect it, sometimes it says "Couldn't process fingerprint. Please try again." After successfully setting up a fingerprint, the phone soft reboots, and then later when I try to unlock it using fingerprint, it doesn't work. Adding more fingerprints does not help in anyway, neither is deleting them.
Click to expand...
Click to collapse
test on aida64 and we will see what your fingerprint :silly:
pumpkins12 said:
are you sure, you have goodix version?
Click to expand...
Click to collapse
harizinside said:
test on aida64 and we will see what your fingerprint :silly:
Click to expand...
Click to collapse
AIDA64 is known to report FPC even though devices have a goodix FP. Anyways, mine shows
Manufacturer: FPC/Goodix
Model: FPC102x / FP
And I have a "goodix" folder in root/data with some folders and files inside, there's also an fpc folder alongside the "goodix" one but there is nothing inside.
Also, running the command "getprop | grep goodix" in shell gave me a goodix result.
All the above should be enough to say that I DO have a goodix sensor. Right?
ASDFking said:
AIDA64 is known to report FPC even though devices have a goodix FP. Anyways, mine shows
Manufacturer: FPC/Goodix
Model: FPC102x / FP
And I have a "goodix" folder in root/data with some folders and files inside, there's also an fpc folder alongside the "goodix" one but there is nothing inside.
Also, running the command "getprop | grep goodix" in shell gave me a goodix result.
All the above should be enough to say that I DO have a goodix sensor. Right?
Click to expand...
Click to collapse
Thats my.. it shown a goodix
Try an librarry pacth and custom kernel.
It's work.
Ps: Sidik jari means Fingerprint
Sent from my Redmi Note 3 using XDA Labs
harizinside said:
Thats my.. it shown a goodix
Try an librarry pacth and custom kernel.
It's work.
Ps: Sidik jari means Fingerprint
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Can I have the link to the library patch and the custom kernel you're using?
And also, what ROM is that?
ASDFking said:
Can I have the link to the library patch and the custom kernel you're using?
And also, what ROM is that?
Click to expand...
Click to collapse
of course
ROM= cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kenzo.zip
KERNEL=Radon Kernel V.3.4
PACTH=Goodix_FP_8
Also
Super Su
Xposed
Mising Blob front camera
and etc.
ASDFking said:
AIDA64 is known to report FPC even though devices have a goodix FP. Anyways, mine shows
Manufacturer: FPC/Goodix
Model: FPC102x / FP
And I have a "goodix" folder in root/data with some folders and files inside, there's also an fpc folder alongside the "goodix" one but there is nothing inside.
Also, running the command "getprop | grep goodix" in shell gave me a goodix result.
All the above should be enough to say that I DO have a goodix sensor. Right?
Click to expand...
Click to collapse
not yet... i think your sensor is FPC
have you try lineage os FPC version by minz1?
pumpkins12 said:
not yet... i think your sensor is FPC
have you try lineage os FPC version by minz1?
Click to expand...
Click to collapse
Yeap, tried it, doesn't work. And if my sensor was FPC, it would've worked fine on all other ROMs right? But it didn't apparently.
harizinside said:
of course
ROM= cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kenzo.zip
KERNEL=Radon Kernel V.3.4
PACTH=Goodix_FP_8
Also
Super Su
Xposed
Mising Blob front camera
and etc.
Click to expand...
Click to collapse
Thanks, I'll try it and report back. BTW, the order or flashing is firmware > ROM zip > Radon Kernel > Goodix patch right?
ASDFking said:
Thanks, I'll try it and report back. BTW, the order or flashing is firmware > ROM zip > Radon Kernel > Goodix patch right?
Click to expand...
Click to collapse
That's right, and don't forget for open gapps haha..
Ohh thanks button please ??
Sent from my Redmi Note 3 using XDA Labs
Nope, doesn't work.
Dude, I was in the same situation as you, and also thought that I have goodix, tried every patch, kernels, everything but it just didnt work. I was using cm13 by santhosh which works with goodix rom (but also fpc) and my fingerprint was working. So when I tried to install official cm13, I immediately installed goodix patch and my fp just didnt work. After that, I tried installing rr 5.8.0, also with goodix fix but it didnt work. And then, I wiped everything, did factory reset in twrp, installed cm13 firmware, rr 5.7.4, open gapps and rebooted the system. When fp settings came, I thought lets give it a try and added fingerprint and to my surprise, it worked. It turned out that I have fpc fingerprint. After that, I flashed radon 3.4, selected the fpc fp and worked.
So, the moral of this story is, you might have fpc fingerprint although you have goodix files in system. Try this steps that I described, or just skip everything, do factory reset and wipe in twrp, flash firmware, rom and gapps and reboot to system and set up the rom and see if it works.
{s3rious} said:
Dude, I was in the same situation as you, and also thought that I have goodix, tried every patch, kernels, everything but it just didnt work. I was using cm13 by santhosh which works with goodix rom (but also fpc) and my fingerprint was working. So when I tried to install official cm13, I immediately installed goodix patch and my fp just didnt work. After that, I tried installing rr 5.8.0, also with goodix fix but it didnt work. And then, I wiped everything, did factory reset in twrp, installed cm13 firmware, rr 5.7.4, open gapps and rebooted the system. When fp settings came, I thought lets give it a try and added fingerprint and to my surprise, it worked. It turned out that I have fpc fingerprint. After that, I flashed radon 3.4, selected the fpc fp and worked.
So, the moral of this story is, you might have fpc fingerprint although you have goodix files in system. Try this steps that I described, or just skip everything, do factory reset and wipe in twrp, flash firmware, rom and gapps and reboot to system and set up the rom and see if it works.
Click to expand...
Click to collapse
When you say it works, you mean it really works flawlessly like it did on MIUI, and it unlocks the lockscreen without the screen on?
Also, may I know the version of RR 5.7.4 that you flashed? And the CM13 firmware I suppose is the one from the official thread right?
Another thing, if you had fpc, then shouldn't the fingerprint have already worked when you first tried installing a custom ROM without any patches or kernels?
It works just like on miui, except when the phone is in deep sleep it takes him about 2 secs to unlock with fp, but if you press power button first and then put fp, it will unlock immediately.
I will provide you files in 5 mins, when I come to pc.
Another thing, if you had fpc, then shouldn't the fingerprint have already worked when you first tried installing a custom ROM without any patches or kernels?
Click to expand...
Click to collapse
I am not sure. After santhosh cm13, I tried flashing official cm13 by strix but I am not sure wether I tried to set up the rom without any patches and fixed and kernels or with them. I think that I didnt, because I thought that I have goodix fp.
Anyway, here is the link to rr 5.7.4-20161119: https://www.androidfilehost.com/?fid=385035244224399916
And here is link to firmware that I used and kernel: https://drive.google.com/open?id=0B0PETL84EtNFUFEwZUdvUGFScnM
Try that, and post results here and any further questions.
Goodluck
Thanks, will try and report back here.
BTW, is that the official ROM or an unofficial one?
Reporting back, NOPE, it doesn't work, sadly.
I am not sure, I found the link in official thread.
I'm sorry that it doesnt work, I really had my hopes up high.
Try again, or try 1113 build, in the official thread in op link.
And try without installing gapps, after you flash rom, reboot to system and set it up. If that doesnt work, try again flashing rom, without gapps and wipe dalvik and cache before first boot
I have my fingers crossed man
Okay, will give another few tried when I have the time. BTW, have you tried Lineage OS?
Related
Hi everybody,
i'm having problems with this smartphone from the day I bought It.
I've received my phone, had a customized ROM by vendor, FP wasn't working (was like disabled). So i installed 7.5 stable (by xiaomi.eu), everything worked fine for one/two weeks, after the day that i wanted to play a game that can't run in rooted devices. First of all i checked on internet something to do, if i could run it, but nothing. So i started searching something in Link2SD and SuperSU settings.
First, i have entered to Link2SD, clicked the app, then "Convert to user app" (You'll sure ask: reasons? Well, don't know). Don't know what I was expecting but happened nothing. Then i said "let me check if there's an option in TWRP 3.0", i went to recovery mode, searched for something and I didn't find anything, so pressed Reboot > System. The smartphone stuck at MI logo and had to flash the ROM again (The same one).
After the flashing operation, there was a surprise. The battery went to -2% and kept stuck at it. I've tried EVERYTHING, installed all type of ROMS (Stable, dev, china, global, custom, etc etc) battery stuck at -2%.
Read online that was a kernel problem, so let's try to find a custom kernel or maybe the ORIGINAL kernel of Redmi Note 3 pro (Kenzo). Everybody said that Radon Kernel was what I was looking for. Installed it.
Yes! It resolved the -2% battery issue, i was so happy. At one cost: the fingerpirnt sensor. After normal reboot of the smartphone the FP sensor turns off and i'm unable to use it. With the first boot after flashing ROM and Radon Kernel, FP works perfectly, but if I reboot the smartphone then it stops run.
Tried with most of kernels for MIUI and Radon was the only one to solve the -2% battery issue.
Follow i just leave thing that i already did or i see everytime:
Discharged battery to 0%, then charged it at 100%;
Tried MIUI 7.1, 7.3, 7.5, 6.8.4 (every tipe, stables, dev, china, global etc);
Everytime i install a new ROM (TWRP or Mi Flash tool - via fastboot -) looks like TWRP disappears, i get instead a battery with low-red health and a charger;
-2% battery issue persist even with other ROMs (Flashed Cyanogenmod 13 by RR).
Still looking for the original Kernel of Kenzo, but I don't think if I will find it.
Can someone of you help me with this embarassing problem??
Thank you all.
i have the same problem, people say its an kernel issue. so far there is no fix.
edit: radon kernel fix this bug.
Use Blaze Kernel , it fixes 2% bug and also it gives more battery backup than radon. Also i get random reboots in radon but blaze has been stable for me so far
Here is the link to the kernel
Hit thanks button if you think i helped you
Being Indian said:
Use Blaze Kernel , it fixes 2% bug and also it gives more battery backup than radon. Also i get random reboots in radon but blaze has been stable for me so far
Here is the link to the kernel
Hit thanks button if you think i helped you
Click to expand...
Click to collapse
Everything is solved with the new version of the Blaze Kernel, v3. The v2 gave me the same problem as the Radon Kernel, but looks like the new version of Blaze is running good!
I can reboot my smartphone everytime i want and the FP sensor keep working!
Flash radon kernal or blaze kernal. I used both and none of them had the -2% issue.
@paprika714 what fingerprint sensor do you have? I have FPC and it doesn't work on any custom rom no matter what kernal I use.
A Sad Napkin said:
Flash radon kernal or blaze kernal. I used both and none of them had the -2% issue.
@paprika714 what fingerprint sensor do you have? I have FPC and it doesn't work on any custom rom no matter what kernal I use.
Click to expand...
Click to collapse
Yes, every custom kernel solve also for me the -2% bug, the problem was the FP sensor that stops working after i reboot the smartphone, but looks like with the new version of Blaze is solved.
If you are so gently to say to me how to check my FP model, i'll tell you.
paprika714 said:
Yes, every custom kernel solve also for me the -2% bug, the problem was the FP sensor that stops working after i reboot the smartphone, but looks like with the new version of Blaze is solved.
If you are so gently to say to me how to check my FP model, i'll tell you.
Click to expand...
Click to collapse
Aida64 you can use but its a bit hit and miss
You need to check what folder you have in the data folder, will either be FPC or goodix.
A Sad Napkin said:
Aida64 you can use but its a bit hit and miss
You need to check what folder you have in the data folder, will either be FPC or goodix.
Click to expand...
Click to collapse
FPC - FPC102x.
What' s the difference between Goodix? What is better?
paprika714 said:
FPC - FPC102x.
What' s the difference between Goodix? What is better?
Click to expand...
Click to collapse
strange how your FP works but mine doesn't and I have the same as yours lol
Goodix isn't supported yet but FPC should be.
What was your flashing procedure mate?
A Sad Napkin said:
strange how your FP works but mine doesn't and I have the same as yours lol
Goodix isn't supported yet but FPC should be.
What was your flashing procedure mate?
Click to expand...
Click to collapse
I have installed TWRP 3.0, everything is copied in my micro SD card (ROM 7.5 stable and kernel).
These are my steps:
- Wipe > Format Data;
- Wipe> Advanced Wipe > everything except external SD;
- Install > Select ROM package;
- Install > Select kernel.zip package > after installation i click wipe cache/dalvik;
- Reboot
This is my usually full wipe installation via TWRP
Hello folks Ive been using fp scanner in 16s Indian with no problem at all.Since ive Ive updated to 19s officially my fp scanner doesn't work when device is lifted after a few seconds or deep sleep.It works flawlessly when I turn on screen & even after that until I keep my phone
Now my question is Can I downgrade to prev version by renaming it to update.zip or Is there any workaround in this version also?
Ive tried reset & restart several times.
Thanks For your time
RISHI RAJ said:
Hello folks Ive been using fp scanner in 16s Indian with no problem at all.Since ive Ive updated to 19s officially my fp scanner doesn't work when device is lifted after a few seconds or deep sleep.It works flawlessly when I turn on screen & even after that until I keep my phone
Now my question is Can I downgrade to prev version by renaming it to update.zip or Is there any workaround in this version also?
Ive tried reset & restart several times.
Thanks For your time
Click to expand...
Click to collapse
Help.
Install twrp. Install a custom eui based on 23s or 26s and install 26s modem. All set and done
Hello LeMax aficionados!
I have a Le Max 2 (4gb, 64gb), bought originally as an X829. I immediately flashed the latest lineage OS and have been updating it weekly (now device info shows X820). Everything worked well for more than a month; fingerprint sensor was working well too.
At the time of the issue I was on the 16th Dec release of LOS and had the superuser addon installed. I decided to move to the latest magisk (v15) and get the systemless Xposed (sdk25) so I could try out the Leeco Infrared Fix and the InstantFaceUnlock module. This is how I went about it.
1 Flashed the superuser addon remover. Rebooted.
2 Installed the XposedInstaller (latest version from the source)
3 Flashed magisk v15.0. Rebooted.
4 Downloaded the Xposed sdk 25 from the downloads section of magisk. Rebooted.
5 Opened XposedInstalled and saw Xposed was installed and everything was green.
6 Downloaded the Leeco Infrared Fix and the InstantFaceUnlock thingy. Rebooted for it to take effect.
Here’s where the problem started. I got stuck on the boot animation screen for a long time. Unsure about what to do I left it like that for 3 hours or more (plugged in). When I finally checked it, the phone was extremely hot. I pressed the power button for 10s to force restart and had the same issue. I used the vol UP+power button combo to boot into recovery. Then:
A I flashed the Magisk uninstaller.
B Dirty flashed the Dec 23 LOS. Rebooted. Thankfully it booted properly.
C Uninstalled the XposedInstaller. Rebooted.
D Flashed the superuser addon.
E Everything seems fine. Except that the fingerprint sensor doesn’t work. Even when I remove all fingerprints and try to register it anew, the calibration process doesn’t proceed beyond the first fingerprint. (1/10).
F I flashed the chinese 26s Modem. Same problem persists.
G I did a basic wipe from TWRP. Restored a nandroid backup from a week back. Everything is fine except that the fingerprint sensor doesn’t work.
Did the overheating mess up some key component of the fingerprint sensor? Any suggestions?
Have a nice day guys!
Bump!
Any ideas guys?
I was reading before that overheating mess up with finger print.
@shanty23 any news thus far? I have the same model but my fingerprint only worked for a few seconds after I purchased the phone. I immediately flashed a custom ROM though.
pinnekeshaar said:
@shanty23 any news thus far? I have the same model but my fingerprint only worked for a few seconds after I purchased the phone. I immediately flashed a custom ROM though.
Click to expand...
Click to collapse
Exactly the same happened to me, I immediately installed a custom Oreo ROM and the fingerprint sensor died. I was resigned to live without it but after installing Xposed framework (I'm using AICP ROM) the fingerprint got back to life...
Enviado desde mi LEX820 mediante Tapatalk
cruizgaray said:
Exactly the same happened to me, I immediately installed a custom Oreo ROM and the fingerprint sensor died. I was resigned to live without it but after installing Xposed framework (I'm using AICP ROM) the fingerprint got back to life...
Enviado desde mi LEX820 mediante Tapatalk
Click to expand...
Click to collapse
Hi @cruizgaray ,
Can you specify which AICP ROM did you install and what Xposed version? Is the FP still working? before the fix did you have any signal from the FP reader? I mean like the FP gestures on camera app working.
Flash this -> https://androidfilehost.com/?fid=818070582850487752
Reflash the ROM and see if it help.
Beackman said:
Flash this -> https://androidfilehost.com/?fid=818070582850487752
Reflash the ROM and see if it help.
Click to expand...
Click to collapse
Done. No change. I'm starting to think it's a hardware failure.
Thanks anyway
surfersea said:
Done. No change. I'm starting to think it's a hardware failure.
Thanks anyway
Click to expand...
Click to collapse
Give time to the sensor, maybe they back to life.
Or, just a hardware damage like you said.
I have posted a solution for this in the treads all eui rom
Mine also dead after 3 days of purchase. But one day it accidentally started responding. Now its working fine. According to me wait for few days, it may work.
surfersea said:
Hi @cruizgaray ,
Can you specify which AICP ROM did you install and what Xposed version? Is the FP still working? before the fix did you have any signal from the FP reader? I mean like the FP gestures on camera app working.
Click to expand...
Click to collapse
Before it got fixed it was completely dead; it just worked a couple of minutes after I received it.
I installed Infrag's AICP and the last version of Xposed (not systemless) for Oreo. I' keep using Infrag's AICP and the FP is working perfectly.
Best regards
Enviado desde mi LEX820 mediante Tapatalk
About This Rom
This is a debloated stock rom based on stock F800K_30H. Most likely the last update the V20 will get.
Installation Procedure for F800 L/K/S
Download the F800***.7z to a PC and extract with 7-zip app on Windows PC or the equivalent on OSX / Linux . This will expand to a single 6GB system.img file. Copy over to internal storage on your device.
Update TRWP recovery to 3.4.x.x using TWRP.
Download also the F800 boot imgage and F800K-ezv2020.zip kernel.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Boot into twrp and flash the system image.
Install>Install_Image(bottom right)>navigate to system.img file and select system image partition.
Repeat the same procedure for the boot.img, flash on boot partition.
Flash ezV2020 Kernel and then Magisk. Done.
If you are coming from Oreo download also the Pie partitions and flash that first, then as above. Also wipe data so have your apps backed up.
In the case your were already on PIE no need to wipe data but do wipe Dalvik / ART cache and Cache in TWRP before reboot. Device will be slow for a while and will speed up as Dalvik cache is rebuilt in the background. Sometimes that can take a while especially if you don't let the device rest.
==========================================================
Update Nov 2022: You now need to flash in twrp this Chrome update to pass initial setup screen after phone reset or fresh flash.
F800 - Google Drive
drive.google.com
Release v2
This is based on K rather than L for no good reason (new: flash the K partitions in my repo and ezv2020 K kernel), but makes no difference as all carrier apps have been deleted. This is a 'start again' version rather than an update to ver 1 and is recommended to update due to reports of better performance.
Added
QLens
V30 and G6 themes ( I like the black one with dark grey accents)
Sim unlock app (I think it's for phones locked to sim, not sure if it is or if it works)
Wap Push Service (for carrier settings sent via text msg)
Collage Wallpapers from G6 - only works on Lock Screen, dunno why, i'll try fix.
LG Smart World. You must hide it in Magisk first, then software update. Don't know how to change Korean language, sorry.
If you don't care for any of these additions delete them from /system/product/app , using a root browser
RCT (root check tool) remover has already been applied.
Known issues (minor)
Touch screen is not responsive after coming out of Laf Download Mode at times. To recover this simply reboot into recovery and reboot. It's not that serious and doesn't occur after a normal reboot. You just need to be aware of the fix in case you experience it.
If you have any apn issues do the 'reset apn settings to default' in the apn settings menu. Cuz my carrier apn didn't show up initially.
==========================================================
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
TarAntonio said:
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
Click to expand...
Click to collapse
Install Mixploer from here http://mixplorer.com/
Download the attachment provided and extract the folder to Internal Storage
Using Mixplorer copy and paste the Folder named LGCalendarProvider to...
root>system>product>priv-app
(you may be asked to grant root permission here)
Make sure you can see the LGCalendarProvider Folder is in priv-app folder, now reboot.
Google calendar is working for me now.
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
TheRoyalDuke said:
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
Click to expand...
Click to collapse
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
ezzony said:
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
Click to expand...
Click to collapse
Bluetooth works fantanstic. Connected my portable speaker and it played smoothly, never disconnected.
TheRoyalDuke said:
Edit: F800L30H_Partitions is needed to get fingerprint working.
Click to expand...
Click to collapse
Thanks for that. It might be just the modem that is needed. Can you get into download mode after flashing the partitions? Be careful. That is why I said in the OP don't flash Pie Partitions on non-F800 although you may not have seen that as I added it later.
I have a zip somewhere to flash back oreo partitions. I'll upload it later.
edit: just checked my us996, fingerprint is working fine without flashing pie partitions. Please delete your edit as I don't want anyone flashing pie partitions on non-f800 devices because of the laf download problem.
I will have to figure out what exactly is going on but until then I don't support of advise anyone to flash Pie partitions on any non-F800 device.
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
TheRoyalDuke said:
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
Click to expand...
Click to collapse
Ah good. Because there was an issue with the new Pie LG LAF (download mode) not being detected in LGUP. Experienced that myself. The danger is then if you accidentally deleted TWRP or somehow got corrupted there would be no way to ever flash the phone again and you'd be stuck with what you have. That is why I'm being extra cautions.
Note:
I still don't advise anyone to flash pie partitions on non-f800. There are so many variants it's not certain or knowable if all will be okay for all of them.
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloated right?
xxseva44 said:
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloat right?
Click to expand...
Click to collapse
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
ezzony said:
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
Click to expand...
Click to collapse
Ahh okay, thx for letting me know
Edit: So i flashed it and at first it was very stable but then it crashed to that green apps watchdog bark, i then rebooted and it crashed and showed the purple secure watchdog bite screen a couple of seconds after unlocking the phone. not sure if this is relevant but when it crashed it was downloading about 40 apps, and i was trying to log into instagram. Maybe it was just a fluke, i'll see if it happens again
Edit2: So i rebooted and everything seems fine again
Edit3: okay so it crahsed again, same thing happened, it crashed to the green watchdog bark screen although this time it went from that screen to the purple watchdog bite screen without rebooting or anything. When it crashed, i went to unlock it and it froze while i was unlocking the phone
Could this have anything to do with the fact that my phone was originally a vs995? Cuz i converted it to a us996, I noticed that there was a vs995 pie kernel, should i flash that and see if the crashes stop? I'm not too sure if it would do anything especially since i was running alpha omega oreo with your us996 oreo kernel just fine but it's worth a shot but just to be sure, for now i'll reflash the us996 kernel again and see if the crashes return
update: It worked fine for the past hour but crashed to the watchdog bite screen again, i'll try flashing the vs995 pie kernel and see if the crashes stop. Okay so i successfully flashed it, now i just have to wait and see
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
xxseva44 said:
Ahh okay, thx for letting me know
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Click to expand...
Click to collapse
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
ezzony said:
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
Click to expand...
Click to collapse
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
TheRoyalDuke said:
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
Click to expand...
Click to collapse
You could try flashing the modem only. The pie modem, in twrp. I'd be curious to know what would happen. I have just uploaded it. Worth a try. The fingerprint for some reason uses files in the modem partition. Why there are there I don't know.
Be advised everyone all this mixing and matching pie with oreo may result in unforeseeable negatives. We can only know what works by trial and error. And, your welcome!
xxseva44 said:
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
Click to expand...
Click to collapse
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
ezzony said:
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
Click to expand...
Click to collapse
Yea i double checked, i flashed the us996 pie kernel twice actually, but had the same results
Okay so before i added anything, i tried to open the alexa app again, this time it worked fine and didn't cause my phone to crash, so this time i'm going to open a lot of apps and see if that will trigger the crash
Edit: nope, that did not cause it to crash either, i have no idea what's causing the crashes, maybe it has something to do with the cache because i remember when i tried rebooting after the second crash, it was stuck at the boot animation, it only rebooted after i cleared delvik and cache. Maybe the cache is getting corrupted after a while?
Update: Phone has been running fine for 1 day
Update2: Phone crashed this morning while scrolling to instagram, these crashes seem to be happening at random. Only thing the crashes have in common is that it would happen roughly every 20 hours to a day. Sometimes if i'm unlucky it just repeatedly crashes after a couple of reboots
Update3: Okay yea theres something funny going on with the cache because, i went to the gallery to look at some videos that i know would play but when i tried to play them it kept saying something went wrong, tried a reboot but still the same result. and when i'd watch videos on instagram they looked corrupted, tried force stopping and clearing the cache but still the same result. reboot didn't help either, only thing that fixed those issues was clearing the cache and delvik in twrp
Update: So i have found a temporary solution which is to clear the cache and delvik every once in a while
Idk if this is relevant but what did you come from before flashing this cuz i came from oreo so idk if that could have anything to do with the issue
HI to all
Strange behaviour with my phone. As title says, I cannot add PIN or fingerprint.
I have unlocked bootloader, flashed TWRP and rooted with Magisk 23. On Dev Settings OEM lock is enabled but I can switch it off if I want. It is not dimmed as it should be. I have checked bootloader unlock status via Fastboot - "fastboot getvar all" and it says (bootloader) unlocked: yes
Has anyone any idea why PIN or fingerprint cannot be added?
I have to say that I am bit frustrated with this phone, always something is not working as it should. Never know what tomorrow happens.
This my second One Plus Nord 2. First one I had 2 months, during that period of time it was 3 times at service. Once motherboard was changed. What they did other (2) times I do not know. And now this new one, which I got as replacement bec older sucks , is starting to suck too
Is metadata responsible for PIN or fingerprint? It holds keys for security, so maybe if I flash new metadata would it help/fix problems or is it device specific?
Any ideas, thank you
I had this exact same issue as well, and it seems to be linked to the way TWRP restores/saves the data partition in my case. My fix was to boot into recovery and wipe/reformat all data.
After a fresh wipe, my issues were resolved, but i had to manually redownload and setup all apps again. I did multiple tests and the issue would always come if i restored my data partition; whether i flashed it via TWRP or via fastboot. It's likely the way TWRP saves the data partition was my issue.
Zombnombs said:
I had this exact same issue as well, and it seems to be linked to the way TWRP restores/saves the data partition in my case. My fix was to boot into recovery and wipe/reformat all data.
After a fresh wipe, my issues were resolved, but i had to manually redownload and setup all apps again. I did multiple tests and the issue would always come if i restored my data partition; whether i flashed it via TWRP or via fastboot. It's likely the way TWRP saves the data partition was my issue.
Click to expand...
Click to collapse
HI and thank you for reply
Do you mean stock recovery? I have tried TWRP - format data, didn't help.
If you format data using TWRP my experience is that TWRP will uninstall itself in the process, so you'll boot into stock recovery after that anyway.
I would honestly suggest doing both. If you have TWRP, reformat and wipe using TWRP wipe. Next time you boot to recovery, it should be stock. Do another reformat+wipe on stock recovery. Should do the trick.
Never mind, I did not want to steal your topic. Open my own!
exis_tenz said:
Never mind, I did not want to steal your topic. Open my own!
Click to expand...
Click to collapse
hi. yes, we have different problem but i have to agree, always something strange happens with this phone. kinda sucks
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
exis_tenz said:
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
Click to expand...
Click to collapse
i had same too, 2 times service flashed stock back and 1 time change motherborad. now they gave me new one, but still prbs. am fed up too
exis_tenz said:
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
Click to expand...
Click to collapse
jis251 said:
i had same too, 2 times service flashed stock back and 1 time change motherborad. now they gave me new one, but still prbs. am fed up too
Click to expand...
Click to collapse
Funnily enough, both of your issues are caused by TWRP not flashing partitions correctly, at least from my testing.
In Jis's case, (RE: Current thread) it's because TWRP does not flash the DATA partition correctly, and prevents the phone from being able to set a lockscreen password (and therefore the Data partition cannot be encrypted). And without a lockscreen, the stockOS does not allow you to set biometrics such as fingerprints/face unlock, though theoretically in this case, both sensors work perfectly, it's a simple software restriction.
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Remember, @TheMalachite 's release of TWRP is an unofficial release and we're just glad to have it working at all. That said though, I wonder if TheMalachite is aware of these issues?
Zombnombs said:
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Click to expand...
Click to collapse
Thing is: I didn't flash ANYTHING in TWRP. It's a clean recovered stock rom done by an official OnePlus servicecenter.
Zombnombs said:
Funnily enough, both of your issues are caused by TWRP not flashing partitions correctly, at least from my testing.
In Jis's case, (RE: Current thread) it's because TWRP does not flash the DATA partition correctly, and prevents the phone from being able to set a lockscreen password (and therefore the Data partition cannot be encrypted). And without a lockscreen, the stockOS does not allow you to set biometrics such as fingerprints/face unlock, though theoretically in this case, both sensors work perfectly, it's a simple software restriction.
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Remember, @TheMalachite 's release of TWRP is an unofficial release and we're just glad to have it working at all. That said though, I wonder if TheMalachite is aware of these issues?
Click to expand...
Click to collapse
This is completely unrelated to TWRP itself. OxygenOS for Nord 2 use ColorOS base which is know to give such issues (Also happen with OPPO and Realme devices on ColorOS and RealmeUI)
exis_tenz said:
Thing is: I didn't flash ANYTHING in TWRP. It's a clean recovered stock rom done by an official OnePlus servicecenter.
Click to expand...
Click to collapse
Then they messed up your persist image and/or calibration data in some way or fashion. Take it back and complain they messed up your stuff. Probably some novice technicians who made a mistake would be my guess.
TheMalachite said:
This is completely unrelated to TWRP itself. OxygenOS for Nord 2 use ColorOS base which is know to give such issues (Also happen with OPPO and Realme devices on ColorOS and RealmeUI)
Click to expand...
Click to collapse
Ah, that's good to know. So it seems everything is the fault of ColorOS.
Camera works, fingerprint doesn't...