• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Optimus v stuck on "android system recovery" after data reset!

i'm stuck at step 4? i downloaded the Stock optimus v rom the one with the 2 folders and 1 boot.img file and i placed them on my SD card and put

adb push f:/boot.img and a bunch of words come up and then
adb shell and then i have a # symbol after and won't let me use adb reboot recovery.

where do i have the push the ROM? on the sd card? or on the computer. i have the 3 files in a folder.

c:/android-sdk-windows/rom/ (3 files here)

i've also put them on the root of my SD card. so what do i gotta type after
ADB PUSH??

i tried so many different combinations like
c:/android-sdk-windows/room/boot.img f:/boot.img?
 
I'm sorry, there was a typo in line 6, you only type reboot recovery, no adb.

Step 5 (adb shell) will open a shell inside your phone, the # sign indicates you do indeed have root. Inside the shell your type "reboot recovery" and your phone should reboot to recovery so you can flash the ROM you "push"ed.
 
ohh ok. i'm still at the Push part lol. i don't know how to push the rom? do i have to have it in phones sd card or on computer
 
not getting no where. i'm stuck at the ADB push. or the ADB Connect part
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>c:\android-sdk-windows\platform-tools\adb.exe
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
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 ocmmand 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 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.

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:\Users\Chris>adb connect
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Chris>adb connect
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Chris>cd c:\android-sdk-windows\platform-tools

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb conneect
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
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 ocmmand 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 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.

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:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:/android-sdk-tools\rom \sdcard
cannot stat 'c:/android-sdk-tools\rom': No such file or directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom \sdcard
cannot stat 'c:\android-sdk-tools\rom': No such file or directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom\boot.img
\sdcard
cannot stat 'c:\android-sdk-tools\rom\boot.img': No such file or directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom\boot.img
/sdcard
cannot stat 'c:\android-sdk-tools\rom\boot.img': No such file or directory

c:\android-sdk-windows\platform-tools>
Click to expand...
 
You don't execute adb.exe, you use it via the command line.

On your PC, press Windows and type command then press enter. This will open a command window, usually under c:/user/YOUR_USERNAME

Use the cd directive to navigate to the folder containing adb.exe by typing:
cd c:\android-sdk-windows\platform-tools\

Now on your phone, press the menu key, then settings>>applications>>development and make sure USB debugging is checked. Then hook your phone up to your PC via USB.

Next, in the command window, type: adb connect

Once it connects to your phone, type: adb shell

You should now be in an adb shell in your phone via your PC. If you see a $ sign, you are not rooted, type exit, then try using SuperOneClick.exe to get a shell root, it may take several tries, you need to see a # sign when you type adb shell.

Once you are in an adb shell with #, your ready to follow the steps as posted. Seems your confusion was in not reading up on how to use ADB.
 
yeah i am confused. the problem is this

Now on your phone, press the menu key, then settings>>applications>>development and make sure USB debugging is checked. Then hook your phone up to your PC via USB
Click to expand...

i can't even get on the phone it does and endless recovery boot. it won't even boot up to android :(
 
when i hit ADB connect is that this

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

C:\Users\Chris>c:/user/chris
The system cannot find the path specified.

C:\Users\Chris>cd c:\android-sdk-windows\platform-tools\

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>
Click to expand...
am i right so far?
 
i am so damn lost :( ughh

c:\android-sdk-windows\platform-tools>adb push c:/android-sdk-windows/platform-t
ools/rom/boot.img \sdcard
cannot stat 'c:/android-sdk-windows/platform-tools/rom/boot.img': No such file o
r directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-windows\rom\boot.i
mg \sdcard
3843 KB/s (3565568 bytes in 0.906s)

c:\android-sdk-windows\platform-tools>adb shell
/ # reboot recovery
reboot recovery

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-windows\rom
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
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 ocmmand 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 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.

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:\android-sdk-windows\platform-tools>adb push c:\android-sdk-windows\rom\boot.i
mg \sdcard
4698 KB/s (3565568 bytes in 0.741s)

c:\android-sdk-windows\platform-tools>adb shell
/ # reboot recovery
reboot recovery

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-windows\rom\ \sd c
ard
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
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 ocmmand 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 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.

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:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom \sdcard
cannot stat 'c:\android-sdk-tools\rom': No such file or directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom\ \sdcard

cannot stat 'c:\android-sdk-tools\rom\': No such file or directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom /sdcard
cannot stat 'c:\android-sdk-tools\rom': No such file or directory

c:\android-sdk-windows\platform-tools>c:\android-sdk-tools\rom\boot.img \sdcard
The system cannot find the path specified.

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom\boot.img
/sdcard
cannot stat 'c:\android-sdk-tools\rom\boot.img': No such file or directory

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-tools\rom\ \sdcard

cannot stat 'c:\android-sdk-tools\rom\': No such file or directory

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:/android-sdk-tools/rom /sdcard/
boot.img
cannot stat 'c:/android-sdk-tools/rom': No such file or directory

c:\android-sdk-windows\platform-tools>
Click to expand...
 
You're close, I think this will work:

Connect as you have been with adb, to test connection type adb shell and if you have the # sign, continue...

Type cd sdcard

Type ls

You should see a list of your sdcard's contents. Look for the boot.img file you pushed before, you just need to confirm it is there, if it is continue...

Type flash_image recovery boot.img

Type reboot recovery

Your phone hopefully will now reboot into the new recovery. If so, use the adb push command to push a new ROM zip file onto your sdcard, then in recovery choose install zip from sdcard, choose the ROM zip, let it load, go back to main menu, and reboot.
 
i typed that and i didn't get a list. i don't know why. when i download the stock rom from google i have these 3 files

META-INF (folder)
System (folder)
Boot.IMG

so i could have to push Just the BOOT.IMG?

here's what i've done

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

C:\Users\Chris>cd c:/android-sdk-tools/platform-tools
The system cannot find the path specified.

C:\Users\Chris>cd c:\android-sdk-tools\platform-tools\
The system cannot find the path specified.

C:\Users\Chris>cd c:\android-sdk-windows\platform-tools\

c:\android-sdk-windows\platform-tools>adb shell
error: protocol fault (no status)

c:\android-sdk-windows\platform-tools>adb shell
/ # cd sdcard
cd sdcard
/sdcard # ls
ls
/sdcard # adb push c:\android-sdk-windows\rom\boot.img \sdcard
adb push c:\android-sdk-windows\rom\boot.img \sdcard
/sbin/sh: adb: not found
/sdcard # exit
exit

c:\android-sdk-windows\platform-tools>adb connect
Usage: adb connect <host>[:<port>]

c:\android-sdk-windows\platform-tools>adb push c:\android-sdk-windows\rom\boot.i
mg \sdcard
4481 KB/s (3565568 bytes in 0.777s)

c:\android-sdk-windows\platform-tools>adb shell
/ # cd sdcard
cd sdcard
/sdcard # ls
ls
/sdcard #
Click to expand...
 
For anyone reading this very confusing thread, we got it working. It was a simple oversight, the sdcard was not mounting automatically. We both are on W7 machines, so we used remote assistance, he hooked the phone up to his computer while it was in recovery, he used the recovery selection for usb mass storage.

I used a command window and adb to access his phone, here are the commands I used:

>adb shell
/ # mount /sdcard
/ # cd /sdcard
/ # ls
this showed the contents of the sdcard, confiming the boot.img file was there
/ # flash_image recovery boot.img
/ # reboot recovery
/ # exit
>exit


After this, the phone rebooted, and cvc7chris is testing it out now.

Mods- you may want to delete this thread, it is very confusing.
 
defenetly works. i just think he flashed the sprint rom by accident? haha i have all the virgin mobile apps but the "home" and "menu" are flipped
 
Worked perfectly. Really like the clockwork recovery but learned my lesson -- NEVER use the android reset. Just would loop into recovery no matter what I tried. This was the fix. Thanks. :)

JerryScript said:
For anyone reading this very confusing thread, we got it working. It was a simple oversight, the sdcard was not mounting automatically. We both are on W7 machines, so we used remote assistance, he hooked the phone up to his computer while it was in recovery, he used the recovery selection for usb mass storage.

I used a command window and adb to access his phone, here are the commands I used:

>adb shell
/ # mount /sdcard
/ # cd /sdcard
/ # ls
this showed the contents of the sdcard, confiming the boot.img file was there
/ # flash_image recovery boot.img
/ # reboot recovery
/ # exit
>exit


After this, the phone rebooted, and cvc7chris is testing it out now.

Mods- you may want to delete this thread, it is very confusing.
Click to expand...
 
I also did the same things....but everytime it would boot into the recovery can you please also connect to me remotelyand help me. plzzz i would really apppreciate it.
 
shahrukhkhan said:
I also did the same things....but everytime it would boot into the recovery can you please also connect to me remotelyand help me. plzzz i would really apppreciate it.
Click to expand...
It's all right,you don't need remote assistance(unless you just absolutely have to) ,someone can talk you through it. What recovery do you have.Thunderc,Xionia,or CWMod EDIT: If nobody else has a chance to help you I'll be back on in 5hours. Got to go help people with there understanding of Gods word.
 
Whyzor said:
Just flash this Xionia recovery from within your current recovery (like a ROM .zip).

Xionia_CWMA_12518.4_VM_Recovery.zip

Then using the new xionia recovery flash a working ROM.
Click to expand...
I now vaguely remember seeing that fix somewhere before. I hate getting older. I still haven't seen enough problems,and there fixes to help everybody just yet. But that's the great thing about this Forum. Everybody helps everybody. Thanks for the help. I was running around in two site's trying to find a fix for one problem and almost forgot about shahrukhkhan
 
i had the xionia recovery. then i reset the phone. it was working fine. i was scrolling through the mailbox. and suddenly the screen blinked and the phone restarted. and booted into the recovery. its a custom recovery. build: RA-thunderc-1.1.0-GNM. what ever i do it just boots up in this recovery. and i also cannot connect to superone click because when i try to its starts to not respond
 
shahrukhkhan said:
i had the xionia recovery. then i reset the phone. it was working fine. i was scrolling through the mailbox. and suddenly the screen blinked and the phone restarted. and booted into the recovery. its a custom recovery. build: RA-thunderc-1.1.0-GNM. what ever i do it just boots up in this recovery. and i also cannot connect to superone click because when i try to its starts to not respond
Click to expand...

See here:

http://androidforums.com/optimus-v-...4-do-not-factory-reset-your-rooted-phone.html

Use my link I provided a few posts back to the recovery .zip because their's is broken.
 
ok my situation is different! I rooted my phone using romtools and flashed everything just fine I loaded 2.3.7 from bobzhome and everything worked great! I was experiencing signal drop and thought maybe it was the new rom acting up so i did a restore back to when i first installed the rom. and when i did this my phone went back to the 2.2 platform. after that i tried to wipe the delvik cache and lg wipe. after doing that and reinstalling the rom.
my phone now will start up in android system recovery then reboot and function. the kernel version is 2.6.32.9-v3.11 and android 2.3.7 from bobzhome.
every time i restart the phone its like its a new install. when i try to restart it in custom recovery it goes only through androids system recovery I've tried some of the suggestions with no luck! I can still use my phone but i cant store contacts or apps to my phone cuz i lose them when i restart my phone. HELP I'm new and dont know a lot of what im doing with this thats why it seemed right to use the romtools app cuz it gave step by step directions and I didnt have to use commands.
 
You must log in or register to reply here.
Back
Top Bottom