Hard bricked during CM9 upgrade from UCLD3 Leak?!
- Thread starter avus_m3
- Start date
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.
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
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!
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/kerne...59551eaf5afc3d68f2da96b0249937bd5e13#L10R1881
Samsung attempted to fix it with:
https://github.com/Entropy512/kernel_galaxys2_ics/commit/d069cc5cb9f0fd9409ea10d4037e4c0e68701b8e
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.
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
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:
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.
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.
LD3 doesn't cause hard bricks I've been using it since it dropped now with absolutely no problems and I flash like a ************
Sent from my SGH-I777 using Tapatalk 2
Sent from my SGH-I777 using Tapatalk 2
Havent you been reading? Something with recent Samsung bases seems to be causing this, so it was a cause
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Just wanted to chime in from the ET4g community to confirm this is exactly what happens to us on ICS leaks. As stated above it only occurs when flashing on a CWM repack kernel. Mobile ODIN is safe. It Is permanent hardware damage. Nothing will fix it, but I believe that some bricks (ones that will boot to download but can't get past data.img in odin) can have low level repartitions set to avoid the factory data partition. Never done it myself and can't find the link.
Sorry to hear you guys have same bug. I just wanted to confirm it happens in CWM ICS as stated above. To flash or nandroid we Odin or mobile Odin a repacked GB kernel and flash from that CWM.
Sent from my SPH-D710 using xda premium
Sorry to hear you guys have same bug. I just wanted to confirm it happens in CWM ICS as stated above. To flash or nandroid we Odin or mobile Odin a repacked GB kernel and flash from that CWM.
Sent from my SPH-D710 using xda premium
Yup. It may only affect a small percentage of users, which is why we get dangerous posts from idiots like virus1x of "it's safe for me so it's safe for you" - For example, gokhanmoral was able to wipe multiple times with siyahkernel 3.1rc6 (which was based off of the SHW-M250L update4 sources), but when he released it, multiple users hardbricked. Task650 was able to flash multiple times without trouble - but others hardbricked.
It may only be 2-3% of users that will hardbrick - but that's still WAY too high considering that a properly working kernel has 0% chance of hardbricking unless you do something really stupid, and even then, until this recent rash of broken ICS kernels, JTAG recovery could resurrect you for $50 or so.
Thanks for flaming me but according to you and post above the kernel leak is what bricks it during the flashing of modem not the modem so my statement that the radio is not the cause was correct its the kernel because if they go to back to gb kernel and flash no problems at all
Sent from my SGH-I777 using Tapatalk 2
Last edited:
So which, if any, of the three ICS kernels available in I777 development forum are safe to use?
NEAK, Siyah, CM9 stock and Entropy's are based on update4 sources AFAIK. That seems to be the safe base.
I believe the safest are cm9, and neak entropy and siyahkernel. And a few others posted in our xda however when in doubt Odin flash your **** or mobile Odin
Sent from my SGH-I777 using Tapatalk 2
dafuq? That's one of the most incomprehensible posts I've ever read.
You claim that the UCLD3 leak kernel doesn't cause hardbricks because you've flashed many times with it, but the fact is - IT DOES. Just because you were OK doesn't mean others will be, as evidenced by the fact that gokhanmoral was safe when he tested his rebase on the M250L sources, and task650 flashed many times using the UCLD3 leak without problems. It has nothing to do with modems, I have no freaking clue why you're ranting about modems now.virus1x said:
Only 3.1rc6 is problematic - all other releases are safe.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7
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/kerne...59551eaf5afc3d68f2da96b0249937bd5e13#L10R1881
Samsung attempted to fix it with:
https://github.com/Entropy512/kernel_galaxys2_ics/commit/d069cc5cb9f0fd9409ea10d4037e4c0e68701b8e
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.3
Yup. It may only affect a small percentage of users, which is why we get dangerous posts from idiots like virus1x of "it's safe for me so it's safe for you" - For example, gokhanmoral was able to wipe multiple times with siyahkernel 3.1rc6 (which was based off of the SHW-M250L update4 sources), but when he released it, multiple users hardbricked. Task650 was able to flash multiple times without trouble - but others hardbricked.
It may only be 2-3% of users that will hardbrick - but that's still WAY too high considering that a properly working kernel has 0% chance of hardbricking unless you do something really stupid, and even then, until this recent rash of broken ICS kernels, JTAG recovery could resurrect you for $50 or so.2
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-62
You're ridiculous. Why are you on XDA. You shouldn't even be flashing anything to your devices with the level of intellect that you've shown here. The poop I took this morning made more of a difference here on XDA then you did in your post.
2Hmm, odd, that's the most likely way to hose you...
Either way, do NOT flash anything or nandroid anything using the CWM-repacked UCLD3 kernel. Do NOT restore any Nandroids made with that kernel. Heimdall/Odin something else FIRST.
