Touchscreen un-responsive after flashing Lineage lineage-16.0-20180812 - Nexus 9 Q&A, Help & Troubleshooting

Kinda newbie to the whole custom ROM world. I was recently given a NEXUS 9 that was unwanted. The device worked fine, just had a very old Cyanogenmod build. I updated it to the latest TWRP (3.3.1.0) and loaded lineage-16.0-20180812. The OS load fine but the touchscreen is unresponsive. I can't "unlock" the screen by swiping. No errors during install and I can still ADB and fastboot. Tried rebooting a number of times and went though the process to reflash..no luck. Any suggestions would be greatly appreciated.

jasonsamuel.email said:
Kinda newbie to the whole custom ROM world. I was recently given a NEXUS 9 that was unwanted. The device worked fine, just had a very old Cyanogenmod build. I updated it to the latest TWRP (3.3.1.0) and loaded lineage-16.0-20180812. The OS load fine but the touchscreen is unresponsive. I can't "unlock" the screen by swiping. No errors during install and I can still ADB and fastboot. Tried rebooting a number of times and went though the process to reflash..no luck. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
My opinion is: First,flash the stock rom , and then you can install the custom rom you want from the beginning with the correct way...

daitalos said:
My opinion is: First,flash the stock rom , and then you can install the custom rom you want from the beginning with the correct way...
Click to expand...
Click to collapse
This did not work for me

[email protected] said:
This did not work for me
Click to expand...
Click to collapse
I do not understand what exactly you mean
What is your problem on this device?

Related

problem solved....ignore post

edit - problem solved......
biggary said:
Hello there, long time member of XDA, but a new user of Honor 5x - Nice to see some devs create some nice roms....but I have a problem.....
I unlocked bootloader via the proper way, and its flashed, rooted etc, and its happily running the newest resurrection remix rom.....but.....
I went to download the great modaco roms by @paulobrien , done what was said, but the phone reboots, and it does the splash screen thing....and thats it....as far as it goes, I try leaving for half a hour, but still nothing......
sometimes i get the error in TWRP that /system cant be mounted, and although it flashes, when rebooting, it says NO OS installed, so i flash it again, and no error but, reboots and sticks at the 'HONOR' logo....
My model is L21, when i clean for a new rom, I advance wipe all sections except internal and external memory, and i also do a factory reset, as I have done with many many other phones
is there a step i am missing? i have read about swap - what is that?
All I want is a nice stock rom which i can debloat, install the htc home launcher, and a few useful apps.....
Who can help me???
Click to expand...
Click to collapse
If you wipe system before flashing the rom you get that error
don't wipe system the rom does it for you
to flash the rom after wiping the system choose reboot / recovery now the rom will flash
Arobase40 said:
"Honor 5x running Resurrection Remix Marshmallow"... ^^
Click to expand...
Click to collapse
@Arobase40 I know my Sig says runing RRemix, but what im asking for, is going back to a stock rom, i can flash any of the CM based roms, but have problems when returning to stock.

Moto E entering directly into the TWRP

Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Nikakz said:
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Click to expand...
Click to collapse
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Rajendran Rasa said:
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Click to expand...
Click to collapse
Guy
Ok, thanks I'll try
Nikakz said:
Guy
Ok, thanks I'll try
Click to expand...
Click to collapse
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Nikakz said:
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Click to expand...
Click to collapse
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
vyshak.sk said:
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
Click to expand...
Click to collapse
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Nikakz said:
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Click to expand...
Click to collapse
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
_sushan_ said:
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
Click to expand...
Click to collapse
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
You flashed latest twrp inside old twrp recovery itself?right?
Rajendran Rasa said:
You flashed latest twrp inside old twrp recovery itself?right?
Click to expand...
Click to collapse
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Nikakz said:
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Click to expand...
Click to collapse
Flash radio files. Google it for ur device.
_sushan_ said:
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Click to expand...
Click to collapse
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Nikakz said:
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Click to expand...
Click to collapse
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
_sushan_ said:
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
Click to expand...
Click to collapse
Okay, thank you, it stabilized the signal from the network operator. I will leave as is and will not make updates at the moment. I just want to know how to make the TV function work. Thanks everyone for the help and I do not know how to mark a topic as closed in the forum.

Need help, endless reboots

Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
jamesvmccann said:
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
Click to expand...
Click to collapse
PMd you.
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
jamesvmccann said:
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
Click to expand...
Click to collapse
No problem ?
Same Problem
I have the exact same problem. I flashed the LineageOS ROM, then flashed Fulmics ROM, then tried to go back to Lineage—and now every ROM just reboots endlessly, but I can boot into recovery and access TWRP just fine.
It looks like jamesvmccann found a fix, by "completely wiped everything and [then] flash[ing] just the stock 7.0 lg bootloader." I'm afraid I don't know where to download the stock 7.0 lg bootloader. This is a h830, so that may matter as well.
Any additional help would be greatly appreciated.
Managed to fix this problem myself
The stock h830 bootloader was linked in this forum post.
I booted into TWRP and flashed the stock bootloader. It has a different bootflash.
H850 keeps booting into Recovery
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
KCKitsune said:
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
Click to expand...
Click to collapse
I had same problem factory reset few times within twrp seem to work after a while. I take it your backup not working? If all else fails flash kdz in lgup
Sent from my LGE LG-H830 using XDA Labs

GApps error after installing custom ROM

So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2

Touchscreen Completely Stopped Working After Boot TWRP

Hello friends. Yesterday evening I was going to flash my phone to stock rom. I opened twrp and the touch problem that I had encountered again. I reset the program again and again by holding down the power button, but it has not been worked. then my phone remained open in twrp. This morning I flashed my phone miui beta on miflash. (Android 8.1 9.6.24) The phone is switched on, but the touch issue still not working. If you could help with this situation, I would greatly appreciate it. Thanks.
Use otg mouse and format data, then install again nee rom or oficial miui
atakrkc said:
Hello friends. Yesterday evening I was going to flash my phone to stock rom. I opened twrp and the touch problem that I had encountered again. I reset the program again and again by holding down the power button, but it has not been worked. then my phone remained open in twrp. This morning I flashed my phone miui beta on miflash. (Android 8.1 9.6.24) The phone is switched on, but the touch issue still not working. If you could help with this situation, I would greatly appreciate it. Thanks.
Click to expand...
Click to collapse
use this twrp for touch issues
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
also use latest Franco kernel having different touch drivers! or Optimus drunk kernel
more oever Twisted kernel releases 3 variants on 3 types of touch drivers ,
you should find them in the developer section and try!
i have same issue i have factory reset using fastboot the display is working but touch isnt working ..
Use an otg cable in Twrp, install another kernel, this has already happened to me and the exchange of the kernel stock for a custom one worked
An unknown said:
Use an otg cable in Twrp, install another kernel, this has already happened to me and the exchange of the kernel stock for a custom one worked
Click to expand...
Click to collapse
OMG! Thank you so much! This tip worked for me and I could fix my screen issue. Thank you very much )))

Categories

Resources