Critical error on lg g2 fixed All Version (New & Easy Method)

Saturday, January 14, 2017

LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]

Problem Description

1.LG G2 stuck at boot logo.
2.Cannot enter download Mode
3.Stuck at factory reset screen (factory reset processing) and cannot enter RECOVERY
4.cannot enter fastboot mode
5.Phone not detecting in your computer either windows or linux!
6.Cannot enter qhsusb mode.
7.Gone to service centre and they said to replace motherboard and u hav no warranty!

This can occur when flashing wrong images to the partitions when in qhsusb mode.

IF YOU CAN ENTER QHSUSB MODE [BLACK SCREEN BOOT] THEN FOLLOW THIS TUTORIAL

http://criticalerroronlgg2fixing.blogspot.in/2017/01/lg-g2-unbrick-qhsusbbulk-no-recovery.html

Only solution for you guys is the following..

[THIS SOLUTION IS EASY BUT NEEDS YOU TO MESS WITH THE MOTHERBOARD.BUT SOLUTION DOESNOT REQUIRE HARDWARE SERVICE SKILLS.THE ONLY OTHER SOLUTION FOR YOU GUYS IS TO CHANGE THE MOTHERBOARD.SO THIS WIL BE YOUR ONLY CHOICE.]

Tools Required
1.Screw driver
2.Pry tool
3.Insulated small wire piece (sharped one edge).

Steps to FIX

1. Remove the Backcover of your phone.

2. Remove the backplastic on upper part of phone using screw driver.
after remove back cover and upper plastic

after remove back cover and upper plastic

3. Remove Battery Connector.
[THIS VIDEO IS A GOOD TUTORIAL TO DO ALL THIS]
https://www.youtube.com/watch?v=dGiNuRKMOZA&index=3&list=PL6179BzZqbzCbrEosyfifKh5ZHc0aJ9kL&t=5s

4.Remove all connectors except camera connector.
After removing connectors

5. Remove Buttons plate,(buttons plate is sticked to the surface.)
After removing buttons plate

6.Reattach connectors except battery connector.
after re-attaching battery connector

7. Connect phone to computer using usb cable

8. Short the capacitors c5000 and c5004 of the IC U5001 using wire end(Keep on trying till phone light comes and pc detects phone.)
capacitors to short

find the capacitors using this image.(short both siverdots and capacitor terminals above it)
find capacitors

Like this,
Shorting the capacitors

9. After going to black screen (qhsusb mode) attach battery connector and remove usb cable..

10. Then follow this thread to flash only laf.img,aboot.img and boot.img of your stock ROM.
http://criticalerroronlgg2fixing.blogspot.in/2017/01/lg-g2-unbrick-qhsusbbulk-no-recovery.html

11. After successful flash of images, remove battery connector and other connectors and reattach buttonsplate.

12 After attaching buttons plate,check your device going into download mode, and use flash tool to flash stock rom.

THEN PHONE SHOULD BOOT NORMALLY...ATTACH BACK PLASTIC AND PHONE BACK COVER..BE CAREFUL NOT TO TOUCH ANY CONTACTS..
THATS ALL,NOW YOU HAVE YOUR DEVICE COME BACK ALIVE...

IF I SAVED YOUR DEVICE, DONT FORGET TO HIT THANKS AND DONATE ME IF YOU CAN!..

Thanks
Partager.info for his linux solution.
brappa for sharing info.

Confirmed Working on
D800 (AT&T)
D801 (Tmobile)
D802 (International)
D803

[LG-G2] Unbrick (qhsusb_bulk)-NO Recovery mode, No download mode, fastboot mode started Fixed

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:

Quote:

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:

Code:

ls /dev/sd*

It should return something like this:

Quote:

/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

Quote:

Originally Posted 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:

Code:

gdisk -l /dev/sdb

you will get result:

Code:

Number  Start (sector)    End (sector)  Size       Code  Name
   1           32768          163839   64.0 MiB    0700  modem
   2          163840          165887   1024.0 KiB  FFFF  sbl1
   3          165888          166911   512.0 KiB   FFFF  dbi
   4          196608          197631   512.0 KiB   FFFF  DDR
   5          229376          231423   1024.0 KiB  FFFF  aboot
   6          231424          233471   1024.0 KiB  FFFF  rpm
   7          262144          294911   16.0 MiB    FFFF  boot
   8          294912          296959   1024.0 KiB  FFFF  tz
   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
  15          458752          491519   16.0 MiB    FFFF  recovery
  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

Code:

sudo -i

then type your password

now you must be under root access.

then type the following dd command:

Code:

dd if=/home/med/Desktop/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:

Code:

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://criticalerroronlgg2fixing.blogspot.in/2017/01/fix-installed-twrp-and-now-youre-stuck.html

Good Luck.

If you have fixed your your phone you can consider to pay me a coffee cup

paypal: prosanta.ghosh91@gmail.com

[FIX] Installed TWRP and now you're stuck after OTA?

Howdy all!

Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?

Here's the easy fix:

If you have ADB access, plug in your phone and run this:

Code:

adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.

If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:

Code:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.

After that finishes, you can reboot and continue on your happy way!

Let me know if this helps anyone!

As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.

Saturday, January 7, 2017

LG G2 Repair [G2 Q&A, HELP & TROUBLESHOOTING]

Saturday, December 31, 2016

Lg g2 repairing link

LG G2 Repair: https://www.youtube.com/playlist?list=PL6179BzZqbzCbrEosyfifKh5ZHc0aJ9kL&jct=B9MFdMxcARHu9hQA8gqR_SeZMV30hw

Monday, October 10, 2016

Mukti sangha Durga pujo 2016 [Ranaghat]

Saturday, October 1, 2016

LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]

YouTube : https://www.youtube.com/watch?v=E7zbs6of_4I

LG G2 Repair

https://www.youtube.com/user/prosantaghosh

Problem Description

1.LG G2 stuck at boot logo.
2.Cannot enter download Mode
3.Stuck at factory reset screen (factory reset processing) and cannot enter RECOVERY
4.cannot enter fastboot mode
5.Phone not detecting in your computer either windows or linux!
6.Cannot enter qhsusb mode.
7.Gone to service centre and they said to replace motherboard and u hav no warranty!

This can occur when flashing wrong images to the partitions when in qhsusb mode.
IF YOU CAN ENTER QHSUSB MODE [BLACK SCREEN BOOT] THEN FOLLOW THIS TUTORIAL
https://prosantaghosh91.blogspot.in/2015/08/lg-g2-repair.html
http://criticalerroronlgg2fixing.blogspot.in/p/blog-page.html

Only solution for you guys is the following..

[THIS SOLUTION IS EASY BUT NEEDS YOU TO MESS WITH THE MOTHERBOARD.BUT SOLUTION DOESNOT REQUIRE HARDWARE SERVICE SKILLS.THE ONLY OTHER SOLUTION FOR YOU GUYS IS TO CHANGE THE MOTHERBOARD.SO THIS WIL BE YOUR ONLY CHOICE.]

Tools Required

1.Screw driver
2.Pry tool
3.Insulated small wire piece (sharped one edge).

Steps to FIX

1. Remove the Backcover of your phone.

2. Remove the backplastic on upper part of phone using screw driver.
after remove back cover and upper plastic