[Q] ADB sideload & fastboot not working

Search This thread
By:
Advanced…
O

oliverm91

Member
Sep 20, 2012
38
0
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:

  1. adb reboot bootloader
  2. fastboot flash bootloader bootloader-mako-makoz30d.img
  3. fastboot reboot-bootloader
  4. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
  5. fastboot reboot-bootloader
  6. fastboot flash system system.img
  7. fastboot flash boot boot.img
  8. fastboot format cache
  9. fastboot reboot

Then installed CWM by:

  1. adb reboot bootloader
  2. fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
  3. 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.
 
Last edited:
taodan

taodan

Senior Member
Nov 27, 2011
978
232
LineageOS
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:

  1. adb reboot bootloader
  2. fastboot flash bootloader bootloader-mako-makoz30d.img
  3. fastboot reboot-bootloader
  4. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
  5. fastboot reboot-bootloader
  6. fastboot flash system system.img
  7. fastboot flash boot boot.img
  8. fastboot format cache
  9. fastboot reboot

Then installed CWM by:

  1. adb reboot bootloader
  2. fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
  3. 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.
 
  • Like
Reactions: oliverm91
audit13

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,911
5,052
Toronto
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?
 
O

oliverm91

Member
Sep 20, 2012
38
0
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.
 
audit13

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,911
5,052
Toronto
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.
 
K

karthi89

Senior Member
Aug 9, 2013
330
166
Revoke USB debugging authorizations for all the devices from the developer options and try again..

Sent from my Nexus 4 using Tapatalk
 
jd1639

jd1639

Inactive Recognized Contributor
Sep 21, 2012
16,833
5,404
Minnesota
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
 
O

oliverm91

Member
Sep 20, 2012
38
0
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
 
Last edited:
You must log in or register to reply here.

Similar threads

C
[Q] Fastboot Recovery/Remotely enable USB debugging
Replies
35
Views
314K
Talysdaddy
Talysdaddy
wzyboy
[SOLVED] "fastboot boot recovery.img" not working in Android 4.3
Replies
12
Views
150K
Longturd
Longturd
handman29
Need adb side load " device not found" fix
Replies
67
Views
169K
M
mtnorbeach
hashworks
[Q] ADB error: device unauthorized and device offline
Replies
30
Views
126K
BenG7
BenG7
S
[Q] - fastboot erase userdata
Replies
13
Views
118K
Azazel13878349
Azazel13878349

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1
    taodan
    taodan
    oliverm91 said:
    Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:

    1. adb reboot bootloader
    2. fastboot flash bootloader bootloader-mako-makoz30d.img
    3. fastboot reboot-bootloader
    4. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
    5. fastboot reboot-bootloader
    6. fastboot flash system system.img
    7. fastboot flash boot boot.img
    8. fastboot format cache
    9. fastboot reboot

    Then installed CWM by:

    1. adb reboot bootloader
    2. fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
    3. 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.
    View

New posts