Semi bricked? [Resolved!]

RaeFlynne

Active member
Feb 24, 2011
27
0
0
Visit site
Well, lets see here...

I've got the optimus V running the 8/30 build of IHO, and I was running the CWM 3.0.1.4 (Or whatever) recovery.

I was trying to install the recovery listed on IHO page (Blarf's recovery) through Mmarz's ROMtools. I tried two or three times with no change at all. After clearing some stuff off my SD card, and making sure everything else was in order, I ran ROMtools again, and it seemed to work at first. Then my phone booted into the Fastboot blue screen error that I've seen talked about in other threads in this forum.

So, I've been putzing around trying to fix it, but I've run into some weird issues. When I try to flash a new recovery, I get an error saying the directory or file could not be found, which is odd, since I was typing it correctly. I could navigate to the directory and find the file just fine, but couldn't for the life of me get it to flash.
(Note here, I tried putting the file in both /sdcard/vrecovery.img and in /system/vrecovery.img, and neither worked)

So then I tried the Fastbootroot.bat file, and Fastboot couldn't find the device, which, again, is odd. Hmm...
Anybody have some suggestions here?

(Note: My phone works just fine, so I'm not stressing over this TOO hard, but it's a little uncomfortable knowing that if something dies, I won't be able to fix it until I take care of this...)
 
Last edited:

jdcnosse

Well-known member
May 11, 2011
512
44
0
Visit site
Re: Semi bricked? Iunno...

If your phone can boot, then what I would try is flashing the recovery through Terminal on your phone.

Open it up, make sure you're root, navigate to wherever your recovery.img file is and then type (where recovery.img is your recovery file):

Code:
flash_image recovery [I]recovery.img[/I]

and if that works then you're golden :) (hint to reboot into recovery after that, just type "reboot recovery")

if not...well either you don't have flash_image on your phone (it's around here somewhere), or your recovery.img file is borked and I'd try re-downloading it.

Otherwise maybe you messed up your recovery partition...
 

camf3xu

Well-known member
Jun 27, 2011
323
12
0
Visit site
Re: Semi bricked? Iunno...

If your phone can boot, then what I would try is flashing the recovery through Terminal on your phone.

Open it up, make sure you're root, navigate to wherever your recovery.img file is and then type (where recovery.img is your recovery file):

Code:
flash_image recovery [I]recovery.img[/I]

and if that works then you're golden :) (hint to reboot into recovery after that, just type "reboot recovery")

if not...well either you don't have flash_image on your phone (it's around here somewhere), or your recovery.img file is borked and I'd try re-downloading it.

Otherwise maybe you messed up your recovery partition...

what he said but

su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
 

RaeFlynne

Active member
Feb 24, 2011
27
0
0
Visit site
Re: Semi bricked? Iunno...

I tried that as well, actually.

I got the same error. "Cannot locate directory or file"

Which was incredibly odd, considering I was IN the directory, looking at the file! XD

And I've tried a couple different recovery files.
I'll try a fresh copy of flash_image tomorrow, when I feel like dealing with it.
 

RaeFlynne

Active member
Feb 24, 2011
27
0
0
Visit site
Re: Semi bricked? Iunno...

Hmm... Curiouser and curiouser...

It seems that the problem I'm having is with my drivers, but even reinstalling them doesn't seem to do the trick...

Whenever I try to do anything through ADB fastboot, I get the "Waiting for Device" forever bit.
Perhaps I'll try again after I restart my computer next...
 

RaeFlynne

Active member
Feb 24, 2011
27
0
0
Visit site
Re: Semi bricked? Iunno...

ASDF-

Okay. So I've found a couple different drivers for my phone, but it continues to derp itself forever.

When I plug it in after installing the drivers, I get the Windows installing drivers window, and I get a list of devices. Six devices, four are unidentified, and two are the LGE Android Platform Composite USB Device, and the USB Mass Storage device.

These two drivers are marked as "Ready to Use" but the four unidentified devices just sit there and do nothing.
Argh.
[EDIT] As soon as I posted this, three of the unidentified drivers installed, but one did not
 

RaeFlynne

Active member
Feb 24, 2011
27
0
0
Visit site
Re: Semi bricked? Iunno...

Alright. So, it seems that there's a driver missing for "Android" which is what the device is named when in the Fastboot screen.

Anybody have some helpful advice here? I've got literally no clue at this point, but I feel like if I can just get this driver, I can fix my phone. >_<

OH. Also, I've found out that what I might need to do is

fastboot erase recovery

Then push a new recovery in. I plan to push CWM back in, but at the moment the entire recovery is broken.
 

RaeFlynne

Active member
Feb 24, 2011
27
0
0
Visit site
Re: Semi bricked? Iunno...

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA-

I FIXED IT!

YES!

YES!
*Screams from the highest mountaintop!*

This entire time, I was trying to run
flash_image recovery /sdcard/vrecovery.img

When I REALLY needed to run
flash_image recovery /mnt/sdcard/vrecovery.img


YES AAAAAAAAAAAH!