Help Restore a modified LG G2 to Original ROM, and unbrick it from Hard Brick, Thanks @iowabowtech

Nikoladj · Jun 7, 2015

iowabowtech said:
Like the OP, you'll want to verify your internal stampings to start with.

TNX for Replay

i have the same prob.as the guy witch u help him before this is the link where i found my prob http://androidforums.com/threads/sprint-lg-g2-stuck-in-fastboot-mode-please-help.865650/ but im using the D802 international variant so i stuck when i need to update my usb drivers coz there is some link for VZW_United Driver... i cant use that driver. I have Windows 7 32bit ..... i need your help

iowabowtech · Jun 7, 2015

Nikoladj said:
TNX for Replay i have the same prob.as the guy witch u help him before this is the link where i found my prob http://androidforums.com/threads/sprint-lg-g2-stuck-in-fastboot-mode-please-help.865650/ but im using the D802 international variant so i stuck when i need to update my usb drivers coz there is some link for VZW_United Driver... i cant use that driver. I have Windows 7 32bit ..... i need your help

For the purpose of getting working fastboot, use the PDAnet drivers:
Install program to PC, no need to run it as the drivers come with the download. Then connect phone and run fastboot reboot command to test connection. If phone reboots, you can proceed. If not, reboot PC, then connect phone and retry fastboot reboot command.

Nikoladj · Jun 7, 2015

iowabowtech said:
For the purpose of getting working fastboot, use the PDAnet drivers:
Install program to PC, no need to run it as the drivers come with the download. Then connect phone and run fastboot reboot command to test connection. If phone reboots, you can proceed. If not, reboot PC, then connect phone and retry fastboot reboot command.

ok il try this and give u feedback ... tnx for helping me :thumbsupdroid:

Nikoladj · Jun 7, 2015

Nikoladj · Jun 7, 2015

Nikoladj said:
ok il try this and give u feedback ... tnx for helping me

it stucks in rebooting ..... something i missing?

rootandroideasy · Jun 8, 2015

iowabowtech said:
Ok so you're on 4.2.2 so to install twrp, you can use Autorec for KitKat:
http://forum.xda-developers.com/showthread.php?t=2715496

Since this is a used D802, I must warn you that there are many sold online which have an alternate model's motherboard but have a d802 rom and d802 marked on the rear cover. The fact you get fastboot mode when trying to enter recovery is a red flag to me that you COULD be in that situation. However, the same could be said if you previously tried to flash twrp with Flashify or a similar app.

So if you want to be on the extreme safe side, remove your rear cover and take a pic of the internals so we can verify model. If you want to roll the dice, then you can use the Autorec app above as mentioned and select the model d802 for your twrp recovery when prompted. As long as you have a genuine d802 with a matching motherboard, that should work well for you.

4.2.2 is JellyBean......

iowabowtech · Jun 8, 2015

rootandroideasy said:
4.2.2 is JellyBean......

Oh my its been so long since anybody's been on JB, I glazed right over that. Thanks for pointing that out. So yeah, KK Autorec won't work in that situation.

2anyone · Jun 8, 2015

iowabowtech said:
edit: ok so i see those are the ones you used. Check your file sizes vs the listed file size to make sure they match. You must left click on each of those when downloading. If you happened to right click and "save as", it will instead save the URL link and that would cause major issues of course when flashing to the phone.

I think I find why I bricked my phone in previous flash. as I used download tool to download the file, the tool download the loading page, not the actually imgs.

And here is the question, as http://forum.xda-developers.com/showthread.php?t=2582142 said, I have to make sure I use the same imgs previous use, but the pervious used is wrong size. Can I use the correct img to replace the wrong size patitions in the Linux fixing processing?

Thanks...

2anyone · Jun 8, 2015

iowabowtech said:
Oh my its been so long since anybody's been on JB, I glazed right over that. Thanks for pointing that out. So yeah, KK Autorec won't work in that situation.

Oh, I was in 4.2.2 too... that's why I can't fix recovery after AutoRec.apk, but it do fixed the fastboot connection with PC, at least in my case.

iowabowtech · Jun 8, 2015

2anyone said:
I think I find why I bricked my phone in previous flash. as I used download tool to download the file, the tool download the loading page, not the actually imgs.

And here is the question, as http://forum.xda-developers.com/showthread.php?t=2582142 said, I have to make sure I use the same imgs previous use, but the pervious used is wrong size. Can I use the correct img to replace the wrong size patitions in the Linux fixing processing?

Thanks...

As long as you still have bulk mode, you should be able to fix. Use the correct partitions.

2anyone · Jun 8, 2015

iowabowtech said:
As long as you still have bulk mode, you should be able to fix. Use the correct partitions.

Could you advise me this, if the previous flash I use the "wrong size" file, and when I following the http://forum.xda-developers.com/showthread.php?t=2582142, should I use the "correct size" file to replace the "wrong size" patition?

Im not good at Linux, not sure what is partitions be setup there. but in windows, if there is a smaller size patition (which in my case is wrong) been settled, I have no way to replace it with a bigger size one(correct one).

So, in case any messes, could you give me some idea if I can go with the tutorial?

Thanks and waiting for your advice.

iowabowtech · Jun 8, 2015

2anyone said:
Could you advise me this, if the previous flash I use the "wrong size" file, and when I following the http://forum.xda-developers.com/showthread.php?t=2582142, should I use the "correct size" file to replace the "wrong size" patition?

Im not good at Linux, not sure what is partitions be setup there. but in windows, if there is a smaller size patition (which in my case is wrong) been settled, I have no way to replace it with a bigger size one(correct one).

So, in case any messes, could you give me some idea if I can go with the tutorial?

Thanks and waiting for your advice.

Yes you need to use the correct size partitions. Hopefully you won't get any "file too large" fails. You'll have to try and see but the only way it will get fixed is by flashing the partitions which are designed for your variant.

2anyone · Jun 8, 2015

iowabowtech said:
Yes you need to use the correct size partitions. Hopefully you won't get any "file too large" fails. You'll have to try and see but the only way it will get fixed is by flashing the partitions which are designed for your variant.

Now I would like to start to following the tutorial, but seems system can't read my phone this time, it not like yeaterday shows "QHSUSB_BULK" in devices manager, today, it shows "Unknown USB Devices (Device Descriptor Request Failed)" with a yellow triangle.

any idea how can I deal with this?

((

iowabowtech · Jun 8, 2015

2anyone said:
Now I would like to start to following the tutorial, but seems system can't read my phone this time, it not like yeaterday shows "QHSUSB_BULK" in devices manager, today, it shows "Unknown USB Devices (Device Descriptor Request Failed)" with a yellow triangle.

any idea how can I deal with this? ((

You need to install the Qualcomm USB driver, then recheck device manager. It may have changed to QDLoader 9008 and that won't show up without the Qualcomm driver installed. I'd link it but I'm mobile..should be able to find it via web search, there's several xda threads and some here that have it linked.

2anyone · Jun 8, 2015

iowabowtech said:
You need to install the Qualcomm USB driver, then recheck device manager. It may have changed to QDLoader 9008 and that won't show up without the Qualcomm driver installed. I'd link it but I'm mobile..should be able to find it via web search, there's several xda threads and some here that have it linked.

tried some of the driver, coming from google search, but seem not working, plug the phone and press power + volume up, still "unknown usb device" shows.

my problem is little bit different I think, as in the windows Device Manger, my phone is: "unknown usb device (device descrptor request failed)", if I download driver, and right click the unknown usb device, update driver, it always show me best driver already installed. But still "unknown".

is that possible you can give me a link for the Qualcomm USB driver? Thanks very much!!!

iowabowtech · Jun 8, 2015

2anyone said:
tried some of the driver, coming from google search, but seem not working, plug the phone and press power + volume up, still "unknown usb device" shows.

my problem is little bit different I think, as in the windows Device Manger, my phone is: "unknown usb device (device descrptor request failed)", if I download driver, and right click the unknown usb device, update driver, it always show me best driver already installed. But still "unknown".

is that possible you can give me a link for the Qualcomm USB driver? Thanks very much!!!

Try this one:
https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

2anyone · Jun 8, 2015

iowabowtech said:
Try this one:
https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

Thanks for reply, but still "unknown usb devices". Any idea?

Why it shows: A request for the USB device descriptor failed? Is that means driver not installed? or this phone broken?

dig to find answer by googling:

my error code is 43 in Device Manager, ref http://www.tomshardware.co.uk/answers/id-1664767/unknown-usb-device.html

the likely problem is:

The USB device may have encountered an internal error and simply stopped functioning.
Worn or faulty USB connectors and cables.
The USB device has failed.

and seems not driver problem (driver problem will have error 28?) as I installed all the Qcomm_Drivers without lucky, including the one you give me.

Calm down and Recall the entire process, yesterday, it was good to show: QHSUSB_BULK, and today when I plug in, shows "unknown", there was nothing changed in my PC nor Phone. Driver shouldn't a problem then?

If that's true, there must something failure inside the phone, as I leave it overnight, not sure if something changed under the whole black bricked screen.

Not sure if i am right, please give me some advice?

if that's seem the problem, is there any way i can try to reset my phone in brick situation? like combine button press or something?
or maybe my phone is run out of battery, and can't charge any more, as it's internal system failure?

iowabowtech · Jun 8, 2015

I don't think the driver is installed.

2anyone · Jun 9, 2015

iowabowtech said:
I don't think the driver is installed.

OK, I will following your advice, and trying to find the driver..

2anyone · Jun 9, 2015

@iowabowtech, finally, I make this phone QHSUSB_BULK mode back!!!

But everytime I plugout and plugin back, it become "unknown" again. So I have to take back cover off and put out the battery connector. wait couple of seconds and put it back again.

Now, I would like to follow the tutorial: http://forum.xda-developers.com/showthread.php?t=2582142, but I met problem in very first step.

connect phone to Ubuntu with usb cable,

ls /dev/sd*

it just output: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5

ls /dev/

it shows lots of devices, comparing the devices between Plugin and Pullout, I found, when plugin, there are 2 device added:

serial
ttyUSB0

tried "gdisk -l /dev/ttyUSB0"

shows me:

The specified path is a character device!

seems Ubuntu didn't recognize this phone? how can I deal with this?

Thank you.

iowabowtech · Jun 9, 2015

2anyone said:
@iowabowtech, finally, I make this phone QHSUSB_BULK mode back!!!

But everytime I plugout and plugin back, it become "unknown" again. So I have to take back cover off and put out the battery connector. wait couple of seconds and put it back again.

Now, I would like to follow the tutorial: http://forum.xda-developers.com/showthread.php?t=2582142, but I met problem in very first step.

connect phone to Ubuntu with usb cable,

ls /dev/sd*

it just output: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5

ls /dev/

it shows lots of devices, comparing the devices between Plugin and Pullout, I found, when plugin, there are 2 device added:

serial
ttyUSB0

tried "gdisk -l /dev/ttyUSB0"

shows me:

The specified path is a character device!

seems Ubuntu didn't recognize this phone? how can I deal with this?

Thank you.

Sometimes Ubuntu struggles to mount the partitions correctly or it does but they don't stay mounted. You should see roughly 36 partitions if bulk is working correctly. Other times it will show QHSUSB_Bulk mode but in reality, you may have QDLoader 9008 instead. It can still be fixed using different means but you really must have the Qualcomm usb driver installed to know for sure if you have 9006 (the bulk you had before) or 9008 (QDLoader mode).

Once you have the Qualcomm usb driver correctly installed, it will give you more information in device manager so you know exactly what you have.

2anyone · Jun 9, 2015

iowabowtech said:
Once you have the Qualcomm usb driver correctly installed, it will give you more information in device manager so you know exactly what you have.

thanks for replying, and great advice

In device manager, I updated QHSUSB_Bulk driver by point to Qcomm_Drivers you gave me. now it shows "Qualcomm HS-USB QDLoader 9008" at com6.

and when I tried this fixing: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830

I stuck in step 3: Test AP & EMMC, and shows me below:
My device still not found?

Any idea of this?

iowabowtech · Jun 9, 2015

Use the tool and instructs here:
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091

It's in the g3 forum but as stated, it also works for the G2 and it's using a different version of software which seems to work better. Also, make sure your device is showing in device manager as com6 as those instructions are simply using the com port that guy's phone was showing up as. Yours could be different and if so, change the com port setting accordingly. Some instructions for the 9008 fix say to reconnect the battery before attempting. I found this was not the case and I had to leave the battery cable unplugged during the duration of the fix.

This will not entirely fix your phone back to a bootable state, but it should fix download mode so you can complete the fix by flashing a stock tot/kdz afterward.

2anyone · Jun 9, 2015

Thank you very much!!!!!!!!!!

I don't know how to say how much you help me in these days! your are a star!

http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091

is really helpful, the software and 1 minute power button save me! now, my phone is unbricked!

@iowabowtech Thanks for your helping during these 2 days! or 3 days? you help me alot, and I learned lot from head to toe of LG G2~~~~

Thank you again and again!!!!

iowabowtech · Jun 9, 2015

Congrats! Well done.

Help Restore a modified LG G2 to Original ROM, and unbrick it from Hard Brick, Thanks @iowabowtech

Lurker

root@android:/ #

Lurker

Lurker

Lurker

Newbie

root@android:/ #

Newbie

Newbie

root@android:/ #

Newbie

root@android:/ #

Newbie

root@android:/ #

Newbie

root@android:/ #

Newbie

root@android:/ #

Newbie

Newbie

root@android:/ #

Newbie

root@android:/ #

Newbie

root@android:/ #

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads