Hi,
I have an O2 retail Galaxy Nexus. Before I began to use the phone I thought I would root it now.
I've read through the instructions and tips but unfortunately my PC can't find the drivers...
I could still access the phone so I opened the .bat for Windows Superboot.
CMD read < Waiting for Device> so I closed the cmd after waiting.
The phone now seems to be stuck on Fastboot Mode. Holding buttons or using the screen do not do anything.
This is my first Android device.
Is there a way for me to get back to normal phone mode until I sort the drivers?
I would be tempted to remove the battery if this were any other circumstance.
Will the older threads about Fastboot being stuck also work?
Thanks in advance.
I hit this myself and yanked out the battery to overcome it. Sorry if that's not what you want to hear, but I do now have a rooted device.
In response to fastboot freezing at <waiting for device> you need to install the fastboot drivers (these are not included in the root zip). Google around to find the best way to install them, I ended up installing pdanet onto my PC - as this has them included - and then removed the application after the drivers were installed.
Thanks for the reassurance, el3ctrik. Battery pull allowed it to boot normally.
Think I'll wait til the morning before trying again... Read some more articles, and try the pdanet method.
Ta!
I remember struggling with the drivers when I rooted my NS - I also ended up installing PDA net to sort out the issue.
Sent from my Nexus S using XDA App
I'm looking at buying a GNex for next to nothing, but the seller says it's stuck in fastboot. Came across this thread after a search, is this a fixable issue?
You need to install two drivers. Actually, it is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode.
I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, NOT the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
OMG... finally got it working. I installed HTC Sync Manager again and decided to run it and see what happened. While it was scanning for music on my computer windows installed the drivers. More than once it seems.
Now I need to know if I can uninstall Sync Manager but keep the drivers. It keeps opening up and I don't know if it's safe to flash recovery if that's going to happen.
Flashed TWRP successfully and made my back up.
--------------------------
OLD NEWS BELOW:
Here's the deal... I just flashed the 3.x RUU so I'm stock but I'm unlocked and s-off. I'm trying to flash TWRP via fastboot so I can get a custom ROM on here. I turned on USB debugging on the phone.
First of all, that stupid HTC Sync manager keeps trying to install and I don't know how to stop it. Googling has not helped with this.
Second, I can't get the device to be seen in adb, or at least not online. I seem to be going backwards with all the steps I have taken to try to get this to happen.
I'm using dotatt's adb package. When I attach the phone while it is off windows looks for drivers and usually fails. One time it seemed to work and adb saw the device but then when it boots up that Sync Manager wants to install so I decline. Then my phone was seen but listed as offline.
So I tried uninstalling all HTC things on my computer and reattach phone. Didn't help anything. I tried installing the HTC Sync then uninstalling it thinking I would get the drivers, no go.
I grabbed these Universal ADB drivers http://www.koushikdutta.com/post/universal-adb-driver linked to from a twrp page here https://twrp.me/devices/htconem9.html
Nothing lists as a device in ADB at all now.
My windows Device Manager shows "Unkown Device" under "Other Devices" with no driver listed.
Tried this:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
http://forum.xda-developers.com/showthread.php?t=2588979
Still not working.
ACK! Can anyone help me out?
Is there still an issue with using usb 3.0 ports? I feel like I heard something about that way back when.
That's pretty much how it's always been. Best way to get the appropriate drivers is to install HTC sync, let it do its thing, reboot the PC, then uninstall HTC sync without removing the drivers. To the best of my knowledge, been that way since at least the days of the Incredible, if not before. At least it's how I've always gotten the drivers to use adb.
Yeah I remember that from the Rezound, which is why I did that, but it seems that the drivers didn't actually get installed this time until I let HTC Sync Manager start running and scanning my computer. That's when I saw the message that it was looking for drivers and twice it told me it installed them.
I would think it would have them installed during the 'actual' installation process. So I guess I just uninstalled prematurely. Seems weird. But it's working now so all good.
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.
Tl;dr: DM-VERITY error after upgrading, SIM card not recognized. Can't get fastboot to work to try out a solution. Everything is going to ****.
So... this one's a doozy.
I tried to install the update by dropping it onto my phone and using TWRP to install it, which I ended up having to update. After I updated, I get a brief second popup screen when I reboot telling me that there is an invalid DM-VERITY (it only pops up for a second). When the phone loads, it doesn't recognize SIMs.
I did some research and it looks like the issue can be fixed by flashing the stock recovery. So I go to flash the stock recovery, which requires the usage of fastboot. Which I always have problems with.
Sure enough, adb recognizes my device but fastboot doesn't. I have all the drivers downloaded, so I go check on my device in device manager. For some reason, it's always listed under "Portable Devices" no matter what I do... no matter whether I enable/disable USB debugging, MTP/PTP/Charging, etc. I was under the impression that a device not being recognized by fastboot meant that you had to go find it under "other devices" and manually update the drivers. However, the only options here are ADB drivers, not bootloader ones.
So I did more research. Turns out that Windows 10 is ****ty and you have to disable secure boot to install unsigned drivers. So I went into my BIOS, disabled it, booted into safe mode, reinstalled the drivers, and... nothing.
So I'm basically where I started and for the first time in a while, I have no clue what to do. Nothing's working. I even tried to load an older version of OxygenOS and install it with TWRP (sideloading didn't work), which didn't work. I'm totally stuck and I have no idea what to do.
If you don't care about your data, just use the unbrick guide method 2. Don't know about the first one, I have never used that. That will get you to a like new phone. You could even get 4.0.3 version, using the newer unbrick toolkit.
Windows 10 x64 isn't that sh**y. I've never had issues with the drivers, and they all install automatically (fastboot, adb, unbrick tool). They all work with 4 phones without any issues: OP3, Nexus 5X, Nexus 5, Nexus 4.
True, I had just unbrick my op3 2 days back by method 2 .
Well this was wild
So I did try to unbrick and got the Sahara communication error.
But I ended up fixing my problem! Someone on Reddit correctly pointed out that the dm-verity screen often exists simply as a result of unlocking the bootloader. I was assuming that one symptom caused the other. They suggested just reflashing OnePlus's 4.1.3 full ROM. I did it exactly the same way as I had when I got the error (with TWRP) and... it worked!
I'm astounded. My phone wouldn't work with fastboot, wasn't recognized by the unbrick toolkit, and had a host of other issues. I did 7 hours of work on it and the solution ended up being that I just needed to reinstall the OS (again). My hypothesis is that there was some hidden issue that resulted in part of the firmware being incorrectly updated, and when I wiped my device as part of my troubleshooting process it was ready to be reflashed with the OS.
Thank you guys so much anyway!
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
dziedziol said:
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
Click to expand...
Click to collapse
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
uweork said:
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
Click to expand...
Click to collapse
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
dziedziol said:
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
Click to expand...
Click to collapse
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
RuedasLocas said:
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
Click to expand...
Click to collapse
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
You could Check if FWUL from SteadfasterX is helping You out with your Problem.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
With the Installed Salt You cann Backup your Device.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
<waiting for any device> because if windows don't recognizes the device as it should adb will never "see" it.
While on the process, pay attention to the device manager. When you get the message in cmd of <waiting for any device>, uninstall your device and make device manager search for devices.
If still shows you as the same device and adb still waiting, you might have to uninstall the device and install it manually choosing from a list. Now I don't remember how it is suppose to be detected...
During install and uninstall don't disconnect the device from the computer, and remember, use a USB2 port.
I already got that several time. Took me time but that's how I managed to fix it.
okay, guys, it is a shame for me... but I worked out what is wrong with my phone.. maybe not with my phone, but what is wrong with me.
all I needed to do to launch a fastboot was type "adb reboot bootloader" and everything is fine now.
Sorry that you had to give me so much tips and this problem turned to be my stupid mistake, but I'm glad that i won't have to install linux and play with virtual machines to repair my phone
Anyway, thanks for your kindness and will to help, greetings for everyone!
@edit: Turns out that i have one more question. I want to uninstall xposed framework. But there are many versions of uninstaller on their site. Is there any risk that i will "break" my G4 if I use the newest one? I have xposed version 87 and I don't want to do something stupid. thanks in advance.
somebody knows? if I can use the newest version of uninstaller no matter which version of xposed framework im using?