Global Mi Note 10, I had an issue where I had to Miflash my phone back to life and now the fingerprint option in settings won't open, It'll go to the black screen where it gives you the warning, then it just kicks back to the settings menu. I've tried TWRP flashing Xiaomi.EU and OTA builds but nothing is bringing the option back, any suggestions?
Edit: Seems to be an issue with either the fingerprint service or library
I had same experience. I escaped from there by wipe cache and flashing Global stable rom with MiFlash.
grd549 said:
I had same experience. I escaped from there by wipe cache and flashing Global stable rom with MiFlash.
Click to expand...
Click to collapse
I tried that and unfortunately didn't help
I had the same problem, I Format, Not wiped the memory in twrp and then I flashed EEA Stable Rom via twrp. That solved the issue.
thor88 said:
I had the same problem, I Format, Not wiped the memory in twrp and then I flashed EEA Stable Rom via twrp. That solved the issue.
Click to expand...
Click to collapse
Can you explain a little more?
deathhall said:
Can you explain a little more?
Click to expand...
Click to collapse
Before flashing a Rom you have to Format the Phone in twrp by typing yes. After Format Flash the Rom. When you press wipe in twrp, you have the Option Just to Format Not to wipe, so Just Use this Option. I flashed after Format the official 11.0.16 EEA Rom.
I recorded in this gif the issue, as soon as the fingerprint loads it immediately crashes, happens on every ROM. Fingerprint sensor passes in CIT but can't input anything into it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Mi Note 10 using Tapatalk
I got a logcat of the error, It appears to be a corrupted fingerprint service library, but I've formatted and flashed the Vendor from the 11.0.8 global Fastboot rom with no fix. Here is an excerpt from the logcat.
04-12 17:45:11.272 I/FingerprintService(1642): fodCallBack cmd: CMD_APP_ENROLL , 0 , backRes:1 touchStatus:2 writeRes:true
04-12 17:45:11.272 D/FingerprintHal(1141): fingerprint_enroll
04-12 17:45:11.272 D/[GF_HAL][FingerprintCore](1141): [enroll] Enroll.
04-12 17:45:11.272 E/[GF_HAL][DelmarFingerprintCore](1141): [checkEnrollAuthReady] cali data not ready caliState=0x00000006
04-12 17:45:11.272 E/[GF_HAL][FingerprintCore](1141): [notifyErrorInfo] err code : -5.
04-12 17:45:11.272 E/[email protected](1141): Unknown error from fingerprint vendor library: -5
04-12 17:45:11.272 W/[email protected](1141): onError(2)
04-12 17:45:11.272 E/[GF_HAL][FingerprintCore](1141): [enroll] exit. err=GF_ERROR_CALIBRATION_NOT_READY, errno=1094
04-12 17:45:11.272 E/[email protected](1141): An unknown error returned from fingerprint vendor library: 1094
04-12 17:45:11.272 W/FingerprintService(1642): startEnroll failed, result=1
04-12 17:45:11.274 I/FingerprintService(1642): fodCallBack cmd: CMD_VENDOR_ERROR , 2 , backRes:1 touchStatus:0 writeRes:true
04-12 17:45:11.275 V/FingerprintService(1642): Done with client: com.android.settings
04-12 17:45:11.275 V/FingerprintService(1642): handleError(client=com.android.settings, error = 2)
Hello, how are you! I was wondering if anyone was successful with the digital problem?
tonny1306 said:
Hello, how are you! I was wondering if anyone was successful with the digital problem?
Click to expand...
Click to collapse
Likewise. I've been tinkering around but to no avail
So doing a bit of research, it's a problem with the Persist partition? I'm not sure how true that is, I've wiped Persist and used the img file from the latest global fastboot ROM. Still no dice.
Sent from my MI CC9 Pro using Tapatalk
Dev for OP 7T Pro 5G here
We are having this exact error in logcat.
Have you guys solved this?
Join us in the community chat in my signature if you;d like to discuss
hello this is a working solution 100% tested!!!!!! for FOD fingerprint add error!
deathhall said:
Global Mi Note 10, I had an issue where I had to Miflash my phone back to life and now the fingerprint option in settings won't open, It'll go to the black screen where it gives you the warning, then it just kicks back to the settings menu. I've tried TWRP flashing Xiaomi.EU and OTA builds but nothing is bringing the option back, any suggestions?
Edit: Seems to be an issue with either the fingerprint service or library
Click to expand...
Click to collapse
hello!
Please go to the CIT menu press the 3 dot in the top right of screen scroll down calibrate the FOD -> place a little mirror on FOD click start, before next step put something black thing on FOD and press next...wait until finish close restart and add your fingerprint have a nice day
cegyedi said:
hello!
Please go to the CIT menu press the 3 dot in the top right of screen scroll down calibrate the FOD -> place a little mirror on FOD click start, before next step put something black thing on FOD and press next...wait until finish close restart and add your fingerprint have a nice day
Click to expand...
Click to collapse
Almost works, it let's me actually start scanning my fingerprint now, but when it tries to save the fingerprint it kicks out of the menu and says the same error, couldn't add fingerprint
Sent from my Mi Note 10 using Tapatalk
deathhall said:
Almost works, it let's me actually start scanning my fingerprint now, but when it tries to save the fingerprint it kicks out of the menu and says the same error, couldn't add fingerprint
Sent from my Mi Note 10 using Tapatalk
Click to expand...
Click to collapse
Please use fresh rom or wipe all !! (don't forget to remove lockscreen password (pin))
deathhall said:
Almost works, it let's me actually start scanning my fingerprint now, but when it tries to save the fingerprint it kicks out of the menu and says the same error, couldn't add fingerprint
Sent from my Mi Note 10 using Tapatalk
Click to expand...
Click to collapse
Repeat this step with different fingers, My thumb failed on first place to, but after sucessful adding another fingrprint I could also add my failing thumb,...
Related
Download from lineageos.org:
Show all merged changes for lithium
Always Topical:
lineage-15.1-20180911-nightly-lithium
Extras:
Weather Providers
YahooWeatherProvider.apk
OpenWeatherMapWeatherProvider.apk
WundergroundWeatherProvider.apk
Changes for lithium:
https://download.lineageos.org/lithium/changes/1496858165
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I have on my Mi Mix the Epic Rom and I would like to try this rom.
What are the steps I must follow?
Erny.xiaomi said:
But I have on my Mi Mix the Epic Rom and I would like to try this rom.
What are the steps I must follow?
Click to expand...
Click to collapse
TWRP -> wipe data/cache/dalvik
flash Rom.zip & Opengapps ARM64/7.1 & Variant... & SuperSU or Magisk-v13-170606.zip + MagiskManager-v5.0-170606.apk (https://github.com/stangri/MagiskFiles)
Hi HenRy,
I followed the steps but for some reason when I record video in the native camera application, the recorded video audio is very low. Somehow the mic sensitivity is extremely low.
Any fix for that? the same thing happens with RR ROM. On stock MIUI video/audio was perfect and mic sensitivity was very good.
It s working fine here...big battery --Question : is it nightly or weekly ?
Anybody can find out ? Thanks
Tried to flash but keep getting failed due to sign verification following said steps using TWRP???????
Info
Just installed astonishing speed, for the moment no problem
FYI, speakerphone echo problem is still there.
does anyone know how to PERMANENTLY get rid of the navigation bar so that it NEVER shows?
yes you can hide it now, but it still shows when you swipe up. i want it gone. a build prop edit that works in miui doesn't work either.
I keep getting error 7 when the log is verifying Xiaomi Lithium modem. Using TWRP and coming from Unofficial Lineage UBERTC ROM. I wiped data, cache, and dalvik. Is it possible to get a mirror on the DL link? I tried deleting and re-downloading the file. I also tried Hen Ry's tip above for refreshing "allow modifications" but still nothing.
Vipermuscle83 said:
I keep getting error 7 when the log is verifying Xiaomi Lithium modem. Using TWRP and coming from Unofficial Lineage UBERTC ROM. I wiped data, cache, and dalvik. Is it possible to get a mirror on the DL link? I tried deleting and re-downloading the file. I also tried Hen Ry's tip above for refreshing "allow modifications" but still nothing.
Click to expand...
Click to collapse
I wiped the system also...all works fine
(BTW I use superSU not magisk)
I tried wiping system as well, still getting Error 7.
knives of ice said:
does anyone know how to PERMANENTLY get rid of the navigation bar so that it NEVER shows?
yes you can hide it now, but it still shows when you swipe up. i want it gone. a build prop edit that works in miui doesn't work either.
Click to expand...
Click to collapse
Open your build.prop
Add or modify the entry with the value of 1
qemu.hw.mainkeys=1
Vipermuscle83 said:
I keep getting error 7 when the log is verifying Xiaomi Lithium modem. Using TWRP and coming from Unofficial Lineage UBERTC ROM. I wiped data, cache, and dalvik. Is it possible to get a mirror on the DL link? I tried deleting and re-downloading the file. I also tried Hen Ry's tip above for refreshing "allow modifications" but still nothing.
Click to expand...
Click to collapse
Yes have same exact problem, I tried all the above and switched (TWRP Smarty and MRRaines) version to no avail, also down loaded ROM three different times after advised tick and untick no screen pops up.???
I have no problem flashing any other rom this is a first.
Arun1314 said:
Yes have same exact problem, I tried all the above and switched (TWRP Smarty and MRRaines) version to no avail, also down loaded ROM three different times after advised tick and untick no screen pops up.???
I have no problem flashing any other rom this is a first.
Click to expand...
Click to collapse
I have clean flashed this great Rom without any problem using TWRP Smarty and Super SU and latest GAPPS ( I ticked or unticked nothing)
knives of ice said:
does anyone know how to PERMANENTLY get rid of the navigation bar so that it NEVER shows?
yes you can hide it now, but it still shows when you swipe up. i want it gone. a build prop edit that works in miui doesn't work either.
Click to expand...
Click to collapse
ro.show.navigationbar=no
Gesendet von meinem MI MIX mit Tapatalk
Any issues with fingerprint and speakerphone echo?
dr.mz said:
Any issues with fingerprint and speakerphone echo?
Click to expand...
Click to collapse
NO issues..and double tap working..
Solution for "Error 7":
download last Miui.
Install it on twrp
download last Lineage
in twrp full wipe
install Lineage.
Solved.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not included in the changelog is the addition of a feature from Paranoid Android, locking recent tasks! And multitouch has also been fixed
Update is a rollout so you may not have it yet.
Factory images now live, check out @linuxct post here
If you come across any bugs please be detailed about it and leave bug reports.
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Wow, just when I finished wiping all my data and installing a Resurrection Remix. Ironic.
Is there any way to extract the camera apk to install it in my current ROM?
guys please i need help. has anyone successfully installed razers stock img files?
After the update, my sim card is no longer being detected. I tried restarting, shutting down, and turning back on. It was working perfectly fine before I restarted after updating.
Edit: It may be the sim card actually died. I tried it on another phone and it doesn't work there either. So it seems like coincidence that it died after the update.
Hmmmmm update fails for me. Not rooted bootloader locked. Error couldn't update installation issue helpfull error.
Fastboot images now live: https://developer.razer.com/razer-phone-dev-tools/factory-images/
Direct link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Taking a hell of a long time to install.... I'm using Snap Camera these days, which is great, I wonder what the new portrait mode is like..... But I can't see me changing back to stock now..
What is the best way to update when I'm rooted and have TWRP installed?
SeriousFlash said:
What is the best way to update when I'm rooted and have TWRP installed?
Click to expand...
Click to collapse
Use the factory images posted here
My update also fails when I'm not rooted and have my bootloader locked
My may update is now installing itself. I do wish it had prompted me rather than having to run a manual update as I was just going through some setting and clicked the update in error.
Updated and noticed loads of fixes, however, Bluetooth is now a complete no go with my car stereo. Sometimes I manage to actually connect it and can play music by pressing play on the phone but no song titles are shown on the car and music playback controls don't work at all... Has anyone had a similar issue or an idea as to what's wrong?
linuxct said:
Use the factory images posted here
Click to expand...
Click to collapse
How would I go about doing that then?
Make sure you go to Settings, system and Razer Preferences and Disable the Share Data again... it gets turned on with the update.
Got the OTA this Morning on my Three branded device and installed without issue.
Nice to see a timely release of the monthly security fixes - is this a benefit of Project Treble support ?
ccjack said:
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Click to expand...
Click to collapse
Just use the factory images but before flashing, edit the flash_all.bat go to the line that reads %fastboot_cmd% erase userdata" and put a pound "#" sign before the line so that adb ignores that line. Also do the same at the end of the script where you see "%fastboot_cmd% reboot". Doing the following will stop the script from formatting your data partition and keep your phone in download mode after the flashing process. Now you can do the "fastboot boot twrp-whatever-filename.img" and boot to twrp like you were to root like before and once in twrp, flash twrp zip and magisk zip same as before. Everything should work fine now.
Again. Make sure you edit the bat file so the factory images dont factory reset your data partition.
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Is there still no way to update and keep twrp?
navin2max said:
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Click to expand...
Click to collapse
Where I can fine a Nokia cam app?
As my main driver is a Redmi Note 7 on crDroid 6.3 with microG/GCam I would like to "free" my new Poco X3 Pro as soon as possible from Bloat/MIUI. As long as no good Xiaomi.eu/mi-globe or even better crDroid ROM is available I will probably not use Poco X3 Pro as main driver, unless I'm able to debloat successfully and a good GCam gets available.
Last time on the RN7 I did the unlock process ca. 20 months ago, so I do remember only some major steps and wanted to create this thread as long as no Tutorial is available here at xda.
I've done
- setup Mi Account
- Dev Unlock on MIUI Version field
- Additional settings > Developer options >
OEM unlocking
Mi Unlock Status
USB debugging
- already had ADB drivers, downloaded miflash_unlock-en-5.5.224.24.zip
with batch_unlock.exe requested unlock
tool says "please unlock 168 hours later"
Would'nt it be nice if for a small quote shops would offer Xiaomi unlocking included? Do exist those? I would seriously consider that in the future to avoid any registration etc. with Xiaomi.
So now I have to wait a week and maybe read some guides. Unsure if I can debloat with XiaomiADBFastbootTools-7.0.3.jar before device is unlocked. I think I had problems unlocking RN7 because I uninstalled some Mi stuff which was necessary to unlock. So I may wait?
Hi,
There already is a xiaomi.eu rom for our poco x3 pro.
Just one week wait isn't a lot...
Ive successfully debloated mine. My unlock timer ends tonight and just waiting to see more confirmation on the TWRP/OrangeFox that appeared.
Has anyone used my script yet to make their Poco X3 Pro fully read-write-able for debloating MIUI and further customizations? By default your stock system is read-only.
It was developed on Poco X3 NFC so it should work well with Poco X3 Pro I believe. Please report back if it works for you or not. Thanks!
hey lebigmac!
just got my x3 pro 2 days ago and it seems like i can debloat just fine using fastboot without using any scripts. even after multiple factory resets
on miui 12.0.4, bootloader still locked.
bought my device from malaysia
Hi xelrix. Congratulations on getting that wonderful device!
My script is useful if you want to remove stubborn system apps that are hidden deep inside your read-only system
You should apply for bootloader unlock as soon as possible. It's very useful if you are hard bricked you can always flash new super image from recovery or fastboot.
168 hours have passed so I successfully unlocked mine with miflash_unlock-en-5.5.224.55.
I look forward to install a Xiaomi.eu/mi-globe unless interesting Custom ROMs (signature spoofing enabled) come fast ;-)
From what I can see this is the situation:
Firmware
V12.0.4.0.RJUEUXM (Android 11.0 Europe) 2021-03-22 see https://xiaomifirmwareupdater.com/firmware/vayu/
Recoveries (Camerado)
OrangeFox-R11.0_5-Unofficial-vayu.img Apr 04, 2021 | 05:55AM
twrp-3.5.1-vayu-Thespartann.img (in Telegram group) Apr 03, 2021 | 06:58AM
kernel sources released Apr 8, 2021
xiaomi.eu_multi_POCOX3Pro_V12.0.4.0.RJUMIXM_v12-11.zip 2021-03-28
mi-globe for X3 Pro not yet online
Have not heard from Custom ROM devs
Elisa forwarded this in the Poco X3 Telegram group:
OrangeFox-Unofficial-vayu7.img (128.0 MB IMG)
this one boots fine and can wipe and flash etc (build from yesterday)
/data still broken (but you can format)
Click to expand...
Click to collapse
here is what i did from the very beginning
1 > fastboot flash recovery ofox_vayu7.img (#ofox in chat)
2 > fastboot boot ofox_vayu7.img (unplug usb when screen goes black and wait untill ofox is fully booted or else MTP dead)
3 > format /data (with yes confirmation)
4 > reboot recovery
5 > transfer files to internal via MTP
flash xiaomi.eu
6 > manually mount odm in recovery settings
7 > flash dfe (disable verity & encrypt)
8 > flash magisk
reboot to system
(6 & 7 is not needed now as we don't have rw permission)
and it ****ing booted (after 10 min wil look like miui logo is stuck (yes it seriously can take this long be patient))
Click to expand...
Click to collapse
xelrix said:
hey lebigmac!
just got my x3 pro 2 days ago and it seems like i can debloat just fine using fastboot without using any scripts. even after multiple factory resets
on miui 12.0.4, bootloader still locked.
bought my device from malaysia
Click to expand...
Click to collapse
Hi Xelrix, Can you tell us the steps to debloat properly. Thanks.
vaidhy2007 said:
Hi Xelrix, Can you tell us the steps to debloat properly. Thanks.
Click to expand...
Click to collapse
You can use this PC tool:
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
The way to install that tool is written here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mark up the app you want to remove and press Uninstall.
You can re-install those removed apps if you need them back.
Hi, I've debloated following these steps and the steps in the F1 & X3 NFC threads.
But my home screen and lock screen are both black.
What do I need to reactivate to restore the home & lock screens?
Thanks in advance
rfa31 said:
Hi, I've debloated following these steps and the steps in the F1 & X3 NFC threads.
But my home screen and lock screen are both black.
What do I need to reactivate to restore the home & lock screens?
Thanks in advance
Click to expand...
Click to collapse
Reinstall/ Enable the apps name with wallpaper or similar.
Then reboot phone.
pl1992aw said:
Reinstall/ Enable the apps name with wallpaper or similar.
Then reboot phone.
Click to expand...
Click to collapse
This worked.
Thank you
- Why downgrade?
If you found that UI 2.0 is performing poor than UI 1.0 then it is better to downgrade for long run
- Is it safe to use UI 1.0?
Yes and No, if you use carefully then UI 1.0 is safe.
Since UI 2.0 has 5th July 2022 Security(for C.13) patch comapred to 5th June 2021 (A.95) in UI 1.0, so more security is provided.
- Can able to update to UI 2.0 after downgrade?
Yes, we can get update to UI 2.0.
Rollback package is A.83, so you get A.95 update first.
When we are in A.95, we will get C.05 (UI 2.0) update.
After updating to C.05, we will get C.13 update which is the last update
Steps:
Make sure that you are in C.13 update, since I only tested this in C.13.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Download Rollback package from Realme Community post. This guide is extended version of that guide.
Rollback package is 3.10 GiB in size and it is resumable, so not a issue if you have less Internet. You can stop and resume in Download Manager(like 1DM) whenever you have Internet. Direct Download link is here
SHA256 sum of Rollback package RMX2189_11_OTA_0830_all_nii0ZtX4H67e.ozip is 3a2a5f0fb40621271240d3c3b31350916560616337fe58304af4056c8147672f
Put the downloaded package in Micro SD Card, since Internal Storage is wiped after flashing, so Rollback package will be deleted if you put in Internal Storage.
Click to expand...
Click to collapse
Backup your data in apps and Internal Storage to Micro SD Card or other places, since all of these are wiped in process
Charge the device upto 60% to be on safe side
Power OFF the device and hold Volume Down + Power keys together to boot to Recovery Mode
Click to expand...
Click to collapse
Choose Language English
Select Install from Storage -> From SD card -> RMX2189_11_OTA_0830_all_nii0ZtX4H67e.ozip
Click to expand...
Click to collapse
It will show a alert window to proceed or not. Choose OK.
Click to expand...
Click to collapse
Now, it will show a progress screen. Wait for upto 10 minutes
At the end of flashing it will show, Wiping, please wait and a prompt window showing Installation Successful will appear, Choose OK.
Goto Wipe data -> Format data. Enter verification code given there. An alert window telling, All user data will be reset will appear. Choose Format.
A popup window showing Wiped successfully will appear. Tap on OK. It will Reboot automatically.
Wait upto 2 minutes and setup your Realme UI 1.0 A.83.
You may get NVRAM Warning Err: 0x10 in WiFi, it is not a issue. You can ignore it.
Click to expand...
Click to collapse
Enjoy!
- How to remove update available notification
Remove com.oppo.ota and com.oppo.otaui apps by following https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
For those wondering if it is tested
I have personally tested this method and it works,
just follow the procedure given completely without skipping anything.
Also Thanks man for the simple guide .
I dont have an SD Card, I can do this using adb?
RehanRashid said:
I dont have an SD Card, I can do this using adb?
Click to expand...
Click to collapse
You can flash from Internal Storage also, but be aware that file will be removed when you Format the data after flashing.
HemanthJabalpuri said:
You can flash from Internal Storage also, but be aware that file will be removed when you Format the data after flashing.
Click to expand...
Click to collapse
Alright, Thanks. Yea no worries I have a copy of the ozip on my computer.
HemanthJabalpuri said:
You can flash from Internal Storage also, but be aware that file will be removed when you Format the data after flashing.
Click to expand...
Click to collapse
Btw I am going to flash Pixel Experience GSI Rom after cause bro Realme UI 2 sucked it was super laggy and literally everything would crash. Do you recommend me flashing this rom to ensure smooth experience and clean ui? (I have a Realme C12)
RehanRashid said:
Btw I am going to flash Pixel Experience GSI Rom after cause bro Realme UI 2 sucked it was super laggy and literally everything would crash. Do you recommend me flashing this rom to ensure smooth experience and clean ui? (I have a Realme C12)
Click to expand...
Click to collapse
I think so. Actually I am a Realme UI 1.0 user with locked bootloader. So can't suggest any of this things since I didn't used them much.
HemanthJabalpuri said:
I think so. Actually I am a Realme UI 1.0 user with locked bootloader. So can't suggest any of this things since I didn't used them much.
Click to expand...
Click to collapse
Edit: Well I won't recommend it to anyone. I think the Realme UI 1 interface is the best so don't bother flashing custom rom.
I'm using a Poco X4 Pro 5G and whenever I try to install a custom rom like ArrowOS or PixelExperience, I can't completely register my fingerprint to my device for security. I know it is not the hardware as the fingerprint sensor works on stock MIUI and Xiaomi.EU, both on MIUI 13.0.4.0.
Also to note, I am in Asia and my phone is the Global variant of the Poco X4 Pro 5G.
So you can just revert from a custom ROM to the stock ROM?
Same here. Works on MIUI but can't register fingerprint in custom ROMs. No idea why. Currently on pixel experience plus.
Apparently, if you switch your SELinux to permissive it fixes the problem, that's what I've seen for other users. Try using a magisk module to switch your SELinux mode.
Ritik17 said:
Apparently, if you switch your SELinux to permissive it fixes the problem, that's what I've seen for other users. Try using a magisk module to switch your SELinux mode.
Click to expand...
Click to collapse
Thanks so much. It finally works!
What module did you use?
Aren't there risks associated with permissive mode?
Thanks Ritik17 for the tip, that definitely worked!
To change SELinux from Enforcing to Permissive, here's what I did:
1. Root device. (By changing Magisk.apk to Magisk.zip then flashing through ADB sideload)
2. Install Terminal application from Play Store.
3. Typed "su" then allowed root access through Magisk.
4. Typed "getenforce" to get the SELinux status (in this case it reported "Enforcing")
5. Typed "setenforce 0" then pressed enter to switch SELinux to Permissive.
6. Typed "exit" to exit out of the root interface.
Afterwards, the fingerprint registration worked!
EDIT: The above steps, while allowing for fingerprint registration, basically makes it so that safetynet checks will always fail. Applying the safetynet fix makes it such that the fingerprints get deleted every after reboot.
EDIT 2: I noticed that while the lockscreen recognizes the fingerprints saved, the phone acts as if there are not biometric sensors enabled. My apps can't detect that I have enrolled fingerprints.
TNTS said:
EDIT: The above steps, while allowing for fingerprint registration, basically makes it so that safetynet checks will always fail. Applying the safetynet fix makes it such that the fingerprints get deleted every after reboot.
Click to expand...
Click to collapse
Try using Zygisk, Denylist and Magiskhide to pass the safetynet, you have to add Google Play services and Play protect (Enable "Show system apps" from 3 dot menu at the top right corner).
You can also use Cygisk, it's a Magisk alternative with some features built-in that were removed from Magisk.
The work is being done, eventually the problem will be resolved completely. If you want to help out then provide logs after using your fingerprint sensor to unlock the device. Reboot the device before recording logs so it's clean.
PE Telegram channel posted this image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ritik17 said:
PE Telegram channel posted this image
Click to expand...
Click to collapse
PE is the only one who added a /data/vendor_de/ rule to selinux. maybe they got it working in the update.
device_xiaomi_veux/file_contexts at c0427d7db3f8b0675dcfee8409ac139de2631f2a · PixelExperience-Devices/device_xiaomi_veux
Dependency of Xiaomi POCO X4 Pro 5G / Redmi Note 11 Pro 5G / Redmi Note 11 Pro+ 5G (veux) - device_xiaomi_veux/file_contexts at c0427d7db3f8b0675dcfee8409ac139de2631f2a · PixelExperience-Devices/de...
github.com
Ritik17 said:
Try using Zygisk, Denylist and Magiskhide to pass the safetynet, you have to add Google Play services and Play protect (Enable "Show system apps" from 3 dot menu at the top right corner).
You can also use Cygisk, it's a Magisk alternative with some features built-in that were removed from Magisk.
The work is being done, eventually the problem will be resolved completely. If you want to help out then provide logs after using your fingerprint sensor to unlock the device. Reboot the device before recording logs so it's clean.
Click to expand...
Click to collapse
Hi, I have the same problem. Install PixelOS and it doesn't allow me to use the fingerprint, it happens to me with any custom rom. I have used this method but Google Pay stops working.
I don't know what else I can do.
Thank you all
Fitatomalo said:
Hi, I have the same problem. Install PixelOS and it doesn't allow me to use the fingerprint, it happens to me with any custom rom. I have used this method but Google Pay stops working.
I don't know what else I can do.
Thank you all
Click to expand...
Click to collapse
Idem