I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
hrffd said:
I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
Click to expand...
Click to collapse
I think you may be hosed but if you have the jig I'd definitely give it a shot (just in case). If that doesn't work you can take it into Sprint. If I remember right with the warranty if they can repair it there's no charge, if they need to send you a new device it's a $100 deductible. Most people just say it quit working on them without offering an explanation, seems to work most of the time.
Good luck!
Apparently JTAG is not going to work either. Something seems to be actually destroying the MMC chip when you mess with ICS and custom recoveries.
sputnik767 said:
Apparently JTAG is not going to work either. Something seems to be actually destroying the MMC chip when you mess with ICS and custom recoveries.
Click to expand...
Click to collapse
JTAG has been able to recover some hard bricks. I think it depends on the extent of the damage.
Sent from my SPH-D710 using Tapatalk
Dchibro said:
JTAG has been able to recover some hard bricks. I think it depends on the extent of the damage.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Have not heard of Jtag bringing anyone back from these bricks though.. Also there is a guy in the thread above yours... right before I posted that had a similar issue with AOKP Build30... Hope there is no problem with that rom..
playya said:
Also there is a guy in the thread above yours... right before I posted that had a similar issue with AOKP Build30... Hope there is no problem with that rom..
Click to expand...
Click to collapse
Ya, Me too.
hrffd said:
I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
Click to expand...
Click to collapse
I am not sure if you listed every step you did or were just summarizing.
Did you have the Yellow Triangle before any of this? I ask because nothing you did should have triggered the yellow triangle unless you had it before (or traditional ODIN'd CWM outside of the steps you listed)
Also, nothing you did should have prevented you from getting into ODIN DL mode. Even in the case of /data EMMC corruption, you can still get into ODIN DL mode.
Are you sure you can't get into ODIN DL mode? Pull the battery, then as you insert the battery press-and-hold Power+VolDown. If it is difficult to do the finger combination, then you are doing it right.
If you can get into ODIN DL mode, use the EL29 OneClick to get back to a known base. Use the Full version. If it hangs on data.img, then you have the /data emmc corruption and your only option is to get the unit replaced. JTAG will not work.
I have a quick question since we seem to be on the topic of bricks today. Has anybody bricked from making a nandroid in ICS recovery then using format all zip and then restoring from it. I am not referring to AOKP, CM9, etc rather stock or themed stock ROMs. I would NEVER recommend anyone to do this but I have made a few and restored them only wiping with format all zip. Am I tempting fate here or what? I thought this was narrowed down to wiping individual partitions or working from AOKP, CM9 recovery. Any thoughts here?
Sent from my Nexus S 4G using xda premium
JohnCorleone said:
I have a quick question since we seem to be on the topic of bricks today. Has anybody bricked from making a nandroid in ICS recovery then using format all zip and then restoring from it. I am not referring to AOKP, CM9, etc rather stock or themed stock ROMs. I would NEVER recommend anyone to do this but I have made a few and restored them only wiping with format all zip. Am I tempting fate here or what? I thought this was narrowed down to wiping individual partitions or working from AOKP, CM9 recovery. Any thoughts here?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
the question is why are you wiping when restoring a nandroid back up?
You should be fine but the wiping step is pointless. The restore process should do it automatically.
Also yes, I have done a backup while in FC22 based CWM and recovered it from another FC22 based CWM install and it worked fine. No need to wipe at all.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
@JohnCorleone,
There are other posters that agree with you that not all ICS ROMs have that problem. Epix4G has reminded me of this on occasion, but that was in regards to using Calk's ROMs and solutions. But I would also caution that this probably isn't a good idea for Joe Schmoe with a shiny new E4GT... maybe those that have been around longer or are willing to take that risk.
In my personal case I don't have the option for insurance and had to pay full price for this phone. I can't afford to brick it so I stick with the ODIN TARs for now. Maybe a few months down the road, once ICS is out and hopefully there's a better handle on this, I'll try some of the other options out there. Besides, coming from an Optimus S stock will do everything I need and more right now.
garwynn said:
@JohnCorleone,
In my personal case I don't have the option for insurance and had to pay full price for this phone. I can't afford to brick it so I stick with the ODIN TARs for now. Maybe a few months down the road, once ICS is out and hopefully there's a better handle on this, I'll try some of the other options out there. Besides, coming from an Optimus S stock will do everything I need and more right now.
Click to expand...
Click to collapse
Ya, I was using my phone on a different carrier, and bricked it. Talk about a ****ty realization. And coming from an Optimus, life is goooood eh? lol.
take the phone to sprint as long as they cant see anything your good to go. tell them you plugged it in to charge came back and smelt something funny and phone was real hot.
Same brick here, only blue led of death and no activity.
The phone is outside US so can't even get warranty / replacement. Can't get get mmc chip from Samsung which in this case is KLMAG4FEJA-A003
Jtag
sent from MY BAD A$$ ET4G
JTAG has failed over RISC
Disillusioned said:
Same brick here, only blue led of death and no activity.
The phone is outside US so can't even get warranty / replacement. Can't get get mmc chip from Samsung which in this case is KLMAG4FEJA-A003
Click to expand...
Click to collapse
Are you able to get ahold of a USB jig and see if this will somehow get it to come to life? If not, have you considered asking someone in the US to try and work with Samsung on your behalf?
Its pretty much dead at this point, time to replace the device. Even if a jig will trigger dl mode it will more than likely fail/hang at /data in odin.
Sent from my SPH-L710
-EViL-KoNCEPTz- said:
Its pretty much dead at this point, time to replace the device. Even if a jig will trigger dl mode it will more than likely fail/hang at /data in odin.
Sent from my SPH-L710
Click to expand...
Click to collapse
Yes, but if there is not a replace option getting that far would mean a modified pit will restore most functionality.
Sent from my SPH-D710 using Tapatalk 2
garwynn said:
Yes, but if there is not a replace option getting that far would mean a modified pit will restore most functionality.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
True, that's a 50/50 shot and worth the try if there's not a warranty or ins option, but if warranty is an option I'd personally grab a replacement instead of patching up a borked one just so I wouldn't run into a major issue from patching it back together and then be out of warranty and stuck with a total brick. I've also seen a few ppl be able to get to dl mode and it fail at data but the pit not work, probably user error but never know could just be totally fubar from the emmc bug
Sent from my SPH-L710
-EViL-KoNCEPTz- said:
True, that's a 50/50 shot and worth the try if there's not a warranty or ins option, but if warranty is an option I'd personally grab a replacement instead of patching up a borked one just so I wouldn't run into a major issue from patching it back together and then be out of warranty and stuck with a total brick. I've also seen a few ppl be able to get to dl mode and it fail at data but the pit not work, probably user error but never know could just be totally fubar from the emmc bug
Sent from my SPH-L710
Click to expand...
Click to collapse
It was def user error. In another post he said he loaded aokp from rujelus recovery:crying:
Related
Maybe a stupid question but I ordered a jig and haven't received it yet but how would I check if it works to leave positive feedback.. I'm stock rooted with Odin no custom recovery.... Would I just turn the phone off take the battery off put it back in and connect the jig? If it goes to download then it works?
Sent from my SPH-D710 using xda premium
Power down the phone, plug in the jig, turn on the phone. It shoudl go into ODIN download mode directly and say something about stats being reset. If it doesn't do the latter, you are probably on a new bootloader and it isn't the fault of the jig.
Turn the phone off, take the battery out for about 15 seconds, put the battery back but leave the phone off. Put in the jig and in a few seconds you should be at the download screen and the download count should say it has been reset.
Sent from my SPH-D710 using XDA
dante32278 said:
Turn the phone off, take the battery out for about 15 seconds, put the battery back but leave the phone off. Put in the jig and in a few seconds you should be at the download screen and the download count should say it has been reset.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
And from there, are you free to just turn the phone back off by taking out battery?
You don't need to take out the battery. Just press and hold the power button until it resets.
Thanks for the quick reply, I bought one in the event I get a brick and need to take it to a store. Oh and it will still work if im on an FC07 leak right? Or will it only work with GB roms, kernels?
It will work with the ICS ROMs as long as you have the original (EG30/31) bootloader. If you flashed the raw leaked tar from Samsung/Sprint, then the reset of flashing data might not work (but it should still put you in ODIN D/L mode). If you flashed one of the ODIN OneClick packages I put together, then all the features will work.
Ok I think Ill be good to go then because Ive always waited til Calk puts up a stock rooted version, not flashing the tars. Anyways while I kind of have you here, I was just wondering if this type of stuff has anything to do with our phones our might show up in the future and which type does our phone use, if any. heres the link http://forum.xda-developers.com/showthread.php?t=1387334 I was rooting my dads Epic 4G so I kept on seeing it in the thread titles. Just curious
rsalinas1 said:
Ok I think Ill be good to go then because Ive always waited til Calk puts up a stock rooted version, not flashing the tars. Anyways while I kind of have you here, I was just wondering if this type of stuff has anything to do with our phones our might show up in the future and which type does our phone use, if any. heres the link http://forum.xda-developers.com/showthread.php?t=1387334 I was rooting my dads Epic 4G so I kept on seeing it in the thread titles. Just curious
Click to expand...
Click to collapse
I didn't read that thread very closely, but MTD is sometimes an overloaded term and could mean different things to different people.
If used to compare flash memory types, we actually have eMMC rather than MTD. eMMC memory are block devices. MTD devices are similar to but not really block devices so they created a new category in the kernel to deal with them.
To get an idea about MTD, read this post:
http://www.linux-mtd.infradead.org/faq/general.html
Not that technical in Linux lol but thanks I will still give it a read. Bottom line of that thread made it just seem like MTD is a huge thing and makes the epic 4g a much better phone versus BML. Oh and it just said that they are types of partition maps, mtd being open and bml being closed source.
Sent from my SPH-D710 using Tapatalk
rsalinas1 said:
Not that technical in Linux lol but thanks I will still give it a read. Bottom line of that thread made it just seem like MTD is a huge thing and makes your phone better versus BML, whatever that is lol.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Ok, I read the thread a little more closely.
It seems the 2 main benefits from switching to the kernel supporting MTD partition format over the stock BML are you can resize the partitions easier and use ext4 (because those new kernels support ext4)
Our kernels already use ext4. w/r/t resizing partitions perhaps some people need more space in /data but most people seem to be ok with it.
It is always nice to have more options, but there is probably less demand for it on this phone than Epic.
I gotcha, maybe we will see it once our devices get older and we need something new lol. So just asking again now that you've read more closely, our phones dont use either of these partition maps correct?
Sent from my SPH-D710 using Tapatalk
I'm actually not sure which partition map we are supporting. I initially read the thread as MTD vs eMMC memory technology, which is different than the purpose of that thread.
I see, maybe you can figure that out for us in your spare time lol (if it really even makes a difference.) The E4GT is a beast of a phone anyways lol.
Sent from my SPH-D710 using Tapatalk
Just an FYI:
I got my jig and put it right in the slot while my phone was still on... it shut down my phone and put it directly into download mode and showed that my counter had been reset.
On a side note, for what ever reason, my GPS started working when I restarted the phone. It hadn't been working for days.
rsalinas1 said:
Thanks for the quick reply, I bought one in the event I get a brick and need to take it to a store. Oh and it will still work if im on an FC07 leak right? Or will it only work with GB roms, kernels?
Click to expand...
Click to collapse
If you "brick" your phone, a JIG is not going to help you.
Drumrocker said:
If you "brick" your phone, a JIG is not going to help you.
Click to expand...
Click to collapse
Depends what kind of brick. The /data nonwritable brick still allows you to write every other partition as well as use the jig to reset the counter
so I was on vacation in europe and my wifi wouldn't connect, so I flashed CM9 as on a whim and the wifi worked great (for google voice wifi calling). The phone was acting wacky so I went into recovery to wipe cache and I accidentally did a full wipe (I blame the jet lag) using the included recovery and rebooted..and my phone was bricked. no samsung screen, no download mode, just solid blue light.
here's my question...
I read in another post that you can try holding the vol down and power until the blue light does the single blink and see if odin recognizes it and trying oding el29. I'm at work, so before I drive all the way home to try it, is there any truth to this idea or should I just wait patiently for my replacement phone?
thanks in advance
I have heard it doesn't work for a full brick, which it sounds like you have. Wouldn't hurt to try though. Usually if you can't access the download screen you're done.
Sent from my SPH-D710 using XDA
dante32278 said:
I have heard it doesn't work for a full brick, which it sounds like you have. Wouldn't hurt to try though. Usually if you can't access the download screen you're done.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I know. and I knew immediately what I did. Not my first brick, lol. having TEP removes all safety protocols I should take when flashing, which I do about 10 times a week
but seeing that post gave me a glimmer of hope that I won't have to keep using my old blackberry until my replacement comes
You'll probably be able to get into ODIN D/L mode and flash everything but your /data partition. The problem is that usually when people do what you did, their /data partition memory gets corrupted in hardware, so you can try, but be prepared to get a replacement.
Oh no Wiz. Weren't you one of the early bricks from CWM Touch? I'm afraid sfhub is probably right. Getting Odin to connect is actually the easy part in these cases. Getting through data.img successfully is another story. Sorry man.
Sounds like you'll be stuck at data.img if you get into Odin. Best of luck though.
Dchibro said:
Oh no Wiz. Weren't you one of the early bricks from CWM Touch? I'm afraid sfhub is probably right. Getting Odin to connect is actually the easy part in these cases. Getting through data.img successfully is another story. Sorry man.
Click to expand...
Click to collapse
I actually never had a problem with the cwm touch, lol. my first brick was when I tripped over my usb cable while using odin XD
after that I got a usb jig... which I recommend EVERYBODY get. It's saved me from that fate at least 3x already.
but it didn't help now
didn't work. odin wouldn't recognize it
guess I'm stuck waiting for my replacement to come in..
I hate using this stupid blackberry
my phone was on aokp and fine but i decided i just wanted to go back to the blazer i had
i boot into recovery and im in my cwm recovery (not rogue)
but when i go to wipe/factor reset the screen flashes its stock recover with the little green android in the background and freezes there
i think WTF? no biggie i pop out battery just boot into recovery again and start over
nope doesnt work im stuck on samsung galaxy s screen with yellow triangle
finally get home to comp and go into odin mode try to flash stock ek02 and that doesnt work just gets me stuck at data
so i try it without data and that works but now it just bootloops
so now i dont know if im brick'd or just in some boot loop
any help would be great!!!
hope everything i typed makes sense if not ill clarify
dont know what to tell ya man....im in a hole right now and i see no light either...
i was on codename and the phone was fine for a whole day and a half. i uncderclocked it to 800mhz and undervolted 100mv and the phone ran beautiful for a day and a half. then all of a sudden like two hours ago it froze. went in to a bootloop. trying to figure this out right now...odin wont recognize my phone at alllllll
damn man that is certainly worse than my situation not
seems like ics isnt as stable as we hope haha, but man idk why my phone get stuck when flashing the data.img in odin it never gets past this... im thinking its bricked which really sucks but just gotta roll with the punches... if anyone can help please do ill be up a little while longer
Yeah its bricked.
ross4747 said:
damn man that is certainly worse than my situation not
seems like ics isnt as stable as we hope haha, but man idk why my phone get stuck when flashing the data.img in odin it never gets past this... im thinking its bricked which really sucks but just gotta roll with the punches... if anyone can help please do ill be up a little while longer
Click to expand...
Click to collapse
ICS isn't unstable you just messed up basically. This is why you should read the brick threads and warnings first about flashing between ICS. And gingerbread. Your phone sounds like it's bricked. Sorry dude.
As for the guy with the boot loop. You're probably not bricked you just need to try and get into download mode and odin a stock rooted rom. How long did you pull the battery for?
Under volting can cause boot loops but your issue could be a combination. I would post in the brick thread. Someone experienced with that problem can help you.
I recommend pulling the battery and waiting an hour or so then redo it.
Good luck!
Sent from my SPH-D710 using Tapatalk 2 Beta-5
LordJummy said:
ICS isn't unstable you just messed up basically. This is why you should read the brick threads and warnings first about flashing between ICS. And gingerbread. Your phone sounds like it's bricked. Sorry dude.
As for the guy with the boot loop. You're probably not bricked you just need to try and get into download mode and odin a stock rooted rom. How long did you pull the battery for?
Under volting can cause boot loops but your issue could be a combination. I would post in the brick thread. Someone experienced with that problem can help you.
I recommend pulling the battery and waiting an hour or so then redo it.
Good luck!
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
ya i tried man...but odin doesnt recognize my phone... im thinking its the LG usb cable i have. i read somewhere that the pins inside the acttual cable arent the same as the E4GTs cable. so tomorrow im gonna get my stock cable.
Carbajal3009 said:
ya i tried man...but odin doesnt recognize my phone... im thinking its the LG usb cable i have. i read somewhere that the pins inside the acttual cable arent the same as the E4GTs cable. so tomorrow im gonna get my stock cable.
Click to expand...
Click to collapse
That's possible if its some proprietary cable. These phones use a standard mini USB to USB so any standard generic cable should work. I use a really thick and durable Logitech cable that came with a mouse, or sometimes a generic super long one I have that's like 10 feet
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Ok u guys to to read the OP again for what your flashing you cannot flash any ROM from ICS right now it has a high risk of brick if your going to flash an ICS ROM the best bet is from a cwm based kernal like EL26 not Rogue and you shud be back on GB so use one of SFhub packages it takes an extra 10 minutes tops
Sent from my SPH-D710 using XDA
MJHawaii said:
Ok u guys to to read the OP again for what your flashing you cannot flash any ROM from ICS right now it has a high risk of brick if your going to flash an ICS ROM the best bet is from a cwm based kernal like EL26 not Rogue
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Wow. Now you're spreading more misinformation. You certainly can flash roms from ICS recovery its just not 100% safe in all versions and flavors.
Its generally user error that's causing the bricks. The OP will usually claim he did everything perfect but 99% of the time it comes out sooner or later they did something wrong out of haste or neglect.
You're not necessarily helping though with your false info. No offense intended I just don't want you further confusing some poor noob who takes your word...
And just to further clarify: yes odin'ing stock EL26 is safer than flashing from ICS based CWM.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Carbajal3009 said:
dont know what to tell ya man....im in a hole right now and i see no light either...
i was on codename and the phone was fine for a whole day and a half. i uncderclocked it to 800mhz and undervolted 100mv and the phone ran beautiful for a day and a half. then all of a sudden like two hours ago it froze. went in to a bootloop. trying to figure this out right now...odin wont recognize my phone at alllllll
Click to expand...
Click to collapse
Get back into DL mode and flash back to stock and invest in a usb download jig its 5$ and comes in handy in soft brick and bootloop situations
Sent from my SPH-D710 using XDA
MJHawaii said:
Get back into DL mode and flash back to stock and invest in a usb download jig its 5$ and comes in handy in soft brick and bootloop situations
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Apparently you're not reading the entire thread lol. Scroll up man.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
LordJummy said:
Wow. Now you're spreading more misinformation. You certainly can flash roms from ICS recovery its just not 100% safe in all versions and flavors.
Its generally user error that's causing the bricks. The OP will usually claim he did everything perfect but 99% of the time it comes out sooner or later they did something wrong out of haste or neglect.
You're not necessarily helping though with your false info. No offense intended I just don't want you further confusing some poor noob who takes your word...
And just to further clarify: yes odin'ing stock EL26 is safer than flashing from ICS based CWM.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
as i said you cannot flash anything from ICS without running a risk of bricking your phone its a known issue
Goodnight jummy:what:
Sent from my SPH-D710 using XDA
MJHawaii said:
as i said you cannot flash anything from ICS without running a risk of bricking your phone its a known issue
Goodnight jummy:what:
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
No. You just flat out said you can't flash from ICS CWM. I was clarifying that is not true. Don't take it personally.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
OP: Phone is bricked, need to take to Sprint for replacement. More on your problem here:
Stuck at Data.img
And to see what the general advice is on avoiding this:
How Not To Brick Your E4GT
@Carbajal, yes it's your LG cable. I have same problem with same cable (from Optimus S). Sammy cable will fix it if you still have it. I forget the specific reason why but in layman's terms it was explained to me that the Sammy cable may have a longer pin which triggers the recognition. If you search the Q&A forum you should be able to find the thread.
MJHawaii said:
Get back into DL mode and flash back to stock and invest in a usb download jig its 5$ and comes in handy in soft brick and bootloop situations
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
i cant get the odin program to see my phone!! i can get into DL mode but am not able to flash anything through it...why?? i tried two different computers and three different cables but no go
Carbajal3009 said:
i cant get the odin program to see my phone!! i can get into DL mode but am not able to flash anything through it...why?? i tried two different computers and three different cables but no go
Click to expand...
Click to collapse
As you didn't clarify it before, did you try the Sammy cable provided with the phone? If that isn't doing it you may want to check Device Manager (assuming Win PC) and make sure nothing is disabled or not working properly. I mention this as it happened to me once when I tried to reassign the COM ports to use CDMA Workshop.
garwynn said:
@Carbajal, yes it's your LG cable. I have same problem with same cable (from Optimus S). Sammy cable will fix it if you still have it. I forget the specific reason why but in layman's terms it was explained to me that the Sammy cable may have a longer pin which triggers the recognition. If you search the Q&A forum you should be able to find the thread.
Click to expand...
Click to collapse
Word!
It freaked me out when I first tested this phone months ago since I came from Optimus S also. Didn't want to unpack all the accessories so just used the cable that came with the LG Optimus S, would charge, but no data. Thought the USB port on the E4GT was busted. Then tried 2 more LG Optimus S cables with the same result. Was about to return the phone when on a whim unpacked the flimsy looking Samsung cable and voila, it worked.
That flimsy looking Samsung cable has gotten me through over 300 flashes now w/o ever having a cable related problem.
garwynn said:
OP: Phone is bricked, need to take to Sprint for replacement. More on your problem here:
Stuck at Data.img
And to see what the general advice is on avoiding this:
How Not To Brick Your E4GT
Click to expand...
Click to collapse
ross, this is your problem. i'm in the same boat. in that thread, someone was able to repartition the /data partition to his sdcard and it worked (albeit at the cost of sdcard space). worth a shot, but keep up with that thread as it's pretty active.
Thanks guys who inputed about that LG cable. I took me a while to find my original sammy cable!! but my phone workds again and im soooooo happy. Thanks a bunch.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
garwynn said:
OP: Phone is bricked, need to take to Sprint for replacement. More on your problem here:
Stuck at Data.img
And to see what the general advice is on avoiding this:
How Not To Brick Your E4GT
Click to expand...
Click to collapse
I did this sunday morning, trying out AOKP. Read that there was a possibility for corruption, did it anyway. after deciding it was too buggy for my liking as a daily driver, i attempted to go back. Tried my USB Jig with no luck.
Took it into Sprint on Monday, an hour later the tech tells me its toast. (Tell me something I don't know). I tried so hard to weasel out a new White model.
I've got a refurb'd black model and i'm suspecting there's a few issues with it. Its completely stock, no root. I've had to reboot four times today already from not turning on or coming out of sleep. Then every so often the phone will not stop vibrating during a haptic feedback response. I've turned haptic and vibrate off, but it still locks up on occasion. Funny but weird as hell. Probably gonna take it in later this week and try my luck again at getting a new model.
So yesterday I flashed the new aokp build 39 know all the risks of bricking but i thought my phone was immuned lmao no jk but i have been flashing for a few months now sometimes going back to el26 and sometimes i just flashed using ics recoveries wiped data and all and since i never bricked I thought it was safe, but yesterday i was not so lucky like i said i was on aokp 39 and wanted to go back to wicked so instead of going back to el26 i used the included cwm recovery and went to restore my backup and to stop this story from dragging on it restored but when it booted back up it would not go past samsung screen i cld get into recovery and odin mode tried sfhub one click same thing stuck at samsung logo everything i tried nothing worked brought it to sprint today I was honest told em i was rooted and explained i already tried to flash back to stock their guy said' "i'll be able to get it." Lol i said okay but I knew he could not he came bck said he couldnt i have tep and he ordered me a new one and i can get it tomorrow with no charge... Just an fyi u can get ur phone replaced for nothing even if u brick so i have my tablet to get me by til tomorrow so the cwm included in aokp 39 is not safe...
Sent from my K1 using xda premium
"MOD EDIT: Always use the Stock CWM5 recovery for anything you want to flash. Do not use the recovery that comes with this rom to flash or do anything with. "
You kind of set your self up there. The thread states that AOKP B39 doesn't come with a safe recovery. Either way, have fun with your new E4GT
MochaCharok said:
"MOD EDIT: Always use the Stock CWM5 recovery for anything you want to flash. Do not use the recovery that comes with this rom to flash or do anything with. "
You kind of set your self up there. The thread states that AOKP B39 doesn't come with a safe recovery. Either way, have fun with your new E4GT
Click to expand...
Click to collapse
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
dafluke24 said:
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
Click to expand...
Click to collapse
Boom. Looks like you're right -- oh well. Sorry OP.
Same thing happened here
sbeekman said:
So yesterday I flashed the new aokp build 39 know all the risks of bricking but i thought my phone was immuned lmao no jk but i have been flashing for a few months now sometimes going back to el26 and sometimes i just flashed using ics recoveries wiped data and all and since i never bricked I thought it was safe, but yesterday i was not so lucky like i said i was on aokp 39 and wanted to go back to wicked so instead of going back to el26 i used the included cwm recovery and went to restore my backup and to stop this story from dragging on it restored but when it booted back up it would not go past samsung screen i cld get into recovery and odin mode tried sfhub one click same thing stuck at samsung logo everything i tried nothing worked brought it to sprint today I was honest told em i was rooted and explained i already tried to flash back to stock their guy said' "i'll be able to get it." Lol i said okay but I knew he could not he came bck said he couldnt i have tep and he ordered me a new one and i can get it tomorrow with no charge... Just an fyi u can get ur phone replaced for nothing even if u brick so i have my tablet to get me by til tomorrow so the cwm included in aokp 39 is not safe...
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Don't feel too bad. I did something similar the other day and experienced a brick myself. I now have a new E4GT, free of charge. I made an elementary mistake, but I knew the risks.
I do not believe the new AOKP posted has a safe updater binary (since they did not say so) which makes it a bad deal to flash in ICS recovery still even a safe one.
Hate to hear this. But seriously OP. Thanks for actually owning up to it. When I bricked mine I did just like you. Sbrissen got me on Gtalk and apologized for bricking my device. I told him that I had not been aware that he had come to my house and flashed my phone for me. He said he hadn't and so I said then how is it your fault. I've seen so many times where someone bricks their phone and blames the dev. So props for being a stand up guy. Also. It is amazing what you can get with sprint reps when you just shoot straight with em isn't it. Glad you got it worked out.
Yea same here bricked mine and was titally my fault did it the same day I got the device and have no insurance really liked this device from the little I got to use it maybe one day I can afford another and nit be so stupid next time but least I know I'm not alone
sent from my Verizon Wireless HTC EVO 3D
@ruffneckZeVo,
First off no need to post the same thing in 3 threads. You'll get a reply.
Even though you didn't have insurance did you try taking it in to get it to Sprint for replacement? Samsung should also cover it but Sprint will probably be the easier solution if possible.
As for modified .PIT files we don't have one for the E4GT - it was quickly recommended not for long term use, so replacement has been the recommended solution. I don't believe anyone has been outright denied one yet - but I could be wrong.
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
dafluke24 said:
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
Click to expand...
Click to collapse
same... second brick too. Should've been more careful though.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
anti-up said:
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Make sure you odin to a stock samsung rom(it will fail at data.img, so just unplug it there. This most hints that youre on a non stock rom such as the warning icon.) and then use a usb jig(~$20) This gets rid of all binary flashes in download mode.
That's if you can turn the phone on. Some can and some can't
garwynn said:
@ruffneckZeVo,
First off no need to post the same thing in 3 threads. You'll get a reply.
Even though you didn't have insurance did you try taking it in to get it to Sprint for replacement? Samsung should also cover it but Sprint will probably be the easier solution if possible.
As for modified .PIT files we don't have one for the E4GT - it was quickly recommended not for long term use, so replacement has been the recommended solution. I don't believe anyone has been outright denied one yet - but I could be wrong.
Click to expand...
Click to collapse
Sorry just anxious to get this fixed I had the device one day and really liked it its not on sprint I got it from cl and flashed to vzw so sprint isn't an option to fix it ill find another asc thanks for the info
sent from my Verizon Wireless HTC EVO 3D
For what it's worth....
I've had my SG2 E4GT since the middle of april. Rooted it about 3 days after having bought it. And have been using Blue Kuban's Rom ever since.
Sadly, for some dumb reason, I decided to try out the new AOKP build -.-
Ironically I think I bricked it trying to flash from Blue Kuban back into a Gingerbread EL29 build...... But it had Team Rogue's CWM 5.1.0 or 5.0.1 one of them -.-
Either way, after flashing AOKP went to reboot and black screen, only blue blinking LCD light of doom.
I've ordered a USB Jig so I can try to use that to reboot into recovery... but I'm prolly messed eh?
Should probably try going to the sprint store where I got it? I do have T.E.P.
anti-up said:
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I did the same thing. I felt bad but well you know. Anyway it worked great, they even had it in stock.
Ok so a little after midnight i rebooted my phone cuz it was being flaky.
Then it got stuck on the Cyanogen SGS boot screen from PAC 20.1 I tryed to ODIN cwm-5.0.2.7-epic4g.tar.md5. I got that to stick but every time i would flash a rom it would get stuck and end up and the samsung boot screen again. i tryed to flach cm9.1 and it hang at the BLM MTD part for a very long long time. then it went to the gray screen(the backgound of cwm 6) so that didn't work. So i tryed to ODIN stock EL30 EC05 just like hear http://forum.xda-developers.com/showthread.php?t=1052813
Well that ended with the phone booting up after about 40 minues. But i could not unlock the dam thing. So i did it again & left it for an hour & now its just siting there 12:19 on the clock but i cant unlock the phone. the sprint 4G boot aniy was/is all chopy and the sound cuts in and out. IDK i think my Epic is Epicing F(ced
(i'v been ODINing & reading xda all night:crying: )
Any ideas?
How about just going back to 100% stock FC09? Use re-partition, and you may even want to consider EFS clear (unless not on Sprint). Try that and let it run on that for a day. Note any issues that appear.
If no issues, then try to flash another rom.
Worst case scenario, your flash memory is on it's last leg and heading to become kaput. Flash memory only has so many reads & writes before it kicks the bucket. Constant flashing of roms over the lifetime of this phone diminishes the lifespan faster than a regular user.
A regular user wouldn't even come close to the read/write red zone for this flash memory, but a custom rom user/tester could (especially given the age of our phone).
Which is precisely why I find a somewhat stable ROM and stick with it for about 3 months, then i update/switch ROMs
Sent from my SPH-D700 using Tapatalk 2
I typically only flash stable roms and stick with one for 4-8 months before doing a fresh Odin, re-root and new rom flash. I'm your normal user here; I stick with what I know works.
jeffreyjicha said:
Which is precisely why I find a somewhat stable ROM and stick with it for about 3 months, then i update/switch ROMs
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Yes that kinda what i have done.
@nikon120 i tryed FC09 100% stock. i didn't try clearing EFS & yes i'm still on Sprint.
IDK i'm guna call sprint and see what they will give me to keep me?
zman519 said:
IDK i'm guna call sprint and see what they will give me to keep me?
Click to expand...
Click to collapse
A big ole nothing. I've tried to get discounts and upgrade fees waived before, and they have given nothing. I'm a 10+ year customer.
Once a nicer than Nexus 4--Nexus device comes out, or if Sprint's suck-tacular service becomes even more sucky, I'm jumping to T-mobile.
nikon120 said:
A big ole nothing. I've tried to get discounts and upgrade fees waived before, and they have given nothing. I'm a 10+ year customer.
Once a nicer than Nexus 4--Nexus device comes out, or if Sprint's suck-tacular service becomes even more sucky, I'm jumping to T-mobile.
Click to expand...
Click to collapse
SGS III Purple for $0.99 FTW
I really loved my Epic & i'l be back around the forums, my buddy has a busted Epic so maybe i can make one working phone out of the two.:good:
zman I have the EXACT problem with my Epic 4g, it's brand new I have only had it a handful of days and I haven't a clue as to what caused this error, my clock also reads 12:19 and the screen is unresponsive, so I can't slide unlock the screen to get usb debugging checked either. I am by no means new to android, flashing roms or anything else so this wasn't some noob error on my part.
I have messaged QBKing77 and he is as perplexed as I am, and well I figure if he can't figure it out, we might just be screwed.
Did you get yours fixed? If so could you please share what you did.
If i get it fixed I'll be sure to let you all know how i did it.
I have been playing with my new Purpal SGS III
Sent from my SPH-L710 using xda app-developers app
nerdygadgetguy said:
zman I have the EXACT problem with my Epic 4g, it's brand new I have only had it a handful of days and I haven't a clue as to what caused this error, my clock also reads 12:19 and the screen is unresponsive, so I can't slide unlock the screen to get usb debugging checked either. I am by no means new to android, flashing roms or anything else so this wasn't some noob error on my part.
I have messaged QBKing77 and he is as perplexed as I am, and well I figure if he can't figure it out, we might just be screwed.
Did you get yours fixed? If so could you please share what you did.
Click to expand...
Click to collapse
Did you ever get your Epic back to life?
Sent from my SPH-L710 using xda app-developers app
Nope. I had it fixed then it went back to the same old issue. I've tried every version of odin, Heimdall and using every possible pit, .tar and md5 file combination I can come up with and I cannot remember what I used the first time to fix it. blah
Did you get yours fixed or figure out what the problem was? If I ca
zman519 said:
Did you ever get your Epic back to life?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse