Hi there, I've recently tried rooting my lgg3 but im running into a few problems.
Just to clarify:
I've installed the drivers
Enabled USB de-bugging
Used task manager to end abd.
Tried MTP and PTP
But when ever I run the Oneclick root, it failes to start abd, then fails daemon, and then 'successfully' starts demon only to fail it again. It does this about 3 times before re-booting the phone into download mode.
From there, it asks me to wait for SuperSU to install, which it never does.
I'm really stuck here and could use any help. I've also tried using the GUI and .bat rooting tools, the .bat gets further into it than the actual, updated GUI, rebooting the phone, whereas the gui fails at the start as it cant start abd nor daemon.
For starters, please update with:
Your variant (model number)
Current Android software version
Which one-click root tool you are trying to use
The output from 'adb devices' entered into ADB
Related
I have tried this several times and it always gets stuck in the same spot. I have used adb before to root several of my Eris's. This one just doesn't seem to be working right.
It gets stuck at the
<waiting for device>
Do you have any suggestions?
scouter68 said:
I have tried this several times and it always gets stuck in the same spot. I have used adb before to root several of my Eris's. This one just doesn't seem to be working right.
It gets stuck at the
<waiting for device>
Do you have any suggestions?
Click to expand...
Click to collapse
Wish I could help.. do you have the drivers installed?
also try turning off your virus protections firewall when trying. never know.
I turned everything off, I installed the drivers in the package and I have the PDAnet drivers installed.
Comments on Red DI2 having issues with downgrade & root - updated w. log
Yeah, I hear you - DW's DI2 in red was in my hands last evening, took several hours while watching TV to get it done, finally - it should've been an easy one, but it wasn't.
Downgrade to HB.97 was easier, after uninstalling/rebooting & installing HTC drivers, etc. per excellent instructions. There're hidden usb/phone/device drivers that're conflicting & trying to run (use the OEM cable, it's better vs. a generic or Moto's.) Had to reboot both pc & phone a few times to try to get it to work together.
Getting the revolutionary to see the phone, run & zerging root was the challenge - finally managed to do it with relative success on an older laptop that I primary used as a backup when I'm on field assignment (XP-SP3 with antivirus/firewall disabled). Next, it would flash CWM's image file, after several attempts, went back to regular PC and used adb command to push it, worked & then reboot into recovery, did a full CWM Backup first, then flash the zip file to gain SU. It's now back on 2.3.3 & Sense 2.1 (instead of 2.3.4 and 3.0 as shipped)
I did it once before with the black DI2 so I figure it should be easy, it took more time with the locked bootloader on this red DI2. Seemed like the hidden VZ VCast Media Manager might be responsible, it's hiding somewhere and/or loading (install to a new PC) as soon as the device is connected, even in Charge Only mode - I'm too tired at this point to track it down & try a # of tools to uninstall it. Check the your lower right corner of the screen for the red V logo/symbol once you connect the DI2 to the PC before running the tools ....
Be patience & repeat, the only thing that I forget to try was to do a battery pull to power cycle it (something that I've done as recommended on SE phones).
[I]P.S. I saved last night's command prompt log of the downgrade - and for awhile, it was at a standstill with ZergRush, waiting for device & unable to find and identify the DI2. (see the attached log) - rechecked md5 sum, etc. - but, it came thru. [/I]
I've tried to uninstall that media sync also to no avail just right click and close you see it disappear if it shows back up close again
Sent from my ADR6350 using xda premium
Letitride said:
Yeah, I hear you - DW's DI2 in red was in my hands last evening, took several hours while watching TV to get it done, finally - it should've been an easy one, but it wasn't.
Downgrade to HB.97 was easier, after uninstalling/rebooting & installing HTC drivers, etc. per excellent instructions. There're hidden usb/phone/device drivers that're conflicting & trying to run (use the OEM cable, it's better vs. a generic or Moto's.) Had to reboot both pc & phone a few times to try to get it to work together.
Getting the revolutionary to see the phone, run & zerging root was the challenge - finally managed to do it with relative success on an older laptop that I primary used as a backup when I'm on field assignment (XP-SP3 with antivirus/firewall disabled). Next, it wouldn't flash CWM's image file, after several attempts, went back to regular PC and used adb command to push it, worked & then reboot into recovery, did a full CWM Backup first, then flash the zip file to gain SU. It's now back on 2.3.3 & Sense 2.1 (instead of 2.3.4 and 3.0 as shipped)
I did it once before with the black DI2 so I figure it should be easy, it took more time with the locked bootloader on this red DI2. Seemed like the hidden VZ VCast Media Manager might be responsible, it's hiding somewhere and/or loading (install to a new PC) as soon as the device is connected, even in Charge Only mode - I'm too tired at this point to track it down & try a # of tools to uninstall it. Check the your lower right corner of the screen for the red V logo/symbol once you connect the DI2 to the PC before running the tools ....
Be patience & repeat, the only thing that I forget to try was to do a battery pull to power cycle it (something that I've done as recommended on SE phones).
Click to expand...
Click to collapse
I had to do this on one of VZW's Red DI2's as well; My main PC is a Linux Mint machine and ADB had been broken for a while... I had to update the Android SDK and re-install Java to get it working again. Try updating the SDK and re-installing java. After that, type in "./adb devices" and see if it can find it. If you still get the "????????????", you may need to change your rules file to identify the phone...
I am not enjoying this... it still gets stuck at the same point. It is waiting on the device, the phone boots into the boot loader and just waits... forever.
I have re-installed the drivers and updated the SDK to make sure I have the latest USB drivers. I will restart the computer and the phone again and try later.
I'm also having some annoying issues with this.
View attachment 942722
Here's the command log that I've typically been getting, tried to downgrade my phone like 10 times, and it normally reboots running 2.3.4 after each try. (HBoot 0.98 fyi)
No idea what's going on, if someone on here is more adept at reading commands, could you tell me what's up?
Thanks in advance.
I had a lot of trouble getting the downgrade to work too. I had to type each command in manually in adb versus letting the tool do it. For some reason the tool was getting hung up during the process. Another thing I did was disabled the screen off on the phone while it is in charging mode and disabled my comps screen saver.
Sent from my Sabotaged Droid Incredible 2.
scouter68 said:
I am not enjoying this... it still gets stuck at the same point. It is waiting on the device, the phone boots into the boot loader and just waits... forever.
I have re-installed the drivers and updated the SDK to make sure I have the latest USB drivers. I will restart the computer and the phone again and try later.
Click to expand...
Click to collapse
This is because you don't have the fastboot drivers working correctly. You'll need to uninstall the PDAnet drivers and all other drivers on your machine for that matter and restart your computer to clean out those uninstalls. Then install the newer HTC drivers.
You can test if you have your adb folder setup correctly by doing "fastboot devices" instead of "adb devices" while in the bootloader
Edit: I had switched to a different (charge-only) cable halfway through and not realized it. Switched back and the phone was recognized again.
Steps:
I unlocked my bootloader with Wug's toolkit.
I installed the zips that it asked me to (that it put on my SD card).
I updated SuperSU
I got a notice to update the SuperSU binary.
SuperSU binary won't install via Play.
Tried to install via TWRP and recovery isn't twrp, seems to be stock recovery (thought I installed it, maybe not)
Now the toolkit won't recognize my device. neither will windows. It gives me the USB noise but won't show the device in the folder list and defaults to USB for Charging. I can change it but it doesn't make it recognizable.
I'm trying ot back out and try again but the toolkit says it finds the device but that it's listed as "offline". When I toggle the USB debugging, it doesn't ask me to fingerprint my computer.
When I try the "soft brick" option to flash from the bootloader, the script reports a failure "data transfer failure (unknown error)", then says "rebooting into bootloader..." and does nothing else BUT my phone's bootloader still says "downloading..." When I reboot, the script throws another failure and says "waiting for device". when I bootload into it again and connect, the script throws more failures.
I've been on this for 4 hours, getting pretty fatigued (through the night on a weekend when family is visiting. yes, I'm an idiot for trying this procedure but the 5 went so smoothly I was optimistic).
try reinstalling the drivers. also the OEM-lock option in the dev-settings may help bringing you back to step one.
I was halfway through installing the drivers when I quit for sleep last night.
I'm using the LG-Mobile-Driver_v3.14.1.exe package, and the installer says it installed successfully, but windows says that MTP and PCI Simple Communications Controller had "No driver found", so the device doesn't show up in my drive list and wugfresh won't detect it.
I've removed all Google, LG, MTP, and Nexus drivers in USBDeview, but can't seem to figure this out.
I was able to get the drivers installed on my wife's system, so I'll open another thread about this if I can't get them to work.
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
oubravs2b said:
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
Click to expand...
Click to collapse
so, the reason my computer stopped recognizing the phone was that I switched to a charge-only cable without realizing it. Switched back and the phone recognized fine.
The weird thing is, the charge-only cable worked fine for data xfer on my wife's system.
Hi all, so this is my first post and a last resort attempt at recovering my phone, after hours of googling and downloading everything suggested by various forums, and still being stuck... Sorry for the long post, just trying to list all my attempts to fix it.
So, I've been on stock 5.0 Lollipop (v20n) for a long time, with the only issue being that android OS suddenly will decide for no good reason to make my phone super hot and drain my whole battery in 2 hours flat... Nothing that worked for other people worked for me, so yesterday I decided f*ck it, i'm gonna root and flash Fulmics 5.0, using this: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 (tried the classic method).
Everything went as per instructions, until I went "Send_Command.exe \\.\COM12 < reboot" and the phone got stuck in a bootloop...
So in other words, my phone is not rooted yet (thus nandroid/titanium backup was not made), TWRP was not installed (so i cant reflash stock kitkat). Latest LG drivers are installed (v4.1.1.0 from http://lgusbdriver.com/windows/lg-usb-driver-v4-1-1-0). Adb and fastboot are installed (http://forum.xda-developers.com/showthread.php?p=48915118#post48915118).
I can boot into download mode (Volume up + plugging in my usb cable), but i cant get adb or fastboot to see my device, when i try to flash twrp.img though command prompt! Downloaded the LG Flash tool 2014 to try and reflash stock kitkat 4.4.2 v10E, but it also can't see my device!! LG PC Suite can't see my phone when trying to connect...
I have removed the LG drivers from device manager and reinstalled the 4.1.1.0 drivers several times, but everytime i plug in my cable Windows (7 ultimate) tries (and fails) to install some drivers for it, even though i installed them already.
I tried to do a factory reset (holding volume - and power button, releasing and pressing them again when i see the LG logo), it gives me the option of doing a reset, but it goes back to the bootloop.
I have installed the Android SDK files (https://developer.android.com/studio/index.html), not the whole 1187mb SDK bundle, just the 144mb installer_r24.4.1-windows.exe. But i cant get my pc to see my device!
Went to a friends house and installed the LG drivers on his pc, installed adb and fastboot (as above), opened a command prompt in the folder where the adb and fastboot dll's are, and neither "adb devices" nor "fastboot devices" lists my phone.
What am i doing wrong???
TL;DR LG G3 d855 stuck in bootloop, but can boot into download mode, no root, twrp recovery not installed, LG drivers and adb fastboot installed on pc, adb refuses to see my device but windows tries (and fails) to install some drivers when i plug the cable in. Factory reset didn't work. Need help please!
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
Hi all,
This is my first thread on this website and I am not that expert of rooting and installing custom ROM's. I am trying to find a solution on your website for 2 days but I couldn't solved although I tried everything.
I have an issue with my LG G Pad 8.3 (LG V500) tablet. It was installed 5.0.2 stock ROM (Korean version) and I decided to root the device and install custom ROM. I used King Root to unlock the device. Then I installed TWRP thing to my tablet and started flashing ROM process. While working the tablet restarted automatically and it was stuck at the startup with a LG icon on the screen.
I decided to make factory hard reset it in order to get rid of this but when I try to make factory reset with button combinations I get the following error;
* Confirmed *
Secure booting Error!
Cause : boot certification verify
Then I searched for the forums and first installed Android Studio, then by using SDK manager tools, I also installed USB drivers.
As the device can connect download mode, I installed adb thing and tried to fix it. But apparently laptop does not recognize the device. I run the command "adb devices" and there is no devices in the list.
I also tried to use twrp recovery tools but again it didn't recognize the device.
When I check the Device Manager when the tablet is connected to laptop on download mode, I can see LGE AndroidNet USB Serial Port (COM4) thing installed. I also tried to install Android Device drivers (Android ADB Interface, Android Bootloader Interface, Android Composite ADB Interface) but they are not working properly and they have question mark on their left side.
So as you can understand I am drawning with the issues and don't know what to do next. Apparently laptop does not recognize the device but although I checked the xda forums and other forums for 2 days, I couldn't solve. I would really appreciate if you can help me.
Best
ironunited said:
Hi all,
This is my first thread on this website and I am not that expert of rooting and installing custom ROM's. I am trying to find a solution on your website for 2 days but I couldn't solved although I tried everything.
I have an issue with my LG G Pad 8.3 (LG V500) tablet. It was installed 5.0.2 stock ROM (Korean version) and I decided to root the device and install custom ROM. I used King Root to unlock the device. Then I installed TWRP thing to my tablet and started flashing ROM process. While working the tablet restarted automatically and it was stuck at the startup with a LG icon on the screen.
I decided to make factory hard reset it in order to get rid of this but when I try to make factory reset with button combinations I get the following error;
* Confirmed *
Secure booting Error!
Cause : boot certification verify
Then I searched for the forums and first installed Android Studio, then by using SDK manager tools, I also installed USB drivers.
As the device can connect download mode, I installed adb thing and tried to fix it. But apparently laptop does not recognize the device. I run the command "adb devices" and there is no devices in the list.
I also tried to use twrp recovery tools but again it didn't recognize the device.
When I check the Device Manager when the tablet is connected to laptop on download mode, I can see LGE AndroidNet USB Serial Port (COM4) thing installed. I also tried to install Android Device drivers (Android ADB Interface, Android Bootloader Interface, Android Composite ADB Interface) but they are not working properly and they have question mark on their left side.
So as you can understand I am drawning with the issues and don't know what to do next. Apparently laptop does not recognize the device but although I checked the xda forums and other forums for 2 days, I couldn't solve. I would really appreciate if you can help me.
Best
Click to expand...
Click to collapse
I couldn't get the computer to recognize one of my LG devices using ADB until I used this...http://forum.xda-developers.com/showthread.php?t=2588979