Help Kernel Crash at boot! No download mode

[digitex3d]

Hello,

My LG G3 D855 crashed and I had to remove the battery to reboot it.

I accidentally removed the usb charger when the battery was already removed, and now, after putting the battery again, the phone takes a lot of time stucked at the LG logo then it goes into kernel crash!

More Details:
-When charger is connected, the phone shows a stuck "loading" battery icon, like when the charge of the phone is too low.
-I dont have acces to recovery mode coz blue screen.
-Only kernel crash section seems to "work".
-I cannot see the device with adb coz usb debugging disabled and cannot log into system

Error message:
-----------------------------------------------------------------------------------------------------------------
DemiGod Crash Handler : Kernel Crash! :

Press key to choose Dload Mode/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 QCT's Memory Debug App

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000b
------------------------------------------------------------------------------------------------------------

ALREADY DONE:
Tryed to flash a .kdz -> the download mode doesn't work correctly, I see a black screen and I see the device as unknown #QHSUSB_BULK#.
Tryed to hard reboot -> kernel crash

compltete original STOCK PHONE - not rooted - TWARP not installed


It seems a power problem, I really don't know how to fix this.

Thanks for your help!

PS.
If cell recovery is not possible , is it at least possible to recovery data?

 

[iowabowtech]

It may be possible to recover from qhusb_bulk mode but you're correct in that it's not a simple fix. Are you still covered by a one year warranty on this phone or no? If so, that would certainly be your easiest way out of this. If not, I will try to help you fix it. That would result in your data being lost, though as you probably know, the kdz would have done the same.

Is your D855 a 16 GB phone?

 

[digitex3d]

I'm sure I will fix it with your precius help. Yes 16 GB

 

[iowabowtech]

I'm sure I will fix it with your precius help. Yes 16 GB

Alright then. Any chance you happen to run Linux on any of your PC's, laptops, etc? If so, what distro? If not, that's ok, I just need to know so I don't waste time typing instructs that are not necessary.

 

[digitex3d]

Alright then. Any chance you happen to run Linux on any of your PC's, laptops, etc? If so, what distro? If not, that's ok, I just need to know so I don't waste time typing instructs that are not necessary.

Yes I've got Ubuntu!

 

[iowabowtech]

Yes I've got Ubuntu!

Perfect. Read through the OP of this thread a few times if you would please:

http://forum.xda-developers.com/showthread.php?t=2582142

You'll note that thread was made for the G2. However, I think the same basic method would work on the G3 as well. However, you would not want to dd write the exact same partitions they did there so we would slightly modify the instructions. You would however do all the steps up to and including getting your partition schedule including the numbers of each partition.

So check that out and let me know if you somewhat see what they were doing there and if you'd like to give it a shot.

 

[iowabowtech]

Didn't mean to scare you away there @digitex3d.

Have you attempted the first portion of that process, up to the point of getting your partition schedule? It'd be nice to know at least if your partitions are visible to the Linux environment in your current iteration of bulk mode. No harm can befall you if you stop at that point. The other way to get a clue if you're in a fixable situation is hooking up the phone to a windows machine. If windows tries to mount a bunch of partitions as drives (that's how windows sees them), then you're likely in a good position to fix.

 

[digitex3d]

I see the device as a:
lsusb output:
Bus 002 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Partitions are not visible to Linux

 

[iowabowtech]

I see the device as a:
lsusb output:
Bus 002 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Partitions are not visible to Linux

Ok well earlier it was showing as qhsusb_bulk per you pasted output, now it's showing as QDloader 9008 mode. I haven't seen anyone recover from 9008 mode without paying for a fix. You can read through THIS thread to see what I'm talking about there. There's a guy that will fix via TeamViewer for $35, he has proprietary software.

It'd be nice if you could plug into a windows machine and verify which mode you are truly dealing with. It does appear to be 9008 at first glance which is bad. You can get out of qhsusb_bulk yourself. You can't get out of QDL 9008 by any means I've seen, other than paying for it.

 

[KOLIO]

I haven't seen anyone recover from 9008 mode without paying for a fix. You can read through THIS thread to see what I'm talking about there. There's a guy that will fix via TeamViewer for $35, he has proprietary software.
You can't get out of QDL 9008 by any means I've seen, other than paying for it.

I'd consider myself fortunate if $35 is all that's standing between a ($600) brick & a usable phone.

 

[iowabowtech]

I'd consider myself fortunate if $35 is all that's standing between a ($600) brick & a usable phone.

Certainly is better than the alternative if outside the 1 year warranty, I agree.

This was a particularly unfortunate situation. A simple charging/battery removal issue should never render your phone in this unusable mode. That is an issue LG should stand behind and take care of in a perfect world.

 

[KOLIO]

I agree.
I've had to go 'round & 'round with a couple of mfgs w/o any resolution & lighter in the pocket to cover shipping on one occasion.

YMMV,but, MOTO seems to put up the least resistance w/warranty claims/etc. & the others are a more or less an equally distant 2nd.

 

[meyerweb]

This was a particularly unfortunate situation. A simple charging/battery removal issue should never render your phone in this unusable mode. That is an issue LG should stand behind and take care of in a perfect world.

Not sure it's totally fair to call this an LG defect. On pretty much any type of computer, if you pull power while system writes are going on, you're going to break something. That's why Windows warns you in big letters not to unplug or power off your PC while system updates are happening. Without knowing exactly what the system was trying to do when the OP pulled power, you can't say this is an LG fault.

 

[iowabowtech]

Not sure it's totally fair to call this an LG defect. On pretty much any type of computer, if you pull power while system writes are going on, you're going to break something. That's why Windows warns you in big letters not to unplug or power off your PC while system updates are happening. Without knowing exactly what the system was trying to do when the OP pulled power, you can't say this is an LG fault.

Why the interest?

He never mentioned anything about an update of any kind. He said the phone crashed so he did a battery pull. A common response to such a failure. He then removed the USB cable.

 

[meyerweb]

Why the interest?

He never mentioned anything about an update of any kind. He said the phone crashed so he did a battery pull. A common response to such a failure. He then removed the USB cable.

While the phone was booting, which may well involve writing to one or more storage partitions.

 

[iowabowtech]

While the phone was booting, which may well involve writing to one or more storage partitions.

My LG G3 D855 crashed and I had to remove the battery to reboot it.

I accidentally removed the usb charger when the battery was already removed, and now, after putting the battery again, the phone takes a lot of time stucked at the LG logo then it goes into kernel crash!

Booting? With the battery already removed?