I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
Coltonbyu said:
I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the Verizon LG G3 at http://forum.xda-developers.com/verizon-lg-g3 which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/verizon-lg-g3/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
Related
Hi I've been searching and searching, but haven't found any answers for my noobie woes!
I have SGS3 Korean model SHVE-210S:
First time attempting to root the phone and kinda jumped into it more quickly than I should have. I assumed I would be using MSkip's Samsung Galaxy S3 Intl Toolkit V6.0. I followed the directions very closely and everything went fine up until I attempted the Rooting Options #3 All in One. When the phone was powered up again, the USB drivers were not recognized. I had my phone debugged prior to shutdown
I've tried all options suggested in the forums- un-install, reboot, re-install / re-installing Kies / uninstalling USB devices via Windows 7 / etc etc.
Currently my phone just powers up to the Galaxy logo. thats it.
Wondering if my problem is that the Intl Toolkit is not the proper method for Korean models. And if not, have I just bricked it? Please help!!!
ALLINONE Rooting: Auto Reboot, then Device Unknown
Just a bit more detail to this problem:
It was during the #3, ALLINONE Rooting process when, after flashing the PDA file & Auto Reboot was selected, my phone reboots but the device drivers are no longer recognized, device unknown.
So I think I soft bricked it, trying to restore factory drivers via Odin, with help and advice from member [email protected] Problem is I didn't make a backup. Does anyone know if during the ALLINONE flash, backup files are made?
Anyhow, I will keep posting and talking to myself if need be. Hopefully this stumbling about will be helpful to someone in the future.
QUOTE=maximumkuo;33940873]Hi I've been searching and searching, but haven't found any answers for my noobie woes!
I have SGS3 Korean model SHVE-210S:
First time attempting to root the phone and kinda jumped into it more quickly than I should have. I assumed I would be using MSkip's Samsung Galaxy S3 Intl Toolkit V6.0. I followed the directions very closely and everything went fine up until I attempted the Rooting Options #3 All in One. When the phone was powered up again, the USB drivers were not recognized. I had my phone debugged prior to shutdown
I've tried all options suggested in the forums- un-install, reboot, re-install / re-installing Kies / uninstalling USB devices via Windows 7 / etc etc.
Currently my phone just powers up to the Galaxy logo. thats it.
Wondering if my problem is that the Intl Toolkit is not the proper method for Korean models. And if not, have I just bricked it? Please help!!![/QUOTE]
maximumkuo said:
Wondering if my problem is that the Intl Toolkit is not the proper method for Korean models. And if not, have I just bricked it? Please help!!!
Click to expand...
Click to collapse
look in My Android Solutions concerning usb problems , advise using a lap top, or testing on one
Hello!
I have an HTC m7, and am using Windows 7 to interface with it. Long story short, I have twrp on it, but no working operating system. For a moment yesterday, it appeared successfully in the results of /adb devices, though when I tried to push a new rom to the internal storage on the phone using adb sideload, it failed (made it to 100% but then said failed, and when I tried to install the created .zip file, it failed as well). Since that attempt, I have been unable to see my phone as an ADB device again - I've reinstalled HTC drivers, tried various usb cables, and gone through many iterations of /adb devices (blank) /adb kill-server. After failing to find a solution elsewhere on these forums or elsewhere, I come to you.
I'd love to know if there's anything that could cause the phone to disappear after it had been previously connected, and if there's some further steps I could take to get it to work!
Thanks for your help,
Devin
Hi there!
I suggest you try returning to stock, since you're having troubles with adb. Tho, it must be a driver issue, or cable, or USB port. Usually it ends up being the cable in cases similar to yours.
Anyway, if you have no luck, try returning to stock....here's a great guide,
>*HTC One*>*One General*>*[GUIDE] How to Return to 100% Stock
Of course you will need to install recovery and root again after.
Any questions on this can be asked in the guide thread.
Good luck!!
Ok so I finally found a way to root this b***h the LG L80. I've had 3 Androids before - Sony and two LG's, rooted them no problem, but this one is just ridicilously hard to root... So I found yet another way the ioroot method, but again I'm encountering some problems, this time it goes like this... I installed all the latest drivers and all, latest SDK and ADB, and everything's fine, the adb shell works and all, but when I put it in recovery mode and choose Apply update from ADB my Windows say's The device is not recognized, one of the devices attached to this computer has malfunctioned and blah, blah...
Could someone help me get the adb sideload thing working, please?
KrustsRZR said:
Ok so I finally found a way to root this b***h the LG L80. I've had 3 Androids before - Sony and two LG's, rooted them no problem, but this one is just ridicilously hard to root... So I found yet another way the ioroot method, but again I'm encountering some problems, this time it goes like this... I installed all the latest drivers and all, latest SDK and ADB, and everything's fine, the adb shell works and all, but when I put it in recovery mode and choose Apply update from ADB my Windows say's The device is not recognized, one of the devices attached to this computer has malfunctioned and blah, blah...
Could someone help me get the adb sideload thing working, please?
Click to expand...
Click to collapse
Hmm ... you have already posted on xda assist ([Completed] [Q] Need rooting help LG L80!).
So I assume that you rooted like described in the linked thread.
If you have issues, you can either ask in the rooting thread, or in the Android Q&A, Help & Troubleshooting forum.
Good luck !
Thread closed and thank you.
Hello, thanks for reading.
I want to start by saying I'm not asking how to fix my phone. All I need to know is how to make my computer recognize my phone so I can give it commands via adb/fastboot. And if you can help me I'd be happy to buy you a beer!
After that I think I can figure out the rest. I've been searching threads and trying things for weeks with no avail. My problem is similar to many, but slightly different so I really do need help. My LG G2 D801 is stuck in Fastboot Mode.
But my primary problem is that my computer doesn't recognize my phone in fastboot or adb, even with Official LG G2 D801 drivers.
I'll try to briefly and clearly describe my situation and what I've tried.
Long Story Short:
1. I rooted using TowelRoot method.
2. I broke my Recovery by trying to flash TWRP using an app called Flashify.
3. I attempted OTA update in spite of my broken Recovery and bricked my phone.
4. Now my phone only shows LG logo, then goes to Fastboot. (XXX = numbers change each time)
Fastboot Screen:
"[XXX] fastboot mode started
[XXX] udc_start ()"
5. Won't boot into Recovery or Download Mode.
6. So on my PC (Windows 8.1) I first cleared all Android drivers, then installed the official LG G2 D801 drivers, and Android Studio with ADB.exe and Fastboot.exe. I also tried different usb ports and cords.
7. But my PC doesn't recognize my phone, so when I run the command "list adb devices", my phone does not appear (However, my Brother's Kindle Fire, Galaxy Note 3, and Galaxy Note 2 show so it's just me). Perhaps this means I never checked USB debugging?
8. If someone can help me I'd be happy to buy them a beer:highfive:. Thanks for reading and I appreciate any help!
9. I should also mention that I also have access to a Linux computer running Ubuntu, although I'm not very familiar with that OS.
My Device's Information:
LG-D801 running LG's stock 4.2.2.
Software version D801V11b
Build Number JDQ39B
Kernel Version 3.4.0
I think I had your similar situation. Go here: http://www.koushikdutta.com/post/universal-adb-driver
Download and install that msi, it will install a universal driver that helped my PC see my phone when no other drivers could.
BrotherPanan said:
I'd be happy to buy you a beer!
Click to expand...
Click to collapse
If I helped you, I'm a Guinness type of girl
I happily accept donations
<--
Hello all,
This seems to be the very best forum for what I need, so I'm here. Here's my problem:
1- LG LS-720 phone, which used to be with Virgin Mobile. The bootloader screen shows Virgin Mobile and it has a few Virgin Mobile apps still on it. I use another phone for my daily usage.
2- I've been able to ROOT it just fine with Kingo.
3- I *think* the bootloader could be locked, but I could easily be wrong.
4- I've tried several different ways to install a new ROM, and all have failed.
5- I think I've installed the drivers correctly for this phone on my desktop, which runs Windows 10 x64.
6- I've used the fastboot and adb method, with Android SDK on my desktop. I keep running into the problem of my phone not being recognized during the
Code:
fastboot devices
step. It will say "Waiting for device".
7-
Code:
Adb devices
returns the model number of my phone along with a number.
8- As far as I can tell, my USB cable is not too long and it's in good shape. I think my USB ports are OK.
9- I'll answer any questions you have for me. I've spent several hours so far on this project, so I'd really like to find the solution, even if it's that my phone cannot be modded. Thank you very much in advance for your help!
Steve, a frustrated newb to Android phone modding
Mods: I placed this at http://forum.xda-developers.com/showthread.php?t=2257421&page=3456#post66963551 , so you can lock this now. Thanks.
Thread closed.
You reposted your thread in the correct section.