1. imekul's Avatar
    I had CM7 on my Optimus S, and I was trying to downgrade the radio as per this thread (http://forums.androidcentral.com/lg-...available.html), and after I did Step A (applied the update.zip) I could no longer get the phone to boot up.

    I see the Sprint splash screen, but then the phone seems to stay at the "Android" screen for a long, long time, and never goes anywhere. I've tried multiple battery pulls.

    I am able to get to the stock recovery, but I don't know what to do there.

    I backed up my data, so I'm not worried about that. I'm just trying to figure out the best way to get a functioning phone again. Any suggestions?
    04-09-2012 01:51 PM
  2. Xmb941's Avatar
    Did You Apply Update.zip In Custom Recovery Or Stock?
    04-09-2012 02:01 PM
  3. eletendre84's Avatar
    if you had CM7 on your phone, you were already on ZVD. I am curious as to what you were trying to accomplish?
    04-09-2012 02:03 PM
  4. hlxanthus's Avatar
    Verify the zvd update.zip is on the root of the SD card (not in any folder) and is named update.zip

    Boot to xionia/ stock recovery, perform a wipe data/ factory reset. Really apply zvd update.zip and reboot

    Sent from my LS670 using Tapatalk
    04-09-2012 02:04 PM
  5. imekul's Avatar
    I should have thought of wiping the data/cache afterwards! Wiping it from stock recovery fixed it.

    I applied the update.zip from the custom recovery initially. My goal was to fix a problem my mom was having with this Optimus S. She would intermittently miss phone calls (the phone wouldn't even ring), and I didn't know if it could be a CM7 or a baseband problem.

    I thought it may possibly have something to do with baseband because it showed "Unknown" under the baseband version on the phone.
    04-09-2012 02:17 PM
  6. garwynn's Avatar
    I had the same problem with my wife's phone yesterday... pulled the battery, put it into recovery and then did a factory reset. She was previously on HydroRom.
    04-09-2012 02:27 PM
  7. czifro's Avatar
    I had the same issue with bootloop on "ANDROID" as well as my uncle. it took a factory reset to fix this.
    04-09-2012 04:13 PM