What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen

Originally Posted by mremale

What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen

Same here, exactly the same.
Does any of this add up to yours? What's happening completely sucks. :/

My once bricked....

Originally Posted by mremale

It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen

Nothing is strange about it. The area of flash the /Data partition is mapped to is corrupted at the wearlevelfs level, something that cant be fixed by JTAG. From what I have seen there are 2 levels, the blue light of death and then able to get to recovery and download. The causes are pretty well known, known by Google and some parts of Samsung before we even knew about it.

Have you tried using ODIN to go back to EL26? sometimes EL29 doesn't work when i flash back to that version.

First off, thank you ALL for your replies and attempts to help. It is very appreciated! I odin'd to pretty much every kernel and rom i could. Some got me further than others. The end result was still the same. I get to see either the frozen battery charging icon or samsung galaxy s2 logo and nothing else. I did finally find a stock unrooted EL29 md5 (since everyone is on the one clicks these days) and was able to odin back to stock unrooted with no yellow triangle in hopes that my visit to sprint doesn't bad. This sucks, i can't believe i am hard bricked yet i can odin, get to recoveries, and even flash roms as well as nandroid restore. I looked into the Jtag thing i the post before this one says that's a no go too. Hopefully someone will have a miracle fix or sprint has a heart...

Think those of us with this problem are pretty much screwed...

If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic

Originally Posted by mremale

If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic

ah, so it looks like you had a bad download of AOKP or a bad flash (they happen) and in your panic forgot to Mobile Odin back and instead you reflashed AOKP from the stock recovery?

Sorry to hear about the brick. It's definitely a good lesson for newer members to read. If you have insurance, at least you'll only have to shell out $60 or so.

Yeah, i think it may have been a bad flash. I don't know what the deal was with all the force close notifications. I didn't try to flash back, i tried to do a wipe and then the trouble came. It was bad after that, so i tried to flash and it was the same situation

To those who have recently suffered a brick due to this issue I will kindly suggest still consider taking your phone to Sprint to ask for replacement. It certainly doesn't hurt to try. As a fallback contact Samsung and you can ask them to fix/replace under warranty.

And just to clarify - is there anyone before this rash of bricks that didn't or wasn't able to get their E4GT replaced? Just curious because it seemed like just about everyone was good.