DriveDroid? - LG V30 Questions & Answers

Just wondering if its possible to get DriveDroid working on the v30? I havent had absolutely any luck trying to get it to work. The computer does recognize anything i try. Ive tried on multiple different computers. I read about the kernel needing patched but i m not sure. Thanks for any help.

Bump

@Jbonn765
As per the notes in the app have you tried using a different image just in case it can't be booted through USB?
Also I have had issues with the new windows UEFI booting structure even with just booting from a regular USB stick so not sure as I haven't tried drive Droid yet but that could also be part of the problem. The one Linux image I had even supported booting from UEFI but still had issues so you may have to change the booting options to legacy boot inside your computers BIOS.

Jbonn765 said:
Bump
Click to expand...
Click to collapse
Have you had any luck with this?
I have LG G4 working without a problem, but I'm having the same trouble with V30 as you did or still do. I'd love to use my V30 with Drivedroid.

Related

[Q] Stuck in boot loop

Hello, usually don't have much issues with this sort of thing as I have decent experience with this.
I'm stuck on this particular issue though as my phone is in a constant boot loop. I was planning on just reflashing a ROM on to the device, but in the bootloader or recovery my pc will not detect the device at all so I am unable to run fastboot or adb commands on it. I have tried this on 3 pc's(2 Windows 8.1 and 1 Windows 7).
Any ideas or help would be greatly appreciated.
Windows 8 & 8.1 will not work. I used the DNA toolkit on a Windows XP laptop to get my phone out of the bootloop (when you were using the Windows 7 computer, were you using the USB 2.0 port? It's been mentioned in many posts that USB 3.0 will not work). Don't use the drivers from HTC SYNC, the proper drivers are here on XDA (just Google it).
Sent from my HTC Droid DNA running KICKDROID Sense 6/4.4.2 ROM via Tapatalk
Yes it was on USB 2.0. Drivers won't do me any good if device manager won't even detect the device is plugged in to begin with. That is the issue is I have no way to flash a new ROM because I can't even get device manager to pickup that the device is plugged in on any computer.
Until I switched to a Windows XP computer, my phone wasn't recognized either, no matter how often I updated the drivers.
Sent from my HTC Droid DNA running KICKDROID Sense 6/4.4.2 ROM via Tapatalk
You can't update the drivers for a device though until it detects there is a device there. There shouldn't be any issue with Windows 7 being able to detect a DNA.
I never had an issue with this until now and now I'm just stuck in either a boot loop or going into recovery.
I would be willing to to try XP for the fun of it when I get an opportunity, but don't feel it is necessary.
If I do a factory reset from CWM Recovery I can get into Cyanogenmod and go through the initial setup steps. After that it sits at a black screen, but I can drag the notification drawer down and get into the settings. Only have a minute or two before it reboots back into a boot loop.
Surely there has to be some way to fix this...
I managed to get it to stay on. Here is what I did to transfer a new ROM over. Since all I could access on the phone was the settings I changed a locksceen slider to the Play Store and installed AirDroid. I then transferred the file over through AirDroid.
I am about to flash it now. If this installs fine and clears up the boot loop issue then I guess that issue is fixed, but that still doesn't solve the problem with my device not connecting to the PC through USB.
Okay I managed to finally get a new ROM to flash over after some issues with the ROM zip itself. It flashed and said updating apps 77/77 and restarted and its been sitting at the boot logo for 10 minutes.
Still never got it to detect USB connection on PC either.
I don't have a single clue what to do now. Am I just out of luck at this point?
Okay I know I have flooded this with messages, but I have Cyanogenmod 10.2.1 on there and it seems to be working fine. I can reboot and it goes back into Android without a boot loop from what I can tell.
USB still does not work even within Android though. Is there an issue with the hardware itself? It charges fine.
justinds89 said:
Okay I know I have flooded this with messages, but I have Cyanogenmod 10.2.1 on there and it seems to be working fine. I can reboot and it goes back into Android without a boot loop from what I can tell.
USB still does not work even within Android though. Is there an issue with the hardware itself? It charges fine.
Click to expand...
Click to collapse
Is MTP checked or USB debugging enabled? If not you need to check them both
Sent from my HTC6435LVW using XDA Premium HD app
Yes both of them are checked.
Have you tried downloading pdanet that will reinstall adb asking with other drivers
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Yes I have. Still should allow normal file transfer without it and also at the very least device manager should detect it. I think I am just out of luck on this. At least it can still charge.
On the Win 7 machine, are you sure that USB port is good? Sorry no one asked that simple question.
Also, have you tried cleaning your micro USB port?
Sent from my HTC6435LVW using xda app-developers app
Yes, like I said other devices work fine on PC and also have tried it on 4 different computers. I also cleaned the port.
NP, appreciate the response.

Nexus 9, no OS, only TWRP, and can't connect to PC

So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...

Phone Not Detected in Flash Mode

Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.

HDX 7 TWRP, no os, no ADB access [Lineage OS]

Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
First verify drivers are working. For whatever reason legacy composite drivers from Motorola seem to work best with this device regardless of platform or host OS. Install the Motorola Device Manager from this page and then switch drivers. No need to launch the utility.
TWRP must be at v2.7 or above for ADB support. If below 2.8.6.0 you should consider updating via fastboot assuming bootloader has been unlocked. See: https://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547
If still no joy you will have to erase/replace aboot and rebuild the device from scratch. Data loss is likely.
hmm yeah, the main problem seems to be the tablet never shows up in device manager as any device... thanks for the hints though, will try the motorola device manager drivers...
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
fufu508 said:
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
Click to expand...
Click to collapse
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
fufu508 said:
In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled?
Click to expand...
Click to collapse
Oh snap, this is a good idea - will try when I get home.
TWRP 3.1.1-1, Win 10 64bit - yeah tested several usb ports on my computer - I originally rooted the HDX with this computer and windows 10 install about 2 years ago [side note do you guys remember reformatting every 6 months because windows was such a pos, I'm really glad those days are long gone!]
LOL yep Windows 10 nowadays does seem a lot more stable than the earlier stuff.
---------- Post added at 06:14 PM ---------- Previous post was at 05:50 PM ----------
Davey126 said:
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
Click to expand...
Click to collapse
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
fufu508 said:
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
Click to expand...
Click to collapse
Fair enough; I may have been a bit harsh in my response. I now see the passing reference to an Apple rig and appreciate the unfiltered perspective often obtained via Linux. That said, there is new info on the table that suggests the OP has access to a Win10x64 box which should connect effortlessly/reliably with Moto drivers and a quality USB cable. Mucking with drivers can be a PiTA on Windows; the Moto variants remove much of the pain - although you still have to select the proper driver after tethering in the target mode (adb or fastboot) as Windows will typically default to Microsoft/stock variants which rarely work with HDX devices.

LG G5 Bootloop

Hi there,
I recently bought a cheap lg G5 from eBay which said it was stuck on a bootloop. The seller said they weren't very tech savvy and I decided to give it a try, seemed fun. I have never done this before, so when searching on Google I stumbled upon threads saying it should be rather easy to fix by using LG Bridge and let it recover/repair the installation. However, after installing LG Bridge and LG Drivers from their website , every time I boot the phone in Download mode and it progresses into a firmware updating screen, my Windows 10 64bit fails to connect the device properly and prompting me with the following message:
USB device not recognized.
The last USB device you connected to this computer malfunctioned, and windows does not recognize it.
And in device manager it shows "Unknown USB Device (Device Descriptor Request Failed).
Is there anything I could try? Is it fixable like I thought?
Bump, anyone? Im stumped but would love tot learn about this
yointed said:
Bump, anyone? Im stumped but would love tot learn about this
Click to expand...
Click to collapse
I have never had the experience to get a bootloop but my guess is that you have some driver problems, thats why its not well recognised by your computer.
Try to check if there is a youtube tutorial with some links to the drivers related to the G5.
Sorry if this isnt very helpful, but its the best I can add to this topic.
---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------
Pistacho123Lol said:
I have never had the experience to get a bootloop but my guess is that you have some driver problems, thats why its not well recognised by your computer.
Try to check if there is a youtube tutorial with some links to the drivers related to the G5.
Sorry if this isnt very helpful, but its the best I can add to this topic.
Click to expand...
Click to collapse
Or try with another pc running windows 7, maybe your OS and compatibility is the problem!
Definitely a driver issue! I had a similar problem with moto x4! It was not being recognised by my pc! Uninstalling the previous usb driver fixed it for me! Try to remove any remnants of drivers you might have installed previously.
Thank you for the replies. I also thought it would be a driver issue, however I have already tried uninstalling and reinstalling the LG drivers for the LG G5 multiple times and I did not get it to work. Unfortunately, I do not have a Windows 7 computer. Would it be possible to install windows 7 solely for this, without a license key?
yointed said:
Thank you for the replies. I also thought it would be a driver issue, however I have already tried uninstalling and reinstalling the LG drivers for the LG G5 multiple times and I did not get it to work. Unfortunately, I do not have a Windows 7 computer. Would it be possible to install windows 7 solely for this, without a license key?
Click to expand...
Click to collapse
If you can find a copy of it some where. You can use it for like 30 days or so before activation.
I do not know any coding, and have never even rooted a device, but i had this problem with stock rom 8.0, tried looking into flashing new stock rom installed all the drivers, still couldnt connect to pc. After 4 days with no phone i thought id throw my other battery in it, it booted up perfectly like it was out of the box, probably because i tried the restore in safe mode... Hope this helps... P.s. id like to learn

Categories

Resources