Related
Hi,
I've just joined after getting linked to this site. Seems like a huge site with plenty of info but unfortunately after a few searches I haven't been able to figure out my problem.
I recently followed a guide on here for replacing the digitizer on my xperia x10 and I followed it to the letter. After re-assembling the phone it refuses to switch on and there is no response when I connect the charger.
A little history.....
The problem started when I dropped the phone in water. I know I have been told that it would never be right again etc etc but I did everything I could to dry the phone and for a couple of months after the incident the phone would switch on and display perfectly and the buttons would work fine also. The only problem was that the touch wouldn't work rendering the phone useless as I couldn't even unlock the screen.
Anyway, every now and again I would switch the phone on again to cHeck if it had made a miraculous recovery but no joy. After asking some questions I decided to replace the screen/digitizer. I remember the last time I tried switching the phone on a few days before taking it apart it wouldn't switch on. It simply gave out a few flashes from the LED. I put this down to the battery being dead and carried on replacing the digitizer.
The only response I get from the phone now is when the charger is connected to my laptop and I remove the battery, the LED gives out a red flash every 2-3 seconds. Although this doesn't happen all the time. Most of the time I get nothing at all. I must add that I did charge the phone at least once or twice successfully after the water incedent so something else must be causing this.
I have heard of issue with these phones not charging but I don't see why this would happen to mine if it wasn't even being used. The phone was only a month or two old when damaged.
Sorry for the long winded introduction and if anyone has any ideas I would greatly appreciate hearing them.
Thanks,
Gav.
anyone had any similar problems to this before?
I know this is an old thread, BUT my X10 won't switch on either now :/ not dropped it ever and ive never got it wet, i turned it off due to it being laggy and unresponsive and now it won't turn on :/ no ROM's not rooted just stock anyone have a fix ? and no i have tried putting it in the computer for the SEUS to fix it but nothing unresponsive
Hi there; Could do with some help please I seem to have a series issue with my Samsung Galaxy S2 today. It started this morning; I noticed the screen was randomly turning on; for no reason what so ever. It only does it when the phone isn't charging, if the data cable or the charger is plugged in; it doesn't do it.
Its on version KE7. I have tried a factory reset, and that hasn't sorted the issue. Therefore I seemed to think it was a hardware fault, however with it not being an issue when plugged in I wondered why it might be doing it.
Tap to speak also kept coming up for no apparent reason, I say kept coming up, doesn't happen all the time, but did come up about 6 times today, when I hadn't pressed anything, which would suggest the bottom centre button could be stuck or sticky, however that seems fine; and its not been near any moisture and has been a hot day.
The phone has not ever been rooted; so no issues there.
The phone battery dies very quickly within about 4 hours with the screen turning on all the time; and the phone will randomly freeze up completely, and I have to remove the battery to reset the phone.
Anybody got any ideas? Really could do with some help
Thanks
Rich
Update: It is plugged in charging now; and the MTP Application has come up; like the data cable is plugged in. That seems very odd to me...
Don't be afraid to send it back. These things aren't cheap even if you're paying through your contact, you're entitled to get what you paid for.
Your specific issues may be down to more than one thing. My screen lights up when I've read my gmail on a different device and it needs to clear the notification. Nothing too worrying about that. The other stuff does sound like some sort of shorting though and people have been given replacements for less serious issues.
I'm tempted to get mine swapped because the wifi often won't pick up an IP address and the gps won't get a fix if the phone gets too hot. Relatively minor compared to your issues.
Sent from my GT-I9100 using XDA App
Yeah I think its going to have to, I've tried playing about with settings, giving it time to cool down; pretty much everything I can think of, I really can't think what it could be, it seems to be many issues rather than just one, with it only being a month old, I expected slightly more.
Love the phone, did brilliantly yesterday; used it for lots of things; then today it just suddenly went, took it of charge, and it played up the whole way through.
Given up with it now, will take it back and see if I can get it fixed, I have 24 month warrenty with my contract.
Thanks
Put your original firmware back on if you can before attempting a warranty claim .
jje
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.
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
after taking the module apart and putting it back the phone stuck not booting up with a message "insert a supported module to turn on your phone".
The issue I believe is not related to the module itself, since the same story with camera module.
The phone could have been exposed to the high humidity the day before. Before taking it apart the phone used to make occasional sound notification like it has been plugged in to charge.
Tried to clean data pins, disassemble it but no success.
I am having the same exact problem and I was wondering if you ever figured out how to fix it?
yobritt said:
I am having the same exact problem and I was wondering if you ever figured out how to fix it?
Click to expand...
Click to collapse
no, LG has told me to send the device for a service.
I'm on a trip and quite far from any cell phone store but I would appreciate on updates with your phone as well.
upd. I have a suspicion on two metal pins going from the module. if that's the module detector pins, then they might not be connected properly. blocking them w a tape on a working phone could shed some light on this theory.
My Experience
Thought I was the only one with this problem! My phone suddenly started constantly flashing the "USB" symbol with the "Insert Cable to Charge Phone" message and associated beep, which forced me to turn off the master volume...so I couldn't hear the phone ring!. The "Insert Supported Module" happened a few times at the beginning when I first pulled out and re-inserted the module/battery, but then mysteriously stopped. I went to an AT&T store and swapped the module with their display phone, and it seemed to stop (at least for the 5+ min I tried it), so I've been trying to find a replacement bottom module (I believe it's called the "Charging Module" or "Loudspeaker"), but to no avail. I tried purchasing one (SSTParts dot com look for "LG G5 Loudspeaker"), but that came without the electronic board, so I also picked up Ebay #282082091333) to go with it...but lo and behold, when I put them together and tried it, the phone gives me the "Insert Supported Module" message and won't boot. I then tried the old circuit board with the new housing, and it did boot up...but the flashing USB came back, at least for a few minutes. So I'm waiting to see if the problem comes back full blast. So we now know that the phone will only take an OEM part, at least regarding the electronics. Called LG to see if I could buy one, but they said I had to send it in for repairs...which I don't want to do (you know how it is with intermittent problems...). One thing I was able to do was to turn off the "Notification" volume (there are four Volume controls in the "Sound" settings; this is the 3rd one down) and it seems that this quieted the problem...so it keeps happening, but it's not causing me any functional concerns...though I worry that one day it might. I've looked at Ebay #401119970468, but though it looks identical, the listing says it's for an H850, and mine's the H820...so is it worth the risk? Any other updates or ideas out there? I'm thinking of going to the AT&T store and swapping out the display model's module when no one's looking...
I sent my phone for service. Hopefully I'll have the news soon.
Okay, so they they returned the phone back to the store saying "the damage is too expensive" and it's beyond the warranty. I'm pretty mad, will go to pick it up and see wtf is going on.
Won't turn back on..
ArtDesire said:
after taking the module apart and putting it back the phone stuck not booting up with a message "insert a supported module to turn on your phone".
The issue I believe is not related to the module itself, since the same story with camera module.
The phone could have been exposed to the high humidity the day before. Before taking it apart the phone used to make occasional sound notification like it has been plugged in to charge.
Tried to clean data pins, disassemble it but no success.
Click to expand...
Click to collapse
Happened to me about 5 minutes ago. Try blowing some air on the module.. trust me it will work.
Also if no airdryer is handy, take out the module let it sit out overnight and reconnect few hours later.it works. It gives time to dry out. This is a major flaw.mother****ers; They owe us the G6
Air it out it'll come back at around half an hour,expect it to also have low battery power.
airing it out didnt work for me.
the only thing that worked for me was to replace the bottom part, ie. the charging module. I got one from ebay and it worked like a charm. My g5 is almost back in its new condition.
on ebay, search for Genuine Charging Module Bottom Chin
Fixed
My wife's phone had this same problem. I think it mostly dirty contacts that cause this problem. I used contact cleaner, let dry assembled and it worked great. These companies have you over a barrel when you send it in.
this issue is with the dumb bottom power module I have same issue but I am lucky that I had bought the LG Camera module that has this module built in, so I had a backup so to speak (other than I can't use my case at the moment) and Sprint no longer has the module, so I will be ordering these http://www.ebay.com/itm/like/282313529509?chn=ps&dispItem=1 (They look new and having a pack of 3 of these should be worth it.) hopefully this works for others too.
Thanks.
I have a doubt
I have in my hands 2 g5 phones
one from sprint and one from cellcom?fixme?
however I CAN NOT exchange this module among phones. If I do so, I receive the error which prevents booting.
But every module works fine on its phone
I talked to a friend who received a lot of these phones for sale
all from sprint, and he say he could not exchange this part in the phones and instead he had to mark every part to its phone to prevent accidental swapping.
I told to him it should be impossible to be this way, and came to this forum/thread to satisfy my ignorance.
any comments?
yurais said:
I have a doubt
I have in my hands 2 g5 phones
one from sprint and one from cellcom?fixme?
however I CAN NOT exchange this module among phones. If I do so, I receive the error which prevents booting.
But every module works fine on its phone
I talked to a friend who received a lot of these phones for sale
all from sprint, and he say he could not exchange this part in the phones and instead he had to mark every part to its phone to prevent accidental swapping.
I told to him it should be impossible to be this way, and came to this forum/thread to satisfy my ignorance.
any comments?
Click to expand...
Click to collapse
I have a Verizon and sprint g5 and its the same between the two modules which irritates me too cause I figured extra parts
ArtDesire said:
Okay, so they they returned the phone back to the store saying "the damage is too expensive" and it's beyond the warranty. I'm pretty mad, will go to pick it up and see wtf is going on.
Click to expand...
Click to collapse
This is far far too late, I know. But those brass (I assume, as they are contacts which would need to be fairly durable) connectors you mentioned covering are 100 % the problem. I lightly, and I do mean very lightly, wet the pad of my fingertip and wet each of those connectors for the hope of conductivity. It worked like a charm. After around 100x of the module error, blowing with a blow dryer and trying to clean off the inner contacts blindly, it finally worked. I've had to do this on a few occasions now and it always works.
Hope this helps someone out,
regurak
I found the solution, you dont have to buy another one, it's just maintenance.
I tried doing some maintenance to all metal contacts I found and it's fixed right away, I assume this would apply to most if not all cases, some contact points are in the upper phone body, so no wonder why someone would get the error with any modules he/she tried. Let me know if it works for you but I think it will, you dont need to buy another part/phone.
Don't forget to hit the THANKS button.
SamaelThuum said:
I tried doing some maintenance to all metal contacts I found and it's fixed right away, I assume this would apply to most if not all cases, some contact points are in the upper phone body, so no wonder why someone would get the error with any modules he/she tried. Let me know if it works for you but I think it will, you dont need to buy another part/phone.
Don't forget to hit the THANKS button.
Click to expand...
Click to collapse
Ok it's been a week or two after I dissassembled the charging piece and posted those pictures and all that and IT JUST HAPPENED AGAIN LAST NIGHT. I noticed it happened because my battery was totally dead and I tried to start charging from my computer's USB 3.0, I remember it also started like this the first time, SO, I guess it's a software thing, not hardware. As soon as you plug it to the computer it will start taking energy, so, you know that even if you unplug the phone from anything, it will still show the error message supported module blabla. As soon as this happens to you, UNPLUG THE PHONE so it doesnt take charge, so, if it keeps showing the error message by itself and hopefully the battery would be so low that it wont show it for more than a minute before it shuts off due to battery. (I know you would say, well, just hard cycle the phone by taking the battery out and in again and try to turn it on or to plug to normal charger, I tried this but it would still show the error, even after I tried draining phone by holding power button without battery for like 1 min, only way that seemed to "reset" it was if batt COMPLETELY died, there's a point where if u try to turn on it only says like "battery too low to turn on"), SO, after battery COMPLETELY died, I plugged it to A NORMAL CHARGER and it worked it time.
SO, if battery is dead, I wont try to charge by PC USB for now
Just happened to my phone out of nowhere.
I kept getting the usb connection options message on my phone, then it just kept buzzing for no reason. So I went to restart the phone and now I'm getting the Insert Supported Module error.
I already know AT&T and our phone insurance will be completely useless. Damn phone isn't even paid off. The LG G5 was the BIGGEST waste of money ever. I hate this stupid phone.
JC Pro1000S Phone NAND IC Programmer
latest JC Pro 1000S programmer which it can match most of the testing module, recently i found a new web for phone repair tools supplying, it is a nice team, and i have ordered a data test module with jc pro 1000s for my phone repair shop, honestly it is a nice experiences, it can save time and solve the motherboard fault fast.
And recently ,i found there exist products in amazon, i want to try, is there someone can provide some advise for me ?
I spilled coffee on my phone and it started sating "insert a supported module to turn on your phone" I put it in a bag of rice over night and it is still displaying the same message. I have no idea what to do. Im worried that all the pictures/videos I have on the phone is lost as well. has anyone that was able to get their phone working again lost all pictures or videos?