Hard Brick on LS991 - G4 Q&A, Help & Troubleshooting

Hi
The other day I was looking for cell ID info on my LG G4 that I have had for a long time in the "hidden menus". I accidentally clicked on the radio test and the screen froze up. I tried to get out of it, but noting would work, not even the power button. After a few minutes, I saw the power off sequence. When I went to turn if back on, it would not power on. I plugged it in, no charge. I tried to boot to recover, nothing. I have the service manual for the h815 variant which differs from mine. I do not have a boardview or anything.
I know trying to permanently fix it is a lost cause, it is old and it had other problems, such as the headphone jack not working even after I replaced it, and the read camera's autofocus being stuck after I replaced it with a cheap knockoff. However, I want to get it running long enough to get important things off of it. I was foolish and a few of my 2FAs are only on that device, and while I have gotten most of them switched to my alternate, I need to make sure to get the rest. I'm not sure which troubleshooting route to follow: Power? Crash/No Boot? No charge? I would follow each but some of the differences between the board I have and the service manual includes a few of the test points I need. Currently I have to attach wires to my multimeter leads to get small enough tips.
If anyone has anything that can help me get this running for a bit, let me know please.\
edit: biggest problem is I don't know how to tell from the schematic what pin is which on the board

Catt0s said:
Hi
The other day I was looking for cell ID info on my LG G4 that I have had for a long time in the "hidden menus". I accidentally clicked on the radio test and the screen froze up. I tried to get out of it, but noting would work, not even the power button. After a few minutes, I saw the power off sequence. When I went to turn if back on, it would not power on. I plugged it in, no charge. I tried to boot to recover, nothing. I have the service manual for the h815 variant which differs from mine. I do not have a boardview or anything.
I know trying to permanently fix it is a lost cause, it is old and it had other problems, such as the headphone jack not working even after I replaced it, and the read camera's autofocus being stuck after I replaced it with a cheap knockoff. However, I want to get it running long enough to get important things off of it. I was foolish and a few of my 2FAs are only on that device, and while I have gotten most of them switched to my alternate, I need to make sure to get the rest. I'm not sure which troubleshooting route to follow: Power? Crash/No Boot? No charge? I would follow each but some of the differences between the board I have and the service manual includes a few of the test points I need. Currently I have to attach wires to my multimeter leads to get small enough tips.
If anyone has anything that can help me get this running for a bit, let me know please.\
edit: biggest problem is I don't know how to tell from the schematic what pin is which on the board
Click to expand...
Click to collapse
Sounds like the ilapo but as you have modified the hardware it can be everything of course . anyways it wouldn't hurt to try some of the Bootloop fixes which you can find in my signature . Your best chance might be flashing the TWRP version for the ilapo and trying to load the recovery. Another option is of course to get into download mode and use salt to backup the user data partition.
Ilapo TWRP (when your device is unlocked only):
https://leech.binbash.rocks:8008/TWRP/ILAPO-O/
SALT (included in mAid / fwul): http://bit.do/FWULatXDA
Sent from my OnePlus 7T Pro using XDA Labs

Related

Help required, possibly bricked?

Hi all,
Hopefully you can help me, i have just installed the latest radio and Modaco ROM (this isn't the first time i've did this).
After installation i got what looked like an image of a drive and an arrow, i assume this meant it couldnt find the boot image. I then tried a couple of times to reboot holding the home key but now i cant even switch it back on... even on charge the light isn't coming on
Any help would be gratefully appreciated
Thanks
GF
When the arrow and drive comes up, you're meant to leave your phone well alone, it means it's flashing something (usually something important!)
If your phone doesn't turn on, sounds like you've made a full hard brick, nothing you can do but see if you can get it repaired.
Gutted, cheers
Can you pull the battery and get into fastboot?
Breakthecycle2 said:
Can you pull the battery and get into fastboot?
Click to expand...
Click to collapse
Not sure what that is? I've tried the various power+key sequences
Thanks
GaelForce said:
Not sure what that is? I've tried the various power+key sequences
Thanks
Click to expand...
Click to collapse
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
docsamsom said:
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
Click to expand...
Click to collapse
Worked a treat, got a doorstep exchange today
Thanks

[Q] Gingerbread G2 Screen DEAD / returning to Tmo / Help please

Ok guys, Long time lurker, First time poster here.
Been hanging out around the forums for a while now, but this is the first problem I've ever had that I just couldn't figure out on my own.
Screen dead. Have to return to TMO. What to do about existing rom???
Last Saturday night I was playing around with my phone before bed. Everything was fine. Woke up in the morning and the screen was dead.
The backlight comes on but no display what so ever. No HTC screen, no bootflash, no nothing. Everything else still works.
I can feel events happening on the screen when I touch so the digitizer is clearly up to snuff.
Also I have been able to get the phone into fastboot from memeory, so its a start.
I contacted Tmo about a replacement and it arrived today. I'm running GingerVillian 1.4. So the big question is what do I do about the ROM on my phone. Also, what happens if they get the phone back and discover it has been rooted. Will I get a bill for the full price of the unit? Anybody know??
The way I see it I have three options, but if I'm missing something please let me know.
1. Attempt to flash stock ROM via recovery using up down vol and track pad. And just not worry about S-off. If it looks the look, will they check Hboot for s-off???
2. Attempt a side by side deroot using the new G2 and the broken one next to each other.
3. Physically damage the memory somehow preventing the phone from booting.
#2 seems like the worst option simply because I will have no way of verifying that any step in the process is successful... (Scary prospect) of course this applies to option 1 as well but I figure I could go through the flash process two or three times just to be sure. Option three doesnt exactly sound like a winner either, just putting it out there.
Comments please, a little help would be greatly appreciated.
I would go for the blind flash of pcimg10 from sd root. Then plead ignorance. Confused tho ...did u say u can see the bootloader txt or no?
Sent from my HTC Vision using XDA App
No, screen displays jack squat, nada.
Also wasnt there a huge writeup about how I'm not supposed to flash pcimg10...?
Bluetygator said:
No, screen displays jack squat, nada.
Also wasnt there a huge writeup about how I'm not supposed to flash pcimg10...?
Click to expand...
Click to collapse
Depends on how you're rooted. I'm gfree'd and every now and then I'll copy that out to sd root and reflash it. It flashes fine, unroots the phone, but still leaves s-off. I've been thinking about this - again- after reading your post because I've thought this would be the worse-case scenario. That is a screen in some state where you just can't see what's going on.
If it were me, I'd at least want the factory load on it and hope that should they run some diags, put on a new LCD then boot it up, it could all be done without really noticing the s-off in bootloader.
For me though, I just would have a hard time physically damaging it - that would get me a 130$ refurb on my handset protection or if I tried to just kill some internal IC like the ram, I'd be even more worried they'd eventually find that for what it was.
edit: obviously your number 1 is the easiest since it's just answering volume up after giving it a few minutes on boot to parse the pcimg10 file.
edit2: okay, how about, hook jumper cables to it, blast it, then send it back and just claim you were hit by lightning
I'm perm rooted using visonary r12.
Yeah not going to damage it. I just wouldn't have it in me.
What worries me is if I flash pc10.img and something goes wrong I would have no way of even knowing it. Was thinking about just regular old CM6.1.
You people worry too much. Just send it in. As long as they receive an intact G2 with no physical damage to the screen (this bit is crucial if you got a swap out for anything screen-related) then you'll be just fine.
I have read on more than one occasion that if you cant turn on or see screen, as long as ur void stickers are still intact, and there is no water damage (moisture detectors all ok) they do not care.
Though not confirmed.
EDIT..... But if I were in your position then I would do as ZKID suggested with the pc10img thingy.
if there is nothing on the screen, it sounds to me that maybe the copper ribbon on the phone that attached the bottom of the phone with the keyboard to the screen portion could be damaged or loose... this happend with a buddies g2 and he was rooted and everything like you... he just sent it in as is and they never mentioned anything to him or gave him any problems because if it. he thinks they just saw the screen wasnt working and that was it.

[Q] Bricked T999

I have a GS3 that was rooted with a CM rom. I was using it the other day and the screen just suddenly went black. I tried rebooting it and popping out the battery, but to no avail. I can't boot it into download or recovery mode either.
When I put in the battery, the phone vibrates but nothing else. When I plug in the USB cable with no battery, it vibrates and the LED comes on for a few seconds before flickering off.
My first priority is data recovery, I've been a bad boy and haven't backed up my data for a while. My second priority is making it so they can't tell I have a flashed ROM when I send it out for warranty service, though AFAIK, this may be a nonissue.
I tried to make a 300k jig, and it didn't work (assuming I got the pins right).
Have you tried KAsp3rd's debrick method?
Stickies in development.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Have you tried KAsp3rd's debrick method?
Stickies in development.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I'm not stuck in QHSUSB-DLOAD as far as I can tell. Would it still be effective?
Could be. It basically allows you to boot download mode from the sdcard. From there you Odin flash the firmware and hopefully that would fix it. But if it's a hardware failure, which it could be per your description, I doubt anything will work.
Sent from my SGH-T999 using Tapatalk
New update. I figured out that the 300k ohm resistor trick DOES work, but only for like three seconds. Meaning that they'll be able to see the custom binary count, but (as far as I know) I can't reset it to 0.
The weird part is that it only works if I plug the usb jig into the phone before putting the battery in, if I put the battery in first, it doesn't work. It almost seems like it constantly thinks the power button is being pressed or something.
I guess I'm opening it up and looking for a short. The power button operates normally tactile-y speaking.
EDIT: new new update. I wasn't able to find anything physical when I looked at the pcb. But I verified my theory, somewhat. When I hold home and volume up/down (without touching the power button) when I put the battery in, it boots into download mode for a second before shutting down.
It's not behaving exactly like it would if it was only that though, because I tried holding the power button down on the t999l I got as a replacement, while inserting the battery, and the boot screen shows up for a few, where a boot screen never shows up on the bad phone.
DOUBLE EDIT: can I swap that pcb with the one from the t999l, or are they too dissimilar? Would I be able to swap it with one from another t999, or does the board that has the power switch also have the onboard storage?
TRIPLE EDIT: I answered my own question, the eMMC and the power switch are on the same board. But if the fault is caused by something else (e.g. a camera), would I be able to plug all the other hardware from the t999l into the t999, or can I just boot up the t999 without most of the hardware connected as a test?
I would not risk going through all that trouble. Not quite sure why you would honestly. You got a T999L right? Warranty replacement I assume? It's a superior device so why my not just use it as is?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
I would not risk going through all that trouble. Not quite sure why you would honestly. You got a T999L right? Warranty replacement I assume? It's a superior device so why my not just use it as is?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
1. I really want my data back.
2. I risk getting charged for out of warranty if they see it was rooted and flashed.
3. I'm going to sell it anyways, I got a note 3 because the S3 was on backorder and I couldn't do my job without a smartphone.
1. I'm sorry to say, but plan on this not being possible.
2. If it won't boot there is little chance you'd have to worry about it. They aren't going to go to extraordinary measures to check k the counter. Many people have claimed they sent a dead device back and never got charged, even though the counter had been tripped.
If you damage the good hardware you won't have much to sell.
I don't understand why you'd be willing to attempt to Frankenstein the two devices, but not at least attempt the debrick method I mentioned.
Also, you should be aware, even if it's something else, not a bad chip, it probably won't work. Much of the hardware is in fact different between the two. Different camera, different radios, different SoC....
I wish you luck if you decide to try this, but imo you are taking an awful big risk to try something that probably won't work anyway.
If your data is really that important maybe you should look into a data recovery service.
And in the future, back up back up back up!
Good luck whatever you decide. Let us know what happens.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
1. I'm sorry to say, but plan on this not being possible.
2. If it won't boot there is little chance you'd have to worry about it. They aren't going to go to extraordinary measures to check k the counter. Many people have claimed they sent a dead device back and never got charged, even though the counter had been tripped.
If you damage the good hardware you won't have much to sell.
I don't understand why you'd be willing to attempt to Frankenstein the two devices, but not at least attempt the debrick method I mentioned.
Also, you should be aware, even if it's something else, not a bad chip, it probably won't work. Much of the hardware is in fact different between the two. Different camera, different radios, different SoC....
I wish you luck if you decide to try this, but imo you are taking an awful big risk to try something that probably won't work anyway.
If your data is really that important maybe you should look into a data recovery service.
And in the future, back up back up back up!
Good luck whatever you decide. Let us know what happens.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Reading through the whole thread, I am going to agree with the Doc. Why would you go to all that trouble ? Nobody is going to be able to salvage that data, let alone snoop in it. You are best move on rather than Creating that Frankenstein Monster as Doc aptly put it.
The frankenphone would only have been for if the phone didn't work without the camera/speaker/etc connected. However when I disconnect everything from the main board except for the screen, I get the same behavior. So I guess the only thing I would want to test would be the touchscreen. I can't find any info on if the t999l touchscreen is compatible with the t999 board, but if anyone knows, that would be great.
I'm still going to try the microsd card debrick method, I was concentrating on the usb jig last night since that got me further than anything else so far.
As to why, I have pictures and whatnot on the phone that I want to save, as well as a bunch of work crap that will take me dozens of hours to recreate, plus a bunch of other personal stuff. If I can't get it, then I can't get it, but I want to exhaust my resources (within reason) before giving up.
dubloe7 said:
I'm still going to try the microsd card debrick method, I was concentrating on the usb jig last night since that got me further than anything else so far.
As to why, I have pictures and whatnot on the phone that I want to save, as well as a bunch of work crap that will take me dozens of hours to recreate, plus a bunch of other personal stuff. If I can't get it, then I can't get it, but I want to exhaust my resources (within reason) before giving up.
Click to expand...
Click to collapse
Try JTAG instead of this if sdcard doesn't work. Most of t999l hardware is supposed to be identical. Since partition are potentially different. So phone may not boot. But you might be able to do adb. Good luck.
Actually it's the other way around. Partition layout is the same (though firmware incompatible) and hardware is definitely different.
Sent from my SGH-T999 using Tapatalk
SD card didn't work, looking for jtag instructions.
EDIT: The more I look, the more it looks like a faulty power switch. Unfortunately, it doesn't look like I have a way to short the power switch or something in a way that doesn't void the warranty...
Any help on this is appreciated.
Well, I think I'm completely screwed now.
I found this, http://androidforums.com/samsung-ga...-help-black-screen-vibrating.html#post5262715 and somehow managed to lift the freaking solder pads.
What do you think the chances that they won't charge me a couple hundred dollars for "out of warranty service" are?
EDIT: good news: Confirmed that the cable that I lifted the solder pads on, which I assume is an antenna, probably isn't the problem (unplugged it on the t999l, and it works fine).
bad news: I also confirmed the power switch itself isn't the problem either. The left and right hand side aren't connected (according to my multimeter) when the button isn't pressed, but they are when it is.
Another edit: I unconfirmed the power switch part. It looks like the button only needs the slightest contact in order to short. I removed the power button from the case, surprisingly difficult since I saw people complaining about it falling out. Now the difficult part is making it think the switch is closed for long enough to not turn it on, but not long enough to turn it back off. I've gotten it to the boot logo, but I haven't gotten it to fully boot.
Yet another EDIT: the only way I can get it to turn on long enough to see the boot logo is by smacking it in my hand after it turns on, which seems to interrupt the constant button press signal. From the metering on the switch, it seems that even less contact is needed to turn on the phone than to signal the multimeter. Any suggestions as to somewhere to cut the power switch signal other than the power switch?

i've been blue screen'd D:

on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Quote100 said:
on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Click to expand...
Click to collapse
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
startswithPendswithOOH said:
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
Click to expand...
Click to collapse
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Board expired
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
It's time to move on.same happened to me a week ago.and I found the reason that my charger was at fault .the charger damaged one of the ics.it causes the board to draw a lot of current and causing severe heating issue within seconds.
So,better buy a new phone.
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
startswithPendswithOOH said:
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
I also ventured for the oven.and within 2 seconds.my board was gone...oven trick is just a sarcasm.don't go for it.
You can extra life of 30 minutes by giving it a Sunbath for some time.
My bad - misquoted a poster.
I kind of forgot about this thread whoops
Well I have news for you guys, I got a used g3 from eBay and wanted my apps from my old phone back and you know what I did?
I stuck it into the oven. I **** you not, after 375 for 5 minutes it started working again and I was able to get my apps and data to an SD card. Its still working but I took the battery out of it to use with the replacement. Can't believe it worked tbh

Nexus 5x shut off and won't turn on

If I posted this in the incorrect place or there is something related to my issue, I apologize in advance.
I've been searching here and all over the internet and no progress yet so I decided to make a new account here just to see if anyone can help me because I'm out of ideas right now.
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas. I just want to at least recover some pictures and information I have in it that isn't backed up, if anyone can help me I would greatly appreciate it.
Thanks in advance
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
At this point, I'm willing to try anything. Thanks
driss.sadok said:
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
Click to expand...
Click to collapse
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
PennyScissors said:
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
Click to expand...
Click to collapse
Same here... cannot enter recovery mode, so flashed new rom stock rom.
The flashing was fine but it didn't help.
guys if u can get to the bootloader, sure it can be fixed.. everything is possible with the fastboot, u can fix any issue. if it's a hardware issue the bootloader wouldn't work as well.
Re Nexus 5X won't turn on - I've had same issue
PennyScissors said:
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas...
Click to expand...
Click to collapse
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
danielledowns01 said:
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
Click to expand...
Click to collapse
I contacted Google and they didn't help me at all because my warranty expired last month, they literally just told me to put in a repair request at the LG repair webpage....this sucks
My experience exactly...
My wife's Nexus 5 exhibited the exact same symptoms this morning. It's been running perfectly for 20 months and today it died, and we're unable to even get into the bootloader screen or power on the phone.
Taking your advice, we put it in the freezer for 15 minutes and were able to perform a factory reset wiping all data from the phone. We are going to take advantage of Google's Christmas 2017 promotion and return the Nexus 5X and buy a Moto 4X. They require you perform a factory reset before returning the phone in order to receive a credit for the returned Nexus 5. Thank you so much for the help!
Dennis
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-5x/help/help-nexus-5x-lg-off-to-t3729739
I've just posted this thread overlooking yours. I think this is becoming another common issue. Has the freezer trick worked with anybody else?
I am having the same issue described here. My Nexus 5x went into a Bootloop about one month ago, but I was able to get it working again by going into Recovery Mode. About 4 days ago it went into a constant Bootloop, just showing the Google screen, and I couldnt get back in to recovery mode. I ordered a new phone on Tuesday (Pixel 2) and as long as I am able to do a factory reset I should get a $150 credit when I send this phone back. So, in desperation, I took a chance on the 15 minute freezer trick, and it worked! I was able to get into recovery mode (power + volume down, select Recovery Mode, little dude on his back came up, pushed power + volume up once) and cleared the cache and applied the factory reset. Ridiculous that this phone only lasted 18 months, but if I get the $150 credit I will be happy.
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
d_ckhole said:
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
Click to expand...
Click to collapse
The only way to connect that buddy to PC is to get SoC (CPU) working, so theoretically you can go towards reballing the chip. But I guess it's not an easy thing for such a little chip. Also u will need kinda plate for balls, i think there are no common ones, so u can make it yourself if have a technical education.
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
orcgoblinsupply said:
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
Click to expand...
Click to collapse
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
d_ckhole said:
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
Click to expand...
Click to collapse
I've seen a post of a guy who sent his motherboard to china and got reballed it and gained 4gb of ram. Can be wrong, but it was around $50 and a month of time.
---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------
Actually found the post itself: https://4pda.ru/forum/index.php?showtopic=722679&st=3440#entry68093395 (it's in russian, so u're welcome at translate.google.com) In short - a guy fount a Chinese service and men in the middle who could resend his motherboard to china, it cost him $100

Categories

Resources