Hello everyone. Before I sell my Atrix on eBay as a broken phone for parts, I thought I would make see if anyone can think of anything I might have missed. I have an unlocked Atrix, using CM7, flashed to CM9, then back down to CM7 until the bugs get worked out. My wife dropped my phone, which caused some problems that have now bricked it.
Specifically...
When she first dropped the phone, I picked it up, turned it on, and immediately noticed that the headphone icon was on, even though no headphones were inserted into the jack. This effectively killed any sound on the device. I rebooted a few times, and occasionally the icon would go off and bring back sound. Then, it would go back.
I noticed that if I sort of twisted the Atrix (held it in my left hand, gripped the top of the phone with my thumb at the top right and my forefinger on the top left and squeezed), I could make the icon go off. It might come back on, but I could squeeze it and make it go away.
A few days of this went by, when I noticed that the headphone icon was staying off. However, when I went to actually insert headphones, they wouldn't register. However, it was at this time that I realized that the volume rocker was dead and unresponsive.
In retrospect, this is probably where I should have realized that I should leave well enough alone and limp along with my crippled, but 80% functioning Atrix until my next upgrade. However, I soon found out about the CM9 betas coming out, and quickly downloaded ROMs to flash. Flashing turned out to be tricky, as the only way I could get into recovery was by shutting down the phone with the command to go into recovery. Holding VOLUME + and power do nothing because the rocker is broken. Similarly, I cannot get into fastboot (presumably because of the broken rocker).
The first thing I noticed with the ICS build that I flashed was that the camera wasn't working. I first assumed that this was a software glitch, except that the camera seemed to be working since the first of February. I then flashed down to CM7. However, the camera still didn't work. It then dawned on me that I had not tried to use the camera since the drop. I then guessed that I just now noticed that my crippled phone is down to about 50% functionality.
So, last night I decide to flash up to a new CM9 beta. Not sure why. Guess it was boredom. The flash, however, didn't take, as my phone now is stuck on the boot screen. Ordinarily, I'd boot into recovery, wipe, and re-flash. Except with the broken rocker, I can't get into recovery without first booting into Android and then re-booting into recovery. So...it is effectively a brick now.
I decided to take it apart using iFixit's guide, but I didn't see any obvious damage. However, I'm guessing that there is some crack on the motherboard from the drop that is not discernible to my untrained eye. The fact that the camera and sound use the same ribbon cable is what is leading me to this conclusion.
So, now that you have the full story, what's the verdict? I'm guessing I need to sell it on eBay as a broken phone for parts. Someone can make good use of the housing, digitizer, and glass. I was thinking of starting at $75, but taking the first offer in the $50 range. Is it time to sell it for parts, or am I missing something?
I don't know how to fix it (I'm sure there's a way!), but if somebody doesn't find the answer soon, PM me about it. I would totally buy the battery if you're willing to part with that.
I ordered a camera/volume rocker module and am waiting for it to arrive. Not sure if this will fix it or now, as I don't know if the motherboard is intact. I figured that it was worth $15 for the part.
I'm actually using an extended battery I bought from Amazon. I'm always looking to make money, but I think for karma's sake, I should advise you to look there for some stock and generic batteries. I found a really good deal on an extended battery that came with a battery door. So, my stock battery and door have been sitting in a desk drawer for weeks.
FIXED
OK, not that anyone seems to care, but in case anyone is Googling with similar problems, I'll go ahead and post a reply. For $15, I was able to buy a camera module. The camera is attached to the volume rocker, so I took the Atrix apart, put the new unit it, and VOILA!!!
The phone seemed to hang on the red Moto logo...but with a working volume rocker, I was able to get into FASTBOOT, wipe the recovery, flash a new recovery, then boot into new recovery, wipe, and flash!!! Back in business!
I'm going to start a new thread as I think this is a new problem, but now the phone has a SOD when I talk on the phone. Battery pull and reboot works, but so doe simply plugging it in to a power source...I have to believe this is a software issue...
Related
well i have an odd problem, one one section of my screen doesn't pick up touches, only the area where the "C" is on the keyboard...its annoying due to thats where the OK buttons are...
i can still navigate sense i can use the track ball..
anyone else have this issue, or something similar?
Try wiping back to factory if stock or reflash the rom if rooted?
I had a weird issue with the touch screen on condemned 18.3 where on the lockscreen trying to drawdown the slider and then draw the pattern, it would freak out and glitch and not follow my finger at all and take several tries to get the pattern correct.
I then wiped and flashed the latest 4.0 GSB and haven't had any issues since.
That's not quite a touch screen failure as yours is, but I thought it would help as an example as something gone wrong and how I was able to remedy it.
i've tried flashing a few different roms, went from cs18.3 to a 2.1 sense rom, back to the latest gsb. it appears its must be a problem with the digitizer...
really sucks, i have to wait to april to upgrade this phone...
might be on craigslist looking for a cheap droid 1...
Ah man, that's unfortunate. Probably wouldn't be worth it to try to replace the screen/digitizer either. Yeah, that's probably your best bet, looking to get another phone. That's how I got my Eris, from craigslist. Great way to go about doing so.
Good luck to ya.
I actually have the same problem and something leads me to believe that an update is causing this. I had it bad a few weeks ago (can't press C, V or X - though I can swipe to the keys sometimes) and then I got a few market updates for Handcent, SuperUser, and something else which then cleared it up for a few days. Then I got more updates and it's back to the failing keyboard!
I really don't know how to pin point it and I haven't done any resetting or testing yet, but I have like gut feeling something is wrong with the software, not the touchscreen since someone else is having this problem.
Mine has been failing little by little. Im now down to the top right corner, bottom left, and bottom middle not responding. It hard to even get the apps drawer to open. It all started with the letter C with me too. Just gets worse.
****, my whole qwerty row doesn't work, neither does the trackball. Upgraded to a SGS2, but I still tinker with the ol' eris.
mine moved, it started working fine for a few days, then just a smaller section to the left of C doesn't work, only really effects when i have an "OK" to press...but track ball still works and typing is so much easier now.
my wife thinks its because i dropped my phone that it started working again
I know this thread is a couple of months old, but...
There's an area on mine at the top right below the notification pull-down that appears to be dead. I'm thinking it's because I've dropped it about 10 times, but nothing looks wrong with the screen otherwise. I've thought about buying a replacement screen for about 15 bucks, but I'll be able to upgrade at the end of March, so I'm really just thinking about holding off (though if the new screen/digitizer worked, it'd make for a good mp3 player with the wifi script).
Digitizer is going bad. Same exact problem happened to mine. I replaced it myself and it works perfect. I found how to videos on youtube and bought a digitizer for about $37 online. Only took a half hour to tear apart and replace. On the difficulty level, I'd give it a 6 or 7.
MBL85 said:
Digitizer is going bad. Same exact problem happened to mine. I replaced it myself and it works perfect. I found how to videos on youtube and bought a digitizer for about $37 online. Only took a half hour to tear apart and replace. On the difficulty level, I'd give it a 6 or 7.
Click to expand...
Click to collapse
YMMV.
Someone gave me an Eris that had digitizer problems along the lower left side of the screen (in portrait orientation). I bought a replacement digitizer ($22 iirc), installed it, and it worked perfectly - for about the first 30 minutes. Then, the problem re-appeared in exactly the same location with the new digitizer.
Same behavior for a variety of stock or developer ROMs, so highly doubtful that it was a "software problem". Very very odd - the chip that does the capacitive sensing is on the flex circuit attached to the digitizer, so it gets replaced when you replace the digitizer; I suppose that the signals that come off the mini-connector between the digitizer assembly and the phone's mobo are only power, ground, and I2C signals.
But there you go; taken all those observations together, I'd suspect that I had a problem on the phone's motherboard which was thermally dependent.
Despite my (negative) experience, the odds are still in favor that a digitizer replacement will fix the problem; but there is an outside chance that it won't.
just sayin',
bftb0
To my surprise the other day I got my phone to turn back on after dropping it in the hot tub while it was on, almost. After pulling off the back half and thoroughly drying it out the phone powered back on everything else works except the home back and search keys the ones that light up at the bottom. But they do work sometimes, most of the time actually. When the keys are working, every once in awhile the menu will keep flashing up on screen and when i hold the menu key it stops.
I re flashed the ROM thinking it may have developed a glitch being wet, nothing.
I tried drying it out more, nothing.
I'm not sure how the keys work but if i completely remove the front glass and clean the inside of it would that do anything? When it dried out the water did leave a slight film. It almost seems like there is a bad connection somewhere.
Thoughts?
should of left power off and in rice for 24-48 hours + befor turning it back on but it may help im not to sure havent taken the glass off my phone yet
let me know what happens
Might not want to hear it, but if you have insurance, NOT warranty, you should go ahead and get it replaced. Water logged phones never work the same, and usually don't last much longer when you do get it running again.
Thus device is still new enough that you should be able to get a replacement brand new out of the box from the insurance company.
Sent from my DROID RAZR using xda premium
Hi guys! I'm new around here, I've been lurking the forums for the past year or 2.
I originally had a i9000. Had it rooted, flashed & running 4.2.2 Hellybean, it was a dream, easiest android phone i've ever dealt with.
Today, I bring you a device that is so mind boggling and mysterious, it's ridiculous. Before you ask, yes I've searched and searched countless hours on end & sleepless nights. Trying to work out how to PERMANENTLY fix this device.
Straight up, I'm going to tell you what I've done, what I've tried, where the phone came from, model of the phone & all the useless stuff.
OKAY. Go.
I got the Samsung Galaxy S2 (i9100T) off a friend recently, about a month or two back. He didn't have a back cover for it, and the camera was all smashed up (back camera). It was running on 4.1.2 Vodaphone Stock DVLSH. It had a few issues when the phone got to me.
I wasn't sure if the phones battery was depleted, but I had to muck around with the phone for a couple of hours just to get the damned thing to turn on.
When I had got the phone to turn on, I kept getting "Warning! Battery Disconnected!" messages, this was frustrating. I eventually let the phone fully charged before I mucked around with it and ignored the warning.
When it was fully charged, I went straight to rooting it. I first rooted it by flashing CF-Root and then flashed a custom rom. (Xylon AOKP. 4.2.2)
From here on, the phone started to randomly restart, drop signal, lose battery after random restarts, get semi boot loops.
So I flashed a different stock (XWPL8) and got rid of the Samsung Galaxy SII i9100T boot logo and it was changed to Samsung Galaxy SII i9100.
After this, I then again rooted the phone but this time a different method and used Siyah kernel and flashed Carbon rom 4.2.2.
I still encountered the same problem as Xylon 4.2.2.
So I kept reverting back to stock, re-rooting & trying again.
I've tried countless methods.
POSSIBLE HARDBRICK RECOVERY DON'T TAKE MY WORD THOUGH: I've even managed to HardBrick the device (yes I mean hardbrick, i didn't even JTAG to bring it back... I flashed Dorimax Kernel at some point and it hardbricked it to all ****.) I spent a few days trying to unbrick it when finally I just plugged it into the charged and forced it to internally turn on (i believe) and let the battery deplete (the phone was hot even when i unplugged it. So I let the battery drain.) Yes I even battery pulled and tried to reboot it to see if I could boot recovery or download or the rom even before I tried any of this! (absolutely nothing.)
I took out my SIM card after a full day of letting it drain (just to be sure) plugged it in, took out the battery while the charger was plugged in, put the battery back in, unplugged the charger while holding power, and plugged it back in and I got the charging logo booted into download mode after 80% charge and flashed stock again.
Now the problem(s) with the phone:
SEMI-BOOTLOOPS: Every time i've rooted the phone and even flashed different roms just to make sure, it does a "semi boot-loop" I've searched everywhere for people with the same problem but found nothing on it.
What it does, is it turns on (boots the samsung logo.) turns off, turns back on, turns off, turns back on etc and then after about 2-8 times of doing is usually it boots to the ROM and the phone works for awhile.
RANDOM REBOOTS: I don't get these much anymore since I found a solution where someone had just folded up a receipt and pushed the battery up against the prongs because it had about .5mm movement off the prongs. This fixed most of the random reboots and don't see many anymore.
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?: This one I'm not 100% sure what it is, I read it's the S.O.D (Sleep of Death). Which is common on 4.0.4 and was apparently fixed in later Android versions. But sometimes, when I lock my phone, or my phone goes to sleep, the screen stays black even after I press the home button or the power button, at first I thought just restart it by battery pull or holding down power like everyone says, yeah it works, my phone boots up and does a semi-bootloop and goes back on eventually, but one day I left it on in the mysterious S.O.D. and waited 5-10 mins pressed the power button and it unlocked... This one really has me baffled and it does it a LOT.
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!: Okay, so sometimes when the phone finally turns on, the screen is really bright, like the brightness is still on half, but it's a lot more noticeable on how much brighter it is, it's nearly like a white.
It's really really BRIGHT. Phone shouldn't be able to look/get that bright. After a reboot though it goes away and goes back to normal but this leads me to believe something to do with the battery just a hunch.
RANDOM FREEZES!??!?: Sometimes the phone will just randomly freeze, I can be doing something and it'll just freeze, it won't turn off, I still get picture on the screen but it's frozen and I can't do anything until I either battery pull or reboot it by holding down the power button.
Before anyone asks, yes, I Factory Reset from recovery, Wipe Cache & Dalvik Cache before, I flash a new rom etc.
- My GApps matches with my Android versions each time.
- The ROMs I have flashed are compatible with my phone.
- And I've made sure everything I have done is completely compatible with my phone and android version.
What I think!:
SEMI BOOT-LOOPS:
This one, I don't think much of, it's got me baffled. It could be something to do with the Boot-Loader, could be something to do with a bad flash (but I've even tried double flashing a single rom.)
the eMMC could be damaged in a certain way that it causes these self proclaimed "semi boot-loops"
RANDOM REBOOTS:
This one, I've pretty much fixed with the help of lurking the internet over and over for hours, so this indicates a battery problem, will be replacing it this week. (Yes I'm aware that this battery problem could be causing everything else to play up and that it could all be due to the battery but can we leave the battery out of this just for now so I have more options on how to fix it.)
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?:
I believe that this could be due to either a high load on the CPU (maybe not so much high but a really low load that it goes into a state of nothing for awhile.) It drops into a mode where it's turned off (something bigger than deep-idle.)
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!:
I haven't changed voltages or messed with any voltages on my phone, but I believe that it does indeed have something to do with the CPU & GPU voltages or even the BATTERY Voltages either undervolting or being to high.
RANDOM FREEZES!??!?:
I think this one is something to do with my phone not liking the voltages stock set to it.
I read that somewhere Freezing the System Alarm Clock can fix the random reboots, so I've done that and also pushed the battery up with a bit of receipt so it touches the prongs completely.
Anyway, right now, the phone is on Stock Kernel with CWM Recovery6, with PacMan's 4.3.1 Nightly release on XWLP8 Baseband and it still does this all.
I know i'm asking for a lot of help and I'm probably going to get yelled at by Devs or forum mods or some body because I've done something wrong.
But if it doesn't belong here, move it please.
IT TRULY IS A PHONE FROM HELL.
-Thanks, Just another man who wants to fix silly problems for fun.
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Hey guys thanks for the speedy replies! I love waking up to instant replies!
theunderling said:
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Click to expand...
Click to collapse
Sorry, I was half asleep when writing all this! I am getting a new battery this week! But I wanted to have a go at trouble shooting it but crossing out the battery from the list of problems seeing as it's being replaced this week @theunderling
MistahBungle said:
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
Click to expand...
Click to collapse
It may sound like it @MistahBungle but I have faith and I come down to being very patient with technology even when I do reach ticking time bomb mode. I believe I can fix it if I just get the right help !
If the new battery doesn't do anything, It might be the logic board and i'll just go buy a new one.
Jimsilver73 said:
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Click to expand...
Click to collapse
@Jimsilver73 It really is!
I'm not the most wealthy person or have money to just throw at things like new phones etc etc. I'd love to see what I can do on my side and try and trouble shoot every problem for even the simpilest of DIY Solutions. I get a kick out of mucking with phones and computers.
Your probably right, but I was thinking that does Dori kernel keep stock voltages or does it change the voltages at all? Because it just managed to Hardbrick its self a few hours after flashing it which was odd, which led me to suspect that my phone didn't like the Dori Kernel & Carbon Rom Combination!
@theunderling I will try that Hawkers script by the way!
Is this the one? http://forum.xda-developers.com/showthread.php?t=2100558
Phone having no back cover and camera smashed suggests that there is a physical damage to the phone, i wouldn't even try battery to this one, it may just kill the new battery if there is some kind of water damage, tho you seem like having fun trying to repair it Yes, that's hawkers script, use it and couple of ROMs, (ICS,GB etc) to see if there is a software problem. If you can dissamble it, you can check if there are some contact problems between pieces.
Hi @Dakura thanks for the reply!
The camera isn't smashed completely, but at fist I thought that the camera would be screwing up the phone in someway.
I know for sure as well that there is no water damage, and the phone was just sitting around he lost the back cover randomly after he had bought an iPhone 4S.
I can disassemble it, I just need to find my little screw driver I use for stand-off changing on PC cases.
I read somewhere that the proximity sensor has a bit to do with things, so seeing as the back cover isn't on, that maybe dust got into it while it was in his draw and that's the reason for screen-offs? because the phone is still responsive. I can receive calls & text messages just the screen is black and doesn't come back on.
The warning in 4.0.4 "Warning! Battery Disconnected!" leads me to think that in versions above 4.0.4 (4.1.2 for example) don't have warnings and the phone just turns off.
**major update**
@Dakura @theunderling @Jimsilver73 @MistahBungle
Hey guys, so I've just taken the back CASING not the cover. Off the phone.
I've been looking for breaks in solder points on the Logic Board and around it.
- The Camera ISN'T smashed it was the lens on the case..
- Looks a tad dusty.
- Semi Boot-Loops have disappeared! booted the phone with the case off and the semi boot loops are gone tried booting multiple times each time with success!
- No breaks on the logic board from what I can see as far!
- For some reason the Camera app would not connect to the Camera. "Can't connect to Camera!" maybe the camera flex cable isn't in properly.
- First boot with case off, battery gave false reading of -1021032418914 (something along those lines). That's usually caused by a lose battery correct me if I'm wrong?
- Everything seemed a lot more responsive and working.
Hmmm.
So removing the screws and taking the back casing off made the Semi Boot-Loops go away.
Maybe a part of the back casing was pushing on the Logic board and shorting it out?
Maybe the screws torque where messing with it (e.g. on a HDD with computers the simpliest change in toque on the screws in the HDD can screw the HDD.)
But the torque of the screws where very loose.
Any ideas are much appreciated!!
Yep, probably a short-circuit or dust problem or displacement somewhere around there. What you said proves that somehow the phone was physically damaged. You may need to actually disassemble all the pieces, inspect them and put them all back together, and it still may not work, for now, try cleaning the dust and tighten the screws, fasten the board.
@Dakura thanks for the help today Dakura!
Finally got around to putting everything back together after an evaluation, made the flex-cables all snug and tightened up the screws a lot!
The phone appears to be working now.
at 100% it even vibrates now when i tap things it never used to.
I couldn't quite locate the problem, but I have a feeling that one of the flex cables could have come loose but only just enough to generate fluctuation of power between full and under to keep the phone on.
Hopefully the phone stays stable!
@theunderling thanks for recommending me HawkerPauls Nuke script, I'll be using that every time I re-rom my phone from now on!
Will update the thread on a possible fix for anyone else with this problem.
It's always good to run through every possibility and solution to fix problems before going out and blowing money.
so my amaze has been out of commission for a solid four months and i now have a nexus 5, but today i tried something. I originally thought my amaze's screen ribbon was messed up (it also has a missing contact in the headphone jack the left one to be exact, and both speakers are shot -prior to demolition-), but as it turns out there is actually a short somewhere in the circuitry. I took the liberty of completely tearing apart the phone (literally the plastic band around the glass is destroyed now). so after I have a pile of phone guts i start to put back together what I can. basically I had the screen, circuit boards, and battery sitting in it's shell. I also cleaned off a little corrosion on some of the parts too. then I plug it into my computer and bam the screen comes on! I almost had a heart attack, I honestly didn't expect that, and what is more interesting is that I was able to everything fine until it came time to flashing a ruu to get it back to stock, it wouldn't do it. but I kid you not, after multiple failed ruu flash attempts and a re-lock of the boot-loader I push the power button (more of a squishie than a button now) it started booting up CM10 like it was the day it died on me four months ago! Then when it finished booting up, the touch screen started freaking out and thought that I was touching it everywhere (i'm so glad I always turn on show touches in dev options) then it died again, I guess the short became active again, but here is the weird part, when I had it plugged into my pc and it started glitching I would unplug it and it shorted my pc and made it do a self-save power-out. I just thought i would share this with you guys to see if you have had any hardware probs out of you'r amazes.
I'm sure plenty of people have them.
Screen bleed is the most famous.
Randomly shutting off is common too.
HTC has crappy power buttons on a lot of devices.
I got bit by all 3 of those (but my power button wasn't quite dead yet) before I got bit by the bug that our flash chip has. I was trying to use my phone as a USB drive and copied a ton of stuff over, the progress bar stopped moving and the phone didn't seem to be running right, so I rebooted. Somehow it bricked and now the charging light wouldn't even come on. Started from the unbrick tricks, but I was way worse off than what they are for and near as I could tell something had disappeared really early on in the bootchain process and it was unfixable without direct access to the eMMC to rewrite the whole image.
Later found out once I got a pantech burst (which has very similar hardware) to replace my amaze that the MMC chip we have can get confused and randomly swaps blocks of storage around. It's easiest to trigger if you have lots of writes pending and the operating system tries to deallocate a block (like trim on a SSD); sometimes the chip will de-allocate the wrong block. Mine happened to garble something really close to the beginning resulting in my brick.
Much later I got a broken phone off ebay to rip apart to see if I could get the many gigs of data I MOVED to my phone immediately before it died only to find it just had a dead battery...maybe. It was well used, but didn't look physically damaged. It turned on but the screen was just static, like an analog tv with no channel. Couldn't get it working, but on other phones it looks like this is what happens when the chip in the LCD dies.
Combined the two broken phones to make a working one and find that this board has something going on where the battery drains when the phone is shut off, thus explaining why the battery that came with it was completely toast. Maybe I screwed up the rebuild, but I don't know how.
tl;dr: Yes, I have had some hardware problems.
Yeah I had that power button issue ( the problem is it splits apart and gets corrosion in it and its awfully wobbly) I had had that problem with my galaxy Nexus's volume rocker too (I had it for development) , i split it open and scraped off the corrosion and closed it back up it didn't come apart after that either it was fine. I also had the reboots , random extreme power drain from 100% - 30% - then dead in minutes ( it was a rare occurrence though), the LCD short, bad charger connection, and like 1/2 inch of the touch sensor didn't work( it was just at the tip of the twrp slider too so I had to use clockwork). You know its ironic looking back before I got it I was looking at reviews and they all said it had that "unmatched build quality" and it ended up being one of the most hardware plagued phones of its time, quality was a key factor when I chose it, though I did slightly overuse it, i think it shouldn't have been so badly designed, I only had mine for just over 1 year of my 2 year contract and I didn't even get it from the contract, I broke my T-Mobile g2x after 6 months with it and got the amaze through insurance [which was BS since i paid monthly for it, had to send my broken phone to them (which I could have fixed for less), and pay the difference between its price and the price of the amaze. I ended up paying full price for the amaze and the monthly insurance bill, I would have been better off not getting the insurance because it limited me to only getting the amaze and the sensation "phones of equal or lessee value" ($250 more than the g2x), they screwed me over]. Even though its in pieces and will most likely never work again I will probably hold onto it forever because it was a great phone, even if it let me down a few times. I learned around 90% of everything I know about android developing and software developing in general from that phone and its really sentimental to me. Lolz all my broken and worthless stuff is sentimental to me, I think I'm may be a little bit of a hoarder but oh well.
Sent from my Nexus 5 using xda app-developers app
Uuhh this post was a mistake... My bad, I done messed up
Here are pictures from after I tore it apart to get it working and it booting up after it was dismembered (after it booted it was fine, It would pick up touch from the messed up side but at the same time it went crazy and picked up "touches" everywhere, even when I wasn't touching it so everything almost worked but then died again) sorry the last one blurred I was riding in a car
Sent from my Nexus 5 using xda app-developers app
Got a unique issue with my G5. Have had it in a Lifeproof case for awhile now.
Last night, it spent most of the time riding in my back jeans pocket where it always does. I've had zero issues with sitting in the car, and whatnot....as I'm not a hipster that wears tight jeans that could possibly damage the device. Anywho, I got out of the car, dropped the phone into my pocket, and went about my evening at work - which involved ZERO sitting.
I go to pull out the device to make a call, verify my fingerprint, and nothing. Well, almost nothing. Its as if half of my screen is "disconnected", and the other half is out of sync. I've attached a youtube video to see what I'm talking about. ( https://youtu.be/357GcnV2-9Y ) My first thought was the ribbon cable became partially dislodged from its plug on the motherboard. I first tried flexing the phone, to see if it magically worked, or changed. Nada.
This am, brought it to the VZW store, expecting a quick fix, but since it shows no damage at all I got nothing but a warranty replacement request, and a promise it would be delivered within 3 days. Thats not good enough, as I use this thing for work. So I looked at alternatives...
I've browsed the teardown on ifixit, and was surprised at its simplicity. I pulled it apart, and re-seated the display ribbon cable, to no avail. Still apparently toast.
I've managed to get through the boot up pattern security I set up, and the phone is active. I just cant get it into MTP mode to copy my crap as I'm guessing I need to pull down and click on the notification to switch it.....which, of course, I cannot see. Basically, I just want to get my crap out of the internal storage before I ship this one back. Obviously I'm going to wipe it with the Android Device Manager before I deactivate, but still would like to salvage something.
Anybody have any thoughts? Or maybe is there a second ribbon cable somewhere that wasnt mentioned in the teardown?
Youtube link: https://youtu.be/357GcnV2-9Y
I have no advice as to how to get your files off, I'm sorry about that.
But I wanted to confirm that this isn't an isolated occurrence and it happened to me! I also babied my phone and never dropped it and it was always in a case.
I don't know what to blame as the cause, I'm hoping just bad quality control. I was hoping it's not due to flexing because it's not as sturdy due to the bottom of the phone not being physically attached.
Photos of the same thing on mine: https://imgur.com/a/eEAmA
This happened 15 days after I bought it and Best Buy returned it for a new one which three weeks later started bootlooping which was a whole fiasco to get repaired and took over a month. LG's quality control is horrible.
+1 as I am having this issue on a Sprint G5, sent to LG for repair after Sprint was no help. 29 days after purchase.
Hello. A few quick searches on my part found a thread here on the forums for controlling your device from your PC. It also includes a script to run when your phone is in recovery to enable USB Debugging. Try it out ( http://forum.xda-developers.com/showthread.php?t=2786395 ). Hopefully I have helped. If you want to just salvage files, you can enable USB Debugging and pull everything through the USB. However, if you want to still use your apps, or harvest app data, or even use titanium backup or the like to make a complete backup to transfer to the new device, enable USB Debugging, then control your phone. Follow the above thread's instructions to do so.
Thank you for your time,
Xzanah