I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the device manager I get a yellow flag on the ADB interface:
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Seleuco said:
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
?
In the device manager I get a yellow flag on the ADB interface:
In the device manager I get a yellow flag on the ADB interface:
?
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Click to expand...
Click to collapse
Honestly you don't need adb portion working to do this. Have you tried seeing if your computer recognizes your opo in fastboot mode?
Turn your phone off hold volume up and power button it will boot into fastboot. Then plug your phone into your computer let it install drivers then open command prompt where your fastboot file is and type fastboot devices if it shows something your good to go follow the rest of the guide unlock bootloader and install a custom recovery and SuperSU to root.
Also if its me I would install twrp recovery.
you sure you got the right drivers?
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
giaur said:
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
Click to expand...
Click to collapse
Honestly I don't even know at this point, I tried deleting and installing them a dozen times from different sources, but it doesn't recognize them. Do you know any idiot-proow way of installing the drivers?
wulsic said:
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
Click to expand...
Click to collapse
Thanks, but I actually took the screenshots right after running that program
Seleuco said:
Thanks, but I actually took the screenshots right after running that program
Click to expand...
Click to collapse
Did you also tried to install the driver manually in device manager?
See this link how you can do that:
http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If these drivers don't work and or can't install then just extract Snoop05's adb installer and use those drivers :good: hope this would work now,
the issue is probably that there are so many drivers installed that they are conflicting with each other and windows is just deciding which one is better, so manually overriding it should fix it and else I guess you have to remove the old adb drivers with an program but first try these easy methods
Related
Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.
After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!
I've tried just about everything to get my fastboot working. I'm running on Windows 8. I've tried tool and scripts, different drivers, HTC Sync, EVERYTHING.
I've gotten ADB to work but fastboot won't recognize my phone.When I put my phone into fastboot mode, I can go into my computer and look up the phone in device manager and I do see the phone. Unfortunately, it presents an error that say the device has failed to start. This has been unchanged through out every "fix" I've tried. Any ideas?
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
timmaaa said:
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
Click to expand...
Click to collapse
Oops, sorry. I've tried the tools that are supposed to set up fastboot for you, I downloaded the SDK and got the fastboot and adb files but nothing shows up in the "fastboot devices". I've also tried the HTC Sync route as well as numerous drivers that are claimed to be the "fix".
What about some of the guides that are available that specifically address this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Evita
timmaaa said:
What about some of the guides that are available that specifically address this problem?
Sent from my Evita
Click to expand...
Click to collapse
I've tried all the results on that first page. Nearly every time, I get an error message with a yellow triangle for an icon:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
timmaaa said:
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
Click to expand...
Click to collapse
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
KungPow90 said:
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
Click to expand...
Click to collapse
Download latest HTC driver , go into your device manager in win 8 and in device mgr menu options on top make sure and click show hidden (not connected ) devices. You then will have to click onto the greyed out HTC or android name in device mgr tree and update manually . you have to actually go to the sub folder in the driver update and not just click the folder that its in. Lol its a pain but it does work. You can Google manually install HTC driver for win 8 and there is couple tutorials. Hope it helps. I beta tested win 8
And had to do that. Lol im back to win 7 and Ubuntu now
Senseless Power Unlocked
I was using wugs toolkit and this brought adb, fastboot and drivers. Now I would like to use adb and fastboot independent from the toolkit. I guess drivers stay the same, but what is the best way to install fastboot and adb systemwide, without having to install the full sdk?
Lownita said:
I was using wugs toolkit and this brought adb, fastboot and drivers. Now I would like to use adb and fastboot independent from the toolkit. I guess drivers stay the same, but what is the best way to install fastboot and adb systemwide, without having to install the full sdk?
Click to expand...
Click to collapse
I, personally, would use the SDK to get everything on your PC. At least then you've got all the files
After that, follow this guide:
http://forum.xda-developers.com/showthread.php?t=1161776
After that, you can use adb/fastboot from any location
Please go to my "adb and fastboot" thread which you can get to via "guides and info threads" link in my signature. This will give you naked drivers and 15 second adb and fastboot installer. Quickest and easiest method IMHO
rootSU said:
Please go to my "adb and fastboot" thread which you can get to via "guides and info threads" link in my signature. This will give you naked drivers and 15 second adb and fastboot installer. Quickest and easiest method IMHO
Click to expand...
Click to collapse
Hey mate, I tried the tool, but it doesn't work:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Lownita just use it for adb and fastboot. In my thread there is a separate link for drivera
@rootSU I'll try! Well, does the device have to be connected to the PC while installing any of those? I guess not? (Ofc drivers install themselves when phones gets connected afterwards).
Lownita said:
@rootSU I'll try! Well, does the device have to be connected to the PC while installing any of those? I guess not? (Ofc drivers install themselves when phones gets connected afterwards).
Click to expand...
Click to collapse
Yeah needs to be connected because you need to right click the device in device manager. Just connect it in recovery or bootloader depending which one you're most likely to use most.
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Adb is adb.
Fastboot is fastboot.
For adb, you need adb binaries.
For fastboot, you need fastboot binaries.
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
kiwigi said:
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
Click to expand...
Click to collapse
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
d
VD171 said:
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Click to expand...
Click to collapse
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
kiwigi said:
d
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
Click to expand...
Click to collapse
Probably because you didn't have drivers installed.
You need to find the specific drivers for your device model and install it.
Good luck.
VD171 said:
....
You need to find the specific drivers for your device model and install it.
..
Click to expand...
Click to collapse
I have searched for hours and all I have found seems not to be compatible with S7 sm-g930f. I have also followed this https://androidadbdriver.com/ specific to my mobile.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you really try to find ?
Here is the download for samsung usb drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Install it and reboot.
If it doesn't work, probably you have any problem in your device manager.
I'm an user linux and I hate windows.
Good luck google'ing it.
Im having the same problem. i don't want to use the adb setup thing becuase its a virus so yeah.
kiwigi said:
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Click to expand...
Click to collapse
THANK YOU!!! From a fellow Kiwi. I followed a tutorial for my Nokia G20 and they left this part out! Faaaaar out. You're my hero
Guys I am getting desperate here. I hate crying in the forums for help, but that's why they are here. I am sorry but here I am to whine about the problem that I am facing whole day.
I tried with OP, Samsung, Xiaomi, Google USB drivers. Nothing so far works. I tried many options but I can' make the Windows to recognize the phone after getting into BL. Windows 11, tried all my USB ports (I have only 3), no success. Pushed even Googles driver files manualy from the Device manager and I chose the BL option of the driver, that didn't work, then I tried the rest of the 3 options of the driver, that didn't work either.
I followed this metod as well - https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
The only thing that has left as an option is the lack of USB 2.0. If this is the problem I am gonna throw up...
Any help or suggestion would be highly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mrpeev said:
Guys I am getting desperate here. I hate crying in the forums for help, but that's why they are here. I am sorry but here I am to whine about the problem that I am facing whole day.
I tried with OP, Samsung, Xiaomi, Google USB drivers. Nothing so far works. I tried many options but I can' make the Windows to recognize the phone after getting into BL. Windows 11, tried all my USB ports (I have only 3), no success. Pushed even Googles driver files manualy from the Device manager and I chose the BL option of the driver, that didn't work, then I tried the rest of the 3 options of the driver, that didn't work either.
I followed this metod as well - https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
The only thing that has left as an option is the lack of USB 2.0. If this is the problem I am gonna throw up...
Any help or suggestion would be highly appreciated.
View attachment 5603673
Click to expand...
Click to collapse
i could be way off base here but your in fastboot so the CMD should be "fastboot devices". Your screen looks no dif then mine
Are the drivers installed correctly, ie with admin rights, and if so, is the help in the link that works, but requires more time and effort. With that guide, I will install the win 11 and win 10 drivers myself.
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
hammered58 said:
i could be way off base here but your in fastboot so the CMD should be "fastboot devices". Your screen looks no dif then mine
Click to expand...
Click to collapse
that was correct, now the fastboot finds the device while in BL, thank you!