Develop Bugs

The Offical how I hard bricked my E4GT thread

Well since I just bricked my phone I decided to start this tread. I figured it would be helpful for people to read to keep them from bricking their phone by not following the same process of the unlucky few who have hard bricked their device.
I flashed the Rogue CM9 kernel through Mobile Odin Pro and while on the FB17 leak from Calk which is where I think I made my mistake. when I went to flash CM9 alpha 3.1 it got stuck at install for about 15 minutes before i decided to the battery which I knew was a HORRIBLE idea. When I tried to boot back up all I got was a blue light. My guess is that the phone didn't like that I had a AOSP Kernel while on a TW rom and got confused and froze because it didn't know what to do next. The good news it that sprint is ever so gracious to provide me with a new phone coming in the mail on Thursday since they don't have any in stock. I just told them I got a update and when it installed it wouldn't boot back up and I should hopefully be back in business with some CM9 yumminess later this week thank the cellular gods for insurance!
Some users are reporting that mobiletechvideos.com is somewhere you can send your phone too have it brought back from the dead.

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

So I just got my second e4gt yesterday from hard bricking mine by flashing CM9 alpha 3 then flashing cwm touch recovery after I restored a nandroid of el29 it just wouldn't boot back
Sent from my SPH-D710 using XDA App

digitalcrash said:
So I just got my second e4gt yesterday from hard bricking mine by flashing CM9 alpha 3 then flashing cwm touch recovery after I restored a nandroid of el29 it just wouldn't boot back
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Everyone should hear this LEAVE CWM TOUCH ALONE ...... DON'T EVER TOUCH IT ... it is most of what is bricking these phones ... Unless they fix it don't use it for this phone .... How many people have to brick because of it .... Use the trusted acs rouge or cwm but not the touch
Sent from my SPH-D710 using xda premium

Somebody should make a sticky thread that warns people not to install the touch recovery from rom manager for this device. I notice everyone who hard bricked their device was by installing touch recovery through rom manager while using the leak ics roms or cm9
Sent from my SPH-D710 using xda premium

I posted it all over shabby's thread.....DONT USE TOUCH RECOVERY.

I learned my lesson with touch recovery and I will never use it again
Sent from my SPH-D710 using XDA App

correct me if im wrong but unless you actually burnt the processor out or dropped it in water ...couldn't u use a usb jig to just put you in download mode and odin from there worked on my fist galaxy s and fortunately i haven't had to use one sense ..and fyi really cheap and easy to make

sfal8705 said:
I got the exact same thing but my sprint reps think that the screen went out and are trying to replace it.
Click to expand...
Click to collapse
thats what happened to me as well after an hour of playing with it they decided to replace it.
the jig does nada for it just to answer that question goes
and I wasn't using touch recovery I was using rouge recovery for CM9... I think I screwed up trying to flash using the cm9 recoveery for a tw rom...

sergioperalta81 said:
correct me if im wrong but unless you actually burnt the processor out or dropped it in water ...couldn't u use a usb jig to just put you in download mode and odin from there worked on my fist galaxy s and fortunately i haven't had to use one sense ..and fyi really cheap and easy to make
Click to expand...
Click to collapse
No sometimes there are hard bricks that don't respond to jig and only fix is a jtag ....happened alot with flashing international ROM ....bootloader would disable the USB port ....
Sent from my SPH-D710 using xda premium

sfal8705 said:
I got the exact same thing but my sprint reps think that the screen went out and are trying to replace it.
Click to expand...
Click to collapse
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

albe070 said:
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
Click to expand...
Click to collapse
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.

blackroseMD1 said:
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.
Click to expand...
Click to collapse
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.

HaiKaiDo said:
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.
Click to expand...
Click to collapse
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

YoungAceAtlanta said:
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?
Click to expand...
Click to collapse
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

Help! Totally bricked my ET4G!

Was running a restore via CWM this morning, but there was nothing happening for a good 20 minutes, restoring from Darkstar to Calkulins (GB), so I left the phone alone for a while. An hour later, says is restoring data (no progress bar) and so after another minute, I rebooted the device. Of course, now I only get a blue LED(nothing on screen) and I cannot seem to get into ODIN mode or recovery. Any ideas?

Its bricked. You need to jtag or take it to sprint.Have you read what everybody is saying?.....if you want to restore gingerbread use odin first

shiftr182 said:
Its bricked. You need to jtag or take it to sprint.Have you read what everybody is saying?.....if you want to restore gingerbread use odin first
Click to expand...
Click to collapse
Sure as **** did not. I have a buddy at the sprint store I guess I need to see.

have u tryed using a usb jig

Sorry man, same thing happened to mine a week ago.

sergioperalta81 said:
have u tryed using a usb jig
Click to expand...
Click to collapse
What's that?

Its a little usb thing that you plug into your phone, it is supposed to put it in download mode/reset your odin counter automatically. I used it on mine when it bricked and it did nothing.

what shiftr said, im goin through this right now, sprint employee might say the screen is dead and make u wait a bit...

T.C.P said:
what shiftr said, im goin through this right now, sprint employee might say the screen is dead and make u wait a bit...
Click to expand...
Click to collapse
So you are getting a replacement T.C.P?
Sent from my Nexus S 4G using xda premium

Have we come to any consensus on what is causing these bricks? It seems to happen often when using CWM to restore between ICS and GB. Or is it something else entirely? I've always just used Odin and haven't had any issues yet.

OP. Could you provide a little more information on your setup? Specifically ...
1) The recovery (specific version) you were using at the time you made your GB Nandroid backup
2) The method you used to flash Darkstar, and how you obtained custom recovery after flashing it and the version of said recovery
3) The recovery (specific version) you tried to use to restore your GB Nandroid backup
We need to find out what is corrupting the data partition and making it un-usable and un-repartitionable (yeah I made up a word).

ajs2677 said:
Have we come to any consensus on what is causing these bricks? It seems to happen often when using CWM to restore between ICS and GB. Or is it something else entirely? I've always just used Odin and haven't had any issues yet.
Click to expand...
Click to collapse
from what I've read, it sounds like its either people coming from ics to gb like you said, or (and I'm really not sure on this one) they are trying to restore a backup from a different kind of recovery and there is being an incompatability at some point. Like restoring a backup made in rogue recovery in cwm recovery. I really don't know though and I'm kinda scared to test it as you can imagine.
Sent from my SPH-D710 using xda premium

Dchibro said:
OP. Could you provide a little more information on your setup? Specifically ...
1) The recovery (specific version) you were using at the time you made your GB Nandroid backup
2) The method you used to flash Darkstar, and how you obtained custom recovery after flashing it and the version of said recovery
3) The recovery (specific version) you tried to use to restore your GB Nandroid backup
We need to find out what is corrupting the data partition and making it un-usable and un-repartitionable (yeah I made up a word).
Click to expand...
Click to collapse
1) CWM Touch 5.8.1.5
2) CWM 5.0.2.7 (sensing a variable)
3) CWM Touch 5.8.1.5

I started with darkstar this morning, from calkulin's via cwm 5.0.2.7, then did a flash from rom manager, via cwm, to cwm touch. From there, without rebooting, I backed my ROM and attempted to reflash to calkulin's via cwm touch. That's when things went icky.

thebenshow said:
1) CWM Touch 5.8.1.5
2) CWM 5.0.2.7 (sensing a variable)
3) CWM Touch 5.8.1.5
Click to expand...
Click to collapse
So touch recovery is involved yet again. I'm assuming this was Koush's CWM Touch recovery, and not Team Rogue's version? If it was Koush's recovery, did you download it and flash it or did you install it via ROM manager?
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
thebenshow said:
I started with darkstar this morning, from calkulin's via cwm 5.0.2.7, then did a flash from rom manager, via cwm, to cwm touch. From there, without rebooting, I backed my ROM and attempted to reflash to calkulin's via cwm touch. That's when things went icky.
Click to expand...
Click to collapse
Okay ... VERY VERY VERY likely that this was your issue.
Lesson learned I guess, but this info is all over the place here on XDA. DO NOT use ROM Manager to flash CWM Touch. In fact, do not use ROM Manager at all, and I'd go further and say avoid any Touch Recovery for now. If if you insist on using Touch Recovery, use Steady Hawkins' version (although I believe he took the link down until this gets sorted out).

Don't know what the issue with the recovery and restore is but I've been dealing with galaxy s phones from all different carriers since they came out and its impossible to brick them. Like the other guy in the thread stated you need a USB jib. You plug it into your phones micro USB port and it automatically puts it in download mode and then you can use ODIN to flash what you want.
Sent from my ADR6300 using xda premium

Better still, my sprint guy said he'd just swap it.

droidboy29 said:
Don't know what the issue with the recovery and restore is but I've been dealing with galaxy s phones from all different carriers since they came out and its impossible to brick them. Like the other guy in the thread stated you need a USB jib. You plug it into your phones micro USB port and it automatically puts it in download mode and then you can use ODIN to flash what you want.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
That's the problem. People are getting stuck at an in between point where Odin won't complete as well.
Sent from my Nexus S 4G using xda premium

droidboy29 said:
Don't know what the issue with the recovery and restore is but I've been dealing with galaxy s phones from all different carriers since they came out and its impossible to brick them. Like the other guy in the thread stated you need a USB jib. You plug it into your phones micro USB port and it automatically puts it in download mode and then you can use ODIN to flash what you want.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Not in this case man. I know it defies all previous knowledge, but this problem is stopping even Odin from being able to re-partition and write to /data.

When using ics 3.0 kernel to flash or restore you have a good chance of a brick .....Odin back before restore ....please read people
And don't use cwm touch
Sent from my SPH-D710 using xda premium

How not to brick my phone?

I should be getting my device within the next day and I am going to root, I'm hearing all this stuff about bricking and I would like to know what to do and what not to do to end up in this situation thanks!
Sent from my Nexus S using xda premium

Darrien13 said:
I should be getting my device within the next day and I am going to root, I'm hearing all this stuff about bricking and I would like to know what to do and what not to do to end up in this situation thanks!
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Follow instructions carefully. If not sure what something is or how to do it, ask instead of blindly flashing. Oh, and don't ever use CWM Touch Recovery. Good Luck

Darrien13 said:
I should be getting my device within the next day and I am going to root, I'm hearing all this stuff about bricking and I would like to know what to do and what not to do to end up in this situation thanks!
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I HIGHLY recommend you follow QBKING77's videos on youtube he has videos on how to root(use the latest) he has review videos and how to install videos on every rom on this site. Stick with his video's follow them to a T and you should be good to go. I have had this phone for a good 3 months now and I LOVE it and have never had a problem while following his videos. You will love this phone it is AMAZING!
---------- Post added at 05:03 PM ---------- Previous post was at 05:02 PM ----------
stargaterules said:
Follow instructions carefully. If not sure what something is or how to do it, ask instead of blindly flashing. Oh, and don't ever use CWM Touch Recovery. Good Luck
Click to expand...
Click to collapse
Yes I can definitely agree with that DO NOT use touch recovery, I soft bricked my phone a couple weeks back using it trying to install Phantom Hackers Blazer rom. AMAZING rom BTW!

1) Don't use ROM Manager to flash anything in its temp recovery while on a ICS kernel
2) Don't use Touch Recovery at all
3) If you want to be as safe as possible, never wipe data while on a ICS + CWM repacked kernel. Anytime you wipe data, make sure you're on a GB + CWM kernel. The EL26 stock CWM repack works nicely, but I trust the EL29 + Rogue CWM repack. Now, I've wiped data on a ICS + Rogue kernel repack twice now and it went just fine, but it does seem that this may be risky. You may never brick doing it, but some have, so it may be better to be safe than sorry.
If you don't plan to flash anything ICS related, you really don't have much to worry about besides possibly #2.

Dchibro said:
1) Don't use ROM Manager to flash anything in its temp recovery while on a ICS kernel
2) Don't use Touch Recovery at all
3) If you want to be as safe as possible, never wipe data while on a ICS + CWM repacked kernel. Anytime you wipe data, make sure you're on a GB + CWM kernel. The EL26 stock CWM repack works nicely, but I trust the EL29 + Rogue CWM repack. Now, I've wiped data on a ICS + Rogue kernel repack twice now and it went just fine, but it does seem that this may be risky. You may never brick doing it, but some have, so it may be better to be safe than sorry.
If you don't plan to flash anything ICS related, you really don't have much to worry about besides possibly #2.
Click to expand...
Click to collapse
i was on calks ics rom and wiped everything then flashed his 2.9 rom. everything went just fine.

M1nze said:
i was on calks ics rom and wiped everything then flashed his 2.9 rom. everything went just fine.
Click to expand...
Click to collapse
As I said ... I have done the same, as have many others. However, just because it worked once, or twice, or twenty times, there could always be that one time where you brick. Steady Hawkin said he used his kernel repack to wipe and flash CM9 4 or 5 times with no issues, then doing the exact same thing again his phone bricked. Here's the quote ...
Steady Hawkin said:
Here is the story fellas:
I was on CM9 Alpha4, and I was flashing our FB21 rev2 to pull some logs. I had flashed Alpha4 and our kernel about four or five times already without any kind of issue. For whatever reason the next time I went to reflash Alpha 4, I booted into recovery wiped cache and dalvik cache (as I had done four or five times already with the same recovery and rom build) and it just hung at installing update. It was at that time I knew my luck had run out. No Odin (including using the jig I have), no connection to ADB, no nothing, just the blue light of death.
These bricks are concerning for a variety of reasons. The biggest IMO, is that there does not seem to be a single constant. People are bricking on different recoveries, with different roms, with different scenarios each time. TBH at this point I have no idea what is causing it or where to even start. I will say it is possible that these stock kernels from Sammie could play a role in the chaos, but thats just a guess.
Bottom line is, playing with ICS before we have any sort of source is going to be a gamble. If you dont have insurance on your phone I would hold off. I'm going to continue to do my best to try and figure out what is going on, but I cant guarantee anything. With the help of the other dev's I hope we can get this situated so we can move forward. In the meantime Team Rogue will continue to play with fire in a quest to move development forward.
Click to expand...
Click to collapse
Whether the extra time it takes to flash back to GB is worth it or not is up to each person.

I would recommend looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1525495
I believe it is the intent of the OP on that thread to get it stickied if possible to avoid duplicate threads like this one.
If I may also share some advice given to me last week: Consider just rooting the stock ROM and getting familiar with it before jumping on to other ROMs. This gives you time to become more familiar with the device and stock capabilities as well as hopefully time to fully identify the brick issues and either work around them or resolve the cause.
I would also recommend keeping tabs on this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
It never hurts to err on the side of caution in this case. Good luck and enjoy your E4GT when it comes in!

[Q] From Evo 3d

I'm someone, like others I've saw, that are coming over here from the EVO 3d after having to go through asurion.
As a good XDA member, I read through the stickies.
I wanted to confirm what I've learned.
ICS for you guys is rather different. I'm seeing many versions of ICS, I'm guessing leaks at different stages (haven't seen many leaks on phones in a while).
I also saw that wipe in custom recoveries is a REALLY bad idea.
In fact it said not to use custom recoveries with ICS stuff.
So why does Calkulin's E4GT rom say you MUST use a custom recovery?
I thought I saw something crazy that said it depends what version you are on for the method you root. But I can't find that again. It seems weird, but please tell me that's wrong and there's only one way to really root.

karate134 said:
I'm someone, like others I've saw, that are coming over here from the EVO 3d after having to go through asurion.
As a good XDA member, I read through the stickies.
I wanted to confirm what I've learned.
ICS for you guys is rather different. I'm seeing many versions of ICS, I'm guessing leaks at different stages (haven't seen many leaks on phones in a while).
I also saw that wipe in custom recoveries is a REALLY bad idea.
In fact it said not to use custom recoveries with ICS stuff.
So why does Calkulin's E4GT rom say you MUST use a custom recovery?
I thought I saw something crazy that said it depends what version you are on for the method you root. But I can't find that again. It seems weird, but please tell me that's wrong and there's only one way to really root.
Click to expand...
Click to collapse
You have to use a specific recovery to flash stuff, called the EL26/29 recovery. It's based on 5.0.2.7 (?) of ClockWorkMod recovery. This is generally accepted as the safest way to flash. Flashing from an ICS based recovery has been known to brick devices.
Samsung devices have Odin, much like HTC devices have Fastboot. We're able to put the device in Odin (download) mode and flash just about anything. There's even an app version called Mobile Odin that allows you to Odin flash directly from the phone without having to plug in.

Correct me if wrong but i think there is only an issue with ics recovery when wiping due to the emmc bug (partition corruption). Thats whats causing the bricks. There are plenty workarounds though. I use ics recovery to flash things, i just make sure to never wipe anything using the recovery. I use calk's format all zip and modified format zip whenever i need to wipe.

puff601 said:
Correct me if wrong but i think there is only an issue with ics recovery when wiping due to the emmc bug (partition corruption). Thats whats causing the bricks. There are plenty workarounds though. I use ics recovery to flash things, i just make sure to never wipe anything using the recovery. I use calk's format all zip and modified format zip whenever i need to wipe.
Click to expand...
Click to collapse
Correct they have come up with ways to use ICS recovery to update and flash certain things. Honestly since the OP is new to Epic Touch I would stick with the very simply odin of el26 recovery and flashing anything you need while in ICS.
agat's threads have great info if you are a stock software guy with ways to flash and upgrade while on ICS. Honestly GB is pretty damn polished and there are some awfully nice roms for it as well and you have no worries at all with how you flash. sfhub has quite a few threads with his odin one click methods which have been a god sent for a lot of us here.
First decide what you want to do then any one of the OP's will direct you in the right direction. Also if you can read up on the How not to brick your phone threads/stickies in general I believe

Would be a better idea to use the cm9 direct boot Odin file. Much easier than pulling the battery 10 times. Read all the release notes on the cm9 wiki and you'll have safe flashing.
Sent from my awesomely EPIC Phone

Rooster-just curious, why would you need to pull the battery? I've flashed plenty of roms and haven't had to pull the battery once...
Karate-the easiest easy to just gain root access is to use sfhub's one click rooted el29-just boot into download mode (vol up + power), plug into the computer and click start...easy peasy
And as playya said, the OP's of any of the rom threads all have great info and directions to keep you flashing safely. Good luck and happy flashing!
Sent from my wickedly sensational e4gt

Sunsparc said:
You have to use a specific recovery to flash stuff, called the EL26/29 recovery. It's based on 5.0.2.7 (?) of ClockWorkMod recovery. This is generally accepted as the safest way to flash. Flashing from an ICS based recovery has been known to brick devices.
Samsung devices have Odin, much like HTC devices have Fastboot. We're able to put the device in Odin (download) mode and flash just about anything. There's even an app version called Mobile Odin that allows you to Odin flash directly from the phone without having to plug in.
Click to expand...
Click to collapse
Can you a link to el2? Recovery
Sent from my SPH-D710 using xda premium

http://forum.xda-developers.com/showthread.php?t=1416477
Check this thread out, make sure to read all the directions and you should be able to find the auto root package where you can add cwm recovery to the kernel
Sent from my wickedly sensational e4gt

karate134 said:
I'm someone, like others I've saw, that are coming over here from the EVO 3d after having to go through asurion.
As a good XDA member, I read through the stickies.
I wanted to confirm what I've learned.
ICS for you guys is rather different. I'm seeing many versions of ICS, I'm guessing leaks at different stages (haven't seen many leaks on phones in a while).
I also saw that wipe in custom recoveries is a REALLY bad idea.
In fact it said not to use custom recoveries with ICS stuff.
So why does Calkulin's E4GT rom say you MUST use a custom recovery?
I thought I saw something crazy that said it depends what version you are on for the method you root. But I can't find that again. It seems weird, but please tell me that's wrong and there's only one way to really root.
Click to expand...
Click to collapse
Im one of those that went through insurance too and ended up with this today and i gotta say I love it!
Sent from my SPH-D710 using XDA

im also coming over from the evo4g and evo3d not because of insurance wanted something different and im loving the phone so far..i will say i was lost at first with odin and el29 its a different way of doin stuff but not hard at all

Welcome, I recently made the switch as well. The screen is incredible after looking at the E3D for so long. Seriously, I stop to look at how pretty it is at least once every day.

SkuzFoz said:
Welcome, I recently made the switch as well. The screen is incredible after looking at the E3D for so long. Seriously, I stop to look at how pretty it is at least once every day.
Click to expand...
Click to collapse
Yup! It truly is amazing!
Sent from my SPH-D710 using XDA

Need help please

Hi i used the wrong recovery to backup my Samsung epic touch and now all I get is a blue light it won't start or boot to recovery or odin any help will be appreceiated. I'm using EL26 kernal to flash ICS roms I went to cwm touch recovery instead of rouge recovery and now I'm stuck.
I do also have the FE02 plus recovery I forgot to mention that with having all my stress.

Sounds like another hard brick... Your only small hope would be in a usb jig and then a jtag service, but both might fail and you now have an expensive paperweight.
Sent from my SPH-D710 using Tapatalk 2

Try the manual method to get into download mode (copied from sfhub's TAR posts):
Code:
Method #1
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Without getting into download mode you're probably a victim of the eMMC lockup. But to know for sure, what kernel version were you on when you last tried a CWM restore or wipe?

I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
BTW it won't go into download mode

bigdaddy619 said:
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
Click to expand...
Click to collapse
OK, the behavior - specifically that the phone froze and wouldn't respond until you pulled the battery - matches the eMMC lockup. Unfortunately yours appears to be locking up during the boot process which is why you can't get to download mode. Only way to fix is to take to Sprint for replacement.
Still curious how you did it though - and let's try our best to find it so that others don't suffer the same fate:
bigdaddy619 said:
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
Click to expand...
Click to collapse
Can you link to the post containing the file you used to flash? I'm not aware of an FE02 build - maybe Agat's FF02 repack? And can you also include source of CWM touch if from a different ROM?

Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT

shiftr182 said:
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
Click to expand...
Click to collapse
Yea even then he stated fe02? Isnt that an ics kernal and also used touch which neither is good for flashing a new rom.. either way people make mistakes and like said already you have a nice paperweight.. to sprint you must go lol
Sent from my SPH-D710 using XDA

http://forum.xda-developers.com/showthread.php?t=1342728 this the link where i got the e4gtauto.
If you want CWM use Option C in the Auto Root Package to install EL26+CWM (you are already rooted so Option A is not necessary)

OOOOOPS it was the FD02+recovery sorry

bigdaddy619 said:
OOOOOPS it was the FD02+recovery sorry
Click to expand...
Click to collapse
There's your culprit. Once you get it replaced you'll want to stick with GB or FF02 repack which was done with care to avoid triggering the lockup for now. Sorry you had to find out this way...
Sent from my SPH-D710 using XDA

Close please
Sent from my MB855 using xda app-developers app

where did you find cmw touch?
I've been looking all over for it!

emottau said:
I've been looking all over for it!
Click to expand...
Click to collapse
Looking for what?
Sent from my MB855 using xda app-developers app