Few days ago, while tinkering with my yu+, i decided to roll back to aosp kitkat (which came preinstalled). The ygpd flash was ok, except for the fact that my screen was all black (phone booted) and there was no yu logo. As usual, i booted to fastboot and flashed cm12.1. Booted, everything went fine only to notice that touch was not working properly. If i touched up it would register down. The main interesting thing was that, if i rebooted, the touch would work fine but as soon as i pressed the power button, it would malfunction. Same issue in twrp too.
These things mentioned below are the methods i tried to fix:
1) Flashing stock rom through YGPD again
2) Flashing stock rom through bootloader
3) Flashing rom through QFIL
4) Flashing stock touchscreen config though GptAdb Tool -reference link: https://forum.xda-developers.com/t/guide-fix-yureka-ao5510-touchscreen-calibration-issue.3488017/
As all hope was lost, i decided to contact our fellow hard working dev @abhishekt295
Back to the GptAdb tool, we tinkered and experimented all day, and found out that for some reason my yureka+ had the touch panel from "each" vendor, which comes with the yureka (AO5510), while the + variant( YU5510a) has the vendor "ofilm". They both have different values in their cfg.
Note: Check your touch firmware version in /sys/devices/virtual/touchscreen/touchscreen_dev/firmware_version file.
There are three vendors which are:
1) Each:GT970:0x1039
2) Ofilm:GT970:0x1039
3) Boen:GT970:0x1039:0x48
This post is applicable to those who have firmware version Each:GT970:0x1039
@abhishekt295 modified the cfg file, i flashed through gpt tool and DONE! My touch was back to normal.
Below is link for the modified cfg by @abhishekt295. You can find the tool and instructions in the reference link above, just be sure to use the cfg given here.
Link: https://androidfilehost.com/?fid=7161016148664782334
Endnote: While my device is working again, i would like to thank abhishek for his continuous efforts all day long. I gave up hope for my device, and was going to shell out money for new panel, but he didn't gave up and in the end fixed the issue. All credits to him.
Related
Hi guys
first, I apologize for my english
Two week ago, I has get started try KK mod on my device.
I encountred several problems, (the biggest was http://forum.xda-developers.com/showthread.php?t=2582142) but all successfully overcome...
...but last week,i had this new problem that seems to affect only my device ... in the world!
1 - Knock-ON has completely stopped functioning (but knock-OFF works perfectly!!!)
2 - five millimeters of the display (right side) does not respond to commands (following a perfectly straight vertical line, including nav-bar and status-bar)!!!
I tried to:
1 flash another ROM (stock, aosp, cm)
2 upgrade/downgrade with FlashTool
3 back to factory stock by LGMobile Support Tool -> options -> resolution update problems
4 upgrade/downgrade by flashing
5 all the recovery
6 all kind of advanced wipe
7 changing kernel (stock, stock-mod and mod)
8 sensor calibration
9 all the test in the hidden menu
...and more
NOTHING
Question: What do you think about flash manually all partitions?(http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions)
if this is a good idea, how I can flash, for example, tz.img or primaryGPT.img etc? What are their locations? I have to use the command fastboot or flashing by including the .img file in a .zip archive?
thank you all, my hopes are in your hands!:angel:
Hi, RomSwitcher has been nagging me to update since I installed it. So finally, I clicked Update.
Now my phone doesn't show the boot logo, it just boots into a blank screen. Adb seems to function:
C:\Unified_Android_ToolKit>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Anyways, if I ODIN any Perseus kernel, then my first ROM boots fine. But if I go into RomSwitcher and install the tools, then reboot boots into blackness again. I've tried to install the tools from the recovery, same thing happens.
I would post this in the Development thread, but I'm not allowed to post there yet. So as I understand it, RomSwitcher boots into it's own environment, changes some directories so one of several ROMS will boot. What seems to happen is that the RomSwitcher environment is just blank. I have no idea where to look, and I can't find the old version of RomSwitcher which worked anymore. I don't really want to reflash everything just to get RomSwitcher functionality back.
There's no information on the internet about how it works or how to fix it. It seems I've probably managed to wipe the configuration when updating it. If anyone can point me to a FAQ or Guide or something about how it works, or summarise it, I'll really appreciate it, as I don't really want to go and dig through the code to figure it out... that might take me several weeks with the little time I have available!
Questions:
What is in the configuration file?
Where is it stored?
Can I re-create it by hand?
What's the simplest way to get RomSwitcher working again, without starting from scratch with all my ROMs?
(I'm just dual booting Phoenix ROM and CM11, which worked fine until I updated RomSwitcher. New RomSwitcher looks good, but doesn't work!)
Thanks
Steps to repeat...
So, I've tried every Perseus kernel: 16, 18, 19
From the main TW based ROM that boots: Phoenix 10.1
RomSwitcher says to install Tools and Reboot before it does anything. Doing that reboots into a black screen, no matter what kernel. I've re-downloaded the main config and the tools several times.
Seems the only thing left to try is re-flash main ROM, re-install RomSwitcher... then it will probably work But that is a 3-4 hour operation I can't afford right now.
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
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.
Hello,
For the last few days I have been trying to update my phone (6T) to the latest version of custom rom Havoc [9].
Unfortunately with not much luck. There was something going wrong every time I tried.
I went back to stock with the fastboot version of mauronofrio and tried versions 2.7, 2.8 (Havoc) and there was always a problem with it. Face recognition didn't work, lag in video's.
So yesterday I went back to version 2.5 and it seemed to work. I just wanted version 2.7, so today I was updating it, not OTA, cause that never worked for me.
Now I am stuck on the part where the phone switches on (through volume up and power button). It shows the havoc splashscreen, but when it is on the last part of booting, the screen goes black and the phone seems to be off.
I have tried to go into fastboot, but nothing works. Same procedure, over and over again
sideload doesn't work, and neither is the fastboot to stock version, because there's no device detected.
Can somebody please help me
Dunno why, but after 2 hours waiting I tried again and it started up in fastboot. I was able to flash a mauronofrio version and got it back to life.
Flashed a Havoc ROM 2.7....and surprise, everything works, except the video lag. Looks like it has to do with sound, cause when I watch a small clip on Instagram, the video works fine. When i turn on the sound, the lag comes back.
Is it perhaps the OOS stock in combination with the version of Havoc?
When I download an original, latest version of stock OOS from the OnePlus website, and try to flash it, it gives an error.
Meh....this sucks
You may need to MSM back to stock and start over. Good luck