Hard bricked during CM9 upgrade from UCLD3 Leak?!
- Thread starter avus_m3
- Start date
I was told that refurb has a special sticker in addtion to the imei sticker to indicate refurbished.
Sent from my SGH-I777 using xda premium
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.
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.
SO, I also believe the serial number might say if the phone was refurbished.
You guys are making me wish I took mine to a service center instead of sending it to Mobile Tech Videos 
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
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
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.
Sent from my SGH-I777 using Tapatalk 2
Sent from my SGH-I777 using Tapatalk 2
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.
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.
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....
Sent from my SGH-I777 using XDA
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....
Sent from my SGH-I777 using XDA
Last edited:
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.
Sent from my SGH-I777 using xda premium
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.
Sent from my SGH-I777 using xda premium
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.
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
Sent from my SGH-I777 using xda premium
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
Sent from my SGH-I777 using xda premium
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.
Eheehe dooty
Sent from my SGH-I777 using xda premium
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!
Sent from my devil-powered all-knowing SGH-I777 using Tapatalk
Cm9 is the reason my dad left my mom when I was 10. Damn u cm9. Damn u.
Sent from my SGH-I777 using Tapatalk
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
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.
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.
