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

Root The Truth About ROM Manager

Go back to the recovery and wipe cache partition then go to advanced section and choose to wipe dalvik cache. Reboot phone then turn off. Turn router off. Wait 10min. Turn both on and sign into your WiFI network making sure the password is correct. If you don't get the password right then select to ignore network and try again.
 
Gave the clearing and rebooting/unplugging a try. Did the unplug for about 2 minutes. Restarted everything. In the morning I'll try the same with a 10 minute power off attempt to see if the added time does anything. When I try to connect to my wifi it just says "obtaining IP address" for a while then starts over and tries again. It was the rom titled "BACKside-IHO-VM670-12212011".
Just so you know, I never had any issue with the wifi prior to the rom flash this morning.
 
Let me know the exact steps you took in your recovery just prior to the ROM install.
There are no WiFi issues with the ROM. Your problems might stem from not formatting or wiping something that was necessary. The ROM download could have gotten corrupted. It happens sometimes.
 
I tried to follow the instructions you had in another post. I did have the zips in a folder called download instead of the root of the sd and originally tried to use clockwork recovery. I restored my backup of the stock rom, then tried to do the whole thing over. The second go round I moved the zip to the root and used the recovery that starts with an x (sorry I forgot the name, I've been doing this for just a week). I am not 100% sure I did it all correct. I got the same result (wifi would not go past obtaining ip). I probably did something dumb I'm sure. I restored the stock rom again and downloaded the picasticks 07 a zip and put that kernel on the stock rom so I can overclock. I think I'm good for now. Someday I'll come back to the custom rom and retry it, but just the overclocked stock situation will be alright for now.
 
Sorry we couldn't be more help. Just for laughs and grins download AFV(Android File Verifier). When you go to a site that has a ROM, write down the md5 sum. After it's downloaded go to the app and select "select file". Long press the ROM.zip. Select the first option.
The md5 sum should match the one in the ROM site.
 
If stock will connect but no custom rom does, then it can't be hardware. It's either a bad download of the rom, or there's some junk data hiding in there that didn't get wiped properly. Either way, I ran stock rooted for quite some time, and had good results.
 
That's what I was thinking as well. JerryScript worked the WiFi bug out of his ROM months ago, nobody's had any complaints about it since.
 
Wait for bigsupersquid to contact you. You have a brick that can only be saved by cramming the S firmware into your phone using the emergency mode.
I know this because my first "V" is a brick. I have tried every devised fix there is and none will work for phones like ours with no working recovery and a borked system that will not allow a PC to recognize it.
Non of the firmware for the V works at all, not the ZV4 nor the ZV5.
 
Thanks in advance to AndyOpie150 for reviewing my issue briefly, and I posted it here as requested.

I recently bought a LG Optimus V that was rooted while 2.2.2 was installed. I tried to backup the BACKside ROM that was initially installed so far with no issue. I was using the flash option with ROM Manager.

Right now all the phone does is go to the BACKside ROM screen with the Android icon and a rotating green circle, and then the circle freezes. During the backup process with ROM Manager it prompted for model and LGE Optimus V was selected. I think that is what started things to go bad perhaps.

If I try to hold down the Home, Volume Down button, and Power button it briefly shows LG icon, and then once gone nothing happens.
I read that for 2.2.2 I can't use ROMTools to try to unbrick though.
http://androidforums.com/optimus-v-...-things-root-guide-updated-27-jan-2012-a.html

I do have the same exact phone that has not been touched if that helps review issues for the messed up one as well. I have made no attempt to install any sort of recovery, and run it out of concern I may make things worse assuming anything is left to try to fix the phone.
 
AndyOpie150 said:
Do you have a PC with the LG drivers installed, and ADB established in your system path?
Click to expand...

Yes I have LG Optimus V drivers on my pc. The Android SDK Manager was downloaded, and setup but is currently located not in the root but in:

C:\Program Files (x86)\Android\android-sdk


I understand how to use cd directory in command prompt but I don't feel very comfortable yet in using this software and/or I probably did something wrong. I could reinstall it directly onto the root of my C drive if that helps simply things.
 
AndyOpie150 said:
Ok go here [FIX]Black screen with custom recovery and custom roms - Page 15 - Android Forums at AndroidCentral.com
Follow the instructions to the t.
The adb.exe is in SDK/platform-tools
Click to expand...

Ok I am within command prompt loaded into folder: C:\SDK\platform-tools

The next steps states I can then type the following in the command line:
Code:
adb shell strings /dev/mtd/mtd8
adb shell flash_eraseall /dev/mtd/mtd8
adb reboot recovery

I'm not clear if I should have the phone connected to the computer just right before I run those commands or not since the next steps states to let it reboot. (The phone normally will lock up once reaching the Android icon with spinning green circle within a few rotations of the circle animation).

I was not sure if the author mean this would be the computer rebooting or the phone, and wanted to make sure I was following the steps correctly.
 
The phone needs to be plugged into the pc before you go to the adb.exe.
Let me pull that up on another page and double check.Edit:yes plug in.
 
AndyOpie150 said:
The phone needs to be plugged into the pc before you go to the adb.exe.
Let me pull that up on another page and double check.Edit:yes plug in.
Click to expand...
Results from Command Line:

C:\SDK\platform-tools>adb shell strings /dev/mtd/mtd8
error: device not found

C:\SDK\platform-tools> adb shell flash_eraseall /dev/mtd/mtd8
error: device not found

C:\SDK\platform-tools> adb reboot recovery
error: device not found


I ran it thru more than once but it looks like it is not finding the phone for some reason to run thru the commands at all. The phone locks up on the Android icon pretty quick too which does not help. Perhaps issue(s) with the installed drivers I have for the phone? I am using Windows 7 if that matters.

Update: I checked with: Control Panel\All Control Panel Items\Devices and Printers and it shows LG Android Phone so it seems Windows is detecting the phone ok there at least.

Trying as linked at bottom of the guide if still have issues to follow these instructions to get it working Pre-packaged ADB Fix:
http://www.support-4-you.com/main/i...e-packaged-adb-sdk&catid=40:how-tos&Itemid=57

Now able to load into ADB Devices from command line. Shows Android Debug Bridge version 1.0.26
However the three commands I was suppose to run earlier still all fail with:
error: device not found

Ran command: adb devices It shows:
List of devices attached
A10000199FA4A3 recovery

Ran command: adb bugreport It shows:
/sbin/sh: bugreport: not found

The current recovery.img that was copied to the C:\SDK\platform-tools folder is: xionia_cwma_12518.6


Thanks again for your help so far AndyOpie150, and I'll work on reviewing this further Tuesday afternoon EST. Certainly made it further than I expected I would be lucky enough to see so far.
 
Pull battery. Hold power button down 30 sec. Reinstall battery, turn power on.
Try commands again.
It was in recovery mode. Needs to be in boot, not recovery.
Sorry, went to lala land.
 
AndyOpie150 said:
Pull battery. Hold power button down 30 sec. Reinstall battery, turn power on.
Try commands again.
It was in recovery mode. Needs to be in boot, not recovery.
Sorry, went to lala land.
Click to expand...

Using command: adb shell strings /dev/mtd/mtd8
doesn't give an error, and goes back to the initial command line folder path

However if I select to run the next command: adb shell strings /dev/mtd/mtd8 I am shown error stating:
flash_eraseall: not found

The SD card currently does not have ROM Manager installed on it, and if it helps the current folders shown are:
.android_secure .estrongs Android data LOST.DIR Titanium Backup
Non folder files:
FlashImageGUI.apk GingerBreak-v1.20.apk TitaniumBackup_latest.apk

The SD card was not in the phone while any work on fixing the phone so far has been done. I still have the files for things like ROM Manager that were saved off of the SD card if needing to go back to them though.

One possible glimmer of hope is I found even if the Backside ROM runs thru to the Android icon, and freezes after about 30 seconds there that the command: adb reboot-bootloader will allow for the phone to reboot past that instead of being forced to remove the battery. Most of the time the phone will just show the battery charging icon.

Also using command: adbbugreport
shows me a long list of information while on the frozen android icon with the green circle now. Unclear what info. from it may be useful.

Using command: adb devices
also shows while on the android frozen icon:
List of devices attached
A10000199FA4A3 device
 
You must log in or register to reply here.
Back
Top Bottom