Originally Posted by dudeimgeorge
oh god. i will now live under a rock for the remainder of the day.
(have been wasting my time doing this on the tmobile SG2..thinking vibrant was its nickname)
i am so SOOO sorry for wasting your time. thank you though, regardless.
(btw, now since i changed the build.prop to that of which you created FOR the vibrant, will this phone have issues! haha...oh god, what have i done)
You have some options. Re-flash the rom you are currently running. If you don't wipe data/factory default, then everything should just work again without losing any data or apps.
Second option, if you made a nandroid backup, just restore it, and all should be good.
Otherwise, if you tell me what rom you are running, I can download it, and grab a build.prop to make a quick cwm flashable for you.
EDIT: The best option above is #2, if not #1. Last choice would be to just restore a build.prop, since I'm not sure if CWM did anything else to your partitions.
I believe, status 7 errors are usually an indicator that CWM Recovery is trying to flash stuff to the wrong place (ie. partitions). That's what prompted me to verify what phone you had.
Daily Driver: TMO SGS3 - Stock/Odex/TW/ICS 4.0.4 UVALI5 + UVALI8 Modem + CWM6 + My Own Custom Kernel (MOCK) Redux
Fine print: v3.0.8 -- 384/1512 MHz -- Noop/Ondemand -- XZ compressed -- 4096K SD read-ahead
blah, blah, blah. something /dev/random. yada, yada, yada.