[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2

[Partager.info]

First of all i must thank @Shelnutt2 from lg-g2 irc channel who helped me to unbrick my phone and get it back alive. The whole process described bellow came from him.


Description of the problem:

Your LG G2 D802 is living this situation:
1- Rooted and got OTA
2- No Download mode
3- No recovery mode
4- Secure booting error
5- LG detected as qhsusb_bulk in device manager
6- When you boot your device it shows only LG logo with secure booting error, then the screen goes black while your phone is still on.
7- Other symptoms

The only solution for you is the following.

I'll explain the solution for an LG G2 D802 10a, then you can apply it for your device model by downloading the appropriate files.
You will need to use linux.
Ubuntu is good enough to make the job. You can use a virtual machine, live cd or a bootable usb stick.

So lets start.

Files to download from here
VERY IMPORTANT!!!!!!!
You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone. The link above is for 10b_EUR_16G firmware version. So don't use those files if your firmware version was not that one. Instead you should look for img files corresponding to the current version installed in your phone. If you don't know what version you've installed then don't use this method because you will break your phone.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802

Thanks to @sabooakhte who has shared his experience:

IMPORTANT: NEVER FLASH ORIGINAL RECOVERY.IMG TO THE RECOVERY PARTITION!!!

Now just boot into ubuntu and plug your LG G2 to the computer.

Put the downloaded files in the desktop or wherever you want. You just need to know the path to your files.
unplug any other usb device except your mouse, keyboard and lg g2.
Open terminal in ubuntu then type:

ls /dev/sd*

It should return something like this:

/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36

In this case your device is detected under sdb. you may have it under sdc. just look for the biggest number, in this case /dev/sdb36 so it is sdb.

Linux keeps poping up error message "unable to mount..."? follow this solution by @priority3

You can stop the "unable to mount..." error messages from popping up by disabling
the automount feature of Ubuntu.
"To enable or disable automount open a terminal and type dconf-editor followed by the [Enter] key.
Browse to org.gnome.desktop.media-handling."

now, according to the result of the first command type the following:

gdisk -l /dev/sdb

you will get result:

Number  Start (sector)    End (sector)  Size       Code  Name
   1           32768          163839   64.0 MiB    0700  modem
   [COLOR="Red"]2          163840          165887   1024.0 KiB  FFFF  sbl1[/COLOR]
   3          165888          166911   512.0 KiB   FFFF  dbi
   4          196608          197631   512.0 KiB   FFFF  DDR
   [COLOR="red"]5          229376          231423   1024.0 KiB  FFFF  aboot[/COLOR]
  [COLOR="red"] 6          231424          233471   1024.0 KiB  FFFF  rpm[/COLOR]
   7          262144          294911   16.0 MiB    FFFF  boot
  [COLOR="red"] 8          294912          296959   1024.0 KiB  FFFF  tz[/COLOR]
   9          296960          296961   1024 bytes  0700  pad
  10          327680          333823   3.0 MiB     FFFF  modemst1
  11          333824          339967   3.0 MiB     FFFF  modemst2
  12          339968          339969   1024 bytes  FFFF  pad1
  13          360448          393215   16.0 MiB    FFFF  misc
  14          393216          458751   32.0 MiB    0700  persist
  [COLOR="red"]15          458752          491519   16.0 MiB    FFFF  recovery[/COLOR]
  16          491520          497663   3.0 MiB     FFFF  fsg
  17          524288          525311   512.0 KiB   FFFF  fsc
  18          525312          526335   512.0 KiB   FFFF  ssd
  19          526336          526337   1024 bytes  FFFF  pad2
  20          526338          527361   512.0 KiB   FFFF  encrypt
  21          557056          573439   8.0 MiB     0700  drm
  22          573440          589823   8.0 MiB     0700  sns
  23          589824          655359   32.0 MiB    FFFF  laf
  24          655360          720895   32.0 MiB    FFFF  fota
  25          720896          786431   32.0 MiB    0700  mpt
  26          786432          787455   512.0 KiB   FFFF  dbibak
  27          787456          789503   1024.0 KiB  FFFF  rpmbak
  28          789504          791551   1024.0 KiB  FFFF  tzbak
  29          791552          791567   8.0 KiB     FFFF  rct
  30          819200         6488063   2.7 GiB     0700  system
  31         6488064         7733247   608.0 MiB   0700  cache
  32         7733248         7897087   80.0 MiB    0700  tombstones
  33         7897088         7929855   16.0 MiB    0700  spare
  34         7929856         8028159   48.0 MiB    0700  cust
  35         8028160        30703615   10.8 GiB    0700  userdata
  36        30703616        30777310   36.0 MiB    0700  grow

We will be interested by lines marked by red color here. those lines show us the partitions numbers of each file we have downloaded at the begining.
I'm talking about
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802

in our case the sbl1.img is located under sdb2
aboot.img under sdb5
rpm.img under sdb6
tz.img under sdb8
recovery under sdb15

now be careful and try to make it the right way.
we will use dd commands to push img files inside the right partitions.
So lets start:

if youare not logged on as root in ubuntu just open terminal and type

sudo -i

then type your password

now you must be under root access.

then type the following dd command:

dd if=[COLOR="Red"]/home/med/Desktop/[/COLOR]sbl1.img of=/dev/sdb2

i put files in the desktop, so the path to the img files for me is /home/med/Desktop/. just replace this path by the appropriate path to your files. one done you will get some information about the file size you pushed and maybe time of the operation.

keep doing the samething for the other files:

dd if=/home/med/Desktop/aboot.img of=/dev/sdb5

dd if=/home/med/Desktop/rpm.img of=/dev/sdb6

dd if=/home/med/Desktop/tz.img of=/dev/sdb8

dd if=/home/med/Desktop/openrecovery-twrp-2.6.3.2-g2d802 of=/dev/sdb15

Once you finish just reboot your phone, if you did things as described you must boot into twrp recovery.

now just use twrp to flash your ROM and follow this tutorial to reboot into your ROM
http://forum.xda-developers.com/showthread.php?t=2451696

Good Luck.
If you have fixed your your phone you can consider to pay me a coffee cup
paypal: [email protected]

 

[geodano]

Thank you, My D800 is working after two weeks

Sent from my LG-D800 using Tapatalk

 

[Partager.info]

Thank you, My D800 is working after two weeks

Sent from my LG-D800 using Tapatalk

Glade to know that.:good:

 

[swagner53]

This process is the same on Verizon LG G2 (VS980). Thanks to Shelnutt2 and Automprime for helping me do the same and great job posting a clear set of instructions Partage!

 

[Partager.info]

This process is the same on Verizon LG G2 (VS980). Thanks to Shelnutt2 and Automprime for helping me do the same and great job posting a clear set of instructions Partage!

nice to see you here swr. :laugh:

 

[toopty]

This process is the same on Verizon LG G2 (VS980). Thanks to Shelnutt2 and Automprime for helping me do the same and great job posting a clear set of instructions Partage!

I'm trying to do this on my Verizon LG G2. When I plug the device into Ubuntu runing in live mode. I geta bunch errors poping up that it's not able to connect the partitions. Is there a way to stop this so i can continue with the process?

 

[Partager.info]

I'm trying to do this on my Verizon LG G2. When I plug the device into Ubuntu runing in live mode. I geta bunch errors poping up that it's not able to connect the partitions. Is there a way to stop this so i can continue with the process?

is it detected as Qualcomm HSUSB_BULK or something else?

 

[toopty]

is it detected as Qualcomm HSUSB_BULK or something else?

Under windows yes that is what it was showing up as. When i plugged the phone into a windows box i get the same thing with it trying to connect a whole bunch of drives if that helps any.

 

[Partager.info]

Under windows yes that is what it was showing up as. When i plugged the phone into a windows box i get the same thing with it trying to connect a whole bunch of drives if that helps any.

I'm talking about linux.

 

[toopty]

I'm talking about linux.

Yes i am working from a live linux disk now and it was throwing up a lot of windows about unmounted disks. I was just letting you know about the partitoins in Windows as well as Linux. I've tried to flash the recovery partitoin. Even with the messages coming up. After reboot now i get a Fastboot mode started message on my phone. How should i procede?

 

[bitdomo]

@Partager.info the phone is turned off when you connect it to the pc or it have to be turned on once then wait to screen goes off? In qhsusb_bulk mode we can see the partitions in linux, or in linux the phone is not in qhsusb_bulk mode. qhsusb_bulk and Qualcomm HS-USB QDLoader 9008 are the same?

 

[Partager.info]

Yes i am working from a live linux disk now and it was throwing up a lot of windows about unmounted disks. I was just letting you know about the partitoins in Windows as well as Linux. I've tried to flash the recovery partitoin. Even with the messages coming up. After reboot now i get a Fastboot mode started message on my phone. How should i procede?

Did you use the described method in this tutorial to flash recovery?
If yes, then you should know that it is not enough to push only recovery. you should push all files in the tutorial.

 

[Partager.info]

@Partager.info the phone is turned off when you connect it to the pc or it have to be turned on once then wait to screen goes off? In qhsusb_bulk mode we can see the partitions in linux, or in linux the phone is not in qhsusb_bulk mode. qhsusb_bulk and Qualcomm HS-USB QDLoader 9008 are the same?

actually once you plug your phon to PC it should start automaticallly if it is shutdown. Then the screen goes black whil the phone is still on.
If you have installed qshusb_dload drivers then it is detected as Qualcomm HS-USB QDLoader 9006 or 9008.
and yes you can see partitions in linux but you can't see their content. that's why we use dd commands to push img files inside the appropriate partitions.

 

[bitdomo]

actually once you plug your phon to PC it should start automaticallly if it is shutdown. Then the screen goes black whil the phone is still on.
If you have installed qshusb_dload drivers then it is detected as Qualcomm HS-USB QDLoader 9006 or 9008.
and yes you can see partitions in linux but you can't see their content. that's why we use dd commands to push img files inside the appropriate partitions.

So if there is some whose phone doesn't turn on at all, just goes to directly to qhsub_dload becuase he/she killed the bootloader, then we can dd the bl images to the phone in linux? Am I correct? .

Sorry for asking such things, but this is really an interesting thing.

Sent from my Nexus 5 using xda app-developers app

 

[Partager.info]

So if there is some whose phone doesn't turn on at all, just goes to directly to qhsub_dload becuase he/she killed the bootloader, then we can dd the bl images to the phone in linux? Am I correct? .

Sorry for asking such things, but this is really an interesting thing.

Sent from my Nexus 5 using xda app-developers app

If you are experiencing the problem just give it a try.

 

[bitdomo]

If you are experiencing the problem just give it a try.

No I am not, but there are lot of people with different devices stucked in that qhsusb_dload mode.

You have a half bricked bootloader, since your phone gave sime sort sign of life when it turned on showed you that error. But i dont know what if it is totaly bricked.

Sent from my Nexus 5 using xda app-developers app

 

[AL_IRAQI]

can i use cygwin in windows ?

 

[toopty]

Did you use the described method in this tutorial to flash recovery?
If yes, then you should know that it is not enough to push only recovery. you should push all files in the tutorial.

I did push all the files, but it was very difficult because my device kept disconnecting while it was trying to connect all the drives on the phone. One of them must have not successfully pushed. I was able to flash all the files I needed via fastboot. Your method got me to that point. I was then able to get into Twrp and run the command at this link to get my phone to boot. http://forum.xda-developers.com/showthread.php?t=2451696. Now I have a working phone.

Thank you for all your help. Without guys like you I would not have been able to recover my phone.

 

[cgillie92]

Is there any way this can work on windows? I have this problem and just got back home and ready to jump on any fixes available

 

[cgillie92]

I almost finished the process in ubuntu but now when my phone is plugged in it keeps flashing on and off it seems and ubuntu seems to freeze while doing so like the phone is opening up a lot of files.. Im just going to call verizon or something tomorrow to see if i can get a replacement nothing seems to be working did anyone have this problem? ? or is it just me