yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] avus_m3:
PM'd...Hopefully I can get this issue resolved before the weekend. This sucks :(

Lessons learned:

1) Stay away from "leaked" builds

2) Make sure the battery is fully fully charged for a flash

3) Have a jig around

4) Let others try out roms for awhile before thinking about using them...DON'T be the guinea pig!!
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
Isn't the first time to be a guinea pig and won't be the last!! :rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] w1209:
My phone was nearly 100% charged when I flashed, so I'm not sure if that had anything to do with it. My homemade USB jig did not do anything (it has worked plenty of times before to reset yellow triangle, and saved me once before from a bad flash). Good luck on your jig, let us know if it worked!

I definitely agree with lesson 4, I'll be patient next time and save another $50 :D
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Did those who hardbricked do a Nandroid restore to CM9 before flashing the nightly?

Flashing CM9 from UCLD3 should've been safe - but Nandroiding back using ktoonsez's kernel would almost surely hardbrick you because he decided to make his own recovery.fstab instead of using a known good one.
[AT&T Samsung Galaxy S II SGH-I777] avus_m3:
I was on CM 9 ->

CWM updated to UCLD3 ->

Nandroid restore back to my stock rooted GB setup ->

CWM updated to UCLD3 ->

CWM updated to CM9 during which it BRICKED
[AT&T Samsung Galaxy S II SGH-I777] robotohshs:
no i did not restore from nandroid
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Hmm, 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.
[AT&T Samsung Galaxy S II SGH-I777] robotohshs:
you think i should replace my phone or wait to see if theres a fix?
[AT&T Samsung Galaxy S II SGH-I777] avus_m3:
So is there any point in trying to build a jig or would it be a wasted effort?
[AT&T Samsung Galaxy S II SGH-I777] Kinador:
well i just assumed my phone died of natural causes, but now i'm not to sure.

Like someone mentioned earlier in this thread or under Tasks leaked ld3 thread i was in mid flash or the beginning i wasn't exactly watching the bar, when the screen went black and nothing would bring it back, and i tried everything i could find useing search including stuffing it in the freezer.

I don't remember the exact order, but i've been flashing it since maybe a month after i bought it in Oct. i was useing phonebricker the night before and i was re-flashing to aokp build 32, i had it on there atleast once before.

I don't useually recover useing the nandriod backup, although i've made a few. My method is reboot into recovery, factory data reset then the cleaner scrpt. then installing the zip.

Well after trying everything listed here i called support and they were sending me a new battery. I went to the AT&T store i bought it and they reffered me to the AT&T support center here locally. They agreed my phone was dead and replaced it.

An observation after getting the new phone. Even with the battery out and plugging in the phone the lights blink. The one i had to replace did nothing.

Well sorry to ramble on, thanks to all you Devs and the community as a whole.
[AT&T Samsung Galaxy S II SGH-I777] thershope:
Same Behavior as your but I reported this on 17th April

Here is the post which I posted on 17th April with the same nature.

17th April 2012, 06:48 AM

http://xdaforums.com/showthread.php?p=24951502#post24951502

I did not get any reply in that forum. I am glad that there is a separate thread about my issue

Same.

I was in LD3 .. Did a nandroid back up for future use --> Flashed CM9 nightly --> HardBrick

(I did not restore from Nandroid anytime. Just took a backup that's it)

I have done 2-4 flashes before (CM9->LC3->CM9->LC5) without any problem. Only difference this time being creating a Nandroid Backup before doing anything.

Please keep updating this thread if anything happens.

Also, please let me know if this can be solved by JTAG.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Replace it or have it JTAGed
[AT&T Samsung Galaxy S II SGH-I777] jpgalaxy:
I did not do a nandroid backup this time when I flashed, but there was an existing nandroid of LD3 that I had done previously. I had restored to this backup previously but was noticing little issues that had started to come up (wifi being wonky, exchange not sending emails) which is why I was flashing to a fresh install of AOKP.

I went into my local AT&T device support center and they exchanged it with a refurb. I'll be staying away from LD3.
[AT&T Samsung Galaxy S II SGH-I777] kuduku:
no Nandroid back up used in any flashing . It was full reset and cache and dalwik wipes
[AT&T Samsung Galaxy S II SGH-I777] mzaur:
Mine came with KK6 too... I successfully flashed KH7 found here and had no issues
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
Already had the file, I was curious if anything is wrong with KK6 bootloader other than not allowing flash counter to reset.

I'm already on shostock2 and enjoying the new my new phone.
[AT&T Samsung Galaxy S II SGH-I777] Sengfeng:
I had the leak installed and had problems when I re-installed a rooted stock rom via cwm. I got lucky - Mine hung at the Samsung logo screen and I was able to re-flash via download mode.
[AT&T Samsung Galaxy S II SGH-I777] kuduku:
confirmed screwed . Jig did not work , tried all means and methods . No reaction no lights nothing . tried everything from here http://xdaforums.com/showthread.php?t=1402286
[AT&T Samsung Galaxy S II SGH-I777] TonyStark R.I.P.:
I created this

Library

more then a year ago. As it did then, it still helps now. There's quite a bit of info in here but the stories I've herd are that after trying a few things people would find things that would help them out. Take a look through and remember to breath:)
[AT&T Samsung Galaxy S II SGH-I777] capathy21:
Mine did it to. Were they pretty cool at the service center? The closest one to me is about 2 hours away but its worth the gas not to have to go the weekend without a phone since I am on call. I noticed there is no contact phone number for the service centers to verify they have the replacement in stock. In the event they do not have any sgs2's do you think they would give something comparable, or would I just be screwed lol

Thanks
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
Did you check out the link I posted for the service center? I found the number to mine on there. I was in and out of the service center with my new phone in less than 10 minutes. The guy was cool, I told them that the phone was acting funny so I did a factory reset from settings and the phone never booted up after restart. He tried another battery and plugged it into their PC and said give me 5 minutes to get your new phone ready :-) . The service center should have it in stock but it definitely doesn't hurt to call in advance wit the distance you have to go. I'm less than 2 miles from mine so it definitely made things easier for me.

Here is the link again. http://www.att.com/esupport/article.jsp?sid=KB91429&cv=820#fbid=CIMrzt20h0e

It shows I777 as something they carry.
[AT&T Samsung Galaxy S II SGH-I777] capathy21:
Sorry I did miss your link earlier! Thanks for the info:)
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
no worries, hope you the best of luck!
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Winning
[AT&T Samsung Galaxy S II SGH-I777] thershope:
Got my Replacement with AT&T

Went to AT&T and back with new (Or Refurbished, either way am Happy) phone within 20 minutes.

I was very lucky I must say.

Thanks for all the help guys.
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
I was told that refurb has a special sticker in addtion to the imei sticker to indicate refurbished.
[AT&T Samsung Galaxy S II SGH-I777] jpgalaxy:
I only have the one sticker under the battery that includes the IMEI, but I suspect its a new sticker and the serial number probably indicates the refurbished status.
[AT&T Samsung Galaxy S II SGH-I777] thershope:
I also think so. I also have only one sticker but that is totally different in size and placement than my other phone.

SO, I also believe the serial number might say if the phone was refurbished.
[AT&T Samsung Galaxy S II SGH-I777] w1209:
You guys are making me wish I took mine to a service center instead of sending it to Mobile Tech Videos :D

Oh well, at least I will have my brand new phone back (is is a little over a month old) and will keep my 1 year warranty instead of 3 month on a refurb.

Lesson learned! I think I'm just going to stick with stock instead of trying experimental leaked ROMs
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Nothing wrong with trying anything experimental, just gotta make sure to do a loooootta reading first. I know how u feel tho, it can seem daunting and scary since these things cost so much. ;-) you'll be fine if u read and search and use common sense. Good luck all, happy flashing.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
And then every once in a while, a package comes along with a serious, dangerous bug in it. No matter how much study you do, or what knowledge you have, you might not be able to avoid the problem. And what other explanation is there for this series of events, than a nasty bug? I dodged the bullet myself, but not because of any knowledge I have. I just never used the nandroid backup, or flashed to an aosp rom. I also never flashed the one-click leak, as I know better than that. Fortunately, this sort of thing happens only very rarely.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Yup - The I777 community has been flashing stuff for months, and until this the only people who had serious problems are those that Odined I9100 bootloaders (and they got lucky, those were functional enough to recover) or flashed an I9100 PIT file.

To my knowledge, this week is the first time anyone has hardbricked when flashing anything in CWM that was meant for their device, and the common theme is an improperly repacked leak kernel with CWM.

There was a similar rash of problems in the N7000 community a couple of weeks ago, it even nailed xplodwild who is (in my opinion) one of the best kernel developers around.
[AT&T Samsung Galaxy S II SGH-I777] Lekerstein:
Thought I'd add my two cents. I started on CM9 4/17. Did a nandroid backup and flashed the leak (LD3) after Task updated the thread like 1 or 2 days ago. Looked around a bit and decided to go back. I did do a full wipe of everything going into the leak, but not back out. I restored from the nandroid. It originally didn't restore cuz of an md5 mismatch but I forced the md5 to agree (ballsy move, I know) and tried again. Boom, restored back to CM9 4/17 no problem. I haven't flashed any other nightly yet.

Edit: I see this thread was started before Task updated the leak. So it looks like I was a guinea pig on the update unknowingly. Thank goodness it was fixed....
[AT&T Samsung Galaxy S II SGH-I777] Kinador:
I was one of the unlucky few to hard brick

I was wondering if we had conformation on exactly what It was. I've read both this thread and what was talked about in Task's.

I only ask because I'm still worried about doing a nandroid backup or restoring. I get there is always a risk, and I'm still bouncing back and fourth from Task's ld3 leek and his aotk + his theme, awesome btw.

Well thanks ya'll.
[AT&T Samsung Galaxy S II SGH-I777] timmetal6669:
Cm9 its the devil. You should see how many bricks over in the epic 4touch section. Cm9 needs to be pulled and tested thoroughly. We know they aren't responsible... Well they're right they know about it and release it anyway. That is irresponsible.
[AT&T Samsung Galaxy S II SGH-I777] TOA Duck:
Really dude. Lol
[AT&T Samsung Galaxy S II SGH-I777] SeanHacker:
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. :D
[AT&T Samsung Galaxy S II SGH-I777] Kinador:
I'm not trying to place blame. I took the risk in flashing my phone hundreds of times, and hell I didn't last a whole day with the replacement being stock.

I'm loving what you guys are doing. I was just asking if we knew for certain. Then again, like it was stated earlier sometimes a bad package comes along.

Anyway, ya'll keep it up and I'll keep fiddling. In between triple wipes ofcourse
[AT&T Samsung Galaxy S II SGH-I777] chibixzero:
Eheehe dooty
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
That's funny are we using Epics? Nope. The devils been running stable as fvck for weeks now so he must be doing something better then the sheep.

Now where's my Slayer and Mayhem ringtones??? You would think Satan would include them with his rom!
[AT&T Samsung Galaxy S II SGH-I777] mgd76:
That's not a dude, it's "The Waterboy"'s mom.

+1 lol
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Cm9 is the reason my dad left my mom when I was 10. Damn u cm9. Damn u.
[AT&T Samsung Galaxy S II SGH-I777] capathy21:
I just wanted to make sure that the issue that caused the hard bricks was taken care of. I just got my replacement and dont want to mess it up again. I just rooted the new device and have installed the NEW corrected leak of LC5. Am I able to flash between LC5 and Cm9, or LC5 and Tasks AOKP? I do not generally create a Nandroid so I would be wiping before I flash anything. Never had any issues before when switching between these roms but I am kind of unsure now that I have experienced a hard brick. Thanks
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
The issue has been resolved in the leaks. I have not flashed since Task updated the leaks but I had no problems moving from shostock2 to aokp and nandroid back to shostock2 with my replacement phone.
[AT&T Samsung Galaxy S II SGH-I777] capathy21:
Awesome thanks for that info :)
[AT&T Samsung Galaxy S II SGH-I777] avus_m3:
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.
[AT&T Samsung Galaxy S II SGH-I777] 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
[AT&T Samsung Galaxy S II SGH-I777] avus_m3:
Wow...good thing your covered.
[AT&T Samsung Galaxy S II SGH-I777] nakedninja42:
Thanks for letting us know, shouldn't be a problem getting a replacement. Best of luck!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
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.
[AT&T Samsung Galaxy S II SGH-I777] kLAcK107:
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
[AT&T Samsung Galaxy S II SGH-I777] w1209:
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 :D
[AT&T Samsung Galaxy S II SGH-I777] jsquaredgto:
Definetely good, nice having that coverage:)
[AT&T Samsung Galaxy S II SGH-I777] Dux302:
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.
[AT&T Samsung Galaxy S II SGH-I777] Virus1x:
LD3 doesn't cause hard bricks I've been using it since it dropped now with absolutely no problems and I flash like a ************
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Havent you been reading? Something with recent Samsung bases seems to be causing this, so it was a cause
[AT&T Samsung Galaxy S II SGH-I777] abhaxus:
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.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
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.
[AT&T Samsung Galaxy S II SGH-I777] Virus1x:
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
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
So which, if any, of the three ICS kernels available in I777 development forum are safe to use?
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
NEAK, Siyah, CM9 stock and Entropy's are based on update4 sources AFAIK. That seems to be the safe base.
[AT&T Samsung Galaxy S II SGH-I777] Virus1x:
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
[AT&T Samsung Galaxy S II SGH-I777] votinh:
Didn't Siyah 3.1r6 fry the SGS2?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
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.

Only 3.1rc6 is problematic - all other releases are safe.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
To my recollection, ktoonsez's releases went from 3.1 rc5 to 3.1 final.

But what's not clear to me is what releases were based on the SHW-M250L update4 sources that Entropy says was the cause of the bug.
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Is this really that hard to comprehend? They wouldn't keep it up to download if they knew it was causing hard bricks. Its gone now. Done. Poof. Good lord people its called common sense. Helpful in situations such as this.
[AT&T Samsung Galaxy S II SGH-I777] abhaxus:
In our community there are still CWM repack released for every leak, and it is still unsafe to wipe anything. And people still wipe. You guys are lucky to have a phone similar enough to intl sgs2 that you have source, but I think given what I've read here, I'd probably odin a GB kernel and wipe/flash from there.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
darchstar and sbrissen are working on forward-porting your CDMA and WiMAX drivers to the I9100 update4 base - I think they have everything but CDMA and WiMAX working right now.

The international Note has the same issue - leaks are dangerous. Good thing the I9100 update4 source was also usable for Note with not much work. :)
[AT&T Samsung Galaxy S II SGH-I777] twstd4lfe:
So since I was an idiot weeks ago and restored my bricked i777 with the broken ucld3 one click..it brought it back from a bad cm9 flash but now all this talk makes me want to downgrade.

Can I use I777UCKH7-CL503881 Stock Binaries from the download repository to restore everything to factory safely?
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
UCLD3 system isn't a problem, it's only the original UCLD3 kernel. You could flash a safe kernel and then use CWM from there, or to be more careful, you could flash a custom Gingerbread kernel and flash from recovery.

As far as using I777UCKH7-CL503881 from the download repository, if you don't need to flash bootloaders, I would use the one from the return to the store or warranty guide, which doesn't have bootloaders.
[AT&T Samsung Galaxy S II SGH-I777] twstd4lfe:
Thanks for the info...I went ahead and did the full restore just to be on the safe side and it went thru without a hitch