[Q] D850 32B ROM NAND Chipset Overheated & Failed - AT&T LG G3

I am going to post what recently happened to my D850 G3 and see if anything similar has happened to others.
Now before I tell what happened to my phone, judging from the past posts I've made generally one of two things will occur.
1. Nearly all forum members who read it will ignore it and move on. (That's expected, if it didn't happen to them why respond?)
2. Those members (with the exception of the civil-mannered ones) who have post counts in the thousands will respond back with an inappropriate comment.
The civil-mannered ones usually always will respond with a suggestion or viewpoint which helps me understand the issue.
[This site is supposed to be about sharing knowledge and helping others, and I realize the "goober factor" does come into play at times.]
My phone got REALLY hot a couple of weeks ago and died. Sent it back to LG repair facility in Ft. Worth TX.
I got it back this last week and the tech stated on the paperwork that came with the repaired phone that the 32GB NAND flash memory chipset was replaced.
When I went online to see exactly where this chipset is located in the phone, it was the location where all the heat was coming from.
I am not a newcomer to computers and their associated hardware and I realize that smartphones are a different beast, so to speak. I've experienced and diagnosed hard drive failures, motherboard and DIMM RAM failures, CPU failures, CD/CD-R RW/DVD DVD-R/ failures, and so on. I have custom built over 50 computer for myself and customers, I have diagnosed and repaired close to 200 computers. All the previous in mostly the desktop format. Mobile phones and smartphones are in which I'm still in a big learning curve here.
What would cause the NAND ROM chipset to overheat like that? Could it be linked to using a custom ROM firmware? Could I have done something wrong?
Was it just hardware failure? I am extremely curious about this.
Anyone who has any constructive comments or suggestions are encouraged to share their opinions and/or views.
Many Thanks in Advance! :fingers-crossed:

Did you have a custom ROM installed on it? I would be surprised if LG covered you even if you had a custom ROM on it. I had the same problem as you once, and I returned it. No idea why my chip decided to fail though.

Likely simply just a case of random factory defect.

I would agree with shimbob, NAND overheating and failing before the processor doesn't follow the logical path of a custom ROM. For the NAND to overheat that would mean an insane amount of data calls and for that to happen the CPU/GPU has to be driving it. That should land up overheating the CPU/GPU first before the memory. What ROM were you running? Did you tinker with the any of the processor settings?

I don't think he'll answer, guys. He's not really asking for help or he would have provided the info you asked about in the first place. He's here to complain about how a genius such as himself could end up with a bad memory chip.
And to the OP (should he read this), that's what you had.
If it makes you feel any better, we felt just as bad as you when we read your post, which divides the world into three camps: the ignorant, the impolite, and those who help you over your little hurdles.
Very edifying.

Related

Are phones becoming more unreliable?

Over the past 2 years I have had 3 separate and different mobile phones. Each with their own problems.
1st a htc hero which had many problems , not anything which needed it sending back but things such as push call and it wouldn't call anyone for 5 mins then place 15 calls to that person. Not sending texts and dropping calls.
2nd a htc desire hd , got the day of release , sent back 4 separate times. Faulty phone which drained the battery dry in 3 hours even when not using it . Another twice for the phone dying and not switching on. And then a problem with the screen not displaying anything aswell as each time taking a photo it would switch the phone off.
3rd and finally the iPhone 4 which I have had for 2 months , and granted to software is a lot more stable than android (and more boring even when jailbroken) but even this phone has a fault with the light sensor so the screen dosnt re illuminate when making a call.
Is it just my bad luck or as phones are packed with more gizmos and gadgets are they becoming less reliable? Because as you can see here the more advanced the phone gets the more issues arise. Now I'm not complaining i think even with the faults there is no way I could live without a smartphone.
Any comments or are other people feeling this way ?
no, in our environment where broadband and instant gratification has become so pervasive our expectations have risen ... sometimes to unrealistic levels
Bummer...fortunately I've had no big issues with my last 3 HTC devices!
I think they're generally just as reliable as before, which is to say not very reliable at all. There's not enough testing and quality control and, as ever, new technology is constantly replacing the old before the old is ever perfected. That applies to both hardware and software where it seems every iteration brings a new set of problems.
Also consider how much more frequently they are used as opposed to the days of the Nokia 33** phones, voice only, no such thing as texting or data.
The more features you have the more these is to go wrong...
omgjosho said:
Also consider how much more frequently they are used as opposed to the days of the Nokia 33** phones, voice only, no such thing as texting or data.
Click to expand...
Click to collapse
This.
Or it is probably your luck
From reading your post, I'd say the majority of the problems lies within the user. It's like giving an inexperienced 18yo a classic Ferrari and expect the kid to know on how to properly take care of it. Maybe it's the case of TOO much technology for one to handle rather than phones becoming more unreliable. Funny how I've had about 4-5 phones in the last 2yrs and none have gone in for repair.
All phones now are unreliable crap. . . . All the way from beyond garbage software that needs to be changed to for even daily use(that is why this community exists), to junk hardware.
Windows 7 < enough said
As an ex-Android and WinMob user I can only agree, phones are unreliable ... and lets be honest, they have been for more than a couple of years!
The problem as I see it with OS's like WinMob and Android - they are written to be "everything to everyone". They are then customised either with drivers or a front end or both by a manufacturer and this is where the weak points come in.
Why do you think IOS and WinPho7 are far more stable? Because they are closed environments with restrictions to hardware access/low level coding. Because of this its much harder to introduce unstable code.
I am now a Winpho 7 owner and I cannot express here just how happy I am with its stability. OK, it *currently* doesn't do everything Android and WinMob do but what it does do, it does reliably
How embarrasing was it when you went to give a friend a phone number and your "contacts" would lock up or, you try to make a phone call and nothing happens or, you don't get phone calls ... only to find out your phone had locked up!
Reliability is now 100% key for me.
omgjosho said:
Also consider how much more frequently they are used as opposed to the days of the Nokia 33** phones, voice only, no such thing as texting or data.
Click to expand...
Click to collapse
dont be rediculous.
I've been using phones as "modems" for years, probably actually thinking about, over a decade! As as for "no such thing as texting"......
jordanprudent said:
Over the past 2 years I have had 3 separate and different mobile phones. Each with their own problems.
1st a htc hero which had many problems , not anything which needed it sending back but things such as push call and it wouldn't call anyone for 5 mins then place 15 calls to that person. Not sending texts and dropping calls.
2nd a htc desire hd , got the day of release , sent back 4 separate times. Faulty phone which drained the battery dry in 3 hours even when not using it . Another twice for the phone dying and not switching on. And then a problem with the screen not displaying anything aswell as each time taking a photo it would switch the phone off.
3rd and finally the iPhone 4 which I have had for 2 months , and granted to software is a lot more stable than android (and more boring even when jailbroken) but even this phone has a fault with the light sensor so the screen dosnt re illuminate when making a call.
Any comments or are other people feeling this way ?
Click to expand...
Click to collapse
It beggars belief that people are saying that these are YOUR fault and the way you use it.... unless of course you decided to throw it on the floor (which i doubt!)
So all those "its your fault" people, how would he/we break a light sensor or stop the screen switching on? Seriously .. would love to hear this!
DirkGently1 said:
I think they're generally just as reliable as before, which is to say not very reliable at all. There's not enough testing and quality control and, as ever, new technology is constantly replacing the old before the old is ever perfected. That applies to both hardware and software where it seems every iteration brings a new set of problems.
Click to expand...
Click to collapse
Would have to 100% agree with this! Too much rush, not enough QA.
no, in our environment where broadband and instant gratification has become so pervasive our expectations have risen ...
Monty Burns said:
dont be rediculous.
I've been using phones as "modems" for years, probably actually thinking about, over a decade! As as for "no such thing as texting"......
Click to expand...
Click to collapse
I'm hardly being ridiculous. It's common sense. If you leave your car in the garage 6 days out of the week and only drive it on Saturday, the probability of failure is significantly lower than if you were to commute daily. There are a number of factors involved: mechanical failure and accidental damage being two examples.
The same could be said of cell phones - when they had less function than the phones of today, there were fewer points of failure and a lower probability that it would occur.
Just because you may be the exception to the rule does not change the rule. Assuming that is ridiculous.
omgjosho said:
I'm hardly being ridiculous. It's common sense. If you leave your car in the garage 6 days out of the week and only drive it on Saturday, the probability of failure is significantly lower than if you were to commute daily. There are a number of factors involved: mechanical failure and accidental damage being two examples.
The same could be said of cell phones - when they had less function than the phones of today, there were fewer points of failure and a lower probability that it would occur.
Just because you may be the exception to the rule does not change the rule. Assuming that is ridiculous.
Click to expand...
Click to collapse
I wasn't refering to the complexity=failability, couldn't agree more!
I was refering to the fact that you suggest that people didn't text or use mobiles as modems, of course we did.. The only diference was that we had a modem cable and proprietry dialer! I even setup an NT4 RAS server for our company...
and texting? Your seriously suggesting texting is a "new" craze....? I might suggest the exception to the rule might be you.
I was referencing the period before SMS was an available service, actually. So you're missing the point.
And the majority of people were not setting up their cell phones as modems on NT4, so you are still missing the point and bordering irrelevancy.
Regarding SMS... I sent my first text message before making my first mobile call...
Regarding reliability, my previous phones (roughly £100 dumb phones) were all useless.
Friend has LG cookie. Worst, least reliable phone known to man.
Hero? Used it heavily for 16 months out of my 18 month contract, and still not seen anything that takes my fancy to replace it comes May...
Best, most reliable phone has been the most recent one.
For those who complain of a device's speed, just whip up a custom rom and optimise it.
Never had any speed issues on my own ROMS... had plenty in others
omgjosho said:
I was referencing the period before SMS was an available service, actually. So you're missing the point.
And the majority of people were not setting up their cell phones as modems on NT4, so you are still missing the point and bordering irrelevancy.
Click to expand...
Click to collapse
I'm guessing your in the USA where adoption of digital networks was far slower (and later) than in the UK (and probably Europe?).
Texts have been an integral part of mobiles since well before your Nokia 33xx models i.e. before 2000.
For example, my first mobile was on Hutchinson Telecom (now Orange) back in 1995 Linky
And do you even know what NT4 RAS was? You wouldn't put a mobile on it! You would use a Win95/98 client to dial into it ... usualy from the laptop with its modem i.e. cellphone! Here in London it was common place for IT support to carry this kind of setup around. IT people were some of the first to take advantage of digital networks.... for this very reason. (Yes you could do it over analogue but it was easily monitored)
So, as we are going to labour a pointless point, why on earth do you think texts are a relatively new thing!? Maybe in the states it is but not here in Europe and certainly not in the UK!
edit:
ahh yeah there we go "Location: Livermore, CA" of course, the rest of the world doesn't exist does it...
There's no point debating with someone who's failing to read.
I never once said that texting was a new thing. You put those words into my mouth, and I'm yet to agree with you about that.
Regardless, let me know when you're ready to actually discuss the topic, sans tossing out insults and making assumptions about what I do and do not know

How would one go about disabling/enabling when a phone can and cannot be charged?

I have a very unique situation.
I dropped my phone in the trash at work(IT Company), accidentally one day, and a small amount of disturbingly gross liquid managed to make it's way into my phone.
I wiped it down, made sure it didn't smell like crap - etc.
Everything worked FINE at first, I said ah, good. Apparently it was not not good.
Now, the phone gets stuck in a loop where it thinks to itself it's charging for a second, then it's not, keeping the screen on and flashing the charging notification repetitively until it decides to stop for an hour, then come back.
Radioshack screwed me over BIG TIME on my phone insurance, I filed a ripoff report etc, and given I need my phone for work related issues I really cannot afford to have any downtime having it be sent in and repaired. NO, I cannot receive an immediate replacement, and NO, I cannot afford another phone.
So, therefore I come to you, my great friends at XDA.
I've a fairly decent background in programming, I understand the just of it. I've taken classes in ASM(Microcomputer Architecture and Programming), C/Java and Python.
And no, I'm not a college-fed programmer, I've been programming in VB, C/C++, PERL etc. since I was 13(22 now.)
So, to the specifics:
My phone is a Samsung Transform Ultra, Android 2.3, rooted and running a "ROM" if you could call it that, but it shouldn't make that much of a difference(just installed it to get rid of CIQ)
Now, I've never wrote a mobile app before but I have the android SDK (1.6-4.0), and I'm fairly certain I could get a hello world going in a matter of minutes.
I'm willing to do the research myself, I just need some good pointers and some people who might be able to answer a few questions along my journey, and when the app is done I will be releasing it in full, yes, to you XDA.
Programming costs time, replacing the phone costs money. I have more time than money.
Best regards!
Bump.
Any help on this issue would be GREATLY, GREATLY appreciated as this is quite possibly the most angering issue imaginable.
I don't know if this will help, but I had a similar problem with my galaxy S. It turned out to be a tiny piece of silver paper that had managed to get into the micro usb slot. A quick shake later and problem solved.
Sent from my GT-I9000 using XDA App
thebotnet said:
I have a very unique situation.
I dropped my phone in the trash at work(IT Company), accidentally one day, and a small amount of disturbingly gross liquid managed to make it's way into my phone.
I wiped it down, made sure it didn't smell like crap - etc.
Everything worked FINE at first, I said ah, good. Apparently it was not not good.
Now, the phone gets stuck in a loop where it thinks to itself it's charging for a second, then it's not, keeping the screen on and flashing the charging notification repetitively until it decides to stop for an hour, then come back.
Radioshack screwed me over BIG TIME on my phone insurance, I filed a ripoff report etc, and given I need my phone for work related issues I really cannot afford to have any downtime having it be sent in and repaired. NO, I cannot receive an immediate replacement, and NO, I cannot afford another phone.
So, therefore I come to you, my great friends at XDA.
I've a fairly decent background in programming, I understand the just of it. I've taken classes in ASM(Microcomputer Architecture and Programming), C/Java and Python.
And no, I'm not a college-fed programmer, I've been programming in VB, C/C++, PERL etc. since I was 13(22 now.)
So, to the specifics:
My phone is a Samsung Transform Ultra, Android 2.3, rooted and running a "ROM" if you could call it that, but it shouldn't make that much of a difference(just installed it to get rid of CIQ)
Now, I've never wrote a mobile app before but I have the android SDK (1.6-4.0), and I'm fairly certain I could get a hello world going in a matter of minutes.
I'm willing to do the research myself, I just need some good pointers and some people who might be able to answer a few questions along my journey, and when the app is done I will be releasing it in full, yes, to you XDA.
Programming costs time, replacing the phone costs money. I have more time than money.
Best regards!
Click to expand...
Click to collapse
One maybe possible solution maybe... (free app) (need root)
Hardware Disabler
The though is, in order to stop that you are going to have to disable the actual USB port. You are going to have to play around and find out what driver corresponds to that USB port ... good luck, let me know if it helped.
(Yes I made that app)

[Q] does flashing damage or decrease phone's life?

I flash like 3 times a day, sometimes 5...I am a flash-maniac, addicted, whatever you want XD
now, does flashing too much damage the phone or decreare our device's life? there's a lot of read/write/format/flashflashflash in every operation!!
I had an hd2 before, and it died because of a bad block...like bricked...and I flashed it so much...maybe I exaggerated XD
so, what you think?
Hi I flash a lot too . Not 3 xs a day but often if there's an update or mod or something I want. I've flashed so much my USB port on my device is kinda loose .(Already have the part to fix just need to take to the shop) but let's be honest here, I'm sure it does decrease life of the device some, how could it not? But I say have fun while you can and enjoy! Maybe cut back a bit from 3 times a day .haha
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, mugen battery. please press thanks if I helped in anyway.
There are devices that have known problems with this. Like the MyTouch 4G for instance had some of it's devices built with a bad batch of emmc chips that eventually failed like 10% of the time and flashing was ultimately determined to be overstressed by flashing. Sometimes they would fail quickly like after 2-3 flashes. Sometimes they would fail after 1000 flashes. Sometimes they never failed.
The Sensation isn't known to have bad chips that fail under stress at a regular rate. So you're okay.
Now that's not to say that your particular phone didnt just happen to get the 1 bad chip in the batch of a million of them. That's possible with any peice of electronics equipment (or anything else for that matter). But it's not a common problem on the Sensation. It is a common problem on some devices.
It you want to learn more about the possibility of it start here....
http://forum.xda-developers.com/showthread.php?t=1081243
Or do a search in ght eMyTouch4G forum for "bad emmc" and you'll have lots of threads that will talk about how they fail.

[Q] "Retroactive Bricking" or "spontaneous" hardware fault?

PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!

[Q&A] WiFi stuck on turning on; MAC 02:00:00:00:00:00; G2 G3 G4 G5 Nexus5 Nexus 7 etc

[Q&A] WiFi stuck on turning on; MAC 02:00:00:00:00:00; G2 G3 G4 G5 Nexus5 Nexus 7 etc
Hi!
If you are reading this now, you are probably one of the unlucky fellows who's WiFi (and Bluetooth) stopped functioning, and if so, you are probably deperately searching for a solution/fix. I might have something for you, but first:
*** DISCLAIMER/WARNING ***
You yourself are exclusively responsible for whatever may (or may not) happen to your mobile device, to yourself or others. I am only giving hints/advices here that *MAY* help, but I will not take any responsability, nor will I provide any support, in absolutely *ANY CASE*, including, but not limited to: your problem not being solved or/and your mobile device becoming partially or completely broken. Let me be very clear: If you do anything to your device rendering it useless, destroying it, seriously or fataly injuring you or others, and then come blaming me or/and cry for help, I will point my index finger at you and laugh at you. Period.
If you are a impatient person and want to get straight to the point, jump right to section 6.
Table of Contents
0. Foreword
1. Description of the problem
2. Urgent advice
3. Things that didn't work
4. There is little hope
5. My most obvious advice
6. LET'S GET SERIOUS!
6.a Sellotape / Scotch tape
6.b Refrigerator / Freezer
6.c Oven
0. Foreword
Two or three months ago, one fine morning, the WiFi/BT of my LG G2 suddenly stopped working. Initially I thought this would be only one stupid annoying minor thingy, that I’d be able to solve it fast. I was wrong.
1. Description of the problem
When turning on the WiFi, it would just stay in "Turning on..." forever. Similar thing for Bluetooth: It would stay on for a few seconds and then turn itself off again after. (But then, who needs Bluetooth anyway, WiFi ist probably 100 times more important...). I have thoroughly searched the internet, and I found quite some videos with exactly the same problem (remove the two blanks from the links to watch):
h ttps://w ww.youtube.com/watch?v=fRGnQz1zUmw
h ttps://w ww.youtube.com/watch?v=4W8YJMDFM88
h ttp://w ww.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
2. Urgent advice
I want to prevent you from wasting countless hours searching for a solution - I wasted so much of my time already, no need for you to repeat that. Therefore: *Please* be aware that there is a VERY HIGH PROBABILITY that this issue is being caused by a hardware defect. I can not speak for all devices of course, but keep in mind that the main reason I wasted so much time, was me beliving it was some software issue! See the next section for a glimpse of stuff I have tried without any success:
3. Things that *DIDN'T* work
01. Restarting WiFi/Bluetooth several times
02. Rebooting the phone
03. Turning airplane mode on/off several times
04. Slapping/hitting the phone (this was indeed suggested in a forum)
05. Using WiFi-Fixer apps
06. Resetting to factory settings
07. Upgrading to newest Android version
08. Fully drained the battery and left it uncharged for several hours
(Rooted the phone)
09. Deleting the /data/misc/wifi/wpa_supplicant.conf
10. Deleting the whole /data/misc/wifi folder
11. Creating a file named ".bdaddr" in /persist/bluetooth containing a MAC-Address in hexadecimal format
12. Creating a file named ".macaddr" in /persist/wifi containing a MAC-Address in hexadecimal format
13. Flashing several custom ROMs to it (CyanogenMod, ParanoidAndroid, ...)
14. Going back to stock ROM
15. etc. etc. etc.
16. Several combinations and permutations of the above
4. There is little hope
Again, as the cause of the problem is most likely a hardware issue, I don't recommend going through all the steps as described in the previous section; however, though none of the steps worked for me, this doesn't mean that none won't work for you neither; you might be luckier than I was. In that case, enjoy your restored WiFi and be happy.
5. My most obvious advice
You need to replace the motherboard (main board) of your device.
Honestly, if you can afford it and it doesn't cause too many inconveniences to you, you'll be better off by simply buying a new device. If you don't want to buy a new device, send it in for repairs. If you don't want to do that as well, you'll have to fallback to a DIY solution:
I. Buy a new main board for your device. Be careful to get exactly the right component for your specific model. If you dont find any shop selling those, there are plenty of individuals out there that own devices with broken displays. You dont need the displays, you need the motherboard. Buy one such broken device, and you'll have your main board replacement.
II. Replace your main board or let someone else do it for you
Continues below.
continuation
6. LET'S GET SERIOUS!
If you are reading this, you either didn't read or you decided not to follow my most obvious advice in section 5. So be it. If you want to carry on from here, be sure to re-read my disclaimer at the top of my post.
There are 3 DIY possible fixes for the WiFi problem - none is guaranteed. I will describe them from the most harmless to the most kamikaze/deadliest. All of them will require you to open your device; if you are not careful and damage any of the components inside, you will end up with a worse device than before - but hey, don't say I didn't warn you.
At this point we assume that the cause of the problem is a faulty solder joint of your WiFi IC. The goal is to try to restore that solder joint. To do that, you will have to:
I. Open your device
II. Find your main board and separate it from all connected plugs
III. Find / identify the WiFi IC chip on the main board. I recommend searching for a service manual for your device, or/and searching for a disassembly video for your device; you need to know which one of the chips on the main board is the WiFi one.
Once you have identified your WiFi chip, you have 3 options, which you may combine with each other, but I recommend to try them out one-by-one as follows:
6.a Sellotape / Scotch tape
You need to make sure that your WiFi chip is pressed against the main board (ideally, this ensures the broken contacts touch each other, solving the problem). The best way to achieve this, is to attach a series of tape strips on the top of the WiFi chip, causing it to be pressed against the main board by the surrounding cover/hull once you reassemble/close the device. The tape strips are just a suggestion, do whatever you find convenient as long as you ensure that the chip is pushed against the board at all times.
This method may solve the WiFi problem already. When you turn your device back on, give it some time (5-10 minutes) and reboot it a few times if the problem still persists. My own WiFi didn't function right away, but after a while it finally recovered - hurray!
6.b Refrigerator / Freezer
Instead of using the tape as described in 6.a, you may first try to put your motherboard in a fridge for a few hours/days. But make sure to put it there in a plastic bag, and avoid moisture as much as you can, specially when taking it out of the fridge. Make sure its completely dry before reassembling your device!
By the way, try the refrigerator option BEFORE you try the freezer option!
6.c Oven
If everything else fails, the oven might be your last chance. This is not a joke, but as you probably can assume, it is "All-In" i.e. highly risky. The theory behind this is that high temperature will cause defective solder joints to reflow, reconnecting and thus fixing the problem.
You should only try this as a matter of last ressort. Be warned that you may fully destroy your main board, and there is a high chance that you will. Also, you may cause serious injury to yourself or others. Make sure you make backups of your data first. DO NOT BAKE THE WHOLE DEVICE, ONLY THE MAIN BOARD. DO NOT BAKE THE BATTERY!!
If you are still reading:
I. pre-heat your oven to 385° Fahrenheit (196° Celsius)
II. put your main board in the oven, bake it there for 7 minutes
III. remove from the oven, let it cool down until every component of the board has room temperature
Finally, here is a video of a guy doing a similar thing, but with a heat gun:
h ttps://w ww.youtube.com/watch?v=A4n0j3uaS7E
Ok, this is all, I hope I could help you.
Good luck!
Summary
Hello all,
first of all, I want to thank brysclar and xbing6 for their valuable feedback! Thanks a lot guys! :good:
Now, in an effort to update this thread and in an effort of trying to summarize it in fewer words (my disclaimer above applies!):
- The described problem seems to affect mainly (all kinds of) LG devices
- The issue seems to be caused by a defective soldering of the Wi-Fi chip on the main board
- The defect seems to be induced by dropping or/and overheating the device; recharging the battery, big/long app or android updates or the flashing of custom roms could cause excessive heating
- brysclar pointed out that replacing the battery might solve the problem (I haven't tried this out myself, so I can neither deny nor confirm this)
- My recommended solution is 6.a - applying pressure on the Wi-Fi chip, pushing it against the main board, using tape stripes
- There is a video of a brasilean guy doing some similar, but using pieces of an old credit card instead of tape strips: https://www.youtube.com/watch?v=OJkdva2iOag BUT PLEASE NOTE THAT HE IS APPLYING THE PRESSURE ON A RANDOM SPOT, NOT DIRECTLY TO THE WIFI CHIP! It *may* work for you, but if it doesn't, find/identify your Wi-Fi chip and apply the pressure there
- If everything else fails, and only as a matter of last ressort, you may try what I have written in 6.c
So... this thread has over 500 views, but not one single reply.
Guys... what has your experience been? Have you tried anything out from the posts above, and if so, what was the result? Did it help you? Do you recommend anything? Has something else, not written here, worked for you?
There are a lot of people out there having the same problem. It would be great if you could give any feedback, share anything that helps the community.
Click to expand...
Click to collapse
I honestly didn't see this post before. You really covered every detail very well. So far, returning my G3 to stock and replacing the battery has fixed it for me. Weird. I know. I did try 90% of the things on your "things that don't work" list and you are correct. They don't work.
wlanmac 02/00/00/00/00, Bluetooth is OK
Hey, i just got an LG LS990 with same Wifi issue and i'm ready to try so WITNESS ME!
Thanks for an amazing and detailed post lml
Simply awesome.
I have similar issue with my Nexus 5x. It is QCA6174 hw 3.2 chip, lspci does not detect this chip any more. I am going to do a little bit investigation from device driver (cnss) perspective. It enables one GPIO to provide power to this WiFi chip, I will try read back this GPIO status to see if it is enabled. I do not have the schematics, I do not know how to check if power is supplied to this wifi chip.
lspci used to show below:
$ ./lspci
00:00.0 PCI bridge: Airgo Networks Inc Device 0300 (rev ff)
01:00.0 Network controller: Atheros Communications Inc. Device 003e (rev ff) (this is qca6174)
If kernel driver investigation does not reveal anything helpful, I will ask other guys to replace the chip.
I thought it is because of vendor partition is accidentally wiped out, maybe it is unlikely.
---------- Post added at 08:49 PM ---------- Previous post was at 08:40 PM ----------
As Bluetooth can not be turned either, I am tending to think this is hardware related as well. As described previously, I will see if I can check that gpio status.
investigating
xbing6 said:
I have similar issue with my Nexus 5x.
(...)
I am going to do a little bit investigation
Click to expand...
Click to collapse
Hi xbing, and thank you for your feedback! :good:
I am really curious and looking forward to hear the results of your investigation! I believe that in your case, too, the Wi-Fi/BT chip is not being supplied correctly due to a defective soldering. Note that I don't think that the chip itself is defective, only the contacts between the chip and the main board. So, before replacing the chip, I'd recommend to first try what I've written in 6.a (or check my update/summary above).
Keep us posted about everything you find out!
Sprint declined to fix my LS990 due to "water damage" being the reason for it not working, and wanted to charge me a $150 deductible for a $100 phone. Shimming the WiFi chip against the metal covering with some thermal pad I had lying around and adding a bit of sticky foam on top of the ribbon cable for the camera worked great! Much thanks!
Tomcat5 said:
Sprint declined to fix my LS990 due to "water damage" being the reason for it not working, and wanted to charge me a $150 deductible for a $100 phone. Shimming the WiFi chip against the metal covering with some thermal pad I had lying around and adding a bit of sticky foam on top of the ribbon cable for the camera worked great! Much thanks!
Click to expand...
Click to collapse
Any idea if thermal paste/grease could work?
unlikely
NavHur said:
Any idea if thermal paste/grease could work?
Click to expand...
Click to collapse
Hi NavHur,
since the problem is mostly caused by a loose Wi-Fi chip, respectively a defective solder joint, using thermal paste or grease is unlikely to help; again, what you need to do is to have your Wi-Fi chip pushed against your main board. You can use your imagination on how to accomplish this; what Tomcat5 described he did ultimately led to exactly having his chip being pressed against the board.
Of course you are free to try whatever you want - if you find new solutions please post some feedback.
Good luck.
NimbleWeasel said:
Hi NavHur,
since the problem is mostly caused by a loose Wi-Fi chip, respectively a defective solder joint, using thermal paste or grease is unlikely to help; again, what you need to do is to have your Wi-Fi chip pushed against your main board. You can use your imagination on how to accomplish this; what Tomcat5 described he did ultimately led to exactly having his chip being pressed against the board.
Of course you are free to try whatever you want - if you find new solutions please post some feedback.
Good luck.
Click to expand...
Click to collapse
Thanks you so much, I placed a small piece of plastic above the wifi chip and one next to the camera lens. Now the wifi works fine. However my screen was pushed up so it bended a little. The faulty thing was my battery, not the added plastic. I compared mine with the one of a friend, mine was 1 mm bigger. (also with the battery of my friend's g3 the screen was fine)
I'll be changing it soon.
same problem as u but sometimes wifi works(mainly fully charged) and sometimes dont
i have lg g2 D802 model. It had a wifi problem as u shown in your videos,my phone also behaves same like yours but sometimes it works normally like while charging,works like 2 or 3 times a day(for 5-10 min).please tell me whether my phone got ic problem or software issue
Pratap94 said:
i have lg g2 D802 model. It had a wifi problem as u shown in your videos,my phone also behaves same like yours but sometimes it works normally like while charging,works like 2 or 3 times a day(for 5-10 min).please tell me whether my phone got ic problem or software issue
Click to expand...
Click to collapse
Hi Pratap94,
nobody, neither here in this forum nor elsewhere in the internet, will be able to give you a reliable answer without having a *physical* look at your phone. Nobody.
However, I can give you my opinion, based on the stuff you wrote: The fact that it works normally sometimes, specially while charging (probably it heats up in the process?), indeed seems to indicate a hardware issue. I believe you have a loose Wi-Fi chip i.e. a defective solder joint, like I had on my LG G2 D802 as well. I solved my problem by doing the stuff I described in 6.a.
Good luck.
Thank you so much
NimbleWeasel said:
Hello all,
first of all, I want to thank brysclar and xbing6 for their valuable feedback! Thanks a lot guys! :good:
Problem solved good bless you!! the problem is fix in that youtube video XD
Click to expand...
Click to collapse
Sadly step 6.a did not help me. Well, it worked for first 5-10 minutes and then back again.
Olzhas18 said:
Sadly step 6.a did not help me. Well, it worked for first 5-10 minutes and then back again.
Click to expand...
Click to collapse
Hi Olzhas18,
that might be an indication that your WiFi chip is still a bit loose and is not sitting tight enough on the main board. On LG G2, it is difficult to push the chip against the board because it's covered by a metal cover...
Also, did you check out this video: https://www.youtube.com/watch?v=OJkdva2iOag ?
Good luck!
NimbleWeasel said:
Hi Olzhas18,
that might be an indication that your WiFi chip is still a bit loose and is not sitting tight enough on the main board. On LG G2, it is difficult to push the chip against the board because it's covered by a metal cover...
Also, did you check out this video: https://www.youtube.com/watch?v=OJkdva2iOag ?
Good luck!
Click to expand...
Click to collapse
Thank you this tip and this whole thread. I have seen this video, but still the same effect. 5-10 minutes, I can rean some news and back to flashing. I'm going to buy Huawei Honor 8 soon, it was the last chance to recover my G4. I doubt I will purchase any other phone from LG.
Same boat
But bluetooth working
In cm roms also wifi tethring can be onn
But u cnt turn onn wifi
I had the same issue, can't turn on Wifi after factory reset.
I turn off my device off after one hour and reboot wifi was OK but when I want to upgrade some apps iwifi turn of again and my phone reboot with no SIM card.
I do "6.a Sellotape / Scotch tape" + a creedit card cut with this video https://www.youtube.com/watch?v=6_0jzp65eLY#t=73.319872
My LG G2 works fine

Categories

Resources