I am having issues w/ fastboot mode. I've installed the appropriate drivers for the Dell Streak, and when in fastboot mode, try to flash stock recovery and it just sits at waiting for device. I checked device manager and it is showing android adb device. It used to work and was able to initially flash clockwork mod recovery. Any one know what could be causing this?
try updating the driver not sure if its supposed to be android composite device.
Sent from my Dell Streak 7
Related
my device is always booting to fastboot and shows me only a blank screen
i was running android 2.3
i tried to install clockworkmod recovery and i lost my all recovery
then i tried to install twrp recovery trough adb and after that my device went to fastboot and now my device is always at fastboot
i can pull the battery out because its like that like iphone
fastboot commands are working and my android is identified by pc
can you please help me to get my device back to working condition
thanks
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!
Hi!
I'm still on my way ro root my Samsung Tab SM-T725, after upgrading to Android 11. Before Android 9 was on the device, succesfully rooted via Magisk. Updating and keeping the root status didn't work properly, the flashing process in Odin failed. Therfefore I had to flash the latest stock recovery, successfully. So now I have Android 11 on my device but no root. The bootloader is open and USB debugging enabled.
I tried the method described here. But the flashing in Odin failed again. So now I try to follow the instructions on the Magisk website. If I get everything right a processed recovery.img has to be flashed via ADB/Fastboot. That's new to me and I have questions.
- Is fastboot and download/recovery mode the same? Booting to the recovery and following "reboot to bootloader" leads to the turquois "Downloading" window. The same occurs when prompting "ADB reboot fastboot" e. g. Again the mentioned Downloading window shows up, nothing (special) with fastboot. Is that correct?
- Will therefore all fastboot commands not work? And only ADB is possible on my tablet? Is that common for Samsung devices?
- Can the flashing of the patched recovery.img (for Magisk) be done with ADB as well? Instructions always mention fastboot.
- My device doesn't show up in ADB when being in recovery mode. In normal mode it is listed when entering "ADB devices". Trying again in recovery mode the list stays empty - and all other commands have no effect. Current Samsung and Google USB drivers are installed. How could that be solved? Without ADB (perhaps fastbood) running in download mode I shouldn't be able to flash (and root the device) as planned.
I hope I described everything properly. I'm not that Android expert - but successfully managed to root a couple of devices over the years.
Samsung devices dont know of Fastboot mode. But you can run them in either Recovery or Odin / Download mode or Normal mode.
Running Samsung devices in Download mode you can flash ROM or update system in the Android device. When the Samsung device has entered Download mode, the device will boot from external sources. You can also make the stock ROM replaced in Download mode.
ADB mode is the Normal mode.
In Recovery mode ADB - with some exceptions - isn't working
Because your device is a Samsung one the Google USB drivers are senseless. Remove them to avoid conflicts.
Thanks for the quick and helpful response!
That makes clear why the tablet didn't show up in ADB. And that all rooting efforts for Samsung devices via that way should be obsolete. Strange enough that Magisk doesn't mention this on their instruction site.
So I'll have to try on with flashing a patched AP via Odin - and hope for a solution for my fail-problem.