Related
Hi, my friends.
Great news . The new official update Leeco that has come in Indian web finally brings everything to their phones sold worldwide:
- Multilanguage. But, really. All are translated (I only tried Spanish, I assume that the other languages also). In Europe only translate to Spanish, English and French. The rest are Asian languages.
- Leeco Account. Integrated with Google account, as it should be. Leeco access to the entire EUI universe. Synchronization of our contacts, photos, etc.
- All active applications, including Leeco LIVE, Levidi, Leview ...
- Google for Works integrated with Gmail Exchange account, Play Music, Play Video, Google+, Yotube .
Only rest check battery perfomance, but ROM it´s smooth and powerful.
Download links:
Official: http://g3.letv.cn/209/7/47/letv-hdtv/0/upload/tmp/20160706171018829/LE_X2_X820-OS-OP-FGXOSOP5801507066S-5.8.015S.zip?b=123456&platid=5&splatid=500
Mega: https://mega.nz/#!wtplFRIQ!l5V9p8PtpmqEznqQjkm9vFNG6LCgM-KrpEDbTShiwn0
Enjoy ¡¡¡
yes, it's a good one. just installed no problems so far.
I had a problem with previous stock versions that 4G speed had some hickups....when I was downloading (for example from google store) it paused for 30 seconds..sometimes longer.
tried SIM in slot 2 and vice versa..but problem remains.
now it goes smoothly without pauses (so far)
also had the CM13 which is almost the best, apart from the sound bug...definitely one I want on this phone for a long time..if sound thingy is fixed.
thanks!
Recommendation Do Not Use India version
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
Hmm..Ok! phone is encrypted indeed..do you know if there's as a way to decrypt or turn it off.?twrp is asking for a password when going onto recovery now...in previous roms the encrypt option was not greyed out.
or is only way to get in twrp and wipe everything.
Thanks !
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
What is the way around the issue of encryption? So we can never install TWRP ever?
sanke1 said:
What is the way around the issue of encryption? So we can never install TWRP ever?
Click to expand...
Click to collapse
Under TWRP data it´s encrypted. But under Windows not. Copy to your computer all files that you need save (photos, music, etc.), and then format data in TWRP.
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
STEVE_MARS said:
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
Click to expand...
Click to collapse
I wold'n say that his rom is better than others, here is still missing the multilingual support and so on. I'm atm with "Revolution 15s EUI 5.8 by TeaMSpaiN" alsolutely happy, just litte fine tuned and see my benchmark with over 143.000 points (first run). And yes the rom is smooth as hell.
Antutu proof pic:
http://www.pic-upload.de/view-31202011/Screenshot_20160714-071230.jpg.html
NU_User said:
I wold'n say that his rom is better than others, here is still missing the multilingual support and so on. I'm atm with "Revolution 15s EUI 5.8 by TeaMSpaiN" alsolutely happy, just litte fine tuned and see my benchmark with over 143.000 points (first run). And yes the rom is smooth as hell.
Antutu proof pic:
http://www.pic-upload.de/view-31202011/Screenshot_20160714-071230.jpg.html
Click to expand...
Click to collapse
:angel: yes, we developed Revolution series :good:. But I recommended you that try this Indian version .
STEVE_MARS said:
:angel: yes, we developed Revolution series :good:. But I recommended you that try this Indian version .
Click to expand...
Click to collapse
no
---------- Post added at 10:53 AM ---------- Previous post was at 10:25 AM ----------
@STEVE
if you want help you can try to fix the CM13 rom, THIS one, if would been fixed where of course the ultimare rom for our little beast.
STEVE_MARS said:
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
Click to expand...
Click to collapse
You did not understand my question properly.
Right now, there is absolutely NO way to install TWRP on Indian X821 model. I cannot format DATA without installing TWRP.
All the TWRPs available on this forum give a BLOD (Blue Led of Death) The screen remains blank but powered on. The Blue LED light remains. There is another guy who is having the same problem and he has created a separate topic for it.
We can restart the phone normally but the installed TWRP gets overwritten with stock recovery.
atm here is no solution for your device, you need to wait until a developer create a TWRP compatible for your device.
sanke1 said:
You did not understand my question properly.
Right now, there is absolutely NO way to install TWRP on Indian X821 model. I cannot format DATA without installing TWRP.
All the TWRPs available on this forum give a BLOD (Blue Led of Death) The screen remains blank but powered on. The Blue LED light remains. There is another guy who is having the same problem and he has created a separate topic for it.
We can restart the phone normally but the installed TWRP gets overwritten with stock recovery.
Click to expand...
Click to collapse
What I did was to go into settings -> fingerprint -> -> other security options -> trusted credentials and disabled the credentials. You have to do this one by one as the clear all option is grayed out. From there I went into and fast boot and flashed TWRP recovery. I rebooted immediately to RECOVERY wiped everything on internal storage. I then transfered a ROM to storage and flashed normally. All is working again and TWRP and root are functioning.
WTF, ok it is a security related issue?
jim262 said:
What I did was to go into settings -> fingerprint -> -> other security options -> trusted credentials and disabled the credentials. You have to do this one by one as the clear all option is grayed out. From there I went into and fast boot and flashed TWRP recovery. I rebooted immediately to RECOVERY wiped everything on internal storage. I then transfered a ROM to storage and flashed normally. All is working again and TWRP and root are functioning.
Click to expand...
Click to collapse
I flashed old 14S Chinese ROM and then flashed recovery. My phone shows X820 now. I guess X820 and X821 may be just the same. It's the Chinese Roms show X820 and Indian Rom shows X821.
BTW I am on TeamSpain's CM Rom. Working good except charging.
If I used my Aukey QC 3.0 charger, the LED flashed like crazy and Ampere current measuring App showed 4680 mAh charging current and was climbing. (QC 3.0 shouldn't exceed 3000 mAh) So I immediately disconected it. Gave me a scare for a moment. Normal charging is slow but no LED blinking and feels safer.
NU_User said:
WTF, ok it is a security related issue?
Click to expand...
Click to collapse
Not a security. Just a way for Indian Dev's to prevent users from messing with their OS and to keep users on 100% stock.
STEVE_MARS said:
Hi, my friends.
Great news . The new official update Leeco that has come in Indian web finally brings everything to their phones sold worldwide:
Enjoy ¡¡¡
Click to expand...
Click to collapse
So can someone clarify if there's a way to clean install this ROM on a Chinese version of the phone and have a) TWRP b) ROOT working or is that impossible for now?
Exactly the same way as you install any other ROM. I have a Chinese phone and installed this ROM and uninstalled it because of its encrypted. Yes, the le-bloat is gone, but you will be unable to install TWRP or root because of the encryption.
jim262 said:
Exactly the same way as you install any other ROM. I have a Chinese phone and installed this ROM and uninstalled it because of its encrypted. Yes, the le-bloat is gone, but you will be unable to install TWRP or root because of the encryption.
Click to expand...
Click to collapse
Copy all your files (photos, videos, music, etc.) under Windows and enter TWRP, format DATA, reboot system, configure setupwizard, reboot TWRP again and copy supersu. zip and flash it.
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Flash fastboot room
Flash fastboot rom
always flash miui with mi flasher
[SOLVED]
alfarhaannizam said:
Flash fastboot rom
Click to expand...
Click to collapse
Worked like a charm. Downloaded MIUI 10.2.3 fastboot rom and flashed using Xiaomi Adb/Fastboot Tools. And then updated to MIUI 10.3.4 via system updater.
Thanks for the heads up. It was really helpful.
mendax99 said:
always flash miui with mi flasher
Click to expand...
Click to collapse
Mi Flasher don't work allright in my computer, since I only have USB 3.0 on my windows device and it seems MI Flasher doesn't work with USB 3.0
I'm using, usually command line abd and fastboot on windows. Today I've downloaded Xiaomi ADb/Fastboot Tolls and it was very useful.
I can't post links yet since I'm new on the forum. But search for Xiaomi ADB/Fastboot Tools GitHub. it is powerful.
otaodofino said:
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Click to expand...
Click to collapse
Why just not just freeze the app/ service ? That's what I did.
MasterFURQAN said:
Why just not just freeze the app/ service ? That's what I did.
Click to expand...
Click to collapse
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
otaodofino said:
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
Click to expand...
Click to collapse
Yeah. I know that flashing a fastboot ROM is the best way to repair corrupt partitions but it also resets the phone and I'm too lazy to restore everything back. Lol.
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.
Hi, I'm facing an issue right now, RevOS received an update that brings Android Q to Pocof1, which I would like to try but it seems that Migrate which I use to transfer apps and data on custom roms simply doesn't work from Pie to Q (Having Error 7 in TWRP, telling me that there's no rom installed on the device).
Also, I get stuck to boot screen if I try to dirty flash it on top of the Pie version.
So, is there any way to proceed so I don't lose everything?
Imposible. 9 to 10 is different system, whole system.
You might be able to restore apps and its data using titanium backup, but its not recommended since there are whole system update from pie to 10. Even on miui official, mods recommend to clean flash to avoid major bugs. And, probably apps that work on 9 will work on 10. So clean flash recommended.
CaPicote said:
Hi, I'm facing an issue right now, RevOS received an update that brings Android Q to Pocof1, which I would like to try but it seems that Migrate which I use to transfer apps and data on custom roms simply doesn't work from Pie to Q (Having Error 7 in TWRP, telling me that there's no rom installed on the device).
Also, I get stuck to boot screen if I try to dirty flash it on top of the Pie version.
So, is there any way to proceed so I don't lose everything?
Click to expand...
Click to collapse
What version of Migrate are you using? 3.0_alpha2?
Sent from my Galaxy Tab S5e using XDA Labs
I was using the latest stable version, I wasn't aware that there was an alpha compatible with Android 10.
In the end though I used Swift Backup before knowing about the Migrate alpha, and it worked well, so my issue is solved now!
Use Migrate
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...