Develop Bugs

hard bricked my phone

Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.

Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.

If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.

brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.

Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux

republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?

If you can't get the phone to turn on you're out of luck.

Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.

thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.

kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots

You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800

lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?

kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/

Call Google and get it replaced. They are very good about that stuff.

kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!

Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.

Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.

kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?

That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!

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

Need help!! LG G4(H815) not starting

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

Questions about bootloop, warranty & repairs and heatsink mods

Hello!
Unfortunately, just some days ago my 5X died. Was on the table, it rebooted itself and then it was stuck in a bootloop. I wasn't even able to use the recovery, and none of the 4-cores mod worked to help me get some of my files. I even opened it, disconnected the battery and reconnected it, but nothing.
So, I send it oot for repairments; luckily I still have 3 months of warranty (I live in Italy). However, I have some questions that maybe you can help me clear out:
Will LG be able to see that I opened the back cover of the phone and also that I modified its software?
Before sending it, since at least fastboot was working without issue, I flashed a stock factory image of Oreo and re-locked the bootloader (also like this, it wasn't booting however), so it was totally stock, but they can see that the bootloader has been unlocked and relocked?
I'm a little worried about LG discovering these things and make me pay for the repairments...
Hoping to getting it back repaired for free, will it be safe from the bootloop issue or it can happen again? Since it's a known problem, does LG started repairing with motherboards with better solderings, or I will find myself in the same situation as now?
If answers to question 2 is "no, they will put inside it the same faulty motherboards", there's anything I can do to prevent this issue? I saw someone using copper plate heatsinks to contrast heat, what do you think about that?
Thank you!

Punkiderma said:
Hello!
Unfortunately, just some days ago my 5X died. Was on the table, it rebooted itself and then it was stuck in a bootloop. I wasn't even able to use the recovery, and none of the 4-cores mod worked to help me get some of my files. I even opened it, disconnected the battery and reconnected it, but nothing.
So, I send it oot for repairments; luckily I still have 3 months of warranty (I live in Italy). However, I have some questions that maybe you can help me clear out:
Will LG be able to see that I opened the back cover of the phone and also that I modified its software?
Before sending it, since at least fastboot was working without issue, I flashed a stock factory image of Oreo and re-locked the bootloader (also like this, it wasn't booting however), so it was totally stock, but they can see that the bootloader has been unlocked and relocked?
I'm a little worried about LG discovering these things and make me pay for the repairments...
Hoping to getting it back repaired for free, will it be safe from the bootloop issue or it can happen again? Since it's a known problem, does LG started repairing with motherboards with better solderings, or I will find myself in the same situation as now?
If answers to question 2 is "no, they will put inside it the same faulty motherboards", there's anything I can do to prevent this issue? I saw someone using copper plate heatsinks to contrast heat, what do you think about that?
Thank you!
Click to expand...
Click to collapse
Hi, I'm Italian too and I had your same problem.
1) My phone died and 20 days before the end of the warranty and I sent it to the repair center.
As you, I opened the device and also I wasn't stock, so I reflashed google stock image and I re-locked the bootloader. The repair center has fixed my device changing the mobo and they didn't charged me for anything.
2) I don't know if they have a new rev. of the mobo that fixes the bootloop problem, but I'm going to apply the copperhead heatsink mod and maybe I will underclock the cpu with EX kernel.
3) I hope that the copperhead mod works, I saw some benchmarks and it seems that this heatsink will lower the temperature by 5/7 degrees.
I'm sorry for my English

CapraNorvegese said:
Hi, I'm Italian too and I had your same problem.
1) My phone died and 20 days before the end of the warranty and I sent it to the repair center.
As you, I opened the device and also I wasn't stock, so I reflashed google stock image and I re-locked the bootloader. The repair center has fixed my device changing the mobo and they didn't charged me for anything.
2) I don't know if they have a new rev. of the mobo that fixes the bootloop problem, but I'm going to apply the copperhead heatsink mod and maybe I will underclock the cpu with EX kernel.
3) I hope that the copperhead mod works, I saw some benchmarks and it seems that this heatsink will lower the temperature by 5/7 degrees.
I'm sorry for my English
Click to expand...
Click to collapse
We have exactly the same situation, I just ordered the copper plates, let's see if it will work! As of now, even if I got my 5X back from warranty, I'm still using my galaxy nexus because I don't want the 5X to overheat, I will start using it again after the heatsink mod

Question *Urgent Help* Bricked Pixel 6 Pro

I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.

Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.

roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.

Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.

Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!

Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.

2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.

verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.

96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port

Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??

liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try