Related
Hi guys,
about a week ago my rooted P9 with Lineage 14.1 crashed and was stuck in the boot screen for hours. I waited until it completely discharged and tried rebooting again but that didn't help either. The only way I could resolve this was to boot to recovery (TWRP) via fastboot and do a factory reset. After that it worked just fine except for setting up fingerprints.
In the settings menu there were no fingerprints set up and I couldn't register fingerprints from the fingers I previously had registered, but I could add a fingerprint I haven't used before. After that, however, all the old fingerprints still worked to unlock the phone even if they don't show up in the settings menu.
Do you know where these old fingerprints are stored and how to delete them manually?
Thanks for the help!
Suggesting to report custom ROM issues under the corresponding custom ROM threads - higher chance that somebody who is familiar with the particular custom ROM can spot and help
zgfg said:
Suggesting to report custom ROM issues under the corresponding custom ROM threads - higher chance that somebody who is familiar with the particular custom ROM can spot and help
Click to expand...
Click to collapse
Thanks, I'll try that.
Hello,
First firmware I was using was Chinese firmware and it worked fine (OTA was updated to 10.3.17). I used it until I got permission to unlock my bootloader. Then every other firmware from Mi or Xiaomi.eu have this problem. I cannot calibrate compass - in compass application or maps app my direction is spinning all the time counter-clockwise. Spin speed is ~5 spins in 3 second. Tried to clean compass app cache - do not help.
Tried to test sensors - in "all specs" click 5 times on Kernel and enter CIT. Result - Accelerometer looks working fine, Gyroscope - Z axis shows -7 all time, Magnetic sensor - spins counter-clockwise all the time.
My bad I have formatted all system before flashing firmware, that may get lost of original "persist" and "vendor" images if they are required.
Summary - looks like gyroscope sensor is failured - Z axis shows -7 rad/s all the time and that makes some functions hardly usable. Compass included.
Phone did not had any drops all the time. Only magnetic car holder was used, but cannot remember it happened same day. It was used with previous phone too and it still worksfine.
I have tried many Cn stable Roms, Indian roms, EEA, Xiaomi.eu. Installing in fastboot mode. No one firmware works fine with compass application.
Several fastboots tried:
Code:
raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea
raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in
raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn
Recovery ROMs tried:
Code:
xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip
xiaomi.eu_multi_HMK20ProMI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip
Maybe you can suggest any possibility to fix this? I assume that should be software issue.
Did you ever flashed Q or Downgraded from Q to P?
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
Did you ever flashed Q or Downgraded from Q to P?
Click to expand...
Click to collapse
Originally was Android 9. My first ROM flashed was Xiaomi.eu V10.4.4.0 - Android Q. Later tried Android 9 and Android 10.
I have just tried to install Lineage ROM over Stable CN 10.3.17 ROM - it misses compass app, but random app from net shows that compass works good. I mage a backup of all partitions. Maybe it is possible to restore some partition over working Xiaomi.eu ROM to keep Miui working and make compass work too?
Aliosa007 said:
Originally was Android 9. My first ROM flashed was Xiaomi.eu V10.4.4.0 - Android Q. Later tried Android 9 and Android 10.
I have just tried to install Lineage ROM over Stable CN 10.3.17 ROM - it misses compass app, but random app from net shows that compass works good. I mage a backup of all partitions. Maybe it is possible to restore some partition over working Xiaomi.eu ROM to keep Miui working and make compass work too?
Click to expand...
Click to collapse
Like others, most probably you broke your device sensors while downgrading. Do a clean restore of Android Pie with a fastboot image. Extract the persist.img from the fastboot package and flash it to the persist partition through LR TWRP. Reboot and Calibrate your front Camera and let other sensors Calibrate aswell. Do a hardware test (*#*#64663#*#*) and you should be able to see values for x,y,z axis for most of the sensors. If the compass still doesn't work, you might have a defective item.
Sent from my Redmi K20 Pro using Tapatalk
Redmi K20 Pro persist backup required
I have tried steps you suggested and works everything except Gyroscope. As before. I have made testing using Sensors Multitool. Rotation vector Z is swinging from -1 to 1 all the time even if phone is still. Gyroscope info shows Z axis always -7 or more. Gravity reacts to movement, but unnatural. On Q everything worked until downgraded back to P.
I have found useful topic about this problem - https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904 . Reading through maybe will find something useful for my phone. I have never rooted my phone. Used Magisk few times. Persist.img I used was from Android 9 Chinese ROM 10.3.16 (As my phone is Chinese version). Persist.img was installed only with TWRP, it showed no problem when processed it.
Maybe someone can share backed up persist partition of Redmi K20 Chinese version? Hardware version in "All specs" page shows "Hardware version: V1". I got instruction to retrieve it. The following should put an image of the persist partition on the phone's internal storage. It should be executed on TWRP from Advanced > Terminal window.
Code:
dd if=/dev/block/by-name/persist of=/sdcard/persist_backup.img
I have made md5 checksums of all persist.img I have in each firmware. Despite file size is same, content each time is different.
Code:
7d75bd5108cf8407431033a96c9da195 *d:\temp\Xiaomi\raphael_global_images_V10.3.2.0.PFKMIXM_20190911.0000.00_9.0_global\images\persist.img
35c6ae0b8ddfffaa2f77525f7d4dc57b *d:\temp\Xiaomi\raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn\images\persist.img
80115db34f9af4b8a4a105dc675f7fa0 *d:\temp\Xiaomi\raphael_images_V10.3.17.0.PFKCNXM_20190816.0000.00_9.0_cn\images\persist.img
a7fb2b49e181096e3345b64b1982b990 *d:\temp\Xiaomi\raphael_global_images_V10.3.1.0.PFKMIXM_20190805.0000.00_9.0_global\images\persist.img
3283790361d575e355929f995c904d23 *d:\temp\Xiaomi\raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea\images\persist.img
2ceeb38f7ca1c32afe6d842d2e9f0ed4 *d:\temp\Xiaomi\raphael_images_V10.3.16.0.PFKCNXM_20190718.0000.00_9.0_cn\images\persist.img
a9e78a1299431e19de73a847c22bc7cc *d:\temp\Xiaomi\raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in\images\persist.img
b979fadaae21f397f4f1f46282305248 *d:\temp\Xiaomi\raphael_images_V10.3.15.0.PFKCNXM_20190709.0000.00_9.0_cn\images\persist.img
dad5c8526ae0c598b31a6c58184bb81b *d:\temp\Xiaomi\raphael_images_V10.3.11.0.PFKCNXM_20190619.0000.00_9.0_cn\images\persist.img
40ddaa6840e63bdf6d04bfb84352bf56 *d:\temp\Xiaomi\raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn\images\persist.img
fff3410c7cf4c3cb5f5490b1dc252c3f *d:\temp\Xiaomi\raphael_images_V10.3.7.0.PFKCNXM_20190528.0000.00_9.0_cn\images\persist.img
03a89f80aa1f3804c03403aa9bdace29 *d:\temp\Xiaomi\raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn\images\persist.img
User which requires sensors fix should do following:
1) Open root shell
2) dd if=/dev/block/by-name/persist of=/sdcard/persist_backup.img
3) Copy new persist.img to your sdcard home directory
4) dd if=/sdcard/persist.img of=/dev/block/by-name/persist
5) Reboot device
Click to expand...
Click to collapse
So, maybe someone with K20 Pro CN version can share their persist.img file with me and others?
Hey, I have the same problem and this is getting me crazy. Have you solved the problem?
No, I got tired trying and now use phone with this problem. I get to much effort live without my new phone as I need on my daily life. Lineage os is not interesting to me too use for working sensors but without miui.
Aliosa007 said:
No, I got tired trying and now use phone with this problem. I get to much effort live without my new phone as I need on my daily life. Lineage os is not interesting to me too use for working sensors but without miui.
Click to expand...
Click to collapse
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
Ok, please returns here after your try and let us know you got sensor fixed
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
hmmm i am seeing a pattern , where many had problems after flashing roms , odd , anyway how to tell needle on the app is really facing north ?
It occurs also on my Mi 9T Pro with official global ROM... Compass spins constantly over Z-axis. It is especially visible for instance in Google Maps and annoys a lot. I think I will wait till MIUI 11 release and then maybe return this phone unless it will recover.
mykel_s said:
It occurs also on my Mi 9T Pro with official global ROM... Compass spins constantly over Z-axis. It is especially visible for instance in Google Maps and annoys a lot. I think I will wait till MIUI 11 release and then maybe return this phone unless it will recover.
Click to expand...
Click to collapse
Yes, looks like it occurs with officials ROM too if ROM was uploaded by FASTBOOT mode. Stock sensor settings gets rewritten with universal settings which do not work as desired.
Yes it seems so. The worst thing is that, it was working just fine at the very beginning, compass was lost just few weeks after I bought the phone
In the meantime maybe there were two official OTA updates, nevertheless I cannot recall what could cause loss of this functionality.
Thanks for your comment anyway.
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
Hi, weekend had passed. Did you tried to fix your K20 pro with your friends phone`s help? It is very interesting how it gone
maybe someone with K20 Pro CN version can share their persist.img file with me and others?
Aliosa007 said:
Hello,
First firmware I was using was Chinese firmware and it worked fine (OTA was updated to 10.3.17). I used it until I got permission to unlock my bootloader. Then every other firmware from Mi or Xiaomi.eu have this problem. I cannot calibrate compass - in compass application or maps app my direction is spinning all the time counter-clockwise. Spin speed is ~5 spins in 3 second. Tried to clean compass app cache - do not help.
Tried to test sensors - in "all specs" click 5 times on Kernel and enter CIT. Result - Accelerometer looks working fine, Gyroscope - Z axis shows -7 all time, Magnetic sensor - spins counter-clockwise all the time.
My bad I have formatted all system before flashing firmware, that may get lost of original "persist" and "vendor" images if they are required.
Summary - looks like gyroscope sensor is failured - Z axis shows -7 rad/s all the time and that makes some functions hardly usable. Compass included.
Phone did not had any drops all the time. Only magnetic car holder was used, but cannot remember it happened same day. It was used with previous phone too and it still worksfine.
I have tried many Cn stable Roms, Indian roms, EEA, Xiaomi.eu. Installing in fastboot mode. No one firmware works fine with compass application.
Several fastboots tried:
Code:
raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea
raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in
raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn
Recovery ROMs tried:
Code:
xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip
xiaomi.eu_multi_HMK20ProMI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip
Maybe you can suggest any possibility to fix this? I assume that should be software issue.
Click to expand...
Click to collapse
Even mine was screwed up..I taught I'll have to take it to service centre ....I had formatted system ...and when I installed fastbiit ROM..the gyroscope and accelerometer was not working.. unfortunately I had relocked my bootloader and had to wait for 30 days to flash persist file....so I just gave factory reset from settings a try..and it worked
vichucoolics said:
Even mine was screwed up..I taught I'll have to take it to service centre ....I had formatted system ...and when I installed fastbiit ROM..the gyroscope and accelerometer was not working.. unfortunately I had relocked my bootloader and had to wait for 30 days to flash persist file....so I just gave factory reset from settings a try..and it worked
Click to expand...
Click to collapse
You did factory reset from ROM version you have uploaded via FASTBOOT earlier and that worked? What persist file you have used? And how compass functionality - works? Fastboot ROM version accelerometer works fine, but compass fails.
Aliosa007 said:
You did factory reset from ROM version you have uploaded via FASTBOOT earlier and that worked? What persist file you have used? And how compass functionality - works? Fastboot ROM version accelerometer works fine, but compass fails.
Click to expand...
Click to collapse
At first my gyroscope also wasn't working....I didn't flash any persist file but now I can see that the compass is buggy... And also the video recording is buggy.... Hope after flashing miui 11 upcoming update it fixes things
I have the same issue. Don't know how to fix it. Am already using miui 11
You are good to go: https://forum.xda-developers.com/k20-pro/help/auto-rotation-issue-custom-roms-t3983169/page2
Let me know if I helped you...
Hey!
Ive been noticing an issue with my device, since I think the update to MIUI 11 (but not sure).
Description:
- The compass (and other apps using compass like Google maps) gives incorrect readings, when put horizontally. When put horizontally and kept still, the compass will spin regularly ca 2 degrees per second completely independent from the actual pointing direction. When the phone is kept vertically the compass works normally. I have made a video displaying the correct reading when vertically, and the spinning when kept horizontally: https://youtu.be/xgC4fHqH4Ys
- When checking the underlying gyroscope functionality with "Sensor Multitool", I have come across what I think is an erratic z axis reading. When I spin the phone randomly, the gyroscope in the x and y axis registers adequate readings, but the z axis stays completely flat. I have produced a video showing this behavior: https://youtu.be/1dY_xdF5Nz8
I have found this thread from Aliosa007 ( https://forum.xda-developers.com/showthread.php?t=3972249 ) that describes a very similar issue, but this user had recently flashed a new rom and the problem is attributed with the flashing. The users there assume the issue being a corrupt persist.img and most problem solving techniques involve flashing etc. But my phone is locked and not rooted. Could I also have received a corrupt persist.img during the normal update process recently to MIUI 11.
Currently trying to figure out, what the best way forward is. Wait and hope that this will be fixed with the next update or go the warranty route?
Thanks for helping me out with this one!
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Tistou52 said:
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Click to expand...
Click to collapse
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
schnodda123 said:
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
Click to expand...
Click to collapse
Hey,
well I couldn't really tell if it's related to an update : I got my mi 9T pro like two or three weeks ago and updated to 11.0.3 the day I got it...
The weird thing is that I noticed the problem one first time, and then two or three days later the issue solved itself without me doing anything particular and my compass started working normally again... And then two or three days ago it started spinning continuously again... I just hope it's software related and not an hardware issue...
I think I'm just going to wait for the next system update and if doesn't solve the problem I may send the phone back (but I don't wanna ... The phone otherwise is so great...).
I'll update the thread if I find something.
Good luck
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
hoopsnake said:
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
Click to expand...
Click to collapse
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
schnodda123 said:
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
Click to expand...
Click to collapse
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
hoopsnake said:
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
Click to expand...
Click to collapse
Sorry sir, but i think you cannot flash persist.img thru fastboot, because it read-only partition ,
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Tistou52 said:
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Click to expand...
Click to collapse
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
schnodda123 said:
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
Click to expand...
Click to collapse
Hola @schnodda123, ¿Logaste darle solución? No he podido arreglar mi eje z en mi caso en un Redmi Note 8, estoy algo incomodo, si bien el celular funciona bien el tener el sensor mal es fastidioso
Hi @ schnodda123, Did you manage to give it a solution? I have not been able to fix my z axis in my case on a Redmi Note 8, I am somewhat uncomfortable, although the cell phone works well, having the wrong sensor is annoying
Hi everyone
I Update my MI 9 Global to android 10 ( MIUI 11.0.6 Stable QFAMIXM) but after setup finish and phone rebooted the touch screen dont work any more.
one month ago my phone touchscreen broke and replaced and worked great before update (android 9 on MIUI 10.2 I think )
but after update it does not react at all . i installed custom recover twrp and installed new rom from xiaomi.eu but nothing changed. :crying:
I connect optical mouse throw otg cable to phone and every thing works normal. sound , network , wifi , bluetooth , camera , .... all work great but touch screen doesnt respond .
I think the problem is kernel dont load driver for touchscreen properly or the new android dont load firmware for touchscreen.
it is dmesg output :
https://pastebin.com/i4Cfyden
if you look at dmesg log you can see some line with error like :
"Firmware in the chip different from the one that was burn! " and "fts_fw_update: firmware update failed again! ERROR 82080B02"
please help me to solve this problem . if I have to use custom kernel or change and compile the driver for new touchscreen ??
based on dmesg log (Read FW from BIN file st_fts_f1.ftb !) firmware must be in file "st_fts_f1.ftb" but I cant find this file in phone memory. I have root access to phone and searched all folder ( including vendor and persist partitions )
Just flash the previous Android version that worked. It sounds as if you bought an aftermarket screen with different hardware.
invisiblewave said:
Just flash the previous Android version that worked. It sounds as if you bought an aftermarket screen with different hardware.
Click to expand...
Click to collapse
hi thanks for your answer. I guess you are right. My Touch screen Replaced and this new hardware does not detected by kernel or need new firmware . I want to know haw can I include it in kernel .How the old vesrion can detect replaced touch screen but new one cant ?? Please Any one exprienced in Kernel Development help me to solve this problem . I dont want to downgrade to android 9 :crying:
I still have problem with android 10 roms . I install several different roms ncluding unofficial lineage 17.1 , Xiaomo.eu rom , MIUI Global 11.06 and ... but none of them detect touch screen even in twrp recovery there is no touch screen and had to use optical mouce to install and test new rom .
I currently downgrade to android 9 ( MIUI Global 10.2.14 ) and everything works normal . If anyone like me have problem with android 10 roms ? please help
MiFlash a stock Android 10 ROM
badaas said:
MiFlash a stock Android 10 ROM
Click to expand...
Click to collapse
thanks for reply:good:
I already download and installed Fastboot stock rom ( cepheus_global_images_V11.0.6.0.QFAMIXM_20200420.0000.00_10.0_global )
But again touch screen dont work . If flash using MiFlash is different from Fastboot instal ?
Yes miflash does some lower level format install
badaas said:
Yes miflash does some lower level format install
Click to expand...
Click to collapse
Ok I will check this method and report you . thanks for your suggestion
badaas said:
Yes miflash does some lower level format install
Click to expand...
Click to collapse
Hi . I flash v11.06 using miflash and again tuch screen doesnt work . I checked clean all option in flash page
I Installed android 10 GSI Rom from https://github.com/phhusson/treble_experimentations and touch screen and finger print sensor start to work !!
but GSI have some problem and limitation for mi 9 for example battery is not so good and full screen gusttures dont work. how is possible touch screen works with this rom but not by official Android 10 ?? If i can use some part of GSI with Official or Xaiomi.eu roms to enable touch screen ?
Maybe pocket mode is interfering on stock ROM?
Try a old stock Chinese ROM?
Start from very old..
badaas said:
Maybe pocket mode is interfering on stock ROM?
Try a old stock Chinese ROM?
Start from very old..
Click to expand...
Click to collapse
How Can I test that ? And yes all android 9 ( official or xiaomi.eu ) work but have some minor finger print problem . But The only Android 10 that has not problem with touch screen is GSI rom even GSI v220 ( based on android 10 ) works . I dont know how this is possible ? I based On this I am sure the problem is software not hardware . A question Sir : If touch screen driver in Kernel (boot.img) or in vendor ? I think If I can merge vendors or kernel from android 9 with system and other from android 10 the problem is solved. Thank you and Please any Of your help and info can solve the problem
I have the same problem, Mi9 running MIUI10 Global, want to upgrade to MIUI11 but after update the touchscreen doesn't work, only via otg USB mouse. Tried to flash MIUI12 ia TWRP, again touchscreen doesn't work.
Have you solved the problem?
Same problem
Guys, has anyone managed to solve this problem?
Mi 9 After changing the screen the touch locks after a few minutes of use
My Mi 9's screen broke and I had to change it, but after a few minutes of use the touch simply stops working.
It happens a lot when I lock the screen, and I try to unlock it after a while.
Guys, I've been looking for the solution for some time but I just don't think so. I even found some forums saying to downgrade to version V10 but I still have this problem.
The screen is original, imported from CHINA and is of high quality.
Has anyone had this problem and can share the solution?
richnbeauty said:
I have the same problem, Mi9 running MIUI10 Global, want to upgrade to MIUI11 but after update the touchscreen doesn't work, only via otg USB mouse. Tried to flash MIUI12 ia TWRP, again touchscreen doesn't work.
Have you solved the problem?
Click to expand...
Click to collapse
unfortunately i dont find any solution yet. and i think no one is kind enough to help us . Now I am sure it is kernel problem. i installed GSI android 10 on android 9 vendor and touch screen works great ( but have some other problem with GIS like cant recieve or send sms messages) So the problem Is kernel used in android 10 . even i installed Quantic-Kernel on aosp and after that again touch screen stop working.Please if any senior member who is familiar with android kernel help us to compile or change touch screen driver used in version 9 and solve the problem . Please Please
br.tgo said:
Guys, has anyone managed to solve this problem?
Mi 9 After changing the screen the touch locks after a few minutes of use
My Mi 9's screen broke and I had to change it, but after a few minutes of use the touch simply stops working.
It happens a lot when I lock the screen, and I try to unlock it after a while.
Guys, I've been looking for the solution for some time but I just don't think so. I even found some forums saying to downgrade to version V10 but I still have this problem.
The screen is original, imported from CHINA and is of high quality.
Has anyone had this problem and can share the solution?
Click to expand...
Click to collapse
Are You using android 10 or 9 ? I think your problem is different because My touch screen dont work AT ALL after upgrade to android 10 . but in android 9 there is no problem
br.tgo said:
Guys, has anyone managed to solve this problem?
Mi 9 After changing the screen the touch locks after a few minutes of use
My Mi 9's screen broke and I had to change it, but after a few minutes of use the touch simply stops working.
It happens a lot when I lock the screen, and I try to unlock it after a while.
Guys, I've been looking for the solution for some time but I just don't think so. I even found some forums saying to downgrade to version V10 but I still have this problem.
The screen is original, imported from CHINA and is of high quality.
Has anyone had this problem and can share the solution?
Click to expand...
Click to collapse
hamedpc007 said:
Are You using android 10 or 9 ? I think your problem is different because My touch screen dont work AT ALL after upgrade to android 10 . but in android 9 there is no problem
Click to expand...
Click to collapse
I'm using android 9. But even so, it keeps crashing.
br.tgo said:
I'm using android 9. But even so, it keeps crashing.
Click to expand...
Click to collapse
You can install new Rom and see if the problem gone or no . I recommentd you install new stock android 10 with MIUI 12 or xiaomi.eu rom .
If after new install problem exist it may be some hardware problem . Even before install new rom you can reset factory your phone and see what happens ( backup up your data before reset factory)
hamedpc007 said:
You can install new Rom and see if the problem gone or no . I recommentd you install new stock android 10 with MIUI 12 or xiaomi.eu rom .
If after new install problem exist it may be some hardware problem . Even before install new rom you can reset factory your phone and see what happens ( backup up your data before reset factory)
Click to expand...
Click to collapse
Right. Dude, thank you very much for your help. As I live here in Brazil, there is almost no content talking about this error. Thank you one more time!!
Has anyone experienced something like this? It’s happening on my Xiaomi K20 Pro after I just updated it to MIUI 12 directly from the settings app
here's a video: youtu.be/ Mv-Qbgb0rR8 (I don't know where else to post this video, but I'm not allowed to post links)
Just in case the video wasn’t very clear, basically when I try to boot everything seems to boot fine to the lock screen, but if I try to unlock the phone with my pin it will just go back to the boot screen again, if I click on the emergency button it also does the same thing and if I just wait a little bit the same thing happens too.
It kinda reminds me of that wallpaper bug that bricked people’s phones, but I didn’t have any problems in MIUI 11 and my wallpaper is from the Google wallpaper app so I don’t expect that to be the problem.
I think it might be because my phone is running the international/global Rom instead of the original rom? I bought this phone used, and the software is saying that its a Mi 9T Pro instead of K20 Pro.
Can someone help me solve this? Or would I need to just factory reset? The phone is also already unlocked, so I was able to back everything up via a custom recovery, but reinstalling and setting everything back up again is just going to take a while, so maybe someone can help?
Maybe I could do something from the custom recovery (currently using orangefox recovery) to save this? I really don't want to factory reset
yes i am facing the same issue
At this point I wouldn't hold much hope on avoiding a clean install.
If you can access the data OK in TWRP/OF, I would suggest backing up your personal data, then try the following.
Dirty flash the MIUI 12 recovery ROM again.
If that fails, clean flash the MIUI 12 recovery ROM.
If that fails, clean flash the MIUI 12 fastboot ROM.
Personally myself, I would go straight to flashing the fastboot ROM, as it's the option almost guaranteed to work.
You can also try to factory reset your phone. Do you have TWRP?
M.isa said:
Has anyone experienced something like this? It’s happening on my Xiaomi K20 Pro after I just updated it to MIUI 12 directly from the settings app
here's a video: youtu.be/ Mv-Qbgb0rR8 (I don't know where else to post this video, but I'm not allowed to post links)
Just in case the video wasn’t very clear, basically when I try to boot everything seems to boot fine to the lock screen, but if I try to unlock the phone with my pin it will just go back to the boot screen again, if I click on the emergency button it also does the same thing and if I just wait a little bit the same thing happens too.
It kinda reminds me of that wallpaper bug that bricked people’s phones, but I didn’t have any problems in MIUI 11 and my wallpaper is from the Google wallpaper app so I don’t expect that to be the problem.
I think it might be because my phone is running the international/global Rom instead of the original rom? I bought this phone used, and the software is saying that its a Mi 9T Pro instead of K20 Pro.
Can someone help me solve this? Or would I need to just factory reset? The phone is also already unlocked, so I was able to back everything up via a custom recovery, but reinstalling and setting everything back up again is just going to take a while, so maybe someone can help?
Maybe I could do something from the custom recovery (currently using orangefox recovery) to save this? I really don't want to factory reset
Click to expand...
Click to collapse
Facing the same issue now. How did you solve it? I also have the Google wallpaper and just updated