Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
BraydenJW said:
Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
Click to expand...
Click to collapse
try these as drivers
Trying now
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
Thank you. Trying this now. I'll let you know how it goes.
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
BraydenJW said:
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
Click to expand...
Click to collapse
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
datechnerd said:
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
Click to expand...
Click to collapse
I'm afraid that did not work. I get an error message saying there wasn't any drivers found in that folder.
i.imgur.com/mkLZzBe.png
The two files are directly within the extract folder on my desktop. I'm running Windows 8. I right-clicked g2 in device manager, and selected update driver software and navigated to the extract folder on my desktop.
Thank you for your help so far, do you know where I could go from here?
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
BraydenJW said:
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
Click to expand...
Click to collapse
go to sideload and install drivers
datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
I'm sorry. I'm not entirely sure what you mean. When I go to sideload on TWRP, it gets stuck on the loading feature part indefinitely.
cityneversleepz said:
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
Click to expand...
Click to collapse
Thank you. I've tried it from my own laptop and my work computer and both have similar results. I'll try it from one of my older computers. I'll post back with my findings.
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
BraydenJW said:
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
datechnerd said:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
Click to expand...
Click to collapse
Thank you! Trying this now. I'll report back soon.
It's looking good! It showed up in my adb devices now. Just have to re-download the rom
I pushed the ROM and am installing it now. If this goes through successfully, I'll send you some money over paypal if you wish. Nothing huge, but at least a little as a token of my appreciation.
The ROM installed successfully. I'm just waiting for the first boot now. It's taking a while (about 5 minutes now) and I'm VERY nervous.
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
BraydenJW said:
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
Click to expand...
Click to collapse
that rom says let the first boot take as much time as needed.
datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Alright! I'll leave it for a few hours. PM me your paypal email if you'd like me to make a donation to you! You've been an extreme help!
datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Left it for over an hour. No luck. Something is wrong.
Related
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
vipergrm said:
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
jgaf said:
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
Click to expand...
Click to collapse
Thanks but that still didn't work for me. What exact driver did you use? Thanks!
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
jgaf said:
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
Click to expand...
Click to collapse
Thanks again. I will give this another go later and see what happens...
Any luck?
jgaf said:
Any luck?
Click to expand...
Click to collapse
I haven't had the opportunity to try it again just yet. I plan to do this tomorrow night on my nightshift in work. I'll let you know then. Thanks for asking
Tried tonight again and still no luck. I know the driver installed on this machine definitely works because its the same one that worked last week when I tried it. Oddly, the ADB driver picks up ok when I'm in the OS with debugging on but I don't think i would be able to flash whilst logged on to the OS. This is concerning because the CM10 ROM 4.2.2 which I have installed a the moment is firing up random reboots. I know it's still in experimental stage and I'm not complaining but it would be nice to change my ROM when needed. Below is a couple of screenshots of the problem I am having.
I had a similar problem my adb worked flawlessly when the OS was running, but it wouldn't get recognized when in recovery (fastboot worked too). So, what I wrote earlier solve my problem. Sucks it didn't work for you. Anyways do you have a recovery installed? If you do why can't you use that one? Also, I'm pretty sure you can install recovery when the OS is running, even from android terminal emulator in the pad.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Thanks again. I did do a backup thankfully and currently it is restoring. I will try to see after restoring the backup if it works. Another method I have found to repair the bootloader is the NVFLASH method, although this does scare me a little! I would be very interested in trying those drivers you have as mine are older but so far I have been unable to find anything newer, despite extensive searching. :crying:
Thanks for your help thus far! :good:
Looks like I'm finally getting somewhere. I decided that I would try connecting directly to the TF300 instead of through the keyboard dock and oddly this worked. The driver is now loading correctly and I am able to flash again! Now to choose a JB ROM... :good:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it
djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.
Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app
So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind
What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app
access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...
well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
You can install the recovery directly through the phone through Goomanager, but the fact that your computer doesn't recognize the device in fastboot is an issue I feel needs to be addressed. Goomanager solves the problem of the recovery, but I'm not sure about the fastboot issue.
Sent from my Nexus 4 using XDA Free mobile app
mikeric said:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
Click to expand...
Click to collapse
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, thank you, thank you. This enabled MTP mode for me in about 3 seconds on my Windows 8 PC. I had tried using Wug's toolkit both automated and manual even disabling enforcement of digital signatures on driver installation and had also installed latest ADK and Google drivers to no avail (all that got me was connection in camera mode and ability to see only DCIM). I don't remember having this kind of trouble last time I decided to play with my Nexus 4. Not sure if I was using my old Windows 7 machine then or if there is a conflict with the other drivers on my machine (I have recently flashed both Motorola and Samsung devices too). I wish you had posted a couple of hours sooner lol.
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.
I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".
I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0
kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.