So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Syflox said:
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Click to expand...
Click to collapse
The GS3 does not have fastboot. All flashing is done through odin.
ddggttff3 said:
The GS3 does not have fastboot. All flashing is done through odin.
Click to expand...
Click to collapse
Thanks! Also, how do I update ClockworkMod recovery to the newest one? I've used ODIN before but am not sure if it is capable of flashing .img files.
EDIT: Nevermind, I just downloaded ROM Manager and used that to flash 6.0.2.3
I'm trying to flash TWRP on a nexus 5. Bootloader is already unlocked. USB debugging is enabled. The command "adb reboot-bootloader" works when the device is on. While in fastboot it does not say USB is connected and doesn't show up on adb devices. (My laptop is currently running Elementary OS)
As soon as you're in bootloader mode you have to use 'fastboot flash recovery recovery.img' adb is used when the device is powered on and in debugging mode - but it's not the right command for flashing [emoji14]
experience7 said:
As soon as you're in bootloader mode you have to use 'fastboot flash recovery recovery.img' adb is used when the device is powered on and in debugging mode - but it's not the right command for flashing [emoji14]
Click to expand...
Click to collapse
Yeah I know HOW to flash a recovery I already tried that exact command. Thanks for the suggestion though. The problem is that it just doesn't know its there.
Sent from my HTC One using XDA Free mobile app
While in bootloader mode (not recovery!) connect your phone and try "fastboot devices". What does it show? Post a screenshot of your command prompt.
Sorry its my friend's phone so I don't have it with me. I will have to get back to you on that
1. USB Debugging ONLY applies to ADB while booted into Android, NOT the bootloader or recovery
2. ADB is only used within Android (with USB Debugging enabled) and recovery, NOT the bootloader
3. Fastboot is whats used while in the bootloader, not ADB (use fastboot devices, not adb devices)
4. Some people find you may need to use 'sudo' for fastboot commands
Hi
I was given a Xiaomi Mi4 with a broken screen by a friend, and I want to use it as part of a robotics project. (I need this phone in particular because it features hardware scheduled shutdown & restart).
I can boot in recovery (mi recovery 2.01) & fastboot. 'fastboot devices' lists a device but 'adb devices' does not.
Is there a way I can remotely install something like JuiceSSH? Or otherwise remotely control it?
I think I need USB Debugging enabled to do this?
any help appreciated.
I can get into the internal storage, and I can boot into recovery and select 'install update.zip', so it should be possible to install a different rom on it.
Is there a rom for the mi4 that has USB Debugging turned on? Or has Vysor or something similar installed by default?
edzillion said:
I can get into the internal storage, and I can boot into recovery and select 'install update.zip', so it should be possible to install a different rom on it.
Is there a rom for the mi4 that has USB Debugging turned on? Or has Vysor or something similar installed by default?
Click to expand...
Click to collapse
some custom ROMs come with USB debugging enabled .
I can't try for you cuz I don't have this phone model .
But I think you can turn on adb via recovery mode .
Are you using custom recovery.
[email protected] said:
some custom ROMs come with USB debugging enabled .
I can't try for you cuz I don't have this phone model .
But I think you can turn on adb via recovery mode .
Are you using custom recovery.
Click to expand...
Click to collapse
It currently has Mi Recovery 2.0.1
edzillion said:
It currently has Mi Recovery 2.0.1
Click to expand...
Click to collapse
Does this stock recovery have adb shell? If not you'll need twrp/cwm
Hi, I am trying to unlock my bootloader,
I got adb to work, my phone shows up when I run the adb device command and the reboot to bootloader, is also working but when I run fastboot devices nothing happens.
In device manager my phone shows up as android, for some reason I seem to be missing fastboot drivers.
I install the minimal adb & fastboot package.
Any help would be appreciated, thanks.
If you have already installed flashtool, try installing the fastboot driver in the flashtool folder，It seems to need to disable mandatory signature verification in order to install successfully. And have you turned on the OEM unlock button in Developer mode?
HoiFung said:
If you have already installed flashtool, try installing the fastboot driver in the flashtool folder，It seems to need to disable mandatory signature verification in order to install successfully. And have you turned on the OEM unlock button in Developer mode?
Click to expand...
Click to collapse
Yeah OEM unlock is turned on, will try to install flash tool.
Noctis Lucis Caelum said:
Yeah OEM unlock is turned on, will try to install flash tool.
Click to expand...
Click to collapse
After the installation is complete, the flashtool folder will have a driver folder and try to install it.
OK sorted, thanks @HoiFung.
Noctis Lucis Caelum said:
Yeah OEM unlock is turned on, .......
Click to expand...
Click to collapse
Don't forget to tick USB-Debugging
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
I had the same issue with my op9 unlocking bl.
ADB and Fastboot 29.0.2.zip | by evildog1 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use these and open your command window from this . Makes a shortcut on your desktop. I did and unlocking bl worked perfectly.
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
Double post
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Make sure you enable oem unlocking in dev options first and reboot.Reboot to bootloader,issue command $fastboot flashing unlock..
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Are you a carrier variant or global unlocked 9/9pro?
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
cass89 said:
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
Click to expand...
Click to collapse
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
mattie_49 said:
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
Click to expand...
Click to collapse
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
cass89 said:
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Try one more thing. Install these and creat shortcut on desktop and try opening cmd in this. We gonna get you unlocked.
One last thing. You have also went into developer options and tic'ed "USB debugging on then ok on device when it asks if you wanna allow phone to communicate.
tried that, still nothing. usb debugging is on.
all I need is a working driver, everything else should be good..
one thing which i'm not sure if it's an issue, I'm using an old usb c to usb 2 cable, I'm not using the cable that came with the phone because my computer doesn't have usb c ports.. but adb and mass storage/file transfers work with no issue
Hate to say it, but it still COULD be your old USB cord even with file transfer and adb functionality preserved. I had a cord that did do file transfer but not adb. You should try another cord...
Here's another driver source to download:
Universal ADB Drivers
2 new cords, and also tried multiple driver downloads, but still nothing... i was really hoping to root this phone and it seemed so easy for everyone else, thats why i bought it.. but I guess I'm stuck with a locked bootloader...
I could try factory resetting windows or the phone, but would that even make a difference?
..rereading the root guide, at the beginning it says "if you're on global and want root, flash the eu boot.img" but I'm not sure if he means do that first or use that for the guide.. I'm assuming I need the bootloader unlocked in order to flash it first, but maybe not..
..also should I have just commented in the root guide post, instead of making a new post?..
I'm sure you've tried another usb port on your computer.
Last thing to try: another PC.
Shouldn't come to that, but that's where you look to be.
Got it!! Someone posted about the op6 not working either and the fix is turning off windows driver signature, not sure why but that worked for me..
Thanks, now on to root lol
I just had some serious fastboot driver issues when setting up my oneplus. Not sure if this helps but can you at least find the driver folder that was installed on your c:drive when you initially installed the drivers. Then check your device manager when your phone is in fastboot and update the device (usually under portable devices) through that path?
If you get a tampering /corrupt error when you do this you can disable driver signing in windows which is what worked for me thanks to this saint.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Edit: you solved it while I was responding....I had the same issue..congrats...I know the feeling!