[HOW TO] ADB Sideload/Push if you Wipe Internal Storage & No ROM to Flash [19 May 15]

[bdorr1105]

[HOW TO] ADB Sideload/Push if you Wipe Internal Storage & No ROM to Flash [19 May 15]

How to Sideload in TWRP if you erase your Internal Memory and don't have a ROM to Flash or Restore


Warning!

#include 
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Requirements

#include 
/*
* Unlocked Phone @ HTCDEV
* Custom Recovery
*/

Before You Start - Update Android SDK - How to set up Android SDK (ADB)








Instructions

• 
  
  MAKE SURE YOU BACK UP YOUR SD CARD FIRST!!!!!!!!
  
  Make Sure HTC Drivers are installed and ADB is already working
  
  1. Reboot into TWRP
  
  2. in TWRP, Hit andvanced and find Sideload
  
  3. Swipe to start Sideload
  
  4. Open a CMD Prompt window and Change Directories to where your adb.exe is
  
  5. type adb devices and it should show your device conntected and say sideload
  
  6. Your ZIP file should already be in your adb folder - See Example Below
  
  
  
  
  
  
  7. You are now ready to push the zip.....
  
  8. type adb sideload nameofzip.zip <------------See Example Below
  
  
  
  
  
  
  9. Wait until it says 100% and reboot back into recovery to flash the ROM
  
  10. If hitting power does not make the screen come one, type adb reboot recovery
  
  11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
  
  
  
  
  ADB Push from Recovery - If Sideload Fails For You ​
  
  
  adb push rom.zip /data/media/0/
  
  
  

​

If You have any Troubles with ADB

Koush Universal ADB Driver - Works on Windows 8 - Thanks xeroxide


YouTube Video for ADB Help

How to install ADB Drivers for any Device



​

​

​

 

[bdorr1105]

FAQ

If your Output looks similiar to this below, then you are not in sideload mode or you typed the command incorrectly

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\William>cd Downloads\ADB

C:\Users\William\Downloads\ADB>adb sideload Slim-nozomi-4.2.2.build.6-OFFICIAL
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\William\Downloads\ADB>-d: \
'-d:' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\William\Downloads\ADB>:-d
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\William\Downloads\ADB

DO THE FOLLOWING - (Refer to Post 1 Before you start for Picture Example)

1. Run sdk manager and update all the 4.1.2 - 4.4.2 binaries, you will see installed if you have done so

2. Reboot into TWRP

3. Go to advanced

4. Touch ADB Sideload

5. Swipe To start sideload

6. in command promt example: cd c:\android\sdk\platform-tools (that is where my adb files are at)

7. Once you have navigated to where your adb is at in command promt type adb devices

8. When you type adb devices, it should show your HTCxxjxihdjiw (whatever yours is) and Sideload which indicates you are set up properly

9. Once you see the above type adb sideload nameofzip.zip

If ADB does not See your device

1. After Download, go to My Computer, your C Drive

2. Create a folder named Android

3. Extract the Android SDK folder inside the Android Folder you just made
You should have the following in the folder only
- eclipse
- sdk
- SDK Manager.exe

4. Double click and open SDK Manager.exe

5. under the 4.1.2, 4.2.2, 4.3, and 4.4.2 section, install all the updates possible and it will show installed next to everything under 4.1.2 and 4.2.2

6. Restart Windows after all the updates
7. Open Command Prompt

8. cd c:\android\sdk\platform-tools

9. type adb devices, if you see your phone then reboot to recovery

10. In recovery, type adb devices, it should show your device in recovery, as a last resort you can use the adb push command

11. However, if you want to tstill try sideload, click advanced

12. Swipe to start Sideload

13. type adb devices and if it shows your device and says Sideload, follow the rest of the instructions

If ADB does not See your device in Recovery or Sideload - Thanks slayaman22232

1. After doing the above and getting ADB to work, but you are still having issues with your device not being seen in Recovery or Sideload even after installing latest HTC Drivers. Do the following, go to Universal ADB Driver link and install.

 

[Nick281051]

Thanks for making a thread like this, not sure if it needs to be in development but was definitely necessary for those who don't like to read through threads completely

Sent from my HTC One using Tapatalk 4 Beta

 

[bdorr1105]

Thanks for making a thread like this, not sure if it needs to be in development but was definitely necessary for those who don't like to read through threads completely

Sent from my HTC One using Tapatalk 4 Beta

Thanks yea just figured most traffic is in here and I had to do this upgrading my ROM especially when my internal memory was wiped

Sent from my HTC One using xda premium

 

[Nick281051]

Thanks yea just figured most traffic is in here and I had to do this upgrading my ROM especially when my internal memory was wiped

Sent from my HTC One using xda premium

I had to as well, to make matters worse, some of my files existed but didn't show up, I eventually got off what I needed though

Sent from my HTC One using Tapatalk 4 Beta

 

[clsA]

Sideloading does work but it's not the best method, for any Aroma based roms. (ARHD)(Trickdroid)..etc
Aroma is known to freeze and restart on it's own and everytime it does this you have to recopy the entire rom through sideload all over again.
The way that makes more sense is to just adb push rom.zip /data/media/0
this way if/when aroma restarts /freezes you already have the rom on the freshly formatted Sdcard
and all you have to do is restart the flash, not wait on it to copy all over again.

Of course having a USB OTG with the rom / backups on it eliminates the need for all this.

 

[Nick281051]

Sideloading does work but it's not the best method, for any Aroma based roms. (ARHD)(Trickdroid)..etc
Aroma is known to freeze and restart on it's own and everytime it does this you have to recopy the entire rom through sideload all over again.
The way that makes more sense is to just adb push rom.zip /data/media/0
this way if/when aroma restarts /freezes you already have the rom on the freshly formatted Sdcard
and all you have to do is restart the flash, not wait on it to copy all over again.

Of course having a USB OTG with the rom / backups on it eliminates the need for all this.

That's not true. Sideload works just fine, in fact it is still on my phone.

Sent from my HTC One using Tapatalk 4 Beta

 

[bdorr1105]

That's not true. Sideload works just fine, in fact it is still on my phone.

Sent from my HTC One using Tapatalk 4 Beta

Thanks for clearing that up brother appreciate it

 

[shook187]

Sideload is how I got my phone setup for 4.2.2

Sent from my HTC One using xda premium

 

[bdorr1105]

Sideload is how I got my phone setup for 4.2.2

Sent from my HTC One using xda premium

That is the method I also used. Thanks

Sent from my HTC One using xda premium

 

[designgears]

Sideloading does work but it's not the best method, for any Aroma based roms. (ARHD)(Trickdroid)..etc
Aroma is known to freeze and restart on it's own and everytime it does this you have to recopy the entire rom through sideload all over again.
The way that makes more sense is to just adb push rom.zip /data/media/0
this way if/when aroma restarts /freezes you already have the rom on the freshly formatted Sdcard
and all you have to do is restart the flash, not wait on it to copy all over again.

Of course having a USB OTG with the rom / backups on it eliminates the need for all this.

It creates and leaves a sideload.zip file on the sdcard. Aroma freezes when you use the buttons instead of using the power button for going to the page, it also freezes if you don't clear cache before you start.

I am surprised by the number of people that don't know about adb sideload!!

 

[clsA]

delete

 

[nolimit78]

I could not get this to work for the life of me. When I typed in the commands it acted as if I asked for help and spit out everything adb could do. However I did try:

adb push rom.zip /data/media/

And it worked just fine. As long as you're able to see your device with adb devices why bother with ADB Sideload? Not being a jerk just asking questions

 

[bdorr1105]

I could not get this to work for the life of me. When I typed in the commands it acted as if I asked for help and spit out everything adb could do. However I did try:

adb push rom.zip /data/media/

And it worked just fine. As long as you're able to see your device with adb devices why bother with ADB Sideload? Not being a jerk just asking questions

Didn't you do that from recovery because when you are in recovery adb push will not work. The reason sideload is in recovery is because that very reason. Additionally the reason it looked like you were asking for help is because you didn't have sideload running. This is emergency only or upgrade to 4.2

Sent from my HTC One using xda premium

 

[nolimit78]

Didn't you do that from recovery because when you are in recovery adb push will not work. The reason sideload is in recovery is because that very reason. Additionally the reason it looked like you were asking for help is because you didn't have sideload running. This is emergency only or upgrade to 4.2

Sent from my HTC One using xda premium

Yeah it was from recovery however, I tried adb sideload as the instructions stated. The file I wanted to push was in my adb folder. I made sure through TWRP I was in adb sideload (advanced > slide for adb sideload) typed in adb sideload rom.zip and It would just spit out something like this. So having a bit of experience in adb I tried adb push and thankfully it worked. My question was, instead of going through that hassle of adb sideload (which some people are having issues with) why not just use adb push instead? Seems that it's a redundant process is all.

The reason I started all of this is because I wanted to completely reformat the sd card because I had a sneaky suspicion that I had some data somewhere taking up data and I wanted it cleared. Ended up saving me about 5-6GB in total. So it was totally worth it

 

[bdorr1105]

Yeah it was from recovery however, I tried adb sideload as the instructions stated. The file I wanted to push was in my adb folder. I made sure through TWRP I was in adb sideload (advanced > slide for adb sideload) typed in adb sideload rom.zip and It would just spit out something like this. So having a bit of experience in adb I tried adb push and thankfully it worked. My question was, instead of going through that hassle of adb sideload (which some people are having issues with) why not just use adb push instead? Seems that it's a redundant process is all.

The reason I started all of this is because I wanted to completely reformat the sd card because I had a sneaky suspicion that I had some data somewhere taking up data and I wanted it cleared. Ended up saving me about 5-6GB in total. So it was totally worth it

Adb push should not work in recovery, they may work in sideload mode but I doubt it. If it does than great but you still have to be in sideload mode. Also it's meant to be easy because there are no paths which a lot of people struggle with and who are not familiar with adb. This automatically pushes to the root of your sd. You don't have to know anything else. Do what works for you. This guide is for people who have issues and ran into the situation

Sent from my HTC One using xda premium

 

[skulldreamz]

If adb sideload didn't work it would have never been incorporated into twrp. Sideloading has been around for a long time. People just don't take the time to read up on it. Adb sideloading works %100! It's nice that you created this thread and actually read intelligent posts for a change...

Sent from my HTC One using xda premium

 

[bdorr1105]

If adb sideload didn't work it would have never been incorporated into twrp. Sideloading has been around for a long time. People just don't take the time to read up on it. Adb sideloading works %100! It's nice that you created this thread and actually read intelligent posts for a change...

Sent from my HTC One using xda premium

+1 man thanks

 

[crash087]

any idea what to do when twrp wont completely start up sideload? it just sits there telling me its starting the adb feature, but never actually does it, so i cant push anything

 

[bdorr1105]

any idea what to do when twrp wont completely start up sideload? it just sits there telling me its starting the adb feature, but never actually does it, so i cant push anything

If it stays on ADB Sideload starting your fine man, just have a command promt open and type adb devices and it should show your device connected to the computer and say Sideload