LG G3s D722 touch screen no longer works after custom recovery - General Questions and Answers

Okay, so I was in the process of putting a custom ROM onto my LG G3s, however, as soon as I flashed in a custom recovery menu (TWRP) and rebooted my touch screen no longer works. The display screen itself is also darker and has "lines" in it, not really sure on how to describe it? I was using a version of TWRP that was "supposedly" supported on the G3s. My phone was running KitKat 4.3.2 I believe. . . With the G3s you have to do some kind of patch for the boot to be able to use a custom recovery without resetting the phone in the process, and I had done that. I know that was not the immediate cause of this problem for I used Flashify to flash the custom recovery. It worked all fine up until I rebooted the phone. I tried looking around, but didn't find anything that was even close to my problem. If someone could be of some help or provide some insight it would be much appreciated.

Related

[Q] Can somebody please help me (G2x)?

I was curious if anybody could help me. I have a g2x from Wind (p-999dw). I am pretty new to rooting and such but wanted to update my phone. I got it rooted successfully and then tried installing the CM7 Rom update. Backed up with cwm first and then continued. Now my phone is pretty f'd. Every time i try to turn it on it just hangs on the LG screen. I tried the flash recovery method with nv flash and was able to get a cwm recovery menu up but when i try loading the previous working setup, it says successful, i restart the phone and now i get the LG logo with the blue status bar below (which wasn't there before I used the flashing tool) it which moves for a few seconds, then freezes. I've tried every option in the menu and i still cant get past the LG logo screen. Can anybody help me? I've spent hours trying and can't seem find a way to fix it. Don't care if i lose all my data and apps just want my phone to work. Any help would be much appreciated. Thanks.

[Q] LG G2 Sprint stuck in bootloop, no recovery please help

Hey guys.
I'm new in the Android world and bought an LG G2 back in november.
I had originally intended to custom install cyanogenmod or KitKat 4.4 to replace stock rom, but I couldn't find a way to install a custom recovery, and was only able to root my device via Kingo Android Root.
A while later I saw an update that popped up, and not knowing any better I clicked install. It was about 114MB. That was about 3 days ago, and my LG G2 has been stuck in a bootloop ever since.
When I try to turn it on the LG logo shows up, then it says "secure booting error"and "Cause: boot certification verify" on the top left corner of the screen in white text.
I tried doing a hard reset, but that didn't work. I don't have a custom recovery so that I can clear the cache and data or something. So pretty much I have a bootlooped phone with no custom recovery, I can't do a hard reset, and it's Sprint and everything's new so it's harder to find a fix.
Does anyone here know of a way I can fix this? It would be much appreciated.
Thanks in advance

[SOLVED] XT1033 with 4.4.4 pre-installed has problem in rooting/custom recoveries

After searching for few days and trying different methods I came to the conclusion that there is an issue in rooting and flashing custom recoveries in XT1033 dual sim phones that were shipped with android 4.4.4 as default ( Most probably the ones sold in august 2014 in India )
In detail...
at least Im lucky because I could successfully unlock my bootloader, but for some the unlock code given by motorola gives " Password incorrect!/OEM unlock failure!" . This is the motorola forum dealing with that issue , more details are int he forum Bootloader Unlock Problems?
So, back to the point, This is the issue..
After successfully unlocking bootloader, I tried flashing custom recoveries, First i tried philz, but when i tried to enter into recovery, phone rebooted- it showed the bootlogo and then some a black blinking screen, the blinking is random, that screen remained until i long press on my power button which boots my phone in the normal way, after that whenever i try to select recovery, what i get is the black screen
This was the case all the recoveries except twrp . In that case, it showed black screen when tried to get into recovery, but if I wait for a minute, the screen times out and after waking up the display by pressing power button, what i see is the twrp recovery window saying "swipe to unlock " but unfortunately touch doesnot work, so i can not unlock it, therefore cannot use it
this issue is present only in phones XT1033 that was pre-installed with 4.4.4
I have tried almost all the recoveries, also tried modified recovery method from modaco
those who have OTAed from 4.4.2 to 4.4.4 were successful in running custom recoveries, but i couldn't find anyone with preinstalled 4.4.4 running a working custom recovery
anyway, somehow the root access can be obtained by sacrificing a working recovery
So, I post this,hoping someone will find a solution soon and if anyone has any feedback please share your suggestions and experiences
edit: problem solved
This is just to inform all those who got their phones with 4.4.4 pre-installed and were suffering from black screen when booted into recovery.
A new version of Philz recovery is released by its maintainer for moto G , which is compatible with the newest bootloader or baseband ( whatever )
Just go to Phil'z recovery and download the latest version ( only 6.57.5 or above )
Devs plz.
can any devs look into this issue, i guess every new motog users from india is facing this issue.. I found another one who bought motog today ( in india ) facing this issue, and many others too...

[Completed] Android stuck on boot screen and recovery doesnt work .

I recently installed custom rom on my phone then i downloaded twrp recovery manager or maybe it was rom installer in my android . Through one of those apps i installed custom boot screen then I decided to change it after few reboots because it was taking longer then the default boot screen so i deleted thought it would go back to default boot screen automatically so to check i restarted my device and phone got stuck at start up screen. I was trying to get my recovery back which wasnt working so i could install custom rom now the phone is stuck at start up and recovery doesnt work already what should i do to fix this epic problem i really dont want to lose my phone over custom roms lol ? Help would be much appreciated .
Thank you.
Hi,
You seem to have opened two(2) threads on the same subject.
Please look here for you assistance.
http://forum.xda-developers.com/general/xda-assist/phone-stuck-boot-screen-deleting-boot-t3019429
Thread closed.
Thanks,
BD619

LG G Pad 7.0 V410

Just wanting some advice (if any) to a white line issue I'm having with this tablet. I bought this tablet with Lollipop 5.0.1 already installed. I managed to get it downgraded, rooted, and currently have TWRP installed as well as CM12.1 nightly. The problem I have is that as soon as I install ANY custom recovery (TWRP or CWM recovery) it boots normally at first giving me the LG logo. Then, instead of getting the AT&T logo (or the CM custom boot animation), it gives me a series of white lines spamming from top to bottom of the screen. I know for a fact it has to be software related as when I return to stock KK everything boots fine, giving me the LG logo followed by the AT&T logo. I did NOT use the ADB method. Instead I downgraded using the LG Flash Tool, and a test KDZ file, which allowed me to install Flashify, then TWRP. My problem ONLY begins once I install ANY custom recovery. This process did not unlock my bootloader, however. Could this be my culprit, or would it be something else? Any help is greatly appreciated, and thanks in advance for any help/tips. More information is completely available upon request.
P.S. The white lines eventually disappear when the screen goes to sleep on it's own. I can then press the power button to wake the device which gives me the lock screen as normal. I just want to know if I can get the boot animation working. Everything else works fine.
You found cwm?

Categories

Resources