Bricked S3: Recovery Booting

bossfan61

Well-known member
Sep 22, 2011
71
0
0
Visit site
Samsung Galaxy S3 (sgh-i747, AT&T)

Well, I thought I read and understood all the instructions and videos about how to root and install a CyanogenMod 10 nightly on my Galaxy S3, but somehow I strayed way off course. At the moment, the current state of my phone is when I power up, I see ?recovery booting? for a couple seconds in the upper Left corner of the screen, and then just a blank screen. No response from any of the buttons.

Only 10 minutes earlier, I was on my way to CM10, and had successfully rooted the S3 (all good with Odin and I confirmed SuperUser installed). Then, while watching a video on installing CM10, an annotation popped up about how I had to have v. 5.8 or higher of ClockworkMod recovery. The one I installed was v. 5.4 or something very close to that. That possibly explained why I kept getting errors when I was actually trying to install CM10.

So, I thought I found and installed a v. 5.8 of ClockworkMod as I got all the right signs again with Odin. Then, that?s where I got into this brick situation. Now I don?t know what to do. I?ve tried rebooting the phone several times (both Volume Up and Down with the other buttons), and even got it going once. At that point, I tried a Factory Reset in hopes of just staring all over. Then the phone wouldn?t boot up after that.

I?m hopeful someone can point me in the right direction to get me out of this situation.

All input is appreciated. Thanks!
 

bossfan61

Well-known member
Sep 22, 2011
71
0
0
Visit site
UPDATE:

I tried removing the battery for 10 minutes, then rebooting. I was able to get to Download Mode, and went thru the entire process again. Now, I get the CM spinning logo and then the following phrase:

"Unfortunately, the process com.google.process.gapps has stopped".

I feel like I'm close. Hopefully this will help generate a suggestion or two. Thanks!
 

bossfan61

Well-known member
Sep 22, 2011
71
0
0
Visit site
SOLVED: I rebooted the phone and magically it came up and seems ready to go. Rebooted twice more and all seems good.

There doesn't seem a way to delete my own post, so all is good...