[Recovery]{CWM} Virgin Mobile Venture 6.0.1.2

[Curtis1973]

pdanet should be in your app drawer on the phone. start it,then start pdanet desktop

 

[SimsKITblue]

go figure pdanet isn't in my apps drawer on my phone i am getting it from market now

ok installed it turned on tether and still got htc sync error =-1 turned it off turned on bluetooth DUN NOW WANTS ME TO DOWNLOAD foxfi which isnt available with my carrier do i install anyway?

 

[Dracable]

oopsie... declutter the forum... sorry!

 

[Dracable]

it might give u that error if adb is open. unplug ur phone, open windows task manager, look for adb. if its there, kill the process. disable and then reenable tethering on ur phone, and then plug it back in. the driver can b picky sometimes if not done in the correct order.

 

[SimsKITblue]

when i went to safely remove my phone from the system tray it asks me to remove adb interface as well. could that be the issue. If i remove the interface instead of

 

[Dracable]

if the adb interface thing came up, u should b good to go. open a command prompt, browse to your sdk folder, then to the folder platform-tools inside of it. once in platform-tools, type adb devices. if it comes up with a string of numbers or a mention of Venture, u should b good to go! the fact that it is giving u the option to safely remove the interface means that ur adb driver is installed. dont worry about the pdanet program. it doesnt have to b connected to the internet to use adb.

 

[SimsKITblue]

open a command prompt

I am assuming that you mean window explore not DOS prompt to my computer C/: and search for the folder SDK which was downloaded through the alternative thread with the EnvSET shortcut or through the SDK in program files in the Android sdk tools file. and if window explorer in windows XP where am i typing devices?

 

[divinebovine]

You shouldn't have to run PDANet anywhere, just install it on the computer so the driver gets installed and then ignore it entirely. Works on my XP computer.

He meant command prompt (it's technically not a DOS prompt and hasn't been since Windows ME), not Explorer.

Start -> Run
CMD <enter>
cd "\Program Files\Android\android-sdk\platform-tools"
adb devices (you should see "List of devices attached" and one item in the list)
adb shell (now you are at a $ prompt, the linux command prompt running on the phone)
su (now you are at a # prompt, the elevated linux command prompt running on the phone)

 

[SimsKITblue]

I am obviously missing a step and i can't figure this out. I opened up the command prompt in DOS it starts with documents and settings instead of just C:\ I am drawing a blank can someone give me all the steps i am missing something .

i opened fastboot.exe and it says adbwinapi.dll was not found

 

[SimsKITblue]

You shouldn't have to run PDANet anywhere, just install it on the computer so the driver gets installed and then ignore it entirely. Works on my XP computer.

He meant command prompt (it's technically not a DOS prompt and hasn't been since Windows ME), not Explorer.

Start -> Run
CMD <enter>
cd "\Program Files\Android\android-sdk\platform-tools"
adb devices (you should see "List of devices attached" and one item in the list)
adb shell (now you are at a $ prompt, the linux command prompt running on the phone)
su (now you are at a # prompt, the elevated linux command prompt running on the phone)

thank you i was doing msconfig and ms-dos in the run this is what i was missing i was using the wrong command. I am so sleepy

 

[Dracable]

thanks divine. i was super tired myself, and typing it all out on my Venture's keyboard, so perhaps i wasnt quite descriptive as i should have been. thanks for clearing up what i was tryin to say. glad to hear u got adb working! happy flashing!

 

[SimsKITblue]

one last thing i have thoroughly confused myself. too many things going on and not enough sleep. ok so i have gotten to the su now am i at the end of the code i need to input or the beginning? and start with the abd push flash_image blah blah blah that followed on the first post in this thread? and when i put in the location i put the directory on the sdcard which i put it in the android folder. with my stock ROM backup and my personal ROM replacement i worked on last night. yes i am on the phone so yes where i put the files on my phone.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>cd "\program files\android\android-sdk\platform-
tools\
The system cannot find the path specified.

C:\Documents and Settings\Owner>cd "\program files\sdk\platform-tools\

C:\Program Files\SDK\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached


C:\Program Files\SDK\platform-tools>adb shell
error: device not found

C:\Program Files\SDK\platform-tools>adb devices
List of devices attached


C:\Program Files\SDK\platform-tools>adb shell
error: device not found

C:\Program Files\SDK\platform-tools>adb devices
List of devices attached


C:\Program Files\SDK\platform-tools>adb devices
List of devices attached


C:\Program Files\SDK\platform-tools>cd "\program files\sdk-tools\"

C:\Program Files\sdk-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
OTA100002648C2DC device


C:\Program Files\sdk-tools>adb shell
$ su
su
# adb push flash_image /sdcard/android/data/flash_image
adb push flash_image /sdcard/android/data/flash_image
adb: not found
# adb push cwm-recovery.img /sdcard/android/data/recovery.img
adb push cwm-recovery.img /sdcard/android/data/recovery.img
adb: not found
# adb push flash_image /sdcard/android/data/flash_image
adb push flash_image /sdcard/android/data/flash_image
adb: not found
# exit
exit
$ su
su
# adb push flash_image /android/data/flash_image
adb push flash_image /android/data/flash_image
adb: not found
#

I am taking a nap if i missed something please respond

 

[Dracable]

once u have set up adb, u need to move the 2 files that u downloaded from the very first posting in this thread (the custom recovery files) into the platform-tools subfolder of your sdk folder. after that (with your phone plugged into your pc), you run the code that is posted in the beginning of this thread in your command prompt. make sure that you are in the platform-tools directory in your command prompt before running the code. if all goes well, cmw recovery should be installed after entering the last line of coding in ur command prompt.

 

[Dracable]

so, first thing u need to do is to copy the flash_image and the cwm-recovery.img files to c:\program files\sdk-tools. after you do that, open command prompt, make sure in the command prompt that you are pointed to the c:\program files\sdk-tools directory, and run the EXACT coding in the first post of this thread. that SHOULD take care of your problems if u follow step by step.

edit: i should make it clear that the flash_image and cwm-recovery.img files do not go on the sd card at all. those files are put into the sdk folder, and the coding that was posted at the beginning of this thread tells adb to "push" the files to your phone's file system. after that, adb tells your phone to flash the boot.img file to the /boot partition. just make sure that flash_image and cwm-recovery.img is in the sdk folder, and follow the exact coding as it is written, and u should b fine.

 

[divinebovine]

adb push is done from the Windows command prompt, not from the phone's linux prompt. Any command beginning with 'adb' is run on your computer at a "C:\{whatever}\>" prompt.

C:\Program Files\sdk-tools>adb push flash_image /sdcard/android/data/flash_image

 

[varenHjames]

i wish someone would edit the instructions, so to tell to install sdk to the main directory of c:\\ so that the file path to run adb would be
cd c:\\android\platform-tools
i dont remember if i added the folder android as the root folder....but regardless. installing to the program folder only makes it entirely harder to manage all around.
all i know after some work, and READING the rest of the forum with help from google i was able to do it.
im not sure where sdk tools is, and if its the updated version of sdk....but yes, like they said you have to have the files you want to push in the platform-tools folder
find your platform tools folder, add the files you want to push, IE the recovery files, then navigate to it on command prompt, then
type adb devices (i dont know why this didnt work in your example)
then you should be able to push them to the correct directory.
like i said dude, this thread has a ton of replys, im sure someone has addressed this before. im just glad these guys are patient and will explain it again.

 

[divinebovine]

i wish someone would edit the instructions, so to tell to install sdk to the main directory of c:\\ so that the file path to run adb would be
cd c:\\android\platform-tools

Just add it to your path. Then you don't need to CD anywhere.
Instructions from http://www.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/ :

1. Go to the Control Panel, and select the System Properties (Windows XP) or System (Windows Vista/7).
2. Select the Advanced settings. (On Windows XP: Click on the Advanced tab. On Windows Vista/7: Click on Advanced system settings on the left.)
3. Click on Environment Variables.
4. Under the

 

[SimsKITblue]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>cd "\program files\sdk-tools"

C:\Program Files\sdk-tools>adb devices
List of devices attached
OTA100002648C2DC device


C:\Program Files\sdk-tools>adb shell
$ su
su
# adb push flash_image /data/local/tmp/flash_image
adb push flash_image /data/local/tmp/flash_image
adb: not found
# adb push flash_image /sdcard/android/data/flash_image
adb push flash_image /sdcard/android/data/flash_image
adb: not found
#


I had placed the recovery files in sdk first and it didnt work so i downloaded the mini-sdk "sdk-tools" that allowed me to get as far as i have and the files are not found. so now i am simply stumped. I took a nap ate some dinner and i am just lost.

 

[divinebovine]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>cd "\program files\sdk-tools"

C:\Program Files\sdk-tools>adb devices
List of devices attached
OTA100002648C2DC device


C:\Program Files\sdk-tools>adb shell
$ su
su
# adb push flash_image /data/local/tmp/flash_image
adb push flash_image /data/local/tmp/flash_image
adb: not found
# adb push flash_image /sdcard/android/data/flash_image
adb push flash_image /sdcard/android/data/flash_image
adb: not found
#


I had placed the recovery files in sdk first and it didnt work so i downloaded the mini-sdk "sdk-tools" that allowed me to get as far as i have and the files are not found. so now i am simply stumped. I took a nap ate some dinner and i am just lost.

You must have missed this post:

adb push is done from the Windows command prompt, not from the phone's linux prompt. Any command beginning with 'adb' is run on your computer at a "C:\{whatever}\>" prompt.

C:\Program Files\sdk-tools>adb push flash_image /sdcard/android/data/flash_image

 

[SimsKITblue]

No. I have read that post and every single post in this tread two or three times. i have been running it from my computer since i realized i wasn't supposed to turn on USB storage and only needed usb debugging enabled. i have to have pdanet turned on on my phone before i connect to avoid an error. and i get further with pdanet turned on my computer as well is it supposed to say "not found" or is it supposed to be blank"

will i really brick my phone if i download the two files to my computer connect my phone and move the two files to the sdcard and then use ROM toolbox to simply move them to the data/local/tmp directory with root browser?
and then while still connected run fastboot.exe on my computer. while in the adb shell mode from the command prompt

 

[Dracable]

there is definately a chance. rom manager is not compatible with our phones right now. i dont understand why you would want to do it that way. u would b taking a bunch of extra and unnessessary steps. the adb method still isnt working?

 

[Dracable]

what error are u getting when u try to connect to the computer without pdanet turned on on ur phone?

edit: nevermind. i saw the error. just missed it thru the first read. the very first time i had flashed cwm, i did it thru fastboot. read up on how to flash recovery thru fastboot.

 

[SimsKITblue]

no it isnt working. i deleted and redownloaded everything moved the SDK AND sdk-tools fileS from proGRAM files to c:/.

I continued through with the commands regardless of the "file not found" response and nothing.
i get get the error HTC sync error = -1 but that is with pdanet turned on my phone.

in command prompt it doesn't read the phone at all and the list is blank.

 

[Shabbypenguin]

i wish someone would edit the instructions, so to tell to install sdk to the main directory of c:\\ so that the file path to run adb would be
cd c:\\android\platform-tools
i dont remember if i added the folder android as the root folder....but regardless. installing to the program folder only makes it entirely harder to manage all around.
all i know after some work, and READING the rest of the forum with help from google i was able to do it.
im not sure where sdk tools is, and if its the updated version of sdk....but yes, like they said you have to have the files you want to push in the platform-tools folder
find your platform tools folder, add the files you want to push, IE the recovery files, then navigate to it on command prompt, then
type adb devices (i dont know why this didnt work in your example)
then you should be able to push them to the correct directory.
like i said dude, this thread has a ton of replys, im sure someone has addressed this before. im just glad these guys are patient and will explain it again.

why should that have to be edited? you are talking about moving two or three folders. if you really wanted to be lazy you could just hold shift and right click in a window, the option to open command prompt will be there. ergo destroying any "hardness" of what you are talking about.

or just setup the path properly like divine pointed out

 

[SimsKITblue]

well i tried something different and got this far recovery is having an issue.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>cd "\sdk_tools"
The system cannot find the path specified.

C:\Documents and Settings\Owner>cd "\sdk-tools"

C:\sdk-tools>adb devices
List of devices attached
OTA100002648C2DC device


C:\sdk-tools>adb shell
$ su
su
# adb push flash_image /data/local/tmp/flash_image
adb push flash_image /data/local/tmp/flash_image
adb: not found
# exit
exit
$ exit
exit

C:\sdk-tools>adb device
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.

C:\sdk-tools>adb push flash_image /data/local/temp/flash_image
646 KB/s (72352 bytes in 0.109s)

C:\sdk-tools>adb push cwm-recovery.imp /data/locla/temp/recovery.img
cannot stat 'cwm-recovery.imp': No such file or directory

C:\sdk-tools>adb shell chmod 755 /data/local/temp/flash_image

C:\sdk-tools>adb shell
$ su
su
# /data/local/temp/flash_image recovey /data/local/temp/recovery.img
/data/local/temp/flash_image recovey /data/local/temp/recovery.img
error opening /data/local/temp/recovery.imgfailed with error: -1
# /data/local/temp/flash_image
/data/local/temp/flash_image
usage: /data/local/temp/flash_image partition file.img
# reovery /data/local/temp/recovery.img
reovery /data/local/temp/recovery.img
reovery: not found
# /data/local/temp/revocery.img
/data/local/temp/revocery.img
/data/local/temp/revocery.img: not found
#