Originally Posted by sfal8705

I got the exact same thing but my sprint reps think that the screen went out and are trying to replace it.

Tell them to put the chip in a different housing and see if it works, if its the screen it would work in a different housing. I did that with my og epic..

---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------

We really should make a sticky, or a thread that says DONT USE TOUCH RECOVERY!!! and just keep bumping it up to the top.

Yup CWM Touch killed my evo during restore and data wipe.. 1st it soft brick my phone and had to factory restore a .tar and now it finally killed my phone. gotta pick up my replacement tmmrow

And yes i was using a ICS FBXX rom during this

What is the recommended way to flash to cm9 3.1 from the calks ics fb17 leak without bricking the phone?

Sent from my SPH-D710 using Tapatalk

Originally Posted by albe070

What is the recommended way to flash to cm9 3.1 from the calks ics fb17 leak without bricking the phone?

Sent from my SPH-D710 using Tapatalk

Flash Miui Rom then flash CM9. Dont use CWM touch at all.. just use a basic recovery like rogue or stock CWM

Yep. Touch recovery seems to be the common denominator amongst the bricked phones. I was lucky enough to just get mine swapped out at a Sprint Service Center. I certainly won't be using CWM Touch for anything ever again.

Originally Posted by blackroseMD1

Yep. Touch recovery seems to be the common denominator amongst the bricked phones. I was lucky enough to just get mine swapped out at a Sprint Service Center. I certainly won't be using CWM Touch for anything ever again.

I think the culprit is using an aosp recovery while on a TWIZ ROM... I would avoid that because I bet that is the issue...

It doesnt seem to be just the Clock Work Mod Touch. It would seem that sbrissen thinks that in ICS the data partition or blocks are slightly different and this is causing errors when flashing ICS or back to GB from ICS. So id say for now stay away from ICS in general until this is completely sorted.

Originally Posted by HaiKaiDo

It doesnt seem to be just the Clock Work Mod Touch. It would seem that sbrissen thinks that in ICS the data partition or blocks are slightly different and this is causing errors when flashing ICS or back to GB from ICS. So id say for now stay away from ICS in general until this is completely sorted.

so what do you say people do who have flash ICS and want to get back to GB without screwing up.. just use a .tar?

You can add me to the list...also was using touch recovery. I wonder what Sprint/Samsung is thinking about all of our E4GTs coming in for repair hahaha

Sent from my (temp) Desire HD using XDA App

Originally Posted by YoungAceAtlanta

so what do you say people do who have flash ICS and want to get back to GB without screwing up.. just use a .tar?

Yes. I odin back to el29 stock with root and then install cwm rogue then restore a previous backup. The process is bit much but better to be safe than sorry

Sent from my SPH-D710 using xda premium