Related
A few users have reported a Blank Screen of Death, with myself included.
The problem being that the phone's display doesn't switch on when you wake up the device. At this time, Everything else will including the Digitizer and Capacitive buttons.
I have spoken with HTC service centers across Australia and NZ to come to the conclusion that this is a motherboard problem. The infamous flickering issue seems to be involved also, which ends up shorting out the video driver.
The issue isn't just limited to the screen not displaying anything either, there's also the possibility that the back light will cut out, and sometimes leading to corruption on the display.
This isn't just with some devices either, it seems like anyone that has had the screen flickering issue are at risk of this.
To give you an idea of how much it costs to fix this issue, I was quoted at $250 AUD for just the motherboard alone.
The best part is, HTC may also deny your warranty for unlocking your bootloader, as they have with me.
I'll be posting more information as it develops.
EDIT 29/07/12 :: I'm going to request a transcript of my last conversation with HTC but until then, they're denying that this is a problem and saying that it's the user's fault. How? We use our phones to much, or inappropriately.
It's becoming obvious that they're trying to avoid spending anymore money fixing these issues, and have decided just to move on and release a new One X model. (according to news sources.)
Also, Boobinator just posted a video of the One X's screen corrupting while it isn't stuck under the BSOD which you can see here and here
Just to recap.
When the initial issues were found with screen flickering and corruption on the display, we were told it was a software issue.
Many months later, I along with many of you are still experiencing it, even though it's not nearly as bad as it once was.
Now there are growing reports that One X's are starting to lose their displays, and the poly-carbonate weakening and bending the antenna pins. (You can find more information here)
This is something you should all be aware about when purchasing this phone.
Best of luck!
Reserved.
Update Bump
Maybe us in America can file a class action lawsuit? I'm no lawyer here but anyone with better understanding of American consumer laws chime in?
This is problem that occurs with normal usage of the phone.
Another day, another hardware issue. HTC is going down the drain, im hugely disappointed in the way they are handling this mess. Improper testing, too slow to fix problems or ignore/deny them. Bull**** games about unlocking and warranty and now they are already talking about releasing more phones. Its easier for them to move on to a new model than to do the right thing and do a complete recall. Is this a QC issue or a design flaw, with all the negative reports I'm thinking its the latter.
HTC better handle this properly, they need to stop development on all new products untill this is solved.
Sent from my HTC One X using xda app-developers app
Can u please send me details about the store that sells the motherboard ?
I have the same problem...and I need my phone fixed !
Thx
Is this the same flickering that happens in some ROMs when you rotate the phone?
Mine too
This just started happening to mine Nothing displayed on the screen, but it still responds to inputs. Even rebooting into fastboot, same problem. So everything is functioning except the display.
Have just handed it back to vodafone for repair, don't like my odds with the unlocked bootloader though :/
I had this issue on Viper or Android Revolution, but not on other ROMs. But I'm starting to get wifi issue, scratches, scratches on camera lins. I should buy S3, not this.
Sent from my HTC One X using XDA Premium HD app
sent it back because of flickering. I just hope they will fix the problem properly and change the motherboard.
Sent from my Legend using xda app-developers app
This happened to my Incredible S too if any one's interested.....
I'm not buying the HOX, I'm sorry. There's just too many different issues for too many people with this phone. It's an expensive top of the line phone, that does appear to be pretty shoddy put together. I don't care if it's under warranty and I have dumbass-insurance if I break it, but I can't send my phone inn all the time even if it's free. You shouldn't have to send it in at all.......
I presume now know we know why HTC is loosing money, market share and their stocks are going down....
This happened to me too, about a month ago, the phones been in repair since then(1 month, are you freaking kidding me HTC). I also unlocked the bootloader, lets see whether HTC charges me or not.
Also, I managed to get the display to work(somewhat) after shaking the device a bit. But even after that the display wont work properly, I even have 2 short videos of the screen acting weird when i got it to work. Here they are - Video 1 Video 2
Sorry for the ****ty quality, got it on my iphone. This was after I shook the device and the display magically started working. Even with the display working you can see it is really weird, even unresponsive at times.
So guys, there are a lot of places you can buy motherboards from, but they will charge you a lot more than what it's worth mainly because of the shortage within HTC.
I'm so sorry all of you are going through this, but i think we need to raise awareness of this issue. People are buying these phones without realizing there's a good chance they're going to have either bad WiFi antenna's or even a bad motherboard.
Send this to your friends, post it around, contact HTC.
Best of luck!
I am having this problem as well, as well as the WiFi antenna issue. The WiFi antenna somehow bent itself somehow, because after a while it was back to normal signal strength, so I didn't feel like sending the phone away for a month. But now with this screen issue it really is unusable, so it seems I don't have a choice anymore
EDIT
Here is a picture of an example of what happens:
http://i.imgur.com/ScIaM.jpg
And here are two 1 minute videos of what happens:
http://www.youtube.com/watch?v=HIY0_Hy2_mA
http://www.youtube.com/watch?v=WYXXvu11f3o
may heat have damaged gpu? it looks like when pc's video card is about to fail (like faulty memories or damaged gpu)
CAPSGUY said:
I am having this problem as well, as well as the WiFi antenna issue. The WiFi antenna somehow bent itself somehow, because after a while it was back to normal signal strength, so I didn't feel like sending the phone away for a month. But now with this screen issue it really is unusable, so it seems I don't have a choice anymore
EDIT
Here is a picture of an example of what happens:
http://i.imgur.com/ScIaM.jpg
And here are two 1 minute videos of what happens:
http://www.youtube.com/watch?v=HIY0_Hy2_mA
http://www.youtube.com/watch?v=WYXXvu11f3o
Click to expand...
Click to collapse
Heat damage.
I doubt it's heat damage, i hardly played games on mine and it had that problem. I think the most i played was Triple Town, and that was it.
Also, wouldn't it be a massive problem if it was heat damage? That means the tegra 3 processor can't handle stress, and given that the phone inherently has heating issues, this just draws the conclusion that the Tegra 3 is bad news?
it may be a faulty soc
From what I've heard, it's been linked directly to the flickering screen problem. Which could mean that the first batch of One X's have all faulty Soc's? I mean, it's not uncommon for there to be manufacturing difficulties for the first few batches, but this is just absurd.
Atrixx said:
From what I've heard, it's been linked directly to the flickering screen problem. Which could mean that the first batch of One X's have all faulty Soc's? I mean, it's not uncommon for there to be manufacturing difficulties for the first few batches, but this is just absurd.
Click to expand...
Click to collapse
Not all of the first batch flickered. Stop exaggerating.
Hi,
I'm on a stock Voda UK and have 1.29.161.13, which I've had ever since it was released - but I still have the screen flicker.
Does anyone else still suffer with this and does anyone have suggestions as to how I might get rid of it? My hardware is rock solid and I don't want to risk a repair or exchange.
Many thanks!
Send it back. No other way to fix it its a hardware fault
Sent from my Legend using xda app-developers app
People say put on a white screen on max brightness that might fix it quicker. You could try a software reset. If that doesnt help id get a replacement.
The flicker remained a little bit for me too even after the OTA. The solution for me has been a complete reflash via the RUU.
Since then the color fix finally works and no more visible flickering.
Sent from my HTC One X using xda premium
ste1164 said:
People say put on a white screen on max brightness that might fix it quicker. You could try a software reset. If that doesnt help id get a replacement.
Click to expand...
Click to collapse
How would I go about doing a software reset? Any other solutions would be gratefully received, thanks!
I just watched this video abot Hox screen flickering.
http://www.youtube.com/watch?v=GX6TSsyL2B0
If this is the case, it is a hardware problem and will never be fixed by software update.
Best regards
flicker
shafez said:
I just watched this video abot Hox screen flickering.
youtube
If this is the case, it is a hardware problem and will never be fixed by software update.
Best regards
Click to expand...
Click to collapse
Pretty sure that's an example of screen corruption. Screen flickering looks quite a bit different to that, and was fixed (for me, and others have said the same), by software update.
Mine took about 3 days after the update to disappear. Has been perfect since.
shafez said:
I just watched this video abot Hox screen flickering.
http://www.youtube.com/watch?v=GX6TSsyL2B0
If this is the case, it is a hardware problem and will never be fixed by software update.
Best regards
Click to expand...
Click to collapse
Ha, would that be the well known and well documented "hardware problem that'll never be fixed with software" that was, in fact, fixed by software? More specifically, v1.28.
Love people who state their uneducated gut feeling as fact. Great way to propogate misinformation.
My unit was down with Flickering issue too..
HTC replace the mian board for me...
and its been working well so far for me.....
Hey guys,
If you have screen flickering issues, please read this thread, there's an arising problem with all One X's
http://forum.xda-developers.com/showthread.php?t=1745886
Best of luck!
Atrixx said:
Hey guys,
If you have screen flickering issues, please read this thread, there's an arising problem with all One X's
http://forum.xda-developers.com/showthread.php?t=1745886
Best of luck!
Click to expand...
Click to collapse
Yeah, it's happened to at least 3 people, so it must affect "all One X's". Great application of deduction, logic and reason.
BenPope said:
Yeah, it's happened to at least 3 people, so it must affect "all One X's". Great application of deduction, logic and reason.
Click to expand...
Click to collapse
That's probably heat either screwing with the GPU or anything else on the rendering chain.
Hunt3r.j2 said:
That's probably heat either screwing with the GPU or anything else on the rendering chain.
Click to expand...
Click to collapse
As anyone in the laptop repair world is well aware Nvidia chips overheating and degrading the solder joints are probably the most common reasons for graphics problems.
Mine flickers ,,it's less than four weeks old BUT it didn't flicker until after the first time my phone got very very warm.
huxleypig said:
As anyone in the laptop repair world is well aware Nvidia chips overheating and degrading the solder joints are probably the most common reasons for graphics problems.
Mine flickers ,,it's less than four weeks old BUT it didn't flicker until after the first time my phone got very very warm.
Click to expand...
Click to collapse
I wonder if any further updates might make a difference?
bigbamboo5 said:
I wonder if any further updates might make a difference?
Click to expand...
Click to collapse
I think it's a hardware issue. Software faults are present from day one usually and show up in virtually all devices. Hardware faults vary from device to device depending on heat range voltage etc etc ..So I doubt very much if there is a software "fix" you might lower the impact by altering the refresh rate say but it is only masking the issue of faulty hardware IMO.
huxleypig said:
I think it's a hardware issue. Software faults are present from day one usually and show up in virtually all devices. Hardware faults vary from device to device depending on heat range voltage etc etc ..So I doubt very much if there is a software "fix" you might lower the impact by altering the refresh rate say but it is only masking the issue of faulty hardware IMO.
Click to expand...
Click to collapse
How would I do that, please?
I often get the flicker on Chrome and apparently other browsers exhibit this less. Does anyone have experience of this?
Update it
Sent from my Legend using xda app-developers app
The assumed s/w fix that got rolled out originally was thought to address voltage regulation issues as well as graphics driver’s anomalies. Early on, in addition to the flickering, there was distortion in the notification bar and funky banding in the camera app. There was a big problem with chip consistency when the Asus Prime first launched. The chip in the One X isn't the same and it’s the first time it's being used. People have posted AnTuTu and Quadrant benchmarks that show some chips seem to be underperforming while others over perform. The problem could be an out-of-spec chip.
BarryH_GEG said:
The assumed s/w fix that got rolled out originally was thought to address voltage regulation issues as well as graphics driver’s anomalies. Early on, in addition to the flickering, there was distortion in the notification bar and funky banding in the camera app. There was a big problem with chip consistency when the Asus Prime first launched. The chip in the One X isn't the same and it’s the first time it's being used. People have posted AnTuTu and Quadrant benchmarks that show some chips seem to be underperforming while others over perform. The problem could be an out-of-spec chip.
Click to expand...
Click to collapse
I think the graphical glitches were fixed in 1.28 and the flickering fixed in the second 1.29.
I think the variable benchmarks are due to temperature of the device and battery level.
At a certain temperature (normal) all 4 cores won't run at 1500MHz, but if you can keep it cool enough, they will.
Atrixx said:
Hey guys,
If you have screen flickering issues, please read this thread, there's an arising problem with all One X's
http://forum.xda-developers.com/showthread.php?t=1745886
Click to expand...
Click to collapse
BenPope said:
Yeah, it's happened to at least 3 people, so it must affect "all One X's". Great application of deduction, logic and reason.
Click to expand...
Click to collapse
I'm staying out of your BSOD thread because I don't want to bump it or add fuel to the fire. But the fact that it's just two pages kind of tells you how widespread the issue is. People unhappy with audio output from the in-built speaker made it to 11 pages to give you a frame of reference. Real problems present themselves and don't need to be promoted.
---------- Post added at 10:34 AM ---------- Previous post was at 09:58 AM ----------
BenPope said:
I think the variable benchmarks are due to temperature of the device and battery level.
Click to expand...
Click to collapse
Nah. People with bad benchmarks got similar results hot or cold and at different battery levels. Some were already experiencing funky problems that they thought were s/w related. Nvidia has big problems with their yields so out-of-spec chips making it in to the wild isn't that surprising. It was a big problem on the first couple of batches of Prime's. I’d bet that people whose flickering wasn’t corrected by the updates have a bad chip (or aspect of a chip).
Hello XDA Community,
My name is Scott, I am the ASUS support specialist responsible for the Nexus 7 2012 and 2013. I am leaving this message in the Q&A section to let everyone know if you are having any issues or need support with your Nexus 7 then please feel to email me. My contact information will be found in my signature once it has been activated. For now see below.
I can only offer warranty and RMA support for customers located in North America, but I would be more than happy to assist with troubleshooting your issues regardless of where you are located.
If you are experiencing issues with a particular ROM or Kernel then I would recommend posting your questions in that thread.
If it is a hardware or stock issue then by all means ask away, I may not always check my PMs so emailing me is the best source of contact.
Thanks XDA Community!
Yeah, when is the 2013 LTE going to be up to date? The point of a nexus device is to always be current but yet us deb owners have been crapped on for more than a month in regards to 4.4.4. Its really gonna suck when Android L comes and us deb owners are the only nexus devices not current for a while.
Can you say something about erratic touch screen issues with Nexus 7 2013? And why ASUS / Google has never acknowledged or officially commented about it?
I'm not sure if i have to explain the issue as it's well known, but basically the touch screen has serious issues if it's laying on desk / bed (is not being held / not connected with usb or headphones)
I can guarantee it's affecting ALL Nexus 7 2013 devices, some people just dont know how to reproduce it.
It's shown on this videos for example:
Before you say it's isolated issue, here is amount of results searching for "Nexus 7 2013 touchscreen issue" on Youtube: https://www.youtube.com/results?search_query=neus+7+2013+touchscreen+issue (over 122.000 results for the lazy)
Here are some potential fixes but they are not working well AFAIK:
http://forum.xda-developers.com/showthread.php?t=2535835
http://forum.xda-developers.com/showthread.php?t=2428133
I had my Nexus 7 RMA'd (motherboard was replaced), and it changed nothing. Still the same issue. (i can send you RMA number if you want)
It seems to be grounding problem. (when tablet is being held or connected with headphones / USB there is no problem - as it's grounded properly)
Care to comment? Is this a bad design (Google) or production issue (ASUS) ?
pre4speed said:
Yeah, when is the 2013 LTE going to be up to date? The point of a nexus device is to always be current but yet us deb owners have been crapped on for more than a month in regards to 4.4.4. Its really gonna suck when Android L comes and us deb owners are the only nexus devices not current for a while.
Click to expand...
Click to collapse
Hello pre4speed,
I am just as anxious as you to see the 4.4.4 update released for the LTE model. At this time I cannot give a release date for this because Google has not released an image for this device. When it comes to the Nexus line Google is responsible for the releases. It could be possible that the LTE edition might skip 4.4.4 and jump straight to Android L when it is released. Let’s hope we see something soon, If you need further assistance you can email me with the Case number N140822232 in the subject line for reference.
k3lcior said:
Can you say something about erratic touch screen issues with Nexus 7 2013? And why ASUS / Google has never acknowledged or officially commented about it?
I'm not sure if i have to explain the issue as it's well known, but basically the touch screen has serious issues if it's laying on desk / bed (is not being held / not connected with usb or headphones)
I can guarantee it's affecting ALL Nexus 7 2013 devices, some people just dont know how to reproduce it.
Before you say it's isolated issue, here is amount of results searching for "Nexus 7 2013 touchscreen issue" on Youtube: https://www.youtube.com/results?search_query=neus+7+2013+touchscreen+issue (over 122.000 results for the lazy)
Here are some potential fixes but they are not working well AFAIK:
http://forum.xda-developers.com/showthread.php?t=2535835
http://forum.xda-developers.com/showthread.php?t=2428133
I had my Nexus 7 RMA'd (motherboard was replaced), and it changed nothing. Still the same issue. (i can send you RMA number if you want)
It seems to be grounding problem. (when tablet is being held or connected with headphones / USB there is no problem - as it's grounded properly)
Care to comment? Is this a bad design (Google) or production issue (ASUS) ?
Click to expand...
Click to collapse
Dear k3lcior,
There are reports of the Nexus 7 suffering from touch issues, most of these reports have been fixed with a software update. If the updates do not resolve the touch issues, I recommend sending it in to be diagnosed. I would be more than happy to help assist you and all others with our RMA process.
Since your Nexus 7 has already been to our repair facility I may be able to see what other options are available. If you are interested please feel free to email me at [email protected] with your serial number. Also, please put case number # N140822280 in the subject line.
Best regards,
I have bought Nexus 7 (2013) last August and the warranty had been void already. Three of the sensors including the accelerometer, gyroscope and the magnetic sensor do not work properly which causing the malfunction of auto-rotating. I have sent the tablet for RMA process before and the sensors have been replaced. However, the sensors worked for a week only. In the most of the time, the accelerometer and gyroscope look like disabled but the magnetic sensor can return some value although I reboot the machine.
Will the smart cover case affect the sensors by magnetic field? <--I'm just guessing
I cannot figure out the reason why the sensors do not work. Can you give some opinions to me? Thanks
The related post: http://forum.xda-developers.com/showthread.php?t=2746045
pc323 said:
I have bought Nexus 7 (2013) last August and the warranty had been void already. Three of the sensors including the accelerometer, gyroscope and the magnetic sensor do not work properly which causing the malfunction of auto-rotating. I have sent the tablet for RMA process before and the sensors have been replaced. However, the sensors worked for a week only. In the most of the time, the accelerometer and gyroscope look like disabled but the magnetic sensor can return some value although I reboot the machine.
Will the smart cover case affect the sensors by magnetic field? <--I'm just guessing
I cannot figure out the reason why the sensors do not work. Can you give some opinions to me? Thanks
The related post: http://forum.xda-developers.com/showthread.php?t=2746045
Click to expand...
Click to collapse
Hello PC323,
I am sorry to hear about three of your sensors failing within a week of the repair. In regards to your question about the smart cover affecting the sensors, there is a very slight possibility, depending on which cover you are using. If you are using the official case for the Nexus 7 then there should be no interference, the magnet that is included should be small enough and placed properly so it does not affect other sensors. I cannot speak about third party covers though. You can always try wiping the cache (done through the recovery) or even a factory reset if you wanted to go that far. If the resets do not resolve you issues then it might be a hardware issue. If you would like you could email me and include case number 140822657 in the subject line for reference. If you provide your Serial Number I will be able to see what was repaired on your device as well.
Hi Scott! Great to see manufacturers represented on the forum! Never seen this before, guess I should have gotten a nexus device sooner. Is there any way we can see phonecall support for the LTE version? I've seen the asus padphone, is our radio missing something hardware wise or is Google/Asus holding back? When I get home from work I go straight from my phone to my nexus 7 but I would love to be able to just pop my sim in and not worry. I'm a job jumper and I need to receive calls on my nexus
@non4 said:
Hi Scott! Great to see manufacturers represented on the forum! Never seen this before, guess I should have gotten a nexus device sooner. Is there any way we can see phonecall support for the LTE version? I've seen the asus padphone, is our radio missing something hardware wise or is Google/Asus holding back? When I get home from work I go straight from my phone to my nexus 7 but I would love to be able to just pop my sim in and not worry. I'm a job jumper and I need to receive calls on my nexus
Click to expand...
Click to collapse
Hello,
I am aware that there are some workarounds that involve using google voice and forwarding your calls. To me the easiest option would be to find an application that uses your Nexus 7 as a Bluetooth device. This will allow you to use your tablet to place phone calls and send text messages. I can’t personally recommend an application that will do this but I do know that there are applications that will let you do this. This would not require you to move your sim card form one device to the other. If you need to contact me your personal case number is N140823357.
trade LTE for non LTE?
I was one of the first purchasers of a Transformer Prime and needed solid GPS performance. Asus bought back my Prime and I purchased a TF 700. I replaced my TF-700 with a Nexus 7 2013 LTE so I could get the benefits of having the most current version of the Android OS. Well, we all know how the most expensive LTE model is the "ugly step child" who's updates actually lag behind non Nexus devices.
I am trying to stay positive here but this level of support isn't what we have been led to expect for Nexus devices. Is it possible to exchange a Nexus 7 2013 LTE for a non LTE model?
With the exception of the uber late updates to the tablet I truly love it. The most expensive model shouldn't be the Cinderella.
Scott, my N7 2013 doesn't get recognised by PC when connected via USB. What may the issue? It is very frustrating. Gives me USB device not recognised(port reset failed) message every time I connect it any PC(I have tried connecting it to a few) using different cables.
[email protected] said:
Hello,
I am aware that there are some workarounds that involve using google voice and forwarding your calls. To me the easiest option would be to find an application that uses your Nexus 7 as a Bluetooth device. This will allow you to use your tablet to place phone calls and send text messages. I can’t personally recommend an application that will do this but I do know that there are applications that will let you do this. This would not require you to move your sim card form one device to the other. If you need to contact me your personal case number is N140823357.
Click to expand...
Click to collapse
But why no native calls? These apps you speak of are unreliable
Nexus 7 USB port needs replaced
[email protected] said:
Hello XDA Community,
My name is Scott, I am the ASUS support specialist responsible for the Nexus 7 2012 and 2013. I am leaving this message in the Q&A section to let everyone know if you are having any issues or need support with your Nexus 7 then please feel to email me. My contact information will be found in my signature once it has been activated. For now see below.
I can only offer warranty and RMA support for customers located in North America, but I would be more than happy to assist with troubleshooting your issues regardless of where you are located.
If you are experiencing issues with a particular ROM or Kernel then I would recommend posting your questions in that thread.
If it is a hardware or stock issue then by all means ask away, I may not always check my PMs so emailing me is the best source of contact.
Thanks XDA Community!
Click to expand...
Click to collapse
Scott,
I saw your post and am taking you up on your offer.
Her's my story so far:
I called Asus this morning to inquire about replacing the USB port on a Nexus 7. After quite some time with the rep all he could say was the estimate was around $200 but it could come up cheaper depending on what the technician finds.
I know the problem with my sons Nexus 7 is simply the USB port needs to be replaced because the tablet still functions 100% in every way. The only issue I have is that when he plugs in the charging cable it will simply fall out. He has to make sure it stays in and not touch or move the tablet while it is charging. There is no need to troubleshoot, only to replace that USB connector part. I see the part on ebay ranging from $44 to $75, but I prefer to have the manufacturer repair my device as opposed to doing it myself or third party. Can you advise me if I can get a more solid price please as I feel that before I spend $200 to repair my sons almost 2 year old tablet I'd sooner replace it. If I replace it, it's likely I may choose the manufacturer that has been supporting me the best, and at the moment that is not Asus. Is this something you can help me with please? Thanks
Probably you can pinch the port .... They seem to open up and get loose pinch it down with a flat head and moderate pressure ..... Worth a try
Sent from my LG-D803 using XDA Free mobile app
Hi! My nexus have problem with wifi. When i download apps from google play, speed is about 0.2-0.3 mb/s. It's very slow. On my phone is 1.0-1.5 mb/s. Chrome and others works great. Is this issue in hardware or software?
Hey Guys,
just noticed that there exists two hardware revisions of the Nexus 5x (1.0 & 1.1). Just curious, what are the differences between them and when do they change according to production date?
You can examine the revision number by booting in fastboot mode (power + volume down button to start).
Thanks
Interesting might be fix bootloop issue.
Update
I got H791 32GB
Hw 1.0
SN 602KP Product on 2/2016
Still alive using 7.0 for a month
Dont know when its going too die
I hold a tricky time bomb.
Sent from my Nexus 5X using Tapatalk
I've read about hardware revision before for this device, I read that some people on the 1.0 had a yellowish screen or a warmer screen and in comparison to the 1.1, apparently they fixed that issue with the revision. I'm not really sure about this, it's just something I read and I don't that has much to do with the dreadful bootloop of death.
X3NOM said:
I've read about hardware revision before for this device, I read that some people on the 1.0 had a yellowish screen or a warmer screen and in comparison to the 1.1, apparently they fixed that issue with the revision. I'm not really sure about this, it's just something I read and I don't that has much to do with the dreadful bootloop of death.
Click to expand...
Click to collapse
Yeah, I'm pretty sure you mean this Reddit thread: https://m.reddit.com/r/nexus5x/comments/3rf6xo/two_questions_for_those_of_you_who_still_have/
What I noticed so far, that printed inside my Nexuses box stands 1.1, but in fastboot mode it says hardware revision 1.0. So obviously these two numbers doesn't necessarily correlate to each other.
Btw. mine was produced in October 2015.
Yeah same here, on the box it says 1.1 but I've never checked in the fastboot because I don't want to mess around xD. P.s I read a different reddit thread than the one you mentioned but that doesn't matter.
Sorry if this has been answered before, I tried looking around the forum and couldn't find a definitive answer about this. Or perhaps people just don't know yet... Anyway, I own a G4 that developed the bootloop and LG agreed to help. I'll supposedly be getting a new replacement phone (mine is a Singapore variant, they're swapping it for a US carrier version instead). Hopefully all goes well and I get a fully functional replacement.
But i'm still concerned. Thanks to videos from CellularDR and others, the exact cause of the defect is known and fixable. If you have the tools and skill to delid the SOC, clean and de-solder the defective materials inside, and re-solder properly (which I don't). I'm sure LG is also aware of the way to fix it themselves if they were so inclined, though i'm not sure if I trust them to apply those corrections properly to prevent the problem from returning. It was initially believed they fixed models manufactured October 2015 and later (serial number beginning in 510). Mine however was a 510 and developed the problem. It can take time for bootloops to start too (mine lasted almost a year and a half), so even a 6xx or 7xx device that works at first may still bootloop later if the proper modifications were not made by LG.
So are newer "fixed" 6xx or 7xx models really fixed and safe from the bootloop? Anyone had any of these fail on them yet? I realize one way to tell- taking apart the Snapdragon SOC and see how the solder looks, but I don't expect anyone would have done this (nor expect them to).
Goatville said:
Sorry if this has been answered before, I tried looking around the forum and couldn't find a definitive answer about this. Or perhaps people just don't know yet... Anyway, I own a G4 that developed the bootloop and LG agreed to help. I'll supposedly be getting a new replacement phone (mine is a Singapore variant, they're swapping it for a US carrier version instead). Hopefully all goes well and I get a fully functional replacement.
But i'm still concerned. Thanks to videos from CellularDR and others, the exact cause of the defect is known and fixable. If you have the tools and skill to delid the SOC, clean and de-solder the defective materials inside, and re-solder properly (which I don't). I'm sure LG is also aware of the way to fix it themselves if they were so inclined, though i'm not sure if I trust them to apply those corrections properly to prevent the problem from returning. It was initially believed they fixed models manufactured October 2015 and later (serial number beginning in 510). Mine however was a 510 and developed the problem. It can take time for bootloops to start too (mine lasted almost a year and a half), so even a 6xx or 7xx device that works at first may still bootloop later if the proper modifications were not made by LG.
So are newer "fixed" 6xx or 7xx models really fixed and safe from the bootloop? Anyone had any of these fail on them yet? I realize one way to tell- taking apart the Snapdragon SOC and see how the solder looks, but I don't expect anyone would have done this (nor expect them to).
Click to expand...
Click to collapse
Nobody really knows.
But I can say that I do not trust any refurbished phone where the mainboard gets replaced!
I believe this is also a hot fix only and it differs from phones produced since 2016.
I own two 603 serials and well I'm a heavy user when it comes to stress test due to development. No issues so far.. But regular backups is a must always
.
Sent from my LG-H815 using XDA Labs
I did see a couple of people in another thread were claiming their 601 G4's bootlooped. So that is troubling to me. Though I also saw someone else claim that there were actually some cases of people lying on here about the issue happening to them (Samsung trolls or something to that effect). I haven't found any posts claiming any G4's with 602 and above are bootlooping.
When I spoke with LG tech support, they said that I would be receiving a replacement phone instead of repairing my original device. Due to it being from a different region. I do not know anything about the "new" G4 they'll be sending back though, except that I think it'll be a T Mobile H811 variant (at least that is the carrier I said i'd be using, they seemed to be allowing me to choose). I don't know if it's going to be a new device or some kind of refurbishment, nor the model number it will have.
I'll have to cross my fingers. And hopefully they honor the replacement and don't find any reason to refuse to help me. I took very good care of the device and didn't go messing with it apart from exchanging the original battery (which went bad for no apparent reason and actually physically inflated, had to get rid of it as it's a fire hazard).
I never saw any proof(!) for a 603 or higher device which gets boot looped. Only one refurbished and actually without any proof. That's why I do not trust any refurbished..
The fix was introduced in late 2015 but I personally believe it takes time to change the production process. This means you would get e.g. a 511 with the fix and and also without (I have no proof for it though) and depending on the time required to change all production paths this can take a while.
I believe that you can be save after 3-4 months after the fix was introduced so 603 and later. But well guarantees are elsewhere..
.
Sent from my LG-H815 using XDA Labs
i would say. from 601 upwards it still can happen but no like before with 505-510's seems there a re slim chances it will.
last ive heard was a 603 about 3 of them.. not bad.. compared to the 505's so id say chances are slimmer..
raptorddd said:
i would say. from 601 upwards it still can happen but no like before with 505-510's seems there a re slim chances it will.
last ive heard was a 603 about 3 of them.. not bad.. compared to the 505's so id say chances are slimmer..
Click to expand...
Click to collapse
My concern with assuming the reliability of 6xx models is the length of time it can take before a bootloop appears. My 510 lasted from January 2016 to May 2017 before it failed. Almost a year and a half. Though I do not know how typical my G4's lifespan was compared to others.
I don't know how typical that length of time is for others who bootlooped, but perhaps the reason so few 6xx devices have failed is because they're not old enough yet. Hopefully we don't see an increasing number of 6xx models failing as the year goes on.
Goatville said:
My concern with assuming the reliability of 6xx models is the length of time it can take before a bootloop appears. My 510 lasted from January 2016 to May 2017 before it failed. Almost a year and a half. Though I do not know how typical my G4's lifespan was compared to others.
I don't know how typical that length of time is for others who bootlooped, but perhaps the reason so few 6xx devices have failed is because they're not old enough yet. Hopefully we don't see an increasing number of 6xx models failing as the year goes on.
Click to expand...
Click to collapse
yes true. about what you say.. but seems that reports are lower. nothing like the 5XX.
I've tried to find any accurate information regarding reliability of more recent versions, but haven't found any reliable source.
I had a 506, and it experienced bootloop after 12 months of moderate usage. It was repaired under warranty, and now it's 705 (motherboard was made in may 2017).
I just can't see any logic in producing crippled motherboards almost two years after cause of boot loop is discovered..
After 1 year and 2 months, my S/N 601 G4 just got bootloop last week. Threw it straight into the dustbin since that device was imported from the UK
just for the sake of the unlockable bootloader that doesn't exist in Asia.
My 511 just started bootlooping. Was able to get my data by setting it in front of my AC but will immediately reboot if it move it away.
Interesting fact is that motherboards usually fail after 1 year and 2 month (most likely). It was the same with my G4.
The replacement model LG sent me has a 701 serial number, so January 2017. Good. I guess this is the best chance of getting a bootloop free G4 that I can hope for. Though there's no telling if these models are safe either due to the time they can take to break. Can take a year or more to tell (and by then who knows if LG will even bother to help anymore).
At least for now though I once again have a working phone. It's also cooler thus far than my former G4, so maybe they did do something. Plus I now have a custom kernel and overclocking enabled on the big cores (though the custom governor settings might actually be helping thermals).