[General Questions and Answers] brightstar2:
SOLVED - LG P506 Trive WORKS - was LG P506 AT&T Thrive Help Request - Post Unroot ...

Thanks to the XDA Forum and users. With it I stitched together a solution and have returned my LG P506 (AT&T Thrive) to good working order with 2.2.2

This was my first Android learner phone, since I would soon need to know Android +/- for work.

Started with a backed up (and backed up) Rooted LG Thrive running 2.2.1 with CWM Recovery. Tried to unroot and return to stock (unfreeze AT&T bloatware, unroot, etc). The AT&T 2.2.2 over-the-air (OTA) was successful, but after reboot the P506 was stuck in a CWM boot-to-recovery mode.

All the fastboot commands, all the CWM recovery commands worked fine. New Custom Stock ROM 2.2.2 re-flashed fine, but the phone would still either boot to CWM Recovery to Fastboot-mode depending on Keys/buttons pressed at boot.

So phone wasn't bricked, but was stuck.

From this XDA forum (this and other XDA forum posting here and there). The Solution was found.

From another LG P506 thread here I got 2 files boot.img and system.img for LG P506 (I did use these files, but perhaps a full custom CWM ROM recovery would be good to -- These are the facts, you can refine)

From the LG Fastboot command I

>fastboot flash boot boot.img

>fastboot flash system system.img

Tried to boot but still stuck at CWM Recovery

POST AFTER POST here says wipe phone more or less. I did wipes with CWM Recovery. I was never really sure how to do enough but NOT TOO MUCH of a WIPE. Too timid as a noob, never tried to fastboot to erase.

LEARNED POINT: fastboot erase is/must-be different than CWM Recovery wipes/formats etc.

The LG P506 was a starter Android phone to learn on, build skill and make mistakes without wrecking an $800 phone.

I had seen another XDA Forum posting about the structure of the phone's file system ... it showed 'system' 'cache' 'userdata' 'misc' 'FOTABIN' 'FOTA' ... plus a few more.

HINDSIGHT: I looked for but could not find a good here is how ANDROID boots for this phone. (1) this .. (2) that ... (3) etc .. kernel, GUI, etc. I suspect I would have learned that something I erased below like FOTA or FOTABIN was running and dying throwing me into CWM Recovery.

I felt I had nothing to loose at this point and no matter what I tried I was (up to that point) still always able to get into CWM Recovery. CWM Recovery ROCKS!

The BREAK THROUGH....

In fastboot mode again.

>flastboot erase FOTA

>flastboot erase FOTABIN

>fastboot erase misc

>fastboot erase cache

>fastboot erase userdata

>fastboot reboot

... there was the LG P506 running 2.2.2 sans the AT&T bloatware. Battery needed recharged, so I took my son to House of Air in the Presidio in San Francisco for trampoline dodgeball.

Nearly 24 hours later the LG P506 Thrive is still working fine.

I suspect that (1) either the boot & system img were needed and something needed erased/wiped.

-- OR --

(2) something like FOTA and/or FOTABIN need erased first and foremost.

As newbie, I was not sure quite what to do at each turn. Using google, I struggled to find insightful android documentation for my problem that was current and not about older versions of ANDROID. The Forum experts use acronyms and speak at an expert-level at times, but the gist of what they shared feels/felt sound. But kind of hard to hear Babe-Ruth explain how to hit a HOME RUN and all together different thing to step into the batter's box and hit a HOME RUN.

Anyhow, the XDA FORUM ROCKS. The experts are EXPERT, I'm unworthy. THANK YOU FOR THE HELP.