Related
Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.
You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app
LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app
Hello, good news!
LG finally admits the problem. Then it will be easier for us to have our devices repaired/replaced! :highfive:
Some of you already shared links on several topics related to bootloop, I think it's better to create a new topic about it, as I wrote an article too for french customers
English: http://www.androidauthority.com/lg-admits-g4-bootloop-problem-hardware-fault-669603/ (official statement)
French: http://www.gamergen.com/actualites/...engage-remplacer-unites-defectueuses-269974-1
For european customers/people who bough it from UE reseller, no worries:
bel57 said:
P.S. furthermore, European Union stipulate under directive 1999/44/CE that it allows users to modify the software, root included. This modification *DOES NOT* void minimum warranty of 2 years on hardware supported by the manufacturer.
Voided warranty by "illegal" software modification has been classed as an unfair term and it's fought by U.E.
Click to expand...
Click to collapse
Sources
https://fsfe.org/freesoftware/legal/flashingdevices.en.html
http://www.bitdefender.com/security...nty-in-eu-but-opens-new-ways-for-malware.html
Already discussed here http://forum.xda-developers.com/showthread.php?t=1998801
EDIT: check out Svartsyn333 feedback
Svartsyn333 said:
Just called them and it's on its way back, should arrive within the next few hours! They told me it got repaired and all is fine. Owner check went through IMEI so no problem with forgetting to add the invoice, too. And no problem with unlocked bootloader and root either! I'm a happy girl now. I will come back here when it arrived and tell if they just repaired it or if I got a new device.
Click to expand...
Click to collapse
EDIT2: Ok guys, I *finally* got my G4 back.
LG PROJECT P1 (H815 - LG G4)
IMEI changed
S/N 505x => 602x
Repair: SWAP motherboard, software update (20D)
But would we all be subjected to the warranty? Otherwise it's not different from before.
At this point it seems like they just realized what the problem is after wrongly sending back a few units as 'repaired' even though it's still having issues.
"Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. "
If you purchased your G4 from a third party website/eBay, it's more difficult to get your warranty recognized.. best is buying it via carrier, LG official store and recognized sellers.
Are they also going to apply the fix during the production of newer LG G4s? because if not, it sounds like all lg g4 will experience the bootloop sooner or later and will only repair it after it has happened
Yes, no detailed information about it, but it seems that they already changed the production process weeks ago and they're just late to communicate on the identification of this breakdown.
bel57 said:
"Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. "
If you purchased your G4 from a third party website/eBay, it's more difficult to get your warranty recognized.. best is buying it via carrier, LG official store and recognized sellers.
Click to expand...
Click to collapse
"For in warranty repair service, you must include a copy of the proof of purchase inside the product packaging returned to the LG Product Repair Center."
Well, I can't see any problem here. You need the original invoice, that's uuuh.. normal?
I just bought the g4 and sadly discovered that my S/N started with 505. Thanks god i did not unlock the bootloader. But I really want to unlock it to install custom rom. I'm thinking of sending my device to LG even if i didn't have the bootloop yet so i'll be sure not to get it after unlocking the bootloader and then having LG not repairing my phone. What do you think ?
Just use it and stop worrying, your device may not be broken as ours.. and no, you can't leave it to repair if it doesn't have the bootloop thing.
So where are all those people now who always wanted to prove not many people are being affected or it's a common thing to have problems when they first come in the market???? I wanna see their faces... I had to hear lots of things when I started writing about it. People made me believe maybe I am the only one annoying the surreal sound of the community. It makes me so happy to see this day which I was crying out loud to happen for so long.
Sent from my LG-H815 using Tapatalk
nipun1110 said:
I had to hear lots of things when I started writing about it.
Click to expand...
Click to collapse
I feel you, bro. I went through all pages of your topic. It's a worldwide issue and it's a shame LG is so late to admit this problem. Well, finally you're right, our posts, our thoughts.. all paid off. Thanks mate.
Often when people are not concerned they tend to underestimate facts.. and this proves too much units are faulty.
bel57 said:
I feel you, bro. I went through all pages of your topic. It's a worldwide issue and it's a shame LG is so late to admit this problem. Well, finally you're right, our posts, our thoughts.. all paid off. Thanks mate.
Often when people are not concerned they tend to underestimate facts.. and this proves too much units are faulty.
Click to expand...
Click to collapse
Thanks man.... Hopefully me and all the other suffered will have our devices repaired. Best of luck for all of us.
Sent from my LG-H815 using Tapatalk
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
spartan268 said:
But would we all be subjected to the warranty? Otherwise it's not different from before.
At this point it seems like they just realized what the problem is after wrongly sending back a few units as 'repaired' even though it's still having issues.
Click to expand...
Click to collapse
Yah, what "warrenty will differ" means, needs to be cleared out.
Sent from my LG-H815 using Tapatalk
Wish you all good luck in this initiative. As for me, I'll go to carrier shop tomorrow to get a spare unit. :good:
Good to see this thread. My phone just died this night and since then is constantly hanging at boot screen. No access to recovery and download mode, no recognition by the computer (only a few seconds, then it restarts and gets disconnected) so no kdz flash via flash tool either. Just sent out a repair request to LG. Now fingers crossed it falls under warranty as I unlocked the bootloader. I purchased it in June and this is clearly of one of the first produced series which has the hardware defect, s/n starts with 505.
Don't worry, LG must repair this harware issue, no matter if BL is unlocked or not.
If you want to wipe or recover your data, try the freezer method. It works.
nipun1110 said:
So where are all those people now who always wanted to prove not many people are being affected or it's a common thing to have problems when they first come in the market???? I wanna see their faces... I had to hear lots of things when I started writing about it. People made me believe maybe I am the only one annoying the surreal sound of the community. It makes me so happy to see this day which I was crying out loud to happen for so long.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
A lot of these 'people' don't really care or look into things until it happens to them.
Then all of a sudden there up in arms being your friend about the issue. It really only took a two second google search to see how widespread this is. On reddit there's a constant stream of bootloop posts if that's not enough proof.
Now? It's just crickets from the ones who were so keen on shooting this off as a small 'problem'. foh
bel57 said:
Don't worry, LG must repair this harware issue, no matter if BL is unlocked or not.
If you want to wipe or recover your data, try the freezer method. It works.
Click to expand...
Click to collapse
I have a backup on the sd card from just a few days ago. I was aware something is wrong as it started to have charging issues, so I made one to better be safe than sorry.
Good idea :good:
Unfortunately mine freeze too fast, I just had time to retrieve my data then wipe all via recovery.. now it's sent for repair.. :crying:
But I can't do anything before this issue occurs? My s/n also starts with 505...My only chance is to keep fingers crossed?:fingers-crossed:
Yo don't complain as your phone is working great, just enjoy it and keep in mind to backup your data to microSD/computer. There's a small percentage that it will brake one day.
I remember mine overheated few times, and it may have broke a hardware component.
If there's nothing to report on your device, then you don't have to worry.
I haven't been on here for quite some time and wanted to know if others with this phone have been able to get something different (possibly V10) from LG. This morning I was looking at a media intensive web page and the phone froze (has done this many times) then rebooted. After the LG splash screen it just died despite having 44% battery. After this it would not recognize being charged and would not power on. If I let it sit long enough and remove and replace the battery it will show the LG splash screen then die again.
I'm asking the question about switching devices because there has been nothing but problems from touch screen misses, to the QC 808 heating up like an oven, now the bootloop issue. I've always came to XDA to mod an already perfectly working phone. I am now feeling like I'll have to start modding my phone just to get it to work right. I am thinking of reaching out to LG to try see if they are giving any options to us.
The same thing happened to me this morning, was looking at a video on Facebook when it suddenly froze up! Did not respond to anything... Had to pull the battery but now it does not respond to anything, had 90% battery!... After doing what You wrote, waiting a while and then put the battery back in it started up, but it stays on the LG logo for aprox a minute, before it just goes black again!? Did You find a solution? It is under a year old, so I presume this is a reclamation from LG? I have never had any issues with it like oveheating etc etc, only thing was a dead pixel on the screen when I bought it, but got a replacement screen without any problems from the service provider, so the sevice and time used was great, really hope that it is going that smoot this time too.... But seems like there are a lot of issues with the G4.... my wifes G4 has has the problems with overheating and battery drain, but mine has worked great, until now ?
Sent from my Nexus 7 using XDA-Developers mobile app
Check your S/N. If that starts with anything between 505 and 509... welcome to the club.
That's a well know issue with logic board on those batches causing the board to die and requiring replacement.
I am in the club, It starts with 505 ?? i tought it was the bootloop issue on those numbers, did not know there was a issue with the motherboards before I started googleing.. And I did not know it replyed the 505-509 batch, so thanks for the info? so if it is a known case for LG and their repair services, it should not be any discussion about replacing it ?
Sent from my Nexus 7 using XDA-Developers mobile app
waagbull said:
I am in the club, It starts with 505 i tought it was the bootloop issue on those numbers, did not know there was a issue with the motherboards before I started googleing.. And I did not know it replyed the 505-509 batch, so thanks for the info so if it is a known case for LG and their repair services, it should not be any discussion about replacing it
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
He's guessing.
Just to be completely clear:
There has been no official confirmation from LG or any official source of what devices are affected and what causes the issues.
Anybody saying it's 505's only, 505-509 are only speculating and have no official information.
LG have stated that the bootloop is covered for another 3 months outside the standard 12 month warranty.
Hello guys i've been seeing a lot of boot loop news and lg starting to refund people because they don't have spare parts : http://www.mobilechoiceuk.com/News/...offering-refunds-instead-of-replacements.aspx .
So should I be worried that my 5x will boot loop ? I've been using it for 2 months now on 7.0 september update .
just yesterday happened to mine!
Did you try to fix it or got it refunded under warranty ? Also rooted or stock with update ?
Hi, i guess that nobody could know that, but the problem seems to be the same as LG G4, LG V10, LG Flex 2 (all 2015 devices with almost the same motherboard that the Nexus 5x). You can search on the web "bootloop G4 reddit" "nexus 5x bootloop reddit" and you will find tons of reports, the majority of them (N5x) from last 3 months, and this holds the theory that is a welding issue on the CPU or sometimes on the EMMC chip (apparently LG did not weld very well that year...). The mentioned devices (included ours) seem to last from 9 to 14 months and finally the welding breaks. But now, we know it's strictly a HARDWARE issue NOT caused by 7.0 upgrade, irt's only a question of coincidence between the useful life of the weld and the launch of the 7.0 OTA.
So we all got very high possibilities that this occurs to our devices, eventually. I'm not sure that this is gonna happen to you, it really dependes of many many many factors (heavy usage, kernel profiles, temperature of your country/city/house/workplace, etc etc).
Maybe it never happens to you, but i know what you feel, is not very nice to feel that your phone could die in any moment. It was a low punch for me (i owned a G4 and it bootlooped twice) anyway i am going to sell my N5x due to this problem. Hope i help you with my point of view.
It is solder not weld.
Only Google/LG know how widespread the problem is on 5x.
My guess is it is far more than normally expected for phones but nowhere near as prevalent as posts on forums might make it seem.
So normally you might expect .01% of these types of solder problems. If the problem went up 100x to 1% and you sold 3m phones, that means 30,000 phones with the problem, whereas before you might only see 300.
30,000 people searching google and seeing other people posting about bootloop can start a panic.
If you actually had 10, 20, 30% of people with this problem you would have huge threads.
That's just my opinion.
sfhub said:
It is solder not weld.
Only Google/LG know how widespread the problem is on 5x.
My guess is it is far more than normally expected for phones but nowhere near as prevalent as posts on forums might make it seem.
So normally you might expect .01% of these types of solder problems. If the problem went up 100x to 1% and you sold 3m phones, that means 30,000 phones with the problem, whereas before you might only see 300.
30,000 people searching google and seeing other people posting about bootloop can start a panic.
If you actually had 10, 20, 30% of people with this problem you would have huge threads.
That's just my opinion.
Click to expand...
Click to collapse
If you said "It is solder not weld." for me, thanks i didn't know the correct word, english is not my native language (I only learn reading on forums), so i see that you know (or it seems) about solder problems. Look i had two LG G4 both of them die, but not just mine even a cousin had the same issue whit his G4, so i really want to know if you think that the 5x soldering problem is a similar case of high-end 2015 LG Phones G4/V10/FLEX2 (of that magnitude)? or if it's just a "paranoia", i mean we know that the bootlooping issue on this device exists but you would recommend me (i really like this phone) to keep it?
This issue got me really worried due to my bad experiencie with the G4. I just bought the N5x 1 month ago. thank you.
same question how to know if my phone will bootloop...i have my nexus 5x 5 week ago but i bay it not new i bay it used...i upgrade to android nougat no issus right now..ho to know if i will have a probleme in the future iam afraid now
moonlightdrive said:
i see that you know (or it seems) about solder problems. Look i had two LG G4 both of them die, but not just mine even a cousin had the same issue whit his G4, so i really want to know if you think that the 5x soldering problem is a similar case of high-end 2015 LG Phones G4/V10/FLEX2 (of that magnitude)? or if it's just a "paranoia", i mean we know that the bootlooping issue on this device exists but you would recommend me (i really like this phone) to keep it?
This issue got me really worried due to my bad experiencie with the G4. I just bought the N5x 1 month ago. thank you.
Click to expand...
Click to collapse
I've been dealing with substandard solder since xbox RROD (red ring of death) where everyone was trying to get their xbox cpu reballed until microsoft admitted the problem.
As I mentioned, I'm sure the incident on 5x is much higher than normal phones, but that might still be a low % (even though it is a relatively high absolute # because of the # of phones that are sold)
I have no idea whether 5x is worse, better, or same as G4 problem. G4 seemed even higher, but could be because more phones were sold. Only LG knows for sure.
A lot of folks in US are finding that their credit card actually extends their warranty beyond manufacturers warranty and people will probably get their money back that way if all else fails.
Of course that doesn't help you if you are traveling and the phone dies. I end up using Google Fi as the service provider for this phone, so if that happened I could just shift all the calls and texts to another phone or tablet and keep going until I get a replacement phone, so I'm not super worried.
I regularly back up the stuff on my phone so the most I would lose is like 1 or 2 days of stuff, which I can deal with.
Personally I wouldn't be super worried this is going to happen to you, but be prepared with backups in case it does, but that is good practice for any phone, because it could always get stolen or drop and break.
Tarbruh said:
Hello guys i've been seeing a lot of boot loop news and lg starting to refund people because they don't have spare parts : http://www.mobilechoiceuk.com/News/...offering-refunds-instead-of-replacements.aspx .
So should I be worried that my 5x will boot loop ? I've been using it for 2 months now on 7.0 september update .
Click to expand...
Click to collapse
I got my 5X a month ago.... I figure it has a 1 yr warranty so I am not too worried yet.... Lets hope if it happens it does it in the next 11 months
please someone tell me how to know if my phone nexus 5x will have bootloop.i bay this phone not new but used .i bay it from a shop he tell me is from usa and me from morroco.i dont have any paper of warranty or something like this i just have the phone...if the bootloop issus touch my phone what can i do?i have the warranty or not???i dont have mony to buy a new phone please help me
znayver said:
please someone tell me how to know if my phone nexus 5x will have bootloop.i bay this phone not new but used .i bay it from a shop he tell me is from usa and me from morroco.i dont have any paper of warranty or something like this i just have the phone...if the bootloop issus touch my phone what can i do?i have the warranty or not???i dont have mony to buy a new phone please help me
Click to expand...
Click to collapse
Well from what I know if you don't have warranty paper then you can't get warranty by just showing the phone . Its not a 100% chance that it will boot loop I think , but if your not safe with it I suggest selling it working rather than looking for help when broken . Thats just my point of view .
moonlightdrive said:
Hi, i guess that nobody could know that, but the problem seems to be the same as LG G4, LG V10, LG Flex 2 (all 2015 devices with almost the same motherboard that the Nexus 5x). You can search on the web "bootloop G4 reddit" "nexus 5x bootloop reddit" and you will find tons of reports, the majority of them (N5x) from last 3 months, and this holds the theory that is a welding issue on the CPU or sometimes on the EMMC chip (apparently LG did not weld very well that year...). The mentioned devices (included ours) seem to last from 9 to 14 months and finally the welding breaks. But now, we know it's strictly a HARDWARE issue NOT caused by 7.0 upgrade, irt's only a question of coincidence between the useful life of the weld and the launch of the 7.0 OTA.
So we all got very high possibilities that this occurs to our devices, eventually. I'm not sure that this is gonna happen to you, it really dependes of many many many factors (heavy usage, kernel profiles, temperature of your country/city/house/workplace, etc etc).
Maybe it never happens to you, but i know what you feel, is not very nice to feel that your phone could die in any moment. It was a low punch for me (i owned a G4 and it bootlooped twice) anyway i am going to sell my N5x due to this problem. Hope i help you with my point of view.
Click to expand...
Click to collapse
Well I think i have the same point of view to sell the phone working rather that having a paper holder . At least for me its the most logical thing to do maybe the chance isn't high for it to happen but I am not secure with a tought that my phone could die + im a heavy user so i migh make it to the boot loop faster .
Tarbruh said:
Well from what I know if you don't have warranty paper then you can't get warranty by just showing the phone . Its not a 100% chance that it will boot loop I think , but if your not safe with it I suggest selling it working rather than looking for help when broken . Thats just my point of view .
Click to expand...
Click to collapse
oooh nooo is there an application or something to know if the motherboard is fine or something like this and the bootloop dont affected my device??
znayver said:
oooh nooo is there an application or something to know if the motherboard is fine or something like this and the bootloop dont affected my device??
Click to expand...
Click to collapse
Well I don't know if there is or not but from what I know about the problem its random af , so I don't think there is unless only some motherboards are prone to the defect but I think it involves all , just happens randomly . Not 100% sure tho !
Tarbruh said:
Well I don't know if there is or not but from what I know about the problem its random af , so I don't think there is unless only some motherboards are prone to the defect but I think it involves all , just happens randomly . Not 100% sure tho !
Click to expand...
Click to collapse
tnx for your reponse my friend
znayver said:
tnx for your reponse my friend
Click to expand...
Click to collapse
No worries , best of luck