Hello, noob here.
I have a serious doubt after having had a replacement for the screen of my phone.
After receiving it, I noticed it was not an original replacement and there was a curious problem: whenever I powered on the phone the display showed very (seriously, VERY) yellowish. It didn't fix until I turned off the screen and turned it on again.
I decided to flash a ROM trying to solve it, but nothing was fixed. Until I flashed Oreo with MiFlash. Whenever I returned to Nougat with MiFlash the yellow screen appeared again.
These days I followed the procedure of flashing Nougat through MiFlash and then flashing LOS 15.1, the yellow screen remained. But if I flashed first Oreo (MiFlash) and then LOS, that problem did not exist.
So, my question is, is there something we are missing when we flash ROMs through TWRP or some other method (fastboot with @JamFlux tool for example) and not MiFlash?
Sorry for making the post so long, but I felt I had to explain everything in detail.
Your display might have some problems.
Roms shouldn't effect it in general. I would suggest you try voidkernel and play with KCAL settings.
alkesh95 said:
Your display might have some problems.
Roms shouldn't effect it in general. I would suggest you try voidkernel and play with KCAL settings.
Click to expand...
Click to collapse
No, sorry if I did not explain it well. ROMs do not change the display settings. What makes a difference is flashing ROMs through recovery or tools here in XDA (display remains yellow if I come from the Nougat November release) and flashing OTAs through MiFlash (display is not yellow anymore after flashing any Oreo OTA)
pabloespe02 said:
No, sorry if I did not explain it well. ROMs do not change the display settings. What makes a difference is flashing ROMs through recovery or tools here in XDA (display remains yellow if I come from the Nougat November release) and flashing OTAs through MiFlash (display is not yellow anymore after flashing any Oreo OTA)
Click to expand...
Click to collapse
That is a weird issue but its possible.
Sorry i couldn't help you much. As this falls out of my knowledge. Maybe someone else might look into it.
Related
after booting deadman twrp 3.1.1 on los 16.1, touch of my phone is not working, even in twrp..
afte that I flash stock oreo via MI flash tool.. but no result, same problem, touch wrong.. like mad, ,
any fix there >???
please some one help me... plz
I think you should select clean flash again while flashing rom through mi flash tool!
Facing same problem, clean flash did not help. Please reply.
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Bro, how about upgrade to Oreo? Is the touch still fixed?
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
Faced the same problem. I played with the firmware and stopped working the touchscreen. This tip rolled back to 7.1,2 helped. The phone began to work.
I updated it after the initial configuration and connection to the network, the phone itself downloaded the update and installed it. Updated to 8.1.0.
Thank you so much for sharing!
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
meet4300 said:
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
Click to expand...
Click to collapse
same problem how did you solved it ?
As my phone was in warranty, I was able to get it solved by replacing motherboard. Booting older versions of TWRP can get the touch working, this is suggestion is still to be tested. Try your luck if you can sort it out. In Pixel experience rom, there is an option of double tap to wake. I think thats the reason this fuss is all about. I think due to a different manufacturer, maybe our screens won't support it.
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Disable DT2W and voila, fixed.
I don't know what the problem is, but I know how to "fix" it.
diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Same problem. Did you make any progress?
leodoct said:
Same problem. Did you make any progress?
Click to expand...
Click to collapse
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
mikla90 said:
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
Click to expand...
Click to collapse
Well i found a solution for my case. The problem for me was the version of platform tools i used to lock-unlock boot-loader, boot the system and running any commands install HAL3 etc..
Every installation i did (firmwares, from nougat to oreo and last to pie) was executed with the platform tools latest windows version that boot.img had (14,888KB) size.
The version that my touch screen began to work again is the platform tools r.28.0.1.windows that had the boot.img (34,928KB) size.
When i booted the phone in fastboot mode, i opened platform tools r.28.0.1.windows and run the command "fastboot boot boot.img" the phone rebooted and the touch was working again I think that the boot.img file of this version is the correct to boot the phone normally.
Hope this helps....
fewome said:
i had the same problem with a new mi a1. After installing twrp and flashing lineageos the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When i flashed stock oreo with miflash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download miflash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official nougat rom (not oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with miflash 2017.7.20.0
after this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to oreo. I didn't even check the stock firmware when it arrived, because i didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
thank you sooooo much dude u saved my ********ing assssss!
ash roxx said:
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
Click to expand...
Click to collapse
Thank You .. You are a lifesaver
:good:
Mi A1 touch responds somewhere on screen
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
packpunk said:
Bro, how about upgrade to Oreo? Is the touch still fixed?
Click to expand...
Click to collapse
Please let me know if someone have solution. PLZ PLZ PLZ
I flashed latest rom pie/ oreo/naughut...but no luck.
I also hotboot recovery start but still touch lagging.
Plesae let me know if there is any solution.
Dear Xda Members I have Problem with my MI A1
I downgrade it to 7.1
Aflter Flashing clean all and relock its with MI flasher tool, My touch Screen misbehave, I try nought and oreo firmware (above mentions also) but problem cant solve
Please help me
Thanks
[if you install this firmware and make clean and relock so you need to unlock bootloader for OTA update]
Thanks You very much Dear your solution is working well.
I downgrade my cell for some reson from pie, when I clean Install and relock I face touch problem, I try manay official firmware but all wrost,
Then I try your shearing mathod, LOL WoW Its worked, I install this firmware then OTA 8.1 and then OTA 9.0 and then AOSP Ex on my cell now its worked fine!
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)
And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !
Hi,
I was on stock Pie firmware on mi a1. I tried to install twrp recovery in my device and somehow messed it up while flashing stock roms and all those things. Now my touch is not working properly. I can flash stock pie rom via fastboot method, but cannot go through setup process because my touch is a bizzare. I then tried to flash stock oreo and nougat firmwares and stuck in bootloop. I'm even tried booting into TWRP to see if anything would help, but the touch issue seems to affect twrp as well. Please help me out with this.
Thanks.
Do you fixed your problem? I don't know what happened but after I flashed the stock ROM the touch screen is useless. I already flashed everything in miflash and the screen is still broken... I don't know what to do, help pls
Hi!
I already fix a similar problem on my phone.
After a screen replacement, I had a touch-screen issue which was detecting the touches, but at a pseudo-random position.
The solution that worked for me was to flash the first stock nougat image released (September 2017 ), and then to upgrade to pie using the classical way through OTAs.
But you have to be very careful while doing this as you will encounter some kind of weird issues if you do this the wrong way, like lost IMEIs and some others that I don't remember.
You'll find some tutorial on how to downgrade from Pie to Oreo and then I don't remember well but I think you will be able to flash directly android one 7.1.2.
I hope this will solve your touchscreen issue (let me know if that worked for you or if you have any other problem occurring)
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.