Optimus V Will Not Boot Into Recovery

buckie bo

Active member
Nov 4, 2010
32
0
0
Hi all.

Im sorta stumped one this one. I have found a couple other threads in the forums where this has happened and some have got out of it, some not!

Had this phone a couple of months run CM7 mod...never activated. Decided to activate for our kids before Virgin has the price increase next week. Bought card, etc...tried to activate..no dice.

Decided to go back to original stock rom, activate and then root and update from there. Problem is, this phone will not go into recovery. I have spent the better part of the last 5 hours working on this and while the phone boots up and operates just fine, when trying to go into a recovery..it hangs on the LG screen

I have attempted to flash another recovery, flash another rom, nada. Used various methods and recoverys, nothing will take.

I have no clue what was done to the phone or what happened to it. It could have been like this a month or more but, unless you had to go to recovery or try to activate the phone, you would never know there is a problem.

Any ideas of what I can do to get this thing back up? Wish I had not posted that topup card on this account now but, what can yah do?
 
Since you posted the S forums, did you also flash an S recovery? S rom? S firmware?
 
This is exactly what just happened to me.
Use the recovery ( recovery-RA-GNM-thunderc-s-1.1.0.img) this guy has in his folder.. Actually do EVERYTHING this guy says in the video.

[/YOUTUBEHD] ‪Root optimus v part 1‬‏ - YouTube
Recovery fixed for me that way. hope it helps yo.
 
Last edited:
It's pretty much accepted that the Xionia recovery is among the best (supports most/all available ROMs for Optimus V).

How are you attempting to enter Recovery Mode? With the phone off, hold Home, Volume Down, and the Power button. If that doesn't work, does a "reboot recovery" command work in adb? If you have a supporting ROM, there may also be the option in the phone's shutdown menu to reboot into recovery. And finally, you can try to "reboot recovery" in a root terminal emulator. Have you tried these options?
 
Sorry guys, I wasnt paying attention..posted to the wrong forum, my bad!

I was attempting the "fix" that Bluntsworth mentioned (thank you)

Something else screwy here. The computer can see the V...the V can see and is connected to the computer and shows as "usb connected" but, the computer doesnt allow me to access the V or the SD card.

Tried this on 3 other computers..same thing. Drivers are installed on all 3 computers and have worked in the past when transferring files.

I assume this issue is being caused by the problems the phone is having going into any type of recovery.
 
It's pretty much accepted that the Xionia recovery is among the best (supports most/all available ROMs for Optimus V).

How are you attempting to enter Recovery Mode? With the phone off, hold Home, Volume Down, and the Power button. If that doesn't work, does a "reboot recovery" command work in adb? If you have a supporting ROM, there may also be the option in the phone's shutdown menu to reboot into recovery. And finally, you can try to "reboot recovery" in a root terminal emulator. Have you tried these options?

Yes, vol down/home'pwr up, the reboot into recovery from within rom manager and when powering off in the menu. I also tried to use Romtools to see if I could do anything with that..no go
 
Sorry guys, I wasnt paying attention..posted to the wrong forum, my bad!

I was attempting the "fix" that Bluntsworth mentioned (thank you)

Something else screwy here. The computer can see the V...the V can see and is connected to the computer and shows as "usb connected" but, the computer doesnt allow me to access the V or the SD card.

Tried this on 3 other computers..same thing. Drivers are installed on all 3 computers and have worked in the past when transferring files.

I assume this issue is being caused by the problems the phone is having going into any type of recovery.
Are you turning on USB Storage from the notification bar? By default, plugging into a USB port will say "USB Connected" and simply just charge. You have to enable USB Storage to see the SD card mounted. Sorry if this basic stuff is stuff you've already tried, but you are not really telling us what you have done so I'll continue with the basics first. :)
 
Sorry guys, I wasnt paying attention..posted to the wrong forum, my bad!

I was attempting the "fix" that Bluntsworth mentioned (thank you)

Something else screwy here. The computer can see the V...the V can see and is connected to the computer and shows as "usb connected" but, the computer doesnt allow me to access the V or the SD card.

Tried this on 3 other computers..same thing. Drivers are installed on all 3 computers and have worked in the past when transferring files.

I assume this issue is being caused by the problems the phone is having going into any type of recovery.

I don't really know man.
You said yours would hang at lg logo..
Well When My recovery got messed up it would hang at the fastboot root blue screen.
Try installing FastbootRoot (patent not pending) for the virgin mobile optimus v
If its not that, check your usb cable that its not the one for the intercept. lastly you can try to identify your device from device manager somehow?
That's all I got..did it work?
 
Yes, I can USB on via notification..then click on the icon to turn on the storage.

Now, when I did this earlier, I could not access the SD card on any pc. After I did a battery pull and plugged it back in. I can now access the SD card and yes it is mounted now and was earlier..pc just would not allow me to access it.

After the latest of many battery pulls today, it still fails to boot into recovery. Also, it looks like there is very little on the SD card now. I know when I worked on this when we first gave it to them, there were a dozen or more files/folders on the SD card..now..there are three folders.

Is it possible that one of the kids popped this card out and it is now corrupt? Dont think that would effect it booting into recovery but, the contents of the SD card are not what they were.
 
Assuming you are already rooted, just reflash the recovery.

Place the file flash_image inside the /system/bin folder and set the permissions:
Code:
adb remount
adb push flash_image /system/bin
adb shell
su
chmod 777 /system/bin/flash_image

Or through terminal emulator (app from the market) after copying flash_image to the SD card:
Code:
su
mount -o remount,rw -t yaffs2 /system /system 
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image

Once you have that binary in place, you can flash a new recovery after placing the recovery onto the SD card and naming it vrecovery.img:
Code:
adb shell
su
flash_image recovery /sdcard/vrecovery.img
reboot recovery

Terminal emulator:
Code:
su
flash_image recovery /sdcard/vrecovery.img
reboot recovery
 
Last edited:
I have terminal emulator on the V so that isnt a problem...the problem is, I have no system folder on the sd card now

I have 3 folders media, android and lost.dir

There are no sub-folders or hidden files in those three folders.

They have screwed this phone havent they?
 
I have terminal emulator on the V so that isnt a problem...the problem is, I have no system folder on the sd card now

I have 3 folders media, android and lost.dir

There are no sub-folders or hidden files in those three folders.

They have screwed this phone havent they?

There isn't supposed to be any system folder on the sdcard. Your sdcard is /sdcard/. Your system folder is /system/. And / is the root of your phone.

Follow the directions, and it'll work.
 
Ok, my mistake..on the sys folder

Ok, installed the flash image to sd card

start terminal emu and as soon as I go for su, SU crashes and asks if I am rooted.

Ran superoneclick again to verify it is rooted and it is...what am I missing here?

Granted I havent kept up with things since I first got this for them but, sheeze, either I have forgotten what I have done or ??
 
Ok, my mistake..on the sys folder

Ok, installed the flash image to sd card

start terminal emu and as soon as I go for su, SU crashes and asks if I am rooted.

Ran superoneclick again to verify it is rooted and it is...what am I missing here?

Granted I havent kept up with things since I first got this for them but, sheeze, either I have forgotten what I have done or ??

Crashes or asks to give terminal emulator for root access? Do you have superuser installed? Is terminal emulator on the list of allowed apps in superuser?

If terminal emulator already has "#" at the beginning instead of "?" then you can skip the "su" portion of the directions.
 
This thing is getting crazier each time I attempt to do something.

Last night, it would say permission denied and then "crash" or exit out of TE

This morning, it took me several reboots to get it to where I could even type in TE

Here is where I attempted to use terminal emulator..does this look correct?


$ export PATH=/data/local/bin:$PATH
$su
# mount -o remount ,rw -t yaffs2 /system /system
BusyBox v1.17.2 (2010-09-05 03:37:08 CDT) multi-call binary.

Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE

Mount a filesystem. Filesystem autodetection requires /proc.

Options:
-a Mount all filesystems in fstab
-f Dry run
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification time
[no]dev (Dis)allow use of special device files
[no]exec(Dis)allow use of executable files
[no]suid(Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slaveConvert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a file or directory to another location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing flags
ro/rw Same as -r/-w

There are filesystem-specific -o flags.

# cat /sdcard/flash_image > /system/bin/flash_image
cannot create /system/bin/flash_image: read-only file system
# chmod 755/system/bin/flash_image
BusyBox v1.17.2 (2010-09-05 03:37:08 CDT) multi-call binary.

Usage: chmod [-Rcvf] MODE[,MODE]... FILE...

Each MODE is one or more of the letters ugoa, one of the
symbols +-= and one or more of the letters rwxst

Options:
-R Recurse
-c List changed files
-v List all files
-f Hide errors

#
 
Ok, it did work and I finally was able to get it to boot to recovery...THANK YOU!

I am trying now to get this back to stock but, when trying to flash the stock flash from the sd card,
I am getting a signature verification error.

Will try to troubleshoot that today while I work and see what becomes of it
 

Trending Posts

Members online

Forum statistics

Threads
956,975
Messages
6,970,879
Members
3,163,677
Latest member
bohanvo2