I unlocked my N7 3G with WugFresh tool and then I rooted and installed a custom recovery.
Everytime I power on my device by pressing Vol DOWN + POWER ON my device is in fastboot mode. But If I try to run adb devices, no devices are found. While if I launch recovery and run the same command, my device is listed.
So I don't understand why I can't communicate with my device if I power on it in fastboot mode, but only if launch it in recovery mode or I power on it with USB debug on.
So I couldn't flash my custom recovery with this command:
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
but I had to use WugFresh's tool to flash a custom recovery, in fact when this program launch command to power on device in fastboot mode, it works! I don't understand why I can't do it manually but only throught this software
Try using the command : fastboot devices
Sent from my Nexus 7 using xda premium
KidCarter93 said:
Try using the command : fastboot devices
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. Now it works. I'm too stupid! :silly:
Adb has no access in bootloader for future reference, only in os and recovery
Sent from my HTC Vision using Tapatalk 2
ADB recognises device while normally running, but not in fastboot. i tried installing the same driver on fastboot, but it still doesnt recognize it as ADB connection.
Adb commands aren't meant to work in fastboot. Only fastboot commands work in fastboot.
Sent using xda-developers app
thank you. ive vigured that i can use ADB in recovery, so thats good.
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
D801
TL;DR: Phone will only boot into download mode, however computer won't recognize my phone.
I installed all the drivers, have multiple versions of flash tool, even tried sideloading via ADB but device isn't recognized. How do I unbrick my phone?
Download and install the Minimal ADB and Fastboot tool v1.1.3...
http://forum.xda-developers.com/showthread.php?t=2317790
While in Download mode and w/ USB Debugging enabled, double click the Minimal ADB and Fastboot shortcut, then at the Minimal ADB and Fastboot> prompt type... adb devices
If your phone isn't recognized by ADB, then you don't have the correct drivers installed.
Windows 7...
Seems I can have either ADB drivers installed for when the phone is booted or when the phone is in fastboot mode, but not both. I have fastboot ADB drivers installed now as I need them the most; it's easy to reboot the phone into bootloader. Am I stuck with one or the other? If I install the ADB driver when the phone is booted I lose the fastboot drivers. TIA.
I don't think you lose the drivers... you just can't see the device using ADB when in fastboot mode and vice versa.
vanish0104 said:
I don't think you lose the drivers... you just can't see the device using ADB when in fastboot mode and vice versa.
Click to expand...
Click to collapse
It's more like I have to install from a different driver package for booted vs fastboot condition. Both work, I just have to redo the driver install depending on the state of the phone. Seems odd.
Hey, I've been having a lot of trouble getting fastboot to work properly. I can get adb commands to work with my phone on but fastboot commands in fastboot mode don't work at all. I've been at this for about an hour.
I sort of get what you mean when you're saying you need to install separate drivers each time you want to switch between having adb and fastboot work. How exactly did you install "fastboot" drivers and how would I go around doing that? Help would really be appreciated!