Develop Bugs

adb help please

alright i deleted htc sync and now for some reason i cant mount my sdcard. so i need to push via adb.
i cant figure out the commands to push a file to sdcard any help please.
im on mac but codes should be about the same
or how can i get to the setting and reset them where is lets you choose charge phone,mount.tether extc

BigBallin said:
alright i deleted htc sync and now for some reason i cant mount my sdcard. so i need to push via adb.
i cant figure out the commands to push a file to sdcard any help please.
im on mac but codes should be about the same
or how can i get to the setting and reset them where is lets you choose charge phone,mount.tether extc
Click to expand...
Click to collapse
I can help with the first part;
Syntax: adb push source destination
Example:
adb push file.apk /sdcard

ive been doin that. and it says adb not found.

or i get this
Code:
Last login: Wed Oct 27 15:57:03 on ttys000
Laptop-5:~ kgirouex$ cd /Users/kgirouex/Documents/android/sdk/tools/
Laptop-5:tools kgirouex$ ./adb push apple.zip/sdcard
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
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 running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment 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] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
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 specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
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 the 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 updated.
- If it is "system" or "data", only the corresponding partition
is updated.
Laptop-5:tools kgirouex$

I don't know much about MAC but did you put the adb in the tools folder and direct the adb command from there for example in Windows its like this C:/Android/tools
sent through my Special Edition White HTC EVO 4g while in the ****ter

ins0dus said:
I don't know much about MAC but did you put the adb in the tools folder and direct the adb command from there for example in Windows its like this C:/Android/tools
sent through my Special Edition White HTC EVO 4g while in the ****ter
Click to expand...
Click to collapse
ya thats how i always run adb is in the tools folder. and the things i need to push are there also

I'm on the phone so the formatting of your post is jacked up, but it looks like you might be missing a space between your source and destination.
Sent from my blah blah blah blah

fachadick said:
I'm on the phone so the formatting of your post is jacked up, but it looks like you might be missing a space between your source and destination.
Sent from my blah blah blah blah
Click to expand...
Click to collapse
thanks. it supposed to read adb push apple.zip /sdcard i was doing the space after the slash and not before.

damnit, now it says cant push because /sdcard is a directory
redid it and pushed to sdcard/download and it worked wtf

Good! Don't you just love that feeling when everything runs smooth.. I hate all the troubleshooting bs
sent through my Special Edition White HTC EVO 4g while in the ****ter

Yeah, nice!
Sent from my blah blah blah blah

[Q] SERIOUS PROBLEM! Save Me...

Okay, here's what happened,
2 days ago, i installed ARHD ROM, works perfectly fine,
next day, i saw a kernel by franco. installed it, then after rebooting.... baamm! my unit is not working anymore, stuck in boot screen,
i tried different ways, followed different forums, like Tutorial Disaster. still to no avail,
the sad thing is, i forgot to back it up before doing the upgrades, i know its my fault..
i tried to erase everything via recovery, still not working,
Just today, went to HTC service center, i'm from the Philippines, but i bought my unit from online selling. as per HTC service center its from indonesia, they tried to re-flash something but they said its not working, so they said that they will need to change the mother board, and it will cost me 14,000 pesos or $350.. i don't want to spend that much, feels like i bought a new one..
can someone please enlighten me?

?!
You can erase everything in recovery, but you have to flash something afterwards, maybe like ARHD.
There's nothing wrong with your device, don't panic. Just do a wipe, then flash the ROM as the directions are given.

if you can still get into recovery
relock it
flash stock recovery
flash stock RUU
done

Download ARHD and CWM Recovery
Rename ARHD to update.zip and CWM to recovery.img
Place update.zip and recovery.img into a folder with fastboot and adb
Extract boot.img from update.zip and place in your fastboot folder
Put your phone into fastboot mode with unlocked bootloader
Flash boot with command 'fastboot flash boot boot.img'
Boot recovery using 'fastboot boot recovery.img' command
Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
Then install rom from update.zip in recovery

It's nothing serious with your phone. It is easily can be recovered. Just don't run here and there so the XDA community can assist you.
There are two ways to recover your phone.
1) flash RUU
2) push xxx_rom.zip to your device.
Already tell you about flashing RUU in the disaster thread.

well, i would like to give thanks to all of you, who answered my questions, helped a lot. trying to read more here before doing another run in fixing my device.
where can i get stock RUU? my device is from indonesia. and one more thing, how to flash RUU?
djpoe said:
Download ARHD and CWM Recovery
Rename ARHD to update.zip and CWM to recovery.img
Place update.zip and recovery.img into a folder with fastboot and adb
Extract boot.img from update.zip and place in your fastboot folder
Put your phone into fastboot mode with unlocked bootloader
Flash boot with command 'fastboot flash boot boot.img'
Boot recovery using 'fastboot boot recovery.img' command
Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
Then install rom from update.zip in recovery
Click to expand...
Click to collapse
very detailed instruction here
where can i get adb BTW?

wintermute000 said:
if you can still get into recovery
relock it
flash stock recovery
flash stock RUU
done
Click to expand...
Click to collapse
This and finish with: fastboot erase cache
Sent from my HTC One X using XDA

wolfraim said:
This and finish with: fastboot erase cache
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
thanks man.. where can i get the stock RUU and stock recovery? and also why do we have to re lock the device?
EDIT: i almost forgot, because this problem started after installing a new kernel by franco, so i guess i need to install a stock kernel? where can i get it?

mikey0105 said:
thanks man.. where can i get the stock RUU and stock recovery? and also why do we have to re lock the device?
EDIT: i almost forgot, because this problem started after installing a new kernel by franco, so i guess i need to install a stock kernel? where can i get it?
Click to expand...
Click to collapse
I had the same problem with franco's kernel, what I did was, go to recovery and re-flash my xx_rom.zip, then it boots ok. You should try the same, provided you still have the ARHD.zip in your sdcard.
Your device from Indonesia ? I believe this is the RUU for you (same for me too):http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257076_signed.exe

ckpv5 said:
I had the same problem with franco's kernel, what I did was, go to recovery and re-flash my xx_rom.zip, then it boots ok. You should try the same, provided you still have the ARHD.zip in your sdcard.
Your device from Indonesia ? I believe this is the RUU for you (same for me too):http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257076_signed.exe
Click to expand...
Click to collapse
thanks ill try it later.. i don't have it on my sdcard, as i've said i erased everything already..
but i guess i'll try the step on top provided by "djpoe" to put the ARHD inside my SD card. hope everything will work..
1 Download ARHD and CWM Recovery
2 Rename ARHD to update.zip and CWM to recovery.img
3 Place update.zip and recovery.img into a folder with fastboot and adb
4 Extract boot.img from update.zip and place in your fastboot folder
5 Put your phone into fastboot mode with unlocked bootloader
6 Flash boot with command 'fastboot flash boot boot.img'
7 Boot recovery using 'fastboot boot recovery.img' command
8 Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
9 Then install rom from update.zip in recovery

For item 7 & 8, maybe you like a safe-proof guide that I posted here
Just replace "D:\HTC\One X\HTC Dev.com unlock\android-sdk\platform-tools>" to your own fastboot/adb folder path
and "recovery-clockwork-touch-5.8.3.1-endeavoru.img" to "recovery.img" if you renamed it.
and "xxx.zip" to "update.zip"

thanks, i'm downloading the files now...
quick question, if i erased all data/cache, the kernel that i installed? will it be deleted as well? because i need to have a stock kernel and i can't see one?

erase all data/system/cache will not delete the installed kernel.
As you said you will follow djpoe's guide, see no. 4 & no. 6 regarding kernel flashing.
Remember the ROM.zip that you have earlier (see Disaster thread), inside the ROM.zip there is a boot_signed.img, that is the stock kernel. But you don't really need the stock kernel, what you need is the AHRD's kernel (see. no.4).

ohhh i see! now that good to know thanks... waiting for the files to be downloaded.. will give you feedback later... fingers cross...

additional question, just wondering, why is it important to re-lock the device before flashing ruu?

i tried to copy the update.zip by doing this
adb push update.zip/sdcard/update.zip
then there are lots of command on the CMD.. see below
C:\fastboot>adb push update.zip/sdcard/update.zip
Android Debug Bridge version 1.0.29
-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
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
-------------------------------
then tried to install it via CWM, apply /sdcard/update.zip
it says
finding update
opening update
E: Can't open sdcard/update.zip
(No such file or directory)
Installation aborted

It should be C:\fastboot>adb push update.zip /sdcard not C:\fastboot>adb push update.zip/sdcard/update.zip
where is your adb files ? In the fastboot folder too ? If yes, try this:
1. C:\fastboot>fastboot boot recovery-clockwork-touch-5.8.3.1-endeavoru.img
2. C:\fastboot>adb devices
enter
C:\fastboot>adb shell
enter then type after ~ # mount sdcard
3. don't close anything, open another cmd prompt
C:\fastboot>adb push update.zip /sdcard
then enter
once completed, choose install from sdcard - choose zip from sdcard, the update.zip should be there

here whats happening. see attachment

mikey0105 said:
here whats happening. see attachment
Click to expand...
Click to collapse
There is no AdbWinUsb.dll in your folder ?

GUYS!!! AT LAST!!!! I'm so happy!!! its all okay now! oh man! this is crazy! hahaha! thank you so much to all!. the feeling is really great! WOOOOOWWWWW!!!!

[Q] How could i transfer files in CWM?

How could i transfer files in CWM?
Both my sdcard and internal partition was accidentally wiped out when trying to fix a bootloop earlier.
Currently, my phone could only access fastboot and recovery mode. I wanted to transfer *.img on my sd partition so i could flash a ROM to fix this problem.
I already tried to mount the usb storage from CWM recovery. but it would give me an error "E: unable to open ums lunfile"
is there any way to push a *.img file to my sdcard? or is there any way that i could flash TWRP?

Update to latest CWM

Check to see if you have the latest CWM. If not then flash the new one. Once your connected you can just drag & drop from your pc.
Sent from my HTC One X using xda app-developers app

BenPope said:
Update to latest CWM
Click to expand...
Click to collapse
Thanks for that Ben, but is it possible to update to the latest CWM, i could not boot my phone, I could only access recovery/fastboot mode. Im sorry being so stupid, im just new to this stuff :crying:
EDIT: my bad. thanks for the advice. trying to update now

Banzai761 said:
Thanks for that Ben, but is it possible to update to the latest CWM, i could not boot my phone, I could only access recovery/fastboot mode. Im sorry being so stupid, im just new to this stuff :crying:
EDIT: my bad. thanks for the advice. trying to update now
Click to expand...
Click to collapse
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!

not working
I unlocked the boot loader after following all the steps on htcdev.com..
it was successful.
then i installed CWM v5.8.4.0
then i tried to install Viper X custom rom from the recovery.
but even with the aroma installer, i has to select next,etc with with vol+,vol- button and then power button to click.
what is wrong with my phone..please help me..

wcypierre said:
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
Click to expand...
Click to collapse
Thanks for your help

George_Orever said:
Thanks for your help
Click to expand...
Click to collapse
thank you very much
---------- Post added at 02:02 AM ---------- Previous post was at 01:54 AM ----------
wcypierre said:
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
Click to expand...
Click to collapse
every time i try to push a file i get this
C:\adbfastboot>adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip/sdcard
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.
What do i do?

I think that you wanted to push adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip to /sdcard.
If yes, then, you need an additional space for it to separate the source and the destination
adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip /sdcard
mikkygwaz24 said:
thank you very much
---------- Post added at 02:02 AM ---------- Previous post was at 01:54 AM ----------
every time i try to push a file i get this
C:\adbfastboot>adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip/sdcard
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.
What do i do?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Why dont you enter the recovery and mount the sdcard as a usb diskdrive and copy to it what you need ?

wcypierre said:
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
Click to expand...
Click to collapse
This!
Just saved my life.
- I had a pandroid LG G2 but locked.
- To unlock, I had to restore to stock (3+ hours mainly download times) and first time setup.
- It was working perfect as stock. But Wanted CWM or TWRP. Installed CWM correctly.
- MAde nandroid backup
- Reboot - said yes to reapply Loki + Super.
- Destroyed everything in the phone. Download mode will not work. Only thing I could do is go in recovery!
- Been working all sort of fix but none worked. Can't put custom roms either (weired loki error)
- Finally thought I should try pushing this original backup on phone! worked and installed in 10 min!!

PrinceMS said:
This!
Just saved my life.
- I had a pandroid LG G2 but locked.
- To unlock, I had to restore to stock (3+ hours mainly download times) and first time setup.
- It was working perfect as stock. But Wanted CWM or TWRP. Installed CWM correctly.
- MAde nandroid backup
- Reboot - said yes to reapply Loki + Super.
- Destroyed everything in the phone. Download mode will not work. Only thing I could do is go in recovery!
- Been working all sort of fix but none worked. Can't put custom roms either (weired loki error)
- Finally thought I should try pushing this original backup on phone! worked and installed in 10 min!!
Click to expand...
Click to collapse
You're welcome. Glad that my solution worked well for you

PrinceMS said:
This!
Just saved my life.
- I had a pandroid LG G2 but locked.
- To unlock, I had to restore to stock (3+ hours mainly download times) and first time setup.
- It was working perfect as stock. But Wanted CWM or TWRP. Installed CWM correctly.
- MAde nandroid backup
- Reboot - said yes to reapply Loki + Super.
- Destroyed everything in the phone. Download mode will not work. Only thing I could do is go in recovery!
- Been working all sort of fix but none worked. Can't put custom roms either (weired loki error)
- Finally thought I should try pushing this original backup on phone! worked and installed in 10 min!!
Click to expand...
Click to collapse
Not trying to highjack this topic, but how did you push the file to the sd card when the LG G2 does not have an sd card, only storage. I ask as I have the LG G2 and have clockworkmod installed as my recovery, but my internal storage is blank and my nandroid backups are gone. I cant find a way to get a rom onto my internal storage so I can flash it.
Edit: After shedding a few tears (Just Kidding) thinking I was screwed since I only had internal storage. As long as you have adb setup correctly, do the following:
1. Enter clockworkmod recovery
2. go to mounts and storage
3. Mount /data
4. Type adb push filename.zip /data/media/0
5. After the file has copied over, unmount /data in the mounts and storage
6. probably not required, but I rebooted recovery.
7. Install your zip.
Thanks wcypierre for basically giving me the process. I just needed to rework it a bit.

[Q] How do you do a full erase of the phone, (eg: externalSD, etc)

Is there a way to do a full wipe of the phone? externalSD and all things in between. Im just curious.

aer0zer0 said:
Is there a way to do a full wipe of the phone? externalSD and all things in between. Im just curious.
Click to expand...
Click to collapse
I used the RUU in the development thread, but you have to be s-off.
I used these instructions:
http://forum.xda-developers.com/showthread.php?t=2251800

If you have a custom recovery installed you can go through and format each partition
Sent from my HTC6500LVW using Tapatalk

mlin said:
If you have a custom recovery installed you can go through and format each partition
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Reading some other posts since this thing came out, beware TWRP and wiping internal storage. That is will cause you to have to sideload a .zip to flash. Still prefer TWRP, just careful not to check that box.

chip.hughes said:
Reading some other posts since this thing came out, beware TWRP and wiping internal storage. That is will cause you to have to sideload a .zip to flash. Still prefer TWRP, just careful not to check that box.
Click to expand...
Click to collapse
Well I wiped internal like an idiot. Phone will go to the HTC screen with the red writing at the bottom but thats it. Any help getting things back together would be greatly appreciated.

unstab1e1199 said:
Well I wiped internal like an idiot. Phone will go to the HTC screen with the red writing at the bottom but thats it. Any help getting things back together would be greatly appreciated.
Click to expand...
Click to collapse
That's one way to do it. You'll have to side load a .zip (ROM) to flash. I have to go pick up pecans, so I can't answer a lot of questions if you are not familiar with ADB or command line. I promise it is not hard. Your not the first here to do this, I think Andybones helped someone not long back with this. I googled it for you, there are some youtube videos and here is a link.
http://www.oppoforums.com/threads/how-to-save-your-device-after-a-full-wipe.1907/
You'll need the drivers for this device and all that can be found here:
http://forum.xda-developers.com/showthread.php?t=2417043
look for "root files"

chip.hughes said:
That's one way to do it. You'll have to side load a .zip (ROM) to flash. I have to go pick up pecans, so I can't answer a lot of questions if you are not familiar with ADB or command line. I promise it is not hard. Your not the first here to do this, I think Andybones helped someone not long back with this. I googled it for you, there are some youtube videos and here is a link.
http://www.oppoforums.com/threads/how-to-save-your-device-after-a-full-wipe.1907/
You'll need the drivers for this device and all that can be found here:
http://forum.xda-developers.com/showthread.php?t=2417043
look for "root files"
Click to expand...
Click to collapse
My main problem at the moment is twrp just says starting sideload mode. It never actually enters it. I have Andy's Bonestock v1.1 and renamed it find5.zip, I've tried just running the command to see if would push but, that dosent seem to work either.

unstab1e1199 said:
My main problem at the moment is twrp just says starting sideload mode. It never actually enters it. I have Andy's Bonestock v1.1 and renamed it find5.zip, I've tried just running the command to see if would push but, that dosent seem to work either.
Click to expand...
Click to collapse
Quick guess is drivers. Never having done this myself, I'm thinking the twrp won't react until push starts. I have had to go to device manager (with device plugged in), uninstalled and reinstall the drivers. Sometimes I have had to just move to one of my other computers, that I never connected the phone to, to start fresh. Windows just wouldn't cooperate and let go of some old drivers. Try pm'ing andybones, if you still aren't having any luck by this evening, I'll remote you and look at it if you want me to.

chip.hughes said:
Quick guess is drivers. Never having done this myself, I'm thinking the twrp won't react until push starts. I have had to go to device manager (with device plugged in), uninstalled and reinstall the drivers. Sometimes I have had to just move to one of my other computers, that I never connected the phone to, to start fresh. Windows just wouldn't cooperate and let go of some old drivers. Try pm'ing andybones, if you still aren't having any luck by this evening, I'll remote you and look at it if you want me to.
Click to expand...
Click to collapse
I'm going to try a fresh download of everything and see if that works. adb devices is showing my phone in sideload but, adb sideload then the path to the zip isn't working. I'll figure it out eventually. Thank you for all the help it's really appreciated

unstab1e1199 said:
I'm going to try a fresh download of everything and see if that works. adb devices is showing my phone in sideload but, adb sideload then the path to the zip isn't working. I'll figure it out eventually. Thank you for all the help it's really appreciated
Click to expand...
Click to collapse
If you're using the push command you don't need/want to have the phone in sideload mode. Per TWRP's website normal adv commands don't work in sideload. I couldn't get sideload to work when I sis this but adb push to /data/media/0/ worked fine.
Sent from my HTC6500LVW using Tapatalk

mlin said:
If you're using the push command you don't need/want to have the phone in sideload mode. Per TWRP's website normal adv commands don't work in sideload. I couldn't get sideload to work when I sis this but adb push to /data/media/0/ worked fine.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
ok I have minimal adb and fastboot installed to c:. I have put my rom zip into the adb folder and opened my command from that folder. I have tried sideload to no avail so could u tell me what I need to type in command to push my zip? I have renamed it find5.zip. I have tried to push and sideload on three differnt computers usin different adb and drivers. Guess I have bricked it

unstab1e1199 said:
ok I have minimal adb and fastboot installed to c:. I have put my rom zip into the adb folder and opened my command from that folder. I have tried sideload to no avail so could u tell me what I need to type in command to push my zip? I have renamed it find5.zip. I have tried to push and sideload on three differnt computers usin different adb and drivers. Guess I have bricked it
Click to expand...
Click to collapse
Okay, do this.
1) Boot into recovery
2) Open command from your minimal fastboot/adb folder
3) type adb devices- you should see something like a serial number if your device is recognized, if not, you will need to install the htc drivers.
4) if your device is recognized, type the following command: adb push find5.zip /data/media/0/
5) Disconnect the phone from computer then in recovery go to install and to the location specified above. Your ROM should be there.
This is exactly what I did 2 days ago and it worked. If you can get to recovery, you're not bricked.
I'll be on my comp for a bit so I can help you trouble shoot through this.

mlin said:
Okay, do this.
1) Boot into recovery
2) Open command from your minimal fastboot/adb folder
3) type adb devices- you should see something like a serial number if your device is recognized, if not, you will need to install the htc drivers.
4) if your device is recognized, type the following command: adb push find5.zip /data/media/0/
5) Disconnect the phone from computer then in recovery go to install and to the location specified above. Your ROM should be there.
This is exactly what I did 2 days ago and it worked. If you can get to recovery, you're not bricked.
I'll be on my comp for a bit so I can help you trouble shoot through this.
Click to expand...
Click to collapse
just says no such file or directory in adb. Device is connected and in recovery
---------- Post added at 03:08 AM ---------- Previous post was at 03:00 AM ----------
unstab1e1199 said:
just says no such file or directory in adb. Device is connected and in recovery
Click to expand...
Click to collapse
This is what I get if I push the whole file path. Same when I try to sideload it
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Minimal ADB and Fastboot>adb push /C:/minimal adb and fastboot/find5.zip /dat
a/media
Android Debug Bridge version 1.0.31
-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 <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
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 [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l 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)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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 get-devpath - prints: <device-path>
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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Minimal ADB and Fastboot>

unstab1e1199 said:
just says no such file or directory in adb. Device is connected and in recovery
---------- Post added at 03:08 AM ---------- Previous post was at 03:00 AM ----------
This is what I get if I push the whole file path. Same when I try to sideload it
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Minimal ADB and Fastboot>adb push /C:/minimal adb and fastboot/find5.zip /dat
a/media
Android Debug Bridge version 1.0.31
-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 <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
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 [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l 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)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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 get-devpath - prints: <device-path>
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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You don't need to enter the path if your ROM is in the same folder as adb abd this is where you are opening the command prompt.
Here is what I did.
Move my ROM, named rom.zip into "c:\programs (x86)\minimal adb and fastboot\" (or whatever its called exactly).
Then, using Windows explorer, while in that folder, in the address bar typed "cmd" without the quotes. This opens command prompt from the present directory.
Then, simply type adb push rom.zip /data/media/0/
***Also, I had to have the /0/ after media. Without it, I got a no such directory message even though I could see the directory was there.***

mlin said:
You don't need to enter the path if your ROM is in the same folder as adb abd this is where you are opening the command prompt.
Here is what I did.
Move my ROM, named rom.zip into "c:\programs (x86)\minimal adb and fastboot\" (or whatever its called exactly).
Then, using Windows explorer, while in that folder, in the address bar typed "cmd" without the quotes. This opens command prompt from the present directory.
Then, simply type adb push rom.zip /data/media/0/
***Also, I had to have the /0/ after media. Without it, I got a no such directory message even though I could see the directory was there.***
Click to expand...
Click to collapse
I stuck everything in C: for easy reference. Opening my command prompt in that window and just typing amd push find5.zip /data/media/0/says no such file. I've been at this all day have to say out of all he rooted devices I have had this is the worst problem I have came across

unstab1e1199 said:
I stuck everything in C: for easy reference. Opening my command prompt in that window and just typing amd push find5.zip /data/media/0/says no such file. I've been at this all day have to say out of all he rooted devices I have had this is the worst problem I have came across
Click to expand...
Click to collapse
Weird. The "no such file" message makes it sound like your ROM is not in the same folder or isn't named as you've indicated.

mlin said:
Weird. The "no such file" message makes it sound like your ROM is not in the same folder or isn't named as you've indicated.
Click to expand...
Click to collapse
Would it make a difference if I downloaded the rom on another pc and copied it to a external drive then copied it back onto this pc? I am in the process of a fresh download onto this pc to see if it helps. Seems all the files are in the zip I copied though.

unstab1e1199 said:
Would it make a difference if I downloaded the rom on another pc and copied it to a external drive then copied it back onto this pc? I am in the process of a fresh download onto this pc to see if it helps. Seems all the files are in the zip I copied though.
Click to expand...
Click to collapse
Just to be clear, you definitely have find5.zip in the same folder as adb.exe?
Try this:
adb push find5.zip /data/media/0/find5.zip

mlin said:
Just to be clear, you definitely have find5.zip in the same folder as adb.exe?
Try this:
adb push find5.zip /data/media/0/find5.zip
Click to expand...
Click to collapse
Yeah I copied the rom to the exact folder. I am gonna have to get in the bed I gotta be at work soon. I'll try this tomorrow with a fresh rom download. Do I need to be on any specific screen in twrp other than the home screen?

unstab1e1199 said:
Yeah I copied the rom to the exact folder. I am gonna have to get in the bed I gotta be at work soon. I'll try this tomorrow with a fresh rom download. Do I need to be on any specific screen in twrp other than the home screen?
Click to expand...
Click to collapse
I don't believe so but I'll try it on my phone to confirm. I'll post here when I find out. Good luck getting this figured out, sorry I wasn't able to help you get it fixed. Very bizarre.

Helpe Me Please !! I delete my rom.

Hello good afternoon, yesterday I tried to change my rom via sdcard on my m7 32gb htc one however he has failed and erased the rom and not open more access to his sdcard to try to correct the mistake he is with root and my biggest doubt I do I return everything to normal? I'm watching videos, reading tutorials all night and nothing helps me what I can really do to put the rom on it again?
Ps: this happened after I sent the rom install google edition by twr recovery and gave error when I start my mobile al it appears google and gets into an infinite boot.
Thank you thank you for all the help.

liufong said:
Hello good afternoon, yesterday I tried to change my rom via sdcard on my m7 32gb htc one however he has failed and erased the rom and not open more access to his sdcard to try to correct the mistake he is with root and my biggest doubt I do I return everything to normal? I'm watching videos, reading tutorials all night and nothing helps me what I can really do to put the rom on it again?
Ps: this happened after I sent the rom install google edition by twr recovery and gave error when I start my mobile al it appears google and gets into an infinite boot.
Thank you thank you for all the help.
Click to expand...
Click to collapse
In twrp go in to menu Sideload
Connect your phone to PC
Now ADB should recognize it in sideload mode
check with command adb sideload in command prompt on PC
you can puch a rom like CM11 because its small in size
the comment is
ADB sideload filename.zip
One its transferred to phone will install automatically
You can google for ADB or sideload if you dont understand it.

please do not get mad
desiwizard said:
In twrp go in to menu Sideload
Connect your phone to PC
Now ADB should recognize it in sideload mode
check with command adb sideload in command prompt on PC
you can puch a rom like CM11 because its small in size
the comment is
ADB sideload filename.zip
One its transferred to phone will install automatically
You can google for ADB or sideload if you dont understand it.
Click to expand...
Click to collapse
do you have a comands in the terminal pass for me ? or a mini tutorial i'am new htc user i have various rom in my pc i can upload in the cellphone anyone ?

liufong said:
do you have a comands in the terminal pass for me ? or a mini tutorial i'am new htc user i have various rom in my pc i can upload in the cellphone anyone ?
Click to expand...
Click to collapse
Open a command prompt in the directory that contains ADB.
Boot your phone into TWRP recovery and connect a USB cable. Do not enter ADB Sideload.
From the command prompt, type 'adb devices' and after a few seconds you should see your phone in the list of connected devices. If the list is blank, you may not have the proper drivers installed for your phone. Assuming you do see a device listed, continue to the next step.
Place a copy of the ROM you wish to install in the same directory from above, naming it ROM.zip
Type the following command: 'adb push ROM.zip /sdcard/ROM.zip' and hit Enter. Depending on ROM size, it may take up to 5 minutes to complete. You will see a message when it completes.
Now unplug your phone, go to the Install option in TWRP, and select ROM.zip.

why?
NotATreoFan said:
Open a command prompt in the directory that contains ADB.
Boot your phone into TWRP recovery and connect a USB cable. Do not enter ADB Sideload.
From the command prompt, type 'adb devices' and after a few seconds you should see your phone in the list of connected devices. If the list is blank, you may not have the proper drivers installed for your phone. Assuming you do see a device listed, continue to the next step.
Place a copy of the ROM you wish to install in the same directory from above, naming it ROM.zip
Type the following command: 'adb push ROM.zip /sdcard/ROM.zip' and hit Enter. Depending on ROM size, it may take up to 5 minutes to complete. You will see a message when it completes.
Now unplug your phone, go to the Install option in TWRP, and select ROM.zip.
Click to expand...
Click to collapse
after executing the last line of the command you gave me "adb push Rom.zip / sdcard / ROM.zip it appears in the what I'm doing wrong screen?:silly:
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a c
onnection
-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 <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
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.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
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 forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l 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)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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 get-devpath - prints: <device-path>
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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

You must have typed something wrong in the cmd when you entered it.
Code:
adb push ROM.zip /sdcard/ROM.zip

The Rom.zip needs to be in the same folder that has adb.exe most folks use their platform tools folder.
You also need to open the cmd window from that same folder.
If you don't have that folder you can use the attached folder.

vish
BD619 said:
The Rom.zip needs to be in the same folder that has adb.exe most folks use their platform tools folder.
You also need to open the cmd window from that same folder.
If you don't have that folder you can use the attached folder.
Click to expand...
Click to collapse
I used the folder that you sent me and put the rom file inside it follows the photos below of the process I'm doing if possible please take a look, see if I'm doing something wrong.
thank you!

liufong said:
I used the folder that you sent me and put the rom file inside it follows the photos below of the process I'm doing if possible please take a look, see if I'm doing something wrong.
thank you!
Click to expand...
Click to collapse
You don't have spaces as I typed above. And you typed ROM2.zip, but the file is named ROM.zip.
adb push ROM.zip /sdcard/ROM.zip

up
NotATreoFan said:
You don't have spaces as I typed above. And you typed ROM2.zip, but the file is named ROM.zip.
adb push ROM.zip /sdcard/ROM.zip
Click to expand...
Click to collapse
I tried the method sideload it up al the rom.zip with the name sideload.zip sent install and gave error sent clean partitions
Now I saw what I was doing wrong were actually spaces, now I did the "adb devices" command does not appear and nothing will I have to update some drive? thank you!

liufong said:
I tried the method sideload it up al the rom.zip with the name sideload.zip sent install and gave error sent clean partitions
Now I saw what I was doing wrong were actually spaces, now I did the "adb devices" command does not appear and nothing will I have to update some drive? thank you!
Click to expand...
Click to collapse
Try using different USB port, USB 3.0 does give problems some time

liufong said:
I tried the method sideload it up al the rom.zip with the name sideload.zip sent install and gave error sent clean partitions
Now I saw what I was doing wrong were actually spaces, now I did the "adb devices" command does not appear and nothing will I have to update some drive? thank you!
Click to expand...
Click to collapse
You have to turn off Sideload. Normal adb commands do not work in that mode. Turn your phone off, then boot into recovery and try again.

I borked my phone in much the same way when I tried to update to kitkat with a crappy hotel Wi-Fi. I ended up having to fastboot flash a RUU. Sideload wasn't working for me.

@NotATreoFan
Why the extra Rom.zip at the end of the command? I have always used adb push Rom.zip /sdcard/ without problems...just curious if I'm missing something.
adb push Rom.zip /sdcard/Rom.zip

BD619 said:
@NotATreoFan
Why the extra Rom.zip at the end of the command? I have always used adb push Rom.zip /sdcard/ without problems...just curious if I'm missing something.
adb push Rom.zip /sdcard/Rom.zip
Click to expand...
Click to collapse
You probably don't need it. Just the way I've always done it.

You can do it both ways. The one way just allows you to push the file to the phone but save it under a different name ( adb push rom.zip /sdcard/myrom.zip)

cmlusco said:
You can do it both ways. The one way just allows you to push the file to the phone but save it under a different name ( adb push rom.zip /sdcard/myrom.zip)
Click to expand...
Click to collapse
Did not know that

Thanks for all !
super thanks for help guys, everything worked out here and conssegui install miui'm trying to google rom edition but this is already failing but alas another story, thank you very much for the help anyway!

liufong said:
super thanks for help guys, everything worked out here and conssegui install miui'm trying to google rom edition but this is already failing but alas another story, thank you very much for the help anyway!
Click to expand...
Click to collapse
Just to confirm you have a verizon HTC one and are trying to install a ROM specifically made for the verizon HTC one?

no
no my smartphone is international xD