Related
Just to give you a brief rundown of everything that's happened..
I'm 17 and saved up for a few months to buy a HTC One X. Needless to say, it's probably the most expensive phone i've ever owned, since all my other phones were hand-me-downs and old phones from eBay.
This morning i wake up and go to work as usual. Just to find my phone's display won't switch on. As you can imagine, I'm tirelessly panicking and try the 3 button combo.. to no avail.
Using Fastboot to reboot didn't work either.
This phone turned into a brick overnight, and i have no idea what happened??
Just before i left for work, i did check my phone and it was working alright.. Then five minutes later, it won't display anything.
The thing is, I can't take it back to HTC either because this is my 5th replacement phone!
First one had black glue smudged on the LCD it's self,
Second one had the screen not glued down and wasn't aligned,
Third one didn't even have any glue applied and the case wasn't even attached properly,
Forth one had this problem where the screen's LCD would dilate if i touched it - even lightly,
and this one is my 5th, the antenna wasn't properly connected and now the screen doesn't work.
I've had terrible luck, and i don't know what i can do?
If you can give me any information to get me out of this, it would be much appreciated.
Although i still can receive text's and calls fine, it's just the display..
Since you’re unlocked and running a non-stock kernel and ROM, maybe some of the dev-ish folks can help you resuscitate it if it’s indeed a s/w problem.
If it’s a h/w problem, what to do depends on where you bought the phone and how old it is. If it’s within the remorse/DOA period maybe you can exchange it. It’ll be hard for whoever you bought it from to see you’ve unlocked it if nothing’s showing on the display.
If it’s outside of the exchange period you’ll have to send it in for repair. If you can’t bring it back to life to flash it back to stock you’ll have to throw yourself on the mercy of HTC Asia in getting it fixed unlocked. HTC's different repair centers seem to all have different policies related to warranty coverage for h/w faults on unlocked phones. If it is a dead display maybe you’ll get lucky.
You might want to put a note in with it telling your “I’m 17” story and how devastated you are something you’ve worked so hard for has failed. Repair techs are people too. Good luck.
BarryH_GEG said:
Since you’re unlocked and running a non-stock kernel and ROM, maybe some of the dev-ish folks can help you resuscitate it if it’s indeed a s/w problem.
If it’s a h/w problem, what to do depends on where you bought the phone and how old it is. If it’s within the remorse/DOA period maybe you can exchange it. It’ll be hard for whoever you bought it from to see you’ve unlocked it if nothing’s showing on the display.
If it’s outside of the exchange period you’ll have to send it in for repair. If you can’t bring it back to life to flash it back to stock you’ll have to throw yourself on the mercy of HTC Asia in getting it fixed unlocked. HTC's different repair centers seem to all have different policies related to warranty coverage for h/w faults on unlocked phones. If it is a dead display maybe you’ll get lucky.
You might want to put a note in with it telling your “I’m 17” story and how devastated you are something you’ve worked so hard for has failed. Repair techs are people too. Good luck.
Click to expand...
Click to collapse
I shook the device out of frustration.. and it started working for a few seconds.
What's going on here? Is it a faulty display/connection? Is there a way to possibly just send it to a nearby phone shop and get it fixed?
Sorry about all the questions, I'm shocked, happy, and devastated all at the same time.
Are HTC refusing then? That seems a bit off/ illegal... Surely under the faulty goods act (I assume the law isn't THAT different in Australia to UK) they have to take it back as it CAN'T be a year old and they can't prove the issue was caused by your mistreatment. It doesn't matter how many phones you've had... Also, where did you buy the phone from? I think you should be able to return it through the shop as THEY sold you the phone, not HTC... They are still under an obligation as they sold you the thing.
Plus, the 'I'm a 17 year old and saved up for ages thing' might work too! I'd try not to get too technical with the law if you go down this route though!
Best of luck sorting this out. It's within your rights to get a replacement (you bought the phone new, I assume?) so I'm sure this will eventually work out. Don't give up! You just need to speak/ write to the right person...
sent from my internet
What rom were you on?
I remember my One X not charging at all while it was turned off completely although it showed Orange charging led.
It could be that you ran out of battery and phone not turning on. Due to no charging effect.
@Op,
Reading your story there's one thing that's crossing my mind.
Could it be possible the battery run dry during the night?
It sounds stupid but those things you forget easy when you're in a hurry or stressed.
I don't read anything in your post you tried to charge.
Atrixx said:
Just to give you a brief rundown of everything that's happened..
I'm 17 and saved up for a few months to buy a HTC One X. Needless to say, it's probably the most expensive phone i've ever owned, since all my other phones were hand-me-downs and old phones from eBay.
This morning i wake up and go to work as usual. Just to find my phone's display won't switch on. As you can imagine, I'm tirelessly panicking and try the 3 button combo.. to no avail.
Using Fastboot to reboot didn't work either.
This phone turned into a brick overnight, and i have no idea what happened??
Just before i left for work, i did check my phone and it was working alright.. Then five minutes later, it won't display anything.
The thing is, I can't take it back to HTC either because this is my 5th replacement phone!
First one had black glue smudged on the LCD it's self,
Second one had the screen not glued down and wasn't aligned,
Third one didn't even have any glue applied and the case wasn't even attached properly,
Forth one had this problem where the screen's LCD would dilate if i touched it - even lightly,
and this one is my 5th, the antenna wasn't properly connected and now the screen doesn't work.
I've had terrible luck, and i don't know what i can do?
If you can give me any information to get me out of this, it would be much appreciated.
Although i still can receive text's and calls fine, it's just the display..
Click to expand...
Click to collapse
privatetrousers said:
Are HTC refusing then?
Click to expand...
Click to collapse
Yes. But not in every region (yet). Do a search. It's been disucssed. Also, it appears Samsung's going down the same path.
http://forum.xda-developers.com/showthread.php?t=1745834
BarryH_GEG said:
Yes. But not in every region (yet). Do a search. It's been disucssed. Also, it appears Samsung's going down the same path.
http://forum.xda-developers.com/showthread.php?t=1745834
Click to expand...
Click to collapse
Aware of the discussion... Using the xda app and didn't pick up that the phone's been 'HTCdev'd (my fault for not reading properly - sorry, folks!). Still not sure HTC/ Samsung can legally 'sign your rights away' though. Still, not a discussion for here...
Hope you got the phone sorted anyway.
sent from my internet
Atrixx said:
I shook the device out of frustration.. and it started working for a few seconds.
What's going on here? Is it a faulty display/connection? Is there a way to possibly just send it to a nearby phone shop and get it fixed?
Sorry about all the questions, I'm shocked, happy, and devastated all at the same time.
Click to expand...
Click to collapse
How or who fixed ur antenna problem, could be related if handset wasnt but back together properly.
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A 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.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*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!
Hi there, I hard bricked my Tab S 8.4. No reaction to anything I did (key combinations, let it charge for hours, stuff like that). Don't know how it happened but it just crashed to death shortly after installing an inofficial Lolloipop build from here. I don't think a ROM can make a device not turn on at all. My money is on hardware failure.
Anyway, brought it in for repairs (willing to pay since I knowingly voided the warranty). Got the call yesterday. They said the software had been tampered with and they can't repair it. I objected that the software won't break the hardware but no dice. They won't even do it for cold hard cash.
BUT: To see the 'illegal' software they HAD to get the thing to turn on . And if they got it to turn on somehow, so can I. Or... am I completely wrong there and they have some magic fairy dust?
Any ideas on how I could accomplish what the repair guys could obviously do? There is no important data or anything on it so I'd be happy with Odin mode, CWM or whatever.
dancress said:
Hi there, I hard bricked my Tab S 8.4. No reaction to anything I did (key combinations, let it charge for hours, stuff like that). Don't know how it happened but it just crashed to death shortly after installing an inofficial Lolloipop build from here. I don't think a ROM can make a device not turn on at all. My money is on hardware failure.
Anyway, brought it in for repairs (willing to pay since I knowingly voided the warranty). Got the call yesterday. They said the software had been tampered with and they can't repair it. I objected that the software won't break the hardware but no dice. They won't even do it for cold hard cash.
BUT: To see the 'illegal' software they HAD to get the thing to turn on . And if they got it to turn on somehow, so can I. Or... am I completely wrong there and they have some magic fairy dust?
Any ideas on how I could accomplish what the repair guys could obviously do? There is no important data or anything on it so I'd be happy with Odin mode, CWM or whatever.
Click to expand...
Click to collapse
I kindof had the same problem, but got mine repaired.
May I ask where you send it to for repairs? Was it Samsung or a local repair shop that told you they could not fix it?
And did they send it back to you? Kindof weird they won't fix your device after you say you are willing to pay for it.
Depending on where you live, Samsung covers a lot of 'problems' in the first year of the standaard warranty.
As for turning on the device..
What options have you tried yet?
If you connect the tablet with usb to your pc and turn it on, does it get recognized?
And if so, as what?
But if your screen doesn't turn on, you're probably going to need repairs anyway.
shifter7 said:
I kindof had the same problem, but got mine repaired.
May I ask where you send it to for repairs? Was it Samsung or a local repair shop that told you they could not fix it?
And did they send it back to you? Kindof weird they won't fix your device after you say you are willing to pay for it.
Depending on where you live, Samsung covers a lot of 'problems' in the first year of the standaard warranty.
As for turning on the device..
What options have you tried yet?
If you connect the tablet with usb to your pc and turn it on, does it get recognized?
And if so, as what?
But if your screen doesn't turn on, you're probably going to need repairs anyway.
Click to expand...
Click to collapse
Over here you bring it back to the shop where you bought it. They will try the simplest solutions in house but usually send it back to the manufacturer. I think the information came from Samsung directly. Another theory I have is a simple lie. They tried it in house, nothing came up, some clever guy screamed 'CYANOGEN!' and they all high fived (I have a vivid imagination )
As for turning it on: tried everything. It's not only the screen, it did nothing at all. No signs of life whatsoever. Of course the PC wouldn't recognize it since it was turned off.
I'll pick it up tonight. Maybe whatever they did to see the software tampering stuck and it will at least go into Odin mode. I can work from there.
dancress said:
Over here you bring it back to the shop where you bought it. They will try the simplest solutions in house but usually send it back to the manufacturer. I think the information came from Samsung directly. Another theory I have is a simple lie. They tried it in house, nothing came up, some clever guy screamed 'CYANOGEN!' and they all high fived (I have a vivid imagination )
Click to expand...
Click to collapse
I lolled
But it you think it came from Samsung directly, then I would advise you to contact Samsung.
Here is a link from an article where it states that Samsung covers bricked devices, but only the first time. (Dutch article, GTranslated english)
I have no idea if this also counts for where you live though.
https://translate.google.com/transl...er-garantie-repareren.html&edit-text=&act=url
dancress said:
As for turning it on: tried everything. It's not only the screen, it did nothing at all. No signs of life whatsoever. Of course the PC wouldn't recognize it since it was turned off.
I'll pick it up tonight. Maybe whatever they did to see the software tampering stuck and it will at least go into Odin mode. I can work from there.
Click to expand...
Click to collapse
Okay.. well.. that sucks.
Don't forget to ask for some of that magic dust they used
shifter7 said:
I lolled
But it you think it came from Samsung directly, then I would advise you to contact Samsung.
Here is a link from an article where it states that Samsung covers bricked devices, but only the first time. (Dutch article, GTranslated english)
I have no idea if this also counts for where you live though.
https://translate.google.com/transl...er-garantie-repareren.html&edit-text=&act=url
Okay.. well.. that sucks.
Don't forget to ask for some of that magic dust they used
Click to expand...
Click to collapse
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
dancress said:
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
Click to expand...
Click to collapse
I'm laughing so hard right now :laugh::laugh::laugh::laugh::laugh::laugh:
dancress said:
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
Click to expand...
Click to collapse
It simply reset itself after the battery completely died. Black screen and no response doesn't mean the device is off.
As soon as they switched it on they would have seen knox had been tripped.
Sort of did you a favour by telling you it wasn't bricked.
I had the same sort of problem i connected my tab to my laptop and used the recovery mode key combination then my tab came back to life
---------- Post added at 04:29 PM ---------- Previous post was at 04:29 PM ----------
Sorry download mode not recovery mode
Comforts me while ROM developing that the only reported case of a hardbrick was here - and the battery just died.
Hi all,
so here is my problem.
Day before yesterday i had a perfectly working LG g4 H815 model with s/n 511 running on firmware v20h, when i decided to root it and install some mods.
so i flashed TWRP, installed xposed and xtrememusic mod. the phone booted normally after installing these. i didn't install any modules under xposed. the phone worked perfectly for two days. however today morning it hanged while taking photo with the camera app. when restarting it got stuck at LG logo for long time. My brother(who doesn't have any technical knowledge) pulled out the battery and restarted. Again it got stuck at LG logo. thinking somthing wrong he again repeated this only to find that it didn't power on at all this time. No LG logo no notofication light nothing.
Tried charging it(although battery was aroung 60-70%), pressing power button removing the battery. still nothing. the phone is not at all powering up.
However when i connect it with USB cable with laptop, laptop makes sound of getting usb connection detected. i took it to a service centre.
the technical guy there told that IC may have been faulty. he told me that motherboard needs to be replaced. however unofficially he may try heating the IC to get it booting.
What should i do now? Is the IC really fried. had the rooting and installing mod caused it?
Please help.
PS- the phone is imported and cannot be sent back for warranty purpose.
I think you are experiencing the dreaded LG G4 bootloop. I don't think rooting or modding caused a software problem. It "may" have caused a hardware problem simply because it generated enough heat to loosen the IC that little bit that initiates the problems you are describing. I rooted and installed the stock image in Nov 2015. Two weeks ago the phone froze - restarted and then could not be booted. LG sent me a Fedex label and I sent it off. Ten days later I received the same phone back. I assume they replaced the mainboard.
You should contact LG directly. I saw a class action suit that was called off because it appeared that LG will fix this particular problem (failed mainboard) out of warranty. Anyone please correct me on this if I'm wrong.
dsteinschneider said:
I think you are experiencing the dreaded LG G4 bootloop. I don't think rooting or modding caused a software problem. It "may" have caused a hardware problem simply because it generated enough heat to loosen the IC that little bit that initiates the problems you are describing. I rooted and installed the stock image in Nov 2015. Two weeks ago the phone froze - restarted and then could not be booted. LG sent me a Fedex label and I sent it off. Ten days later I received the same phone back. I assume they replaced the mainboard.
You should contact LG directly. I saw a class action suit that was called off because it appeared that LG will fix this particular problem (failed mainboard) out of warranty. Anyone please correct me on this if I'm wrong.
Click to expand...
Click to collapse
Hi thanks for the help.
But isn't the dreaded bootloop is that where the phone is stuck at the LG logo. Mine isn't booting at all. And the bootloop problem is due to big cores or such and not due to ic?
Mine wouldn't start at all - it bootlooped once for about a split second - then it was dead
Same is the problem with me. Bootlooped twice and then its completely dead. I have tried contacting Lg UK. Lets see what they say.
Ok so i got a reply from LG and they suggested me some steps to take (which are obviously not useful as it is completely dead). however they have also told me that they are willing to help me and asked me about details of purchase etc and "whether it was rooted".
so what should i reply rooted or not? will they detect it as it is dead.
dbzgoku said:
Ok so i got a reply from LG and they suggested me some steps to take (which are obviously not useful as it is completely dead). however they have also told me that they are willing to help me and asked me about details of purchase etc and "whether it was rooted".
so what should i reply rooted or not? will they detect it as it is dead.
Click to expand...
Click to collapse
Sorry to be late on reply. I advise to not answer question whether phone was rooted. Here is my reasoning:
1. This problem is widely occuring - only a tiny percentage of people root their phones therefore question is irrelevant.
2. The problem is known to be that an IC becomes loose most likely due to heat - a better question would be - do you place the phone on a hot dashboard with GPS running while you are charging?
dsteinschneider said:
Sorry to be late on reply. I advise to not answer question whether phone was rooted. Here is my reasoning:
1. This problem is widely occuring - only a tiny percentage of people root their phones therefore question is irrelevant.
2. The problem is known to be that an IC becomes loose most likely due to heat - a better question would be - do you place the phone on a hot dashboard with GPS running while you are charging?
Click to expand...
Click to collapse
thanks for the reply (although late). i have already sent the phone to LG replying as no root. Lets hope they repair it without any problems.
second i didnt do anything of anysort like placing on hot dashboard or such. one day while opening the camera app it decided to just hang and later on die on me.
I hope you didn't think I was saying you might have done something that would overheat your phone such as my second example. I was trying to come up with an example reason the IC loosens. Even if you did that the phone should survive such conditions. Let's hope the replacement motherboards somehow do better. My guess is that the soldering job is fine, the problem is probably bad design that doesn't "vent" the heat from chip.
dsteinschneider said:
I hope you didn't think I was saying you might have done something that would overheat your phone such as my second example. I was trying to come up with an example reason the IC loosens. Even if you did that the phone should survive such conditions. Let's hope the replacement motherboards somehow do better. My guess is that the soldering job is fine, the problem is probably bad design that doesn't "vent" the heat from chip.
Click to expand...
Click to collapse
so what do you suggest after repair should i keep it or sell it? Lg g4 is no doubt the best phone when considering the value for money. no phone even twice in price comes close in camera and screen quality especially. but the unreliability of this phone has made me to consider selling it as soon as i get it back.
I'd keep it if your new board is high serial
lukem99626 said:
I'd keep it if your new board is high serial
Click to expand...
Click to collapse
Well my old board was also high serial, beginning with 511
I'm going to take my chances - it's a great phone until it bootloops. I'm going to avoid scenarios best I can that could result in the phone heating up inside. That would be charging only if absolutely necessary while in my ProClip dash mount if the car is hot, using backup battery after depletion instead of charging more often etc. Thinking back I rarely put the phone into heat inducing situations - normal use results in the IC becoming loose at the 1 year mark. If mine bootloops exactly a year from now and LG fixes it again I'm an LG fan. If they blow me off no more LG.
I really regret not paying it off early and taking the $15/month deal for an S7 Edge last month
dbzgoku said:
Well my old board was also high serial, beginning with 511
Click to expand...
Click to collapse
I mean like 611 ect thats what i got from lg
dsteinschneider said:
I'm going to take my chances - it's a great phone until it bootloops. I'm going to avoid scenarios best I can that could result in the phone heating up inside. That would be charging only if absolutely necessary while in my ProClip dash mount if the car is hot, using backup battery after depletion instead of charging more often etc. Thinking back I rarely put the phone into heat inducing situations - normal use results in the IC becoming loose at the 1 year mark. If mine bootloops exactly a year from now and LG fixes it again I'm an LG fan. If they blow me off no more LG.
I really regret not paying it off early and taking the $15/month deal for an S7 Edge last month
Click to expand...
Click to collapse
Well lg did mention in my communication with them that this carries 2 year warranty.
lukem99626 said:
I mean like 611 ect thats what i got from lg
Click to expand...
Click to collapse
Didn't know that serials have gone so high
dbzgoku said:
Didn't know that serials have gone so high
Click to expand...
Click to collapse
I brought a g4 in the new year sale it has the serial of 611 i had a 601 few months back i returned it ran hot and laggy the 611 one is cool running and lag free so i think something changed
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
@gwynlordofcinder: sad for you. But why you ask the same question as 20 others before? Try freezer and/or oven to get back the mainboard-connections. If successfull, you can save your data or go on with a kernel-profile which makes the big core sleep. Use search for details.
gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.
Most likely fixable, but with the need of special files.
Search up on QD Loader 9008 on this subforum and read through it.
i'm on the hunt to find a fix for it, hopefully i'll make it. gonna share my findings asap!
Voicebox said:
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.
Click to expand...
Click to collapse
There is no extended warranty in the UK, which is where I purchased the phone.
gwynlordofcinder said:
There is no extended warranty in the UK, which is where I purchased the phone.
Click to expand...
Click to collapse
Since this happened from normal usage and not from you installing a custom ROM or updating the bootloader, or something like that, I think you have the bootloop problem. I normally think of a hard brick being the result of flashing say the incorrect bootloader, or a corrupt file, etc. which can then hopefully be undone by software means to get the right software back on there.
If you have the bootloop, it is a hardware problem. The fact that the phone doesn't bootloop does not mean you don't have the hardware problem. Boot looping was just the most common way to identify it, but many, like mine would just either never even start booting, or would start, then go black.
If you don't figure out any software way to do anything, then try to look for bootloop fixes. Searching for that might get you further. But with a hardware problem, everything except the fix for disabling the big cores (in XDA threads), is temporary unless you are lucky.
Assuming you have a hardware issue, here's some steps to maybe try. I was able to get the rescue fix installed on my phone after using a hair dryer on the motherboard. But that didn't fix anything since my problem was hardware. But if your OTA update was maybe slightly corrupted, maybe it'll help.
https://productforums.google.com/forum/#!topic/nexus/G_0s70PzK_s
To jump right to trying a rescue OTA, go here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/hdrNONCCoNE
If it doesn't react enough to do anything from a computer, you may have to resort to putting it in the freezer for a while first. Which may give a short period where it'll boot and you can maybe adjust the settings so you can try one of the XDA fixes that disable the big cores.
One fix that disables the big cores:
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E
Voicebox said:
which can then hopefully be undone by software means to get the right software back on there.
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E
Click to expand...
Click to collapse
except that the files needed for unbricking corrupt bootloaders/eMMCs' are so hard to find it's incredible.
bought a used 5X that "suddenly died in a pocket", now that you mention all of this, i might try doing the hardware fixes and then apply the big core disabling and hopefully get my phone to work.
the phone did get serviced though, so they might've installed bad firmware since the phone is in QDLoader & in EDL mode (PC recognizes the phone, while fastboot/adb/LGUP doesn't)
gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
Can you update driver "QHSUSB_BULK" in device manager by choose driver manually . I have problem like this in Inew V3 (Chaina Phone) and can fix by choose driver manually.