First time poster, long time user of XDA...I tend to lurk.
Anyway, I just rooted, TWRP'd, and downloaded the newest PA for my LG G2 (ATT) but when I went to wipe, I accidentally clicked internal storage. So I'm stuck in TWRP right now. I decide to try my hand at side-loading, but I get the error message of: error: device not found. I checked device manager and the G2 is listed as an "Other Device" with an exclamation point on it. I go to load the driver... Can't find one.
Does anyone have any idea what driver I can use so the system will recognize my G2? I'd rather not go back to stock just to re-root/recovery/install. I have all the current drivers from LG, but as this is the G2 in recovery mode, I don't know how to get it recognized.
Thank you, in advance, for any help!
pseudohybrid said:
First time poster, long time user of XDA...I tend to lurk.
Anyway, I just rooted, TWRP'd, and downloaded the newest PA for my LG G2 (ATT) but when I went to wipe, I accidentally clicked internal storage. So I'm stuck in TWRP right now. I decide to try my hand at side-loading, but I get the error message of: error: device not found. I checked device manager and the G2 is listed as an "Other Device" with an exclamation point on it. I go to load the driver... Can't find one.
Does anyone have any idea what driver I can use so the system will recognize my G2? I'd rather not go back to stock just to re-root/recovery/install. I have all the current drivers from LG, but as this is the G2 in recovery mode, I don't know how to get it recognized.
Thank you, in advance, for any help!
Click to expand...
Click to collapse
If you're using windows 8 then you'll have to disable driver signing to install the adb driver. Google it.
Google universal adb driver (i think by koush). I had the same issue. I am on Windows 8 and didn't have to disable anything.
or if the universal adb drivers probably wont work you can try downloading the lg united mobile driver
http://www.lg.com/us/support-mobile/lg-D800
Thanks for the responses everyone!
I actually faked the device by using PDA net. It installed a generic lg driver for my G2, then adb was able to recognize the device and side load after that.
Hope this helps someone in the future.
Sent from my LG G2 using xda app-developers app
pseudohybrid said:
Thanks for the responses everyone!
I actually faked the device by using PDA net. It installed a generic lg driver for my G2, then adb was able to recognize the device and side load after that.
Hope this helps someone in the future.
Sent from my LG G2 using xda app-developers app
Click to expand...
Click to collapse
I am in the same position right now except i lost everything due to encryoting my phone how exactly did you get sideload to recognize your phone
---------- Post added at 09:58 PM ---------- Previous post was at 09:10 PM ----------
Never mind got working
Sent from my LG-D800 using xda app-developers app
pseudohybrid said:
Thanks for the responses everyone!
I actually faked the device by using PDA net. It installed a generic lg driver for my G2, then adb was able to recognize the device and side load after that.
Hope this helps someone in the future.
Sent from my LG G2 using xda app-developers app
Click to expand...
Click to collapse
Thanks, it took me forever of searching on XDA to find this. Works great after faking the ADB drivers for recovery. I used some other ADB driver, from Google inc, I believe. Great work.
pseudohybrid said:
Thanks for the responses everyone!
I actually faked the device by using PDA net. It installed a generic lg driver for my G2, then adb was able to recognize the device and side load after that.
Hope this helps someone in the future.
Sent from my LG G2 using xda app-developers app
Click to expand...
Click to collapse
plz im in the same position i stucked in philz recovery what can i do step by step and in device manager i got my device with yellow mark on it
make sure disable driver signing then install http://pdanet.co/bin/PdaNetA4180.exe and while install select LG, finished.
Related
Long story short. I had 2 streaks to update today, my friends and a coworkers. I started with my coworkers and used the QDL tool, it went fine. Proceeded with update 318 which also was fine. When I went to do my friends it kept erroring out. (He got it 2 days ago from best buy if that makes any difference.) I tried reinstalling the drivers, using different ports (reinstalled on those ports), didn't work. Went to fastboot let the driver install there, retried the method, nothing. Once his gets to the part where the phone needs to go to fastboot the charging screen that shows battery percentage comes up and the process fails.
I know this doesn't belong on development, but in general it wont get much action....
Any way to fix this issue with QDL not being able to put this device in fastboot? Remember the first streak worked fine.......
Sent from my Sprint Galaxy Tab
Where is the first streak from? What other differences were there between the two (softfware version, etc...)? Also, what is the status of the second streak now? Is it still functional with 1.6? Just asking because I got mine from Best Buy and I'm gonna try this method tomorrow...
Sent from my Dell Streak using XDA App
Use a different usb port. thats what fixed that error for me. You will have to reload the drivers for the new port. Good luck
Check out the FAQ section I added onto the guides page on streakdroid.com. The shorter version is that its probably related either to the usb port used or fastboot isn't working correctly. I'd try three things:
1. use a different USB port.
2. Try with the battery removed (Download and Fastboot mode don't need the battery, can get power through the usb cable)
3. In the case of a damaged fastboot, download streakflash from the Downloads section on streakdroid.com (may have to go into the Recovery section). Extract it into its own folder and use the older version of QDLTool included in it. This version only flashes certain system files. Once complete, go back and use QDLTool from repairtool.zip
slaydog said:
Where is the first streak from? What other differences were there between the two (softfware version, etc...)? Also, what is the status of the second streak now? Is it still functional with 1.6? Just asking because I got mine from Best Buy and I'm gonna try this method tomorrow...
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Both devices has 1.6 on them. Yeah, my friends just fails with the tool... boots back fine to 1.6 it's not soft bricked.
carhigh said:
Use a different usb port. thats what fixed that error for me. You will have to reload the drivers for the new port. Good luck
Click to expand...
Click to collapse
I also tried that! I tried 3 different ports! I'm thinking of trying a different PC.. At his work he has a 32-bit XP system, I ran the tool on a Win7 32-bit.
kantras said:
Check out the FAQ section I added onto the guides page on streakdroid.com. The shorter version is that its probably related either to the usb port used or fastboot isn't working correctly. I'd try three things:
1. use a different USB port.
2. Try with the battery removed (Download and Fastboot mode don't need the battery, can get power through the usb cable)
3. In the case of a damaged fastboot, download streakflash from the Downloads section on streakdroid.com (may have to go into the Recovery section). Extract it into its own folder and use the older version of QDLTool included in it. This version only flashes certain system files. Once complete, go back and use QDLTool from repairtool.zip
Click to expand...
Click to collapse
I'll have to try it with the battery removed completely.
If fast boot was damaged would I still be able to get into it? I was able to get to it fine?
I'll have time this weekend to tinker with it, so we'll see!
He was so bummed that he couldn't get Froyo LOL
Maybe it is just me...
When I picked up my streak, i first updated to 2.1 using Modaco's instructions. Then used clockmod for any future flashes.
It was simple and painless. It seems so many people are having problems / bricking their devices with QDL...
If I can't get ny friends to go ill just push clockwork to it and install 318 that way. If its even possible to flash a .pkg file in clockwork?
Sent from my ADR6300 using Tapatalk
still can't get it!!
Ok. I basically tried everything with this White Streak.
This time I jumped on a 32bit XP box.
Installed the Dell Fasboot drivers that are listed on the StreakDroid site
Installed the Qualcomm drivers as described
Still fails when trying to get ADB.
So I found this link that describes how to get ADB installed, so I followed it.
When I enabled USB debugging on the PC it was listed as 'Dell Streak' under the device manager, so per the link I had to 'Update Driver'. From there I chose 'android_winusb.inf' and the device was now listed as (I think) 'Android ADB composite interface' in the device manager.
Proceeded to run the program again and it still fails!
I told my buddy to go return his white one for a black one as because maybe white ones are an issue?
people are only having driver issues with the tool - no one is bricking their devices. The cases of where someone has actually 'bricked' it has been from internal sd card issues (hardware issues). QDL tools is being used to un 'brick' devices. getting the drivers installed is just a pain in the a$$
Not possible to flash .pkg via anything other than stock recovery.
I sent you a PM back on pocketables too but- leaving the phone sitting in waiting for fastboot while you do all of the below, click the driver thats listed as dell streak and uninstall. It should be listed as ADB composite bridge or something to that effect (cant remember off the top of my head). So once you uninstall, don't let it install it automatically, because it will most likely put it back right where it was. It will hopefully show as an 'Android 1.0' device with the yellow triangle. At that point, right click, update driver, and point it to the adb driver that is in the QDL tool folder. This is the only way that worked for me...
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
jeremyritzmann said:
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
Click to expand...
Click to collapse
yeah, thats where he is failing. The fail point is at 'waiting for adb device', meaning the qualcom driver is installed correctly (since it was able to even get that far) but the adb driver is failing - thus not allowing the tool to push files via fastboot.
jeremyritzmann said:
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
Click to expand...
Click to collapse
Yeah, it won't go to Fastboot. No matter what I do it just won't show Android 1.0 in the device manager.
Only time I can get it to show is if I uninstall the drivers while manually in fastboot mode. Once I uninstall the driver it says Android 1.0 with a (!). If I install the driver file it goes back to android adb composite interface.
shoman24v said:
Yeah, it won't go to Fastboot. No matter what I do it just won't show Android 1.0 in the device manager.
Only time I can get it to show is if I uninstall the drivers while manually in fastboot mode. Once I uninstall the driver it says Android 1.0 with a (!). If I install the driver file it goes back to android adb composite interface.
Click to expand...
Click to collapse
Thats what you want, you want it to show android adb composite interface
We only wanted the android 1.0 to show at first, signifying that the no drivers had been installed yet. Basically, starting fresh. Once you get it to show the android 1.0 driver, you right click, and update it and then it should update to the composite interface driver. Then you should be good to go.
Kohawk09 said:
Thats what you want, you want it to show android adb composite interface
We only wanted the android 1.0 to show at first, signifying that the no drivers had been installed yet. Basically, starting fresh. Once you get it to show the android 1.0 driver, you right click, and update it and then it should update to the composite interface driver. Then you should be good to go.
Click to expand...
Click to collapse
Oh ok. Well then everything seems to be ok. Just for some reason the program won't force the device into fastboot!
shoman24v said:
Oh ok. Well then everything seems to be ok. Just for some reason the program won't force the device into fastboot!
Click to expand...
Click to collapse
hmm - could be the fastboot driver possible. Hop on here, meralias is on and he is a master at the tool http://irc.netsplit.de/channels/?net=freenode&chat=#dellstreak
Hey.... well we got it.
I'll just say this.
Doesn't work with the white one
Worked with a black one
I thought you were crazy about the white ones, but I just read this in another post about flashing a new rom:
Kohawk09 said:
Only way to upgrade the white dell streaks is with the qdl tool. Theres something about them... All other methods just leave you in a boot loop.
Click to expand...
Click to collapse
Of course you are using qdl, but I guess ther must be a difference...
Sent from my Dell Streak using XDA App
Yeah there's something with the white ones. Further research proved it. I found a guide for it but we can't try it now. Black ones are the best to do it with.
Sent from my Sprint Galaxy Tab
any idea where I can find instructions for updating my white streak? I can't seem to get it to work following the streakdroid instructions.
Thanks
when its start fastBoot desconect the usb and continue let me know! sent from my Dell Streak using XDA App
okay ive tried everything but its still offline ive downloaded the drivers numerous time didnt work my adb is updated to to 1.0.31 ive tried different usb ports and when i try to root its saying looking for device and cant get past that so if you can help me out please im on the verizon lg g2 also
Jduncan312 said:
okay ive tried everything but its still offline ive downloaded the drivers numerous time didnt work my adb is updated to to 1.0.31 ive tried different usb ports and when i try to root its saying looking for device and cant get past that so if you can help me out please im on the verizon lg g2 also
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44461762&postcount=7
still isnt working man idk what the problem is
wargreymon89 said:
http://forum.xda-developers.com/showpost.php?p=44461762&postcount=7
Click to expand...
Click to collapse
Its either showing offline or unauthorized ive got sdk and java downloaded
On my Verizon model, when you plug in your usb cable, it will ask you how you want to connect (media sync, etc). You have to choose "Internet Connection" and the Ethernet, then adb will find it. The first time you connect with adb, you also have to accept an RSA certificate on your phone. Hope that helps
If it's showing offline and you have the correct pc connection selected, try disabling usb debugging then re-enabling it. Type adb devices in a command prompt and the RSA security should popup on the phone. That's what I had to do.
Sent from Verizon logo plastered G2 bastard
How do you get that RSA popup? or is there a way to add another? I haven't seen this at all.
I had this happen and it was I had the wrong lg drivers loaded. I googled Verizon LG G2 drivers and uninstalled the old ones and installed the new ones. That fixed the problem. Sorry I don't have the link handy.
I have a D802 and mine showed the same thing even when I have it set to media link but I went ahead with the root process with no issues and now have root. Before I switched it to media link it would just say disable in the comand prompt.
It's probably an sdk issue. Make sure you have sdk 16 and 17 fully downloaded. It's a security issue built in to 4.2 and I had this issue.
Sent from my VS980 4G using XDA Premium 4 mobile app
please help i cant get my computer to even recognize my g2 it also wont even go into download moad. Wth is wrong did i actually brick the thing
Your really need to give more detail for help here. Look in development for returning to stock for drivers and such
Sent from my LG-D800 using Tapatalk
no download mode
[email protected] said:
Your really need to give more detail for help here. Look in development for returning to stock for drivers and such
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Hello, I have the same issue.
I rooted the phone and unlocked the bootlader, it had cwm 6.0.4.5 installed. the phone took an owa update. the symptoms are as follows:
the phone only boots to the cwm recovery.
I can not get into download mode trying the up or down volume. My pc refuses to install the driver for the d800 even though i can see it as a device in device manager. I have installed lLGMlauncher as well as the LGUnitedMobileDriver.
Thank you for any ideas you may have
jflash101 said:
Hello, I have the same issue.
I rooted the phone and unlocked the bootlader, it had cwm 6.0.4.5 installed. the phone took an owa update. the symptoms are as follows:
the phone only boots to the cwm recovery.
I can not get into download mode trying the up or down volume. My pc refuses to install the driver for the d800 even though i can see it as a device in device manager. I have installed lLGMlauncher as well as the LGUnitedMobileDriver.
Thank you for any ideas you may have
Click to expand...
Click to collapse
Have you gone to device manager, update drivers on your device, let me choose and then pick the ( I cant remember the exact name but it has to do with media, maybe mtp driver. It will then mount you phone
download a Rom along with gaps and flash
This is the basics, as I am away from my PC right now, there are many guides in the general area, I believe.
Sorry I cant be of more help at the moment
easiest would be to go to the dev section and download one of the many kits to get you back on track though.
Sorry. Was traveling and in cebu now. When I get my internet running I will try to check the driver. I still can not get into downliad mode on the phone however. I think it isn't PC dependant
Hello today i got my g2 and downloaded the latest software. I am now attempting to root it with no success at all. Please assist me. Btw i try useing ioroot15
i used the IOROOT15 as well just today. worked fine for me. make sure all drivers are installed and ADB is recognized.
EDIT: mine was a Verizon variant.
I had to download drivers from lgs website then ioroot 15 worked for me mine is vzw too
Sent from my VS980 4G using XDA Premium 4 mobile app
Carloskeee said:
i used the IOROOT15 as well just today. worked fine for me. make sure all drivers are installed and ADB is recognized.
EDIT: mine was a Verizon variant.
Click to expand...
Click to collapse
Can to u send me a link for the driver down load my pc is not picking up my device
illusionnova said:
Can to u send me a link for the driver down load my pc is not picking up my device
Click to expand...
Click to collapse
Google is your friend: http://www.lg.com/us/support-mobile/lg-LGVS980
Thanks everyone root is successfully c:
Rooted went well... not the reboot
I was successful in rooting then attempted to install TWRP. The phone turned off then turned on with the "android open stomach and !" icon... it shut off a few mins later.
Now, all I get is the buzz when you power it on and a black screen. Im not able to enter the recovery mode using any combination of buttons.
LG Mobile Support Tool nor my computer will even recognize the device. Am I truly bricked beyond repair?
Hey guys, i need your help please.
My Lg G2 D802 goes only in download mode and i cant proceed with flashing recovery or anything because the MTP driver fails to be installed correctly.
The background of this is that i installed a marshmallow ROM it all went fine and booted. But then i realized that my recovery wasn't supported anymore so i had to install a newer one. That means that although i managed to install marshmallow with an old recovery, i could not get my phone into recovery after marshmallow booted normally. So i was trying to install a new recovery through bad apps and some windows programs. All i did was to soft brick my phone cause now the phone gets stuck in booting logo. I manage to get into download mode and connect it to windows 7 64 bit and windows 10 64bit but the MTP driver wont install correctly. I have tried a bunch of drivers and versions. Non work. So i cant use the LG windows tools.
I must add that fastboot hasnt worked also. Maybe i havent tried it in the correct way.
Please give me a way to proceed fixing my phone from download mode.
Same thing happened to me. Some guys say that it could only be recovered with J-tagging. Please someone share some kind of experience. Phone lays down with running LG logo, nothing else..
egemet said:
Same thing happened to me. Some guys say that it could only be recovered with J-tagging. Please someone share some kind of experience. Phone lays down with running LG logo, nothing else..
Click to expand...
Click to collapse
I dont know anything about J-tagging. Any instructions for LG G2 D802?
St.Stefanos said:
I dont know anything about J-tagging. Any instructions for LG G2 D802?
Click to expand...
Click to collapse
J Tagging is a professional thing with special equipment and a thorough knowledge of hardware / software. So try to find some pros who can handle it, and, of course it is not free..:crying:
---------- Post added at 07:22 PM ---------- Previous post was at 07:14 PM ----------
egemet said:
J Tagging is a professional thing with special equipment and a thorough knowledge of hardware / software. So try to find some pros who can handle it, and, of course it is not free..:crying:
Click to expand...
Click to collapse
My LG G2 had a nicely running ICEX ROM Final with TWRP recovery. Why on earth I thought of putting that f***king Optimus G3 ROM instead. It was installed, but right after, went bootlooping like crazy. Now I sent the phone for J-tag. I will have to wait another 2 weeks, if it can be recovered at all...
I am sure that J-tagging is not necessary. There must be a work around this MTP driver. How should i use the fastboot? Can i use google drivers of some sort?
St.Stefanos said:
I am sure that J-tagging is not necessary. There must be a work around this MTP driver. How should i use the fastboot? Can i use google drivers of some sort?
Click to expand...
Click to collapse
Maybe you can try this extensive method. I wish I had seen this before I sent G2 for repairs.
http://forum.xda-developers.com/lg-g2/general/mega-tut-how-to-fix-bricked-lg-g2-t3055033
What is your device shown on device manager? The port? I used to have same problem while ago
Sent from my LG-D802 using XDA-Developers mobile app