Hello,
My nexus 5 is rooted, rom custom (great terminus) and kernel code blue.
I have recently to try change my kernel for Stock Kernel [L-preview r3] [LPX13D] : I take the kernel stock on this page : http://forum.xda-developers.com/google-nexus-5/general/kernel-t2518816
I have just reboot my device on recovery (TWRP) and flash the kernel and reeboot. No wipe. Nothing else. But my phone doesn't start : Now after bootanimation, I have "update of app 14 on 95.." and at the end of this loading
phone reboot and "update of app" again.. endlessly.
So I try reinstall a factory ROM, bootloader, radio, kernel. All. The problem is my phone is not found on adb command :
HOWEVER USB debugging is activated.
On windows, the device is recognized on device Manager "android device" "android bootloader interface".
I have the latest version of fastboot tools of android sdk installed.
My phone is boot on bootloader and plug in USB
The following command :
adb devices
list of devices attached
adb usb
error device not found
I also tried on my macbook pro. Same problem, all seem work fine but device not found.
Have you an idea to force the recognition of the device ?
If you're in the bootloader its fastboot not adb
Fastboot devices
Sent from my Nexus 5 using Tapatalk
Yes, was that^^ Thanks !
Related
Ok, here's what's up. I have updated my ME301T from 4.1.1 to 4.2.1 on the 10.6.1.15.4 build number, and successfully unlocked my bootloader using the TF300T apk file, but when I try to use fastboot to load TWRP on as my recovery, my computer cannot find the tablet to send the commands to. I have tried two different computers with two different operating systems, used the naked drivers, and even forced a bootloader reboot from adb but still cannot get the tablet to accept fastboot commands. What am I doing wrong and is there another workaround for getting TWRP 2.5.0.0 loaded on my tablet?
Bump. Still not getting commands through to my fastboot.
Me too!
I'm in the same situation. Can't seem to get the fastboot usb drivers to work with fastboot commands. Fastboot devices command doesn't display any devices.
Current setup on my me301t:
- bootloader unlocked
- android version 4.2.1
- build # 0.6.1.25
- rooted
I would like to use the fastboot to install twrp or cwm so I can install a custom rom. GooManager won't install custom recovery, says no recoveries are available for my device. Rom Manager says it flashes the CWM recovery but doesn't work. If I take the OTA update to go to build 0.6.1.31 I lose root and am unable to restore root. I then have to reflash to .25 by placing the ASUS stock firmware on my micro-SD card and rebooting into RCK (recovery) using vol-down while powering up.
fastboot
First of all You should to be shure that tablet connected directly to the usb port without any usb-hub. Sometimes usb on front panel of PC may cause same problem, so use one on the rear side. If You use windows os check device manager. You should see something like asus fasboot inteface or bootloader interface, if is not there - reinstall drivers.
P.S.: I hope my English is not too terrible.
The device shows up as "bootloader interface" when in fastboot bootloader. The command adb devices works fine. fastboot devices shows nothing. this is obviously a driver issue, otherwise fastboot devices would show the device same as adb devices. I've tried both on ubuntu and windows with no results.
---------- Post added at 10:05 PM ---------- Previous post was at 09:46 PM ----------
darktowermage said:
The device shows up as "bootloader interface" when in fastboot bootloader. The command adb devices works fine. fastboot devices shows nothing. this is obviously a driver issue, otherwise fastboot devices would show the device same as adb devices. I've tried both on ubuntu and windows with no results.
Click to expand...
Click to collapse
I finally got fastboot to show the device on Ubuntu 12.04. Here's how:
- install the adb fastboot ppa on ubuntu following the instructions at webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html. Can't post the full link because of my XDA perms.
- run fastboot as root like so:
sudo fastboot devices
Didn't initially run it as root. That was the key for me. Still not sure why Windoze didn't work, but that's typical.
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
J0hncramer said:
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
Click to expand...
Click to collapse
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
LokifiedMee said:
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
Click to expand...
Click to collapse
I just tried fastboot devices in powershell while the phone is connected via USB in fastboot mode and nothing was listed
Edit: i was able to get fastboot to work, I had to do the following steps i found on stack exchange to get my device to show up properly in device manager:
https://stackoverflow.com/questions/8588595/android-fastboot-devices-not-returning-device
Open device manager
Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
Update driver
Browse my computer for driver software
Let me pick from a list of devices, select List All Devices
Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
Choose "Android Bootloader Interface"
Click "yes" when it says that driver might not be compatible
Click to expand...
Click to collapse
With fastboot working and issues in device manager solved I was able to get TWRP loaded to my phone via fastboot and change my boot slot to get back into the phone
Hi,
i'm facing the problem that my phone only starts in "FastBoot Mode" at least i guess that's the mode.
OnePlus 6 with root.
It happened after i rebooted after installing an OTA Update and installing a Magisk Manager Update.
I used the method described here. The last few times it worked perfectly.
But now the only thing that happens when i try to boot the phone is a screen that says
FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - d8a34971
SECURE BOOT - yes
DEVICE STATE - unlocked
with the volume button i can select "START, Restart bootloader, Recovery Mode and Power off"
but nothing happens when i select e.g. Recovery Mode, or simply START.
The phone shows the boot logo for a second, then I'm back at the screen with "FastBoot Mode"
I installed the USB-drivers for the device and can find it with my PC when i type "fastboot devices" in the command prompt.
But that's pretty much all. I don't know how to continue.
I would be very glad if i could keep my data, is there a way to save my phone and if not how do i install the normal OS again?
I really hope someone can help me here.
Edit:
When I type "adb devices" it says "List of devices attached" but there is no entry.
USB-Debugging is on, since the Root-process i didn't touch the developer options
So should be the USB mode for file transfer (MTP)
I'm not sure if i checked the "always allow from this computer" setting
So following this guide the only thing i can't do is checking the prompt for USB-debugging since i can't boot the OS.
Is there anoter way to get a adb connection?
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
For everyone that can't connect to the device via ADB but fastboot, this does the trick.
Thank you guys!
Hello,
I am trying to install CM on my old Android tablet - Lenovo TAB 2 A7-30DC, Android version : 5.0.1 , Kernel version: 3.10.54 . I have downloaded the zip cm-12.1-Tab2A710F-20210102-1707.zip , but I cant install it . I have root on the tablet, installed flashify, twrp, but I cannot unlock the bootloader - I dont have OEM unlocking as an option in Developer Mode menu. Please let me know what should be my next steps. Thank you.
Download "ADB fastboot tools"
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to Computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click Now type the command in your command window:
-----------------------
adb devices
------------------------
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloader:
-------------------------------------
adb reboot bootloader
-------------------------------------
Once your phone reboot into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers are installed properly.
-------------------------------------
fastboot devices
-------------------------------------
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
(Remember that this step will wipe EVERYTHING off the phone)
-------------------------------------
fastboot oem unlock
-------------------------------------
After the above command has finished executing, run the following:
---------------------------
fastboot reboot
---------------------------
The phone will reboot. Wait until the phone has fully booted up into android, and enjoy.
The link you posted is the only link I found on the internet that is not dead. It is impossible to find some link for custom rom and twrp that works. I have the same tablet. I unlocked the bootloader and that’s all I managed to do.
petko.dimitrov said:
Hello,
I am trying to install CM on my old Android tablet - Lenovo TAB 2 A7-30DC, Android version : 5.0.1 , Kernel version: 3.10.54 . I have downloaded the zip cm-12.1-Tab2A710F-20210102-1707.zip , but I cant install it . I have root on the tablet, installed flashify, twrp, but I cannot unlock the bootloader - I dont have OEM unlocking as an option in Developer Mode menu. Please let me know what should be my next steps. Thank you.
Click to expand...
Click to collapse
I have this problem too. And I have another problem my device recognizes my tab when I type adb devices but it doesn't recognize it in fastboot mode. I have installed all drivers I don't know what else to do.