Post Reply

Hard bricked during CM9 upgrade from UCLD3 Leak?!

OP avus_m3

23rd April 2012, 04:46 PM   |  #101  
capathy21's Avatar
Senior Member
Flag Pineville,La
Thanks Meter: 49
 
228 posts
Join Date:Joined: Jul 2011
More
Awesome thanks for that info
23rd April 2012, 09:17 PM   |  #102  
OP Senior Member
Thanks Meter: 25
 
142 posts
Join Date:Joined: Mar 2009
Forgot to mention, I stopped by the service center Friday and picked up what appears to be a new phone (not refurbished)! Not only that...after talking to the girl behind the counter she hooked me up with a new (spare) battery shipped to my house. Time to root and get back on CM9 (or AOKP). From now on the only "leak" I will have is the one I leave in the toilet.
26th April 2012, 07:11 PM   |  #103  
Junior Member
Thanks Meter: 1
 
9 posts
Join Date:Joined: Apr 2012
Just thought I'd post an update on my hard bricked phone:
Josh from Mobile Tech Videos got a chance to look at my phone today and according to him the eMMC chip is toast. He was unable to recover it using JTAG. Could it just have been a coincidence that several people hard bricked around the same time or did flashing have something to do with the eMMC chip becoming defective?
Will take my phone back to an ATT service center as soon as I get it back. I don't think I will have much of an issue getting a replacement
The Following User Says Thank You to w1209 For This Useful Post: [ View ]
26th April 2012, 07:24 PM   |  #104  
OP Senior Member
Thanks Meter: 25
 
142 posts
Join Date:Joined: Mar 2009
Wow...good thing your covered.
26th April 2012, 08:18 PM   |  #105  
nakedninja42's Avatar
Senior Member
Flag Bay Area, CA
Thanks Meter: 700
 
1,975 posts
Join Date:Joined: Oct 2009
Donate to Me
More
Quote:
Originally Posted by w1209

Just thought I'd post an update on my hard bricked phone:
Josh from Mobile Tech Videos got a chance to look at my phone today and according to him the eMMC chip is toast. He was unable to recover it using JTAG. Could it just have been a coincidence that several people hard bricked around the same time or did flashing have something to do with the eMMC chip becoming defective?
Will take my phone back to an ATT service center as soon as I get it back. I don't think I will have much of an issue getting a replacement

Thanks for letting us know, shouldn't be a problem getting a replacement. Best of luck!
26th April 2012, 10:05 PM   |  #106  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,470
 
13,360 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by w1209

Just thought I'd post an update on my hard bricked phone:
Josh from Mobile Tech Videos got a chance to look at my phone today and according to him the eMMC chip is toast. He was unable to recover it using JTAG. Could it just have been a coincidence that several people hard bricked around the same time or did flashing have something to do with the eMMC chip becoming defective?
Will take my phone back to an ATT service center as soon as I get it back. I don't think I will have much of an issue getting a replacement

Right now, the general consensus is:
With the exception of I9100 leaks and kernels built from I9100 update4 sources, Samsung ICS kernels for Exynos4 devices have a SERIOUS bug that causes them to do permanent damage to the eMMC chip. This is most likely to occur when doing a major erase operation (such as a wipe in CWM, but a wipe/factory reset in stock 3e recovery is likely to be just as dangerous)
This includes kernels from:
All Epic 4G Touch ICS leaks
All GT-N7000 (International Note) ICS leaks
The UCLD3 I777 leak (probably all of the I777 ICS leaks)
Anything built from the Korean SHW-M250S/K/L bases - this is why there was just a rash of hardbricks with SiyahKernel 3.1rc6 - it was based off of the Korean M250L sources.

Right now the suspicion is that it is due to this:
https://github.com/Entropy512/kernel...d5e13#L10R1881

Samsung attempted to fix it with:
https://github.com/Entropy512/kernel...7e4c0e68701b8e

but they only disabled TRIM and not ERASE (which are related)

Unfortunately there's no way to test this without risk of hardware damage... you can't declare something fixed unless you can reproduce the problem - but you can reproduce this problem once per device repair. So really only Samsung can declare it fixed - but then they'd have to actually interface with the development community.
The Following 7 Users Say Thank You to Entropy512 For This Useful Post: [ View ]
30th April 2012, 04:06 AM   |  #107  
kLAcK107's Avatar
Member
Thanks Meter: 5
 
81 posts
Join Date:Joined: Apr 2011
I also got this hard brick.

I flashed from LD3 to Showstock2 to LD3 over the course of the week.Today I tried to goto AKOP.

The phone will not turn on, and charging it just makes it hot.


UPDATE:
Got a new phone from AT&T no charge, within 30 days
Last edited by kLAcK107; 30th April 2012 at 07:50 PM.
30th April 2012, 08:47 PM   |  #108  
Junior Member
Thanks Meter: 1
 
9 posts
Join Date:Joined: Apr 2012
Thanks for the info Entropy, that makes sense.

I was able to get a replacement from the AT&T Service Center. Since my battery was fully drained they also sent me a replacement, so now I have two batteries as well as a new phone
30th April 2012, 11:18 PM   |  #109  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Apr 2012
Quote:
Originally Posted by avus_m3

Wow...good thing your covered.

Definetely good, nice having that coverage
1st May 2012, 05:22 AM   |  #110  
Junior Member
Thanks Meter: 1
 
5 posts
Join Date:Joined: Feb 2011
More
Hoping to offer what I did just in case I can help anyone with a possible bricking situation.
This afternoon I wanted to install a non-secure email client to remove that stupid password but in doing so through CWM I was never able to power back up. The phone had similar symptoms to what people are saying here.
I wasnt able to boot up to do anythign useful to my phone so I tried to flash the stock kernel (The one Entropy has listed) through Odin and while that seemed to work the one would still not come up completely. It was in a rolling reboot until I booted up in the Stock recovery and did a factory reset/clear data... At that point the phone came back up and I was able to root it again and then restore my AOKP nandroid.

I know these are trivial steps and the symptoms for me may be different but just in case they can help someone I posted them.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes