Database Users

[Q] Boot not completing - likely hardware problem

In brief:
The N4 is stuck on the whirling circles during boot. It is likely due to some broken bit of hardware. I would like to determine where it's stuck. After that I can decide if repair is possible or if I don't need that feature and it can be skipped one way or another or toss the brick altogether.
In full:
While out of town S.O. dropped the phone and the digitizer shattered. She said the screen appeared to still work, but no input was possible. She ordered a new digitizer and dumped it on me to repair, little realizing the difficulty of replacing only the digitizer. Still, I gave it the ol' college try on a slow day at work, heating the glass shards to yield the glue and get them off the screen. After installing new digitizer I was not surprised that I had damaged the screen and just a few colored stripes displayed.
So I ordered and installed a digi/lcd assembly and I now have a functioning screen and digitizer. The problem is the system won't completely boot and is stuck on the infamous whirling circles. I am fairly certain that during boot some device is being queried and is broken, and the boot has no timeout to skip it and move on. I would like to know where it's stuck. I *think* the way to do that is to somehow direct kernel messages out the phone's USB so I can use PuTTY to display them on a workstation. I do not know how to do that. If there's some other way, like getting the messages to display on the phone's screen, I don't know that either. Hence my post.
The techie bits:
Long story short here's a summary of relevant actions I've done so far.
Phone still goes into the mako bootloader and I can use fastboot.
Used TWRP recovery to wipe everything (including itself)
Flashed factory 4.4.2 OS
Reinstalled TWRP recovery and had it root for me
I now have two ways to access the phone - fastboot when in the stock mako bootloader, and adb when I fire up TWRP.
Now what can I do to find where the system boot is hanging? Suggestions welcome.

first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.

RolF2 said:
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
Click to expand...
Click to collapse
I will check that. Thanks for the reply.
Edit: I just checked, and you were right on the money. The tab with the connector for that device had flipped under the mainboard so I didn't connect it. All fixed now and I have a working phone. I owe you a couple beers. Thanks.

Hi, you are lucky
I have a similar problem.
Yesterday i restarted my phone and >problem, stuck at X-boot-logo<
Already tried different roms.
Can get into fastboot-mode and therefore can have ADB with CMW-recovery.
I replaced my screen a few months ago.
Already checked proximity sensor cable.
btw:
at the beginning, one time I got it to "optimizing apps...", but it was stuck at "starting apps"
How can I see if my proximity/light sensor is dead?
can I use the Nexus 4 serial?
Any other solution?
Regards

You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.

RolF2 said:
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
Click to expand...
Click to collapse
OK, I'll try to go back to 4.2.
Anything I can do if I really lost IMEI?
I think you could be right.
I rebooted my phone because i got no network connection. (even after airplanemode on/off)
---------- Post added at 07:05 PM ---------- Previous post was at 06:45 PM ----------
OK, 4.2 booted successfully
Thanks.
but phone does not connect to network.
IMEI seems to be lost (*#06# shows nothing for imei)
What do you think about restoring IMEI with dd-command from "somewhere"?

take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...

RolF2 said:
take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...
Click to expand...
Click to collapse
no baseband too.
imei empty, not zero
I don't think dd mmcblk0p1 would be useful as it is only the radio.img.
You can find it in the stock image
The first step now is backupping the efs-partitions
do you mean directly writing IMEI to it?
I can try to copy the IMEI(or all partitions) from my brother's phone to mine
Thx

don't hurt to try dd modem partition first, maybe it's corrupted in some way ... why it's unknown ?

[Q] Damaged EFS, no backup - how to repair S5 with NULL IMEI?

Hi,
I have a problem with my S5. After flashing a custom ROM I found out that my IMEI is null, and so the EFS is corrupted. I tried to restore it from backup only to find out that I have deleted the backup
What can I do now? I anything? Would restoring EFS from another S5 (with damaged mainboard) could be a solution?
Generally everything works except of phone modem, I have got IMEI written - is there maybe a method to set the IMEI without EFS or a method to create EFS? I already tried sam IMEI changers, but I found out that they only do this on the application level - apps will be able to read different IMEI for licensing, but phone still sees NULL IMEI.

You can't restore EFS from another S5 coz it'll brick your device.

Bruce666 said:
You can't restore EFS from another S5 coz it'll brick your device.
Click to expand...
Click to collapse
Thanks for answer
So what can I do?

Found sth like this:
Never tried coz never lost IMEI
In the dialer, type- *#197328640# or *#*#197328640#*#*
>You will be prompted into the Command mode, provided On the screen, Select on Common, normally option 6
> Now Select (FTM) Option 1
>FTM is for debugging and testing., (Field Test Mode)
>If (FTM) is on, you will have to turn this OFF
>As soon as you turned this off your NULL or altered IMEI number will be restored
>(Important) Without leaving the Command screen, press the Menu key, the button that’s found left of the Home button.
> Select Key input and enter option 2. In this case, you want to turn it off
>Wait for a minute. This will turn your FTM OFF
> Remove your battery and SIM card for two minutes
>Place your battery in your phone, (important) do not place your SIM card in.
> When the phone is booted, enter the command mode again dial – *#197328640#
>Select the Debug Screen, normally option 1
>After that, choice phone control, option eight
>Click on nas control, option 3
>Afterwards, click “RRC (HSDPA), option 5
>To Fix not registered on network or Null IMEI #, click RRC revision, option 2.
>Choose the released of your phone, here we will choose option 5 (HSDPA only)
>Final step to fix Null IMEI not registered on a network for Samsung Galaxy is to turn off your phone and insert your Sim card
or
>Insert your Sim card, afterwards reboot your phone

Thanks - are you sure about this bricking device?
I already tried this numbers but it always says "No Network", The only instruction that I found was to use *#0011# and it goes into the Service Menu, but it doesn't look like that described. There is something called NVM restore, but it doesn't do anything with IMEI
I am gonnna post screenshots at evening.
Bruce666 said:
Found sth like this:
Never tried coz never lost IMEI
In the dialer, type- *#197328640# or *#*#197328640#*#*
>You will be prompted into the Command mode, provided On the screen, Select on Common, normally option 6
> Now Select (FTM) Option 1
>FTM is for debugging and testing., (Field Test Mode)
>If (FTM) is on, you will have to turn this OFF
>As soon as you turned this off your NULL or altered IMEI number will be restored
>(Important) Without leaving the Command screen, press the Menu key, the button that’s found left of the Home button.
> Select Key input and enter option 2. In this case, you want to turn it off
>Wait for a minute. This will turn your FTM OFF
> Remove your battery and SIM card for two minutes
>Place your battery in your phone, (important) do not place your SIM card in.
> When the phone is booted, enter the command mode again dial – *#197328640#
>Select the Debug Screen, normally option 1
>After that, choice phone control, option eight
>Click on nas control, option 3
>Afterwards, click “RRC (HSDPA), option 5
>To Fix not registered on network or Null IMEI #, click RRC revision, option 2.
>Choose the released of your phone, here we will choose option 5 (HSDPA only)
>Final step to fix Null IMEI not registered on a network for Samsung Galaxy is to turn off your phone and insert your Sim card
or
>Insert your Sim card, afterwards reboot your phone
Click to expand...
Click to collapse

evilsnailofdestruction said:
Thanks - are you sure about this bricking device?
I already tried this numbers but it always says "No Network", The only instruction that I found was to use *#0011# and it goes into the Service Menu, but it doesn't look like that described. There is something called NVM restore, but it doesn't do anything with IMEI
I am gonnna post screenshots at evening.
Click to expand...
Click to collapse
Yes I'm sure about bricking. EFS partition on your phone is made for ONLY YOUR PHONE. This is sth like restoring TA Partition on xperia devices. When you flash ta from another xperia, you brick device
Tapatalked from SM-G900F

I read someone saying they had successfully restored a backed up EFS partition from an identical model S5 to another, and it worked
The problem I can see, is if the original gets blocked by the carrier, chances are so will the clone
Not sure about network issues having two identical devices on the same network at the same time, both making calls, might end up like an IP conflict

Pretty sure that transferring IMEI from one device to another is against the law too......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

Yes, I also know that is it against the law, but I have a complete phone with broker mainboard (so even the IMEI is written on the back), and I would like to use this opportunity to copy the IMEI from old (broken) mainboard to the new one. It even looks better than the situation when I have got and old case with written IMEI that doesn't correspond to the IMEI on the new mainboard.
The mainboard is broken that way, that there is short-circuit somewhere and the CPU is constantly using power and it get's really hot, so it use useless.
I am trying to flash EFS, let's see what is gonna to happen
keithross39 said:
Pretty sure that transferring IMEI from one device to another is against the law too......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse

1. Tried flashing EFS = nothing happened
2. Tried flashing EFS + Modem + ModemST1 + ModemST2 = nothing happened
3. Restored android to STOCK
I can't get into the service menu.
The only Service menu that I can get into is this one, but there isn't any fixing IMEI/NVRAM option
Code:
*#0011#
Menu > Back
Menu > keyInput "Q"
Menu > keyInput "0000"
Wait for few seconds
evilsnailofdestruction said:
Yes, I also know that is it against the law, but I have a complete phone with broker mainboard (so even the IMEI is written on the back), and I would like to use this opportunity to copy the IMEI from old (broken) mainboard to the new one. It even looks better than the situation when I have got and old case with written IMEI that doesn't correspond to the IMEI on the new mainboard.
The mainboard is broken that way, that there is short-circuit somewhere and the CPU is constantly using power and it get's really hot, so it use useless.
I am trying to flash EFS, let's see what is gonna to happen
Click to expand...
Click to collapse

Hi,
you have 2 options
1. Use Samsung Kies which will repair you efs
2. Flash with Odin the official rom 5.0
If you install another efs, the data installed may be not work, even if it is same model. In S5, nothing to do with the IMEI
You can also root the phone and with adb commands, erase all the efs
you can also use Z3X tools

Hi,
Thanks - some new ideas
So if I understand you correctly, I have 3 options:
1. Use Samsung Kies which will repair you efs - how to repair EFS with Samsung Kies?
2. Flash with Odin the official rom 5.0 -> I tried flashing oryginal 4.4 and it didn't helped. Should flashing 5.0 help?
3. You can also root the phone and with adb commands, erase all the efs - What will erasing EFS will give me? Shouldn't I have EFS partition with some data?
you can also use Z3X tools -> ok... I am gonna figure this out, 'cause I don't know it yet
FrenchSnake said:
Hi,
you have 2 options
1. Use Samsung Kies which will repair you efs
2. Flash with Odin the official rom 5.0
If you install another efs, the data installed may be not work, even if it is same model. In S5, nothing to do with the IMEI
You can also root the phone and with adb commands, erase all the efs
you can also use Z3X tools
Click to expand...
Click to collapse

I have the same issue. Anybody may help me ? (galaxy S5 SM-G900H made in Vietinam)
thanks in advance

Bruce666 said:
Found sth like this:
In the dialer, type- *#197328640# or *#*#197328640#*#*
>Insert your Sim card, afterwards reboot your phone
Click to expand...
Click to collapse
This does nothing on Galaxy A5!
attached 0011 code screen

Has anybody found the solution? Efs professional gives me error " device connection lost" while using Qualcomm nv tools on s5.

D800 - Unusual semi-brick (9008/9006/TOT doesn't resolve)

I have a D800 I'm working on for someone. They did a real number on it. It was semi-functional, but would randomly lose all screen function and had no service. Also had a persistent "ERROR" right above the home keys.
I performed a TOT reset to 20c, and everything seemed fine. I verified functionality and downloaded some apps using my google account, so once everything was fine I performed a standard Factory Reset via Volume - + Home/Home. Now, all hell has broken loose. It retained download mode - for a while - and I was able to flash all 3 available TOT's with semi-success. OS was bootable, sometimes, other times it was pure bootloop. Factory resets performed before and after TOT flashes. Confirmed MD5's, correct TOT+DLL combinations, etc etc. The phone is just pissed. Currently, the IMEI is now gone, but I know it. I wrote it down prior to doing anything the moment I got it. It also matches the IMEI on the inside of the back cover. I have confirmed this is not a frankenstien refurb - D800 on rear of mainboard / all panels / battery ribbon cables / etc. I lost download mode at one point, had fastboot. Couldn't get fastboot mode to work with my pc to repair it, so I manually put the phone into QHUSB 9008 mode, then 9006, then repaired fastboot so Download mode would work. Back to step one....Bootloops, hard freezes, random reboots, "ERROR" during RANDOM boots sometimes no ERROR, etc etc.... Something somewhere is just not meshing. I thought MAYBE the lack of an IMEI might be throwing the OS for a loop, so I tried the qualcomm and EFS Professional programs with no luck. The phone throws an error when trying to backup the memory, as well as write the HEX IMEI. I've tried various ports. Drivers are all current, and I've tried every available version of drivers I've been able to locate.
Anyone have any ideas? At all....? I'm familiar with most of the processes involved here, I just can't figure out how a full TOT reflash isn't wiping the issue...

Sorry, meant to put in Troubleshooting. Apologies!

adamlee06 said:
I have a D800 I'm working on for someone. They did a real number on it. It was semi-functional, but would randomly lose all screen function and had no service. Also had a persistent "ERROR" right above the home keys.
I performed a TOT reset to 20c, and everything seemed fine. I verified functionality and downloaded some apps using my google account, so once everything was fine I performed a standard Factory Reset via Volume - + Home/Home. Now, all hell has broken loose. It retained download mode - for a while - and I was able to flash all 3 available TOT's with semi-success. OS was bootable, sometimes, other times it was pure bootloop. Factory resets performed before and after TOT flashes. Confirmed MD5's, correct TOT+DLL combinations, etc etc. The phone is just pissed. Currently, the IMEI is now gone, but I know it. I wrote it down prior to doing anything the moment I got it. It also matches the IMEI on the inside of the back cover. I have confirmed this is not a frankenstien refurb - D800 on rear of mainboard / all panels / battery ribbon cables / etc. I lost download mode at one point, had fastboot. Couldn't get fastboot mode to work with my pc to repair it, so I manually put the phone into QHUSB 9008 mode, then 9006, then repaired fastboot so Download mode would work. Back to step one....Bootloops, hard freezes, random reboots, "ERROR" during RANDOM boots sometimes no ERROR, etc etc.... Something somewhere is just not meshing. I thought MAYBE the lack of an IMEI might be throwing the OS for a loop, so I tried the qualcomm and EFS Professional programs with no luck. The phone throws an error when trying to backup the memory, as well as write the HEX IMEI. I've tried various ports. Drivers are all current, and I've tried every available version of drivers I've been able to locate.
Anyone have any ideas? At all....? I'm familiar with most of the processes involved here, I just can't figure out how a full TOT reflash isn't wiping the issue...
Click to expand...
Click to collapse
baseband is known or unknown.

kalpesh patil said:
baseband is known or unknown.
Click to expand...
Click to collapse
Unknown. I just PMd you as well, but my XDA PMs havent been sending all week. Maybe you're went through

D800 - Unusual semi-brick (9008/9006/TOT doesn't resolve)

I have a D800 I'm working on for someone. They did a real number on it. It was semi-functional, but would randomly lose all screen function and had no service. Also had a persistent "ERROR" right above the home keys.
I performed a TOT reset to 20c, and everything seemed fine. I verified functionality and downloaded some apps using my google account, so once everything was fine I performed a standard Factory Reset via Volume - + Home/Home. Now, all hell has broken loose. It retained download mode - for a while - and I was able to flash all 3 available TOT's with semi-success. OS was bootable, sometimes, other times it was pure bootloop. Factory resets performed before and after TOT flashes. Confirmed MD5's, correct TOT+DLL combinations, etc etc. The phone is just pissed. Currently, the IMEI is now gone, but I know it. I wrote it down prior to doing anything the moment I got it. It also matches the IMEI on the inside of the back cover. I have confirmed this is not a frankenstien refurb - D800 on rear of mainboard / all panels / battery ribbon cables / etc. I lost download mode at one point, had fastboot. Couldn't get fastboot mode to work with my pc to repair it, so I manually put the phone into QHUSB 9008 mode, then 9006, then repaired fastboot so Download mode would work. Back to step one....Bootloops, hard freezes, random reboots, "ERROR" during RANDOM boots sometimes no ERROR, etc etc.... Something somewhere is just not meshing. I thought MAYBE the lack of an IMEI might be throwing the OS for a loop, so I tried the qualcomm and EFS Professional programs with no luck. The phone throws an error when trying to backup the memory, as well as write the HEX IMEI. I've tried various ports. Drivers are all current, and I've tried every available version of drivers I've been able to locate.
Anyone have any ideas? At all....? I'm familiar with most of the processes involved here, I just can't figure out how a full TOT reflash isn't wiping the issue...
Imgur Album of components to confirm full D800: http://imgur.com/a/PciLM
EDIT: BASEBAND UNKNOWN

[Q] Any advice for bricked G2 [D802] make unbrick ?

Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.

metobayrak said:
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
Click to expand...
Click to collapse
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)

brainvision said:
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
Click to expand...
Click to collapse
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.

metobayrak said:
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
Click to expand...
Click to collapse
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before

brainvision said:
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
Click to expand...
Click to collapse
I used this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i opened my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.

metobayrak said:
I use this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i open my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
Click to expand...
Click to collapse
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while

brainvision said:
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
Click to expand...
Click to collapse
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.

metobayrak said:
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
Click to expand...
Click to collapse
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?

brainvision said:
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
Click to expand...
Click to collapse
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU

metobayrak said:
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
Click to expand...
Click to collapse
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?

brainvision said:
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
Click to expand...
Click to collapse
Yes, because of the eMMC chip is damaged. But the crux of the problem is processor heats and cause of no proper heat dissipation this damages other chipsets. Thermal pad solution must be done after chip replacement.