How do I use ADB Sideload?

Search This thread

sevenpioverthree

Senior Member
Mar 7, 2013
368
131
A couple of days ago, I nearly bricked my phone to no return. In the process of this I remembered reading about ADB sideload. So I went ahead and tried to use the function to re-flash my ROM in TWRP. However, when I connected my phone my computer didn't recognize it and the "adb sideload 'filename'" command wasn't working it just kept telling me "device not connected". Is there a way I can set up my computer/phone for ADB sideload in case this ever happens to me again?
 
  • Like
Reactions: mcfarlan

CNexus

Senior Member
May 17, 2012
9,009
13,994
~/android
Did you have the drivers installed? Go to Control Panel > Hardware and Sound > Devices and Printers and make sure your phone shows up

You can also run this:
Code:
adb devices

To see connected devices
 
  • Like
Reactions: sevenpioverthree

sevenpioverthree

Senior Member
Mar 7, 2013
368
131
Did you have the drivers installed? Go to Control Panel > Hardware and Sound > Devices and Printers and make sure your phone shows up

You can also run this:
Code:
adb devices

To see connected devices

Yeah I have the drivers installed and I've always been able to use ADB just fine when my phone is up and booted but when I entered ADB sideload in TWRP it couldn't detect my device, adb devices showed no devices.
 

sevenpioverthree

Senior Member
Mar 7, 2013
368
131
Adb won't detect devices that are in recovery, it has to be booted up because it checks whether debugging is enabled too

I'm not saying you're wrong, and I thought the same was true too. But if that's the case why does a function like "ADB sideload" exist on TWRP at all? I just don't get it. I followed the instructions on their website to no avail. There must be some way to get my phone recognized in recovery
 

CNexus

Senior Member
May 17, 2012
9,009
13,994
~/android
WAIT, no ignore that post lol
The evo lte can be rebooted into recovery through adb even when it's dead.....

So if the hardware supports it then it does work.....

To your question....that's strange, maybe your phone just isn't compatible with it for some reason
I know some peoples phones won't mount the sdcard through recovery, ever
 
Last edited:
  • Like
Reactions: sevenpioverthree

sevenpioverthree

Senior Member
Mar 7, 2013
368
131
WAIT, no ignore that post lol
The evo lte can be rebooted into recovery through adb even when it's dead.....

So if the hardware supports it then it does work.....

To your question....that's strange, maybe your phone just isn't compatible with it for some reason
I know some peoples phones won't mount the sdcard through recovery, ever

Forgive me if this is a dumb question but what if I reinstall my drivers and connect my phone while it's in recovery?
 

sevenpioverthree

Senior Member
Mar 7, 2013
368
131
Reinstall the drivers and make sure that your adb is updated so u have the side load function.

Sent from my SPH-L900 using xda premium

My ADB is completely up to date and has a sideload function. I have figured it out though.

Basically I edited the "android_winusb.inf" file under "C:\android-sdk-windows\extras\google\usb_driver". I put my device into recovery and then went into device manager on my computer. I right clicked my phone which had a yellow exclamation mark and was named "Samsung_SPH_L710" (or something close to that) and went into properties, then the details tab and then chose "hardware ID". There were 2 lines there. The lines were:

Code:
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01

I took those lines and pasted them under:

[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx

I put the lines after the last line under the "Google Nexus (generic)". If you have a 64-bit computer then instead of [Google.NTx86] you put them under [Google.NTamd64]. The lines still go after the last line of "Google Nexus (generic)". The lines then looked like this:

Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE1
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE3
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE5
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
[COLOR="Red"]%SingleAdbInterface% 	    = USB_Install, USB\VID_18D1&PID_D001&MI_01
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_D001&REV_0228&MI_01[/COLOR]

The red lines are the new ones I inputted. I saved the file, uninstalled my phone under device manager, disconnected it, and while it was still in recovery, reconnected it and installed the driver. I had to point the installer to the "C:\android-sdk-windows\extras\google\usb_driver" folder. My computer then prompted me to reboot and upon rebooting it asked me to install the driver but this time I did not need to point it to any folder, and voila! I can now use adb in recovery. If you are using this method, then after you are done type in:

Code:
adb devices

If your device shows up, then you have successfully completed this!

I probably explained this is a really god awful way. This might be common knowledge among you guys but if it isn't then maybe one of you can re-write this in a more comprehensive way since ADB sideload could come in handy.

EDIT: I want to add that I did not figure this out on my own. I got it from this thread: http://forum.xda-developers.com/showpost.php?p=37993317&postcount=22. The only thing is I couldn't copy those values directly I had to find them myself under "hardware id"
 
Last edited:

sevenpioverthree

Senior Member
Mar 7, 2013
368
131
Nice! :thumbup:
Thanks for the fix as well

No problem! I feel pretty awesome answering my own question. Is this worth making a guide for? I'm thinking it could come in handy if someone bricked their phone and wanted to use ADB sideload

By the way did you confirm this for yourself?
 

galearned

Senior Member
Apr 6, 2012
452
138
Gainesville
No problem! I feel pretty awesome answering my own question. Is this worth making a guide for? I'm thinking it could come in handy if someone bricked their phone and wanted to use ADB sideload

By the way did you confirm this for yourself?

Afternoon: I have a sideload usage question.

I have tried ADB side load numerous times from various folders and nothing seems to work for me.
Is there an actual how to for ADB side load?
My adb works just fine.
The note on the TRWP utility screen says "usage: adb sideload filename.zip
When I make the side load selection in TWRP, and issue adb devices on PC, I receive "XXXXXXXserial sideload"

Can this be executed on the PC using path statements?
ex:
adb sideload \folderA\folderB\name_of_File.zip

The file can be any installation that uses a zipped manifest file such as ROM or APK.zip files?
I receive a listing of ADB help when I use the above syntax.
 

bschuster

Senior Member
Nov 18, 2010
87
19
Chicago
Just force the ADB Drivers for your device

If you have the exclamation mark beside the device when within recovery, just update the driver in device manager and manually locate and install the ADB driver for your device, it will give you a message that this may not be for your device blah blah blah, just say continue...it will install and your device will be detected.


My ADB is completely up to date and has a sideload function. I have figured it out though.

Basically I edited the "android_winusb.inf" file under "C:\android-sdk-windows\extras\google\usb_driver". I put my device into recovery and then went into device manager on my computer. I right clicked my phone which had a yellow exclamation mark and was named "Samsung_SPH_L710" (or something close to that) and went into properties, then the details tab and then chose "hardware ID". There were 2 lines there. The lines were:

Code:
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01

I took those lines and pasted them under:

[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx

I put the lines after the last line under the "Google Nexus (generic)". If you have a 64-bit computer then instead of [Google.NTx86] you put them under [Google.NTamd64]. The lines still go after the last line of "Google Nexus (generic)". The lines then looked like this:

Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE1
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE3
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE5
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
[COLOR="Red"]%SingleAdbInterface% 	    = USB_Install, USB\VID_18D1&PID_D001&MI_01
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_D001&REV_0228&MI_01[/COLOR]

The red lines are the new ones I inputted. I saved the file, uninstalled my phone under device manager, disconnected it, and while it was still in recovery, reconnected it and installed the driver. I had to point the installer to the "C:\android-sdk-windows\extras\google\usb_driver" folder. My computer then prompted me to reboot and upon rebooting it asked me to install the driver but this time I did not need to point it to any folder, and voila! I can now use adb in recovery. If you are using this method, then after you are done.

Code:
adb devices

If your device shows up, then you have successfully completed this!

I probably explained this is a really god awful way. This might be common knowledge among you guys but if it isn't then maybe one of you can re-write this in a more comprehensive way since ADB sideload could come in handy.

EDIT: I want to add that I did not figure this out on my own. I got it from this thread: http://forum.xda-developers.com/showpost.php?p=37993317&postcount=22. The only thing is I couldn't copy those values directly I had to find them myself under "hardware id"
 

Yharooer

Member
May 22, 2009
33
2
Adb won't detect devices that are in recovery, it has to be booted up because it checks whether debugging is enabled too

Forgive me if this has been pointed out, and I realise this topic is quite old but adb will detect devices which are in the 'sideload'ing state in recovery.
 

gnome9er

Member
Oct 16, 2010
37
1
40
langley
twitter.com
stumbled onto this thread, thought i would respond: just mount data, then try adb..

C:\adb>adb devices
List of devices attached
FA2BXW4000XX recovery

thats what i get while browsing for a zip in TWRP (no sideload command)

when i run sideload adb doesnt recognize. :eek:
 

Perry2547

Senior Member
Sep 25, 2013
250
27
What these instructors fail to realize is that most of us haven't been using shell commands since we were 11 years old.
I'm not even sure how to start ADB sideload. I just downloaded a whopping 389 mb package for the entire sdk when all I needed was adb sideload.
(but I couldn't find any place to download just the adb sideload).

Now when I double click on adb, the black screen comes up for two seconds and I see a whole bunch of lines scrolling down and then the black screen disappears.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Reinstall the drivers and make sure that your adb is updated so u have the side load function.

    Sent from my SPH-L900 using xda premium

    My ADB is completely up to date and has a sideload function. I have figured it out though.

    Basically I edited the "android_winusb.inf" file under "C:\android-sdk-windows\extras\google\usb_driver". I put my device into recovery and then went into device manager on my computer. I right clicked my phone which had a yellow exclamation mark and was named "Samsung_SPH_L710" (or something close to that) and went into properties, then the details tab and then chose "hardware ID". There were 2 lines there. The lines were:

    Code:
    USB\VID_18D1&PID_D001&MI_01
    USB\VID_18D1&PID_D001&REV_0228&MI_01

    I took those lines and pasted them under:

    [Google.NTx86]
    xxxxxx
    ;Google Nexus (generic)
    xxxx

    I put the lines after the last line under the "Google Nexus (generic)". If you have a 64-bit computer then instead of [Google.NTx86] you put them under [Google.NTamd64]. The lines still go after the last line of "Google Nexus (generic)". The lines then looked like this:

    Code:
    ;Google Nexus (generic)
    %SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
    %SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE1
    %CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2
    %CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
    %SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE3
    %CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
    %SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4EE5
    %CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
    [COLOR="Red"]%SingleAdbInterface% 	    = USB_Install, USB\VID_18D1&PID_D001&MI_01
    %CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_D001&REV_0228&MI_01[/COLOR]

    The red lines are the new ones I inputted. I saved the file, uninstalled my phone under device manager, disconnected it, and while it was still in recovery, reconnected it and installed the driver. I had to point the installer to the "C:\android-sdk-windows\extras\google\usb_driver" folder. My computer then prompted me to reboot and upon rebooting it asked me to install the driver but this time I did not need to point it to any folder, and voila! I can now use adb in recovery. If you are using this method, then after you are done type in:

    Code:
    adb devices

    If your device shows up, then you have successfully completed this!

    I probably explained this is a really god awful way. This might be common knowledge among you guys but if it isn't then maybe one of you can re-write this in a more comprehensive way since ADB sideload could come in handy.

    EDIT: I want to add that I did not figure this out on my own. I got it from this thread: http://forum.xda-developers.com/showpost.php?p=37993317&postcount=22. The only thing is I couldn't copy those values directly I had to find them myself under "hardware id"
    1
    A couple of days ago, I nearly bricked my phone to no return. In the process of this I remembered reading about ADB sideload. So I went ahead and tried to use the function to re-flash my ROM in TWRP. However, when I connected my phone my computer didn't recognize it and the "adb sideload 'filename'" command wasn't working it just kept telling me "device not connected". Is there a way I can set up my computer/phone for ADB sideload in case this ever happens to me again?
    1
    Did you have the drivers installed? Go to Control Panel > Hardware and Sound > Devices and Printers and make sure your phone shows up

    You can also run this:
    Code:
    adb devices

    To see connected devices
    1
    Adb won't detect devices that are in recovery, it has to be booted up because it checks whether debugging is enabled too
    1
    WAIT, no ignore that post lol
    The evo lte can be rebooted into recovery through adb even when it's dead.....

    So if the hardware supports it then it does work.....

    To your question....that's strange, maybe your phone just isn't compatible with it for some reason
    I know some peoples phones won't mount the sdcard through recovery, ever