So ive finally got a working version of BoardDiag tool going, after shorting the capacitors to get it from unknown usb device to Qualcomm 9008(com41) i being the tests. AP check and EMMC test both pass than i get this error:
Code:
Device Reset!!
Waiting for DDR test....
Waiting for the device to connect in flash prg
connected to flash programmer
DDR TEST = NUK
sbl1 partition write done...
======== END
and TEST RESULT for SDRAM is FAIL
any thoughts, help or insight is appreciated.
Anyone? Same problem here
me myself and i said:
So ive finally got a working version of BoardDiag tool going, after shorting the capacitors to get it from unknown usb device to Qualcomm 9008(com41) i being the tests. AP check and EMMC test both pass than i get this error:
Code:
Device Reset!!
Waiting for DDR test....
Waiting for the device to connect in flash prg
connected to flash programmer
DDR TEST = NUK
sbl1 partition write done...
======== END
and TEST RESULT for SDRAM is FAIL
any thoughts, help or insight is appreciated.
Click to expand...
Click to collapse
Sorry for the necroposting, but i'm still trying to fix an hard bricked g3 (not g2). The phone seems to be recognized perfectly from windows 10 64 bit pc (Qualcomm HS-USB QDLoader 9008 (COM6) ) but when I try to flash mbn partitions (after 4 or 5 successful flash) phone disconnect or boarddiag say that phone isn't in DLOAD mode and I can't continue.
I think that I did everything in the right way: disable windows driver signature, shortcut right pin on motherboard, installed qualcomm drivers, remove battery, tried various tot file and kdz (for files from kdz I build partition.txt file by myself following this guide http://www.ez-pg.com/how-to-create-partition-txt-file-from-kdz.html) and tried on another windows 10 64bit pc.
With boarddiag I did the sdram test and the result is DDR TEST = NUK, test failed. Someone managed to solve?
Shadow 00 said:
Sorry for the necroposting, but i'm still trying to fix an hard bricked g3 (not g2). The phone seems to be recognized perfectly from windows 10 64 bit pc (Qualcomm HS-USB QDLoader 9008 (COM6) ) but when I try to flash mbn partitions (after 4 or 5 successful flash) phone disconnect or boarddiag say that phone isn't in DLOAD mode and I can't continue.
I think that I did everything in the right way: disable windows driver signature, shortcut right pin on motherboard, installed qualcomm drivers, remove battery, tried various tot file and kdz (for files from kdz I build partition.txt file by myself following this guide http://www.ez-pg.com/how-to-create-partition-txt-file-from-kdz.html) and tried on another windows 10 64bit pc.
With boarddiag I did the sdram test and the result is DDR TEST = NUK, test failed. Someone managed to solve?
Click to expand...
Click to collapse
Same problem here. Did you manage to solve it?
I open a Thread explaining: http://forum.xda-developers.com/lg-g3/general/restoring-boot-sequence-boarddiag-v2-99a-t3374096
Nash L. said:
Same problem here. Did you manage to solve it?
I open a Thread explaining: http://forum.xda-developers.com/lg-g3/general/restoring-boot-sequence-boarddiag-v2-99a-t3374096
Click to expand...
Click to collapse
It was an hardware, emmc related, problem. Seems that flash process was successfull, even if I had to disconnect and reconnect the phone everytime it gave me that problem.
The real problem was the emmc overheating, so (after the flashing process) I put the phone in the coldest place of my house... the freezer. I turned it on, then (really fast) I put the emmc in direct contact with an ice pack; the phone has been on long enough to allow me to backup all the files. Then it died again.
Shadow 00 said:
It was an hardware, emmc related, problem. Seems that flash process was successfull, even if I had to disconnect and reconnect the phone everytime it gave me that problem.
The real problem was the emmc overheating, so (after the flashing process) I put the phone in the coldest place of my house... the freezer. I turned it on, then (really fast) I put the emmc in direct contact with an ice pack; the phone has been on long enough to allow me to backup all the files. Then it died again.
Click to expand...
Click to collapse
Well, that sound like a unique solution. Where you able to sense the heat from the emmc with your hand/fingers? I don't believe my phone has the same problem, mine is dead cold all the time.
Nash L. said:
Well, that sound like a unique solution. Where you able to sense the heat from the emmc with your hand/fingers? I don't believe my phone has the same problem, mine is dead cold all the time.
Click to expand...
Click to collapse
Not during the flashing process. Disassemble the phone, turn it on and try to touch the emmc.
For the flashing process: just try to flash mentioned partition one by one; if bord diag says the phone isn't in dload mode anymore, try disconnect and reconnect the phone and continue from where it stopped
Related
Yesterday I flashed (CSE flash) v30a KDZ to recover my GPS which as having problems getting locks and it all went well, it seemed the GPS got back working.
Later I used the DP Root to root it and it went ok.
After using the DP REC (if required for evaluation, please inform), my phone rebooted and it showed me the following message:
ERROR : boot certification verify
[1040] ------------------------------------------
[1090]
[1140] Secure booting Error!
[1200] Cause : boot certification verify
[1250]
[1300] ------------------------------------------
Click to expand...
Click to collapse
Then goes to this:
------------------------------------------
Critical Error!
------------------------------------------
Demigod Crash Handler : Critical Error!
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration.
------------------------------------------
Board Info
rev. : 1.1 speed,pvs : 1,2 serial : XXXXXXXXXX
------------------------------------------
Click to expand...
Click to collapse
Pressing the power button for more than 13s I can shut it down so that I can try the Volume Up + connect USB, but then it just powers the phone on and starts the above stated.
By pressing the Volume down + Power and pressing again after the LG Logo shows up, I can go to the reset screen but at the finish it doesn't show the factory reset or TWRP, just starts the sequence of screens above.
By pressing the Volume Up on the Demigod Crash screen, it show the following message:
Volume Up is pressed : Jump to Dload Mode.
Click to expand...
Click to collapse
and stays that way, but then the computer recognizes the "LGE AndroidNet USB Modem" and "LGE AndroidNet Serial Port", no more LG stuff there, and the LG Flash Tool doesn't go past 4%.
On Ubuntu it recognizes the same devices, but doesn't get the partitions
Does anyone know any way so that I can get out of this?
Hi @darknessmessiah,
Any luck with your issue? I've received a strikingly similar result after attempting to flash the stock lollipop to my LG G2 801 from the T-mobile forum.
jjmontem said:
Hi @darknessmessiah,
Any luck with your issue? I've received a strikingly similar result after attempting to flash the stock lollipop to my LG G2 801 from the T-mobile forum.
Click to expand...
Click to collapse
Hi there! Yes, I got to get it back... But it was this hard
Anyway there goes some tips:
After you remove the battery plug, you only need to put it back after everything is done.
You have to keep trying the short circuit until you get a new hardware called "Qualcomm hs-diagnostics 9006" and you computer recognizes a lot of disk partitions. The normal device my computer recognized was "Qualcomm HS-USB QDLoader 9008" and no tip out there worked.
When the computer recognizes the wrong device, remove the USB, plug it back and try again. One time it recognized one whole 32GB partition, but thankfully I didn't try anything besides removing the USB and try again.
After everything, I got Download Mode back and, after some tries (I've got some errors), got the flashtool to flash the ROM back.
jjmontem said:
Hi @darknessmessiah,
Any luck with your issue? I've received a strikingly similar result after attempting to flash the stock lollipop to my LG G2 801 from the T-mobile forum.
Click to expand...
Click to collapse
infect you need to fix the download mod
i can fix plz contact me https://www.facebook.com/faheem.anjum2
Wow, that's miserably complicated. And to show you my naivite, I wasn't aware that one could enter download mode by plugging in the phone to a computer with a USB cord, and holding the volume up button as it started up. My phone successfully entered download mode and I was able to use LG Flash Tool 2014 to return my phone to Stock 4.2.2 using this thread and a KDZ I had long ago stored.
Thanks for the help though!
darknessmessiah said:
Hi there! Yes, I got to get it back... But it was this hard
Anyway there goes some tips:
After you remove the battery plug, you only need to put it back after everything is done.
You have to keep trying the short circuit until you get a new hardware called "Qualcomm hs-diagnostics 9006" and you computer recognizes a lot of disk partitions. The normal device my computer recognized was "Qualcomm HS-USB QDLoader 9008" and no tip out there worked.
When the computer recognizes the wrong device, remove the USB, plug it back and try again. One time it recognized one whole 32GB partition, but thankfully I didn't try anything besides removing the USB and try again.
After everything, I got Download Mode back and, after some tries (I've got some errors), got the flashtool to flash the ROM back.
Click to expand...
Click to collapse
jjmontem said:
Wow, that's miserably complicated. And to show you my naivite, I wasn't aware that one could enter download mode by plugging in the phone to a computer with a USB cord, and holding the volume up button as it started up. My phone successfully entered download mode and I was able to use LG Flash Tool 2014 to return my phone to Stock 4.2.2 using this thread and a KDZ I had long ago stored.
Thanks for the help though!
Click to expand...
Click to collapse
Well... You were in a better situation than myself... holding the volume up and plugging the USB didn't work for me either... It was heavily messed up!
hi do you find solution
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
i have same probleme with my lg g F320L can anyone help ?
Guide fix "device not found in dload trying flash programmer" when use boardiag .
Lg g3 qualcomm 9008 when install driver then use tool boardiag fake tool say device not found in dload trying flash programmer
when you use tool fake board share in xda another tool say device not found in dload trying flash programmer you need remove battery (of lg g2 hold power 1 minute) then connect cable again and use tool again
Sure install driver 100% wrong
With windowns 64 bit you need restart pc then click f8 choose disbable driver singturne....
Then remove battery (hold power 1 minute with lg g2) then connect cable try use tool unbrick >> sure done 100%
I will updload video error dload
Remember disbbale tool sony erricson if you have open tool in taskbar
then read topic use tool of my unbrick
http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
i have same problem when i hit start button show that error ( b2bsuppportlg device was not found in dload trying flash programmer )
i tried on 4 different pcs (win7 .. win xp service pack 3 .. ) but same result any one have solution ???
driver signature check disabled?
drivers correctly installed? (lg AND qcom)
edit unfortunately, the tootls provided here on xda are mostly broken or missing important files...
this seems to be due people not wanting other people (support-shops) beeing fired
weird weird stuff tho
everything fine but still same error u have working link ??
hey there guys, somebody has resolve this problem? im suffering the same problem in a nexus 5
im also facing the same prob
all are dumb
No one want helping others they only want donations from us so guys carry on if u dont want to help us then no worry
Hi All! I've found a solution!
The trick is to use a Heat Gun for heating up both ICs on both sides of motherboard.
I've had the same problem:
"device not found in dload trying flash programmer" when use boarddiag​I also tried SRKtool, but in last step, I couldn't find the partition.
So both SRKtool and BoardDiag failed.
All hope was lost. So I did warm the CPU and Storage IC on both sides with Heat gun!
about a minute or so for both ICs until both were very hot.
That did the magic.
After that both SRKtool and BoardDiag worked for me perfectly and I was able to revive my phone.
I think in all our cases this problem is because storage IC and CPU IC have been out of work for a long time and they need to get warm to work after all this time of being turned off.
Really hope this works for you all.
my phone LG G2 D802 International Version was running perfectly fine i tried to flash another rom by LG FlashTOOL and in the first i got soft bricked on that fastboot screen i recoverd it by ADB (fastboot.exe)
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
and then i tried to reflash it then i got this mesg on screen
---------------------------------------------------------------------------
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
-------------------------------------------------------------------------
Board Info
Rev. : 1.1 speed.pvs : 1.1 Serial : 01e862cf934fc622
Please Help me somebody ... i cant afford to buy new phone i just bought this phone a week ago ..
Having same issue ! XDA forum experts always helped me with every situation with my phones. Expecting help this time as well from you experts.
Same here, enyone can help, i stuck with the sam message, presing vol- just rebots, and vol+ sends message "jump to download mode" but i cant flash stock firmware
i have the same problem any help ??
I have the same issue too, can anyone help?
I heard that this can help you guys. Use the search option there and try to fix it. Actually i had the same problem few months ago, but for me mew motherboard was the solution... If you're device is under warranty send it saying it failed while taking OTA. Good luck...
lg g2 critical error
I have done a flash to my g2 32gb d802 and it suddenly entered into critical error not going into any of thefastboot mode or download mode even though it is giving me options.....please any one help me out to get my phone back to normal ........
PM me if you guys need help.
I had the exactly same problem, and I had to go to afterservice center to repair. Engineer told he would wipe everything and install new rom. but He failed to write rom so he simply changed mainboard.
At first I had thought about open my g2 and makes it go into qualcomm download mode by short-circuit.
the reason I didn't was my warranty was still available.
I tried every method to make it boot into recovery or download mode but I failed. In my opinion, you may try short-circuit method for last solution. In this situation, even linux doesn't mount rom's storage section. Only if you can make G2 recognized in Linux, G2 will revive.
good luck.
xmayhemreturnsx said:
PM me if you guys need help.
Click to expand...
Click to collapse
i still don't know what to do HELP
yassou92 said:
i still don't know what to do HELP
Click to expand...
Click to collapse
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. However, when you get the demigod error plug in you usb and click up and it should start download mode even though it doesn't show it.
xmayhemreturnsx said:
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. .
Click to expand...
Click to collapse
How do you short the pins? There's a guide here on xda but it's so difficult to undestand. I need to know how can I short the pins.
it should start download mode even though it doesn't show it.
Click to expand...
Click to collapse
No, it doesn't. I try to use flashtool but it doesn't recognize the phone. No download mode in any method I tried
I got into this error after I had previously recovered into qhs_usb9006_bulk mode from a hard bricked D801, by shorting the capacitors on the main board. After entering qhs_usb9006, I used srk tools 2.1 for my phone, and after they finished, I tried entering download mode, only to get into this error. I really don't know what it is to say about this. Everything turned wrong with this phone, it went from simply failing a .kdz, to stock .tot, to hard brick, and now to this error, whereas it should've just enter the download mode, as for the 99,99% of the others. Any help would be really appreciated. Thanks.
L.E. I shorted the capacitors again (the one i the middle, like I did the first time, when i got into 9006 mode. 5000 and 5004 didn't work for some reason). This time I got into dload mode, which is 9008. I'll try to recover the phone from here, with this method:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
i had this problem while trying to return to stock. Fixed it by following this guide http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 . it needs some hardware tampering though. i tried and tried but i cant flash the phone any other way. the way i understand this is due to bootloader being corrupt.
I installed autorec from playstore solved all the problems
Than you! autorec worked for me too
Can someone post a KK baseband for D801 (T-Mobile)? I'm on D80120a software version with unknown IMEI and baseband (the phone is a D801 refurbished into D802, I more than hardbricked it by flashing wrong .kdz, got it recovered through shorting pins, 9008 mode, got download mode, D80120a stock, root, twrp, after a very long and painful process of about 1 month). Now I have to make use of QPST, but I have to obtain a valid baseband first. Of all links I've stumbled upon, only 5% or less of them are still working, so I only have one flashable modem, in twrp recovery, which corresponds to D801 jb version.
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems
cloudyfa kk_baseband_D801 only make my phone restarts like crazy.
I'm simply stuck and pray for some devine help.
Thank you.
Weird enough, I flashed a canadian modem and I got both baseband and IMEI. Why did I do that in the first place? Because I remembered that before all these things happened to my phone, the baseband was M8974A-AAAANAZM-1.0.190082, which corresponds to D803. So I said to myself what can happen by flashing the wrong modem? Boot loop, easily fixable with the phone in it's current state. But again, after 1 month of trouble with the phone, I'm back to what exactly started it in the first place: phone seem to work OK but it has 2 huge problems: WiFi extremely weak (2 meters away and a wall or 5 meters away and no wall a and I lose the signal in both cases; the 2nd is wit the GPS - 20-30 meters error). No idea how should I adapt the radio to Europe region (by keeping the canadian one and change the settings, if it's even possible/fixable this way or if this even does make any sense).
I had to do a hard brick fix to get it into the QSUSB mode to flash TOT.
Have you tried using LG Support tool to put it back to stock?
Sent from my LG-F350K using XDA Free mobile app
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
sree27 said:
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
Click to expand...
Click to collapse
Can you go to recovery mode ?? If yes please flash your device compatibility custom rom like RR rom ..if u cant go to even recovery mode..
RIP asus zenfone max Just Change your Motherboard of your phone
Thanks
Its dead u can recover i also had same issue ...mine works now ....email me [email protected]
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
MJMarra34 said:
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
Click to expand...
Click to collapse
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
sree27 said:
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
Click to expand...
Click to collapse
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
MJMarra34 said:
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
Click to expand...
Click to collapse
It's on my profile. I haven't mentioned the disassembly part since it was not required in general cases. Check my profile for the detailed instructions
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
MJMarra34 said:
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
Click to expand...
Click to collapse
Are you on fastboot mode? What is on your display?
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
MJMarra34 said:
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
Click to expand...
Click to collapse
If you're having trouble with QFIL, best thing to do is uninstall Qualcomm drivers, reboot, reinstall, try again. Repeat until you can flash without problem.
I had to uninstall many times. Don't lose hope. It takes a lot of effort
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
MJMarra34 said:
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
Click to expand...
Click to collapse
I don't know. I used the latest one. Try the version linked in my original post. Also, of you're getting sahara fail, it's ok. You're on right track. Uninstall driver, reboot and reinstall. It'll take hell a lot of tries, but will work eventually
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.