I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard
Related
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
I just purchased by OnePlus 3T and in the process of trying to unlock the bootloader. I have ADB while in stock oxygen os 4.0.2 but when entering fastboot to unlock the bootloader I no longer have access to the device. As per some searching I switched to a USB 2.0 port and still no luck. In device manager it shows my phone under "Other devices -> Android." I'm pretty sure i'm missing a driver for ADB, but can't figure out what is missing. Any help would be greatly appreciated!
http://www.androidusbdrivers.com/oneplus-3t-usb-drivers
Install, restart.
Specifically in folder you have adb files, hold Shift+Right Click, open command prompt.
fastboot devices to confirm connection
fastboot oem unlock to get started.
Search for the one plus 3t toolkit. It has the original one plus drivers.
Then install minimal adb and fastboot.
And it should work. If it doesn't, try on another pc.
Well it's been a while since my last new phone totally forgot to install USB drivers all good to go, newb mistake thank you!
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Jo_Jo_2000 said:
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Click to expand...
Click to collapse
After having my phone since Monday, I just now noticed that emulated drive when I had to nuke it earlier today, lol.
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Hii. you go to device manager. find your phone in unknown device. Update the driver using i have a disk option. Then try again. it will work.
Disable windows 10 Driver signature and install Fastboot USB drivers again.
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Sathelp said:
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Click to expand...
Click to collapse
I'm able to detect device in "ADB Devices" when phone is booted into android OS, even the MiFlashTool also detects the device when phone in booted into OS.
But after i type ADB reboot bootloader, phone restarts into FASTBOOT, i can see RED "FASTBOOT" logo in phone screen but it doesn't get detected.
How come phone gets detected in ADB when Phone is booted into OS MIUI13 but not in FASTBOOT.
I'm on windows 11 .
I changed the cable also with a new Xiaomi cable purchased recently, still the same result.
You can never see a result to detect mi 11 ultra through ADB devices. Rest assured your device is already detected and ready to use. Even though can not see device address.
I had the same case. Make sure all the necessary drivers are installed.
At first mine was also not detected in fastboot. When I first ran MI Flash Tool, it automatically installed some drivers. And I also manually installed USB driver of MI 11 Ultra.
After that MI Flash detected my phone in fastboot.
A small suggestion from me: Use "Xiaomi ADB Fastboot Tools" for flashing. MI Flash was giving me, timeout error and my device got into fastboot loop. After flashing with "Xiaomi ADB Fastboot Tools" all went well.
hello, I also had this problem and to solve it I used the driver of Mi unlock which is at the level of the parameters and launch it in fastboot then connect it to the pc and the drivers must be installed
I had a similar problem with my Mi 10. Found via ADB but wouldn't show in fastboot. Tge way I solved it was to boot into TWRP recovery (assuming you have it) and then go to their reboot menu and choose fastboot from there. It will then put you into their version of fastboot and your computer should recognise the phone in fastboot mode.
I hope this helps
jaggub4u said:
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Click to expand...
Click to collapse
Adb and Fastboot is not the same thing!
If you're phone is detected in ADB, it means you have install the Adb Driver ( which more than probably is Google Driver or Xiaomi driver for ADB ).
In order for you phone to be in Fastboot do the following:
- Reboot to Fastboot and connect your phone to PC with original Xiaomi cable from the box
- Go to Device Manager > Other Devices > Android Device ( you will see a yellow sign, which means you don't have the Fastboot Driver )
- Download XiaomiMi11 Ultra Bootloader Driver.zip, unzip it
- Click on the Android Device with yellow sign > Update driver > Browse my computer for drivers > Select the Xiaomi Bootloader Folder
It will install the driver.
From here you're good to go!