Hi All,
I recently started having a problem with my G2. Upon a reboot, I noticed that the digitizer was not working. None of my touch was recognized, not even the home/menu/back/search area. I powered down the G2 and rebooted, and again the same thing. I disconnected the battery, removed the SIM and SD Card, and tried again after a few hours. This time it worked. Rebooted again, no go. Strange, right?
I thought it might be a faulty digitizer, so I replaced it with a new one. Same problem persists.
The weird thing is that I have figured out after about ~25 reboots, it works again. And once the digitizer works on reboot, it works fine until the phone shuts down, so I just keep it on as long as I can. If the battery dies or I have to reboot, then I have to reboot about ~25 times before it works again - then the cycle continues - I keep the phone on as long as I can until it powers down - reboot with the digitizer not working, ~25 reboots later, the digitizer works again. It's freaking annoying.
So, my question is...if the digitizer is not the issue, where could the problem be? I have tried flashing different ROMs, they all exhibit the same issue.
Any help would be appreciated - I really love this phone and don't want to upgrade yet.
First thing that came to mind was the faulty digitizer... But on further ponering, maybe its not the digitizer, but the ribbon cable. Try replacing it. That could be the cause f your issues. Hope i helped.
Sent from my HTC Desire Z using xda premium
The digitizer part included the ribbon cable, so when I replaced the digitizer, I also replaced the cable. It is too weird. If the digitizer or cable was bad, I would expect the digitizer to behave erratically during the times when it does work, but as long as the phone doesn't power off - it works fine!
My suspicion is that it could be some kind of software/firmware fault where...for some reason the digitizer is just not initializing on every boot up. It only initializes once every ~25 boot ups, then works fine until the phone powers off.
I plan on fully restoring the phone to factory stock condition soon, relocking the bootloader and all, then seeing if the problem still persists. If it does, then I'm done with the phone. It's too much of a pain in the butt to keep the phone alive and on for weeks on end just to keep the digitizer working. At times it dies at an inopportune time and then I'm just power cycling it like an idiot hoping that it works again on the next reboot - which it eventually does, but I don't always have the time to reboot the phone endlessly while keeping my fingers crossed.
Thanks for the suggestion though!
So last night my fiance's phone started to constantly turn itself on and off, i factory reset it it has been dropped but she bought it cracked. its not water damaged and its not a lose connection because me being an IT i took it apart, her S3 Now suffers a black screen. im thinking because the phone did something in the middle of the factory reset maybe the Firmware got corrupt? or something.. it will go into DL mode with HUGE difficulty.
then the download mode goes black. havent plugged into my pc yet havent had time
any ideas? i looked over some of the other threads. None seemed relevant.
Close thread. phones mainboard died.. nevermind.
Ok so prior to getting the AT&T s3 i747 I had a s2 i727 and on two occasions I cracked the screen and/or LCD and just purchased a broken s2 (water damage..etc) off ebay and then put my motherboard in a new shell basically. I’m attempting to do that now with the s3. The seller on ebay said he was told it was an issue with the motherboard but the screen and lcd were good. I tested it when it first got here and it would not turn on at all. Now that I have switched the motherboards around it will turn on. It goes through the logo screens and starts up fine EXCEPT the screen continually flashes and after a few minutes will restart itself. I messed with the power button but I don’t think that is the problem. When I turn it off and charge it with my battery it does exactly what it should but when I do the same with the battery that was sent with it the battery display flashes on off on off and it pretty much won’t keep the charger connection going. Every time I google it or read a forum its ppl who can’t get past the Samsung screen and I’m having no luck getting answers. So if anyone knows whether this is a screen/lcd/digitizer issue or something internal please help me so I can return the phone before it’s too late! Thanks
Oh and I can boot into download mode but not into recovery mode and I have already reflashed using odin which seemed to be successful..it said pass
so one of my friend gave me a galaxy s3 today, it vibrates when i click power button, and after that the blue light on the top lights up.
and the capacity button lights up however screen is black. cant hear any volumes either.
i tried to boot into recovery, and download mode but the screen is pitch black. i tried holding volume up, home power button then after waiting few seconds click volume up button( screen is still pitch black) then connected to my computer.
my computer and odin can recognize the phone, so i tried flashing stock rom but no go, screen is still pitch black.
so i thought it was the screen that was the problem. i happened to have another galaxy s 3 lying around so i disassembled both of the phones and switched motherboard. and the screen works noproblem. so im guessing its the motherboard that is the problem.
is it possible that motherboard is dead? even though my computer can recognize the phone?
or could it be like damaged?
well i guess i could try and download another rom and flashing it again but wanted to know if anyone had similar problems before.
any suggestions?
Sounds like the digitizer is shot.
Should be a semi cheap fix at the right shop.
Sent from my SGH-T999 using Tapatalk
Could be the digitizer, or it could be a dead gpu. Did you ever overclock or anything like that? Did you plug the supposedly bad mobo into the good phone to see what happens? Inspect the ribbon and solder poonts really closely too.
Sent from my SGH-T999 using Tapatalk
nono the screen works, i siwtched motherboard and digitizer screen everything is working.
but if i switch the motherboard back again its not working.
digitizer is working. idk what is problem with the motherboard
Theres probably not much you can do other than getting a new motherboard then.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Theres probably not much you can do other than getting a new motherboard then.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
could it be like brick? or something like jtag can fix? is there anything i can do through cmd?
i just want to make sure before i go ahead and buy motherboard.
if i can connect it to computer and computer recognizes motherboard isnt dead right?
Motherboard itself is not dead, but a component on it most likely is. Like I mentioned earlier, could be the gpu. If that failed it would explain why you get nothing on the screen.
But no, its not a brick in the usual sense. If it were, the red led would come on when connected to the computer and it would show QHS_USB in device manager. Odin would not be able to see it.
You can try getting it into download mode (hold vol down, home and power when booting up. Then press volume up after a few seconds) do not hold power long or itll just hard reboot. Then try to odin flash the firmware.
If that doesnt bring it back then its definitely hardware failure.
Sent from my SGH-T999 using Tapatalk
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
rewkim said:
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
Click to expand...
Click to collapse
Do you get the blue screen when attempting both recovery and download mode?
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
rewkim said:
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
Click to expand...
Click to collapse
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
I appreciate your help - thank you. For what it's worth, no - there was never any text on my blue screen, and I couldn't ever get it to get into Download Mode. Plugging it in to a computer did nothing except give me a blue screen, and the computer never recognized it as a device.
I ended up getting a replacement G3, so [for now] my troubles are over. Thanks, again, for your help.
(I guess this thread can be closed now.)
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
rewkim said:
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
Click to expand...
Click to collapse
Glad you got it replaced!!
And a shame for your friend :/
In my case, it was practically hopeless, nothing seemed to work, eventually i had to have the motherboard replaced. It was clearly a damaged bootloader, yet, they repaired it under warranty! funny
I doubt you can damage a bootloader without root or stuff.
I wonder what would suddenly mess with the bootloader after months of no issues?
I'm having the same issue. Or rather I had the same issue but I was able to get it back to stock through all the various .tot methods and using download mode and everything. I had no issues so I rooted it again, installed the 35B firmware from xdabbeb, as well as his 46A so everything is still stock, and running the latest android update, but the phone is still rooted. In any case it has been working fine for almost a week. Today it shut itself off again and now only blue screen when I turn it on. It barely gets past the LG logo before it blue screens again. I can't enter download mode because while installing the device on the PC it blue screens and crashes in download mode.
So I'm not sure what the deal is. I have the extended insurance and warranty but if you pull the battery for a couple hours and put it back in it will boot past the LG screen and start the OS, but the boot loading screen shows "Android" instead of "Verizon" so they'll know it's a custom firmware and do nothing for me. If anyone has any ideas I'm open to them! I would love to revert back to stock but with it crashing in download mode I can't even do that.
try these things but g3 is crap phone
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
can you explain what outfit in you are talking about? i am facing the same problem,
Simaramis said:
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
Click to expand...
Click to collapse
..
ARYA3 said:
..
Click to expand...
Click to collapse
Sorry "outfit on ebay" means seller on ebay. Don't remember what their name was. With the g3 it's like this: bootloop is usually fixable with a new battery. If it loads with charger connected, then definitely try new battery. If blue screen without a number, it's likely faulty motherboard. It may still boot occasionally, after leaving batt out or putting in freezer (yes freezer). If it does boot then do a backup immediately but phone is likely in need of new motherboard.
http://forum.xda-developers.com/showpost.php?p=70264535&postcount=9
BSOD is not so BSOD as you might think. This is actually the default view of the screen controller. It just means.... well... basicly... you're ****ed....
Something in the hardware doesn't fire up as it should and it's usually the SoC.... or the so called processor. Heating and baking might help if the problem is with low temperature welding but again it might not. And even if it does... it will be totally temporary (most cases weeks) because of the rapid increase/decrease of the processor temperature and thus welding joints... I'm basically in the same situation right now with the same phone... he fought well as it is 2014 phone after all but in the end it died heroically.... ;(