So guys when I got my phone (around 1.5 years back), I didn't face any kind of ghost touch issues or image retention problems(till 1.2 years). But as soon as I unlocked bootloader and installed custom roms, I started facing image retention problem but no ghost touches. Then I installed MIUI again, but this problem was still there. So, I used Twilight to solve this problem. Then again I unlocked my bootloader and started flashing custom roms, and now I face ghost touches, screen freezes and image retention problems. Then again I installed MIUI latest version using Mi flash tool but still I was facing ghost touch issues. So I though of installing this MIUI version(the oldest one): beryllium_global_images_V9.6.14.0.OEJMIFD_20180730.0000.00_8.1_global
and after installing this the ghost touches are gone but the screen retention problem still persists(without Twilight fix).
So, is there any way to fix this retention problem by using some other MIUI version?
When I unlock the bootloader and flash custom roms over this version of MIUI: beryllium_global_images_V9.6.14.0.OEJMIFD_20180730.0000.00_8.1_global
then I never face any ghost touches or other problems, but as soon as I update the custom rom from TWRP, then again I face ghost touch issues. I even tried dirty flashing old firmware but it didn't work.
So I thought maybe its due to the MIUI version installed before flashing twrp and custom roms and somehow after updating the custom rom/flashing some other rom, the vendor/firmware is changed and this leads to ghosting and retention.
The problem is everything started when I started flashing custom roms 3 months back, before it was completely fine with MIUI. (And yeah I'm flashing MIUI and locking the bootloader correctly).
And I can't get my display changed as the phone is out of warranty.
Android 10
try some custom kernels like lawrun, they have the latest screen drivers. If it does'nt work wipe everything with TWRP and start fresh. I recomend MIUI.EU stable. it is better than official global ones, more features, less bloatware and more fixes. All AOSP roms are not 100% stable. Also, everytime you make some change in TWRP like wiping or installing something, make sure to reboot to recovery before proceeding.
Related
Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...
Hey, recently i've been having issues with the proximity sensor on my vince. This started a couple of days ago when i decided i wanna go back to miui from custom roms and i did a full fastboot reflash. So basically i flashed everything clean without locking the bootloader.
And now the proximity sensor went nuts. (it was working fine until i flashed the fastboot rom)
It works, but barely. I gotta put my finger really close to the screen for it to actually work. So if i'm in a call it's annoying, screen is staying on since my ear can't get that close to turn off the screen, unless i press it hard against my head.
I've tried recalibrating it from miui, i've tried flashing different version of miui rom (both in fastboot and recovery) with no avail.
Also, i've removed the tempered glass i had on it and i cleaned its surface.
Anyone had this issue? Can anyone give me some pointers?
attitude12 said:
Hey, recently i've been having issues with the proximity sensor on my vince. This started a couple of days ago when i decided i wanna go back to miui from custom roms and i did a full fastboot reflash. So basically i flashed everything clean without locking the bootloader.
And now the proximity sensor went nuts. (it was working fine until i flashed the fastboot rom)
It works, but barely. I gotta put my finger really close to the screen for it to actually work. So if i'm in a call it's annoying, screen is staying on since my ear can't get that close to turn off the screen, unless i press it hard against my head.
I've tried recalibrating it from miui, i've tried flashing different version of miui rom (both in fastboot and recovery) with no avail.
Also, i've removed the tempered glass i had on it and i cleaned its surface.
Anyone had this issue? Can anyone give me some pointers?
Click to expand...
Click to collapse
Try flashing the custom rom which you used before flashing the miui roms...it may work...
takke8 said:
Try flashing the custom rom which you used before flashing the miui roms...it may work...
Click to expand...
Click to collapse
Did that, i flashed a plethora of custom roms and nothing changed. I've read some stuff and maybe it's related to the persist partition, but i can't erase that in fastboot (something about image not being allowed to download), tho i can flash it. I've flashed the persist.img twice now, once with a developer stable rom and once with a simple stable rom. Still the same issue.
attitude12 said:
Did that, i flashed a plethora of custom roms and nothing changed. I've read some stuff and maybe it's related to the persist partition, but i can't erase that in fastboot (something about image not being allowed to download), tho i can flash it. I've flashed the persist.img twice now, once with a developer stable rom and once with a simple stable rom. Still the same issue.
Click to expand...
Click to collapse
Have you tried wiping the cache after the first boot of the rom (custom / miui)..?
If above doesn't work, try to turn off auto brightness(if enabled) and then check if the sensor works on call....
My phone freezes on every miui rom (fastboot flashed) (not rooted) ..only a forced reboot will fix this issue....ive tried disabling notch and many other methods ...it kept freeze atleast once a day.......this is the main reason i started flashing rom by unlocking the bootloader!!
Freezes only on stock miui!!
Its stable on every other rom. Im on PE+ latest right now!
Does anyone have this issue!
If there is any fix for this kindly share your thoughts
I have the same issue on MIUI, also looking for a solution other than flashing other custom rom. Miss the features from MIUI too much.
Edit even nonstock MIUI such as MIUI.eu freezes.
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.
Hi everyone. this is my very first post. I'm an Owner of a Redmi 6a (Cactus) Running Lineage OS 17.1 Unofficial (20200727) and I'm having some issues with the from so. first, I would like to know which Custom ROM Its better for this model now in 2022. more stable and updated. and also. if I can change the custom ROM to another without problems, just wiping some things ( I have TWRP and Bootloader unlocked already), or I have to get back to MIUI again.
I'm seeking something with the highest android version available for this model without problems like slow charging. camera stops or issues with daily usage, I would like to get my phone a little more powerful again.
Any suggestions, and comments, are well received by me.
Thanks to everybody
welcome to the dark side
so at the beginning i just tested some of the available costom roms, each for a few days (like go shopping) to get to know the functions and to see if they are stable (stable enough - because you can't find all bugs in short time). i am now using LineageOs but this is a personal preference. maybe i should go "shopping" again to see how the other costom roms have evolved over the past two years. as long as i did this testing i flashed all the roms "dirty", this means as you said, just wiping/formatting in twrp and flash new rom but as soon as i left testing and decided to use a rom for a longer period of time i did a "clean" flash. this means flash stock rom again (be careful to don't lock your bootloader again, its preselected in miflash unlock tool), then boot system, enable adb debugging, flash twrp, flash costom rom. i would say from experience that if you do a dirty or even clean flash, lets say you do it 10 times in a row, you will not always get the same result. maybe sometimes in LineageOs (at some devices) the radio is missing, sometimes it's not. sometimes you have a bug with a camera, sometimes you don't. flashing clean should reduce the error rate. this in the first place and the different region versions make it hard to help someone who has a device specific - rom specific - one in a hundred times bug - they need some help with.